TASKING VX-toolset for C166 v2.5r1
Release Note


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


New in v2.5

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

Device support synchronized

The device support has been synchronized in v2.4r2 and in v2.5r1 with the latest list of Infineon.

New series of devices that are added:

Added several missing devices to XC22xxN, XC23xxA, XC23xxB, XC23xxC, XC27x8X, XC27x6X, XE167FH and XE169FH series.

A few devices have been renamed for consistency reasons. You will need to update the processor selection for your project when using one of these devices.

ICACHE support added

Devices with an ICACHE are now supported.

The ICACHE control registers can be initialized from the C startup code. In Eclipse the C startup code editor can be used to enable the ICACHE with the ICACHE_CTRL.ICEN bit (issue 119-37883).

The linker script language (LSL) has been extend to make it possible to tell whether code sections will be located by default into the cached or into the uncached memory area (issue 119-37460). The standard LSL files in the product's include.lsl directory have been updated to prevent data being located into the cached area (119-37837). By default sections will be located into the uncached area.

See the User Guide section "4.3.1. ICACHE Support" and "8.7.10. ICACHE Support and Named Memory Mappings" for detailed information.

Updated Eclipse

The Eclipse distribution is updated to the Galileo release (Eclipse Platform 3.5 and CDT 6.0).

The "new TASKING VX-toolset for C166 C/C++ Project wizard" is extended with a page to select the processor.

The options to enable Application wide optimizations (MIL-linking) is moved from the Global Options page to the Optimization page. The description and layout of these options are also improved.

MIL files now versioned

MIL files and MIL archives are now stamped with a version. When MIL-linking all MIL files and archives must be created with the same version of the compiler. If this is not the case an error will be issued. (issue 119-37750)

MISRA-C checking improved

The compiler now checks for MISRA-C rules 5.5, 5.7, 6.2, 8.8, 8.9. (issue 119-37621)

High level object dumper

A new tool is included in the product: The high level object dumper, hldump166. (issue 119-37676) With this tool the ELF file can be displayed in a readable way. The output includes:

An example of the high level symbol table:

  ---------- HLL symbol table ----------

Address    Size HLL Type             Name
0000F620    440 struct struct2_tag __near struct2_array[10] [hldump.c]
0000F620     44   struct struct2_tag   
0000F620      2     unsigned int         field1
0000F622     40     struct struct1_tag   array[10]
0000F622      4       struct struct1_tag   
0000F622      1         char                 field1
0000F624      2         int                  field2
0000F626      4       struct struct1_tag   
0000F626      1         char                 field1
0000F628      2         int                  field2
0000F62A      4       struct struct1_tag   
0000F62A      1         char                 field1
0000F62C      2         int                  field2

Data and Code address ranges separated for XC2000 and XE166

The product's standard LSL files no longer allow code to be located in DSRAM and DPRAM. For devices with an ICACHE the cached flash areas can only be used for code (issue 119-37460). This change is required for ICACHE, but also makes it easier to execute code from PSRAM. See "8.7.9. Copying Code Sections to PSRAM at Startup" in the User Guide.

On-chip flash support for XC2000 and XE166 updated

The product's standard LSL files for XC2000 and XE166, defining the on-chip memories, have been updated to match the device documentation more accurately. Each on-chip flash array now has it's own flash memory definition in LSL. This also includes the flash array mapped at the end of the flash memory range (issue 119-37708). The previously used name Program_Flash is replaced by the names Flash0..FlashN (issue 119-37920). The belonging flash definitions for the debugger have been updated similarly.

DAS LPT support dropped

The support for debugging via the parallel port has been dropped since v2.5r1. The new version of DAS no longer supports the parallel port. It is recommended to use the miniWiggler for debugging (issue 119-37817).

Fixed issues for v2.5r1


New Features

Fixed Problems

The list of open issues for v2.5r1 can be found on the internet.

Fixed issues for v2.4r2


New Features

Fixed Problems

The list of open issues for v2.4r2 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.