User manual

Raisonance Tools for ARM 4. Creating a project
4.4.2 LD linker options
The LD Linker provides various options:
• General
• Startup
• Scripts
• Libraries. Ride7 provides some libraries which you can
choose to include (or not) by (un)selecting the
corresponding options.
• More
• C++ applications (RKit-ARM Enterprise version only).
When you are using the Thumb instruction set, or Interworked
mode, the libraries used are the corresponding Thumb libraries.
Thumb libraries have the same name as the non-thumb libraries,
with _thumb appended.
4.4.2.1 General
Generate MAP file: Makes the Linker produce a map file (.MAP).
Warn once for undefined symbols: If checked, only one warning is displayed for each undefined
symbol, rather than once per module which refers to it.
Remove unused sections: If checked, the linker does not link the sections that are not used. Activate
this together with the GCC Compiler option Per function sections in order to have the linker remove
any unused function from the application.
4.4.2.2 Startup
Default startup: Set to Yes to use the default startup file. Set to No to use your own startup file.
Startup File: Indicate the path of your own startup file (or not if your startup file is part of the source
files). You can see the default startup and linker script files provided by Ride7 in the directory <Ride>\lib
(which you can copy and modify).
Use GCC Startups: The default option No adds the '-nostartfiles' switch to the linker command line.
That removes the standard GCC startups, which are not usually required in embedded C applications
and might interfere with the startup provided by Ride7 or the chip manufacturer (or at least adds useless
code). However, these files must be included for C++ applications because they hold some constructors
that are required.
4.4.2.3 Scripts
Use Default script file: Set to Yes to use the default script file. Set to No to use your own script file,
and fill in the Script File box (you must use a linker script).
Script file: Indicate the path of the linker script file that you want to use.
• The linker script (in several parts) is generated just before the link. If you want to see the script
used for your application, just link your project and look in the application's directory for the
associated script file. For example, if your application is called MyApplication.elf, the script
generated is called MyApplication.elf.ld.
This primary script is generated at each link, and includes the input files, output files, and main
linker script, which is either the default or the custom linker script that you specified using the
Script File option.
The main default script includes three sub-scripts.
• The virtual device STRx-TEST has no default linker script, therefore you must use a custom
linker script when you use this device.
- 17 -