• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Clocks & Timers » Clocks & Timers Forum » synchronizing CDCE72010 dividers across a large system
Share
Clocks & Timers
  • Forum
  • Announcements
  • Files
  • E2E Wiki
Options
  • Subscribe via RSS

Forums

synchronizing CDCE72010 dividers across a large system

This question is answered
David Burton
Posted by David Burton
on Feb 05 2012 13:49 PM
Intellectual820 points

I have a system with 8 CDCE72010 clock drivers.  I need to set up all the dividers and then have them synchronized over the entire system.  I expect I need to use the nReset hardware input to do this.  I don't see how it could work doing it through an SPI command.

I don't see any power down or reset recovery timing in the data sheet.  Is there a spec for this?  What should I need to do to make sure all 8 of my devices are in synch?

Thanks.

CDCE72010 reset power down divider synchronization
Report Abuse
  • Reply
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
All Replies
  • Matt Sunna
    Posted by Matt Sunna
    on Feb 06 2012 10:24 AM
    Expert3240 points

    Hi David,

    On page 68 of the latest datasheet, there is a list of events that can trigger a SYNC event. This can be done using a SPI command. If you are able to connect multiple outputs from the EVM to an oscilloscope, this allows a good way to view the edge alignment before and after a sync event.

    The PDN and RST recovery time is possible to spec to some extent (although it would take me some time to get this data), however there is a significant amount of time afterwards for the PLL to lock which is dependent on input/VCXO frequencies, divider settings, and loop filter configuration. So it can be a little complex to predict this accurately. Fortunately, I don't think it is necessary to use the nRest pin to acheive SYNC.

    Best regards,

    Matt

     

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • David Burton
    Posted by David Burton
    on Feb 08 2012 15:24 PM
    Intellectual820 points

    Since SPI is so vastly slower than my input clock (120MHz) I don't see how I can be confident to get a good sync across multiple systems.  I don't think I can even confidently send the SPI command simultaneously.

    I am not using the VCO or PLL functions.  I have a fixed high precision clock that is input to the VCXO input and used directly in the dividers.  I guess this is why I believed the hardware reset line could be used to sync the dividers.  There should be no PLL lock issues needing to wait for.

    I have:

    120MHz input to VCXO

    1 divider set to 1

    1 divider set to 3.

    8 dividers identically set to  between 6 and 20.  (Whatever the choice is they are all the same)  These are the ones I MUST have synched across the system of 8 clock chips.

    Thanks,

    David B

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • David Burton
    Posted by David Burton
    on Feb 13 2012 20:43 PM
    Intellectual820 points

    I have been able to sync the dividers by setting reg 6 bit 5 high and using the reset input.

    I would like to hear other ways that can work across a large system if you have other ideas.

    Thanks.

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Michael S
    Posted by Michael S
    on Feb 23 2012 07:47 AM
    Verified Answer
    Verified by Fritz
    Genius9640 points

    Hi team,

     

    Do we have an update available?

     

    regards,

    Michael

    Regards,

    Michael S.

    ACSC Digital Apps

     

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Fritz
    Posted by Fritz
    on Feb 23 2012 13:11 PM
    Expert4370 points

    Hi David,

    To have a deterministic output on multiple CDCE72010, you would need to elimiate the device delay from input to output. This is called "zero delay" and is done by using the external feeback mode. basically, you want to feed one of your outputs back into the AUXILARY INPUT of the CDCE72010 and set the internal mux to the PFD such that the feedback divider is driven from the AUX input and not the VCXO input.

     

    Best regards,  Falk

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Fritz
    Posted by Fritz
    on Feb 23 2012 13:13 PM
    Expert4370 points

    PS: I forgot to mention: this zero delay tunes out both the CDE72010 delay AND the VCXO output phase uncertainty. If you keep the line length the same from the common clock source to all CDCE72010, and of course also keep all output trace lengths the same, you have a total compensated clock distribution, and the clock phase of the central source is phase aligned to all output clocks.

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • David Burton
    Posted by David Burton
    on Feb 23 2012 13:37 PM
    Intellectual820 points

    Thanks for the info.  This is fairly bad news for us since all ten of the outputs are used in our system.

    It's possible we could move our divide by 1 output to another clock driver, or do without it.  If we can use our divide by 3 output for the feedback source as well as the input to a CDCLVD1208 this could work.  We would have to route the div by 3 past the AUX input with no termination and then to the 1208 where it would be terminated.

    We need 8 divide by 6..12 outputs that must by synced.  We have one divide by one that doesn't care about sync.  We have one divide by 3 that doesn't care about sync.  If we give up one output in order to use the AUX in, we then only have 8 divide by 6..12 and the divide by 3 available as outputs for the feedback.

    Thanks

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • David Burton
    Posted by David Burton
    on Feb 23 2012 13:37 PM
    Intellectual820 points

    Thanks for the info.  This is fairly bad news for us since all ten of the outputs are used in our system.

    It's possible we could move our divide by 1 output to another clock driver, or do without it.  If we can use our divide by 3 output for the feedback source as well as the input to a CDCLVD1208 this could work.  We would have to route the div by 3 past the AUX input with no termination and then to the 1208 where it would be terminated.

    We need 8 divide by 6..12 outputs that must by synced.  We have one divide by one that doesn't care about sync.  We have one divide by 3 that doesn't care about sync.  If we give up one output in order to use the AUX in, we then only have 8 divide by 6..12 and the divide by 3 available as outputs for the feedback.

    Thanks, this issue is most urgent.

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
TI E2E™ Community
  • Support Forums
  • Blogs
  • Videos
  • Groups
  • Site Support & Feedback
  • Settings
TI E2E™ Community Groups
  • TI University Program
  • Make the Switch
  • Microcontroller Projects
  • Motor Drive & Control
Other Communities
  • Deyisupport
  • Designsomething.org
  • beagleboard.org
  • TI on Element 14
  • TI on TechXchangeSM
Other Technical & Support Resources
  • WEBENCH® Design Center
  • Product Information Centers
  • Technical Documents
  • TI Design Network
  • TI Technical Articles
  • TI Training

All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
embedded processors, along with software, tools and the industry’s largest sales/support staff.

© Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
Trademarks | Privacy Policy | Terms of Use