I have an IIC master connected to DS90UB954 deserializer via a "local" IIC connection.
The DS90UB954 is connected to a DS90UB913A serializer via a FPD serial connection.
The DS90UB913A is connected to an imager via a "remote" IIC connection.
The IIC master is able to communicate with the DS90UB954 deserializer.
The DS90UB954 deserializer is able to communicate with the DS90UB913A serializer, and indicates "lock".
The remote IIC connection between the serializer and the image appears functional, as i've viewed the IIC traffic present on the "remote" IIC bus, and have confirmed that the device address present in the traffic is correct.
When the IIC master attempts to write to the imager, the imager successfully sees the IIC write command on the remote IIC connection, AND it acknowledges that message with an ACK on the "remote" IIC bus.
However, back at the "local" IIC bus (the one between the master and the DS90UB954 deserializer), I do not see that ack coming out of the DS90UB954 deserializer (and subsequently being passed back to the IIC master). As a result, the IIC master never sees that the imager has acked its IIC message, so the master assumes IIC communication has failed.
My question is, why is the DS90UB954 deserializer not relaying the ack to the "local" IIC bus?
DS90UB954 Device configuration notes:
* Address 0x4C is set to 0x03
* Address 0x58 is set to 0x58
* Address 0x5B is automatically populated with B0 (which is correct)
* Address 0x5C is set to 0xB0
* Address 0x5D is set to 0x20 (which is the address of the imager)
* Address 0x65 is set to 0x20
