XDC 3.00.05 Release Notes

Feb 6, 2008

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.

back to top

---

Known Issues

None.

back to top

---

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.

back to top

---

What's New

The following significant changes have been made since 3.00.04:

• Device and platform support for OMAP25xx, OMAP35xx and DRA4xx
• CodeSourcery GCC target for ARM v5T
• New configuro, cdoc and repoman features
• Backwards-compatible and forwards-compatible change to XDC module binary contract for improved forwards compatibility
• Bug fixes detailed below

3.00.05 (This Release)

Targets

• Built gnu.targets using XDC 3.00.04 tools to get the runtime libraries for MVArm9 and UCArm9
• Added a target package 'gnu.targets.codesourcery' with two targets GCArmv5t (v5t architecture) and GCArmv6 (v6 architecture). The suffix for GCArmv5t is "470MV" so the libraries built for MVArm9 are going to be supplied to GCArmv5t. getLibs() functions should use target.suffix to decide which library to supply.

Catalogs

• Added support for OMAP devices 2431, 2530, 2531, 3530 3425 and 3525 to ti.catalog.c6000 and ti.catalog.c470
• Added catalog files for DRA402/DRA404/DRA414/DRA416, and updated DRA406 to reflect rev A of data manual
• Changed generic platform so we can use the prefix "OMAP" for OMAP device modules instead of "TMS320C"
• fixed incomplete checks for the presence of properties in the sructure 'regs' when calling getMemoryMap()
• reorganized OMAP devices in c6000 so they all inherit from the interfaces IOMAP2x3x and IOMAP3xxx. Same for DRA4xx devices, to inherit from DRA406

Platforms

• Added evm2530 and evm3530 platforms.
• Added evmDRA416 platform.

Core

• Changed the default implementation of IPackage.getLibs() so that it returns libraries based on the name of the target for which a library was built and the name of the target building the program. If the names are not the same, then suffixes are compared. Currently, the suffix for the library is guessed from the library name because the structure LibDesc does not contain that information.
• Changed VERS for package.c files in Body.java to ensure that package.c files generated by XDC 3.05 and later tools will be rebuilt by the tools based on this XDC 3.00.05 product. This ensures forwards compatibility with target content produced by upcoming XDC releases.
• Added a __FAR__ qualifier and a module name to the symbol __dummy__ declared in package C files. This change makes this file compatible with xDAIS standards.
• Removed dependency of .interfaces goal on .vers files. This dependency prevents us from removing old .vers files when a package is built with different tools without cleaning the package first.
• Extended xdc.exec() and xdc.services.global.Host.exec() to optionally accept the command line via an array of strings. The program name and the arguments are each in a separate array element. Useful when the program name or arguments might contain spaces. Previous versions of xdc.exec() will return a status of -1 if given an array of strings.
• added GZIP support to package release.
• added xdclpf utility to list all package files not in a nested packages. This can be used in conjunction with tar to create a development "snapshot" of a package to be exchanged with others

        cd <package-repository>
        xdclpf ./my/pkg > list
        tar czf my_pkg.tar.gz -T list
  

• fixed bug in XUTL_scanFS where Windows file scan is passed "." and ".." as ordinary files
• hacked fixlist to manipulate file times to avoid tar failures
• fix XUTL_scanFS to behave the same on Windows as on UNIX wrt files that begin with '.' (i.e, they are treated as though they are hidden files).
• added an "all files" flag to XDC_scanFS() to allow clients to include hidden files in the scan.
• extended hacked fixlist to *recursively* manipulate file times to avoid tar failures, made this hack optional (requires -t option), and added a -z option to cause the output to be appropriate for zip rather than tar.
• fixed xdclpf to output *all* files not just the non-hidden files; this makes it more useful for creating a "snapshot" package archive list for tar or zip
• fixed xs usage string

Configuro

• Added new command line options --rtsName and --linkTemplate, giving the ability to specify the XDC rts package name and the linker command file template from the command line.

Cdoc Command Line and GUI

• Made unified C + XS view the default view in cdoc.sg
• Fixed bug in -PR operation, previously behaved like XDC command option "-Pr"
• Removed construct() from XS language view.

Repoman Command Line and GUI

• handle packages and bundles in .zip files

Path Command Line and GUI

• Added -PR option with the same meaning as in XDC and XDOC commands -- find packages recursively, not necessarily rooted at the given directory. Added -Pr option, an alias for -d.

Enhancements

The following minor enhancements were resolved:

Defects

The following defects were resolved:

SDSCM00008143	xdoc does not properly inherit "nodoc"
SDSCM00020709	CDOC generates bad link to type docs
SDSCM00021761	cdoc fixed-width font size in struct field descriptions is microscopic in Firefox
SDSCM00022450	@_nodoc instance paramaters are still being documented
SDSCM00022540	System CDOC is not visible
SDSCM00022656	cdoc should not define construct for metaonly modules
SDSCM00022728	cdoc -l U does not show proxy config parameters
SDSCM00022790	cdoc does not allow @see `links`
SDSCM00022850	Cannot modify decorated name of executable
SDSCM00022907	Offline CDOC must support @link to files
SDSCM00023066	Incorrect linker command template file for sdp2430 package
SDSCM00023151	cdoc in-line code style (via `s) should be able span lines
SDSCM00023391	config.bld along XDCPATH is NOT getting imported.
SDSCM00023410	Offline CDOC has bad links in index tree

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:

• M = Major. A difference in M indicates a break in compatibility.
• S = Source. A difference in S indicates source compatibility. 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.

back to top

---

Host Support

This release supports the following hosts:

• Windows XP
• RedHat Enterprise Linux 3

back to top

---

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.5
• GCC for x86 version 3.2.3 or later
• GCC for ARM version 3.2.3 or later

back to top

---

Device Support

This release supports the following device families:

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

back to top

---

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

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: Feb 6, 2008 Build Ver: 3.00.05.23 Rev: h14