• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 33 subscribers
  • Views 178 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DS90UB953-Q1: can't visit 0x25 address

Amelie Zheng
Genius 10865 points
Part Number: DS90UB953-Q1

Hi Team,

My customer would like to visit 0x25 device from 954 side, which means when using i2cdetect -r -y bus_num, it could see the address 0x25.

           sensor( address 0x25)  <--->   933(address 0x58)     <---->     954(address 0x30)     <----->   CPU

Customer now configure as this document shows:

            i2cwrite  0x58 0x58     //enable pass through
            i2cwrite  0x5c 0xb0     //953 device address

            i2cwrite  0x5d 0x4a     //0x25 address

            i2cwrite  0x65 0x4a    //0x25 address

But after this configuration, customer still can't visit 0x25. Could you kindly give some advice?

  • 0
    TI__Guru** 107810 points

    Hello Amilie,

    can you clarify what SER are you using? In the title and in the configs you are saying 953 but on the main clarification you said 933!!

  • 0 in reply to Hamzeh Jaradat
    TI__Genius 10865 points

    Oh! Terrible sorry for this. customer use 954+933. Sorry for make you misunderstanding...

  • 0 in reply to Amelie Zheng
    TI__Guru** 107810 points

    Hello Amilie,

    Please check if they 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 automatically.

    -Reg 0x5C SER_ALIAS_ID: Set the serializer Alias
    -Reg 0x5D SlaveID[0]: Set the real sensor I2C address
    -Reg 0x65 SLAVE_ALIAS_ID[0] (camera alias ID): Set the sensor Alias

    - Only communicate to the serializer using the Alias indicated in 0x5C (the address indicated in 0x5C is 8-bit)
    - Only communicate to the imager using the Alias indicated in 0x65 (the address indicated in 0x65 is 8-bit)

    Also, please double check

    - The I2C pull-ups?
    - Is the imager initialized properly?
    - Does the SoC support clock stretching? The SoC needs this feature to communicate to the imager.