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.

DS90UB960-Q1: MIPI CSI-2 errors between DS90UB960-Q1 and Nivida Jetson TX2

Part Number: DS90UB960-Q1

Hardware configuration is as follows:

sensor–> TI DS90UB953 (serializer)--------TI DS90UB960 (deserializer)–> TX2 MIPI CSI2(4 lane)

The problem is:

TX2 failed to receive image data from MIPI CSI2 if the UB960(deserializer) 's MIPI lane bitrate is set to 1.6Gbps(1x4lane),

while everything works fine with 800Mbps MIPI lane (1x4lane).

And we also test the MIPI CSI-2 communication using 960's pattern generator,

instead of inputs from image sensors.

The same problem occurs.

So seems there is some problem with the MIPI-CS-2 interface between 960 and Jetson Tx2.

We also checked the PCB trace delay carefully, according to the 960's data sheet, "10.1.3 CSI-2 Guidelines".

And we confirm that the MIPI CSI-2 trace and layout satisfy the requirements:

  1. The max trace length is less than 2800mil, which is approximately less than 540ps.
  2. the Intra-pair length mismatch is less than 5mil, so the intra-pair skew is less than 1ps;
  3. the inter-pair length mismatch is less than 10mil, so the inter-pair skew is less than 5ps.

While we try to capture image on Nvidia Jetson TX2,  the kernel outputs some MIPI CSI-2 related errors,

showing that there are some CRC / ECC errors in the MIPI packet.

What's the difference between 800Mbps and 1.6Gbps MIPI data rate?

Should 960's MIPI CSI-2 timing parameters be adjusted for 1.6Gbps data rate?

  • Fred,

    thanks for detailed debug on this case. You are great to have this step-by-step record.

    You are right that the issue could be from the section between 960 CSI2 i/f and Jetson TX2.

    since it has CRC/ECC error in the TX2 side, it could be the CSI2 link jitter margin issue:

    1. make sure TX2 can support up to 1.6Gbps CSI2 data rate

    2. if possible you can test the 1.6Gbps DPHY signal with MIPI analyzer and check what spec. is NOT met

    3. pls check if your board has cross-talk which makes the CSI2 link marginal 

    For 960, the 1.6Gbps dphy meets mipi csi2 compliance test. You can focus on your CSI2 i/f jitter margin design.

    regards,

    Steven

  • Hi Steven, 

    We did some further tests today.

    With the same 960 and TX2 MIPI configuration (register settings),

    953 / 960 PG  works fine with 2-lane@1.2Gbps, and 2-lane@1.6Gbps,

    but failed with  4-lane@1.2Gbps, and 4-lane@1.6Gbps.

    Seems that MIPI data channel D0, D1 work fine, 

    but something wrong with MIPI channel D2, D3.

    Any idea?

    Is it possible to switch to route data on MIPI channel D2 and D3, instead of D0 and D1, with 2-lane@1.6Gbps?

    Regards,

    Fred

  • It is ok. It further indicates that this is CSI2 link jitter margin issue. please check it as suggested above focusing on link jitter margin analysis.

    regards,

    Steven

  • Steven,

    Do you mean CSI2 CLOCK jitter?

    Could you please explain more on how to do the jitter margin analysis?

    Or recommend some tools to me ?

    Thanks.

  • Hi,

    I more concern the data lane (lane2/lane3) jitter performance. you can use MIPI analyzer instrument from Tek or keysight to capture these two lanes electrical spec. based on MIPI conformance spec. from MIPI org.

    regards,

    Steven