Hi team，
As shown in the attachment, the 962 register detects the existence of CSI ERROR in the video data:
1. Is CSI ERROR a problem with the link between the 962 deserializer and the SOC? For example, in Appendix 2, can you please point out which process of data transmission has a greater probability of a problem?
2. What is the reason for detecting CSI ERROR in video data?
Hi Glenn，
Since this problem is a customer after-sales problem for the time being, we can only get a set of data and the problem time log to print screenshots of several register values such as 0X4D, 0X4E (in the attachment). FPD LINK is connected to four cameras, namely DMS, Among 360, ROA and driving recorders, 360 has the highest probability of having this problem and the probability is relatively frequent. The problem has occurred in many cases and affects the customer's driving experience. If multiple sets of register data are needed later, we will communicate and request them later.
ser/des: DS90UB953-Q1 / DS90UB962-Q1
Resolution: 1920*720
Data type: YUV422
CSI rate: The specific rate is not clear yet. What is known is that the maximum rate of data output by the ser end is 2GBPS.
# /bin/camera/ccidbgr /dev/cci2 0x30 write 0x4c 0x12;/update/ccidbgr /dev/cci2 0x30 dump 0x00 1 2
0x4c <- 0x12
00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f *ASCII*
00: 60 00 3f 40 d0 01 00 fe 1c 10 7a 7a 0f 09 00 ff `.?@......zz....
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 00 ................
20: 00 03 00 8f 00 00 00 00 00 00 00 00 00 00 00 00 ................
30: 00 00 01 01 00 01 00 00 00 00 00 00 00 00 00 00 ................
40: 00 a9 71 01 00 00 20 00 00 00 00 1e 12 43 0c 64 ..q... ......C.d
50: 00 00 00 02 00 00 00 00 5e 00 00 30 22 30 00 00 ........^..0"0..
60: 00 00 00 00 00 94 00 00 00 00 00 00 00 7c 88 88 .............|..
70: 6b 6c e1 02 d0 0f 00 c5 00 01 02 05 e1 10 00 00 kl..............
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
90: 54 7a 00 00 ff ff 00 00 00 00 00 00 00 00 00 00 Tz..............
a0: 00 00 00 00 00 1d 00 00 00 00 00 00 00 00 00 00 ................
b0: 1c 3a 14 08 25 00 18 00 8b 33 83 74 80 00 00 00 .:..%....3.t....
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
d0: 00 43 94 04 60 f2 00 02 00 73 00 00 00 00 00 00 .C..`....s......
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
f0: 5f 55 42 39 36 30 00 00 00 00 00 00 00 00 00 00 _UB960..........
HI Alan,
Register 0x4D and 0x4E are port specific register. In the log you sent what port are they looking at? Are all ports having the same errors?
0x4D and 0x4E are indicating there is some errors on the link but we really need a register dump on a good and bad system to compare (make sure we get all ports use register 0x4C to select port ). This will help narrow down further.
Can customer turn on the pattern generator on the 953 to see if the same errors are detected? Patgen is on page 0 and turn on by writing on indirect register 0x01 = 0x01.
Glenn
