Texas Instruments Technology for Innovators(tm)

IPC 1.21.02.23 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 GA release of IPC 1.21.02

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 (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.01:

SDOCM00073312evm6474 example Platform.xdc has incorrect memory size for DDR2
SDOCM00073098Ipc_readConfig logic defects.
SDOCM00069771DM8168/DSS should be renamed to DM8168/VPSS
SDOCM00071733ListMP: obj->attrs must be flushed from cache to help ROV (not a runtime problem, but a big ROV issue)
SDOCM00068467Need Ipc_detach() to handshake with remote core
SDOCM00072080add support for catalog/Netra part -- C6A8168
SDOCM00072213MultiProc_getId should assert that name != NULL
SDOCM00072433Notify_sendEvent: uninitialized 'status' variable is returned upon successfully executing loopback event
SDOCM00072646MultiProc.setConfig should check for duplicate names in nameList
SDOCM00072649change notify ids used internally by IPC to be 0, 1, .., n. Use Notify system key when registering internally within IPC.
SDOCM00072082GateMP should use a 'GateAll' gate instead of GateHwi
SDOCM00072942GateAAMonitor_Instance_init hits assert when cacheLineSize = 0
SDOCM00071788Notify_Module_startup should assert that MultiProc_self() != MultiProc_INVALIDID
SDOCM00071741Tom/Far/Nyq/Shan should offer ability to set MultiProc ID automatically at startup time
SDOCM00071907update C6x/ELF targets to use mid-July 7.2 "alpha-build3" codegen for ELF targets (not COFF)

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.02 are compatible with IPC 1.20. However, code using IPC 1.20 will have to be recompiled for use with IPC 1.21.02. You must recompile -- relink will not work.

The following shared-memory interface changes have been made between IPC 1.21.01 and 1.21.02:

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.

DM8168 MultiProc name changes

The valid MultiProc names for DM8168 have been changed in IPC 1.21.02 to match the official names. They are now as follows:

If legacy/incorrect names are used in the MultiProc configuration, a RTSC build error will be displayed. However, runtime usage of any legacy or incorrect MultiProc names cannot be caught until runtime.

DM8168 Example platform changes

'ti.sdo.ipc.examples.platforms.simDM8168.xxx' sample platforms in IPC have been renamed to 'ti.sdo.ipc.examples.platforms.evmDM8168.xxx'. Applications should use 'evmDM8168' instead of 'simDM8168' if the applications are using the example platforms packaged with IPC. Existing platforms generated using the platform wizard are not affected by this change.


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

SDOCM00068256The linker will product a warning about "placing code in a data section" when building c6x applications using the whole_program[_debug] build profile for some devices. It is safe to ignore this warning.


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 basic 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: Aug 09, 2010