 RealView Linker and Utilities Guide | |
| Home Products Events Support | |
On-Line Manuals
RealView Linker and Utilities Guide
Preface Introduction The Linker Command Syntax Using the Basic Linker Functionality Specifying the image structure
Building blocks for objects and images Load view and execution view of an image Specifying an image memory map Image entry points Section placement Ordering input sections by attribute Using FIRST and LAST to place sections Aligning sections Ordering execution regions containing Thumb code Optimizations and modifications Common debug section elimination Common group or section elimination Unused section elimination Unused function elimination Linker feedback RW data compression PI to absolute veneers Veneer generation Reuse of veneers with overlay execution regions Branch inlining Using command-line options to create simple images Type 1, one load region and contiguous execution r Type 2, one load region and non contiguous executi Type 3, two load regions and non contiguous execut Using command-line options to handle C++ exception Getting information about images Using image-related information Accessing Image Symbols Using Scatter-loading Description Files Using the ARM Librarian Using fromelfType 3, two load regions and non contiguous execution regions
  | |||
  |  | ||
| |||
| Home > Using the Basic Linker Functionality > Using command-line options to create simple images > Type 3, two load regions and non contiguous execution regions | |||
This type of image is similar to images of type 2 except that the single load region is now split into two load regions (see Figure 3.5).
Use the following command for images of this type:
armlink ‑‑split ‑‑ro‑base 0x8000 ‑‑rw‑base 0xE000
In the load view, the first load region consists of the RO output section, and the second load region consists of the RW output section. The ZI output section does not exist at load time. It is created before execution using the description of the output section contained in the image file.
In the execution view, the first execution region contains the RO output section and the second execution region contains the RW and ZI output sections.
The execution address of the RO region is the same as its load address, so the contents of the RO output section do not have to be moved or copied from their load address to their execution address. Both RO and RW are root regions.
The execution address of the RW region is also the same as its load address, so the contents of the RW output section are not moved from their load address to their execution address. However, the ZI output section is created before execution begins and placed after the RW region.
Specify the load and execution address using the following linker options:
‑‑splitSplits the default single load region (that contains both the RO and RW output sections) into two load regions (one containing the RO output section and one containing the RW output section) so that they can be placed separately using
‑‑ro‑baseand‑‑rw‑base.‑‑ro‑baseaddressInstructs armlink to set the load and execution address of the region containing the RO section at a four-byte aligned
address‑‑ro‑baseoption to specify the address, the default value of0x8000is used by armlink.
‑‑rw‑baseaddressInstructs armlink to set the execution address of the region containing the RW output section at a four-byte aligned
address‑‑split, this specifies both the load and execution addresses of the RW region, for example, it is a root region.
| Copyright © 2007 ARM Limited. All rights reserved. | ARM DUI 0377A |
 PDF version | |
| Home > Using the Basic Linker Functionality > Using command-line options to create simple images > Type 3, two load regions and non contiguous execution regions | |
| |
| Contact Site Map Press Privacy | Copyright © 2008 Keil™, An ARM® Company. All rights reserved. |
