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.

TDA4VM: How to monitor CSIRX status?

Part Number: TDA4VM

Hi TI experts,

Is there have any registers can monitor CSIRX status?

Our customers has noticed that there may be situations where the display cannot be performed properly. In this case, the mipi output of the deserialization string measured by an oscilloscope is normal, but the capture node frame rate printing is abnormal.

Thanks & Regards.

  • Hi xie jc,

    What is abnormal frame rate? can you please share these statistics? 

    Are you getting any CRC/ECC/Overflow errors? or any frame drop errors from the drivers?

    Regards,

    Brijesh

  • Hi  Brijesh,

    What is abnormal frame rate? can you please share these statistics? 
    We monitored the frame rate printing during capture node dequeue. Under normal circumstances, it can reach 30fps, but under abnormal circumstances, the frame rate cannot reach 30fps.

    Are you getting any CRC/ECC/Overflow errors? or any frame drop errors from the drivers?

    Can you tell me which CSIRX error registers are? Is there a register that can restart the CSIRx driver?

    Thanks & Regards.

  • Hi xie jc,

    When you print the statistics from the driver, it also includes CRC/ECC and overflow errors. So please check if any of these errors are coming. In this case, fps can potentially drop..

    Can you also elaborate more on what is abnormal condition? When do you see this condition? under any specific situation? 

    Regards,

    Brijesh

  • Hi Brijesh,

    When you print the statistics from the driver, it also includes CRC/ECC and overflow errors

    Does this CRC/ECC error refer to SOC or deserialization?How do I get CRC/ECC errors for SOC?

    Can you also elaborate more on what is abnormal condition? When do you see this condition? under any specific situation? 

    We are conducting pulse automation testing on the board. Power on the board and check if it displays normally on ICC,

    When he displayed an abnormality, we found that the frame rate printing of the capture node could not reach 30fps, and at this time, the mipi input had 30fps.

    This phenomenon occurs occasionally, possibly dozens or hundreds of times once.

    Q:

    1)Can this phenomenon be caused by a certain temporal sequence? What power-on timing does Csirx need to meet?

    Thanks &Regards.

  • Hi xie jc,

    Does this CRC/ECC error refer to SOC or deserialization?How do I get CRC/ECC errors for SOC?

    ECC and CRC are included as part of MIPI stream. So the check is done against received streams data.. Is this what you are looking for? 

    1)Can this phenomenon be caused by a certain temporal sequence? What power-on timing does Csirx need to meet?

    Well, difficult to say without data. When this issue occurs, do you see any temperature issue? or any CRC/ECC issue? What SDK version are you using? I remember there was an startup sequence change in CSIRX in one of the release. Are you checking with the latest release? 

    Regards,

    Brijesh

  • Hi Brijesh,

    SDK Version : 8.4

    Under abnormal circumstances, the temperature is normal, and other functions are also operating normally. The display screen only displays the car model but does not have camera data.

    Under abnormal circumstances, there was no error log reported, only 8 frames came from the frame rate filled by the VX_EVENT_NODE_ERROR event. I don't know what data to provide to you.

    We can now measure that the mipi signal extracted from the deserialization is normal, but we cannot know why the frame rate calculated by the capture node is abnormal.

    May I ask how I can further investigate the problem?

    Thanks & Regards.

  • Hi xie jc,

    In both the cases, can you please print and share detailed performance statistics to know the error? We need to understand first if capture is working or not, and if it is not working, then are there any errors reported by the capture node?

    Regards,

    Brijesh

  • Also please note that SDK8.4 uses old DPHY bringup sequence, it has been updated in the SDK8.5, can you either use the latest release or take CSIRX driver from the latest release and use it on SDK8.4?

    Regards,

    Brijesh

  • Hi Brijesh,

    Thanks. I wiil try it and take CSIRX driver from the latest release and use it on SDK8.4.Will this change affect the use of other nodes in OPVX?

    Can you let me know what the different in bringup sequence between SDK8.4 and SDK8.5?

    Regards.

  • Hi xie jc,

    CSIRX DPHY bringup/startup sequence is changed and is as recommended by the IP/HW team, so please use the driver from the latest release.

    If you are porting the driver, then i would also recommend porting OVX capture node. But lets first see if capture works fine by just porting the capture driver.

    Regards,

    Brijesh

  • Hi Brijesh,

    About csirx driver porting, I just replaced the csirx(psdkra\pdk_j721s2_08_06_01_03\packages\ti\drv\csirx) folder of SDK8.4 with SDK8.6, and then compiled and burned the entire file system, but it didn't look normal and didn't show up.

    At this time, the Mipi output of the oscilloscope measurement deserializer is 30fps.

    May I ask if I am missing some operations?

            

    Thanks & Regards.

  • Hi xie jc,

    ok, driver alone porting seems not working. can you please revert to SDK8.4 release driver and apply attached patch on top of it and try it out? 

    /cfs-file/__key/communityserver-discussions-components-files/791/CSIRX_5F00_Updated_5F00_Bringup_5F00_Sequence.zip

    Regards,

    Brijesh

  • Hi Brijesh,

    The patch is work, thank you for your help.

    I will do a test for a period of time and give you feedback.

    Thanks & Regards.

  • Thanks Xie jc, i will move this ticket to waiting state.