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: Multiple non-consecutive RAM regions


Tord.Andersson@combitechsystems.com writes:

[...]

> I plan to instruct the linker to place some of the object files 
> text in a new text2 segment. Would target.ld be the right file to modify 
> with something like this:
> 
> SECTIONS {
> .text2 : { Gr*(.text) }
> ... 

If you do this, I think you'll get problems when converting your ELF image into
a binary image because the gap between the two regions will appear in the binary
image. If you can fit every output sections with the LOAD flag in your first
memory region (and the .bss section if it fits too), then you can just modify the
definition of your __heap1 symbol to start at the beginning of your second RAM
region. The configuration tool should let you do this.

If your .bss section doesn't fit in your first RAM region then move it to your
second RAM region and the __heap1 symbol will follow it automatically.

All this implies that at least the .rom_vectors, .text, .rodata and .data sections
must fit in your first RAM region.

Robin


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