This is the mail archive of the ecos-discuss@sources.redhat.com 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]

RE: Modifying memory layout, possible?


> >>>>> "Andreas" == Andreas Karlsson 

> <Andreas.Karlsson@combitechsystems.com> writes:

> 

> Andreas> Hello, I'm wondering if it is possible to run eCos after

> Andreas> adding more memory, in any case it seems to be hard to edit

> Andreas> the memory layout, which is a bad feature for eCos.

> 

> There is a GUI for doing this, but it is only available on WinDOS.



Where do I find this GUI and how to use it?



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

> 

Where is the memory setup when using RAM-startup. For instance the
START,STOP,SDR and BCR registers have to be given values but I just can't
see where this is done for RAM-startup.



> Andreas> How can I tell eCos that there are more memory available so I

> Andreas> can get rid of those ".bss is not within region RAM"?

> 

> Maybe the linker map doesn't have the right dependencies. Did you try

> creating a new build directory after updating the .ldi and .h files?



No, I didn't. 

The warnings where gone when I modified target.ld but of course there was a
big error after downloading since I hadn't defined, in BCR, which chip
selects that should be used for the added memory. So the program was
downloaded outside the addressable region.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]