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.

DS125DF1610 locking.

Other Parts Discussed in Thread: DS125DF1610

Hi,

I have a question regarding the use of the DS125DF1610.

1. I would like to be able to use the pattern generator without having a data input to the chip. Is it possible to do so?

2. Will I be able to generate patterns at different rates for different channels?

3. In the case where I do have an sinal going through the CDR, will the pattern generator's frequency be locked with the data?

Thank you in advance,

Yuval 

  • Hi Yuval,

    1. Technically, yes, you can use the pattern generator without a data input to the chip by putting the device in free run mode. However, the data rate will not be as precise as when the DF1610 locks onto a known data input that operates at a fixed rate. This could be problematic if you need to output a specific data rate, such as a 10.3125 Gbps signal, and the DF1610 transmitter's free run mode does not give you the appropriate amount of precision to be used in your system.

    2. Yes, you can generate patterns at different rates for each channel. Each channel has its own VCO group and CAP DAC settings that can be applied independently.

    3. Yes, if the CDR is locked to an input signal, the pattern generator's frequency will be locked with that of the incoming data. If you wish to lock to higher frequency multiples of the input signal's data rate (not exceeding the VCO frequency), then you can accomplish this by disabling single bit transition checking.

    I would recommend that, in order to run the pattern generator at a certain desired rate, you should apply a clock signal at the input that is a divide-by-2 or more factor of the VCO operating range. This means applying a divide-by-2, 4, 8, or 16 clock on the input. (Remember that to convert the clock frequency in GHz looks like a "1010" data pattern that is operating at double the frequency in Gbps.) From there, you will be able to output a fixed pattern from the DF1610 output that is operating at a known data rate rather than at a less consistent free-run setting.

    Thanks,

    Michael
  • Thank you for the answer, Michael.
    Is it possible to get the pattern generator to lock on the reference clock signal?
    ref clock is 312.5MHz and the output frequency is 5GHz.
  • Hi Yuval,

    Thanks for your patience this past week. We were on holiday in the U.S. this past week.

    I do not expect you to lock onto a 312.5 MHz reference clock. The reason for this is because you will only be able to lock onto divide-by-2, 4, 8, or 16 value with relation to the VCO operating range. Since the operating VCO range for the DS125DF1610 is 9-12.5 GHz, the minimum clock that you will be able to lock to is 9 GHz / 16 = 562.5 MHz.

    With that having been said, it may still be possible to lock onto a 312.5 MHz clock signal at the input if you disable Single-Bit Transition checks (in order to enable locking at sub-harmonic rates of the actual operating rate), since 312.5 MHz is a divide-by-32 factor of 10 GHz.

    Thanks,

    Michael
  • Thanks Michael.

    The datasheet seems to state a 9-12.5 Gbps (not GHz) so I am assuming it will be OK, right?
    will it perform better if I provide a 625MHz clock as a data input instead (5GHz divided by 8 instead of 16).

    Thanks,
    Yuval
  • Hi Yuval,

    The internal VCO must operate at least twice as fast as the fastest frequency presented by the data. If we looked at a '1010' pattern at 9-12.5 Gbps, it would be the same as looking at a 4.5-6.25 GHz oscillator. Therefore, in order to sample 9-12.5 Gbps data accurately, the VCO must be running at 9-12.5 GHz. Thus, in the datasheet we state that we can lock to 9-12.5 Gbps data, but internally, the VCO is running at 9-12.5 GHz, and the divide-by ratios allow the retimer to lock to subrates of the VCO lock range.

    I believe you will have better success locking to an input clock at 625 MHz.

    Thanks,

    Michael
  • Thanks. You've cleared it up for me.
  • Hi,
    When trying to this, The output rate of the chip was the same as the input, meaning 625MHz. The only way I could get the 10Gbps output was by disabling the Single-Bit Transition checks, and trying to lock onto a high frequency data.
    Is there a way of locking to the low speed data in, and outputting a high frequency output, without disabling the single bit transition checks?

    Thanks,
    Yuval
  • Hi Yuval,

    Unfortunately, there is not. The DS125DF1610 (as well as our dual channel and quad channel 10-12.5G retimers) are designed so that in typical applications, they are able to filter out the possibility of two problematic situations:

    1. False Lock Detection (FLD): The retimer would false lock if it locks to a subharmonic of the real data rate's clock. This happens when the retimer misses transitions in the data rate because it is locking to that subharmonic data rate. FLD is able to check for this situation and prevent the retimer from undersampling.

    2. Single Bit Transition (SBT): If the recovered clock is a harmonic of the real data rate's clock, the retimer will be oversampling and reading multiple 0's and 1's without any single-bit transitions. SBT checks allow the retimer to ensure that it is not locking onto a data stream with a recovered clock much higher than the real clock used by the actual data. Therefore, SBT checks prevent the retimer from oversampling.

    Since you are looking for a unique case where you intentionally want the higher data rate output (10 Gbps), you must disable SBT checks. Otherwise, the retimer will implement FLD and SBT in its locking scheme by default.

    Thanks,

    Michael
  • Thank you, Michael.
    Will disabling the SBT cause an increased BER, or decrease the performance in any way?
    -Yuval
  • Hi Yuval,

    In the situation that you are using the DS125DF1610, you should not have a decreased performance as a result of disabling SBT, since you are using the 625 MHz clock input to the DF1610 as a reference clock type input.

    Your question got me thinking about how the device would behave if we disabled SBT checking in general. After discussing with my colleagues, I have realized the following. From the perspective of using the DS125DF1610 in "mission mode," meaning the regular operating mode where the device is used between two endpoints to recover incoming data and retime the output, disabling SBT checks may ultimately result in you incurring a smaller input jitter tolerance budget due to the decreased UI, since the clock will be attempting to capture data at a higher data rate than is actually presented at the input of the DF1610. While this may not necessarily result in more bit errors, capturing at a higher data rate than necessary may be more problematic in a particularly noisy or lossy scenario. Thus, in mission mode, we recommend keeping SBT enabled.

    Thanks,

    Michael