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.

DS90UB913,4A-Q1 / PLL Lock time at the temporary stop of PCLK input

Guru 20090 points
Other Parts Discussed in Thread: DS90UB913A-Q1

Hello,

Please see the attached file as the DS90UB913/4A-Q1 VSYNC/PCLK/Lock  wavefroms.

20150107_ds90ub913waveform of serdes.pdf

Input PCLK for DS90UB913A-Q1 was stopped temporarily.
In this time, VSYNC of DES is asserted Low and this time is longer than VSYNC of SER.
As a result, image data was missed at the time between SER VSYNC is high and DES VSYNC is low.

(1)
Can we correct this missing time?

(2)
Could you please let me know the PLL lock time of DS90UB913/4A-Q1 when PCLK time was stopped temporarily ?
I think that this time is shoter than the PLL lock time on the datasheet EC table.

Best Regards,
Ryuji Asaka

  • Hello,

    Since our customer reqest the reply within today, could I have the reply please ? 
    Sorry for bothering you...

    Best Regards,
    Ryuji Asaka

  • Hello Ryuji,

    1) No, as you mentioned in your waveforms there is a PLL lock time associated with the incoming data on the 914A side.

    2) The PLL deserializer data lock time will still be approximately the same. This value is listed between 15 -22 ms (typical - maximum). Looking at Figure 17 in the datasheet, it would only be slightly less than the lock time on startup because the PDB pin has already reached VDDIO. The same formula applies for the PLL lock time on the serializer which will still be in the range of ~1-2 ms even after PCLK is stopped temporarily.

    -Sean

  • Hello Sean san,

    Thank you for your prompt reply.
    I understood.

    Best Regards,
    Ryuji Asaka

  • Hello Sean san,

    I got additional question from the customer.

    In our customer, DS90UB914A lock time is 3.7ms.
    There are the big difference between 15ms-22ms of datasheet and 3.7ms.
    I understood that the PDB pin has already reached VDDIO. But I think that this effect is small.
    Could you please let me know the reason ?

    I understood that there are the diffrence between measured value and specifications.
    However, could you please let me know the thing thought to be the element to affect at PLL lock time?

    Best Regards,
    Ryuji Asaka

  • Hi Ryuji,

    Are you sure that this is the data lock time on the 914A side? The lock time for the PLL on the 913A to sync to the incoming LVCMOS inputs is ~1-2 ms and much closer to the 3.7 ms that your customer is seeing.

    How is your customer measuring the lock time on the deserializer? This time should be from the PDB reaching a voltage of VDDIO/2 to the LOCK pin asserting high.

    -Sean

  • Hello Sean san,

    3.7ms is the lock time of 914 after PCLK is stopped temporarily. Our customer measured the PLL lock time of 913 as 0.6ms.
    And PDB is already high.
    Please see the attached file page 2.( this file is same with the attachment of my first post)

    0181.20150107_ds90ub913waveform of serdes.pdf

    According to your first reply, lock time is slightly less than the lock time on startup because the PDB pin has already reached VDDIO.
    Are there any possibility that  the lock time change to 3.7ms from 15-22ms if the PDB pin has already reached VDDIO ?

    Best Regards,
    Ryuji Asaka
    Ryuji

  • Hi Ryuji-San,

    The datasheet is slightly confusing because the lock time mentioned for 914A which is 12-15 ms is really the power-up to
    LOCK delay which as you know was stated previously as the time taken from PDB = VDDIO/2 until LOCK = HIGH. The main point
    to note here is that valid LVDS data is constantly being streamed in over R_IN+/-.

    There is a more specific definition of "lock time" which is the time from the LVDS data on R_IN+/- becoming valid to the
    LOCK pin rising HIGH. This ASSUMES that PDB = HIGH already and this lock time is actually much less than the power-up to LOCK
    delay described above. The 3.7 ms that your customer is seeing for LOCK time (with PDB = HIGH and PCLK restarted) is
    a typical measurement one would expect to see and there is no need for worry.

    I believe the reason why this difference in LOCK time is hard to see with the PDB transition from VDDIO/2 to VDDIO is
    because Figure 12 in the datasheet is not necessarily drawn to scale in regards to the start-up timing of the PDB pin.

    Best regards,
    Sean

  • Hello Sean san,

    Thank you for the reply.
    I understood that the lock time with PDB=High and PCLK restarted is may reduced to 3.7ms from the datasheet lock time of 15-22ms.

    Can we show the maximum lock time of 914A with PDB=High and PCLK restarted?
    Our customer request the maixmum time of this condition.
    I already explained we can gurantee the lock time of 22ms(max) only to our customer.
    However, if there are the refference data which you can share with us please let me know.

    Best regards,
    Ryuji Asaka

  • Hi Ryuji-san,

    Testing this on a bench in the lab, the LOCK delay should very close to 3.7 ms in testing on our 913A/914A EVM's. This would be a typical condition.

    Unfortunately, we cannot provide a maximum condition as reference data because this would need to go through characterization like all of the datasheet conditions that we test for.

    The correlation here makes sense because measuring the LOCK time from PDB going HIGH will be a much longer time compared to waiting for valid data on RIN+/-. This is because the deserializer device is still booting up during and after the ramp of the PDB pin, whereas this is not the case when the system is waiting on valid data to be received over the link and both Ser/Des devices have already been ON for a long time.

    Hope this helps Ryuji-san.

    Sean

  • Hello Sean san,

    Thank you for your help.
    I understood.

    Best Regards,
    Ryuji Asaka