Texas Instruments Codec Engine Server manual Editing the DSP/BIOS Configuration Script

Page 30

Creating a Codec Server

Engine.algs[].groupId

For each local algorithm, if the optional groupId field is uninitialized, the algorithm is configured into its own, unique groupId. This is because we don't know what priority the algorithm will run at, so we place it into a unique group to prevent preemption by any other algorithm.

Note that for remote algorithms, the groupId field is ignored. In such cases, the algorithm is placed into the Server-configured groupId.

2.2.4Editing the DSP/BIOS Configuration Script

The Codec Server runs as a DSP/BIOS application on the DSP. As such, it has a static DSP/BIOS configuration. This is created with a .tcf file as described in the DSP/BIOS Tconf User’s Guide (SPRU007) and in the DSP/BIOS online help. The syntax used in Tconf configurations is based on JavaScript.

To create your own .tcf file for your server, follow these steps:

1)Copy all.tcf from CE_INSTALL_DIR/examples/servers/all_codecs to your server directory. Rename it to match the name of your server. For example, your file might be called "my_server.tcf".

2)Edit the servername.tcf file with a text editor.

3)Make any changes your Codec Server requires and save the file.

For the Codec Server, the task threads used to process algorithms are created dynamically at runtime. This configuration file statically configures several aspects of the DSP/BIOS kernel, including:

❏The base DSP/BIOS kernel

❏Memory section names, sizes, and locations

❏Platform-specific attributes such as clock rates

❏Enables the task manager and dynamic heap allocation

❏Configures the C64+ L1 cache and corresponding memory segment

You can learn more about all of these modules and attributes in the DSP/BIOS online help or the C6000 DSP/BIOS API Reference (SPRU403).

You can add your own non-Codec Engine configuration items here if you need to add your own functionality to the Server. The settings have been tested for use with Codec Engine as is. You should be careful about changing the settings.

2-14

Page 29 Page 31
Image 30
Page 29 Page 31
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 AuthorCodec Engine API Reference Where Can I Get More Information?Configuration 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 main.c File Editing the Linker Command FileDelivering a Codec Server 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