Texas Instruments Technology for Innovators(tm)

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

Introduction

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

Documentation

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

SDOCM00078115Ipc_readConfig does not free shared memory for the entry after returning it to the user
SDOCM00078946write test cases to look for IPC memory leaks
SDOCM00085207Ipc_stop not supported on all-bios system
SDOCM00095908IPC does not allow single core Stellaris parts to be specified
SDOCM00095961IPC: pre-built instrumented and nonInstrumented library build flows have a flaw in their makefile dependencies
SDOCM00096267Memory leak in Ipc_attach() and Ipc_detach() loop
SDOCM00096667Bug in GateHWSem_getReservedMask()
SDOCM00096671Look at removing restriction of limiting cache invalidates to one core at a time
SDOCM00097085Source files *.c and *.cfg missing from ti/sdo/ipc/examples/multicore

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:


Dependencies

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



Examples

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.
ipc\examples\singlecore
- 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.

ipc\examples\multicore
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. 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.


Technical Support

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


Last updated: November 07, 2012