|
|||
| Products Download Events Support Videos | |||
Technical Support
On-Line Manuals
Linker User Guide
Conventions and feedback
Overview of the linker
Linking models supported by armlink
Image structure and generation
Using linker optimizations
Getting information about images
Accessing and managing symbols with armlink
Using scatter files
About scatter-loading
When to use scatter-loading
Scatter-loading command-line option
Images with a simple memory map
Images with a complex memory map
Linker-defined symbols that are not defined when s
Specifying stack and heap using the scatter file
What is a root region?
Creating root execution regions
Using the FIXED attribute to create root regions
Placing functions and data at specific addresses
Placing a named section explicitly using scatter-l
Placing unassigned sections with the .ANY module s
Examples of using placement algorithms for .ANY se
Example of next_fit algorithm showing behavior of
Examples of using sorting algorithms for .ANY sect
Selecting veneer input sections in scatter-loading
Using __attribute__((section("name"))) t
Using __at sections to place sections at a specifi
Restrictions on placing __at sections
Automatic placement of __at sections
Manual placement of __at sections
Placing a key in flash memory using __at
Placing a structure over a peripheral register usi
Placement of sections with overlays
About placing ARM C and C++ library code
Example of placing code in a root region
Example of placing ARM C library code
Example of placing ARM C++ library code
Example of placing ARM library helper functions
Reserving an empty region
About creating regions on page boundaries
Overalignment of execution regions and input secti
Using preprocessing commands in a scatter file
Expression evaluation in scatter files
Using expression evaluation in a scatter file to a
Equivalent scatter-loading descriptions for simple
Type 1 image, one load region and contiguous execu
Type 2 image, one load region and non-contiguous e
Type 3 image, two load regions and non-contiguous
Scatter file to ELF mapping
Linker User Guide
Selecting veneer input sections in scatter-loading descriptions
| |||
| Home > Using scatter files > Selecting veneer input sections in scatter-loading descriptions | |||
Veneers are used to switch between ARM and Thumb code or to
perform a longer program jump than can be specified in a single
instruction. You can place veneers at a specific location by including
the linker-generated symbol Veneer$$Code in a
scatter file. At most, one execution region in the scatter file
can have the *(Veneer$$Code) section selector.
If it is safe to do so, the linker places veneer input sections
into the region identified by the *(Veneer$$Code) section
selector. It might not be possible for a veneer input section to
be assigned to the region because of address range problems or execution
region size limitations. If the veneer cannot be added to the specified
region, it is added to the execution region containing the relocated
input section that generated the veneer.
Note
Instances of *(IWV$$Code) in scatter files
from earlier versions of ARM tools are automatically translated
into *(Veneer$$Code). Use *(Veneer$$Code) in
new descriptions.
*(Veneer$$Code) is ignored when the amount
of code in an execution region exceeds 4Mb of Thumb code, 16Mb of
32-bit Thumb code, and 32Mb of ARM code.
See also- Concepts
| Copyright © 2007-2008, 2011-2012 ARM. All rights reserved. | ARM DUI 0377D |
| Non-Confidential | ID062912 |
 PDF version | |
| Home > Using scatter files > Selecting veneer input sections in scatter-loading descriptions |
ProductsDevelopment Tools |
Hardware & Collateral |
Downloads |
Support |
Buy |
|
 |
|||
