Texas Instruments Technology for Innovators(tm)

XDC 3.00.04.22 Release Notes

Dec 21, 2007

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


Introduction

eXpress DSP Components (XDC) is a standard for reusable software components, optimized for real-time embedded systems. XDC 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.

This XDC release includes the following sets of packages:

back to top

Known Issues

None.

back to top


Documentation

The following documentation is available:

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

back to top


What's New

The following significant changes have been made since 3.00:

3.00.04.22 (This Release)

Targets

Repoman

3.00.03

Targets

Platforms

Catalogs

Runtime

Core

Configuro

Configuro CCS 3.3 Integration

Enhancements

The following minor enhancements were resolved:

Defects

The following defects were resolved:

SDSCM00007080 XDC command help message is hard to find
SDSCM00015332 XDC Verbose option should print the full path to each package it loads
SDSCM00018922 xdc.runtime.Text.isLoaded = false does not work
SDSCM00019111 Diags: Config Parameter "setMaskEnabled" has issues
SDSCM00019208 Both HeapMin and HeapStd do not allow 0 for the size (both static and dynamic creates).
SDSCM00019240 HeapStd now keeps track of how much RTS memory it has used and errors if too much is requested.
SDSCM00019775 Configuro Fails in CreateProcess() call in WindowsXP if XDCPATH too long
SDSCM00019874 Added cdoc info for isBlocking.
SDSCM00019875 Added Memory_query function.
SDSCM00020681 Added assert in HeapStd_free if remainSize is greater than startSize
SDSCM00021010 'Ptr' type for ti.targets.C28_float should be 2 words (not 1)
SDSCM00021126 name resolution fails on Windows
SDSCM00021632 System_atexit() always returns FALSE
SDSCM00021675 xdc.runtime.Error.getCode() always returns 0
SDSCM00021676 instanceof fails on structs
SDSCM00021972 Bad interaction with Linux automount directory during package release
back to top

Upgrade and Compatibility Information

Warning: Beginning with XDC 2.95, XDC modules with target content (i.e. non-meta-only) are incompatible with non-metaonly modules from XDC 2.94 and earlier. Metaonly modules are not affected. Non-metaonly modules require at least a recompile.

Warning: Beginning with xdc-o02, internal C files generated when building package schemas are named package_<package name>.c instead of <package_name>.c. This may introduce incompatibilities with older xdc-n and xdc-o trees (XDC 2.X products). The compatibility with metaonly xdc-m packages (XDC 1.X products) is still maintained.

Compatibility Key Definitions

Compatibility keys are intentionally independent of Marketing product numbers and 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.

Compatibility keys are composed of 3 comma-delimited numbers - M,S,R - 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:

back to top

Version Information

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, e.g. xdc_3_00.

Subsequent releases of patch upgrades will be identified by the patch number, ex. XDC 3.00.03 with directory xdc_3_00_03. 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

For technical support, contact rtsc_champs@list.ti.com

back to top


Last updated: Dec 21, 2007 Rev: h13