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

Scope

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

Contents

• New in v4.2
• Fixed Issues in v4.2r1
• License Information

New in v4.2

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

Device Support

Infineon XMC4500

With v4.2r1 support for the following devices has been added:
XMC4500-x1024, XMC4500-x768, XMC4502-x768, XMC4504-x512

Board support has been added for the Infineon Hexagon Application Kit.

Infineon TriCore Aurix HSM Core

The TriCore Aurix family has a Cortex-M3 core on-chip. This core is now supported with an add-on package to the standard TASKING VX-toolset. This package is only available upon request

STMicroelectronics STM32F0

With v4.2r1 support has been added for STM32F051x6 and STM32F051x8 devices:
STM32F051x6: STM32F051K6, STM32F051C6, STM32F051R6
STM32F051x8: STM32F051C8, STM32F051R8, STM32F051K8

Board support has been added for the STMicroelectronics STM320518-EVAL and STM32F0 Discovery.

STMicroelectronics STM32W

With v4.2r1 support has been added for the STM32W Cortex-M3 series. Supported devices:
STM32W108C8, STM32W108CB, STM32W108HB,STM32W108CZ, STM32W108CC

At time of release no CMSIS header and SVD files were available. The ARMCM3 core SFR header and XML files are used

Board support has been added for STM32W108 Starter Kit, STM32W108 Extension Kit and STM32W RF Control Kit through the SEGGER debug probes.

Fujitsu FM3

With v4.2r1 support has been added for the Fujitsu FM3 devices:
MB9AF102N, MB9AF102R
MB9AF104N, MB9AF104R
MB9AF111L, MB9AF111M, MB9AF111N
MB9AF112L, MB9AF112M, MB9AF112N
MB9AF114L, MB9AF114M, MB9AF114N
MB9AF115M, MB9AF115N
MB9AF116M, MB9AF116N
MB9AF131K, MB9AF131L
MB9AF132K, MB9AF132L
MB9AF311L, MB9AF311M, MB9AF311N
MB9AF312L, MB9AF312M, MB9AF312N
MB9AF314L, MB9AF314M, MB9AF314N
MB9AF315M, MB9AF315N, MB9AF316M, MB9AF316N
MB9BF102N, MB9BF102R
MB9BF104N, MB9BF104R
MB9BF105N, MB9BF105R
MB9BF106N, MB9BF106R
MB9BF116S, MB9BF116T
MB9BF117S, MB9BF117T
MB9BF118S, MB9BF118T
MB9BF216S, MB9BF216T
MB9BF217S, MB9BF217T
MB9BF218S, MB9BF218T
MB9BF304N, MB9BF304R
MB9BF305N, MB9BF305R
MB9BF306N, MB9BF306R
MB9BF316S, MB9BF316T
MB9BF317S, MB9BF317T
MB9BF318S, MB9BF318T
MB9BF404N, MB9BF404R
MB9BF405N, MB9BF405R
MB9BF406N, MB9BF406R
MB9BF416S, MB9BF416T
MB9BF417S, MB9BF417T
MB9BF418S, MB9BF418T
MB9BF504N, MB9BF504R
MB9BF505N, MB9BF505R
MB9BF506N, MB9BF506R
MB9BF516S, MB9BF516T
MB9BF517S, MB9BF517T
MB9BF518S, MB9BF518T
MB9BF616S, MB9BF616T
MB9BF617S, MB9BF617T
MB9BF618S,MB9BF618T
MB9BFD1XT

Board support has been added for Fujitsu SK-FM3-64PMC1 and SK-FM3-100PMC boards

Eclipse

• Selecting a target board is made more easier. The Execution Environment selection in the Debug Configurations is now shown as first tab and also includes the selection of the debug probe and its parameters. It is now also possible to disable filtering boards for the selected processor
• When starting a debug session, Eclipse now checks if the required drivers from SEGGER, STMicroelectronics or Infineon are installed. If not you will be prompted to install the drivers with a link to where they can be downloaded. See for more details 101-38258
• At project creation the start-up files are added to the project. Usually this is the CMSIS file with the SystemInit() function. In some cases, like for Infineon XMC4500, the C start-up file is also added. See for more details 101-37582
• At project creation a default launch configuration is no longer created. You will have to create one as soon as the debugger is started for the first time
• A new import wizard has been added for importing projects created with Infineon Dave 3.0
• The TASKING specific preference pages are reorganized and are now all grouped under 'TASKING'
• The list of views that is shown when opening a view is reorganized and all views are now grouped under 'TASKING'

