• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 259 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.

TDA3XEVM: ISS Check for frame drops/bad data

David Dominguez Moises
Intellectual 570 points
Part Number: TDA3XEVM

Hi,

I'm using TDA3x with ISS and D90UB960 to interface with one of our cameras. We want to use the board to run some EMC tests  on our camera module and would like to detect if there were any frame drops.

Is there something that can be done from TDA3 side to detect frame drops or issues with the camera?

We are planning to read registers from 960, but this questions is to specifically check if TDA3 has any other way to detect bad transmissions/frame drops.

Thanks,

David

  • 0
    TI__Guru**** 476235 points

    David,

    One of the way to check the frame drop is by comparing timestamp of the captured frame. If timestamp difference is more than one frame time period, we can assume that there is a frame drop.

    But there is no inbuild logic correctly in driver/link to detect frame drop, as the driver/link are generic, supporting all fps, so not possible to detect drop for particular fps.

    Regards,

    Brijesh 

  • 0 in reply to Brijesh Jadav
    Intellectual 570 points

    Thanks Brijesh, this sounds doable. Is there any example in the SDK on how to add a callback function that is executed on any frame reception?

    Going through ISS link code I see on new data it actually checks if there is a callback function and executes it if available. I think I could create a custom function for my sensor there and put some checks in it.

  • 0 in reply to David Dominguez Moises
    TI__Guru**** 476235 points

    Hi David,

    If you are using ISS Capture link, you could capture timestamp in issCaptDrvCallback API in the file vision_sdk\links_fw\src\rtos\links_ipu\iss_capture\issCaptureLink_drv.c. 

    I think even driver provides timestamp in fvid2 frame. After calling fvid2_dequeue in the processData API, you could get the exact timestamp in fvid2frame->timeStamp/timeStamp64 variable.  You could use them to determine if there is any frame drop, depending on expected frame rate. 

    Regards,

    Brijesh