This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Modifying memory layout, possible?
- To: Gary Thomas <gthomas at redhat dot com>
- Subject: Re: [ECOS] Modifying memory layout, possible?
- From: Jesper Skov <jskov at redhat dot com>
- Date: Tue, 31 Oct 2000 15:54:34 +0100 (CET)
- Cc: Jesper Skov <jskov at redhat dot com>, ecos-discuss at sourceware dot cygnus dot com, jlarmour at redhat dot com, Andreas dot Karlsson at combitechsystems dot com
- References: <otlmv5qe1t.fsf@thinktwice.zoftcorp.dk><XFMail.20001031080629.gthomas@redhat.com>
>>>>> "Gary" == Gary Thomas <gthomas@redhat.com> writes:
Andreas> I thought that it was in hal_platform_setup.h but this script
Andreas> (PLATFORM_SETUP1)just runs when
Andreas> CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS is defined and it is not
>> This is wrong. The startup code should allow the target to run
>> with ROM startup, doing all the necessary initializations -
>> regardless of the inclusion/exclusion of the GDB stubs.
>>
Gary> Sorry, but on this and some other platforms, no can do :-( The
Gary> startup code moves memory around, and in some cases at least, it
Gary> would be very difficult to allow this code to run after this
Gary> remap had taken place.
Ah, good point. But still, the current code only executes when stubs
are included. That's wrong. In a production system you don't
(necessarily) want stubs to take up space.
So the condition should be:
#if !defined(CYG_HAL_STARTUP_RAM)
Preventing the code from screwing up a RAM based system.
Right?!? Or am I missing something else?
Jesper