IPC 1.21.01.16 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

This is the GA release of IPC 1.21.01

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 three main packages

ti.ipc: Contains common interface files (e.g. MessageQ, ListMP, HeapMemMP, Notify, etc.)
ti.sdo.io: Contains I/O modules (e.g. Stream, IDriver interface, etc.)
ti.sdo.utils: Contains helper modules (e.g. MultiProc, List and NameServer)
ti.sdo.ipc: Contains multicore modules (e.g. MessageQ, Notify, ListMP, etc.)

These packages are provided as source code and prebuilt libraries.

Documentation

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.

What's new

Changes since IPC 1.21:

SDOCM00071349	If cacheEnable is false and cacheLineSize = 0, IPC does not work on evmOMAPL138
SDOCM00071442	TransportShm_put incorrectly uses the cache settings to wbInv message (iff SR0 cacheFlag false and msg is in SR w/ flag true)
SDOCM00071491	Heap[MemMP, QueueMgr, BufMP, MultiBufMP]_free should invalidate entire mem being freed
SDOCM00071557	update IPC examples to use groups for the multicore examples

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:

All of the APIs in IPC 1.21.01 are compatible with IPC 1.20. However, code using IPC 1.20 will have to be recompiled for use with IPC 1.21.01. You must recompile -- relink will not work.

Shared memory protocols and interfaces are identical to IPC 1.20.00.23. Syslink Linux-side applications should work with IPC 1.20.00.23 or IPC 1.21.01.16 without any changes. Syslink target-side code that used IPC 1.20 will have to be recompiled for use with IPC 1.21.01 (as noted above).

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.

Host Support

This release supports the following hosts:

Windows XP SP2/SP3

Windows Vista

Linux (Redhat 4 and 5)

Dependencies

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

CCS 4.2.0.08024 (or later)
SYS/BIOS 6.30.00.28 (or later)
XDCTools 3.20.00.41 (or later)

Device Support

Validation Information

This release was validated using the following components:

CCS 4.2.0.08024
SYS/BIOS 6.30.00.28
XDCTools 3.20.00.41

Known Issues

There are no known issues with this release

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.
io\examples

- stream: This example shows the use of ti.sysbios.io.Stream module to demonstrate IO streaming using a driver.

utils\examples

- list:The list example shows how to use the basical functionality of the ti.sdo.utils.List module
- multiProc: The multiProc example shows how to use the basical functionality of the ti.sdo.utils.MultiProc module
- multiProcSingleImage: The multiProcSingleImage example shows how to configure an image to be able to run on multiple cores.

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 messageQ on a multiprocessor system.
- notify: This example shows how to run the Notify module only 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: Jun 24, 2010