Overview

■A message queue is created to allow the remote node to receive commands from the GPP.

■The node-specific "create" function (for example, AUDENC_create() ) is called to initialize the node state and algorithm-specific memory and resources. (Note that this call is made from within the dispatcher execution context.)

■A dedicated execution thread (task) is created for the node. The new thread does not run yet, but is in a suspended state.

■In the dispatcher thread, instance data for the new node is saved, and then the dispatcher sends a status response back to the GPP.

■On success, the GPP-side instance object is updated with appropriate handles and data for the new "remote" node.

■A "start" message is then formed and sent to the dispatcher on the DSP to start execution of the remote node.

■Upon receiving the "start" command, the DSP-side dispatcher changes the priority of the node's thread from suspended to its configured execution priority. This change in priority causes the node’s "execute" function to run in the newly created node's execution context. This function blocks, awaiting commands from the GPP.

2)The application calls the VISA process API (for example, AUDENC_process() ), which results in a remote procedure call to the DSP:

■The GPP-side algorithm stub is invoked and performs some basic argument validation.

■A message structure is allocated and filled in with marshalled arguments, including translated (DSP) physical addresses for buffers.

■The "process" message is sent to the remote node's message queue on the DSP to invoke the remote algorithm.

■On the DSP-side, the node's thread wakes upon receipt of the "process" message, and calls the algorithm skeleton.

■The skeleton unmarshalls the arguments and input and output buffers and then invalidates the buffers from the DSP cache.

■Any algorithm scratch memory is then "activated".

■The algorithm's actual "process" function is invoked to do the encoding.

2-4

Page 19 Page 21
Page 20
Image 20
Texas Instruments Codec Engine Server manual Overview
Page 19 Page 21

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