DS90UB962-Q1: connection questions between DS90UB962 and DS90UB933

Hello,

When you say sometimes there is any issue to you mean that sometimes when the system is power cycled it does not come up correctly? But other times it is working without issue?

Best Regards,
Casey 

Hello,

In addition to what Casey suggested, I would like to check if you're seeing consistent lock. Could you repeatedly read reg 0x4D and 0x4E let me know if you see any lock issues?

Best,

Jiashow

Hello,

Normal image Size:1920x384.

Sensor power on-(MIPI-4Lane)-ISP--DS90UB933--DS90UB962--power off.

Repeat this process, sometimes the image data that DS90UB933 sends to DS90UB962 is normal, sometimes it is problematic.

The DS90UB962 register shows that when the image data is normal, LINE_COUNT:0x73=01,0x74=0x80, LINE_LEN:0x75=0x0F,0x76=0x08,(1920x384).

When the image data is abnormal LINE_COUNT:0x73=01,0x74=0xA4,LINE_LEN:0x75=0x00,0x76=0x04(4x420).

I suspect that the register matching between DS90UB933 and DS90UB962 is not done well, because for the same camera, the debugging of DS90UB933 and DS90UB934 is ok,

but I have not found out which register is not matched well.

Best Regards

Hello,

First read 0x4D,0x4E: 0x4D=0x13,0x4E = 0xCD,

Then repeat reading 0x4D, 0x4E: 0x4D = 0x03, 0x4E = 0x0C

Best Regards

Hello,

Are the readings for register 0x4D the same between a passing case and a failing case? In register 0x4E it looks like you're reading buffer and CSI errors.

Since you're reading the wrong line count/length, could you verify your imager initialization and make sure everything is programmed correctly and consistently? Also, could you verify the FV/LV timing control (refer to datasheet sec 7.4.12).

Hello Jiashow,

Sorry for the late reply.

After testing, the value of register 0x4D is the same.

SerDes(DS90UB962,DS90UB933) initialization is performed after each power on supply.

FV,LV is controlled by 0x7C,0x7C=0x81.

Now sometimes the Line_Count is read correctly (384) and sometimes incorrectly (420), please help to check the initialization Settings of SerDes in my question. Is it because some registers between DS90UB933 and DS90UB962 do not match correctly, which causes the synchronization problem?

Thank you very much.

Best Regards

Hello Jiashow,

The correct value of FV_MIN_TIME is not known.

Now FV_MIN_TIME 0xBC defaults to 0x80(128), FV_MIN_TIME according to 7.4.12 Mode Raw10 is 261(0x0105),0xBC cannot fill in 0x0105.

I tried to change the value of 0xBC to something else, but nothing worked.

Thank you very much.

Best Regards

Hello,

Just to confirm, changing the FV_MIN_TIME didn't help?

Could you check the following:

1.  933 power sequence to make sure it's following the datasheet.

2. Enable and disabling camera streaming to see if the issue goes away.

Best,

Jiashow

Hello Jiashow,

I'm really sorry that I don't quite understand what you mean. Could you please tell me which registers I need to operate?

The image information output by the Sensor is 1920x1080, and then after being processed by ISP, the output to DS90UB933 is 1920x384. When 1920x384 is transferred between DS90UB962 and DS90UB933, does it need to carry out special operation on some registers?

In addition, the camera hardware is OK, so I think some registers between DS90UB962 and DS90UB933 do not match correctly. Please help to check the following initialization Settings of DS90UB962 and

DS90UB933:

DS90UB962 initialization Settings:

WriteI2C(0x01, 0x12)

WriteI2C(0x4C, 0x01) // Set up Port0

WriteI2C(0x70, 0x1F)

WriteI2C(0x6D, 0x7F) // RAW10 Mode

WriteI2C(0x6E, 0xAA)

WriteI2C(0x5C, 0xB0) //933 alias id

WriteI2C(0x7C, 0x81)

WriteI2C(0x10, 0x91)

WriteI2C(0x58, 0x58)

WriteI2C(0x19, 0x0D)   //FS_HIGH_TIME_1

WriteI2C(0x1A, 0x04)   //FS_HIGH_TIME_0

WriteI2C(0x1B, 0x75)   //FS_LOW_TIME_1

WriteI2C(0x1C, 0x2E)   //FS_LOW_TIME_0

WriteI2C(0x18, 0x01)

WriteI2C(0x20, 0x00)

WriteI2C(0x32, 0x01)

WriteI2C(0x33, 0x01)

DS90UB933 initialization Settings:

WriteI2C(0x01, 0x31)

WriteI2C(0x0D, 0x99)

Thank you very much.

Best Regards