XDCtools 3.22.03.41 GA Release Notes

September 16, 2011

Introduction, Documentation, License, What's New, Upgrade & Compatibility Information, Host Support, Dependencies, Device Support, Validation Info, Known Issues, Version Information, Technical Support.

---

Introduction

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.

The XDCtools product includes the following components:

• Core (xdc.*) - the xdc and xs command line utilities for building packages and executing scripts as well as core packages used during the configuration and target execution of RTSC modules;
• 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;
• Platforms (*.platforms.*) - definitions for linking and running code on various TI and third-party board-level hardware and simulator products; and finally
• Eclipse (eclipse) - a set of integration plugins for RTSC for the eclipse platform. These plugins are leveraged by CCS (Code Composer Studio) to provide support for integrating RTSC content in the IDE environment.

back to top

---

Documentation

The product documentation for this release is available in two formats:

• Compressed .zip file archive
• Microsoft HTML Help .chm file

Both formats are delivered with the product in the docs subdirectory. The most up-to-date docs can also be viewed online in the RTSC-Pedia.

Release notes from previous product releases are available in the relnotes_archive directory. Note that  XDCtools 3.21 (which supports only the MSP430 device family) is shipped only with the Grace product. 

back to top

---

License

XDCtools contains elements released under the Eclipse Public License v1.0 and a number of other open-source licenses, detailed here.

---

What's New

The following significant changes are included in XDCtools 3.22 :

• XGCONF Enhancements
• New Platform Support
• Eclipse Integration Enhancements

XGCONF Enhancements

• Script generation now produces shorter more readable scripts
• Real-time validation is now possible; this makes it possible to validate user input before re-building
• Modules can now provide graphical view of their configuration parameters
• The available packages view can now show a device specific subset
  

New Host and Target Platform Support

• XDCtools now supports Windows 7 and Ubuntu 10.04
• added support for the evm5525, evmAM3359, ezdsp5502, and ezdsp5535 hardware platforms (ti.platforms.evm5525, ti.platforms.evmAM3359, ti.platforms.ezdsp5502, ti.platforms.ezdsp5535)
• added Arm A8 Neon, vector floating point target (ti.targets.arm.elf.A8Fnv)
• added support for TI's MSP430 4.0 compiler (COFF only)
• added support for TI's Arm 4.9 compiler

Eclipse Integration Enhancements

• Product supports CCSv5 on Linux(Ubuntu 10.04) and Windows XP/7
• An enhanced error parser is provided with this release
• Standard make project integration allows users to leverage RTSC build within CCS.

---

Defect history and changes in 3.22.03.41 (This Release)

ID	Headline
351983	dependencies between executables and imported libraries is broken
291686	multiple imports of the same named module do not trigger error
344740	Error when SourceDir.outputDir is set to a relative path within a directory with spaces
355425	configuro output directory names can't end with a slash
347085	configuro syntax error in generated config.bld
354063	Concerto 28x memory map needs to reserve FLASH/password section

---

Upgrade and Compatibility Information

 The following section describes 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 in XDCtools 3.20. 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.
• 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.20 and 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:

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

---

Host Support

This release supports the following hosts:

• Windows XP, Windows 7
• RedHat Enterprise Linux 3 and Ubuntu 10.04 . Note that IDE integration on Linux is only supported for CCSv5 on Ubuntu 10.04.

back to top

---

Dependencies

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 ARM Code Generation Tools version 4.5 or later
• TI MSP430 Code Generation Tools version 3.3.0 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.10017 and 5.0.0.00095. Note that this release will not work with CCS 4.1.3 and earlier releases.

back to top

---

Device Support

This release supports the following device families:

• C6000 family - C674, C67P, C64P, C66, C64T
• C2000 family - C28
• ARM processors - TMS470, ARM7/9, Cortex A8/M3/R4
• MSP430
• 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  4.2.0.10017 and 5.0.0.00095
• TI ARM Code Generation Tools version 4.9.0 
• TI C6x Code Generation Tools version 7.0.3,7.2.0
• TI MSP430 Code Generation Tools version 3.3.0
• TI C28 Code Generation Tools version 5.2.3
• GCC for ARM version 4.3.2 (CodeSourcery), 4.2.1 and 3.4.3 (Montavista) 

The code generation tools used for the various RTSC targets shipped with the product are shown below:

RTSC Target	Code Generation Tools
ti.targets.[C64P,C64P_big_endian,C67P,C674,C674_big_endian,C64T,C64T_big_endian,C66,C66_big_endian]	7.0.3 (TMS320C6x, COFF)
ti.targets.[C28,C28_large,C28_float]	5.2.3 (TMS320C2000)
ti.targets.elf.[C64P,C64P_big_endian,C64T,C64T_big_endian,C66,C66_big_endian,C674,C674_big_endian,C67P]	7.2.0 (TMS320C6x, ELF)
ti.targets.arm.elf.[TMS470,Arm7,Arm9,Arm9t,A8Ft,M3,M3_big_endian,R4,R4_big_endian,R4t,R4t_big_endian,R4F,R4F_big_endian,R4Ft_big_endian]	4.9.0 (ARM/TMS470)
gnu.targets.MVArm9,gnu.targets.arm.GCArmv5T	3.4.3 (GCC Montavista)
gnu.targets.UCArm9	4.2.1 (GCC Opensource)
gnu.targets.arm.GCArmv6,GCArmv7A	4.3.2 (GCC Codesourcery)
gnu.targets.[Linux86,Sparc]	4.1.0 (GCC Opensource)
gnu.targets.Mingw	4.4.0 (GCC MingW)
microsoft.targets.Net32	13.10.3052 (Microsoft .NET C/C++)
microsoft.targets.Win32	14.00.50727.42 (Microsoft Visual C/C++)
microsoft.targets.VC98	12.00.8168 (Microsoft Visual C/C++)
microsoft.targets.arm.WinCE	14.01.60511 (Microsoft WinCE 6.00)
ti.targets.msp430.[MSP430,MSP430X,MSP430X_small]	3.3.0 (MSP430)

back to top

---

Known Issues

ID	Headline
280863	xgconf: If instances have required args, should force user to enter something
280869	xgconf: Can create two instances with the same name
305948	xgconf does not respond to config file rename
321074	xgconf and XDCtools error parser add duplicate errors to Problems view

Editing RTSC .cfg file while using ROV can cause Java out of memory error

The RTSC editor for .cfg files (XGCONF), and the Runtime Object Viewer debug window (ROV) both consume a lot of Java heap memory. Using both at the same time, or editing multiple .cfg files at the same time, can cause CCS (v4 or v5) to run out of Java heap memory and crash during heavy use. Workaround is to edit only one .cfg file at a time, and close XGCONF while using ROV.

back to top

---

Version Information

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

---

Technical Support

Support questions on the product should be posted to the RTSC newsgroup. Check the XDCtools download site for the latest releases and RTSC-Pedia (http://rtsc.eclipse.org/docs) for the latest documentation.

back to top

---

Last updated: September 16, 2011 Build Ver: 3.22.03.41 Rev: