TASKING C166/ST10 Tool Chain v8.8r1
This release note covers the changes between v8.7r1 and v8.8r1 of the TASKING C166/ST10 Tool Chain.
New Devices Supported
The new devices XC2200N/XC2300B/XC27x4X/XE16xxN, XC2200H/XC27x7X/XE16xxH and XC2000ED are supported in this release. This includes the support of Infineon EasyKit boards. See issue 019-37009 for a full list of added devices.
In v8.7r2 support was already added for XC2267M-104F, XC2287M-104F, XC2365A-104F, XC2387A-104F,
XC2765X-104F, XC2785X-104F, XE162FM-72F, XE164FM-72F and XE167FM-72F, including EasyKit board
Support for DAP
With the installation on Windows a new version of DAS (v2.9.0) is installed. With this version the new Infineon MiniWiggler with support for DAP is supported.
For using DAP on the EasyKit boards the dip switches have to be set correctly (1,2 and 5 on; 3 and 4 off). In EDE you have to select "MiniWiggler" as DAS wiggler type.
- 019-37309 - The one's complement operator is not recommnded for bit variables.
- 019-37320 - Add support for DAvE for XE16xxH/N, XC2200H/N, XC2300B/C and XC2704X/7X
- 019-37324 - Add support for all XE166M devices
- 019-37326 - It is not clear from the compiler manual under which conditions no interrupt register bank is generated
- 019-37330 - Update to DAS version 2.9.0
- 019-37331 - Add support for new DAP miniWiggler
- 019-37009 - Add support for XC2200N/XC2300B/XC27x4X/XE16xxN, XC2200H/XC27x7X/XE16xxH and XC2000ED
- 019-36883 - ERROR: PSM can't request interrupt number 0x00
- 019-36926 - CAPCOM peripheral simulation not working correctly.
- 019-36979 - Start address of an interrupt task not calculated correctly
- 019-36989 - Compiler setting should be checked when importing a DAvE project
- 019-37077 - Incorrect result after shifting a long with DFAP enabled
- 019-37234 - m166 does not support files larger than 32768 lines
- 019-37266 - non-existing SFR names for XC164CM
- 019-37299 - conversion failed for sfr bits BNKSELx_GPRSELx after DAvE import
- 019-37302 - S 524: (line xx) assertion failed - please report
- 019-37303 - Interrupt Enabled Debugging not documented
- 019-37305 - DAvE import not supported for XE16xFM and XE16xFM derivatives
- 019-37307 - Programming external Flash not working for Phytec miniMODULE 167CX
- 019-37312 - Fill bytes may end up in the middle of ROM data sections when using FILLGAPS
- 019-37313 - -Oc (CSE optimization) causes R14 / R15 content overwrite
- 019-37315 - Compiler quits without error message when a function contains more than about 60000 lines
- 019-37317 - sections may get overlapped unexpectedly when empty sections are located in the same area
- 019-37318 - wrong pointer used for struct assignment in huge memory model
- 019-37319 - Segmentation fault after running munch166 on Redhat AS5
- 019-37321 - FASTBL bit missing in CPUCON2 in register files
- 019-37322 - Interrupt Enabled Debugging option in EDE does not work
- 019-37323 - segmentation fault when running munch166 on Fedora Core 6
The list of open issues for v8.8r1 can be found on the internet.
- 019-36167 - Using -BZinsert_mdlh_muldiv results in protected NOP instead of DIV
- 019-36205 - S 723: (line ?) assertion failed - please report
- 019-36235 - OCDS via DAS could not be set for user defined boards
- 019-36238 - Update examples for not using a fixed (extern) memory range
- 019-36370 - User defined "output directoy" doesn't allow spaces in its name
- 019-36497 - Linux and Windows compiler creates different code
- 019-36544 - With -zfragment the compiler starts a new section at the use of intrinsic
- 019-36580 - Unexpected floating point trap
- 019-36601 - The project file xxxx.dpt appears to be invalid
- 019-36656 - E 51: cannot hold that many operators
- 019-36658 - CAN libraries not working in huge memory model
The list of open issues for v8.7r3 can be found on the internet.
- 019-36377 - Bring back the _inline keyword in the XE166 compiler
- 019-36382 - "E 62: bad storage class" on inline function returning a function pointer
The list of open issues for v8.7r2 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.