This release note covers the changes between v6.1r1 and v6.2r1 of the TASKING VX-toolset for TriCore.
For release notes prior to v6.2r1, please visit the TASKING TriCore support website.
The v6.2r1 has been tested with the latest DAS version 6.0.0 of Infineon. No problems have been found. It is recommended to use DAS 6.0.0 with TriCore v6.2r1. Download here.
This section gives an overview of the most important new features and improvements in v6.2r1. See the sections with fixed issues for a complete list.
MISRA C:2012 Amendment 1 sets out a number of additional guidelines to improve the coverage of the security concerns, highlighted by the ISO C Secure Guidelines. Several of these address specific issues pertaining to the use of untrustworthy data, a well-known security vulnerability. Most of these additional rules for secure coding practices are supported now in this release.
The Memory Protection Unit (MPU) that is present in several TriCore derivatives uses Memory Protection Register Sets. Each register set specifies memory protection ranges and permissions for code and data.
Within some multi-core automotive applications it is required to partition code and data into different safety groups based on ISO 26262 ASIL levels. Safety groups have to be isolated from each other: bugs in low-safety-level code should not effect high-safety-level data, and high-safety-level code should not depend on low-safety-level code. So, low-safety-level code is not allowed to write in high-safety-level data sections, and high-safety-level code is not allowed to call low-safety-level functions. The safety groups are defined in the Linker Script Language (LSL).
For AURIX derivatives the linker supports a new feature to generate information to set up the MPU for a specific application, based on the safety group definitions and the locate result of the application (safety class 0 cannot be used in this context).
For detailed information see section 7.9.12. "MPU Configuration Data" in the TASKING VX-toolset for TriCore User Guide.
This release supports the TriCore EABI v3.0, which has now been officially released by Infineon.
In EABI V3.0 the requirements of structure alignment have changed (section 18.104.22.168 Unions and Structures).
Conforming to this EABI structure alignment breaks compatibility with previous releases, it requires re-compilation of all sources including libraries. It also may result in run-time errors when linking objects that use different alignment implementations of structures.
An EABI compatibility option is made to switch between TASKING structure alignment and EABI compatible structure alignment: --eabi=+word-struct-align. With the 'word-struct-align' flag set, structures and unions with a size >= 64-bit get a minimum word alignment, to guarantee penalty free performance of double word copy with instructions ld.d and st.d. This may result in additional padding.
The following option has been extended with the W flag: -eabi-compliant is an alias for --eabi=CFHNSW.
The latest version of the simulator from Infineon, TSIM v1.17.11, is included in this release.
The PCP simulator has been upgraded too. TSIM v1.40 is included in this release.
The Integrated Safety Checker (ichk) has been extended with support for XML output. Option -Tx --output-type=xml has been added for this.
The list of open issues for v6.2r1 can be found on the internet.
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.
TASKING products are protected with TASKING license management software.
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.
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.