| |
|
Introduction, Documentation, What's New, Upgrade & Compatibility Information, Host Support, Dependencies, Device Support, Validation Info, Known Issues, Version Information, Technical Support.
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 3.10 is an Engineering Release. It includes the following sets of packages:
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 in the 3.10 release:
Starting with release 3.10 this product is known as "XDCtools", replacing its previous name "XDC". For now we'll continue to refer to pre-3.10 product releases as "XDC" but will use "XDCtools" for new releases.
The name of the default product install location has also changed from "xdc_version" to to "xdctools_version".
Note: The change in the name of the default installation directory may require customers to change makefiles or other build artifacts when migrating to this release.
By default, XDCtools will now install under "C:\Program Files\Texas Instruments" on Windows, instead of its previous "C:\". Note that on Windows XDCtools now supports space characters in the install location and in repository names.
Note: If you are using XDCtools from Makefiles or other build systems, the space character in the path to XDCtools may impact your own build files. Workarounds are to quote the path to XDCtools in your makefiles, or to install XDCtools in a non-default location.
XDCtools now integrates with Code Composer Studio v4 (CCSv4) IDE and is bundled with the CCSv4 Early Adopter product. Users can build and run applications that use RTSC content in an integrated graphical environment.
The integration features include:
The product documentation has been rewritten to make it easier to find what you need, more accurate, more complete, and more up to date.
In addition to the documents delivered in the product, we'll update and add to the documents on a public web site, so you can always access the most useful information available. Check for announcements at http://rtsc.eclipse.org.
The new gnu.targets.arm.* RTSC target modules
can be used with any GCC-based compiler for Arm.
Three such targets are available: gnu.targets.arm.GCArmv5T,
GCArmv6 and GCArmv7A. These targets
support Arm instruction set devices, using little-endian byte ordering, and using GLIBC. The targets are binary compatible with the gnu.targets.MVArm9 and gnu.targets.codesourcery.GCArmv5T targets. The new targets are configured by setting the name of the gcc executable in
their LONGNAME config parameter, typically in config.bld.
The new host.platforms.arm platform package supports any
Arm-based board that does not need a platform memory map. Many Linux-based
applications don't care about memory map, since Linux takes care of that for
user space. This RTSC platform package supports most such applications, even
on custom hardware, without the need for a custom RTSC platform package.
The host.platforms.arm platform need only be configured to
name the (Arm-based) device present on the board, which can then supply the
device's on-chip memory map and other similar information. The device is
named using the platform's config params deviceName and
catalogName, typically in the user's
config.bld file.
The xdc.tools.cdoc and xdc.tools.cdoc.sg documentation tools feature a new presentation format along with complete and accurate API information for all spec'd RTSC objects. The tools remain command-line compatible with previous releases.
The xdc.bld.ITarget interface now supports features for declaring and testing binary compatibility between different targets. This allows the
targets for device families with compatible instruction sets, such as Arm and TI C6000 devices, to mix target content built for different instruction sets. The new features are the findSuffix() method and the compatibleSuffixes config param, and are of interest to anyone who writes a target or a getLibs() function.
The following defects were resolved in this release:
| SDSCM00027063 | %XDCROOT% added to System Variable Path does not always expand |
| SDSCM00027015 | xdc -PD . fails from with cygwin shell |
| SDSCM00026849 | ROV fails with strange error message if .out file lives in a directory with spaces. |
| SDSCM00026768 | Semaphore ROV view is distorted for test case ipc/tests/MailboxTest3 |
| SDSCM00026711 | Get this warning when section placed at a specific address. |
| SDSCM00026589 | System_flush call is required to flush legacy LOG buffers to CIO when using ROM |
| SDSCM00026529 | Pkg.addExecutable should validate 'name' argument |
| SDSCM00026519 | Can't open cdoc via command line |
| SDSCM00026494 | utils.tci file permissions result in build error on Linux |
| SDSCM00026477 | Shortcut link in start menu to XDCtools API Documentation is broken |
| SDSCM00026447 | cdoc index.html fails to open correctly on Linux due to case sensitive issue |
| SDSCM00026437 | HeapMem should have an Assert to catch non-zero alignment parameter |
| SDSCM00026433 | CCS4.0 ROV GUI: " No Instance "message is vanishes if switch to another view and return |
| SDSCM00026167 | do not generate --symbol_map aliases in TI linker .cmd file for ROM app builds (affects debug) |
| SDSCM00026035 | problem with ROM build in recent xdc tree ('field is sealed error message)' |
| SDSCM00025965 | Further deprecate Arg to avoid accidental usage |
| SDSCM00025956 | With spaces in the installation path xdc -P throws error |
| SDSCM00025894 | Configuration support for DM360 needed |
| SDSCM00025788 | cdoc for ICmd tools should provide "man page" view |
| SDSCM00025719 | Typing error in XDC consumer's user guide |
| SDSCM00025605 | ROV should display IArg and UArg fields as 0x000-padded hex values by default |
| SDSCM00025599 | cdoc should provide a way to specify initial page |
| SDSCM00025571 | command line tools are inconsistently/incoherently documented |
| SDSCM00025382 | Can't open XDC file in the CDOC |
| SDSCM00025375 | need catalog file for DA830 (and other DA8xx devices) and platform file for evmDA830 |
| SDSCM00025336 | we need whole_programd profile for assorted targets to build whole_program with debug |
| SDSCM00025333 | remove -oe from debug and release profiles, add support for whole_program library builds |
| SDSCM00025328 | xgconf issues dialog error when adding modules via the GUI interface |
| SDSCM00025303 | change to Types.xdc in xdc.runtime is not compatible with BIOS 6.10.00.10 ROM |
| SDSCM00025269 | Can' run ROV test Scripts: Error about timestamp |
| SDSCM00025176 | "??????" shows up in several cdoc pages |
| SDSCM00025175 | need fixed syntax for links into cdoc generated html |
| SDSCM00025174 | Uninstall shortcut is created on desktop instead of in the Start --> Program Folder where the doc shortcuts are created |
| SDSCM00025162 | Incorrect list from GCArmv6 target getISAChain |
| SDSCM00025122 | Module instance should contain name of instances used when created in the configuration file |
| SDSCM00025082 | Unable to downgrade compatibility check in config.bld script |
| SDSCM00025028 | sdp3430 platform does not accept code built for v7A architecture |
| SDSCM00024967 | Reduce length of cast when converting a real module/handle to an abtract module/handle. |
| SDSCM00024819 | Targets should be able to declare ABI compatibility with other targets |
| SDSCM00024719 | Java class files with '$' in the name should not be in the release |
| SDSCM00024626 | Static Params structs are not fully initialized |
| SDSCM00024622 | Need to add support for multicore Arm devices with shared memory |
| SDSCM00024530 | Unable to create static instance of GateNull |
| SDSCM00024448 | module configs don't appear in Module-Wide Configuration Parameters section of CDOCs. |
| SDSCM00024414 | Module.common$.gate when used with non-gated modules should issue a warning |
| SDSCM00024380 | xdc.tools.mkpkg is missing from XDC 3.10.00.16 package |
| SDSCM00024033 | if not set, LoggerBuf's default TimestampProxy should be assigned to Timestamp's proxy (not TimestampNull) |
| SDSCM00023979 | RuntimeExecptions should display stack traceback |
| SDSCM00023931 | Support for generating indexes in cdoc |
| SDSCM00023928 | The -P option to cdoc is broken |
| SDSCM00023873 | CDOC does not escape some illegal XML characters |
| SDSCM00023870 | Program section map property not working |
| SDSCM00023813 | Core_createObject() should use 'malloc' not 'calloc' for consistent create/construct precondition |
| SDSCM00023810 | SysStd_ready CDOC issue |
| SDSCM00023793 | xs -m option is broken |
| SDSCM00023700 | XDC product should deliver prebuilt cdoc |
| SDSCM00023686 | cdoc does not allow @nodoc of fields |
| SDSCM00023578 | Error in lexical analysis phase does not return information about location |
| SDSCM00023530 | GNU targets should use lazy version check on codegen tools |
| SDSCM00023472 | Confirm install directory during installation |
| SDSCM00023458 | Linker warning issued from generated linker file when ROM image is used |
| SDSCM00023410 | Offline CDOC has bad links in index tree |
| SDSCM00023249 | paths ending with '/' are not treated as identical to those without the '/' on Windows |
| SDSCM00023225 | Gate_enterSystem() does not always enter the System gate |
| SDSCM00023151 | cdoc in-line code style (via `s) should be able span lines |
| SDSCM00023066 | Incorrect linker command template file for sdp2430 package |
| SDSCM00023044 | SysMin needs user supplied flush function |
| SDSCM00022907 | Offline CDOC must support @link to files |
| SDSCM00022905 | CDOC @see must be allowed anywhere in a comment |
| SDSCM00022826 | Corrupt .ccs file needs better error message |
| SDSCM00022817 | xdc.runtime.startup module CDOC description needs to explain the start up sequence |
| SDSCM00022794 | XDC tool does not report location of type error in specification file |
| SDSCM00022790 | cdoc does not allow @see `links` |
| SDSCM00022728 | cdoc -l U does not show proxy config parameters |
| SDSCM00022656 | cdoc should not define construct for metaonly modules |
| SDSCM00022597 | "cdoc -l C" fails on meta-only units |
| SDSCM00022540 | System CDOC is not visible |
| SDSCM00022500 | XDC release note issue |
| SDSCM00022492 | xdc.runtome.LoggerBuf may corrupt memory |
| SDSCM00022491 | xdc.runtime.Memory may leak memory |
| SDSCM00022475 | GetStats for Heapmin allocs returns invalid free size on PADK |
| SDSCM00022464 | HeapMin CDOC issues |
| SDSCM00022450 | @_nodoc instance paramaters are still being documented |
| SDSCM00022284 | Error_raise may spontaneously abort |
| SDSCM00021991 | error message when client app uses incompat codegen needs to be improved |
| SDSCM00021945 | Docs to state buffer is not flushed until flush() called explicitely if SysMin proxy used |
| SDSCM00021931 | Configuro BTI uses config.importPath incorrectly |
| SDSCM00021901 | Error_getMsg returns extra char along with message |
| SDSCM00021757 | cdoc struct field summaries are not output |
| SDSCM00021756 | cdoc shows bogus internal data structures not in any spec file |
| SDSCM00021755 | links can't be copied from cdoc pages into emails |
| SDSCM00021754 | links into cdoc don't work with IE |
| SDSCM00021632 | System_atexit() always returns FALSE (new bug in 3.00.03) |
| SDSCM00021494 | whole_program profiles need to provide hooks to add additional options (e.g., code size -ms1) |
| SDSCM00021208 | comment has repeating words... |
| SDSCM00021045 | System_printf() should support %f for floating point parts |
| SDSCM00021033 | Error_getSite returns null for file name field |
| SDSCM00020839 | In XDC Diags module: setMask API is not working |
| SDSCM00020828 | assorted configuration parameters for binding system gate are confusing |
| SDSCM00020777 | In XDC Diags module: setMaskEnabled API is not working correctly |
| SDSCM00020724 | add catalog files for OMAP35xx and OMAP25xx |
| SDSCM00020682 | LoggerBuf_flushAll ( ) does not flush log to stdout |
| SDSCM00020676 | Log and System need to support 32-bit floats |
| SDSCM00020604 | XDC error messages should be short and helpful |
| SDSCM00020601 | XDC should support script trace level command line options |
| SDSCM00020500 | Incorrect linker command template filename for sdp3430 platform |
| SDSCM00020425 | ROM - No default heap inst in romimage |
| SDSCM00020418 | Poor error message for misplaced package requires statement |
| SDSCM00020305 | LoggerBuf_Params |
| SDSCM00020304 | LoggerBuf_flush() description needs modification in CDOC |
| SDSCM00020303 | LoggerBuf_getNextEntry() needs more description in CDOC |
| SDSCM00020302 | Conversion functions from LoggerBuf_Struct * to LoggerBuf_Handle missing in CDOC |
| SDSCM00020276 | Issue with errorID.code parameters |
| SDSCM00019876 | CDOC for Memory_getMaxDefaultTypeAlign needs modification |
| SDSCM00019319 | HeapStd documentation should discuss heap locking |
| SDSCM00018941 | cdoc static generation should allow generation of both C and XS |
| SDSCM00018901 | System should validate that System gate is non-blocking and not preemptive |
| SDSCM00018900 | Need to handle STATIC_POLICY in System.xs |
| SDSCM00018899 | Need more comments in System module |
| SDSCM00018693 | Select declaration in content browser when specified on cdoc.sg command line |
| SDSCM00017878 | random characters in the XDCPATH environment variable cause problems, error message is vague |
| SDSCM00017876 | Module inheritance not shown in cdoc |
| SDSCM00016712 | LoggerBuf.enableFlush = true does not work as expected when using SysMIn. |
| SDSCM00016451 | DOC - ROV section in UG |
| SDSCM00016323 | Error_raise requires too much stack |
| SDSCM00015096 | cdoc should include all the good stuff from xdoc (except back bug) and replace xdoc |
| SDSCM00014204 | xgconf app icon is missing |
| SDSCM00012331 | xdoc does not show override docs |
| SDSCM00012325 | xdoc @a and @b headings should support multiple white space separated words |
| SDSCM00010402 | Object deletion must be carefully orchestrated so ROV doesn't get confused |
| SDSCM00007060 | 'can't find package' error could be clearer |
| SDSCM00007050 | XDC build should print where loaded packages are found |
| SDSCM00006989 | repositories in directories with embedded spaces should be supported |
| SDSCM00003764 | RTA should show CPU % utilization by thread |
| SDSCM00003758 | Display HWIs in the execution graph |
| SDSCM00003753 | DSP/BIOS RTA execution graph should support dynamic objects |
Warning:Starting with XDC 2.95, XDC packages with target content are incompatible with target content from previous releases. Compatibility of meta only content is not affected. Packages with target content would require a recompile. Starting with XDC 3.00 release both backward and forward compatibility is maintained for all content.
The packages comprising the XDC 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:
Package compatibility keys are composed of 4 comma-delimited numbers - M, S, R, P - 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:
| SDSCM00026703 | ROV - Crashes when opened while target is running |
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. xdctools_3_00.
Subsequent releases of patch upgrades will be identified by the patch number, ex. XDCtools 3.00.03 with directory xdctools_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: August 01, 2008 Build Ver: 3.10.00.42 Rev: j41