![]() |
![]() |
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:
SDSCM00023774 | Partial stack traces are emitted if an exception is thrown in the 'close' method in package.xs |
SDSCM00023772 | gnu.targets.Linux86 target no longer supports GCC 3.X |
SDSCM00021754 | links into cdoc don't work with IE |
SDSCM00021126 | name resolution fails on Windows |
SDSCM00021087 | ti.targets.c6x targets need to flag incompatible libraries when using whole_program and 6.1/6.0 tool mix |
SDSCM00023928 | The -P option to cdoc is broken |
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.05 release:
The following defects were resolved in this release:
SDSCM00024530 | Unable to create static instance of GateNull |
SDSCM00024226 | xs xdc.tools.cdoc.sg --help dumps stack |
SDSCM00024033 | if not set, LoggerBuf's default TimestampProxy should be assigned to Timestamp's proxy (not TimestampNull) |
SDSCM00023991 | Main and Memory modules "namedModule" value being set true, internally though default is false |
SDSCM00023979 | RuntimeExecptions should display stack traceback |
SDSCM00023873 | CDOC does not escape some illegal XML characters |
SDSCM00023813 | Core_createObject() should use 'malloc' not 'calloc' for consistent create/construct precondition |
SDSCM00023810 | SysStd_ready CDOC issue |
SDSCM00023793 | xs -m option is broken |
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 |
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 |
SDSCM00023044 | SysMin needs user supplied flush function |
SDSCM00022985 | can't create genx examples |
SDSCM00022982 | Can't open online documention for XDC package - xs xdc.tools.cdoc.sg |
SDSCM00022905 | CDOC @see must be allowed anywhere in a comment |
SDSCM00022794 | XDC tool does not report location of type error in specification file |
SDSCM00022597 | "cdoc -l C" fails on meta-only units |
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 |
SDSCM00022284 | Error_raise may spontaneously abort |
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 |
SDSCM00021754 | links into cdoc don't work with IE |
SDSCM00021676 | instanceof fails on structs |
SDSCM00021675 | xdc.runtime.Error.getCode() always returns 0 |
SDSCM00021632 | System_atexit() always returns FALSE (new bug in 3.00.03) |
SDSCM00021045 | System_printf() should support %f for floating point parts |
SDSCM00021044 | Add format description to System_printf() cdoc (similar to SYS_printf()) |
SDSCM00021033 | Error_getSite returns null for file name field |
SDSCM00021010 | 'Ptr' type for ti.targets.C28_float should be 2 words (not 1) |
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 |
SDSCM00020682 | LoggerBuf_flushAll ( ) does not flush log to stdout |
SDSCM00020681 | In XDC Memory module: The Memory Free API wrongly updates the Total Free Size |
SDSCM00020676 | Log and System need to support 32-bit floats |
SDSCM00020605 | troubleshooting doc indexed by error codes |
SDSCM00020604 | XDC error messages should be short and helpful |
SDSCM00020582 | platform ti.platforms.sdp3430 must support TI and GCC targets |
SDSCM00020449 | xdc.useModule() fails on interfaces |
SDSCM00020425 | ROM - No default heap inst in romimage |
SDSCM00020418 | Poor error message for misplaced package requires statement |
SDSCM00020380 | rtsarm9/boot.asm in ti.targets.arm9 contains 16-bit code in 32-bit section |
SDSCM00020305 | LoggerBuf_Params needs more description in CDOC |
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 |
SDSCM00020271 | Errors in XDC Getting Started Guide |
SDSCM00019876 | CDOC for Memory_getMaxDefaultTypeAlign needs modification |
SDSCM00019875 | We need to have Memory_isBlocking API |
SDSCM00019775 | Configuro Fails in CreateProcess() call in WindowsXP if XDCPATH too long |
SDSCM00019319 | HeapStd documentation should discuss heap locking |
SDSCM00019240 | HeapStd needs to check Program.heap before creating instance |
SDSCM00019143 | Diags: ENTRY and EXIT masks have issues with SysStd |
SDSCM00019114 | Diags: setMaskMeta() is not recognised |
SDSCM00019111 | Diags: Config Parameter "setMaskEnabled" has issues |
SDSCM00018941 | cdoc static generation should allow generation of both C and XS |
SDSCM00018922 | xdc.runtime.Text.isLoaded = false does not work |
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 |
SDSCM00018190 | xdc.runtime.Defaults needs proper xdoc |
SDSCM00017878 | random characters in the XDCPATH environment variable cause problems, error message is vague |
SDSCM00017876 | Module inheritance not shown in cdoc |
SDSCM00017816 | xdoc parser fails on doc tag before module |
SDSCM00016712 | LoggerBuf.enableFlush = true does not work as expected when using SysMIn. |
SDSCM00016323 | Error_raise requires too much stack |
SDSCM00015332 | XDC Verbose option should print the full path to each package it loads |
SDSCM00015096 | cdoc should include all the good stuff from xdoc (except back bug) and replace xdoc |
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 |
SDSCM00007080 | XDC command help message is hard to find |
SDSCM00007060 | 'can't find package' error could be clearer |
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:
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: Mar 28, 2008 Build Ver: 3.05.00.05 Rev: i05