XDCtools 3.24.00.08 GA Release Notes

February 06, 2012

Introduction, License, What's New, Upgrade & Compatibility Information, Host Support, Device Support, 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:

• Core (xdc.*) - the xdc and xs command line utilities for building packages and executing scripts respectively; packages that implement the RTSC standard;
• User tools (xdc.tools.*) - command-line and graphical utilities for working with packages and repositories;
• Targets (*.targets.*) - definitions for using various TI and third-party compiler tool chains;
• Platforms (*.platforms.*) - definitions for linking and running code on various TI and third-party board-level hardware and simulator products.
• Eclipse (eclipse) - A set of integration plugins  for RTSC for the eclipse platform. These plugins are leveraged by CCS (Code Composer Studio) to provide support for integrating RTSC content in the IDE environment.

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

This release of XDCtools is exclusively for use with the MSP430 Grace stand-alone product.

---

Upgrade and Compatibility Information

 The following section describes compatibility breaks, and workarounds where available

• Packages are forwards and backwards compatible starting from XDCtools 3.20
  

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:

• M = Major - A difference in M indicates a break in compatibility. The package consumer is required to re-write its source code in order to use the package.
• S = Source - A difference in S indicates source compatibility. The package consumer’s source code doesn't require change, but does require a recompile.
• R = Radix - A difference in R indicates an introduction of new features, but compatibility with previous interfaces is not broken. If libraries are provided by the package, an application must re-link with the new libraries, but is not required to recompile its source.
• P = Patch - A difference in P indicates that only bugs have been fixed in the latest package and no new features have been introduced. If libraries are provided by the package, an application must re-link with the new libraries, but is not required to recompile its source.

back to top

---

Host Support

This release supports the following hosts:

• Windows XP, Windows 7

back to top

---

Device Support

This release is solely for use within the MSP430 Grace stand-alone product.

back to top

---

Known Issues

To see a complete list of XDCTools issues, see the Eclipse Bugzilla.

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

We encourage you to alert the Grace development team to any issues you may find.  Post any issues or questions to the TI E2E forum at: https://www.ti.com/gracefeedback.

back to top

---

Last updated: February 06, 2012 Build Ver: 3.24.00.08 Rev: