• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 33 subscribers
  • Views 495 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DS90UB936-Q1: ds90ub936-q1 power-up sequence vs. I2C commands

Piotr F.
Intellectual 2910 points
Part Number: DS90UB936-Q1

Hello Team,

Can you help in understanding:

  1. What is the minimum time after deserializer is put out of reset (PDB pin is HIGH) and first local I2C message that can be issued (t1)?
  2. What is the minimum time after LOCK indication is asserted and first remote I2C message that can be issued (t2)?

  • 0
    TI__Intellectual 2930 points

    Piotr

        These are not specified since these numbers vary from different system configurations. Assuming all power supplies are stable, including VDD11, local I2C communication can be ready within typically 10 ms, assuming the bus is free and not being held up by any other slaves. Far end is even more system dependent and depends on potential bus hold up scenarios due to spurious noise on the system at power up. Assuming worst case, meaning bus is held up due to some noise event at power up , this could be as much as 1s. This could be drastically reduced by programming Reg0x0A[1] which will speedup the internal watchdog timer on 953/935. In these cases the bus can be available for external communications typically within 400ms. Again this assumes a typical use case, no issues with cables, no issues with PCB or potential loss of lock issues

    Thanks

    Vijay