RTSC / XDC (eXpanDed C) is a standard for reusable software
components, optimized for real-time embedded systems. RTSC 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.
XDCtools contains elements released under the Eclipse Public
License v1.0
and a number of other open-source licenses, detailed
here.
Bugs against the XDCtools product maybe filed in the eclipse bugzilla.
The following defects were resolved in this release:
ID | Headline |
ECL276792 | ROV shouldn't require all packages to be found |
ECL322305
| it is not possible to change common$ LOG bits using xgconf |
ECL322947
| Complete list of RTSC platforms do not showup |
back to top
This
release contains some compatibility breaks in order to introduce new
features. The following section describes those compatibility breaks,
and workarounds where available
- Packages with meta-only content are forwards and backwards compatible starting from XDCtools 2.95.01
- xdc.runtime.ILogger interface has changed. Implementors of this interface need to make source code changes. The rest of the xdc.runtime package
is source compatible with XDCtools releases starting from version 3.00.
Target content using this package needs to be recompiled from
source.
- xdc.runtime.knl
package is source compatible with XDCtools releases starting from
version 3.15. Target content using this package needs to be
recompiled from source.
- The package ti.catalog.c470 (deprecated since XDCtools 3.10.04) has been removed. The package ti.catalog.arm. should be used instead.
- C6000 compiler has been upgraded to 7.0. Consumers of C6000 RTSC content built with the whole_program or whole_program_debug profile need to upgrade their compiler version to 7.0 or later.
- Compatibility with specific products
- SYS/BIOS 6.2x or earlier- Incompatible due to changes in xdc.runtime and C6000 compiler versions
- SYS/BIOS 6.30 - Compatible
- DSP/BIOS 5.33.05 or earlier - Compatible but some users may see references to ti.catalog.c470
- DSP/BIOS 5.33.06 or later - Compatible
- Codec Engine 3.00 - Incompatible because of SYS/BIOS 6.2x and changes to xdc.runtime.ILogger
- Codec Engine 2.24,2.25 - Compatible
- Codec Engine 2.20,2.10 - Requires upgrade to DSP/BIOS 5.33.06 or later for compatibility
- Codec Engine 2.00,1.x - Incompatible because of xdc.runtime changes
Package Compatibility Keys
The packages comprising the XDCtools release are uniquely
identified by a
compatibility key defined in the
package.xdc
file of a package. Please note that the package compatibility keys are
independent of XDC product release
numbers.
Package compatibility keys are intended to:
- Enable tooling to identify incompatibilities between
components, and
- Convey a level of compatibility between different releases
to set end user expectations.
Package compatibility keys are composed of 4 comma-delimited
numbers -
M, S, R, P - where:
- M = Major
- A difference in M indicates a break in compatibility. The
package consumer is required to re-write its source code in order to
use the package.
- S =
Source - A difference in S indicates source compatibility.
The package consumer’s source code doesn't require change, but does
require a recompile.
- R = Radix
- A difference in R indicates an introduction of new
features, but compatibility with previous interfaces is not broken. If
libraries are provided by the package, an application must re-link with
the new libraries, but is not required to recompile its source.
- P = Patch
- A difference in P indicates
that only bugs have been fixed in the latest package and no new
features have been introduced. If libraries are provided
by the package, an application must re-link with the new libraries, but
is not required to recompile its source.
back to top
This release supports the following hosts:
- Windows XP
- RedHat Enterprise Linux 3 . CCSv4 IDE integration is not supported on Linux.
back to top
This release requires the following other software components
and tools versions to successfully function:
- TI C6x Code Generation Tools version 7.0 or later
- TI C55 Code Generation Tools version 3.2.0. or later
- TI C54 Code Generation Tools version 4.2.0. or later
- TI C28 Code Generation Tools version 5.2.1 or later
- TI ARM Code Generation Tools version 4.5 or later
- TI MSP430 Code Generation Tools version 3.3.0B1 or later
- GCC for x86 version 3.2.3 or later
- GCC for ARM version 3.2.3 or later
- Code Composer Studio version 4.2.0.09000. Note that this release will not work with CCS 4.1.3 and earlier releases.
back to top
This release supports the following device families:
- C6000 family - C674, C67P, C67, C64P, C64, C62, C66
- C5000 family - C55P, C55, C54
- C2000 family - C28
- ARM processors - TMS470, ARM9, ARM Cortex M3/R4
- MSP430
- Native development host (Windows, Linux)
back to top
This release was built and validated against using the
following components:
- Code Composer Studio version 4.2.0.09000
- TI ARM Code Generation Tools version 4.5.0 and 4.6.1
- TI C6x Code Generation Tools version 7.0.0,7.1.0B2 ,7.2.0A
- TI MSP430 Code Generation Tools version 3.3.0
- TI C55 Code Generation Tools version 3.3.2
- TI C54 Code Generation Tools version 4.2.0
- TI C28 Code Generation Tools version 5.2.3
- GCC for ARM version 3.4.3 and 4.2.1
back to top
The following issues are known to affect this release:ID | Headline |
ECL314790 | Default JVM memory not enough for cdoc |
back to top
All releases have 4 digits (M.mm.pp.bb).
This includes GA and
pre-releases (engineering, EA etc.). Pre-releases are denoted
with a
suffix (e.g. 3.15.01.51-eng).
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, ex. xdctools_3_15_00_50.
Subsequent releases of patch upgrades will be identified by
the patch
number, ex. XDCtools 3.15.01.67 with directory xdctools_3_15_01_67.
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
Support questions on the product should be posted to the RTSC newsgroup. Check the XDCtools download site for the latest releases.
back to top
Last updated: August 24, 2010 Build Ver: 3.20.03.63 Rev: m63