Texas Instruments Technology for Innovators(tm)

XDCtools 3.22.00.09 GA Release Notes

May 02, 2011

Introduction, Documentation, License, What's New, Upgrade & Compatibility Information, Host Support, Dependencies, Device Support, Validation Info, Known Issues, Version Information, Technical Support.


Introduction

RTSC / XDC (eXpanDed C) is a standard for reusable software components, optimized for real-time embedded systems. RTSC components have hardware-neutral formal interfaces, are configurable offline to optimize memory and performance, and support custom automation in the development environment via a scripting language.

The XDCtools product includes the following components:

back to top

Documentation

The product documentation for this release is available in two formats:

Both formats are delivered with the product in the docs subdirectory. The most up-to-date docs can also be viewed in the RTSC-pedia

Release notes from previous product releases are available in the relnotes_archive directory. Note that  XDCtools 3.21 (supports only the MSP430 device family) is shipped only with the Grace product. 

back to top


License

XDCtools contains elements released under the Eclipse Public License v1.0 and a number of other open-source licenses, detailed here.


What's New

The following significant changes are included in XDCtools 3.22 :

XGCONF Enhancements

The following enhancements have been made to the XGCONF tool

New Host Support

Eclipse Integration Enhancements


Defect history for 3.22.00.09 (This Release)

Bugs against the XDCtools product maybe filed in the eclipse bugzilla.

The following defects were resolved in this release:

IDHeadline
ECL283354Templates that throw exceptions can corrupt the config model
ECL291248
Closing XGCONF "Available Packages" view before it is populated causes an exception
ECL291845mod__prologue.h and mod__epilogue.h are not automatically added to pkg
ECL293232gconf: closing the outline view of a config corrupts the GUI lists
ECL303338xgconf: should remember previous property page when configuring a module
ECL315708cannot set 'fxn' field in ti.sysbios.family.c64p.EventCombiner array
ECL317527IInstance.name needs link to common$.namedInstance
ECL321075XDCtool error parser should filter out stack traceback error
ECL321158Config crash when XDCBUILDCFG assigned a file with a space in its path
ECL322858Building Java code in packages fails if pathnames have spaces
ECL328989setting Text.isLoaded to true causes Diags_setMask() to access random memory
ECL329837Platform wizard throws an exception while using the TMS320DM365 device
ECL331949gnu.targets.ITarget.xs's link cmd should first rm the generated .map file (in case it's read only)
ECL332570xdc.tools.Server SecurityManager can cause CCSv5 to refuse to close
ECL332985gnu.targets link fails if a filename contains '-'
ECL334317trailing white space in XDCTARGETS corrupts the environment
ECL340213Platform wizard does not search user repository while importing platforms

back to top


Upgrade and Compatibility Information

 The following section describes compatibility breaks, and workarounds where available

Package Compatibility Keys

The packages comprising the XDCtools release are uniquely identified by a compatibility key defined in the package.xdc file of a package. Please note that the package compatibility keys are independent of XDC product release numbers.

Package compatibility keys are intended to:

  1. Enable tooling to identify incompatibilities between components, and
  2. Convey a level of compatibility between different releases to set end user expectations.

Package compatibility keys are composed of 4 comma-delimited numbers - M, S, R, P - where:



back to top

Host Support

This release supports the following hosts:

back to top

Dependencies

This release requires the following other software components and tools versions to successfully function:

back to top

Device Support

This release supports the following device families:

back to top

Validation Information

This release was built and validated against using the following components:

The code generation tools used for the various RTSC targets shipped with the product are shown below:


RTSC TargetCode Generation Tools
ti.targets.[C64P,C64P_big_endian,C67P,C674,C674_big_endian,C64T,C64T_big_endian]7.0.3 (TMS320C6x)
ti.targets.[C28,C28_large,C28_float]5.2.3 (TMS320C2000)
ti.targets.[C66,C66_big_endian];ti.targets.elf.[C64P,C64P_big_endian,C64T,C64T_big_endian,C674,C674_big_endian,C67P,C66,C66_big_endian]7.2.0 (TMS320C6x)
ti.targets.arm.elf.[TMS470,Arm7,Arm9,Arm9t,A8Ft,M3,M3_big_endian,R4,R4_big_endian,R4t,R4t_big_endian,R4F,R4F_big_endian,R4Ft_big_endian]4.9.0 (ARM/TMS470)
gnu.targets.MVArm9,gnu.targets.arm.GCArmv5T3.4.3 (GCC Montavista)
gnu.targets.UCArm94.2.1 (GCC Opensource)
gnu.targets.arm.GCArmv6,GCArmv7A4.3.2 (GCC Codesourcery)
gnu.targets.[Linux86,Sparc]4.1.0 (GCC Opensource)
gnu.targets.Mingw4.4.0 (GCC MingW)
microsoft.targets.Net3213.10.3052 (Microsoft .NET C/C++)
microsoft.targets.Win3214.00.50727.42 (Microsoft Visual C/C++)
microsoft.targets.VC9812.00.8168 (Microsoft Visual C/C++)
microsoft.targets.arm.WinCEMicrosoft WinCE 6.00
ti.targets.msp430.[MSP430,MSP430X,MSP430X_small]3.3.0(MSP430)


back to top


Known Issues


IDHeadline
ECL280863xgconf: If instances have required args, should force user to enter something
ECL280869xgconf: Can create two instances with the same name
ECL305948
xgconf does not respond to config file rename
ECL321074xgconf and XDCtools error parser add duplicate errors to Problems view
ECL342651XGCONF should allow disable static creation in a RTSC modules


back to top


Version Information

All releases have 4 digits (M.mm.pp.bb). This includes GA and pre-releases (engineering, EA  etc.). Pre-releases are denoted with a suffix (e.g. 3.15.01.51-eng).

This product's version follows a version format, M.mm.pp.bb, where M is a single digit Major number, mm is 2 digit minor number, pp is a 2 digit patch number, and b is an unrestricted set of digits used as an incrementing build counter.

To support multiple side-by-side installations of the product, the product version is encoded in the top level directory, ex. xdctools_3_15_00_50.

Subsequent releases of patch upgrades will be identified by the patch number, ex. XDCtools 3.15.01.67 with directory xdctools_3_15_01_67. Typically, these patches only include critical bug fixes.

Please note that version numbers and compatibility keys are NOT the same. For an explanation of compatibility keys, please refer to the 'Upgrade and Compatibility Information' section.

back to top


Technical Support

Support questions on the product should be posted to the RTSC newsgroup.   Check the XDCtools download site  for the latest releases.

back to top


Last updated: May 02, 2011 Build Ver: 3.22.00.09 Rev: