Filter
Top Products
Where Can I Get More Information?
Codec Engine Overview 1-9
❏ Various Codec packages from Algorithm Creators
❏ A Codec Server DSP executable from the Server Integrator if codec
will run on a DSP
❏ An Engine config file (.cfg) from the Engine Integrator
The Application Author write application code, generates output from the
Engine configuration file (.c and .xdl output files) using the XDC Tools,
compiles the application code and generated files. This person then links
the files, including the generated linker command file (.xdl) into an
executable. The end result is the application executable.
The process for generating an application executable is highly dependant
on the application's operating system. If the application runs on the DSP
using DSP/BIOS, for example, a .tcf file is needed to configure the
DSP/BIOS kernel as well. If the application runs on Linux, the application
does not need to configure the operating system.
The Application Author uses the following resources:
❏ Codec Engine Application Developer’s Guide (SPRUE67)
❏ Codec Engine API Reference.
CE_INSTALL_DIR/docs/html/index.html
❏ Example Build and Run Instructions.
CE_INSTALL_DIR/examples/build_instructions.html
1.5 Where Can I Get More Information?
The release_notes.html file at the top of the Codec Engine installation
provides general information, information about changes in the latest
version, devices supported and validation information, known issues, and
links to online documentation provided with the Codec Engine. The
online documentation provided with the Codec Engine is as follows:
❏ Codec Engine API Reference.
CE_INSTALL_DIR/docs/html/index.html
❏ Configuration Reference.
CE_INSTALL_DIR/packages/xdoc/index.html
❏ Example Build and Run Instructions.
CE_INSTALL_DIR/examples/build_instructions.html
For information about xDM, see the xDAIS-DM (Digital Media) User
Guide (SPRUEC8).