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.

DS90UB927Q-Q1: DS90UB927 / 928 I2C communication error

Part Number: DS90UB927Q-Q1
Hi
My customers are testing SERDES with the configuration of DS90UB927 and DS90UB928. (Transmit data to DIFFERENTIAL using STP CABLE)
However, when the serializer (DS90UB927) calls the Deserializer (DS90UB928) using I2C, the SERDES lock is broken (the lock pin drops to low).
When calling Deserializer, we confirmed that Neck was returned from Deserializer, and confirmed that 0X0C of DS90UB927 was "01".
So I tried the test by connecting DS90UB928 EVM, but the lock is still broken. However, remote control of the 927 to 927 registers works normally.
And until the serializer calls the deserializer, it is confirmed that the lock is maintained well.
Could you advise me on why this is happening?
Is there a point I can check?
Below are all the settings that are changed from the default value in Serializer before calling Deserializer.

And 927,928 peripheral circuits are attached as follows.
Please ask for a review.
Please Check it
Thank you
Best Regards
From Anthony
  • Hello Anthoy,

    may I have your help to clarify some questions:

    1. how the LOCK is indicated as "LOW"? it happened when you start the I2C visit? how about the LOCK status in normal operation? do you use the scope to measure the LOCK signal whether it has high/low toggling?

    2. for i2c, first of all, you should make sure the link is robust (no bit error), you can check the 928's lock status  and error registers in d/s, also you need check 927's error register which is relative with the back channel communication

    3. if the link is robust, you need have correct I2C reg. setting: a. pass-through is enabled; b. the paired ser or deser's ID addr., alias name; c. you can use the alias ID to visit the remote device's I2C bus

    best regards,

    Steven