Part Number: DS90UB954-Q1
I have a DS90UB954 connected remotely to a pcb with two DS90UB953.
There are two possible I2C addresses for the 953 – 0x18, 0x19.
RX Port 0 is connected to 0x18 and RX Port 1 is connected to 0x19.
There is an accelerometer on the pcb also has the same two possible address 0x18 and 0x19.
I have selected 0x19 and connected it to the 953 (0x18) on RX Port 0.
I am using aliased addressing. BCC_CONFIG REG 0x58 is set to 0x5D
On most occasions I can correctly read the accelerometer ID register (0x33) without any problem.
However, sometimes the device powers up in such a way that the value returned is (0x00)
I scope both the 954 I2C bus and the 953 I2C bus. The correct data is output by the accelerometer (0x33) but it isn’t transferred correctly to the 954 I2C where it appears as (0x00)
I am wondering if there is some problem with the addresses being so close in value. I can't see why this should be but this is the only device which ever causes an issue.
The transaction always appears on the 953 I2C bus which implies that it is being recognised as external to the 953 - at least in the Maser -> Slave direction.
Any help would be much appreciated.
Thanks
Paul