DS90UB960-Q1: [DS90UB960-Q1] about the resized image in DS90UB960-Q1

Hi Shin,

Thank you for your inquiry. Could you please help to answer some of the questions below regarding this issue?

1. What serializer is used in this application? 
2. Is the same serializer used in both of these imagers?
3. Are all 4 serializers connected to the DS90UB960?
4. Are there any differences in the serializer register settings on the first image size and second image size?
5. Could you confirm which CSI-2 forwarding mode is being used by the DS90UB960?

These questions will help us to get a better understanding of your application to resolve this issue.

Best,

Thomas

Hi Thomas,

I add it like below

1. What serializer is used in this application? 
2. >> It's the camera module ( include the ISX016 sony's sensor and the DS90UB913 )
3. Is the same serializer used in both of these imagers?
4. >> yes, it's the same serializer ( same HW )
5. Are all 4 serializers connected to the DS90UB960?
6. >> yes, that's right.
7. Are there any differences in the serializer register settings on the first image size and second image size?
8. >> it's the sony ISX016 sensor's register
9.      in case first image, use the defined value setting
10.      ( effective image size (  H 1280 / V 720) and output image height ( H 3300 / V 750 )
11.      in case second image, use the user defined value setting.
12.      ( effective image size (  H 1024 / V 768)  and output image height ( H 0 / V  0 )  >> can't set the output image height.
13. Could you confirm which CSI-2 forwarding mode is being used by the DS90UB960?
14. >> yes, that's right.

best regards,

hosung shin.

Hi Shin,

Thanks for your follow up.

1. Have you confirmed that the serializer and deserializer are locked in the situation for the second camera where video is not obtained? This can be checked via register 0x4D on the deserializer
2. What PCLK rate & mode (10 bit vs. 12 bit) is used in the serializer?
3. If lock is detected, could you check the PCLK_DETECT bit in register 0x0C on the DS90UB933?
4. When checking register 0x73 and 0x74 for line lengths, what do these registers read? Do these registers also read 0?

Essentially I'd like to confirm if we're getting valid data from the serializer, or if this is a CSI output issue from the deserializer. These questions will help to narrow this down.

Best,

Thomas

Hi Shin,

Please be noted that the E2E support forums will undergo maintenance from Sept. 28 to Oct. 2, hence it will not be available during this time. If you need design support during this time, you can reach me at t-bejin@ti.com where we can continue this discussion.

Normal E2E support should be back by Monday, Oct. 3.

Best,

Thomas

Hi Thomas,

It's reply to your question  like below..

I think the answer would be a register dumped value.

Also, as you can see the register dumped value, the register 0x73 and 0x74 for line lengths is 0 (Zeor).

[ second image ] >> effective image size (  H 1024 / V 768)  and output image height ( H 0 / V  0 )

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 00 00 00 00 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 ec 00 00 00 00 00 00 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 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:~#

and..for your question 2  >> 

1. What PCLK rate & mode (10 bit vs. 12 bit) is used in the serializer?

        >> It's use the 8bit mode ( YUV 8bit multiple)  and PCLK is 74.25 MHz 

           ( also, the frame rate is 30 fps )

best regards,

hosung shin

Hi Shin,

Thanks for your follow up, let me review this tomorrow and provide feedback for you.

Best,

Thomas

Hi Shin,

Do you know if we're able to read the serializer registers as well?

From the register dump it appears that we can confirm a few points. All FPD RX ports are enabled, lock is confirmed high with register 0x4D, we're using the correct BC frequency. While the DS90UB960 is set up correctly, it appears that we're still not getting any video data from the serializer as we can see in registers 0x73 and 0x74.

One potential issue here could be that we're not getting any data from the imager to the serializer. It could be helpful to look into this path.

Best,

Thomas

Hi Thomas,

Yes, you are right.

And, I think that It's not unreadable, it's read as 0 ( zero )

As I said..

In case my first image ( normal case )

it's register dumped value like below

This image set the effective image size H:1280 V720 and output image  H:3300 V:750 

( register 0x73 and 0x74 is 0x02 and 0xd0 )

But, in case second image, it's 0 (Zero )

>> ths second image set the effective image size H 1024 V768 and output image H:0 V:0

Then, when it's read as 0 (zero), Is there a way to force it to read a fixed size (1024x768 ) ? 

     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: 1b 4c 0d a6 ff ff 00 00 00 00 00 00 00 00 00 00    ?L??............

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 0f 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..........

best regards,

hosung shin.

Hi Shin,

The line length and line count registers are read only, and provide information on the CSI data which is received from the imager/serializer. In your case, it appears that we're not getting any data from the imager in case 2 (as we have lock but no data). Could we confirm that the imager is transmitting CSI data to the serializer in this case?

Best,

Thomas

Hi Thomas,

Thanks you for your support.

I think that this issue is solved in camera module.

Anyway, I am closing it.

best regards,

hosung shin.