Texas Instruments Technology for Innovators(tm)

XDCtools GA Release Notes

May 28, 2010

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


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


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 on-line at:

Release notes from previous product releases are available in the relnotes_archive directory.

back to top


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

Data Memory Footprint Reduction

Release  implements optimizations in the generated target code that result in data memory footprint reduction. Refer to ECL278643
for more details.

 Tool Performance Improvements

Refer to this link for details on performance improvements in RTSC configuration.


Enhanced Logging Capabilities

The logging capabilities of the xdc.runtime package has been enhanced with the following new functionality

 Platform Wizard Enhancements

An improved  platform wizard is available with this release 

 Support for Peripherals in RTSC Platform Model

The RTSC platform model has been extended to support peripherals.

Defect history for (This Release)

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

The following defects were resolved in this release:

ECL280878xgconf: Deleting project with cfg file open doesn't close the window
XGCONF: On changing Configuro –D options, config is not re-validated, need to re-save script
configuro exit status is 0 even when command usage is wrong
ECL306433a second package release that specifies "exportAll" has an incomplete manifest
ECL287731Updating XDC version fails to regenerate package/rel/*.tar.dep files
ECL289229When xs xdc.tools.repoman fails it should exit with non-zero exit status
ECL289144cdoc: @_nodoc on per-instance config is ignored
ECL285460cdoc does not properly escape '<' in strings
ECL285331XGCONF gives NullPointerException when certain modules are used.
ECL280875xgconf: hand-editing to add ti.bios.MEM throws NPE
ECL280861xgconf: Renaming an instance does not create a Program.global entry if the instance has no Params struct
ECL276101xgconf: hover help text does not properly format xdoc text
ECL304758microsoft.targets.arm.WinCE's default platform is incorrectly an x86 device
ECL280858xgconf: Can't double-click on Problems view to go to offending module/instance
ECL301761xgconf should add the project cfg path when processing app.cfg file
ECL303793Platform wizard does not support c28xx devices
ECL313408package whose repository is in the current directory can cause NullPointer exception
ECL264025cannot define an interface instance as a global variable
ECL312963SysMin_ready fails
ECL307806the config error for uninitialized array values is confusing
ECL312965ROV view of SysMin outbuf is garbled
ECL302355Closure tool gives erroneous message
ECL296749Dereferencing undefined object in user's Build.targets array leads to confusing error msg
ECL312648When assigning Pkg.libTemplate, compile options need extra space padding.
ECL309514System_printf bug with extended specifiers
ECL302614Incomprehensible error message when incorrect package name is loaded
ECL291830can't use modules that have @NoRuntime attribute set

back to top

Upgrade and Compatibility Information

This release contains some compatibility breaks in order to introduce new features. The following section describes those 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


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:

back to top

Known Issues

The following issues are known to affect this release:

ECL314909Closing the Path app (launched from CCS) with File|Exit crashes CCS
ECL314790Default JVM memory not enough for cdoc

back to top

Version Information

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

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 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.   

back to top

Last updated: May 28, 2010 Build Ver: Rev: m41