Texas Instruments Technology for Innovators(tm)

IPC GA Release Notes

This release note is divided into the following sections:

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


IPC 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

These packages are provided as source code and prebuilt libraries.


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.

What's new

Changes since IPC 1.24.01:

SDOCM00089325Add support for TI811X and TI813X devices
SDOCM00089327Add support for evm6657

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.

Upgrade and Compatibility Information

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 changes

Host Support

This release supports the following operating systems:


This release requires the following other software components and tools versions to successfully function:

Device Support

Validation Information

This release was validated using the following components:

Known Issues

No known issues


The IPC product ships with several examples. The following is an explaination of each one. Refer to the User Install Guide for details on building.
- stream: This example shows the use of ti.sysbios.io.Stream module to demonstrate IO streaming using a driver.

- notify_loopback: This example demonstrates the Notify module on a single core using loopback functionality.
- message: This example demonstrates the MessageQ module on a single core.

Please refer to the readme.txt in the multicore platform specific directories for details on how to run.
- message: This example shows how to use MessageQ on a multiprocessor system.
- notify: This example shows how to use IPC notifications on a multiprocessor system.

Version Information

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.

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 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.

Technical Support

For technical support, use the community forum TI E2E Community, or email softwaresupport@ti.com.

Last updated: February 10, 2012