C166/ST10 Tool Chain v8.7r2

RELEASE NOTE

SUMMARY

This release note covers version v8.7r2. It describes the changes and new features of all TASKING C166/ST10 products since v8.6r1.

The following sections are included in this release note:

LICENSING
C COMPILER
EDE
CROSSVIEW PRO

Summary of changes between v8.7r1 and v8.7r2:

Summary of changes between v8.6r3 and v8.7r1:

Summary of changes between v8.6r2 and v8.6r3:

Summary of changes between v8.6r1 and v8.6r2:

LICENSING

Software Bundle

In previous versions three different software bundles existed. Starting with v8.7r1 only one software bundle is left and the license determines which tools can be used. The licenses have the same differentiation as the different software bundles before (SW019024, SW019012 and SW019002). The licensing is done with so-called FLEXlm package licenses. Like before, older versions will run on the license of this new version.

15-Day Trial

The product can be used for 15 days without a license. This 15-day trial period replaces the in functionality restricted demo version and gives the opportunity to try out the full featured product. After this trial period a license is mandatory.

C COMPILER

New Pragma indirect_access

The following pragma has been added:

#pragma indirect_access [([_]near)]<address>[-<address>],...

With this pragma the address (ranges) that have to be accessed using an indirect addressing mode can be specified. When a near address is specified the ([_]near) keyword must be added, otherwise the address will be interpreted as _huge. In the segmented memory models, _near, _xnear and _system/_iram/_bita are all separate near memory spaces. The correct DPP-number must be included in the address.
Multiple uses of this pragma accumulate the specified addresses.

Example for a segmented memory model:

	#pragma indirect_access	(near)0x9234,(near)0x5232-0x5236,0x200200	/* include DPP number in address */

	void	main( void )
	{
		*((_near int *)0x1234)  = 5;
		*((_xnear int *)0x1234) = 10;
		*((_far int *)0x200200) = 15;
		return;
	}

This pragma applies to constant pointers only.

EDE

Microsoft Vista Support

The EDE now works on systems where the installation directory is write protected by default, such as Microsoft Vista. At startup of EDE you will be asked to copy the examples to a project space. By default a project space directory in your "My Documents" folder is proposed.
All configuration files, such as cwright.ini will be placed and maintained in a directory TASKING in the local settings directory in your profile. The default local settings directories are:

Windows Vista
C:\Users\USERNAME\AppData\Local\TASKING\SW019800\v8.7r2
Windows XP/2000/Server 2003
C:\Documents and Settings\USERNAME\Local Settings\Application Data\TASKING\SW019800\v8.7r2
Windows NT
C:\WINNT\Profiles\USERNAME\Local Settings\Application Data\TASKING\SW019800\v8.7r2

Help Files

The help files of the manuals and context sensitive help are all in the WinHlp32 format. This format is not officially supported on Windows Vista (see Microsoft Knowledge Base article http://support.microsoft.com/kb/917607). Opening the help files will therefor result in an error. The solution is to add WinHlp32 support to Vista: http://go.microsoft.com/fwlink/?LinkID=82148

Rebuilding Libraries or Monitors

The library and monitor sources are included as encrypted archives, which can only be unpacked using the belonging unpack tool with a valid license. For rebuilding the libraries or monitors it is recomended to copy the whole source directory to a location that is writable, such as your Documents directory, before unpacking the sources.

Flash and RAM Configuration

The flash configuration in the Project Properties dialog has changed. The following changes were made:

Additionally you can now enable the on-chip RAM mapping from the Application -> Processor page. This makes it easier to use a processor in single chip mode, without having to make other settings than those on the Processor page.

Selecting Target Boards Using DAS

Selecting a target board with OCDS via DAS from the Project Properties dialog -> CrossView Pro -> Execution Environment has changed to accommodate more wigglers and boards. Now first a board must be selected from the "Board configuration" list and addionally a selection of the used wiggler must be made from the CrossView Pro -> OCDS via DAS page.

CROSSVIEW PRO

Naming of On-Chip Flash

Starting with version v8.6r2 the naming of the on chip flash devices has changed. Previously the names did include the stepping code, for example "XC167CI-16FF AB". Now the stepping code is no longer included, except for steppings that have a different flash algorithm. For example:

XC167CI-16FF (< AC)
XC167CI-16FF
XC167CI-32FF

When using EDE to configure and launch CrossView Pro, the configuration should be updated automatically. When starting CrossView Pro outside EDE, you may need to update *.cfg files or select the correct Flash device from the Target => Flash Setup... dialog within CrossView Pro.

Infineon EasyKit Boards and Wigglers

The C166 v8.7r2 installs DAS v2.6.1. This enables the support for the new Infineon EasyKit onboard USB wiggler, Infineon miniWiggler II and the newly added devices. The CrossView Pro debugger has an additional selection of the wiggler when a configuration file is selected for DAS. From EDE you can select the wiggler from the "OCDS via DAS Setup" page in the Project Options dialog

When using the Infineon USB Wiggler Box, DAS v2.6.1 will update the firmware as soon as CrossView is started. During the firmware update CrossView may report connection problems. After closing and restarting CrossView, connecting to the board should pass normally.

@(#)readme.html 1.44