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: memory maps, linker control files, etc.


>> So the ROMRAM or RAM versions of redboot cannot be used to load and debug
>> ECOS programs? I don't remember reading that anywhere. But of course I've
>> been reading so much new stuff, I may have not have noticed it.
>
>Not correct.  ROMRAM is used for RedBoot (or any monitor) and is 
>perfectly suited for loading RAM programs.  RAM mode is designed for
>general eCos applications.
>
>The ROMRAM and RAM loader templates (.ldi files) are structured so that
>memory used by one does not conflict with the other.  In most cases, 
>ROMRAM uses a chunk of low memory and RAM version are allowed to use
>everything else.

Let's see if I've got this straight:

1. The ROMRAM and RAM memory "loader templates" don't interfere, so a ROMRAM
monitor can be used to load/debug a RAM ECOS program.

2. The ROM and RAM memory "loader templates" don't interfere, so a ROM
monitor can be used to load/debug a RAM ECOS program.

3. Because the "loader templates" interfere, a ROMRAM monitor cannot be used
to load/debug a ROMRAM ECOS program.

4. Because the "loader templates" interfere, a ROM monitor cannot be used to
load/debug a ROMRAM ECOS program.

5. The "loader template" consists of the .ldi file and the memory layout
header file, both in the same folder. The value of HAL_STARTUP determines
which "loader template" to use.

Correct?

- Andy


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