This is a GA release of IPC 1.21.02
Interprocess communication mechanisms including message passing, streams, and linked lists, which work transparently in both uniprocessor and muiltiprocessor configurations.
The IPC product is comprised of the following main packages
The following documentation is available:
User Install Guide | |
User Guide (SPRUGO6A) | |
Doxygen API guide | Documents runtime-APIs, type definitions, error codes and constants |
Cdoc API guide | Documents config-time (RTSC) APIs, Asserts and Errors |
Release notes from previous releases are also available in the relnotes_archive directory.
Changes since IPC 1.21.01:
SDOCM00073312 | evm6474 example Platform.xdc has incorrect memory size for DDR2 |
SDOCM00073098 | Ipc_readConfig logic defects. |
SDOCM00069771 | DM8168/DSS should be renamed to DM8168/VPSS |
SDOCM00071733 | ListMP: obj->attrs must be flushed from cache to help ROV (not a runtime problem, but a big ROV issue) |
SDOCM00068467 | Need Ipc_detach() to handshake with remote core |
SDOCM00072080 | add support for catalog/Netra part -- C6A8168 |
SDOCM00072213 | MultiProc_getId should assert that name != NULL |
SDOCM00072433 | Notify_sendEvent: uninitialized 'status' variable is returned upon successfully executing loopback event |
SDOCM00072646 | MultiProc.setConfig should check for duplicate names in nameList |
SDOCM00072649 | change notify ids used internally by IPC to be 0, 1, .., n. Use Notify system key when registering internally within IPC. |
SDOCM00072082 | GateMP should use a 'GateAll' gate instead of GateHwi |
SDOCM00072942 | GateAAMonitor_Instance_init hits assert when cacheLineSize = 0 |
SDOCM00071788 | Notify_Module_startup should assert that MultiProc_self() != MultiProc_INVALIDID |
SDOCM00071741 | Tom/Far/Nyq/Shan should offer ability to set MultiProc ID automatically at startup time |
SDOCM00071907 | update C6x/ELF targets to use mid-July 7.2 "alpha-build3" codegen for ELF targets (not COFF) |
For information on enhancements and defect fixes in earlier releases, please refer to the release notes from previous releases that are available in the relnotes_archive directory.
Interface/API changes:
All of the APIs in IPC 1.21.02 are compatible with IPC 1.20. However, code using IPC 1.20 will have to be recompiled for use with IPC 1.21.02. You must recompile -- relink will not work.
The following shared-memory interface changes have been made between IPC 1.21.01 and 1.21.02:
ti.sdo.ipc.* and ti.sdo.utils.* APIs in the IPC 1.21.XX.XX releases are not compatible with those in the IPC 1.00.0X.XX (GA) release. These APIs have been updated to be consistent with the Linux APIs to share common header files in ti/ipc/. However, APIs in the ti.sdo.io package have not changed since the 1.00 GA release.
DM8168 MultiProc name changes
The valid MultiProc names for DM8168 have been changed in IPC 1.21.02 to match the official names. They are now as follows:
'ti.sdo.ipc.examples.platforms.simDM8168.xxx' sample platforms in IPC have been renamed to 'ti.sdo.ipc.examples.platforms.evmDM8168.xxx'. Applications should use 'evmDM8168' instead of 'simDM8168' if the applications are using the example platforms packaged with IPC. Existing platforms generated using the platform wizard are not affected by this change.
This release supports the following hosts:
Windows XP SP2/SP3
Windows Vista
Linux (Redhat 4 and 5)
This release requires the following other software components and tools versions to successfully function:
SDOCM00068256 | The linker will product a warning about "placing code in a data section" when building c6x applications using the whole_program[_debug] build profile for some devices. It is safe to ignore this warning. |
All releases have 4 digits (M.mm.pp.bb). This includes GA and pre-releases (engineering, EA, beta, etc.). Pre-releases are denoted with a suffix (e.g. 1.21.00.01_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. ipc_1_21_00_01.
Subsequent releases of patch upgrades will be identified by the patch number, ex. IPC 1.21.00.01 with directory ipc_1_21_00_01. 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, use the community forum TI E2E Community, or email softwaresupport@ti.com.
Last updated: Aug 09, 2010