Ug472 7series Clocking

7 Series FPGAs
Clocking Resources
User Guide
UG472 (v1.12) September 27, 2016

The information disclosed to you hereunder (the Materials) is provided solely for the selection and use of Xilinx products. To the maximum
extent permitted by applicable law: (1) Materials are made available "AS IS" and with all faults, Xilinx hereby DISCLAIMS ALL
WARRANTIES AND CONDITIONS, EXPRESS, IMPLIED, OR STATUTORY, INCLUDING BUT NOT LIMITED TO WARRANTIES OF
MERCHANTABILITY, NON-INFRINGEMENT, OR FITNESS FOR ANY PARTICULAR PURPOSE; and (2) Xilinx shall not be liable (whether
in contract or tort, including negligence, or under any other theory of liability) for any loss or damage of any kind or nature related to, arising
under, or in connection with, the Materials (including your use of the Materials), including for any direct, indirect, special, incidental, or
consequential loss or damage (including loss of data, profits, goodwill, or any type of loss or damage suffered as a result of any action
brought by a third party) even if such damage or loss was reasonably foreseeable or Xilinx had been advised of the possibility of the same.
Xilinx assumes no obligation to correct any errors contained in the Materials or to notify you of updates to the Materials or to product
specifications. You may not reproduce, modify, distribute, or publicly display the Materials without prior written consent. Certain products are
subject to the terms and conditions of Xilinxs limited warranty, please refer to Xilinxs Terms of Sale which can be viewed at
www.xilinx.com/legal.htm#tos; IP cores may be subject to warranty and support terms contained in a license issued to you by Xilinx. Xilinx
products are not designed or intended to be fail-safe or for use in any application requiring fail-safe performance; you assume sole risk and
liability for use of Xilinx products in such critical applications, please refer to Xilinxs Terms of Sale which can be viewed at
www.xilinx.com/legal.htm#tos.
Automotive Applications Disclaimer
AUTOMOTIVE PRODUCTS (IDENTIFIED AS "XA" IN THE PART NUMBER) ARE NOT WARRANTED FOR USE IN THE DEPLOYMENT
OF AIRBAGS OR FOR USE IN APPLICATIONS THAT AFFECT CONTROL OF A VEHICLE ("SAFETY APPLICATION") UNLESS THERE
IS A SAFETY CONCEPT OR REDUNDANCY FEATURE CONSISTENT WITH THE ISO 26262 AUTOMOTIVE SAFETY STANDARD
("SAFETY DESIGN"). CUSTOMER SHALL, PRIOR TO USING OR DISTRIBUTING ANY SYSTEMS THAT INCORPORATE PRODUCTS,
THOROUGHLY TEST SUCH SYSTEMS FOR SAFETY PURPOSES. USE OF PRODUCTS IN A SAFETY APPLICATION WITHOUT A
SAFETY DESIGN IS FULLY AT THE RISK OF CUSTOMER, SUBJECT ONLY TO APPLICABLE LAWS AND REGULATIONS GOVERNING
LIMITATIONS ON PRODUCT LIABILITY.
Copyright 20112016 Xilinx, Inc. Xilinx, the Xilinx logo, Artix, ISE, Kintex, Spartan, Virtex, Vivado, Zynq, and other designated brands
included herein are trademarks of Xilinx in the United States and other countries. PCI, PCIe, and PCI Express are trademarks of PCI-SIG
and used under license. All other trademarks are the property of their respective owners.
7 Series FPGAs Clocking Resources User Guide www.xilinx.com UG472 (v1.12) September 27, 2016
Revision History
The following table shows the revision history for this document.
.
Date Version Revision

03/01/2011 1.0 Initial Xilinx release.
03/28/2011 1.1 Updated disclaimer and copyright on page 2. Updated Clocking Architecture Overview
and Figure 2-2. Revised the discussion in Clock-Capable Inputs including adding
Table 1-1 and Figure 2-1. Revised some of the Global Clock Buffers descriptions. Revised
the description under Figure 2-17. Updated the I/O Clock BufferBUFIO section.
Updated Figure 2-20. Updated the Regional Clock BufferBUFR section. Updated the
description in Table 2-8. Revised Figure 2-23. Added the BUFMRCE to the BUFMR
Primitive section including Figure 2-25. Added BUFHCE to the Horizontal Clock
BufferBUFH, BUFHCE section. Moved Clock Gating for Power Savings.
Updated the MMCMs and PLLs section. Revised the Frequency Synthesis Only Using
Integer Divide section including Figure 3-4. Revised the discussion around adjacent
regions in CLKOUT[0:6] Output Clocks. Updated the examples after Equation 3-11.
Moved and revised VHDL and Verilog Templates and the Clocking Wizard.
Added Appendix A, Multi-Region Clocking.
05/31/2011 1.2 Added section on 7 Series FPGAs Clocking Differences from Previous FPGA
Generations.
Updated Figure 2-2. Clarified discussion in Clock-Capable Inputs section including
removing Table 1-1: Migration of devices in the same package with different top/bottom
alignments. Redrew Figure 2-4, Figure 2-16, Figure 2-18, and Figure 2-22.
Updated description of CLKOUT[0:6] in Table 3-5. Updated CLKFBSTOPPED
Feedback Clock Status, page 81. Clarified the MMCM/PLL relationship including
updating Figure 3-10. Added more information to the Phase Shift section, including
Equation 3-5.
Revised Figure A-6 and Figure A-7. Added Appendix B, Clocking Resources and
Connectivity Variations per Clock Region.
10/27/2011 1.3 Moved 7 Series FPGAs Clocking Differences from Previous FPGA Generations. Added
Clock Buffer Selection Considerations. Clarified description in Clock-Capable Inputs.
Added another note after Figure 2-22, page 51. Added the Stacked Silicon Interconnect
Clocking section.
Updated Figure 3-6, page 71. Clarified descriptions in Frequency Synthesis Using
Fractional Divide in the MMCM, page 71, Interpolated Fine Phase Shift in Fixed or
Dynamic Mode in the MMCM, page 73, Determine the Input Frequency, page 74,
CLKOUT[0:6] Output Clocks, page 80, and Reference Clock Switching, page 89.
Revised description of STARTUP_WAIT, page 83. Updated RST description in Table 3-5,
page 76. Updated CLKOUT[0]_DIVIDE_F(2) allowed values in Table 3-7, page 81.
Updated Clock Network Deskew, page 70 adding Figure 3-12, page 90.
Updated Table B-1 and added Table B-2.
02/16/2012 1.4 Replaced clocking backbone with clock backbone and clocking region with clock
region throughout.
Added Chapter 1, Clocking Overview, containing 7 Series FPGAs Clocking Differences
from Previous FPGA Generations from Chapter 2 and Summary of Clock Connectivity
from Appendix B. Updated Table 1-1. Removed XC7A8, XC7A15, XC7A30T, and
XC7A50T from Table 1-2.
Added Clock-Capable Inputs. Updated Global Clocking Resources, including BUFMR
Primitive. Updated Horizontal Clock BufferBUFH, BUFHCE. Updated paragraph
before Figure 2-27.
UG472 (v1.12) September 27, 2016 www.xilinx.com 7 Series FPGAs Clocking Resources User Guide
Date Version Revision
02/16/2012 1.4 In introductory paragraph of High-Performance Clocks, removed description of HPCs
(Contd) connecting to OSERDES and buffers. Replaced cross reference to UG429, 7 Series FPGAs
Migration Methodology Guide, with UG872, Large FPGA Methodology Guide. Updated
Stacked Silicon Interconnect Clocking. Replaced SRL with SLR in Figure 2-29. Added
Figure 2-31.
Removed hold block from Figure 3-2. Updated clock frequencies in Frequency Synthesis
Only Using Integer Divide. Replaced 64 with 63 in Equation 3-4. Updated Interpolated
Fine Phase Shift in Fixed or Dynamic Mode in the MMCM. Updated pin description of
LOCKED in Table 3-5. Updated LOCKED. In Table 3-7, updated type and allowed
values of CLKOUT[0]_DIVIDE_F and CLKFBOUT_MULT_F, and description of
STARTUP_WAIT and COMPENSATION. In Table 3-8, added STARTUP_WAIT and
updated description of COMPENSATION. Replaced GTX with GT in Figure 3-10.
Updated Dynamic Reconfiguration Port.
Added Appendix B, Clocking Resources and Connectivity Variations per Clock Region.
07/13/2012 1.5 Updated paragraph after Figure 1-4. Added bullet about spread spectrum support to
Key Differences from Virtex-6 FPGAs. Updated BUFG and BUFH pins, and removed
IBUFDS_GTE2.O/IBUFDS_GTE2.ODIV2 pin from Table 1-1. Updated Table 1-2.
Updated note 5 in Table 2-1. Added Figure 2-29.
Updated last sentence of Introduction. Updated DO[15:0] Dynamic Reconfiguration
Output Bus. Added SS_EN, SS_MODE, and SS_MOD_PERIOD to Table 3-7. Added
Spread-Spectrum Clock Generation.
10/02/2012 1.6 Added note to Table 1-1. Removed XC7A350T and XC7V1500T from Table 1-2.
Updated first paragraph of Single Clock Driving Multiple CMTs. Added notes 5 and 8 to
Table 2-1. Updated paragraph after Table 2-10.
Added Table 3-9 and timing constraint calculations for 25 MHz and 80 MHz input
clocks. In Table 3-10, changed Bandwidth value from N/A to Low, and removed
duplicate paragraph after table.
Removed XC7A350T from title of Figure B-4.
04/03/2013 1.7 Updated Figure 1-3, Figure B-2, and Figure B-3. Added BUFMR to Table 1-1. Updated
second paragraph in Dynamic Phase Shift Interface in the MMCM. Added note to
Table 2-7.
08/07/2013 1.8 Updated Table 1-2 and Table 3-7. Updated the figure titles for Figure B-2 and Figure B-3.
Updated Clock Buffer Placement.
04/08/2014 1.9 Updated Clock-Capable Inputs and Dynamic Phase Shift Interface in the MMCM.
Updated allowed values and the default value for CLKFBOUT_MULT in Table 3-8.
05/24/2014 1.10 Changed the value of minimum clock regions from six to four in Clocking Architecture
Overview. Added information to MGTREFCLK0 in Table 1-1. Added section on GTZ
Loopback Clock Buffer BUFG_LB (HT devices only) to Chapter 2. Changed
description of REF_JITTER1 and REF_JITTER2 in Table 3-7 and Table 3-8. Updated first
paragraph in Use Cases.
11/19/2014 1.11 Removed general interconnect from this bulleted list on page 47. Updated the figure
titles for Figure B-2 and Figure B-3.
03/04/2015 1.11.1 Updated Frequency Synthesis Using Fractional Divide in the MMCM, page 71 by
changing 0.125 degrees to 0.125.
06/12/2015 1.11.2 Fixed broken link in three references to 7 Series FPGA Data Sheets on page 71 and page 72.
09/27/2016 1.12 Added the Spartan-7 FPGAs and the Artix-7 (XC7A12T and XC7A25T) devices where
applicable including updating Appendix B. Updated the BUFR Alignment section.
Updated the Automotive Applications Disclaimer.
7 Series FPGAs Clocking Resources User Guide www.xilinx.com UG472 (v1.12) September 27, 2016
Table of Contents
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Preface: About This Guide

Guide Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 1: Clocking Overview

Clocking Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Clock Routing Resources Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
CMT Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Clock Buffers, Management, and Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7 Series FPGAs Clocking Differences from Previous FPGA Generations . . . . . 19
Key Differences from Virtex-6 FPGAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Key Differences from Spartan-6 FPGAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Summary of Clock Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Clocking Differences in 7 Series FPGAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 2: Clock Routing Resources

Clock Buffer Selection Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Clock-Capable Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Single Clock Driving a Single CMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Single Clock Driving Multiple CMTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Clock-Capable Input Pin Placement Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Global Clocking Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Clock Tree and Nets - GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Clock Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Global Clock Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Global Clock Buffer Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Additional Use Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Regional Clocking Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Clock-Capable I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
I/O Clock BufferBUFIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
BUFIO Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
BUFIO Use Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Regional Clock BufferBUFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
BUFR Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
BUFR Attributes and Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
BUFR Use Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Regional Clock Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Multi-Region Clock BufferBUFMR/BUFMRCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
BUFMR Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Horizontal Clock BufferBUFH, BUFHCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
GTZ Loopback Clock Buffer BUFG_LB (HT devices only). . . . . . . . . . . . . . . . . . . . 56
High-Performance Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
7 Series FPGAs Clocking Resources User Guide www.xilinx.com 5

Send Feedback
UG472 (v1.12) September 27, 2016
Clock Gating for Power Savings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Stacked Silicon Interconnect Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Placement of Clocking Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Clock Buffer Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Chapter 3: Clock Management Tile

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
MMCMs and PLLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
General Usage Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
MMCM and PLL Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
MMCME2_BASE and PLLE2_BASE Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
MMCME2_ADV and PLLE2_ADV Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Clock Network Deskew . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Frequency Synthesis Only Using Integer Divide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Frequency Synthesis Using Fractional Divide in the MMCM . . . . . . . . . . . . . . . . . . . . 71
Jitter Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
VCO Operating Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Minimum and Maximum Input Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Duty Cycle Programmability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Phase Shift . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Dynamic Phase Shift Interface in the MMCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
MMCM Counter Cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
MMCM/PLL Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Determine the Input Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Determine the M and D Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
MMCM Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
PLL Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
MMCM and PLL Port Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
MMCM Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
PLL Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
MMCM Clock Input Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Counter Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Detailed VCO and Output Counter Waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Reference Clock Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Missing Input Clock or Feedback Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
MMCM and PLL Use Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Clock Network Deskew . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
MMCM with Internal Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Zero Delay Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
CMT to CMT Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Spread-Spectrum Clock Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
MMCM Application Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Dynamic Reconfiguration Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
VHDL and Verilog Templates and the Clocking Wizard . . . . . . . . . . . . . . . . . . . . 100
Appendix A: Multi-Region Clocking

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Clocking Across Multiple Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
BUFMR Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
6 www.xilinx.com 7 Series FPGAs Clocking Resources User Guide

Send Feedback
UG472 (v1.12) September 27, 2016
Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Clock Alignment Across Clock Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Single Buffer per Clock Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Driving Multiple BUFIOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Driving Multiple BUFRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Multiple Buffers Per Clock Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Driving Multiple BUFRs (with Divide) and BUFIO . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Driving Multiple BUFRs (With and Without Divide) . . . . . . . . . . . . . . . . . . . . . . . . . . 107
BUFR Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Appendix B: Clocking Resources and Connectivity Variations per

Clock Region

Send Feedback
UG472 (v1.12) September 27, 2016
Send Feedback
UG472 (v1.12) September 27, 2016
Preface
About This Guide

Xilinx 7 series FPGAs include four FPGA families that are all designed for lowest power
to enable a common design to scale across families for optimal power, performance, and
cost. The Spartan-7 family is the lowest density with the lowest cost entry point into the
7 series portfolio. The Artix-7 family is optimized for highest performance-per-watt and
bandwidth-per-watt for cost-sensitive, high-volume applications. The Kintex-7 family is
an innovative class of FPGAs optimized for the best price-performance. The Virtex-7
family is optimized for highest system performance and capacity.
This 7 series FPGAs clocking resources user guide, part of an overall set of documentation
on the 7 series FPGAs, is available on the Xilinx website at
www.xilinx.com/documentation.
Guide Contents
This manual contains the following chapters:
Chapter 1, Clocking Overview
Chapter 2, Clock Routing Resources
Chapter 3, Clock Management Tile
Appendix A, Multi-Region Clocking
Appendix B, Clocking Resources and Connectivity Variations per Clock Region
Additional Resources
To find additional documentation, see the Xilinx website at:
www.xilinx.com/support/documentation/index
To search the Answer Database of silicon, software, and IP questions and answers, or to
create a technical support WebCase, see the Xilinx website at:
www.xilinx.com/support

Send Feedback
UG472 (v1.12) September 27, 2016
Preface: About This Guide

Send Feedback
UG472 (v1.12) September 27, 2016
Chapter 1
Clocking Overview
This chapter provides an overview of the 7 series FPGAs clocking, a comparison between
7 series FPGAs clocking and previous FPGA generations, and a summary of clocking
connectivity within the 7 series FPGAs. For detailed information on usage of 7 series
FPGAs clocking resources, see Chapter 2, Clock Routing Resources and Chapter 3, Clock
Management Tile.
Clocking Architecture Overview

The 7 series FPGAs clocking resources manage complex and simple clocking requirements
with dedicated global and regional I/O and clocking resources. The clock management
tiles (CMT) provide clock frequency synthesis, deskew, and jitter filtering functionality.
Non-clock resources, such as local routing, are not recommended when designing for clock
functions.
Global clock trees allow clocking of synchronous elements across the device.
I/O and regional clock trees allow clocking of up to three vertically adjacent clock
regions.
CMTs, each containing one mixed-mode clock manager (MMCM) and one
phase-locked loop (PLL), reside in the CMT column next to the I/O column.
For clocking purposes, each 7 series device is divided into clock regions.
The number of clock regions varies with device size, from one clock region in the
smallest device to 24 clock regions in the largest one.
A clock region includes all synchronous elements (for instance: CLB, I/O, serial
transceivers, DSP, block RAM, CMT) in an area spanning 50 CLBs and one I/O bank
(50 I/Os), with a horizontal clock row (HROW) in its center.
Each clock region spans 25 CLBs up and 25 CLBs down from the HROW, and
horizontally across each side of the device.
Clock Routing Resources Overview

Each I/O bank contains clock-capable input pins to bring user clocks onto the
7 series FPGA clock routing resources. In conjunction with dedicated clock buffers, the
clock-capable input bring user clocks on to:
Global clock lines in the same top/bottom half of the device
I/O clocks lines within the same I/O bank and vertically adjacent I/O banks
Regional clock lines within the same clock region and vertically adjacent clock regions
CMTs within the same clock region and, with limitations, vertically adjacent clock
regions

Send Feedback
UG472 (v1.12) September 27, 2016
Each 7 series monolithic device has 32 global clock lines that can clock and provide control
signals to all sequential resources in the whole device. Global clock buffers (BUFGCTRL,
simplified as BUFG throughout this user guide) drive the global clock lines and must be
used to access global clock lines. Each clock region can support up to 12 of these global
clock lines using the 12 horizontal clock lines in the clock region.
The global clock buffers:
Can be used as a clock enable circuit to enable or disable clocks that span multiple
clock regions
Can be used as a glitch-free multiplexer to:
select between two clock sources
switch away from a failed clock source
Are often driven by a CMT to:
eliminate the clock distribution delay
adjust clock delay relative to another clock
The horizontal clock buffer (BUFH/BUFHCE) allows access to the global clock lines in a
single clock region through the horizontal clock row. It can also be used as a clock enable
circuit (BUFHCE) to independently enable or disable clocks that span a single clock region.
Each clock region can support up to 12 clocks using the 12 horizontal clock lines in each
clock region.
Each 7 series FPGA has regional and I/O clock trees that can clock all sequential resources
in one clock region. Each device also has multi-clock region buffers (BUFMR) that allow
regional and I/O clocks to span up to three vertically adjacent clock regions.
The I/O clock buffer (BUFIO) drives the I/O clock tree, providing access to clock all
sequential I/O resources in the same I/O bank.
The regional clock buffer (BUFR) drives regional clock trees that drive all clock
destinations in the same clock region and can be programmed to divide the incoming
clock rate.
In conjunction with the programmable serializer/deserializer in the IOB (refer to the
Advanced SelectIO Logic Resources chapter in UG471, 7 Series FPGAs SelectIO Resources
User Guide), the BUFIO and BUFR clock buffers allow source-synchronous systems to
cross clock domains without using additional logic resources.
The regional and I/O clock trees in adjacent clock regions and I/O banks can be
driven using the multi-clock region buffer (BUFMR) when used with the associated
BUFR or BUFIO.
Up to four unique I/O clocks and four unique regional clocks can be supported in one
clock region or I/O bank.
High-performance clock routing connects certain outputs of the CMT to the I/O on a very
low jitter, minimal duty-cycle distorted direct path.
Chapter 2, Clock Routing Resources, has further details on global, regional, and I/O
clocks. It also describes which clock routing resources to use for various applications.
CMT Overview
Each 7 series FPGA has up to 24 CMTs, each consisting of one MMCM and one PLL. The
MMCMs and PLLs serve as frequency synthesizers for a wide range of frequencies, serve
as a jitter filters for either external or internal clocks, and deskew clocks. The PLL contains

Send Feedback
UG472 (v1.12) September 27, 2016
a subset of the MMCM functions. The 7 series FPGA clock input connectivity allows
multiple resources to provide the reference clocks to the MMCM and PLL.
7 series FPGAs MMCMs have infinite fine phase-shift capability in either direction and can
be used in dynamic phase-shift mode. MMCMs also have a fractional counter in either the
feedback path or in one output path, enabling further granularity of frequency synthesis
capabilities.
The LogiCORE IP clocking wizard is available to assist in utilizing MMCMs and PLLs to
create clock networks in 7 series FPGA designs. The GUI interface is used to collect clock
network parameters. The clocking wizard chooses the appropriate CMT resource and
optimally configures the CMT resource and associated clock routing resources.
Chapter 3, Clock Management Tile, includes details on the CMT block features and
connectivity.
Clock Buffers, Management, and Routing

The figures in this section provide a visual and layered explanation of the 7 series FPGAs
clock architecture.
Figure 1-1 is a high-level view of the 7 series FPGAs clocking architecture. The vertical
clocking center line (the clock backbone) divides the device into adjacent left and right
regions while the horizontal center line divides the device into its top and bottom sides.
The resources in the clock backbone are mirrored to both sides of the horizontally adjacent
regions, thus extending certain clock resources into the horizontal adjacent region. The top
and bottom division separates two sets of global clock buffers (BUFGs) and imposes some
limitations on how they can be connected. However, BUFGs do not belong to a clock
region and can reach any clocking point on the device. All horizontal clock resources are
contained in the center of the clock region horizontal clock row (HROW), and vertical,
non-regional clock resources are contained in either the clock backbone or CMT backbone.

Send Feedback
UG472 (v1.12) September 27, 2016
X-Ref Target - Figure 1-1
Clocking
Center
Clock Region Clock Region
Clock Horizontal Clock

Region Row (HROW)
BUFG 16 Clock
Horizontal Region
Center Detailed
View
16

(HROW)
Region Row (HROW)

Region Row (HROW)
CMT Column I/O Column

CMT Backbone CMT Backbone
I/O Column Clock Backbone CMT Column GT Column
UG472_c1_30_020712
Figure 1-1: 7 Series FPGA High-Level Clock Architecture View
A clock region always contains 50 CLBs per column, ten 36K block RAMs per column
(unless five 36K blocks are replaced by an integrated block for PCI Express), 20 DSP slices
per column, and 12 BUFHs. A clock region contains, if applicable, one CMT (PLL/
MMCM), one bank of 50 I/Os, one GT quad consisting of four serial transceivers, and half
a column for PCIe in a block RAM column.

Send Feedback
UG472 (v1.12) September 27, 2016
Figure 1-2 is a high-level overview of clock resources available in a clock region and their
fundamental connectivity. The global clock buffer can drive into every region through the
HROW even if not physically located there. The horizontal clock buffers (BUFH) drive
through the HROW to every clocking point in the region. BUFGs and BUFHs share routing
tracks in the HROW. The I/O buffers (BUFIO) and regional clock buffers (BUFR) are
located inside the I/O banks. The BUFIO only drives I/O clocking resources while the
BUFR drives I/O resources and logic resources. The BUFMR enables multi-region chaining
of BUFIOs and BUFRs. The clock-capable inputs connect external clocks to clocking
resources on the device. Certain resources can connect to regions above and below through
the CMT backbone.
Clock
Backbone
PLL I/O
Bank
Fabric Fabric
CC
CMT
BUFIO
Column
BUFMR
HROW GT
Quad
BUFG
BUFH
BUFR
CC
MMCM
CMT
Backbone
UG472_c1_31_020712
Figure 1-2: Basic View of Clock Region

Send Feedback
UG472 (v1.12) September 27, 2016
Figure 1-3 shows a more detailed view of clocking in a single clock region on the right edge
of the device.
To Bank Above
Global Clocking CMT Clocking

Backbone 32 Backbone 2
CMT I/O Bank

PLL X0Yn in
Same Region 4
4 1
SRCC Pin Pair
1
MRCC Pin Pair
CE
CLR
2
7 Clock
3
Region
HROW
14 50 CLBs
3
Interconnect 12 High
CE 4
12
1
Interconnect BUFHs MRCC Pin Pair
4 1
CE SRCC Pin Pair
MMCM X0Yn
4
in Same Region
BUFGs
4
Two BUFMRs (MRCC pins only)
Four BUFRs
Four BUFIOs
To Bank Below
UG472_c1_32_011713
Figure 1-3: Single Clock Region (Right Side of the Device)

