Texas Instruments Codec Engine Server manual Editing the Package Definition

Page 24

Creating a Codec Server

3)Edit the examples/xdcpaths.mak file with a text editor to specify the CE_INSTALL_DIR, XDC_ROOT, and BIOS_ROOT variables. Again, see examples/build_instructions.html for details.

4)Make a duplicate of one of the Codec Server examples in the examples/servers directory. Each of these directories is a "package". Packages must have names that match their directory location. So, you should give your duplicate directory a path that follows the examples/my_company/my_project/my_server naming convention. You will name the package to match this location in the following section.

2.2.2Editing the Package Definition

The package.xdc file is the package definition file, which defines your

Codec Server’s name and its dependencies.

Follow these steps to name your server package.

1)Edit the package.xdc file with a text editor. Rename the server package. For example, to call your server "my_server", change the bolded portion as follows:

package my_companyname.my_project.my_server

The package name must reflect the directory structure under the examples directory. For example, a package in the example/my_company/my_project/my_server directory must have a name of my_company.my_project.my_server. You should use this companyname convention to ensure that your server has a unique package name.

2.2.3Editing the Codec Server Configuration Script

Afile named servername.cfg configures the non-DSP/BIOS aspects of the Codec Server. To create this file for your own server, it is best to modify an existing example file.

The syntax used in this Server configurations is based on JavaScript, which is also used for the Tconf language used to statically configure DSP/BIOS. (See SPRU007 for details.)

Unlike the JavaScript used in web pages, an object model is provided to meet the needs of Engine configuration. This object model is documented in the Configuration Reference, which is available at CE_INSTALL_DIR/xdoc/index.html.

2-8

Page 23 Page 25
Image 24
Page 23 Page 25
Contents Codec Engine Server Integrator Users Guide Important Notice Preface Notational Conventions Contents Page Codec Engine Overview This chapter introduces the Codec Engine TopicWhat is the Codec Engine? Why Should I Use It? Where Does the Codec Engine Fit into My Architecture? Role 3 Core Engine APIsVisa APIs Core Engine APIs Visa APIs Runtime Video EncodeWhat Are the User Roles? Algorithm CreatorServer Integrator Engine Integrator Application AuthorWhere Can I Get More Information? Configuration ReferenceCodec Engine API Reference Example Build and Run InstructionsPage Configuring a Codec Server Overview What is a Codec Server? What is the Execution Flow?Overview What About Single-Processor Systems? What is the Config Kit? What Algorithms Can a Codec Server Integrate?What Examples Exist? Creating a Codec Server Creating a PackageEditing the Codec Server Configuration Script Editing the Package DefinitionVar LogServer = xdc.useModuleti.sdo.ce.bioslog.LogServer Creating a Codec Server Controlling I/O Buffer Caching for xDM 0.9 Codecs Specifying Scratch Group and DMA Resources for a Codec More About the groupId Field Server.algs.groupIdEditing the DSP/BIOS Configuration Script Engine.algs.groupId4.1 DSP/BIOS Threads and Module Use Editing the Build ScriptEditing the Linker Command File Delivering a Codec ServerEditing the main.c File Editing the makefileDelivering Server Packages for Servers Built with XDC Delivering a Codec Server Index Index

Codec Engine Server specifications

Texas Instruments Codec Engine Server (CES) is a powerful software framework designed to handle audio and video processing on embedded systems. It serves as a bridge between high-level application programming and low-level codec implementations, simplifying the development of multimedia applications. The Codec Engine's primary focus is on optimizing media codecs for applications such as telecommunications, video conferencing, multimedia playback, and streaming services.

One of the standout features of the CES is its ability to support multiple codecs simultaneously, allowing developers to efficiently decode and encode various media formats in real time. This flexibility is crucial for applications that demand high-quality audio and video processing without compromising performance. Furthermore, the CES architecture promotes modular design, enabling developers to swap in and out different codec implementations based on specific project requirements.

The CES leverages advanced technologies including simultaneous multithreading, which maximizes the processing power of multi-core processors. With this capability, developers can allocate threads efficiently across multiple cores, tackling demanding tasks without latency. Additionally, the framework supports dynamic codec allocation, meaning that resources can be managed and adjusted on-the-fly as needed, ensuring optimal performance in varying conditions.

Another significant characteristic of the CES is its compatibility with various Texas Instruments DSP (Digital Signal Processor) platforms. This ensures that developers can take advantage of the specialized capabilities of TI's hardware, including their power management features and high-performance processing capabilities. The integration of hardware and software within the CES architecture allows for optimized resource utilization, leading to energy-efficient applications.

The development process is further streamlined through the use of a comprehensive API (Application Programming Interface) that provides access to codec functionalities while abstracting the complexities of underlying hardware. This allows developers to focus on building high-level features without getting bogged down in low-level programming details.

In conclusion, Texas Instruments Codec Engine Server stands out as a robust solution for developers aiming to create high-performance media applications. Its support for multiple codecs, efficient resource management, and compatibility with TI DSP platforms make it an indispensable tool in the multimedia processing space. By facilitating seamless interaction between hardware and software, CES empowers developers to deliver richer multimedia experiences in their applications.
Top Page Image Contents