This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: redboot over VxWorks
- From: David Vrabel <dvrabel at arcom dot com>
- To: Andrew Lunn <andrew at lunn dot ch>
- Cc: Nickolay <nickolay at protei dot ru>, ecos-discuss at ecos dot sourceware dot org
- Date: Mon, 10 Jan 2005 12:37:47 +0000
- Subject: Re: [ECOS] redboot over VxWorks
- References: <41E26D8E.7080505@protei.ru> <20050110120619.GE11664@lunn.ch>
Andrew Lunn wrote:
eCos image are position dependant. It has to be loaded at the address
it expects to be loaded. You can then execute it by jumping to the
first instruction.
Take a look at the .ldi file in the hal includes/pkgconf for your
target.
I find it easiest to look at the redboot.elf with objdump rather than
ferreting around in linker scripts.
$ arm-elf-objdump --all redboot.elf
...
start address 0x00400040
Program Header:
LOAD off 0x00008000 vaddr 0x00400000 paddr 0x00400000 align 2**15
...
i.e., load the .bin at 0x400000 and start at 0x400040.[*]
You may even find that the VxWorks loader understands the ELF format and
will automatically load an ELF image into the correct locations. If
that's the case then just load redboot.elf and ignore redboot.bin.
David Vrabel
[*] You'll probably find that your .bin loads and starts at the same
position. I think I've messed something up in my linker script...
--
David Vrabel, Design Engineer
Arcom, Clifton Road Tel: +44 (0)1223 411200 ext. 3233
Cambridge CB1 7EA, UK Web: http://www.arcom.com/
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss