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.

DS90UB926Q-Q1: can't detect 926 via I2C

Part Number: DS90UB926Q-Q1


Hi team,

customer use 927+926, found that sometimes the 927 can't detect 926 and, can't read or write 926.  the 926 ID address is 0x2C.

because there have  two slave device at 927 I2C bus, one is 926 one is others.  both of them I2C address is 0x2C(7bit),0x58(8bit). so, customer use alias ID to read/ write 926.

below is 927 reg in abnormal condition. the lock is stable high, 0x06 is 0x58, correct. set slave ID of 0x07 is 0x58 and slave alias ID is 0x98. but, from SOC log, it say that can't detect 0x98 slave device at I2C bus.

can you help share your comments?

in additional, I have questions is that 

1. if in 927 side, set DES slave alias ID, how about the 926 reg 0x00 value? does the reg 0x00 of 926 will be changed to slave alias ID? for example, in this case, the IDx of 926 is 0x58, set alias ID to 0x98 in 927, read the 0x00 0f 926, what's the value? 0x58 or 0x98?

2. for the DES ID and slave ID in 927 side,, does it can be changed in real-time or only power up? during the normal work, disconnect DES, what's the values of DES ID and SLAVE ID in 927? keep previous ID address or will change to 0x00?

  • Hi Betty

    customer use 927+926, found that sometimes the 927 can't detect 926 and, can't read or write 926.  the 926 ID address is 0x2C.

    I'm not 100% following what the normal and abnormal conditions are here. Can you create a simple block diagram of the master/slaves and their addresses?

    Are the serializer and deserializer getting initialized to the same settings during normal and abnormal conditions? 

    How often does the abnormal condition of not being able to read/write to des occur? 

    Do you have a register dump of a normal condition? 

    Regards, 

    Logan