Send Feedback
UG472 (v1.12) September 27, 2016
Figure 1-4 shows a more detailed diagram of the global BUFG and regional BUFH/CMT/
CC pin connectivity as well as the number of resources available in a region (a right side
region is shown here).
CMT
Backbone
From To other
other BUFGs
BUFGs CMT I/O
Column Bank
32
Interconnect Fabric Fabric
32 CE PLL
Interconnect CC
Left <0-3>
CC
Region
BUFG 7 GT
4
Quad
4
12
10
BUFH HROW
14
Left 12
CC
Region
MMCM CC
Interconnect
CE BUFR
Interconnect <0-3>
32
Clock
Backbone
UG472_c1_33_020712
Figure 1-4: BUFG/BUFH/CMT Clock Region Detail
Any of the four clock-capable input pins can drive the PLL/MMCM in the CMT and the
BUFH. The BUFG is shown as present in the region, but can be located physically
somewhere else in the clock backbone. BUFG and BUFH share 12 routing tracks in the
HROW and can drive all clocking points in the region. BUFGs can also drive BUFHs (not
shown in Figure 1-4). This allows for individual clock enables (CE) on an otherwise global
clock distribution. A GT quad has ten dedicated tracks to drive the CMT and clock buffers
in the clock backbone. The BUFRs located in the I/O bank have four tracks driving
clocking points in the logic, CMT, and BUFG. CMTs can, with limitations, drive other
CMTs in the adjacent regions using the CMT backbone. Similarly, clock-capable pins can
drive, with the same limitations, CMTs in adjacent regions. Clock-capable pins can drive
BUFGs anywhere in the same top/bottom side of the device. There are four tracks in the
CMT backbone to support connectivity between vertical regions.
Clock sources from one region can drive clock buffer resources in its own region as well as
in a horizontally adjacent region. CMTs, clock-capable pins, and serial transceivers can
drive clocks into the horizontal adjacent region via the BUFH and also connect to the
BUFGs in the same top/bottom side of the device.

Send Feedback
UG472 (v1.12) September 27, 2016
Logic interconnects drive the CE pins of BUFG and BUFH. Logic interconnects can also
drive clocks into the same buffers, but care must be taken because the timing is not
predictable.
Figure 1-5 shows a more detailed diagram of the I/O clocking resources and connectivity.
I/O
4 4 4
2 Bank
Fabric Fabric
Clock CMT BUFR BUFIO
Backbone Column
SRCC
PLL Pair
MRCC
Pair
BUFMR GT
4
BUFMR
Quad
BUFG HROW
BUFH
<0>
4
<1> MRCC
<2> Pair
<3>
SRCC
Pair
BUFR BUFIO
MMCM
CMT
Backbone
UG472_c1_34_020712
Figure 1-5: BUFR/BUFMR/BUFIO Clock Region Detail
Each I/O bank contains four BUFIOs and four BUFRs. Each of these clock buffers can be
driven by a specific clock-capable input clock pin pair or can be driven directly by a
specific output clock of the MMCM. Two of the clock-capable input pin pairs, called
MRCCs, support a multi-region clocking scheme. An MRCC pin pair can drive a specific
BUFMR, which in turn can drive BUFIOs and BUFRs in the same and adjacent regions
facilitating multi-region/bank interfaces. Similarly, a GT quad can also drive the BUFMRs.
The MMCM<3:0> outputs have a dedicated high-performance differential path to the
BUFRs and BUFIOs. This feature is also referred to as high-performance clocks (HPC).
Although all 7 series devices have the same fundamental architecture, there are some
architectural differences between the families and devices within families. Every 7 series
FPGA has a minimum of one complete I/O column on the left edge of the device. A GT can
be any one of the serial transceivers supported by the 7 series FPGAs (GTP, GTX, or GTH).
Devices with GTs either have a mixed column of GTs and I/Os to the right edge of the
device (some Kintex-7 devices and some Artix-7 devices) or have a complete column of
GTs to the right edge (some Kintex-7 devices and some Virtex-7 devices) and a complete
I/O column on the right side of the device. Other Virtex-7 devices have complete GT

Send Feedback
UG472 (v1.12) September 27, 2016
7 Series FPGAs Clocking Differences from Previous FPGA Generations
columns on the left and right edges with a complete I/O column in the left and right sides.
The Artix-7 200T device has GTP transceivers on the top and bottom next to the clocking
column.
Therefore, not all clock regions in 7 series devices contain all of the blocks shown in the
previous figures. For a block-level architectural view of the 7 series devices, see the Die
Level Bank Numbering Overview section in UG475, 7 Series FPGA Packaging and Pinout
Specification. Appendix B, Clocking Resources and Connectivity Variations per Clock
Region includes detailed figures showing clocking resources and connectivity for the clock
region variations.
7 Series FPGAs Clocking Differences from Previous FPGA

Generations
The 7 series FPGAs clocking has a similar structure to Virtex-6 FPGAs and supports many
of the same features. However, there are some architectural differences and modifications
to the various clocking elements and their functionality. When compared with
Spartan-6 FPGAs, there are some significant changes in both architecture and functionality.
Some Spartan-6 FPGA clock primitives are no longer available and are replaced by more
powerful and simpler structures.
Key Differences from Virtex-6 FPGAs

The 7 series FPGAs basic BUFIO clocking functions have not changed with the
exception that the BUFIO now only spans a single bank. Direct clocking of adjacent
banks is replaced by a new clock buffer. There are now four BUFIOs per bank. Similar
to the BUFIO evolution, the basic purpose of the BUFR has not changed. However,
now the BUFR only directly spans a single clock region. There are now four BUFRs
and four regional clocks (tracks) per region.
The 7 series FPGAs introduced a new buffer type: BUFMR/BUFMRCE. The BUFMR/
BUFMRCEs drive BUFIOs and/or BUFRs in the same and vertically adjacent regions.
They also provide the same multi-clock region/multi-bank clock routing available in
Virtex-6 FPGAs which support the same three clock regions/banks capability.
BUFMRCE has a selectable synchronous or asynchronous switching feature.
The global clock (GC) input pins in the Virtex-6 family are no longer supported by the
7 series FPGAs. Four clock-capable clock input pin/pairs per bank replace the GCs.
The connectivity of the clock-capable input pins has been enhanced to support much
of the previous GC capabilities.
The global clock multiplexer BUFGMUX has added an attribute, CLK_SEL_TYPE, for
allowing either synchronous or asynchronous clock switching of the two input clocks
(previously only available through the IGNORE port).
The BUFHCE has an enhanced clock enable to allow for either a synchronous or
asynchronous enable of the input clock.
The CMT now contains one MMCM and one PLL (a subset of the MMCM), instead of
two MMCMs, and dedicated memory interface logic, which is reserved. The CMT
column is located adjacent to the SelectIO columns/banks within the CMT and has
dedicated access to the I/Os for high performance. The global clock buffers are still
located in the vertical center of the device between I/O columns driven by the CMTs.
Direct cascading within the CMT is no longer supported. Cascading to adjacent CMTs
directly is possible but limited due to limited resources. Cascading to other CMTs

Send Feedback
UG472 (v1.12) September 27, 2016
beyond the adjacent CMTs results in a phase offset between the source and
destination MMCMs/PLLs and requires a special attribute setting.
Fractional dividers no longer share output counters. This frees up those counters for
other uses. Fractional counters have added a static phase-shift capability.
The CLOCK_HOLD feature is no longer available.
MMCMs support spread spectrum.
Key Differences from Spartan-6 FPGAs

Some of the Spartan-6 FPGA clocking circuit topologies, functions, and blocks that are
unique to the Spartan-6 architecture are not supported and have been replaced by the
7 series FPGAs clocking features. Features and functions such as DCM_SP,
DCM_CLKGEN, BUFIO2, BUFIO2_2CLK, BUFIO2FB, BUFPLL, and BUFPLL_MCB
are not directly supported in 7 series devices.
The PLL is a subset of the MMCM with the same performance (except minimum
CLKIN/PFD and minimum/maximum VCO frequencies), some connectivity
limitations, and some reduced functionality. When compared to previous Spartan
FPGA PLLs, the 7 series FPGAs PLLs add power down, input clock switching, and
cascading to adjacent CMTs. The PLLs do not have a direct connection to the BUFIO
or BUFR.
In the 7 series FPGAs, there is no direct replacement for the BUFIO2 and
BUFIO2_2CLK primitives. Use the BUFIO and BUFR instead with the recommended
connections to drive the ILOGIC and OLOGIC.
The Spartan-6 FPGA BUFIO2 dedicated input routing from GCLKs to the CMT and
global clock buffers are no longer supported. To migrate to the 7 series FPGAs, use the
dedicated input routing from the CCIO pins.
There is no direct equivalent in the 7 series FPGAs to the Spartan-6 FPGA BUFPLL. To
migrate, use the BUFIO and BUFR with the recommended connections to the ILOGIC
and OLOGIC. The high-performance clock routing from MMCME2 CLKOUT[0:3]
replaces the dedicated routing to the BUFPLL. The ISERDES and OSERDES circuitry
is based on the Virtex-6 architecture. See UG471: 7 Series FPGAs SelectIO Resources User
Guide.
In the 7 series FPGAs, the BUFPLL_MCB primitive is no longer required. DDR
memory interfaces have a different (soft) implementation in the 7 series FPGAs.
Consult the UG586: Memory Interface Solutions User Guide.
In the 7 series FPGAs, the BUFIO2FB primitive is no longer required. For MMCM and
PLL feedback connections the CLKFBIN can be directly connected to global clock
buffers, input pins, or CLKFBOUT depending on the feedback used.
Spartan-6 FPGAs only supported BUFH. The 7 series FPGAs BUFHCE primitive adds
the ability to disable the clock for potential power savings in the clock region driven
by this resource.
The 7 series FPGAs new buffers, BUFMR/BUFMRCE, drive BUFIOs and/or BUFRs in
the same and vertically adjacent clock regions. When used with a BUFIO or BUFR,
BUFMR/BUFMRCE allow MRCC inputs to access BUFIO and BUFR in adjacent clock
regions. BUFMRCE has a selectable synchronous or asynchronous switching feature.
A new primitive for Spartan-6 FPGA design migration is the BUFR. When used in
conjunction with BUFIO the BUFRs functionality replaces the BUFIO2,
BUFIO2_2CLK, and BUFPLL capabilities. There are four BUFRs in each clock region.

Send Feedback
UG472 (v1.12) September 27, 2016
7 Series FPGAs Clocking Differences from Previous FPGA Generations
Another new primitive for Spartan-6 FPGA design migration is the BUFIO. When
used with the BUFR, the BUFIO functionality replaces the BUFIO2, BUFIO2_2CLK,
and BUFPLL capabilities. There are four BUFIOs per bank.
Instead of two DCMs and one PLL in the Spartan-6 architecture, the 7 series FPGAs
use a CMT that contains one MMCM, one PLL, and dedicated memory interface logic
which is reserved for Xilinx use at this time. DCMs and their associated capabilities
are now supported with these functions. The CMTs are located in a separate column
adjacent to the SelectIO columns and have dedicated access to the I/O. DCM_SP and
DCM_CLKGEN are no longer available and their functionality is now supported in
the MMCMs and PLLs.
Global clock (GCLK) inputs are no longer supported in the 7 series FPGAs. Four
clock-capable input pins are now available in every bank that support much of the
Spartan-6 FPGA GCLK pin capabilities.
To Spartan-6 FPGA designers, the MMCM is a new functional block. The MMCM
adds fractional divide, fine phase shifting, dynamic phase shifting, inverted clock
outputs, CLKOUT6 to CLKOUT4 cascading, and some other features. The direct
routing connection to the BUFPLL is replaced by the HPC connection from the
MMCMs to the BUFIO/BUFR using CLKOUT[0:3]. A more extensive DRP is also
available.
Using the PLL is no longer the recommended CMT function for general-purpose
high-speed I/O clocking. The PLL does not have a direct connection to the BUFIO or
BUFR. CLKOUT0 feedback is no longer supported. Use the MMCM for high-speed
I/O interfaces. Cascade connections use limited CMT backbone resources. There is
also a new power down mode. Input clock switching is fully supported. Operating
ranges are different between the Spartan-6 FPGAs and the 7 series FPGAs. The DRP
functionality is still available. The DRP functional locations and addresses have
changed.
The Spartan-6 FPGAs DCM_SP is no longer supported. To migrate to the 7 series
FPGAs, use the MMCM and PLL.
The Spartan-6 FPGAs DCM_CLKGEN is not directly supported in the 7 series FPGAs.
Use MMCM or PLL with low bandwidth for input jitter filtering. Dynamic
reprogramming of the M/D values can also be accomplished using the DRP reference
design for the MMCM or PLL.

Send Feedback
UG472 (v1.12) September 27, 2016
Summary of Clock Connectivity

Table 1-1 summarizes the 7 series FPGAs clock connectivity.
Table 1-1: Summary of Clock Connectivity

Clocking Function or Pin Directly Driven By Used to Directly Drive
MRCCs that are located in the same clock region
and on the same left/right side of the device
drive:
Four BUFIOs
Four BUFRs
Multi-region clock-capable Two BUFMRs
I/O (MRCC) One CMT (one MMCM and one PLL)
External Clock
There are two pin/pairs in CMTs above and below (using limited CMT
each bank. backbone resources) (1).
MRCCs within the same half top/bottom drive:
16 BUFGs
MRCCs within the same horizontally adjacent
clock regions drive:
BUFHs
SRCCs that are located in the same clock region
and on the same left/right side of the device
drive:
Four BUFIOs
Four BUFRs
Single-region clock-capable One CMT (one MMCM and one PLL)
I/O (SRCC)
External Clock CMTs above and below (using limited CMT
There are two pin/pairs in backbone resources) (1).
each bank.
SRCCs within the same half top/bottom drive:
16 BUFGs
SRCCs within the same horizontally adjacent
clock region drive:
BUFHs
Within the same clock region, When used within the same clock region, BUFIOs
BUFIOs are driven by: drive:
MRCCs (dedicated 1:1) ILOGIC.clk
SRCCs (dedicated 1:1) ILOGIC.clkb
BUFIO MMCM.CLKOUT0 OLOGIC.clk
MMCM.CLKOUT3 OLOGIC.clkb
CLKFBOUT OLOGIC.oclk
BUFMRs in the same clock region OLOGIC.oclkb
and clock regions below and
above

Send Feedback
UG472 (v1.12) September 27, 2016
Table 1-1: Summary of Clock Connectivity (Contd)

Within the same clock region, BUFRs When used within the same clock region, BUFRs
are driven by: drive:
MRCC CMT
SRCC Any clocking point in the same clock region
MMCM.CLKOUT0- the BUFG can drive
BUFR
MMCM.CLKOUT3 When used within the same half top/bottom,
CLKFBOUT BUFRs drive:
BUFMR from the clock region 16 BUFGs (not recommended)
above and below
General interconnect
Within the same clock region, When used within the same clock region and the
BUFMRs are driven by: clock regions above and below, BUFMRs drive:
MRCCs (dedicated 1:1) BUFIOs
BUFMR GT clock outputs listed in this BUFRs
table (see GT Transceiver Clocks)
Interconnect
(not recommended)
Within the same top/bottom half, CMT
BUFGs are driven by: GT clock outputs listed in this table
SRCCs (see GT Transceiver Clocks:)
MRCCs Adjacent BUFGs in same top/bottom half
CMTs Any clocking point in the fabric and I/O
GT clock outputs listed in this CLB control signals
BUFG
table (see GT Transceiver Clocks) BUFH
BUFRs (not recommended)
Interconnect
(not recommended)
Adjacent BUFG in the same top/
bottom half
Within the same clock region and the When used within the same clock region, BUFHs
horizontally adjacent clock region, drive:
BUFHs are driven by: CMT
SRCC GT clock outputs listed in this table
MRCC (see GT Transceiver Clocks:)
BUFH CMT Any clocking point in the same clock region
BUFG the BUFG can drive
GT clock outputs listed in this
table (see GT Transceiver Clocks)
Interconnect
(not recommended)
GT Transceiver Clocks Any BUFG N/A
RXUSRCLK Within the same clock region, GTs are
RXUSRCLK2 driven by:
TXUSRCLK BUFH
TXUSRCLK2

Send Feedback
UG472 (v1.12) September 27, 2016
Table 1-1: Summary of Clock Connectivity (Contd)

N/A BUFG within the same half top/bottom
When used within the same clock region, GTs can
GT Transceiver Clocks: drive:
RXOUTCLK CMT
TXOUTCLK BUFMR
BUFH and BUFH in the horizontally adjacent
clock region
External GT reference clock GT reference clock
MGTREFCLK0/1P
BUFG within the same half top/bottom
MGT positive differential
reference clock pins When used within the same clock region,
external GT reference clock pins can drive:
CMT
MGTREFCLK0/1N
BUFMR
MGT negative differential
reference clock pins BUFH and BUFH in the horizontally adjacent
clock region
BUFG Any BUFG in same top/bottom half
SRCC (same and adjacent clock When used within the same clock region, CMTs
regions) can drive:
MRCC (same and adjacent clock BUFIO (MMCM)
regions) BUFR (MMCM)
CMT (1)
GTs in the same clock region BUFH and BUFH in the horizontally adjacent
A BUFR within the same clock clock region
region, and the clock region above MMCM/PLL (with phase offset if not
or below using a BUFMR adjacent)
MMCM/PLL.CLKOUT0-3
MRCC/SRCC N/A
IDELAYCNTRL.CLK BUFG
BUFH
CCLK pin Configuration logic Configuration logic
EMCCLK pin N/A Configuration logic
TCK pin N/A JTAG configuration logic and Boundary Scan
Notes:
1. Certain restrictions apply. See Single Clock Driving Multiple CMTs, page 29.

Send Feedback
UG472 (v1.12) September 27, 2016
Clocking Differences in 7 Series FPGAs

Each of the 7 series FPGA families have some unique connectivity requirements. Table 1-2
lists the connectivity limitations described in Table 1-1 by device family. For a
comprehensive graphical representation of the GT, CMT, and I/O locations and
alignments, see the Die Level Bank Numbering Overview section in UG475, 7 Series FPGA
Packaging and Pinout Specification.
Table 1-2: Clocking Connectivity Differences by 7 Series FPGAs

Family Exceptions
Spartan-7 FPGAs: There are no connectivity exceptions.
All devices
Artix-7 FPGAs: There are no direct connections from the GTP transceivers to the
CMTs and BUFMRs. When connecting from the GTP transceivers to
All devices a CMT, a BUFH or BUFG is required.
Kintex-7 FPGAs: There are no direct connections from the GTX transceivers to the
CMTs and BUFMRs. When connecting from the GTX transceivers to
All devices a CMT, a BUFH or BUFG is required.
There are no connectivity exceptions. See Stacked Silicon
All Virtex-7 T and XT
Interconnect Clocking in Chapter 2 for clocking guidelines when
FPGAs
designing with the XC7V2000T and XC7VX1140T devices.
GTZ transceivers can only connect to the interposer clock backbone
to connect to SLRs. Thus, they can only drive global clock networks
All Virtex-7 HT FPGAs
(BUFG routing tracks) and BUFHs and can only be driven by
BUFGs. See Stacked Silicon Interconnect Clocking in Chapter 2.

Send Feedback
UG472 (v1.12) September 27, 2016

Send Feedback
UG472 (v1.12) September 27, 2016
Chapter 2
Clock Routing Resources

7 series FPGAs have several clock routing resources to support various clocking schemes
and requirements, including high fanout, short propagation delay, and extremely low
skew. To best utilize the clock routing resources, you must understand how to get user
clocks from the PCB to the FPGA, decide which clock routing resources are optimal, and
then access those clock routing resources by utilizing the appropriate I/O and clock
buffers.
This chapter covers:
Clock Buffer Selection Considerations
Clock-Capable Inputs
Global Clocking Resources
Regional Clocking Resources
High-Performance Clocks
Clock Buffer Selection Considerations

7 series FPGAs have a rich set of clocking resources. The various buffer types, clock input
pins, and clocking connectivity satisfy many different application requirements. Selecting
the proper clocking resources can improve routeability, performance, and general FPGA
resource utilization. For some applications and designs, floor planning or other types of
manual guidance can also greatly impact the implementation.
BUFGCTRL (most often used as a BUFG) is the most commonly used clock routing
resource. These truly global clocks can connect to every clocking point on the device.
However, in some cases it is more advantageous to use alternate clocking buffers for either
performance, functional, or clocking resource availability reasons. BUFGs are best
deployed when:
Designs or portions of a design have global reach across large areas of the device and
localization of functions is not possible.
Hardware functional blocks such as block RAM, DSP, or integrated IP that spans
many clock regions, are cascaded, or need connections to CLBs that are not nearby.
By switching clocks synchronous (glitch free) or asynchronous, applications are able
to switch away from a stopped clock or select a clock with a different frequency (for
example, power reduction).
The clock enable (CE) functionality can be used to reduce power during
non-operating periods. However, in most cases, the CE capability should not be used
to simulate a true CE logic function at the clocking elements due to timing (CE delay)
limitations.

Send Feedback
UG472 (v1.12) September 27, 2016
The CE function can be used to synchronize initialized clocking elements after device
startup.
The main purpose of the BUFR and BUFIO combination is to support source-synchronous
interfaces. When an interface is placed into a single region, the BUFIO clocks the
high-speed side of the SelectIOs and the BUFR clocks the deserialized/serialized side at a
lower speed into the FPGA logic providing the clock domain transfer function. For
interfaces that require more logic and/or I/Os than are available in a single clock region/
bank, the BUFMR (BUFMRCE) is used to expand clock domain transfer functionality into
the clock regions above and below. Certain types of applications that require a divided
clock not related to the source-synchronous I/O use case can use a BUFR as a simple clock
divider when an MMCM/PLL cannot be used or is not available for the frequency divide
function. In this case, particular attention must be paid to the timing and skew because this
is not the primary purpose of the BUFR. For more information on clocking SelectIO
resources, consult UG471, 7 Series FPGAs SelectIO Resources User Guide.
The horizontal clock buffer BUFH (BUFHCE) is strictly a regional resource and cannot
span clock regions above or below. Unlike BUFR, BUFH does not have the ability to divide
the clock.
BUFHs are similar to a global clocking resource only on a regional basis spanning two
horizontal regions.
BUFHs have the ability to serve as a feedback to the MMCM/PLL and the clock
insertion delay can be compensated for.
BUFHs are the preferred clocking resource when an interface or cloud of logic can be
localized to one clock region or two horizontally adjacent clock regions.
The BUFH also has a clock enable pin (BUFHCE) that can be used to reduce dynamic
power consumption when either the logic or an interface and its associated logic are
not active.
The clock enable feature can provide a gated clock on a clock cycle-to-cycle basis.
Similar to the global clock tree, the BUFH can also connect to non-clocking resources
in the CLB (enable/reset) but with better skew characteristics.
BUFH can also be used for the synchronous startup of clocking elements in a clock
region.
For stacked silicon interconnect (SSI) device limitations with respect to clocking resource
selection, see Stacked Silicon Interconnect Clocking.
External user clocks must be brought into the FPGA on differential clock pin pairs called
clock-capable (CC) inputs. Clock-capable inputs provide dedicated, high-speed access to
the internal global and regional clock resources. Clock-capable inputs use dedicated
routing and must be used for clock inputs to guarantee timing of various clocking features.
General-purpose I/O with local interconnects should not be used for clock signals.
Each I/O bank is located in a single clock region and includes 50 I/O pins. Of the 50 I/O
pins in each I/O bank in every I/O column, there are four clock-capable input pin pairs (a
total of eight pins). Each clock-capable input:
Can be connected to a differential or single-ended clock on the PCB
Can be configured for any I/O standard, including differential I/O standards
Has a P-side (master), and an N-side (slave)

