|
|||
| 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
The image structure
Input sections, output sections, regions, and Prog
Load view and execution view of an image
Methods of specifying an image memory map with the
Types of simple image
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
Image entry points
About specifying an initial entry point
Section placement with the linker
Placing sections with FIRST and LAST attributes
Section alignment with the linker
Demand paging
About ordering execution regions containing Thumb
Overview of veneers
Veneer sharing
Veneer types
Generation of position independent to absolute ven
Reuse of veneers when scatter-loading
Using command-line options to control the generati
About weak references and definitions
How the linker performs library searching, selecti
Controlling how the linker searches for the ARM st
Specifying user libraries when linking
How the linker resolves references
Use of the strict family of options in the linker
Using linker optimizations
Getting information about images
Accessing and managing symbols with armlink
Using scatter files
Linker User Guide
About specifying an initial entry point
| |||
| Home > Image structure and generation > About specifying an initial entry point | |||
You must specify at least one initial entry point for a program otherwise the linker produces a warning. Not every source file has to have an entry point. Multiple entry points in a single source file are not permitted.
For embedded applications with ROM at zero use --entry
0x0, or optionally 0xFFFF0000 for CPUs
that are using high vectors.
The initial entry point must meet the following conditions:
the image entry point must always lie within an execution region
the execution region must not overlay another execution region, and must be a root execution region (the load address is the same as the execution address).
If you do not use the --entry option to specify
the initial entry point then:
if the input objects contain only one entry point set by the
ENTRYdirective, the linker uses that entry point as the initial entry point for the imagethe linker generates an image that does not contain an initial entry point when either:
more than one entry point has been specified by using the
ENTRYdirectiveno entry point has been specified by using the
ENTRYdirective.
See also- Concepts
- Reference
| Copyright © 2007-2008, 2011-2012 ARM. All rights reserved. | ARM DUI 0377D |
| Non-Confidential | ID062912 |
 PDF version | |
| Home > Image structure and generation > About specifying an initial entry point |
ProductsDevelopment Tools |
Hardware & Collateral |
Downloads |
Support |
Buy |
|
 |
|||
