From: Devraj Mukherjee <lugs@eternitytechnologies.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problem loading ELF image on LPD7A400
Date: Mon, 01 Nov 2004 13:15:14 +1100 [thread overview]
Message-ID: <41859C32.2060909@eternitytechnologies.com> (raw)
Hi everyone,
A bit more information from what we have been doing with U-Boot and the
LogicPD boards. We managed to compile the U-Boot images, tried to load
elf image using LogicLoader (that already comes on it) and here is what
we get.
Does anyone think the image that we made has something wrong with it?
The following is a dump of what happened. Thanks in advance for any advise.
Please note our versions of GCC/GlibC for ARM created using Kegel's scripts.
Regards,
Devraj
losh> load elf /tftp/10.0.1.2:u-boot
loading from /tftp/10.0.1.2:u-boot:
R............
elf file type : 0x0002
machine type: 0028 version: 1
prog start addr : 0xc1fc0000
num prog headers: 1
num sect headers: 23
offset : 0x00008000 disk length: 0x0001662c mem len: 0x0001aa30
phyaddr: 0xc1fc0000 vaddr : 0xc1fc0000 dl addr: 0xc1fc0000
ignoring rest of file...done
running md5sum on the _loaded_ portion of the file:
0d5cf2336110e4fcdc35b446b224f8f5 - addr: c1fc0000 len: 0001662c
losh> burn
unable to burn without a loaded flash image
--
----------------------------------------------------------------------
Devraj Mukherjee, Eternity Technologies Pty. Ltd. Australia
Host: Debian (Sarge) 3.1 Kernel 2.4.27-1-686 / GCC version 3.3.5
Target: LPD7A400 (ARM9) LogicPD eval. board / ARM GCC 3.3 GlibC 2.3.2
----------------------------------------------------------------------
next reply other threads:[~2004-11-01 2:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-01 2:15 Devraj Mukherjee [this message]
2004-11-01 8:52 ` [U-Boot-Users] Problem loading ELF image on LPD7A400 Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41859C32.2060909@eternitytechnologies.com \
--to=lugs@eternitytechnologies.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox