Texas Instruments Technology for Innovators(tm)

IPC 1.20.00.21 Engineering 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 a engineering release of IPC 1.20

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

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

1.20.00.21 Engineering Release (this release)

This is an Early Adopter Release of IPC 1.20. This release should be used for evaluation and early development only. It will not be supported once the official IPC 1.20 GA release is available (April timeframe). Only minor, if any, API changes will occur between this release and the GA release.

The IPC User's Guide examples and code samples are slightly out of synch with the APIs in this version of the software. The documentation available via the 'cdoc' documentation and CCSv4 Help are accurate and should be used as reference. User code should use the APIs defined by the headers in /docs/doxygen/html/index.html

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: This release is not compatible with IPC 1.00.0X.XX (GA) release. The APIs have been updated to be consistent with the Linux APIs to share common header files in ti/ipc/. Source files that use IPC 1.00 will have to be reviewed and updated.


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:


Device Support


Validation Information

This release was validated using the following components:

Known Issues

There are the following known issues with this release (which is at EA status)

ID Headline


Examples

The IPC product ships with several examples. The following is an explaination of each one. Refer to the User InstallGuide 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 shows how to use the Notify module. The driver is the NotifyDriverLoopback, so it can be run on a single processor.

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 releaseshave 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.20.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_20_00_01.

Subsequent releases of patch upgrades will be identified by the patch number, ex. IPC 1.20.00.01 with directoryipc_1_20_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, contact softwaresupport@ti.com


Last updated: April 01, 2010