Version 4.4

Corresponding Revisions of 4.4 and 4.3 are functionally identical, except the change from FLEXlm to TASKING License Management (TLM)

Version 3.1

November 2008
File Date Size Description
Apr 2018

Linker Script Language (LSL) Tips & Tricks for TASKING TriCore Toolset

This application note provides several helpful tips and tricks to help you benefit from the opportunities that LSL provides.

Download link

AP3211020_TC1796_Cookery_Book.pdf Jan 2009 12 MB

Starter Kit TC1796 for TASKING TriCore VX-toolset v2.3r1

AP3213320_TC1766_Starter-Kit_Cookery-Book_TASKING.pdf Jan 2009 14 MB

Starter Kit TC1766 for TASKING TriCore VX-toolset v2.3r1

AP3211720_TC1130_Cookery_Book.pdf Jan 2009 18 MB

Starter Kit TC1130 for TASKING TriCore VX-toolset v2.3r1

LSL-using-Control-Program.pdf Mar 2005 200 KB

LSL Sample Cases using Control Program

Demonstration of the usage of the Linker Script Language while using the TriCore toolchain to locate your application. It contains examples that deal with the most commonly used aspects of the language.

LSL-using-EDE.pdf Mar 2005 205 KB

LSL Sample Cases using EDE

Demonstration of the usage of the EDE's Script File page while using the TriCore toolchain to locate your application. It contains examples that deal with the most commonly used locating aspects.

an060-01.pdf Apr 2002 76 KB

Application Note: Setting Locator Options (v1.4r1 & v1.5r1)

This application note shows how the locator controls influence the locating process. It is intended both for EDE and command line tools users. After reading, the user should be able to configure the locating process and resolve possible errors that may result from applied settings and controls.

an060-02.pdf Apr 2002 60 KB

Application Note: The saturate type qualifier and integral types

This application note covers all aspects of using saturation with integral types.

This page contains TriCore compiler tips & tricks from our customer support staff.

Show help on tool errors

Show Help on Tool Errors is a feature that allows you to get more details/information about errors/warnings that are encountered during the build process.

To use this feature go to the menu 'Help | Show Help on Tool Errors...', a new Errors/Warnings window will pop up. Now double click on the error/warning within the 'Build' tab of the 'Output' window. Within the new window, a detailed description of the error/warning will appear, often accompanied with clarifying examples.

Template expansion for C/C++

Template expansion is available for C and C++ sources from version v1.5r1 or newer of the TriCore Toolchain. Template expansions are useful for taking the drudgery out of repetitive editing tasks. They are designed to insert frequently used text into files at the press of a button, or to automatically expand common statements used in programming languages when appropriate abbreviations are typed.

To activate template expansion, go to Customize | Language | Tab "Templates" and tick the option Template expansion.

The expansions are activate by the space bar, for example:

Typing #d followed by pressing the space bar will cause an expansion to #define

How can I minimize the impact of turning off a particular optimization?

Enabling and disabling optimizations for the complete project or one of its modules can have significant consequences. With the #pragma optimize instructions you are able to selectively enable/disable specific optimizations at source level, and obtain more fine-tuned result.

#pragma optimize [flags] Controls the amount of optimization. The remainder of the source line is scanned for option characters, which are processed like the flags of the -O command line option.

#pragma optimize restore End a region that was optimized with a #pragma optimize. The pragma optimize restore restores the situation as it was before the corresponding pragma optimize. #pragma optimize/optimize restore pairs can be nested.


#pragma optimize Y
#pragma optimize restore

In this example, the peephole optimization is turned off for the code that's between the #pragma optimize instructions.

After stepping into a function while debugging, how can I return quickly?

If you (accidentally) step into a function, you can return to the higher level by selecting the Run | Return from Function menu item.

Is there a way to handle repeated actions within CrossView Pro?

CrossView Pro fully supports macros. A macro is a user-created shorthand for any sequence of CrossView Pro or C commands and expressions. Macros can be used anywhere a CrossView Pro or C expression is valid. CrossView Pro also allows you to save macro definitions, so they are always available. By passing parameters to a macro, you can create powerful and flexible methods to debug your code more efficiently. To control the macros, go to Tools | Macro Definitions. Here you can define new macros, edit your existing macros and save them in a file.

There is also a feature to connect macros to a graphical toolbox. You can have this toolbox visible as a CrossView Pro window and use it to execute a macro by clicking a button.

Item File/Notes
Infineon miniWiggler

Debugger driver

The Infineon DAS driver for the miniWiggler are available from the TASKING site: 

Note that Infineon may make newer versions available on their own website. Please understand that these newer versions may not work with your toolset version though, so it is advised to keep a backup copy of your existing installation upon trying a new version.