XDC __VERSTRDOTSPECIFIC__ Release Notes

__DATE__

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:

• XDC core (xdc.*) - the xdc and xs command line utilities for building packages and execting scripts, together with the packages that implement XDC itself;
• 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 with XDC;
• Platforms (ti.platforms.*) - definitions for linking and running code on various TI board-level hardware and simulator products using XDC.

---

Known Issues

None.

---

Documentation

The following documentation is available:

• XDC Getting Started Guide
• XDC Consumer User's Guide
• XDC Documents Index

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

---

What's New

The following significant changes have been made since 3.00:

• Bug fixes to enable XDC 3 to replace XDC 1 in DSP/BIOS 5 product.
• Added platform and device support for C2833x, DM355.
• Bug fixes detailed below.

__VERSTRDOT__ (This Release)

Targets

• Added C28_float to ti.targets
• xdc.runtime for TI Arm targets build using codegen 4.5.0A07292
• added the missing '-mt' switch to Arm9t alchemy options

Platforms

• Added ezdsp28335 platform
• Fixed evmDM6446 so it has the right codeMemory for both DSP and ARM; added SRAM to the external memory for ARM
• Added evmDM355 platform
• added the package tests and XDC configuration files for osk5912
• removed evmDM6446arm and osk5912arm
• fixed platform description comments in ezdsp2812 and ezdsp28335
• Added Arm configuration to sdp3430 (SDSCM00020582)

Catalogs

• Fixed 'space' property in memory maps for 283xx devices
• Added DM355 device
• Added TMS320C3430 to ti.catalog.c470
• Added .xs file for F761990 device in c6000
• Added C28332, C28334, C28335 catalog files to c2800 catalog

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.
• Deprecated xdc.usePackage(), which has a bad use model. It "uses" every module in the named package, which almost always leads to unintentional, unreported bloat in the executable. Now issues a warning when called. Also fixed a bug in this function that suggests that it is not actually called by anyone (SDSCM00020812).
• fixed incompatibilities with glibc on older linux releases (CQ18575, CQ20886)

Enhancements

The following minor enhancements were resolved:

Defects

The following defects were resolved:

SDSCM00014176	Memory leak in Project Manager
SDSCM00018575	Redhat 9 Codec Engine Server build errors
SDSCM00018799	evmDM6446arm platform should be removed, and evmDM6446 used instead
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
SDSCM00020217	Description for eZdsp2812 configuration seed file needs correction
SDSCM00020380	rtsarm9/boot.asm in ti.targets.arm9 contains 16-bit code in 32 bit section
SDSCM00020403	xdc build should not include --args in .cmd file when building tconf based project
SDSCM00020489	The Raven [F761990] catalog part needs to be fixed
SDSCM00020582	platform ti.platforms.sdp3430 must support TI and GCC targets
SDSCM00020595	assert.tci is missing from xdctools/include directory
SDSCM00020775	remove .template/C++ workaround from generated .xdl file for TI targets
SDSCM00020807	alchemy options for Arm9t (thumb) are incorrect
SDSCM00020812	xdc.usePackage should be deprecated
SDSCM00020855	loadXML() in xdc.tci doesn't close BufferedReader before returning
SDSCM00020886	BIOS 5.32's version of tconf crashes or hangs on older versions of Linux

---

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:

• 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: __DATE__ Rev: __REV__