Send Feedback
UG472 (v1.12) September 27, 2016
Single-ended clock inputs must be assigned to the P (master) side of the clock-capable
input pin pair.
If a single-ended clock is connected to the P-side of a differential clock pin pair, the N-side
cannot be used as another single-ended clock pinit can only be used as a user I/O. For
pin naming conventions, refer to UG475, 7 Series FPGA Packaging and Pinout Specification.
Clock-capable inputs are organized as 2 MRCC and 2 SRCC pairs in each I/O bank. SRCCs
access a single clock region and the global clock tree, as well as other CMTs above and
below in the same column. SRCCs can drive:
Regional clocks lines (BUFR, BUFH, BUFIO) within the same clock region
CMTs in the same clock region and adjacent clock regions.
Global clocks lines (BUFG) in the same top/bottom half of the device. Refer to 7 Series
FPGA Packaging and Pinout Specification for BUFG and I/O bank alignments.
MRCCs can access multiple clock regions and the global clock tree. MRCCs function the
same as SRCCs and can additionally drive multi-clock region buffers (BUFMR) to access
up to three clock regions.
Clock-capable inputs can be used as regular I/O if not used as clocks. When used as
regular I/O, clock-capable input pins can be configured as any single-ended or differential
I/O standard.
Clock-capable inputs can connect to the CMT in the same clock region, and the CMT in the
clock regions above and below with some restrictions.
Single Clock Driving a Single CMT

When a clock input drives a single CMT, the clock-capable input and CMT (MMCM/PLL)
must be in the same clock region.
Single Clock Driving Multiple CMTs

A single clock input can drive other CMTs in the same column. In this case, an MMCM/
PLL must be placed in the same clock region as the clock-capable input. It is more optimal
to place additional CMTs into adjacent regions, but CMTs further than one CMT away in
the same column can be driven as well. The resources used in the CMTs must be identical
for this configuration to be automatically placed without a CLOCK_DEDICATED_ROUTE
constraint. If a mixture of MMCMs/PLLs is required, they should be placed in the same
CMT first.
If it is necessary to drive a CMT from a clock-capable input that is not in the same clock
region, and there is no MMCM/PLL in the same clock region as the clock-capable input,
the attribute CLOCK_DEDICATED_ROUTE = BACKBONE must be set. In this case, the
MMCM or PLL do not properly align outputs to the input clock.
There are limited dedicated resources to drive CMTs in the same column. Some Xilinx IP
uses these resources, thus making them unavailable for additional design uses and
resulting in unroutable designs. If the dedicated routes to the other clock regions are not
available, setting CLOCK_DEDICATED_ROUTE to FALSE allows the local interconnect
logic to be used, although it results in longer, uncompensated delays.
Clock-Capable Input Pin Placement Rules

The two main considerations when manually choosing clock-capable input pins in
advance of creating the initial design are:

Send Feedback
UG472 (v1.12) September 27, 2016
Ensure that the clock-capable input can connect to the desired clock resource. The
placement rules to ensure connectivity are shown in Table 2-1.
Ensure that the desired clock resources are available and not already used by another
portion of the design. The best way to ensure that both external clocks coming in
through clock-capable inputs and internally generated clocks coming from IP do not
run into conflicts accessing the internal clock networks is to build an initial design
containing the desired clock networks and IP, and run it through the implementation
tools. This significantly increases checking and confidence that the pinout will not
need to change due to clocking reasons.
The placement rules shown in Table 2-1 should be followed to ensure that the
clock-capable input pin selection has access to the desired internal clock network. Each
I/O bank resides in a single clock region.
Note: Avoid costly board respins and poor clock timing by ensuring that clock-capable input pinout
placement is chosen properly.
Table 2-1: Clock-Capable Input Placement Rules
Valid
Clock Inputs To Resource Utilization and Placement Rules (1) (2) (3) Clock-Capable
Input Pin
I/Os and/or sequential elements Clock-capable input > BUFG > global clock tree SRCC or MRCC
throughout the device (4) The clock-capable input must be placed in the same top or
bottom half as the BUFG.
There are 16 BUFGs in the top half and 16 BUFGs in the
bottom half of each device.
Each clock region can have up to 12 unique global clocks
and use the horizontal clock lines.
I/O and/or sequential elements Clock-capable input > BUFH > horizontal clock line SRCC or MRCC
within a single clock region using Clock-capable inputs must be placed in the same clock
BUFH (4) region or the horizontally adjacent clock region as the
BUFH (5).
There are 12 BUFHs and 12 horizontal clock lines in each
clock region.
I/Os and/or sequential elements Throughout the device: SRCC or MRCC
using CMTs (6) Clock-capable input > CMT > BUFG > global clock tree
In a single clock region or adjacent clock regions:
Clock-capable input > CMT > BUFR/BUFH > regional clock
tree/horizontal clock line
Input routing from clock-capable inputs to CMT:
A CMT must be placed in the same clock region as the
clock-capable input.
CMTs can also be placed in the clock region immediately
above or below when multiple CMTs are needed (5).
There is one CMT per clock region.

Send Feedback
UG472 (v1.12) September 27, 2016
Table 2-1: Clock-Capable Input Placement Rules (Contd)

Valid
Input Pin
I/Os and/or sequential elements Clock-capable input > BUFR > regional clock tree: SRCC or MRCC
in a single clock region using The clock-capable input must be placed in the same clock
BUFR region as the BUFR, I/Os, and sequentially clocked
elements.
A specific clock-capable pin pair connects to a specific BUFR
and BUFIO. Therefore it is not recommended to manually
LOC the BUFR/BUFIO.
There are four clock-capable inputs and four BUFRs per
clock region.
I/Os and/or sequential elements Clock-capable input > BUFMR > BUFR > regional clock tree (8) MRCC only
in up to three adjacent clock I/Os and other sequential elements that the BUFRs are
regions (7) driving must be in the same clock region or in the clock
region immediately above or below the clock-capable input.
The BUFMR must be used to drive BUFRs in the same clock
region and adjacent clock regions.
LOC the BUFR/BUFIO.
There are four clock-capable inputs, four BUFRs, and two
BUFMRs per clock region.
Only high-performance SelectIO Clock-capable input> BUFIO > I/O clock tree SRCC or MRCC
interfaces in one clock region The clock-capable input must be placed in same clock
(50 I/Os) region as the BUFIO and I/O flip-flops it will be driving.
LOC the BUFR/BUFIO.
There are four clock-capable inputs and four BUFIOs per
clock region.

Send Feedback
UG472 (v1.12) September 27, 2016
Table 2-1: Clock-Capable Input Placement Rules (Contd)

Valid
Input Pin
Only high-performance SelectIO Clock-capable input > BUFMR >BUFIOs > I/O clock tree (8) MRCC only
interfaces in up to two adjacent Sequential I/Os and BUFIOs must be placed in the same
clock regions (7) clock region as the clock-capable input, or in immediately
adjacent clock regions above or below.
The BUFMR must be used to access BUFIOs and I/O clocks
in the same clock region and adjacent clock regions.
LOC the BUFR/BUFIO.
There are four clock-capable inputs, four BUFIOs, and two
BUFMRs per clock region.
Notes:
1. Refer to Clocking Differences in 7 Series FPGAs, page 25, for details on devices that have exceptions to these placement rules and
UG475, 7 Series FPGA Packaging and Pinout Specification, for CMT, BUFG, and I/O bank alignments.
2. Ensure that the clock-capable input pinout does not require more resources than available, that is, more than the 16 BUFGs per
half of the device, one CMT per clock region, four BUFRs per clock region, etc. If more clocking resources are needed than are
available, the clock-capable inputs should be reassigned so that they can reach clocking resources in other clock regions.
3. If defining clock or high-speed bus interface pinouts for SSI devices, refer to UG872: Large FPGA Design Methodology Guide.
4. BUFH and BUFG use the same horizontal clock line resources within the clock regions. Each BUFG or BUFH uses one of the 12
horizontal clock lines in a clock region.
5. Certain restrictions apply. See Single Clock Driving Multiple CMTs, page 29.
6. CLOCK_DEDICATED_ROUTE = BACKBONE is required when clock-capable inputs drive CMTs in other clock regions in the same
column but not in the same clock region.
7. When driving clocks into adjacent clock regions using the BUFMR or CMT, reduced clock resources can impact the adjacent clock
regions. For example, using a BUFMR to drive a BUFR in an adjacent clock region prohibits one of the clock-capable input pairs in
the adjacent clock region from driving the regional clock tree in its own clock region. A BUFH or BUFG can still be used to drive the
global clock lines in that adjacent clock region.
8. If a memory interface is placed in the same bank or region that the BUFRs/BUFIOs reside in, the connectivity from the BUFMR to
those BUFHs/BUFIOs in that bank or region might be restricted.

Send Feedback
UG472 (v1.12) September 27, 2016
When migrating between devices in the same package, the top/bottom center line that
organizes BUFGs into 16 top and 16 bottom resources can appear to have shifted with
respect to the other columns. Specifically, the I/O banks change alignment to the top/
bottom BUFGs. This results in a different alignment of the clock-capable input pins
accessing the BUFGs. Figure 2-1 shows a center alignment example using the XC7K325T
and XC7K160T devices. In this case, the center line is lower (with respect to the I/O
columns) when moving from a large to a small device in the same package, or higher when
moving from a small to a large device. If the clock-capable input pins are LOCed, the
design can be unroutable.
XC7K160T XC7K325T
Bank 18 GTX Quad

HR 118
Bank 17 GTX Quad

HR 117
Bank 16 GTX Quad Bank 16 GTX Quad

HR 116 HR Top BUFGs 116 Device
Bottom BUFGs Center
Bank 15 GTX Quad Bank 15 GTX Quad
PCIe
HR Top BUFGs 115 Device HR 115
Bottom BUFGs Center
Bank 14 Bank 34 Bank 14 Bank 34
PCIe
HR HP HR HP

HR HP HR HP

HR HP HR HP
UG472_c1_29_010612
Figure 2-1: Center Alignment Example using XC7K325T and XC7K160T Devices
There can also be situations when migrating to a smaller device in the same package where
all BUFGs in the larger devices south side are already utilized and no more BUFGs are
available. See UG475: 7 Series FPGAs Packaging and Pinout Specification for BUFG and I/O
bank alignments.
Additionally, devices with multiple super logic regions (SLRs) can have similar restrictions
when migrating to/from monolithic paths in a single SLR in the same package.

Global clocks are a dedicated network of interconnect specifically designed to reach all
clock inputs to the various resources in an FPGA. These networks are designed to have low
skew and low duty cycle distortion, low power, and improved jitter tolerance. They are
also designed to support very high frequency signals.
Understanding the signal path for a global clock expands the understanding of the various
global clocking resources. The global clocking resources and network consist of the
following paths and components:
Clock Tree and Nets - GCLK

Send Feedback
UG472 (v1.12) September 27, 2016
Clock Regions
Global Clock Buffers
Clock Tree and Nets - GCLK

7 series FPGAs clock trees are designed for low-skew and low-power operation. Any
unused branch is disconnected. The clock trees can also be used to drive logic resources
such as reset or clock enable. This is mostly used for high fanout/load nets.
In the 7 series FPGAs architecture, the pin access of the global clock lines are not limited to
the logic resources clock pins. The global clock lines can drive pins in the CLB other than
CLK pins (for example: the control pins SR and CE). Applications requiring a very fast
signal connection and large load/fanout benefit from this architecture.
Clock Regions
7 series devices improve the clocking distribution by the use of clock regions. Each clock
region can have up to 12 global clock domains. These 12 global clocks can be driven by any
combination of the 32 global clock buffers available in a monolithic device or SLR. The
dimensions of a clock region are fixed to 50 CLBs tall (50 IOBs) and spanning the left or
right side of the die. In 7 series devices, the clock backbone splits the device into a left or
right side. The backbone is not located in the center of the die. By fixing the dimensions of
the clock region, larger 7 series devices can have more clock regions. The 7 series FPGAs
supply from 1 to 24 clock regions.
Global Clock Buffers

There are up to 32 global clock buffers in 7 series devices. A CCIO input can directly
connect to any global clock buffer in the same half of the device. Each differential clock pin
pair can connect to either a differential or single-ended clock on the PCB. When used as a
differential clock input, the direct connection comes from the P-side of the differential
input pin pair. When used as a single-ended clock input, the P-side of the pin pair must be
used because a direct connection only exists on this pin. For pin naming conventions, refer
to the UG475: 7 Series FPGAs Packaging and Pinout Specification. If a single-ended clock is
connected to the P-side of a differential pin pair, then the N-side cannot be used as another
single-ended clock pin. However, it can be used as a user I/O.
CMTs in the top half of the device can only drive the BUFGs in the top half of the device
and CMTs in bottom half can only drive BUFGs in the bottom half. Similarly, only BUFGs
in the same half of the device can be used as feedback to the CMTs in the same half of the
device. Gigabit transceivers (GTs) can only directly connect to MMCMs/PLLs when the
CMT column extends into regions that also contain a full column of GTs and I/Os. The
Virtex-7T and Virtex-7XT devices have these full columns. The GTs and CMTs in the
Spartan-7, Artix-7, Kintex-7, and Zynq-7000 devices can only be connected using BUFHs
(preferred) or BUFGs.
Global clock buffers allow various clock/signal sources to access the global clock trees and
nets. The possible sources for input to the global clock buffers include:
Clock-capable inputs
Clock management tile (CMT) consisting of mixed-mode clock managers (one
MMCM and one PLL per CMT) driving BUFGs in the same half of the device.
Adjacent global clock buffer outputs (BUFGs)

Send Feedback
UG472 (v1.12) September 27, 2016
Regional clock buffers (BUFRs)

Gigabit transceivers
The 7 series FPGAs clock-capable inputs can drive global clock buffers indirectly through
the vertical clock network that exists in the clock backbone column. The 32 BUFGs are
organized into two groups of 16 BUFGs in the top and bottom of the device. Any resources
(for example, GTX transceivers) connecting to the BUFGs directly have a top/bottom
limitation. For example, each MMCM in the top can only drive the 16 BUFGs residing in
that top of the device. Similarly, the MMCMs in the bottom drive the 16 BUFGs in the
bottom.
All global clock buffers can drive all clock regions in 7 series devices. However, only 12
different clocks can be driven in a single clock region. A clock region (50 CLBs) is a branch
of the clock tree consisting of 25 CLB rows up and 25 CLB rows down. A clock region spans
halfway across the device.
The clock buffers are designed to be configured as a synchronous or asynchronous
glitch-free 2:1 multiplexer with two clock inputs. There is a dedicated path (routing
resource) for BUFG cascading to allow for more than two clock input selections. The
7 series FPGAs control pins provide a wide range of functionality and robust input
switching.
In the 7 series FPGAs clocking architecture BUFGCTRL multiplexers and all derivatives
can be cascaded to adjacent clock buffers within the group of 16 in the upper and lower
half of the device, effectively creating a ring of 16 BUFGMUXes (BUFGCTRL multiplexers)
in the upper half and another ring of 16 in the lower half. Figure 2-2 shows a simplified
diagram of cascading BUFGs.
UG472_c1_03_091010
Figure 2-2: Cascading BUFGs
The following subsections detail the various configurations, primitives, and use models of
the 7 series FPGAs clock buffers.

Send Feedback
UG472 (v1.12) September 27, 2016
Global Clock Buffer Primitives

The primitives in Table 2-2 are different configurations of the global clock buffers. The
ISE or Vivado design tools manage the configuration of all these primitives, the
Constraints Guide describes the LOC constraint.
Table 2-2: Global Clock Buffer Primitives

Primitive Input Output Control
BUFGCTRL I0, I1 O CE0, CE1, IGNORE0, IGNORE1, S0, S1
BUFG I O
BUFGCE I O CE
BUFGCE_1 I O CE
BUFGMUX I0, I1 O S
BUFGMUX_1 I0, I1 O S
BUFGMUX_CTRL I0, I1 O S
Notes:
1. All primitives are derived from a software preset of BUFGCTRL.
BUFGCTRL
The BUFGCTRL primitive shown in Figure 2-3, can switch between two asynchronous
clocks. All other global clock buffer primitives are derived from certain configurations of
BUFGCTRL.
BUFGCTRL has four select lines, S0, S1, CE0, and CE1. It also has two additional control
lines, IGNORE0 and IGNORE1. These six control lines are used to control the input I0 and
I1.
BUFGCTRL
IGNORE1
CE1
S1
I1
O
I0
S0
CE0
IGNORE0
UG472_c1_03_061310
Figure 2-3: BUFGCTRL Primitive
BUFGCTRL is designed to switch between two clock inputs without the possibility of a
glitch. When the presently selected clock transitions from High to Low after S0 and S1
change, the output is kept Low until the other (to-be-selected) clock transitions from High

Send Feedback
UG472 (v1.12) September 27, 2016
to Low. Then the new clock starts driving the output.The default configuration for
BUFGCTRL is falling-edge sensitive and held at Low prior to the input switching.
BUFGCTRL can also be rising-edge sensitive and held at High prior to the input switching
by using the INIT_OUT attribute.
In some applications the conditions previously described are not desirable. Asserting the
IGNORE pins will bypass the BUFGCTRL from detecting the conditions for switching
between two clock inputs. In other words, asserting IGNORE causes the MUX to switch
the inputs at the instant the select pin changes. IGNORE0 causes the output to switch away
from the I0 input immediately when the select pin changes, while IGNORE1 causes the
output to switch away from the I1 input immediately when the select pin changes.
Selection of an input clock requires a select pair (S0 and CE0, or S1 and CE1) to be
asserted High. If either S or CE is not asserted High, the desired input will not be selected.
In normal operation, both S and CE pairs (all four select lines) are not expected to be
asserted High simultaneously. Typically only one pin of a select pair is used as a select
line, while the other pin is tied High. The truth table is shown in Table 2-3.
Table 2-3: Truth Table for Clocking Resources

CE0 S0 CE1 S1 O
1 1 0 X I0
1 1 X 0 I0
0 X 1 1 I1
X 0 1 1 I1
1 1 1 1 Old Input (1)
Notes:
1. Old input refers to the valid input clock before this state is achieved.
2. For all other states, the output becomes the value of INIT_OUT and does not toggle.
Although both S and CE are used to select a desired output, only S is suggested for glitch
free switching. This is because when using CE to switch clocks, the change in clock
selection can be faster than when using S. A violation in the Setup/Hold time of the CE
pins causes a glitch at the clock output. On the other hand, using the S pins allows you to
switch between the two clock inputs without regard to Setup/Hold times. As a result,
using S to switch clocks will not result in a glitch. See BUFGMUX_CTRL. The CE pin is
designed to allow backward compatibility from previous Virtex architectures.

Send Feedback
UG472 (v1.12) September 27, 2016
The timing diagram in Figure 2-4 illustrates various clock switching conditions using the
BUFGCTRL primitives. Exact timing numbers are best found using the speed specification.
1 2 3 4 5 6
I0
I1
TBCCCK_CE
CE0
CE1
S0
S1
IGNORE0
IGNORE1
TBCCKO_O TBCCKO_O TBCCKO_O
at I0 Begin I1 Begin I0
UG472_c1_04_033030
Figure 2-4: BUFGCTRL Timing Diagram
Before time event 1, output O uses input I0.

At time TBCCCK_CE, before the rising edge at time event 1, both CE0 and S0 are
deasserted Low. At about the same time, both CE1 and S1 are asserted High.
At time TBCCKO_O, after time event 3, output O uses input I1. This occurs after a High
to Low transition of I0 (event 2) followed by a High to Low transition of I1.
At time event 4, IGNORE1 is asserted.
At time event 5, CE0 and S0 are asserted High while CE1 and S1 are deasserted Low.
At TBCCKO_O, after time event 6, output O has switched from I1 to I0 without
requiring a High to Low transition of I1.
Other capabilities of BUFGCTRL are:
Pre-selection of the I0 and I1 inputs are made after configuration but before device
operation.
The initial output after configuration can be selected as either High or Low.
Clock selection using CE0 and CE1 only (S0 and S1 tied High) can change the clock
selection without waiting for a High to Low transition on the previously selected
clock.

Send Feedback
UG472 (v1.12) September 27, 2016
Table 2-4 summarizes the attributes for the BUFGCTRL primitive.
Table 2-4: BUFGCTRL Attributes

Attribute Name Description Possible Values
INIT_OUT Initializes the BUFGCTRL output to the specified 0 (default), 1
value after configuration. Sets the positive or
negative edge behavior. Sets the output level when
changing clock selection.
PRESELECT_I0 If TRUE, BUFGCTRL output will use the I0 input FALSE (default),
after configuration(1) TRUE
PRESELECT_I1 If TRUE, BUFGCTRL output will use the I1 input FALSE (default),
after configuration(1) TRUE
Notes:
1. Both PRESELECT attributes cannot be TRUE at the same time.
BUFG
BUFG is a clock buffer with one clock input and one clock output. This primitive is based
on BUFGCTRL with some pins connected to logic High or Low. Figure 2-5 illustrates the
relationship of BUFG and BUFGCTRL. The LOC constraint is available for manually
placing the BUFG location. See the Constraints Guide for more information.
IGNORE1
VDD
CE1
GND
GND S1
BUFG
I1
VDD
O O
I
I0
I
VDD S0
VDD CE0
IGNORE0
GND
UG472_c1_05_112310
Figure 2-5: BUFG as BUFGCTRL
The output follows the input as shown in the timing diagram in Figure 2-6.
BUFG(I)
BUFG(O)
TBCCKO_O
UG472_c1_06_061310
Figure 2-6: BUFG Timing Diagram

Send Feedback
UG472 (v1.12) September 27, 2016
BUFGCE and BUFGCE_1

Unlike BUFG, BUFGCE is a clock buffer with one clock input, one clock output and a clock
enable line. This primitive is based on BUFGCTRL with some pins connected to logic High
or Low. Figure 2-7 illustrates the relationship of BUFGCE and BUFGCTRL. The LOC
constraint is available for manually placing the BUFGCE and BUFGCE_1 locations. See the
Constraints Guide for more information.
BUFGCE as BUFGCTRL
IGNORE1
VDD
CE1
GND
BUFGCE GND S1
CE
I1
VDD
O O
I
I0
I
VDD S0
CE CE0
IGNORE0
GND
UG472_c1_07_061310
Figure 2-7: BUFGCE as BUFGCTRL
The switching condition for BUFGCE is similar to BUFGCTRL. If the CE input is Low prior
to the incoming rising clock edge, the following clock pulse does not pass through the
clock buffer, and the output stays Low. Any level change of CE during the incoming clock
High pulse has no effect until the clock transitions Low. The output stays Low when the
clock is disabled. However, when the clock is being disabled it completes the clock High
pulse.
Since the clock enable line uses the CE pin of the BUFGCTRL, the select signal must meet
the setup time requirement. Violating this setup time can result in a glitch. Figure 2-8
illustrates the timing diagram for BUFGCE.
BUFGCE(I)
TBCCCK_CE
BUFGCE(CE)
BUFGCE(O)
TBCCKO_O
UG472_c1_08_061310
Figure 2-8: BUFGCE Timing Diagram
BUFGCE_1 is similar to BUFGCE, with the exception of its switching condition. If the CE
input is Low prior to the incoming falling clock edge, the following clock pulse does not
pass through the clock buffer, and the output stays High. Any level change of CE during
the incoming clock Low pulse has no effect until the clock transitions High. The output
stays High when the clock is disabled. However, when the clock is being disabled it
completes the clock Low pulse.

Send Feedback
UG472 (v1.12) September 27, 2016
Figure 2-9 illustrates the timing diagram for BUFGCE_1.

BUFGCE_1(I)
TBCCCK_CE
BUFGCE_1(CE)
BUFGCE_1(O)
TBCCKO_O
UG472_c1_09_061310
Figure 2-9: BUFGCE_1 Timing Diagram
BUFGMUX and BUFGMUX_1

BUFGMUX is a clock buffer with two clock inputs, one clock output, and a select line. This
primitive is based on BUFGCTRL with some pins connected to logic High or Low.
Figure 2-10 illustrates the relationship of BUFGMUX and BUFGCTRL. The LOC constraint
is available for manually placing the BUFGMUX and BUFGCTRL locations. See the
Constraints Guide for more information.
IGNORE1
GND
S CE1
VDD S1
BUFGMUX
I1 I1
O O
I0 I0
S
VDD S0
CE0
IGNORE0
GND
UG472_c1_10_061310
Figure 2-10: BUFGMUX as BUFGCTRL
Since the BUFGMUX uses the CE pins as select pins, when using the select, the setup time
requirement must be met. Violating this setup time can result in a glitch.

