• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 1603 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.

CLK_gethtime

Genady Kagan
Intellectual 320 points

Other Parts Discussed in Thread: TMS320DM642

Hi

I am using the TMS320dm642 DSP , I use the CLK_gethtime function for time measurement . Can I  disable interrupts , when I use this functions?  Does the disable /enable interrupts have any influence on  the CLK_gethtime results.

 

Thanks

  • 0
    TI__Mastermind 32475 points

    Yes, you can disable when calling CLK_gethtime.  NO, it will not have any effect on the results.  The CLK_gethtime for your device is really fast and it simply returns the TSCL count.

    Judah

  • 0 in reply to judahvang
    Intellectual 320 points

    Hi

    Thanks for response

    I see ther folowing explanation in TI help file (from Code Composer 3.3):

    You can use the CLK_gethtime function to get the high-resolution time and the CLK_countspms function to get the number of hardware timer counter register ticks per millisecond.

    The high-resolution time is stored as a 32-bit value. For platforms that use the same timer counter as the low-resolution time, the 32-bit high-resolution time is actually calculated by multiplying the low-resolution time by the value of the PRD property and adding number of timer counter increments since the last timer counter reset.

     

    As  I understand , the DSP BIOS on TMS320DM642 uses the same timer for low and high resolution time measurment,  if  i understand the help file right , the value of high CLK_gethtime depends on low  resolution time , and low  resolution time  is affected by disable /enable interrupts .

    Did i miss something?

    Thanks

     

     

     

     

     

     

  • 0 in reply to Genady Kagan
    TI__Mastermind 32475 points

    Opps...sorry, you are correct about the high timer resoution clock use the same lower resolution clock on DM642.  I thought because DM642 was a DaVinci device it was based upon C64x+ device but its only a C64x device so it does not have a separate timestamp counter as I previously stated.  So, yes it can be affected by a disable/enable of interrupts.

    Judah