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.

DS90UB953-Q1: Figure out CSI-2 Errors between Sensor and Serializer

Part Number: DS90UB953-Q1


Trying to if verify SER is receiving valid sensor CSI-2 packets from the connected sensor

Registers read below values each time i access these

reg. 0x5c - value 0xff

reg. 0x5d - value 0x0e

reg. 0x5e - value 0x00

What could be the issue ? I believe all these registers should show 0x00 

  • 0x5C is CSI-2 error counter, and each bits of 0x5D and 0x5E is for a different CSI-2 error status. You could look up the register description in the 953 datasheet.

    0x5D =0x0E means that there're line length mismatch than received package header word count, checksum error, and 2 bit ECC error in package header. Check to see if the CSI package header info is set up correctly or not. 

    These registers are read to clear. You could try to read twice to check if the issue is persistent or not. 

    Best Regards,

    Charley Cai

  • Yes, the errors are persistent. What are the minimum settings needed to be checked/done in order to correct these errors ?

    Trying to figure out whether modifications need to be done on image sensor registers or the serializer registers ?

    Also, does reading the status registers during the exposure time of sensor give errors ? I am getting errors persistently regardless of when i read it.

    Is there a specific window these status registers need to be read. (Image sensor is set to trigger mode)

  • This issue need to be addressed at the imager side. The serializer doesn't reconfigure any data it received.
    Read timing of these registers should be irreverent.

    Best Regards,
    Charley Cai
  • Is there any specific section/register in the image sensor that i can look upon to set up the CSI package header info correctly

  • This would depend on the imager you are using. Try to look at the imager datasheet or check with the imager manufacturer.
    I cannot provide much more info regarding imagers.


    Best Regards,
    Charley Cai