TASKING VX-toolset for C166 v3.0r3
Release Note

Scope

This release note covers the changes between v2.5r1 and v3.0r3 of the TASKING VX-toolset for C166.

Contents

New in v3.0

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

Various Significant Eclipse Changes

In v3.0r1 a major overhaul in various Eclipse parts has been made to improve ease of use. A summary of the changes:

The XML schema for the debug target configuration files (.dtc) has been modified to accommodate some of the changes mentioned. In case you have created a .dtc file for your own board it shall be updated accordingly. (119-38028)

Device support updated

The device support has been updated with the latest status from Infineon.

The following devices have updated SFR files:

LSL Changes

The device specific LSL files in the product's include.lsl directory have been updated. When you copied such a file completely or parts of its contents to your project, you may need to update these files in your project. The following changes may be relevant:

Flash memories got a priority attribute

The linker's algorithm for putting sections in memory is such that when a section is placed, a place for the next section is searched starting the end address of the just placed section. It may happen that after placing a data section in flash in an uncached range, the linker tries to put sections that are located later at addresses higher than this data section. This may result in the behavior as described in issue 119-37974.

To force the linker to always start searching for a place for a section in the first flash memory (Flash0) the flash memory definitions now got a 'priority' attribute.

When you have copied the contents (especially the memory definitions) of the processor's LSL file to the project's LSL file, you probably don't have the speed or priority attributes on the flash memories. Unless you applied the workaround. It is recommended either to add the priority attribute to the flash memory definitions, or to copy the processor's LSL file contents again to your project's LSL file.

Tags of memory maps have changed

In v2.5r1 the memory maps of the Flash memory definitions for devices with an ICACHE were tagged 'cached' and 'uncached'. This has changed to 'cached' and 'not_cached'. You must update your LSL file if you have references to the 'mem:spe:Flash0/uncached' in group definitions. This must be updated to 'mem:spe:Flash0/not_cached'

Macro to allow redefinition of on-chip memories

The definition of on-chip memories and reserved ranges in the device specific LSL file can now be suppressed by defining the macro __REDEFINE_ON_CHIP_ITEMS before inclusion of the device LSL file in your project's LSL file. The Eclipse Memory properties page automatically inserts this macro in the project's LSL file as soon as you modify one of the on-chip memory definitions. At the same time it places the modified memory definitions in the project's LSL file.

Linker predefined macro __LITE__ added

A new predefined linker macro __LITE__ has been introduced. This macro is only defined in the linker included in the Lite edition. With this macro you can make conditional implementations for the Lite and full versions in your LSL file. (119-38037)

New LSL attribute: priority

The LSL 'priority' attribute has been introduced as an alias for the 'speed' attribute. This to avoid confusion for memories that you want to prioritize, but don't have a speed difference. The standard LSL files in the product's include.lsl directory only use the 'priority' attribute. (119-38056)

Updated DAS to 3.3.1

The DAS server and drivers that are (optionally) installed in the setup have been updated to version 3.3.1 to support the latest devices and boards. (119-37706)

Fixed issues for v3.0r3

Fixed Problems

The list of open issues for v3.0r3 can be found on the internet.

Fixed issues for v3.0r2

New Features

Improvements

Fixed Problems

The list of open issues for v3.0r2 can be found on the internet.

Fixed issues for v3.0r1

New Features

Improvements

Fixed Problems

The list of open issues for v3.0r1 can be found on the internet.

License Information

15-day Trial

When using the product without a valid license, the tools will run in trial mode. This means you can use the toolset 15 days with full functionality. When running in trial mode, each tool will report the number of days left. When using a license that does not cover the full toolset, the tools that are not covered by the license will run in trial mode.

When after installing the license file the tools that are covered by the license still report that they are running in trial mode, this means that there is a license error. If you want to force the termination of the trial mode to get the FLEXlm error message you can set the environment variable FORCE_NO_TRIAL to "yes".

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, although you can use the full functionality during the 15 day trial period as described above. 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.