APPLICATION
NOTE
LINKER SCRIPT LANGUAGE (LSL)
TIPS & TRICKS FOR TASKING TRICORE TOOLSET
INTRODUCTION
The TASKING
®
Linker/Loader in the VX-toolset for TriCoreTM is a very feature rich tool, oering many helpful func-
tionalities to create an ecient application. For example, it provides optimization options, it supports multi-core
development and incremental linking, and it can be steered through an advanced Linker Script Language (LSL).
This LSL is a very powerful language, used by many of our customers to optimize their application to their specic
needs.
This document provides several helpful tips and tricks to help you benet from the opportunities that LSL pro-
vides. Our support sta has worked with many of our users on LSL tuning and collected frequently used hints for
this tips and tricks overview. We believe you can also learn from these hints and become an LSL expert. If you have
any questions or maybe other suggestions/hints, please don’t hesitate to contact us through support@tasking.
com.
For detailed information about the linker and LSL we refer to the User Manual, chapter 7 Using the Linker, 10.5
Linker Options and 16 Linker Script Language (LSL).
LSL CODE CORE ASSOCIATION AND DATA CORE ASSOCIATION
The TASKING TriCore tools feature the language extensions __share, __private0, __private1, __private2
and __clone to assign a code section or data section to core local memory. You can achieve the same goal with
the following pragmas:
#pragma code_core_association share | private{012} | clone
#pragma data_core_association share | private{012} | clone
This method inuences the section name that the linker uses to assign the section appropriately. To do so, the linker
adds the core association name to the section name. E.g. .bss.private1.module_name.variable_name for a non
initialized variable which must be placed in core 1 local memory.
When the C source code is not available (e.g. because a 3rd party library is used or an object le is already certied
and thus the C source may not be modied) the core assignment using the above mentioned C language extensions
or the pragma is no longer possible. To assign a section to a dierent core, you can use the linker LSL language
keyword ‘modify input’.
For the following C code, compiled with default options but with -N0 for no default near allocation of variables, the
variable my_var_1 will be placed in section .bss.le_1.my_var_1 and the code for init_func will be placed in
section .text.le_1.init_func.
le_1.c
int my_var_1;
void init_func(void);
void main(void)
{
init_func();
while(1)
{
__nop();
}
}
void init_func(void)
{
my_var_1 = 0x1234;
}
