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.

DS90UB953A-Q1: Question about 954 and 953

Part Number: DS90UB953A-Q1

Dear Team,

Customer use 953 954+ 953 954 in cascade.
They faced 2-stage 954-953 configuration issue as below,
Could you guide us how to use by-pass mode or share 2-stage 954-953 reference code for us?



We appreciated your great support!

How would we connect the second 954 for same i2c address?

I think serializer/ deserializer's device ID need to different. right?

If device ID is the same. could we read it and set Alias ID? 
Is it bypass mode at first stage 954-953?

Many Thanks,

Jimmy

  • Hi Jimmy,

    Thanks for reaching out about this question. I think the critical piece here will be setting the slave alias and slave ID correctly on the deserializer side. We could then enable pass through from the SOC I2C bus to the 953 repeater I2C bus (and ultimately the final 953 and imager).

    We're directing a training over the start of this week in Santa Clara, I can provide some more detailed guidance here tomorrow if needed.

    Best,

    Thomas

  • Hi Thomas,

    We appreciated your great support!

    Please provide some more detailed guidance to us.

    We need your strong support!

    Many Thanks,

    Jimmy 

  • Hi Jimmy,

    In this case we'd set up a slave ID on the SOC 954 as the physical address of the remote deserializer (connected to the first hop 953) as shown below.

    The slave alias[0] will be set up on the 954 connected to the SOC, and will be the address which is used for the remote 954 on the SOC I2C bus.

    A similar process will be set up on the remote 954 to allow for the targeting of the Imager.

    For the targeting of the serializer on both the local and remote 954 we will need to configure the SER_ALIAS register.

    Does this make sense?

    Best,

    Thomas