Texas Instruments Technology for Innovators(tm)

Codec Engine Release Notes

June 2010

This Codec Engine Release is targetted to DaVinci and OMAP platforms, enabling users to instantiate and utilize both local and remote codecs. In addition to heterogenous devices (e.g. DM644x, DM6467, OMAP2530, OMAP3530, etc.), it supports single processor environments as well; specifically C64+ devices (e.g. DM643x, and DM648), ARM devices (e.g. DM355, DM365, OMAP3503) and x86 devices running Linux.

Introduction, Documentation, What's New, Upgrade Info, Compatibility Information, Device Support, Validation Info, Known Issues, Examples, Version Information, Technical Support.


The Codec Engine is a software platform for algorithm execution that satisfies the following, high-level goals:

Primary packages in this Codec Engine release are briefly described here. (There are others, see the Configuration Reference Guide documentation for a complete package list.)

Additionally, this release of the Codec Engine continues to support the deprecated XDM interfaces included in XDAIS 5.00. This support is provided in the following packages:

Codec Engine is provided as non-rebuildable libraries. Source is provided for debugging and educational value, but is not intended to be modified. Modified sources will not be supported.

Some distributions of this product include a "cetools" directory containing some dependent products for convenience. Products included in this release are:

See this Codec Engine cetools explanation for further details.


The following documentation is available:

In addition, users are encouraged to monitor (and contribute to!) the TI Embedded Processors Wiki.

Release notes from previous releases are also available in the relnotes_archive directory.

What's New

The following significant changes have been made since 1.00












Upgrade Information

The Codec Engine packages are available in the "packages/" subdirectory of the product. If you have a previous release of the Codec Engine product, you can install this release next to it, and modify your application and/or server builds to use this newer release.

If you're using the DVEVM, this can be done by setting the CE_INSTALL_DIR variable in the Rules.make file at the top of the DVEVM distribution directory.

Compatibility Breaks!

In order to address SDOCM00062629 (ICodec.serverFxns and .stubFxns shouldn't be 'readonly' so app and server cfg scripts can assign them), the ti.sdo.ce.ICodec interface changed 2 fields (.serverFxns and .stubFxns), removing the 'readonly' attribute so they can be overridden at config time by a .cfg script. The result is that any Modules that implement ICodec (e.g. if you've implemented your own ICodec-derived interface with your own stubs/skels), you need to remove the 'readonly' attribute from your <Module>.xdc file and rebuild your Module. Most users, including those that are simply using the standard VISA interfaces, will not have to do this.

Note, if you're upgrading from a release earlier than Codec Engine 2.24, be sure to review the Upgrade section for each of the releases between your current Codec Engine release and this one. Previous release notes are available in the relnotes_archive directory.

Compatibility Information

The details provided below describe each package's compatibility with the previous release (2.24).

Some packages have broken compatibility with previous releases. The details provided below describe each package's compatibility with the previous release (2.23).

Note, the Configuration Reference Guide contains further details about each package.

The following packages are being introduced in this release, and therefore have no compatibility with previous releases.

The following packages are beta quality, and therefore compatibility keys are not maintained.

If migrating from a release prior to CE 2.24, consult previous releases available in the relnotes_archive directory.

Compatibility Key Definitions

Compatibility keys are intentionally independent of Marketing product numbers and are intended to:

  1. Enable tooling to identify incompatibilities between components, and
  2. Convey a level of compatibility between different releases to set end user expectations.

Compatibility keys are composed of 3 comma-delimited numbers - M,S,R - where:

Device Support

This release supports the following devices:


This release was built and validated against using the following software components:

This release was validated using the following hardware platforms:

Known Issues

See the Codec Engine Known Issues wiki article for issues found after these release notes were compiled.


Codec Engine examples and instructions are located in the "examples" directory.

Version Information

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. codec_engine_2_25_05_16.

Subsequent releases of patch upgrades will be identified by the patch number, ex. CE 2.25.01 with directory codec_engine_2_25_01. Typically, these patches only include critical bug fixes.

Technical Support

For technical support, contact softwaresupport@ti.com

Check the following web site for updates: https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/ce/index.html

Last updated: June 19, 2010