This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Redboot run image issues
- From: Gary Thomas <gary at mlbassoc dot com>
- To: joseph biswal <joseph dot biswal at gmail dot com>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Sat, 21 Feb 2009 05:15:53 -0700
- Subject: Re: [ECOS] Redboot run image issues
- References: <6aca9e460902202121s62a5eda0hf01d29215ca4640e@mail.gmail.com>
joseph biswal wrote:
> Hi ALl;
> I am working on the MX31 platform wijht ARM 11 core.
> When i run the image from RAM from another image, its stops after
> printing this :
> load entry_address=0x100000
> virt_addr=0x100000
> phys_addr=0x80100000
>
> Heres a snapshot.
>
> RedBoot> load -r -b 0x100000 /redboot.0220
> Using default protocol (TFTP)
> Raw file loaded 0x00100000-0x0012bc13, assumed entry at 0x00100000
> RedBoot> run 0x100000
> load entry_address=0x100000
> virt_addr=0x100000
> phys_addr=0x80100000
>
>
> Would it be something to do with the image size or linker script?
> I have ensured that my target.ld and mlt_romram.h are correct for the
> ROM addresses
> Thansks in advance for your help.
>
What sort of an image is 'redboot.0220'? Most times, the
files we load to execute are either ELF binary images, or
Motorola S-record files. In both of these cases, the '-r'
option should *not* be used.
My [first] guess is that you've loaded some sort of structured
file (ELF, S-record) using '-r' which will not get the correct
instructions in the correct location, hence not run.
Try it without '-r'
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss