This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: RE: EB40a: Linking application for flash
- From: Ketil Harald Ruud <ketil dot ruud at kitron dot com>
- To: 'Andrew Lunn ' <andrew dot lunn at ascom dot ch>
- Cc: "'ecos-discuss at sources dot redhat dot com'" <ecos-discuss at sources dot redhat dot com>
- Date: Thu, 10 Jul 2003 15:35:05 +0200
- Subject: RE: [ECOS] RE: EB40a: Linking application for flash
I have obviously used a wrong binary format for the intermediate storage in
external ram.
When I converted the file using objcopy -O and used this output for loading,
everything worked fine.
Thank you.
Ketil
-----Original Message-----
From: Andrew Lunn
To: Ketil Harald Ruud
Cc: 'Øyvind Harboe '; 'ecos-discuss@sources.redhat.com'
Sent: 7/10/03 1:41 PM
Subject: Re: [ECOS] RE: EB40a: Linking application for flash
On Thu, Jul 10, 2003 at 01:27:42PM +0200, Ketil Harald Ruud wrote:
>
> I have done everything as you suggest, but get the same result.
> However, I realize that the linking is not the problem since objdump
> (disassable) is saying that the code starts at address 0x1040000 as
> expected.
>
> The problem arises when I try to load the file to the external memory
before
> flashing. I do the following (RedbootROM is running):
>
> RedBoot> load -r -m ymodem -b 0x2000000
> (use minicom/ymodem to load the ecosROM file a.out)
> RedBoot> dump -b 0x2000000 -l 0x200 -4
What exactly are you uploading? the elf? A binary produced using
objcopy -O binary?
Im assuming the latter.
> The expected file content is not showing up, but if I change the dump
> address to 0x2008000 I find what I expect.
Use od and take a look at the beginning of the file. Does it have
0x8000 of 0's at the beginning?
Andrew
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss