TASKING VX-toolset for C166 v2.1r2
RELEASE NOTE

Introduction

This release note covers the TASKING VX-toolset for C166 version 2.1r2. This toolset is a complete new toolset for the Infineon C16x/XC16x/XC2xxx and STMicroelectronics ST10/Super10 families of microcontrollers. All tools in this new product, from IDE and compiler to debugger, are new and based on the latest TASKING technology. This brings advanced features and optimizations, that were not possible in the technology as used in the classic TASKING C166/ST10 toolset. Unfortunately this also means that existing projects have to be migrated and converted. To ease this process the product includes conversion tools and import wizards.

SUMMARY OF CHANGES

Summary of changes between v2.1r1 and v2.1r2:

ELF/DWARF fixup to descrease object and library file size
Renaming all option IDs in Eclipse to avoid conflicts with other toolsets
Includes DAS v2.5.1 to support on-board wigglers for Infineon EasyKit boards and to support the Infineon miniWiggler II
New compiler option and pragmas to control bit variable clearing
Added support for the XC164CS EasyKit board with onboard wiggler.
New heap view in Eclipse to display the allocations on the heap.
Added support for STMicroelectronics ST10F252 Evaluation Board
Added CAN libraries for C16x derivatives
STLPort iostream libraries added
Solving of reported problems

Solved and known problems are listed in a separate file, solved_2_1r2.html, delivered with the product.

Moving From A previous version

IMPORTANT NOTE: Moving from version v2.1r1 or older to version v2.1r2 requires to create your project(s) again:

Create a new project:

File -> New -> Project ... -> TASKING C/C++ -> TASKING VX-toolset for C166 C/C++ Project
Click Next
Enter your project name
Click Next
On the "Select a type of project" page, click Next
On the "Additional Project Settings" page, click Next
Disable "Add C startup code to the project"
Disable "Add Linker script file to the project"
Click Finish

Add all files of your existing project:

File -> Import... -> General -> File System
Click Next
Fill in the directory of your original project in "From directory"
Select all files except: .cdtbuild, .cdtproject and .project
Do not select the Debug and .settings directory
Select the folder of the newly created project in "Into folder"
Click Finish

Set all option as you had set in the original project

This way of importing a project is necessary because starting with v2.1r2 the option IDs as written in the project files are all changed to avoid conflicts with other toolsets that use the Eclipse CDT. Migrating from v2.1r2 to a future release will not need this kind of import.

Quick Start

For a quick start, just start the "TASKING VX-toolset for C166" 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.

Licensing issues

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 this. 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".

Library Sources

For using the library source a valid license is needed. The library sources are stored in a packed file in the library directory. To unpack this file just execute the "unpack-*.exe" tool in the library directory. Without a valid license the library sources cannot be unpacked.

Detailed Release Information

Clearing of Global and Static Bit Variables

A new option is added:

--no-clear-bit

Don't clear non-initialized global/static bit variables. This option is the same as --no-clear, except that it only applies to __bit variables.

New pragmas:

#pragma clear_bit

Performs 'clearing' of non-initialized global/static bit variables.

#pragma noclear_bit

Performs no 'clearing' of non-initialized global/static bit variables.

STLPort IO-stream Libraries

With version 2.1r2 the STLPort io-stream libraries are included for all data models. When you want to use the io-stream libraries when using single precision float (-F option) or the user-stack model (--user-stack option) you will have to build these libraries from the sources. See the User Guide Chapter 11 for more information on building these libraries.

Infineon EasyKit Boards and Wigglers

This version of the TASKING VX-toolset for C166 installs DAS v2.5.1. This enables the support for the new Infineon XC164CS EasyKit board's onboard USB wiggler and the Infineon miniWiggler II. To select these wigglers in the TASKING debugger, you should use the Target Board Configuration (Project menu). First select the target board and then select the appropriate wiggler from the "Communication" list.

1.18

TASKING VX-toolset for C166 v2.1r2 RELEASE NOTE