XDC 3.00.01.10 Release Notes

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.

Known Issues

Documentation

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

What's New

3.00.01.10 (This Release)

Targets

Added C28_float to ti.targets
Fixed C647 compiler options

Platforms

Added DM355 device
Fixed 'space' property in memory maps for 283xx devices
Fixed memory map for MSP430
Added C28332, C28334, C28335 catalog files to c2800 catalog
Added ezdsp28335 platform
Added an initial version of evmDM355 platform
Fixed evmDM6446 so it has the right codeMemory for both DSP and ARM; added SRAM to the external memory for ARM
Set external SRAM to "code/data" in ezdsp28335

XDC Core

The vector 'allvec' in Proto.java in xdc.services.intern.xsr kept references to all created structures, even temporary ones. As a result, the Java's garbage collector couldn't delete any of them, and for some large packages the "out of memory" error would occur. The vector is now removed, and Error.xs and Assert.xs now use a different way to search for their descriptors, the same one that Log.xs was using previously. Schemas have two new sections to allow for the new functionality.
Array that keeps track of dependencies between packages was incomplete and incorrect; the first problem was that is xdc.useModule was called for a module from an already loaded package, xdc.loadPackage wasn't called and the dependency wasn't recorded; the second problem was that xdc.useModule did not set $curpkg correctly before calling xdc.module (SDSCM00019923); the issues were fixed in this tree
Reduced tool execution time in some cases using buffered Java file operations. Changes are in xdc.services.* and xdc/template.xs.

Enhancements

The following minor enhancements were resolved:

Defects

The following defects were resolved:

SDSCM00014176	Memory leak in Project Manager
SDSCM00019239	Pkg.attrs.exportAll should not release package.mak
SDSCM00019638	exportAll bring in too much on Windows
SDSCM00019923	module$use does not always record additional package-to-package dependencies
SDSCM00019993	ti.targets.C647.xdc uses wrong rts library
SDSCM00019996	DSP BIOS: Can't run tcf file using Graphical Debugger
SDSCM00020028	xdc.useModule() fails on interfaces
SDSCM00020068	use "code/data" for external SRAM

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:

Enable tooling to identify incompatibilities between components, and
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:

M = Major. A difference in M indicates a break in compatibility.
S = Source. A difference in S indicates source compability. That is, the user's source doesn't require change, but does require rebuilding.
R = Radix. A difference in R indicates an introduction of new features, but compatibility with previous interfaces has not broken. If libraries are provided by the package, an application must re-link with the new libraries, but not rebuild from source.

Host Support

This release supports the following hosts:

Windows XP
RedHat Enterprise Linux 3

Dependencies

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

C6x Code Generation Tools version 5.3.0 or later. Version 6.0.13 or later is required in order to use whole_program build profile.
C55 Code Generation Tools version 3.2.0. or later
TMS470 (Arm) Code Generation Tools version 4.1.4
GCC for x86 version 3.2.3 or later
GCC for ARM version 3.2.3 or later

Device Support

This release supports the following device families:

C67P, C67, C64P, C64, C62
C55P, C55, C54
C28
TMS470
Native development host (Windows, Linux)

Validation Information

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

Code Composer Studio version 3.3
C6x Code Generation Tools version 6.0.7 and 6.0.13
C55 Code Generation Tools version 3.2.2
GCC for x86 version 3.2.3
GCC for ARM version 3.2.3

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.

Technical Support

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

Last updated: Oct 02, 2007

XDC 3.00.01 Release Notes

Oct 02, 2007

Introduction