Send Feedback
UG472 (v1.12) September 27, 2016
Switching conditions for BUFGMUX are the same as the CE pins on BUFGCTRL.
Figure 2-11 illustrates the timing diagram for BUFGMUX.
TBCCCK_CE
I0
I1
O
TBCCKO_O TBCCKO_O
begin
switching using I1
ug472_c1_11_112310
Figure 2-11: BUFGMUX Timing Diagram
In Figure 2-11:
The current clock is I0.
S is activated High.
If I0 is currently High, the multiplexer waits for I0 to deassert Low.
Once I0 is Low, the multiplexer output stays Low until I1 transitions High to Low.
When I1 transitions from High to Low, the output switches to I1.
If Setup/Hold are met, no glitches or short pulses can appear on the output.
BUFGMUX_1 is rising edge sensitive and held at High prior to input switch. Figure 2-12
illustrates the timing diagram for BUFGMUX_1. The LOC constraint is available for
manually placing the BUFGMUX and BUFGMUX_1 locations. See the Constraints Guide for
more information.
TBCCCK_CE
S
I0
I1
O
TBCCKO_O
ug472_c1_12_061310
Figure 2-12: BUFGMUX_1 Timing Diagram
In Figure 2-12:
The current clock is I0.
If I0 is currently Low, the multiplexer waits for I0 to be asserted High.
Once I0 is High, the multiplexer output stays High until I1 transitions Low to High.
When I1 transitions from Low to High, the output switches to I1.

Send Feedback
UG472 (v1.12) September 27, 2016
If Setup/Hold are met, no glitches or short pulses can appear on the output.
Table 2-5: BUFGMUX Attributes
CLK_SEL_TYPE Specifies synchronous or asynchronous clock SYNC (default),
switching. ASYNC
BUFGMUX_CTRL
The BUFGMUX_CTRL replaces the BUFGMUX_VIRTEX4 legacy primitive.
BUFGMUX_CTRL is a clock buffer with two clock inputs, one clock output, and a select
line. This primitive is based on BUFGCTRL with some pins connected to logic High or
Low. Figure 2-13 illustrates the relationship of BUFGMUX_CTRL and BUFGCTRL.
IGNORE1
GND
VDD CE1
S S1
BUFGMUX_CTRL
I1 I1
O O
I0 I0
S
S0
CE0
VDD
IGNORE0
GND
ug472_c1_13_061310
Figure 2-13: BUFGMUX_CTRL as BUFGCTRL
BUFGMUX_CTRL uses the S pins as select pins. S can switch anytime without causing a
glitch. The Setup/Hold time on S is for determining whether the output will pass an extra
pulse of the previously selected clock before switching to the new clock. If S changes as
shown in Figure 2-14, prior to the setup time TBCCCK_S and before I0 transitions from High
to Low, then the output will not pass an extra pulse of I0. If S changes following the hold
time for S, then the output will pass an extra pulse. If S violates the Setup/Hold
requirements, the output might pass the extra pulse, but it will not glitch. In any case, the
output will change to the new clock within three clock cycles of the slower clock.
The Setup/Hold requirements for S0 and S1 are with respect to the falling clock edge, not
the rising edge as for CE0 and CE1.

Send Feedback
UG472 (v1.12) September 27, 2016
Switching conditions for BUFGMUX_CTRL are the same as the S pin of BUFGCTRL.
Figure 2-14 illustrates the timing diagram for BUFGMUX_CTRL.
I0
I1
O
TBCCKO_O
TBCCKO_O
ug472_c1_14_061310
Figure 2-14: BUFGMUX_CTRL Timing Diagram
Other capabilities of the BUFGMUX_CTRL primitive are:

Pre-selection of I0 and I1 input after configuration.
Initial output can be selected as High or Low after configuration.
Additional Use Models

Asynchronous MUX Using BUFGCTRL
In some cases an application requires immediate switching between clock inputs or
bypassing the edge sensitivity of BUFGCTRL. An example is when one of the clock inputs
is no longer switching. If this happens, the clock output would not have the proper
switching conditions because the BUFGCTRL never detected a clock edge. This case uses
the asynchronous MUX. Figure 2-15 illustrates an asynchronous MUX with BUFGCTRL
design example. Figure 2-16 shows the asynchronous MUX timing diagram.
IGNORE1
VDD
VDD CE1
S S1
Asynchronous MUX
Design Example
I1 I1
O O
I0 I0
S0
CE0
VDD
VDD IGNORE0
ug472_c1_15_061310
Figure 2-15: Asynchronous MUX with BUFGCTRL Design Example

Send Feedback
UG472 (v1.12) September 27, 2016
I1
I0
S
TBCCKO_O TBCCKO_O
O
at I0 Begin I1
UG472_c1_16_033011
Figure 2-16: Asynchronous MUX Timing Diagram
In Figure 2-16:
The current clock is from I0.
The Clock output immediately switches to I1.
When Ignore signals are asserted High, glitch protection is disabled.
BUFGMUX_CTRL with a Clock Enable

A BUFGMUX_CTRL with a clock enable BUFGCTRL configuration allows you to choose
between the incoming clock inputs. If needed, the clock enable is used to disable the
output. Figure 2-17 illustrates the BUFGCTRL usage design example and Figure 2-18
shows the timing diagram.
IGNORE1
GND
CE CE1
S S1
BUFGMUX_CTRL+CE
Design Example
I1 I1
O O
I0 I0
S
S0
CE
CE0
IGNORE0
GND
ug472_c1_17_061310
Figure 2-17: BUFGMUX_CTRL with a CE and BUFGCTRL

Send Feedback
UG472 (v1.12) September 27, 2016
1 2 3
I0
I1
S
TBCCCK_CE
CE
TBCCKO_O TBCCKO_O
O
Begin I1
at I0 Clock Off
ug472_c1_18_033011
Figure 2-18: BUFGMUX_CTRL with a CE Timing Diagram
In Figure 2-18:
At time event 1, output O uses input I0.
Before time event 2, S is asserted High.
At time TBCCKO_O, after time event 2, output O uses input I1. This occurs after a High
to Low transition of I0 followed by a High to Low transition of I1 is completed.
At time TBCCCK_CE, before time event 3, CE is asserted Low. To avoid any output clock
glitches, the clock output is switched Low and kept at Low until after a High to Low
transition of I1 is completed.

Regional clock networks are clock networks independent of the global clock network.
Unlike global clocks, the span of a regional clock signal (BUFR) is limited to one clock
region, one I/O clock signal drives a single bank. These networks are especially useful for
source-synchronous interface designs. The I/O banks in 7 series devices are the same size
as a clock region.
To understand how regional clocking works, it is important to understand the signal path
of a regional clock signal. The regional clocking resources and network in 7 series devices
consist of the following paths and components:
Clock-Capable I/O
I/O Clock BufferBUFIO
Regional Clock BufferBUFR
Regional Clock Nets
Multi-Region Clock BufferBUFMR/BUFMRCE
Horizontal Clock BufferBUFH, BUFHCE

Send Feedback
UG472 (v1.12) September 27, 2016
Clock-Capable I/O
Each clock region has four clock-capable I/O pin pairs per I/O bank in every I/O column.
Clock-capable I/O pairs are specialized I/O pairs in select locations with special hardware
connections to nearby regional clocking resources and other clocking resources.
Additionally, clock capable I/O pairs can be used as regular I/O pairs. There are four
dedicated clock-capable I/O sites in every bank. When used as clock inputs, clock-capable
pins can drive BUFIO, BUFMR, and BUFR. Each I/O column supports regional clock
buffers (BUFR). There are two I/O columns in each device.
When used as single-ended clock pins, then as described in Global Clock Buffers the P-side
of the pin pair must be used because a direct connection only exists on this pin.
A CCIO can drive any BUFR in the region, but only dedicated CCs can drive specific
BUFIOs and MRCCs can drive BUFMRs in a 1:1 relationship. This means that a CCIO has
only a single connection to a specific BUFIO or BUFMR.
I/O Clock BufferBUFIO

The I/O clock buffer (BUFIO) is a clock buffer available in 7 series devices. The BUFIO
drives a dedicated clock net within the I/O bank, independent of the global clocking
resources. Thus, BUFIOs are ideally suited for source-synchronous data capture
(forwarded/receiver clock distribution). BUFIOs are driven by clock-capable I/Os located
in the same bank, by the HPC from the MMCM, or by the BUFMRs in the same and
adjacent regions. In a clock region, there are four BUFIOs per bank. Each BUFIO can drive
a single I/O clock network in the same region/bank. BUFIOs cannot drive logic resources
(CLB, block RAM, DSP, etc.) because the I/O clock network only reaches the I/O column in
the same bank/clock region. For multi-region bank support, see Multi-Region Clock
BufferBUFMR/BUFMRCE.
BUFIOs are driven by:
SRCCs and MRCCs in the same clock region
MRCCs in an adjacent clock region using BUFMRs
MMCMs clock outputs 0-3 driving the HPC in the same clock region

Send Feedback
UG472 (v1.12) September 27, 2016
BUFIO Primitive
BUFIO is a clock in, clock out buffer. There is a phase delay between input and output.
Figure 2-19 shows the BUFIO. Table 2-6 lists the BUFIO ports. A location constraint is
available for BUFIO.
BUFIO
O
I
ug472_c1_19_061310
Figure 2-19: BUFIO Primitive
Table 2-6: BUFIO Port List and Definitions

Port Name Type Width Definition
O Output 1 Clock output port
I Input 1 Clock input port
BUFIO Use Models

In Figure 2-20, a BUFIO is used to drive the I/O logic using the clock-capable I/O. This
implementation is ideal in source-synchronous applications where a forwarded clock is
used to capture incoming data.

Send Feedback
UG472 (v1.12) September 27, 2016
I/O
I/O
I/O
I/O
I/O
I/O
P I/O
N I/O
P I/O
N I/O
BUFIO
BUFR
Not all available BUFIOs and

BUFRs are shown. BUFR To FPGA
Logic
BUFIO
P I/O
N I/O
P I/O
N I/O
I/O
I/O
I/O
I/O
I/O
I/O
ug472_c1_20_030311
Figure 2-20: BUFIO Driving I/O Logic

Send Feedback
UG472 (v1.12) September 27, 2016
Regional Clock BufferBUFR

The regional clock buffer (BUFR) is another clock buffer available in 7 series devices.
BUFRs drive clock signals to a dedicated clock net within a clock region, independent from
the global clock tree. Each BUFR can drive the four regional clock nets in the region it is
located. Unlike BUFIOs, BUFRs can drive the I/O logic and logic resources (CLB, block
RAM, etc.). BUFRs can be driven by clock-capable pins, local interconnect, and the
MMCMs HPCs (CLKOUT0 through CLKOUT3), or the BUFMRs in the same and adjacent
regions. In addition, BUFRs are capable of generating divided clock outputs with respect
to the clock input. The divide values are an integer between one and eight. BUFRs are ideal
for source- synchronous applications requiring clock domain crossing or serial-to-parallel
conversion.
BUFRs are driven by:
SRCCs and MRCCs in the same clock region
MRCCs in an adjacent clock region using BUFMRs
MMCMs clock outputs 0-3 driving the HPC in the same clock region
MMCMs clock outputs 0-3
Each I/O column supports regional clock buffers. There are two I/O columns in a device.
BUFRs can also directly drive MMCM clock inputs and BUFGs.
BUFR Primitive
BUFR (Figure 2-21 and Table 2-7) is a clock-in/clock-out buffer with the capability to
divide the input clock frequency. The 7 series FPGAs BUFRs can also directly drive
MMCM clock inputs and BUFGs.
I O
CE
CLR
ug472_c1_21_061310
Figure 2-21: BUFR Primitive
Table 2-7: BUFR Port List and Definitions

CE(1) Input 1 Asynchronous output clock enable
port. Cannot be used in BYPASS mode.
CLR Input 1 Asynchronous clear for the divide
logic, and sets the output Low. Cannot
be used in BYPASS mode.

Send Feedback
UG472 (v1.12) September 27, 2016
Table 2-7: BUFR Port List and Definitions (Contd)

1. CE is not intended to be used as an actively switching signal and is not timed by the ISE or Vivado
design tools.
Additional Notes on the CE Pin

When CE is asserted/deasserted, the output clock signal turns on/off. When global set/
reset (GSR) signal is High, the BUFR output is held in reset, even if CE is held High. The
BUFR output toggles after the GSR signal is deasserted when a clock is on the BUFR input
port.
BUFR Attributes and Modes

Clock division in the BUFR is controlled in software through the BUFR_DIVIDE attribute.
Table 2-8 lists the possible values when using the BUFR_DIVIDE attribute.
Table 2-8: BUFR_DIVIDE Attribute

BUFR_DIVIDE Defines whether the output clock is a 1, 2, 3, 4, 5, 6, 7, 8
frequency divided version of the input clock. BYPASS (default)
Notes:
1. Location constraint is available for BUFR.
The propagation delay through BUFR is different for BUFR_DIVIDE = 1 and

BUFR_DIVIDE = BYPASS. When set to 1, the delay is slightly more than BYPASS. All other
divisors have the same delay BUFR_DIVIDE = 1. The phase relationship between the input
clock and the output clock is the same for all possible divisions except BYPASS.
The timing relationship between the inputs and output of BUFR when using the
BUFR_DIVIDE attribute is illustrated in Figure 2-22. In this example, the BUFR_DIVIDE
attribute is set to three. Sometime before this diagram CLR was asserted.
1 2 3 4
CE
CLR
TBRCKO_O TBRDO_CLRO TBRCKO_O
ug472_c1_22_033011
Figure 2-22: BUFR Timing Diagrams with BUFR_DIVIDE Values
In Figure 2-22:
Before clock event 1, CE is asserted High.

Send Feedback
UG472 (v1.12) September 27, 2016
After CE is asserted and time TBRCKO_O, the output O begins toggling at the divide by
three rate of the input I. TBRCKO_O and other timing numbers are best found in the
speed specification.
Note: Note: The duty cycle is not 50/50 for odd division. The Low pulse is one cycle of I longer.
At time event 2, CLR is asserted. After TBRDO_CLRO from time event 2, O stops
toggling.
At time event 3, CLR is deasserted.
At time TBRCKO_O after clock event 4, O begins toggling again at the divided by three
rate of I.
Note: For proper operation, if the clock to the BUFR is stopped, then a reset (CLR) must be applied
after the clock returns.
BUFR Use Models

BUFRs are ideal for source-synchronous applications requiring clock domain crossing or
serial-to-parallel conversion. Unlike BUFIOs, BUFRs are capable of clocking logic
resources in the FPGAs other than the IOBs. Figure 2-23 is a BUFR design example.
I/O CLBs
I/O CLBs
Block DSP
RAM Tile
I/O CLBs
I/O CLBs
CLBs
P I/O
Clock Capable I/O
CLBs
N I/O Block DSP
RAM Tile
CLBs
P I/O
Clock Capable I/O
CLBs
N I/O
BUFIO
BUFR
To more
FPGA logic
resources
ug472_c1_23_032111
Figure 2-23: BUFR Driving Various Logic Resources
Regional Clock Nets

In addition to global clock trees and nets, 7 series devices contain regional clock trees and
nets. The regional clock trees are also designed for low-skew and low-power operation.
Unused branches are disconnected. The regional clock trees also manage the load/fanout
when all the logic resources are used.
Regional clock nets do not propagate throughout the whole 7 series device. Instead, they
are limited to only one clock region. One clock region contains four independent regional

Send Feedback
UG472 (v1.12) September 27, 2016
clock nets. To access regional clock nets, BUFRs must be instantiated. For multi-region
support, see Multi-Region Clock BufferBUFMR/BUFMRCE.
Multi-Region Clock BufferBUFMR/BUFMRCE

The BUFMR replaces the multi-region/bank support for BUFR and BUFIO available in
previous Virtex architectures. There are two BUFMRs in every bank and each buffer can be
driven by one specific MRCC in the same bank. MRCC pins are labeled with MRCC in the
pin name for both the P and N pins of the pin pair (for example: IO_L12P_T1_MRCC_12 or
IO_L12N_T1_MRCC_12). The BUFMRs drive the BUFIOs and/or BUFRs in the same region/
banks and in the regions/banks above and below. BUFR and BUFIO primitives must be
separately instantiated. When using BUFR dividers (not in bypass), the BUFMR must be
disabled by deasserting the CE pin, the BUFR must be reset (cleared by asserting CLR), and
then the CE signal should be asserted. This sequence ensures that all BUFR output clocks
are phase aligned. If the dividers within the BUFRs are not used, then the circuit topology
only requires the use of BUFMR.
BUFMR inputs include:
MRCCs in the same bank
GT clocks in the same region
BUFMR Primitive
BUFMRs (Figure 2-24, Table 2-9, and Table 2-10) are a clock-in/clock-out buffer with clock
enable (CE). Deasserting CE stops the output clock. BUFMRs must drive BUFRs and
BUFIOs to route to the same region/bank and adjacent regions/banks. BUFMRs are
driven by the MRCCs or the GT clocks in the same region.
BUFMR
I O
BUFMRCE
I O
CE
ug472_c1_24_062210
Figure 2-24: BUFMR and BUFMRCE Primitives
Table 2-9: BUFMR and BUFMRCE Port List and Definitions

Port Type Width Definition
CE Input 1 Output clock enable port

Send Feedback
UG472 (v1.12) September 27, 2016
Table 2-10: BUFMR and BUFMRCE Attributes

INIT_OUT Initializes the BUFGCTRL output to the specified 0 (default), 1
value after configuration. Sets the positive or
negative edge behavior. Sets the output level when
changing clock selection.
CE_TYPE Set to SYNC for CE to be synchronous from input to SYNC (default),
output O, or set to ASYNC for asynchronous input to ASYNC
output.
To use BUFMR or BUFMRCE with BUFIOs, the interface pins must fit within three banks.
Similarly, if used with BUFRs, the logic must fit in up to three regions (if three BUFRs are
used). If a memory interface is placed in the same bank or region that the BUFRs/BUFIOs
reside in, the connectivity from the BUFMR to those BUFHs/BUFIOs in that bank or region
might be restricted. Figure 2-25 shows the topology of the BUFMRCE.
CLR
BUFR
Region/Bank
BUFIO
CLR CE
Region/Bank MRCC
BUFMRCE
CLR
Region/Bank
ug472_c1_25_030111
Figure 2-25: Multi-Region Buffer Topology
The CE_TYPE attribute should always be set to SYNC to ensure that the clock output is
glitch free. If the clock output of the BUFMRCE is stopped (for example, by deasserting
CE), the BUFR must be reset (CLR) after the BUFMRCE is enabled again. The main
purpose of CE on the BUFMRCE is to provide a synchronous, phase-aligned clock to the
BUFRs and BUFIOs. For more details on the use of BUFMR in driving BUFRs and BUFIOs,
see Appendix A, Multi-Region Clocking.

Send Feedback
UG472 (v1.12) September 27, 2016
Horizontal Clock BufferBUFH, BUFHCE

The horizontal clock buffer (BUFH) drives a horizontal global clock tree spine in a single
region (Figure 2-26). Each region has 12 BUFHs available. Every BUFH has a clock enable
pin (CE) that allows the clocks to be turned-off dynamically. BUFHs can be driven by:
MMCM/PLL outputs in the same region
BUFG outputs
GT output clocks in the same or horizontal adjacent clock region
Local interconnect
Clock-capable inputs from either the left or right side I/O banks in the same
horizontal adjacent regions/banks
BUFH
I O
BUFHCE
I O
CE
ug472_c1_24_061310
Figure 2-26: BUFH and BUFHCE Primitives
Table 2-11: BUFH and BUFHCE Port List and Definitions

CE Input 1 Output clock enable port
Table 2-12: BUFH and BUFHCE Attributes

INIT_OUT Initializes the BUFH output to the specified value 0 (default), 1
after configuration. Sets the positive or negative edge
behavior. Sets the output level when changing clock
selection.
CE_TYPE Set to SYNC for CE to be synchronous from input to SYNC (default),
output O, or set to ASYNC for asynchronous input to ASYNC
output.

Send Feedback
UG472 (v1.12) September 27, 2016
To use the BUFH, the logic must fit into the two regions horizontally adjacent to each other
(left and right) as illustrated in Figure 2-27. The clock enable pin can completely turn off
the clocks thus realizing potential power savings. The power consumption and jitter in a
BUFH is lower when compared to a BUFG driving two adjacent regions.
Quad GT Transceivers
Clock Backbone
I/O Bank and

I/O Bank
12 12
Clock
Region
BUFH BUFH
ug472_c1_27_020812
Figure 2-27: Example of a Horizontal Clock Buffer
GTZ Loopback Clock Buffer BUFG_LB (HT devices only)

BUFG_LB (Figure 2-28) is a clock buffer with one clock input and one clock output. This
loopback buffer is required if the TXOUTCLKs and/or RXOUTCLKs drive user logic
directly in the fabric without the use of an MMCM. They also drive back to their
corresponding TXUSRCLK and RXUSRCLK. Typically, these clock buffers are part of the
7 series transceiver wizard for the GTZ gigabit transceivers. The BUFG_LBs are located at
the top in the XC7VH580T and XC7VH870T and at the bottom in the XC7VH870T of the
clock backbone next to the GTZ SLRs. In the XC7VH870T, there are 16 bottom (X3Y0 to
X3Y15) and 16 top (X1Y16 to X1Y31) BUFG_LBs. In the XC7VH580T, there are 16 top (X1Y0
to X1Y15) BUFG_LBs. They have a fixed, relative location to the GTZ octals and connect to
the GTZ octals clocks as listed in Table 2-13.
Note: Not all of these clock buffers are used.
BUFG_LB
CLKIN CLKOUT
ug472_c2_28a_042814
Figure 2-28: BUFG_LB Primitive

Send Feedback
UG472 (v1.12) September 27, 2016
Table 2-13: BUFG_LB locations

TX/RX OUTCLK to TX/RX BUFG_LB Locations in the BUFG_LB Locations in the
USERCLKs XC7VH580T XC7VH870T
Top GTZ Octals
TXOUTCLK0 BUFG_LB_X1Y0 BUFG_LB_X1Y16
TXOUTCLK1 BUFG_LB_X1Y4 BUFG_LB_X1Y20
RXOUTCLK0 BUFG_LB_X1Y12 BUFG_LB_X1Y28
Bottom GTZ Octals
TXOUTCLK0 N/A BUFG_LB_X3Y15
TXOUTCLK1 N/A BUFG_LB_X3Y11
RXOUTCLK0 N/A BUFG_LB_X3Y3
For more details, see the 7 Series FPGAs GTZ Transceivers Advance Specification User Guide
(UG478).
7 series FPGAs contain four HPCs per I/O bank. These clocks are a direct short differential
connection to BUFIOs and BUFRs in the I/O. Therefore, these clocks exhibit very low jitter
and minimal duty-cycle distortion. In the I/O columns, the HPC connects to the BUFIO/
BUFRs and drives the I/O logic. Since the CMT column is co-located next to the I/O
column, the HPC drives directly into the I/O bank next to a CMT.
HPCs are driven by CLKOUT[3:0] of the MMCM (only).
Clock Gating for Power Savings

The 7 series FPGA clock architecture provides a straightforward means of implementing
clock gating for the purposes of powering down portions of a design. Most designs contain
several unused BUFGCE or BUFHCE resources. A clock can drive a BUFGCE or BUFHCE
input, a BUFGCE output can drive distinct regions of logic, and a BUFHCE can drive a
single region. For example, if all the logic that is required to always be operating is
constrained to a few clock regions, then the BUFGCE output can drive those regions. Or, if
a BUFHCE drives an interface fitting in a single region, then that interface could be
shutdown during non-operation. Toggling the enable of the BUFGCE or BUFHCE
provides a simple means of stopping all dynamic power consumption in the logic regions
available for power savings.

Send Feedback
UG472 (v1.12) September 27, 2016
The Xilinx Power Estimator (XPE) tool is used to estimate power savings. The difference is
calculated by setting the frequency on the corresponding clock net to 0 MHz or providing
the appropriate stimulus data to the tool.
Stacked Silicon Interconnect Clocking

The clocking structure in the Virtex-7 FPGAs that are built using the stacked silicon
interconnect (SSI) technology is largely the same as the clocking structure in other,
monolithic 7 series devices (see Figure 2-29 and Figure 2-30). There are 32 global clock
buffers (BUFGs) and 32 global clock lines (the clock backbone) in each super logic region
(SLR) which connect to adjacent SLR clock backbones via fast, dedicated, 3-stateable
vertical routes in the interposer. The interposer clock backbone is an extension of the clock
backbone used to connect the clock backbone for each of the SLRs. The ability for the 32
global clock lines to travel across the interposer means that the global clock lines run the
height of the device, enabling BUFGs in one SLR to clock components anywhere in the
FPGA. The interposer clock backbone is the only dedicated clocking resource across SLRs.
A BUFG on any SLR can drive a specific, dedicated global clock track on any or all other
SLRs. Each SSI SLR has 32 global clocks (BUFGs) available and other clocking resources are
the same as monolithic devices. The total number of BUFGs in the SSI devices are available
with the limitations described in the clock placement sections below. The BUFGs are only
driven by the sources within the SLR where they reside. Each SLR is three clock regions
tall. Clocks that cross from one SLR to an adjacent SLR are subject to more skew than clocks
that stay within a single SLR. Attention must be paid to minimize skew when placing
clocking networks by placing related BUFG clocking structures into the same SLR, which
might require duplication of external clocks.

