Introduction, Known Issues, Documentation, What's New, Upgrade & Compatibility Information, Host Support, Dependencies, Device Support, Validation Info, Version Information, Technical Support.
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:
None.
The following documentation is available:
Release notes from previous releases are also available in the relnotes_archive directory.
The following significant changes have been made since 3.00.04:
cd <package-repository> xdclpf ./my/pkg > list tar czf my_pkg.tar.gz -T list
The following minor enhancements were resolved:
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 |
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 keys are intentionally independent of Marketing product numbers and are intended to:
Compatibility keys are composed of 3 comma-delimited numbers - M,S,R - where:
This release supports the following hosts:
This release requires the following other software components and tools versions to successfully function:
This release supports the following device families:
This release was built and validated against using the following components:
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.
For technical support, contact rtsc_champs@list.ti.com
Last updated: Feb 6, 2008 Build Ver: 3.00.05.23 Rev: h14