RE: [ECOS] RE: Running a program from

[Gary Thomas <gthomas at redhat dot com>]

On 24-Aug-2001 Trenton D. Adams wrote:
> I know, my outlook screwed up.  eCos Discussion was supposed to be the
> first one in my list, but Outlook seems to like to change that once in
> awhile.  Don't know if you received it yet or not, but I did send an
> apology already! :)  I also reposted it to the eCos Discussion list!
> 
> Linker script?  I assume you mean my Makefile?  Nope, didn't even think
> about changing the entry point if that's what you mean!
> 
> I have now changed my GCC line to contain "-Wl,--entry=0xe0040000".  Is
> that what you mean?
> 
> Still doesn't work.

Alternative to making this a ROM program, you can leave it as RAM startup
and just keep the image in FLASH.  Then use RedBoot to load it into RAM
before startup.

An example of this is the RAM based RedBoot we provide, which is normally
kept in FLASH as RedBoot[backup].  See the RedBoot manual for examples and
some further discussion.

> 
> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com
> [mailto:ecos-discuss-owner@sources.redhat.com] On Behalf Of Gary Thomas
> Sent: Friday, August 24, 2001 11:15 AM
> To: Trenton D. Adams
> Cc: eCos Discussion
> Subject: [ECOS] RE: Running a program from
> 
> 
> Firstly - don't send messages to ecos-maintainers use ecos-discuss.
> 
> On 24-Aug-2001 Trenton D. Adams wrote:
>> I do the following after loading my image into redboot at 0x20000.
> I'm
>> not running a RAM version of RedBoot so this should be ok at 0x20000
>> right?
>> RedBoot> fis create -b 0x20000 -l 0x64700 -f 0xe0040000 RigSystem
>> ... Erase from 0xe0040000-0xe00c0000: ....
>> ... Program from 0x00020000-0x00084700 at 0xe0040000: ....
>> ... Erase from 0xe0fe0000-0xe1000000: .
>> ... Program from 0x00fa7000-0x00fc7000 at 0xe0fe0000: .
>> RedBoot> go 0xe0040000
> 
> Was this program configured for ROM startup?  Did you adjust the
> linker script so that it would run from 0xE0040000?