Send Feedback
UG472 (v1.12) September 27, 2016
From Local SLR

Clock Connection 16 BUFGs To SLR Global
Clock Network
To SLR Global
Clock Network 16 BUFGs
HROW
SLR Clock Backbone

32 12 BUFHCEs
Bidirectional 3-Stateable
Interposer Connection Super Logic Region
32 Interposer Clock
Backbone Connections
From Local SLR

Clock Network
To SLR Global
HROW
SLR Clock Backbone

32 12 BUFHCEs
Bidirectional 3 Stateable
32 Interposer Clock
From Local SLR

Clock Network
To SLR Global
HROW
SLR Clock Backbone

32 12 BUFHCEs
Interposer
UG472_c1_28_020712
Figure 2-29: SSI Technology Example for Virtex-7 XT Devices

Send Feedback
UG472 (v1.12) September 27, 2016
GTZ Quad GTZ Quad
32 Interposer Clock
From Local SLR

Clock Connection
16 BUFGs To SLR Global
Clock Network
To SLR Global
HROW
SLR Clock Backbone

32 12 BUFHCEs
32 Interposer Clock
More SLRs
and Bottom GTZ Quads
Interposer
UG472_c2_19_061212
Figure 2-30: SSI Technology Example for Virtex-7 HT Devices (Top Side View)
Certain clocking resources cannot cross the boundaries between SLRs. CCIOs cannot drive
CMTs or BUFGs in another SLR. Similarly, the BUFMR cannot drive BUFRs and BUFIOs in
adjacent SLRs. BUFGs and CMTs cannot be cascaded across the interposer. These
limitations should be understood when migrating designs between SSI devices and
monolithic devices. For specific guidance on clocking pinout planning, see UG872: Large
FPGA Methodology Guide.
Placement of Clocking Structures

Whenever possible, place related clocking structures such as I/O clocking (I/O interfaces),
MMCMs, PLLs, and global clocks into the same SLR. Placement of these structures within
the SLR follow the same rules as a monolithic device. The software automatically resolves
conflicting rules when the clocking logic is constrained to the SLR level by you. However,
placement of clock structures within single SLR can minimize skew effect. If a global clock
drives resources in two other SLRs, then place the driving BUFG in an SLR that is centered
between the destination SLRs, thus driving to the SLRs above and below.

Send Feedback
UG472 (v1.12) September 27, 2016
Clock Buffer Placement

A single global clock buffer can drive any clocking point in any SLR. The global clock
buffers are competing for the 32 available interposer clock backbone tracks. A track driven
by a BUFG in one SLR cannot be driven by another BUFG in the same or any other SLR.
Because each SLR clock track is segmentable at the SLR boundary, a BUFG in one SLR can
use the same track as a BUFG in an adjacent SLR as long as the clocking is local to the SLR
and does not need to connect to an adjacent SLR.
For example, in the largest SSI device (XC7V2000T), each of the SLRs has 32 BUFGs. The
BUFGs and the associated clock nets can be viewed as four groups of 031, 3263, 6495,
and 96127 from the bottom SLR up to the top. BUFGs and clock nets that are multiples of
32 (32 indices apart from each other) contend for the same interposer backbone resources.
In this XC7V2000T example, these are SLR clock nets 0, 32, 64, and 96; 1, 33, 65, and 97; and
so on. With four SLRs, the BUFGs X0Y0, X0Y32, X0Y64, and X0Y96 (all called BUFG0s in
Figure 2-31) connect to the same track 0 in the interposer backbone. Therefore, only one of
those buffers can be used in the design. Similarly, the BUFGs X0Y1, X0Y33, X0Y65, and
X0Y97 (all BUFG1s) compete for interposer backbone track 1.

Send Feedback
UG472 (v1.12) September 27, 2016
Interposer
BUFG31 (X0Y127)
96 97 98 99 12
BUFG2 (X0Y98)
7
BUFG1 (X0Y97)
SLR3
BUFG0 (X0Y96)
Interposer Clock Backbone Tracks 0 1 2 3 31
BUFG31 (X0Y95)
64 65 66 67 95
BUFG2 (X0Y66)
BUFG1 (X0Y65)
SLR2
BUFG0 (X0Y64)
Interposer Clock Backbone Tracks 0 1 2 3 31
BUFG31 (X0Y63)
32 33 34 35 63
BUFG2 (X0Y34)
BUFG1 (X0Y33) SLR1

BUFG0 (X0Y32)
Interposer Clock Backbone tracks 0 1 2 3 31
BUFG31 (X0Y31)
SLR Clock Backbone 0 1 2 3 31

BUFG2 (X0Y2)
BUFG1 (X0Y1) SLR0

BUFG0 (X0Y0)
Interposer
UG472_c2_18_011712
Figure 2-31: BUFG Connectivity across Interposer Clock Backbone

Send Feedback
UG472 (v1.12) September 27, 2016
Chapter 3
Clock Management Tile

Introduction
In 7 series FPGAs, the clock management tile (CMT) includes a mixed-mode clock
manager (MMCM) and a phase-locked loop (PLL). The PLL contains a subset of the
MMCM functions. At the core of the 7 series FPGAs CMT is the architecture similar to the
Virtex-5 and Virtex-6 FPGAs with enhanced functions and capabilities. The CMT backbone
can be used to chain CMT clocking functions; however, there are limitations to placement,
distance, and connectivity resources. See Appendix B, Clocking Resources and
Connectivity Variations per Clock Region.
The CMT diagram (Figure 3-1) shows a high-level view of the connection between the
various clock input sources and the MMCM/PLL. In 7 series FPGAs, the clock input
connectivity allows multiple resources to provide the reference clock(s) to the MMCM/
PLL. The number of output counters (dividers) is eight with some of them capable of
driving out an inverted clock signal (180 phase shift). For backward compatibility with
DCMs, nine independent outputs can be selected for mapping the DCM outputs directly
into the MMCM. 7 series FPGAs MMCMs have infinite fine phase-shift capability in either
direction and can be used in dynamic phase-shift mode. The resolution of the fine phase
shift depends on the VCO frequency. Fractional divide functionality in increments of 1/8th
(0.125) for CLKFBOUT and CLKOUT0 are available to support greater clock frequency
synthesis capability. 7 series FPGAs have added spread spectrum capabilities to the
MMCMs. If the MMCM spread spectrum feature is not used, a spread spectrum on an
external input clock will not be filtered and thus passed on to the output clock.

Send Feedback
UG472 (v1.12) September 27, 2016
BUFR
IBUFG (CC)
BUFG CLKIN1
GT CLKIN2
BUFH
Local Routing
(not recommended) PLL
BUFG
BUFH
CLKFB
CLKIN1
CLKIN2
MMCM BUFG
BUFH
CLKFB
ug472_c2_01_032511
Figure 3-1: Block Diagram of the 7 Series FPGAs CMT
MMCMs and PLLs

7 series devices contain up to 24 CMT tiles. The MMCMs and PLLs serve as frequency
synthesizers for a wide range of frequencies, serve as a jitter filters for either external or
internal clocks, and deskew clocks.
The PLL in the 7 series FPGAs, a subset of the MMCM functionality, is based on the
MMCM and not necessarily based on previous PLL designs. The additional features
supported by the MMCM are:
Direct HPC to BUFR or BUFIO using CLKOUT[0:3]
Inverted clock outputs (CLKOUT[0:3]B)
CLKOUT6
CLKOUT4_CASCADE
Fractional divide for CLKOUT0_DIVIDE_F
Fractional multiply for CLKFBOUT_MULT_F
Fine phase shifting
Dynamic phase shifting
Input multiplexers select the reference and feedback clocks from either the IBUFG, BUFG,
BUFR, BUFH, GTs (CLKIN only), or interconnect (not recommended). Each clock input has
a programmable counter divider (D). The phase-frequency detector (PFD) compares both
phase and frequency of the rising edges of both the input (reference) clock and the
feedback clock. If a minimum High/Low pulse is maintained, the duty cycle is ancillary.
The PFD is used to generate a signal proportional to the phase and frequency between the
two clocks. This signal drives the charge pump (CP) and loop filter (LF) to generate a

Send Feedback
UG472 (v1.12) September 27, 2016
Introduction
reference voltage to the VCO. The PFD produces an up or down signal to the charge pump
and loop filter to determine whether the VCO should operate at a higher or lower
frequency. When VCO operates at too high of a frequency, the PFD activates a down signal,
causing the control voltage to be reduced decreasing the VCO operating frequency. When
the VCO operates at too low of a frequency, an up signal will increase voltage. The VCO
produces eight output phases and one variable phase for fine-phase shifting. Each output
phase can be selected as the reference clock to the output counters (Figure 3-2 and
Figure 3-3). Each counter can be independently programmed for a given customer design.
A special counter, M, is also provided. This counter controls the feedback clock of the
MMCM and PLL, allowing a wide range of frequency synthesis.
In addition to integer divide output counters, MMCMs add a fractional counter for
CLKOUT0 and CLKFBOUT.
Clock
General Lock Detect
Routing Switch Lock
Circuit Lock Monitor
8-phase taps + 1 variable phase tap
CLKIN1 9
D O0 CLKOUT0
CLKIN2 PFD CP LF VCO
Fractional Divide CLKOUT0B
CLKFB CLKOUT1
O1 CLKOUT1B
CLKOUT2
O2 CLKOUT2B
CLKOUT3
O3 CLKOUT3B
CLKOUT4
O4
CLKOUT5
O5
CLKOUT6
O6
M CLKFBOUT
(Fractional Divide) CLKFBOUTB
ug472_c2_02_020712
Figure 3-2: Detailed MMCM Block Diagram

Send Feedback
UG472 (v1.12) September 27, 2016
Clock
General Lock Detect
Routing Switch Lock
Circuit Lock Monitor
8-phase taps
CLKIN1 8
D
CLKIN2 PFD CP LF VCO O0 CLKOUT0
CLKFB O1 CLKOUT1
O2 CLKOUT2
O3 CLKOUT3
O4 CLKOUT4
O5 CLKOUT5
M CLKFBOUT
ug472_c2_03_030211
Figure 3-3: Detailed PLL Block Diagram

Send Feedback
UG472 (v1.12) September 27, 2016
General Usage Description
MMCM and PLL Primitives

The two 7 series FPGAs MMCM primitives, MMCME2_BASE and MMCME2_ADV, are
shown in Figure 3-4.
CLKIN1 CLKOUT0 CLKIN1 CLKOUT0

CLKOUT0B CLKIN2 CLKOUT0B
CLKFBIN CLKOUT1 CLKFBIN CLKOUT1
RST CLKOUT1B RST CLKOUT1B
PWRDWN CLKOUT2 PWRDWN CLKOUT2
CLKOUT2B CLKINSEL
CLKOUT2B
CLKOUT3 DADDR[6:0]
CLKOUT3
CLKOUT3B DI[15:0]
CLKOUT3B
CLKOUT4 DWE
CLKOUT4
CLKOUT5 DEN
CLKOUT5
CLKOUT6 DCLK
CLKOUT6
CLKFBOUT PSINCDEC
CLKFBOUT
CLKFBOUTB PSEN
PSCLK CLKFBOUTB
LOCKED
LOCKED
DO[15:0]
DRDY
PSDONE
CLKINSTOPPED
MMCME2_BASE
CLKFBSTOPPED
MMCME2_ADV
ug472_c2_04_062210
Figure 3-4: MMCM Primitives

Send Feedback
UG472 (v1.12) September 27, 2016
The two 7 series FPGAs PLL primitives, PLLE2_BASE and PLLE2_ADV, are shown in
Figure 3-5.
CLKIN1 CLKOUT0 CLKIN1 CLKOUT0

CLKOUT1 CLKIN2 CLKOUT1
CLKFBIN CLKOUT2 CLKFBIN CLKOUT2
RST CLKOUT3 RST CLKOUT3
PWRDWN CLKOUT4 CLKINSEL CLKOUT4
CLKOUT5 DADDR[4:0] CLKOUT5
CLKFBOUT DI[15:0] CLKFBOUT
DWE
DEN
DCLK
LOCKED LOCKED
PWRDWN
DO[15:0]
DRDY
PLLE2_BASE PLLE2_ADV
UG472_c2_05_112310
Figure 3-5: PLL Primitives
MMCME2_BASE and PLLE2_BASE Primitives

The MMCME2_BASE primitive provides access to the most frequently used features of a
stand-alone MMCM. Clock deskew, frequency synthesis, coarse phase shifting, and duty
cycle programming are available to use with the MMCME2_BASE. The ports are listed in
Table 3-1.
Table 3-1: MMCME2_BASE Ports

Description Ports
Clock Input CLKIN1, CLKFBIN
Control Inputs RST
Clock Output CLKOUT0 to CLKOUT6, CLKOUT0B to CLKOUT3B,
CLKFBOUT, and CLKFBOUTB
Status and Data Outputs LOCKED
Power Control PWRDWN

Send Feedback
UG472 (v1.12) September 27, 2016
The PLLE2_BASE primitive provides access to the most frequently used features of a
stand-alone PLL. Clock deskew, frequency synthesis, coarse phase shifting, and duty cycle
programming are available to use with the PLLE2_BASE. The ports are listed in Table 3-2.
Table 3-2: PLLE2_BASE Ports

Description Port
Clock Input CLKIN1, CLKFBIN
Control Inputs RST
Clock Output CLKOUT0 to CLKOUT5, CLKFBOUT
Status and Data Outputs LOCKED
MMCME2_ADV and PLLE2_ADV Primitive

The MMCME2_ADV primitive provides access to all MMCME2_BASE features plus
additional ports for clock switching, access to the Dynamic Reconfiguration Port (DRP), as
well as dynamic fine-phase shifting. The ports are listed in Table 3-3.
Table 3-3: MMCME2_ADV Ports

Description Ports
Clock Input CLKIN1, CLKIN2, CLKFBIN, DCLK, PSCLK
Control and Data Input RST, CLKINSEL, DWE, DEN, DADDR, DI, PSINCDEC, PSEN
Clock Output CLKOUT0 to CLKOUT6, CLKOUT0B to CLKOUT3B,
CLKFBOUT, and CLKFBOUTB
Status and Data Output LOCKED, DO, DRDY, PSDONE, CLKINSTOPPED,
CLKFBSTOPPED
The PLLE2_ADV primitive provides access to all PLLE2_BASE features plus additional
ports for clock switching, and access to the Dynamic Reconfiguration Port. The ports are
listed in Table 3-4.
Table 3-4: PLLE2_ADV Ports

Description Port
Clock Input CLKIN1, CLKIN2, CLKFBIN, DCLK
Control and Data Input RST, CLKINSEL, DWE, DEN, DADDR, DI
Clock Output CLKOUT0 to CLKOUT5, and CLKFBOUT
Status and Data Output LOCKED, DO, DRDY

Send Feedback
UG472 (v1.12) September 27, 2016
The 7 series FPGAs MMCM and PLL are mixed-signal blocks designed to support clock
network deskew, frequency synthesis, and jitter reduction. These three modes of operation
are discussed in more detail within this section. The Voltage Controlled Oscillator (VCO)
operating frequency can be determined by using the following relationship:
M
F VCO = F CLKIN ----- Equation 3-1
D
M
F OUT = F CLKIN --------------- Equation 3-2
DO
where the M, D, and O counters are shown in Figure 3-2. The value of M corresponds to the
CLKFBOUT_MULT_F setting, the value of D to the DIVCLK_DIVIDE, and O to the
CLKOUT_DIVIDE.
The seven O counters can be independently programmed. For example, O0 can be
programmed to do a divide-by-two while O1 is programmed for a divide by three. The
only constraint is that the VCO operating frequency must be the same for all the output
counters since a single VCO drives all the counters.
Clock Network Deskew

In many cases, designers do not want to incur the delay on a clock network in their I/O
timing budget therefore they use a MMCM/PLL to compensate for the clock network
delay. 7 series FPGAs support this feature. A clock output matching the reference clock
CLKIN frequency (always CLKFBOUT) is connected to a BUFG in the same half of the
device and fed back to the CLKFBIN feedback pin of the MMCM/PLL. The remaining
outputs can still be used to divide the clock down for additionally synthesized frequencies.
In this case, all output clocks have a defined phase relationship to the input reference clock.
The CLKOUT0CLKOUT3 of either the MMCM or PLL can be used to cascade to other
MMCMs/PLLs. However, there is a phase offset on the output clocks between cascaded
MMCMs/PLLs.
Frequency Synthesis Only Using Integer Divide

The MMCMs and PLLs can also be used for stand-alone frequency synthesis. In this
application, the MMCM/PLL is not used to deskew a clock network, but rather generate
an output clock frequency for other blocks. In this mode, the MMCM/PLL feedback paths
are internal, which keeps all the routing local, minimizing the jitter. Figure 3-6 shows the
MMCM configured as a frequency synthesizer. In this example, an external 33 MHz
reference clock is available. The reference clock can be a crystal oscillator or the output of
another MMCM. Setting the M counter to 32 makes the VCO oscillate at 1056 MHz
(33 MHz x 32). The MMCM outputs are programmed to provide (for example) a 528 MHz
processor clock, a 264 MHz gasket clock, a 176 MHz clock, a 132 MHz memory interface
clock, a 66 MHz interface, and a 33 MHz interface. In this example, there are no required
phase relationships between the reference clock and the output clocks, but there are
required relationships between the output clocks.

Send Feedback
UG472 (v1.12) September 27, 2016
33 MHz
Reference PFD, CP, Processor
D=1 O0 = 2
Clock LF, VCO
O1 = 4 Gasket
M = 32
O2 = 6 CLB/Fabric
O3 = 8 Memory Interface
O4 = 16 66 MHz Interface
O5 = 32 33 MHz Interface
O6 = 1 not used
ug472_c2_06_062711
Figure 3-6: MMCM as a Frequency Synthesizer
Frequency Synthesis Using Fractional Divide in the MMCM

7 series FPGAs support fractional (non-integer) divides in the CLKOUT0 output path. The
resolution of the fractional divide is 1/8 or 0.125, effectively increasing the number of
synthesizeable frequencies by a factor of eight. For example, if the CLKIN frequency is
100 MHz and the M divide value is set to 8, then the VCO frequency is 800 MHz.
CLKOUT0 can be used to further fractionally divide the 800 MHz VCO frequency (for
example, CLKOUT0_DIVIDE = 2.5 resulting in a 320 MHz output frequency).
When using the fractional divider, the duty cycle is not programmable for outputs used in
the fractional mode.
Jitter Filter
MMCMs and PLLs reduce the jitter inherent on a reference clock. The MMCM and PLL can
be instantiated as a standalone function to support filtering jitter from an external clock
before it is driven into the another block. As a jitter filter, it is usually assumed that the
MMCM and PLL will act as a buffer and regenerates the input frequency on the output (for
example, FIN = 100 MHz, FOUT = 100 MHz). In general, greater jitter filtering is possible by
using the MMCM attribute BANDWIDTH set to Low. Setting the BANDWIDTH to Low
can incur an increase in the static offset of the MMCM.
Limitations
The MMCM and the PLL have some restrictions that must be adhered to. These are
summarized in the MMCM and the PLL electrical specifications in the 7 Series FPGA Data
Sheets (DS181, DS182, and DS183). In general, the major limitations are VCO operation
range, input frequency, duty cycle programmability, and phase shift. In addition, there are
connectivity limitations to other clocking elements (pins, GTs, and clock buffers) as
outlined in Appendix B, Clocking Resources and Connectivity Variations per Clock
Region. Cascading MMCMs/PLLs can only occur with adjacent CMTs.
VCO Operating Range

The minimum and maximum VCO operating frequencies are defined in the electrical
specification of the 7 Series FPGA Data Sheets DS181, DS182, and DS183). These values can
also be extracted from the speed specification.

Send Feedback
UG472 (v1.12) September 27, 2016
Minimum and Maximum Input Frequency

The minimum and maximum CLKIN input frequency are defined in the electrical
specification of the 7 Series FPGA Data Sheets (DS181, DS182, and DS183).
Duty Cycle Programmability
Only discrete duty cycles are possible given a VCO operating frequency. Depending on the
CLKOUT_DIVIDE value, a minimum and maximum range is possible with a step size that
is also depending on the CLKOUT_DIVIDE value. The Clocking Wizard tool gives the
possible values for a given CLKOUT_DIVIDE.
Phase Shift
In many cases, there needs to be a phase shift between clocks. The MMCM has multiple
options to implement phase shifting. The PLL also has the basic static phase shift
capability. Static phase shifting can be achieved by selecting one of the eight VCO output
phases with additional fine phase shifting available in the CLKOUT output counters
depending on the CLKOUT divide value. In 7 series FPGAs there is also an interpolated
phase shifting capability in either fixed or dynamic mode. The MMCM phase shifting
capabilities are very powerful which can lead to complex scenarios. By using the Clocking
Wizard, the allowable phase shift values are determined based on the MMCM
configuration settings.
Static Phase Shift Mode
The static phase shift (SPS) resolution in time units is defined as:
1 D
SPS = ------------------period or ------------------ period Equation 3-3
8F VCO 8MF IN
Since the VCO can provide eight phase shifted clocks at 45 each; always providing
possible settings for 0, 45, 90, 135, 180, 225, 270, and 315 of phase shift. The higher
the VCO frequency is, the smaller the phase-shift resolution. Since the VCO has a distinct
operating range, it is possible to bound the phase-shift resolution using from
1 1
---------------------------- to ------------------------------ period.
8F VCOMIN 8F VCOMAX
Each CLKOUT output counter is individually programmable allowing each to have an

additional phase-shift resolution in degrees based on the phase of the VCO selected and
the CLKOUT counter divide value. The granularity of the CLKOUT phase-shift value can
be calculated as 45/CLKOUT_DIVIDE value. The maximum phase-shift range is also
determined by the CLKOUT_DIVIDE value. The maximum phase shift is 360 when
CLKOUT_DIVIDE 64. When CLKOUT_DIVIDE is > 64, the maximum phase shift is:
Maximum Phase Shift = ----------------------------------------------------- 360 + ( 7 Phase Shift Value )
63
Equation 3-4
CLKOUT_ DIVIDE
It is possible to phase shift the CLKFBOUT feedback clock. In that case all CLKOUT output
clocks are negatively phase shifted with respect to CLKIN.
The two fractional counters (CLKFBOUT and CLKOUT0) also have static phase shift
capability. A phase shift step is defined as:
360 45
SPS ( frac ) = ----------------------------------------------------------------------or ------------------------------------------------------------- Equation 3-5
8 fractional_divide_value fractional_divide_value
For example, if the fractional divide value is 2.125, then a static phase shift step is
360/(2.125 x 8) = 21.176 degrees.

Send Feedback
UG472 (v1.12) September 27, 2016
Interpolated Fine Phase Shift in Fixed or Dynamic Mode in the MMCM

Interpolated fine phase shift (IFPS) mode in the MMCM has linear shift behavior
independent of the CLKOUT_DIVIDE value and the phase shift resolution only depends
on the VCO frequency. In this mode the output clocks can be rotated 360 round robin
1
in linear increments of ---------------------- .
56F VCO
If the VCO runs at 600 MHz, then the phase resolution is approximately (rounded) 30 ps
and at 1.6 GHz is approximately (rounded) 11 ps.
The phase shift value can be programmed as a fixed value set during configuration or a
dynamic increment/decrement under application control after configuration. The
dynamic phase shift is controlled by the PS interface of the MMCME2_ADV. This
phase-shift mode equally affects all CLKOUT output clocks that are selected for this mode
by setting the USE_FINE_PS attribute to TRUE. In interpolated fine phase-shift mode, a
clock must always be connected to the PSCLK pin of the MMCM. Regardless of the
interpolated fine phase-shift mode (fixed or dynamic) a clock is in, the clock must always
be connected to the PSCLK pin of the MMCM. Each individual CLKOUT counter can
independently either select the interpolated phase shift, the previously described static
phase-shift mode, or none. Fractional divide is not allowed in either fixed or dynamic
interpolated fine phase-shift mode. Fixed or dynamic phase shifting of the feedback path
will result in a negative phase shift of all output clocks with respect to CLKIN. The
dynamic phase-shift interface cannot be used when the phase-shift mode is set to fixed.
Dynamic Phase Shift Interface in the MMCM

