TASKING VX-toolset for TriCore v6.3r1 patch 6
Release Note

Scope

This release note covers the changes between v6.3r1 and v6.3r1 patch 6 of the TASKING VX-toolset for TriCore.

For release notes prior to v6.3r1, please visit the TASKING TriCore support website.

Contents

Important Notices

Changed components

This patch contains changes to the following components:

Please note that the TriCore and ARM libraries (HSM) have been rebuilt. These libraries are also part of this patch.

Non EABI compliant bitfield offset used in a struct

Due to fixing issue TCVX-44802 Non EABI compliant bitfield offset used in a struct the alignment of a bitfield in a struct may change in your application after applying this patch. When linking with v6.3r1 objects not having this fix or cross-linking older objects (see the User Guide section 7.5. Cross-Linking), this might cause run-time problems due to the usage of different offsets for bitfield accesses.

To verify whether your application is impacted, please apply linker option --global-type-checking and ensure that all modules are compiled with --global-type-checking or --debug-info. When affected it will show the following linker error:

ltc E163:  redeclared with a different type

When this error shows up or you want to assure backward compatibility for bitfield alignment in a struct anyway, the fix for issue TCVX-44802 can be easily reverted by applying C compiler option: --mitigation=tcvx-44802.

Changed license manager component

For the executables with changed build numbers in this patch, the Altium license manager component (libmcrypt) has been replaced by the newly implemented TASKING license manager component (AES library by Dr Brian Gladman).

Added Open Source Software license files

The following Open Source Software license files have been added to the \doc\oss\ directory:

Build Numbers

For this patch, the following executable files have an updated build number: Build 22081062

All other executable files still have the original v6.3r1 build number: Build 19041558

Fixed Issues in v6.3r1p6

Fixed Problems

Fixed Problems in the ARM compiler (HSM)

Fixed Issues in v6.3r1p5

Fixed Problems

Fixed Problems in the ARM compiler (HSM)

Fixed Issues in v6.3r1p4

Fixed Problems

Fixed Issues in v6.3r1p3

Fixed Problems

Fixed Issues in v6.3r1p2

Fixed Problems

New Device Support

Fixed Issues in v6.3r1p1

Fixed Problems

New Device Support

Uninstalling the Patch

After installation of this patch, the directory backup_patch6 is present in the installation directory of the product.

  1. Copy the contents of directory backup_patch6 to the installation directory. This way you overwrite the files installed by the patch.
  2. Remove directory backup_patch6.

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 TASKING or one of its distributors, a license key will be sent to you by email or on paper.

See Obtaining a License on our website for more information.

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 TASKING 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.