Debugger

• The debugger now takes advantage of performance optimization from the SEGGER software by passing the selected processor name to the SEGGER software. This includes using the flash mechanism of the SEGGER software.
• With the SEGGER probes the debugger will now set software breakpoints in flash as soon as the hardware breakpoints are all in use.
• When starting a new debugger all debugger sessions that are open will be terminated before the new session is started. This avoids confusion about parallel sessions for novice users. Through the preference pages it is possible to enable parallel debug sessions.
• The debug connections for SEGGER and STMicroelectronics now provide more detailed messages when the connection fails. Of course this is restricted to the information provided by the vendor's drivers.
• To allow simulating projects that include a SytemInit() function the simulator now skips the call to SystemInit() from the start-up code. This avoids hangups in SystemInit() code when it waits for external events that will never happen in a simulated environment.

CMSIS

• CMSIS 2.10 patches 2, 3 and 4 are applied to the CMSIS folders that are included in the product.
• The CMSIS DSP library is now included as pre-compiled library. When using the new --dsp-library option of the control program (ccarm) at link time, the appropriate library will be linked automatically. In Eclipse this option can be enabled on the project properties page C/C++ Build > Settings > Linker > Libraries.
• The product now includes the CMSIS DSP Library examples as Eclipse projects. You can add them to your workspace through File > Import > TASKING C/C++ > TASKING ARM Example Project

C Compiler

• The C compiler optimization is improved through various small enhancements.
• The GCC attribute "flatten" has been added
• New intrinsics __getfpscr() and __setfpscr() have been added

Fixed issues for v4.2r1

New Features

• 101-36995 - Add support for software breakpoints in Flash
• 101-37847 - Add support for Fujitsu FM3 MB9xx00 Series
• 101-37874 - Add support Fujitsu SK-FM3-100PMC board
• 101-38079 - Add support for Infineon XMC4500
• 101-38113 - Include the CMSIS DSP library as binary in the product
• 101-38121 - Add support for STM32W
• 101-38123 - Add support for STM32F051x6 and STM32F051x8 devices
• 101-38143 - Import wizard for Infineon Dave 3.0 project
• 101-38146 - Add option to display the list of available CPUs for the -C/--cpu option
• 101-38150 - Add support for Aurix HSM core
• 101-38226 - Include the CMSIS DSP library examples as Eclipse example projects
• 101-38249 - New intrinsics: __getfpscr() and __setfpscr()
• 101-38252 - Add support for Fujitsu SK-FM3-64PMC1 board
• 101-38258 - Check at launch time if drivers required for debug probe are installed

Improvements

• 101-37582 - Automatically add CMSIS SystemInit() code to project
• 101-38152 - Better organization of preferences and views
• 101-38158 - Apply CMSIS v2.10 patch 2
• 101-38159 - Apply CMSIS v2.10 patch 3
• 101-38200 - Apply CMSIS v2.10 patch 4
• 101-38211 - Support "flatten" GCC attribute
• 101-38214 - debugger may read memory slowly when not of all of it is readable
• 101-38233 - Board selection improvements
• 101-38240 - Improved propagation for struct/array initialisers
• 101-38248 - cmsis requires preprocessor symbol to detect FPU code generation
• 101-38281 - by default disallow multiple simultaneous debug sessions
• 101-38287 - Add more detailed messages when connection fails
• 101-38290 - Simulator / startup code tweaks to skip SystemInit() call
• 101-38319 - Add new --dsp-library option to ccarm
• 101-38320 - Add check box for linking DSP Library to tool settings properties
• 101-38337 - Add startup code check box on Processor properties page
• 101-38341 - Do not create a simulator launch configuration for a new project

Fixed Problems

• 101-38048 - Cannot find a board that should be supported
• 101-38132 - Code Analysis and indexer fail to resolve stdio.h
• 101-38188 - if one register in the Registers view cannot be read, none of them can
• 101-38189 - Cannot edit inactive part of #if/#ifdef in LSL
• 101-38191 - VTOR register not initialized in startup code
• 101-38192 - __VECTOR_TABLE_RAM_ADDR not always defined in SRAM
• 101-38197 - ldrd/strd : in ARM mode first register must be even
• 101-38201 - Fix anonymous unions messages in register files
• 101-38207 - __NOP intrinsic is missing
• 101-38286 - More detailed message for missing supply voltage with J-Link
• 101-38364 - MIL linking fails for Cortex-M3, resulting in multiple definitions of _START

The list of open issues for v4.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.