The MMCME2_ADV primitive provides three inputs and one output for dynamic
fine-phase shifting. Each CLKOUT and the CLKFBOUT divider can be individually
selected for phase shifting. The attributes CLKOUT[0:6]_USE_FINE_PS and
CLKFBOUT_USE_FINE_PS select the output clocks to be dynamically phase shifted. The
dynamic phase-shift amount is common to all the output clocks selected.
The variable phase shift is controlled by the PSEN, PSINCDEC, PSCLK, and PSDONE
ports (Figure 3-7). After the MMCM locks, the initial phase is determined by the
CLKOUT_PHASE attribute. Most commonly, no initial phase shift is selected. The phase of
the MMCM output clock(s) increments/decrements according to the interaction of PSEN,
PSINCDEC, PSCLK, and PSDONE from the initial or previously performed dynamic
phase shift. PSEN, PSINCDEC, and PSDONE are synchronous to PSCLK. When PSEN is
asserted for one PSCLK clock period, a phase-shift increment/decrement is initiated.
When PSINCDEC is High, an increment is initiated and when PSINCDEC is Low, a
decrement is initiated. Each increment adds to the phase shift of the MMCM clock outputs
by 1/56th of the VCO period. Similarly, each decrement decreases the phase shift by
1/56th of the VCO period. PSEN must be active for one PSCLK period. PSDONE is High
for exactly one clock period when the phase shift is complete. The number of PSCLK cycles
is deterministic and is always 12 PSCLK cycles. After initiating the phase shift by asserting
PSEN, the MMCM output clocks move from their original phase shift to an increment/
decrement phase shift. The completion of the increment or decrement is signaled when
PSDONE asserts High. After PSDONE has pulsed High, another increment/decrement
can be initiated. There is no maximum phase shift or phase-shift overflow. An entire clock
period (360 degrees) can always be phase shifted regardless of frequency. When the end of
the period is reached, the phase shift wraps around round-robin style.

Send Feedback
UG472 (v1.12) September 27, 2016
,
PSCLK
PSEN
PSDONE
PSINCDEC
ug472_c2_07_061710
Figure 3-7: Phase-Shift Timing Diagram
MMCM Counter Cascading

The CLKOUT6 divider (counter) can be cascaded with the CLKOUT4 divider. This
provides a capability to have an output divider that is larger than 128. CLKOUT6 feeds the
input of the CLKOUT4 divider. There is a static phase offset between the output of the
cascaded divider and all other output dividers.
MMCM/PLL Programming
Programming of the MMCM/PLL must follow a set flow to ensure configuration that
guarantees stability and performance. This section describes how to program the MMCM/
PLL based on certain design requirements. A design can be implemented in two ways,
directly through the GUI interface (the Clocking Wizard) or implementing the MMCM/
PLL through instantiation. Regardless of the method selected, the following information is
necessary to program the MMCM/PLL:
Reference clock period
Output clock frequencies (up to seven maximum)
Output clock duty cycle (default is 50%)
Output clock phase shift in number of degrees relative to the original 0 phase of the
clock.
Desired bandwidth of the MMCM/PLL (default is OPTIMIZED and the bandwidth is
chosen in software)
Compensation mode (automatically determined by the software)
Reference clock jitter in UI (that is, a percentage of the reference clock period)
Determine the Input Frequency

The first step is to determine the input frequency. This allows all possible output
frequencies to be determined by using the minimum and maximum input frequencies to
define the D counter range, the VCO operating range to determine the M counter range,
and the output counter range. There can be a very large number of frequencies. When
using integer divides, in the worst case, there will be 106 x 64 x 136 = 868,363 possible
combinations. In reality, the total number of different frequencies is less since the entire
range of the M and D counters cannot be realized and there is overlap between the various
settings.

Send Feedback
UG472 (v1.12) September 27, 2016
As an example, consider FIN = 100 MHz. If the minimum PFD frequency is 10 MHz, then D
can only go from 1 to 10.
D = 1, M can only have values from four to 16.
D = 2, M can only have values from eight to 32.
D = 4, M can only have values from 16 to 64.
In addition, D = 1 M = 4 is a subset of D = 2 M = 8, D = 4 M = 16, and D = 8 M = 32
allowing these cases to be dropped. For this case, only D = 1, 3, 5, 6, 7, and 9 are considered
since all other D values are subsets of these cases. This drastically reduces the number of
possible output frequencies. The output frequencies are sequentially selected. The desired
output frequency should be checked against the possible output frequencies generated.
Once the first output frequency is determined, an additional constraint can be imposed on
the values of M and D. This can further limit the possible output frequencies for the second
output frequency. Continue this process until all the output frequencies are selected.
The constraints used to determine the allowed M and D values are shown in the following
equations:
f IN
D MIN = roundup ------------------------ Equation 3-6
f PFD MAX
f IN
D MAX = rounddown ----------------------- Equation 3-7
f PFD MIN
f VCOMIN
M MIN = roundup ---------------------- D MIN Equation 3-8
f IN
f VCOMAX
M MAX = rounddown ------------------------ D MAX Equation 3-9
f IN
Determine the M and D Values

Determining the input frequency can result in several possible M and D values. The next
step is to determine the optimum M and D values. The starting M value is first determined.
This is based off the VCO target frequency, the ideal operating frequency of the VCO.
D MIN f VCOMAX
M IDEAL = -------------------------------------------- Equation 3-10
f IN
The goal is to find the M value closest to the ideal operating point of the VCO. The
minimum D value is used to start the process. The goal is to make D and M values as small
as possible while keeping VCO as high as possible.

Send Feedback
UG472 (v1.12) September 27, 2016
MMCM Ports
Table 3-5 summarizes the MMCM ports. Table 3-7 lists the MMCM attributes.
Table 3-5: MMCM Ports(1)

Pin Name I/O Pin Description
CLKIN1 Input General clock input. See CLKIN1 Primary Reference Clock Input.
Secondary clock input for the MMCM reference clock. See CLKIN2 Secondary
CLKIN2 Input
Clock Input.
CLKFBIN Input Feedback clock input. See CLKFBIN Feedback Clock Input.
Signal controls the state of the clock input MUX, High = CLKIN1, Low = CLKIN2.
CLKINSEL Input Dynamically switches the MMCM reference clock. See CLKINSEL Clock Input
Select.
Asynchronous reset signal. The RST signal is an asynchronous reset for the MMCM.
The MMCM will synchronously re-enable itself when this signal is released (that is,
RST Input
MMCM re-enabled). A reset is required when the input clock conditions change (for
example, frequency). See RST Asynchronous Reset Signal.
PWRDWN Input Powers down instantiated but unused MMCMs. See PWRDWN Power Down.
The dynamic reconfiguration address (DADDR) input bus provides a
DADDR[6:0] Input reconfiguration address for the dynamic reconfiguration. When not used, all bits
must be assigned zeros. See DADDR[6:0] Dynamic Reconfiguration Address.
The dynamic reconfiguration data input (DI) bus provides reconfiguration data.
DI[15:0] Input When not used, all bits must be set to zero. See DI[15:0] Dynamic Reconfiguration
Data Input.
The dynamic reconfiguration write enable (DWE) input pin provides the write
DWE Input enable control signal to write the DI data into the DADDR address. When not used,
it must be tied Low. See DWE Dynamic Reconfiguration Write Enable.
The dynamic reconfiguration enable (DEN) provides the enable control signal to
access the dynamic reconfiguration feature. When the dynamic reconfiguration
DEN Input
feature is not used, DEN must be tied Low. See DEN Dynamic Reconfiguration
Enable Strobe.
The DCLK signal is the reference clock for the dynamic reconfiguration port. See
DCLK Input
DCLK Dynamic Reconfiguration Reference Clock.
PSCLK Input Phase shift clock. See PSCLK Phase-Shift Clock.
PSEN Input Phase shift enable. See PSEN Phase-Shift Enable.
Phase shift increment/decrement control. See PSINCDEC Phase-Shift Increment/
PSINCDEC Input
Decrement Control.
User configurable clock outputs (0 through 6) that can be divided versions of the
VCO phase outputs (user controllable) from 1 (bypassed) to 128. The output clocks
are phase aligned to each other (unless phase shifted) and aligned to the input clock
CLKOUT[0:6] Output with a proper feedback configuration.
Direct HPC connections to BUFR/BUFIO are only supported on CLKOUT[0:3]. See
CLKOUT[0:6] Output Clocks.
CLKOUT[0:3]B Output Inverted CLKOUT[0:3]. See CLKOUT[0:3]B Inverted Output Clocks.

Send Feedback
UG472 (v1.12) September 27, 2016
Table 3-5: MMCM Ports(1) (Contd)

Dedicated MMCM feedback output. See CLKFBOUT Dedicated MMCM and PLL
CLKFBOUT Output
Feedback Output.
CLKFBOUTB Output Inverted CLKFBOUT. See CLKFBOUTB Inverted CLKFBOUT.
Status pin indicating that the input clock has stopped. See CLKINSTOPPED Input
CLKINSTOPPED Output
Clock Status.
Status pin indicating that the feedback clock has stopped. See CLKFBSTOPPED
CLKFBSTOPPED Output
Feedback Clock Status.
An output from the MMCM that indicates when the MMCM has achieved phase
alignment within a predefined window and frequency matching within a
predefined PPM range. The MMCM automatically locks after power on. No extra
LOCKED Output
reset is required. LOCKED will be deasserted if the input clock stops or the phase
alignment is violated (for example, input clock phase shift). The MMCM must be
reset after LOCKED is deasserted.
The dynamic reconfiguration output bus provides MMCM data output when using
DO[15:0] Output
dynamic reconfiguration. See DO[15:0] Dynamic Reconfiguration Output Bus.
The dynamic reconfiguration ready output (DRDY) provides the response to the
DRDY Output DEN signal for the MMCMs dynamic reconfiguration feature. See DRDY Dynamic
Reconfiguration Ready.
PSDONE Output Phase shift done. See PSDONE Phase Shift Done.
Notes:
1. All control and status signals except PSINCDEC are active-High.
PLL Ports
Table 3-6 summarizes the PLL ports.
Table 3-6: PLL Ports

CLKIN1 Input General clock input.
CLKIN2 Input Secondary clock input to dynamically switch the PLL reference clock.
CLKFBIN Input Feedback clock input.
Signal controls the state of the input multiplexer, High = CLKIN1, Low = CLKIN2.
CLKINSEL Input
Dynamically switches the PLL reference clock. See CLKINSEL Clock Input Select.
Asynchronous reset signal. The RST signal is an asynchronous reset for the PLL. The
PLL will synchronously re-enable itself when this signal is released (that is, PLL
RST Input
re-enabled). A reset is required when the input clock conditions change (for
example, frequency).
PWRDWN Input Powers down instantiated but unused PLL. See PWRDWN Power Down.
The dynamic reconfiguration address (DADDR) input bus provides a
DADDR[6:0] Input reconfiguration address for the dynamic reconfiguration. When not used, all bits
must be assigned zeros.

Send Feedback
UG472 (v1.12) September 27, 2016
Table 3-6: PLL Ports (Contd)

The dynamic reconfiguration data input (DI) bus provides reconfiguration data.
DI[15:0] Input
When not used, all bits must be set to zero.
The dynamic reconfiguration write enable (DWE) input pin provides the write
DWE Input enable control signal to write the DI data into the DADDR address. When not used,
it must be tied Low.
The dynamic reconfiguration enable (DEN) provides the enable control signal to
DEN Input access the dynamic reconfiguration feature. When the dynamic reconfiguration
feature is not used, DEN must be tied Low.
DCLK Input The DCLK signal is the reference clock for the dynamic reconfiguration port.
User configurable clock outputs (0 through 5) that can be divided versions of the
CLKOUT[0:5](1) Output VCO phase outputs (user controllable) from 1 (bypassed) to 128. The input clock and
output clocks are phase aligned.
CLKFBOUT Output Dedicated PLL feedback output.
An output from the PLL that indicates when the PLL has achieved phase alignment
within a predefined window and frequency matching within a predefined PPM
range. The PLL automatically locks after power on, no extra reset is required.
LOCKED Output
LOCKED will be deasserted if the input clock stops or the phase alignment is
violated (for example, input clock phase shift). The PLL must be reset after LOCKED
is deasserted.
The dynamic reconfiguration output bus provides PLL data output when using
DO[15:0] Output
dynamic reconfiguration.
The dynamic reconfiguration ready output (DRDY) provides the response to the
DRDY Output
DEN signal for the PLLs dynamic reconfiguration feature.
MMCM and PLL Port Descriptions

CLKIN1 Primary Reference Clock Input
CLKIN1 can be driven by SRCC or MRCC I/O directly within the same clock region, SRCC
or MRCC I/O through the CMT backbone in a vertically adjacent clock region, BUFG,
BUFR, BUFH, interconnect (not recommended), or directly by a high-speed serial
transceiver. When the clock input is coming from another CMT block for cascading CMT
functions, only CLKOUT[0:3] can be used.
CLKIN2 Secondary Clock Input

CLKIN2 is a secondary clock input that is used to dynamically switch the MMCM/PLL
reference clock. CLKIN2 can be driven by SRCC or MRCC I/O directly within the same
clock region, SRCC or MRCC I/O through the CMT backbone in a vertically adjacent clock
region, BUFG, BUFR, BUFH, interconnect (not recommended), or directly by a high-speed
serial transceiver.
CLKFBIN Feedback Clock Input

Must be connected either directly to the CLKFBOUT for internal feedback or IBUFG
(through a clock-capable pin for external deskew), BUFG, BUFH, or interconnect (not
recommended). For external clock alignment, the feedback path clock buffer type should

Send Feedback
UG472 (v1.12) September 27, 2016
match the forward clock buffer type with the exception of BUFR. BUFR cannot be
compensated for.
CLKFBOUT Dedicated MMCM and PLL Feedback Output

For possible configuration see MMCM and PLL Use Models. CLKFBOUT can also drive
logic similar to the CLK0 of the DCM in Virtex-5 FPGAs.
CLKFBOUTB Inverted CLKFBOUT

This signal should not be used for feedback. It provides an additional, inverted
CLKFBOUT output clock. CLKFBOUTB can drive logic similar to the CLK180 clock of the
DCM in Virtex-5 FPGAs. Not available in the PLL.
CLKINSEL Clock Input Select

The CLKINSEL signal controls the state of the clock input MUXes, High = CLKIN1,
Low = CLKIN2 (see Reference Clock Switching). The MMCM/PLL must be held in RESET
during clock switchover.
RST Asynchronous Reset Signal

The RST signal is an asynchronous reset for the MMCM/PLL. The MMCM/PLL will be
synchronously re-enabled when this signal is deasserted.
PWRDWN Power Down

Powers down instantiated but currently unused MMCMs/PLLs. This mode can be used to
save power for temporarily inactive portions of the design and/or MMCMs/PLLs that are
not active in certain system configurations. No MMCM/PLL power is consumed in this
mode.
DADDR[6:0] Dynamic Reconfiguration Address

The dynamic reconfiguration address (DADDR) input bus provides a reconfiguration
address for the dynamic reconfiguration. The address value on this bus specifies the 16
configuration bits that are written or read with the next DCLK cycle. When not used, all
bits must be assigned zeros.
DI[15:0] Dynamic Reconfiguration Data Input

The dynamic reconfiguration data input (DI) bus provides reconfiguration data. The value
of this bus is written to the configuration cells. The data is presented in the cycle that DEN
and DWE are active. The data is captured in a shadow register and written at a later time.
DRDY indicates when the DRP port is ready to accept another write. When not used, all
bits must be set to zero.
DWE Dynamic Reconfiguration Write Enable

The dynamic reconfiguration write enable (DWE) input pin provides the write/read
enable control signal to write the DI data into or read the DO data from the DADDR
address. When not used, it must be tied Low.
DEN Dynamic Reconfiguration Enable Strobe

The dynamic reconfiguration enable strobe (DEN) provides the enable control signal to
access the dynamic reconfiguration feature and enables all DRP port operations. When the
dynamic reconfiguration feature is not used, DEN must be tied Low.

Send Feedback
UG472 (v1.12) September 27, 2016
DCLK Dynamic Reconfiguration Reference Clock

The DCLK signal is the reference clock for the dynamic reconfiguration port. The rising
edge of this signal is the timing reference for all other port signals. The setup time is
specified in the data sheet. There is no hold time requirement for the other input signals
relative to the rising edge of the DCLK. The pin can be drive by an IBUF, IBUFG, BUFG,
BUFR, or BUFH. There are no dedicated connections to this clock input.
PSCLK Phase-Shift Clock

This input pin provides the source clock for the dynamic phase-shift interface. All other
inputs are synchronous to the positive edge of this clock. The pin can be drive by an IBUF,
IBUFG, BUFG, BUFR, or BUFH. There are no dedicated connections to this clock input.
Not available in the PLL.
PSEN Phase-Shift Enable

A dynamic (variable) phase-shift operation is initiated by synchronously asserting this
signal. It must be activated for one cycle of the PSCLK. After initiating a phase-shift the
phase is gradually shifted until a High pulse on PSDONE indicates that the operation is
complete. There are no glitches or sporadic changes during the operation. From the start to
the end of the operation the phase is shifted in a continuous analog manner. Not available
in the PLL.
PSINCDEC Phase-Shift Increment/Decrement Control

This input signal synchronously indicates if the dynamic phase shift is an increment or
decrement operation (positive or negative phase-shift). PSENCDEC is asserted High for
increment and Low for decrement. There is no phase-shift overflow associated with the
dynamic phase shift operation. If more 360 or more are shifted, then the phase will wrap
around starting at the original phase. Not available in the PLL.
CLKOUT[0:6] Output Clocks

These user-configurable clock outputs (CLKOUT0 through CLKOUT6 for the MMCM or
CLKOUT0 through CLKOUT5 for the PLL) can be divided versions of the VCO phase
outputs (user controllable) from 1 (bypassed) to 128. The input clock and output clocks can
be phase aligned.
When used with BUFR or BUFIO, only the MMCM can directly connect to the HPC from
the clock outputs CLKOUT0 through CLKOUT3. Additionally, CLKOUT0 through
CLKOUT3 can connect to the CMT backbone, for cascading MMCMs and PLLs. Similar to
driving MMCMs and PLLs from the CCIO pins to adjacent regions (see Clock-Capable
Inputs), cascading uses some of the limited resources available in the CMT backbone to
connect clocking resources directly in adjacent regions. A phase offset between the
cascaded elements within the same column will also result.
For possible configurations see MMCM and PLL Use Models. In the MMCM, CLKOUT0
and CLKFBOUT can be used in fractional divide mode. All CLKOUT outputs can be used
in non-fractional mode to provide a static or dynamic phase shift. In fractional mode, only
fixed phase-shift is allowed. See Static Phase Shift Mode for more information.
CLKOUT[0:3]B Inverted Output Clocks

Inverted (180 phase shift) of CLKOUT[0:3]. Not available in the PLL.

Send Feedback
UG472 (v1.12) September 27, 2016
CLKINSTOPPED Input Clock Status

Status pin indicating that the input clock has stopped. This signal is asserted within one
clock cycle of clock stoppage. The signal is deasserted after the clock has restarted and
LOCKED is achieved or the clock is switched to the alternate clock input and the MMCM
has re-locked. Not available in the PLL.
CLKFBSTOPPED Feedback Clock Status

Status pin indicating that the feedback clock has stopped. This signal is asserted within one
clock cycle of clock stoppage. The signal is deasserted after the feedback clock has restarted
and the MMCM has re-locked. Not available in the PLL.
LOCKED
An output from the MMCM/PLL used to indicate when the MMCM/PLL have achieved
phase and frequency alignment of the reference clock and the feedback clock at the input
pins. Phase alignment is within a predefined window and frequency matching within a
predefined PPM range. The MMCM automatically locks after power on, no extra reset is
required. LOCKED will be deasserted within one PFD clock cycle if the input clock stops,
the phase alignment is violated (for example, input clock phase shift) or the frequency has
changed. The MMCM/PLL must be reset when LOCKED is deasserted. The clock outputs
should not be used prior to the assertion of LOCKED.
DO[15:0] Dynamic Reconfiguration Output Bus

The dynamic reconfiguration output bus provides MMCM data output when using
dynamic reconfiguration. If DWE is inactive while DEN is active at the rising edge of
DCLK, then this bus holds the content of the configuration cells addressed by DADDR.
The DO bus must be captured on the rising edge of DCLK when DRDY is active. The DO
bus value is held until the next DRP operation.
DRDY Dynamic Reconfiguration Ready

The dynamic reconfiguration ready output (DRDY) provides the response to the DEN
signal for the MMCMs dynamic reconfiguration feature. This signal indicates that a DEN/
DCLK operation has completed.
PSDONE Phase Shift Done

The phase-shift done output signal is synchronous to the PSCLK. When the current
phase-shift operation is completed, the PSDONE signal is asserted for one clock cycle
indicating that a new phase-shift cycle can be initiated. Not available in the PLL.
MMCM Attributes
Table 3-7 lists the attributes for the MMCME2_BASE and MMCME2_ADV primitives.
Table 3-7: MMCM Attributes

Attribute Type Allowed Values Default Description
BANDWIDTH String HIGH OPTIMIZED Specifies the MMCM
LOW programming algorithm affecting
OPTIMIZED the jitter, phase margin and other
characteristics of the MMCM.

Send Feedback
UG472 (v1.12) September 27, 2016
Table 3-7: MMCM Attributes (Contd)

CLKOUT[1:6]_DIVIDE Integer 1 to 128 1 Specifies the amount to divide the
associated CLKOUT clock output
CLKOUT[0]_DIVIDE_F(2) Integer 1 to 128 or 1 if a different frequency is desired.
or 2.000 to 128.000 in This number in combination with
Real increments of 0.125 the CLKFBOUT_MULT_F and
DIVCLK_DIVIDE values will
determine the output frequency.
CLKOUT[0:6]_PHASE Real 360.000 to 360.000 in 0.0 Allows specification of the output
increments of phase relationship of the
1/56 the FVCO and/or associated CLKOUT clock output
increments depending in number of degrees offset (that is,
on CLKOUT_DIVIDE. 90 indicates a 90 or cycle offset
phase offset while 180 indicates a
180 offset or cycle phase offset).
CLKOUT[0:6]_ Real 0.01 to 0.99 0.50 Specifies the Duty Cycle of the
DUTY_CYCLE associated CLKOUT clock output
in percentage (that is, 0.50 will
generate a 50% duty cycle).
CLKFBOUT_MULT_F(2) Integer 2 to 64 or 5 Specifies the amount to multiply
or 2.000 to 64.000 in all CLKOUT clock outputs if a
Real increments of 0.125 different frequency is desired. This
number, in combination with the
associated CLKOUT#_DIVIDE
value and DIVCLK_DIVIDE value,
will determine the output
frequency.
DIVCLK_DIVIDE Integer 1 to 106 1 Specifies the division ratio for all
output clocks with respect to the
input clock. Effectively divides the
CLKIN going into the PFD.
CLKFBOUT_PHASE Real 0.00 to 360.00 0.0 Specifies the phase offset in
degrees of the clock feedback
output. Shifting the feedback clock
results in a negative phase shift of
all output clocks to the MMCM.
REF_JITTER1 Real 0.000 to 0.999 0.010 This attribute is for simulation
REF_JITTER2 purposes only. Simulation checks
against the maximum allowed
value. If known, then the value
provided should be specified in
terms of the unit interval (UI) (the
maximum peak to peak value) of
the expected jitter on the input
clock.

Send Feedback
UG472 (v1.12) September 27, 2016

CLKIN1_PERIOD Real 0.938 to 100.000 0.000 Specifies the input period in ns to
the MMCM CLKIN1 input.
Resolution is down to the ps. This
information is mandatory and
must be supplied.
the MMCM CLKIN2 input.
Resolution is down to the ps. This
information is mandatory and
must be supplied.
CLKFBOUT_USE_FINE_PS Boolean FALSE, TRUE FALSE CLKFBOUT counter variable fine
phase shift enable.
CLKOUT0_USE_FINE_PS Boolean FALSE, TRUE FALSE CLKOUT0 counter variable fine
phase shift enable.
CLKOUT0_DIVIDE must be an
integer and therefore fractional
divide is not allowed.
CLKOUT[1:6]_USE_FINE_PS Boolean FALSE, TRUE FALSE CLKOUT[1:6] variable fine phase
shift enable.
STARTUP_WAIT Boolean FALSE, TRUE FALSE Wait during the configuration
start-up cycle for the MMCM to
lock.
CLKOUT4_CASCADE Boolean FALSE, TRUE FALSE Cascades the output divider
(counter) CLKOUT6 into the input
of the CLKOUT4 divider for an
output clock divider that is greater
than 128, effectively providing a
total divide value of 16,384.

