• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 707 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DSP Trace Ticks profiling

John Tan
Intellectual 430 points

Hi 

I used GT_Trace to collect the time difference between trigger time and completion time.

Eg:

1st Attempt

[DSP] @5,320,291tk [+3 T:0x00000000] codec.edma - GPIO Trigger

[DSP] @5,627,793tk [+3 T:0x00000000] codec.edma - Complete Processing

2nd Attempt

[DSP] @6,492,935tk [+3 T:0x00000000] codec.edma - GPIO Trigger

[DSP] @6,884,080tk [+3 T:0x00000000] codec.edma - Complete Processing

With reference to this site, http://processors.wiki.ti.com/index.php/Codec_Engine_Profiling , the trace output is different from mine.

It has microseconds instead of tk.

My DSP clock is at 300000 returned by GBL_getFrequency().

I would like to know how to calculate the time difference.

Thanks.

  • 0
    TI__Mastermind 35645 points

    Hi,

    Thanks for your post.

    Try running your application as below:

    > CE_DEBUG=2 ./encode

    instead of

    > ./encode

    Here's an article below with further details to debug & trace codec engine issues:

    http://processors.wiki.ti.com/index.php/CE_DEBUG

    If you are including gt.h in your codec, and building this codec with the defines:-

    GT_ASSERT=1

    GT_TRACE=1

    Then you should see trace from your codec, if  your "main" function has GT_set("*" "=01234567")

    Also, there is an engineering notation followed in GT_calls on the DSP side, I guess. For more details, kindly refer the below E2E post:

    https://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/29738

    Thanks & regards,

    Sivaraj K

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.

    -------------------------------------------------------------------------------------------------------

  • 0 in reply to Sivaraj Kuppuraj
    Intellectual 430 points
    Hi,

    Thanks for your response.
    I have tried to use CE_DEBUG=2 on my own application and I can see the result like the Status Log in the CE_DEBUG website you provided.

    The issue is the GT_0trace(...) that I have printed out appears as [DSP] xxx ticks and I have no idea how to calculate the time difference between each ticks.

    For example from the Status Log from CE_DEBUG website,
    [DSP] @0,623,750tk: [+0 T:0x8fa470ac] CV - VISA_create(0x0, 'videnc_copy', 0x0, 0x828, 'ti.sdo.ce.video.IVIDENC')
    [DSP] @0,623,818tk: [+0 T:0x8fa470ac] CV - VISA_create2(0x0, 'videnc_copy', 0x0, 0x0, 0x828, 'ti.sdo.ce.video.IVIDENC')

    How do I calculate the difference between the VISA_create & VISA_create2 based on the difference between the ticks. @0,623,750tk, and @0,623,818tk.

    Thanks.