TASKING VX-toolset for TriCore v6.2r2
Release Note


This release note covers the changes between v6.2r1 and v6.2r2 of the TASKING VX-toolset for TriCore. Besides new content, release v6.2r2 also includes all fixes on release v6.2r1 which were released as patches between the release dates of v6.2r1 and v6.2r2. These patches are: v6.2r1p1, v6.2r1p2, v6.2r1p3, v6.2r1p4.

For release notes prior to v6.2r2, please visit the TASKING TriCore support website.


Important Notices

TriCore C Compiler changes

The changes in the TriCore C compiler between release v6.2r1p4 and release v6.2r2 are limited to a new compiler optimization and two fixed C compiler issues: TCVX-43383 and TCVX-43407.

RTOS and SWP to be discontinued

Release v6.2r2 includes the Pin Mapper, the TASKING RTOS and the iLLD Software Platform, collectively refered to as the AURIX Configuration Tools (ACT). The TASKING RTOS and the ILLD Software Platform are designated Bonusware (see the EULA). Support for those two ACT components will be discontinued after this release. They will no longer be maintained and will be removed from the product. The Pin Mapper will remain available.

DAS 6.0.0 support

The v6.2r2 was tested with DAS version 6.0.0 of Infineon. It can be downloaded from here. This version does not function properly with the new TC38x devices. Check the Infineon website for a DAS update for these devices.

New in v6.2r2

Project support for TC38x and TC39xB derivatives

With this release you can select the TC38x or TC39xB processor when building your application. You can make the selection from within the Eclipse IDE environment or from the command line by using the --cpu/-C option of the control program. The tools will automatically use the proper SFR files, linker script files, start-up code and libraries for the specified processor.

New TriCore compiler optimization for double word loads and stores

The TriCore C compiler has a new optimization which combines two consecutive single word loads or stores into one double word load or store. This optimization is highly effective when compiling the TASKING LAPACK Performance Libraries v1.0r2. User application code may also benefit from this optimization, especially in cases where array data processing loops are heavily used.

Pin Mapper support for TC38x and TC39xB devices

The Pin Mapper can now be used to configure TC38x and TC39xB devices. Supported packages are LFBGA292 and LFBGA516. Infineon's low-level drivers (iLLD) for these devices are not icluded. This implies that there is no Software Platform support for TC38x and TC39xB and that initialization code generated by the Pin Mapper can only be used in a context external to the product.

Support for the SCR on AURIX 2G devices

The 8051 (XC800) compiler supports the stand-by controller (SCR) of AURIX 2G. There are hardware differences with the SCR of AURIX which affect the compiler and the libraries. For a number of core SFR registers the hardware addresses have changed and some registers are no longer bit addressable. A new --core option has been added to the 8051 tools to specify the proper SCR version. New libraries have been added supporting the AURIX 2G SCR version.

Debugger performance improvement

The debugger's launch preparation time and download time of larger applications has been improved.

New hardware debug support

With this release, hardware debug support has been added for the following Infineon boards:

With some earlier versions of these boards there is a problem with the external watchdog timer, also known as the TLE35584 bug. This problem prevents the debugger to properly connect to and initialize the hardware. As a work-around, Infineon's 'memtool' can be used to disable the watchdog first, before connecting the debugger to the board.

Fixed issues in v6.2r2

Fixed Issues in v6.2r1 patch 4

Fixed Issues in v6.2r1 patch 3

Fixed Issues in v6.2r1 patch 2

Fixed Issues in v6.2r1 patch 1

The list of open issues for v6.2r2 can be found on the internet.

Quick start

For a quick start, just start the TriCore Eclipse IDE from the Start menu. This will start the Eclipse based development environment. You will be asked to select a workspace. In case you used Eclipse before it is recommended to select a new workspace. After clicking OK, you will see the 'Welcome' view. On this view you will see icons that link to specific information. You can, for example, select the 'Samples' icon and import the TriCore project examples, PCP project examples, MCS project examples, 8051 project examples and/or ARM example projects.

Another icon on the Welcome page, the 'First Steps' icon, links to the 'TriCore Getting Started' document. This is a good starting point for exploring the capabilities of the environment and the tools.

License Information

TASKING products are protected with TASKING license management software.

License key

You need a license key when you install a TASKING product on a computer. When you order a TASKING product from Altium or one of its distributors, a license key will be sent to you by email or on paper.

See the Getting Started with the TASKING VX-toolset for TriCore guide for information on obtaining a license.

Local TASKING License Server (not applicable to evaluation licenses)

If you have ordered a TASKING product with a floating license, you can have it serviced by the Remote TASKING License Server (the most convenient solution) or through a Local TASKING License Server (in case you have no external network access for example). Consult your Altium representative for assistance on deciding what the best setup would be for your situation.

If you like to setup up a local license server, we kindly refer you for more information to Support for TASKING License Management System (TLM) on our website. Here you can also download the Local TASKING License Server package.

It is advised that you install the Local TASKING License Server before you install products that require this server.