Keil Logo

Technical Support

On-Line Manuals

Linker User Guide

Preface Overview of the Linker Linking Models Supported by armlink Image Structure and Generation Linker Optimization Features Getting Image Details Accessing and Managing Symbols with armlink Scatter-loading Features Scatter File Syntax BNF notation used in scatter-loading description s Syntax of a scatter file Load region descriptions Components of a load region description Syntax of a load region description Load region attributes Inheritance rules for load region address attribut Inheritance rules for the RELOC address attribute Considerations when using a relative address +offs Execution region descriptions Components of an execution region description Syntax of an execution region description Execution region attributes Inheritance rules for execution region address att Considerations when using a relative address +offs Input section descriptions Components of an input section description Syntax of an input section description Examples of module and input section specification Expression evaluation in scatter files Expression usage in scatter files Expression rules in scatter files Execution address built-in functions for use in sc ScatterAssert function and load address related fu Symbol related function in a scatter file AlignExpr(expr, align) function GetPageSize() function SizeOfHeaders() function Example of aligning a base address in execution sp Scatter files containing relative base address loa Linker Command-line Options Linker Steering File Command Reference Via File Syntax

Syntax of an execution region description

8.4.2 Syntax of an execution region description

An execution region specifies where the input sections are to be placed in target memory at run-time.

The syntax of an execution region description, in Backus-Naur Form (BNF), is:
execution_region_description ::= 
  exec_region_name (base_address | "+" offset) [attribute_list] [max_size | length]
        "{" 
            input_section_description* 
        "}"
where:
exec_region_name
Names the execution region. You can use a quoted name. The name is case-sensitive only if you use any region-related linker-defined symbols.
base_address
Specifies the address where objects in the region are to be linked. base_address must be word-aligned.

Note

Using ALIGN on an execution region causes both the load address and execution address to be aligned.
+offset
Describes a base address that is offset bytes beyond the end of the preceding execution region. The value of offset must be zero modulo four.
If this is the first execution region in the load region then +offset means that the base address begins offset bytes after the base of the containing load region.
If you use +offset, then the execution region might inherit certain attributes from the parent load region, or from a previous execution region within the same load region.
attribute_list
The attributes that specify the properties of the execution region contents.
max_size
For an execution region marked EMPTY or FILL the max_size value is interpreted as the length of the region. Otherwise the max_size value is interpreted as the maximum size of the execution region.
[–]length
Can only be used with EMPTY to represent a stack that grows down in memory. If the length is given as a negative value, the base_address is taken to be the end address of the region.
input_section_description
Specifies the content of the input sections.

Note

The BNF definitions contain additional line returns and spaces to improve readability. They are not required in scatter-loading descriptions and are ignored if present in a scatter file.
Non-ConfidentialPDF file icon PDF versionARM DUI0377H
Copyright © 2007, 2008, 2011, 2012, 2014-2016 ARM. All rights reserved. 
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.