ARM Compiler toolchain Using the Linker - ARM Information Center

0x00000200 0x00000010 Code RO 3 sec3 sections.o
0x00000210 0x00000004 Code RO 4 sec4 sections.o
0x00000214 0x00000004 Code RO 5 sec5 sections.o
0x00000218 0x00000004 Code RO 6 sec6 sections.o
Execution Region ER_3 (Base: 0x00000300, Size: 0x00000014, Max: 0x00000020, ABSOLUTE)
Base Addr Size Type Attr Idx E Section Name Object
0x00000300 0x00000014 Code RO 2 sec2 sections.o
8.15.1 See also
In this example:
Using scatter files
• The linker places sec1 in ER_1 because ER_1 has the most specific selector. ER_1 now has
0x6 bytes remaining.
• The linker then tries to place sec2 in ER_1, because it has the most specific selector, but
there is not enough space. Therefore, ER_1 is marked as full and is not considered in
subsequent placement steps. The linker chooses ER_3 for sec2 because it has higher
priority than ER_2.
• The linker then tries to place sec3 in ER_3. It does not fit, so ER_3 is marked as full and the
linker places sec3 in ER_2.
• The linker now processes sec4. This is 0x4 bytes so it can fit in either ER_1 or ER_3. Because
both of these sections have previously been marked as full, they are not considered. The
linker places all remaining sections in ER_2.
• If another section sec7 of size 0x8 exists, and is processed after sec6 the example fails to
link. The algorithm does not attempt to place the section in ER_1 or ER_3 because they have
previously been marked as full.
Concepts
• Placing unassigned sections with the .ANY module selector on page 8-25
• Examples of using placement algorithms for .ANY sections on page 8-28.
Linker Reference:
• How the linker resolves multiple matches when processing scatter files on page 4-26
• Behavior when .ANY sections overflow because of linker-generated content on page 4-28.
Reference
Linker Reference:
• --any_placement=algorithm on page 2-9
• --scatter=file on page 2-142.
ARM DUI 0474C Copyright © 2010-2011 ARM. All rights reserved. 8-31
ID080411 Non-Confidential