Send Feedback
UG472 (v1.12) September 27, 2016

(1)
COMPENSATION String ZHOLD , ZHOLD Clock input compensation. Must
EXTERNAL, be set to ZHOLD. Defines how the
INTERNAL, MMCM feedback is configured.
BUF_IN ZHOLD: Indicates the MMCM is
configured to provide a negative
hold time at the I/O registers.
EXTERNAL: Indicates a network
external to the FPGA is being
compensated.
INTERNAL: Indicates the MMCM
is using its own internal feedback
path so no delay is being
compensated.
BUF_IN: Indicates that the
configuration does not match with
the other compensation modes and
no delay will be compensated. This
is the case if a clock input is driven
by a BUFG/BUFH/BUFR or GTX/
GTH/GTP.
SS_EN Boolean FALSE, TRUE FALSE Enables spread spectrum
generation.
SS_MODE String DOWN_LOW, CENTER_HIGH Controls the spread spectrum
DOWN_HIGH, frequency deviation and the
CENTER_LOW, spread type.
CENTER_HIGH
SS_MOD_PERIOD Integer 400040000 10000 Specifies the spread spectrum
modulation period (ns).
Notes:
1. The COMPENSATION attribute values are documented for informational purpose only. The ISE or Vivado design tools
automatically select the appropriate compensation based on circuit topology. Do not manually select a compensation value, leave
the attribute at the default value.
2. The ISE or Vivado design tools will round up or down to the nearest multiple of 0.125 if the value is not specified as an exact 1/8th
fraction.

Send Feedback
UG472 (v1.12) September 27, 2016
PLL Attributes
Table 3-8 lists the attributes for the PLLE2_BASE and PLLE2_ADV primitives.
Table 3-8: PLL Attributes

COMPENSATION String ZHOLD(1), ZHOLD Clock input compensation. Must
EXTERNAL, INTERNAL, be set to ZHOLD. Defines how the
BUF_IN PLL feedback is configured.
ZHOLD: Indicates the PLL is
configured to provide a negative
hold time at the I/O registers.
EXTERNAL: Indicates a network
external to the FPGA is being
compensated.
INTERNAL: Indicates the MMCM
is using its own internal feedback
path so no delay is being
compensated.
BUF_IN: Indicates that the
configuration does not match with
the other compensation modes
and no delay will be compensated.
This is the case if a clock input is
driven by a BUFG/BUFH/BUFR
or GTX/GTH/GTP.
BANDWIDTH String HIGH OPTIMIZED Specifies the PLL programming
LOW algorithm affecting the jitter, phase
OPTIMIZED margin and other characteristics of
the PLL.
CLKOUT[0:5]_DIVIDE Integer 1 to 128 1 Specifies the amount to divide the
if a different frequency is desired.
This number in combination with
the CLKFBOUT_MULT and
DIVCLK_DIVIDE values will
determine the output frequency.
CLKOUT[0:5]_PHASE Real 360.0 to 360.0 0.0 Allows specification of the output
phase relationship of the
in number of degrees offset (that
is, 90 indicates a 90 or cycle
offset phase offset while 180
indicates a 180 offset or cycle
phase offset).
CLKOUT[0:5]_ Real 0.01 to 0.99 0.50 Specifies the Duty Cycle of the
DUTY_CYCLE associated CLKOUT clock output
in percentage (that is, 0.50 will
generate a 50% duty cycle).

Send Feedback
UG472 (v1.12) September 27, 2016
Table 3-8: PLL Attributes (Contd)

CLKFBOUT_MULT Integer 2 to 64 5 Specifies the amount to multiply
all CLKOUT clock outputs if a
different frequency is desired. This
number, in combination with the
associated CLKOUT#_DIVIDE
value and DIVCLK_DIVIDE
value, will determine the output
frequency.
DIVCLK_DIVIDE Integer 1 to 56 1 Specifies the division ratio for all
output clocks with respect to the
input clock.
CLKFBOUT_PHASE Real 0.0 to 360.0 0.0 Specifies the phase offset in
degrees of the clock feedback
output. Shifting the feedback clock
results in a negative phase shift of
all output clocks to the PLL.
REF_JITTER1 Real 0.000 to 0.999 0.010 This attribute is for simulation
REF_JITTER2 purposes only. Simulation checks
against the maximum allowed
value. If known, then the value
provided should be specified in
terms of the unit interval (UI) (the
maximum peak to peak value) of
the expected jitter on the input
clock.
the PLL CLKIN1 input. Resolution
is down to the ps. This information
is mandatory and must be
supplied.
the PLL CLKIN2 input. Resolution
is down to the ps. This information
is mandatory and must be
supplied.
STARTUP_WAIT Boolean FALSE, TRUE FALSE Wait during the configuration
start-up cycle for the PLL to lock.
Notes:
1. The COMPENSATION attribute values are documented for informational purpose only. The ISE or Vivado design tools
automatically select the appropriate compensation based on circuit topology. Do not manually select a compensation value, leave the
attribute at the default value.

Send Feedback
UG472 (v1.12) September 27, 2016
MMCM Clock Input Signals

The possible clock sources for the MMCM include:
IBUFG - Clock-capable input buffer, the MMCM will compensate the delay of this
path. IBUFG represents a clock-capable clock pin in the same region.
BUFGCTRL or BUFG - Internal global clock buffer, the MMCM will not compensate
the delay of this path.
IBUF - Regular input buffer, not recommended because the input buffer can use
general routing. An IBUF clock input must route to a BUFG before routing to an
MMCM/PLL. The MMCM/PLL does not compensate for the delay of this path.
BUFR - Regional clock input buffer, the MMCM/PLL will not compensate the delay of
this path.
GT - The gigabit transceiver can directly connect to the MMCM.
Counter Control
The MMCM/PLL output counters provide a wide variety of synthesized clocks using a
combination of DIVIDE, DUTY_CYCLE, and PHASE. Figure 3-8 illustrates how the
counter settings impact the counter output.
The top waveform represents the output from the VCO.
Counter Clock Input

(VCO)
DIVIDE = 2
DUTY_CYCLE = 0.5
PHASE = 0
DIVIDE = 2
DUTY_CYCLE = 0.5
PHASE = 180
DIVIDE = 2
DUTY_CYCLE = 0.75
PHASE = 180
DIVIDE = 1
DUTY_CYCLE = 0.5
PHASE = 0
DIVIDE = 1
DUTY_CYCLE = 0.5
PHASE = 360
DIVIDE = 3
DUTY_CYCLE = 0.33
PHASE = 0
DIVIDE = 3
DUTY_CYCLE = 0.5
PHASE = 0
UG472_c2_08_061710
Figure 3-8: Output Counter Clock Synthesis Examples

Send Feedback
UG472 (v1.12) September 27, 2016
Detailed VCO and Output Counter Waveforms

Figure 3-9 shows the eight VCO phase outputs and four different counter outputs. Each
VCO phase is shown with the appropriate start-up sequence. The phase relationship and
start-up sequence are guaranteed to ensure the correct phase is maintained. This means the
rising edge of the 0 phase will happen before the rising edge of the 45 phase. The O0
counter is programmed to do a simple divide by two with the 0 phase tap as the reference
clock. The O1 counter is programmed to do a simple divide by two but uses the 180 phase
tap from the VCO. This counter setting could be used to generate a clock for a DDR
interface where the reference clock is edge aligned to the data transition. The O2 counter is
programmed to do a divide by three. The O3 output has the same programming as the O2
output except the phase is set for a one cycle delay. Phase shifts greater than one VCO
period are possible.
If the MMCM/PLL is configured to provide a certain phase relationship and the input
frequency is changed, then this phase relationship is also changed since the VCO
frequency changes and therefore the absolute shift in picoseconds will change. This aspect
must be considered when designing with the MMCM/PLL. When an important aspect of
the design is to maintain a certain phase relationship amongst various clock outputs, (for
example, CLK and CLK90) then this relationship will be maintained regardless of the input
frequency.
45
90
VCO 135
8 Phases
180
225
270
315
O0
Counter O1
Outputs O2
O3
One Cycle Delay

ug472_02_09_061710
Figure 3-9: Selecting VCO Phases
All O counters can be equivalent, anything O0 can do, O1 can do. In 7 series devices, the
O0 counter has the additional capability to be used in fractional divide mode. The
MMCM/PLL outputs are flexible when connecting to the global clock network since they
are identical. In most cases, this level of detail is imperceptible to you as the software and
Clocking Wizard determines the proper settings through the MMCM/PLL attributes and
Wizard inputs.

Send Feedback
UG472 (v1.12) September 27, 2016
Reference Clock Switching
Reference Clock Switching

The MMCM and PLL reference clock can be dynamically switched by using the CLKINSEL
pin. The switching is done asynchronously. Once the clock switches, the MMCM/PLL is
likely to lose LOCKED and automatically lock onto the new clock. Therefore, once the
clock switches, the MMCM/PLL must be reset. The MMCM/PLL clock MUX switching is
shown in Figure 3-10. The CLKINSEL signal directly controls the MUX. No
synchronization logic is present.
CLKINSEL
BUFG
CLKIN1
IBUFG (CC)
BUFR
GT
BUFH
Local Rounting
(not recommended)
MMCM/PLL
CLKIN
BUFG
CLKIN2
IBUFG (CC)
BUFR
GT
BUFH
Local Rounting
(not recommended) UG472_c2_10_012712
Figure 3-10: Input Clock Switching
Missing Input Clock or Feedback Clock

When the input clock or feedback clock is lost, the CLKINSTOPPED or CLKFBSTOPPED
status signal is asserted. The MMCM deasserts the LOCKED signal. After the clock
returns, the CLKINSTOPPED signal is deasserted and a RESET must be applied.
MMCM and PLL Use Models

The examples in this section show the MMCM, however, they can equally be applied to the
PLL. There are several methods to design with the MMCM and/or PLL. The Clocking
Wizard in the ISE or Vivado design tools can assist with generating the various MMCM
and PLL parameters. Additionally, the MMCM can be manually instantiated as a
component. It is also possible for the MMCM to be merged with an IP core. The IP core
would contain and manage the MMCM.
Clock Network Deskew

One of the predominant uses of the MMCM is for clock network deskew. Figure 3-11 and
Figure 3-12 show the MMCM in this mode. The clock output from one of the CLKOUT
counters is used to drive logic within the fabric and/or the I/Os. The feedback counter is
used to control the exact phase relationship between the input clock and the output clock
(if, for example a 90 phase shift is required). The associated clock waveforms are shown to
the right for the case where the input clock and output clock need to be phase aligned. The
configuration in Figure 3-11 is the most flexible, but it does require two global clock
networks.

Send Feedback
UG472 (v1.12) September 27, 2016
IBUFG BUFG
1 2 4 5
CLKIN1 CLKOUT0 To Logic
3
CLKFBIN CLKOUT0B
RST CLKOUT1
CLKOUT1B
CLKOUT2
CLKOUT2B
CLKOUT3
CLKOUT3B 1
CLKOUT4
2
CLKOUT5
BUFG 3
CLKOUT6
6
CLKFBOUT
4
CLKFBOUTB
LOCKED 5
MMCM
6
UG472_c2_11_061710
Figure 3-11: Global Clock Network Deskew Using Two BUFGs

IBUFG BUFH
1 2 4 5
3
CLKFBIN CLKOUT0B
RST CLKOUT1
CLKOUT1B
CLKOUT2
CLKOUT2B
CLKOUT3
CLKOUT3B 1
CLKOUT4
2
CLKOUT5
BUFH 3
CLKOUT6
6
CLKFBOUT
4
CLKFBOUTB
LOCKED 5
MMCM
6
UG472_c2_17_011712
Figure 3-12: Horizontal Clock Network Deskew Using Two BUFHs

Send Feedback
UG472 (v1.12) September 27, 2016
There are certain restrictions on implementing the feedback. The CLKFBOUT output can
be used to provide the feedback clock signal. When an MMCM is driving both BUFGs and
BUFH, only one of the clock buffers that is also used in the feedback path is deskewed. The
fundamental restriction is that both input frequencies to the PFD must be identical.
Therefore, the following relationship must be met:
f IN f VCO
------- = f FB = ------------- Equation 3-11
D M
As an example, if IN is 166 MHz, D = 1, M = 6, and O = 2, then VCO is 996 MHz and the
clock output frequency is 498 MHz. Since the M value in the feedback path is 6, both input
frequencies at the PFD are 166 MHz.
In another more complex scenario has an input frequency of 66.66 MHz and D = 2, M = 30,
and O = 4. The VCO frequency in this case is 1000 MHz and the CLKOUT output
frequency is 250 MHz. Therefore, the feedback frequency at the PFD is 1000/30 or
33.33 MHz, matching the 66.66 MHz/2 input clock frequency at the PFD.
MMCM with Internal Feedback

The MMCM feedback can be internal to the MMCM when the MMCM is used as a
synthesizer or jitter filter and there is no required phase relationship between the MMCM
input clock and the MMCM output clock. The MMCM performance increases because the
feedback clock is not subjected to noise on the core supply since it never passes through a
block powered by this supply. Of course, noise introduced on the CLKIN signal and the
BUFG will still be present (Figure 3-13).
IBUFG BUFG

CLKFBIN CLKOUT0B
RST CLKOUT1
CLKOUT1B
CLKOUT2
CLKOUT2B
CLKOUT3
CLKOUT3B
CLKOUT4
CLKOUT5
CLKOUT6
CLKFBOUT
CLKFBOUTB
LOCKED
MMCM
UG472_c2_12_061710
Figure 3-13: MMCM with Internal Feedback

Send Feedback
UG472 (v1.12) September 27, 2016
Zero Delay Buffer

The MMCM can also be used to generate a zero delay buffer clock. A zero delay buffer can
be useful for applications where there is a single clock signal fan out to multiple
destinations with a low skew between them. This configuration is shown in the
Figure 3-14. Here, the feedback signal drives off chip and the board trace feedback is
designed to match the trace to the external components. In this configuration, it is assumed
that the clock edges are aligned at the input of the FPGA and the input of the external
component. The input clock buffers for CLKIN and CLKFBIN must be in the same bank.
IBUFG BUFG OBUF

Inside FPGA
CLKIN1 CLKOUT0
CLKOUT0B To
External
CLKOUT1 Components
CLKFBIN
CLKOUT1B
RST CLKOUT2
CLKOUT2B
CLKOUT3
CLKOUT3B
CLKOUT4
CLKOUT5
BUFG
CLKOUT6
CLKFBOUT
CLKFBOUTB
MMCM LOCKED
ug472_c2_13_061710
Figure 3-14: Zero Delay Buffer
In some cases, precise alignment cannot occur because of the difference in loading between
the input capacitance of the external component and the feedback path capacitance of the
FPGA. For example, the external components can have an input capacitance of 1 pF to 4 pF
while the FPGA has an input capacitance of around 8 pF. There is a difference in the signal
slope, which is basically skew. Designers need to be aware of this effect to ensure timing.
CMT to CMT Connection

The MMCM and PLL can be cascaded using CLKOUT0 to CLKOUT3 through the CMT
backbone to allow generation of a greater range of clock frequencies. No buffer is needed
when used with the CMT backbone (Figure 3-15 and Figure 3-16). There will be a phase
offset between the output clocks of the two MMCMs because the backbone delay is not
compensated.
The frequency range restrictions still apply. Equation 3-12 shows the relationship between
the final output frequency and the input frequency and counter settings of the two
MMCMs (Figure 3-15 and Figure 3-16). The phase relationship between the output clock of
the second MMCM and the input clock is undefined, and an additional phase offset is
added between the two MMCMs because the backbone connection is not compensated. To
cascade MMCMs, route the output of the first MMCM to the CLKIN pin of the second

Send Feedback
UG472 (v1.12) September 27, 2016
MMCM. This path provides the lowest device jitter. Cascading using the inverted
CLKOUTxB outputs is not available.
M MMCM2 M MMCM1 M MMCM2

- = f IN -------------------------------------------------
f OUTMMCM2 = f OUTMMCM1 ------------------------------------------------- - -------------------------------------------------
- Equation 3-12
D MMCM2 O MMCM2 D MMCM1 O MMCM1 D MMCM2 O MMCM2
IBUFG BUFG
CLKIN1 CLKOUT0 CLKIN1 CLKOUT0 To Logic

BUFG
CLKFBIN CLKOUT0B CLKFBIN CLKOUT0B
RST CLKOUT1 To Logic RST CLKOUT1
CLKOUT1B CLKOUT1B
CLKOUT2 CLKOUT2
CLKOUT2B CLKOUT2B
CLKOUT3 CLKOUT3
CLKOUT3B CLKOUT3B
CLKOUT4 CLKOUT4
CLKOUT5 CLKOUT5
CLKOUT6 CLKOUT6
CLKFBOUT CLKFBOUT
CLKFBOUTB CLKFBOUTB
MMCM MMCM
LOCKED LOCKED
ug472_c2_14_061710
Figure 3-15: Cascading Two MMCMs Without Any Clock Alignment

Uncompensated Delay
IBUFG BUFG
CLKIN1 CLKOUT0 CLKIN1 CLKOUT0 To Logic

BUFG
CLKFBIN CLKOUT0B CLKFBIN CLKOUT0B
RST CLKOUT1 To Logic RST CLKOUT1
CLKOUT1B CLKOUT1B
CLKOUT2 CLKOUT2
CLKOUT2B CLKOUT2B
CLKOUT3 CLKOUT3
CLKOUT3B CLKOUT3B
CLKOUT4 CLKOUT4
CLKOUT5 CLKOUT5
BUFG
CLKOUT6 CLKOUT6
CLKFBOUT To Logic CLKFBOUT
CLKFBOUTB CLKFBOUTB
MMCM MMCM
LOCKED LOCKED
ug472_c2_15_042611
Figure 3-16: Cascading Two MMCMs With the Closest Possible Clock Alignment

Send Feedback
UG472 (v1.12) September 27, 2016
Spread-Spectrum Clock Generation

Spread-spectrum clock generation (SSCG) is widely used by manufacturers of electronic
devices to reduce the spectral density of the electromagnetic interference (EMI) generated
by these devices. Manufacturers must ensure that levels of electromagnetic energy emitted
do not interfere with the operation of other nearby electronic devices. For example, the
clarity of a phone call should not degrade when the phone is next to a video display. In the
same way, the display should not be affected when the phone is used.
Electromagnetic Compatibility (EMC) regulations are used to control the noise or EMI that
causes these disturbances. Typical solutions for meeting EMC requirements involve
adding expensive shielding, ferrite beads, or chokes. These solutions can adversely impact
the cost of the final product by complicating PCB routing and forcing longer product
development cycles.
SSCG spreads the electromagnetic energy over a large frequency band to effectively reduce
the electrical and magnetic field strengths measured within a narrow window of
frequencies. The peak electromagnetic energy at any one frequency is reduced by
modulating the SSCG output.
The MMCME2 can generate a spread-spectrum clock from a standard fixed frequency
oscillator when SS_EN is set to TRUE (see Figure 3-17). Within the MMCME2, the VCO
frequency is modulated along with CLKFBOUT and CLKOUT[6:4,1,0]. Clock outputs
CLKOUT[3:2] are used to control the modulation period and are not available for general
use. As long as the clock frequency is adjusted slowly, the spread spectrum will not affect
the period jitter of the MMCME2.
Modulation Period
Frequency
FIN
Frequency
Deviation
Time UG472_c3_01_070212
Figure 3-17: Center-Spread Modulation
Adjusting the modulation period SS_MOD_PERIOD allows the FPGA designer to direct
the tools to select the closest modulation period based on the MMCME2 settings. The
spread-spectrum modulation will reduce EMI as long as the modulation frequencies are
higher than the audible frequency range of 30 kHz. Typically, lower modulation
frequencies are preferred by designers to minimize the impact of the introduction of
spread spectrum.
Increasing the frequency deviation with SS_MODE (CENTER_HIGH or DOWN_HIGH)
will increase the overall EMI reduction, but care must be taken to ensure that the increased
range of frequencies does not affect the overall system operation (see Figure 3-18). Because
the spread-spectrum clock and the input clock are operating at different frequencies, any
data being transferred between the clock domains should use an asynchronous FIFO to
ensure that data is not lost. Increasing the frequency deviation will require a larger FIFO.

Send Feedback
UG472 (v1.12) September 27, 2016
Frequency
FIN CENTER_HIGH
CENTER_LOW
Time UG472_c3_02_070212
Figure 3-18: Center-Spread Modulation

(CENTER_LOW vs. CENTER_HIGH)
Another design trade-off is the decision to use a center spread or down spread. Selecting
SS_MODE (DOWN_HIGH, DOWN_LOW) spreads the frequencies to lower frequencies as
shown in Figure 3-19. DOWN_HIGH will have similar frequency deviation to
CENTER_LOW.
FIN
Frequency
DOWN_LOW
DOWN_HIGH
Time UG472_c3_03_070212
Figure 3-19: Down-Spread Modulation
The decision to use down spread is often the result of considering the timing analysis
impact of spread spectrum. When using a spread-spectrum clock, the design must meet
timing at the highest frequency in the frequency deviation. Therefore, if a 100 MHz clock
with SS_MODE (CENTER_LOW) produces a 3% (1.5%) center spread, the 100 MHz clock
with 3% center spread must pass timing analysis as a 101.5 MHz clock. However, if
SS_MODE (DOWN_HIGH) produces a 3% down spread, the input frequency is the
highest frequency within the frequency deviation. Consequently, for a 100 MHz clock with
3% down spread, the down-spread clock would continue to be analyzed by timing analysis
as a 100 MHz clock.
As an example of adjusting timing constraints to allow for the range of frequencies within
the spread, the input frequency can be adjusted to manually account for the increased
range of frequencies, as shown in Table 3-9.

Send Feedback
UG472 (v1.12) September 27, 2016
Table 3-9: Manual Spread Spectrum Timing Adjustment Using Input Frequency
Input Frequency Input Frequency Adjustment
Parameter M
(MHz) (FIN_SS)
25 < FIN < 35 M = 28 FIN_SS = FIN x 56/55
M = 21 FIN_SS = FIN x 42/41
35 < FIN < 50
M = 22 FIN_SS = FIN x 44/43
SS_MODE(CENTER_HIGH)
50 < FIN < 75 M = 28 FIN_SS = FIN x 56/55
M= 21 FIN_SS = FIN x 42/41
75 < FIN < 150
M = 22 FIN_SS = FIN x 44/43
25 < FIN < 35 M = 56 FIN_SS = FIN x 112/111
M = 42 FIN_SS = FIN x 84/83
35 < FIN < 50
M= 44 FIN_SS = FIN x 88/87
SS_MODE (CENTER_LOW)
50 < FIN < 75 M = 56 FIN_SS = FIN x 112/111
M = 42 FIN_SS = FIN x 84/83
75 < FIN < 150
M = 44 FIN_SS = FIN x 88/87
25 < FIN < 35 M=28 FIN_SS = FIN
35 < FIN < 50 M = 21, 22 FIN_SS = FIN
SS_MODE (DOWN_HIGH) 50 < FIN < 75 M = 28 FIN_SS = FIN
75 < FIN < 100 M = 21, 22 FIN_SS = FIN
100 < FIN < 150 M = 21, 22 FIN_SS = FIN
25 < FIN < 35 M = 56 FIN_SS = FIN
35 < FIN < 50 M = 42, 44 FIN_SS = FIN
SS_MODE (DOWN_LOW) 50 < FIN < 75 M = 56 FIN_SS = FIN
75 < FIN < 100 M = 42, 44 FIN_SS = FIN
100 < FIN < 150 M = 42, 44 FIN_SS = FIN
For a 25 MHz input clock, the new timing constraints would be:
SS_MODE(CENTER_HIGH) = 25 x 56/55 = 25.45 MHz
SS_MODE (CENTER_LOW) = 25 x 112/111 = 25.23 MHz
SS_MODE (DOWN_HIGH) =25 MHz
SS_MODE (DOWN_LOW) = 25 MHz
For an 80 MHz input clock, the new timing constraints would be:
SS_MODE(CENTER_HIGH) = 80 x 44/43 = 81.86 MHz
SS_MODE (CENTER_LOW) = 80 x 88/87 = 80.92 MHz
SS_MODE (DOWN_HIGH) =80 MHz
SS_MODE (DOWN_LOW) = 80 MHz

