|
|
|
IPC 1.24.01.24 is an GA release of IPC
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 (SPRUGO6D) | |
| Doxygen API guide | Documents runtime-APIs, type definitions, error codes and constants |
| Cdoc API guide | Documents config-time (RTSC) APIs, Asserts and Errors; Indexed and searchable within CCS/Eclipse |
Manifest and License:
IPC Software Manifest and License
Release notes from previous releases are also available in the relnotes_archive directory.
Changes since IPC 1.24.00:
| SDOCM00082673 | SharedRegion_start() asserts if SR owner is not SR0 owner and tries to create a heap |
| SDOCM00083262 | Resolve IPC startup handshake and Flash boot sequencing on Concerto |
| SDOCM00084333 | New "LibType_DebugCustom" build profile should be similar LibType_Custom but with -g |
| SDOCM00084552 | Unbounded bit shifting in GateMP |
| SDOCM00085206 | Ipc_detach corrupts memory |
| SDOCM00085483 | update IPC examples to better support clean when using the custom build. |
| SDOCM00085513 | IPC documentation main page is empty |
| SDOCM00085515 | GateMP_Params description is garbled |
| SDOCM00085568 | NameServer_getLocalUInt32() documentation is garbled |
| SDOCM00085951 | GateMP_openByAddr is not thread-safe |
| SDOCM00085965 | GateMP risky use of Cache_wbInv |
| SDOCM00086030 | ipc.mak should not build examples |
| SDOCM00086137 | NameServer.SetupProxy needs to be bound in a null proxy when ti.sdo.ipc in not in use |
| SDOCM00086284 | NotifyDriverCirc for Concerto devices contains a bug |
| SDOCM00086359 | add makefile.defs to IPC examples to support clean of custom build (similar to BIOS examples) |
| SDOCM00086360 | update custom build for IPC to match latest improvements from BIOS 6.33.00 |
| SDOCM00086611 | ipc.bld does not correctly assign ccOpts to the target.ccOpts |
| SDOCM00086669 | NameServer_get() bug in "else" clause when nsRemoteHandle[0] == NULL |
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:
SharedRegion_DEFAULTOWNERID has been removed from the SharedRegon common header file, ti/ipc/SharedRegion.h (SDOCM00083271). Applications referencing this value should use MultiProc_INVALIDID instead (defined in ti/ipc/MultiProc.h).
Most of the APIs in IPC 1.24 are compatible with IPC 1.22/1.23. However, code using IPC 1.22/1.23 will have to be recompiled for use with IPC 1.24.00. You must recompile -- relink will not work.
ti.sdo.ipc.* and ti.sdo.utils.* APIs in the IPC 1.2X.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.
OMAP3530 Mailbox assignments swapped
In previous IPC releases, Mailbox 0 was used for DSP-to-ARM notifications and 1 was used for ARM-to-DSP communication. This has been swapped as of IPC 1.22.02. In order for ARM-DSP notifications to work, both the ARM and the DSP must use the same mailbox assignments.
DM8168 MultiProc name changesThis release supports the following operating systems:
This release requires the following other software components and tools versions to successfully function:
No known issues
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: December 19, 2011