TASKING VX-toolset for ARM Cortex v3.2r1
Release Note


These release notes cover the changes between v3.1r1 and v3.2r1 of the TASKING VX-toolset for ARM Cortex.


New in v3.2

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

Board Support

Support for the following boards is added in v3.2r1:

With v3.2r1 the STMicroelectronics STLink debug interface can be used for all STMicroelectronics evaluation boards.

Note: Before using the SEGGER debug probes it is required to install drivers. These can be downloaded from http://www.segger.com/cms/jlink-software.html.

Device Support

With v3.2r1 support for the following devices has been added:

For STM32L15x preliminary CMSIS header files are included.

For ST32F2xx no CMSIS header files are available yet.

Cortex-M4 support

This release implements Cortex-M4 support. The compiler option -CARMv7EM is available to enable code generation for the Cortex-M4. With the --fpu=FPv4-sp option the FPU code generation is enabled. When selecting the processor "C/C++ Build" > "Processor" > "Select by core" > "Cortex-M4F (ARMv7E-M)" in Eclipse the FPU code generation is enabled by default. In Eclipse you can disable FPU code generation by either selecting "C/C++ Build" > "Processor" > "Select by core" > "Cortex-M4 (ARMv7E-M)" or by disabling the checkbox "C/C++ Build" > "Settings" > "Tool settings" tab > "C/C++ Compiler" > "Code Generation" > "Use FPU".

The C compiler is extended with the CMSIS 2.00 DSP intrinsics.

Fixed issues for v3.2r1

New Features



The list of open issues for v3.2r1 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.