Send Feedback
UG472 (v1.12) September 27, 2016
Because the average output frequency when using down spread is lower than the input
frequency, an asynchronous FIFO must be used for transferring data between the input
and output clock domains. Logic within the MMCME2 controls the spread-spectrum
modulation based on a given input frequency and SS_MOD_PERIOD. The restrictions
shown in Table 3-10 apply when using spread-spectrum generation.
Table 3-10: Spread-Spectrum Generation Restrictions for MMCME2

Parameter Value
FMODULATION Minimum 25 [kHz]
Maximum 250 [kHz]
Input Clock Frequency Minimum 25 [MHz]
Maximum 150 [MHz]
SS_MODE(CENTER_HIGH) M = 28
25 MHz < FIN < 35 MHz
D=1
M = 21, 22
D=1
M = 28
D=2
M = 21, 22
D=2
M = 21, 22
100 MHz < FIN < 150 MHz
D=3
SS_MODE (CENTER_LOW) M = 56
D=2
M = 42, 44
D=2
M = 56
D=4
M = 42, 44
D=4
M = 42, 44
100 MHz < FIN < 150 MHz
D=6
SS_MODE (DOWN_HIGH) M = 28
D=1
M = 21, 22
35 < FIN < 50 MHz
D=1
M = 28
D=2
M = 21, 22
D=2
M = 21, 22
100 MHz < FIN < 150 MHz
D=3

Send Feedback
UG472 (v1.12) September 27, 2016
Table 3-10: Spread-Spectrum Generation Restrictions for MMCME2 (Contd)

Parameter Value
SS_MODE (DOWN_LOW) M = 56
D=2
M = 42, 44
D=2
M = 56
D=4
M = 42, 44
D=4
M = 42, 44
100 MHz < FIN < 150 MHz
D=6
CLKOUT[3:2]_DIVIDE N/A
CLKOUT[6:4,1,0]_DIVIDE 1 to 128
Bandwidth Low
When using spread-spectrum generation, the VCO frequency is set by the clocking wizard
based on the input frequency and SS_MODE. As a result, the clocking wizard is
recommended to set the output frequencies for CLKOUT[6:4,1,0].
Based on the VCO frequency and SS_MOD_PERIOD, the clocking wizard also determines
the correct modulation settings to set the modulation frequency within 10% of
SS_MOD_PERIOD. Because the modulation frequency is dependent on the VCO
frequency, the modulation frequency will scale as the input frequency changes for a given
compilation.

Send Feedback
UG472 (v1.12) September 27, 2016
MMCM Application Example

The following MMCM attribute settings result in a wide variety of synthesized clocks:
CLKOUT0_PHASE = 0;
CLKOUT0_DUTY_CYCLE = 0.5;
CLKOUT0_DIVIDE = 2;
CLKOUT1_PHASE = 90;
CLKOUT1_DIVIDE = 2;
CLKOUT2_PHASE = 0;
CLKOUT2_DIVIDE = 4;
CLKOUT3_PHASE = 90;
CLKOUT3_DIVIDE = 8;
CLKOUT4_PHASE = 0;
CLKOUT4_DIVIDE = 8;
CLKOUT5_PHASE = 135;
CLKOUT5_DIVIDE = 8;
CLKFBOUT_PHASE = 0;
CLKFBOUT_MULT_F = 8;
DIVCLK_DIVIDE = 1;
CLKIN1_PERIOD = 10.0;
Figure 3-20 displays the resulting waveforms.
REFCLK
VCOCLK
CLKOUT0
CLKOUT1
CLKOUT2
CLKOUT3
CLKOUT4
CLKOUT5
UG472_c2_16_061710
Figure 3-20: Example Waveform
Dynamic Reconfiguration Port

For DRP usage, see XAPP888, MMCM and PLL Dynamic Reconfiguration and the associated
reference design.

Send Feedback
UG472 (v1.12) September 27, 2016
VHDL and Verilog Templates and the Clocking Wizard

The VHDL and Verilog code for all clocking resource primitives and the ISE or Vivado
design tools language templates are available in the Libraries Guide.
The Clocking Wizard helps to correctly set up the 7 series MMCM and PLL resources.
Additionally, the Clocking Wizard reports the jitter and supports phase and frequency
synthesis.

Send Feedback
UG472 (v1.12) September 27, 2016
Appendix A
Multi-Region Clocking
Introduction
Clocking and I/O interconnect logic across multiple clock regions in 7 series FPGAs is
different from how it was done in previous generations of Xilinx FPGAs. While the
increase in I/O and logic resources in a clock region has reduced the need for clock signals
to span multiple clock regions, these same wide I/O interfaces still demand the ability to
drive interconnect and I/O logic in more than one clock region. The 7 series FPGAs
BUFMR/BUFMRCE primitives enable clock-capable input pins to drive BUFIOs and
BUFRs in the region same region the input resides as well as the regions above and below.
This appendix details using the BUFIO and BUFR clock buffers to drive clock signals
across multiple clock regions.
All 7 series FPGAs are divided into areas known as clock regions. A clock region spans
from the global clocking column in the center of the device to either the left or right edge of
the device and is 50 rows of CLBs high (Figure A-1).
X-Ref Target - Figure A-1
Global Clock Column
CMT Column
I/O Column
7 Series FPGAs Architecture 7 Series FPGAs Clock Region

ug472_aA_01_ 022811
Figure A-1: 7 Series Clocking Architecture Example

Send Feedback
UG472 (v1.12) September 27, 2016
Each clock region has its own resources. The horizontal clock row (Figure A-2) sits in the
middle of the clock region with 25 rows of CLBs above and 25 rows of CLBs below. The I/
O column that resides in each clock region is 50 I/O high and is exactly one I/O bank.
There are four clock-capable input (CCIO) pins located in the I/O bank within each clock
region, two above the horizontal clock row and two below.
PLL
CCIO
Horizontal
Clock Row
CCIO
MMCM

ug472_aA_02_022811
Figure A-2: Clock Region Resources
Clocking Across Multiple Regions

While the increase in logic and I/O resources within a clock region reduces the need for
designs to span multiple clock regions, some designs still require larger I/O interfaces to
drive the same clock signal from an input source across multiple clock regions. Without
using any other primitives, a clock signal entering the device on a CCIO pin can only drive
the BUFRs and/or BUFIOs within the same region. Some design require the incoming
clock signal to clock interconnect logic (such as slice flip-flops, block RAM and DSP slices)
and I/O logic (such as ISERDES, OSERDES, ILOGIC, OLOGIC, IDELAY and ODELAY) in
more than one clock region. To accomplish this, the BUFMR primitive must be used.
BUFMR Primitive
The BUFMR primitive is a multi-region clock buffer that allows clock signals to access
BUFRs and BUFIOs in regions above and below the region where the clock signal enters
the device. BUFMRs can span more than one clock region (Figure A-3). There are two
BUFMRs located in each clock region. The BUFMRs drive the dedicated low-skew clocking
resources residing within the CMT column, ensuring that the least possible skew is
inserted when driving clock signals into multiple regions.

Send Feedback
UG472 (v1.12) September 27, 2016
Use Cases
Dedicated Routing
PLL
SRCC
MRCC
Horizontal Serial
Clock Row Transceiver
BUFMR
Clocks
MRCC
SRCC
MMCM

ug472_aA_03_022811
Figure A-3: BUFMR Primitive
Every BUFMR is capable of driving the BUFRs and BUFIOs in the same region and the
regions directly above and below. BUFMRs are driven by CCIO or gigabit-transceiver (GT)
outputs in the same clock region. This allows the CCIO and GT output clocks to span
multi-regions using the same circuit topology. Of the four CCIOs present in every clock
region, two can drive BUFMRs. These pins are labeled as MRCC to denote their
multi-region ability. The two CCIOs that cannot drive BUFMRs are labeled as SRCC for
single-region CCIO. Every MRCC pin has a master or P-side and a slave or N-side. When
using a MRCC pin to drive a BUFMR, use only the master or P-side. To identify the master
or P-side, look for a P in the pin name (for example: IO_LxxP_Tx_MRCC_xx).
The GT inputs to the Virtex-6 FPGA BUFRs are not available in the 7 series FPGAs
architecture. The BUFMR, however, can get its inputs from any one of the GT clocks within
the clock region. This allows the GT clocks to span multi-regions using the same circuit
topology as shown in Figure A-3. Also, BUFMRs cannot cross the boundary between
super-logic regions (SLRs) on the devices using stacked-silicon interconnect technology.
Use Cases
When using BUFMRs to drive logic in multiple regions, group the logic being driven by
the multiple BUFRs or BUFIOs into (up to three) subsets, each with a separate BUFR or
BUFIO. Use the Vivado design tools to floorplan and constrain the design so that logic is
assigned to the individual BUFRs and BUFIOs.
For illustration purposes, the following clocking schemes use an MRCC as the input;
however, a GT clock can be used instead. Also, some of these examples show the topology
when using the built-in divide feature of the BUFR. The BUFR can divide by 1-to-8 in
integer steps. The divide value is specified by the BUFR_DIVIDE attribute during design.
Additionally, the BUFR has a BYPASS setting which turns off the divide capability and

Send Feedback
UG472 (v1.12) September 27, 2016
disables the output clock enable (CE) and asynchronous clear for the divide logic (CLR).
For more information on BUFRs, see BUFR Primitive in Chapter 2.
Clock Alignment Across Clock Regions

Although the behavior of the BUFR primitive when using the BUFR_DIVIDE=BYPASS or
BUFR_DIVIDE=1 attributes is similar, the delay through the BUFRs when using
BUFR_DIVIDE=BYPASS is less than when using BUFR_DIVIDE=1. However, the delay
through a BUFR is the same when using the BUFR_DIVIDE=1 attribute or
BUFR_DIVIDE=2, 38. Therefore, when using BUFRs with the divide feature, the
non-dividing BUFRs should have BUFR_DIVIDE set to 1 rather than to BYPASS to ensure
the best possible clock alignment across the clock regions.
Single Buffer per Clock Region

Driving Multiple BUFIOs
When driving only I/O logic across three clock regions, the BUFMR can drive three
BUFIOs. Although BUFRs can perform this function, BUFIOs supply the highest
performance operation and drive dedicated clock nets within the I/O column. Group the
I/O logic by the three BUFIOs into three separate subsets, each is clocked by its own
BUFIO (Figure A-4).
I/O Logic
BUFIO
Clock Region Boundary
MRCC I/O Logic
BUFMR BUFIO
I/O Logic
BUFIO
ug472_aA_04_030111
Figure A-4: Driving Multiple BUFIOs

Send Feedback
UG472 (v1.12) September 27, 2016
Use Cases
Driving Multiple BUFRs

When driving interconnect logic and I/O logic at the same clock rate from the same clock
source across three clock regions, use a BUFMRCE primitive (multi-region clock buffer
with clock enable). For more information on BUFMRCEs, see BUFMR Primitive in
Chapter 2. A BUFMRCE can drive three BUFRs which, in turn, drive both interconnect
logic and I/O logic (Figure A-5). Group the logic clocked by the three BUFRs into separate
subsets, each driven by its own BUFR.
Software Automatically Places
Interconnect
Logic and
I/O Logic
BUFR
Interconnect
MRCC Logic and
I/O Logic
BUFMRCE BUFR
BUFR Alignment
RST
Circuit
Interconnect
Logic and
I/O Logic
BUFR
ug472_aA_05_030111
Figure A-5: Driving Multiple BUFRs
If the divide value in the BUFR is being used, then all BUFR instances must be reset while
the BUFMRCE is disabled. See BUFR Alignment for more details. In the use cases
described in Figure A-4 and Figure A-5, the placer software automatically places the
buffers in the appropriate location.
Multiple Buffers Per Clock Region

Driving Multiple BUFRs (with Divide) and BUFIO
When driving the ISERDES/OSERDES CLK and CLKDIV pins, use BUFIOs in conjunction
with BUFRs that have their divide capability activated. The BUFIO drives a clean,
low-skew clock to the CLK port of the ISERDES/OSERDES and the BUFR drives the
slower CLKDIV input. For example in Figure A-6, when a 250 MHz input clock comes in to
the FPGA on a MRCC pin, the BUFIO drives the CLK input at the full rate of 250 MHz and
the BUFR with BUFR_DIVIDE=2 drives the CLKDIV inputs at the half rate of 125 MHz.
When driving multiple buffers in this manner, manually place the buffers with a LOC
constraint. The logic driven by the buffers is automatically placed in the appropriate
location.

Send Feedback
UG472 (v1.12) September 27, 2016
ISERDES/OSERDES
CLKDIV
BUFR
CLK
BUFIO
ISERDES/OSERDES
CLKDIV
BUFR
MRCC CLK
BUFMRCE BUFIO
BUFR Alignment
RST
Circuit

ISERDES/OSERDES
CLKDIV
BUFR
CLK
BUFIO
ug472_aA_06_051311
Figure A-6: Driving Multiple BUFRs (With Divide) and BUFIO

Send Feedback
UG472 (v1.12) September 27, 2016
Use Cases
Driving Multiple BUFRs (With and Without Divide)

Similar to the example in Figure A-6, if the BUFIOs are not available (used for another
purpose), the CLK inputs of the ISERDES/OSERDES can be driven by BUFRs (see
Figure A-7).
When a BUFMR drives more than three BUFRs, manually place the BUFRs with a LOC
constraint. The logic driven by the BUFRs is automatically placed in the appropriate
location.
ISERDES/OSERDES
CLKDIV
BUFR
CLK
BUFR
ISERDES/OSERDES
CLKDIV
BUFR
MRCC CLK
BUFMRCE BUFR
BUFR Alignment
RST
Circuit

ISERDES/OSERDES
CLKDIV
BUFR
CLK
BUFR
ug472_aA_07_051311
Figure A-7: Driving Multiple BUFRs (With and Without Divide)

Send Feedback
UG472 (v1.12) September 27, 2016
BUFR Alignment
When using the built in divide capability of the BUFR (shown in Figure A-6 and
Figure A-7, the clock must be stopped at the BUFMR and reset signals applied to the
BUFRs, to align the BUFR divide counters across the multiple clock regions. This will
require using the BUFMRCE primitive, which allows you to disable the output of the
BUFMR during the reset. To successfully align the BUFRs in adjacent regions, the
following procedure must be followed:
Connect the clock enable to the CE port of the BUFMRCE
Hold the CE pin of the BUFMRCE in its inactive state to disable the output of the
BUFMRCE
Reset all BUFRs by applying a reset signal to the CLR pin of the BUFR
Re-enable the BUFMRCE after the BUFR reset/CLR signal is released
Releasing the reset signal of the BUFRs
To turn off clocks during circuit operations, that is after the reset/CLR signal to the BUFRs
is deasserted, disable the BUFMRCE using its CE pin. This ensures that the BUFRs
continue to be aligned when the clock signal is reinstated.

Send Feedback
UG472 (v1.12) September 27, 2016
Appendix B
Clocking Resources and Connectivity

Variations per Clock Region
Figure B-1 through Figure B-4 show the clocking resources and connectivity for the clock
region variations.
X-Ref Target - Figure B-1
Clock Fabric - Multiple Columns of CLB/Block RAM/DSP Fabric - Multiple Columns of CLB/Block RAM/DSP
Backbone
5x36K 10x 5x36K 10x
Block RAMs/ DSP48 Block RAMs/ DSP48
FIFOs Slices PLL I/O Bank FIFOs Slices GT Quad
CLB CLKA CLK SelectIO Logic CLB CLKA CLK

GTX/GTH
CLKB CLKB
SelectIO Logic
25 25 RX/TXUSRCLKs
SelectIO Logic
CLBs CLBs RX/TXOUTCLKs
IBUFDS O/ODIV2
CLB
25 CLB
SelectIO
Logic Resources
CLB CLB
CLB
BUFIO CLB GTX/GTH
BUFR
CLB SelectIO Logic CLB RX/TXUSRCLKs

BUFIO/BUFR RX/TXOUTCLKs
CE CLB CLB IBUFDS O/ODIV2
Any I/O Clock CC
Left Side
Clock Horizontal
Connections Clocking
BUFH
Row BUFMR HROW
or
GTX/GTH
BUFG
CLB Any I/O Clock CC CLB RX/TXUSRCLKs

BUFIO/BUFR
RX/TXOUTCLKs
CE CLB SelectIO Logic CLB
IBUFDS O/ODIV2
CLB BUFR CLB

BUFIO
CLB CLB
25 GTX/GTH
SelectIO
CLB CLB
Logic Resources
RX/TXUSRCLKs
25 25 RX/TXOUTCLKs
CLBs SelectIO Logic CLBs
IBUFDS O/ODIV2
SelectIO Logic
CLB SelectIO Logic CLB
5x36K 10x MMCM 5x36K 10x

Block RAMs/ DSP48 Block RAMs/ DSP48
FIFOs Slices FIFOs Slices
UG472_aB_01_020812
Figure B-1: Clock Region in Virtex-7 FPGAs (Right Side)

Send Feedback
UG472 (v1.12) September 27, 2016
Appendix B: Clocking Resources and Connectivity Variations per Clock Region
Fabric - Multiple Columns of CLB/Block RAM/DSP I/O Bank

CLB CLKA CLK SelectIO Logic
CLKB
SelectIO Logic
25 CLBs SelectIO Logic
CLB 5x36K 25 SelectIO

Clock Block RAMs/
10x Logic Resources
PLL/
Backbone DSP48
CLB FIFOs PHASER
Slices
CLB BUFR BUFIO

CE
CLB SelectIO Logic
BUFIO/BUFR
CLB Any I/O Clock CC
BUFH
Left Side Clock or
BUFMR
Connections Horizontal Clocking Row
BUFG
BUFIO/BUFR
CLB SelectIO Logic
CE
CLB BUFR BUFIO
5x36K
CLB 10x
Block RAMs/
DSP48 MMCM
FIFOs 25 SelectIO
Slices
CLB Logic Resources
SelectIO Logic
CLB SelectIO Logic
UG472_aB_02_011713
Figure B-2: Clock Region in Spartan-7 FPGAs, Kintex-7 FPGAs, and all Artix-7 FPGAs (except for the
XC7A200T) with I/O Banks and No GT Transceivers (Right Side)
Note: See Figure B-4 for the XC7A200T diagram.

Send Feedback
UG472 (v1.12) September 27, 2016
Fabric - Multiple Columns of CLB/Block RAM/DSP GT Quad

CLB CLKA CLK
GTX/GTP
CLKB
RX/TXUSRCLKs
25 CLBs
RX/TXOUTCLKs
IBUFDS O/ODIV2
CLB 5x36K
Clock Block RAMs/
10x
Backbone DSP48
CLB FIFOs
Slices
GTX/GTP
CLB
CE RX/TXUSRCLKs
CLB
RX/TXOUTCLKs
IBUFDS O/ODIV2
CLB
BUFH
or
Left Side Clock HROW
Connections
GTX/GTP
BUFG
CLB RX/TXUSRCLKs
RX/TXOUTCLKs
CLB
CE IBUFDS O/ODIV2
CLB
5x36K
CLB 10x
Block RAMs/
DSP48
FIFOs
Slices GTX/GTP
CLB
RX/TXUSRCLKs
RX/TXOUTCLKs
25 CLBs IBUFDS O/ODIV2
CLB
UG472_aB_03_011713
Figure B-3: Clock Region in Spartan-7 FPGAs, Kintex-7 FPGAs, and all
Artix-7 FPGAs (except for the XC7A200T) with
GT Transceivers and No I/O Banks (Right Side)
Note: See Figure B-4 for the XC7A200T diagram.

Send Feedback
UG472 (v1.12) September 27, 2016
Appendix B: Clocking Resources and Connectivity Variations per Clock Region
GT Quad Fabric - Multiple Columns of CLB/Block RAM/DSP I/O Bank

CLB CLKA CLK SelectIO Logic
Clock GTP
CLKB
Backbone SelectIO Logic
RX/TXUSRCLKs
RX/TXOUTCLKs
IBUFDS O/ODIV2
CLB 5x36K 25 SelectIO
10x
Block RAMs/ Logic Resources
DSP48 PLL
CLB FIFOs
Slices
GTP
CLB BUFR BUFIO
CE RX/TXUSRCLKs
CLB SelectIO Logic
RX/TXOUTCLKs
BUFIO/BUFR
IBUFDS O/ODIV2
Left Side BUFH
Clock or
Horizontal BUFMR
Connections HROW
Clocking Row
BUFG
RX/TXUSRCLKs
BUFIO/BUFR
RX/TXOUTCLKs
CLB SelectIO Logic
CE IBUFDS O/ODIV2
CLB BUFR BUFIO

GTP
5x36K
CLB 10x
Block RAMs/
DSP48 MMCM
GTP FIFOs
Slices 25 SelectIO
CLB Logic Resources
RX/TXUSRCLKs
RX/TXOUTCLKs
IBUFDS O/ODIV2 25 CLBs SelectIO Logic
SelectIO Logic
CLB SelectIO Logic
UG472_aB_04_020812
Figure B-4: Clock Region in a Artix-7 XC7A200T Device with GTP Transceivers
and I/O Banks (Right Side)

Send Feedback
UG472 (v1.12) September 27, 2016

Ug472 7series Clocking

Uploaded by

Copyright:

Available Formats

Ug472 7series Clocking

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ug472 7series Clocking

Uploaded by

Copyright:

Available Formats

7 Series FPGAs

UG472 (v1.12) September 27, 2016

Date Version Revision

Preface: About This Guide

Chapter 1: Clocking Overview

Chapter 2: Clock Routing Resources

7 Series FPGAs Clocking Resources User Guide www.xilinx.com 5

Chapter 3: Clock Management Tile

Appendix A: Multi-Region Clocking

6 www.xilinx.com 7 Series FPGAs Clocking Resources User Guide

Appendix B: Clocking Resources and Connectivity Variations per

7 Series FPGAs Clocking Resources User Guide www.xilinx.com 7

About This Guide

7 Series FPGAs Clocking Resources User Guide www.xilinx.com 9

10 www.xilinx.com 7 Series FPGAs Clocking Resources User Guide

Clocking Architecture Overview

Clock Routing Resources Overview

7 Series FPGAs Clocking Resources User Guide www.xilinx.com 11

12 www.xilinx.com 7 Series FPGAs Clocking Resources User Guide

Clock Buffers, Management, and Routing

7 Series FPGAs Clocking Resources User Guide www.xilinx.com 13

X-Ref Target - Figure 1-1

Clock Region Clock Region

Clock Horizontal Clock

Clock Horizontal Clock

Clock Horizontal Clock

CMT Column I/O Column

Figure 1-1: 7 Series FPGA High-Level Clock Architecture View

14 www.xilinx.com 7 Series FPGAs Clocking Resources User Guide

Figure 1-2: Basic View of Clock Region

7 Series FPGAs Clocking Resources User Guide www.xilinx.com 15

Global Clocking CMT Clocking

CMT I/O Bank

Figure 1-3: Single Clock Region (Right Side of the Device)

16 www.xilinx.com 7 Series FPGAs Clocking Resources User Guide

Figure 1-4: BUFG/BUFH/CMT Clock Region Detail

7 Series FPGAs Clocking Resources User Guide www.xilinx.com 17

Figure 1-5: BUFR/BUFMR/BUFIO Clock Region Detail

18 www.xilinx.com 7 Series FPGAs Clocking Resources User Guide

7 Series FPGAs Clocking Differences from Previous FPGA

Key Differences from Virtex-6 FPGAs

7 Series FPGAs Clocking Resources User Guide www.xilinx.com 19

Key Differences from Spartan-6 FPGAs

20 www.xilinx.com 7 Series FPGAs Clocking Resources User Guide

7 Series FPGAs Clocking Resources User Guide www.xilinx.com 21

Summary of Clock Connectivity

Table 1-1: Summary of Clock Connectivity

22 www.xilinx.com 7 Series FPGAs Clocking Resources User Guide

Table 1-1: Summary of Clock Connectivity (Contd)

7 Series FPGAs Clocking Resources User Guide www.xilinx.com 23

Table 1-1: Summary of Clock Connectivity (Contd)

24 www.xilinx.com 7 Series FPGAs Clocking Resources User Guide

Clocking Differences in 7 Series FPGAs

Table 1-2: Clocking Connectivity Differences by 7 Series FPGAs

7 Series FPGAs Clocking Resources User Guide www.xilinx.com 25

26 www.xilinx.com 7 Series FPGAs Clocking Resources User Guide

Clock Routing Resources

Clock Buffer Selection Considerations

7 Series FPGAs Clocking Resources User Guide www.xilinx.com 27