DSP56xxx Toolchain v3.6r3
Release Note


This release note covers the changes between v3.5r1 and v3.6r3 of the DSP56xxx Toolchain.


Important Notices

Windows 95 and Windows 98 are no longer supported (since version 3.6r1)

Version 3.6r1 and later do not support Windows 95 and Windows 98 anymore.

DELFEE language: Asterisks (*) allowed in names (since version 3.0r2)

Version 3.0r2 of the locater allows asterisks (*) in names. The consequence is that the asterisks should be separated by spaces to specify a valid multiply.


  #define INT_P_RAM (80k - SWITCH_SIZE*SWITCH_SELECT)  // Wrong since v3.0r2
#define INT_P_RAM (80k - SWITCH_SIZE * SWITCH_SELECT) // Correct

Please check your user defined DELFEE files (*.dsc, *.cpu and *.mem) for non-space separated asterisks

Default interrupt priority of serial port (since version 3.0r1)

The default of the IPR for the serial port was set to 1 in previous releases. In the current release the default is set to 2 to make it possible to have a higher and a lower priority. It is possible to overwrite this default by setting the define SER_IRQ_LEVEL when building serio.c.

Windows Vista

In Windows Vista, the User Account Control (UAC) introduces fundamental changes to enhance the experience for the non-administrative user. Registry and file virtualization in Windows Vista redirects per-machine file and registry writes to per-user locations if the user doesn't have administrative privileges. The DSP56xxx Toolchain will be installed in the C:\Program Files directory by default. For all executables, this is the preferred location. But for configuration files, the example working directory and the library rebuild environment, this can cause weird behavior, because generated/updated files are put physical elsewhere. These files should be moved (or copied) to a location within the users documents directory. For the example directory this will be handled by EDE. The first time EDE is started, a dialog box appears and a destination location for all examples can be entered. Examples will be copied only once. For the the library rebuild environment, you have to copy the contents of the lib\src directory to another location yourself.

New in v3.6

Default working directory changed

Since version 3.6r1, the first time EDE is started, all examples will be copied to the users documents directory. This location will become the default EDE working directory. The examples will be copied only once.

Viterbi Example

Based on Motorola's application note "Implementing viterbi decoders using the VSL instruction on the DSP families DSP56300 and DSP56600" by Dana Taipale we added an IS-136 convolutional error correcting code example to this revision release almost entire written in C. The example has been added to the examples project space and is stored in the examples\viterbi folder.

Support for USB

Now also universal DSP emulators with USB interface of Domain Technologies are supported. (USB-EMU since version 3.5r3)

Fixed issues for v3.6r3

Fixed Problems

The list of open issues for v3.6r3 can be found on the internet.

Fixed issues for v3.6r2


Fixed Problems

The list of open issues for v3.6r2 can be found on the internet.

Fixed issues for v3.6r1


Fixed Problems

The list of open issues for v3.6r1 can be found on the internet.

Fixed issues for v3.5r3


Fixed Problems

The list of open issues for v3.5r3 can be found on the internet.

Fixed issues for v3.5r2

New Features


Fixed Problems

The list of open issues for v3.5r2 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 the toolset can be used for 15 days with full functionality. When running in trial mode tools will emit an informational trial mode message. When using a license that does not cover the full toolset, the tools which are not covered by the license will run in trial mode.

If after installing a valid license file the tools which are covered by the license still report they are running in trial mode, then there is a license error. You can force termination of trial mode to get the actual FLEXlm license error message by setting 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.