• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 21 subscribers
  • Views 422 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.

CDCE913 Spec

Mike H Meyer
Expert 1560 points
Other Parts Discussed in Thread: CDCE913, CDCE62002, CDCM61004

I'm looking at using the CDCE913 with a Gigabit Ethernet PHY that has requirements for 4ps RMS jitter (12KHz to 20MHz) or 200ps “total jitter”.  The CDCE specifies 70 ps cycle-to-cycle (10K cycles) and 100ps peak-to-peak (10K cycles).  If I understand correctly the difference between these two methods of measuring jitter is the statistical modeling that’s included in the Total and RMS measurements, but not in the 10K cycles of pk-pk or cyc-cyc.  I’m thinking I may need to use something better, like the CDCE62002, but at 3x the cost I want to make sure I really need that.

  • 0
    TI__Mastermind 32575 points

    Yes, indeed, you'll need a part with lower jitter.  You may consider the CDCM61004 family of pin-configurable clock gens.

    Alan

  • 0 in reply to Alan O
    Expert 1560 points
    Thanks for the quick response. The problem I’m having is that I need to justify the better/more-expensive parts. Can you point me to documentation that says that the CDCE913 isn’t good enough for the Gigabit PHY I’m using? Alternately, is there something (app note? math?) that I can use to demonstrate that 100ps pk-pk over 10K cycles isn’t better than 200ps total jitter (or 4ps RMS jitter 12KHz-20MHz).