TASKING VX-toolset for TriCore v4.1r2
Release Note

Scope

This release note covers the changes between v4.1r1 and v4.1r2 of the TASKING VX-toolset for TriCore.

For release notes prior to v4.1r2, please visit the TASKING TriCore support website.

Contents

Important Notices

DAS no longer installed

Due to the fact that Infineon's DAS drivers might cause instabilities in the drivers and the system, the drivers are no longer included in the installation. Besides this the latest DAS installation package did take (up to 45) minutes before installation was ready. Therefore in agreement with Infineon we decided to no longer distribute the DAS package with the TASKING product. Instead it may be downloaded from the FTP site from Infineon. When the debugger is started it will check if there is a DAS version available on the system and whether it has the minimum required version (for this release that is V4.0.5). If this is not the case you will be offered to download the package after which you need to install it manually.

Communication method via DAS-LPT no longer supported

Since several years computers are no longer equipped with an LPT printer port. Furthermore Infineon has ceased DAS LPT drivers already a long time ago. All current TriBoards have the possibility to be accessed via an on-board wiggler, USB wiggler or miniWiggler. It is therefore decided to suspend DAS LPT support. If you need the DAS LPT driver you may download this from the Infineon FTP site and install the driver manually.

New in v4.1r2

This section gives an overview of the most important new features and improvements in v4.1r2. See the sections with fixed issues for a complete list.

Elfpatch integrated in Eclipse and TriCore control program

With the increasing complexity of applications it was desired to integrate the elfpatch utility into Eclipse. This makes it easier to patch objects and libraries from the project and partners in an automated way, and control it completely via a user interface.

The patch settings are part of  the linker properties page in tab Patching. Here you can decide to have the elfpatch utility run and can specify the necessary options for the utility. Eclipse build will generate a project makefile in which the control program is called per step, i.e. per compiler, per assembler and linker. The control program is therefore extended to support the elfpatch utility options. The control program will invocate the elfpatch prior to linking for each object and each library which are passed to the linker/locator. System libraries (such as libc.a) are not patched. Option files (-f <file>) are not scanned. The elfpatch will create temporary objects and libraries which will be removed after linking.

TriBoard support for TC1728 and TC1784

With this release debug support is made available for the TriBoards TC1728 and TC1784.

New SFR files for TC27x A-step, TC27x B-step, TC26x, TC2d5t

The named SFR files have been updated with the latest descriptions from Infineon. Furthermore are these SFR files updated with respect to merging double defined structures (B1, B2 etc) into one structure (B) in several SFR union definitions.

Fixed issues for v4.1r2

New Features

Improvements

Fixed Problems

The list of open issues for v4.1r2 can be found on the internet.

Quick start

For a quick start, just start the TASKING VX-toolset for TriCore 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 and/or the MCS project examples.

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

License Information

15-day Trial

This release does not support the regular 15-day trial mode.

How to obtain a license key

All TASKING products include the industry standard FLEXlm license management software. In order to be able to run this toolset, you will need a license key. You can only obtain a license key if you have purchased this product.

To obtain a license key, you can start the License Administrator from the program group of your installed TASKING toolset. In case you still need to install the toolset, you can start the License Administrator by setting a check mark at the end of the setup/installation process. The wizard of the License Administrator will guide you through the steps to obtain your license key.

Once you have received your license key from Altium, you can install it on your system by running the License Administrator again. Alternatively you can simply save the license key as the file 'license.dat' in the C:\FLEXLM folder on your PCs hard disk.

More information is available on http://www.tasking.com/support/flexlm. On this page you also find assistance to setup a floating network license, or for installation on Linux or Sun systems.

Bundles

Altium's TASKING VX-toolset for TriCore is available as Standard, Professional and Premium Edition. At installation time all tools are installed, no matter what bundle you purchased or want to evaluate. However, each tool is protected with its own unique key. After your purchase you will release a license key - specific for the bundle - to unlock the appropriate tools.