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.

DS90UB960-Q1: Ser_ID and General Status Clarification

Part Number: DS90UB960-Q1

My customer is having issues connecting the Deserializer to the Serializer, but I think this is due to the fact that the I2C Master does not support I2C Stretching. That being said, there are a few issues they are still seeing that are leading to a few additional questions:

On SER_ID (0x5B) register on the deserializer, the datasheet said "this field is normally loaded automatically from the remote Serializer". Do you mean this field is automatically loaded when you power-up the system or it needs some configuration in the register ?

GENERAL_STATUS Register 0x52 Questions:

When I power up the SerDeser system and read the GENERAL_STATUS register 0x52, without any configuration command, I can see some changes in this register.

Most of the time I read the value 0x00 but sometimes, the value is 0x01, 0x20 or 0x21.

Value 0x01 appear very few times, like 20-30 times per hour (we made a script which read the register each second).

Value 0x20 appear for a unknown reason and usually never return to 0x00 unless I reset the device. 

Is this normal if the link has not been established between the SerDes?

 

In typical condition, does bit 0 (LINK_DET) should stay at 0x1 ? Do I need to configure the Des or the Ser to stabilize this link?

  • Hey Matt,

    SER_ID is loaded automatically once the SER/DES are locked to each other which should also be automatic once they are connected together. No configuration is needed.

    Not sure your question about 0x52 - this register is not "GENERAL_STATUS." It is "SENSOR_STS1" and not sure why they are monitoring this register?

    Best Regards,
    Casey
  • Hi Casey,

    Sorry, the questions regarding GENERAL_STATUS were in regards to the Serializer DS90UB953. Should I move this over to a separate thread in regards to the serializer instead?

    Thanks,
    Matt
  • Hey Matt,

    This makes more sense now. Based on the registers there doesn't appear to be any solid link between the 953/960. What hardware are they using to perform this test?

    Best Regards,
    Casey
  • Hi Casey,

    They are using their own designed boards with the 953/960 on them. Power is provided using DC supplies, and the clock is provided to the 960 that I've verified is a very clean 25MHz. I'm assuming that the issue is the Raspberry Pi 3 as it does not natively support I2C Clock Stretching.

    If the behavior is normal if there is no link, the only question is should the LINK_DET bit be set as soon as the link is established or does anything need to be configured beforehand?
  • Hey Matt,

    Nothing needs to be configured if the parts are properly strapped into CSI-2 mode (not backwards compatibility mode, plus the proper clocking mode for what they are using).

    Please verify the mode strapping matches expectations on both sides

    Best Regards,
    Casey