The short answer is to change the GT_set() call in
servers/video_copy/main.c from this:
GT_set("servers.video_copy=01234567");
... to this:
GT_set("*=01234567");
This says:  Don't just set the "servers.video_copy" trace mask to "all 8
levels on", but rather, set "ALL" trace masks (including the trace mask
in your codec) to "all 8 levels on".
 
In your particular example, you'll need your codec's trace mask (I think
it's probably "codecs.videnc_copy" - look for the string passed to
GT_create()) set with trace level 4 on (because this trace statement is
associated with GT_4CLASS).  Knowing that detail, you could
alternatively enable _just_ the trace statement you mentioned below
with:
GT_set("codecs.videnc_copy=4");
Also, you might re-read section 4.7 of the CE Application Developer's
Guide for some further details:
http://www-s.ti.com/sc/techlit/sprue67
 
You can change the trace masks in several different ways (e.g.
environment vars, API calls, config settings, etc.) to lots of different
settings (e.g. different trace levels - 0 though 7 - for different masks
in the system).  I'm trying not to confuse you with more details... but
believe me, there are more details.  :)
 
Chris


________________________________

        From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Jeremy Larsen
        Sent: Friday, September 14, 2007 10:59 AM
        To: [email protected]
        Subject: Need help seeing DSP traces
        
        
        When I run the DSP examples (and my own DSP code) I cannot see
any of the trace statements that should be printed out from the DSP side
code.
         
        For example:
        Using Codec Engine version 1_20 and running the video_copy
example I see
         
        [DSP] @0x0000016b:[T:0x00000000] servers.video_copy - main>
Welcome to DSP server's main()
         
        but I dont get anything else.  I should get a trace from:
         
        GT_3trace(curTrace, GT_4CLASS, "VIDENCCOPY_TI_alloc(0x%x, 0x%x,
0x%x)\n",
                algParams, pf, memTab);
         
        found in the VIDENCCOPY_TI_alloc function.
         
         
        Is there something else I must configure to see these traces?
         
        
        
________________________________

        Can you find the hidden words?  Take a break and play Seekadoo!
Play now! <http://club.live.com/seekadoo.aspx?icid=seek_wlmailtextlink>


_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to