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: RAM vs. ROMRAM question


>>>What is the exact complaint you are getting?
>> 
>> That being a ROM monitor is a conflict with RAM startup but not
>> with ROMRAM startup.
>
> ecos.ecc:
>
> cdl_option CYGSEM_HAL_ROM_MONITOR {
>      # Flavor: bool
>      # No user value, uncomment the following line to provide one.
>      # user_value 0
>      # value_source default
>      # Default value: 0
>      # Requires:  CYG_HAL_STARTUP == "ROM" || CYG_HAL_STARTUP == "ROMRAM"

Exactly.  

It's been stated that it doesn't make sense for
CYGSEM_HAL_ROM_MONITOR to be set for RAM startup because
RedBoot would be loading apps into the RAM where RedBoot itself
is running.  

ROMRAM RedBoot runs in the exact same memory locations as RAM
RedBoot, so why doesn't that reasoning apply to ROMRAM startup?

-- 
Grant Edwards                   grante             Yow!  Is the EIGHTIES
                                  at               when they had ART DECO
                               visi.com            and GERALD McBOING-BOING
                                                   lunch boxes??

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