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: [DS90UB960-Q1] use the 3 camera module in DS90UB960.

Part Number: DS90UB960-Q1

Dear,

I had used the 4 camera module in DS90UB960 ( like below picture )

Also, I used the Line-Concatenated format like below picture 

It work fine. ( in case 4 camera )

But, if I use the 3 camera, It doesn't work.

Please, let me know what do I do in this case ( 3 or 2 camera).

best regards,

hosung shin.

  • Hi Hosung,

    Thanks for your inquiry. Do you have any feedback on if this issue is observed in only line concatenated forwarding? Or if this issue is also observed when basic synchronized forwarding is being used? Also, do you have a register dump of the DS90UB960 which I could take a look at?

    Best,

    Thomas

  • Hi Hosung,

    One other follow up question, what do you mean here by the below statement?

    But, if I use the 3 camera, It doesn't work.

    Does this mean that the serializers in the camera module do not lock to the deserializer? CSI data output from the deserializer is not recognized by the SOC? Other potential issues?

    Best,

    Thomas

  • Hi Thomas,

    [1] It's your register dump of the DS90UB960.

        As you saw, the lock's register is 0xc3 ( reg 0x4d )  it's LOCK status.

    [normal case >> connect the 4 camera ]
    root@imx8mp-var-dart:~# i2cdump -f 2 0x3d
    No size specified (using byte-data access)
    WARNING! This program can confuse your I2C bus, cause data loss and worse!
    I will probe file /dev/i2c-2, address 0x3d, mode byte
    Continue? [Y/n] Y
    0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
    00: 7a 00 1e 40 d0 01 00 fe 1c 10 7a 7a 0f b9 00 ff z.?@??.???zz??..
    10: 91 00 00 00 00 00 00 00 01 0a d7 61 a0 00 04 02 ?.......???a?.??
    20: 00 3c 01 00 00 00 00 00 00 00 00 00 00 00 00 00 .<?.............
    30: 00 00 01 03 01 03 00 00 00 00 00 00 00 00 00 00 ..????..........
    40: 00 a9 71 01 00 00 20 00 00 00 00 12 38 c3 04 25 .?q?.. ....?8??%
    50: 20 00 00 00 00 00 00 00 58 00 00 b0 00 00 00 00 .......X..?....
    60: 00 00 00 00 00 00 00 00 00 00 00 00 00 7f aa 88 .............???
    70: 1e ec e4 02 d0 0c 80 c5 00 01 00 00 20 00 00 00 ????????.?.. ...
    80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
    90: 01 f0 01 74 ff ff 00 00 00 00 00 00 00 00 00 00 ???t............
    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 ff 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 02 60 f2 00 02 00 00 00 00 00 00 00 00 .C??`?.?........
    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..........
    root@imx8mp-var-dart:~#

    [abnormal case >> it's connect the 4 camera, but one of 4 camera was broken.]
    root@imx8mp-var-dart:~# i2cdump -f 2 0x3d
    No size specified (using byte-data access)
    WARNING! This program can confuse your I2C bus, cause data loss and worse!
    I will probe file /dev/i2c-2, address 0x3d, mode byte
    Continue? [Y/n] Y
    0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
    00: 7a 00 1e 40 d0 01 00 fe 1c 10 7a 7a 0f b9 00 ff z.?@??.???zz??..
    10: 91 00 00 00 00 00 00 00 01 0a d7 61 a0 00 04 02 ?.......???a?.??
    20: 00 3c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .<..............
    30: 00 00 01 03 01 00 00 03 00 00 00 00 00 00 00 00 ..???..?........
    40: 00 a9 71 01 00 00 20 00 00 00 00 12 38 c3 14 25 .?q?.. ....?8??%
    50: 1f 00 00 00 00 00 00 00 58 00 00 b0 00 00 00 00 ?.......X..?....
    60: 00 00 00 00 00 00 00 00 00 00 00 00 00 7f aa 88 .............???
    70: 1e ec e4 02 d0 0c 80 c5 00 01 00 00 20 00 00 00 ????????.?.. ...
    80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
    90: 03 ae 03 ae ff ff 03 ae 00 00 00 00 00 00 00 00 ????..??........
    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 ff 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 02 60 f2 00 02 00 00 00 10 00 00 00 00 .C??`?.?...?....
    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..........
    root@imx8mp-var-dart:~#

    [2]  You said >> "One other follow up question, what do you mean here by the below statement? "

    it's abnormal case.

    I means, it's connect the 4 camera, but one of 4 camera was broken.

    As this status, the output signal of DS90UB960 doesn't work.  ( I check it by oscilloscope )

    best regards,

    hosung shin.

  • Hi Hosung,

    Thanks for your follow up and for providing these registers. Have you tried the 3 camera configuration using other CSI forwarding modes? Specifically I'd be curious if any issue was observed both line concatenated forwarding and basic synchronized forwarding.

    Best,

    Thomas

  • Hi Tomas,

    I had already tried it.

    [1] the 3 camera configuration >> it work fine

    [2] the 2 camera configuration >> it work fine

    But, as our case, we don't recognize the broken camera.

    then, we don't change the camera's configuration.

    Is there a way like this ( don't recognize the broken camera ) ?

    best regards,

    hosung shin.

  • Hi Hosung,

    To clarify, there are no issues using the 2 or 3 camera configurations, however you'd like to know if the other images which are connected are not sending error-free CSI data? Would one of the bits in RX_PORT_STS2 register (0x4E) be helpful here? There are bits in this register to detect CSI-2 errors, line length change, and unstable line length.

    Best,

    Thomas

  • Hi Thomas,

    I got it, thanks you

    best regards,

    hosung shin.