Part Number: DS90UB954-Q1
Dear team,
My customer design with our 953 and 954 FPDlink device, but face to I2C no ACK during initialization.
I have search on E2E post( as below link), and get feedback from customer.
Please find customer's feedback below in red. Could you help to solve this issue? thanks.
local or remote?
Ans: Happened on the remote side.
If it's the SoC communication with the imager: (remote)
- Did you set the alias correctly? If not, follow the instructions below:
Ans: Yes, the same coding as order project and no issue happened in those projects.
-Des reg 0x4C: Select the right RX port to write
Ans: {0x4C, 0x01, 0},.
-Set/Check real I2C addresses:
Ans:
DS90UB953 I2C addr: 0x32
DS90UB954 I2C addr: 0x60
IMX307 I2C addr: 0x34
-Reg 0x5B SER DEVICE ID: Set the real serializer I2C address. This is typically loaded already
-Reg 0x5D SlaveID[0]: Set the real CMOS sensor I2C address
Ans: My 0x5D is 0x34.
-Reg 0x5C SER_ALIAS_ID: Set the alias serializer I2C address
Ans: My 0x65 is 0x32.
-Reg 0x65 SLAVE_ALIAS_ID[0] (camera alias ID): Set the alias CMOS sensor I2C address
Ans: My 0x65 is 0x34.
- Only communicate to the serializer using the alias address indicated in 0x5C (the address indicated in 0x5C is 8-bit)
- Only communicate to the imager using the alias address indicated in 0x65 (the address indicated in 0x65 is 8-bit)
- What is your I2C pull-ups?
Ans: We used two 4.7K ohm.
Regards,
Ben
