API functions using Codec Engine (vii)

This article is translated from TI's Handbook, the Handbook is a study of gpp+dsp development of the Golden Code document, I hope that the introduction of the help, there is an inappropriate understanding of the hope please enlighten.
Codec Engine application Developer User ' s Guide.pdf (literature number:sprue67d)
"Codec Engine Application Development Manual" http://blog.csdn.net/dyzok88/article/details/42154487
Chapter One Codec Engine Overview http://blog.csdn.net/dyzok88/article/details/42214813
Chapter II Installation and setup of Codec Engine http://blog.csdn.net/dyzok88/article/details/42278109

Chapter Three uses CODEC Engine's sample application http://blog.csdn.net/dyzok88/article/details/42302793

Body

4.7 How to debug Codec Engine?

The Codec Engine module provides a number of active tracking information in the application and server side, revealing what is happening inside.

When any object creation of your application fails-codec or engine, on-premises or in DSP-in order to do basic debugging, follow the instructions in this section to turn on CODEC Engine tracking. Section 4.8, how to use software tracking? Provides detailed information about CODEC Engine tracking, which is typically needed when debugging real-time, performance issues.

4.7.1 in the ARM-side debug ARM+DSP systemCodec Engine

Open the lowest level of Codec Engine debugging, get all warnings and error messages on ARM and individual DSPs, and simply set the environment variable ce_debug=1 of the target Development Board before running the application. All application and server CE warnings and errors will be printed to standard output in the correct order.

Setting the CE_DEBUG environment variable causes the CODEC Engine on arm to automatically collect any trace information about the completion of the CE API on the DSP server, in addition to printing its own tracking information-whether it is a failure or a success. The value of this variable affects only the verbosity of the information that is collected and printed.

Set the ce_debug=2, you can get a very detailed trace information. This produces a lot of text, so we recommend running your application as follows:

[Email protected]:~# ce_debug=2/app.out [any app args here ...] | Tee Log.txt

After the application runs, examine the Log.txt file.

Set up ce_debug=3, you can open all the tracking information, you usually need to be a CE expert with the help of analysis to generate this kind of tracking information.

4.7.2 Debug Codec Engine on a single-core DSP system

In a single-core DSP system, assume that you are debugging an application from code Composer Studio and have C code trace debugging turned on.

doing so when you are ready to display CODEC Engine tracking information-after calling Ceruntime_init () can be right as soon as possible-the following lines are added to your code (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 how many traces to open, and to open all traces, use the following line instead:

Gt_set ("*+01234567,gt_prefix=1235,gt_time=0");

API functions using Codec Engine (vii)