This is the mail archive of the ecos-discuss@sourceware.org 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]
Other format: [Raw text]

ROMRAM question


Hello,
I am running eCos on an Atmel AT91 target and I have a question about ROMRAM startup.

As I understand it, when I have built my application for a ROMRAM startup and programmed it into the flash memory on my target board, the application will boot up and copy itself into the SDRAM and continue running from there.

The question I have is this:  is there an 'easy' way (i.e built into the config tool perhaps) of not copying certain areas of my application into SDRAM ?   My application contains several large firmware images for supporting devices which do not need to live in SDRAM at run-time and are just read once when they are transferred to the appropriate device. These firmware images are essentially part of my eCos application and are held as a large table array of bytes.

Anyone know of an easy solution for achieving this ?

DJ.




Send instant messages to your online friends http://uk.messenger.yahoo.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


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