• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 33 subscribers
  • Views 803 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.

SigCon Architect - "Reset CDR" button

Kawai
Guru 19785 points
Other Parts Discussed in Thread: DS125DF410

Hello Team,

Please tell me about SigCon Architect GUI.

What is the difference between the "Reset CDR" button in the High Level Page and Eye Monitor Page ?

I am using DS125DF410 for 5Gbps input signal. After setting the data rate settings to Infiniband or manual setting to 5Gbps, I am clicking "Reset CDR" button in the High Level Page, however, the device would not lock to the input data (looses lock frequently). Instead of clicking the "Reset CDR" button in the High Level Page, I tried the one in the Eye Monitor Page. In this case, CDR seems to be resetting correctly and locked to the input data. I believe they are not completely the same.

It also acquired LOCK by starting the eye monitor. Is that because this step includes CDR reset in REG 0x0A ?

Best Regards,

Kawai

  • 0
    TI__Mastermind 29655 points
    Hi Kawai-san,

    There should be no difference in how the "Reset CDR" button works for either of those pages. The button causes the selected channel register's Reg 0x0A[4:3] to assert to 11'b and then de-assert 00'b in order to set and then release CDR reset.

    Sometimes, I have noticed on the Eye Monitor page that it will not show the most updated CDR lock status, and clicking "Refresh from Device" will fix this issue. Also, in the DS125DF410 profile, I recall that a CDR reset is included when the user clicks "Single Capture" or "Continuous Capture."

    I believe a way to determine whether the buttons are truly the same is to "record" the Read/Write functions of SigCon Architect through the Python scripting utility. I will provide further details in the following thread:

    e2e.ti.com/.../502583

    Michael