TASKING VX-toolset for ARM Cortex v4.3r1
Release Note
Scope
These release notes cover the changes between v4.2r1 and v4.3r1 of the TASKING VX-toolset for ARM Cortex.
Contents
This section gives an overview of the most important new features and improvements in v4.3 (compared to v4.2). See the sections with fixed issues for a complete list.
Device Support
Infineon
XMC4500 series: CMSIS files have been updated, Silicon workarounds in cstart for XMC4500 have been removed
because these do not apply to production versions.
XMC4400: Support for XMC4400 series has been added, including support for the XMC4400 Hexagon board and
on-board miniWiggler.
Support for Hitex XMC-HiLight board has been added
Energy Micro
CMSIS files for EMF32 Gecko devices have been updated
Added support for EFM32 Tiny Gecko, Giant Gecko and Leopard Gecko devices
Added board support for:
- EFM32 Tiny Gecko Starter Kit
- EFM32 Giant Gecko Starter Kit
- EFM32 Leopard Gecko Starter Kit
- EFM32 Gecko Starter Kit
- EFM32 Gecko Development Kit
STMicroelectronics
Added support for STM32F30x series and STM32303C-EVAL evaluation board
Added support for STM32F37x series and STM32373C-EVAL evaluation board
Updated CMSIS files for all STM32 devices
Eclipse and Debugger
Board selection and configuration has been improved. It is now possible to select a target board when
creating a new project. The Debug configuration dialog has been reorganized and now only has one level of
tabs to make it easier setting up a configuration.
The debugger will now show a popup to notify when the ELF file has changed on disk and offers to download
it again.
The debugger now supports data breakpoints when debugging with ST-Link.
Segger debug probes
When debugging with a Segger debug probe the TASKING debugger now uses the Segger jlinkarm.dll from the
Segger installation. This means that when updating the Segger software to a newer version, the debugger will
automatically use the new Segger jlinkarm.dll installed with the Segger software.
It is now required to have the Segger software v4.54 or higher installed.
CMSIS
The CMSIS distribution has been updated to CMSIS v3.00.
C Compiler
Various optimization improvements have been made.
A new intrinsic function __BKPT() has been added
New Features
- 101-37738 - support use of data breakpoints with ST Link
- 101-38237 - Update CMSIS to v3.00
- 101-38265 - support J-Trace for Fujitsu SK-FM3-100PMC board
- 101-38377 - New tool for showing size summary of sections in object files
- 101-38383 - Add support for Hitex XMC-HiLight board
- 101-38397 - Add support for STM32F37x
- 101-38398 - Add support for STM32F30x
- 101-38426 - Add support for STM32303C-EVAL
- 101-38427 - Add support for STM32373C-EVAL
- 101-38429 - Add support for EFM32 Tiny Gecko Starter Kit
- 101-38430 - Add support for EFM32 Giant Gecko Starter Kit
- 101-38445 - Add support for EFM32 Leopard Gecko Starter Kit
- 101-38446 - Add support for EFM32 Gecko Starter Kit
- 101-38447 - Add support for EFM32 Gecko Development Kit
- 101-38476 - Add support for Infineon XMC4400 series
- 101-38479 - Add __BKPT intrinsic
Improvements
- 101-38054 - Make profiling views aware of active project
- 101-38296 - show dialog suggesting re-download when ELF file has changed on disk
- 101-38299 - Reorganize tabs in debug configurations dialog
- 101-38303 - Select a target board and configuration when creating a new project
- 101-38355 - allow "variable method"-breakpoints
- 101-38366 - Cleanup of Reset_Handler alias to _START
- 101-38368 - Show popup message when processor does not match target at launch time
- 101-38400 - Update CMSIS to V3.01
- 101-38408 - Extend hldump with support for displaying multiple source lines per address
- 101-38410 - Add/Update support for EFM32 Gecko devices
- 101-38411 - Add support for EFM32 Tiny Gecko devices
- 101-38412 - Add support for EFM32 Giant Gecko devices
- 101-38413 - Add support for EFM32 Leopard Gecko devices
- 101-38418 - Add support for EFM32TG225 and EFM32TG825 Tiny Gecko devices
- 101-38422 - Remove duplicate code sections improvement
- 101-38470 - Update XMC4500 XML SFR files to v1.1.2 of SVD file
- 101-38477 - Update XMC4500 CMSIS files to latest versions
- 101-38485 - Remove silicon workarounds in cstart for XMC4500
Fixed Problems
- 101-38090 - Eclipse does not substitute ${ProjName} when a Workspace folder is selected at "Include paths"
- 101-38097 - certain AFIO bit fields are not shown in the debugger
- 101-38100 - floating point registers not shown when using ST-LINK
- 101-38165 - Add STM32W CMSIS register files (C & XML)
- 101-38227 - Undeserved MISRA-C rule 17.4 violation when using an array as struct member or a 2-dimensional array
- 101-38260 - Sorting of non-default columns in map file table "Locate Result: Sections" does not work
- 101-38262 - Standard Eclipse disassembly view pops up when switching to Instruction stepping
- 101-38304 - Avoid jlinkarm.dll being out-of-sync with the actual Segger installation
- 101-38310 - Cannot find core_cm4.h when debugging
- 101-38314 - When debug probe hangs in call it is not possible to terminate the debugger
- 101-38323 - Core registers not in XMC4500.xml
- 101-38356 - TASKING breakpoint button grayed initially
- 101-38360 - --dsp-library option does not pass macro settings to C++ compiler
- 101-38362 - Multiple popups when the debugger cannot set some breakpoints at startup
- 101-38367 - Symbolic register view shows only zeros
- 101-38375 - Usage linker is incorrect for -O option
- 101-38379 - change in Memory view does not propagate to TASKING Registers view
- 101-38385 - For an array of SFRs only the first element is displayed in SFR view
- 101-38387 - Include paths imported from Dave not expanded, DAVE3.h not found
- 101-38393 - CMSIS: smlald smlaldx smlsld smlsldx wrong in little endian
- 101-38394 - Several DSP instructions in the simulator contained bugs.
- 101-38396 - Unaligned accesses with the ldr and str instructions run into an exception.
- 101-38407 - The prototype of some CMSIS 3.0 intrinsic functions have been changed to use unsigned arguments and return value.
- 101-38414 - printf zero padding before 0X
- 101-38415 - tracing functionality does not work with STM3220G-EVAL and SEGGER J-Trace
- 101-38416 - Pending edits in LSL file are undone when opening project properties dialog
- 101-38419 - Linker message "lkarm E100: unexpected error: Fatal error occurred" when non-existing memory is referenced in LSL sizeof() or addressof()
- 101-38420 - The [ and ] can not be used in select statement
- 101-38456 - Compiler generates constant pool inside code without branch
- 101-38465 - debugger may malfunction if illegal access is attempted via FSS
- 101-38492 - Still FPU code generated when disabling 'Use FPU'
- 101-38493 - Update CMSIS files for STM32
The list of open issues for v4.3r1 can be found on the internet.
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".
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.