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.

DS90UB954-Q1: DS90UB943 I2C have no ack

Part Number: DS90UB954-Q1

HI TI employee

My client encountered a problem when using 954+953 to design the camera. When the MCU configured the camera by writing 954, the I2C of 954 had no ACK, and generally occurred in the third byte.

The waveform of I2C is as follows.

  • Hello,

    Are you having issue with SoC communication with 954 OR SoC communication with the imager?

    If it's SoC communication with 954:
    - What's your I2C pull-ups?
    - What is the I2C address of the 954?
    - The I2C address can be shown in 7-bit or 8-bit mode. Make sure you are using the right I2C address.
    - Can you read reg 0x00 from the 954 and see what it gives back?



    If it's the SoC communication with the imager:
    - Did you set the alias correctly? If not, follow the instructions below:

    -Des reg 0x4C: Select the right RX port to write
    -Set/Check real I2C addresses:
    -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
    -Reg 0x5C SER_ALIAS_ID: Set the alias serializer I2C address
    -Reg 0x65 SLAVE_ALIAS_ID[0] (camera alias ID): Set the alias CMOS sensor I2C address

    - 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?
    - Is the imager initialized properly?
    - Does the SoC support clock stretching? The SoC needs this feature to communicate to the imager.


    Best,
    Jiashow