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

c6657 Clock Requirements

Lou Dickinson
Prodigy 240 points

Other Parts Discussed in Thread: CDCE62005

Must a customer use CDCE62005 if they are not using PCI, SRIO, and MCM/hyperlink?  How are those pins handled?  No connect or tied high/low/Gnd?

They do require ENET, does this mean they need the shared clock with SRIO?

Given above subset of interfaces to be used, is there a simpler/smaller clock we recommend?  Do they need jitter cleaning?

 

  • 0
    TI__Mastermind 42545 points

    The use of the CDCE62005 is not required but it does meet the jitter specification for C6657.  If the customer is using the Ethernet interface they will still need clocks for the CORECLK, the DDRCLK and the SRIOSGMIICLK. The later is used by the Ethernet interface and must be present.  While I know of a two output clock generator in the same family as the CDCE62005, I am not familiar with a three output version of the device.  If they pick a different device they will have to compare the jitter with the requirements provided in the hardware design guide.  The clocks must meet these specifications for proper operation.