DS90UB953A-Q1: Disable pairing 953 with 954

Juergen Suetterlin

Part Number: DS90UB953A-Q1

Hello,

we develop testing tools which will be inserted into a FPDLINK3 link (called TAP, test access point). So a ECU deserializer (ECU_DES) connects to our TAP_SER which is logically connected to a TAP_DES which will connect to the sensor serializer (CAM_SER).

ECU_DES <= cable => TAP_SER <-logic-> TAP_DES <= cable => CAM_SER <-> CAM

Without TAP a ECU would configure the ECU_DES first and then the CAM_SER and the CAM.

When the TAP is introduced, the ECU_DES is connected to the TAP_SER, the ECU_DES pairs with the TAP_SER. This leads to the situation that the ECU now configures the TAP_SER instead of the CAM_SER.

Is there any possibility to disable the pairing between the ECU_DES and TAP_SER?

This shall avoid that ECU accesses via the serializer alias address (954.ALIAS_REMOTE_SER_ADDRESS) address the TAP_SER, but come out of the TAP_SER as I2C packets?

over 4 years ago

0 Nicholas Darash over 4 years ago

TI__Mastermind 18755 points

Hello,

It sounds like you are essentially using a repeater in this system to deserialize and re-serialize the data coming from the camera. Is the issue that you are trying to write I2C to the camera serializer but it is only makes it to the TAP serializer? If so, then the solution is to use the SLAVE_ID regsisters (0x5D to 0x64) and the SLAVE_ALIAS registers (0x65 to 0x6C) to alias the TAP_DES and and the CAM_SER devices.

For example:

in ECU_DES

SER_ID = TAP_SER I2C address
SER_ALIAS = some unique I2C address
SLAVE_ID[0] = TAP_DES I2C address
SLAVE_ALIAS[0] = some unique I2C address
SLAVE_ID[1] = TAP_DES SER_ALIAS register value
SLAVE_ALIAS[1] = some unique I2C address

Obviously set the address of the devices to something that will work in your system but this is the idea.

Regards,

Nick

Interface

Interface forum

DS90UB953A-Q1: Disable pairing 953 with 954