SPRAD49 January 2023 F29H850TU , F29H859TU-Q1 , TMS320F2800132 , TMS320F2800133 , TMS320F2800135 , TMS320F2800137 , TMS320F2800152-Q1 , TMS320F2800153-Q1 , TMS320F2800154-Q1 , TMS320F2800155 , TMS320F2800155-Q1 , TMS320F2800156-Q1 , TMS320F2800157 , TMS320F2800157-Q1 , TMS320F280021 , TMS320F280021-Q1 , TMS320F280023 , TMS320F280023-Q1 , TMS320F280023C , TMS320F280025 , TMS320F280025-Q1 , TMS320F280025C , TMS320F280025C-Q1 , TMS320F280033 , TMS320F280034 , TMS320F280034-Q1 , TMS320F280036-Q1 , TMS320F280036C-Q1 , TMS320F280037 , TMS320F280037-Q1 , TMS320F280037C , TMS320F280037C-Q1 , TMS320F280038-Q1 , TMS320F280038C-Q1 , TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-Q1 , TMS320F280040-Q1 , TMS320F280040C-Q1 , TMS320F280041 , TMS320F280041-Q1 , TMS320F280041C , TMS320F280041C-Q1 , TMS320F280045 , TMS320F280048-Q1 , TMS320F280048C-Q1 , TMS320F280049 , TMS320F280049-Q1 , TMS320F28374D , TMS320F28375D , TMS320F28376D , TMS320F28377D , TMS320F28377D-EP , TMS320F28377D-Q1 , TMS320F28378D , TMS320F28379D , TMS320F28379D-Q1 , TMS320F28384D , TMS320F28384D-Q1 , TMS320F28384S , TMS320F28384S-Q1 , TMS320F28386D , TMS320F28386D-Q1 , TMS320F28386S , TMS320F28386S-Q1 , TMS320F28388D , TMS320F28388S , TMS320F28P650DH , TMS320F28P650DK , TMS320F28P650SH , TMS320F28P650SK , TMS320F28P659DH-Q1 , TMS320F28P659DK-Q1 , TMS320F28P659SH-Q1
Linker command files play an important role in embedded programs as they specify where code and data sections get allocated into target memory. Without this file, the linker does not know the target memory configuration and how to properly allocate the sections. For C2000™ real-time controllers, you have to understand the device memory by reviewing the device-specific data sheet and technical reference manual. Example C2000 linker command files are available in C2000Ware SDK but for any given application, you might have to modify the template linker command files available in the C2000Ware SDK to fit your application needs. This requires that you to learn the syntax and options available when writing a linker command file. The C2000 Linker CMD Tool simplifies the task of creating application-specific linker command files by providing an intuitive GUI and automatic code generation.
C2000™ and Code Composer Studio™ are trademarks of Texas Instruments.
All trademarks are the property of their respective owners.
The linker command file is used during the link stage of the application build where the linker combines object files and allocates sections into the target system's configured memory. The linker command file is an ASCII file that uses two linker directives, MEMORY and SECTIONS, to allocate sections into specific areas of memory. The MEMORY directive defines target memory configuration. The SECTIONS directive controls how sections are built and allocated. In addition, the linker command file can also include input filenames and linker options.
The Linker Command File Primer page covers the basics of linker command files, focusing on the MEMORY and SECTIONS directives.
Creating a new linker command file from scratch or even editing an existing linker command file template can be difficult for new users. Users must understand the structure of linker command files along with their specific device’s memory structure.
The C2000 Linker CMD Tool significantly simplifies the task of creating new or editing existing linker command files by providing the following features:
Utilizing the C2000 Linker CMD tool can speed up the software development for new and advanced users.
The C2000 Linker Command Tool is a SysConfig-based product that is seamlessly integrated in C2000 System Configuration Tool.
For more information on the C2000 System Configuration Tool visit:
Video Series:
Benefits of C2000 SysConfig:
Application report - step by step guide for using C2000 SysConfig:
SW getting started Guide:
In order for developers to use the C2000 Linker CMD Tool, they must launch the C2000 SysConfig tool for their given device and package. C2000 SysConfig walks you through the steps needed to launch the C2000 SysConfig tool both in the context of a Code Composer Studio project as well as the SysConfig standalone tool.
The C2000 Linker Command Tool is shown in Figure 2-1.
Once a CMD module is added, additional files are generated by the tool.
Note that you can add more than one CMD module. All the different instances of the CMD module can be saved within the syscfg file. You can decide which one of the CMD modules is active by selecting it in the Global Parameters.
Each instance of the CMD module has the following entries: