TDA4VH-Q1: Runtime FPS switch for single cam application

Part Number: TDA4VH-Q1
Other Parts Discussed in Thread: TDA4VH

Tool/software:

Hi Experts ,

i am working with AR0233 on the TDA4VH platform SDK RTOS version  :11.00.00.06

Currently, FPS is fixed by the initial sensor configuration (FRAME_LENGTH_LINES / LINE_LENGTH_PCK). To change FPS, I need to stop the sensor, reconfigure, and restart streaming.

I’d like to understand:
1. Is it possible to change FPS at runtime by writing AR0233 registers directly (e.g.,  FRAME_LENGTH_LINES,  LINE_LENGTH_PCK) from the sensor driver while single_cam_app is running?
2. For FPS change from 30 to 60FPS, is a brief stream off/on sequence required to keep CSI-2 timings stable?
3. Any precautions with UB960/UB9702 deserializers when line/frame timings change mid-stream?

Kindly request your suggestions on this topic and whether the VISS / Capture nodes etc.. can tolerate runtime FPS changes without needing graph teardown?


Thank you..

  • Hi Ajay,

    Let me check this internally and get back to you soon.

    Regards,
    Gokul

  • Hi Ajay,

    1. Is it possible to change FPS at runtime by writing AR0233 registers directly (e.g.,  FRAME_LENGTH_LINES,  LINE_LENGTH_PCK) from the sensor driver while single_cam_app is running?

    Yes you can but you need to follow the sequence that is required for the sensor like stop stream, config then start stream. Do check with the sensor vendor on the config values and sequence.

    2. For FPS change from 30 to 60FPS, is a brief stream off/on sequence required to keep CSI-2 timings stable?

    this is not required for cxirx, but for the deserializer you need to follow stream_off/on sequence.

    3. Any precautions with UB960/UB9702 deserializers when line/frame timings change mid-stream?

    No need to change any configuration for deserializer, just stream_off and do the serializer/sensor config for different fps and stream_on. We have tested this for imx390 sensor with ub9702. I am not sure of the ub960 deserializer.

    Kindly request your suggestions on this topic and whether the VISS / Capture nodes etc.. can tolerate runtime FPS changes without needing graph teardown?

    Graph teardown i not required for change in fps, but you might have to register the error frame for capture node so that when you stream_off the capture node will pass the error frame to the pipeline and resume when stream_on.

    Regards,
    Gokul