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]

Re: Seperate RedBoot and eCos application RAM blocks?


On Sun, Mar 05, 2006 at 10:30:36PM +0100, Reginald Deschrijver wrote:
> Hi all,
> 
> I have an ARM7 processor with 2 blocks of RAM, and one block of ROM.
> 
> The first RAM block is 4MB and starts at 0x02000000.
> The second RAM block is 64KB and starts at 0x03000000.
> 
> The ROM block is 2MB and starts at 0x08000000.
> 
> The problem I am having is that I wish to place Redboot ROM into the ROM
> area,
> and have the second RAM block of 64KB (0x03000000) allocated to the RAM
> resources Redboot needs,
> such as for GDB debugging support etc.
> And, I wish to assign the first RAM block of 4MB (0x02000000) only for
> the eCos application, and the malloc function used by the eCos
> application should only allocate RAM from this region.
> It is strictly forbidden that RedBoot resources are put into this RAM
> block.
> 
> I've tried to look at the memory files generated for other ARM7
> architectures, but the Redboot RAM and eCos RAM always seem to be on the
> same RAM block.

Redboot will be a ROM startup application. So it will use the
*_ROM.[h|ldi] in .../current/include/pkgconf.You application will be a
RAM startup so will use the _RAM.[h|ldi] files. You need to modify
these files to put your code and variables where you want them.

        Andrew

-- 
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]