This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Modifying memory layout, possible?
- To: Andreas dot Karlsson at combitechsystems dot com
- Subject: RE: [ECOS] Modifying memory layout, possible?
- From: Jesper Skov <jskov at redhat dot com>
- Date: Tue, 31 Oct 2000 15:56:42 +0100 (CET)
- Cc: jskov at redhat dot com, jlarmour at redhat dot com, ecos-discuss at sourceware dot cygnus dot com
- References: <2253171AF143D21185A60000F8FA748B0229AA7C@pluto.combitech.se>
>>>>> "Andreas" == Andreas Karlsson <Andreas.Karlsson@combitechsystems.com> writes:
>> There is a GUI for doing this, but it is only available on WinDOS.
Andreas> Where do I find this GUI and how to use it?
sources.redhat.com, I'm sure.
>> Changes in the memory layout has to be matched with appropriate
>> changes to the startup code. Arguably, it should be automatic, but
>> I suspect we didn't have the .h file when the AEB HAL was written.
Andreas> Where is the memory setup when using RAM-startup. For
Andreas> instance the START,STOP,SDR and BCR registers have to be
Andreas> given values but I just can't see where this is done for
Andreas> RAM-startup.
As Gary pointed out, it cannot be done from RAM startup. Or at least
you have to rewrite the code to do so, using position independant code
to do so.
Andreas> The warnings where gone when I modified target.ld but of
Andreas> course there was a big error after downloading since I hadn't
Andreas> defined, in BCR, which chip selects that should be used for
Andreas> the added memory. So the program was downloaded outside the
Andreas> addressable region.
You need to update the stub running on the board. The stub is the one
settin up the memory.
Jesper