This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: The basics


> RAM/ROM?  Could you provide more details?  Use the same offsets, make it
> PIC?

Some of the HALs support ROMRAM. The application lives in ROM, but
once the platform has been initialized and RAM is available, the
application copies itself into RAM and runs from there. You don't need
to worry about PIC for 99% of the code. The main image is linked with
its RAM address. You have to be careful with the startup code since
that is linked to its RAM address, but runs at its ROM address.
Luckily, in the ARM, this code is PIC, and you only have to worry
about it getting the first jump in the reset vector correct. 

Now, redboot is just an eCos application. So anything eCos can do,
redboot can also do. I build redboot to use ROMRAM start. I know i can
do whatever i want to the flash and redboot wont be affected because
its in RAM. 

The AT91 is one example platform to look at.

    Andrew


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]