Use the Codec Engine API function (7), codecengine

Use the Codec Engine API function (7), codecengine
This article is translated from TI's manual, which is a golden document for studying GPP + DSP development. I hope it will be helpful for you to get started. Please kindly advise if you have any improper understanding.
Codec Engine Application Developer User's Guide.pdf (Literature Number: SPRUE67D)
Codec Engine application development user manual http://blog.csdn.net/dyzok88/article/details/42154487
Chapter I Codec Engine overview http://blog.csdn.net/dyzok88/article/details/42214813
Chapter 2 Codec Engine installation and setting http://blog.csdn.net/dyzok88/article/details/42278109

Chapter 3 sample applications using Codec Engine http://blog.csdn.net/dyzok88/article/details/42302793

// Body

4.7 how to debug Codec Engine?

The Codec Engine module provides a large number of activable tracking information in applications and servers to reveal what happens internally.

When any object in your application fails to be created-the codecs or engines are enabled locally or locally on the DSP-to achieve basic debugging, follow the instructions in this section. Section 4.8, how to use software tracking? It provides detailed information about Codec Engine tracking. This software is generally used when debugging is real-time and performance problems.

4.7.1 debug the Codec Engine in the ARM + DSP System

Open the lowest level of Codec Engine debugging and obtain all warning and error messages on ARM and a separate DSP. You only need to set the environment variable CE_DEBUG = 1 on the target development board before running the application. CE warnings and errors for all applications and servers are printed to standard output in the correct order.

Setting the CE_DEBUG environment variable causes the Codec Engine on the ARM to not only print its own tracing information, but also automatically collect any tracing information of the DSP server about ce api completion-whether it is a failure or a success. The value of this variable only affects the details of the collected and printed information.

Set CE_DEBUG = 2 to obtain detailed tracing information. This produces a large amount of text. Therefore, we recommend that you run your application as follows:

root@146.252.161.13:~# CE_DEBUG=2 ./app.out [any app args here...] | tee log.txt 

After the application is running, check the log.txt file.

Set CE_DEBUG = 3 to enable all the trace information. You usually need to analyze and generate the trace information like this with the help of a CE expert.

4.7.2 debug the Codec Engine on a single-core DSP System

In a single-core DSP system, assume that you are debugging the application from Code Composer Studio and have enabled C Code tracking debugging.

In this way, when you prepare to display the Codec Engine trace information-call CERuntime_init () you can add the following lines to your code as soon as possible (assuming you have done # include <stdio. h> and # include <ti/sdo/ce/trace/gt. h> ):

GT_setprintf( (GT_PrintFxn)printf );GT_set( "*+67" ); /* turn on trace for warnings and errors */

The last line shows the number of trails to be opened. To open all trails, use the following line instead:

GT_set( "*+01234567,GT_prefix=1235,GT_time=0" );