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 (SPRUGO6E)
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
Static Analysis Reports

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

SDOCM00077977Documentation on NameServer create is incorrect
SDOCM00087514MessageQ_getReplyQueue docs are unclear
SDOCM00087991Default synchronizer for MessageQ is incorrectly documented in IPC user guide
SDOCM00088041IPC user guide documentation needs correction for MultiProc
SDOCM00089938IPC 1.24 User's Guide "rebuild" chapter needs to be updated for the new 'ipc.mak' and 'ipc.bld' scheme
SDOCM00091084HeapBufMP, HeapMemMP and HeapMultiBufMP _getExtendedStats/_getStats function issues
SDOCM00091092Documentation issues in ListMP,Notify and SharedRegion
SDOCM00091816NameServer_delete() docs should indicate behavior when instance isn't empty
SDOCM00092962deprecate ti.sdo.io and remove it from the docs and UI elements
SDOCM00093123Need to build IPC for M4 target
SDOCM00093750IPC interrupt module for TCI663x devices not working
SDOCM00094029HeapMemMP_alloc() and other Heap*MP_alloc() API doxygen docs should say "NULL" is returned on failure.
SDOCM00094499IPC: add A8Fnv target support
SDOCM00094508IPC should allow shared regions to be defined in .cmd file if size is 0 in .cfg file
SDOCM00094803update concerto IPC examples to use linker.cmd files on package path (instead of providing duplicates in product)
SDOCM00094872Remove I/O from IPC documentation and rename the document
SDOCM00095512IPC interrupt causing double interrupt on OMAPL138 ARM
SDOCM00095863Need ARP32 Far target build in IPC

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:

No APIs or shared memory interfaces were changed in this release. However, this release requires new SYS/BIOS, XDC, and CCS components as described in the dependency section below.

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.
- 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: September 17, 2012