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.

Clock_getTicks is inaccurate

Other Parts Discussed in Thread: SYSBIOS

Hi!

I've measured the Clock_getTicks() accuracy and I found that it is inaccurate. It runs 0.7899 time slower. 
The  configuration:

var Clock = xdc.useModule('ti.sysbios.knl.Clock');
Clock.tickPeriod = 1000;  // 1ms

What could be the error?

Best regards,
Lajos
 

 

  • Lajos,

    It is probably because the timer peripheral used by Clock is not being driven at the expected rate.  

    What device are you using?

    If there are multiple types of timer peripherals available for your device, which type is being used?

    Have you verified that the related clock frequencies (the CPU clock, if the timer is driven from that, or maybe a separate clock feeding the timer) are running at the expected rates?

    Are you running on a TI development board, or custom hardware?

    Also, please post the contents of the application configuration file (with the .cfg extension) so we can look at that…

    Scott

  • Dear ScottG,

    I have met the same problem. Only the vpss m3 have this problem.

    When call Clock_getTicks() like

    if(Clock_getTicks() - curtime > 10 * 1000)// print statitistic info per 10s
    {
    //Vps_captPrintStatistic();
    Vps_captPrintAdvancedStatistics(curtime);
    curtime = Clock_getTicks();
    }

    actually, the statistic info is print every 7.9s., the info is below: 

    [m3vpss ] ***39113 Capture Driver Advanced Statistics ***
    [m3vpss ]
    [m3vpss ] IP Parser Reset Count : 0
    [m3vpss ]
    [m3vpss ] | Total Even Odd Total Even Odd Min / Max Min / Max Dropped Fid Repeat Frame Error Y/C
    [m3vpss ] CH | Fields Fields Fields FPS FPS FPS Width Height Fields Count (Desc Error Y/C)
    [m3vpss ] ------------------------------------------------------------------------------------------------------------
    [m3vpss ] 200 | 436 436 0 24 24 0 1920 / 1920 1080 / 1080 1 0 0/0 (0/0)
    [m3vpss ]
    [m3vpss ] VIP Capture Port 2 | DescMissMatch1 = 0, DescMissMatch2 = 0 , DescMissMatch3 = 0
    [m3vpss ]
    [m3vpss ] *** Capture List Manager Advanced Statistics ***
    [m3vpss ]
    [m3vpss ] List Post Count : 2314
    [m3vpss ] List Stall Count : 0
    [m3vpss ] List Post Time (ms) : Max = 0, Min = 0, Avg = 0, Total = 0
    [m3vpss ] INTC Timeout Count : (0, 0) (Min timeout value = 993, 1000)
    [m3vpss ] Descriptor miss found count : 0
    [m3vpss ]
    [m3vpss ]
    [m3vpss ] VIP and VPDMA registers,
    [m3vpss ] VIP0 : FIQ_STATUS : 0x4810551c = 0x00000000
    [m3vpss ] VIP1 : FIQ_STATUS : 0x48105a1c = 0x00000000
    [m3vpss ] VPDMA: LIST_BUSY : 0x4810d00c = 0x00160000
    [m3vpss ]
    [m3vpss ]
    [m3vpss ] 39174: CAPTURE: Fields = 435 (fps = 23, CPU Load = 0)

    real capture fps is 30

    how to fix this problem? ths

  • This is a closed thread.  Please start a new forum thread for your question, and please indicate answers for the questions I’d originally asked Lajos, to provide some background information.  That will help others in responding to your question.

    Thanks,
    Scott