|
|||||||||||
Technical Support On-Line Manuals Linker User Guide ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Image entry points
3.1.5 Image entry pointsAn entry point in an image is the location that is loaded into the PC. It is the location where program execution starts. Although there can be more than one entry point in an image, you can specify only one when linking. Not every ELF file has to have an entry point. Multiple entry points in a single ELF file
are not permitted.
NoteFor embedded Cortex-M programs, the program starts at whatever value is loaded into the PC from the Reset vector. Typically, the Reset vector points to the CMSISReset_Handler function.Types of entry pointThere are two distinct types of entry point:
The initial entry point for an imageThere can be only one initial entry point for an image, otherwise linker warning The initial entry point must meet the following conditions:
If you do not use the
--entry option to specify the initial entry point
then:
For embedded applications with ROM at zero use
--entry , or optionally
for processors that are using high vectors.Related conceptsRelated reference | ||||||||||
|
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.