Virtex-5 FPGA User Guide

UG190 (v5.3) May 17, 2010

Xilinx is disclosing this user guide, manual, release note, and/or specification (the "Documentation") to you solely for use in the development of designs to operate with Xilinx hardware devices. You may not reproduce, distribute, republish, download, display, post, or transmit the Documentation in any form or by any means including, but not limited to, electronic, mechanical, photocopying, recording, or otherwise, without the prior written consent of Xilinx. Xilinx expressly disclaims any liability arising out of your use of the Documentation. Xilinx reserves the right, at its sole discretion, to change the Documentation without notice at any time. Xilinx assumes no obligation to correct any errors contained in the Documentation, or to advise you of any corrections or updates. Xilinx expressly disclaims any liability in connection with technical support or assistance that may be provided to you in connection with the Information. THE DOCUMENTATION IS DISCLOSED TO YOU AS-IS WITH NO WARRANTY OF ANY KIND. XILINX MAKES NO OTHER WARRANTIES, WHETHER EXPRESS, IMPLIED, OR STATUTORY, REGARDING THE DOCUMENTATION, INCLUDING ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT OF THIRD-PARTY RIGHTS. IN NO EVENT WILL XILINX BE LIABLE FOR ANY CONSEQUENTIAL, INDIRECT, EXEMPLARY, SPECIAL, OR INCIDENTAL DAMAGES, INCLUDING ANY LOSS OF DATA OR LOST PROFITS, ARISING FROM YOUR USE OF THE DOCUMENTATION. 20062010 Xilinx, Inc. XILINX, the Xilinx logo, Virtex, Spartan, ISE, and other designated brands included herein are trademarks of Xilinx in the United States and other countries. PCI, PCI Express, PCIe, and PCI-X are trademarks of PCI-SIG. The PowerPC name and logo are registered trademarks of IBM Corp. and used under license. All other trademarks are the property of their respective owners.

Revision History
The following table shows the revision history for this document.
Date 04/14/06 05/12/06 Version 1.0 1.1 Initial Xilinx release. Minor typographical edits and clarifications. Chapter 1: Revised Figure 1-21. Chapter 2: Revised Figure 2-2 and Figure 2-4. Removed reference to a DCM_PS primitive. Removed outdated clocking wizard section page 83. Chapter 3: Revised Figure 3-1, Figure 3-2, Table 3-2, Table 3-4, Figure 3-9, Equation 3-8, and Figure 3-12. Added PLL in Virtex-4 FPGA PMCD Legacy Mode section. Chapter 4: Added a note to Table 4-5, page 124. Clarified the RAMB36 port mapping design rules on page 132. Chapter 5: Added Figure 5-7 and Figure 5-11, revised Figure 5-32 for clarity. Chapter 6: Updated Simultaneous Switching Output Limits section. Chapter 7: Revised ILOGIC Resources, page 318 including Figure 7-1. Revised Table 7-3. Chapter 8: Revised Table 8-1. 7/19/06 1.2 Chapter 1: Revised Global Clock Buffers, page 27 to clarify single-ended clock pins. Changed the P and N I/O designations in Figure 1-19. Chapter 4: Added Block RAM SSR in Register Mode, page 133 and FIFO Architecture: a Top-Level View, page 142. Revised the FIFO operations Reset, page 144 description. Chapter 6: Minor clarification edits. Changed to N/A from unused in Table 6-36, Table 6-37, and Table 6-38. Chapter 7: Minor edits to clarify IODELAY in this chapter. Chapter 8: Small clarifications in ISERDES_NODELAY Ports, page 355. Revision

Virtex-5 FPGA User Guide

www.xilinx.com

UG190 (v5.3) May 17, 2010

Date 9/06/06

Version 2.0

Revision Added the LXT platform devices throughout document. Chapter 1: Revised Figure 1-22, page 45. Updated Clock Capable I/O, page 40. Chapter 2: Updated Output Clocks, page 65. Chapter 4: Clarified the rules regarding FULL and EMPTY flags on page 139. Chapter 5: Revised Storage Elements, page 178. Chapter 6: Differential Termination Attribute, page 237 is updated for the latest syntax and settings. Replaced the link to the SSO calculator.

10/12/06

2.1

Added System Monitor User Guide reference in the Preface. Added XC5VLX85T to Table 1-5, Table 2-1, and Table 5-2. Chapter 3: Revised Figure 3-1. Chapter 4: Added cascade to Table 4-7, page 126. Revised ADDR in Figure 4-9, page 124. Removed scrub mode in Built-in Error Correction section. Chapter 5: Revised Figure 5-22, page 197.

02/02/07

3.0

Added the three SXT devices and the XC5VLX220T to Table 1-5, Table 2-1, and Table 5-2. Chapter 4: Clarified wording in Synchronous Clocking, page 119. Chapter 6: Added DCI Cascading, page 220. Changed VREF for SSTL18_II_T_DCI to 0.9 in Table 6-39. Chapter 7: Revised OQ in Figure 7-27, page 349. Chapter 8: Clock Enable Inputs - CE1 and CE2, page 356.

UG190 (v5.3) May 17, 2010

www.xilinx.com

Virtex-5 FPGA User Guide

Date 09/11/07

Version 3.1

Revision Chapter 1: Added Clock Gating for Power Savings, page 26. Revised Figure 1-2, page 30. Revised Figure 1-16, page 37. Chapter 2: Revised DCM reset and locking process in Reset Input - RST, page 53. Updated DO[2] description in Table 2-4, page 56. Changed the multiply value range on page 58. Revised the description for FACTORY_JF Attribute, page 61. Revised Output Clocks, page 65, updated Figure 2-7, page 74, and added a BUFG to Figure 2-10, page 72. Added more steps to Dynamic Reconfiguration (DRPs) when loading new M and D values on page 73. Updated Figure 2-7, page 74. Revised bulleted descriptions under Figure 2-20, page 87. Chapter 3: Updated Figure 3-1, page 90. Add notes to Table 3-2, page 93. Added a note to Phase Shift, page 95. Added rounding to Equation 3-3 through Equation 3-6. Revised CLKFBIN, CLKFBDCM, CLKFBOUT, RST, LOCKED, and added the REL pin and note 2 to Table 3-3, page 96. Added RESET_ON_LOSS_OF_LOCK attribute to Table 3-4, page 98. Removed general routing discussion from PLL Clock Input Signals. Revised Missing Input Clock or Feedback Clock section. Added waveforms to Figure 3-13. Corrected the Virtex-4 port mapping in Figure 3-17 and Table 3-8, page 111. Chapter 4: Revised and clarified Built-in Error Correction. Edited WE signal throughout. Clarified Readback limitation in Simple Dual-Port Block RAM, page 121. Edited Set/Reset - SSR[A|B], page 125. Added Block RAM Retargeting, page 139. Revised latency values and added Note 1 to Table 4-16, page 145. Updated Cascading FIFOs to Increase Depth, page 157. Chapter 5: Clarified information about common control signals in a slice in Storage Elements, page 178. Chapter 6: Updated the DCI cascading guidelines on page 223. Removed references to HSLVDCI Controlled Impedance Driver with Unidirectional Termination since it is not supported in software. Added note 3 to Table 6-17, page 256. Clarified the introduction to SSTL (Stub-Series Terminated Logic), page 274. Revised DIFF_SSTL2_II_DCI, DIFF_SSTL18_II_DCI, page 275. Fixed DIFF_SSTL2_II references in Figure 6-74, page 282. Revised rules 2 and 3 in Rules for Combining I/O Standards in the Same Bank, page 298. Deleted of absolute maximum table from Overshoot/Undershoot, page 302. Chapter 7: Removed DDLY port from IDDR primitive page 321. Added the SIGNAL _PATTERN, DELAY_SRC, and REFCLK_FREQUENCY attributes to Table 7-10, page 329. Revised Figure 7-9, page 330. Removed Table 7-12: Generating Reference Clock From DCM and updated REFCLK section in IDELAYCTRL Ports, page 338. Clarified introduction in IDELAYCTRL Locations, page 339. Changed ODDR Clock Forwarding, page 347. Chapter 8: Updated SR and O in Figure 8-2 and Table 8-1, page 355. Updated the entire section for BITSLIP Submodule, page 366. Fixed typographical errors in Figure 8-14, page 370.

Virtex-5 FPGA User Guide

www.xilinx.com

UG190 (v5.3) May 17, 2010

Date 12/11/07

Version 3.2

Revision Chapter 1: Revised description in Clock Gating for Power Savings, page 26. Added the XC5VLX20T, XC5VLX155, and XC5VLX155T devices to Table 1-5. Chapter 2: Added the XC5VLX20T, XC5VLX155, and XC5VLX155T devices to Table 2-1. Chapter 3: Revised Clock Network Deskew, page 93. Removed note 2 and revised descriptions of CLKFBOUT and DEN in Table 3-3, page 96. Revised allowed value of CLKOUT[0:5]_PHASE and CLKFBOUT_MULT description in Table 3-4, page 98. Revised Figure 3-13 and Figure 3-14 including waveforms. Chapter 5: Added the XC5VLX20T, XC5VLX155, and XC5VLX155T devices to Table 5-2. Chapter 6: Clarified discussion of cascading across CMT tiles in DCI Cascading. Changed the split termination to VTT = 0.9V in Figure 6-84, page 292. Chapter 7: Added to the descriptions of the HIGH_PERFORMANCE_MODE Attribute, and the SIGNAL_PATTERN Attribute, page 330,including Table 7-10. Revised description in Instantiating IDELAYCTRL Without LOC Constraints, page 340. Chapter 8: Complete rewrite of the chapter. Many changes to descriptions, tables, and figures.

02/05/08

3.3

Chapter 1: Updated discussion under I/O Clock Buffer - BUFIO, page 41. Chapter 3: Revised LOCKED description in Table 3-3, page 96. Revised discussion under Detailed VCO and Output Counter Waveforms, page 103. Chapter 5: Updated description of Figure 5-17. Chapter 7: Updated description under Clock Input - C, page 327. Updated default value to TRUE for HIGH_PERFORMANCE_MODE in Table 7-10, page 329. Chapter 8: Revised TRISTATE_WIDTH in Table 8-7, page 374. Updated discussion under TRISTATE_WIDTH Attribute and added section on OSERDES Clocking Methods, page 375.

03/31/08

4.0

Added the FXT platform to Table 1-5, Table 2-1, and Table 5-2. Revised timing event description under Figure 1-21, page 44. Revised Dynamic Reconfiguration, page 73 to remove adjustment of PHASE_SHIFT. Added CLKOUT[0:5]_DESKEW_ADJUST to Table 3-4, page 98. Corrected READ_WIDTH_B = 9 to WRITE_WIDTH_B = 9 in the block RAM usage rules on page 114. Revised High-Speed Clock for Strobe-Based Memory Interfaces - OCLK, page 357. Corrected BITSLIP_ENABLE value from string to boolean in ISERDES_NODELAY Attributes, page 358.

04/25/08

4.1

Added the XC5VSX240T to Table 1-5, Table 2-1, and Table 5-2. Revised Figure 1-21, page 44. Removed a pad notation from the ODDR output of Figure 2-9. Removed the BUFG on the output of Figure 2-10. Updated CLKOUT[0:5]_DESKEW_ADJUST description in Table 3-4, page 98. Revised equations Equation 3-5 and Equation 3-6. Updated the notes in Table 4-16, page 145. Revised description of Instantiating IDELAYCTRL with Location (LOC) Constraints, page 342.

UG190 (v5.3) May 17, 2010

www.xilinx.com

Virtex-5 FPGA User Guide

Date 05/09/08

Version 4.2

Revision Revised clock routing resources in BUFGCTRL to DCM, page 73. Removed example Figure 2-10 on page 76. Corrected note 1 in Table 4-5, page 124. Added Legal Block RAM and FIFO Combinations, page 171. Clarified Note 7 in DCI in Virtex-5 Device I/O Standards. Master DCI is not supported in Banks 1 and 2.

09/23/08

4.3

Added the TXT platform to Table 1-5, Table 2-1, and Table 5-2. Chapter 2: Revised Reset Input - RST, page 53 and System-Synchronous Setting (Default), page 66. Chapter 3: Updated Jitter Filter, page 94. Chapter 4: Updated Write Modes, page 117, and Asynchronous Clocking, page 119. Chapter 6: Labeled all the DCI_18 standards consistently in Table 6-39 and Table 6-40. Replaced the link to the Full Device SSO Calculator. Chapter 8: Updated CLKB in Table 8-1, page 355 and High-Speed Clock Input - CLKB, page 357.

12/02/08

4.4

Chapter 2: Changed edge to half in IBUFG Global Clock Input Buffer description on page 51, page 52, and page 53. Chapter 4: Added new text and equation to Almost Empty Flag, page 146. Added note 1 to Table 4-19, page 148. Chapter 5: Changed RAM#XM to RAM#M in Figure 5-32, page 212. Chapter 6: Corrected PCI acronym definition in PCI-X, PCI-33, PCI-66 (Peripheral Component Interconnect), page 247. Added to the description of the SSTL18_II_T_DCI standard in SSTL18_II_T_DCI (1.8V) Split-Thevenin Termination, page 293. Chapter 7: Added mode to caption of Figure 7-7, page 323 for clarification. Chapter 8: Added statement about shared resources between OCLK and CLK in HighSpeed Clock for Strobe-Based Memory Interfaces - OCLK, page 357.

01/09/09

4.5

Chapter 4: Revised the paragraph below Equation 4-1 on page 146. Chapter 6: Added IBUFDS_DIFF_OUT to the list of primitive names for differential I/O standards in Virtex-5 FPGA SelectIO Primitives, page 233. Added new section IBUFDS_DIFF_OUT, page 235. Chapter 7: In the Verilog code segment for bidirectional IODELAY on page 333, corrected the setting of RST.

03/19/09

4.6

Chapter 3: Added reference to the Virtex-5 FPGA Configuration Guide in PLL_ADV Primitive, page 93. Chapter 4: In the second paragraph of Write Modes, page 117, added in ECC configuration after READ_FIRST. Chapter 5: In the third sentence of the second paragraph of Look-Up Table (LUT), page 178, changed slices to LUTs. Removed MC31 and SHIFTOUT from the bottom SRL32 in Figure 5-19, page 193. Chapter 6: Inserted sentence about at least one I/O being configured as DCI to the paragraph after Figure 6-4, page 220.

Virtex-5 FPGA User Guide

www.xilinx.com

UG190 (v5.3) May 17, 2010

Date 05/01/09

Version 4.7

Revision Chapter 3: Added 7 as one of the values of D in the last sentence of the first paragraph of Determine the Input Frequency, page 95. Updated waveform 1 in Figure 3-10, page 105. Chapter 4: In the second paragraph of Write Modes, page 117, rephrased the second paragraph. Changed Clock Cycle Latency to Write/Read Cycle Latency in Table 4-16, page 145. In ECC Modes Overview, page 159, changed READ_FIRST to NO_CHANGE in the last bullet of the section.

06/19/09

5.0

Chapter 1: Updated instances of BUFGMUX_VIRTEX4 to BUFGMUX_CTRL throughout chapter. Clarified global and local clocking in first paragraph of Global and Regional Clocks, page 25. Chapter 2: Updated Dynamic Reconfiguration description in DCM Summary, page 48 to remove different phase shift as an attribute changeable via dynamic reconfiguration. Chapter 3: Updated definition of LOCKED pin in Table 3-3, page 96.

09/18/09

5.1

Chapter 5: Changed combine all slices to combine all LUTs in second paragraph of Look-Up Table (LUT), page 178. Changed 16 to 32 in the first paragraph of Static Read Operation, page 195. Chapter 6: In DCI Cascading, page 220, deleted the following: Sentence that stated that DCI control for a particular bank can come from the bank immediately above or below. Fourth bulleted item in guidelines when using DCI cascading that stated that DCI cascading must extend across consecutive banks in the same column.

11/05/09

5.2

05/17/10

5.3

Chapter 2: In first paragraph of Source Clock Input - CLKIN, added sentence about DCM powering down when CLKIN is stopped for 100 ms or longer.

UG190 (v5.3) May 17, 2010

www.xilinx.com

Virtex-5 FPGA User Guide

Virtex-5 FPGA User Guide

www.xilinx.com

UG190 (v5.3) May 17, 2010

Table of Contents
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Preface: About This Guide

Additional Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Additional Support Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Online Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 1: Clock Resources

Global and Regional Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Global Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Regional Clocks and I/O Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Global Clocking Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Global Clock Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Clock Input Buffer Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Gating for Power Savings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Clock Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Clock Buffer Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Use Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Tree and Nets - GCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Capable I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I/O Clock Buffer - BUFIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BUFIO Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BUFIO Use Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Regional Clock Buffer - BUFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BUFR Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BUFR Attributes and Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BUFR Use Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Regional Clock Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 26 26 27 28 36 38 38 40 41 41 41 42 43 44 45 46

Regional Clocking Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

VHDL and Verilog Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 2: Clock Management Technology

Clock Management Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 DCM Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 DCM Primitives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
DCM_BASE Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 DCM_ADV Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

DCM Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
DCM Clock Input Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Source Clock Input - CLKIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feedback Clock Input - CLKFB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phase-Shift Clock Input - PSCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 51 52 52

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

Dynamic Reconfiguration Clock Input - DCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCM Control and Data Input Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reset Input - RST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phase-Shift Increment/Decrement Input - PSINCDEC . . . . . . . . . . . . . . . . . . . . . . . . . Phase-Shift Enable Input - PSEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Reconfiguration Data Input - DI[15:0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Reconfiguration Address Input - DADDR[6:0] . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Reconfiguration Write Enable Input - DWE . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Reconfiguration Enable Input - DEN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCM Clock Output Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1x Output Clock - CLK0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1x Output Clock, 90 Phase Shift - CLK90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1x Output Clock, 180 Phase Shift - CLK180 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1x Output Clock, 270 Phase Shift - CLK270 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2x Output Clock - CLK2X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2x Output Clock, 180 Phase Shift - CLK2X180 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency Divide Output Clock - CLKDV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency-Synthesis Output Clock - CLKFX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency-Synthesis Output Clock, 180 - CLKFX180 . . . . . . . . . . . . . . . . . . . . . . . . . . DCM Status and Data Output Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Locked Output - LOCKED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phase-Shift Done Output - PSDONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status or Dynamic Reconfiguration Data Output - DO[15:0] . . . . . . . . . . . . . . . . . . . . . Dynamic Reconfiguration Ready Output - DRDY . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

53 53 53 53 54 54 54 54 54 54 54 55 55 55 55 55 55 55 55 56 56 56 56 57 58 58 58 59 59 59 60 60 60 60 60 61 61 61 63 63 64 64 65 65 65 67 67 67 68 68 68

DCM Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
CLKDV_DIVIDE Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKFX_MULTIPLY and CLKFX_DIVIDE Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKIN_PERIOD Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKIN_DIVIDE_BY_2 Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKOUT_PHASE_SHIFT Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLK_FEEDBACK Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DESKEW_ADJUST Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DFS_FREQUENCY_MODE Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DLL_FREQUENCY_MODE Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DUTY_CYCLE_CORRECTION Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCM_PERFORMANCE_MODE Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FACTORY_JF Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PHASE_SHIFT Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . STARTUP_WAIT Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Deskew . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Deskew Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input Clock Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input Clock Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCM During Configuration and Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deskew Adjust . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Characteristics of the Deskew Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency Synthesis Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency Synthesizer Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phase Shifting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phase-Shifting Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DCM Design Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

10

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Interaction of PSEN, PSINCDEC, PSCLK, and PSDONE . . . . . . . . . . . . . . . . . . . . . . . . 71 Phase-Shift Overflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Phase-Shift Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Dynamic Reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Connecting DCMs to Other Clock Resources in Virtex-5 Devices . . . . . . . . . . . . . 73

IBUFG to DCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCM to BUFGCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BUFGCTRL to DCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLL To and From DCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCM To and From PMCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Board-Level Clock Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Board Deskew with Internal Deskew . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Switching Between Two DCMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCM with PLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 73 73 74 74 75 75 77 80 81

Application Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

VHDL and Verilog Templates, and the Clocking Wizard . . . . . . . . . . . . . . . . . . . . . 83 DCM Timing Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Reset/Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fixed-Phase Shifting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Variable-Phase Shifting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 85 86 87

Legacy Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Chapter 3: Phase-Locked Loops (PLLs)

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Phase Locked Loop (PLL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

General Usage Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

PLL Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 PLL_BASE Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 PLL_ADV Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Clock Network Deskew . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Frequency Synthesis Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Jitter Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 VCO Operating Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Minimum and Maximum Input Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Duty Cycle Programmability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Phase Shift . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 PLL Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Determine the Input Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Determine the M and D Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 PLL Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 PLL Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 PLL CLKIN1 and CLKIN2 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 PLL Clock Input Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Counter Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Clock Shifting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Detailed VCO and Output Counter Waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Reference Clock Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Missing Input Clock or Feedback Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

11

PLL Use Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Clock Network Deskew . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLL with Internal Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Zero Delay Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCM Driving PLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLL Driving DCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PLL to PLL Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 106 106 107 108 109

Application Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

PLL Application Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

PLL in Virtex-4 FPGA PMCD Legacy Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Chapter 4: Block RAM

Block RAM Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Block RAM Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Synchronous Dual-Port and Single-Port RAMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Read Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Write Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Write Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WRITE_FIRST or Transparent Mode (Default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . READ_FIRST or Read-Before-Write Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NO_CHANGE Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conflict Avoidance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Asynchronous Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronous Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optional Output Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Independent Read and Write Port Width Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . Simple Dual-Port Block RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cascadable Block RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Byte-wide Write Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Block RAM Error Correction Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 117 117 117 118 118 118 119 119 119 120 120 121 122 122 123

Additional Block RAM Features in Virtex-5 Devices . . . . . . . . . . . . . . . . . . . . . . . . 120

Block RAM Library Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Block RAM Port Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Clock - CLK[A|B] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable - EN[A|B] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Byte-wide Write Enable - WE[A|B] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Register Enable - REGCE[A|B] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set/Reset - SSR[A|B] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Address Bus - ADDR[A|B]<13:#><14:#><15:#> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data-In Buses - DI[A|B]<#:0> & DIP[A|B]<#:0> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data-Out Buses - DO[A|B]<#:0> and DOP[A|B]<#:0> . . . . . . . . . . . . . . . . . . . . . . . . Cascade In - CASCADEINLAT[A|B] and CASCADEINREG[A|B] . . . . . . . . . . . . . Cascade Out - CASCADEOUTLAT[A|B] and CASCADEOUTREG[A|B] . . . . . . . Inverting Control Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unused Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 125 125 125 125 125 126 126 127 127 127 127 127

Block RAM Address Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Block RAM Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Content Initialization - INIT_xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Content Initialization - INITP_xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

12

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Output Latches Initialization - INIT (INIT_A or INIT_B) . . . . . . . . . . . . . . . . . . . . . . Output Latches/Registers Synchronous Set/Reset (SRVAL_[A|B]) . . . . . . . . . . . . . Optional Output Register On/Off Switch - DO[A|B]_REG . . . . . . . . . . . . . . . . . . . . Extended Mode Address Determinant - RAM_EXTENSION_[A|B] . . . . . . . . . . . . Read Width - READ_WIDTH_[A|B] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Write Width - WRITE_WIDTH_[A|B] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Write Mode - WRITE_MODE_[A|B] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Block RAM Location Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

129 130 130 130 130 130 130 131

Block RAM Initialization in VHDL or Verilog Code . . . . . . . . . . . . . . . . . . . . . . . . 131 Additional RAMB18 and RAMB36 Primitive Design Considerations . . . . . . . . 131
Optional Output Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Independent Read and Write Port Width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RAMB18 and RAMB36 Port Mapping Design Rules . . . . . . . . . . . . . . . . . . . . . . . . . . Cascadable Block RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Byte-wide Write Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 131 132 132 132

Additional Block RAM Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Block RAM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Creating Larger RAM Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Block RAM SSR in Register Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Block RAM Timing Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Block RAM Timing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Block RAM Timing Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Event 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Event 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Event 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Event 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Block RAM Timing Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 136 136 137 137 137 138

Block RAM Retargeting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Built-in FIFO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Multirate FIFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Synchronous FIFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Synchronous FIFO Implementations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

FIFO Architecture: a Top-Level View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIFO Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIFO Port Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIFO Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . First Word Fall Through (FWFT) Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Empty Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Almost Empty Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Read Error Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Full Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Write Error Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Almost Full Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

142 142 143 144 144 144 144 144 145 145 146 146 146 146 146

FIFO Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

FIFO Almost Full/Empty Flag Offset Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

FIFO VHDL and Verilog Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

13

FIFO Timing Models and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

FIFO Timing Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Case 1: Writing to an Empty FIFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Case 2: Writing to a Full or Almost Full FIFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Case 3: Reading From a Full FIFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Case 4: Reading From An Empty or Almost Empty FIFO . . . . . . . . . . . . . . . . . . . . . . Case 5: Resetting All Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Case 6: Simultaneous Read and Write for Multirate FIFO . . . . . . . . . . . . . . . . . . . . . . 150 151 152 154 155 156 157

FIFO Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Cascading FIFOs to Increase Depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Connecting FIFOs in Parallel to Increase Width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Built-in Error Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

ECC Modes Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Top-Level View of the Block RAM ECC Architecture . . . . . . . . . . . . . . . . . . . . . . . . . Block RAM and FIFO ECC Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Block RAM and FIFO ECC Port Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Block RAM and FIFO ECC Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ECC Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard ECC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ECC Encode-Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ECC Decode-Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ECC Timing Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard ECC Write Timing (Figure 4-31) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard ECC Read Timing (Figure 4-32) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encode-Only ECC Write Timing (Figure 4-31) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encode-Only ECC Read Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Decode-Only ECC Write Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Decode-Only ECC Read Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Block RAM ECC Mode Timing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Deliberate Error in a 72-bit Word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Eight Parity Bits for a 64-bit Word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inserting a Single or Double Bit Error into a 72-bit Word . . . . . . . . . . . . . . . . . . . . . . Block RAM ECC VHDL and Verilog Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 160 161 162 164 165 166 166 167 168 168 168 169 169 169 169 169 170 170 170 171

Legal Block RAM and FIFO Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Chapter 5: Configurable Logic Blocks (CLBs)

CLB Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Slice Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLB/Slice Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Look-Up Table (LUT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storage Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributed RAM and Memory (Available in SLICEM only) . . . . . . . . . . . . . . . . . . . . Read Only Memory (ROM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shift Registers (Available in SLICEM only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiplexers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Designing Large Multiplexers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fast Lookahead Carry Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 177 178 178 180 190 190 195 196 198

CLB / Slice Timing Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

General Slice Timing Model and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Timing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Timing Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Slice Distributed RAM Timing Model and Parameters (Available in SLICEM only)204

14

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Distributed RAM Timing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Distributed RAM Timing Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Slice SRL Timing Model and Parameters (Available in SLICEM only) . . . . . . . . . . . Slice SRL Timing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Slice SRL Timing Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Slice Carry-Chain Timing Model and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . Slice Carry-Chain Timing Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributed RAM Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Port Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shift Registers (SRLs) Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Port Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other Shift Register Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronous Shift Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Static-Length Shift Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiplexer Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Port Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carry Chain Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Port Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

207 208 208 210 210 211 212 213 213 214 214 214 215 215 215 216

CLB Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Chapter 6: SelectIO Resources

I/O Tile Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 SelectIO Resources Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 SelectIO Resources General Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Virtex-5 FPGA I/O Bank Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reference Voltage (VREF) Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output Drive Source Voltage (VCCO) Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtex-5 FPGA Digitally Controlled Impedance (DCI) . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCI Cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Xilinx DCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Controlled Impedance Driver (Source Termination) . . . . . . . . . . . . . . . . . . . . . . . . . . Controlled Impedance Driver with Half Impedance (Source Termination) . . . . . . . . . Input Termination to VCCO (Single Termination) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input Termination to VCCO/2 (Split Termination) . . . . . . . . . . . . . . . . . . . . . . . . . . . Driver with Termination to VCCO (Single Termination) . . . . . . . . . . . . . . . . . . . . . . . . Driver with Termination to VCCO /2 (Split Termination) . . . . . . . . . . . . . . . . . . . . . . . DCI in Virtex-5 Device I/O Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCI Usage Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IBUF and IBUFG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OBUF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OBUFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IOBUF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IBUFDS and IBUFGDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IBUFDS_DIFF_OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OBUFDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OBUFTDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IOBUFDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtex-5 FPGA SelectIO Attributes/Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IOSTANDARD Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 219 219 220 220 220 223 224 224 225 226 227 228 229 230 233 233 234 234 234 235 235 235 236 236 236 236

Virtex-5 FPGA SelectIO Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

15

237 237 237 237 Virtex-5 FPGA I/O Resource VHDL/Verilog Examples . . . . . . . . . . . . . . . . . . . . . . . 238

Output Slew Rate Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output Drive Strength Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PULLUP/PULLDOWN/KEEPER for IBUF, OBUFT, and IOBUF . . . . . . . . . . . . . . . . Differential Termination Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Specific Guidelines for I/O Supported Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

LVTTL (Low Voltage Transistor-Transistor Logic) . . . . . . . . . . . . . . . . . . . . . . . . . . . LVCMOS (Low Voltage Complementary Metal Oxide Semiconductor). . . . . . . . . . LVDCI (Low Voltage Digitally Controlled Impedance) . . . . . . . . . . . . . . . . . . . . . . . . LVDCI_DV2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSLVDCI (High-Speed Low Voltage Digitally Controlled Impedance) . . . . . . . . . . . . PCI-X, PCI-33, PCI-66 (Peripheral Component Interconnect) . . . . . . . . . . . . . . . . . . . GTL (Gunning Transceiver Logic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GTL_DCI Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GTLP (Gunning Transceiver Logic Plus) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GTLP_DCI Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSTL (High-Speed Transceiver Logic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSTL_ I, HSTL_ III, HSTL_ I_18, HSTL_ III_18, HSTL_I_12 . . . . . . . . . . . . . . . . . . . . . HSTL_ I_DCI, HSTL_ III_DCI, HSTL_ I_DCI_18, HSTL_ III_DCI_18 . . . . . . . . . . . . . . HSTL_ II, HSTL_ IV, HSTL_ II_18, HSTL_ IV_18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSTL_ II_DCI, HSTL_ IV_DCI, HSTL_ II_DCI_18, HSTL_ IV_DCI_18 . . . . . . . . . . . . HSTL_ II_T_DCI, HSTL_ II_T_DCI_18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DIFF_HSTL_ II, DIFF_HSTL_II_18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DIFF_HSTL_II_DCI, DIFF_HSTL_II_DCI_18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DIFF_HSTL_I, DIFF_HSTL_I_18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DIFF_HSTL_I_DCI, DIFF_HSTL_I_DCI_18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSTL Class I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Differential HSTL Class I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSTL Class II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Differential HSTL Class II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSTL Class III . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSTL Class IV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSTL_II_T_DCI (1.5V) Split-Thevenin Termination . . . . . . . . . . . . . . . . . . . . . . . . . . HSTL Class I (1.8V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Differential HSTL Class I (1.8V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSTL Class II (1.8V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Differential HSTL Class II (1.8V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSTL Class III (1.8V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSTL Class IV (1.8V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSTL_II_T_DCI_18 (1.8V) Split-Thevenin Termination . . . . . . . . . . . . . . . . . . . . . . . HSTL Class I (1.2V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSTL (Stub-Series Terminated Logic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSTL2_I, SSTL18_I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSTL2_I_DCI, SSTL18_I_DCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSTL2_II, SSTL18_II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSTL2_II_DCI, SSTL18_II_DCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DIFF_SSTL2_I, DIFF_SSTL18_I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DIFF_SSTL2_I_DCI, DIFF_SSTL18_I_DCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DIFF_SSTL2_II, DIFF_SSTL18_II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DIFF_SSTL2_II_DCI, DIFF_SSTL18_II_DCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSTL2_II_T_DCI, SSTL18_II_T_DCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSTL2 Class I (2.5V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Differential SSTL2 Class I (2.5V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 241 243 244 246 247 248 248 249 249 250 250 250 250 251 251 251 251 251 251 252 253 254 256 259 260 262 263 264 265 267 270 271 273 274 274 275 275 275 275 275 275 275 275 275 276 277

16

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

SSTL2 Class II (2.5V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Differential SSTL2 Class II (2.5V). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSTL2_II_T_DCI (2.5V) Split-Thevenin Termination . . . . . . . . . . . . . . . . . . . . . . . . . . SSTL18 Class I (1.8V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Differential SSTL Class I (1.8V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSTL18 Class II (1.8V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Differential SSTL Class II (1.8V). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSTL18_II_T_DCI (1.8V) Split-Thevenin Termination . . . . . . . . . . . . . . . . . . . . . . . . . Differential Termination: DIFF_TERM Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LVDS and Extended LVDS (Low Voltage Differential Signaling) . . . . . . . . . . . . . . . Transmitter Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receiver Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HyperTransport Protocol (HT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reduced Swing Differential Signaling (RSDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BLVDS (Bus LVDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Differential LVPECL (Low-Voltage Positive Emitter-Coupled Logic) . . . . . . . . . . . LVPECL Transceiver Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

279 281 284 285 286 288 291 293 294 294 295 295 296 296 296 297 297

Rules for Combining I/O Standards in the Same Bank . . . . . . . . . . . . . . . . . . . . . . 298

3.3V I/O Design Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 I/O Standard Design Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Mixing Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Simultaneous Switching Output Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Sparse-Chevron Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Nominal PCB Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCB Construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signal Return Current Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Distribution System Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Nominal SSO Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Actual SSO Limits versus Nominal SSO Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Electrical Basis of SSO Noise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parasitic Factors Derating Method (PFDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Weighted Average Calculation of SSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Full Device SSO Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other SSO Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LVDCI and HSLVDCI Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bank 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 306 306 306 306 306 307 312 312 312 314 315 315 315 315

Chapter 7: SelectIO Logic Resources

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 ILOGIC Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Combinatorial Input Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input DDR Overview (IDDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OPPOSITE_EDGE Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAME_EDGE Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAME_EDGE_PIPELINED Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input DDR Primitive (IDDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IDDR VHDL and Verilog Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ILOGIC Timing Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ILOGIC Timing Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ILOGIC Timing Characteristics, DDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 319 319 320 320 321 322 322 322 323

Input/Output Delay Element (IODELAY) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

17

IODELAY Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IODELAY Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IODELAY Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IODELAY Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stability after an Increment/Decrement Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . IODELAY VHDL and Verilog Instantiation Template . . . . . . . . . . . . . . . . . . . . . . . . . IODELAY Turnaround Time Usage Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IDELAYCTRL Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IDELAYCTRL Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IDELAYCTRL Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IDELAYCTRL Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IDELAYCTRL Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IDELAYCTRL Usage and Design Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Combinatorial Output Data and 3-State Control Path . . . . . . . . . . . . . . . . . . . . . . . . . Output DDR Overview (ODDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OPPOSITE_EDGE Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAME_EDGE Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output DDR Primitive (ODDR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ODDR VHDL and Verilog Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OLOGIC Timing Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timing Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

326 327 329 330 331 331 332 337 338 338 339 339 340 345 345 346 346 347 347 348 348 348

OLOGIC Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

Chapter 8: Advanced SelectIO Logic Resources

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Input Serial-to-Parallel Logic Resources (ISERDES). . . . . . . . . . . . . . . . . . . . . . . . . 353
ISERDES Primitive (ISERDES_NODELAY) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISERDES_NODELAY Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Registered Outputs - Q1 to Q6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bitslip Operation - BITSLIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock Enable Inputs - CE1 and CE2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High-Speed Clock Input - CLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High-Speed Clock Input - CLKB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Divided Clock Input - CLKDIV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Serial Input Data from IOB - D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High-Speed Clock for Strobe-Based Memory Interfaces - OCLK . . . . . . . . . . . . . . . . . Reset Input - RST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISERDES_NODELAY Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BITSLIP_ENABLE Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DATA_RATE Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DATA_WIDTH Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INTERFACE_TYPE Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NUM_CE Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SERDES_MODE Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISERDES_NODELAY Clocking Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Networking Interface Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Memory Interface Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISERDES Width Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Guidelines for Expanding the Serial-to-Parallel Converter Bit Width . . . . . . . . . . . . . ISERDES Latencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISERDES Timing Model and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 355 355 356 356 357 357 357 357 357 357 358 358 358 359 359 360 360 360 360 361 361 362 363 363

18

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Timing Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Reset Input Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

ISERDES VHDL and Verilog Instantiation Template. . . . . . . . . . . . . . . . . . . . . . . . . . BITSLIP Submodule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bitslip Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bitslip Timing Model and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

365 366 366 368

Output Parallel-to-Serial Logic Resources (OSERDES) . . . . . . . . . . . . . . . . . . . . . . 370

Data Parallel-to-Serial Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 3-State Parallel-to-Serial Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

OSERDES Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OSERDES Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Path Output - OQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-state Control Output - TQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High-Speed Clock Input - CLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Divided Clock Input - CLKDIV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parallel Data Inputs - D1 to D6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output Data Clock Enable - OCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parallel 3-state Inputs - T1 to T4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-state Signal Clock Enable - TCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reset Input - SR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OSERDES Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DATA_RATE_OQ Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DATA_RATE_TQ Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DATA_WIDTH Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SERDES_MODE Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRISTATE_WIDTH Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OSERDES Clocking Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OSERDES Width Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Guidelines for Expanding the Parallel-to-Serial Converter Bit Width . . . . . . . . . . . . . OSERDES Latencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OSERDES Timing Model and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timing Characteristics of 2:1 SDR Serialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timing Characteristics of 8:1 DDR Serialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timing Characteristics of 4:1 DDR 3-State Controller Serialization . . . . . . . . . . . . . . . Reset Output Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OSERDES VHDL and Verilog Instantiation Templates . . . . . . . . . . . . . . . . . . . . . . . .

371 372 372 372 372 372 373 373 373 373 373 374 374 374 375 375 375 375 375 376 377 377 378 379 380 381 382 383

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

19

20

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Preface

About This Guide

This document describes the Virtex-5 architecture. Complete and up-to-date documentation of the Virtex-5 family of FPGAs is available on the Xilinx website at http://www.xilinx.com/virtex5.

Additional Documentation
The following documents are also available for download at http://www.xilinx.com/virtex5. Virtex-5 Family Overview The features and product selection of the Virtex-5 family are outlined in this overview. Virtex-5 FPGA Data Sheet: DC and Switching Characteristics This data sheet contains the DC and Switching Characteristic specifications for the Virtex-5 family. Virtex-5 FPGA RocketIO GTP Transceiver User Guide This guide describes the RocketIO GTP transceivers available in the Virtex-5 LXT and SXT platforms. Virtex-5 FPGA RocketIO GTX Transceiver User Guide This guide describes the RocketIO GTX transceivers available in the Virtex-5 TXT and FXT platforms. Virtex-5 FPGA Embedded Processor Block for PowerPC 440 Designs This reference guide is a description of the embedded processor block available in the Virtex-5 FXT platform. Virtex-5 FPGA Tri-Mode Ethernet Media Access Controller This guide describes the dedicated Tri-Mode Ethernet Media Access Controller available in the Virtex-5 LXT, SXT, TXT and FXT platforms. Virtex-5 FPGA Integrated Endpoint Block User Guide for PCI Express Designs This guide describes the integrated Endpoint blocks in the Virtex-5 LXT, SXT, TXT and FXT platforms used for PCI Express designs. XtremeDSP Design Considerations This guide describes the XtremeDSP slice and includes reference designs for using the DSP48E slice.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

21

Preface: About This Guide

Virtex-5 FPGA Configuration Guide This all-encompassing configuration guide includes chapters on configuration interfaces (serial and SelectMAP), bitstream encryption, Boundary-Scan and JTAG configuration, reconfiguration techniques, and readback through the SelectMAP and JTAG interfaces.

Virtex-5 FPGA System Monitor User Guide The System Monitor functionality available in all the Virtex-5 devices is outlined in this guide.

Virtex-5 FPGA Packaging and Pinout Specification This specification includes the tables for device/package combinations and maximum I/Os, pin definitions, pinout tables, pinout diagrams, mechanical drawings, and thermal specifications.

Virtex-5 FPGA PCB Designers Guide This guide provides information on PCB design for Virtex-5 devices, with a focus on strategies for making design decisions at the PCB and interface level.

Additional Support Resources

To find additional documentation, see the Xilinx website at: http://www.xilinx.com/support/documentation/index.htm. 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: http://www.xilinx.com/support.

Typographical Conventions
This document uses the following typographical conventions. An example illustrates each convention.
Convention Meaning or Use References to other documents Italic font Emphasis in text Example See the Virtex-5 FPGA Configuration Guide for more information. The address (F) is asserted after clock event 2.

22

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Typographical Conventions

Online Document
The following conventions are used in this document:
Convention Meaning or Use Example See the section Additional Documentation for details. Refer to Clock Management Summary in Chapter 2 for details. Go to http://www.xilinx.com for the latest documentation.

Blue text

Cross-reference link to a location in the current document

Blue, underlined text

Hyperlink to a website (URL)

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

23

Preface: About This Guide

24

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Chapter 1

Clock Resources
Global and Regional Clocks
For clocking purposes, each Virtex-5 device is divided into regions. The number of regions varies with device size, eight regions in the smallest device to 24 regions in the largest one. Global I/O and regional clocking resources manage complex and simple clocking requirements. Non-clock resources, such as local routing, are not recommended when performing clock functions.

Global Clocks
Each Virtex-5 device has 32 global clock lines that can clock all sequential resources on the whole device (CLB, block RAM, CMTs, and I/O), and also drive logic signals. Any ten of these 32 global clock lines can be used in any region. Global clock lines are only driven by a global clock buffer, which can also be used as a clock enable circuit, or a glitch-free multiplexer. It can select between two clock sources, and can also switch away from a failed clock source. A global clock buffer is often driven by a Clock Management Tile (CMT) to eliminate the clock distribution delay, or to adjust its delay relative to another clock. There are more global clocks than CMTs, but a CMT often drives more than one global clock.

Regional Clocks and I/O Clocks

Each region has two regional clock buffers and four regional clock trees. A Virtex-5 I/O bank spans exactly one region with the exception of some banks in the center column. Each bank with the size identical to a region contains four clock-capable clock inputs. Each of these inputs can differentially or single-endedly drive four I/O clocks and two regional clocks in the same bank or region. In addition, regional clocks can drive regional clock trees in the adjacent regions. When the clock-capable I/Os are driven by single-ended clocks, then the clock must be connected to the positive (P) side of the differential clock capable pin pair. The negative (N) side can be used as a general purpose I/O or left unconnected. The regional clock buffer can be programmed to divide the incoming clock rate by any integer number from 1 to 8. This feature, in conjunction with the programmable serializer/deserializer in the IOB, (see Chapter 8, Advanced SelectIO Logic Resources), allows source-synchronous systems to cross clock domains without using additional logic resources. A third type of clocking resource, I/O clocks, are very fast and serve localized I/O serializer/deserializer circuits. See Chapter 8, Advanced SelectIO Logic Resources.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

25

Chapter 1: Clock Resources

Global Clocking Resources

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 clock resources. The global clocking resources and network consist of the following paths and components: Global Clock Inputs Global Clock Buffers Clock Tree and Nets - GCLK Clock Regions

Global Clock Inputs

Virtex-5 FPGAs contain specialized global clock input locations for use as regular user I/Os if not used as clock inputs. There are 20 global clock inputs per device. Clock inputs can be configured for any I/O standard, including differential I/O standards. Each clock input can be either single-ended or differential. All 20 clock inputs can be differential if desired. When used as outputs, global clock input pins can be configured for any output standard. Each global clock input pin supports any single-ended output standard or any output differential standard.

Global Clock Input Buffer Primitives

The primitives in Table 1-1 are different configurations of the input clock I/O input buffer. Table 1-1: Clock Buffer Primitives
Input I I, IB Output O O Description Input clock buffer for single-ended I/O Input clock buffer for differential I/O

Primitive IBUFG IBUFGDS

These two primitives work in conjunction with the Virtex-5 FPGA I/O resource by setting the IOSTANDARD attribute to the desired standard. Refer to Chapter 6, I/O Compatibility Table 6-39 for a complete list of possible I/O standards.

Clock Gating for Power Savings

The Virtex-5 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 resources. A clock can drive a BUFGCE input, and a BUFGCE output can drive distinct regions of logic. For example, if all the logic that is required to always be operating is constrained to a few clocking regions, then the BUFGCE output can drive those regions. Toggling the enable of the BUFGCE provides a simple means of stopping all dynamic power consumption in the logic regions available for power savings. The Xilinx Power Estimator (XPE) or the Xilinx Power Analyzer (XPower) tools are 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.

26

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Global Clocking Resources

Global Clock Buffers

There are 32 global clock buffers in every Virtex-5 device. Each half of the die (top/bottom) contains 16 global clock buffers. A global clock input can directly connect from the P-side of the differential input pin pair to any global clock buffer input in the same half, either top or bottom, of the device. Each differential global clock pin pair can connect to either a differential or single-ended clock on the PCB. If using a single-ended clock, then the P-side of the pin pair must be used because a direct connection only exists on this pin. For pin naming conventions please refer to the Virtex-5 Family Packaging Specifications. A singleended clock must be connected to the positive (P) side of the differential global clock pins. If a single-ended clock is connected to the P-side of a differential pin pair, then the N-side can not be used as another single-ended clock pin. However, it can be used as a user I/O. The 20 global clock pins on Virtex-5 devices can be connected to 20 differential or 20 singleended board clocks. 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: Global clock inputs Clock Management Tile (CMT) outputs including: Digital Clock Managers (DCMs) Phase-Locked Loops (PLLs)

Other global clock buffer outputs General interconnect

The global clock buffers can only be driven by sources in the same half of the die (top/bottom). All global clock buffers can drive all clock regions in Virtex-5 devices. The primary/secondary rules from Virtex-II and Virtex-II Pro FPGAs do not apply. However, only ten different clocks can be driven in a single clock region. A clock region (20 CLBs) is a branch of the clock tree consisting of ten CLB rows up and ten CLB rows down. A clock region only spans halfway across the device. The clock buffers are designed to be configured as a synchronous or asynchronous glitchfree 2:1 multiplexer with two clock inputs. Virtex-5 FPGA control pins provide a wide range of functionality and robust input switching. The following subsections detail the various configurations, primitives, and use models of the Virtex-5 FPGA clock buffers.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

27

Chapter 1: Clock Resources

Global Clock Buffer Primitives

The primitives in Table 1-2 are different configurations of the global clock buffers. Table 1-2: Global Clock Buffer Primitives
Input I0, I1 I I I I0, I1 I0, I1 I0, I1 Output O O O O O O O Control CE0, CE1, IGNORE0, IGNORE1, S0, S1 CE CE S S S

Primitive(1) BUFGCTRL BUFG BUFGCE BUFGCE_1 BUFGMUX BUFGMUX_1 BUFGMUX_CTRL(2)

Notes:

1. All primitives are derived from a software preset of BUFGCTRL. 2. This primitive replaces the BUFGMUX_VIRTEX4 primitive.

BUFGCTRL
The BUFGCTRL primitive shown in Figure 1-1, can switch between two asynchronous clocks. All other global clock buffer primitives are derived from certain configurations of BUFGCTRL. The ISE software tools manage the configuration of all these primitives. 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.
X-Ref Target - Figure 1-1

BUFGCTRL IGNORE1 CE1 S1

I1 O I0

S0 CE0 IGNORE0
ug190_1_01_032206

Figure 1-1:

BUFGCTRL Primitive

28

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Global Clocking Resources

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 has transitioned from High 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. 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 1-3. Table 1-3:
CE0 1 1 0 X 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.

Truth Table for Clock Resources

S0 1 1 X 0 1 CE1 0 X 1 1 1 S1 X 0 1 1 1 O I0 I0 I1 I1 Old Input (1)

Although both S and CE are used to select a desired output, each one of these pins behaves slightly different. When using CE to switch clocks, the change in clock selection can be faster than when using S. Violation in Setup/Hold time of the CE pins causes a glitch at the clock output. On the other hand, using the S pins allows the user to switch between the two clock inputs without regard to Setup/Hold times. It will not result in a glitch. See BUFGMUX_CTRL. The CE pin is designed to allow backward compatibility from Virtex-II and Virtex-II Pro FPGAs.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

29

Chapter 1: Clock Resources

The timing diagram in Figure 1-2 illustrates various clock switching conditions using the BUFGCTRL primitives. Exact timing numbers are best found using the speed specification.
X-Ref Target - Figure 1-2

I0 I1
TBCCCK_CE

CE0 CE1 S0 S1 IGNORE0 IGNORE1

TBCCKO_O TBCCKO_O TBCCKO_O

O
at I0 Begin I1 Begin I0
ug190_1_02_071707

Figure 1-2:

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.

30

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Global Clocking Resources

Table 1-4 summarizes the attributes for the BUFGCTRL primitive. Table 1-4: BUFGCTRL Attributes
Description Initializes the BUFGCTRL output to the specified value after configuration. Sets the positive or negative edge behavior. Sets the output level when changing clock selection. If TRUE, BUFGCTRL output uses the I0 input after configuration(1) If TRUE, BUFGCTRL output uses the I1 input after configuration(1) Possible Values 0 (default), 1

Attribute Name INIT_OUT

PRESELECT_I0 PRESELECT_I1
Notes:

FALSE (default), TRUE FALSE (default), TRUE

1. Both PRESELECT attributes cannot be TRUE at the same time. 2. The LOC constraint is available.

BUFG
BUFG is simply 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 1-3 illustrates the relationship of BUFG and BUFGCTRL. A LOC constraint is available for BUFG.
X-Ref Target - Figure 1-3

IGNORE1 VDD CE1 GND GND S1 BUFG VDD I I1 O I0

VDD S0 VDD CE0 IGNORE0 GND

ug190_1_03_032206

Figure 1-3:

BUFG as BUFGCTRL

The output follows the input as shown in the timing diagram in Figure 1-4.
X-Ref Target - Figure 1-4

BUFG(I) BUFG(O) TBCCKO_O

ug190_1_04_032206

Figure 1-4:

BUFG Timing Diagram

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

31

Chapter 1: Clock Resources

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 1-5 illustrates the relationship of BUFGCE and BUFGCTRL. A LOC constraint is available for BUFGCE and BUFGCE_1.
X-Ref Target - Figure 1-5

BUFGCE as BUFGCTRL IGNORE1 VDD CE1 GND GND S1

BUFGCE CE

VDD I

I1 O I0

VDD S0 CE CE0 IGNORE0 GND

ug190_1_05_032206

Figure 1-5:

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 may result in a glitch. Figure 1-6 illustrates the timing diagram for BUFGCE.
X-Ref Target - Figure 1-6

BUFGCE(I) BUFGCE(CE) BUFGCE(O) TBCCKO_O

TBCCCK_CE

ug190_1_06_032206

Figure 1-6: 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.

32

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Global Clocking Resources

Figure 1-7 illustrates the timing diagram for BUFGCE_1.

X-Ref Target - Figure 1-7

BUFGCE_1(I) BUFGCE_1(CE) BUFGCE_1(O) TBCCKO_O

ug190_1_07_032206

TBCCCK_CE

Figure 1-7:

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 1-8 illustrates the relationship of BUFGMUX and BUFGCTRL. A LOC constraint is available for BUFGMUX and BUFGCTRL.
X-Ref Target - Figure 1-8

GND VDD

IGNORE1 CE1 S1

BUFGMUX I1 O I0 I0 I1 O

VDD S0 CE0 IGNORE0 GND

ug190_1_08_032206

Figure 1-8:

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 might result in a glitch. Switching conditions for BUFGMUX are the same as the CE pins on BUFGCTRL. Figure 1-9 illustrates the timing diagram for BUFGMUX.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

33

Chapter 1: Clock Resources

X-Ref Target - Figure 1-9

TBCCCK_CE S I0 I1 O TBCCKO_O begin switching using I1 TBCCKO_O

ug190_1_09_032306

Figure 1-9: In Figure 1-9: The current clock is I0. S is activated High.

BUFGMUX Timing Diagram

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 1-10 illustrates the timing diagram for BUFGMUX_1. A LOC constraint is available for BUFGMUX and BUFGMUX_1.
X-Ref Target - Figure 1-10

TBCCCK_CE S I0 I1 O TBCCKO_O
ug190_1_10_032306

Figure 1-10: In Figure 1-10: The current clock is I0. S is activated High.

BUFGMUX_1 Timing Diagram

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. If Setup/Hold are met, no glitches or short pulses can appear on the output.

34

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Global Clocking Resources

BUFGMUX_CTRL
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 1-11 illustrates the relationship of BUFGMUX_CTRL and BUFGCTRL.
X-Ref Target - Figure 1-11

S BUFGMUX_CTRL I1 O I0

IGNORE1 GND VDD CE1 S1

I1 O I0

S0 CE0 VDD IGNORE0 GND

UG190_1_11_052009

Figure 1-11:

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 1-12, 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 (assuming INIT_OUT = 0), not the rising edge as for CE0 and CE1. Switching conditions for BUFGMUX_CTRL are the same as the S pin of BUFGCTRL. Figure 1-12 illustrates the timing diagram for BUFGMUX_CTRL.
X-Ref Target - Figure 1-12

S I0 I1 O
TBCCKO_O TBCCKO_O
UG190_1_12_061909

Figure 1-12:

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.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

35

Chapter 1: Clock Resources

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 1-13 illustrates an asynchronous mux with BUFGCTRL design example. Figure 1-14 shows the asynchronous mux timing diagram.
X-Ref Target - Figure 1-13

S Asynchronous MUX Design Example I1 I0 S

IGNORE1 VDD VDD CE1 S1

I1 O I0

S0 CE0 VDD VDD IGNORE0

ug190_1_13_032306

Figure 1-13:
X-Ref Target - Figure 1-14

Asynchronous Mux with BUFGCTRL Design Example

I1 I0 S
TBCCKO_O TBCCKO_O

O
at I0 Begin I1
UG190_1_14_032306

Figure 1-14: In Figure 1-14: The current clock is from I0. S is activated High.

Asynchronous Mux Timing Diagram

The Clock output immediately switches to I1. When Ignore signals are asserted High, glitch protection is disabled.

36

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Global Clocking Resources

BUFGMUX_CTRL with a Clock Enable

A BUFGMUX_CTRL with a clock enable BUFGCTRL configuration allows the user to choose between the incoming clock inputs. If needed, the clock enable is used to disable the output. Figure 1-15 illustrates the BUFGCTRL usage design example and Figure 1-16 shows the timing diagram.
X-Ref Target - Figure 1-15

CE BUFGMUX_CTRL+CE Design Example I1 O I0 S

GND

IGNORE1 CE1 S1

I1 O I0

S CE GND

S0 CE0 IGNORE0
UG190_1_15_052009

Figure 1-15: BUFGMUX_CTRL with a CE and BUFGCTRL

X-Ref Target - Figure 1-16

1 I0 I1 S

TBCCCK_CE

CE
TBCCKO_O TBCCKO_O

O
at I0 Begin I1 Clock Off
ug190_1_16_040907

Figure 1-16: In Figure 1-16:

BUFGMUX_CTRL with a CE Timing Diagram

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. The clock output is switched Low and kept at Low after a High to Low transition of I1 is completed.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

37

Chapter 1: Clock Resources

Clock Tree and Nets - GCLK

Virtex-5 clock trees are designed for low-skew and low-power operation. Any unused branch is disconnected. The clock trees also manage the load/fanout when all the logic resources are used. All global clock lines and buffers are implemented differentially. This facilitates much better duty cycles and common-mode noise rejection. In the Virtex-5 architecture, the pin access of the global clock lines are not limited to the logic resources clock pins. The global clock lines can access other pins in the CLBs without using local interconnects. Applications requiring a very fast signal connection and large load/fanout benefit from this architecture.

Clock Regions
Virtex-5 devices improve the clocking distribution by the use of clock regions. Each clock region can have up to 10 global clock domains. These 10 global clocks can be driven by any combination of the 32 global clock buffers. The dimensions of a clock region are fixed to 20 CLBs tall (40 IOBs) and spanning half of the die (Figure 1-17). By fixing the dimensions of the clock region, larger Virtex-5 devices can have more clock regions. As a result, Virtex-5 devices can support many more multiple clock domains than previous FPGA architectures. Table 1-5 shows the number of clock regions in each Virtex-5 device. The logic resources in the center column (CMTs, IOBs, etc.) are located in the left clock regions. The CMTs, if used, utilize the global clocks in the left regions as feedback lines. Up to four CMTs can be in a specific region. If used in the same region, IDELAYCTRL uses another global clock in that region. See Chapter 2, Clock Management Technology.
X-Ref Target - Figure 1-17

XC5VLX30 has 8 Clock Regions

10 CLBs 10 CLBs

XC5VLX330 has 24 Clock Regions

All clock regions span half the die

All clock regions are 20 CLBs tall (10 CLBs above and 10 CLBs below a horizontal clock line)

Center Column Logic Resources

ug190_1_17_042406

Figure 1-17:

Clock Regions

38

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Global Clocking Resources

Table 1-5:
Device XC5VLX30 XC5VLX50 XC5VLX85

Virtex-5 FPGA Clock Regions

Number of Clock Regions 8 12 12 16 16 16 24 6 There are 3 regions on each side of the device. There are no BUFRs on the right side of this device. Notes

XC5VLX110 XC5VLX155 XC5VLX220 XC5VLX330 XC5VLX20T

XC5VLX30T XC5VLX50T XC5VLX85T XC5VLX110T XC5VLX155T XC5VLX220T XC5VLX330T XC5VTX150T XC5VTX240T XC5VSX35T XC5VSX50T XC5VSX95T XC5VSX240T XC5VFX30T XC5VFX70T XC5VFX100T XC5VFX130T XC5VFX200T

8 12 12 16 16 16 24 20 24 8 12 16 24 8 16 16 20 24

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

39

Chapter 1: Clock Resources

Regional Clocking Resources

Regional clock networks are a set of clock networks independent of the global clock network. Unlike global clocks, the span of a regional clock signal (BUFR) is limited to three clock regions, while the I/O clock signal drives a single region only. These networks are especially useful for source-synchronous interface designs. The I/O banks in Virtex-5 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 Virtex-5 devices consist of the following paths and components: Clock Capable I/O I/O Clock Buffer - BUFIO Regional Clock Buffer - BUFR Regional Clock Nets

Clock Capable I/O

In a typical clock region there are four clock-capable I/O pin pairs (there are exceptions in the center column). Clock-capable I/O pairs are regular I/O pairs in select locations with special hardware connections to nearby regional clock resources. Some global clock inputs are also clock-capable I/Os. There are four dedicated clock-capable I/O sites in every bank. When used as clock inputs, clock-capable pins can drive BUFIO and BUFR. Clockcapable I/Os in the center column can not drive BUFRs. Clock-capable I/Os can not directly connect to the global clock buffers. 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.

40

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Regional Clocking Resources

I/O Clock Buffer - BUFIO

The I/O clock buffer (BUFIO) is a clock buffer available in Virtex-5 devices. The BUFIO drives a dedicated clock net within the I/O column, independent of the global clock resources. Thus, BUFIOs are ideally suited for source-synchronous data capture (forwarded/receiver clock distribution). BUFIOs can only be driven by clock capable I/Os located in the same clock region. In a typical clock region, there are four BUFIOs. Each BUFIO can drive a single I/O clock network in the same region/bank, as well as the regional clock buffers (BUFR). BUFIOs cannot drive logic resources (CLB, block RAM, IODELAY, etc.) because the I/O clock network only reaches the I/O column in the same bank or clock region.

BUFIO Primitive
BUFIO is simply a clock in, clock out buffer. There is a phase delay between input and output. Figure 1-18 shows the BUFIO. Table 1-6 lists the BUFIO ports. A location constraint is available for BUFIO.
X-Ref Target - Figure 1-18

BUFIO

ug190_1_18_032306

Figure 1-18: Table 1-6:

BUFIO Primitive

BUFIO Port List and Definitions

Type Output Input 1 1 Width Definition Clock output port Clock input port

Port Name O I

BUFIO Use Models

In Figure 1-19, 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.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

41

Chapter 1: Clock Resources

X-Ref Target - Figure 1-19

I/O I/O I/O I/O I/O I/O P Clock Capable I/O N P Clock Capable I/O N I/O BUFIO BUFR Not all available BUFIOs are shown. BUFR I/O I/O I/O

To Adjacent Region

To Fabric

BUFIO P Clock Capable I/O N P Clock Capable I/O N I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O

To Adjacent Region
ug190_1_19_060706

Figure 1-19:

BUFIO Driving I/O Logic In a Single Clock Region

Regional Clock Buffer - BUFR

The regional clock buffer (BUFR) is another clock buffer available in Virtex-5 devices. BUFRs drive clock signals to a dedicated clock net within a clock region, independent from

42

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Regional Clocking Resources

the global clock tree. Each BUFR can drive the four regional clock nets in the region it is located, and the four clock nets in the adjacent clock regions (up to three clock regions). Unlike BUFIOs, BUFRs can drive the I/O logic and logic resources (CLB, block RAM, etc.) in the existing and adjacent clock regions. BUFRs can be driven by clock capable pins or local interconnect. In addition, BUFR is 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-toparallel conversion. There are two BUFRs in a typical clock region (four regional clock networks). The center column does not have BUFRs.

BUFR Primitive
BUFR is a clock-in/clock-out buffer with the capability to divide the input clock frequency.
X-Ref Target - Figure 1-20

CE CLR
ug190_1_20_032306

Figure 1-20: Table 1-7:

BUFR Primitive

BUFR Port List and Definitions

Type Output Input Input 1 1 1 Width Definition Clock output port Clock enable port. Cannot be used in BYPASS mode. Asynchronous clear for the divide logic, and sets the output Low. Cannot be used in BYPASS mode. Clock input port

Port Name O CE CLR

Input

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, BUFR does not toggle, 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.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

43

Chapter 1: Clock Resources

BUFR Attributes and Modes

Clock division in the BUFR is controlled in software through the BUFR_DIVIDE attribute. Table 1-8 lists the possible values when using the BUFR_DIVIDE attribute. Table 1-8: BUFR_DIVIDE Attribute
Description Defines whether the output clock is a divided version of the input clock. Possible Values 1, 2, 3, 4, 5, 6, 7, 8 BYPASS (default)

Attribute Name BUFR_DIVIDE

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 1-21. In this example, the BUFR_DIVIDE attribute is set to three. Sometime before this diagram CLR was asserted.
X-Ref Target - Figure 1-21

1 I CE CLR
TBRCKO_O TBRDO_CLRO

TBRCKO_O

O
ug190_1_21_041808

Figure 1-21: In Figure 1-21:

BUFR Timing Diagrams with BUFR_DIVIDE Values

Before clock event 1, CE is asserted High. 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: 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.

44

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Regional Clocking Resources

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 1-22 is a BUFR design example.
X-Ref Target - Figure 1-22

To Region Above
I/O Tile I/O Tile I/O Tile I/O Tile I/O Tile I/O Tile I/O Tile Clock Capable I/O I/O Tile BUFIO BUFR CLBs CLBs CLBs CLBs CLBs CLBs CLBs CLBs Block RAM DSP Tile Block RAM DSP Tile

To Center of Die To Region Below

Figure 1-22: BUFR Driving Various Logic Resources
UG190_c1_22_022609

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

45

Chapter 1: Clock Resources

Regional Clock Nets

In addition to global clock trees and nets, Virtex-5 devices contain regional clock nets. These clock trees are also designed for low-skew and low-power operation. Unused branches are disconnected. The clock trees also manage the load/fanout when all the logic resources are used. Regional clock nets do not propagate throughout the whole Virtex-5 device. Instead, they are limited to only one clock region. One clock region contains four independent regional clock nets. To access regional clock nets, BUFRs must be instantiated. A BUFR can drive regional clocks in up to two adjacent clock regions (Figure 1-23). BUFRs in the top or bottom region can only access one adjacent region; below or above respectively. The left side BUFRs can feed the center column I/Os.
X-Ref Target - Figure 1-23

BUFRs

ug190_1_23_012306

Figure 1-23:

BUFR Driving Multiple Regions

VHDL and Verilog Templates

The VHDL and Verilog code for all clocking resource primitives and ISE language templates are available in the Libraries Guide.

46

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Chapter 2

Clock Management Technology

Clock Management Summary
The Clock Management Tiles (CMTs) in the Virtex-5 family provide very flexible, highperformance clocking. Each CMT contains two DCMs and one PLL. Figure 2-1 shows a simplified view of the center column resources including the CMT block, where the DCM is located. Each CMT block contains two DCMs and one PLL.
X-Ref Target - Figure 2-1

I/O Banks (Larger Devices Only) CMT Blocks (Top Half DCMs/PLLs) Clock I/O (Top Half) Config I/O (Top Half) Config Blocks and BUFGs Config I/O (Bottom Half) Clock I/O (Bottom Half) CMT Blocks (Bottom Half DCMs/PLLs) I/O Banks (Larger Devices Only)
UG190_c2_01_022609

Virtex-5 FPGA Center Column

Figure 2-1:

CMT Location

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

47

Chapter 2: Clock Management Technology

Table 2-1 summarizes the availability of CMTs, DCMs, and PLLs in each Virtex-5 device. Table 2-1: Available CMT, DCM, and PLL Resources
Number of CMTs 1 2 Available DCMs 2 4 Bottom half: DCM_ADV_X0Y0, DCM_ADV_X0Y1, PLL_ADV_X0Y0 XC5VLX30 XC5VFX30T XC5VLX30T XC5VSX35T XC5VLX50 XC5VLX50T XC5VSX50T XC5VFX70T XC5VLX85 XC5VLX85T XC5VSX95T XC5VFX100T XC5VLX110 XC5VLX110T XC5VFX130T XC5VTX150T XC5VLX155 XC5VLX155T XC5VFX200T XC5VLX220 XC5VLX220T XC5VSX240T XC5VTX240T XC5VLX330 XC5VLX330T Bottom half: DCM_ADV_X0Y0, DCM_ADV_X0Y1, PLL_ADV_X0Y0 Top half: DCM_ADV_X0Y2, DCM_ADV_X0Y3, PLL_ADV_X0Y1 6 12 Bottom half: DCM_ADV_X0Y0, DCM_ADV_X0Y1, PLL_ADV_X0Y0 DCM_ADV_X0Y2, DCM_ADV_X0Y3, PLL_ADV_X0Y1 DCM_ADV_X0Y4, DCM_ADV_X0Y5, PLL_ADV_X0Y2 Top half: DCM_ADV_X0Y6, DCM_ADV_X0Y7, PLL_ADV_X0Y3 DCM_ADV_X0Y8, DCM_ADV_X0Y9, PLL_ADV_X0Y4 DCM_ADV_X0Y10, DCM_ADV_X0Y11, PLL_ADV_X0Y5 Site Names

Device XC5VLX20T

DCM Summary
The Digital Clock Managers (DCMs) in Virtex-5 FPGAs provide a wide range of powerful clock management features: Clock Deskew The DCM contains a delay-locked loop (DLL) to completely eliminate clock distribution delays, by deskewing the DCM's output clocks with respect to the input clock. The DLL contains delay elements (individual small buffers) and control logic. The incoming clock drives a chain of delay elements, thus the output of every delay element represents a version of the incoming clock delayed at a different point. The control logic contains a phase detector and a delay-line selector. The phase detector compares the incoming clock signal (CLKIN) against a feedback input (CLKFB) and steers the delay line selector, essentially adding delay to the output of DCM until the CLKIN and CLKFB coincide.

48

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

DCM Summary

Frequency Synthesis Separate outputs provide a doubled frequency (CLK2X and CLK2X180). Another output, CLKDV, provides a frequency that is a specified fraction of the input frequency. Two other outputs, CLKFX and CLKFX180, provide an output frequency derived from the input clock by simultaneous frequency division and multiplication. The user can specify any integer multiplier (M) and divisor (D) within the range specified in the DCM Timing Parameters section of the Virtex-5 FPGA Data Sheet. An internal calculator determines the appropriate tap selection, to make the output edge coincide with the input clock whenever mathematically possible. For example, M = 9 and D = 5, multiply the frequency by 1.8, and the output rising edge is coincident with the input rising edge after every fifth input period, or after every ninth output period.

Phase Shifting The DCM allows coarse and fine-grained phase shifting. The coarse phase shifting uses the 90, 180, and 270 phases of CLK0 to make CLK90, CLK180, and CLK270 clock outputs. The 180 phase of CLK2X and CLKFX provide the respective CLK2X180 and CLKFX180 clock outputs. There are also four modes of fine-grained phase-shifting; fixed, variable-positive, variable-center, and direct modes. Fine-grained phase shifting allows all DCM output clocks to be phase-shifted with respect to CLKIN while maintaining the relationship between the coarse phase outputs. With fixed mode, a fixed fraction of phase shift can be defined during configuration and in multiples of the clock period divided by 256. Using the variable-positive and variable-center modes the phase can be dynamically and repetitively moved forward and backwards by 1/256 of the clock period. With the direct mode the phase can be dynamically and repetitively moved forward and backwards by the value of one DCM_TAP. See the DCM Timing Parameters section in the Virtex-5 FPGA Data Sheet.

Dynamic Reconfiguration There is a bus connection to the DCM to change DCM attributes without reconfiguring the rest of the device. For more information, see the Dynamic Reconfiguration chapter of the Virtex-5 FPGA Configuration Guide. The DADDR[6:0], DI[15:0], DWE, DEN, DCLK inputs and DO[15:0], and DRDY outputs are available to dynamically reconfigure select DCM functions. With dynamic reconfiguration, DCM attributes can be changed to select a multiply (M) or divide (D) from the currently configured settings.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

49

Chapter 2: Clock Management Technology

DCM Primitives
The DCM primitives DCM_BASE and DCM_ADV are shown in Figure 2-2.
X-Ref Target - Figure 2-2

DCM_BASE
CLKIN CLKFB RST CLK0 CLK90 CLK180 CLK270 CLK2X CLK2X180 CLKDV CLKFX CLKFX180 LOCKED

DCM_ADV
CLKIN CLKFB RST CLK0 CLK90 CLK180 CLK270

PSINCDEC CLK2X PSEN CLK2X180 PSCLK CLKDV DADDR[6:0] CLKFX DI[15:0] CLKFX180 DWE LOCKED DEN DCLK PSDONE DO[15:0] DRDY
ug190_2_02_042706

Figure 2-2:

DCM Primitives

DCM_BASE Primitive
The DCM_BASE primitive accesses the basic frequently used DCM features and simplifies the user-interface ports. The clock deskew, frequency synthesis, and fixed-phase shifting features are available to use with DCM_BASE. Table 2-2 lists the available ports in the DCM_BASE primitive. Table 2-2: DCM_BASE Primitive
Port Names CLKIN, CLKFB RST CLK0, CLK90, CLK180, CLK270, CLK2X, CLK2X180, CLKDV, CLKFX, CLKFX180 LOCKED Available Ports Clock Input Control and Data Input Clock Output Status and Data Output

50

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

DCM Ports

DCM_ADV Primitive
The DCM_ADV primitive has access to all DCM features and ports available in DCM_BASE plus additional ports for the dynamic reconfiguration feature. It is a superset of the DCM_BASE primitive. DCM_ADV uses all the DCM features including clock deskew, frequency synthesis, fixed or variable phase shifting, and dynamic reconfiguration. Table 2-3 lists the available ports in the DCM_ADV primitive. Table 2-3: DCM_ADV Primitive
Port Names CLKIN, CLKFB, PSCLK, DCLK RST, PSINCDEC, PSEN, DADDR[6:0], DI[15:0], DWE, DEN CLK0, CLK90, CLK180, CLK270, CLK2X, CLK2X180, CLKDV, CLKFX, CLKFX180 LOCKED, PSDONE, DO[15:0], DRDY Available Ports Clock Input Control and Data Input Clock Output Status and Data Output

DCM Ports
There are four types of DCM ports available in the Virtex-5 architecture: DCM Clock Input Ports DCM Control and Data Input Ports DCM Clock Output Ports DCM Status and Data Output Ports

DCM Clock Input Ports

Source Clock Input - CLKIN
The source clock (CLKIN) input pin provides the source clock to the DCM. The CLKIN frequency must fall in the ranges specified in the Virtex-5 FPGA Data Sheet. If CLKIN is stopped for 100 ms or longer, the DCM powers down. The clock input signal comes from one of these buffers: 1. IBUFG Global Clock Input Buffer The DCM compensates for the clock input path when CLKFB is connected and an IBUFG on the same half (top or bottom) of the device as the DCM is used. 2. BUFGCTRL Internal Global Clock Buffer Any BUFGCTRL can drive any DCM in the Virtex-5 device using dedicated global routing. A BUFGCTRL can drive the DCM CLKIN pin when used to connect two DCMs in series. 3. PLL Phase-Locked Loop A PLL block within the same CMT can drive the CLKIN input of either DCM in the CMT block. No global buffer is required in between. See Application Examples, page 75 for more information. 4. IBUF Input Buffer When an IBUF drives the CLKIN input, the PAD to DCM input skew is not compensated.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

51

Chapter 2: Clock Management Technology

Feedback Clock Input - CLKFB

The feedback clock (CLKFB) input pin provides a reference or feedback signal to the DCM to delay-compensate the clock outputs, and align them with the clock input. To provide the necessary feedback to the DCM, connect only the CLK0 DCM output to the CLKFB pin. When the CLKFB pin is connected, all clock outputs are deskewed to CLKIN. When the CLKFB pin is not connected, DCM clock outputs are not deskewed to CLKIN. However, the relative phase relationship between all output clocks is preserved. During internal feedback configuration, the CLK0 output of a DCM connects to a global buffer on the same top or bottom half of the device. The output of the global buffer connects to the CLKFB input of the same DCM. During the external feedback configuration, the following rules apply: 1. 2. To forward the clock, the CLK0 of the DCM must directly drive an OBUF or a BUFGto-DDR configuration. External to the FPGA, the forwarded clock signal must be connected to the IBUFG (GCLK pin) or the IBUF driving the CLKFB of the DCM. Both CLK and CLKFB should have identical I/O buffers.

Figure 2-9 illustrates clock forwarding with external feedback configuration. The feedback clock input signal can be driven by one of the following buffers: 1. IBUFG Global Clock Input Buffer This is the preferred source for an external feedback configuration. When an IBUFG drives a CLKFB pin of a DCM in the same top or bottom half of the device, the pad to DCM skew is compensated for deskew. 2. 3. BUFGCTRL Internal Global Clock Buffer This is an internal feedback configuration driven by CLK0. IBUF Input Buffer This is an external feedback configuration. When IBUF is used, the PAD to DCM input skew is not compensated and performance can not be guaranteed.

Phase-Shift Clock Input - PSCLK

The phase-shift clock (PSCLK) input pin provides the source clock for the DCM phase shift. The PSCLK can be asynchronous (in phase and frequency) to CLKIN. The phase-shift clock signal can be driven by any clock source (external or internal), including: 1. 2. IBUF Input Buffer IBUFG Global Clock Input Buffer To access the dedicated routing, only the IBUFGs on the same half of the device (top or bottom) as the DCM can be used to drive a PSCLK input of the DCM. 3. 4. BUFGCTRL An Internal Global Buffer Internal Clock Any internal clock using general purpose routing.

The frequency range of PSCLK is defined by PSCLK_FREQ_LF/HF. See the Virtex-5 FPGA Data Sheet. This input must be tied to ground when the CLKOUT_PHASE_SHIFT attribute is set to NONE or FIXED.

52

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

DCM Ports

Dynamic Reconfiguration Clock Input - DCLK

The dynamic reconfiguration clock (DCLK) input pin provides the source clock for the DCM's dynamic reconfiguration circuit. The frequency of DCLK can be asynchronous (in phase and frequency) to CLKIN. The dynamic reconfiguration clock signal is driven by any clock source (external or internal), including: 1. 2. IBUF Input Buffer IBUFG Global Clock Input Buffer Only the IBUFGs on the same half of the device (top or bottom) as the DCM can be used to drive a CLKIN input of the DCM. 3. 4. BUFGCTRL An Internal Global Buffer Internal Clock Any internal clock using general purpose routing.

The frequency range of DCLK is described in the Virtex-5 FPGA Data Sheet. When dynamic reconfiguration is not used, this input must be tied to ground. See the dynamic reconfiguration chapter in the Virtex-5 FPGA Configuration Guide for more information.

DCM Control and Data Input Ports

Reset Input - RST
The reset (RST) input pin resets the DCM circuitry. The RST signal is an active High asynchronous reset. Asserting the RST signal asynchronously forces all DCM outputs Low (the LOCKED signal, all status signals, and all output clocks) after some propagation delay. When the reset is asserted, the last cycle of the clocks can exhibit a short pulse and a severely distorted duty cycle, or no longer be deskewed with respect to one another while asserting High. Deasserting the RST signal starts the locking process at the next CLKIN cycle. To ensure a proper DCM reset and locking process, the RST signal must be held until the CLKIN signal is present and stable for at least three CLKIN cycles. The time it takes for the DCM to lock after a reset is specified in the Virtex-5 FPGA Data Sheet as LOCK_DLL (for a DLL output) and LOCK_FX (for a DFS output). These are the CLK and CLKFX outputs described in DCM Clock Output Ports. The DCM locks faster at higher frequencies. The worse-case numbers are specified in the Virtex-5 FPGA Data Sheet. In all designs, the DCM must be held in reset until CLKIN is stable.

Phase-Shift Increment/Decrement Input - PSINCDEC

The phase-shift increment/decrement (PSINCDEC) input signal must be synchronous with PSCLK. The PSINCDEC input signal is used to increment or decrement the phaseshift factor when PSEN is activated. As a result, the output clocks are shifted. The PSINCDEC signal is asserted High for increment or deasserted Low for decrement. This input must be tied to ground when the CLKOUT_PHASE_SHIFT attribute is set to NONE or FIXED.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

53

Chapter 2: Clock Management Technology

Phase-Shift Enable Input - PSEN

The phase-shift enable (PSEN) input signal must be synchronous with PSCLK. A variable phase-shift operation is initiated by the PSEN input signal. It must be activated for one period of PSCLK. After PSEN is initiated, the phase change is gradual with completion indicated by a High pulse on PSDONE. There are no sporadic changes or glitches on any output during the phase transition. From the time PSEN is enabled until PSDONE is flagged, the DCM output clock moves bit-by-bit from its original phase shift to the target phase shift. The phase shift is complete when PSDONE is flagged. PSEN must be tied to ground when the CLKOUT_PHASE_SHIFT attribute is set to NONE or FIXED. Figure 2-6 shows the timing for this input.

Dynamic Reconfiguration Data Input - DI[15:0]

The dynamic reconfiguration data (DI) input bus provides reconfiguration data for dynamic reconfiguration. When not used, all bits must be assigned zeros. See the Dynamic Reconfiguration chapter of the Virtex-5 FPGA Configuration Guide for more information.

Dynamic Reconfiguration Address Input - DADDR[6:0]

The dynamic reconfiguration address (DADDR) input bus provides a reconfiguration address for the dynamic reconfiguration. When not used, all bits must be assigned zeros and the DO output bus reflects the DCMs status. See the Dynamic Reconfiguration chapter of the Virtex-5 FPGA Configuration Guide for more information.

Dynamic Reconfiguration Write Enable Input - DWE

The dynamic reconfiguration write enable (DWE) input pin provides the write enable control signal to write the DI data into the DADDR address. When not used, it must be tied Low. See the Dynamic Reconfiguration chapter of the Virtex-5 FPGA Configuration Guide for more information.

Dynamic Reconfiguration Enable Input - DEN

The dynamic reconfiguration enable (DEN) input pin provides the enable control signal to access the dynamic reconfiguration feature. When the dynamic reconfiguration feature is not used, DEN must be tied Low. When DEN is tied Low, DO reflects the DCM status signals. See the Dynamic Reconfiguration chapter of the Virtex-5 FPGA Configuration Guide for more information.

DCM Clock Output Ports

A DCM provides nine clock outputs with specific frequency and phase relationships. When CLKFB is connected, all DCM clock outputs have a fixed phase relationship to CLKIN. When CLKFB is not connected, the DCM outputs are not phase aligned. However, the phase relationship between all output clocks is preserved.

1x Output Clock - CLK0

The CLK0 output clock provides a clock with the same frequency as the DCMs effective CLKIN frequency. By default, the effective input clock frequency is equal to the CLKIN frequency. Set the CLKIN_DIVIDE_BY_2 attribute to TRUE to make the effective CLKIN frequency the actual CLKIN frequency. The CLKIN_DIVIDE_BY_2 Attribute description provides further information. When CLKFB is connected, CLK0 is phase aligned to CLKIN.

54

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

DCM Ports

1x Output Clock, 90 Phase Shift - CLK90

The CLK90 output clock provides a clock with the same frequency as the DCMs CLK0 phase-shifted by 90.

1x Output Clock, 180 Phase Shift - CLK180

The CLK180 output clock provides a clock with the same frequency as the DCMs CLK0 phase-shifted by 180.

1x Output Clock, 270 Phase Shift - CLK270

The CLK270 output clock provides a clock with the same frequency as the DCMs CLK0 phase-shifted by 270.

2x Output Clock - CLK2X

The CLK2X output clock provides a clock that is phase aligned to CLK0, with twice the CLK0 frequency, and with an automatic 50/50 duty-cycle correction. Until the DCM is locked, the CLK2X output appears as a 1x version of the input clock with a 25/75 duty cycle. This behavior allows the DCM to lock on the correct edge with respect to the source clock.

2x Output Clock, 180 Phase Shift - CLK2X180

The CLK2X180 output clock provides a clock with the same frequency as the DCMs CLK2X phase-shifted by 180.

Frequency Divide Output Clock - CLKDV

The CLKDV output clock provides a clock that is phase aligned to CLK0 with a frequency that is a fraction of the effective CLKIN frequency. The fraction is determined by the CLKDV_DIVIDE attribute. Refer to the CLKDV_DIVIDE Attribute for more information.

Frequency-Synthesis Output Clock - CLKFX

The CLKFX output clock provides a clock with the following frequency definition: CLKFX frequency = (M/D) effective CLKIN frequency In this equation, M is the multiplier (numerator) with a value defined by the CLKFX_MULTIPLY attribute. D is the divisor (denominator) with a value defined by the CLKFX_DIVIDE attribute. Specifications for M and D, as well as input and output frequency ranges for the frequency synthesizer, are provided in the Virtex-5 FPGA Data Sheet. The rising edge of CLKFX output is phase aligned to the rising edges of CLK0, CLK2X, and CLKDV. When M and D to have no common factor, the alignment occurs only once every D cycles of CLK0.

Frequency-Synthesis Output Clock, 180 - CLKFX180

The CLKFX180 output clock provides a clock with the same frequency as the DCMs CLKFX phase-shifted by 180.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

55

Chapter 2: Clock Management Technology

DCM Status and Data Output Ports

Locked Output - LOCKED
The LOCKED output indicates whether the DCM clock outputs are valid, i.e., the outputs exhibit the proper frequency and phase. After a reset, the DCM samples several thousand clock cycles to achieve lock. After the DCM achieves lock, the LOCKED signal is asserted High. The DCM timing parameters section of the Virtex-5 FPGA Data Sheet provides estimates for locking times. To guarantee an established system clock at the end of the start-up cycle, the DCM can delay the completion of the device configuration process until after the DCM is locked. The STARTUP_WAIT attribute activates this feature. The STARTUP_WAIT Attribute description provides further information. Until the LOCKED signal is asserted High, the DCM output clocks are not valid and can exhibit glitches, spikes, or other spurious movement. In particular, the CLK2X output appears as a 1x clock with a 25/75 duty cycle.

Phase-Shift Done Output - PSDONE

The phase-shift done (PSDONE) output signal is synchronous to PSCLK. At the completion of the requested phase shift, PSDONE pulses High for one period of PSCLK. This signal also indicates a new change to the phase shift can be initiated. The PSDONE output signal is not valid if the phase-shift feature is not being used or is in fixed mode.

Status or Dynamic Reconfiguration Data Output - DO[15:0]

The DO output bus provides DCM status or data output when using dynamic reconfiguration (Table 2-4). Further information on using DO as the data output is available in the Dynamic Reconfiguration chapter of the Virtex-5 FPGA Configuration Guide for more information. If the dynamic reconfiguration port is not used, using DCM_BASE instead of DCM_ADV is strongly recommended. Table 2-4:
DO Bit DO[0]

DCM Status Mapping to DO Bus

Status Phase-shift overflow Description Asserted when the DCM is phase-shifted beyond the allowed phase-shift value or when the absolute delay range of the phase-shift delay line is exceeded. DO[0] is deasserted if the phase shift feature is not used (CLKOUT_PHASE_SHIFT=NONE). Asserted when the input clock is stopped (CLKIN remains High or Low for one or more clock cycles). When CLKIN is stopped, the DO[1] CLKIN stopped status is asserted within nine CLKIN cycles. When CLKIN is restarted, CLK0 starts toggling and DO[1] is deasserted within nine clock cycles. Asserted when CLKFX stops. The DO[2] CLKFX stopped status is asserted within 260 cycles after CLKFX stopped. CLKFX does not resume, and DO[2] is not deasserted until the DCM is reset. DO[2] is deasserted if the CLKFX/CLKFX180 output is not used.

DO[1]

CLKIN stopped

DO[2]

CLKFX stopped

56

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

DCM Ports

Table 2-4:
DO Bit DO[3]

DCM Status Mapping to DO Bus (Continued)

Status CLKFB stopped Description Asserted when the feedback clock is stopped (CLKFB remains High or Low for one or more clock cycles). The DO[3] CLKFB stopped status is asserted within six CLKIN cycles after CLKFB is stopped. CLKFB stopped will deassert within six CLKIN cycles when CLKFB resumes after being stopped momentarily. An occasionally skipped CLKFB does not affect the DCM operation. However, stopping CLKFB for a long time can result in the DCM losing LOCKED. When LOCKED is lost, the DCM needs to be reset to resume operation. When the DLL portion of the DCM is not used (for example, when using CLKFX output only), the CLKFB can be left unconnected. In this case, DO[3] is deasserted.

DO[15:4]

Not assigned

When LOCKED is Low (during reset or the locking process), all the status signals are deasserted Low.

Dynamic Reconfiguration Ready Output - DRDY

The dynamic reconfiguration ready (DRDY) output pin provides the response to the DEN signal for the DCMs dynamic reconfiguration feature. Further information on the DRDY pin is available in the dynamic reconfiguration section in the Virtex-5 FPGA Configuration Guide.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

57

Chapter 2: Clock Management Technology

DCM Attributes
A handful of DCM attributes govern the DCM functionality. Table 2-6 summarizes all the applicable DCM attributes. This section provides a detailed description of each attribute. For more information on applying these attributes in UCF, VHDL, or Verilog code, refer to the Constraints Guide at: http://www.support.xilinx.com/support/software_manuals.htm.

CLKDV_DIVIDE Attribute
The CLKDV_DIVIDE attribute controls the CLKDV frequency. The source clock frequency is divided by the value of this attribute. The possible values for CLKDV_DIVIDE are: 1.5, 2, 2.5, 3, 3.5, 4, 4.5, 5, 5.5, 6, 6.5, 7, 7.5, 8, 9, 10, 11, 12, 13, 14, 15, or 16. The default value is 2. In the low frequency mode, any CLKDV_DIVIDE value produces a CLKDV output with a 50/50 duty-cycle. In the high frequency mode, the CLKDV_DIVIDE value must be set to an integer value to produce a CLKDV output with a 50/50 duty-cycle. For non-integer CLKDV_DIVIDE values, the CLKDV output duty cycle is shown in Table 2-5. Table 2-5: Non-Integer CLKDV_DIVIDE
CLKDV Duty Cycle in High Frequency Mode (High Pulse/Low Pulse Value) 1/3 2/5 3/7 4/9 5/11 6/13 7/15

CLKDV_DIVIDE Value 1.5 2.5 3.5 4.5 5.5 6.5 7.5

CLKFX_MULTIPLY and CLKFX_DIVIDE Attribute

The CLKFX_MULTIPLY attribute sets the multiply value (M) of the CLKFX output. The CLKFX_DIVIDE attribute sets the divisor (D) value of the CLKFX output. Both control the CLKFX output making the CLKFX frequency equal the effective CLKIN (source clock) frequency multiplied by M/D. The possible values for M are any integer from two to 33. The possible values for D are any integer from 1 to 32. The default settings are M = 4 and D = 1.

CLKIN_PERIOD Attribute
The CLKIN_PERIOD attribute specifies the source clock period (in nanoseconds). The default value is 0.0 ns. Setting this attribute to the input period values produces the best results.

58

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

DCM Attributes

CLKIN_DIVIDE_BY_2 Attribute
The CLKIN_DIVIDE_BY_2 attribute is used to enable a toggle flip-flop in the input clock path to the DCM. When set to FALSE, the effective CLKIN frequency of the DCM equals the source clock frequency driving the CLKIN input. When set to TRUE, the CLKIN frequency is divided by two before it reaches the rest of the DCM. Thus, the DCM sees half the frequency applied to the CLKIN input and operates based on this frequency. For example, if a 100 MHz clock drives CLKIN, and CLKIN_DIVIDE_BY_2 is set to TRUE; then the effective CLKIN frequency is 50 MHz. Thus, CLK0 output is 50 MHz and CLK2X output is 100 MHz. The effective CLKIN frequency must be used to evaluate any operation or specification derived from CLKIN frequency. The possible values for CLKIN_DIVIDE_BY_2 are TRUE and FALSE. The default value is FALSE.

CLKOUT_PHASE_SHIFT Attribute
The CLKOUT_PHASE_SHIFT attribute indicates the mode of the phase shift applied to the DCM outputs. The possible values are NONE, FIXED, VARIABLE_POSITIVE, VARIABLE_CENTER, or DIRECT. The default value is NONE. When set to NONE, a phase shift cannot be performed and a phase-shift value has no effect on the DCM outputs. When set to FIXED, the DCM outputs are phase-shifted by a fixed phase from the CLKIN. The phase-shift value is determined by the PHASE_SHIFT attribute. If the CLKOUT_PHASE_SHIFT attribute is set to FIXED or NONE, then the PSEN, PSINCDEC, and the PSCLK inputs must be tied to ground. When set to VARIABLE_POSITIVE, the DCM outputs can be phase-shifted in variable mode in the positive range with respect to CLKIN. When set to VARIABLE_CENTER, the DCM outputs can be phase-shifted in variable mode, in the positive and negative range with respect to CLKIN. If set to VARIABLE_POSITIVE or VARIABLE_CENTER, each phase-shift increment (or decrement) increases (or decreases) the phase shift by a period of 1/256 x CLKIN period. When set to DIRECT, the DCM output can be phase-shifted in variable mode in the positive range with respect to CLKIN. Each phase-shift increment/decrement will increase/decrease the phase shift by one DCM_TAP. See the Virtex-5 FPGA Data Sheet. The starting phase in the VARIABLE_POSITIVE and VARIABLE_CENTER modes is determined by the phase-shift value. The starting phase in the DIRECT mode is always zero, regardless of the value specified by the PHASE_SHIFT attribute. Thus, the PHASE_SHIFT attribute should be set to zero when DIRECT mode is used. A non-zero phase-shift value for DIRECT mode can be loaded to the DCM using Dynamic Reconfiguration Ports in the Virtex-5 FPGA Configuration Guide.

CLK_FEEDBACK Attribute
The CLK_FEEDBACK attribute determines the type of feedback applied to the CLKFB. The possible values are 1X or NONE. The default value is 1X. When set to 1X, CLKFB pin must be driven by CLK0. When set to NONE leave the CLKFB pin unconnected.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

59

Chapter 2: Clock Management Technology

DESKEW_ADJUST Attribute
The DESKEW_ADJUST attribute affects the amount of delay in the feedback path. The possible values are SYSTEM_SYNCHRONOUS, SOURCE_SYNCHRONOUS, 0, 1, 2, 3, ..., or 31. The default value is SYSTEM_SYNCHRONOUS. For most designs, the default value is appropriate. In a source-synchronous design, set this attribute to SOURCE_SYNCHRONOUS. The remaining values should only be used after consulting with Xilinx. For more information, consult the Source-Synchronous Settingsection.

DFS_FREQUENCY_MODE Attribute
The DFS_FREQUENCY_MODE attribute specifies the frequency mode of the digital frequency synthesizer (DFS). The possible values are Low and High. The default value is Low. The frequency ranges for both frequency modes are specified in the Virtex-5 FPGA Data Sheet. DFS_FREQUENCY_MODE determines the frequency range of CLKIN, CLKFX, and CLKFX180.

DLL_FREQUENCY_MODE Attribute
The DLL_FREQUENCY_MODE attribute specifies either the High or Low frequency mode of the delay-locked loop (DLL). The default value is Low. The frequency ranges for both frequency modes are specified in the Virtex-5 FPGA Data Sheet.

DUTY_CYCLE_CORRECTION Attribute
The DUTY_CYCLE_CORRECTION attribute controls the duty cycle correction of the 1x clock outputs: CLK0, CLK90, CLK180, and CLK270. The possible values are TRUE and FALSE. The default value is TRUE. When set to TRUE, the 1x clock outputs are duty cycle corrected to be within specified limits. See the Virtex-5 FPGA Data Sheet for details. It is strongly recommended to always set the DUTY_CYCLE_CORRECTION attribute to TRUE. Setting this attribute to FALSE does not necessarily produce output clocks with the same duty cycle as the source clock.

DCM_PERFORMANCE_MODE Attribute
The DCM_PERFORMANCE_MODE attribute allows the choice of optimizing the DCM either for high frequency and low jitter or for low frequency and a wide phase-shift range. The attribute values are MAX_SPEED and MAX_RANGE. The default value is MAX_SPEED. When set to MAX_SPEED, the DCM is optimized to produce high frequency clocks with low jitter. However, the phase-shift range is smaller than when MAX_RANGE is selected. When set to MAX_RANGE, the DCM is optimized to produce low-frequency clocks with a wider phase-shift range. The DCM_PERFORMANCE_MODE affects the following specifications: DCM input and output frequency range, phase-shift range, output jitter, DCM_TAP, CLKIN_CLKFB_PHASE, CLKOUT_PHASE, and dutycycle precision. The Virtex-5 FPGA Data Sheet specifies these values. For most cases, the DCM_PERFORMANCE_MODE attribute should be set to MAX_SPEED (default). Consider changing to MAX_RANGE only in the following situations: The frequency needs to be below the low-frequency limit of the MAX_SPEED setting. A greater absolute phase-shift range is required.

60

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

DCM Attributes

FACTORY_JF Attribute
The Factory_JF attribute affects the DCMs jitter filter characteristics. This attribute controls the DCM tap update rate. The default value is 0xF0F0 corresponding to DLL_FREQUENCY_MODE = LOW and DLL_FREQUENCY_MODE = HIGH.

PHASE_SHIFT Attribute
The PHASE_SHIFT attribute determines the amount of phase shift applied to the DCM outputs. This attribute can be used in both fixed or variable phase-shift mode. If used with variable mode, the attribute sets the starting phase shift. When CLKOUT_PHASE_SHIFT = VARIABLE_POSITIVE, the PHASE_SHIFT value range is 0 to 255. When CLKOUT_PHASE_SHIFT = VARIABLE_CENTER or FIXED, the PHASE_SHIFT value range is 255 to 255. When CLKOUT_PHASE_SHIFT = DIRECT, the PHASE_SHIFT value range is 0 to 1023. The default value is 0. Refer to the Phase Shifting section for information on the phase-shifting operation and its relationship with the CLKOUT_PHASE_SHIFT and PHASE_SHIFT attributes.

STARTUP_WAIT Attribute
The STARTUP_WAIT attribute determines whether the DCM waits in one of the startup cycles for the DCM to lock. The possible values for this attribute are TRUE and FALSE. The default value is FALSE. When STARTUP_WAIT is set to TRUE, and the LCK_cycle BitGen option is used, then the configuration startup sequence waits in the startup cycle specified by LCK_cycle until the DCM is locked. Table 2-6: DCM Attributes
Description
This attribute controls CLKDV such that the source clock is divided by N. This feature provides automatic duty cycle correction such that the CLKDV output pin has a 50/50 duty cycle always in low-frequency mode, as well as for all integer values of the division factor N in high-frequency mode. CLKFX_DIVIDE CLKFX_MULTIPLY CLKIN_PERIOD This specifies the source clock period to help DCM adjust for optimum CLKFX/CLKFX180 outputs. This attribute allows for the input clock frequency to be divided in half when such a reduction is necessary to meet the DCM input clock frequency requirements. Real: 1.5, 2.0, 2.5, 3.0, 3.5, 4.0, 4.5, 5.0, 5.5, 6.0, 6.5, 7.0, 7.5, 8, 9, 10, 11, 12, 13, 14, 15, 16

DCM Attribute Name

CLKDV_DIVIDE

Values

Default Value
2.0

Integer: 1 to 32 Integer: 2 to 32 Real in ns

1 4 0.0

CLKIN_DIVIDE_BY_2

Boolean: FALSE or TRUE

FALSE

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

61

Chapter 2: Clock Management Technology

Table 2-6:

DCM Attributes (Continued)

Description
This attribute specifies the phaseshift mode.

DCM Attribute Name

CLKOUT_PHASE_SHIFT

Values
String: NONE or FIXED or VARIABLE_POSITIVE or VARIABLE_CENTER or DIRECT String: SYSTEM_SYNCHRONOUS or SOURCE_SYNCHRONOUS String: LOW or HIGH String: LOW or HIGH Boolean: TRUE or FALSE

Default Value
NONE

DESKEW_ADJUST

This affects the amount of delay in the feedback path, and should be used for source-synchronous interfaces. This specifies the frequency mode of the frequency synthesizer. This specifies the frequency mode of the DLL. This controls the DCM 1X outputs (CLK0, CLK90, CLK180, and CLK270), to exhibit a 50/50 duty cycle. Leave this attribute set at the default value. Allows selection between maximum frequency/ minimum jitter, and low frequency/maximum phase-shift range DLL_FREQUENCY_MODE=LOW default (0xF0F0). DLL_FREQUENCY_MODE=HIGH default (0xF0F0).

SYSTEM_ SYNCHRONOUS

DFS_FREQUENCY_MODE DLL_FREQUENCY_MODE DUTY_CYCLE_CORRECTION

LOW LOW TRUE

DCM_PERFORMANCE_MODE

String: MAX_SPEED or MAX_RANGE

MAX_SPEED

FACTORY_JF

BIT_VECTOR

0xF0F0

PHASE_SHIFT

This specifies the phase-shift numerator. The value range depends on CLKOUT_PHASE_SHIFT and clock frequency. When this attribute is set to TRUE, the configuration startup sequence waits in the specified cycle until the DCM locks.

Integer: 255 to 1023

STARTUP_WAIT

Boolean: FALSE or TRUE

FALSE

62

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

DCM Design Guidelines

DCM Design Guidelines

This section provides a detailed description on using the Virtex-5 FPGA DCM and design guidelines.

Clock Deskew
The Virtex-5 FPGA DCM offers a fully digital, dedicated, on-chip clock deskew. The deskew feature provides zero propagation delay between the source clock and output clock, low clock skew among output clock signals distributed throughout the device, and advanced clock domain control. The deskew feature also functions as a clock mirror of a board-level clock serving multiple devices. This is achieved by driving the CLK0 output off-chip to the board (and to other devices on the board) and then bringing the clock back in as a feedback clock. See the Application Examples section. Taking advantage of the deskew feature greatly simplifies and improves system-level design involving high-fanout, high-performance clocks.

Clock Deskew Operation

The deskew feature utilizes the DLL circuit in the DCM. In its simplest form, the DLL consists of a single variable delay line (containing individual small delay elements or buffers) and control logic. The incoming clock drives the delay line. The output of every delay element represents a version of the incoming clock (CLKIN) delayed at a different point. The clock distribution network routes the clock to all internal registers and to the clock feedback CLKFB pin. The control logic contains a phase detector and a delay-line selector. The phase detector compares the incoming clock signal (CLKIN) against a feedback input (CLKFB) and steers the delay-line selector, essentially adding delay to the DCM output until the CLKIN and CLKFB coincide, putting the two clocks 360 out-ofphase, (thus, in phase). When the edges from the input clock line up with the edges from the feedback clock, the DCM achieves a lock. The two clocks have no discernible difference. Thus, the DCM output clock compensates for the delay in the clock distribution network, effectively removing the delay between the source clock and its loads. The size of each intrinsic delay element is a DCM_TAP (see the AC Characteristics table in the Virtex-5 FPGA Data Sheet). Figure 2-3 illustrates a simplified DLL circuit.
X-Ref Target - Figure 2-3

CLKIN

Variable Delay Line

CLKOUT

Clock Distribution Network

Control

CLKFB
ug190_2_03_032506

Figure 2-3:

Simplified DLL Circuit

To provide the correct clock deskew, the DCM depends on the dedicated routing and resources used at the clock source and feedback input. An additional delay element (see Deskew Adjust) is available to compensate for the clock source or feedback path. The Xilinx ISE tools analyze the routing around the DCM to determine if a delay must be inserted to compensate for the clock source or feedback path. Thus, using dedicated routing is required to achieve predictable deskew.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

63

Chapter 2: Clock Management Technology

Input Clock Requirements

The clock input of the DCM can be driven either by an IBUFG/IBUFGDS, IBUF, BUFGMUX, or a BUFGCTRL. Since there is no dedicated routing between an IBUF and a DCM clock input, using an IBUF causes additional input delay that is not compensated by the DCM and performance can not be guaranteed. The DCM output clock signal is essentially a delayed version of the input clock signal. It reflects any instability on the input clock in the output waveform. The DCM input clock requirements are specified in the Virtex-5 FPGA Data Sheet. Once locked, the DCM can tolerate input clock period variations of up to the value specified by CLKIN_PER_JITT_DLL_HF (at high frequencies) or CLKIN_PER_JITT_DLL_LF (at low frequencies). Larger jitter (period changes) can cause the DCM to lose lock, indicated by the LOCKED output deasserting. The user must then reset the DCM. The cycle-to-cycle input jitter must be kept to less than CLKIN_CYC_JITT_DLL_LF in the low frequencies and CLKIN_CYC_JITT_DLL_HF for the high frequencies.

Input Clock Changes

Changing the period of the input clock beyond the maximum input period jitter specification requires a manual reset of the DCM. Failure to reset the DCM produces an unreliable LOCKED signal and output clock. It is possible to temporarily stop the input clock and feedback clock with little impact to the deskew circuit, as long as CLKFX or CLKFX180 is not used. If the input clock is stopped and CLKFX or CLKFX180 is used, the CLKFX or CLKFX180 outputs might stop toggling, and DO[2] (CLKFX stopped) is asserted. The DCM must be reset to recover from this event. The DO[2] CLKFX stopped status is asserted 100 s after CLKFX is stopped. CLKFX does not resume and DO[2] does not deassert until the DCM is reset. In any other case, the clock should not be stopped for more than 100 ms to minimize the effect of device cooling; otherwise, the tap delays might change. The clock should be stopped during a Low or a High phase, and must be restored with the same input clock period/frequency. During this time, LOCKED stays High and remains High when the clock is restored. Thus, a High on LOCKED does not necessarily mean that a valid clock is available. When stopping the input clock (CLKIN remains High or Low for one or more clock cycles), one to nine more output clock cycles are still generated as the delay line is flushed. When the output clock stops, the CLKIN stopped (DO[1]) signal is asserted. When the clock is restarted, the output clock cycles are not generated for one to eight clocks while the delay line is filled. The most common case is two or three clocks. The DO[1] signal is deasserted once the output clock is generated. CLKIN can be restarted with any phase relationship to the previous clock. If the frequency has changed, the DCM requires a reset. The DO[1] is forced Low whenever LOCKED is Low. When the DCM is in the locking process, DO[1] status is held Low until LOCKED is achieved.

64

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

DCM Design Guidelines

Output Clocks
Any or all of the DCMs nine clock outputs can be used to drive a global clock network. The fully-buffered global clock distribution network minimizes clock skew caused by loading differences. By monitoring a sample of the output clock (CLK0), the deskew circuit compensates for the delay on the routing network, effectively eliminating the delay from the external input port to the individual clock loads within the device. Output pin connectivity carries some restrictions. The DCM clock outputs must drive a global clock buffer BUFGCTRL. The DCM clock outputs can not drive general routing. To use dedicated routing, the DCM clock outputs must drive BUFGCTRLs on the same top or bottom half of the device. If the DCM and BUFGCTRL are not on the same top or bottom half, local routing is used and the DCM might not deskew properly. Do not use the DCM output clock signals until after activation of the LOCKED signal. Prior to the activation of the LOCKED signal, the DCM output clocks are not valid.

DCM During Configuration and Startup

During the FPGA configuration, the DCM is in reset and starts to lock at the beginning of the startup sequence. A DCM requires both CLKIN and CLKFB input clocks to be present and stable when the DCM begins to lock. If the device enters the configuration startup sequence without an input clock, or with an unstable input clock, then the DCM must be reset after configuration with a stable clock. The following startup cycle dependencies are of note: 1. The default value is -g LCK_cycle:NoWait. When this setting is used, the startup sequence does not wait for the DCM to lock. When the LCK_cycle is set to other values, the configuration startup remains in the specified startup cycle until the DCM is locked. Before setting the LCK_cycle option to a startup cycle in BitGen, the DCMs STARTUP_WAIT attribute must be set to TRUE. If the startup sequence is altered (by using the BitGen option), do not place the LCK_cycle (wait for the DCM to lock) before the GTS_cycle (deassert GTS). Incorrect implementation results in the DCM not locking and an incomplete configuration.

2. 3.

Deskew Adjust
The DESKEW_ADJUST attribute sets the value for a configurable, variable-tap delay element to control the amount of delay added to the DCM feedback path (see Figure 2-4).

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

65

Chapter 2: Clock Management Technology

X-Ref Target - Figure 2-4

Data Input
VCCO

FF
D Q Into the FPGA

CLK Source IBUFG

DCM
CLKIN CLKFB DCM Power Regulator VCCAUX CLK0

Feedback Tap Delays System-Synchronous Default Setting Source-Synchronous Setting (Delay set to zero) VCCINT
ug190_2_04_042506

Figure 2-4:

DCM and Feedback Tap-Delay Elements

This delay element allows adjustment of the effective clock delay between the clock source and CLK0 to guarantee non-positive hold times of IOB input flip-flop in the device. Adding more delay to the DCM feedback path decreases the effective delay of the actual clock path from the FPGA clock input pin to the clock input of any flip-flop. Decreasing the clock delay increases the setup time represented in the input flip-flop, and reduces any positive hold times required. The clock path delay includes the delay through the IBUFG, route, DCM, BUFG, and clock-tree to the destination flip-flop. If the feedback delay equals the clock-path delay, the effective clock-path delay is zero.

System-Synchronous Setting (Default)

By default, the feedback delay is set to system-synchronous mode. The primary timing requirements for a system-synchronous system are non-positive hold times (or minimally positive hold times) and minimal clock-to-out and setup times. Faster clock-to-out and setup times allow shorter system clock periods. Ideally, the purpose of a DLL is to zero-out the clock delay to produce faster clock-to-out and non-positive hold times. The systemsynchronous setting (default) for DESKEW_ADJUST configures the feedback delay element to guarantee non-positive hold times for all input IOB registers. The exact delay number added to the feedback path is device size dependent. This is determined by characterization. In the timing report, this is included as timing reduction to input clock path represented by the TDCMINO parameter. As shown in Figure 2-4, the feedback path includes tap delays in the default setting (red line). The pin-to-pin timing parameters (with DCM) on the Virtex-5 FPGA Data Sheet reflects the setup/hold and clock-to-out times when the DCM is in system-synchronous mode. In some situations, the DCM does not add this extra feedback delay, and the DESKEW_ADJUST parameter has no effect. BitGen selects the appropriate DCM Tap settings. These situations include:

66

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

DCM Design Guidelines

Downstream DCMs when two or more DCMs are cascaded DCMs with external feedback DCMs with an external CLKIN that does not come from a dedicated clock input pin.

Source-Synchronous Setting
When DESKEW_ADJUST is set to source-synchronous mode, the DCM feedback delay element is set to zero. As shown in Figure 2-4, in source-synchronous mode, the DCM clock feedback delay element is set to minimize the sampling window. This results in a more positive hold time and a longer clock-to-out compared to system-synchronous mode. The source-synchronous switching characteristics section in the Virtex-5 FPGA Data Sheet reflects the various timing parameters for the source-synchronous design when the DCM is in source-synchronous mode.

Characteristics of the Deskew Circuit

Eliminate clock distribution delay by effectively adding one clock period delay. Clocks are deskewed to within CLKOUT_PHASE, specified in the Virtex-5 FPGA Data Sheet. Eliminate on-chip as well as off-chip clock delay. No restrictions on the delay in the feedback clock path. Requires a continuously running input clock. Adapts to a wide range of frequencies. However, once locked to a frequency, large input frequency variations are not tolerated. Does not eliminate jitter. The deskew circuit output jitter is the accumulation of input jitter and any added jitter value due to the deskew circuit. The completion of configuration can be delayed until after DCM locks to guarantee the system clock is established prior to initiating the device.

Frequency Synthesis
The DCM provides several flexible methods for generating new clock frequencies. Each method has a different operating frequency range and different AC characteristics. The CLK2X and CLK2X180 outputs double the clock frequency. The CLKDV output provides a divided output clock (lower frequency) with division options of 1.5, 2, 2.5, 3, 3.5, 4, 4.5, 5, 5.5, 6, 6.5, 7, 7.5, 8, 9, 10, 11, 12, 13, 14, 15, and 16. The DCM also offers fully digital, dedicated frequency-synthesizer outputs CLKFX and its opposite phase CLKFX180. The output frequency can be any function of the input clock frequency described by M D, where M is the multiplier (numerator) and D is the divisor (denominator). The frequency synthesized outputs can drive the global-clock routing networks within the device. The well-buffered global-clock distribution network minimizes clock skew due to differences in distance or loading.

Frequency Synthesis Operation

The DCM clock output CLKFX is any M D factor of the clock input to the DCM. Specifications for M and D, as well as input and output frequency ranges for the frequency synthesizer, are provided in the Virtex-5 FPGA Data Sheet.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

67

Chapter 2: Clock Management Technology

Only when feedback is provided to the CLKFB input of the DCM is the frequency synthesizer output phase aligned to the clock output, CLK0. The internal operation of the frequency synthesizer is complex and beyond the scope of this document. As long as the frequency synthesizer is within the range specified in the Virtex-5 FPGA Data Sheet, it multiplies the incoming frequencies by the pre-calculated quotient M D and generates the correct output frequencies. For example, assume an input frequency of 50 MHz, M = 25, and D = 8 (M and D values do not have common factors and cannot be reduced). The output frequency is 156.25 MHz although separate calculations, 25 x 50 MHz = 1.25 GHz and 50 MHz 8 = 6.25 MHz, seem to produce separate values outside the range of the input frequency.

Frequency Synthesizer Characteristics

The frequency synthesizer provides an output frequency equal to the input frequency multiplied by M and divided by D. The outputs CLKFX and CLKFX180 always have a 50/50 duty-cycle. Smaller M and D values achieve faster lock times. Whenever possible, divide M and D by the largest common factor to get the smallest values. (e.g., if the required CLKFX = 9/6 x CLKIN, instead of using M = 9 and D = 6, use M = 3 and D = 2.) When CLKFB is connected, CLKFX is phase aligned with CLK0 every D cycles of CLK0 and every M cycles of CLKFX if M/D is a reduced fraction.

Phase Shifting
The DCM provides coarse and fine-grained phase shifting. For coarse-phase control, the CLK0, CLK90, CLK180, and CLK270 outputs are each phase-shifted by of the input clock period relative to each other. Similarly, CLK2X180 and CLKFX180 provide a 180 coarse phase shift of CLK2X and CLKFX, respectively. The coarse phase-shifted clocks are produced from the delay lines of the DLL circuit. The phase relationship of these clocks is retained when CLKFB is not connected. Fine-grained phase shifting uses the CLKOUT_PHASE_SHIFT and PHASE_SHIFT attributes to phase-shift DCM output clocks relative to CLKIN. Since the CLKIN is used as the reference clock, the feedback (CLKFB) connection is required for the phase-shifting circuit to compare the incoming clock with the phase-shifted clock. The rest of this section describes fine-grained phase shifting in the Virtex-5 FPGA DCM.

Phase-Shifting Operation
All nine DCM output clocks are adjusted when fine-grained phase shifting is activated. The phase shift between the rising edges of CLKIN and CLKFB is a specified fraction of the input clock period or a specific amount of DCM_TAP. All other DCM output clocks retain their phase relation to CLK0.

Phase-Shift Range
The allowed phase shift between CLKIN and CLKFB is limited by the phase-shift range. There are two separate phase-shift ranges: PHASE_SHIFT attribute range FINE_SHIFT_RANGE DCM timing parameter range

68

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

DCM Design Guidelines

In the FIXED, VARIABLE_POSITIVE, and VARIABLE_CENTER phase-shift mode, the PHASE_SHIFT attribute is in the numerator of the following equation. Phase Shift (ns) = (PHASE_SHIFT/256) PERIODCLKIN Where PERIODCLKIN denotes the effective CLKIN frequency. In VARIABLE_CENTER and FIXED modes, the full range of the PHASE_SHIFT attribute is always 255 to +255. In the VARIABLE_POSITIVE mode, the range of the PHASE_SHIFT attribute is 0 to +255. In the DIRECT phase-shift mode, the PHASE_SHIFT attribute is the multiplication factor in the following equation: Phase Shift (ns) = PHASE_SHIFT DCM_TAP In DIRECT modes, the full range of the PHASE_SHIFT attribute is 0 to 1023. FINE_SHIFT_RANGE represents the total delay achievable by the phase-shift delay line. Total delay is a function of the number of delay taps used in the circuit. The absolute range is specified in the DCM Timing Parameters section of the Virtex-5 FPGA Data Sheet across process, voltage, and temperature. The different absolute ranges are outlined in this section. The fixed mode allows the DCM to insert a delay line in the CLKFB or the CLKIN path. This gives access to the +FINE_SHIFT_RANGE when the PHASE_SHIFT attribute is set to a positive value, and FINE_SHIFT_RANGE when the PHASE_SHIFT attribute is set to a negative value.

Absolute Range (Variable-Center Mode) = FINE_SHIFT_RANGE 2

The variable-center mode allows symmetric, dynamic sweeps from 255/256 to +255/256, by having the DCM set the zero-phase-skew point in the middle of the delay line. This divides the total delay-line range in half. Absolute Range (Fixed) = FINE_SHIFT_RANGE In the fixed mode, a phase shift is set during configuration in the range of 255/256 to +255/256.

Absolute Range (Variable-Positive and Direct Modes) = + FINE_SHIFT_RANGE

In the variable-positive and direct modes, the phase-shift only operates in the positive range. The DCM sets the zero-phase-skew point at the beginning of the delay line. This produces a full delay line in one direction. Both the PHASE_SHIFT attribute and the FINE_SHIFT_RANGE parameter need to be considered to determine the limiting range of each application. The Phase-Shift Examples section illustrates possible scenarios. In variable and direct mode, the PHASE_SHIFT value can dynamically increment or decrement as determined by PSINCDEC synchronously to PSCLK, when the PSEN input is active.

Phase-Shift Examples
The following usage examples take both the PHASE_SHIFT attribute and FINE_SHIFT_RANGE into consideration: If PERIODCLKIN = 2 FINE_SHIFT_RANGE, then the PHASE_SHIFT in fixed mode is limited to 128. In variable-positive mode, PHASE_SHIFT is limited to +128. In variable-center mode the PHASE_SHIFT is limited to 64.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

69

Chapter 2: Clock Management Technology

If PERIODCLKIN = FINE_SHIFT_RANGE, then the PHASE_SHIFT in variablepositive mode is limited to +255. In fixed and variable-center mode the PHASE_SHIFT is limited to 255. If PERIODCLKIN FINE_SHIFT_RANGE, then the PHASE_SHIFT in variablepositive mode is limited to +255. In fixed and variable-center mode the PHASE_SHIFT is limited to 255. For all previously described cases, the direct mode is always limited to +1023.

If the phase shift is limited by the FINE_SHIFT_RANGE, use the coarse-grained phase shift to extend the phase-shift range or set DCM_PERFORMANCE_MODE attribute to MAX_RANGE to increase the FINE_SHIFT_RANGE. Figure 2-5 illustrates using CLK90, CLK180, and CLK270 outputs assuming FINE_SHIFT_RANGE = 10 ns.
X-Ref Target - Figure 2-5

10 ns For frequency 100 MHz (period 10 ns) CLK0 PHASE_SHIFT = 0 - 255 covers the whole range of period. For frequency between 50 - 100 MHz (period 10 - 20 ns). At 50 MHz, use CLK0 PHASE_SHIFT= 0 - 127 for the first 10 ns. CLK0(50 MHz) Use CLK180 with PHASE_SHIFT= 0 - 127 for the next 10 ns. For frequency between 25 - 50 MHz (period 20 - 40 ns). At 25 MHz, use CLK0 PHASE_SHIFT= 0 - 63 for the first 10 ns. Use CLK90 with PHASE_SHIFT= 0 - 63 for the next 10 ns. Use CLK180 with PHASE_SHIFT= 0 - 63 for the next 10 ns. Use CLK270 with PHASE_SHIFT= 0 - 63 for the last 10 ns. CLK180(50 MHz)

10 ns

10 ns

10 ns

CLK0(100 MHz)

CLK0(25 MHz) CLK90(25 MHz) CLK180(25 MHz) CLK270(25 MHz)

ug0190_2_05_032506

Figure 2-5:

Fixed Phase-Shift Examples

In variable mode, the phase-shift factor is changed by activating PSEN for one period of PSCLK. At the PSCLK clock cycle where PSEN is activated, the level of PSINCDEC input determines whether the phase-shift increases or decreases. A High on PSINCDEC increases the phase shift, and a Low decreases the phase shift. After the deskew circuit increments or decrements, the signal PSDONE is asserted High for a single PSCLK cycle. This allows the next change to be performed. The user interface and the physical implementation are different. The user interface describes the phase shift as a fraction of the clock period (N/256). The physical implementation adds the appropriate number of buffer stages (each DCM_TAP) to the clock delay. The DCM_TAP granularity limits the phase resolution at higher clock frequencies. All phase-shift modes, with the exception of DIRECT mode, are temperature and voltage adjusted. Hence, a VCC or temperature adjustment does not change the phase shift. The DIRECT phase shift is not temperature or voltage adjusted since it directly controls

70

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

DCM Design Guidelines

DCM_TAP. Changing the ratio of VCC/temperature results in a phase-shift change proportional to the size of the DCM_TAP at the specific voltage and temperature.

Interaction of PSEN, PSINCDEC, PSCLK, and PSDONE

The variable and direct phase-shift modes are controlled by the PSEN, PSINCDEC, PSCLK, and PSDONE ports. In addition, a phase-shift overflow (DO[0]) status indicates when the phase-shift counter has reached the end of the phase-shift delay line or the maximum value (255 for variable mode, +1023 for direct mode). After the DCM locks, the initial phase in the VARIABLE_POSITIVE and VARIABLE_CENTER modes is determined by the PHASE_SHIFT value. The initial phase in the DIRECT mode is always 0, regardless of the value specified by the PHASE_SHIFT attribute. The phase of the DCM output clock is incremented/decremented according to the interaction of PSEN, PSINCDEC, PSCLK, and PSDONE from the initial or dynamically reconfigured phase. 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 DCM clock outputs by 1/256 of the CLKIN period. Similarly, each decrement decreases the phase shift by 1/256 of the CLKIN period. PSEN must be active for exactly one PSCLK period; otherwise, a single phase-shift increment/decrement is not guaranteed. PSDONE is High for exactly one clock period when the phase shift is complete. The time required to complete a phase-shift operation varies. As a result, PSDONE must be monitored for phase-shift status. Between enabling PSEN and PSDONE is flagged, the DCM output clocks gradually change from their original phase shift to the incremented/decremented 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. Figure 2-6 illustrates the interaction of phase-shift ports.
X-Ref Target - Figure 2-6

PSCLK

PSEN

PSDONE

PSINCDEC
ug190_2_06_032506

Figure 2-6:

Phase-Shift Timing Diagram

When PSEN is activated after the phase-shift counter has reached the maximum value of PHASE_SHIFT, the PSDONE is still pulsed High for one PSCLK period some time after the PSEN is activated (as illustrated in Figure 2-6). However, the phase-shift overflow pin, STATUS(0), or DO(0) is High to flag this condition, and no phase adjustment is performed.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

71

Chapter 2: Clock Management Technology

Phase-Shift Overflow
The phase-shift overflow (DO[0]) status signal is asserted when either of the following conditions is true: The DCM is phase-shifted beyond the allowed phase-shift value. In this case, the phase-shift overflow signal is asserted High when the phase shift is decremented beyond 255 and incremented beyond +255 for VARIABLE_CENTER mode, incremented beyond +255 for VARIABLE_POSITIVE mode, or decremented beyond 0 and incremented beyond 1023 for DIRECT mode. The DCM is phase-shifted beyond the absolute range of the phase-shift delay line. In this case, the phase-shift overflow signal is asserted High when the phase-shift in time (ns) exceeds the FINE_SHIFT_RANGE/2 in the VARIABLE_CENTER mode, the +FINE_SHIFT_RANGE in the VARIABLE_POSITIVE mode, or exceeds 0 to +FINE_SHIFT_RANGE in the DIRECT mode. The phase-shift overflow signal can toggle once it is asserted. The condition determining if the delay line is exceeded is calibrated dynamically. Therefore, at the boundary of exceeding the delay line, it is possible for the phase-shift overflow signal to assert and deassert without a change in phase shift. Once asserted, it remains asserted for at least 40 CLKIN cycles. If the DCM is operating near the FINE_SHIFT_RANGE limit, do not use the phase-shift overflow signal as a flag to reverse the phase shift direction. When the phase-shift overflow is asserted, deasserted, then asserted again in a short phase shift range, it can falsely reverse the phase shift direction. Instead, use a simple counter to track the phase shift value and reverse the phase shift direction (PSINCDEC) only when the counter reaches a previously determined maximum/minimum phase shift value. For example, if the phase shift must be within 0 to 128, set the counter to toggle PSINCDEC when it reaches 0 or 128.

Phase-Shift Characteristics
Offers fine-phase adjustment with a resolution of 1/256 of the clock period (or one DCM_TAP, whichever is greater). It can be dynamically changed under user control. The phase-shift settings affect all nine DCM outputs. VCC and temperature do not affect the phase shift except in direct phase-shift mode. In either fixed or variable mode, the phase-shift range can be extended by choosing CLK90, CLK180, or CLK270, rather than CLK0, choosing CLK2X180 rather than CLK2X, or choosing CLKFX180 rather than CLKFX. Even at 25 MHz (40 ns period), the fixed mode coupled with the various CLK phases allows shifting throughout the entire input clock period range. MAX_RANGE mode extends the phase-shift range. The phase-shifting (DPS) function in the DCM requires the CLKFB for delay adjustment. Because CLKFB must be from CLK0, the DLL output is used. The minimum CLKIN frequency for the DPS function is determined by DLL frequency mode.

72

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Connecting DCMs to Other Clock Resources in Virtex-5 Devices

Dynamic Reconfiguration
The Dynamic Reconfiguration Ports (DRPs) can update the initial DCM settings without reloading a new bit stream to the FPGA. The DRP address mapping changed in Virtex-5 FPGAs. The Virtex-5 FPGA Configuration Guide provides more information on using DRPs. Specific to the DCM, DRPs allow dynamic adjustment of the CLKFX_MULTIPLY(M) and CLKFX_DIVIDE(D) values to produce a new CLKFX frequency. The following steps are required when using DRPs to load new M and D values: Subtract the desired M and D values by one. For example, if the desired M/D = 9/4, then load M/D = 8/3. Hold DCM in reset (assert RST signal) and release it after the new M and D values are written. The CLKFX outputs can be used after LOCKED is asserted High again. Read DADDR0 to restore the default status on D0. Release RST.

Connecting DCMs to Other Clock Resources in Virtex-5 Devices

Most DCM functions require connection to dedicated clock resources, including dedicated clock I/O (IBUFG), clock buffers (BUFGCTRLs), and PLLs. These clock resources are located in the center column of the Virtex-5 devices. This section provides guidelines on connecting the DCM to dedicated clock resources.

IBUFG to DCM
Virtex-5 devices contain 20 clock inputs. These clock inputs are accessible by instantiating the IBUFG. Each top and bottom half of a Virtex-5 device contains 10 IBUFGs. Any of the IBUFG in top or bottom half of the Virtex-5 device can drive the clock input pins (CLKIN, CLKFB, PSCLK, or DCLK) of a DCM located in the same top/bottom half of the device.

DCM to BUFGCTRL
Any DCM clock output can drive any BUFGCTRL input in the same top/bottom half of the device. There are no restrictions on how many DCM outputs can be used simultaneously.

BUFGCTRL to DCM
Any BUFGCTRL can drive any DCM in the Virtex-5 devices. However, only up to ten dedicated clock routing resources exist in a particular clock region. Since the clock routing is accessed via the BUFGCTRL outputs, this indirectly limits the BUFGCTRL to DCM connection. If ten BUFGCTRL outputs are already accessing a clock region, and a DCM is in that region, then no additional BUFGCTRL can be used in that region, including a connection to the CLKFB pin of the DCM.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

73

Chapter 2: Clock Management Technology

PLL To and From DCM

Figure 2-7 summarizes the dedicated connection between the DCM and the PLL in the same CMT block. The PLL can drive either DCM in the same CMT block using a dedicated connection. Similarly, the DCM can drive the PLL within the same CMT block with a dedicated connection. There is no BUFGCTRL required between the PLL and the DCM.
X-Ref Target - Figure 2-7

From any IBUFG implementation From any BUFG implementation

CLKIN DCM1 CLKFB PLL to DCM Input DCM to PLL Input CLKIN PLL CLKFBIN DCM to PLL Input PLL to DCM Input CLKIN DCM2 CLKFB
ug190_2_07_072307

To Global Routing (BUFG)

To Global Routing (BUFG)

To Global Routing (BUFG)

Figure 2-7:

DCM and PLL Connection in Same CMT Block

DCM To and From PMCD

The PMCD block is not available in the Virtex-5 devices. However, a limited retargeting using the PLL is possible. Refer to PLL in Virtex-4 FPGA PMCD Legacy Mode in Chapter 3 for more information.

74

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Application Examples

Application Examples
The Virtex-5 FPGA DCM can be used in a variety of creative and useful applications. The following examples show some of the more common applications.

Standard Usage
The circuit in Figure 2-8 shows DCM_BASE implemented with internal feedback and access to RST and LOCKED pins. This example shows the simplest use case for a DCM.
X-Ref Target - Figure 2-8

IBUFG CLKIN

DCM_BASE
CLK0 CLK90 CLK180 CLK270 CLK2X CLK2X180 CLKDV CLKFX CLKFX180 LOCKED

BUFG

CLKFB IBUF RST

OBUF

ug190_2_08_032506

Figure 2-8:

Standard Usage

Board-Level Clock Generation

The board-level clock generation example in Figure 2-9 illustrates how to use a DCM to generate output clocks for other components on the board. This clock can then be used to interface with other devices. In this example, a DDR register is used with its inputs connected to GND and VCC. Because the output of the DCM is routed to BUFG, the clock stays within global routing until it reaches the output register. The quality of the clock is maintained. The board-level clock generation example in Figure 2-10, with internal feedback, illustrates the clock generation for a forwarded clock on the board.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

75

Chapter 2: Clock Management Technology

X-Ref Target - Figure 2-9

Outside FPGA Inside FPGA

VCC

ODDR
IBUFG CLKIN IBUFG CLKFB

DCM_ADV
CLK0 CLK90 CLK180 CLK270 CLK2X CLK2X180 CLKDV CLKFX CLKFX180

BUFG D1 D2 GND C Q

RST PSINCDEC PSEN PSCLK DADDR[6:0] DI[15:0] DWE DEN DCLK

LOCKED DO(15:0)

UG190_2_09_042308

Figure 2-9: Board-Level Clock Using DDR Register with External Feedback
X-Ref Target - Figure 2-10

VCC

ODDR
IBUFG CLKIN CLKFB

DCM_ADV
CLK0 CLK90 CLK180 CLK270 CLK2X CLK2X180 CLKDV CLKFX CLKFX180

BUFG D1 D2 GND C Q

RST PSINCDEC PSEN PSCLK DADDR[6:0] DI[15:0] DWE DEN DCLK

LOCKED DO(15:0)

ug190_2_11_032506

Figure 2-10:

Board-Level Clock with Internal Feedback

76

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Application Examples

Board Deskew with Internal Deskew

Some applications require board deskew with internal deskew to interface with other devices. These applications can be implemented using two or more DCM. The circuit shown in Figure 2-11 can be used to deskew a system clock between multiple Virtex devices in the same system.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

77

Chapter 2: Clock Management Technology

X-Ref Target - Figure 2-11

Virtex-5 FPGA

IBUFG CLKIN IBUFG CLKFB RST

VCC
BUFG GND

ODDR D1 D2 C Q

DCM_ADV
CLK0 CLK90 CLK180 CLK270 CLK2X CLK2X180 CLKDV CLKFX CLKFX180

PSINCDEC PSEN PSCLK DADDR[6:0] DI[15:0] DWE DEN DCLK

INV LOCKED DO[15:0] BUFG

OBUF

to RST

DCM_ADV
CLKIN CLKFB RST PSINCDEC PSEN PSCLK DADDR[6:0] DI[15:0] DWE DEN DCLK CLK0 CLK90 CLK180 CLK270 CLK2X CLK2X180 CLKDV CLKFX CLKFX180

LOCKED DO[15:0]

Virtex-5 FPGA

IBUFG CLKIN CLKFB RST

BUFG

DCM_ADV
CLK0 CLK90 CLK180 CLK270 CLK2X CLK2X180 CLKDV CLKFX CLKFX180

PSINCDEC PSEN PSCLK DADDR[6:0] DI[15:0] DWE DEN DCLK

LOCKED DO(15:0)

This circuit can be duplicated to multiple Virtex devices. Use CLKDLL for Virtex and Virtex-E devices, DCM for Virtex-II and Virtex-II Pro devices.
ug190_2_12_032506

Figure 2-11: Board Deskew with Internal Deskew Interfacing to Other Virtex Devices

78

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Application Examples

The example in Figure 2-12 shows an interface from Virtex-5 FPGAs to components other than Virtex FPGAs.
X-Ref Target - Figure 2-12

Virtex-5 FPGA

VCC
BUFG GND

ODDR D1 D2 C Q

IBUFG CLKIN IBUFG CLKFB

DCM_ADV
CLK0 CLK90 CLK180 CLK270 CLK2X CLK2X180 CLKDV CLKFX CLKFX180

RST PSINCDEC PSEN PSCLK DADDR[6:0] DI[15:0] DWE DEN DCLK

LOCKED DO[15:0]

BUFG

DCM_ADV
CLKIN CLKFB RST PSINCDEC PSEN PSCLK DADDR[6:0] DI[15:0] DWE DEN DCLK CLK0 CLK90 CLK180 CLK270 CLK2X CLK2X180 CLKDV CLKFX CLKFX180

LOCKED DO[15:0]

...non-Virtex chips

ug190_2_13_032506

Figure 2-12:

Board Deskew with Internal Deskew Interfacing to Other Components

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

79

Chapter 2: Clock Management Technology

Clock Switching Between Two DCMs

Figure 2-13 illustrates switching between two clocks from two DCMs while keeping both DCMs locked.
X-Ref Target - Figure 2-13

IBUFG CLKIN CLKFB RST

DCM_ADV
CLK0 CLK90 CLK180 CLK270 CLK2X CLK2X180 CLKDV CLKFX CLKFX180

BUFG

CLKA

PSINCDEC PSEN PSCLK DADDR[6:0] DI[15:0] DWE DEN DCLK

BUFGMUX

I0 LOCKED DO(15:0)

I0 S

IBUFG CLKIN

DCM_ADV
CLK0 CLK90 CLK180 CLK270 CLK2X CLK2X180 CLKDV CLKFX CLKFX180

BUFG

CLKB

CLKFB RST PSINCDEC PSEN PSCLK DADDR[6:0] DI[15:0] DWE DEN DCLK

LOCKED DO(15:0)

ug190_2_14_032506

Figure 2-13:

Clock Switching Between Two DCMs

80

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Application Examples

DCM with PLL

The PLL can be used to drive the DCM to reduce the source clocks incoming jitter before inputting DCM. This setup reduces the source clock jitter while enabling user access to all available DCM clock outputs. Figure 2-14 illustrates the PLL driving a DCM within the same CMT block using the dedicated routing resource (without BUFG).
X-Ref Target - Figure 2-14

IBUFG CLKIN1 CLKFBIN RST

PLL
CLKOUT0 CLKOUT1 CLKOUT2 CLKOUT3 CLKOUT4 CLKOUT5 CLKFBOUT

BUFG

DCM
CLKIN CLKFBIN RST CLK0 CLK90 CLK180 CLK270 CLK2X CLK2X180 CLKDV CLKFX CLKFX180

BUFG

ug190_2_15_040906

Figure 2-14:

PLL Driving DCM

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

81

Chapter 2: Clock Management Technology

It is also possible to use the DCM to drive a PLL. This setup reduces the overall jitter of both the source clock and the DCM clock output. In this case, only up to two of the DCM output clocks can drive the PLL. Therefore, only up to two DCM clocks can access the PLL and benefit from the reduced jitter. Figure 2-15 and Figure 2-16 illustrate two scenarios of the DCM driving a PLL. Figure 2-15 illustrates the direct connection between DCM and PLL within a CMT. Only one DCM output can drive PLL using the direct connection within a CMT without routing through a global buffer (BUFG). The DCM and PLL can be within the same or different CMTs. Figure 2-16 illustrates two DCMs driving a PLL. In this case, BUFG must also be inserted between the DCM clocks driving the PLL input clocks. The DCM and PLL can be within the same or different CMTs. Refer to Chapter 3, Phase-Locked Loops (PLLs) for more information on PLLs.
X-Ref Target - Figure 2-15

IBUFG

BUFG

DCM
CLKIN CLKFBIN RST CLK0 CLK90 CLK180 CLK270 CLK2X CLK2X180 CLKDV CLKFX CLKFX180

PLL
CLKIN1 CLKFBIN RST CLKOUT0 CLKOUT1 CLKOUT2 CLKOUT3 CLKOUT4 CLKOUT5 CLKFBOUT

BUFG

ug190_2_16_040906

Figure 2-15:

Direct Connection between DCM and PLL

82

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

VHDL and Verilog Templates, and the Clocking Wizard

X-Ref Target - Figure 2-16

IBUFG

BUFG

DCM1
CLKIN CLKFBIN RST CLK0 CLK90 CLK180 CLK270 CLK2X CLK2X180 CLKDV CLKFX CLKFX180

BUFG

PLL
CLKIN1 CLKIN2 CLKFBIN RST CLKOUT0 CLKOUT1 CLKOUT2 CLKOUT3 CLKOUT4 CLKOUT5 CLKFBOUT

BUFG

IBUFG

BUFG

DCM
CLKIN CLKFBIN CLK0 CLK90 CLK180 CLK270 CLK2X CLK2X180 CLKDV CLKFX CLKFX180

BUFG

ug190_2_18_040906

Figure 2-16:

Two DCMs Driving a PLL

VHDL and Verilog Templates, and the Clocking Wizard

VHDL and Verilog instantiation templates are available in the Libraries Guide for all primitives. In addition, VHDL and Verilog files are generated by the Clocking Wizard in the ISE software. The Clocking Wizard sets appropriate DCM attributes, input/output clocks, and buffers for general use cases.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

83

Chapter 2: Clock Management Technology

DCM Timing Models

The following timing diagrams describe the behavior of the DCM clock outputs under four different conditions: 1. 2. 3. 4. Reset/Lock Fixed-Phase Shifting Variable-Phase Shifting Status Flags

Reset/Lock
In Figure 2-17, the DCM is already locked. After the reset signal is applied, all output clocks are stabilized to the desired values, and the LOCKED signal is asserted.
X-Ref Target - Figure 2-17

CLKIN RST CLK0 CLK90 CLK180 CLKFX CLKFX180 CLKDV LOCKED

Figure 2-17: Prior to Clock Event 1 Prior to clock event 1, the DCM is locked. All clock outputs are in phase with the correct frequency and behavior. Clock Event 1 Some time after clock event 1 the reset signal is asserted at the (RST) pin. While reset is asserted, all clock outputs become a logic zero. The reset signal is an asynchronous reset. Note: the diagram is not shown to scale. For the DCM to operate properly, the reset signal must be asserted for at least three CLKIN periods. Clock Event 2 Clock event 2 occurs a few cycles after reset is asserted and deasserted. At clock event 2, the lock process begins. At time LOCK_DLL, after clock event 2, if no fixed phase shift was selected then all clock outputs are stable and in phase. LOCKED is also asserted to signal completion.
LOCK DLL 3 Periods

ug190_2_18_042406

RESET/LOCK Example

84

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

DCM Timing Models

Fixed-Phase Shifting
In Figure 2-18, the DCM outputs the correct frequency. However, the clock outputs are not in phase with the desired clock phase. The clock outputs are phase-shifted to appear sometime later than the input clock, and the LOCKED signal is asserted.
X-Ref Target - Figure 2-18

CLKIN CLK0 CLK90 CLK180 CLK2X LOCKED

Lock Time
ug190_2_19_042406

Figure 2-18: Clock Event 1

Phase Shift Example: Fixed

Clock event 1 appears after the desired phase shifts are applied to the DCM. In this example, the shifts are positive shifts. CLK0 and CLK2X are no longer aligned to CLKIN. However, CLK0, and CLK2X are aligned to each other, while CLK90 and CLK180 remain as 90 and 180 versions of CLK0. The LOCK signal is also asserted once the clock outputs are ready.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

85

Chapter 2: Clock Management Technology

Variable-Phase Shifting
In Figure 2-19, the CLK0 output is phase-shifted using the dynamic phase-shift adjustments in the synchronous user interface. The PSDONE signal is asserted for one cycle when the DCM completes one phase adjustment. After PSDONE is deasserted, PSEN can be asserted again, allowing an additional phase shift to occur. As shown in Figure 2-19, all the variable-phase shift control and status signals are synchronous to the rising edge of PSCLK.
X-Ref Target - Figure 2-19

CLKIN CLK0
1 2

PSCLK PSEN
TDMCCK_PSEN

PSDONE
TDMCCK_PSINCDEC

TDMCKO_PSDONE

PSINCDEC

D.C.

D.C.
ug190_2_20_0042406

Figure 2-19: Clock Event 1

Phase Shift Example: Variable

At TDMCCK_PSEN, before clock event 1, PSEN is asserted. PSEN must be active for exactly one clock period; otherwise, a single increment/decrement of phase shift is not guaranteed. Also, the PSINCDEC value at TDMCCK_PSINCDEC, before clock event 1, determines whether it is an increment (logic High) or a decrement (logic Low). Clock Event 2 At TDMCKO_PSDONE, after clock event 2, PSDONE is asserted to indicate one increment or decrement of the DCM outputs. PSDONE is High for exactly one clock period when the phase shift is complete. The time required for a complete phase shift varies. As a result, PSDONE must be monitored for phase-shift status.

86

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

DCM Timing Models

Status Flags
The example in Figure 2-20 shows the behavior of the status flags in the event of a phaseshift overflow and CLKIN/CLKFB/CLKFX failure.
X-Ref Target - Figure 2-20

CLKIN
3

CLKFB
2

CLKFX DO(0) DO(1)

257 - 260 Cycles

DO(2)
1

PSCLK PSEN PSDONE DO(3)

ug190_2_21_042406

Figure 2-20: Status Flags Example Clock Event 1 Prior to the beginning of this timing diagram, CLK0 (not shown) is already phaseshifted at its maximum value. At clock event 1, PSDONE is asserted. However, since the DCM has reached its maximum phase-shift capability no phase adjustment is performed. Instead, the phase-shift overflow status pin DO(0) is asserted to indicate this condition. Clock Event 2 The CLKFX output stops toggling. Within 257 to 260 clock cycles after this event, the CLKFX stopped status DO(2) is asserted to indicate that the CLKFX output stops toggling. Clock Event 3 The CLKFB input stops toggling. Within 257 to 260 clock cycles after this event, the CLKFB stopped status DO(3) is asserted to indicate that the CLKFB output stops toggling. Clock Event 4 The CLKIN input stops toggling. Within 9 clock cycles after this event, DO(1) is asserted to indicate that the CLKIN output stops toggling.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

87

Chapter 2: Clock Management Technology

Legacy Support
The Virtex-5 FPGA DCMs (DCM_BASE and DCM_ADV) have exactly the same port names as the Virtex-4 FPGA DCMs. However, the DRP address mapping has changed. Refer to the Virtex-5 FPGA Configuration Guide for more information. The Virtex-5 device supports the Virtex-II family and Virtex-II Pro FPGA DCM primitives. The mapping of Virtex-II or Virtex-II Pro FPGA DCMs to Virtex-5 FPGA DCM_ADVs are as follows: CLKIN, CLKFB, PSCLK, PSINDEC, PSEN, RST, CLK0, CLK90, CLK180, CLK270, CLK2X, CLK2X180, CLKFX, CLKFX180, CLKDV, PSDONE, LOCKED of Virtex-5 FPGA primitives (DCM_BASE/DCM_ADV) map to the same corresponding pins of a Virtex-II or Virtex-II Pro FPGA DCM. Dynamic reconfiguration pins of Virtex-5 FPGA DCM_ADV are not accessible when a Virtex-II or Virtex-II Pro FPGA DCM is used, except for DO[15:0]. DO[7:0] pins of Virtex-5 FPGA DCM_ADV map to Status[7:0] of the Virtex-II or Virtex-II Pro FPGA DCMs. DO[15:8] of DCM_ADV are not available when using Virtex-II or Virtex-II Pro FPGA DCMs.

88

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Chapter 3

Phase-Locked Loops (PLLs)

Introduction
The clock management tile (CMT) in Virtex-5 FPGAs includes two DCMs and one PLL. There are dedicated routes within a CMT to couple together various components. Each block within the tile can be treated separately, however, there exists a dedicated routing between blocks creating restrictions on certain connections. Using these dedicated routes frees up global resources for other design elements. Additionally, the use of local routes within the CMT provides an improved clock path because the route is handled locally, reducing chances for noise coupling. The CMT diagram (Figure 3-1) shows a high-level view of the connection between the various clock input sources and the DCM-to-PLL and PLL-to-DCM dedicated routing. The six (total) PLL output clocks are muxed into a single clock signal for use as a reference clock to the DCMs. Two output clocks from the PLL can drive the DCMs. These two clocks are 100% independent. PLL output clock 0 could drive DCM1 while PLL output clock 1 could drive DCM2. Each DCM output can be muxed into a single clock signal for use as a reference clock to the PLL. Only one DCM can be used as the reference clock to the PLL at any given time. A DCM can not be inserted in the feedback path of the PLL. Both the PLLs or DCMs of a CMT can be used separately as stand-alone functions. The outputs from the PLL are not spread spectrum.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

89

Chapter 3: Phase-Locked Loops (PLLs)

X-Ref Target - Figure 3-1

From any IBUFG implementation From any BUFG implementation DCM1 To any BUFG implementation

PLL

clkout_pll<5:0>

To any BUFG implementation

DCM2

To any BUFG implementation

UG190_c3_01_022709

Figure 3-1:

Block Diagram of the Virtex-5 FPGA CMT

Phase Locked Loop (PLL)

Virtex-5 devices contain up to six CMT tiles. The PLLs main purpose is to serve as a frequency synthesizer for a wide range of frequencies, and to serve as a jitter filter for either external or internal clocks in conjunction with the DCMs of the CMT. The PLL block diagram shown in Figure 3-2 provides a general overview of the PLL components.
X-Ref Target - Figure 3-2

D Clock Pin

PFD

CP

LF

VCO

O0 O1 O2

M O3 O4 O5
ug190_3_02_030506

Figure 3-2:

Block Diagram of the Virtex-5 FPGA PLL

90

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Introduction

Input muxes select the reference and feedback clocks from either the IBUFG, BUFG, IBUF, PLL outputs, or one of the DCMs. Each clock input has a programmable counter D. The Phase-Frequency Detector (PFD) compares both phase and frequency of the input (reference) clock and the feedback clock. Only the rising edges are considered because as long as a minimum High/Low pulse is maintained, the duty cycle is not important. 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 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. Each output phase can be selected as the reference clock to the output counters (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 PLL allowing a wide range of frequency synthesis.
X-Ref Target - Figure 3-3

General Routing Clock Switch Circuit CLKIN1 CLKIN2 Lock Detect Lock Monitor Lock

8-phase taps

PFD

CP

LF

VCO

O0 O1 O2 O3

CLKFBOUT

CLKFB VCO feedback phase selection for negative phase-shift affecting all outputs

O4 O5
UG190_c3_03_022709

Figure 3-3:

Detailed PLL Block Diagram

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

91

Chapter 3: Phase-Locked Loops (PLLs)

General Usage Description

PLL Primitives
Figure 3-4 shows the two Virtex-5 FPGA PLL primitives, PLL_BASE and PLL_ADV.
X-Ref Target - Figure 3-4

CLKIN1

CLKOUT0 CLKOUT1

CLKIN1 CLKIN2 CLKFBIN RST CLKINSEL DADDR[4:0] DI[15:0] DWE DEN DCLK REL

CLKOUT0 CLKOUT1 CLKOUT2 CLKOUT3 CLKOUT4 CLKOUT5 CLKFBOUT CLKOUTDCM0 CLKOUTDCM1 CLKOUTDCM2 CLKOUTDCM3 CLKOUTDCM4 CLKOUTDCM5 CLKFBDCM

CLKFBIN RST

CLKOUT2 CLKOUT3 CLKOUT4 CLKOUT5 CLKFBOUT

LOCKED

LOCKED DO[15:0] DRDY

PLL_BASE

PLL_ADV
UG190_c3_04_022709

Figure 3-4:

PLL Primitives

PLL_BASE Primitive
The PLL_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 PLL_BASE. The ports are listed in Table 3-1. Table 3-1: PLL_BASE Ports
Port CLKIN, CLKFBIN RST CLKOUT0 to CLKOUT5, CLKFBOUT LOCKED

Description Clock Input Control Inputs Clock Output Status and Data Outputs

92

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

General Usage Description

PLL_ADV Primitive
The PLL_ADV primitive provides access to all PLL_BASE features plus additional ports for clock switching, connectivity to DCMs in the same CMT, and access to the Dynamic Reconfiguration Port (DRP). The ports are listed in Table 3-2. Detailed DRP information can be found in the Virtex-5 FPGA Configuration Guide. Table 3-2: PLL_ADV Ports
Port CLKIN1, CLKIN2, CLKFBIN, DCLK RST, CLKINSEL, DWE, DEN, DADDR, DI, REL(1) CLKOUT0 to CLKOUT5, CLKFBOUT, CLKOUTDCM0 to CLKOUTDCM5, CLKFBDCM LOCKED, DO, DRDY

Description Clock Input Control and Data Input Clock Output Status and Data Output
Notes:

1. REL is used in PMCD mode only. In PLL mode, leave REL unconnected or tied Low.

The Virtex-5 FPGA PLL is a mixed signal block 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 Equation 3-1 F VCO = F CLKIN ---D M Equation 3-2 F OUT = F CLKIN -------DO where the M, D, and O counters are shown in Figure 3-3. The six 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 PLL or DLL to compensate for the clock network delay. Virtex-5 FPGA PLLs support this feature. A clock output matching the reference clock CLKIN frequency (usually CLKFBOUT) is connected to a BUFG and fed back to the CLKFBIN feedback pin of the 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.

Frequency Synthesis Only

The PLLs can also be used for stand alone frequency synthesis. In this application, the PLL can not be used to deskew a clock network, but rather generate an output clock frequency for other blocks. In this mode, the PLL feedback path should be set to INTERNAL since it keeps all the routing local and should minimize the jitter. Figure 3-5 shows the PLL 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 PLL. Setting the M counter to 16 makes the VCO oscillate at 533 MHz (33.333 MHz x 16). The six

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

93

Chapter 3: Phase-Locked Loops (PLLs)

PLL outputs are programmed to provide a 533 MHz PowerPC processor clock, a 266 MHz PowerPC processor gasket clock, a 178 MHz clock, a 133 MHz memory interface clock, a 66 MHz PCI clock, and a 33 MHz PCI clock. 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.
X-Ref Target - Figure 3-5

33 MHz Reference Clock

D=1

PFD, CP, LF, VCO M = 16

D0 = 1 D0 = 2 D0 = 3 D0 = 4 D0 = 8 D = 16

PowerPC Processor Core PowerPC Processor Gasket CLB/Fabric Memory Interface PCI-66 PCI-33
UG190_3_05_111808

Figure 3-5: PLL as a Frequency Synthesizer

Jitter Filter
PLLs always reduce the jitter inherent on a reference clock. The PLL can be instantiated as a standalone function to simply support filtering jitter from an external clock before it is driven into the another block (including the DCM). As a jitter filter, it is usually assumed that the PLL acts as a buffer and regenerates the input frequency on the output (e.g., FIN = 100 MHz, FOUT = 100 MHz). In general, greater jitter filtering is possible by using the PLL attribute BANDWIDTH set to Low. Setting the BANDWIDTH to Low can incur an increase in the static offset of the PLL.

Limitations
The PLL has some restrictions that must be adhered to. These are summarized in the PLL electrical specification in the Virtex-5 FPGA Data Sheet. In general, the major limitations are VCO operation range, input frequency, duty cycle programmability, and phase shift.

VCO Operating Range

The minimum and maximum VCO operating frequencies are defined in the electrical specification of the Virtex-5 FPGA Data Sheet. These values can also be extracted from the speed specification.

Minimum and Maximum Input Frequency

The minimum and maximum CLKIN input frequency are defined in the electrical specification of the Virtex-5 FPGA Data Sheet.

Duty Cycle Programmability

Only discrete duty cycles are possible given a VCO operating frequency. The counter settings to determine the output duty cycle is further discussed under Counter Control.

94

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

General Usage Description

Phase Shift
In many cases, there needs to be a phase shift between clocks. The phase shift resolution in time units is defined as: PS = 1/8 FVCO or D/8MFIN since the VCO can provide eight phase shifted clocks at 45 each. The higher the VCO frequency, 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/8 FVCO_MIN to 1/8 FVCO_MAX. Each output counter is individually programmable allowing each counter to have a different phase shift based on the output frequency of the VCO. Note: Phase shifts other than 45 are possible. A finer phase shift resolution depends on the output duty cycle and 0 value. Consult the architecture wizard for other phase-shift settings.

PLL Programming
Programming of the PLL must follow a set flow to ensure configuration that guarantees stability and performance. This section describes how to program the PLL based on certain design requirements. A design can be implement in two ways, directly through the GUI interface (the PLL Wizard) or directly implementing the PLL through instantiation. Regardless of the method selected, the following information is necessary to program the PLL: Reference clock period Output clock frequencies (up to six maximum) Output clock duty cycle (default is 50%) Output clock phase shift relative in number of clock cycles relative to the fastest output clock. Desired bandwidth of the PLL (default is OPTIMIZED and the bandwidth is chosen in software) Compensation mode (automatically determined by the software) Reference clock jitter in UI (i.e., 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 since it has no restrictions. There can be a very large number of frequencies. In the worst case, there will be 52 x 64 x 128 = 425,984 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. As an example, consider FIN = 100 MHz. If the minimum PFD frequency is 20 MHz, then D can only go from 1 to 5. For D = 1, M can only have values from four to 11. If D = 2, M can have values from 8 to 22. In addition, D = 1 M = 4 is a subset of D = 2 M = 8 allowing the D = 1 M = 4 case to be dropped. For this case, only D = 3, 4, 5, and 7 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

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

95

Chapter 3: Phase-Locked Loops (PLLs)

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 Equation 3-3 D MIN = roundup -----------------------f PFD MAX f IN D MAX = rounddown ----------------------f PFD MIN f VCOMIN M MIN = roundup ----------------------- D MIN f IN D MAX f VCOMAX M MAX = rounddown ------------------------------------------------f IN Equation 3-4

Equation 3-5

Equation 3-6

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 = ----------------------------------------------f IN

Equation 3-7

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.

PLL Ports
Table 3-3 summarizes the PLL ports. Table 3-4 lists the PLL attributes. Table 3-3: PLL Ports
I/O Input Input Input Input General clock input. Secondary clock input to dynamically switch the PLL reference clock. Feedback clock input. Signal controls the state of the input mux, High = CLKIN1, Low = CLKIN2 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 (i.e., PLL reenabled). A reset is required when the input clock conditions change (e.g., frequency). The dynamic reconfiguration address (DADDR) input bus provides a reconfiguration address for the dynamic reconfiguration. When not used, all bits must be assigned zeros. Pin Description

Pin Name CLKIN1 CLKIN2 CLKFBIN CLKINSEL

RST

Input

DADDR[4:0]

Input

96

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

General Usage Description

Table 3-3:

PLL Ports (Continued)

I/O Input Pin Description The dynamic reconfiguration data input (DI) bus provides reconfiguration data. When not used, all bits must be set to zero. The dynamic reconfiguration write enable (DWE) input pin provides the write 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 access the dynamic reconfiguration feature. When the dynamic reconfiguration feature is not used, DEN must be tied Low. The DCLK signal is the reference clock for the dynamic reconfiguration port. The release pin is used when the PLL is in PMCD mode. When in PLL mode, leave unconnected or tied Low. Only use this pin when porting existing Virtex-4 designs containing the legacy PMCD mode. User configurable clock outputs (0 through 5) that can be divided versions of the VCO phase outputs (user controllable) from 1 (bypassed) to 128. The input clock and output clocks are phase aligned. Dedicated PLL feedback output. User configurable clocks (0 through 5) that can only connect to the DCM within the same CMT as the PLL. PLL feedback used to compensate if the PLL is driving the DCM. If the CLKFBOUT pin is used for this purpose, the software will automatically map to the correct port. 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 will be deasserted if the input clock stops or the phase alignment is violated (e.g., input clock phase shift). The PLL must be reset after LOCKED is deasserted. The dynamic reconfiguration output bus provides PLL data output when using dynamic reconfiguration. The dynamic reconfiguration ready output (DRDY) provides the response to the DEN signal for the PLLs dynamic reconfiguration feature.

Pin Name DI[15:0]

DWE

Input

DEN DCLK REL

Input Input Input

CLKOUT[0:5](1) CLKFBOUT CLKOUTDCM[0:5](1) CLKFBDCM

Output Output Output Output

LOCKED

Output

DO[15:0] DRDY
Notes:

Output Output

1. CLKOUTN and CLKOUTDCMN are utilizing the same output counters and can not be operated independently.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

97

Chapter 3: Phase-Locked Loops (PLLs)

PLL Attributes
Table 3-4: PLL Attributes
Type String Allowed Values Default Description Attribute COMPENSATION

Specifies the PLL phase SYSTEM_SYNCHRONOUS SYSTEM_ SOURCE_SYNCHRONOUS SYNCHRONOUS compensation for the incoming clock. SYSTEM_SYNCHRONOUS attempts to compensate all clock delay for 0 hold time. SOURCE_SYNCHRONOUS is used when a clock is provided with data and thus phased with the clock. Additional attributes automatically selected by the ISE software: INTERNAL EXTERNAL DCM2PLL PLL2DCM

BANDWIDTH

String

HIGH LOW OPTIMIZED 1 to 128

OPTIMIZED

Specifies the PLL programming algorithm affecting the jitter, phase margin and other characteristics of the PLL. Specifies the amount to divide the associated CLKOUT clock output if a different frequency is desired. This number in combination with the CLKFBOUT_MULT and DIVCLK_DIVIDE values will determine the output frequency. Allows specification of the output phase relationship of the associated CLKOUT clock output in number of degrees offset (i.e., 90 indicates a 90 or cycle offset phase offset while 180 indicates a 180 offset or cycle phase offset). Specifies the Duty Cycle of the associated CLKOUT clock output in percentage (i.e., 0.50 will generate a 50% duty cycle). 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.

CLKOUT[0:5]_DIVIDE

Integer

CLKOUT[0:5]_PHASE

Real

360.0 to 360.0

0.0

CLKOUT[0:5]_ DUTY_CYCLE

Real

0.01 to 0.99

0.50

CLKFBOUT_MULT

Integer

1 to 64

98

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

General Usage Description

Table 3-4:

PLL Attributes (Continued)

Type Integer Allowed Values 1 to 52 Default 1 Description Specifies the division ratio for all output clocks with respect to the input clock. 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. Allows specification of the expected jitter on the reference clock in order to better optimize PLL performance. A bandwidth setting of OPTIMIZED will attempt to choose the best parameter for input clocking when unknown. If known, then the value provided should be specified in terms of the UI percentage (the maximum peak to peak value) of the expected jitter on the input clock. Specifies the input period in ns to the PLL CLKIN1 input. Resolution is down to the ps. This information is mandatory and must be supplied. Specifies the input period in ns to the PLL CLKIN2 input. Resolution is down to the ps. This information is mandatory and must be supplied. Fixed delay used when the PLL is used in a PPC440 system. See UG200: Embedded Processor Block in Virtex-5 FPGAs Reference Guide for details. Must be set to FALSE, not supported in silicon.

Attribute DIVCLK_DIVIDE

CLKFBOUT_PHASE

Real

0.0 to 360.0

0.0

REF_JITTER

Real

0.000 to 0.999

0.100

CLKIN1_PERIOD

Real

1.408 to 52.630

0.000

CLKIN2_PERIOD

Real

1.408 to 52.630

0.000

CLKOUT[0:5]_ DESKEW_ADJUST

String

PPC or None

None

RESET_ON_LOSS _OF_LOCK

String

FALSE

FALSE

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

99

Chapter 3: Phase-Locked Loops (PLLs)

PLL CLKIN1 and CLKIN2 Usage

CLKIN1 is the general purpose input to the PLL. The CLKIN2 pin is used to dynamically switch between CLKIN1 and CLKIN2 during operation, as selected by the CLKINSEL pin. If both CLKIN1 and CLKIN2 are used, and the PLL input clocks are driven by global clock pins, there are several restrictions on the placement of both clock signal pins. CLKIN1 can only come from IBUFG[4-0]. CLKIN2 can only come from IBUFG[9-5]. Further, CLKIN2 has to be mapped to a specific location depending on the value of CLKIN1. These rules are as follows: If CLKIN1 is connected to IBUFG [x], CLKIN2 needs to be IBUFG [y] of the same type. Table 3-5 shows the general clock pin pairing. Table 3-5: Mapping Locations
CLKIN2 [5] [6] [7] [8] [9] CLKIN1 [0] [1] [2] [3] [4]

When the PLL input clocks are driven by the global clock trees (BUFGs), both clock inputs must be connected to the same clock input type. Driving one PLL clock input with a IBUFG and the other with a BUFG is not possible. The following tables map the Virtex-5 FPGA global clock IBUFG pins with respect to CLKIN1 and CLKIN2. PLLs in the top half of the Virtex-5 device are driven by the global clock pins in bank3 and can be paired as listed in Table 3-6. Table 3-6: PLLs in the Top Half Pairing
CLKIN2 IO_L4P_GC_3 IO_L3P_GC_3 IO_L2P_GC_3 IO_L1P_GC_3 IO_L0P_GC_3 CLKIN1 IO_L9P_GC_3 IO_L8P_GC_3 IO_L7P_GC_3 IO_L6P_GC_3 IO_L5P_GC_3

100

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

General Usage Description

PLLs in the bottom half of the Virtex-5 device are driven by the global clock pins in bank4 and can be paired as listed in Table 3-6. Table 3-7: PLLs in the Bottom Half Pairing
CLKIN2 IO_L4P_GC_4 IO_L3P_GC_4 IO_L2P_GC_4 IO_L1P_GC_4 IO_L0P_GC_4 CLKIN1 IO_L9P_GC_4 IO_L8P_GC_4 IO_L7P_GC_4 IO_L6P_GC_4 IO_L5P_GC_4

Other important notes on these pairings: The pin description names do not contain other possible multipurpose functions such as _CC, _VRN, _VRP or _VREF. Only the P-side pins are shown. For differential clock connections use the equivalent N-side pin. Inside the FPGA, only the P-side of the differential pin pair can connect to the CMT. For a mapping to the actual pin numbers consult the Virtex-5 Family Packaging Specifications.

PLL Clock Input Signals

The PLL clock source can come from several sources including: IBUFG - Global clock input buffer, the PLL will compensate the delay of this path. BUFGCTRL - Internal global clock buffer, the PLL will not compensate the delay of this path. IBUF - Not recommended since the PLL can not compensate for the delay of the general route. An IBUF clock input must route to a BUFG before routing to a PLL. DCMOUT - Any DCM output to PLL will compensate the delay of this path.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

101

Chapter 3: Phase-Locked Loops (PLLs)

Counter Control
The PLL output counters provide a wide variety of synthesized clock using a combination of DIVIDE, DUTY_CYCLE, and PHASE. Figure 3-6 illustrates how the counter settings impact the counter output. The top waveform represents either the output from the VCO in PLL mode.
X-Ref Target - Figure 3-6

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
UG190_3_06_041406

Figure 3-6:

Output Counter Clock Synthesis Examples

102

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Detailed VCO and Output Counter Waveforms

Clock Shifting
The PLL output clocks can be shifted by inserting delay by selecting one of the eight phases in either the reference or the feedback path. Figure 3-7 shows the effect on a clock signal edge at the output of the PLL without any shifting versus the two cases (delay inserted in the feedback path and delay inserted in the reference path).
X-Ref Target - Figure 3-7

original clock dT feedback added delay in feedback path dT reference added delay in reference path
Figure 3-7: Basic Output Clock Shifting

ug190_03_07_032506

Detailed VCO and Output Counter Waveforms

Figure 3-8 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 insure 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. Phase shifts greater than one VCO period are possible. 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. If the 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 PLL. When an important aspect of the design is to maintain a certain phase relationship amongst various clock outputs, (e.g., CLK and CLK90) then this relationship will be maintained regardless of the input frequency.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

103

Chapter 3: Phase-Locked Loops (PLLs)

X-Ref Target - Figure 3-8

0 45 90 VCO 8 Phases 135 180 225 270 315 O0 Counter Outputs O1 O2 O3 One Cycle Delay
ug190_03_08_032506

Figure 3-8:

Selecting VCO Phases

All O counters are equivalent, anything O0 can do, O1 can do. The 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 the designer as the software and PLL Wizard determines the proper settings through the PLL attributes and Wizard inputs.

Reference Clock Switching

The PLL reference clock can be dynamically switched by using the CLKINSEL pin. The switching is done asynchronously. Since the clock signal can generate a narrow pulse resulting in erroneous behavior of the PLL, the PLL should be held in RESET while selecting the alternate clock with the CLKINSEL (CLKSRC) signal. The PLL clock mux switching is shown in Figure 3-9. The CLKINSEL (CLKSRC) signal directly controls the mux. No synchronization logic is present.
X-Ref Target - Figure 3-9

CLKSRC BUFG IBUFG DCM CLKIN1 PLL CLKIN

BUFG IBUFG DCM CLKIN2

ug190_3_09_050906

Figure 3-9: Input Clock Switching

104

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

PLL Use Models

Missing Input Clock or Feedback Clock

When the input clock or feedback clock is lost, the PLL will drive the output clocks to a lower or higher frequency, causing all of the output clocks to increase/decrease in frequency. The frequency increase/decrease can cause the clock output frequencies to change to as much as six times the original configuration.

PLL Use Models

There are several methods to design with the PLL. The PLL wizard in ISE software can assist with generating the various PLL parameters. Additionally, the PLL can be manually instantiated as a component. It is also possible for the PLL to be merge with an IP core. The IP core would contain and manage the PLL.

Clock Network Deskew

One of the predominant uses of the PLL is for clock network deskew. Figure 3-10 shows the PLL in this mode. The clock output from one of the O 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. This configuration is the most flexible, but it does require two global clock networks (Figure 3-10).
X-Ref Target - Figure 3-10

IBUFG 1 2 3 CLKIN1 RST CLKOUT0 CLKOUT2 CLKOUT3 CLKOUT4 CLKOUT5 CLKFBOUT 6 CLKFBIN CLKOUT1 4

BUFG 5 1 To Logic 2 3 BUFG 4 5 6

UG190_3_10_040809

PLL

Figure 3-10:

Clock Deskew Using Two BUFGs

There are certain restrictions on implementing the feedback. The CLKFBOUT output can be used to provide the feedback clock signal. 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 = -----------D M

Equation 3-8

As an example, if IN is 166 MHz, D = 1, M = 3, and O = 1, then VCO and the clock output frequency are both 498 MHz. Since the M value in the feedback path is 3, 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 = 15, and O = 2. The VCO frequency in this case is 500 MHz and the O output frequency is 250 MHz. Therefore, the feedback frequency at the PFD is 500/15 or 33.33 MHz, matching the 66.66MHz/2 input clock frequency at the PFD.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

105

Chapter 3: Phase-Locked Loops (PLLs)

PLL with Internal Feedback

The PLL feedback can be internal to the PLL when the PLL is used as a synthesizer or jitter filter and there is no required phase relationship between the PLL input clock and the PLL output clock. The PLL performance should increase since 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-11).
X-Ref Target - Figure 3-11

IBUFG CLKIN1 RST CLKOUT0 CLKOUT2 CLKOUT3 CLKOUT4 CLKOUT5 CLKFBOUT

BUFG To Logic

CLKFBIN CLKOUT1

PLL

UG190_3_11_040906

Figure 3-11:

PLL with Internal Feedback

Zero Delay Buffer

The PLL 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-12. 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. There will be a limitation on the maximum delay allowed in the feedback path.
X-Ref Target - Figure 3-12

IBUFG

Inside FPGA CLKIN1 CLKOUT0 CLKOUT1 CLKFBIN CLKOUT2 RST CLKOUT3 CLKOUT4

BUFG

OBUF

To External Components

PLL

CLKOUT5 CLKFBOUT

BUFG

UG190_3_12_120108

Figure 3-12:

Zero Delay Buffer

106

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

PLL Use Models

In some cases precise alignment will not 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 on 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.

DCM Driving PLL

The DCM provides an excellent method for generating precision phase-shifted clocks. However, the DCM cannot reduce the jitter on the reference clock. The PLL can be used to reduce the output jitter of one DCM clock output. This configuration is shown in Figure 3-13. The PLL is configured to not introduce any phase shift (zero delay through the PLL). The associated waveforms are shown to the right of the block diagram. When the output of the DCM is used to drive the PLL directly, both DCM and PLL must reside within the same CMT block. This is the preferred implementation since it produces a minimal amount of noise on the local, dedicated route. However, a connection can also be made by connecting the DCM to a BUFG and then to the CLKIN input of a PLL.
X-Ref Target - Figure 3-13

IBUFG 1 2 3 CLKIN CLKFBIN RST DCM CLK0 CLK90 CLK180 CLK270 CLK2X CLK2X180 CLKDV CLKFX CLKFX180

BUFG

1 2 3 4 BUFG 5 To Logic, etc. 6

4 Matches 5

CLKIN1 CLKFBIN RST PLL

CLKOUT0 CLKOUT1 CLKOUT2 CLKOUT3 CLKOUT4 CLKOUT5 CLKFBOUT

ug190_3_13_092107

Figure 3-13:

DCM Driving a PLL

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

107

Chapter 3: Phase-Locked Loops (PLLs)

PLL Driving DCM

A second option for reduce clock jitter is to use the PLL to clean-up the input clock jitter before driving into the DCM. This will improve the output jitter of all DCM outputs, but any added jitter by the DCM will still be passed to the clock outputs. Both PLL and DCM should reside in the same CMT block because dedicated resources exist between the PLL and DCM to support the zero delay mode. When the PLL and DCM do not reside in the same CMT, then the only connection is through a BUFG hindering the possibility of deskew. One PLL can drive multiple DCMs as long as the reference frequency can be generated by a single PLL. For example, if a 33 MHz reference clock is driven into the PLL, and the design uses one DCM to operate at 200 MHz and the other to run at 100 MHz, then the VCO can be operated at 600 MHz (M1 = 18). The VCO frequency can be divided by three to generate a 200 MHz clock and another counter can be divided by six to generate the 100 MHz clock. For the example in Figure 3-14, one PLL can drive both DCMs.
X-Ref Target - Figure 3-14

IBUFG 1 2 3 CLKIN1 CLKFBIN RST PLL CLKOUT0 CLKOUT1 CLKOUT2 CLKOUT3 CLKOUT4 CLKOUT5 CLKFBOUT Matches

1 BUFG 4 5 To Logic, etc. 3 6 To Logic, etc. 2

CLKIN CLKFBIN RST DCM

CLK0 CLK90 CLK190 CLK270 CLK2X CLK2X190 CLKDV CLKFX CLKFX180

4 5 6
ug190_3_14_092107

Figure 3-14:

PLL Driving a DCM

108

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Application Guidelines

PLL to PLL Connection

The PLL can be cascaded to allow generation of a greater range of clock frequencies. The frequency range restrictions still apply. Equation 3-9 shows the relationship between the final output frequency and the input frequency and counter settings of the two PLLs (Figure 3-15.) The phase relationship between the output clock of the second PLL and the input clock is undefined.To cascade PLLs, route the output of the first PLL to a BUFG and then to the CLKIN pin of the second PLL. This path provides the lowest device jitter. M PLL2 M PLL2 M PLL1 f OUTPLL2 = f OUTPLL1 --------------------------------------- = f IN --------------------------------------- --------------------------------------- Equation 3-9 D PLL2 O PLL2 D PLL1 O PLL1 D PLL2 O PLL2
X-Ref Target - Figure 3-15

IBUFG CLKIN1 RST CLKOUT0 CLKOUT2 CLKOUT3 CLKOUT4 CLKOUT5 CLKFBOUT

BUFG CLKIN1 RST CLKOUT0 CLKOUT2 CLKOUT3 CLKOUT4 CLKOUT5 CLKFBOUT

BUFG To Logic

CLKFBIN CLKOUT1

CLKFBIN CLKOUT1

PLL

PLL

ug190_3_16_032506

Figure 3-15:

Cascading Two PLLs

Application Guidelines
This section summarizes when to select a DCM over a PLL, or a PLL over a DCM. Virtex-5 FPGA PLLs support up to six independent outputs. Designs using several different outputs should use PLLs. An example of designs using several different outputs follows. The PLL is an ideal solution for this type of application because it can generate a configurable set of outputs over a wide range while the DCM has a fixed number of predetermined outputs based off the reference clock. When the application requires a fine phase shift or a dynamic variable phase shift, a DCM could be a better solution.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

109

Chapter 3: Phase-Locked Loops (PLLs)

PLL Application Example

The following PLL 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_DUTY_CYCLE = 0.5; CLKOUT1_DIVIDE = 2; CLKOUT2_PHASE = 0; CLKOUT2_DUTY_CYCLE = 0.25; CLKOUT2_DIVIDE = 4; CLKOUT3_PHASE = 90; CLKOUT3_DUTY_CYCLE = 0.5; CLKOUT3_DIVIDE = 8; CLKOUT4_PHASE = 0; CLKOUT4_DUTY_CYCLE = 0.5; CLKOUT4_DIVIDE = 8; CLKOUT5_PHASE = 135; CLKOUT5_DUTY_CYCLE = 0.5; CLKOUT5_DIVIDE = 8; CLKFBOUT_PHASE = 0; CLKFBOUT_MULT = 8; DIVCLK_DIVIDE = 1; CLKIN1_PERIOD = 10.0;

Figure 3-16 displays the resulting waveforms.

X-Ref Target - Figure 3-16

REFCLK VCOCLK CLKOUT0 CLKOUT1 CLKOUT2 CLKOUT3 CLKOUT4 CLKOUT5

UG190_3_19_032506

Figure 3-16:

Example Waveform

110

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

PLL in Virtex-4 FPGA PMCD Legacy Mode

PLL in Virtex-4 FPGA PMCD Legacy Mode

Virtex-5 devices do not have Phase-Matched Clock Dividers (PMCDs). The Virtex-5 FPGA PLL supports the Virtex-4 FPGA PMCD mode of operation. To take advantage of the inherently more powerful features of the Virtex-5 FPGA PLL, Xilinx recommends redesigning Virtex-4 FPGA PMCDs by implementing PLLs directly. The difference between the Virtex-5 FPGA PLL and the Virtex-4 FPGA PMCD block in Virtex-4 FPGA PMCD legacy mode is that only two clock inputs are supported in the Virtex-5 device implementation. The Virtex-4 device implementation supported up to four clock inputs. If four clock inputs must be used, then two PLLs can be put into PMCD mode. In this case, delay matching is not optimal. Figure 3-17 shows the Virtex-4 FPGA PMCD primitive implemented using a PLL. A PLL can not be used as a PLL if it is already being used as a PMCD. To design-in the Virtex-5 FPGA PMCD functionality, instantiate a Virtex-4 FPGA PMCD primitive. ISE software maps the Virtex-4 FPGA PMCD primitive into a Virtex-5 FPGA PLL.
X-Ref Target - Figure 3-17

CLKFBIN

CLKFBOUT

CLKIN

O0

O1

To BUFG

O2

O3
ug190_3_16_022207

Figure 3-17:

PMCD Primitive Implemented Using the PLL in PMCD Legacy Mode

Table 3-8 shows the port mapping between Virtex-5 FPGA PLL in PMCD legacy mode and the Virtex-4 FPGA PMCD port names. Table 3-8: Mapping of Port Names
Virtex-5 FPGA Port Name CLKIN CLKFBIN n/a n/a CLKOUT3 CLKOUT2 CLKOUT1 CLKOUT0

Virtex-4 FPGA Port Name CLKA CLKB CLKC CLKD CLKA1 CLKA1D2 CLKA1D4 CLKA1D8

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

111

Chapter 3: Phase-Locked Loops (PLLs)

Table 3-8:

Mapping of Port Names (Continued)

Virtex-5 FPGA Port Name CLKFBOUT n/a n/a RST REL

Virtex-4 FPGA Port Name CLKB1 CLKC1 CLKD1 RST REL

Table 3-9 shows the PLL attributes in Virtex-4 FPGA PMCD legacy mode. Table 3-9: PLL Attributes When in Virtex-4 FPGA PMCD Legacy Mode
Type Boolean Boolean Allowed Values TRUE or FALSE TRUE or FALSE Default FALSE FALSE Description Enables PLL to act as PMCDs When in PMCD mode (PLL_PMCD_MODE = TRUE), specifies release of divided clock CLKA outputs when the REL input pin is asserted. When in PMCD mode (PLL_PMCD_MODE = TRUE), specifies a clock to synchronize with the release of RST.

Attribute PLL_PMCD_MODE EN_REL

RST_DEASSERT_CLK

String

CLKA CLKB

CLKA

Table 3-10 shows the PLL ports in Virtex-4 FPGA PMCD legacy mode. Table 3-10:
Port Name CLKFB CLKIN RST

PLL Ports in Virtex-4 FPGA PMCD Legacy Mode

I/O Input Input Input Pin Description Virtex-4 FPGA PMCD legacy mode CLKB input clock to the PMCD. Virtex-4 FPGA PMCD legacy mode CLKA input clock to the PMCD. RST is the reset input to the Virtex-4 FPGA PMCD legacy mode. Asserting RST signal asynchronously forces all outputs Low. Deasserting RST synchronously allows all outputs to toggle. REL is the release input to the Virtex-4 FPGA PMCD legacy mode. Asserting the REL signal releases the divided outputs synchronous to CLKA. Virtex-4 FPGA PMCD legacy mode CLKB1. Virtex-4 FPGA PMCD legacy mode CLKA1. Virtex-4 FPGA PMCD legacy mode CLKA1D2. Virtex-4 FPGA PMCD legacy mode CLKA1D4. Virtex-4 FPGA PMCD legacy mode CLKA1D8.

REL CLKOUT0 CLKOUT1 CLKOUT2 CLKOUT3 CLKOUT4

Input Output Output Output Output Output

112

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Chapter 4

Block RAM
Block RAM Summary
The block RAM in Virtex-5 FPGAs stores up to 36K bits of data and can be configured as either two independent 18 Kb RAMs, or one 36 Kb RAM. Each 36 Kb block RAM can be configured as a 64K x 1 (when cascaded with an adjacent 36 Kb block RAM), 32K x 1, 16K x 2, 8K x 4, 4K x 9, 2K x 18, or 1K x 36 memory. Each 18 Kb block RAM can be configured as a 16K x 1, 8K x2 , 4K x 4, 2K x 9, or 1K x 18 memory. Similar to the Virtex-4 FPGA block RAMs, Write and Read are synchronous operations; the two ports are symmetrical and totally independent, sharing only the stored data. Each port can be configured in one of the available widths, independent of the other port. In addition, the read port width can be different from the write port width for each port. The memory content can be initialized or cleared by the configuration bitstream. During a write operation the memory can be set to have the data output either remain unchanged, reflect the new data being written or the previous data now being overwritten. Virtex-5 FPGA block RAM enhancements include: Increased memory storage capability per block. Each block RAM can store up to 36K bits of data. Support of two independent 18K blocks, or a single 36K block RAM. Each 36K block RAM can be set to simple dual-port mode, doubling data width of the block RAM to 72 bits. The 18K block RAM can also be set to simple dual-port mode, doubling data width to 36 bits. Simple dual-port mode is defined as having one readonly port and one write-only port with independent clocks. Two adjacent block RAMs can be combined to one deeper 64K x 1 memory without any external logic. One 64-bit Error Correction Coding block is provided per 36 Kb block RAM or 36 Kb FIFO. Separate encode/decode functionality is available. Synchronous Set/Reset of the outputs to an initial value is available for both the latch and register modes of the block RAM output. An attribute to configure the block RAM as a synchronous FIFO to eliminate flag latency uncertainty. The Virtex-5 FIFO does not have FULL flag assertion latency.

Virtex-5 FPGA block RAM features: 18, 36, or 72-bit wide ports can have an individual write enable per byte. This feature is popular for interfacing to an on-chip microprocessor. Each block RAM contains optional address sequencing and control circuitry to operate as a built-in multirate FIFO memory. In Virtex-5 architecture, the block RAM can be configured as an 18Kb or 36Kb FIFO.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

113

Chapter 4: Block RAM

All inputs are registered with the port clock and have a setup-to-clock timing specification. All outputs have a read function or a read-during-write function, depending on the state of the write enable (WE) pin. The outputs are available after the clock-to-out timing interval. The read-during-write outputs have one of three operating modes: WRITE_FIRST, READ_FIRST, and NO_CHANGE. A write operation requires one clock edge. A read operation requires one clock edge. All output ports are latched. The state of the output port does not change until the port executes another read or write operation. The default block RAM output is latch mode. The output data path has an optional internal pipeline register. Using the register mode is strongly recommended. This allows a higher clock rate, however, it adds a clock cycle latency of one.

Virtex-5 FPGA block RAM usage rules: The Synchronous Set/Reset (SSR) port cannot be used when the ECC decoder is enabled (EN_ECC_READ = TRUE). The setup time of the block RAM address and write enable pins must not be violated. Violating the address setup time (even if write enable is Low) will corrupt the data contents of the block RAM. The block RAM register mode SSR requires REGCE = 1 to reset the output DO register value. The block RAM array data output latch does not get reset in this mode. The block RAM latch mode SSR requires the block RAM enable, EN = 1, to reset the output DO latch value. Although RAMB18SDP (x36 18k block RAM) and RAMB36SDP (x72 36k block RAM) are simple dual-port primitives, the true dual-port primitives (RAMB18 and RAMB36) can be used with one read-only port and one write-only port. For example: a RAMB18s READ_WIDTH_A = 18, WRITE_WIDTH_B = 9, with WEA = 0 and WEB = 1 is effectively a simple dual-port block RAM with a smaller port width having been derived from the true dual-port primitive. Similarly, a ROM function can be built out of either the true dual-port (RAMB18 or RAMB36) or the simple dual-port block RAM primitives (RAMB18SDP or RAMB36SDP). Different read and write port width choices are available when using specific block RAM primitives. The parity bits are only available for the x9, x18, and x36 port widths. The parity bits should not be used when the read width is x1, x2, or x4. If the read width is x1, x2 or x4, the effective write width is x1, x2, x4, x8, x16, or x32. Similarly, when a write width is x1, x2, or x4, the actual available read width is x1, x2, x4, x8, x16, or x32 even though the primitive attribute is set to 1, 2, 4, 9, 18, or 36 respectively. Table 4-1 shows some possible scenarios. Parity Use Sceneries
Settings Primitive Read Width RAMB18 RAMB18 RAMB18 RAMB18 1, 2, or 4 9 or 18 1, 2, or 4 9 or 18 Write Width 9 or 18 1, 2, or 4 1, 2, or 4 9 or 18 Same as setting 8 or 16 Same as setting Same as setting 8 or 16 Same as setting Same as setting Same as setting Effective Read Width Effective Write Width

Table 4-1:

114

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Block RAM Introduction

Table 4-1:
Primitive

Parity Use Sceneries (Continued)

Settings Effective Read Width Effective Write Width Read Width Write Width 9, 18, or 36 1, 2, or 4 1, 2, or 4 9, 18, or 36 Same as setting 8, 16, or 32 Same as setting Same as setting 8, 16, or 32 Same as setting Same as setting Same as setting 1, 2, or 4 9, 18, or 36 1, 2, or 4 9, 18, or 36

RAMB36 RAMB36 RAMB36 RAMB36

Notes:

1. Do not use parity bits DIP/DOP when one port widths is less than nine and another port width is nine or greater.

Block RAM Introduction

In addition to distributed RAM memory and high-speed SelectIO memory interfaces, Virtex-5 devices feature a large number of 36 Kb block RAMs. Each 36 Kb block RAM contains two independently controlled 18 Kb RAMs. Block RAMs are placed in columns, and the total number of block RAM memory depends on the size of the Virtex-5 device. The 36 Kb blocks are cascadable to enable a deeper and wider memory implementation, with a minimal timing penalty. Embedded dual- or single-port RAM modules, ROM modules, synchronous FIFOs, and data width converters are easily implemented using the Xilinx CORE Generator block memory modules. Multirate FIFOs can be generated using the CORE Generator FIFO Generator module. The synchronous or asynchronous (multirate) FIFO implementation does not require additional CLB resources for the FIFO control logic since it uses dedicated hardware resources.

Synchronous Dual-Port and Single-Port RAMs

Data Flow
The true dual-port 36 Kb block RAM dual-port memories consist of a 36 Kb storage area and two completely independent access ports, A and B. Similarly, each 18 Kb block RAM dual-port memory consists of an 18 Kb storage area and two completely independent access ports, A and B. The structure is fully symmetrical, and both ports are interchangeable. Figure 4-1 illustrates the true dual-port data flow. Table 4-2 lists the port names and descriptions. Data can be written to either or both ports and can be read from either or both ports. Each write operation is synchronous, each port has its own address, data in, data out, clock, clock enable, and write enable. The read and write operations are synchronous and require a clock edge. There is no dedicated monitor to arbitrate the effect of identical addresses on both ports. It is up to the user to time the two clocks appropriately. Conflicting simultaneous writes to the same location never cause any physical damage but can result in data uncertainty.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

115

Chapter 4: Block RAM

X-Ref Target - Figure 4-1

CASCADEOUTLATA CASCADEOUTREGA

CASCADEOUTLATB CASCADEOUTREGB

36-Kbit Block RAM DIA DIPA ADDRA WEA ENA SSRA CLKA REGCEA 36 Kb Memory Array DOB DOPB

Port A

DOA DOPA

DIB DIPB ADDRB WEB ENB SSRB CLKB REGCEB

Port B

CASCADEINLATA CASCADEINREGA

CASCADEINLATB CASCADEINREGB
ug0190_4_01_032106

Figure 4-1: Table 4-2:

True Dual-Port Data Flows

True Dual-Port Names and Descriptions

Description Data Input Bus Data Input Parity Bus, can be used for additional data inputs Address Bus Byte-wide Write Enable When inactive no data is written to the block RAM and the output bus remains in its previous state Synchronous Set/Reset for either latch or register modes Clock Input Data Output Bus Data Output Parity Bus, can be used for additional data outputs Output Register Enable Cascade input pin for 64K x 1 mode when optional output registers are not enabled

Port Name DI[A|B] DIP[A|B](1) ADDR[A|B] WE[A|B] EN[A|B] SSR[A|B] CLK[A|B] DO[A|B] DOP[A|B](1) REGCE[A|B] CASCADEINLAT[A|B]

116

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Synchronous Dual-Port and Single-Port RAMs

Table 4-2:

True Dual-Port Names and Descriptions (Continued)

Description Cascade output pin for 64K x 1 mode when optional output registers are not enabled Cascade input for 64K x 1 mode when optional input register is enabled Cascade output for 64K x 1 mode when optional output register is enabled

Port Name CASCADEOUTLAT[A|B] CASCADEINREG[A|B] CASCADEOUTREG[A|B]

Notes:

1. The Data-In Buses - DI[A|B]<#:0> & DIP[A|B]<#:0> section has more information on data parity pins.

Read Operation
In latch mode, the read operation uses one clock edge. The read address is registered on the read port, and the stored data is loaded into the output latches after the RAM access time. When using the output register, the read operation will take one extra latency cycle.

Write Operation
A write operation is a single clock-edge operation. The write address is registered on the write port, and the data input is stored in memory.

Write Modes
Three settings of the write mode determines the behavior of the data available on the output latches after a write clock edge: WRITE_FIRST, READ_FIRST, and NO_CHANGE. Write mode selection is set by configuration. The Write mode attribute can be individually selected for each port. The default mode is WRITE_FIRST. WRITE_FIRST outputs the newly written data onto the output bus. READ_FIRST outputs the previously stored data while new data is being written. NO_CHANGE maintains the output previously generated by a read operation. For the simple dual port block RAM and ECC configurations, the Write mode is always READ_FIRST, and therefore no collision can occur when used in synchronous mode.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

117

Chapter 4: Block RAM

WRITE_FIRST or Transparent Mode (Default)

In WRITE_FIRST mode, the input data is simultaneously written into memory and stored in the data output (transparent write), as shown in Figure 4-2. These waveforms correspond to latch mode when the optional output pipeline register is not used.
X-Ref Target - Figure 4-2

CLK WE DI ADDR DO EN
Disabled Read Write MEM(bb)=1111 Write MEM(cc)=2222 Read 0000 XXXX 1111 2222 XXXX

aa

bb

cc

dd

MEM(aa)

1111

2222

MEM(dd)

ug190_4_03_032206

Figure 4-2:

WRITE_FIRST Mode Waveforms

READ_FIRST or Read-Before-Write Mode

In READ_FIRST mode, data previously stored at the write address appears on the output latches, while the input data is being stored in memory (read before write). The waveforms in Figure 4-3 correspond to latch mode when the optional output pipeline register is not used.
X-Ref Target - Figure 4-3

CLK WE DI ADDR DO EN
Disabled Read Write MEM(bb)=1111 Write MEM(cc)=2222 Read 0000 XXXX 1111 2222 XXXX

aa

bb

cc

dd

MEM(aa)

old MEM(bb)

old MEM(cc)

MEM(dd)

ug190_4_04_032206

Figure 4-3:

READ_FIRST Mode Waveforms

NO_CHANGE Mode
In NO_CHANGE mode, the output latches remain unchanged during a write operation. As shown in Figure 4-4, data output remains the last read data and is unaffected by a write operation on the same port. These waveforms correspond to latch mode when the optional output pipeline register is not used.

118

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Synchronous Dual-Port and Single-Port RAMs

X-Ref Target - Figure 4-4

CLK WE DI ADDR DO EN
Disable Read Write MEM(bb)=1111 Write MEM(cc)=2222 Read
ug190_4_05_032206

XXXX

1111

2222

XXXX

aa

bb

cc

dd

0000

MEM(aa)

MEM(dd)

Figure 4-4:

NO_CHANGE Mode Waveforms

Conflict Avoidance
Virtex-5 FPGA block RAM memory is a true dual-port RAM where both ports can access any memory location at any time. When accessing the same memory location from both ports, the user must, however, observe certain restrictions. There are two fundamentally different situations: The two ports either have a common clock (synchronous clocking), or the clock frequency and phase is different for the two ports (asynchronous clocking).

Asynchronous Clocking
Asynchronous clocking is the more general case, where the active edges of both clocks do not occur simultaneously: There are no timing constraints when both ports perform a read operation. When one port performs a write operation, the other port must not read- or writeaccess the same memory location. The simulation model will produce an error if this condition is violated. If this restriction is ignored, a read or write operation will produce unpredictable results. There is, however, no risk of physical damage to the device. If a read and write operation is performed, then the write will store valid data at the write location.

Synchronous Clocking
Synchronous clocking is the special case, where the active edges of both port clocks occur simultaneously: There are no timing constraints when both ports perform a read operation. When one port performs a write operation, the other port must not write into the same location, unless both ports write identical data. When one port performs a write operation, the write operation succeeds; the other port can reliably read data from the same location if the write port is in READ_FIRST mode. DATA_OUT on both ports will then reflect the previously stored data. If the write port is in either WRITE_FIRST or in NO_CHANGE mode, then the DATAOUT on the read port would become invalid (unreliable). The mode setting of the read-port does not affect this operation.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

119

Chapter 4: Block RAM

Additional Block RAM Features in Virtex-5 Devices

Optional Output Registers
The optional output registers improve design performance by eliminating routing delay to the CLB flip-flops for pipelined operation. An independent clock and clock enable input is provided for these output registers. As a result the output data registers hold the value independent of the input register operation. Figure 4-5 shows the optional output register.
X-Ref Target - Figure 4-5

DO Address DI Register Memory Array (common to both ports) Write Strobe WE EN Read Strobe Control Engine D Q Latches D Q Register

Latch Enable

CLK

Optional Inverter Configurable Options

UG190_4_06_040606

Figure 4-5:

Block RAM Logic Diagram (One Port Shown)

Independent Read and Write Port Width Selection

Each block RAM port has control over data width and address depth (aspect ratio). The true dual-port block RAM in Virtex-5 FPGAs extends this flexibility to Read and Write where each individual port can be configured with different data bit widths. For example, port A can have a 36-bit Read width and a 9-bit Write width, and port B can have a 18-bit Read width and a 36-bit Write width. See Block RAM Attributes, page 128. If the Read port width differs from the Write port width, and is configured in WRITE_FIRST mode, then DO shows valid new data for all the enabled write bytes. The DO port outputs the original data stored in memory for all not enabled bytes. Independent Read and Write port width selection increases the efficiency of implementing a content addressable memory (CAM) in block RAM. This option is available for all Virtex-5 FPGA true dual-port RAM port sizes and modes.

120

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Additional Block RAM Features in Virtex-5 Devices

Simple Dual-Port Block RAM

Each 18 Kb block and 36 Kb block can also be configured in a simple dual-port RAM mode. In this mode, the block RAM port width doubles to 36 bits for the 18 Kb block RAM and 72 bits for the 36 Kb block RAM. In simple dual-port mode, independent Read and Write operations can occur simultaneously, where port A is designated as the Read port and port B as the Write port. When the Read and Write port access the same data location at the same time, it is treated as a collision, similar to the port collision in true dual-port mode. Readback through the configuration port is not supported in simple dual-port block RAM mode. Figure 4-6 shows the simple dual-port data flow.
X-Ref Target - Figure 4-6

36 Kb Memory Array
64 8 8 9
DI DO DIP DOP WE WEADDR WRCLK WREN RDEN

64 8

RDADDR RDCLK REGCE SSR

ug190_4_02_041206

Figure 4-6: Table 4-3:

Simple Dual-Port Data Flow

Simple Dual-Port Names and Descriptions

Descriptions Data Output Bus Data Output Parity Bus Data Input Bus Data Input Parity Bus Read Data Address Bus Read Data Clock Read Port Enable Output Register Clock Enable Synchronous Set/Reset Byte-wide Write Enable Write Data Address Bus Write Data Clock Write Port Enable

Port Names DO DOP DI DIP RDADDR RDCLK RDEN REGCE SSR WE WRADDR WRCLK WREN

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

121

Chapter 4: Block RAM

Cascadable Block RAM

In the Virtex-5 block RAM architecture, two 32K x 1 RAMs can be combined to form one 64K x 1 RAM without using local interconnect or additional CLB logic resources. Any two adjacent block RAMs can be cascaded to generate a 64K x 1 block RAM. Increasing the depth of the block RAM by cascading two block RAMs is available only in the 64K x 1 mode. Further information on cascadable block RAM is described in the Additional RAMB18 and RAMB36 Primitive Design Considerations section. For other wider and/or deeper sizes, consult the Creating Larger RAM Structures section. Figure 4-7 shows the block RAM with the appropriate ports connected in the Cascadable mode.
X-Ref Target - Figure 4-7

CASCADEOUT (No Connect)

DI A[14:0] A15 RAM_EXTENSION = UPPER(0) 0 1 WE[3:0] DI A[14:0] A15 RAM_EXTENSION = LOWER(1) 0 1 WE[3:0] Interconnect Block RAM

D Q D Q D Q

DI A[14:0] A15

D0

Optional Output FF

1 D0 0

WE D Q CASCADEIN of Top DI A[14:0] 1 A15 0 WE D Q CASCADEIN Connect to logic High or Low

ug190_4_07_071607

D Q D Q D Q

D0

Optional Output FF

CASCADEOUT of Bottom

D0 Not Used

Figure 4-7:

Cascadable Block RAM

Byte-wide Write Enable

The byte-wide write enable feature of the block RAM gives the capability to write eight bit (one byte) portions of incoming data. There are four independent byte-wide write enable inputs to the RAMB36 true dual-port RAM. There are eight independent byte-wide write enable inputs to block RAM in simple dual-port mode (RAMB36SDP). Table 4-4 summarizes the byte-wide write enables for the 36K and 18K block RAM. Each byte-wide write enable is associated with one byte of input data and one parity bit. All byte-wide write enable inputs must be driven in all data width configurations. This feature is useful when using block RAM to interface with a microprocessor. Byte-wide write enable is not available in the multirate FIFO or ECC mode. Byte-wide write enable is further described in the Additional RAMB18 and RAMB36 Primitive Design Considerations section. Figure 4-8 shows the byte-wide write-enable timing diagram for the RAMB36. Table 4-4: Available Byte-wide Write Enables
Maximum Bit Width 36 72 Number of Byte-wide Write Enables 4 8

Primitive RAMB36 RAMB36SDP

122

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Block RAM Library Primitives

Table 4-4:

Available Byte-wide Write Enables (Continued)

Maximum Bit Width 18 36 Number of Byte-wide Write Enables 2 4

Primitive RAMB18 RAMB18SDP

When the RAMB36 is configured for a 36-bit or 18-bit wide data path, any port can restrict writing to specified byte locations within the data word. If configured in READ_FIRST mode, the DO bus shows the previous content of the whole addressed word. In WRITE_FIRST mode, DO shows a combination of the newly written enabled byte(s), and the initial memory contents of the unwritten bytes.
X-Ref Target - Figure 4-8

CLK WE DI ADDR DO EN
Disabled Read Write MEM(bb)=1111 Byte Write MEM(bb)=1122 Read 0000 XXXX 1111 1111 0011 2222 XXXX

aa

bb

bb

cc

MEM(aa)

1111

1122

MEM(cc)

ug190_4_10_032106

Figure 4-8:

Byte-wide Write Operation Waveforms (x36 WRITE_FIRST)

Block RAM Error Correction Code

Both block RAM and FIFO implementations of the 36 Kb block RAM support a 64-bit Error Correction Code (ECC) implementation. The code is used to detect single and double-bit errors in block RAM data read out. Single-bit errors are then corrected in the output data.

Block RAM Library Primitives

The Virtex-5 FPGA block RAM library primitives, RAMB18 and RAMB36, are the basic building blocks for all block RAM configurations. Other block RAM primitives and macros are based on these primitives. Some block RAM attributes can only be configured using one of these primitives (e.g., pipeline register, cascade, etc.). See the Block RAM Attributes section. The input and output data buses are represented by two buses for 9-bit width (8 + 1), 18-bit width (16 + 2), and 36-bit width (32 + 4) configurations. The ninth bit associated with each byte can store parity/error correction bits or serve as additional data bits. No specific function is performed on the ninth bit. The separate bus for parity bits facilitates some designs. However, other designs safely use a 9-bit, 18-bit, or 36-bit bus by merging the regular data bus with the parity bus. Read/write and storage operations are identical for all bits, including the parity bits.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

123

Chapter 4: Block RAM

Figure 4-9 illustrates all the I/O ports of the 36 Kb true dual-port block RAM primitive (RAMB36). Table 4-5 lists these primitives.
X-Ref Target - Figure 4-9

CASCADEOUTLATA CASCADEOUTREGA

CASCADEOUTLATB CASCADEOUTREGB

32 4 16 4

DIA DIPA ADDRA WEA ENA REGCEA SSRA CLKA

DOA DOPA

32 4

32 4 16 4

DIB DIPB ADDRB WEB ENB REGCEB SSRB CLKB DOB DOPB

32 4

CASCADEINLATA CASCADEINREGA

CASCADEINLATB CASCADEINREGB
ug0190_4_10_100906

Figure 4-9: Table 4-5:

Block RAM Port Signals (RAMB36)

Virtex-5 FPGA Block RAM, FIFO, Simple Dual Port, and ECC Primitives
Description Supports port widths of x1, x2, x4, x9, x18, x36 Simple dual port (port width x72) and 64-bit ECC primitive (see Figure 4-29) Supports port widths of x4, x9, x18, x36 FIFO (port width x72), optional ECC support Supports port widths of x1, x2, x4, x9, x18 Simple dual port (port width x36) Supports port widths of x4, x9, x18 FIFO (port width x36)

Primitive RAMB36 RAMB36SDP FIFO36 FIFO36_72 RAMB18 RAMB18SDP FIFO18 FIFO18_36

Notes:

1. All eight primitives are described in the software Libraries guide as well as the language templates.

124

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Block RAM Port Signals

Block RAM Port Signals

Each block RAM port operates independently of the other while accessing the same set of 36K-bit memory cells.

Clock - CLK[A|B]
Each port is fully synchronous with independent clock pins. All port input pins have setup time referenced to the port CLK pin. The output data bus has a clock-to-out time referenced to the CLK pin. Clock polarity is configurable (rising edge by default).

Enable - EN[A|B]
The enable pin affects the read, write, and set/reset functionality of the port. Ports with an inactive enable pin keep the output pins in the previous state and do not write data to the memory cells. Enable polarity is configurable (active High by default).

Byte-wide Write Enable - WE[A|B]

To write the content of the data input bus into the addressed memory location, both EN and WE must be active within a set-up time before the active clock edge. The output latches are loaded or not loaded according to the write configuration (WRITE_FIRST, READ_FIRST, NO_CHANGE). When inactive, a read operation occurs, and the contents of the memory cells referenced by the address bus appear on the data-out bus, regardless of the write mode attribute. Write enable polarity is not configurable (active High).

Register Enable - REGCE[A|B]

The register enable pin (REGCE) controls the optional output register. When the RAM is in register mode, REGCE = 1 registers the output into a register at a clock edge. The polarity of REGCE is not configurable (active High).

Set/Reset - SSR[A|B]
In latch mode, the SSR pin forces the data output latches, to contain the value SRVAL. See Block RAM Attributes, page 128. When the optional output registers are enabled, the data output registers can also be forced by the SSR pin to contain the value SRVAL. SSR does not affect the latched value. The data output latches or output registers are synchronously asserted to 0 or 1, including the parity bit. Each port has an independent SRVAL[A|B] attribute of 36 bits. This operation does not affect RAM memory cells and does not disturb write operations on the other port. Similar to the read and write operation, the set/reset function is active only when the enable pin of the port is active. Set/reset polarity is configurable (active High by default).

Address Bus - ADDR[A|B]<13:#><14:#><15:#>

The address bus selects the memory cells for read or write. The data bit width of the port determines the required address bus width for a single RAMB18 or RAMB36, as shown in Table 4-6 and Table 4-7.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

125

Chapter 4: Block RAM

Table 4-6:

Port Aspect Ratio for RAMB18 and RAMB18SDP

Port Address Width 14 13 12 11 10 9 Depth 16,384 8,192 4,096 2,048 1,024 512 ADDR Bus <13:0> <13:1> <13:2> <13:3> <13:4> <13:5> DI Bus / DO Bus <0> <1:0> <3:0> <7:0> <15:0> <31:0> DIP Bus / DOP Bus NA NA NA <0> <1:0> <3:0>

Port Data Width 1 2 4 9 18 36 (RAMB18SDP)

Table 4-7:

Port Aspect Ratio for RAMB36

Port Address Width 15 14 13 12 11 10 9 16 Depth 32,768 16,384 8,192 4,096 2,048 1,024 512 65536 ADDR Bus <14:0> <14:1> <14:2> <14:3> <14:4> <14:5> <14:6> <15:0> DI Bus / DO Bus <0> <1:0> <3:0> <7:0> <15:0> <31:0> <63:0> <0> DIP Bus / DOP Bus NA NA NA <0> <1:0> <3:0> <7:0> NA

Port Data Width 1 2 4 9 18 36 72 (RAMB36SDP) 1 (Cascade)

For cascadable block RAM using the RAMB36, the data width is one bit, and the address bus is 16 bits <15:0>. The address bit 15 is only used in cascadable block RAM. For noncascading block RAM, connect High. Data and address pin mapping is further described in the Additional RAMB18 and RAMB36 Primitive Design Considerationssection.

Data-In Buses - DI[A|B]<#:0> & DIP[A|B]<#:0>

Data-in buses provide the new data value to be written into RAM. The regular data-in bus (DI), plus the parity data-in bus (DIP) when available, have a total width equal to the port width. For example the 36-bit port data width is represented by DI<31:0> and DIP<3:0>, as shown in Table 4-6 and Table 4-7.

Data-Out Buses - DO[A|B]<#:0> and DOP[A|B]<#:0>

Data-out buses reflect the contents of memory cells referenced by the address bus at the last active clock edge during a read operation. During a write operation (WRITE_FIRST or READ_FIRST configuration), the data-out buses reflect either the data being written or the stored value before write. During a write operation in NO_CHANGE mode, data-out buses are not changed. The regular data-out bus (DO) plus the parity data-out bus (DOP) (when available) have a total width equal to the port width, as shown in Table 4-6 and Table 4-7.

126

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Block RAM Port Signals

Cascade In - CASCADEINLAT[A|B] and CASCADEINREG[A|B]

The CASCADEIN pins are used to connect two block RAMs to form the 64K x 1 mode (Figure 4-10.) This pin is used when the block RAM is the UPPER block RAM, and is connected to the CASCADEOUT pins of the LOWER block RAM of the same port. When cascade mode is not used, this pin does not need to be connected. Refer to the Cascadable Block RAM for further information.
X-Ref Target - Figure 4-10

Upper RAMB36
CASCADEINLATA/B 2 CASCADEOUTLATA/B CASCADEINREGA/B 2 CASCADEOUTREGA/B

Lower RAMB36

ug190_4_12_040606

Figure 4-10:

Two RAMB36s Cascaded

Cascade Out - CASCADEOUTLAT[A|B] and CASCADEOUTREG[A|B]

The CASCADEOUT pins are used to connect two block RAMs to form the 64K x 1 mode. This pin is used when the block RAM is the LOWER block RAM, and is connected to the CASCADEIN pins of the UPPER block RAM of the same port. When cascade mode is not used, this pin does not need to be connected. Refer to the Cascadable Block RAM for further information.

Inverting Control Pins

For each port, the six control pins (CLK, EN, and SSR) each have an individual inversion option. EN and SSR control signals can be configured as active High or Low, and the clock can be active on a rising or falling edge (active High on rising edge by default), without requiring other logic resources.

GSR
The global set/reset (GSR) signal of a Virtex-5 device is an asynchronous global signal that is active at the end of device configuration. The GSR can also restore the initial Virtex-5 device state at any time. The GSR signal initializes the output latches to the INIT (simple dual port), or to the INIT_A and INIT_B value (true dual port.) See Block RAM Attributes. A GSR signal has no impact on internal memory contents. Because it is a global signal, the GSR has no input pin at the functional level (block RAM primitive).

Unused Inputs
Unused data and/or address inputs should be connected High.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

127

Chapter 4: Block RAM

Block RAM Address Mapping

Each port accesses the same set of 18,432 or 36,864 memory cells using an addressing scheme dependent on whether it is a RAMB18 or RAMB36. The physical RAM locations addressed for a particular width are determined using the following formula (of interest only when the two ports use different aspect ratios): END = ((ADDR + 1) Width) -1 START = ADDR Width Table 4-8 shows low-order address mapping for each port width. Table 4-8: Port Address Mapping
Data Locations 3 1 15 7 3 2 1 0 1 0 0 3 1 0 3 0 2 9 14 2 8 2 7 13 6 2 6 2 5 12 2 4 2 3 11 5 2 2 2 2 1 10 2 0 1 9 9 4 1 8 1 7 8 1 6 1 5 7 3 1 0 1 4 1 3 6 1 2 11 1 0 5 2 9 8 7 6 5 4 3 2 1 0

Port Parity Width Locations 1 N.A.

2 4 8+1 16 + 2 32 + 4

3 1

1 0 0

Block RAM Attributes

All attribute code examples are discussed in the Block RAM Initialization in VHDL or Verilog Code section. Further information on using these attributes is available in the Additional RAMB18 and RAMB36 Primitive Design Considerations section.

Content Initialization - INIT_xx

INIT_xx attributes define the initial memory contents. By default, block RAM memory is initialized with all zeros during the device configuration sequence. The 64 initialization attributes from INIT_00 through INIT_3F for the RAMB18, and the 128 initialization attributes from INIT_00 through INIT_7F for the RAMB36 represent the regular memory contents. Each INIT_xx is a 64-digit hex-encoded bit vector. The memory contents can be partially initialized and are automatically completed with zeros. The following formula is used for determining the bit positions for each INIT_xx attribute. Given yy = conversion hex-encoded to decimal (xx), INIT_xx corresponds to the memory cells as follows: from [(yy + 1) 256] 1 to (yy) 256

For example, for the attribute INIT_1F, the conversion is as follows: yy = conversion hex-encoded to decimal (xx) 1F = 31 from [(31+1) 256] 1 = 8191 to 31 256 = 7936

More examples are given in Table 4-9.

128

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Block RAM Attributes

Table 4-9:

Block RAM Initialization Attributes

Memory Location

Attribute From INIT_00 INIT_01 INIT_02 INIT_0E INIT_0F INIT_10 INIT_1F INIT_20 INIT_2F INIT_30 INIT_3F INIT_7F 255 511 767 3839 4095 4351 8191 8447 12287 12543 16383 32767 To 0 256 512 3584 3840 4096 7936 8192 12032 12288 16128 32512

Content Initialization - INITP_xx

INITP_xx attributes define the initial contents of the memory cells corresponding to DIP/DOP buses (parity bits). By default these memory cells are also initialized to all zeros. The initialization attributes represent the memory contents of the parity bits. The eight initialization attributes are INITP_00 through INITP_07 for the RAMB18. The 16 initialization attributes are INITP_00 through INITP_0F for the RAMB36. Each INITP_xx is a 64-digit hex-encoded bit vector with a regular INIT_xx attribute behavior. The same formula can be used to calculate the bit positions initialized by a particular INITP_xx attribute.

Output Latches Initialization - INIT (INIT_A or INIT_B)

The INIT (single-port) or INIT_A and INIT_B (dual-port) attributes define the output latches or output register values after configuration. The width of the INIT (INIT_A and INIT_B) attribute is the port width, as shown in Table 4-10. These attributes are hexencoded bit vectors, and the default value is 0. In cascade mode, both the upper and lower block RAM should be initialized to the same value.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

129

Chapter 4: Block RAM

Output Latches/Registers Synchronous Set/Reset (SRVAL_[A|B])

The SRVAL (single-port) or SRVAL_A and SRVAL_B (dual-port) attributes define output latch values when the SSR input is asserted. The width of the SRVAL (SRVAL_A and SRVAL_B) attribute is the port width, as shown in Table 4-10. These attributes are hexencoded bit vectors and the default value is 0. This attribute sets the value of the output register when the optional output register attribute is set. When the register is not used, the latch gets set to the SRVAL instead. In the 36-bit mode, SRVAL[35:32] corresponds to DP[3:0]. Table 4-10: Port Width Values
DOP Bus NA NA NA <0> <1:0> <3:0> DO Bus <0> <1:0> <3:0> <7:0> <15:0> <31:0> INIT / SRVAL 1 2 4 (1 + 8) = 9 (2 + 16) = 18 (4 + 32) = 36 Port Data Width 1 2 4 9 18 36

Optional Output Register On/Off Switch - DO[A|B]_REG

This attribute sets the number of pipeline register at A/B output of the block RAM. The valid values are 0 (default) or 1.

Extended Mode Address Determinant - RAM_EXTENSION_[A|B]

This attribute determines whether the block RAM of interest has its A/B port as UPPER/LOWER address when using the cascade mode. Refer to the Cascadable Block RAM section. When the block RAM is not used in cascade mode, the default value is NONE.

Read Width - READ_WIDTH_[A|B]

This attribute determines the A/B read port width of the block RAM. The valid values are: 0 (default), 1, 2, 4, 9, 18, and 36.

Write Width - WRITE_WIDTH_[A|B]

This attribute determines the A/B write port width of the block RAM. The valid values are: 0 (default), 1, 2, 4, 9, 18, and 36.

Write Mode - WRITE_MODE_[A|B]

This attribute determines the write mode of the A/B input ports. The possible values are WRITE_FIRST (default), READ_FIRST, and NO_CHANGE. Additional information on the write modes is in the Write Modes section.

130

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Block RAM Initialization in VHDL or Verilog Code

Block RAM Location Constraints

Block RAM instances can have LOC properties attached to them to constrain placement. Block RAM placement locations differ from the convention used for naming CLB locations, allowing LOC properties to transfer easily from array to array. The LOC properties use the following form: LOC = RAMB36_X#Y# The RAMB36_X0Y0 is the bottom-left block RAM location on the device. If RAMB36 is constrained to RAMB36_X#Y#, the FIFO cannot be constrained to FIFO36_X#Y# since they share a location. Two RAMB18s can be placed in the same RAMB36 location by using the BEL UPPER/LOWER constraint:
inst my_ramb18 LOC = RAMB36_X0Y0 | BEL = UPPER inst my_ramb18 LOC = RAMB36_X0Y0 | BEL = LOWER

In addition, one FIFO18 and one RAMB16 can be placed in the same RAMB36 location, no BEL constraint is required:
inst my_fifo18 LOC = RAMB36_X0Y0 inst my_ramb18 LOC = RAMB36_X0Y0

Block RAM Initialization in VHDL or Verilog Code

Block RAM memory attributes and content can be initialized in VHDL or Verilog code for both synthesis and simulation by using generic maps (VHDL) or defparams (Verilog) within the instantiated component. Modifying the values of the generic map or defparam will effect both the simulation behavior and the implemented synthesis results. The Virtex-5 FPGA Libraries Guide includes the code to instantiate the RAMB36 primitive.

Additional RAMB18 and RAMB36 Primitive Design Considerations

The RAMB18 and RAMB36 primitives are integral in the Virtex-5 FPGA block RAM solution.

Optional Output Registers

Optional output registers can be used at either or both A|B output ports of RAMB18 and RAMB36. The choice is made using the DO[A|B]_REG attribute. The two independent clock enable pins are REGCE[A|B]. When using the optional output registers at port [A|B], assertion of the synchronous set/reset (SSR) pin of ports [A|B] causes the value specified by the attribute SRVAL to be registered at the output. Figure 4-5 shows an optional output register.

Independent Read and Write Port Width

To specify the port widths using the dual-port mode of the block RAM, designers must use the READ_WIDTH_[A|B] and WRITE_WIDTH_[A|B] attributes. The following rules should be considered: Designing a single port block RAM requires the port pair widths of one write and one read to be set (e.g., READ_WIDTH_A and WRITE_WIDTH_A). Designing a dual-port block RAM requires all port widths to be set.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

131

Chapter 4: Block RAM

When using these attributes, if both write ports or both read ports are set to 0, the Xilinx ISE tools will not implement the design. In simple dual-port mode, the port width is fixed and the read port width is equal to the write port width. The RAMB18 has a data port width of 36, while the RAMB36 has a data port width of 72.

RAMB18 and RAMB36 Port Mapping Design Rules

The Virtex-5 FPGA block RAM are configurable to various port widths and sizes. Depending on the configuration, some data pins and address pins are not used. Table 4-6, page 126 shows the pins used in various configurations. In addition to the information in Table 4-6, the following rules are useful to determine port connections for the RAMB36: 1. 2. 3. 4. 5. When using RAMB36, if the DI[A|B] pins are less than 32 bits wide, concatenate (32 DI_BIT_WIDTH) logic zeros to the front of DI[A|B]. If the DIP[A|B] pins are less than 4-bits wide, concatenate (4 DIP_BIT_WIDTH) logic zeros to the front of DIP[A|B]. DIP[A|B] can be left unconnected when not in use. DO[A|B] pins must be 32 bits wide. However, valid data is only found on pins DO_BIT_WIDTH 1 down to 0. DOP[A|B] pins must be 4 bits wide. However, valid data is only found on pins DOP_BIT_WIDTH 1 down to 0. DOP[A|B] can be left unconnected when not in use. ADDR[A|B] pins must be 16 bits wide. However, valid addresses for non-cascadable block RAM are only found on pin 14 to (15 address width). The remaining pins, including pin 15, should be tied High. Address width is defined in Table 4-6, page 126.

Cascadable Block RAM

To use the cascadable block RAM feature: 1. 2. 3. Two RAMB36 primitives must be instantiated. Set the RAM_EXTENSION_A and RAM_EXTENSION_B attribute for one RAMB36 to UPPER, and another to LOWER. Connect the upper RAMB36s CASCADEINA and CASCADEINB ports to the CASCADEOUTA and CASCADEOUTB ports of the lower RAMB36. The CASCADEOUT ports for the upper RAMB36 do not require a connection. Connect the CASCADEIN ports for the lower RAMB36 to either logic High or Low. The data output ports of the lower RAMB36 are not used. These pins are unconnected. If placing location constraints on the two RAMB36s, they must be adjacent. If no location constraint is specified, the Xilinx ISE software will automatically manage the RAMB36 locations. The address pins ADDR[A|B] must be 16 bits wide. Both read and write ports must be one bit wide.

4. 5.

6.

Figure 4-7 shows the cascadable block RAM.

Byte-wide Write Enable

The following rules should be considered when using the byte-wide write enable feature: In x36 mode, WE[3:0] is connected to the four user WE inputs. In x18 mode, WE[0] and WE[2] are connected and driven by the user WE[0], while WE[1], and WE[3] are driven by the user WE[1]. In x9, x4, x2, x1, WE[3:0] are all connected to a single user WE.

132

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Additional Block RAM Primitives

In x72 simple dual-port mode, WE[7:0] is connected to the eight user WE inputs.

Additional Block RAM Primitives

In addition to RAMB18 and RAMB36, there are other block RAM primitives available for specific implementations. RAMB18SDP and RAMB36SDP implement the simple dual-port mode configurations of the block RAM. Table 4-3, page 121 shows the ports available for the 18 Kb block RAM configured in simple dual-port mode. The RAMB36SDP can also be configured for the built-in block RAM ECC. For more information on RAMB36SDP with the ECC feature, see Built-in Error Correction, page 158.

Block RAM Applications

Creating Larger RAM Structures
Block RAM columns have special routing to create wider/deeper blocks using 36 Kb block RAMs with minimal routing delays. Wider or deeper RAM structures are achieved with a smaller timing penalty than is encountered when using normal routing resources. The Xilinx CORE Generator program offers the designer an easy way to generate wider and deeper memory structures using multiple block RAM instances. This program outputs VHDL or Verilog instantiation templates and simulation models, along with an EDIF file for inclusion in a design.

Block RAM SSR in Register Mode

A block RAM SSR in register mode can be used to control the output register as a true pipeline register independent of the block RAM. As shown in Figure 4-11, block RAM can be read and written independent of register enable or set/reset. In register mode SSR sets DO to the SRVAL and data can be read from the block RAM to DBRAM. Data at DBRAM can be clocked out (DO) on the next cycle. The timing diagrams in Figure 4-12 and Figure 4-13 show different cases of the SSR operation.
X-Ref Target - Figure 4-11

Block RAM
DI EN BRAM_RAMEN BRAM_SSR REGCE SSR In register mode, the block RAM SSR is disabled and the SSR pin only sets/resets the output registers.
ug190_4_28_071707

DBRAM

Output Register

DO

Figure 4-11:

Block RAM SSR in Register Mode

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

133

Chapter 4: Block RAM

X-Ref Target - Figure 4-12

CLK RAMEN

REGCE

SSR

DBRAM

D0

D1 Block RAM can be read when SSR is active.

D2

D3

DO

D0

SRVAL

D1

SRVAL

D2

Data appears on the output of the next REGCE.

ug190_4_29_071607

Figure 4-12:
X-Ref Target - Figure 4-13

SSR Operation in Register Mode with REGCE High

CLK RAMEN

REGCE

SSR

DBRAM

D0

D1

D2

D3

SSR only sets/resets DO when REGCE is also High. DO D0 SRVAL D1 D2

ug190_4_29_071607

Figure 4-13:

SSR Operation in Register Mode with Variable REGCE

Block RAM Timing Model

This section describes the timing parameters associated with the block RAM in Virtex-5 devices (illustrated in Figure 4-14). The switching characteristics section in the Virtex-5 FPGA Data Sheet and the Timing Analyzer (TRCE) report from Xilinx software are also available for reference.

134

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Block RAM Timing Model

Block RAM Timing Parameters

Table 4-11 shows the Virtex-5 FPGA block RAM timing parameters. Table 4-11: Block RAM Timing Parameters
Function Control Signal Description

Parameter

Setup and Hold Relative to Clock (CLK)

TRxCK_x = Setup time (before clock edge) and TRCKx_x = Hold time (after clock edge) TRCCK_ADDR TRCKC_ADDR TRDCK_DI TRCKD_DI TRCCK_EN TRCKC_EN TRCCK_SSR TRCKC_SSR TRCCK_WE TRCKC_WE TRCCK_REGCE TRCKC_REGCE Optional Output Register Enable REGCE Write Enable WE Synchronous Set/Reset SSR Enable EN Data inputs DI Address inputs ADDR Time before the clock that address signals must be stable at the ADDR inputs of the block RAM.(1) Time after the clock that address signals must be stable at the ADDR inputs of the block RAM.(1) Time before the clock that data must be stable at the DI inputs of the block RAM. Time after the clock that data must be stable at the DI inputs of the block RAM. Time before the clock that the enable signal must be stable at the EN input of the block RAM. Time after the clock that the enable signal must be stable at the EN input of the block RAM. Time before the clock that the synchronous set/reset signal must be stable at the SSR input of the block RAM. Time after the clock that the synchronous set/reset signal must be stable at the SSR input of the block RAM. Time before the clock that the write enable signal must be stable at the WE input of the block RAM. Time after the clock that the write enable signal must be stable at the WE input of the block RAM. Time before the CLK that the register enable signal must be stable at the REGCE input of the block RAM. Time after the clock that the register enable signal must be stable at the REGCE input of the block RAM.

Clock to Out Delays TRCKO_DO (latch mode) TRCKO_DO (register mode)

Notes:
1. While EN is active, ADDR inputs must be stable during the entire setup/hold time window, even if WE is inactive. Violating this requirement can result in block RAM data corruption. If ADDR timing could violate the specified requirements, EN must be inactive (disabled).

Clock to Output Clock to Output

CLK to DO CLK to DO

Time after the clock that the output data is stable at the DO outputs of the block RAM (without output register). Time after the clock that the output data is stable at the DO outputs of the block RAM (with output register).

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

135

Chapter 4: Block RAM

Block RAM Timing Characteristics

The timing diagram in Figure 4-14 describes a single-port block RAM in write-first mode without the optional output register. The timing for read-first and no-change modes are similar. For timing using the optional output register, an additional clock latency appears at the DO pin. These waveforms correspond to latch mode when the optional output pipeline register is not used.
X-Ref Target - Figure 4-14

1 CLK TRCCK_ADDR ADDR DI DO EN 00 TRDCK_DI DDDD TRCKO_DO MEM (00) TRCCK_EN

0F CCCC CCCC*

7E BBBB MEM (7E)

8F AAAA 0101**

20 0000

TRCCK_SSR SSR TRCCK_WE WE Disabled Read Write Read Reset Disabled

* Write Mode = "WRITE_FIRST" ** SRVAL = 0101

ug190_4_13_022207

Figure 4-14:

Block RAM Timing Diagram

At time 0, the block RAM is disabled; EN (enable) is Low.

Clock Event 1
Read Operation
During a read operation, the contents of the memory at the address on the ADDR inputs remain unchanged. TRCCK_ADDR before clock event 1, address 00 becomes valid at the ADDR inputs of the block RAM. At time TRCCK_EN before clock event 1, enable is asserted High at the EN input of the block RAM, enabling the memory for the READ operation that follows. At time TRCKO_DO after clock event 1, the contents of the memory at address 00 become stable at the DO pins of the block RAM. Whenever EN is asserted, all address changes must meet the specified setup and hold window. Asynchronous address changes can affect the memory content and block RAM functionality in an unpredictable way.

136

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Block RAM Timing Model

Clock Event 2
Write Operation
During a write operation, the content of the memory at the location specified by the address on the ADDR inputs is replaced by the value on the DI pins and is immediately reflected on the output latches (in WRITE_FIRST mode); when Write Enable (WE) is High. At time TRCCK_ADDR before clock event 2, address 0F becomes valid at the ADDR inputs of the block RAM. At time TRDCK_DI before clock event 2, data CCCC becomes valid at the DI inputs of the block RAM. At time TRCCK_WE before clock event 2, write enable becomes valid at the WE following the block RAM. At time TRCKO_DO after clock event 2, data CCCC becomes valid at the DO outputs of the block RAM.

Clock Event 4
SSR (Synchronous Set/Reset) Operation
During an SSR operation, initialization parameter value SRVAL is loaded into the output latches of the block RAM. The SSR operation does NOT change the contents of the memory and is independent of the ADDR and DI inputs. At time TRCCK_SSR before clock event 4, the synchronous set/reset signal becomes valid (High) at the SSR input of the block RAM. At time TRCKO_DO after clock event 4, the SRVAL 0101 becomes valid at the DO outputs of the block RAM.

Clock Event 5
Disable Operation
Deasserting the enable signal EN disables any write, read, or SSR operation. The disable operation does NOT change the contents of the memory or the values of the output latches. At time TRCCK_EN before clock event 5, the enable signal becomes invalid (Low) at the EN input of the block RAM. After clock event 5, the data on the DO outputs of the block RAM is unchanged.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

137

Chapter 4: Block RAM

Block RAM Timing Model

Figure 4-15 illustrates the delay paths associated with the implementation of block RAM. This example takes the simplest paths on and off chip (these paths can vary greatly depending on the design). This timing model demonstrates how and where the block RAM timing parameters are used. NET = Varying interconnect delays TIOPI = Pad to I-output of IOB delay TIOOP = O-input of IOB to pad delay TBCCKO_O = BUFGCTRL delay

X-Ref Target - Figure 4-15

FPGA
Block RAM
Data Address Write Enable Enable Synchronous Set/Reset
[TIOPI + NET] + TRDCK_DI [TIOPI + NET] + TRCCK_ADDR [TIOPI + NET] + TRCCK_WEN [TIOPI + NET] + TRCCK_EN [TIOPI + NET] + TRCCK_SSR

DI ADDR WE EN SSR CLK DO

TRCKO_DO + [NET + TIOOP]

Data

[TBCCKO_O + NET] BUFGCTRL

Clock

[TIOPI + NET]
ug190_4_14_022207

Figure 4-15: Block RAM Timing Model

138

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Block RAM Retargeting

Block RAM Retargeting

Table 4-12 suggests the most appropriate primitives to choose when mapping a Virtex-4 FPGA block RAM design in a new Virtex-5 FPGA design. Table 4-12: Block RAM Retargeting
18k Virtex-5 Block RAM Primitive Depth 1k to 16k N/A 512 N/A Port Width R/W 36k Virtex-5 Block RAM Primitive Depth 2k to 32k 1k 1k N/A Port Width R/W 1, 2, 4, 9, 18 36/36 36/36 N/A

Virtex-4 Block RAM Primitive RAMB16 True dual port RAMB16 True dual port RAMB16 Simple dual port RAMB16 Simple dual port CASC of two RAMB16s 32k Depth 1k to 16k 512 512 Port Width R/W

1, 2, 4, 9, 18 RAMB18 36/36 36/36 Variable N/A RAMB18

Simple dual port

1, 2, 4, 9, 18 RAMB36 N/A 36/36 N/A RAMB36 RAMB36 Simple dual port Use closest RAMB36 True dual port RAMB36

Use closest RAMB18 True dual-port N/A

N/A

N/A

32k

Built-in FIFO Support

Many FPGA designs use block RAMs to implement FIFOs. In the Virtex-5 architecture, dedicated logic in the block RAM enables users to easily implement synchronous or multirate (asynchronous) FIFOs. This eliminates the need for additional CLB logic for counter, comparator, or status flag generation, and uses just one block RAM resource per FIFO. Both standard and first-word fall-through (FWFT) modes are supported. In the Virtex-5 architecture, the FIFO can be configured as a 18 Kb or 36 Kb memory. For the 18 Kb mode, the supported configurations are 4K x 4, 2K x 9, 1K x 18, and 512 x 36. The supported configurations for the 36 Kb FIFO are 8K x 4, 4K x 9, 2K x 18, 1K x 36, and 512 x 72. The block RAM can be configured as first-in/first-out (FIFO) memory with common or independent read and write clocks. Port A of the block RAM is used as a FIFO read port, and Port B is a FIFO write port. Data is read from the FIFO on the rising edge of read clock and written to the FIFO on the rising edge of write clock. Independent read and write port width selection is not supported in FIFO mode without the aid of external CLB logic.

Multirate FIFO
The multirate FIFO offers a very simple user interface. The design relies on free-running write and read clocks, of identical or different frequencies up to the specified maximum frequency limit. The design avoids any ambiguity, glitch, or metastable problems, even when the two frequencies are completely unrelated. The write operation is synchronous, writing the data word available at DI into the FIFO whenever WREN is active a set-up time before the rising WRCLK edge. The read operation is also synchronous, presenting the next data word at DO whenever the RDEN is active one set-up time before the rising RDCLK edge.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

139

Chapter 4: Block RAM

Data flow control is automatic; the user need not be concerned about the block RAM addressing sequence, although WRCOUNT and RDCOUNT are also brought out, if needed for special applications. The user must, however, observe the FULL and EMPTY flags, and stop writing when FULL is High, and stop reading when EMPTY is High. If these rules are violated, an active WREN while FULL is High will activate the WRERR flag, and an active RDEN while EMPTY is High will activate the RDERR flag. In either violation, the FIFO content will, however, be preserved, and the address counters will stay valid. Programmable ALMOSTFULL and ALMOSTEMPTY flags are brought out to give the user an early warning when the FIFO is approaching its limits. Both these flag values can be set by configuration to (almost) anywhere in the FIFO address range. Two operating modes affect the reading of the first word after the FIFO is emptied: In standard mode, the first word written into an empty FIFO will appear at DO after the user has activated RDEN. The user must pull the data out of the FIFO. In FWFT mode, the first word written into an empty FIFO will automatically appear at DO without the user activating RDEN. The next RDEN will then pull the subsequent data word onto DO. Standard and FWFT mode differ only in the reading of the first word entry after the FIFO is empty.

Use the EN_SYN = FALSE setting in the following cases: when the clocks are asynchronous when the frequencies of the two clocks are the same but the phase is different when one frequency is a multiple of the other.

Synchronous FIFO
Virtex-4 FPGA designs used the same FIFO logic for multirate and synchronous FIFOs, thus flag latency in synchronous FIFOs can vary. By setting the EN_SYN attribute to TRUE when using Virtex-5 FPGA synchronous FIFOs, any clock cycle latency when asserting or deasserting flags is eliminated. First-word fall-through (FWFT) mode is only supported in the multirate FIFO (EN_SYN = FALSE). Table 4-13 shows the FIFO capacity in the two modes.

140

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Built-in FIFO Support

Table 4-13:

FIFO Capacity
Standard Mode FWFT Mode 18 Kb FIFO 4k + 2 entries by 4 bits 2k + 2 entries by 9 bits 1k + 2 entries by 18 bits 512 + 2 entries by 36 bits 36 Kb FIFO 8k + 2 entries by 4 bits 4k + 2 entries by 9 bits 2k + 2 entries by 18 bits 1k + 2 entries by 36 bits 512 + 2 entries by 72 bits

18 Kb FIFO 4k + 1 entries by 4 bits 2k + 1 entries by 9 bits 1k + 1 entries by 18 bits 512 + 1 entries by 36 bits

36 Kb FIFO 8k + 1 entries by 4 bits 4k + 1 entries by 9 bits 2k + 1 entries by 18 bits 1k + 1 entries by 36 bits 512 + 1 entries by 72 bits

Synchronous FIFO Implementations

Table 4-14 outlines varied implementations of synchronous FIFOs. Figure 4-16 shows the timing differences. Table 4-14: Comparison of Synchronous FIFO Implementations
Advantages No flag uncertainty Faster clock-to-out signals, no flag uncertainty Faster clock-to-out signals. Similar to a Virtex-4 FIFO. Disadvantages Longer clock-to-out signals Data Latency increased by one. Behaves like a synchronous FIFO with an extra data output pipeline register Falling-edge flag uncertainty. Rising-edge guaranteed on FULL and EMPTY

Synchronous FIFO Implementations EN_SYN = TRUE, DO_REG = 0 EN_SYN = TRUE, DO_REG = 1

EN_SYN = FALSE, DO_REG = 1 RDCLK = WRCLK

X-Ref Target - Figure 4-16

rdclk

rden DO EN_SYN = TRUE DO_REG = 0 DO EN_SYN = TRUE DO_REG = 1 DO EN_SYN = FALSE DO_REG = 1
ug190_c4_x1_071007

TCKO = 1.9ns

Figure 4-16:

Synchronous FIFO Data Timing Diagram

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

141

Chapter 4: Block RAM

FIFO Architecture: a Top-Level View

Figure 4-17 shows a top-level view of the Virtex-5 FIFO architecture. The read pointer, write pointer, and status flag logic are dedicated for FIFO use only.
X-Ref Target - Figure 4-17

WRCOUNT

waddr

raddr

RDCOUNT

Write Pointer

Block RAM
mem_wen

Read Pointer

mem_ren

oe

DIN/DINP WRCLK WREN RST

DO/DOP RDCLK RDEN

Status Flag Logic

WRERR RDERR ALMOSTEMPTY ALMOSTFULL EMPTY FULL

ug190_4_27_061906

Figure 4-17:

Top-Level View of FIFO in Block RAM

FIFO Primitives
Figure 4-18 shows the FIFO36 primitive.
X-Ref Target - Figure 4-18

FIFO36 DI[31:0] DIP[3:0] RDEN RDCLK WREN WRCLK RST DO[31:0] DOP[3:0] WRCOUNT[12:0] RDCOUNT[12:0] FULL EMPTY ALMOSTFULL ALMOSTEMPTY RDERR WRERR
ug190_4_15_021107

Figure 4-18:

FIFO36 Primitive

142

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

FIFO Port Descriptions

Figure 4-19 shows the FIFO18 primitive.

X-Ref Target - Figure 4-19

FIFO18 DI[15:0] DIP[1:0] RDEN RDCLK WREN WRCLK RST DO[15:0] DOP[1:0] WRCOUNT[11:0] RDCOUNT[11:0] FULL EMPTY ALMOSTFULL ALMOSTEMPTY RDERR WRERR
ug190_4_15_040606

Figure 4-19:

FIFO18 Primitive

FIFO Port Descriptions

Table 4-15 lists the FIFO I/O port names and descriptions. Table 4-15: FIFO I/O Port Names and Descriptions
Direction Input Input Input Input Input Input Input Output Output Output Output Data input. Parity-bit input. Write enable. When WREN = 1, data will be written to memory. When WREN = 0, write is disabled. Clock for write domain operation. Read enable. When RDEN = 1, data will be read to output register. When RDEN = 0, read is disabled. Clock for read domain operation. Asynchronous reset of all FIFO functions, flags, and pointers. RESET must be asserted for three clock cycles. Data output, synchronous to RDCLK. Parity-bit output, synchronous to RDCLK. All entries in FIFO memory are filled. No additional writes are accepted. Synchronous to WRCLK. Almost all entries in FIFO memory have been filled. Synchronous to WRCLK. The offset for this flag is user configurable. See Table 4-16 for the clock latency for flag deassertion. FIFO is empty. No additional reads are accepted. Synchronous to RDCLK. Description Port Name DI DIP WREN WRCLK RDEN RDCLK RESET DO DOP FULL ALMOSTFULL

EMPTY

Output

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

143

Chapter 4: Block RAM

Table 4-15:

FIFO I/O Port Names and Descriptions (Continued)

Direction Output Description Almost all valid entries in FIFO have been read. Synchronous with RDCLK. The offset for this flag is user configurable. See Table 4-16 for the clock latency for flag deassertion. The FIFO data read pointer. It is synchronous with RDCLK. The value will wrap around if the maximum read pointer value has been reached. The FIFO data write pointer. It is synchronous with WRCLK. The value will wrap around if the maximum write pointer value has been reached. When the FIFO is full, any additional write operation generates an error flag. Synchronous with WRCLK. When the FIFO is empty, any additional read operation generates an error flag. Synchronous with RDCLK.

Port Name ALMOSTEMPTY

RDCOUNT

Output

WRCOUNT

Output

WRERR RDERR

Output Output

FIFO Operations
Reset
Reset is an asynchronous signal for both multirate and synchronous FIFO. Reset must be asserted for three cycles to reset all read and write address counters and initialize flags after power up. Reset does not clear the memory, nor does it clear the output register. When reset is asserted High, EMPTY and ALMOST_EMPTY will be set to 1, FULL and ALMOST_FULL will be reset to 0. The reset signal must be High for at least three read clock and write clock cycles to ensure all internal states are reset to the correct values. During RESET, RDEN and WREN must be held Low.

Operating Mode
There are two operating modes in FIFO functions. They differ only in output behavior immediately after the first word is written to a previously empty FIFO.

Standard Mode
After the first word is written into an empty FIFO, the Empty flag deasserts synchronously with RDCLK. After Empty is deasserted Low and RDEN is asserted, the first word will appear at DO on the rising edge of RDCLK.

First Word Fall Through (FWFT) Mode

After the first word is written into an empty FIFO, this word automatically appears at DO before RDEN is asserted. Subsequent Read operations require Empty to be Low and RDEN to be High. Figure 4-20 illustrates the difference between standard mode and FWFT mode.

144

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

FIFO Operations

X-Ref Target - Figure 4-20

RDCLK RDEN EMPTY DO (Standard) DO (FWFT) Previous Data W1 W1 W2 W2 W3

ug190_4_17_032506

W3

Figure 4-20:

Read Cycle Timing (Standard and FWFT Modes)

Status Flags
Table 4-16 shows the number of clock cycles to assert or deassert each flag of a multirate FIFO. Synchronous FIFOs do not have a clock cycle latency when asserting or deasserting flags. Due to the asynchronous nature of the clocks, the simulation model only reflects the deassertion latency cycles listed. Table 4-16: Multirate FIFO Flag Assertion and Deassertion Latency
Write/Read Cycle Latency(1) Status Flag Assertion Standard EMPTY(2) FULL(2) ALMOST EMPTY(3) 0 0 1 1 0 0 FWFT 0 0 1 1 0 0 Deassertion Standard 3 3 3 3 0 0 FWFT 4 3 3 3 0 0

ALMOST FULL(3) READ ERROR WRITE ERROR

Notes:

1. Latency is with respect to RDCLK and WRCLK. 2. Depending on the offset between read and write clock edges, the Empty and Full flags can deassert one cycle later. 3. Depending on the offset between read and write clock edges, the Almost Empty and Almost Full flags can deassert one cycle later.

Empty Flag
The Empty flag is synchronous with RDCLK, and is asserted when the last entry in the FIFO is read. When there are no more valid entries in the FIFO queue, the read pointer will be frozen. The Empty flag is deasserted after three (in standard mode) or four (in FWFT mode) read clocks after new data is written into the FIFO. The empty flag is used in the read clock domain. The rising edge of EMPTY is inherently synchronous with RDCLK. The empty condition can only be terminated by WRCLK, usually asynchronous to RDCLK. The falling edge of EMPTY must, therefore, artificially be moved onto the RDCLK time domain. Since the two clocks have an unknown phase

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

145

Chapter 4: Block RAM

relationship, it takes several cascaded flip-flops to guarantee that such a move does not cause glitches or metastable problems. The falling edge of EMPTY is thus delayed by several RDCLK periods after the first write into the previously empty FIFO. This delay guarantees proper operation under all circumstances, and causes an insignificant loss of performance after the FIFO had gone empty.

Almost Empty Flag

The Almost Empty flag is set when the FIFO contains the number of entries specified by the ALMOST_EMPTY_OFFSET value or fewer entries. The Almost Empty flag warns the user to stop reading. It deasserts when the number of entries in the FIFO is greater than the ALMOST_EMPTY_OFFSET value plus one. Assertion and deassertion is synchronous to RDCLK. Flag latency is described in Table 4-16. When a Virtex-5 FPGA FIFO is instantiated in FWFT mode, ALMOST_EMPTY_OFFSET must be set to a value that satisfies Equation 4-1. WRCLK frequency ALMOST_EMPTY_OFFSET 4 Roundup ------------------------------------------------- RDCLK frequency Equation 4-1

For example, if the read frequency is 1/2 the write frequency, ALMOST_EMPTY_OFFSET needs to be greater than or equal to 8. This equation also means that any time the read frequency is greater than or equal to the write frequency, any legal value of ALMOST_EMPTY_OFFSET works.

Read Error Flag

Once the Empty flag has been asserted, any further read attempts will not increment the read address pointer but will trigger the Read Error flag. The Read Error flag is deasserted when Read Enable or Empty is deasserted Low. The Read Error flag is synchronous to RDCLK.

Full Flag
The Full flag is synchronous with WRCLK, and is asserted when there are no more available entries in the FIFO queue. When the FIFO is full, the write pointer will be frozen. The Virtex-5 FPGA Full flag is deasserted three write clock cycles after two subsequent read operations. In Virtex-4 FPGA designs a Full flag is asserted one write clock cycle after the last write, and is deasserted three write clock cycle after the first read.

Write Error Flag

Once the Full flag has been asserted, any further write attempts will not increment the write address pointer but will trigger the Write Error flag. The Write Error flag is deasserted when Write Enable or Full is deasserted Low. This signal is synchronous to WRCLK.

Almost Full Flag

The Almost Full flag is set when the FIFO has the number of available empty spaces specified by the ALMOST_FULL_OFFSET value or fewer spaces. The Almost Full flag warns the user to stop writing. It deasserts when the number of empty spaces in the FIFO is greater than the ALMOST_FULL_OFFSET value plus one. Assertion and deassertion is synchronous to WRCLK. Flag latency is described in Table 4-16.

146

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

FIFO Attributes

FIFO Attributes
Table 4-17 lists the FIFO18 and FIFO36 attributes. The size of the multirate FIFO can be configured by setting the DATA_WIDTH attribute. The FIFO VHDL and Verilog Templates section has examples for setting the attributes. Table 4-17: FIFO18 and FIFO36 Attributes
Type 13-bit HEX Values See Table 4-19 Default Notes Setting determines the difference between FULL and ALMOSTFULL conditions. Must be set using hexadecimal notation. Setting determines the difference between EMPTY and ALMOSTEMPTY conditions. Must be set using hexadecimal notation. FALSE If TRUE, the first word written into the empty FIFO appears at the FIFO output without RDEN asserted. For multirate (asynchronous) FIFO, must be set to 1. For synchronous FIFO, DO_REG must be set to 0 for flags and data to follow a standard synchronous FIFO operation. When DO_REG is set to 1, effectively a pipeline register is added to the output of the synchronous FIFO. Data then has a one clock cycle latency. However, the clock-to-out timing is improved. DATA_WIDTH LOC(1, 2) EN_SYN Integer String Boolean 4, 9, 18, 36, 72 Valid FIFO18 or FIFO36 location FALSE, TRUE FALSE 4 Sets the location of the FIFO18 or FIFO36. When set to TRUE, ties WRCLK and RDCLK together. When set to TRUE, FWFT must be FALSE. When set to FALSE, DO_REG must be 1.
Notes:
1. If FIFO18 is constrained to FIFO18_X#Y#, then RAMB18 can not be constrained to RAMB18_X#Y# since the same location would be used. 2. If a FIFO18 is constrained to FIFO18_X#Y#, corresponding to the lower RAMB18_X#Y# of the RAMB18 pair, a RAMB18 can be constrained to the upper RAMB18_X#Y# of the pair.

Attribute Name ALMOST_FULL_OFFSET

ALMOST_EMPTY_OFFSET

13-bit HEX

See Table 4-19

FIRST_WORD_FALL_THROUGH

Boolean

FALSE, TRUE 0, 1

DO_REG

1-bit Binary

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

147

Chapter 4: Block RAM

FIFO Almost Full/Empty Flag Offset Range

The offset ranges for Almost Empty and Almost Full are listed in Table 4-19. Table 4-18: FIFO Data Depth
Block RAM Memory 8192 4096 2048 1024 512 FIFO Capacity Standard 8193 4097 2049 1025 513 FWFT 8194 4098 2050 1026 514

Data Width FIFO18 FIFO36 x4 x4 x9 x18 x36

Notes:

x9 x18 x36 x72

1. ALMOST_EMPTY_OFFSET and ALMOST_FULL_OFFSET for any design must be less than the total FIFO depth.

Table 4-19:

FIFO Almost Full/Empty Flag Offset Range

ALMOST_EMPTY_OFFSET ALMOST_FULL_OFFSET Min Max

Data Width Standard FIFO18 FIFO36 Min Max

FWFT(1) Min Max

Multirate (Asynchronous) EN_SYN=FALSE x4 x4 x9 x18 x36 x9 x18 x36 x72 5 5 5 5 5 8187 4091 2043 1019 507 6 6 6 6 6 8188 4092 2044 1020 508 4 4 4 4 4 8187 4091 2043 1019 507

Synchronous mode EN_SYN=TRUE x4 x4 x9 x18 x36

Notes:
1. For limitations under certain conditions, refer to Equation 4-1 on page 146.

1 1 1 1 1

8190 4094 2046 1022 510

1 1 1 1 1

8190 4094 2046 1022 510

x9 x18 x36 x72

The Almost Full and Almost Empty offsets are usually set to a small value of less than 10 to provide a warning that the FIFO is about to reach its limits. Since the full capacity of any FIFO is normally not critical, most applications use the ALMOST_FULL flag not only as a warning but also as a signal to stop writing.

148

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

FIFO VHDL and Verilog Templates

Similarly, the ALMOST_EMPTY flag can be used to stop reading. However, this would make it impossible to read the very last entries remaining in the FIFO. The user can ignore the Almost Empty signal and continue to read until EMPTY is asserted. The Almost Full and Almost Empty offsets can also be used in unstoppable block transfer applications to signal that a complete block of data can be written or read. When setting the offset ranges in the design tools, use hexadecimal notation.

FIFO VHDL and Verilog Templates

VHDL and Verilog templates are available in the Libraries Guide.

FIFO Timing Models and Parameters

Table 4-20 shows the FIFO parameters. Table 4-20: FIFO Timing Parameters
Function Control Signal Description

Parameter

Setup and Hold Relative to Clock (CLK) TRXCK = Setup time (before clock edge) TRCKX = Hold time (after clock edge) TRDCK_DI/ TRCKD_DI(4) TRCCK_RDEN/ TRCKC_RDEN(5) TRCCK_WREN/ TRCKC_WREN(5) Clock to Out Delays TRCKO_DO(1) Clock to data output DO Time after RDCLK that the output data is stable at the DO outputs of the FIFO. The synchronous FIFO with DO_REG = 0 is different than in multirate mode. Time after RDCLK that the Almost Empty signal is stable at the ALMOSTEMPTY outputs of the FIFO. Time after WRCLK that the Almost Full signal is stable at the ALMOSTFULL outputs of the FIFO. Time after RDCLK that the Empty signal is stable at the EMPTY outputs of the FIFO. Time after WRCLK that the Full signal is stable at the FULL outputs of the FIFO. Time after RDCLK that the Read Error signal is stable at the RDERR outputs of the FIFO. Time after WRCLK that the Write Error signal is stable at the WRERR outputs of the FIFO. Data inputs Read enable Write enable DI RDEN WREN Time before/after WRCLK that D1 must be stable. Time before/after RDCLK that RDEN must be stable. Time before/after WRCLK that WREN must be stable.

TRCKO_AEMPTY(2) TRCKO_AFULL(2) TRCKO_EMPTY(2) TRCKO_FULL(2) TRCKO_RDERR(2) TRCKO_WRERR(2)

Clock to almost empty output Clock to almost full output Clock to empty output Clock to full output Clock to read error output Clock to write error output

AEMPTY AFULL EMPTY FULL RDERR WRERR

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

149

Chapter 4: Block RAM

Table 4-20:

FIFO Timing Parameters (Continued)

Function Clock to read pointer output Clock to write pointer output Control Signal RDCOUNT WRCOUNT Description Time after RDCLK that the Read pointer signal is stable at the RDCOUNT outputs of the FIFO. Time after WRCLK that the Write pointer signal is stable at the WRCOUNT outputs of the FIFO.

Parameter TRCKO_RDCOUNT(3) TRCKO_WRCOUNT(3) Reset to Out TRCO_AEMPTY TRCO_AFULL TRCO_EMPTY TRCO_FULL TRCO_RDERR TRCO_WRERR TRCO_RDCOUNT TRCO_WRCOUNT
Notes:

Reset to almost empty output Reset to almost full output Reset to empty output Reset to full output Reset to read error output Reset to write error output Reset to read pointer output Reset to write pointer output

AEMPTY AFULL EMPTY FULL RDERR WRERR RDCOUNT WRCOUNT

Time after reset that the Almost Empty signal is stable at the ALMOSTEMPTY outputs of the FIFO. Time after reset that the Almost Full signal is stable at the ALMOSTFULL outputs of the FIFO. Time after reset that the Empty signal is stable at the EMPTY outputs of the FIFO. Time after reset that the Full signal is stable at the FULL outputs of the FIFO. Time after reset that the Read error signal is stable at the RDERR outputs of the FIFO. Time after reset that the Write error signal is stable at the WRERR outputs of the FIFO. Time after reset that the Read pointer signal is stable at the RDCOUNT outputs of the FIFO. Time after reset that the Write pointer signal is stable at the WRCOUNT outputs of the FIFO.

1. TRCKO_DO includes parity output (TRCKO_DOP). 2. In the Virtex-5 FPGA Data Sheet, TRCKO_AEMPTY, TRCKO_AFULL, TRCKO_EMPTY, TRCKO_FULL, TRCKO_RDERR, TRCKO_WRERR are combined into TRCKO_FLAGS. 3. In the Virtex-5 FPGA Data Sheet, TRCKO_RDCOUNT and TRCKO_WRCOUNT are combined into TRCKO_POINTERS. 4. TRCDCK_DI includes parity inputs (TRCDCK_DIP). 5. In the Virtex-5 FPGA Data Sheet, WRITE and READ enables are combined into TRCCK_EN.

FIFO Timing Characteristics

The various timing parameters in the FIFO are described in this section. There is also additional data on FIFO functionality. The timing diagrams describe the behavior in these six cases. Case 1: Writing to an Empty FIFO Case 2: Writing to a Full or Almost Full FIFO Case 3: Reading From a Full FIFO Case 4: Reading From An Empty or Almost Empty FIFO Case 5: Resetting All Flags Case 6: Simultaneous Read and Write for Multirate FIFO

150

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

FIFO Timing Models and Parameters

Case 1: Writing to an Empty FIFO

Prior to the operations performed in Figure 4-21, the FIFO is completely empty.
X-Ref Target - Figure 4-21

1 WRCLK TFCCK_WREN WREN TFDCK_DI DI RDCLK RDEN 00 01 02

2 3

TFDCK_DI 03 04 05 06

TFCKO_DO DO EMPTY TFCKO_AEMPTY AEMPTY

ug190_4_18_032506

00 TFCKO_EMPTY

Figure 4-21: Writing to an Empty FIFO in FWFT Mode

Clock Event 1 and Clock Event 3: Write Operation and Deassertion of EMPTY Signal
During a write operation to an empty FIFO, the content of the FIFO at the first address is replaced by the data value on the DI pins. Three read-clock cycles later (four read-clock cycles for FWFT mode), the EMPTY pin is deasserted when the FIFO is no longer empty. The RDCOUNT also increments by one due to an internal read preloading the data to the output registers. For the example in Figure 4-21, the timing diagram is drawn to reflect FWFT mode. Clock event 1 is with respect to the write-clock, while clock event 3 is with respect to the readclock. Clock event 3 appears four read-clock cycles after clock event 1. At time TFDCK_DI, before clock event 1 (WRCLK), data 00 becomes valid at the DI inputs of the FIFO. At time TFCCK_WREN, before clock event 1 (WRCLK), write enable becomes valid at the WREN input of the FIFO. At time TFCKO_DO, after clock event 3 (RDCLK), data 00 becomes valid at the DO output pins of the FIFO. In standard mode, data 00 does not appear at the DO output pins of the FIFO. At time TFCKO_EMPTY, after clock event 3 (RDCLK), EMPTY is deasserted. In standard mode, EMPTY is deasserted one read-clock earlier than clock event 3.

If the rising WRCLK edge is close to the rising RDCLK edge, EMPTY could be deasserted one RDCLK period later.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

151

Chapter 4: Block RAM

Clock Event 2 and Clock Event 4: Write Operation and Deassertion of Almost EMPTY Signal
Three read-clock cycles after the fourth data is written into the FIFO, the Almost EMPTY pin is deasserted to signify that the FIFO is not in the almost EMPTY state. For the example in Figure 4-21, the timing diagram is drawn to reflect FWFT mode. Clock event 2 is with respect to write-clock, while clock event 4 is with respect to read-clock. Clock event 4 appears three read-clock cycles after clock event 2. At time TFDCK_DI, before clock event 2 (WRCLK), data 03 becomes valid at the DI inputs of the FIFO. Write enable remains asserted at the WREN input of the FIFO. At clock event 4, DO output pins of the FIFO remains at 00 since no read has been performed. In the case of standard mode, data 00 will never appear at the DO output pins of the FIFO. At time TFCKO_AEMPTY, after clock event 4 (RDCLK), almost empty is deasserted at the AEMPTY pin. In the case of standard mode, AEMPTY deasserts in the same way as in FWFT mode.

If the rising WRCLK edge is close to the rising RDCLK edge, AEMPTY could be deasserted one RDCLK period later.

Case 2: Writing to a Full or Almost Full FIFO

Prior to the operations performed in Figure 4-22, the FIFO is almost completely full. In this example, the timing diagram reflects of both standard and FWFT modes.
X-Ref Target - Figure 4-22

1
WRCLK

TFCCK_WREN
WREN

TFCCK_WREN TFDCK_DI 02 03 04 05 TFDCK_DI 06

TFDCK_DI
DI RDCLK RDEN

00

01

TFCKO_FULL
FULL AFULL WRERR

TFCKO_WERR TFCKO_AFULL TFCKO_WERR

ug190_4_18_012605

Figure 4-22: Writing to a Full / Almost Full FIFO

152

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

FIFO Timing Models and Parameters

Clock Event 1: Write Operation and Assertion of Almost FULL Signal

During a write operation to an almost full FIFO, the Almost FULL signal is asserted. At time TFDCK_DI, before clock event 1 (WRCLK), data 00 becomes valid at the DI inputs of the FIFO. At time TFCCK_WREN, before clock event 1 (WRCLK), write enable becomes valid at the WREN input of the FIFO. At time TFCKO_AFULL, one clock cycle after clock event 1 (WRCLK), Almost Full is asserted at the AFULL output pin of the FIFO.

Clock Event 2: Write Operation, and Assertion of FULL Signal

The FULL signal pin is asserted when the FIFO is full. At time TFDCK_DI, before clock event 2 (WRCLK), data 04 becomes valid at the DI inputs of the FIFO. Write enable remains asserted at the WREN input of the FIFO. At time TFCKO_FULL, after clock event 2 (WRCLK), Full is asserted at the FULL output pin of the FIFO.

If the FIFO is full, and a read followed by a write is performed, the FULL signal remains asserted.

Clock Event 3: Write Operation and Assertion of Write Error Signal

The write error signal pin is asserted when data going into the FIFO is not written because the FIFO is in a Full state. At time TFDCK_DI, before clock event 3 (WRCLK), data 05 becomes valid at the DI inputs of the FIFO. Write enable remains asserted at the WREN input of the FIFO. At time TFCKO_WRERR, after clock event 3 (WRCLK), a write error is asserted at the WRERR output pin of the FIFO. Data 05 is not written into the FIFO.

Clock Event 4: Write Operation and Deassertion of Write Error Signal

The write error signal pin is deasserted when a user stops trying to write into a full FIFO. At time TFCCK_WREN, before clock event 4 (WRCLK), write enable is deasserted at the WREN input of the FIFO. At time TFCKO_WRERR, after clock event 4 (WRCLK), write error is deasserted at the WRERR output pin of the FIFO.

The write error signal is asserted/deasserted at every write-clock positive edge. As long as both the write enable and Full signals are true, write error will remain asserted.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

153

Chapter 4: Block RAM

Case 3: Reading From a Full FIFO

Prior to the operations performed in Figure 4-23, the FIFO is completely full.
X-Ref Target - Figure 4-23

1 WRCLK WREN RDCLK RDEN DO FULL AFULL

TFCCK_RDEN TFCKO_DO

00

01

02

03

04
TFCKO_FULL

05

06
TFCKO_AFULL

ug190_4_19_040606

Figure 4-23: Reading From a Full FIFO

Clock Event 1 and Clock Event 2: Read Operation and Deassertion of Full Signal
During a read operation on a full FIFO, the content of the FIFO at the first address is asserted at the DO output pins of the FIFO. Two RDEN operations ensure that the FIFO is no longer full, and after three WRCLK cycles the FULL pin is deasserted. The example in Figure 4-23 reflects both standard and FWFT modes. Clock event 1 and 2 are with respect to read-clock. Clock event 4 appears three write-clock cycles after clock event 2. At time TFCCK_RDEN, before clock event 1 (RDCLK), read enable becomes valid at the RDEN input of the FIFO. At time TFCKO_DO, after clock event 1 (RDCLK), data 00 becomes valid at the DO outputs of the FIFO. At time TFCKO_FULL, after clock event 4 (WRCLK), FULL is deasserted.

If the rising RDCLK edge is close to the rising WRCLK edge, FULL could be deasserted one WRCLK period later.

Clock Event 3 and Clock Event 5: Read Operation and Deassertion of Almost FULL Signal
Three write-clock cycles after the fourth data is read from the FIFO, the Almost FULL pin is deasserted to signify that the FIFO is not in the almost FULL state. The example in Figure 4-23 reflects both standard and FWFT modes. Clock event 3 is with respect to read-clock, while clock event 5 is with respect to write-clock. Clock event 5 appears three write-clock cycles after clock event 3. Read enable remains asserted at the RDEN input of the FIFO. At time TFCKO_AFULL, after clock event 5 (RDCLK), Almost FULL is deasserted at the AFULL pin.

154

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

FIFO Timing Models and Parameters

There is minimum time between a rising read-clock and write-clock edge to guarantee that AFULL will be deasserted. If this minimum is not met, the deassertion of AFULL can take an additional write clock cycle.

Case 4: Reading From An Empty or Almost Empty FIFO

Prior to the operations performed in Figure 4-24, the FIFO is almost completely empty. In this example, the timing diagram reflects standard mode. For FWFT mode, data at DO appears one read-clock cycle earlier.
X-Ref Target - Figure 4-24

1 WRCLK WREN RDCLK RDEN DO EMPTY

TFCKO_AEMPTY TFCCK_RDEN TFCKO_DO TFCKO_DO

TFCCK_RDEN

00

01

02
TFCKO_EMPTY

03

04

AEMPTY RDERR

TFCKO_RDERR TFCKO_RDERR
ug190_4_21_032506

Figure 4-24:

Reading From an Empty / Almost Empty FIFO (Standard Mode)

Clock Event 1: Read Operation and Assertion of Almost EMPTY Signal

During a read operation to an almost empty FIFO, the Almost EMPTY signal is asserted. At time TFCCK_RDEN, before clock event 1 (RDCLK), read enable becomes valid at the RDEN input of the FIFO. At time TFCKO_DO, after clock event 1 (RDCLK), data 00 becomes valid at the DO outputs of the FIFO. At time TFCKO_AEMPTY, one clock cycle after clock event 1 (RDCLK), Almost Empty is asserted at the AEMPTY output pin of the FIFO.

Clock Event 2: Read Operation and Assertion of EMPTY Signal

The EMPTY signal pin is asserted when the FIFO is empty. Read enable remains asserted at the RDEN input of the FIFO. At time TFCKO_DO, after clock event 2 (RDCLK), data 04 (last data) becomes valid at the DO outputs of the FIFO. At time TFCKO_EMPTY, after clock event 2 (RDCLK), Empty is asserted at the EMPTY output pin of the FIFO.

In the event that the FIFO is empty and a write followed by a read is performed, the EMPTY signal remains asserted.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

155

Chapter 4: Block RAM

Clock Event 3: Read Operation and Assertion of Read Error Signal

The read error signal pin is asserted when there is no data to be read because the FIFO is in an empty state. Read enable remains asserted at the RDEN input of the FIFO. At time TFCKO_RDERR, after clock event 3 (RDCLK), read error is asserted at the RDERR output pin of the FIFO. Data 04 remains unchanged at the DO outputs of the FIFO.

Clock Event 4: Read Operation and Deassertion of Read Error Signal

The read error signal pin is deasserted when a user stops trying to read from an empty FIFO. At time TFCCK_RDEN, before clock event 4 (RDCLK), read enable is deasserted at the RDEN input of the FIFO. At time TFCKO_RDERR, after clock event 4 (RDCLK), read error is deasserted at the RDERR output pin of the FIFO.

The read error signal is asserted/deasserted at every read-clock positive edge. As long as both the read enable and empty signals are true, read error will remain asserted.

Case 5: Resetting All Flags

X-Ref Target - Figure 4-25

RST WRCLK RDCLK

TFCO_EMPTY

EMPTY AEMPTY

TFCO_AEMPTY TFCO_FULL

FULL
TFCO_AFULL

AFULL
ug190_4_22_032506

Figure 4-25:

Resetting All Flags

When the reset signal is asserted, all flags are reset. At time TFCO_EMPTY, after reset (RST), empty is asserted at the EMPTY output pin of the FIFO. At time TFCO_AEMPTY, after reset (RST), almost empty is asserted at the AEMPTY output pin of the FIFO. At time TFCO_FULL, after reset (RST), full is deasserted at the FULL output pin of the FIFO. At time TFCO_AFULL, after reset (RST), almost full is deasserted at the AFULL output pin of the FIFO.

Reset is an asynchronous signal used to reset all flags. Hold the reset signal High for three read and write clock cycles to ensure that all internal states and flags are reset to the correct value.

156

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

FIFO Applications

Case 6: Simultaneous Read and Write for Multirate FIFO

Simultaneous read and write operations for an asynchronous FIFO is not deterministic when the FIFO is at the condition to assert a status flag. The FIFO logic resolves the situation (either assert or not assert the flag), the software simulation model can not reflect this behavior and mismatch can occur. When using a single clock for RDCLK and WRCLK, use the FIFO in synchronous mode (EN_SYN=TRUE).

FIFO Applications
A FIFO larger than a single Virtex-5 FPGA FIFO block can be created by: Cascading two or more FIFOs to form a deeper FIFO. Building a wider FIFO by connecting two or more FIFOs in parallel.

Cascading FIFOs to Increase Depth

Figure 4-26 shows a way of cascading N FIFO36s to increase depth. The application sets the first N1 FIFOs in FWFT mode and uses external resources to connect them together. The data latency of this application is the sum of the individual FIFO latencies. The maximum frequency is limited by the feedback path. The NOR gate is implemented using CLB logic.
X-Ref Target - Figure 4-26

N can be 2 or more; if N is 2, the middle FIFOs are not needed. If WRCLK is faster than RDCLK, then INTCLK = WRCLK If WRCLK is equal to or slower than RDCLK, then INTCLK = RDCLK ALMOST_EMPTY threshold is set in the Nth FIFO; ALMOST_FULL threshold is set in 1st FIFO.

DI<3:0> WREN WRCLK

DI<3:0> WREN RDEN WRCLK RDCLK FWFT Mode

DO<3:0> EMPTY

DI<3:0> WREN FWFT Mode

DO<3:0> EMPTY

DI<3:0> WREN

DO<3:0>

DO<3:0> ALMOST EMPTY EMPTY

ALMOSTFULL FIFO 1 FULL

RDEN FULL WRCLK RDCLK FIFO 2 ... (N1)

FULL RDEN ALMOST EMPTY WRCLK RDCLK FIFO N EMPTY

INTCLK RDEN RDCLK

ALMOST FULL FULL N x 8K x 4 FIFO

ug190_4_23_090407

Figure 4-26:

Example: Cascading Multiple FIFOs by Depth

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

157

Chapter 4: Block RAM

Connecting FIFOs in Parallel to Increase Width

As shown in Figure 4-27, the Virtex-5 FPGA FIFO36 can be connected to add width to the design. CLB logic is used to implement the AND/OR gates. All the FIFO AFULL signals must be ORed together to created the output AFULL signal and all the FIFO EMPTY signals must be ORed together to created the output EMPTY signal. The maximum frequency is limited by the logic gate feedback path.
X-Ref Target - Figure 4-27

512 x 144 FIFO

DIN<71:0> RDEN WRCLK RDCLK

DIN<71:0> WREN RDEN WRCLK RDCLK

DOUT<71:0>

DOUT<71:0>

EMPTY

EMPTY

FIFO #1

AFULL

DIN<143:72> WREN

DIN<71:0> WREN RDEN WRCLK RDCLK

DOUT<71:0>

DOUT<143:72>

EMPTY

AFULL

FIFO #2

AFULL

ug190_4_24_012706

Figure 4-27:

Example: Connecting FIFOs in Parallel to Increase Width

Built-in Error Correction

Each simple dual-port block RAM can be configured as a single 512 x 64 RAM with built in Hamming code error correction, using the extra eight bits in the 72-bit wide RAM. The operation is transparent to the user. Eight protection bits (ECCPARITY) are generated during each write operation and stored with the 64-bit data into the memory. These ECCPARITY bits are used during each read operation to correct any single-bit error, or to detect (but not correct) any double-bit error. The ECCPARITY bits are written into the memory and output to the FPGA fabric at each rising edge of the WRCLK. There are no optional output registers available on the ECCPARITY output bits. During each read operation, 72 bits of data (64 bits of data and an 8-bit parity) are read from the memory and fed into the ECC decoder. The ECC decoder generates two status outputs (SBITERR and DBITERR) that are used to indicate the three possible read results: No error, single-bit error corrected, double-bit error detected. In the standard ECC mode, the read operation does not correct the error in the memory array, it only presents corrected data on DO. To improve FMAX, optional registers controlled by the DO_REG attribute are available for data output (DO), SBITERR, and DBITERR. This ECC configuration option is available with a 36K block RAM simple dual-port primitive (RAMB36SDP) or a 36K FIFO primitive (FIFO36_72). A Virtex-4 FPGA ECC 18K block RAM mapped for a Virtex-5 FPGA design will occupy the entire RAMB36 site. FIFO36_72 supports standard ECC mode only.

158

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Built-in Error Correction

ECC Modes Overview

In the standard ECC mode (EN_ECC_READ = TRUE and EN_ECC_WRITE = TRUE), both encoder and decoder are enabled. During write, 64-bit data and 8-bit ECC generated parity are stored in the array. The external parity bits are ignored. During read, the 72-bit decoded data and parity are read out. The encoder and decoder can be accessed separately for external use in RAMB36SDP. To use the encoder by itself, send the data in through the DI port and sample the ECCPARITY output port. To use the decoder by itself, disable the encoder, write the data into the block RAM and read the corrected data and status bits out of the block RAM. See Block RAM (RAMB36SDP) Attributes. To use the decoder in ECC decode-only mode, set EN_ECC_WRITE = FALSE and EN_ECC_READ = TRUE. The encoder can be used in two ways: To use the encoder in standard ECC mode, set (EN_ECC_WRITE = TRUE and EN_ECC_READ = TRUE). In this mode, the DI setup time is smaller but the clock-toout for ECCPARITY is larger. To use the encoder-only mode, set (EN_ECC_WRITE = TRUE and EN_ECC_READ = FALSE). In this mode, the DI setup time is larger but the clock-toout for ECCPARITY is smaller.

The functionality of the block RAM when using the ECC mode is described as follows: The block RAM ports still have independent address, clocks, and enable inputs, but one port is a dedicated write port, and the other is a dedicated read port (simple dualport). DO represents the read data after correction. DO stays valid until the next active read operation. Simultaneous decoding and encoding, even with asynchronous clocks, is allowed, but requires careful clock timing if read and write addresses are identical. The NO_CHANGE or WRITE_FIRST modes of the normal block RAM operation are not applicable to the ECC configuration.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

159

Chapter 4: Block RAM

Top-Level View of the Block RAM ECC Architecture

Figure 4-28 shows the top-level view of a Virtex-5 FPGA block RAM in ECC mode.
X-Ref Target - Figure 4-28

WRADDR[8:0] RDADDR[8:0] DIP[7:0] ECCPARITY[7:0]

8

wraddr rdaddr
8 0 1 8

9 9 8

DI[63:0]

64

64-bit ECC Encode

EN_ECC_WRITE

Data In

64

DO_REG EN_ECC_READ

Block RAM 512 x 72

DO[63:0]

0 1
Q D

64

0 1

64 64

Data Out

64

DO_REG

DBITERR

0 1
Q D

0 1 1

DO_REG

SBITERR

0 1
Q D

Decode and Correct

1 0 1 1

DO_REG

DOP[7:0]

0 1
Q D

1 0

8 8

Parity Out

8
UG190_c4_25_022609

EN_ECC_READ

Figure 4-28:

Top-Level View of Block RAM ECC

160

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Built-in Error Correction

Block RAM and FIFO ECC Primitive

Figure 4-29 shows the block RAM (RAMB36SDP) ECC primitive. Figure 4-30 shows the FIFO36_72 ECC primitive. The FIFO36_72 only supports standard mode.
X-Ref Target - Figure 4-29

RAMB36SDP
DI[63:0] DIP[7:0] (Decode Only) WRADDR[8:0] RDADDR[8:0] WREN RDEN SSR WRCLK RDCLK
ug190_4_26_022207

DO[63:0] DOP[7:0]

ECCPARITY[7:0] (Standard or Encode Only) SBITERR DBITERR

Figure 4-29:
X-Ref Target - Figure 4-30

RAMB36SDP: Block RAM ECC Primitive

FIFO36_72
DI[63:0] DIP[7:0] DO[63:0] DOP[7:0] ECCPARITY[7:0] SBITERR DBITERR WREN RDEN RST WRCLK RDCLK FULL EMPTY ALMOSTFULL ALMOSTEMPTY WRERR RDERR WRCOUNT[8:0] RDCOUNT[8:0]
ug190_4_34_022207

Figure 4-30: FIFO36_72: FIFO ECC Primitive

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

161

Chapter 4: Block RAM

Block RAM and FIFO ECC Port Descriptions

Table 4-21 lists and describes the block RAM ECC I/O port names. Table 4-21: Block RAM ECC Port Names and Descriptions
Direction Input Input Input Input Input Input Input Input Input Output Output Output Output Output Data input bus. Data input parity bus. Used in decode-only mode to input the precalculated ECC parity bits. Write address bus. Read address bus. Write enable. When WREN = 1, data will be written into memory. When WREN = 0, write is disabled Read enable. When RDEN = 1, data will be read from memory. When RDEN = 0, read is disabled. Not supported when using the block RAM ECC primitive. Always connect to GND. Clock for write operations. Clock for read operations. Data output bus. Data output parity bus. Used in encode-only mode to output the stored ECC parity bits. Single-bit error status. Double-bit error status. ECC encoder output bus. Signal Description

Port Name DI[63:0] DIP[7:0] WRADDR[8:0] RDADDR[8:0] WREN RDEN SSR WRCLK RDCLK DO[63:0] DOP[7:0] SBITERR(1) DBITERR(1) ECCPARITY[7:0]
Notes:

1. Hamming code implemented in the block RAM ECC logic detects one of three conditions: no detectable error, single-bit error detected and corrected on DO (but not corrected in the memory), and double-bit error detected without correction. SBITERR and DBITERR indicate these three conditions.

162

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Built-in Error Correction

Table 4-22 lists and describes the FIFO ECC I/O port names. Table 4-22: FIFO ECC Port Names and Descriptions
Direction Input Input Input Input Input Input Input Output Output Output Output Output Output Output Output Output Output Output Output Output Data input bus. Data input parity bus. Not used when standard mode is used. Write enable. When WREN = 1, data will be written into memory. When WREN = 0, write is disabled Read enable. When RDEN = 1, data will be read from memory. When RDEN = 0, read is disabled. Asynchronous reset of FIFO counter and flags. Reset must be asserted for three clock cycles. Reset does not affect DO or ECC signals. Clock for write operations. Clock for read operations. Data output bus. Data output parity bus. Single-bit error status. Double-bit error status. ECC encoder output bus. FIFO FULL flag. FIFO ALMOSTFULL flag. FIFO EMPTY flag. FIFO ALMOSTEMPTY flag. The FIFO data read pointer. The FIFO data write pointer. When the FIFO is full, any additional write operation generates an error flag. When the FIFO is empty, any additional read operation generates an error flag. Signal Description

Port Name DI[63:0] DIP[7:0] WREN RDEN RST WRCLK RDCLK DO[63:0] DOP[7:0] SBITERR(1) DBITERR(1) ECCPARITY[7:0] FULL ALMOSTFULL EMPTY ALMOSTEMPTY RDCOUNT WRCOUNT WRERR RDERR
Notes:

1. Hamming code implemented in the FIFO ECC logic detects one of three conditions: no detectable error, single-bit error detected and corrected on DO (but not corrected in the memory), and double-bit error detected without correction. SBITERR and DBITERR indicate these three conditions.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

163

Chapter 4: Block RAM

Block RAM and FIFO ECC Attributes

In addition to the built-in registers in the decode and correct logic, the RAMB36SDP primitive allows the use of optional pipeline registers controlled by the DO_REG attribute to produce higher performance with one additional latency. Table 4-23 and Table 4-24 list the block RAM and FIFO ECC attributes. Table 4-23: Block RAM (RAMB36SDP) Attributes
Type Boolean Boolean 1-bit Binary Values TRUE, FALSE TRUE, FALSE 0, 1 Default FALSE FALSE 0 Notes Set to TRUE to enable ECC encoder. Set to TRUE to enable ECC decoder. Enables register mode or latch mode.

Attribute Name EN_ECC_WRITE EN_ECC_READ DO_REG

Table 4-24:

FIFO (FIFO36_72) Attributes

Type Values Default FALSE FALSE 1 Notes Both attributes must be set to TRUE to enable ECC functionality in a FIFO36_72. Enables register mode or latch mode. See Table 4-17 for details on multirate and synchronous FIFOs. When set to TRUE, ties WRCLK and RDCLK together. Boolean TRUE, FALSE FALSE When set to TRUE, FWFT must be FALSE. When set to FALSE, DO_REG must be 1.

Attribute Name EN_ECC_WRITE EN_ECC_READ DO_REG

Boolean TRUE, FALSE Boolean TRUE, FALSE 1-bit Binary 0, 1

EN_SYN

ALMOST_EMPTY_OFFSET 9-bit Hex ALMOST_FULL_OFFSET 9-bit Hex FIRST_WORD_FALL_THROUGH

Setting determines the difference between EMPTY and ALMOST_EMPTY See Table 4-19 See Table 4-19 conditions. Must be set using hexadecimal notation. Setting determines the difference between FULL and ALMOST_FULL See Table 4-19 See Table 4-19 conditions. Must be set using hexadecimal notation. When set to TRUE, the first word written into the empty FIFO36_72 appears at the FIFO36_72 output without RDEN asserted.

Boolean TRUE, FALSE

FALSE

164

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Built-in Error Correction

ECC Modes of Operation

There are three types of ECC operation: standard, encode only, and decode only. The standard ECC mode uses both the encoder and decoder. The various modes of ECC operation in both block RAM and FIFO are shown in Figure 4-31 and Figure 4-32. The block RAM WRADDR and RDADDR address inputs are supplied by the user. The FIFO WRADDR and RDADDR addresses are generated internally from the write counter and read counter.
X-Ref Target - Figure 4-31

T1W
WRCLK WREN
TRCCK_EN

T2W

T3W

T4W

T5W

WRADDR[8:0] DI[63:0] DIP[7:0] (Decode Only Mode) ECCPARITY[7:0]

a
TRCCK_ADDR

b B PB PA PB

c C PC PC

d D PD PD

A
TRCCK_DI_ECC

PA

TRCKO_ECC_PARITY
ug190_4_32_022307

Figure 4-31:
X-Ref Target - Figure 4-32

ECC Write Operation

T2R T3R T4R

T1R
RDCLK RDEN
TRCCK_EN

RDADDR[8:0] DO[63:0] (Latch Mode) DOP[7:0] (Latch Mode) SBITERR (Latch Mode) DBITERR (Latch Mode) DO[63:0] (Register Mode) DOP[7:0] (Register Mode) SBITERR (Register Mode) DBITERR (Register Mode)

a
TRCCK_ADDR

b A
TRCKO_DO (Latch Mode)

c B C

PA
Single Bit Error

PB

PC

TRCKO_ECC_SBITERR (Latch Mode) Double Bit Error TRCKO_ECC_DBITERR (Latch Mode)

A
TRCKO_DO (Register Mode)

PA
Single Bit Error

PB

PC

TRCKO_ECC_SBITERR (Register Mode) Double Bit Error TRCKO_ECC_DBITERR (Register Mode)

ug190_4_33_020707

Figure 4-32: ECC Read Operation

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

165

Chapter 4: Block RAM

Standard ECC
Set by Attributes
EN_ECC_READ = TRUE EN_ECC_WRITE = TRUE

Standard ECC Write

At time T1W, DI[63:0] = A is written into memory location a. The corresponding 8 bits of ECC parity PA (hex) are generated internally, appended to the 64 data bits, and written into the memory. Immediately after the write, the parity value PA appears at output ECCPARITY[7:0]. Since ECC parity is generated internally, DIP[7:0] pins are not used. Similarly, at time T2W and T3W, DI[63:0] = B and C, together with their corresponding parity bits PB (hex) and PC (hex) are written into memory locations b and c. PB and PC appear at output ECCPARITY[7:0] shortly after T2W and T3W.

Standard ECC Read

At time T1R, the 72-bit memory content, consisting 64 bits of data A and 8 bits of parity PA (hex), of address location a is read and decoded internally. If there is no error, the original data and parity are output at DO[63:0] and DOP[7:0]. If there is a single-bit error in either the data or the parity, the error is corrected, and SBITERR is High. If there is a double-bit error in the data and parity, the error is not corrected. The original data and parity is output and DBITERR is High. If attribute DO_REG is set to 0, DO[63:0] = A and DOP[7:0] = PA shortly after T1R. Similarly, at time T2R and T3R, the memory content at address locations b and c are read and decoded at DO[63:0] and DOP[7:0]. SBITERR/DBITERR outputs can also switch after T1R if a single or double-bit error is detected on dataset A. Figure 4-32 shows a single-bit error (SBITERR) being detected on data A in latch mode after clock edge T1R and a doublebit error (DBITERR) being detected on data B in latch mode after clock edge T2R. If attribute DO_REG is set to 1, DO[63:0] = A and DOP[7:0] = PA shortly after T2R. Similarly, at time T3R and T4R, the memory content at address locations b and c are read and decoded at DO[63:0] and DOP[7:0]. SBITERR/DBITERR outputs may also switch after T2R if a single or double-bit error is detected on dataset A. Figure 4-32 shows a single-bit error (SBITERR) being detected on data A in register mode after clock edge T2R and a double-bit error (DBITERR) being detected on data B in register mode after clock edge T3R. In ECC mode, the encode-only port and the decode-only port operate independently of each other.

ECC Encode-Only
Set by Attributes
EN_ECC_READ = FALSE EN_ECC_WRITE = TRUE

ECC Encode-Only Write

At time T1W, DI[63:0] = A is written into memory location a. The corresponding 8 bits of ECC parity PA (hex) are generated internally, appended to the 64 data bits, and written into the memory. Immediately after the write, the parity value PA appears at output ECCPARITY[7:0]. Since ECC parity is generated internally, DIP[7:0] pins are not used.

166

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Built-in Error Correction

Similarly, at time T2W and T3W, DI[63:0] = B and C, together with their corresponding parity bits PB (hex) and PC (hex) are written into memory locations b and c. PB and PC appear at output ECCPARITY[7:0] shortly after T2W and T3W.

ECC Encode-Only Read

ECC encode-only read is identical to normal block RAM read. 64-bit data appears at DO[63:0] and 8-bit parity appears at DOP[7:0]. Single-bit error correction does not happen, and the error flags SBITERR and DBITERR is never asserted.

ECC Decode-Only
Set by Attributes
EN_ECC_READ = TRUE EN_ECC_WRITE = FALSE In ECC decode-only, only the ECC decoder is enabled. The ECC encoder is disabled. Decode-only mode is used to inject single-bit or double-bit errors to test the functionality of the ECC decoder. The ECC parity bits must be externally supplied using the DIP[7:0] pins.

Using ECC Decode-Only to Inject Single-Bit Error

At time T1W, T2W, T3W, DI[63:0] = A, B, C with single-bit error and DIP[7:0] = PA (hex), PB (hex), PC (hex), the corresponding ECC parity bits for A, B, and C are written into memory locations a, b, and c. At time T1R, T2R, T3R, the contents of address a, b, and c are read out and corrected as needed. Latch mode: DO[63:0] = A, B, C, DOP[7:0] = PA, PB, PC shortly after T1R, T2R, T3R. Register mode: DO[63:0] = A, B, C, DOP[7:0] = PA, PB, PC shortly after T2R, T3R, T4R. SBITERR lines up with the corresponding DO/DOP data.

The ECC decoder also corrects single-bit error in parity bits.

Using the ECC Decode-Only to Inject Double-Bit Error

At time T1W, T2W, T3W, DI[63:0] = A, B, C with double-bit error and DIP[7:0] = PA (hex), PB (hex), PB (hex), the corresponding ECC parity bits for A, B, and C are written into memory location a, b, and c. At time T1R, T2R, T3R, the original contents of address a, b, and c are read out and a double-bit error is detected. Latch mode: DO[63:0] = A, B, C with double-bit error, DOP[7:0] = PA, PB, PC shortly after T1R, T2R, T3R. Register mode: DO[63:0] = A, B, C with double-bit error, DOP[7:0] = PA, PB, PC shortly after T2R, T3R, T4R. DBITERR lines up with the corresponding DO/DOP data.

The ECC decoder also detects when double-bit error in parity bits occurs, and when a single-bit error in the data bits and a single-bit error in the corresponding parity bits occurs.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

167

Chapter 4: Block RAM

ECC Timing Characteristics

The various ECC timing parameters are also shown in Figure 4-31 and Figure 4-32. Since write clock and read clock are independent of each other, all write timing in Figure 4-31 is referenced to WRCLK. All read timing in Figure 4-32 is referenced to RDCLK.

Standard ECC Write Timing (Figure 4-31)

At time TRCCK_EN, before time T1W, write enable becomes valid at the WREN input of the block RAM. At time TRCCK_ADDR, before time T1W, write address a becomes valid at the WRADDR[8:0] inputs of the block RAM. WRADDR input is not needed for FIFO. At time TRDCK_DI_ECC (standard ECC), before time T1W, write data A (hex) becomes valid at the DI[63:0] inputs of the block RAM. At time TRCKO_ECC_PARITY (standard ECC), after time T1W, ECC parity data PA (hex) becomes valid at the ECCPARITY[7:0] output pins of the block RAM.

Standard ECC Read Timing (Figure 4-32)

At time TRCCK_EN, before time T1R, read enable becomes valid at the RDEN input of the block RAM. At time TRCCK_ADDR, before time T1R, write address a becomes valid at the RDADDR[8:0] inputs of the block RAM. RDADDR input is not needed for FIFO.

DO_REG = 0
At time TRCKO_DO (latch mode), after time T1R, data A (hex) becomes valid at the DO[63:0] output pins of the block RAM. At time TRCKO_DOP (latch mode), after time T1R, data PA (hex) becomes valid at the DOP[7:0] output pins of the block RAM. At time TRCKO_ECC_SBITERR (latch mode), after time T1R, SBITERR is asserted if single-bit error is detected and corrected on data set A. At time TRCKO_ECC_DBITERR (latch mode), after time T2R, DBITERR is asserted if double-bit error is detected on data set B.

DO_REG = 1
At time TRCKO_DO (register mode), after time T2R, data A (hex) becomes valid at the DO[63:0] output pins of the block RAM. At time TRCKO_DOP (register mode), after time T2R, data PA (hex) becomes valid at the DOP[7:0] output pins of the block RAM. At time TRCKO_ECCR_SBITERR (register mode), after time T2R, SBITERR is asserted if single-bit error is detected and corrected on data set A. At time TRCKO_ECCR_DBITERR (register mode), after time T3R, DBITERR is asserted if double-bit error is detected on data set B.

168

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Built-in Error Correction

Encode-Only ECC Write Timing (Figure 4-31)

Setup/hold time for WREN and WRADDR are the same as standard ECC. At time TRDCK_DI_ECC (encode-only ECC), before time T1W, write data A (hex) becomes valid at the DI[63:0] inputs of the block RAM. At time TRCKO_ECC_PARITY (encode-only ECC), after time T1W, ECC parity data PA (hex) becomes valid at the ECCPARITY[7:0] output pins of the block RAM.

Encode-Only ECC Read Timing

Encode-only ECC read timing are the same as normal block RAM read timing.

Decode-Only ECC Write Timing

Decode-only ECC write timing is the same as normal block RAM write timing.

Decode-Only ECC Read Timing

Decode-only ECC read timing is the same as standard ECC read timing.

Block RAM ECC Mode Timing Parameters

Table 4-25 shows the Virtex-5 FPGA block RAM ECC mode timing parameters. Table 4-25: Block RAM ECC Mode Timing Parameters
Function Control Signal Description

Parameter

Setup and Hold Relative to Clock (CLK)

TRxCK_x = Setup time (before clock edge) and TRCKx_x = Hold time (after clock edge) TRDCK_DI_ECC (Standard ECC Mode) TRCKD_DI_ECC (Standard ECC Mode) TRDCK_DI_ECC (Encode-only Mode) TRCKD_DI_ECC (Encode-only Mode) Clock to Out Delays TRCKO_DO (latch mode) TRCKO_DO (register mode) Clock to Output(2) CLK to DO Clock to Output(2) CLK to DO Time after the clock that the output data is stable at the DO outputs of the block RAM (without output register). Time after the clock that the output data is stable at the DO outputs of the block RAM (with output register). Time before the clock that data must be stable at the DI inputs of the block RAM. Standard ECC mode. DI Time after the clock that data must be stable at the DI inputs of the block RAM. Standard ECC mode. Time before the clock that data must be stable at the DI inputs of the block RAM. Encode-only mode. DI Time after the clock that data must be stable at the DI inputs of the block RAM. Encode-only mode.

Data inputs(1)

Data inputs(1)

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

169

Chapter 4: Block RAM

Table 4-25:

Block RAM ECC Mode Timing Parameters (Continued)

Function Control Signal Description

Parameter Clock to ECC Delays TRCKO_ECC_PARITY (encode-only mode)(3) TRCKO_ECC_SBITERR(3)

Clock to ECC Parity Output Clock to ECC Single-Bit-Error Output Clock to ECC Single-Bit-Error Output Clock to ECC Double-Bit-Error Output Clock to ECC Double-Bit-Error Output

ECCPARITY

Time after WRCLK that the ECC parity signals are stable at the ECCPARITY outputs of the block RAM (in encode-only mode). Time after RDCLK that the single-bit-error signal is stable at the SBITERR output of the block RAM (without output register). Time after RDCLK that the single-bit-error signal is stable at the SBITERR output of the block RAM (with output register). Time after RDCLK that the double-bit-error signal is stable at the DBITERR output of the block RAM (without output register). Time after RDCLK that the double-bit-error signal is stable at the DBITERR output of the block RAM (with output register).

SBITERR

TRCKO_ECCR_SBITERR(4)

SBITERR

TRCKO_ECC_DBITERR(3)

DBITERR

TRCKO_ECCR_DBITERR(4)

DBITERR

Notes:
1. TRDCK_DI_ECC/TRCKD_DI_ECC include the parity input TRDCK_DIP_ECC/TRCKD_DIP_ECC. 2. TRCKO_DO includes parity output (TRCKO_DOP). 3. TRCKO_ECC_PARITY, TRCKO_ECC_SBITERR, and TRCKO_ECC_DBITERR are combined into the TRCKO_ECC parameter in the Virtex-5 FPGA Data Sheet. 4. TRCKO_ECC_SBITERR and TRCKO_ECC_DBITERR are combined into the TRCKO_ECCR parameter in the Virtex-5 FPGA Data Sheet.

Creating a Deliberate Error in a 72-bit Word

To deliberately create an error in a 72-bit word, configure the ECC decode-only mode and create a 72-bit word with one or two bit errors. Write the word into the block RAM. Reading the 72-bit word automatically corrects the single-bit error and asserts the SBITERR error flag or it detects the double-bit error and asserts the DBITERR error flag.

Creating Eight Parity Bits for a 64-bit Word

Using logic external to the block RAM (a large number of XOR circuits), eight parity bits can be created for a 64-bit word. However, using ECC encoder-only mode, the eight parity bits can be automatically created without additional logic by writing any 64-bit word into a separate block RAM. The encoded 8-bit ECC parity data is immediately available, or the complete 72-bit word can be read out.

Inserting a Single or Double Bit Error into a 72-bit Word

By reading a 72-bit word and selectively modifying one or two bits, then writing all 72 bits into the block RAM under test in ECC decode-only mode, a single or double bit error can be inserted.

170

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Legal Block RAM and FIFO Combinations

Block RAM ECC VHDL and Verilog Templates

VHDL and Verilog templates are available in the Libraries Guide.

Legal Block RAM and FIFO Combinations

The block RAMFIFO combinations shown in Figure 4-33 are supported in a single RAMB36 primitive. When placing block RAM and FIFO primitives in the same location, the FIFO must occupy the lower port.
X-Ref Target - Figure 4-33

RAMB18

RAMB18SDP

RAMB18

RAMB18SDP

RAMB18

RAMB18SDP

FIFO18

FIFO18_36

ug0190_4_35_050208

Figure 4-33:

Legal Block RAM and FIFO Combinations

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

171

Chapter 4: Block RAM

172

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Chapter 5

Configurable Logic Blocks (CLBs)

CLB Overview
The Configurable Logic Blocks (CLBs) are the main logic resources for implementing sequential as well as combinatorial circuits. Each CLB element is connected to a switch matrix for access to the general routing matrix (shown in Figure 5-1). A CLB element contains a pair of slices. These two slices do not have direct connections to each other, and each slice is organized as a column. Each slice in a column has an independent carry chain. For each CLB, slices in the bottom of the CLB are labeled as SLICE(0), and slices in the top of the CLB are labeled as SLICE(1).
X-Ref Target - Figure 5-1

COUT CLB

COUT

Slice(1) Switch Matrix Slice(0)

CIN

CIN
UG190_5_01_122605

Figure 5-1:

Arrangement of Slices within the CLB

The Xilinx tools designate slices with the following definitions. An X followed by a number identifies the position of each slice in a pair as well as the column position of the slice. The X number counts slices starting from the bottom in sequence 0, 1 (the first CLB column); 2, 3 (the second CLB column); etc. A Y followed by a number identifies a row of slices. The number remains the same within a CLB, but counts up in sequence from one CLB row to the next CLB row, starting from the bottom. Figure 5-2 shows four CLBs located in the bottom-left corner of the die.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

173

Chapter 5: Configurable Logic Blocks (CLBs)

X-Ref Target - Figure 5-2

COUT CLB

COUT

COUT CLB

COUT

Slice X1Y1

Slice X3Y1

Slice X0Y1 CIN COUT CLB Slice X1Y0 CIN COUT

Slice X2Y1 CIN COUT CLB Slice X3Y0 CIN COUT

Slice X0Y0

Slice X2Y0
UG190_5_02_122605

Figure 5-2:

Row and Column Relationship between CLBs and Slices

Slice Description
Every slice contains four logic-function generators (or look-up tables), four storage elements, wide-function multiplexers, and carry logic. These elements are used by all slices to provide logic, arithmetic, and ROM functions. In addition to this, some slices support two additional functions: storing data using distributed RAM and shifting data with 32-bit registers. Slices that support these additional functions are called SLICEM; others are called SLICEL. SLICEM (shown in Figure 5-3) represents a superset of elements and connections found in all slices. SLICEL is shown in Figure 5-4.

174

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB Overview

X-Ref Target - Figure 5-3

COUT

Reset Type
Sync

DI D6 D5 D4 D3 D2 D1 A6 A5 A4 A3 A2 A1 DI2 DPRAM64/32 SPRAM64/32 SRL32 O6 SRL16 O5 LUT DI1 RAM ROM MC31

Async DMUX

D DX D CE CK

D FF LATCH Q INIT1 INIT0 SRHIGH SRLOW SR REV DQ

WA1-WA6 WA7 WA8 DX CI C6 C5 C4 C3 C2 C1 DI2 A6 DPRAM64/32 A5 SPRAM64/32 O6 A4 SRL32 SRL16 O5 A3 LUT DI1 A2 RAM A1 ROM MC31 WA1-WA6 WA7 WA8

CMUX

C CX D CE CK

C FF LATCH Q INIT1 INIT0 SRHIGH SRLOW SR REV CQ

CX BI B6 B5 B4 B3 B2 B1 DI2 A6 DPRAM64/32 A5 SPRAM64/32 O6 A4 SRL32 SRL16 O5 A3 LUT DI1 A2 RAM A1 ROM MC31 WA1-WA6 WA7 WA8 BMUX

B BX D CE CK

B FF LATCH Q INIT1 INIT0 SRHIGH SRLOW SR REV BQ

BX AI A6 A5 A4 A3 A2 A1 DI2 A6 DPRAM64/32 A5 SPRAM64/32 O6 A4 SRL32 SRL16 O5 A3 LUT DI1 A2 RAM A1 ROM MC31 WA1-WA6 WA7 WA8 0/1

AMUX

A AX D CE CK

A FF LATCH Q INIT1 INIT0 SRHIGH SRLOW SR REV AQ

AX SR CE CLK CLK WSGEN WE WE

CIN

UG190_c5_03_022709

Figure 5-3:

Diagram of SLICEM

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

175

Chapter 5: Configurable Logic Blocks (CLBs)

X-Ref Target - Figure 5-4

COUT

Reset Type
Sync Async DMUX

D6 D5 D4 D3 D2 D1 DX

A6 A5 A4 A3 A2 A1

LUT ROM

O6 O5

D DX D CE CK

D FF LATCH Q INIT1 INIT0 SRHIGH SRLOW SR REV DQ

CMUX C6 C5 C4 C3 C2 C1 CX A6 A5 A4 A3 A2 A1 LUT ROM

O6 O5

C CX D CE CK

C FF LATCH Q INIT1 INIT0 SRHIGH SRLOW SR REV CQ

BMUX B6 B5 B4 B3 B2 B1 BX A6 A5 A4 A3 A2 A1 LUT ROM

O6 O5

B BX D CE CK

B FF LATCH Q INIT1 INIT0 SRHIGH SRLOW SR REV BQ

AMUX A6 A5 A4 A3 A2 A1 AX SR CE CLK A6 A5 A4 A3 A2 A1 LUT ROM

O6 O5

A AX D CE CK 0/1

A FF LATCH Q INIT1 INIT0 SRHIGH SRLOW SR REV AQ

CIN

UG190_5_04_032606

Figure 5-4:

Diagram of SLICEL

Each CLB can contain zero or one SLICEM. Every other CLB column contains a SLICEMs. In addition, the two CLB columns to the left of the DSP48E columns both contain a SLICEL and a SLICEM.

176

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB Overview

CLB/Slice Configurations
Table 5-1 summarizes the logic resources in one CLB. Each CLB or slice can be implemented in one of the configurations listed. Table 5-2 shows the available resources in all CLBs. Table 5-1:
Slices 2
Notes:
1. SLICEM only, SLICEL does not have distributed RAM or shift registers.

Logic Resources in One CLB

Flip-Flops 8 Arithmetic and Carry Chains 2 Distributed RAM(1) 256 bits Shift Registers(1) 128 bits

LUTs 8

Table 5-2:

Virtex-5 FPGA Logic Resources Available in All CLBs

CLB Array Row x Column 60 x 26 80 x 30 80 x 38 80 x 30 80 x 34 120 x 30 120 x 30 120 x 34 160 x 38 120 x 54 120 x 54 160 x 46 160 x 56 160 x 54 160 x 54 200 x 56 200 x 58 160 x 76 160 x 76 240 x 68 160 x 108 160 x 108 240 x 78 240 x 78 240 x 108 240 x 108 Number of 6-Input LUTs 12,480 19,200 20,480 19,200 21,760 28,800 28,800 32,640 44,800 51,840 51,840 58,880 64,000 69,120 69,120 81,920 92,800 97,280 97,280 122,880 138,240 138,240 149,760 149,760 207,360 207,360 Maximum Distributed RAM (Kb) 210 320 380 320 520 480 480 780 820 840 840 1,520 1,240 1,120 1,120 1,580 1,500 1,640 1,640 2,280 2,280 2,280 4,200 2,400 3,420 3,420 Shift Register (Kb) 105 160 190 160 260 240 240 390 410 420 420 760 620 560 560 790 750 820 820 1140 1140 1140 2100 1200 1710 1710 Number of Flip-Flops 12,480 19,200 20,480 19,200 21,760 28,800 28,800 32,640 44,800 51,840 51,840 58,880 64,000 69,120 69,120 81,920 92,800 97,280 97,280 122,880 138,240 138,240 149,760 149,760 207,360 207,360

Device XC5VLX20T XC5VLX30 XC5VFX30T XC5VLX30T XC5VSX35T XC5VLX50 XC5VLX50T XC5VSX50T XC5VFX70T XC5VLX85 XC5VLX85T XC5VSX95T XC5VFX100T XC5VLX110 XC5VLX110T XC5VFX130T XC5VTX150T XC5VLX155 XC5VLX155T XC5VFX200T XC5VLX220 XC5VLX220T XC5VSX240T XC5VTX240T XC5VLX330 XC5VLX330T

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

177

Chapter 5: Configurable Logic Blocks (CLBs)

Look-Up Table (LUT)

The function generators in Virtex-5 FPGAs are implemented as six-input look-up tables (LUTs). There are six independent inputs (A inputs - A1 to A6) and two independent outputs (O5 and O6) for each of the four function generators in a slice (A, B, C, and D). The function generators can implement any arbitrarily defined six-input Boolean function. Each function generator can also implement two arbitrarily defined five-input Boolean functions, as long as these two functions share common inputs. Only the O6 output of the function generator is used when a six-input function is implemented. Both O5 and O6 are used for each of the five-input function generators implemented. In this case, A6 is driven High by the software. The propagation delay through a LUT is independent of the function implemented, or whether one six-input or two five-input generators are implemented. Signals from the function generators can exit the slice (through A, B, C, D output for O6 or AMUX, BMUX, CMUX, DMUX output for O5), enter the XOR dedicated gate from an O6 output (see Fast Lookahead Carry Logic), enter the carry-logic chain from an O5 output (see Fast Lookahead Carry Logic), enter the select line of the carry-logic multiplexer from O6 output (see Fast Lookahead Carry Logic), feed the D input of the storage element, or go to F7AMUX/F7BMUX from O6 output. In addition to the basic LUTs, slices contain three multiplexers (F7AMUX, F7BMUX, and F8MUX). These multiplexers are used to combine up to four function generators to provide any function of seven or eight inputs in a slice. F7AMUX and F7BMUX are used to generate seven input functions from LUTs A and B, or C and D, while F8MUX is used to combine all LUTs to generate eight input functions. Functions with more than eight inputs can be implemented using multiple slices. There are no direct connections between slices to form function generators greater than eight inputs within a CLB or between slices.

Storage Elements
The storage elements in a slice can be configured as either edge-triggered D-type flip-flops or level-sensitive latches. The D input can be driven directly by a LUT output via AFFMUX, BFFMUX, CFFMUX or DFFMUX, or by the BYPASS slice inputs bypassing the function generators via AX, BX, CX, or DX input. When configured as a latch, the latch is transparent when the CLK is Low. The control signals clock (CK), clock enable (CE), set/reset (SR), and reverse (REV) are common to all storage elements in one slice. When one flip-flop in a slice has SR or CE enabled, the other flip-flops used in the slice will also have SR or CE enabled by the common signal. Only the CLK signal has independent polarity. Any inverter placed on the clock signal is automatically absorbed. The CE, SR, and REV signals are active High. All flip-flop and latch primitives have CE and non-CE versions. The SR signal forces the storage element into the state specified by the attribute SRHIGH or SRLOW. SRHIGH forces a logic High at the storage element output when SR is asserted, while SRLOW forces a logic Low at the storage element output. When SR is used, an optional second input (DX) forces the storage element output into the opposite state via the REV pin. The reset condition is predominant over the set condition (see Figure 5-5). Table 5-3 and Table 5-4 provide truth tables for SR and REV depending on whether SRLOW or SRHIGH is used. Table 5-3: Truth Table when SRLOW is Used (Default Condition)
SR 0 0 REV 0 1 Function No Logic Change 1

178

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB Overview

Table 5-3:

Truth Table when SRLOW is Used (Default Condition) (Continued)

SR 1 1 REV 0 1 Function 0 0

Table 5-4:

Truth Table when SRHIGH is Used

SR 0 0 1 1 REV 0 1 0 1
DFF
FF LATCH Q INIT1 D INIT0 SRHIGH CE SRLOW CK SR REV DX DQ

Function No Logic Change 0 1 0

X-Ref Target - Figure 5-5

LUT D Output

LUT C Output

CFF
FF LATCH Q INIT1 D INIT0 SRHIGH CE SRLOW CK SR REV CQ

CX

SR

Reset Type
Sync

LUT B Output BFF

BX CE CLK FF LATCH Q INIT1 D INIT0 SRHIGH CE SRLOW CK SR REV

Async

BQ

LUT A Output

AFF
FF LATCH Q INIT1 D INIT0 SRHIGH CE SRLOW CK SR REV AQ

AX

UG190_5_05_071207

Figure 5-5:

Register/Latch Configuration in a Slice

SRHIGH and SRLOW can be set individually for each storage element in a slice. The choice of synchronous (SYNC) or asynchronous (ASYNC) set/reset (SRTYPE) cannot be set individually for each storage element in a slice.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

179

Chapter 5: Configurable Logic Blocks (CLBs)

The initial state after configuration or global initial state is defined by separate INIT0 and INIT1 attributes. By default, setting the SRLOW attribute sets INIT0, and setting the SRHIGH attribute sets INIT1. Virtex-5 devices can set INIT0 and INIT1 independent of SRHIGH and SRLOW. The configuration options for the set and reset functionality of a register or a latch are as follows: No set or reset Synchronous set Synchronous reset Synchronous set and reset Asynchronous set (preset) Asynchronous reset (clear) Asynchronous set and reset (preset and clear)

Distributed RAM and Memory (Available in SLICEM only)

Multiple LUTs in a SLICEM can be combined in various ways to store larger amount of data. The function generators (LUTs) in SLICEMs can be implemented as a synchronous RAM resource called a distributed RAM element. RAM elements are configurable within a SLICEM to implement the following: Single-Port 32 x 1-bit RAM Dual-Port 32 x 1-bit RAM Quad-Port 32 x 2-bit RAM Simple Dual-Port 32 x 6-bit RAM Single-Port 64 x 1-bit RAM Dual-Port 64 x 1-bit RAM Quad-Port 64 x 1-bit RAM Simple Dual-Port 64 x 3-bit RAM Single-Port 128 x 1-bit RAM Dual-Port 128 x 1-bit RAM Single-Port 256 x 1-bit RAM

Distributed RAM modules are synchronous (write) resources. A synchronous read can be implemented with a storage element or a flip-flop in the same slice. By placing this flipflop, the distributed RAM performance is improved by decreasing the delay into the clockto-out value of the flip-flop. However, an additional clock latency is added. The distributed elements share the same clock input. For a write operation, the Write Enable (WE) input, driven by either the CE or WE pin of a SLICEM, must be set High.

180

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB Overview

Table 5-5 shows the number of LUTs (four per slice) occupied by each distributed RAM configuration. Table 5-5: Distributed RAM Configuration
RAM 32 x 1S 32 x 1D 32 x 2Q(2) 32 x 6SDP(2) 64 x 1S 64 x 1D 64 x 1Q(3) 64 x 3SDP(3) 128 x 1S 128 x 1D 256 x 1S
Notes:
1. S = single-port configuration; D = dual-port configuration; Q = quad-port configuration; SDP = simple dual-port configuration. 2. RAM32M is the associated primitive for this configuration. 3. RAM64M is the associated primitive for this configuration.

Number of LUTs 1 2 4 4 1 2 4 4 2 4 4

For single-port configurations, distributed RAM has a common address port for synchronous writes and asynchronous reads. For dual-port configurations, distributed RAM has one port for synchronous writes and asynchronous reads, and another port for asynchronous reads. In simple dual-port configuration, there is no data out (read port) from the write port. For quad-port configurations, distributed RAM has one port for synchronous writes and asynchronous reads, and three additional ports for asynchronous reads. In single-port mode, read and write addresses share the same address bus. In dual-port mode, one function generator is connected with the shared read and write port address. The second function generator has the A inputs connected to a second read-only port address and the WA inputs shared with the first read/write port address. Figure 5-6 through Figure 5-14 illustrate various example distributed RAM configurations occupying one SLICEM. When using x2 configuration (RAM32X2Q), A6 and WA6 are driven High by the software to keep O5 and O6 independent.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

181

Chapter 5: Configurable Logic Blocks (CLBs)

X-Ref Target - Figure 5-6

RAM 32X2Q
(DX) (AI/BI/CI/DI) D[5:1] 5
5

DPRAM32 DI1 DI2 A[6:1] WA[6:1] CLK WE O6 DOD[0]

DID[1] DID[0] ADDRD[4:0] WCLK WED

(CLK) (WE)

O5

DOD[1]

DPRAM32 DI1 DI2 A[6:1] WA[6:1] CLK WE O6 DOC[0]

ADDRC[4:0]

C[5:1] 5
5

O5

DOC[1]

DPRAM32 DI1 DI2 A[6:1] WA[6:1] CLK WE O6 DOB[0]

ADDRB[4:0]

B[5:1] 5
5

O5

DOB[1]

DPRAM32 DI1 DI2 A[6:1] WA[6:1] CLK WE O6 DOA[0]

ADDRA[4:0]

A[5:1] 5
5

O5

DOA[1]

UG190_5_06_032706

Figure 5-6:

Distributed RAM (RAM32X2Q)

182

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB Overview

X-Ref Target - Figure 5-7

RAM 32X6SDP
DPRAM32 unused unused WADDR[5:1] WADDR[6] = 1 WCLK WED DI1 DI2 A[6:1] WA[6:1] CLK WE

D[5:1] 5
5

(CLK) (WE)

DPRAM32 DATA[1] DATA[2] RADDR[5:1] RADDR[6] = 1 DI1 DI2 A[6:1] WA[6:1] CLK WE O6 O[1]

C[5:1] 5
5

O5

O[2]

DPRAM32 DATA[3] DATA[4] B[5:1] 5

5

DI1 DI2 A[6:1] WA[6:1] CLK WE

O6

O[3]

O5

O[4]

DPRAM32 DATA[5] DATA[6] DI1 DI2 A[6:1] WA[6:1] CLK WE O6 O[5]

A[5:1] 5
5

O5

O[6]

UG190_5_06_032706

Figure 5-7:

Distributed RAM (RAM32X6SDP)

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

183

Chapter 5: Configurable Logic Blocks (CLBs)

X-Ref Target - Figure 5-8

RAM64X1S
SPRAM64 DI1 A[6:1] WA[6:1] CLK WE O6

D A[5:0] WCLK WE

(DX)
6 (D[6:1]) 6

O D Q

Output Registered Output (Optional)

(CLK) (WE/CE)

ug190_5_07_032706

Figure 5-8:

Distributed RAM (RAM64X1S)

If four single-port 64 x 1-bit modules are built, the four RAM64X1S primitives can occupy a SLICEM, as long as they share the same clock, write enable, and shared read and write port address inputs. This configuration equates to 64 x 4-bit single-port distributed RAM.
X-Ref Target - Figure 5-9

RAM64X1D
DPRAM64 DI1 A[6:1] WA[6:1] CLK WE O6

D A[5:0] WCLK WE

(DX) (D[6:1]) 6
6

SPO D Q Registered Output (Optional)

(CLK) (WE/CE)

DPRAM64 DI1 DPRA[5:0] (C[6:1]) 6

6

O6

DPO D Q Registered Output (Optional)

A[6:1] WA[6:1] CLK WE

UG190_5_09_050506

Figure 5-9:

Distributed RAM (RAM64X1D)

If two dual-port 64 x 1-bit modules are built, the two RAM64X1D primitives can occupy a SLICEM, as long as they share the same clock, write enable, and shared read and write port address inputs. This configuration equates to 64 x 2-bit dual-port distributed RAM.

184

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB Overview

X-Ref Target - Figure 5-10

RAM64X1Q

DID ADDRD WCLK WE

(DX) (D[6:1]) (CLK) (WE)

DPRAM64 DI1 A[6:1] WA[6:1] CLK WE O6

DOD Registered Output (Optional)

DPRAM64 DI1 ADDRC (C[6:1]) A[6:1] WA[6:1] CLK WE O6 DOC Registered Output (Optional)

DPRAM64 DI1 ADDRB (B[6:1]) A[6:1] WA[6:1] CLK WE O6

DOB Registered Output (Optional)

DPRAM64 DI1 ADDRA (A[6:1]) A[6:1] WA[6:1] CLK WE O6

DOA Registered Output (Optional)

ug190_5_10_032706

Figure 5-10:

Distributed RAM (RAM64X1Q)

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

185

Chapter 5: Configurable Logic Blocks (CLBs)

X-Ref Target - Figure 5-11

RAM 64X3SDP
DPRAM32 unused unused WADDR[6:1] WCLK WED DI1 DI2 A[6:1] WA[6:1] CLK WE

D[6:1] 6
6

(CLK) (WE)

DPRAM32 DATA[1] RADDR[6:1] C[6:1] 6

6

DI1 DI2 A[6:1] WA[6:1] CLK WE

O6

O[1]

O5

DPRAM32 DATA[2] B[6:1] 6

6

DI1 DI2 A[6:1] WA[6:1] CLK WE

O6

O[2]

O5

DPRAM32 DATA[3] A[6:1] 6

6

DI1 DI2 A[6:1] WA[6:1] CLK WE

O6

O[3]

O5

UG190_5_06_050506

Figure 5-11:

Distributed RAM (RAM64X3SDP)

Implementation of distributed RAM configurations with depth greater than 64 requires the usage of wide-function multiplexers (F7AMUX, F7BMUX, and F8MUX).

186

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB Overview

X-Ref Target - Figure 5-12

RAM128X1S
A6 (CX) (DX)
[5:0]

SPRAM64 DI1 A[6:1] WA[7:1] CLK WE 0 SPRAM64 DI1 O6 F7BMUX D Q Output Registered Output (Optional) A[6:1] WA[7:1] CLK WE
ug190_5_12_050506

D A[6:0] WCLK WE

O6

(CLK) (WE/CE)

[5:0] 7

Figure 5-12:

Distributed RAM (RAM128X1S)

If two single-port 128 x 1-bit modules are built, the two RAM128X1S primitives can occupy a SLICEM, as long as they share the same clock, write enable, and shared read and write port address inputs. This configuration equates to 128 x 2-bit single-port distributed RAM.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

187

Chapter 5: Configurable Logic Blocks (CLBs)

X-Ref Target - Figure 5-13

RAM128X1D
A6 (CX) DX
6 7

DPRAM64 DI1 A[6:1] WA[7:1] CLK WE SPO DPRAM64 DI1

6 7

D A[6:0] WCLK WE

O6

(CLK) (WE)

F7BMUX

D Q

O6

Registered Output (Optional)

A[6:1] WA[7:1] CLK WE

DPRAM64 DI1 DPRA[6:0]

6 7

O6

A[6:1] WA[7:1] CLK WE DPO DPRAM64 DI1 O6 D Q Registered Output (Optional) A[6:1] WA[7:1] CLK WE

F7AMUX

6 7

AX
UG190_5_13_050506

Figure 5-13:

Distributed RAM (RAM128X1D)

188

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB Overview

X-Ref Target - Figure 5-14

RAM256X1S

SPRAM64 D A[7:0] WCLK WE (CLK) (WE/CE)

6 8

DI1 A[6:1] WA[8:1] CLK WE

O6

A6 (CX)

SPRAM64 DI1
6 8

F7BMUX

O6

A[6:1] WA[8:1] CLK WE

A7 (BX) O Output D Q Registered Output (Optional)

SPRAM64 DI1
6 8

F8MUX

O6

A[6:1] WA[8:1] CLK WE

A6 (AX)

SPRAM64 DI1
6 8

F7AMUX

O6

A[6:1] WA[8:1] CLK WE

UG190_5_14_050506

Figure 5-14:

Distributed RAM (RAM256X1S)

Distributed RAM configurations greater than the provided examples require more than one SLICEM. There are no direct connections between slices to form larger distributed RAM configurations within a CLB or between slices.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

189

Chapter 5: Configurable Logic Blocks (CLBs)

Distributed RAM Data Flow

Synchronous Write Operation

The synchronous write operation is a single clock-edge operation with an active-High write-enable (WE) feature. When WE is High, the input (D) is loaded into the memory location at address A.
Asynchronous Read Operation

The output is determined by the address A (for single-port mode output/SPO output of dual-port mode), or address DPRA (DPO output of dual-port mode). Each time a new address is applied to the address pins, the data value in the memory location of that address is available on the output after the time delay to access the LUT. This operation is asynchronous and independent of the clock signal.

Distributed RAM Summary

Single-port and dual-port modes are available in SLICEMs. A write operation requires one clock edge. Read operations are asynchronous (Q output). The data input has a setup-to-clock timing specification.

Read Only Memory (ROM)

Each function generator in SLICEMs and SLICELs can implement a 64 x 1-bit ROM. Three configurations are available: ROM64x1, ROM128x1, and ROM256x1. ROM contents are loaded at each device configuration. Table 5-6 shows the number of LUTs occupied by each ROM configuration. Table 5-6: ROM Configuration
ROM 64 x 1 128 x 1 256 x 1 Number of LUTs 1 2 4

Shift Registers (Available in SLICEM only)

A SLICEM function generator can also be configured as a 32-bit shift register without using the flip-flops available in a slice. Used in this way, each LUT can delay serial data anywhere from one to 32 clock cycles. The shiftin D (DI1 LUT pin) and shiftout Q31 (MC31 LUT pin) lines cascade LUTs to form larger shift registers. The four LUTs in a SLICEM are thus cascaded to produce delays up to 128 clock cycles. It is also possible to combine shift registers across more than one SLICEM. Note that there are no direct connections between slices to form longer shift registers, nor is the MC31 output at LUT B/C/D available. The resulting programmable delays can be used to balance the timing of data pipelines. Applications requiring delay or latency compensation use these shift registers to develop efficient designs. Shift registers are also useful in synchronous FIFO and content addressable memory (CAM) designs. The write operation is synchronous with a clock input (CLK) and an optional clock enable (CE). A dynamic read access is performed through the 5-bit address bus, A[4:0]. The LSB of the LUT is unused and the software automatically ties it to a logic High. The configurable shift registers cannot be set or reset. The read is asynchronous; however, a storage element

190

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB Overview

or flip-flop is available to implement a synchronous read. In this case, the clock-to-out of the flip-flop determines the overall delay and improves performance. However, one additional cycle of clock latency is added. Any of the 32 bits can be read out asynchronously (at the O6 LUT outputs) by varying the 5-bit address. This capability is useful in creating smaller shift registers (less than 32 bits). For example, when building a 13-bit shift register, simply set the address to the 13th bit. Figure 5-15 is a logic block diagram of a 32-bit shift register.
X-Ref Target - Figure 5-15

SRLC32E
SHIFTIN (MC31 of Previous LUT) SRL32 SHIFTIN (D) (AX) DI1 MC31 A[4:0] CLK CE
5 (A[6:2])

SHIFTOUT (Q31)

A[6:2] CLK CE O6 Output (Q) (AQ) Registered D Q Output (Optional)

ug190_5_15_050506

(CLK) (WE/CE)

Figure 5-15: 32-bit Shift Register Configuration Figure 5-16 illustrates an example shift register configuration occupying one function generator.
X-Ref Target - Figure 5-16

32-bit Shift Register SHIFTIN (D) WE CLK SHIFTOUT(Q31)

Address (A[4:0])

MUX

UG190_5_16_050506

Figure 5-16:

Representation of a Shift Register

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

191

Chapter 5: Configurable Logic Blocks (CLBs)

Figure 5-17 shows two 16-bit shift registers. The example shown can be implemented in a single LUT.
X-Ref Target - Figure 5-17

SRL16 SHIFTIN1 (AX) A[3:0] CLK CE

4

DI1 A[5:2] CLK WE

O5

SRL16 SHIFTIN2 (AI) DI2 O6

A[5:2] CLK WE

MC31

UG190_5_17_050506

Figure 5-17:

Dual 16-bit Shift Register Configuration

As mentioned earlier, an additional output (MC31) and a dedicated connection between shift registers allows connecting the last bit of one shift register to the first bit of the next, without using the LUT O6 output. Longer shift registers can be built with dynamic access to any bit in the chain. The shift register chaining and the F7AMUX, F7BMUX, and F8MUX multiplexers allow up to a 128-bit shift register with addressable access to be implemented in one SLICEM. Figure 5-18 through Figure 5-20 illustrate various example shift register configurations that can occupy one SLICEM.
X-Ref Target - Figure 5-18

SRL32 SHIFTIN (D) A[5:0] CLK WE (CLK) (WE/CE)

5

DI1 A[6:2]

O6

MC31 CLK WE

A5 (AX)

Output (Q) SRL32 DI1 O6 F7AMUX D Q (AQ) Registered Output

(Optional)
5

A[6:2] CLK WE

MC31

(MC31)

SHIFTOUT (Q63)
UG190_5_18_050506

Figure 5-18: 64-bit Shift Register Configuration

192

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB Overview

X-Ref Target - Figure 5-19

CX (A5) SRL32 SHIFTIN (D) A[6:0] CLK WE (CLK) (WE/CE)

5

DI1 A[6:2]

O6

MC31 CLK WE

F7BMUX

BX (A6) (BMUX) (BQ)

Output (Q) Registered Output

F8MUX SRL32 DI1

5

D Q

(Optional) O6

A[6:2] MC31 CLK WE

AX (A5)

SRL32 DI1
5

Not Used O6 F7AMUX

A[6:2] CLK WE
UG190_c5_19_020909

Figure 5-19:

96-bit Shift Register Configuration

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

193

Chapter 5: Configurable Logic Blocks (CLBs)

X-Ref Target - Figure 5-20

SRL32 SHIFTIN (D) A[6:0] CLK WE

5

DI1 A[6:2]

O6

(CLK) (WE/CE)

MC31 CLK WE

CX (A5)

SRL32 DI1 A[6:2] MC31 CLK WE O6

F7BMUX

BX (A6)

(BMUX) (BQ)

Output (Q) Registered Output

F8MUX SRL32 DI1 A[6:2] MC31 CLK WE AX (A5) O6

D Q

(Optional)

SRL32 DI1 A[6:2] MC31 CLK WE O6

F7AMUX

(MC31) SHIFTOUT (Q127)

UG190_5_20_050506

Figure 5-20: 128-bit Shift Register Configuration It is possible to create shift registers longer than 128 bits across more than one SLICEM. However, there are no direct connections between slices to form these shift registers.

Shift Register Data Flow

Shift Operation

The shift operation is a single clock-edge operation, with an active-High clock enable feature. When enable is High, the input (D) is loaded into the first bit of the shift register. Each bit is also shifted to the next highest bit position. In a cascadable shift register configuration, the last bit is shifted out on the M31 output. The bit selected by the 5-bit address port (A[4:0]) appears on the Q output.
Dynamic Read Operation

The Q output is determined by the 5-bit address. Each time a new address is applied to the 5-input address pins, the new bit position value is available on the Q output after the time

194

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB Overview

delay to access the LUT. This operation is asynchronous and independent of the clock and clock-enable signals.
Static Read Operation

If the 5-bit address is fixed, the Q output always uses the same bit position. This mode implements any shift-register length from 1 to 32 bits in one LUT. The shift register length is (N+1), where N is the input address (0 31). The Q output changes synchronously with each shift operation. The previous bit is shifted to the next position and appears on the Q output.

Shift Register Summary

A shift operation requires one clock edge. Dynamic-length read operations are asynchronous (Q output). Static-length read operations are synchronous (Q output). The data input has a setup-to-clock timing specification. In a cascadable configuration, the Q31 output always contains the last bit value. The Q31 output changes synchronously after each shift operation.

Multiplexers
Function generators and associated multiplexers in Virtex-5 FPGAs can implement the following: 4:1 multiplexers using one LUT 8:1 multiplexers using two LUTs 16:1 multiplexers using four LUTs

These wide input multiplexers are implemented in one level or logic (or LUT) using the dedicated F7AMUX, F7BMUX, and F8MUX multiplexers. These multiplexers allow LUT combinations of up to four LUTs in a slice.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

195

Chapter 5: Configurable Logic Blocks (CLBs)

Designing Large Multiplexers

4:1 Multiplexer
Each LUT can be configured into a 4:1 MUX. The 4:1 MUX can be implemented with a flipflop in the same slice. Up to four 4:1 MUXes can be implemented in a slice, as shown in Figure 5-21.
X-Ref Target - Figure 5-21

SLICE LUT
O6 SEL D [1:0], DATA D [3:0] Input (D[6:1]) 6 A[6:1] D Q (D) (DQ) 4:1 MUX Output Registered Output

LUT
O6 SEL C [1:0], DATA C [3:0] Input (C[6:1]) 6 A[6:1]

(Optional) (C) D Q (CQ) 4:1 MUX Output Registered Output

LUT
O6 SEL B [1:0], DATA B [3:0] Input (B[6:1]) 6 A[6:1]

(Optional) (B) D Q (BQ) 4:1 MUX Output Registered Output

LUT
O6 SEL A [1:0], DATA A [3:0] Input (A[6:1])
6

(Optional) (A) D Q (AQ) 4:1 MUX Output Registered Output

A[6:1]

(CLK) CLK

(Optional)
UG190_5_21_050506

Figure 5-21:

Four 4:1 Multiplexers in a Slice

196

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB Overview

8:1 Multiplexer
Each slice has an F7AMUX and an F7BMUX. These two muxes combine the output of two LUTs to form a combinatorial function up to 13 inputs (or an 8:1 MUX). Up to two 8:1 MUXes can be implemented in a slice, as shown in Figure 5-22.
X-Ref Target - Figure 5-22

SLICE LUT
O6 SEL D [1:0], DATA D [3:0] Input (1) (D[6:1]) 6 A[6:1] F7BMUX (CMUX) 8:1 MUX Output (1) Registered Output

LUT
O6 SEL C [1:0], DATA C [3:0] Input (1) (C[6:1]) 6 A[6:1] (Optional) (CX) (CLK) D Q (CQ)

SELF7(1) CLK

LUT
O6 SEL B [1:0], DATA B [3:0] Input (2) (B[6:1]) 6 A[6:1] F7AMUX (AMUX) 8:1 MUX Output (2) Registered Output

LUT
O6 SEL A [1:0], DATA A [3:0] Input (2) (A[6:1])
6

D Q

(AQ)

A[6:1] (Optional)

SELF7(2)

(AX)
UG190_5_22_090806

Figure 5-22:

Two 8:1 Multiplexers in a Slice

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

197

Chapter 5: Configurable Logic Blocks (CLBs)

16:1 Multiplexer
Each slice has an F8MUX. F8MUX combines the outputs of F7AMUX and F7BMUX to form a combinatorial function up to 27 inputs (or a 16:1 MUX). Only one 16:1 MUX can be implemented in a slice, as shown in Figure 5-23.
X-Ref Target - Figure 5-23

SLICE LUT
O6 SEL D [1:0], DATA D [3:0] Input (D[6:1]) 6 A[6:1] F7BMUX

LUT
O6 SEL C [1:0], DATA C [3:0] Input (C[6:1]) 6 A[6:1] F8MUX (CX) (BMUX) 16:1 MUX Output Registered Output

SELF7

LUT
O6 SEL B [1:0], DATA B [3:0] Input (B[6:1]) 6 A[6:1] F7AMUX D Q

(B)

(Optional)

LUT
O6 SEL A [1:0], DATA A [3:0] Input (A[6:1])
6

A[6:1]

SELF7 SELF8 CLK

(AX) (BX) (CLK)

UG190_5_23_050506

Figure 5-23:

16:1 Multiplexer in a Slice

It is possible to create multiplexers wider than 16:1 across more than one SLICEM. However, there are no direct connections between slices to form these wide multiplexers.

Fast Lookahead Carry Logic

In addition to function generators, dedicated carry logic is provided to perform fast arithmetic addition and subtraction in a slice. A Virtex-5 FPGA CLB has two separate carry chains, as shown in Figure 5-1. The carry chains are cascadable to form wider add/subtract logic, as shown in Figure 5-2. The carry chain in the Virtex-5 device is running upward and has a height of four bits per slice. For each bit, there is a carry multiplexer (MUXCY) and a dedicated XOR gate for adding/subtracting the operands with a selected carry bits. The dedicated carry path and

198

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB Overview

carry multiplexer (MUXCY) can also be used to cascade function generators for implementing wide logic functions. Figure 5-24 illustrates the carry chain with associated logic elements in a slice.
X-Ref Target - Figure 5-24

COUT (To Next Slice) Carry Chain Block (CARRY4) CO3 O6 From LUTD O5 From LUTD DX S3 MUXCY O3 DI3 D Q DQ (Optional) CO2 O6 From LUTC O5 From LUTC CX S2 MUXCY O2 DI2 D Q CQ (Optional) CO1 O6 From LUTB O5 From LUTB BX S1 MUXCY O1 DI1 D Q BQ (Optional) CO0 O6 From LUTA O5 From LUTA AX CYINIT CIN S0 MUXCY O0 DI0 D Q AQ (Optional)
* Can be used if unregistered/registered outputs are free.
UG190_5_24_050506

DMUX/DQ*

DMUX

CMUX/CQ*

CMUX

BMUX/BQ*

BMUX

AMUX/AQ*

AMUX

01 CIN (From Previous Slice)

Figure 5-24:

Fast Carry Logic Path and Associated Elements

The carry chains carry lookahead logic along with the function generators. There are ten independent inputs (S inputs S0 to S3, DI inputs DI1 to DI4, CYINIT and CIN) and eight independent outputs (O outputs O0 to O3, and CO outputs CO0 to CO3). The S inputs are used for the propagate signals of the carry lookahead logic. The propagate signals are sourced from the O6 output of a function generator. The DI inputs are used for the generate signals of the carry lookahead logic. The generate signals are sourced from either the O5 output of a function generator or the BYPASS input (AX, BX, CX, or DX) of a slice. The former input is used to create a multiplier, while the latter is used

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

199

Chapter 5: Configurable Logic Blocks (CLBs)

to create an adder/accumulator. CYINIT is the CIN of the first bit in a carry chain. The CYINIT value can be 0 (for add), 1 (for subtract), or AX input (for the dynamic first carry bit). The CIN input is used to cascade slices to form a longer carry chain. The O outputs contain the sum of the addition/subtraction. The CO outputs compute the carry out for each bit. CO3 is connected to COUT output of a slice to form a longer carry chain by cascading multiple slices. The propagation delay for an adder increases linearly with the number of bits in the operand, as more carry chains are cascaded. The carry chain can be implemented with a storage element or a flip-flop in the same slice.

CLB / Slice Timing Models

Due to the large size and complexity of Virtex-5 FPGAs, understanding the timing associated with the various paths and functional elements is a difficult and important task. Although it is not necessary to understand the various timing parameters to implement most designs using Xilinx software, a thorough timing model can assist advanced users in analyzing critical paths or planning speed-sensitive designs. Three timing model sections are described: Functional element diagram basic architectural schematic illustrating pins and connections Timing parameters definitions of Virtex-5 FPGA Data Sheet timing parameters Timing Diagram - illustrates functional element timing parameters relative to each other

Use the models in this chapter in conjunction with both the Xilinx Timing Analyzer software (TRCE) and the section on switching characteristics in the Virtex-5 FPGA Data Sheet. All pin names, parameter names, and paths are consistent with the post-route timing and pre-route static timing reports. Most of the timing parameters found in the section on switching characteristics are described in this chapter. All timing parameters reported in the Virtex-5 FPGA Data Sheet are associated with slices and CLBs. The following sections correspond to specific switching characteristics sections in the Virtex-5 FPGA Data Sheet: General Slice Timing Model and Parameters (CLB Switching Characteristics) Slice Distributed RAM Timing Model and Parameters (Available in SLICEM only) (CLB Distributed RAM Switching Characteristics) Slice SRL Timing Model and Parameters (Available in SLICEM only) (CLB SRL Switching Characteristics) Slice Carry-Chain Timing Model and Parameters (CLB Application Switching Characteristics)

200

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB / Slice Timing Models

General Slice Timing Model and Parameters

A simplified Virtex-5 FPGA slice is shown in Figure 5-25. Some elements of the slice are omitted for clarity. Only the elements relevant to the timing paths described in this section are shown.
X-Ref Target - Figure 5-25

LUT
D Inputs
6

O6 O5 FE/LAT D CE CLK Q

D DMUX DQ

DX

SR REV

LUT
C Inputs
6

F7BMUX C CMUX FE/LAT

O6 O5 D CE CLK Q

CX

CQ

F8MUX

SR REV

LUT
B Inputs
6

O6 O5 FE/LAT D CE CLK Q

B BMUX

BX

BQ

SR REV

LUT
A Inputs
6

F7AMUX A AMUX FE/LAT

O6 O5 D CE CLK Q

AX CE CLK SR REV (DX)

AQ

SR REV

UG190_5_25_050506

Figure 5-25:

Simplified Virtex-5 FPGA Slice

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

201

Chapter 5: Configurable Logic Blocks (CLBs)

Timing Parameters
Table 5-7 shows the general slice timing parameters for a majority of the paths in Figure 5-25. Table 5-7: General Slice Timing Parameters
Parameter Combinatorial Delays TILO(1) A/B/C/D inputs to A/B/C/D outputs Propagation delay from the A/B/C/D inputs of the slice, through the look-up tables (LUTs), to the A/B/C/D outputs of the slice (six-input function). Propagation delay from the A/B/C/D inputs of the slice, through the LUTs and F7AMUX/F7BMUX to the AMUX/CMUX outputs (seven-input function). Propagation delay from the A/B/C/D inputs of the slice, through the LUTs, F7AMUX/F7BMUX, and F8MUX to the BMUX output (eight-input function). Time after the clock that data is stable at the AQ/BQ/CQ/DQ outputs of the slice sequential elements (configured as a flip-flop). Time after the clock that data is stable at the XQ/YQ outputs of the slice sequential elements (configured as a latch). Time before/after the CLK that data from the AX/BX/CX/DX inputs of the slice must be stable at the D input of the slice sequential elements (configured as a flip-flop). Time before/after the CLK that the CE input of the slice must be stable at the CE input of the slice sequential elements (configured as a flip-flop). Time before/after the CLK that the SR (Set/Reset) and the BY (Rev) inputs of the slice must be stable at the SR/Rev inputs of the slice sequential elements (configured as a flip-flop). Minimum Pulse Width for the SR (Set/Reset) and BY (Rev) pins. Propagation delay for an asynchronous Set/Reset of the slice sequential elements. From the SR/BY inputs to the AQ/BQ/CQ/DQ outputs. Toggle Frequency Maximum frequency that a CLB flip-flop can be clocked: 1 / (TCH + TCL). Function Description

TILO_2

A/B/C/D inputs to AMUX/CMUX outputs

TILO_3

A/B/C/D inputs to BMUX output

Sequential Delays TCKO FF Clock (CLK) to AQ/BQ/CQ/DQ outputs Latch Clock (CLK) to AQ/BQ/CQ/DQ outputs

TCKLO

Setup and Hold Times for Slice Sequential Elements(2) TDICK/TCKDI AX/BX/CX/DX inputs

TCECK/TCKCE

CE input

TSRCK/TCKSR

SR/BY input

Set/Reset TRPW TRQ

FTOG
Notes:

1. This parameter includes a LUT configured as two five-input functions. 2. TXXCK = Setup Time (before clock edge), and TCKXX = Hold Time (after clock edge).

202

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB / Slice Timing Models

Timing Characteristics
Figure 5-26 illustrates the general timing characteristics of a Virtex-5 FPGA slice.
X-Ref Target - Figure 5-26

1 CLK TCEO CE AX/BX/CX/DX (DATA) SR (RESET) TDICK

TSRCK TCKO TCKO

AQ/BQ/CQ/DQ (OUT)

ug190_5_26_050506

Figure 5-26:

General Slice Timing Characteristics

At time TCEO before clock event (1), the clock-enable signal becomes valid-High at the CE input of the slice register. At time TDICK before clock event (1), data from either AX, BX, CX, or DX inputs become valid-High at the D input of the slice register and is reflected on either the AQ, BQ, CQ, or DQ pin at time TCKO after clock event (1). At time TSRCK before clock event (3), the SR signal (configured as synchronous reset) becomes valid-High, resetting the slice register. This is reflected on the AQ, BQ, CQ, or DQ pin at time TCKO after clock event (3).

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

203

Chapter 5: Configurable Logic Blocks (CLBs)

Slice Distributed RAM Timing Model and Parameters (Available in SLICEM only)
Figure 5-27 illustrates the details of distributed RAM implemented in a Virtex-5 FPGA slice. Some elements of the slice are omitted for clarity. Only the elements relevant to the timing paths described in this section are shown.
X-Ref Target - Figure 5-27

RAM
DX DI D input CLK WE 6 DI1 DI2 A[6:0] WA[6:0] CLK WE O6 D

O5

DMUX

RAM
CX CI C input 6 DI1 DI2 A[6:0] WA[6:0] CLK WE O6 C

O5

CMUX

RAM
BX BI B input 6 DI1 DI2 A[6:0] WA[6:0] CLK WE O6 B

O5

BMUX

RAM
AX AI A input 6 DI1 DI2 A[6:0] WA[6:0] CLK WE O6 A

O5

AMUX
UG190_5_27_050506

Figure 5-27:

Simplified Virtex-5 FPGA SLICEM Distributed RAM

204

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB / Slice Timing Models

Distributed RAM Timing Parameters

Table 5-8 shows the timing parameters for the distributed RAM in SLICEM for a majority of the paths in Figure 5-27. Table 5-8: Distributed RAM Timing Parameters
Parameter Function Description

Sequential Delays for a Slice LUT Configured as RAM (Distributed RAM) TSHCKO(1) CLK to A/B/C/D outputs Time after the CLK of a write operation that the data written to the distributed RAM is stable on the A/B/C/D output of the slice.

Setup and Hold Times for a Slice LUT Configured as RAM (Distributed RAM)(2) TDS/TDH(3) TACK/TCKA AX/BX/CX/DX configured as data input (DI1) A/B/C/D address inputs Time before/after the clock that data must be stable at the AX/BX/CX/DX input of the slice. Time before/after the clock that address signals must be stable at the A/B/C/D inputs of the slice LUT (configured as RAM). Time before/after the clock that the write enable signal must be stable at the WE input of the slice LUT (configured as RAM).

TWS/TWH

WE input

Clock CLK TWPH TWPL TWC

Notes:
1. This parameters includes a LUT configured as a two-bit distributed RAM. 2. TXXCK = Setup Time (before clock edge), and TCKXX = Hold Time (after clock edge). 3. Parameter includes AI/BI/CI/DI configured as a data input (DI2).

Minimum Pulse Width, High Minimum Pulse Width, Low Minimum clock period to meet address write cycle time.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

205

Chapter 5: Configurable Logic Blocks (CLBs)

Distributed RAM Timing Characteristics

The timing characteristics of a 16-bit distributed RAM implemented in a Virtex-5 FPGA slice (LUT configured as RAM) are shown in Figure 5-28.
X-Ref Target - Figure 5-28

1 TWC TWPH TWPL CLK A/B/C/D (ADDR) AX/BX/CX/DX (DI) WE DATA_OUT A/B/C/D Output 1 TWS TAS 2 TDS

X TILO

X TILO

TSHCKO 1 WRITE MEM(F) READ 0 WRITE 1 WRITE WRITE 0 MEM(E) READ

UG190_5_28_050506

Figure 5-28:

Slice Distributed RAM Timing Characteristics

Clock Event 1: Write Operation

During a Write operation, the contents of the memory at the address on the ADDR inputs are changed. The data written to this memory location is reflected on the A/B/C/D outputs synchronously. At time TWS before clock event 1, the write-enable signal (WE) becomes valid-High, enabling the RAM for a Write operation. At time TAS before clock event 1, the address (2) becomes valid at the A/B/C/D inputs of the RAM. At time TDS before clock event 1, the DATA becomes valid (1) at the DI input of the RAM and is reflected on the A/B/C/D output at time TSHCKO after clock event 1.

This is also applicable to the AMUX, BMUX, CMUX, DMUX, and COUT outputs at time TSHCKO and TWOSCO after clock event 1.

Clock Event 2: Read Operation

All Read operations are asynchronous in distributed RAM. As long as WE is Low, the address bus can be asserted at any time. The contents of the RAM on the address bus are reflected on the A/B/C/D outputs after a delay of length TILO (propagation delay through a LUT). The address (F) is asserted after clock event 2, and the contents of the RAM at address (F) are reflected at the output after a delay of length TILO.

206

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB / Slice Timing Models

Slice SRL Timing Model and Parameters (Available in SLICEM only)

Figure 5-29 illustrates shift register implementation in a Virtex-5 FPGA slice. Some elements of the slice have been omitted for clarity. Only the elements relevant to the timing paths described in this section are shown.
X-Ref Target - Figure 5-29

SRL
DX D address DI1 O6 6 A CLK CLK W MC31 WE D

SRL
DI1 CX C address 6 A CLK O6 MC31 WE C

SRL
DI1 BX B address 6 A CLK O6 MC31 WE B

SRL
DI1 AX A address 6 A CLK O6 MC31 WE A DMUX

UG190_5_29_050506

Figure 5-29:

Simplified Virtex-5 FPGA Slice SRL

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

207

Chapter 5: Configurable Logic Blocks (CLBs)

Slice SRL Timing Parameters

Table 5-9 shows the SLICEM SRL timing parameters for a majority of the paths in Figure 5-29. Table 5-9: Slice SRL Timing Parameters
Parameter Function Description

Sequential Delays for a Slice LUT Configured as an SRL TREG(1) CLK to A/B/C/D outputs Time after the CLK of a write operation that the data written to the SRL is stable on the A/B/C/D outputs of the slice.

TREG_MUX(1)

CLK to AMUX - DMUX output Time after the CLK of a write operation that the data written to the SRL is stable on the DMUX output of the slice. CLK to DMUX output via MC31 output Time after the CLK of a write operation that the data written to the SRL is stable on the DMUX output via MC31 output.

TREG_M31

Setup and Hold Times for a Slice LUT Configured SRL(2) TWS/TWH CE input (WE) Time before/after the clock that the write enable signal must be stable at the WE input of the slice LUT (configured as an SRL). Time before the clock that the data must be stable at the AX/BX/CX/DX input of the slice (configured as an SRL).

TDS/TDH(3)

AX/BX/CX/DX configured as data input (DI)

Notes:
1. This parameter includes a LUT configured as a two-bit shift register. 2. TXXCK = Setup Time (before clock edge), and TCKXX = Hold Time (after clock edge). 3. Parameter includes AI/BI/CI/DI configured as a data input (DI2) or two bits with a common shift.

Slice SRL Timing Characteristics

Figure 5-30 illustrates the timing characteristics of a 16-bit shift register implemented in a Virtex-5 FPGA slice (a LUT configured as an SRL).
X-Ref Target - Figure 5-30

1 CLK Write Enable (WE) Shift_In (DI) Address (A/B/C/D) Data Out (A/B/C/D) MSB (MC31/DMUX) X X 0 TWS TDS

32

1 0 TREG 0 TREG X 1 X

0 2 TILO 1 X 0 1 X

0 1

TILO 1 X 0 1 X 0

ug190_5_30_050506

Figure 5-30:

Slice SRL Timing Characteristics

208

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB / Slice Timing Models

Clock Event 1: Shift In

During a write (Shift In) operation, the single-bit content of the register at the address on the A/B/C/D inputs is changed, as data is shifted through the SRL. The data written to this register is reflected on the A/B/C/D outputs synchronously, if the address is unchanged during the clock event. If the A/B/C/D inputs are changed during a clock event, the value of the data at the addressable output (A/B/C/D outputs) is invalid. At time TWS before clock event 1, the write-enable signal (WE) becomes valid-High, enabling the SRL for the Write operation that follows. At time TDS before clock event 1 the data becomes valid (0) at the DI input of the SRL and is reflected on the A/B/C/D output after a delay of length TREG after clock event 1. Since the address 0 is specified at clock event 1, the data on the DI input is reflected at A/B/C/D output, because it is written to register 0.

Clock Event 2: Shift In

At time TDS before clock event 2, the data becomes valid (1) at the DI input of the SRL and is reflected on the A/B/C/D output after a delay of length TREG after clock event 2. Since the address 0 is still specified at clock event 2, the data on the DI input is reflected at the D output, because it is written to register 0.

Clock Event 3: Shift In/Addressable (Asynchronous) READ

All Read operations are asynchronous to the CLK signal. If the address is changed (between clock events), the contents of the register at that address are reflected at the addressable output (A/B/C/D outputs) after a delay of length TILO (propagation delay through a LUT). At time TDS before clock event 3, the data becomes valid (1) at the DI input of the SRL and is reflected on the A/B/C/D output TREG time after clock event 3. The address is changed (from 0 to 2). The value stored in register 2 at this time is a 0 (in this example, this was the first data shifted in), and it is reflected on the A/B/C/D output after a delay of length TILO.

Clock Event 32: MSB (Most Significant Bit) Changes

At time TREG after clock event 32, the first bit shifted into the SRL becomes valid (logical 0 in this case) on the DMUX output of the slice via the MC31 output of LUT A (SRL). This is also applicable to the AMUX, BMUX, CMUX, DMUX, and COUT outputs at time TREG and TWOSCO after clock event 1.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

209

Chapter 5: Configurable Logic Blocks (CLBs)

Slice Carry-Chain Timing Model and Parameters

Figure 5-24, page 199 illustrates a carry chain in a Virtex-5 FPGA slice. Some elements of the slice have been omitted for clarity. Only the elements relevant to the timing paths described in this section are shown.

Slice Carry-Chain Timing Parameters

Table 5-10 shows the slice carry-chain timing parameters for a majority of the paths in Figure 5-24, page 199. Table 5-10: Slice Carry-Chain Timing Parameters
Parameter Function Description

Sequential Delays for Slice LUT Configured as Carry Chain TAXCY/TBXCY/TCXCY/TDXCY AX/BX/CX/DX input to COUT output CIN input to COUT output Propagation delay from the AX/BX/CX/DX inputs of the slice to the COUT output of the slice. Propagation delay from the CIN input of the slice to the COUT output of the slice. Propagation delay from the A/B/C/D inputs of the slice to the COUT output of the slice. Propagation delay from the A/B/C/D inputs of the slice to AMUX/BMUX/CMUX/DMUX output of the slice using XOR (sum).

TBYP

TOPCYA/TOPCYB/TOPCYC/TOPCYD A/B/C/D input to COUT output TCINA/TCINB/TCINC/TCIND A/B/C/D input to AMUX/BMUX/CMUX/DMU X output

Setup and Hold Times for a Slice LUT Configured as a Carry Chain(1) TCINCK/TCKCIN CIN Data inputs Time before the CLK that data from the CIN input of the slice must be stable at the D input of the slice sequential elements (configured as a flip-flop).

Notes:
1. TXXCK = Setup Time (before clock edge), and TCKXX = Hold Time (after clock edge).

Slice Carry-Chain Timing Characteristics

Figure 5-31 illustrates the timing characteristics of a slice carry chain implemented in a Virtex-5 FPGA slice.
X-Ref Target - Figure 5-31

1 CLK CIN (DATA) SR (RESET) TCINCK

TSRCK TCKO AQ/BQ/CQ/DQ (OUT) TCKO

ug190_5_31_050506

Figure 5-31:

Slice Carry-Chain Timing Characteristics

210

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB Primitives

At time TCINCK before clock event 1, data from CIN input becomes valid-High at the D input of the slice register. This is reflected on any of the AQ/BQ/CQ/DQ pins at time TCKO after clock event 1. At time TSRCK before clock event 3, the SR signal (configured as synchronous reset) becomes valid-High, resetting the slice register. This is reflected on any of the AQ/BQ/CQ/DQ pins at time TCKO after clock event 3.

CLB Primitives
More information on the CLB primitives are available in the software libraries guide.

Distributed RAM Primitives

Seven primitives are available; from 32 x 2 bits to 256 x 1 bit. Three primitives are singleport RAM, two primitives are dual-port RAM, and two primitives are quad-port RAM, as shown in Table 5-11. Table 5-11: Single-Port, Dual-Port, and Quad-Port Distributed RAM
RAM Size 32-bit 32-bit 32-bit Type Single-port Dual-port Quad-port Address Inputs A[4:0] (read/write) A[4:0] (read/write) DPRA[4:0] (read) RAM32M ADDRA[4:0] (read) ADDRB[4:0] (read) ADDRC[4:0] (read) ADDRD[4:0] (read/write) RAM64X1S RAM64X1D RAM64M 64-bit 64-bit 64-bit Single-port Dual-port Quad-port A[5:0] (read/write) A[5:0] (read/write) DPRA[5:0] (read) ADDRA[5:0] (read) ADDRB[5:0] (read) ADDRC[5:0] (read) ADDRD[5:0] (read/write) RAM128X1S RAM128X1D RAM256X1S 128-bit 128-bit 256-bit Single-port Dual-port Single-port A[6:0] (read/write) A[6:0], (read/write) DPRA[6:0] (read) A[7:0] (read/write)

Primitive RAM32X1S RAM32X1D

The input and output data are 1-bit wide (with the exception of the 32-bit RAM). Figure 5-32 shows generic single-port, dual-port, and quad-port distributed RAM primitives. The A, ADDR, and DPRA signals are address buses.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

211

Chapter 5: Configurable Logic Blocks (CLBs)

X-Ref Target - Figure 5-32

RAM#X1S
D WE WCLK O D WE WCLK

RAM#X1D
SPO DI[A:D][#:0] WE WCLK

RAM#M
DOD[#:0]

A[#:0]

A[#:0]

R/W Port DPO

ADDRD[#:0]

R/W Port DOC[#:0]

DPRA[#:0]

Read Port

ADDRC[#:0]

Read Port

ADDRB[#:0]

Read Port

DOB[#:0]

ADDRA[#:0]

Read Port

DOA[#:0]
UG190_5_32_112108

Figure 5-32:

Single-Port, Dual-Port, and Quad-Port Distributed RAM Primitives

Instantiating several distributed RAM primitives can be used to implement wide memory blocks.

Port Signals
Each distributed RAM port operates independently of the other while reading the same set of memory cells.

Clock WCLK
The clock is used for the synchronous write. The data and the address input pins have setup times referenced to the WCLK pin.

Enable WE/WED
The enable pin affects the write functionality of the port. An active write enable prevents any writing to memory cells. An active write enable causes the clock edge to write the data input signal to the memory location pointed to by the address inputs.

Address A[#:0], DPRA[#:0], and ADDRA[#:0] ADDRD[#:0]

The address inputs A[#:0] (for single-port and dual-port), DPRA[#:0] (for dual-port), and ADDRA[#:0] ADDRD[#:0] (for quad-port) select the memory cells for read or write. The width of the port determines the required address inputs. Some of the address inputs are not buses in VHDL or Verilog instantiations. Table 5-11 summarizes the function of each address pins.

Data In D, DID[#:0]
The data input D (for single-port and dual-port) and DID[#:0] (for quad-port) provide the new data value to be written into the RAM.

Data Out O, SPO, DPO and DOA[#:0] DOD[#:0]

The data out O (single-port or SPO), DPO (dual-port), and DOA[#:0] DOD[#:0] (quadport) reflects the contents of the memory cells referenced by the address inputs. Following an active write clock edge, the data out (O, SPO, or DOD[#:0]) reflects the newly written data.

212

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB Primitives

Inverting Clock Pins

The clock pin (CLK) has an individual inversion option. The clock signal can be active at the negative edge of the clock or the positive edge for the clock without requiring other logic resources. The default is at the positive clock edge

Global Set/Reset GSR

The global set/reset (GSR) signal does not affect distributed RAM modules.

Shift Registers (SRLs) Primitive

One primitive is available for the 32-bit shift register (SRLC32E). Figure 5-33 shows the 32-bit shift register primitive.
X-Ref Target - Figure 5-33

SRLC32E
6

D A[4:0] CE

Q31 CLK
UG190_5_33_050506

Figure 5-33:

32-bit Shift Register

Instantiating several 32-bit shift register with dedicated multiplexers (F7AMUX, F7BMUX, and F8MUX) allows a cascadable shift register chain of up to 128-bit in a slice. Figure 5-18 through Figure 5-20 in the Shift Registers (Available in SLICEM only) section of this document illustrate the various implementation of cascadable shift registers greater than 32 bits.

Port Signals
Clock CLK
Either the rising edge or the falling edge of the clock is used for the synchronous shift operation. The data and clock enable input pins have setup times referenced to the chosen edge of CLK.

Data In D
The data input provides new data (one bit) to be shifted into the shift register.

Clock Enable - CE
The clock enable pin affects shift functionality. An inactive clock enable pin does not shift data into the shift register and does not write new data. Activating the clock enable allows the data in (D) to be written to the first location and all data to be shifted by one location. When available, new data appears on output pins (Q) and the cascadable output pin (Q31).

Address A[4:0]
The address input selects the bit (range 0 to 31) to be read. The nth bit is available on the output pin (Q). Address inputs have no effect on the cascadable output pin (Q31). It is always the last bit of the shift register (bit 31).

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

213

Chapter 5: Configurable Logic Blocks (CLBs)

Data Out Q
The data output Q provides the data value (1 bit) selected by the address inputs.

Data Out Q31 (optional)

The data output Q31 provides the last bit value of the 32-bit shift register. New data becomes available after each shift-in operation.

Inverting Clock Pins

The clock pin (CLK) has an individual inversion option. The clock signal can be active at the negative or positive edge of the clock without requiring other logic resources. The default is positive clock edge.

Global Set/Reset GSR

The global set/reset (GSR) signal does not affect the shift registers.

Other Shift Register Applications

Synchronous Shift Registers
The shift-register primitive does not use the register available in the same slice. To implement a fully synchronous read and write shift register, output pin Q must be connected to a flip-flop. Both the shift register and the flip-flop share the same clock, as shown in Figure 5-34.
X-Ref Target - Figure 5-34

SRLC32G
D Address CE CLK (Write Enable) Q31 Q D

FF
Q Synchronous Output

UG190_5_34_050506

Figure 5-34:

Synchronous Shift Register

This configuration provides a better timing solution and simplifies the design. Because the flip-flop must be considered to be the last register in the shift-register chain, the static or dynamic address should point to the desired length minus one. If needed, the cascadable output can also be registered in a flip-flop.

Static-Length Shift Registers

The cascadable 32-bit shift register implements any static length mode shift register without the dedicated multiplexers (F7AMUX, F7BMUX, and F8MUX). Figure 5-35 illustrates a 72-bit shift register. Only the last SRLC32E primitive needs to have its address inputs tied to 0b00111. Alternatively, shift register length can be limited to 71 bits (address tied to 0b00110) and a flip-flop can be used as the last register. (In an SRLC32E primitive, the shift register length is the address input + 1).

214

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

CLB Primitives

X-Ref Target - Figure 5-35

LUT
D D D D

LUT

Q31

Q31

SRLC32G

SRLC32G

LUT
D D

LUT

Q31

Q31

SRLC32G

SRLC32G FF

LUT
D 00111 5 A[4:0] Q31 Q OUT (72-bit SRL) D 00110 5

LUT
Q D Q A[4:0] Q31 OUT (72-bit SRL)

SRLC32G

SRLC32G
UG190_5_35_050506

Figure 5-35:

Example Static-Length Shift Register

Multiplexer Primitives
Two primitives (MUXF7 and MUXF8) are available for access to the dedicated F7AMUX, F7BMUX and F8MUX in each slice. Combined with LUTs, these multiplexer primitives are also used to build larger width multiplexers (from 8:1 to 16:1). The Designing Large Multiplexers section provides more information on building larger multiplexers.

Port Signals
Data In I0, I1
The data input provides the data to be selected by the select signal (S).

Control In S
The select input signal determines the data input signal to be connected to the output O. Logic 0 selects the I0 input, while logic 1 selects the I1 input.

Data Out O
The data output O provides the data value (one bit) selected by the control inputs.

Carry Chain Primitive

The CARRY4 primitive represents the fast carry logic for a slice in the Virtex-5 architecture. This primitive works in conjunction with LUTs in order to build adders and multipliers. This primitive is generally inferred by synthesis tools from standard RTL code. The synthesis tool can identify the arithmetic and/or logic functionality that best maps to this

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

215

Chapter 5: Configurable Logic Blocks (CLBs)

logic in terms of performance and area. It also automatically uses and connects this function properly. Figure 5-24, page 199 illustrates the CARRY4 block diagram.

Port Signals
Sum Outputs O[3:0]
The sum outputs provide the final result of the addition/subtraction.

Carry Outputs CO[3:0]

The carry outputs provide the carry out for each bit. A longer carry chain can be created if CO[3] is connected to CI input of another CARRY4 primitive.

Data Inputs DI[3:0]

The data inputs are used as generate signals to the carry lookahead logic. The generate signals are sourced from LUT outputs.

Select Inputs S[3:0]

The select inputs are used as propagate signals to the carry lookahead logic. The propagate signals are sourced from LUT outputs.

Carry Initialize CYINIT

The carry initialize input is used to select the first bit in a carry chain. The value for this pin is either 0 (for add), 1 (for subtract), or AX input (for the dynamic first carry bit).

Carry In CI
The carry in input is used to cascade slices to form longer carry chain. To create a longer carry chain, the CO[3] output of another CARRY4 is simply connected to this pin.

216

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Chapter 6

SelectIO Resources
I/O Tile Overview
Input/output characteristics and logic resources are covered in three consecutive chapters. Chapter 6, SelectIO Resources describes the electrical behavior of the output drivers and input receivers, and gives detailed examples of many standard interfaces. Chapter 7, SelectIO Logic Resources, describes the input and output data registers and their DoubleData-Rate (DDR) operation, and the programmable input delay (IDELAY). Chapter 8, Advanced SelectIO Logic Resources, describes the data serializer/deserializer (SERDES). An I/O tile contains two IOBs, two ILOGICs, two OLOGICs, and two IODELAYs. Figure 6-1 shows a Virtex-5 FPGA I/O tile.
X-Ref Target - Figure 6-1

IODELAY (Chapter 7)

ILOGIC (Chapter 7) or ISERDES (Chapter 8) IOB (Chapter 6) OLOGIC (Chapter 7) or OSERDES (Chapter 8) Pad

ILOGIC (Chapter 7) or ISERDES (Chapter 8) IOB (Chapter 6) OLOGIC (Chapter 7) or OSERDES (Chapter 8) Pad

IODELAY (Chapter 7)
ug190_6_01_041106

Figure 6-1:

Virtex-5 FPGA I/O Tile

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

217

Chapter 6: SelectIO Resources

SelectIO Resources Introduction

All Virtex-5 FPGAs have configurable high-performance SelectIO drivers and receivers, supporting a wide variety of standard interfaces. The robust feature set includes programmable control of output strength and slew rate, and on-chip termination using Digitally Controlled Impedance (DCI). Each IOB contains both input, output, and 3-state SelectIO drivers. These drivers can be configured to various I/O standards. Differential I/O uses the two IOBs grouped together in one tile. Single-ended I/O standards (LVCMOS, LVTTL, HSTL, SSTL, GTL, PCI) Differential I/O standards (LVDS, HT, LVPECL, BLVDS, Differential HSTL and SSTL) Differential and VREF dependent inputs are powered by VCCAUX

Each Virtex-5 FPGA I/O tile contains two IOBs, and also two ILOGIC blocks and two OLOGIC blocks, as described in Chapter 7, SelectIO Logic Resources. Figure 6-2 shows the basic IOB and its connections to the internal logic and the device Pad.
X-Ref Target - Figure 6-2

DIFFO_IN DIFFO_OUT

PAD

PADOUT

O OUTBUF INBUF

DIFFI_IN
ug190_6_02_021306

Figure 6-2:

Basic IOB Diagram

Each IOB has a direct connection to an ILOGIC/OLOGIC pair containing the input and output logic resources for data and 3-state control for the IOB. Both ILOGIC and OLOGIC can be configured as ISERDES and OSERDES, respectively, as described in Chapter 8, Advanced SelectIO Logic Resources.

SelectIO Resources General Guidelines

This section summarizes the general guidelines to be considered when designing with the SelectIO resources in Virtex-5 FPGAs.

Virtex-5 FPGA I/O Bank Rules

In Virtex-5 devices, with some exceptions in the center column, an I/O bank consists of 40 IOBs (20 CLBs high and a single clock region). There are always four half-sized banks (20 IOBs) and a single configuration bank in the center column. The number of banks

218

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

SelectIO Resources General Guidelines

depends upon the device size, and in larger devices, there are additional full-sized banks in the center column. In the Virtex-5 Family Overview the total number of I/O banks is listed by device type. The XC5VLX30 has 12 usable I/O banks and one configuration bank. Figure 6-3 is an example of a columnar floorplan showing the XC5VLX30 I/O banks.
X-Ref Target - Figure 6-3

BANK 40 I/O BANK 20 I/O BANK 20 I/O CONFIG BANK 20 I/O BANK 40 I/O BANK 20 I/O

BANK 40 I/O

BANK 40 I/O

BANK 40 I/O

BANK 40 I/O

BANK 40 I/O

BANK 40 I/O

ug190_6_03_021306

Figure 6-3:

Virtex-5 FPGA XC5VLX30 I/O Banks

Reference Voltage (VREF) Pins

Low-voltage, single-ended I/O standards with a differential amplifier input buffer require an input reference voltage (VREF). VREF is an external input into Virtex-5 devices. Within each I/O bank, one of every 20 I/O pins is automatically configured as a VREF input, if using a single-ended I/O standard that requires a differential amplifier input buffer.

Output Drive Source Voltage (VCCO) Pins

Many of the low-voltage I/O standards supported by Virtex-5 devices require a different output drive voltage (VCCO). As a result, each device often supports multiple output drive source voltages. Output buffers within a given VCCO bank must share the same output drive source voltage. The following input buffers use the VCCO voltage: LVTTL, LVCMOS, PCI, LVDCI and other DCI standards.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

219

Chapter 6: SelectIO Resources

Virtex-5 FPGA Digitally Controlled Impedance (DCI)

Introduction
As FPGAs get bigger and system clock speeds get faster, PC board design and manufacturing becomes more difficult. With ever faster edge rates, maintaining signal integrity becomes a critical issue. PC board traces must be properly terminated to avoid reflections or ringing. To terminate a trace, resistors are traditionally added to make the output and/or input match the impedance of the receiver or driver to the impedance of the trace. However, due to increased device I/Os, adding resistors close to the device pins increases the board area and component count, and can in some cases be physically impossible. To address these issues and to achieve better signal integrity, Xilinx developed the Digitally Controlled Impedance (DCI) technology. DCI adjusts the output impedance or input termination to accurately match the characteristic impedance of the transmission line. DCI actively adjusts the impedance of the I/O to equal an external reference resistance. This compensates for changes in I/O impedance due to process variation. It also continuously adjusts the impedance of the I/O to compensate for variations of temperature and supply voltage fluctuations. In the case of controlled impedance drivers, DCI controls the driver impedance to match two reference resistors, or optionally, to match half the value of these reference resistors. DCI eliminates the need for external series termination resistors. DCI provides the parallel or series termination for transmitters or receivers. This eliminates the need for termination resistors on the board, reduces board routing difficulties and component count, and improves signal integrity by eliminating stub reflection. Stub reflection occurs when termination resistors are located too far from the end of the transmission line. With DCI, the termination resistors are as close as possible to the output driver or the input buffer, thus, eliminating stub reflections.

DCI Cascading
Previously, using DCI I/O standards in a bank required connecting external reference resistors to the VRN and VRP pins in that same bank. The VRN/VRP pins provide a reference voltage used by internal DCI circuitry to adjust the I/O output impedance to match the external reference resistors. As shown in Figure 6-4, a digital control bus is internally distributed throughout the bank to control the impedance of each I/O.
X-Ref Target - Figure 6-4

To Local Bank

DCI

VRN/VRP

UG190_6_95_019507

Figure 6-4:

DCI Use within a Bank

The Virtex-5 FPGA banks using DCI I/O standards now have the option of deriving the DCI impedance values from another DCI bank. With DCI cascading, one bank (the master bank) must have its VRN/VRP pins connected to external reference resistors. Also, at least one I/O in that bank (the master bank) must be configured as DCI. Other banks in the same column (slave banks) can use DCI standards with the same impedance as the master bank,

220

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

SelectIO Resources General Guidelines

without connecting the VRN/VRP pins on these banks to external resistors. DCI impedance control in cascaded banks is received from the master bank. When using DCI cascading, the DCI control circuitry in the master bank creates and routes DCI control to the cascaded banks in daisy-chain style. Only the master banks VRN/VRP pins are required when using DCI cascading. Also, when using DCI cascading, only one set of VRN/VRP pins provides the DCI reference voltage for multiple banks. DCI cascading: Reduces overall power, since fewer voltage references are required Frees up VRN/VRP pins on slave banks for general customer use DCI in banks 1 and 2 is supported only through cascading. These two banks do not have VRN/VRP pins and therefore cannot be used as master or stand-alone DCI banks. Cascading is not possible through bank 0.

Similarly, due to the center column architecture, the half-size banks 1, 2, 3, and 4 are separated from all the other banks in the center column by the CMT tiles. It is not possible to cascade across the CMT tiles. This affects the larger devices that have more than four user I/O center column banks (plus bank 0). For instance, bank 4 cannot be cascaded with bank 6, and bank 3 cannot be cascaded with bank 5. Bank 3 can only be cascaded with bank 1, and bank 4 can only be cascaded with bank 2. Figure 6-5 shows DCI cascading support over multiple banks. Bank B is the master bank.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

221

Chapter 6: SelectIO Resources

X-Ref Target - Figure 6-5

To Banks Above (When Cascaded)

To Local Bank

Bank A

To Local Bank

DCI

VRN/VRP

Bank B

To Local Bank

Bank C

To Banks Below (When Cascaded)

UG190_6_96_012907

Figure 6-5:

DCI Cascading Supported Over Multiple Banks

The guidelines when using DCI cascading are as follows: The master and slave banks must all reside on the same column (left, center, or right) on the device. Master and slave banks must have the same VCCO and VREF (if applicable) voltage. DCI I/O banking compatibility rules must be satisfied across all master and slave banks (for example, only one DCI I/O standard using single termination type is allowed across all master and slave banks). DCI I/O standard compatibility is not constrained to one bank when DCI cascading is implemented; it extends across all master and slave banks. DCI cascading can span the entire column as long as the above guidelines are met. Locate adjacent banks. Bank location information is best determined from partgen generated package files (partgen -v XC5VLX50TFF1136). The resulting package file with a .pkg extension contains XY I/O location information. The X designator indicates I/Os in the same column. The Y designator indicates the position of an I/O within a specific bank. The bank number is also shown. Consecutive Y locations across bank boundaries show adjacent banks. For example, the XC5VLXT in an FF1136 package shows bank 11 starting with I/O X0Y159 end ending with I/O location X0Y120. Bank 13 starts with I/O X0Y119 and ends with X0Y80. Bank 15 starts

222

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

SelectIO Resources General Guidelines

with X0Y199 and ends with X0Y160. This indicates that bank 13 is to the south of bank 11, and bank 15 is to the north. As the Y coordinates of these two banks are consecutive, these two banks are considered consecutive banks and can be DCI cascaded. It is possible to cascade through an unbonded bank. DCI cascade is enabled by using the DCI_CASCADE constraint described in the constraints guide.

Xilinx DCI
DCI uses two multi-purpose reference pins in each bank to control the impedance of the driver or the parallel termination value for all of the I/Os of that bank. The N reference pin (VRN) must be pulled up to VCCO by a reference resistor, and the P reference pin (VRP) must be pulled down to ground by another reference resistor. The value of each reference resistor should be equal to the characteristic impedance of the PC board traces, or should be twice that value. See Driver with Termination to VCCO /2 (Split Termination), page 228. When a DCI I/O standard is used on a particular bank, the two multi-purpose reference pins cannot be used as regular I/Os. However, if DCI I/O standards are not used in the bank, these pins are available as regular I/O pins. The Virtex-5 Family Packaging Specifications gives detailed pin descriptions. DCI adjusts the impedance of the I/O by selectively turning transistors in the I/Os on or off. The impedance is adjusted to match the external reference resistors. The impedance adjustment process has two phases. The first phase compensates for process variations by controlling the larger transistors in the I/Os. It occurs during the device startup sequence. The second phase maintains the impedance in response to temperature and supply voltage changes by controlling the smaller transistors in the I/Os. It begins immediately after the first phase and continues indefinitely, even while the device is operating. By default, the DONE pin does not go High until the first phase of the impedance adjustment process is complete. The coarse impedance calibration during the first phase of impedance adjustment can be invoked after configuration by instantiating the DCIRESET primitive. By toggling the RST input to the DCIRESET primitive while the device is operating, the DCI state machine is reset and both phases of impedance adjustment proceed in succession. All I/Os using DCI will be unavailable until the LOCKED output from the DCIRESET block is asserted. This functionality is useful in applications where the temperature and/or supply voltage changes significantly from device power-up to the nominal operating condition. Once at the nominal operating temperature and voltage, performing the first phase of impedance adjustment allows optimal headroom for the second phase of impedance adjustment. For controlled impedance output drivers, the impedance can be adjusted either to match the reference resistors or half the resistance of the reference resistors. For on-chip termination, the termination is always adjusted to match the reference resistors. DCI can configure output drivers to be the following types: 1. 2. Controlled Impedance Driver (Source Termination) Controlled Impedance Driver with Half Impedance (Source Termination)

It can also configure inputs to have the following types of on-chip terminations: 1. 2. Input termination to VCCO (Single Termination) Input termination to VCCO/2 (Split Termination, Thevenin equivalent)

For bidirectional operation, both ends of the line can be DCI-terminated regardless of direction:

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

223

Chapter 6: SelectIO Resources

1. 2.

Driver with termination to VCCO (Single Termination) Driver with termination to VCCO/2 (Split Termination, Thevenin equivalent)

Alternatively, bidirectional point-to-point lines can use controlled-impedance drivers (with 3-state buffers) on both ends.

Controlled Impedance Driver (Source Termination)

Some I/O standards, such as LVCMOS, must have a drive impedance matching the characteristic impedance of the driven line. DCI can provide controlled impedance output drivers to eliminate reflections without an external source termination. The impedance is set by the external reference resistors with resistance equal to the trace impedance. The DCI I/O standards supporting the controlled impedance driver are: LVDCI_15, LVDCI_18, LVDCI_25, LVDCI_33, HSLVDCI_15, HSLVDCI_18, HSLVDCI_25, and HSLVDCI_33. Figure 6-6 illustrates a controlled impedance driver in a Virtex-5 device.
X-Ref Target - Figure 6-6

IOB

R Z0
Virtex-5 DCI
UG190_6_04_012706

Figure 6-6:

Controlled Impedance Driver

Controlled Impedance Driver with Half Impedance (Source Termination)

DCI also provides drivers with one half of the impedance of the reference resistors. This doubling of the reference resistor value reduces the static power consumption through these resistors by a factor of half. The DCI I/O standards supporting controlled impedance drivers with half-impedance are LVDCI_DV2_15, LVDCI_DV2_18, and LVDCI_DV2_25. Figure 6-7 illustrates a controlled driver with half impedance inside a Virtex-5 device. The reference resistors R must be 2 Z0 in order to match the impedance of Z0.
X-Ref Target - Figure 6-7

IOB

R/2 Z0
Virtex-5 DCI
UG190_6_05_021206

Figure 6-7:

Controlled Impedance Driver with Half Impedance

224

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

SelectIO Resources General Guidelines

Input Termination to VCCO (Single Termination)

Some I/O standards require an input termination to VCCO (see Figure 6-8).
X-Ref Target - Figure 6-8

VCCO
IOB

Z0

VREF
Virtex-5 FPGA
UG190_c6_06_022609

Figure 6-8:

Input Termination to VCCO without DCI

DCI can also provide input termination to VCCO using single termination. The termination resistance is set by the reference resistors. Both GTL and HSTL standards are controlled by 50 reference resistors. The DCI I/O standards supporting single termination are: GTL_DCI, GTLP_DCI, HSTL_III_DCI, HSTL_III_DCI_18, HSTL_IV_DCI, and HSTL_IV_DCI_18. Figure 6-9 illustrates DCI single termination inside a Virtex-5 device.
X-Ref Target - Figure 6-9

IOB

VCCO R

Z0

VREF
Virtex-5 DCI
UG190_6_07_021206

Figure 6-9:

Input Termination Using DCI Single Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

225

Chapter 6: SelectIO Resources

Input Termination to VCCO /2 (Split Termination)

Some I/O standards (e.g., HSTL Class I and II) require an input termination voltage of VCCO/2 (see Figure 6-10).
X-Ref Target - Figure 6-10

VCCO/2
IOB

Z0

VREF
Virtex-5 FPGA
UG190_c6_08_022609

Figure 6-10:

Input Termination to VCCO /2 without DCI

This is equivalent to having a split termination composed of two resistors. One terminates to VCCO, the other to ground. The resistor values are 2R. DCI provides termination to VCCO/2 using split termination. The termination resistance is set by the external reference resistors, i.e., the resistors to VCCO and ground are each twice the reference resistor value. Both HSTL and SSTL standards need 50 external reference resistors. The DCI input standards supporting split termination are shown in Table 6-1. Table 6-1: DCI Input Standards Supporting Split Termination
DIFF_HSTL_I_DCI DIFF_HSTL_I_DCI_18 DIFF_HSTL_II_DCI DIFF_HSTL_II_DCI_18 SSTL2_I_DCI SSTL2_II_DCI SSTL18_I_DCI SSTL18_II_DCI SSTL2_II_T_DCI SSTL18_II_T_DCI DIFF_SSTL2_I_DCI DIFF_SSTL2_II_DCI DIFF_SSTL18_I_DCI DIFF_SSTL18_II_DCI HSTL_I_DCI HSTL_I_DCI_18 HSTL_II_DCI HSTL_II_DCI_18 HSTL_II_T_DCI HSTL_II_T_DCI_18

226

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

SelectIO Resources General Guidelines

Figure 6-11 illustrates split termination inside a Virtex-5 device.

X-Ref Target - Figure 6-11

IOB

VCCO 2R

Z0 2R

VREF

Virtex-5 DCI
UG190_6_09_021206

Figure 6-11:

Input Termination to VCCO /2 Using DCI Split Termination

Driver with Termination to VCCO (Single Termination)

Some I/O standards (e.g., HSTL Class IV) require an output termination to VCCO. Figure 6-12 illustrates an output termination to VCCO.
X-Ref Target - Figure 6-12

VCCO
IOB

Z0
Virtex-5 FPGA
UG190_c6_10_022609

Figure 6-12:

Driver with Termination to VCCO without DCI

DCI can provide an output termination to VCCO using single termination. In this case, DCI only controls the impedance of the termination, but not the driver. Both GTL and HSTL standards need 50 external reference resistors. The DCI I/O standards supporting drivers with single termination are: GTL_DCI, GTLP_DCI, HSTL_IV_DCI, and HSTL_IV_DCI_18.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

227

Chapter 6: SelectIO Resources

Figure 6-13 illustrates a driver with single termination inside a Virtex-5 device.
X-Ref Target - Figure 6-13

VCCO R

IOB

Z0
Virtex-5 DCI
UG190_6_11_021206

Figure 6-13: Driver with Termination to VCCO Using DCI Single Termination

Driver with Termination to VCCO /2 (Split Termination)

Some I/O standards, such as HSTL Class II, require an output termination to VCCO/2 (see Figure 6-14).
X-Ref Target - Figure 6-14

VCCO/2
IOB

Z0
Virtex-5 FPGA
UG190_c6_12_022609

Figure 6-14:

Driver with Termination to VCCO /2 without DCI

DCI can provide output termination to VCCO/2 using split termination. DCI only controls the impedance of the termination, but not the driver. Both HSTL and SSTL standards need 50 external reference resistors. The DCI output standards supporting drivers with split termination are shown in Table 6-2. Table 6-2: DCI Output Standards Supporting Split Termination
DIFF_HSTL_II_DCI DIFF_HSTL_II_DCI_18 SSTL2_II_DCI SSTL18_II_DCI DIFF_SSTL2_II_DCI DIFF_SSTL18_II_DCI HSTL_II_DCI HSTL_II_DCI_18

228

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

SelectIO Resources General Guidelines

Figure 6-15 illustrates a driver with split termination inside a Virtex-5 device.
X-Ref Target - Figure 6-15

VCCO

IOB

2R

Z0 2R

Virtex-5 DCI
UG190_6_13_021206

Figure 6-15:

Driver with Termination to VCCO /2 Using DCI Split Termination

DCI in Virtex-5 Device I/O Standards

DCI works with single-ended I/O standards. DCI supports the standards shown in Table 6-3. Table 6-3:
LVDCI HSLVDCI

Virtex-5 Device DCI I/O Standards

HSTL_I_DCI HSTL_I_DCI_18 DIFF_HSTL_I_DCI DIFF_HSTL_I_DCI_18 DIFF_HSTL_II_DCI DIFF_HSTL_II_DCI_18 HSTL_III_DCI HSTL_III_DCI_18 HSTL_IV_DCI HSTL_IV_DCI_18 SSTL2_I_DCI SSTL2_II_DCI SSTL18_I_DCI SSTL18_II_DCI SSTL2_II_T_DCI SSTL18_II_T_DCI DIFF_SSTL2_I_DCI DIFF_SSTL2_II_DCI DIFF_SSTL18_I_DCI DIFF_SSTL18_II_DCI

LVDCI_DV2 HSTL_II_DCI GTL_DCI GTLP_DCI HSTL_II_DCI_18 HSTL_II_T_DCI HSTL_II_T_DCI_18

To correctly use DCI in a Virtex-5 device, users must follow the following rules: 1. 2. 3. VCCO pins must be connected to the appropriate VCCO voltage based on the IOSTANDARDs in that bank. Correct DCI I/O buffers must be used in the software either by using IOSTANDARD attributes or instantiations in the HDL code. Some DCI standards require connecting the external reference resistors to the multipurpose pins (VRN and VRP) in the bank. Where this is required, these two multipurpose pins cannot be used as general-purpose I/O. Refer to the Virtex-5 FPGA pinout tables for the specific pin locations. Pin VRN must be pulled up to VCCO by its reference resistor. Pin VRP must be pulled down to ground by its reference resistor. Some DCI standards do not require connecting the external reference resistors to the VRP/VRN pins. When these DCI-based I/O standards are the only ones in a bank, the the VRP and VRN pins in that bank can be used as general-purpose I/O.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

229

Chapter 6: SelectIO Resources

DCI outputs that do not require reference resistors on VRP/VRN: HSTL_I_DCI HSTL_III_DCI HSTL_I_DCI_18 HSTL_III_DCI_18 SSTL2_I_DCI SSTL18_I_DCI

DCI inputs that do not require reference resistors on VRP/VRN: LVDCI_15 LVDCI_18 LVDCI_25 LVDCI_33 LVDCI_DV2_15 LVDCI_DV2_18 LVDCI_DV2_25

4.

The value of the external reference resistors should be selected to give the desired output impedance. If using GTL_DCI, HSTL_DCI, or SSTL_DCI I/O standards, then the external reference resistors should be 50 . The values of the reference resistors must be within the supported range (20 100 ). Follow the DCI I/O banking rules: a. b. c. VREF must be compatible for all of the inputs in the same bank. VCCO must be compatible for all of the inputs and outputs in the same bank. No more than one DCI I/O standard using single termination type is allowed per bank.

5. 6.

d. No more than one DCI I/O standard using split termination type is allowed per bank. e. 7. Single termination and split termination, controlled impedance driver, and controlled impedance driver with half impedance can co-exist in the same bank.

Master DCI is not supported in Banks 1 and 2.

The behavior of a DCI 3-state outputs is as follows: If a LVDCI or LVDCI_DV2 driver is in 3-state, the driver is 3-stated. If a driver with single or split termination is in 3-state, the driver is 3-stated but the termination resistor remains. The following section lists actions that must be taken for each DCI I/O standard.

DCI Usage Examples

Figure 6-16 provides examples illustrating the use of the HSTL_I_DCI, HSTL_II_DCI, HSTL_III_DCI, and HSTL_IV_DCI I/O standards. Figure 6-17 provides examples illustrating the use of the SSTL2_I_DCI and SSTL2_II_DCI I/O standards.

230

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

SelectIO Resources General Guidelines

X-Ref Target - Figure 6-16

HSTL_I

HSTL_II

HSTL_III

HSTL_IV

VCCO/2

VCCO/2 R Z0

VCCO/2 R Z0

VCCO R

VCCO R Z0

VCCO R

Conventional

R Z0

VCCO/2

VCCO 2R Z0 2R Virtex-5 DCI

VCCO/2 R Z0 Virtex-5 DCI

DCI Transmit Conventional Receive

Virtex-5 DCI

VCCO R

VCCO R Z0 Virtex-5 DCI

VCCO R

R Z0

VCCO

VCCO/2 R Z0

VCCO 2R Z0 Virtex-5 DCI VCCO R 2R Virtex-5 DCI VCCO R Z0 Virtex-5 DCI VCCO R

Conventional Transmit DCI Receive

2R Z0 2R Virtex-5 DCI

VCCO 2R

VCCO 2R Z0 2R Virtex-5 DCI

VCCO 2R Z0 Virtex-5 DCI Virtex-5 DCI VCCO R 2R Virtex-5 DCI VCCO R Z0 Virtex-5 DCI VCCO R

DCI Transmit DCI Receive

Z0 2R Virtex-5 DCI

VCCO 2R Z0

VCCO 2R 2R Virtex-5 DCI

VCCO R

VCCO R Z0

Bidirectional

N/A

2R Virtex-5 DCI

N/A
Virtex-5 DCI

Virtex-5 DCI

Reference Resistor

VRN = VRP = R = Z0 50

VRN = VRP = R = Z0 50

VRN = VRP = R = Z0 50

VRN = VRP = R = Z0 50

Recommended Z0

Notes: 1. Z0 is the recommended PCB trace impedance.

ug190_6_14_021206

Figure 6-16:

HSTL DCI Usage Examples

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

231

Chapter 6: SelectIO Resources

X-Ref Target - Figure 6-17

SSTL2_I or SSTL18_I
VCCO/2 R

SSTL2_II or SSTL18_II

VCCO/2 R

VCCO/2 R Z0

Conventional

R/2

Z0 R/2

VCCO/2

VCCO 25(1) 2R Z0 2R

VCCO/2 R

DCI Transmit Conventional Receive

25(1) Z0 Virtex-5 DCI

Virtex-5 DCI

VCCO

VCCO/2 R Z0 R/2

VCCO 2R

Conventional Transmit DCI Receive

2R Z0 R/2 2R Virtex-5 DCI

2R Virtex-5 DCI

25(1)

VCCO 2R Z0 25(1)

VCCO 2R Z0 2R Virtex-5 DCI

VCCO 2R

DCI Transmit DCI Receive

Virtex-5 DCI

2R Virtex-5 DCI

2R Virtex-5 DCI

VCCO 25(1) 2R Z0

VCCO 2R 2R 25 Virtex-5 DCI

Bidirectional

N/A
Virtex-5 DCI

2R

Reference Resistor

VRN = VRP = R = Z0 50

VRN = VRP = R = Z0 50

Recommended Z0(2)

Notes: 1. The SSTL-compatible 25 or 20 series resistor is accounted for in the DCI buffer, and it is not DCI controlled. 2. Z0 is the recommended PCB trace impedance. ug190_6_15_041106

Figure 6-17:

SSTL DCI Usage Examples

232

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Virtex-5 FPGA SelectIO Primitives

Virtex-5 FPGA SelectIO Primitives

The Xilinx software library includes an extensive list of primitives to support a variety of I/O standards available in the Virtex-5 FPGA I/O primitives. The following are five generic primitive names representing most of the available single-ended I/O standards. IBUF (input buffer) IBUFG (clock input buffer) OBUF (output buffer) OBUFT (3-state output buffer) IOBUF (input/output buffer)

These six generic primitive names represent most of the available differential I/O standards: IBUFDS (input buffer) IBUFGDS (clock input buffer) OBUFDS (output buffer) OBUFTDS (3-state output buffer) IOBUFDS (input/output buffer) IBUFDS_DIFF_OUT (input buffer)

IBUF and IBUFG

Signals used as inputs to Virtex-5 devices must use an input buffer (IBUF). The generic Virtex-5 FPGA IBUF primitive is shown in Figure 6-18.
X-Ref Target - Figure 6-18

IBUF/IBUFG
I (Input) From device pad O (Output) into FPGA

ug190_6_16_022806

Figure 6-18:

Input Buffer (IBUF/IBUFG) Primitives

The IBUF and IBUFG primitives are the same. IBUFGs are used when an input buffer is used as a clock input. In the Xilinx software tools, an IBUFG is automatically placed at clock input sites.

OBUF
An output buffer (OBUF) must be used to drive signals from Virtex-5 devices to external output pads. A generic Virtex-5 FPGA OBUF primitive is shown in Figure 6-19.
X-Ref Target - Figure 6-19

OBUF
I (Input) From FPGA O (Output) to device pad
ug190_6_17_022806

Figure 6-19: Output Buffer (OBUF) Primitive

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

233

Chapter 6: SelectIO Resources

OBUFT
The generic 3-state output buffer OBUFT, shown in Figure 6-20, typically implements 3-state outputs or bidirectional I/O.
X-Ref Target - Figure 6-20

T 3-state input I (Input) From FPGA

OBUFT

O (Output) to device pad

ug190_6_18_022806

Figure 6-20:

3-State Output Buffer (OBUFT) Primitive

IOBUF
The IOBUF primitive is needed when bidirectional signals require both an input buffer and a 3-state output buffer with an active High 3-state pin. Figure 6-21 shows a generic Virtex-5 FPGA IOBUF.
X-Ref Target - Figure 6-21

IOBUF
T 3-state input I (Input) from FPGA I/O to/from device pad

O (Output) to FPGA
ug190_6_19_022806

Figure 6-21:

Input/Output Buffer (IOBUF) Primitive

IBUFDS and IBUFGDS

The usage and rules corresponding to the differential primitives are similar to the singleended SelectIO primitives. Differential SelectIO primitives have two pins to and from the device pads to show the P and N channel pins in a differential pair. N channel pins have a B suffix. Figure 6-22 shows the differential input buffer primitive
X-Ref Target - Figure 6-22

IBUFDS/IBUFGDS I IB
Inputs from device pads ug190_6_20_022806

Output to FPGA

Figure 6-22:

Differential Input Buffer Primitive (IBUFDS/IBUFGDS)

234

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Virtex-5 FPGA SelectIO Primitives

IBUFDS_DIFF_OUT
Figure 6-23 shows the differential input buffer primitive with a complementary output (OB). This primitive is for expert users only.
X-Ref Target - Figure 6-23

IBUFDS_DIFF_OUT
I Input from Device Pad IB O OB Output into FPGA

UG190_6_97_122208

Figure 6-23:

Differential Input Buffer Primitive (IBUFDS_DIFF_OUT)

OBUFDS
Figure 6-24 shows the differential output buffer primitive.
X-Ref Target - Figure 6-24

OBUFDS

I
Input from FPGA

O
Output to Device Pads

OB
ug190_6_21_022806

Figure 6-24:

Differential Output Buffer Primitive (OBUFDS)

OBUFTDS
Figure 6-25 shows the differential 3-state output buffer primitive.
X-Ref Target - Figure 6-25

OBUFTDS
3-state Input

I
Input from FPGA

O
Output to Device Pads

OB
ug190_6_22_022806

Figure 6-25:

Differential 3-state Output Buffer Primitive (OBUFTDS)

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

235

Chapter 6: SelectIO Resources

IOBUFDS
Figure 6-26 shows the differential input/output buffer primitive.
X-Ref Target - Figure 6-26

IOBUFDS
T 3-state Input I (Input) from FPGA

IO I/O to/from IOB device pad

O (Output) to FPGA

+
ug190_6_23_022806

Figure 6-26:

Differential Input/Output Buffer Primitive (IOBUFDS)

Virtex-5 FPGA SelectIO Attributes/Constraints

Access to some Virtex-5 FPGA I/O resource features (e.g., location constraints, input delay, output drive strength, and slew rate) is available through the attributes/constraints associated with these features. For more information a Constraints Guide is available on the Xilinx website with syntax examples and VHDL/Verilog reference code. This guide is available inside the Software Manuals at: http://www.support.xilinx.com/support/software_manuals.htm

Location Constraints
The location constraint (LOC) must be used to specify the I/O location of an instantiated I/O primitive. The possible values for the location constraint are all the external port identifiers (e.g., A8, M5, AM6, etc.). These values are device and package size dependent. The LOC attribute uses the following syntax in the UCF file:
INST <I/O_BUFFER_INSTANTIATION_NAME> LOC = "<EXTERNAL_PORT_IDENTIFIER>";

Example:
INST MY_IO LOC=R7;

IOSTANDARD Attribute
The IOSTANDARD attribute is available to choose the values for an I/O standard for all I/O buffers. The supported I/O standards are listed in Table 6-39. The IOSTANDARD attribute uses the following syntax in the UCF file:
INST <I/O_BUFFER_INSTANTIATION_NAME> IOSTANDARD=<IOSTANDARD VALUE>;

The IOSTANDARD default for single-ended I/O is LVCMOS25, for differential I/Os the default is LVDS_25.

236

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Virtex-5 FPGA SelectIO Primitives

Output Slew Rate Attributes

A variety of attribute values provide the option of choosing the desired slew rate for single-ended I/O output buffers. For LVTTL and LVCMOS output buffers (OBUF, OBUFT, and IOBUF), the desired slew rate can be specified with the SLEW attribute. The allowed values for the SLEW attribute are: SLEW = SLOW (Default) SLEW = FAST

The SLEW attribute uses the following syntax in the UCF file:
INST <I/O_BUFFER_INSTANTIATION_NAME> SLEW = "<SLEW_VALUE>";

By the default, the slew rate for each output buffer is set to SLOW. This is the default used to minimize the power bus transients when switching non-critical signals.

Output Drive Strength Attributes

For LVTTL and LVCMOS output buffers (OBUF, OBUFT, and IOBUF), the desired drive strength (in mA) can be specified with the DRIVE attribute. The allowed values for the DRIVE attribute are: DRIVE = 2 DRIVE = 4 DRIVE = 6 DRIVE = 8 DRIVE = 12 (Default) DRIVE = 16 DRIVE = 24

LVCMOS12 only supports the 2, 4, 6, 8 mA DRIVE settings. LVCMOS15 and LVCMOS18 only support the 2, 4, 6, 8, 12, and 16 mA DRIVE settings. The DRIVE attribute uses the following syntax in the UCF file:
INST <I/O_BUFFER_INSTANTIATION_NAME> DRIVE = "<DRIVE_VALUE>";

PULLUP/PULLDOWN/KEEPER for IBUF, OBUFT, and IOBUF

When using 3-state output (OBUFT) or bidirectional (IOBUF) buffers, the output can have a weak pull-up resistor, a weak pull-down resistor, or a weak keeper circuit. For input (IBUF) buffers, the input can have either a weak pull-up resistor or a weak pull-down resistor. This feature can be invoked by adding the following possible constraint values to the relevant net of the buffers: PULLUP PULLDOWN KEEPER

Differential Termination Attribute

The differential termination (DIFF_TERM) attribute is designed for the Virtex-5 FPGA supported differential input I/O standards. It is used to turn the built-in, 100, differential termination on or off.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

237

Chapter 6: SelectIO Resources

The allowed values for the DIFF_TERM attribute are: TRUE FALSE (Default)

To specify the DIFF_TERM attribute, set the appropriate value in the generic map (VHDL) or inline parameter (Verilog) of the instantiated IBUFDS or IBUGDS component. Please refer to the ISE Language Templates or the Virtex-5 FPGA HDL Libraries Guide for the proper syntax for instantiating this component and setting the DIFF_TERM attribute.

Virtex-5 FPGA I/O Resource VHDL/Verilog Examples

The VHDL and Verilog example syntaxes to declare a standard for Virtex-5 FPGA I/O resources are found in the Virtex-5 FPGA Libraries Guide.

238

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Specific Guidelines for I/O Supported Standards

The following subsections provide an overview of the I/O standards supported by all Virtex-5 devices. While most Virtex-5 FPGA I/O supported standards specify a range of allowed voltages, this chapter records typical voltage values only. Detailed information on each specification can be found on the Electronic Industry Alliance JEDEC web site at http://www.jedec.org.

LVTTL (Low Voltage Transistor-Transistor Logic)

The low-voltage TTL (LVTTL) standard is a general purpose EIA/JESDSA standard for 3.3V applications using an LVTTL input buffer and a push-pull output buffer. This standard requires a 3.3V input and output supply voltage (VCCO), but does not require the use of a reference voltage (VREF) or a termination voltage (VTT). Sample circuits illustrating both unidirectional and bidirectional LVTTL termination techniques are shown in Figure 6-27 and Figure 6-28.
X-Ref Target - Figure 6-27

IOB LVTTL Z0

IOB LVTTL

IOB LVTTL RS = Z0 RD Z0

IOB LVTTL

IOB LVTTL RP = Z0 Z0

VTT

IOB LVTTL

Note: VTT is any voltage from 0V to VCCO

ug190_6_24_022806

Figure 6-27:

LVTTL Unidirectional Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

239

Chapter 6: SelectIO Resources

X-Ref Target - Figure 6-28

IOB LVTTL Z0

IOB LVTTL

IOB LVTTL

VTT RP = Z0 Z0 RP = Z0

VTT

IOB LVTTL

Note: VTT is any voltage from 0V to VCCO

ug190_6_25_022806

Figure 6-28:

LVTTL Bidirectional Termination

Table 6-4 lists the LVTTL DC voltage specifications. Table 6-4: LVTTL DC Voltage Specifications
Min 3.0 2.0 0.2 2.4 Note 2 Note 2 Typ 3.3 Max 3.45 3.45 0.8 0.4 Parameter VCCO VREF VTT VIH VIL VOH VOL IOH at VOH (mA) IOLat VOL (mA)
Notes:
1. VOL and VOH for lower drive currents are sample tested. 2. Supported DRIVE strengths are 2, 4, 6, 8, 12, 16, and 24 mA

240

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Table 6-5 details the allowed attributes that can be applied to the LVTTL I/O standard. Table 6-5: Allowed Attributes for the LVTTL I/O Standard
Primitives Attributes IBUF/IBUFG IOSTANDARD DRIVE SLEW LVTTL UNUSED UNUSED OBUF/OBUFT LVTTL 2, 4, 6, 8, 12, 16, 24 {FAST, SLOW} IOBUF LVTTL 2, 4, 6, 8, 12, 16, 24 {FAST, SLOW}

LVCMOS (Low Voltage Complementary Metal Oxide Semiconductor)

LVCMOS is a widely used switching standard implemented in CMOS transistors. This standard is defined by JEDEC (JESD 8-5). The LVCMOS standards supported in Virtex-5 FPGAs are: LVCMOS12, LVCMOS15, LVCMOS18, LVCMOS25, and LVCMOS33. Sample circuits illustrating both unidirectional and bidirectional LVCMOS termination techniques are shown in Figure 6-29 and Figure 6-30.
X-Ref Target - Figure 6-29

IOB LVCMOS Z0

IOB LVCMOS

IOB LVCMOS RS = Z0 RD Z0

IOB LVCMOS

IOB LVCMOS RP = Z0 Z0

VTT

IOB LVCMOS

Note: VTT is any voltage from 0V to VCCO

ug190_6_26_022806

Figure 6-29:

LVCMOS Unidirectional Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

241

Chapter 6: SelectIO Resources

X-Ref Target - Figure 6-30

IOB LVCMOS Z0

IOB LVCMOS

IOB LVCMOS

VTT RP = Z0 Z0 RP = Z0

VTT

IOB LVCMOS

Note: VTT is any voltage from 0V to VCCO

ug190_6_27_022806

Figure 6-30:

LVCMOS Bidirectional Termination

Table 6-6 details the allowed attributes that can be applied to the LVCMOS33 and LVCMOS25 I/O standards. Table 6-6: Allowed Attributes for the LVCMOS33 and LVCMOS25 I/O Standards
Primitives Attributes IBUF/IBUFG IOSTANDARD DRIVE SLEW LVCMOS33 LVCMOS25 UNUSED UNUSED OBUF/OBUFT LVCMOS33 LVCMOS25 2, 4, 6, 8, 12, 16, 24 {FAST, SLOW} IOBUF LVCMOS33 LVCMOS25 2, 4, 6, 8, 12, 16, 24 {FAST, SLOW}

Table 6-7 details the allowed attributes that can be applied to the LVCMOS18 and LVCMOS15 I/O standards. Table 6-7: Allowed Attributes for the LVCMOS18 and LVCMOS15 I/O Standard
Primitives Attributes IBUF/IBUFG IOSTANDARD DRIVE SLEW LVCMOS18 LVCMOS15 UNUSED UNUSED OBUF/OBUFT LVCMOS18 LVCMOS15 2, 4, 6, 8, 12, 16 {FAST, SLOW} IOBUF LVCMOS18 LVCMOS15 2, 4, 6, 8, 12, 16 {FAST, SLOW}

242

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Table 6-8 details the allowed attributes that can be applied to the LVCMOS12 I/O standard. Table 6-8: Allowed Attributes for the LVCMOS12 I/O Standard
Primitives Attributes IBUF/IBUFG IOSTANDARD DRIVE SLEW LVCMOS12 UNUSED UNUSED OBUF/OBUFT LVCMOS12 2, 4, 6, 8 {FAST, SLOW} IOBUF LVCMOS12 2, 4, 6, 8 {FAST, SLOW}

LVDCI (Low Voltage Digitally Controlled Impedance)

Using these I/O buffers configures the outputs as controlled impedance drivers. The receiver of LVDCI is identical to a LVCMOS receiver. Some I/O standards, such as LVTTL, LVCMOS, etc., must have a drive impedance that matches the characteristic impedance of the driven line. Virtex-5 devices provide a controlled impedance output driver to provide series termination without external source termination resistors. The impedance is set by the common external reference resistors, with resistance equal to the trace characteristic impedance, Z0. Sample circuits illustrating both unidirectional and bidirectional termination techniques for a controlled impedance driver are shown in Figure 6-31 and Figure 6-32. The DCI I/O standards supporting a controlled impedance driver are: LVDCI_15, LVDCI_18, LVDCI_25, and LVDCI_33.
X-Ref Target - Figure 6-31

IOB LVDCI Z0
R0 = RVRN = RVRP = Z0

IOB LVDCI

ug190_6_28_022806

Figure 6-31:
X-Ref Target - Figure 6-32

Controlled Impedance Driver with Unidirectional Termination

IOB

IOB LVDCI Z0

LVDCI

R0 = RVRN = RVRP = Z0

R0 = RVRN = RVRP = Z0

ug190_6_29_022806

Figure 6-32:

Controlled Impedance Driver with Bidirectional Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

243

Chapter 6: SelectIO Resources

LVDCI_DV2
A controlled impedance driver with half impedance (source termination) can also provide drivers with one half of the impedance of the reference resistors. This allows reference resistors to be twice as large, thus reducing static power consumption through VRN/VRP. The I/O standards supporting a controlled impedance driver with half impedance are: LVDCI_DV2_15, LVDCI_DV2_18, and LVDCI_DV2_25. Figure 6-33 and Figure 6-34 illustrate a controlled driver with half impedance unidirectional and bidirectional termination. To match the drive impedance to Z0 when using a driver with half impedance, the reference resistor R must be twice Z0.
X-Ref Target - Figure 6-33

IOB LVDCI_DV2 Z0
R0 = RVRN = RVRP = Z0

IOB LVDCI_DV2

ug190_6_30_022806

Figure 6-33:

Controlled Impedance Driver with Half Impedance Unidirectional Termination

IOB

X-Ref Target - Figure 6-34

IOB LVDCI_DV2 Z0

LVDCI_DV2

R0 = RVRN = RVRP = Z0

R0 = RVRN = RVRP = Z0

ug190_6_31_022806

Figure 6-34:

Controlled Impedance Driver with Half Impedance Bidirectional Termination

There are no drive strength settings for LVDCI drivers. When the driver impedance is onehalf of the VRN/VRP reference resistors, it is indicated by the addition of DV2 to the attribute name. Table 6-9 lists the LVCMOS, LVDCI, and LVDCI_DV2 voltage specifications.

244

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Table 6-9: LVCMOS, LVDCI, and LVDCI_DV2 DC Voltage Specifications at Various Voltage References
+3.3V Standard Min Typ VCCO [V] VIH [V] 3.0 2.0 0.2 2.6 3.3 Max 3.45 3.45 0.8 0.4 5 Min Typ 2.3 1.7 0.3 1.9 2.5 Max 2.7 VCCO+ 0.3 0.7 0.4 5 Min 1.7 1.105 0.3 1.25 Typ 1.8 Max 1.9 VCCO+ 0.3 0.665 0.45 5 Min Typ 1.4 0.91 0.3 1.05 1.5 Max 1.6 Min 1.1 Typ 1.2 Max 1.3 VCCO +0.3 0.455 0.325 10 +2.5V +1.8V +1.5V +1.2V(2)

VCCO+ 0.715 0.3 0.56 0.825 0.4 10 0.3

VIL [V]
VOH [V] VOL [V] IIN [A]
Notes:

1. VOL and VOH for lower drive currents are sample tested. 2. Only LVCMOS is supported at + 1.2V with valid DRIVE attributes of 2, 4, 6, 8.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

245

Chapter 6: SelectIO Resources

HSLVDCI (High-Speed Low Voltage Digitally Controlled Impedance)

The HSLVDCI standard is intended for bidirectional use. The driver is identical to LVDCI, while the input is identical to HSTL and SSTL. By using a VREF-referenced input, HSLVDCI allows greater input sensitivity at the receiver than when using a single-ended LVCMOS-type receiver. A sample circuit illustrating bidirectional termination techniques for an HSLVDCI controlled impedance driver is shown in Figure 6-35. The DCI I/O standards supporting a controlled impedance driver with a VREF referenced input are: HSLVDCI_15, HSLVDCI_18, HSLVDCI_25, and HSLVDCI_33.
X-Ref Target - Figure 6-35

IOB HSLVDCI

IOB HSLVDCI Z0 + VREF = VCCO/2

R0 = RVRN = RVRP = Z0

R0 = RVRN = RVRP = Z0

ug190_6_33_022806

Figure 6-35:

HSLVDCI Controlled Impedance Driver with Bidirectional Termination

For output DC voltage specifications, refer to the LVDCI VOH and VOL entries in Table 6-9 LVCMOS, LVDCI, and LVDCI_DV2 DC Voltage Specifications at Various Voltage References. Table 6-10 lists the input DC voltage specifications when using HSLVDCI. Valid values of VCCO are 1.5V, 1.8V, 2.5V, and 3.3V. Select VREF to provide the optimum noise margin in specific use conditions. Table 6-10: HSLVDCI Input DC Voltage Specifications
Min VREF + 0.1 Typ VCCO/2 Max VREF 0.1 Standard VREF VIH VIL

246

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

PCI-X, PCI-33, PCI-66 (Peripheral Component Interconnect)

The PCI standard specifies support for 33 MHz and 66 MHz bus applications. The PCI-X standard specifies support for 66 MHz and 133 MHz bus applications. These standards use an LVTTL input buffer and a push-pull output buffer. These standards do not require the use of a reference voltage (VREF) or a board termination voltage (VTT). However, they do require 3.3V input/output source voltage (VCCO). A PCI undershoot/overshoot specification could require VCCO to be regulated at 3.0V as discussed in Regulating VCCO at 3.0V, page 304. This is not necessary if overshoot and undershoot are controlled by careful design. Table 6-11 and Table 6-12 lists the DC voltage specifications. Table 6-11: PCI33_3, PCI66_3 Voltage Specifications(2)
Parameter VCCO VREF VTT VIH = 0.5 VCCO VIL = 0.3 VCCO VOH = 0.9 VCCO VOL = 0.1 VCCO IOH at VOH (mA) IOL at VOL (mA)
Notes:
1. Tested according to the relevant specification. 2. For complete specifications, refer to the PCI specification.

Min 3.0 1.5 0.2 2.7 (Note 1) (Note 1)

Typ 3.3 1.65 0.99

Max 3.5 VCCO 1.05 0.35

Table 6-12:

PCI-X DC Voltage Specifications(2)

Parameter Min 3.0 1.5 0.2 2.7 (Note 1) (Note 1) Typ 3.3 1.65 1.155 Max 3.5 VCCO 1.225 0.35

VCCO VREF VTT VIH = 0.5 VCCO VIL = 0.35 VCCO VOH = 0.9 VCCO VOL = 0.1 VCCO IOH at VOH (mA) IOL at VOL (mA)
Notes:

1. Tested according to the relevant specification. 2. For complete specifications, refer to the PCI-X specification.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

247

Chapter 6: SelectIO Resources

GTL (Gunning Transceiver Logic)

The Gunning Transceiver Logic (GTL) standard is a high-speed bus standard (JESD8.3) invented by Xerox. Xilinx has implemented the terminated variation for this standard. This standard requires a differential amplifier input buffer and an open-drain output buffer. The negative terminal of the differential input buffer is referenced to the VREF pin. A sample circuit illustrating a valid termination technique for GTL with external parallel termination and unconnected VCCO is shown in Figure 6-36.
X-Ref Target - Figure 6-36

IOB

VTT = 1.2V
RP = Z0 = 50

VTT = 1.2V
RP = Z0 = 50

IOB

VCCO = Unconnected

Z0 = 50

VREF = 0.8V

ug190_6_34_022806

Figure 6-36:

GTL with External Parallel Termination and Unconnected VCCO

GTL_DCI Usage
GTL does not require a VCCO voltage. However, for GTL_DCI, VCCO must be connected to 1.2V. GTL_DCI provides single termination to VCCO for inputs or outputs. A sample circuit illustrating a valid termination technique for GTL_DCI with internal parallel driver and receiver termination is shown in Figure 6-37.
X-Ref Target - Figure 6-37

VCCO = 1.2V

IOB

IOB V CCO = 1.2V RVRP = Z0 = 50 Z0 = 50 +

RVRP = Z0 = 50

VREF = 0.8V

ug190_6_35_030206

Figure 6-37:

GTL_DCI with Internal Parallel Driver and Receiver Termination

Table 6-13 lists the GTL DC voltage specifications. Table 6-13: GTL DC Voltage Specifications
Parameter VCCO VREF = N VTT (1) VTT VIH = VREF + 0.05 VIL = VREF 0.05 VOH Min 0.74 1.14 0.79 Typ N/A 0.8 1.2 0.83 0.77 Max 0.86 1.26 0.81

248

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Table 6-13:

GTL DC Voltage Specifications (Continued)

Parameter Min 32 Typ 0.2 Max 0.4 40

VOL IOH at VOH (mA) IOL at VOL (mA) at 0.4V IOL at VOL (mA) at 0.2V
Notes:

1. N must be greater than or equal to 0.653 and less than or equal to 0.68.

GTLP (Gunning Transceiver Logic Plus)

The Gunning Transceiver Logic Plus, or GTL+ standard is a high-speed bus standard (JESD8.3) first used by the Pentium Pro Processor. This standard requires a differential amplifier input buffer and a open-drain output buffer. The negative terminal of the differential input buffer is referenced to the VREF pin. A sample circuit illustrating a valid termination technique for GTL+ with external parallel termination and unconnected VCCO is shown in Figure 6-38.
X-Ref Target - Figure 6-38

IOB VCCO = Unconnected

VTT = 1.5V
RP = Z0 = 50

VTT = 1.5V
RP = Z0 = 50 Z0 = 50

IOB

VREF = 1.0V

ug190_6_36_030206

Figure 6-38:

GTL+ with External Parallel Termination and Unconnected VCCO

GTLP_DCI Usage
GTL+ does not require a VCCO voltage. However, for GTLP_DCI, VCCO must be connected to 1.5V. GTLP_DCI provides single termination to VCCO for inputs or outputs. A sample circuit illustrating a valid termination technique for GTLP_DCI with internal parallel driver and receiver termination is shown in Figure 6-39.
X-Ref Target - Figure 6-39

VCCO = 1.5V 50

IOB

IOB V CCO = 1.5V RVRP = Z0 = 50 Z0 = 50 +

VREF = 1.0V

ug190_6_37_030206

Figure 6-39: GTLP_DCI Internal Parallel Driver and Receiver Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

249

Chapter 6: SelectIO Resources

Table 6-14 lists the GTLP DC voltage specifications. Table 6-14: GTLP DC Voltage Specifications
Min VCCO VREF = N VTT (1) VTT VIH = VREF + 0.1 VIL = VREF 0.1 VOH VOL IOH at VOH (mA) IOL at VOL (mA) at 0.6V IOL at VOL (mA) at 0.3V
Notes:
1. N must be greater than or equal to 0.653 and less than or equal to 0.68.

Typ 1.0 1.5 1.1 0.9 0.45

Max 1.12 1.65 1.02 0.6 48

0.88 1.35 0.98 0.3 36

HSTL (High-Speed Transceiver Logic)

The High-Speed Transceiver Logic (HSTL) standard is a general-purpose high-speed bus standard sponsored by IBM (EIA/JESD8-6). The 1.5V and 1.8V have four variations or classes. To support clocking high-speed memory interfaces, a differential version of this standard was added. Virtex-5 FPGA I/O supports all four classes for 1.5V and 1.8V and the differential versions of classes I and II. These differential versions of the standard require a differential amplifier input buffer and a push-pull output buffer.

HSTL_ I, HSTL_ III, HSTL_ I_18, HSTL_ III_18, HSTL_I_12

HSTL_I uses VCCO/2 as a parallel termination voltage (VTT). HSTL_III uses VCCO as a parallel termination voltage (VTT). HSTL_I and HSTL_III are intended to be used in unidirectional links.

HSTL_ I_DCI, HSTL_ III_DCI, HSTL_ I_DCI_18, HSTL_ III_DCI_18

HSTL_I_DCI provides on-chip split thevenin termination powered from VCCO, creating an equivalent parallel termination voltage (VTT) of VCCO/2. HSTL_III_DCI provides on-chip single termination powered from VCCO. HSTL_I_DCI and HSTL_III_DCI are intended to be used in unidirectional links.

HSTL_ II, HSTL_ IV, HSTL_ II_18, HSTL_ IV_18

HSTL_II uses VCCO/2 as a parallel termination voltage (VTT). HSTL_IV uses VCCO as a parallel termination voltage (VTT). HSTL_II and HSTL_IV are intended to be used in bidirectional links.

250

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

HSTL_ II_DCI, HSTL_ IV_DCI, HSTL_ II_DCI_18, HSTL_ IV_DCI_18

HSTL_II_DCI provides on-chip split thevenin termination powered from VCCO, creating an equivalent termination voltage of VCCO/2. HSTL_IV_ DCI provides single termination to VCCO (VTT). HSTL_II_DCI and HSTL_IV_ DCI are intended to be used in bidirectional links.

HSTL_ II_T_DCI, HSTL_ II_T_DCI_18

HSTL_ II_T_DCI and HSTL_ II_T_DCI_18 provide on-chip split-thevenin termination powered from VCCO that creates an equivalent termination voltage of VCCO/2 when these standards are 3-stated. When not 3-stated, these two standards do not have termination.

DIFF_HSTL_ II, DIFF_HSTL_II_18

Differential HSTL class II pairs complimentary single-ended HSTL_II type drivers with a differential receiver. Differential HSTL class II is intended to be used in bidirectional links. Differential HSTL can also be used for differential clock and DQS signals in memory interface designs.

DIFF_HSTL_II_DCI, DIFF_HSTL_II_DCI_18
Differential HSTL class II pairs complimentary single-ended HSTL_II type drivers with a differential receiver, including on-chip differential split-thevenin termination. Differential HSTL class II is intended to be used in bidirectional links. Differential HSTL can also be used for differential clock and DQS signals in memory interface designs.

DIFF_HSTL_I, DIFF_HSTL_I_18
Differential HSTL class I pairs complimentary single-ended HSTL_I type drivers with a differential receiver. Differential HSTL class I is intended to be used in unidirectional links.

DIFF_HSTL_I_DCI, DIFF_HSTL_I_DCI_18
Differential HSTL class I pairs complimentary single-ended HSTL_I type drivers with a differential receiver, including on-chip differential split-thevenin termination. Differential HSTL class I is intended to be used in unidirectional links.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

251

Chapter 6: SelectIO Resources

HSTL Class I
Figure 6-40 shows a sample circuit illustrating a valid termination technique for HSTL Class I.
X-Ref Target - Figure 6-40

External Termination
IOB HSTL_I VTT = 0.75V RP = Z0 = 50 Z0 VREF = 0.75V IOB HSTL_I +

DCI
IOB IOB VCCO = 1.5V 2RVRP = 2Z0= 100 HSTL_I_DCI Z0 VREF = 0.75V 2RVRN = 2Z0= 100 HSTL_I_DCI +

ug190_6_38_030206

Figure 6-40:

HSTL Class I Termination

Table 6-15 lists the HSTL Class I DC voltage specifications. Table 6-15: HSTL Class I DC Voltage Specifications
Min VCCO VREF (2) VTT VIH VIL VOH VOL IOH at VOH (mA)(1) IOL at VOL (mA)(1)
Notes:
1. VOL and VOH for lower drive currents are sample tested. 2. Per EIA/JESD8-6, The value of VREF is to be selected by the user to provide optimum noise margin in the use conditions specified by the user.

Typ 1.50 0.75 VCCO 0.5

Max 1.60 0.90 VREF 0.1 0.4

1.40 0.68 VREF + 0.1 VCCO 0.4 8 8

252

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Differential HSTL Class I

Figure 6-41 shows a sample circuit illustrating a valid termination technique for differential HSTL Class I (1.5V) with unidirectional termination.
X-Ref Target - Figure 6-41

External Termination
IOB DIFF_HSTL_I Z0 DIFF_HSTL_I + VTT = 0.75V DIFF_HSTL_I Z0 50 VTT = 0.75V 50 IOB

ug190_6_39_030206

Figure 6-41:

Differential HSTL (1.5V) Class I Unidirectional Termination

Figure 6-42 shows a sample circuit illustrating a valid termination technique for differential HSTL Class I (1.5V) with unidirectional DCI termination.
X-Ref Target - Figure 6-42

DCI
IOB IOB VCCO = 1.5V DIFF_HSTL_I_DCI Z0 2RVRN = 2Z0= 100 DIFF_HSTL_I_DCI + VCCO = 1.5V DIFF_HSTL_I_DCI Z0 2RVRN = 2Z0= 100 2RVRP = 2Z0= 100 2RVRP = 2Z0= 100

ug190_6_40_030206

Figure 6-42:

Differential HSTL (1.5V) Class I DCI Unidirectional Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

253

Chapter 6: SelectIO Resources

Table 6-16 lists the differential HSTL Class I DC voltage specifications. Table 6-16: Differential HSTL Class I DC Voltage Specifications
Min VCCO VTT VIN (DC) VDIFF (DC) VCM (DC)(1) VDIFF (AC) VX (Crossover)(2)
Notes:
1. Common mode voltage: VCM = VP ((VP VN)/2) 2. Crossover point: VX where VP VN = 0 (AC coupled)

Typ 1.50 VCCO 0.5

Max 1.60 VCCO + 0.30 VCCO + 0.60 0.90 VCCO + 0.60 0.90

1.40 0.30 0.20 0.68 0.40 0.68

HSTL Class II
Figure 6-43 shows a sample circuit illustrating a valid termination technique for HSTL Class II (1.5V) with unidirectional termination.
X-Ref Target - Figure 6-43

External Termination
IOB HSTL_II VTT = 0.75V RP = Z0 = 50 VTT = 0.75V RP = Z0 = 50 Z0 VREF = 0.75V IOB HSTL_II +

DCI
IOB VCCO = 1.5V 2RVRP = 2Z0= 100 HSTL_II_DCI Z0 VREF = 0.75V 2RVRN = 2Z0= 100 2RVRN = 2Z0= 100 IOB VCCO = 1.5V 2RVRP = 2Z0= 100 HSTL_II_DCI +

ug190_6_41_030206

Figure 6-43:

HSTL (1.5V) Class II Unidirectional Termination

254

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Figure 6-44 shows a sample circuit illustrating a valid termination technique for HSTL Class II (1.5V) with bidirectional termination.
X-Ref Target - Figure 6-44

External Termination
IOB HSTL_II VTT = 0.75V RP = Z0 = 50 VTT = 0.75V RP = Z0 = 50 Z0 VREF = 0.75V IOB HSTL_II +

VREF = 0.75V

DCI
IOB VCCO = 1.5V 2RVRP = 2Z0= 100 HSTL_II_DCI Z0 VREF = 0.75V 2RVRN = 2Z0= 100 VREF = 0.75V 2RVRN = 2Z0= 100
ug190_6_42_030306

IOB VCCO = 1.5V 2RVRP = 2Z0= 100 HSTL_II_DCI +

Figure 6-44:

HSTL (1.5V) Class II Bidirectional Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

255

Chapter 6: SelectIO Resources

Table 6-17 lists the HSTL (1.5V) Class II DC voltage specifications. Table 6-17: HSTL (1.5V) Class II DC Voltage Specifications
Min VCCO VREF (2) VTT VIH VIL VOH VOL IOH at VOH (mA)(1) IOL at VOL (mA)(1) (3)
Notes:
1. VOL and VOH for lower drive currents are sample tested. 2. Per EIA/JESD8-6, The value of VREF is to be selected by the user to provide optimum noise margin in the use conditions specified by the user. 3. HSTL_II_T_DCI has a weaker driver than HSTL_II_DCI.

Typ 1.50 0.75 VCCO 0.5

Max 1.60 0.90 VREF 0.1 0.4

1.40 0.68 VREF + 0.1 VCCO 0.4 16 16

Differential HSTL Class II

Figure 6-45 shows a sample circuit illustrating a valid termination technique for differential HSTL Class II (1.5V) with unidirectional termination.
X-Ref Target - Figure 6-45

External Termination
IOB DIFF_HSTL_II VTT = 0.75V 50 Z0 DIFF_HSTL_II + VTT = 0.75V DIFF_HSTL_II 50 Z0 VTT = 0.75V 50 VTT = 0.75V 50 IOB

ug190_6_40_030206

Figure 6-45:

Differential HSTL (1.5V) Class II Unidirectional Termination

256

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Figure 6-46 shows a sample circuit illustrating a valid termination technique for differential HSTL Class II (1.5V) with unidirectional DCI termination.
X-Ref Target - Figure 6-46

DCI
IOB VCCO = 1.5V DIFF_HSTL_II_DCI 2RVRP = 2Z0= 100 Z0 2RVRN = 2Z0= 100 2RVRN = 2Z0= 100 DIFF_HSTL_II_DCI + VCCO = 1.5V DIFF_HSTL_II_DCI 2RVRP = 2Z0= 100 Z0 2RVRN = 2Z0= 100 2RVRN = 2Z0= 100 VCCO = 1.5V 2RVRP = 2Z0= 100 IOB VCCO = 1.5V 2RVRP = 2Z0= 100

ug190_6_44_020306

Figure 6-46:

Differential HSTL (1.5V) Class II DCI Unidirectional Termination

Figure 6-47 shows a sample circuit illustrating a valid termination technique for differential HSTL Class II (1.5V) with bidirectional termination.
X-Ref Target - Figure 6-47

External Termination
IOB DIFF_HSTL_II VTT = 0.75V 50 Z0 VTT = 0.75V 50 IOB DIFF_HSTL_II

VTT = 0.75V DIFF_HSTL_II 50 Z0 DIFF_HSTL_II +

VTT = 0.75V DIFF_HSTL_II 50

DIFF_HSTL_II +
ug190_6_45_020306

Figure 6-47:

Differential HSTL (1.5V) Class II Bidirectional Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

257

Chapter 6: SelectIO Resources

Figure 6-48 shows a sample circuit illustrating a valid termination technique for differential HSTL Class II (1.5V) with bidirectional DCI termination.
X-Ref Target - Figure 6-48

DCI
IOB VCCO = 1.5V DIFF_HSTL_II_DCI 2RVRP = 2Z0= 100 Z0 2RVRN = 2Z0= 100 DIFF_HSTL_II_DCI Z0 DIFF_HSTL_II_DCI + 2RVRN = 2Z0= 100 2RVRN = 2Z0= 100 VCCO = 1.5V 2RVRP = 2Z0= 100 VCCO = 1.5V 2RVRP = 2Z0= 100 DIFF_HSTL_II_DCI + 2RVRN = 2Z0= 100 DIFF_HSTL_II_DCI IOB VCCO = 1.5V 2RVRP = 2Z0= 100 DIFF_HSTL_II_DCI

ug190_6_46_020306

Figure 6-48:

Differential HSTL (1.5V) Class II DCI Bidirectional Termination

Table 6-18 lists the differential HSTL Class II DC voltage specifications. Table 6-18: Differential HSTL Class II DC Voltage Specifications
Min VCCO VTT VIN (DC) VDIFF (DC) VCM (DC)(1) VDIFF (AC) VX (Crossover)(2)
Notes:
1. Common mode voltage: VCM = VP ((VP VN)/2) 2. Crossover point: VX where VP VN = 0 (AC coupled)

Typ 1.50 VCCO 0.5

Max 1.60 VCCO + 0.30 VCCO + 0.60 0.90 VCCO + 0.60 0.90

1.40 0.30 0.20 0.68 0.40 0.68

258

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

HSTL Class III

Figure 6-49 shows a sample circuit illustrating a valid termination technique for HSTL Class III.
X-Ref Target - Figure 6-49

External Termination
IOB HSTL_III VTT = 1.5V RP = Z0 = 50 Z0 VREF = 0.9V IOB HSTL_III +

DCI
IOB IOB VCCO = 1.5V RVRP = Z0= 50 HSTL_III_DCI Z0 VREF = 0.9V HSTL_III_DCI +

ug190_6_47_030306

Figure 6-49:

HSTL Class III Termination

Table 6-19 lists the HSTL Class III DC voltage specifications. Table 6-19: HSTL Class III DC Voltage Specifications
Min VCCO VREF (2) VTT VIH VIL VOH VOL IOH at VOH (mA)(1) IOL at VOL (mA)(1)
Notes:
1. VOL and VOH for lower drive currents are sample tested. 2. Per EIA/JESD8-6, The value of VREF is to be selected by the user to provide optimum noise margin in the use conditions specified by the user.

Typ 1.50 0.90 VCCO

Max 1.60 VREF 0.1 0.4

1.40 VREF + 0.1 VCCO 0.4 8 24

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

259

Chapter 6: SelectIO Resources

HSTL Class IV
Figure 6-50 shows a sample circuit illustrating a valid unidirectional termination technique for HSTL Class IV.
X-Ref Target - Figure 6-50

External Termination
IOB HSTL_IV VTT = 1.5V RP = Z0 = 50 VTT = 1.5V RP = Z0 = 50 Z0 VREF = 0.9V IOB HSTL_IV +

DCI
IOB VCCO = 1.5V RVRP = Z0= 50 HSTL_IV_DCI Z0 VREF = 0.9V IOB VCCO = 1.5V RVRP = Z0= 50 HSTL_IV_DCI +

ug190_6_48_030306

Figure 6-50:

HSTL Class IV Unidirectional Termination

260

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Figure 6-51 shows a sample circuit illustrating a valid bidirectional termination technique for HSTL Class IV.
X-Ref Target - Figure 6-51

External Termination
IOB HSTL_IV VTT = 1.5V RP = Z0 = 50 VTT = 1.5V RP = Z0 = 50 Z0 VREF = 0.9V IOB HSTL_IV +

VREF = 0.9V

DCI
IOB VCCO = 1.5V RVRP = Z0= 50 HSTL_IV_DCI Z0 VREF = 0.9V IOB VCCO = 1.5V RVRP = Z0= 50 HSTL_IV_DCI +

VREF = 0.9V
ug190_6_49_030306

Figure 6-51:

HSTL Class IV Bidirectional Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

261

Chapter 6: SelectIO Resources

Table 6-20 lists the HSTL Class IV DC voltage specifications. Table 6-20: HSTL Class IV DC Voltage Specifications
Min VCCO VREF (2) VTT VIH VIL VOH VOL IOH at VOH (mA)(1) IOL at VOL (mA)(1)
Notes:
1. VOL and VOH for lower drive currents are sample tested. 2. Per EIA/JESD8-6, The value of VREF is to be selected by the user to provide optimum noise margin in the use conditions specified by the user.

Typ 1.50 0.90 VCCO

Max 1.60 VREF 0.1 0.4

1.40 VREF + 0.1 VCCO 0.4 8 48

HSTL_II_T_DCI (1.5V) Split-Thevenin Termination

Figure 6-52 shows a sample circuit illustrating a valid termination technique for HSTL_II_T_DCI (1.5V) with on-chip split-Thevenin termination. In this bidirectional case, when 3-stated, the termination is invoked on the receiver and not on the driver.
X-Ref Target - Figure 6-52

DCI

Not 3-stated
IOB

3-stated
IOB VCCO = 1.5V 2RVRP = 2Z0= 100

HSTL_II_T_DCI Z0 VREF = 0.75V

HSTL_II_T_DCI +

VREF = 0.75V

2RVRN = 2Z0= 100

ug190_6_90_041206

Figure 6-52: HSTL_II_T_DCI (1.5V) Split-Thevenin Termination

262

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

HSTL Class I (1.8V)

Figure 6-53 shows a sample circuit illustrating a valid termination technique for HSTL Class I (1.8V).
X-Ref Target - Figure 6-53

External Termination
IOB HSTL_I_18 VTT = 0.9V RP = Z0 = 50 Z0 VREF = 0.9V IOB HSTL_I_18 +

DCI
IOB IOB VCCO = 1.8V 2RVRP = 2Z0= 100 HSTL_I_DCI_18 Z0 VREF = 0.9V 2RVRN = 2Z0= 100 HSTL_I_DCI_18 +

ug190_6_50_030306

Figure 6-53:

HSTL Class I (1.8V) Termination

Table 6-21 lists the HSTL Class I (1.8V) DC voltage specifications. Table 6-21: HSTL Class I (1.8V) DC Voltage Specifications
Min VCCO VREF (2) VTT VIH VIL VOH VOL IOH at VOH (mA)(1) IOL at VOL (mA)(1)
Notes:
1. VOL and VOH for lower drive currents are sample tested. 2. Per EIA/JESD8-6, The value of VREF is to be selected by the user to provide optimum noise margin in the use conditions specified by the user.

Typ 1.8 0.9 VCCO 0.5

Max 1.9 1.08 VREF 0.1 0.4

1.7 0.83 VREF + 0.1 VCCO 0.4 8 8

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

263

Chapter 6: SelectIO Resources

Differential HSTL Class I (1.8V)

Figure 6-54 shows a sample circuit illustrating a valid termination technique for differential HSTL Class I (1.8V) with unidirectional termination.
X-Ref Target - Figure 6-54

External Termination
IOB DIFF_HSTL_I_18 Z0 DIFF_HSTL_I_18 VTT = 0.9V DIFF_HSTL_I_18 Z0 50 + VTT = 0.9V 50 IOB

ug190_6_51_030306

Figure 6-54:

Differential HSTL (1.8V) Class I Unidirectional Termination

Figure 6-55 shows a sample circuit illustrating a valid termination technique for differential HSTL Class I (1.8V) with unidirectional DCI termination.
X-Ref Target - Figure 6-55

DCI
IOB IOB VCCO = 1.8V DIFF_HSTL_I_DCI_18 Z0 2RVRN = 2Z0= 100 DIFF_HSTL_I_DCI_18 + VCCO = 1.8V DIFF_HSTL_I_DCI_18 Z0 2RVRN = 2Z0= 100 2RVRP = 2Z0= 100 2RVRP = 2Z0= 100

ug190_6_52_030306

Figure 6-55:

Differential HSTL (1.8V) Class I DCI Unidirectional Termination

264

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Table 6-22 lists the differential HSTL Class I (1.8V) DC voltage specifications. Table 6-22: Differential HSTL Class I (1.8V) DC Voltage Specifications
Min VCCO VTT VIN (DC) VDIFF (DC) VCM (DC)(1) VDIFF (AC) VX (Crossover)(2)
Notes:
1. Common mode voltage: VCM = VP ((VP VN)/2) 2. Crossover point: VX where VP VN = 0 (AC coupled)

Typ 1.8 VCCO 0.5

Max 1.9 VCCO + 0.30 VCCO + 0.60 1.08 VCCO + 0.60 1.08

1.7 0.30 0.20 0.83 0.40 0.83

HSTL Class II (1.8V)

Figure 6-56 shows a sample circuit illustrating a valid termination technique for HSTL Class II (1.8V) with unidirectional termination.
X-Ref Target - Figure 6-56

External Termination
IOB HSTL_II_18 VTT = 0.9V RP = Z0 = 50 VTT = 0.9V RP = Z0 = 50 Z0 VREF = 0.9V IOB HSTL_II_18 +

DCI
IOB VCCO = 1.8V 2RVRP = 2Z0= 100 HSTL_II_DCI_18 Z0 VREF = 0.9V 2RVRN = 2Z0= 100 2RVRN = 2Z0= 100 IOB VCCO = 1.8V 2RVRP = 2Z0= 100 HSTL_II_DCI_18 +

ug190_6_53_030306

Figure 6-56:

HSTL Class II (1.8V) with Unidirectional Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

265

Chapter 6: SelectIO Resources

Figure 6-57 shows a sample circuit illustrating a valid termination technique for HSTL Class II (1.8V) with bidirectional termination.
X-Ref Target - Figure 6-57

External Termination
IOB HSTL_II_18 VTT = 0.9V RP = Z0 = 50 VTT = 0.9V RP = Z0 = 50 Z0 VREF = 0.9V IOB HSTL_II_18 +

VREF = 0.9V

DCI
IOB VCCO = 1.8V 2RVRP = 2Z0= 100 HSTL_II_DCI_18 Z0 VREF = 0.9V 2RVRN = 2Z0= 100 VREF = 0.9V 2RVRN = 2Z0= 100
ug190_6_54_030306

IOB VCCO = 1.8V 2RVRP = 2Z0= 100 HSTL_II_DCI_18 +

Figure 6-57:

HSTL Class II (1.8V) with Bidirectional Termination

266

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Table 6-23 lists the HSTL Class II (1.8V) DC voltage specifications. Table 6-23: HSTL Class II (1.8V) DC Voltage Specifications
Min VCCO VREF (2) VTT VIH VIL VOH VOL IOH at VOH (mA)(1) IOL at VOL (mA)(1)
Notes:
1. VOL and VOH for lower drive currents are sample tested. 2. Per EIA/JESD8-6, The value of VREF is to be selected by the user to provide optimum noise margin in the use conditions specified by the user.

Typ 1.8 0.9 VCCO 0.5

Max 1.9 VREF 0.1 0.4

1.7 VREF + 0.1 VCCO 0.4 16 16

Differential HSTL Class II (1.8V)

Figure 6-58 shows a sample circuit illustrating a valid termination technique for differential HSTL Class II (1.8V) with unidirectional termination.
X-Ref Target - Figure 6-58

External Termination
IOB DIFF_HSTL_II_18 VTT = 0.9V 50 Z0 DIFF_HSTL_II_18 VTT = 0.9V DIFF_HSTL_II_18 50 Z0 VTT = 0.9V 50 + VTT = 0.9V 50 IOB

ug190_6_55_030306

Figure 6-58:

Differential HSTL (1.8V) Class II Unidirectional Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

267

Chapter 6: SelectIO Resources

Figure 6-59 shows a sample circuit illustrating a valid termination technique for differential HSTL Class II (1.8V) with unidirectional DCI termination.
X-Ref Target - Figure 6-59

DCI
IOB VCCO = 1.8V DIFF_HSTL_II_DCI_18 2RVRP = 2Z0= 100 Z0 2RVRN = 2Z0= 100 2RVRN = 2Z0= 100 DIFF_HSTL_II_DCI_18 + VCCO = 1.8V DIFF_HSTL_II_DCI_18 2RVRP = 2Z0= 100 Z0 2RVRN = 2Z0= 100 2RVRN = 2Z0= 100 VCCO = 1.8V 2RVRP = 2Z0= 100 IOB VCCO = 1.8V 2RVRP = 2Z0= 100

ug190_6_56_121506

Figure 6-59:

Differential HSTL (1.8V) Class II DCI Unidirectional Termination

Figure 6-60 shows a sample circuit illustrating a valid termination technique for differential HSTL Class II (1.8V) with bidirectional termination.
X-Ref Target - Figure 6-60

External Termination
IOB VTT = 0.9V DIFF_HSTL_II_18 50 Z0 VTT = 0.9V DIFF_HSTL_II_18 50 IOB

VTT = 0.9V DIFF_HSTL_II_18 50 Z0 DIFF_HSTL_II_18 +

VTT = 0.9V DIFF_HSTL_II_18 50

DIFF_HSTL_II_18 +
ug190_6_57_030306

Figure 6-60:

Differential HSTL (1.8V) Class II Bidirectional Termination

268

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Figure 6-61 shows a sample circuit illustrating a valid termination technique for differential HSTL Class II (1.8V) with bidirectional DCI termination.
X-Ref Target - Figure 6-61

DCI
IOB VCCO = 1.8V DIFF_HSTL_II_DCI_18 2RVRP = 2Z0= 100 Z0 2RVRN = 2Z0= 100 DIFF_HSTL_II_DCI_18 Z0 DIFF_HSTL_II_DCI_18 + 2RVRN = 2Z0= 100 2RVRN = 2Z0= 100 VCCO = 1.8V 2RVRP = 2Z0= 100 VCCO = 1.8V 2RVRP = 2Z0= 100 DIFF_HSTL_II_DCI_18 + 2RVRN = 2Z0= 100 DIFF_HSTL_II_DCI_18 IOB VCCO = 1.8V 2RVRP = 2Z0= 100 DIFF_HSTL_II_DCI_18

ug190_6_58_030306

Figure 6-61:

Differential HSTL (1.8V) Class II DCI Bidirectional Termination

Table 6-24 lists the differential HSTL Class II (1.8V) DC voltage specifications. Table 6-24: Differential HSTL Class II (1.8V) DC Voltage Specifications
Min VCCO VTT VIN (DC) VDIFF (DC) VCM (DC)(1) 1.7 0.30 0.20 0.83 0.40 0.83 Typ 1.8 VCCO 0.5 Max 1.9 VCCO + 0.30 VCCO + 0.60 1.08 VCCO + 0.60 1.08

VDIFF (AC) VX (Crossover)(2)

Notes:

1. Common mode voltage: VCM = VP ((VP VN)/2) 2. Crossover point: VX where VP VN = 0 (AC coupled)

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

269

Chapter 6: SelectIO Resources

HSTL Class III (1.8V)

Figure 6-62 shows a sample circuit illustrating a valid termination technique for HSTL Class III (1.8V).
X-Ref Target - Figure 6-62

External Termination
IOB HSTL_III_18 VTT = 1.8V RP = Z0 = 50 Z0 VREF = 1.1V IOB HSTL_III_18 +

DCI
IOB IOB VCCO = 1.8V RVRP = Z0= 50 HSTL_III_DCI_18 Z0 VREF = 1.1V HSTL_III_DCI_18 +

ug190_6_59_030306

Figure 6-62:

HSTL Class III (1.8V) Termination

Table 6-25 lists the HSTL Class III (1.8V) DC voltage specifications. Table 6-25: HSTL Class III (1.8V) DC Voltage Specifications
Min VCCO VREF (2) VTT VIH VIL VOH VOL IOH at VOH (mA)(1) IOL at VOL (mA)(1)
Notes:
1. VOL and VOH for lower drive currents are sample tested. 2. Per EIA/JESD8-6, The value of VREF is to be selected by the user to provide optimum noise margin in the use conditions specified by the user.

Typ 1.8 1.1 VCCO

Max 1.9 VREF 0.1 0.4

1.7 VREF + 0.1 VCCO 0.4 8 24

270

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

HSTL Class IV (1.8V)

Figure 6-63 shows a sample circuit illustrating a valid unidirectional termination technique for HSTL Class IV (1.8V).
X-Ref Target - Figure 6-63

External Termination
IOB HSTL_IV_18 VTT = 1.8V RP = Z0 = 50 VTT = 1.8V RP = Z0 = 50 Z0 VREF = 1.1V IOB HSTL_IV_18 +

DCI
IOB VCCO = 1.8V RVRP = Z0= 50 HSTL_IV_DCI_18 Z0 VREF = 1.1V IOB VCCO = 1.8V RVRP = Z0= 50 HSTL_IV_DCI_18 +

ug190_6_60_030306

Figure 6-63:

HSTL Class IV (1.8V) with Unidirectional Termination

Figure 6-64 shows a sample circuit illustrating a valid bidirectional termination technique for HSTL Class IV (1.8V).

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

271

Chapter 6: SelectIO Resources

X-Ref Target - Figure 6-64

External Termination
IOB HSTL_IV_18 VTT = 1.8V RP = Z0 = 50 VTT = 1.8V RP = Z0 = 50 Z0 VREF = 1.1V IOB HSTL_IV_18 +

VREF = 1.1V

DCI
IOB VCCO = 1.8V RVRP = Z0= 50 HSTL_IV_DCI_18 Z0 VREF = 1.1V IOB VCCO = 1.8V RVRP = Z0= 50 HSTL_IV_DCI_18 +

VREF = 1.1V
ug190_6_61_030306

Figure 6-64:

HSTL Class IV (1.8V) with Bidirectional Termination

272

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Table 6-26 lists the HSTL Class IV (1.8V) DC voltage specifications. Table 6-26: HSTL Class IV (1.8V) DC Voltage Specifications
Min VCCO VREF (2) VTT VIH VIL VOH VOL IOH at VOH (mA)(1) IOL at VOL (mA)(1)
Notes:
1. VOL and VOH for lower drive currents are sample tested. 2. Per EIA/JESD8-6, The value of VREF is to be selected by the user to provide optimum noise margin in the use conditions specified by the user.

Typ 1.8 1.1 VCCO

Max 1.9 VREF 0.1 0.4

1.7 VREF + 0.1 VCCO 0.4 8 48

HSTL_II_T_DCI_18 (1.8V) Split-Thevenin Termination

Figure 6-65 shows a sample circuit illustrating a valid termination technique for HSTL_II_T_DCI_18 (1.8V) with on-chip split-thevenin termination. In this bidirectional case, when 3-stated, the termination is invoked on the receiver and not on the driver.
X-Ref Target - Figure 6-65

DCI

Not 3-stated
IOB

3-stated
IOB VCCO = 1.8V 2RVRP = 2Z0= 100

HSTL_II_T_DCI_18 Z0 VREF = 0.9V

HSTL_II_T_DCI_18 +

VREF = 0.9V

2RVRN = 2Z0= 100

ug190_6_91_041206

Figure 6-65: HSTL_II_T_DCI_18 Split-Thevenin Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

273

Chapter 6: SelectIO Resources

HSTL Class I (1.2V)

Figure 6-66 shows a sample circuit illustrating a valid termination technique for HSTL Class I (1.2V). It is used for unidirectional links.
X-Ref Target - Figure 6-66

External Termination
IOB HSTL_I_12 VTT = 0.6V RP = Z0 = 50 Z0 VREF = 0.6V IOB HSTL_I_12 +

ug190_6_62_030306

Figure 6-66:

HSTL Class I (1.2V) Termination

Table 6-21 lists the HSTL Class I (1.2V) DC voltage specifications. Table 6-27: HSTL Class I (1.2V) DC Voltage Specifications
Min VCCO VREF (2) VTT VIH VIL VOH VOL IOH at VOH (mA)(1) IOL at VOL
Notes:
1. VOL and VOH for lower drive currents are sample tested. 2. Per EIA/JESD8-6, The value of VREF is to be selected by the user to provide optimum noise margin in the use conditions specified by the user.

Typ 1.2 0.6 VCCO 0.5

Max 1.26 VCCO 0.52 VREF 0.08 0.315

1.14 VCCO 0.48 VREF + 0.08 VCCO .0.315 6.3 6.3

(mA)(1)

SSTL (Stub-Series Terminated Logic)

The Stub-Series Terminated Logic (SSTL) for 2.5V (SSTL2) and 1.8V (SSTL18) standards are for general purpose memory buses. SSTL2 is defined by the JEDEC standard JESD8-9B and SSTL18 is defined by the JEDEC standard JESD8-15. The SSTL2 standard has two classes; Class I is for unidirectional and class II is for bidirectional signaling. Virtex-5 FPGA I/O supports both standards for single-ended signaling and differential signaling. This standard requires a differential amplifier input buffer and a push-pull output buffer.

274

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

SSTL2_I, SSTL18_I
Class I signaling uses VTT (VCCO/2) as a parallel termination voltage to a 50 resistor at the receiver. A series resistor (25 at 2.5V, 20 at 1.8V) must be connected to the transmitter output.

SSTL2_I_DCI, SSTL18_I_DCI
The DCI transmitter provides the internal series resistance (25 at 2.5V, 20 at 1.8V). The DCI receiver has an internal split thevenin termination powered from VCCO creating an equivalent VTT voltage and termination impedance.

SSTL2_II, SSTL18_II
Class II signaling uses VTT (VCCO/2) as a parallel termination voltage to a 50 resistor at the receiver and transmitter respectively. A series resistor (25 at 2.5V, 20 at 1.8V) must be connected to the transmitter output for a unidirectional link. For a bidirectional link, 25 series resistors must connected the transmitters of the transceivers.

SSTL2_II_DCI, SSTL18_II_DCI
The DCI circuits have a split thevenin termination powered from VCCO and an internal series resistor (25 at 2.5V, 20 at 1.8V). For a unidirectional link the internal series resistance is supplied only for the transmitter. A bidirectional link has the internal series resistor for both transmitters.

DIFF_SSTL2_I, DIFF_SSTL18_I
Differential SSTL 2.5V and 1.8V Class I pairs complementary single-ended SSTL_I type drivers with a differential receiver.

DIFF_SSTL2_I_DCI, DIFF_SSTL18_I_DCI
Differential SSTL 2.5V and 1.8V Class I pairs complementary single-ended SSTL_II type drivers with a differential receiver, including on-chip differential split thevenin termination.

DIFF_SSTL2_II, DIFF_SSTL18_II
Differential SSTL 2.5V and 1.8V Class II pairs complementary single-ended SSTL_II type drivers with a differential receiver. For a bidirectional link, a series resistor must be connected to both transmitters.

DIFF_SSTL2_II_DCI, DIFF_SSTL18_II_DCI
Differential SSTL 2.5V and 1.8V Class II pairs complementary single-ended SSTL_II type drivers with a differential receiver, including on-chip differential termination. DCI can be used for unidirectional and bidirectional links.

SSTL2_II_T_DCI, SSTL18_II_T_DCI
SSTL2_II_T_DCI and SSTL18_II_T_DCI provide on-chip split thevenin termination powered from VCCO that creates an equivalent termination voltage of VCCO/2 when these standards are 3-stated. When not 3-stated, these two standards do not have parallel termination but when invoked they have an internal series resistor (25 at 2.5V and 20 at 1.8V.)

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

275

Chapter 6: SelectIO Resources

SSTL2 Class I (2.5V)

Figure 6-67 shows a sample circuit illustrating a valid termination technique for SSTL2 Class I.
X-Ref Target - Figure 6-67

External Termination
IOB SSTL2_I RS = 25 VTT = 1.25V RP = Z0 = 50 Z0 VREF = 1.25V IOB SSTL2_I +

DCI
IOB IOB VCCO = 2.5V 2RVRP = 2Z0= 100 SSTL2_I_DCI Z0
R0 = 25

SSTL2_I_DCI + VREF = 1.25V 2RVRN = 2Z0= 100

ug190_6_63_030506

Figure 6-67:

SSTL2 Class I Termination

276

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Table 6-28 lists the SSTL2 DC voltage specifications for Class I. Table 6-28: SSTL2 DC Voltage Specifications Class I
Min VCCO VREF = 0.5 VCCO VTT = VREF + N(1) VIH VREF + 0.15 VIL VREF 0.15 VOH VREF + 0.61 VOL VREF 0.61(4) IOH at VOH (mA) IOL at VOL (mA)
Notes:
1. 2. 3. 4. N must be greater than or equal to 0.04 and less than or equal to 0.04. VIH maximum is VCCO +0.3. VIL minimum does not conform to the formula. Because SSTL2_I_DCI uses a controlled-impedance driver, VOH and VOL are different.

Typ 2.5 1.25 1.25 1.4 1.1 1.84 0.66

Max 2.7 1.38 1.42 VCCO + 0.3(2) 1.23 1.94 0.76

2.3 1.13 1.09 1.28 0.3(3) 1.74 0.56 8.1 8.1

Differential SSTL2 Class I (2.5V)

Figure 6-68 shows a sample circuit illustrating a valid termination technique for differential SSTL2 Class I (2.5V) with unidirectional termination.
X-Ref Target - Figure 6-68

External Termination
IOB DIFF_SSTL2_I RS = 25 Z0 DIFF_SSTL2_I VTT = 1.25V DIFF_SSTL2_I RS = 25 RP = Z0 = 50 Z0 + VTT = 1.25V 50 IOB

ug190_6_64_030506

Figure 6-68:

Differential SSTL2 Class I Unidirectional Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

277

Chapter 6: SelectIO Resources

Figure 6-69 shows a sample circuit illustrating a valid termination technique for differential SSTL2 Class I (2.5V) with unidirectional DCI termination.
X-Ref Target - Figure 6-69

DCI
IOB VCCO = 2.5V DIFF_SSTL2_I_DCI Z0
R0 = 25

2RVRP = 2Z0= 100

2RVRN = 2Z0= 100

DIFF_SSTL2_I_DCI +

VCCO = 2.5V DIFF_SSTL2_I_DCI Z0

R0 = 25

2RVRP = 2Z0= 100

2RVRN = 2Z0= 100

ug190_6_65_030506

Figure 6-69:

Differential SSTL2 (2.5V) Class I Unidirectional DCI Termination

Table 6-29 lists the differential SSTL2 Class I DC voltage specifications. Table 6-29: Differential SSTL2 Class I DC Voltage Specifications
Min VCCO Input Parameters VTT VIN (DC)(1) VID (DC)(2) 0.30 0.3 0.62 0.95 VCCO 0.5 VCCO + 0.30 VCCO + 0.60 VCCO + 0.60 1.55 2.3 Typ 2.5 Max 2.7

VID (AC) VIX (AC)(3) Output Parameters VOX (AC)(4)

Notes:
1. 2. 3. 4.

1.0

1.5

VIN (DC) specifies the allowable DC excursion of each differential input. VID (DC) specifies the input differential voltage required for switching. VIX (AC) indicates the voltage where the differential input signals must cross. VOX (AC) indicates the voltage where the differential output signals must cross.

278

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

SSTL2 Class II (2.5V)

Figure 6-70 shows a sample circuit illustrating a valid unidirectional termination technique for SSTL2 Class II.
X-Ref Target - Figure 6-70

External Termination
IOB SSTL2_II VTT = 1.25V RP = Z0 = 50 25 VTT = 1.25V RP = Z0 = 50 Z0 VREF = 1.25V IOB SSTL2_II +

DCI
IOB VCCO = 2.5V 2RVRP = 2Z0= 100 SSTL2_II_DCI Z0
R0 = 25

IOB VCCO = 2.5V 2RVRP = 2Z0= 100 SSTL2_II_DCI + VREF = 1.25V

2RVRN = 2Z0= 100

2RVRN = 2Z0= 100

ug190_6_66_030506

Figure 6-70:

SSTL2 Class II with Unidirectional Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

279

Chapter 6: SelectIO Resources

Figure 6-71 shows a sample circuit illustrating a valid bidirectional termination technique for SSTL2 Class II.
X-Ref Target - Figure 6-71

External Termination
IOB SSTL2_II RS = 25 VTT = 1.25V VTT = 1.25V RS = 25 + VREF = 1.25V IOB SSTL2_II RP = Z0 = 50 RP = Z0 = 50 Z0

VREF = 1.25V

DCI
IOB VCCO = 2.5V 2RVRP = 2Z0= 100 SSTL2_II_DCI Z0
R0 = 25

IOB VCCO = 2.5V 2RVRP = 2Z0= 100 SSTL2_II_DCI + VREF = 1.25V

2RVRN = 2Z0= 100 VREF = 1.25V

2RVRN = 2Z0= 100

R0 = 25
ug190_6_67_030506

Figure 6-71:

SSTL2 Class II with Bidirectional Termination

280

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Table 6-30 lists the SSTL2 DC voltage specifications for Class II. Table 6-30: SSTL2 DC Voltage Specifications Class II
Min VCCO VREF = 0.5 VCCO VTT = VREF + N(1) VIH VREF + 0.15 VIL VREF 0.15 VOH VREF + 0.81 VOL VREF 0.81(4) IOH at VOH (mA) IOL at VOL (mA)
Notes:
1. 2. 3. 4. N must be greater than or equal to 0.04 and less than or equal to 0.04. VIH maximum is VCCO +0.3. VIL minimum does not conform to the formula. Because SSTL2_I_DCI uses a controlled-impedance driver, VOH and VOL are different.

Typ 2.5 1.25 1.25 1.40 1.1 2.03 0.46

Max 2.7 1.38 1.42 VCCO + 0.3(2) 1.27 2.13 0.55

2.3 1.13 1.09 1.28 0.3(3) 1.93 0.36 16.2 16.2

Differential SSTL2 Class II (2.5V)

Figure 6-72 shows a sample circuit illustrating a valid termination technique for differential SSTL2 Class II (2.5V) with unidirectional termination.
X-Ref Target - Figure 6-72

External Termination
IOB DIFF_SSTL2_II RS = 25 VTT = 1.25V 50 Z0 DIFF_SSTL2_II VTT = 1.25V DIFF_SSTL2_II RS = 25 50 Z0 VTT = 1.25V 50 + VTT = 1.25V 50 IOB

ug190_6_68_030506

Figure 6-72:

Differential SSTL2 Class II Unidirectional Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

281

Chapter 6: SelectIO Resources

Figure 6-73 shows a sample circuit illustrating a valid termination technique for differential SSTL2 Class II (2.5V) with unidirectional DCI termination.
X-Ref Target - Figure 6-73

DCI
IOB VCCO = 2.5V DIFF_SSTL2_II_DCI 2RVRP = 2Z0= 100 Z0
R0 = 25

IOB VCCO = 2.5V 2RVRP = 2Z0= 100

2RVRN = 2Z0= 100

2RVRN = 2Z0= 100

DIFF_SSTL2_II_DCI +

VCCO = 2.5V DIFF_SSTL2_II_DCI 2RVRP = 2Z0= 100 Z0

R0 = 25

VCCO = 2.5V 2RVRP = 2Z0= 100

2RVRN = 2Z0= 100

2RVRN = 2Z0= 100

ug190_6_69_030506

Figure 6-73:

Differential SSTL2 (2.5V) Class II Unidirectional DCI Termination

Figure 6-74 shows a sample circuit illustrating a valid termination technique for differential SSTL2 Class II (2.5V) with bidirectional termination.
X-Ref Target - Figure 6-74

External Termination
IOB DIFF_SSTL2_II 25 Z0 VTT = 1.25V DIFF_SSTL2_II 25 50 Z0 DIFF_SSTL2_II + DIFF_SSTL2_II +
ug190_6_70_071707

VTT = 1.25V 50

VTT = 1.25V 50 25

IOB DIFF_SSTL2_II

VTT = 1.25V DIFF_SSTL2_II 50 25

Figure 6-74:

Differential SSTL2 (2.5V) Class II with Bidirectional Termination

282

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Figure 6-75 shows a sample circuit illustrating a valid termination technique for differential SSTL2 Class II (2.5V) with bidirectional DCI termination.
X-Ref Target - Figure 6-75

DCI
IOB VCCO = 2.5V DIFF_SSTL2_II_DCI 2RVRP = 2Z0= 100 Z0
R0 = 25

IOB VCCO = 2.5V 2RVRP = 2Z0= 100 DIFF_SSTL2_II_DCI

2RVRN = 2Z0= 100

2RVRN = 2Z0= 100

R0 = 25

DIFF_SSTL2_II_DCI Z0
R0 = 25

DIFF_SSTL2_II_DCI

R0 = 25

DIFF_SSTL2_II_DCI +

VCCO = 2.5V 2RVRP = 2Z0= 100

VCCO = 2.5V 2RVRP = 2Z0= 100

DIFF_SSTL2_II_DCI +

2RVRN = 2Z0= 100

2RVRN = 2Z0= 100

ug190_6_71_041106

Figure 6-75: Differential SSTL2 (2.5V) Class II with DCI Bidirectional Termination Table 6-31 lists the differential SSTL2 Class II DC voltage specifications. Table 6-31: Differential SSTL2 Class II DC Voltage Specifications
Min VCCO Input Parameters VTT VIN (DC)(1) VID (DC)(2) VID (AC) VIX (AC)(3) Output Parameters VOX (AC)(4)
Notes:
1. 2. 3. 4. VIN (DC) specifies the allowable DC excursion of each differential input. VID (DC) specifies the input differential voltage required for switching. VIX (AC) indicates the voltage where the differential input signals must cross. VOX (AC) indicates the voltage where the differential output signals must cross.

Typ 2.5

Max 2.7

2.3

0.30 0.3 0.62 0.95

VCCO 0.5

VCCO + 0.30 VCCO + 0.60 VCCO + 0.60 1.55

1.0

1.5

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

283

Chapter 6: SelectIO Resources

SSTL2_II_T_DCI (2.5V) Split-Thevenin Termination

Figure 6-76 shows a sample circuit illustrating a valid termination technique for SSTL2_II_T_DCI (2.5V) with on-chip split-Thevenin termination. In this bidirectional I/O standard, when 3-stated, the termination is invoked on the receiver and not on the driver.
X-Ref Target - Figure 6-76

DCI

Not 3-stated
IOB

3-stated
IOB VCCO = 2.5V 2RVRP = 2Z0= 100

SSTL2_II_T_DCI Z0
R0 = 25

SSTL2_II_T_DCI + VREF = 1.25V 2RVRN = 2Z0= 100 VREF = 1.25V

R0 = 25
ug190_6_92_041206

Figure 6-76:

SSTL2_II_T_DCI (2.5V) Split-Thevenin Termination

284

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

SSTL18 Class I (1.8V)

Figure 6-77 shows a sample circuit illustrating a valid termination technique for SSTL Class I (1.8V).
X-Ref Target - Figure 6-77

External Termination
IOB SSTL18_I RS = 20 Z0 VREF = 0.9V VTT = 0.9V 50 IOB SSTL18_I +

DCI
IOB IOB VCCO = 1.8V 2RVRP = 2Z0= 100 SSTL18_I_DCI Z0
R0 = 20

SSTL18_I_DCI + VREF = 0.9V 2RVRN = 2Z0= 100

ug190_6_72_030506

Figure 6-77:

SSTL18 (1.8V) Class I Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

285

Chapter 6: SelectIO Resources

Differential SSTL Class I (1.8V)

Figure 6-78 shows a sample circuit illustrating a valid termination technique for differential SSTL Class I (1.8V) with unidirectional termination.
X-Ref Target - Figure 6-78

External Termination
IOB DIFF_SSTL18_I RS = 20 Z0 DIFF_SSTL18_I + VTT = 0.9V DIFF_SSTL18_I RS = 20 RP = Z0 = 50 Z0 VTT = 0.9V 50 IOB

ug190_6_73_030506

Figure 6-78:

Differential SSTL (1.8V) Class I Unidirectional Termination

Figure 6-79 shows a sample circuit illustrating a valid termination technique for differential SSTL Class I (1.8V) with unidirectional DCI termination.
X-Ref Target - Figure 6-79

DCI
IOB IOB VCCO = 1.8V DIFF_SSTL18_I_DCI Z0
R0 = 20

2RVRP = 2Z0= 100

2RVRN = 2Z0= 100

DIFF_SSTL18_I_DCI +

VCCO = 1.8V DIFF_SSTL18_I_DCI Z0

R0 = 20

2RVRP = 2Z0= 100

2RVRN = 2Z0= 100

ug190_6_74_032206

Figure 6-79:

Differential SSTL (1.8V) Class I Unidirectional DCI Termination

286

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Table 6-32 lists the differential SSTL (1.8V) Class I DC voltage specifications. Table 6-32: Differential SSTL (1.8V) Class I and Class II DC Voltage Specifications
Min VCCO Input Parameters VTT VIN (DC)(1) VID (DC)(3) VID (AC) VIX (AC)(4) Output Parameters VOX (AC)(5)
Notes:
1. VIN (DC) specifies the allowable DC excursion of each differential input. 2. Per EIA/JESD8-6, The value of VREF is to be selected by the user to provide optimum noise margin in the use conditions specified by the user. 3. VID (DC) specifies the input differential voltage required for switching. 4. VIX (AC) indicates the voltage where the differential input signals must cross. 5. VOX (AC) indicates the voltage where the differential output signals must cross.

Typ 1.8

Max 1.9

1.7

0.30 0.25 0.50 0.675

VCCO 0.5

VCCO + 0.30 VCCO + 0.60 VCCO + 0.60 1.125

0.725

1.075

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

287

Chapter 6: SelectIO Resources

SSTL18 Class II (1.8V)

Figure 6-80 shows a sample circuit illustrating a valid unidirectional termination technique for SSTL Class II (1.8V).
X-Ref Target - Figure 6-80

External Termination
IOB SSTL18_II RS = 20 VTT = 0.9V RP = Z0 = 50 VTT = 0.9V RP = Z0 = 50 Z0 VREF = 0.9V IOB SSTL18_II +

DCI
IOB VCCO = 1.8V 2RVRP = 2Z0= 100 SSTL18_II_DCI Z0
R0 = 20

IOB VCCO = 1.8V 2RVRP = 2Z0= 100 SSTL18_II_DCI + VREF = 0.9V

2RVRN = 2Z0= 100

2RVRN = 2Z0= 100

ug190_6_75_030506

Figure 6-80:

SSTL18 (1.8V) Class II Unidirectional Termination

Figure 6-81 shows a sample circuit illustrating a valid bidirectional termination technique for SSTL (1.8V) Class II.

288

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

X-Ref Target - Figure 6-81

External Termination
IOB SSTL18_II RS = 20 VTT = 0.9V RP = Z0 = 50 VTT = 0.9V RP = Z0 = 50 Z0 VREF = 0.9V RS = 20 + IOB SSTL18_II

VREF = 0.9V

DCI
IOB VCCO = 1.8V 2RVRP = 2Z0= 100 SSTL18_II_DCI Z0
R0 = 20

IOB VCCO = 1.8V 2RVRP = 2Z0= 100 SSTL18_II_DCI + VREF = 0.9V

2RVRN = 2Z0= 100 VREF = 0.9V

2RVRN = 2Z0= 100

R0 = 20
ug190_6_76_071707

Figure 6-81:

SSTL (1.8V) Class II Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

289

Chapter 6: SelectIO Resources

Table 6-33 and Table 6-34 lists the SSTL (1.8V) DC voltage specifications for Class I and Class II, respectively. Table 6-33: SSTL (1.8V) DC Voltage Specifications Class I
Class I Min VCCO VREF = 0.5 VCCO VTT = VREF + N(1) VIH VREF + 0.125 VIL VREF 0.125 VOH VTT + 0.47(4) VOL VTT 0.47(4) IOH at VOH (mA) IOL at VOL (mA)
Notes:
1. 2. 3. 4. N must be greater than or equal to 0.04 and less than or equal to 0.04. VIH maximum is VCCO +0.3. VIL minimum does not conform to the formula. Because SSTL_I_DCI uses a controlled-impedance driver, VOH and VOL are different.

Typ 1.8 0.9 0.9

Max 1.9 0.969 1.009 VCCO + 0.3(2) 0.844 0.539

1.7 0.833 0.793 0.958 0.3(3) 1.263 6.7 6.7

Table 6-34:

SSTL (1.8V) DC Voltage Specifications Class II

Class II Min Typ 1.8 0.9 0.9 Max 1.9 0.969 1.009 VCCO + 0.3(2) 0.844 0.406

VCCO VREF = 0.5 VCCO VTT = VREF + N(1) VIH VREF + 0.125 VIL VREF 0.125 VOH VTT + 0.603(4) VOL VTT 0.603(4) IOH at VOH (mA) IOL at VOL (mA)
Notes:
1. 2. 3. 4.

1.7 0.833 0.793 0.958 0.3(3) 1.396 13.4 13.4

N must be greater than or equal to 0.04 and less than or equal to 0.04. VIH maximum is VCCO +0.3. VIL minimum does not conform to the formula. Because SSTL_I_DCI uses a controlled-impedance driver, VOH and VOL are different.

290

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Differential SSTL Class II (1.8V)

Figure 6-82 shows a sample circuit illustrating a valid termination technique for differential SSTL Class II (1.8V) with unidirectional termination.
X-Ref Target - Figure 6-82

External Termination
IOB DIFF_SSTL18_II RS = 20 VTT = 0.9V 50 Z0 DIFF_SSTL18_II + VTT = 0.9V DIFF_SSTL18_II RS = 20 50 Z0 VTT = 0.9V 50 VTT = 0.9V 50 IOB

ug190_6_77_030506

Figure 6-82:

Differential SSTL (1.8V) Class II Unidirectional Termination

Figure 6-83 shows a sample circuit illustrating a valid termination technique for differential SSTL Class II (1.8V) with unidirectional DCI termination.
X-Ref Target - Figure 6-83

DCI
IOB VCCO = 1.8V DIFF_SSTL18_II_DCI 2RVRP = 2Z0= 100 Z0
R0 = 20

IOB VCCO = 1.8V 2RVRP = 2Z0= 100

2RVRN = 2Z0= 100

2RVRN = 2Z0= 100

DIFF_SSTL18_II_DCI +

VCCO = 1.8V DIFF_SSTL18_II_DCI 2RVRP = 2Z0= 100 Z0

R0 = 20

VCCO = 1.8V 2RVRP = 2Z0= 100

2RVRN = 2Z0= 100

2RVRN = 2Z0= 100

ug190_6_78_030506

Figure 6-83:

Differential SSTL (1.8V) Class II Unidirectional DCI Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

291

Chapter 6: SelectIO Resources

Figure 6-84 shows a sample circuit illustrating a valid termination technique for differential SSTL Class II (1.8V) with bidirectional termination.
X-Ref Target - Figure 6-84

External Termination
IOB VTT = 0.9V DIFF_SSTL18_II 20 Z0 50 VTT = 0.9V 50 20 DIFF_SSTL18_II IOB

VTT = 0.9V DIFF_SSTL18_II 20 50 Z0 DIFF_SSTL18_II +

VTT = 0.9V DIFF_SSTL18_II 50 20

DIFF_SSTL18_II +
ug190_6_79_091807

Figure 6-84:

Differential SSTL (1.8V) Class II with Bidirectional Termination

Figure 6-85 shows a sample circuit illustrating a valid termination technique for differential SSTL Class II (1.8V) with bidirectional DCI termination.
X-Ref Target - Figure 6-85

DCI
IOB VCCO = 1.8V DIFF_SSTL18_II_DCI 2RVRP = 2Z0= 100 Z0
R0 = 20

IOB VCCO = 1.8V 2RVRP = 2Z0= 100 DIFF_SSTL18_II_DCI

2RVRN = 2Z0= 100

2RVRN = 2Z0= 100

R0 = 20

DIFF_SSTL18_II_DCI Z0
R0 = 20

DIFF_SSTL18_II_DCI

DIFF_SSTL18_II_DCI +

VCCO = 1.8V 2RVRP = 2Z0= 100

VCCO = 1.8V 2RVRP = 2Z0= 100

R0 = 20 DIFF_SSTL18_II_DCI

2RVRN = 2Z0= 100

2RVRN = 2Z0= 100

ug190_6_80_030506

Figure 6-85: Differential SSTL (1.8V) Class II with DCI Bidirectional Termination

292

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Table 6-35 lists the differential SSTL (1.8V) Class II DC voltage specifications. Table 6-35: Differential SSTL (1.8V) Class II DC Voltage Specifications
Min VCCO Input Parameters VTT VIN (DC)(1) VID (DC)(3) VID (AC) VIX (AC)(4) Output Parameters VOX (AC)(5)
Notes:
1. VIN (DC) specifies the allowable DC excursion of each differential input. 2. Per EIA/JESD8-6, The value of VREF is to be selected by the user to provide optimum noise margin in the use conditions specified by the user. 3. VID (DC) specifies the input differential voltage required for switching. 4. VIX (AC) indicates the voltage where the differential input signals must cross. 5. VOX (AC) indicates the voltage where the differential output signals must cross.

Typ 1.8

Max 1.9

1.7

0.30 0.25 0.50 0.675

VCCO 0.5

VCCO + 0.30 VCCO + 0.60 VCCO + 0.60 1.125

0.725

1.075

SSTL18_II_T_DCI (1.8V) Split-Thevenin Termination

Figure 6-86 shows a sample circuit illustrating a valid termination technique for SSTL18_II_T_DCI (1.8V) with on-chip split-Thevenin termination. In this bidirectional I/O standard, when 3-stated, the termination is invoked on the receiver and not on the driver. Because the Thevenin termination on the I/O is disabled for a driving I/O, the line is equivalent to the SSTL18_I termination scheme. This allows the line to be driven by the weaker SSTL class I driver. The SSTL18_II_T_DCI standard behaves like a normal SSTL18_II I/O in a bidirectional environment but has the advantage of lower drive strength and lower power consumption due to the optimized termination circuit.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

293

Chapter 6: SelectIO Resources

X-Ref Target - Figure 6-86

DCI

Not 3-stated
IOB

3-stated
IOB VCCO = 1.8V 2RVRP = 2Z0= 100

SSTL18_II_T_DCI Z0
R0 = 20

SSTL18_II_T_DCI + VREF = 0.9V 2RVRN = 2Z0= 100 VREF = 0.9V

R0 = 20
ug190_6_93_041206

Figure 6-86:

SSTL18_II_T_DCI (1.8V) Split-Thevenin Termination

Differential Termination: DIFF_TERM Attribute

Virtex-5 FPGA IOBs provide a 100 differential termination across the input differential receiver terminals. This attribute is used in conjunction with LVDS_25, LVDSEXT_25, HT_25, and RSDS_25. HT_25 replaces the Virtex-4 FPGA LDT_25 standard. The on-chip input differential termination in Virtex-5 devices provides major advantages over the external resistor by removing the stub at the receiver completely and therefore greatly improving signal integrity: Consumes less power than DCI termination Does not use VRP/VRN pins (DCI)

The VCCO of the I/O bank must be connected to 2.5V 5% to provide 100 of effective differential termination. DIFF_TERM is only available for inputs and can only be used with a bank voltage of VCCO = 2.5V. The Differential Termination Attribute (DIFF_TERM) section outlines using this feature.

LVDS and Extended LVDS (Low Voltage Differential Signaling)

Low Voltage Differential Signaling (LVDS) is a very popular and powerful high-speed interface in many system applications. Virtex-5 FPGA I/Os are designed to comply with the EIA/TIA electrical specifications for LVDS to make system and board design easier. With the use of an LVDS current-mode driver in the IOBs, the need for external source termination in point-to-point applications is eliminated, and with the choice of an extended mode, Virtex-5 devices provide the most flexible solution for doing an LVDS design in an FPGA. Extended LVDS provides a higher drive capability and voltage swing (350 - 750 mV), making it ideal for long-distance or cable LVDS links. The output AC characteristics of the LVDS extended mode driver are not within the EIA/TIA specifications. The LVDS extended mode driver is intended for situations requiring higher drive capabilities to produce an LVDS signal within the EIA/TIA specification at the receiver.

294

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Transmitter Termination
The Virtex-5 FPGA LVDS transmitter does not require any external termination. Table 6-36 lists the allowed attributes corresponding to the Virtex-5 FPGA LVDS current-mode drivers. Virtex-5 FPGA LVDS current-mode drivers are a true current source and produce the proper (EIA/TIA compliant) LVDS signal.

Receiver Termination
Figure 6-87 is an example of differential termination for an LVDS receiver on a board with 50 transmission lines.
X-Ref Target - Figure 6-87

External Termination
IOB IOB

LVDS_25

Z0 RDIFF = 2Z0= 100 Z0

LVDS_25 +

ug190_6_81_030506

Figure 6-87:

LVDS_25 Receiver Termination

Figure 6-88 is an example of a differential termination for an LVDS receiver on a board with 50 transmission lines.
X-Ref Target - Figure 6-88

IOB LVDS_25
0 Z0 = 50

IOB LVDS_25 +
RDIFF= 100

Z0 = 50 0

Data in

ug190_6_82_030506

Figure 6-88: LVDS_25 With DIFF_TERM Receiver Termination Table 6-36 lists the available Virtex-5 FPGA LVDS I/O standards and attributes supported. Table 6-36: Allowed Attributes of the LVDS I/O Standard
Primitives Attributes IBUFDS/IBUFGDS IOSTANDARD DIFF_TERM OBUFDS/OBUFTDS LVDS_25, LVDSEXT_25 TRUE, FALSE N/A

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

295

Chapter 6: SelectIO Resources

HyperTransport Protocol (HT)

The HyperTransport protocol (HT) also known as Lightning Data Transport (LDT), is a low-voltage standard for high-speed interfaces. Its differential signaling based interface is very similar to LVDS. Virtex-5 FPGA IOBs are equipped with HT buffers. Table 6-38 summarizes all the possible HT I/O standards and attributes supported. Table 6-37: Allowed Attributes of the HT I/O Standard
Primitives Attributes IBUFDS/IBUFGDS IOSTANDARD DIFF_TERM TRUE, FALSE HT_25 N/A OBUFDS/OBUFTDS

Reduced Swing Differential Signaling (RSDS)

Reduced Swing Differential Signaling (RSDS) is similar to an LVDS high-speed interface using differential signaling. RSDS has a similar implementation to LVDS in Virtex-5 devices and is only intended for point-to-point applications. Table 6-38: Allowed Attributes of the RSDS I/O Standard
Primitives Attributes IBUFDS/IBUFGDS IOSTANDARD DIFF_TERM TRUE, FALSE RSDS_25 N/A OBUFDS/OBUFTDS

BLVDS (Bus LVDS)

Since LVDS is intended for point-to-point applications, BLVDS is not an EIA/TIA standard implementation and requires careful adaptation of I/O and PCB layout design rules. The primitive supplied in the software library for bidirectional LVDS does not use the Virtex-5 FPGA LVDS current-mode driver, instead, it uses complementary single-ended differential drivers. Therefore, source termination is required. Figure 6-89 shows the BLVDS transmitter termination.
X-Ref Target - Figure 6-89

BLVDS_25

IOB RS 165 Z0 = 50 IN

IOB BLVDS_25 + INX Data in

BLVDS_25 RS 165

RDIV 140

RDIFF = 100 Z0 = 50

ug190_6_83_030506

Figure 6-89:

BLVDS Transmitter Termination

296

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Specific Guidelines for I/O Supported Standards

Differential LVPECL (Low-Voltage Positive Emitter-Coupled Logic)

LVPECL is a very popular and powerful high-speed interface in many system applications. Virtex-5 FPGA I/Os are designed to comply with the EIA/TIA electrical specifications for 2.5V LVPECL to make system and board design easier.

LVPECL Transceiver Termination

The Virtex-5 FPGA LVPECL transmitter and receiver requires the termination shown in Figure 6-90, illustrating a Virtex-5 FPGA LVPECL transmitter and receiver on a board with 50 transmission lines. The LVPECL driver is composed of two LVCMOS drivers that form a compliant LVPECL output when combined with the three resistor output termination circuit.
X-Ref Target - Figure 6-90

LVPECL_25

IOB RS 70 Z0 = 50 IN

IOB LVPECL_25 + INX Data in

LVPECL_25 RS 70

RDIV 187

RDIFF = 100 Z0 = 50

ug190_6_84_030506

Figure 6-90:

LVPECL Transmitter Termination

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

297

Chapter 6: SelectIO Resources

Rules for Combining I/O Standards in the Same Bank

The following rules must be obeyed to combine different input, output, and bidirectional standards in the same bank: 1. Combining output standards only. Output standards with the same output VCCO requirement can be combined in the same bank. Compatible example: SSTL2_I and LVDCI_25 outputs Incompatible example: SSTL2_I (output VCCO = 2.5V) and LVCMOS33 (output VCCO = 3.3V) outputs 2. Combining input standards only. Input standards with the same VCCO and VREF requirements can be combined in the same bank. Compatible example: LVCMOS15 and HSTL_IV inputs Incompatible example: LVCMOS15 (input VCCO = 1.5V) and LVCMOS18 (input VCCO = 1.8V) inputs Incompatible example: HSTL_I_DCI_18 (VREF = 0.9V) and HSTL_IV_DCI_18 (VREF = 1.1V) inputs 3. Combining input standards and output standards. Input standards and output standards with the same VCCO requirement can be combined in the same bank. Compatible example: LVDS_25 output and HSTL_I input Incompatible example: LVDS_25 output (output VCCO = 2.5V) and HSTL_I_DCI_18 input (input VCCO = 1.8V) 4. Combining bidirectional standards with input or output standards. When combining bidirectional I/O with other standards, make sure the bidirectional standard can meet the first three rules. Additional rules for combining DCI I/O standards. a. No more than one Single Termination type (input or output) is allowed in the same bank. Incompatible example: HSTL_IV_DCI input and HSTL_III_DCI input b. No more than one Split Termination type (input or output) is allowed in the same bank. Incompatible example: HSTL_I_DCI input and HSTL_II_DCI input The implementation tools enforce these design rules.

5.

298

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Rules for Combining I/O Standards in the Same Bank

Table 6-39 summarizes the Virtex-5 FPGA supported I/O standards. Table 6-39: I/O Compatibility
VCCO Output LVTTL (1) LVCMOS33 (1) LVDCI_33 (1) HSLVDCI_33 (1) PCIX (1) PCI33_3 (1) PCI66_3 (1) LVDS_25 LVDSEXT_25 HT_25 RSDS_25(4) BLVDS_25 LVPECL_25 SSTL2_I SSTL2_II DIFF_SSTL2_I DIFF_SSTL2_II LVCMOS25 LVDCI_25 HSLVDCI_25 LVDCI_DV2_25 SSTL2_I_DCI SSTL2_II_DCI SSTL2_II_T_DCI DIFF_SSTL2_I_DCI DIFF_SSTL2_II_DCI 2.5 2.5 Note (2) 3.3 Input 3.3 VREF Input N/R N/R N/R VCCO/2 N/R N/R N/R N/R N/R N/R N/R N/R N/R 1.25 1.25 N/R N/R N/R N/R VCCO/2 N/R 1.25 1.25 1.25 N/R N/R Termination Type Output N/R N/R Series Series N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R Series Series Series N/R Split N/R N/R Split Input N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R Split Split Split Split Split

I/O Standard

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

299

Chapter 6: SelectIO Resources

Table 6-39:

I/O Compatibility (Continued)

VCCO Output Input Note (2) VREF Input 1.08 1.08 0.9 0.9 N/R N/R 0.9 0.9 N/R N/R 1.8 N/R N/R VCCO/2 N/R 1.08 1.08 0.9 0.9 0.9 N/R N/R 0.9 0.9 0.9 N/R N/R Termination Type Output N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R Series Series Series N/R Single N/R Split N/R N/R Split N/R Split N/R N/R Split Input N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R Single Single Split Split Split Split Split Split Split Split Split Split

I/O Standard HSTL_III_18 HSTL_IV_18 HSTL_I_18 HSTL_II_18 DIFF_HSTL_I_18 DIFF_HSTL_II_18 SSTL18_I SSTL18_II DIFF_SSTL18_I DIFF_SSTL18_II LVCMOS18 LVDCI_18 HSLVDCI_18 LVDCI_DV2_18 HSTL_III_DCI_18 HSTL_IV_DCI_18 HSTL_I_DCI_18 HSTL_II_DCI_18 HSTL_II_T_DCI_18 DIFF_HSTL_I_DCI_18 DIFF_HSTL_II_DCI_18 SSTL18_I_DCI SSTL18_II_DCI SSTL18_II_T_DCI DIFF_SSTL18_I_DCI DIFF_SSTL18_II_DCI 1.8

300

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Rules for Combining I/O Standards in the Same Bank

Table 6-39:

I/O Compatibility (Continued)

VCCO Output Input Note (2) VREF Input 0.9 0.9 0.75 0.75 N/R N/R 1.5 N/R N/R VCCO/2 N/R 1 0.9 0.9 0.75 0.75 0.75 N/R N/R 1.2 N/R 1.2 Note (2) 0.8 1 0.8
1.2 1.2

Termination Type Output N/R N/R N/R N/R N/R N/R N/R Series Series Series Single N/R Single N/R Split N/R N/R Split Single N/R N/R N/R N/R Input N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R Single Single Single Split Split Split Split Split Single N/R N/R N/R N/R

I/O Standard HSTL_III HSTL_IV HSTL_I HSTL_II DIFF_HSTL_I DIFF_HSTL_II LVCMOS15 LVDCI_15 HSLVDCI_15 LVDCI_DV2_15 GTLP_DCI HSTL_III_DCI HSTL_IV_DCI HSTL_I_DCI HSTL_II_DCI HSTL_II_T_DCI DIFF_HSTL_I_DCI DIFF_HSTL_II_DCI GTL_DCI GTLP GTL LVCMOS12 HSTL_I_12
Notes:

1.5

N/R 0.6

1. See 3.3V I/O Design Guidelines for more detailed information 2. Differential inputs and inputs using VREF are powered from VCCAUX. However, pin voltage must not exceed VCCO, due to the presence of clamp diodes to VCCO. 3. N/R = no requirement. 4. RSDS_25 has the same DC specifications as LVDS_25. All information pertaining to LVDS_25 is applicable to RSDS_25. 5. I/O standard is selected using the IOSTANDARD attribute.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

301

Chapter 6: SelectIO Resources

3.3V I/O Design Guidelines

To achieve maximum performance in Virtex-5 devices, several 3.3V I/O design guidelines and techniques are highlighted in this section. This includes managing overshoot/undershoot with termination techniques, regulating VCCO at 3.0V with a voltage regulator, using external bus switches, reviewing configuration methods, and other design considerations.

I/O Standard Design Rules

Overshoot/Undershoot
Undershoot and overshoot voltages on I/Os operating at 3.3V should not exceed the absolute maximum ratings of 0.3V to 4.05V, respectively, when VCCO is 3.75V. These absolute maximum limits are stated in the absolute maximum ratings table in the Virtex-5 FPGA Data Sheet. However, the maximum undershoot value is directly affected by the value of VCCO. The voltage across the gate oxide at any time must not exceed 4.05V. Consider the case in which the I/O is either an input or a 3-stated buffer as shown in Figure 6-91. The gate of the output PMOS transistor P0 and NMOS transistor N0 is connected essentially to VCCO and ground, respectively. The amount of undershoot allowed without overstressing the PMOS transistor P0 is the gate voltage minus the gate oxide limit, or VCCO 4.05V. Similarly, the absolute maximum overshoot allowed without overstressing the NMOS transistor N0 is the gate voltage plus the gate oxide limit, or Ground + 4.05V.
X-Ref Target - Figure 6-91

Output Driver
VCCO Po Power Clamp Diode DP

Input Buffer
VCCO

External Pin

Pi

No Ground Clamp Diode DG

Ni

GND

GND
ug190_6_85_030506

Figure 6-91:

Virtex-5 FPGA I/O: 3-State Output Driver

The clamp diodes offer protection against transient voltage beyond approximately VCCO + 0.5V and Ground 0.5V. The voltage across the diode increases proportionally to the current going through it. Therefore the clamped level is not fixed and can vary

302

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Rules for Combining I/O Standards in the Same Bank

depending on the board design. The absolute maximum I/O limits might be exceeded even if the clamp diode is active. The IBIS models contain the voltage-current characteristics of the I/O drivers and clamp diodes. To verify overshoot and undershoot are within the I/O absolute maximum specifications, Xilinx recommends proper I/O termination and performing IBIS simulation.

Source Termination and LVDCI_33

In general, the I/O drivers should match the board trace impedance to within 10% to minimize overshoot and undershoot. Source termination is often used for unidirectional interfaces. The DCI feature has built-in source termination on all user output pins. It compensates for impedance changes due to voltage and/or temperature fluctuations, and can match the reference resistor values. Assuming the reference resistor values are the same as the board trace impedance, the output impedance of the driver will closely match with the board trace. The LVDCI_33 standard is used to enable the DCI features for 3.3V I/O operations. As shown in Figure 6-92, the OBUF_LVDCI_33 primitive is used to implement the source termination function in Virtex-5 FPGA output drivers. The pull-up resistor connected to VRN and the pull-down resistor connected to VRP determine the output impedance of all the output drivers in the same bank. The Virtex-5 FPGA Digitally Controlled Impedance (DCI) section has more details on using DCI. Since the LVDCI_33 standard does not offer input termination, source termination must be implemented on the driver side. Figure 6-92 shows the recommended external source termination resistors to be incorporated on the external device side. The total impedance of the LVTTL/LVCMOS driver added to the series termination resistor R0 must match the board trace impedance 10 percent to minimize overshoot and undershoot. An IBIS simulation is advised for calculating the exact value needed for R0.
X-Ref Target - Figure 6-92

VCCO = 3.3V R0 Z0 LVTTL/ LVCMOS Driver R0 + RDriver = Z0 = 50 (typical)

VCCO RREF

VRN VRP IBUF_LVDCI_33

RREF

Virtex-5 FPGA Z0
OBUF_LVDCI_33

Any 3.3V I/O Device

External Device

ug190_6_86_030506

Figure 6-92: Connecting LVTTL or LVCMOS Using the LVDCI_33 Standard

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

303

Chapter 6: SelectIO Resources

The connection scheme shown in Figure 6-93 is for a bidirectional bus scenario. The signal performance may be degraded by R0. Therefore, it is also recommended to verify the R0 value and performance with an IBIS simulation.
X-Ref Target - Figure 6-93

OBUFT_LVDCI_33

R0 Z0

IBUF_LVDCI

Virtex-5 FPGA
Figure 6-93:

External Device
ug190_6_87_030506

3.3V I/O Configuration

When designing with the LVDCI_33 standard: The output drive strength and slew rates are not programmable. The output impedance references the VRP and VRN resistors, and the output current is determined by the output impedance. If only LVDCI_33 inputs are used, it is not necessary to connect VRP and VRN to external reference resistors. The implementation pad report does not record VRP and VRN being used. External reference resistors are required only if LVDCI_33 outputs are present in a bank. LVDCI_33 is compatible with LVTTL and LVCMOS standards only.

In addition, changing the slew rate from fast to slow and/or reducing the current drive could significantly reduce overshoot and undershoot. The Virtex-5 FPGA PCB Designers Guide contains additional design information to assist PCB designers and signal integrity engineers.

Regulating VCCO at 3.0V

The following section discusses alternatives for managing overshoot and undershoot for LVTTL, LVCMOS33, and PCI applications. When VCCO is lowered to 3.0V, the power clamp diode turns on at about 3.5V. Therefore it limits any overshoot higher than 3.5V before reaching the absolute maximum level of 4.05V. In addition, instead of 0.3V when VCCO = 3.75V, the lower absolute maximum limit corresponding to VCCO = 3.0V is 1.05V. In this case, the ground clamp diode clips undershoot before reaching the lower absolute maximum limit. As a result, lowering VCCO to 3.0V addresses the overshoot and undershoot specifications for all supported 3.3 V standards, including LVCMOS_33, LVTTL, LVDCI_33, and PCI.

Mixing Techniques
Either using LVDCI_33 standard or lowering the VCCO to 3.0V is a good approach to address overshoot and undershoot. It is also acceptable to combine both methods. When VCCO is lowered to 3.0V, it is not necessary to adjust the reference resistors VRP and VRN. The VRP and VRN values should always be the same as the board trace impedance.

304

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Simultaneous Switching Output Limits

Simultaneous Switching Output Limits

When multiple output drivers change state at the same time, power supply disturbance occurs. These disturbances can cause undesired transient behavior in output drivers, input receivers, or in internal logic. These disturbances are often referred to as SimultaneousSwitching Output (SSO) noise. The SSO limits govern the number and type of I/O output drivers that can be switched simultaneously while maintaining a safe level of SSO noise.

Sparse-Chevron Packages
Virtex-5 FPGA packaging utilizes a sparse-chevron pinout arrangement. The sparsechevron pinout style is an improvement over previous designs, offering low crosstalk and SSO noise. The pinout is designed to minimize PDS inductance and keep I/O signal return current paths very closely coupled to their associated I/O signal. The maximum ratio of I/O to reference pins (VCCO and GND) in sparse-chevron packages is 4:1. For every four I/O pins, there is always at least one reference pin. For boards that do not meet the nominal PCB requirements listed in Nominal PCB Specifications, the Virtex-5 FPGA SSO calculator is available, containing all SSO limit data for all I/O standards. For designs in nominal PCBs mixing limited and no limit I/O standards, the Virtex-5 FPGA SSO calculator must be used to ensure that I/O utilization does not exceed the limit. Information on the calculator is available under the Full Device SSO Calculator section. Unlike devices in previous families, Virtex-5 devices have only two bank sizes: 20 I/O and 40 I/O. With the ratio of signal to reference pins always constant, the SSO capacity of all banks of 20 I/O are the same, and the capacity of all banks of 40 I/O are the same. The SSO limits for Virtex-5 devices are listed on a per-bank basis rather than a limit per VCCO/GND pair.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

305

Chapter 6: SelectIO Resources

Nominal PCB Specifications

The nominal SSO table (Table 6-40) contains SSO limits for cases where the PCB parameters meet the following requirements. Note: In cases where PCB parameters do not meet all requirements listed below, the Virtex-5 FPGA
SSO Calculator must be used to determine the SSO limit, according to the physical factors of the unique PCB.

PCB Construction
VCCO and GND vias should have a drill diameter no less than 11 mils (279 ). Total board thickness must be no greater than 62 mils (1575 ).

Signal Return Current Management

Traces must be referenced to a plane on an adjacent PCB layer. The reference plane must be either GND or the VCCO associated with the output driver. The reference layer must remain uninterrupted for its full length from device to device.

Load Traces
All IOB output buffers must drive controlled impedance traces with characteristic impedance of 50 10%. Total capacitive loading at the far end of the trace (input capacitance of receiving device) must be no more than 10 pF.

Power Distribution System Design

Designed according to the Virtex-5 FPGA PCB Designers Guide. Decoupling capacitors per the device guideline Approved solder land patterns

VCCO and GND planes cannot be separated by more than 5.0 mils (152 )

306

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Simultaneous Switching Output Limits

Nominal SSO Limit

Table 6-40 provides the guidelines for the maximum number of simultaneously switching outputs allowed per bank to avoid the effects of ground bounce. Table 6-40:
Voltage 1.2V

Maximum Number of Simultaneously Switching Outputs per Bank

IOSTANDARD HSTL_I_12 LVCMOS12_2_slow LVCMOS12_4_slow LVCMOS12_6_slow LVCMOS12_8_slow LVCMOS12_2_fast LVCMOS12_4_fast LVCMOS12_6_fast LVCMOS12_8_fast Limit per 20-pin Bank 20 20 20 20 20 20 20 20 20 Limit per 40-pin Bank 40 40 40 40 40 40 40 40 40

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

307

Chapter 6: SelectIO Resources

Table 6-40:
Voltage 1.5V

Maximum Number of Simultaneously Switching Outputs per Bank (Continued)

IOSTANDARD LVCMOS15_2_slow LVCMOS15_4_slow LVCMOS15_6_slow LVCMOS15_8_slow LVCMOS15_12_slow LVCMOS15_16_slow LVCMOS15_2_fast LVCMOS15_4_fast LVCMOS15_6_fast LVCMOS15_8_fast LVCMOS15_12_fast LVCMOS15_16_fast LVDCI_15 50 HSTL_I_15 HSTL_I_15_DCI HSTL_II_15 HSTL_II_15_DCI HSTL_III_15 HSTL_III_15_DCI HSTL_IV_15 HSTL_IV_15_DCI HSLVDCI_15 50 DIFF_HSTL_I_15 DIFF_HSTL_I_15_DCI DIFF_HSTL_II_15 DIFF_HSTL_II_15_DCI Limit per 20-pin Bank 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 12 12 20 20 20 20 20 Limit per 40-pin Bank 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 25 25 40 40 40 40 40

308

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Simultaneous Switching Output Limits

Table 6-40:
Voltage 1.8V

Maximum Number of Simultaneously Switching Outputs per Bank (Continued)

IOSTANDARD LVCMOS18_2_slow LVCMOS18_4_slow LVCMOS18_6_slow LVCMOS18_8_slow LVCMOS18_12_slow LVCMOS18_16_slow LVCMOS18_2_fast LVCMOS18_4_fast LVCMOS18_6_fast LVCMOS18_8_fast LVCMOS18_12_fast LVCMOS18_16_fast LVDCI_18 50 HSTL_I_18 HSTL_I_DCI_18 HSTL_II_18 HSTL_II_DCI_18 HSTL_III_18 HSTL_III_DCI_18 HSTL_IV_18 HSTL_IV_DCI_18 SSTL18_I SSTL18_I_DCI SSTL18_II SSTL18_II_DCI HSLVDCI_18 50 DIFF_HSTL_I_18 DIFF_HSTL_I_DCI_18 DIFF_HSTL_II_18 DIFF_HSTL_II_DCI_18 DIFF_SSTL18_I DIFF_SSTL18_I_DCI DIFF_SSTL18_II DIFF_SSTL18_II_DCI Limit per 20-pin Bank 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 17 17 10 10 20 20 20 20 20 20 20 20 20 20 20 20 20 Limit per 40-pin Bank 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 35 35 20 20 40 40 40 40 40 40 40 40 40 40 40 40 40

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

309

Chapter 6: SelectIO Resources

Table 6-40:
Voltage 2.5V

Maximum Number of Simultaneously Switching Outputs per Bank (Continued)

IOSTANDARD LVCMOS25_2_slow LVCMOS25_4_slow LVCMOS25_6_slow LVCMOS25_8_slow LVCMOS25_12_slow LVCMOS25_16_slow LVCMOS25_24_slow LVCMOS25_2_fast LVCMOS25_4_fast LVCMOS25_6_fast LVCMOS25_8_fast LVCMOS25_12_fast LVCMOS25_16_fast LVCMOS25_24_fast LVDCI_25 50 SSTL2_I SSTL2_I_DCI SSTL2_II SSTL2_II_DCI HSLVDCI_25 50 DIFF_SSTL_I DIFF_SSTL_I_DCI DIFF_SSTL_II DIFF_SSTL_II_DCI LVPECL_25 BLVDS_25 LVDS_25 LVDSEXT_25 RSDS_25 HT_25 Limit per 20-pin Bank 20 20 20 20 20 20 20 20 20 20 20 20 20 15 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 Limit per 40-pin Bank 40 40 40 40 40 40 40 40 40 40 40 40 40 30 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40

310

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Simultaneous Switching Output Limits

Table 6-40:
Voltage 3.3V

Maximum Number of Simultaneously Switching Outputs per Bank (Continued)

IOSTANDARD LVCMOS33_2_slow LVCMOS33_4_slow LVCMOS33_6_slow LVCMOS33_8_slow LVCMOS33_12_slow LVCMOS33_16_slow LVCMOS33_24_slow LVCMOS33_2_fast LVCMOS33_4_fast LVCMOS33_6_fast LVCMOS33_8_fast LVCMOS33_12_fast LVCMOS33_16_fast LVCMOS33_24_fast LVTTL_2_slow LVTTL_4_slow LVTTL_6_slow LVTTL_8_slow LVTTL_12_slow LVTTL_16_slow LVTTL_24_slow LVTTL_2_fast LVTTL_4_fast LVTTL_6_fast LVTTL_8_fast LVTTL_12_fast LVTTL_16_fast LVTTL_24_fast PCI33_3 PCI66_3 PCIX Limit per 20-pin Bank 20 20 20 20 20 20 20 20 20 20 20 20 20 15 20 20 20 20 20 20 20 20 20 20 20 20 20 15 20 20 20 Limit per 40-pin Bank 40 40 40 40 40 40 40 40 40 40 40 40 40 30 40 40 40 40 40 40 40 40 40 40 40 40 40 30 40 40 40

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

311

Chapter 6: SelectIO Resources

Table 6-40:
Voltage 3.3V

Maximum Number of Simultaneously Switching Outputs per Bank (Continued)

IOSTANDARD GTL GTL_DCI GTLP GTLP_DCI LVDCI_33 50 HSLVDCI_33 50 Limit per 20-pin Bank 12 12 12 12 20 20 Limit per 40-pin Bank 25 25 25 25 40 40

Actual SSO Limits versus Nominal SSO Limits

The Virtex-5 FPGA SSO limits are defined for a set of nominal system conditions in Table 6-40. To compute the actual limits for a specific user's system, the Parasitic Factors Derating Method (PFDM) must be used. The PFDM allows the user to account for differences between actual and nominal PCB power systems, receiver capacitive loading, and maximum allowable ground bounce or VCC bounce. A spreadsheet calculator, Full Device SSO Calculator, automates this process.

Electrical Basis of SSO Noise

SSO noise can manifest as power supply disturbance, in the form of ground bounce or VCC bounce. GND and VCC bounce is a deviation of the die supply voltage (die GND rail or die VCC rail) with respect to the voltage of the associated PCB supply (PCB GND rail or PCB VCC rail). The deviation of die supplies from PCB supplies comes from the voltage induced across power system parasitics by supply current transients. One cause of current transients is output driver switching events. Numerous output switching events occurring at the same time lead to bigger current transients, and therefore bigger induced voltages (ground bounce, VCC bounce, or rail collapse). Relevant transient current paths exist in the die, package, and PCB, therefore, parasitics from all three must be considered. The larger the value of these parasitics, the larger the voltage induced by a current transient (powersupply disturbance). VCC bounce affects stable high outputs. Ground bounce affects stable low outputs. Ground bounce also affects inputs configured as certain I/O standards because they interpret incoming signals by comparing them to a threshold referenced to the die ground (as opposed to I/O standards with input thresholds referenced to a VREF voltage). If the die voltage disturbance exceeds the instantaneous noise margin for the interface, then a nonchanging input or output can be erroneously interpreted as changing. SSO noise can also manifest in the form of crosstalk between I/Os in close proximity to one another. The sparse chevron pinout of Virtex-5 devices reduces crosstalk in the pinout region to a minimum.

Parasitic Factors Derating Method (PFDM)

This section describes a method to evaluate whether a design is within the SSO limits when taking into account the specific electrical characteristics of the user's unique system. The SSO limits in Table 6-40 assume nominal values for the parasitic factors of the system. These factors fall into three groups of electrical characteristics: PCB PDS parasitics (nominal 1 nH per via)

312

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Simultaneous Switching Output Limits

Maximum allowable power system disturbance voltage (nominal 600 mV) Capacitive loading (nominal 10 pF per load)

When the electrical characteristics of a design differ from the nominal values, the system SSO limit changes. The degree of difference determines the new effective limit for the design. A figure called SSO Allowance is used as a single derating factor, taking into account the combined effect of all three groups of system electrical characteristics. The SSO allowance is a number ranging from 0 to 100% and is a product of three scaling factors: The First Scaling Factor accounts for the PCB PDS parasitic inductance. It is determined by dividing the nominal PCB PDS inductance by the user's PCB PDS inductance, LPDS_USR. The PCB PDS inductance is determined based on a set of board geometries: board thickness, via diameter, breakout trace width and length, and any other additional structures including sockets. The Second Scaling Factor accounts for the maximum allowable power system disturbance. It is determined by dividing the user's maximum allowable power system disturbance, (VDISTURBANCE_USER) by the nominal maximum power system disturbance. VDISTURBANCE_USER is usually determined by taking the lesser of input undershoot voltage and input logic low threshold. The Third Scaling Factor accounts for the capacitive loading of outputs driven by the FPGA. It is based on the transient current impact of every additional picofarad of load capacitance above the assumed nominal. For every additional 1 pF of load capacitance over the nominal, approximately 9 mV of additional power system disturbance will occur. The additional power system disturbance is compared to the nominal power system disturbance, and a scale factor is derived from the relationship. CLOAD_USER is the user's average load capacitance. Example calculations show how each scale factor is computed, as well as the SSO allowance. The system parameters used in this example are: LPDS_USER VDISTURBANCE_USER CLOAD_USER First Scaling Factor (SF1) = 1.1 nH = 550 mV = 22 pF = LPDS_NOM/LPDS_USER = 1.0 nH/1.1 nH = 0.909 = VDISTURBANCE_USER/VDISTURBANCE_NOM = 550 mV/600 mV = 0.917 Third Scaling Factor (SF3) = VDISTURBANCE_NOM/((CLOAD_USER CLOAD_NOM) 9 mV/pF) + VDISTURBANCE_NOM = 600 mV/((22 pF 15 pF) 9 mV/pF) + 600 mV = 600 mV/663 mV = 0.905

Second Scaling Factor (SF2)

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

313

Chapter 6: SelectIO Resources

SSO Allowance

= SF1 SF2 SF3 100% = 0.909 0.917 0.905 100% = 75.4%

Weighted Average Calculation of SSO

This section describes the SSO calculation where the SSO contributions of all I/O in a bank are combined into a single figure. SSO of an individual bank is calculated by summing the SSO contributions of the individual I/O standards in the bank. The SSO contribution is the percentage of full utilization of any one I/O standard in any one bank. For drivers of each I/O standard, the calculation follows: SSO Contribution (I/ O group n) = (quantity of drivers)/(Bank SSO limit) For a bank with drivers of multiple I/O standards, the SSO calculation is: Bank SSO =
( 1 to n )

SSO Contribution ( n )

A sample SSO calculation follows. The system parameters used are: Device: Bank: XC5VLX50 FF1153 11 12 6 19

I/O Standards, Quantities: SSTL2_II, LVCMOS25_24 Fast, LVCMOS25_6 Fast,

First, SSO limits for each I/O standard are obtained from Table 6-40:
I/O Group 1 2 3 I/O Standard SSTL2_II LVCMOS25_24 Fast LVCMOS25_6 Fast SSO Limit (Drivers per Bank) 40 30 40

The SSO contribution of each I/O standard is calculated as:

SSO Contribution SSO Contribution (1) SSO Contribution (2) SSO Contribution (3) = (quantity of drivers)/(Bank SSO limit) = = = 12/40 6/30 19/40 = = = 30% 20% 48%

Finally, the bank SSO is calculated: Bank 1 SSO = SSO contribution (1) + SSO contribution (2) + SSO Contribution (3) = 30% + 20% + 48% = 98%

314

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Simultaneous Switching Output Limits

Full Device SSO Calculator

A Microsoft Excel-based spreadsheet, the Virtex-5 FPGA SSO Calculator, automates all the PFDM and SSO calculations. The Virtex-5 FPGA SSO calculator uses PCB geometry, (board thickness, via diameter, and breakout trace width and length) to determine power system inductance. It determines the smallest undershoot and logic-low threshold voltage among all input devices, calculates the average output capacitance, and determines the SSO allowance by taking into account all of the board-level design parameters mentioned in this document. In addition, the Virtex-5 FPGA SSO calculator checks the adjacent bank and package SSO ensuring the full device design does not exceed the SSO allowance. Since bank-number assignment for Virtex-5 devices is different from package to package due to its columnar architecture (versus the peripheral I/O architecture of previous devices), there is a separate tab at the bottom of the SSO calculator display for each Virtex-5 FPGA package. This customizing allows for the arrangement of physically adjacent banks (as they appear clockwise on each unique package, even though they are not labeled in a contiguous manner), and the hard-coding of the number of VCCO/GND pairs per bank. The Virtex-5 FPGA SSO Calculator file (ug190_SSO_Calculator.zip) is available at: https://secure.xilinx.com/webreg/clickthrough.do?cid=30154.

Other SSO Assumptions

LVDCI and HSLVDCI Drivers
All limits for controlled impedance DCI I/O standards assume a 50 output impedance. For higher reference resistor (RR) values, less drive strength is needed, and the SSO limit increases linearly. To calculate the SSO limit for a controlled impedance driver with different reference resistors, the following formula is used: User RR User SSO = ----------------------- ( SSO Limit for ) 50

Example
The designer uses LVDCI_18 driver with 65 reference resistors. The LVDCI_18 SSO limit for 50 impedance is first taken from Table 6-40. The SSO limit for LVDCI_18 at 50 is 11 SSO per VCCO/GND pin pair. Therefore, the SSO limit for LVDCI_18 at 65 is: SSO Limit LVDCI_18 at 65 = ((65 )/50 ) 11 = 14.3

Bank 0
Bank 0 in all devices contains only configuration and dedicated signals. Since there is no user I/O in Bank 0, no SSO analysis is necessary for this bank.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

315

Chapter 6: SelectIO Resources

316

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Chapter 7

SelectIO Logic Resources

Introduction
This chapter describes the logic directly behind the I/O drivers and receivers covered in Chapter 6, SelectIO Resources. Virtex-5 FPGAs contain all of the basic I/O logic resources from Virtex-II/Virtex-II Pro FPGAs. These resources include the following: Combinatorial input/output 3-state output control Registered input/output Registered 3-state output control Double-Data-Rate (DDR) input/output DDR output 3-state control

In addition, Virtex-5 FPGAs implement the following architectural features that are also supported in Virtex-4 FPGAs: IODELAY provides users control of an adjustable, fine-resolution delay element SAME_EDGE output DDR mode SAME_EDGE and SAME_EDGE_PIPELINED input DDR mode

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

317

Chapter 7: SelectIO Logic Resources

ILOGIC Resources
The ILOGIC block shown in Figure 7-1.
X-Ref Target - Figure 7-1

D O DDLY

Q1 Q2

Q1 Q2

CE1 CLK

CE CK SR

REV

SR REV
ug190_7_01_050906

Figure 7-1: ILOGIC Block Diagram ILOGIC can support the following operations: Edge-triggered D-type flip-flop IDDR mode (OPPOSITE_EDGE or SAME_EDGE or SAME_EDGE_PIPELINED). See Input DDR Overview (IDDR), page 319 for further discussion on input DDR. Level sensitive latch Asynchronous/combinatorial

All ILOGIC block registers have a common clock enable signal (CE1) that is active High by default. If left unconnected, the clock enable pin for any storage element defaults to the active state. All ILOGIC block registers have a common synchronous or asynchronous set and reset (SR and REV signals). The set/reset input pin, SR forces the storage element into the state specified by the SRVAL attributes. When using SR, a second input, REV forces the storage element into the opposite state. The reset condition predominates over the set condition. Table 7-1 and Table 7-2 describe the operation of SR in conjunction with REV. Table 7-1:
SR 0 0 1 1

Truth Table when SRVAL = 0 (Default Condition)

REV 0 1 0 1 NOP Reset Set Reset Function

318

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

ILOGIC Resources

Table 7-2:
SR 0 0 1 1

Truth Table when SRVAL = 1

REV 0 1 0 1 NOP Set Reset Reset Function

The SRVAL attributes can be set individually for each storage element in the ILOGIC block, but the choice of synchronous or asynchronous set/reset (SRTYPE) can not be set individually for each storage element in the ILOGIC block. The following sections discuss the various resources within the ILOGIC blocks. All connections between the ILOGIC resources are managed in Xilinx software.

Combinatorial Input Path

The combinatorial input path is used to create a direct connection from the input driver to the FPGA fabric. This path is used by software automatically when: 1. 2. There is a direct (unregistered) connection from input data to logic resources in the FPGA fabric. The "pack I/O register/latches into IOBs" is set to OFF.

Input DDR Overview (IDDR)

Virtex-5 devices have dedicated registers in the ILOGIC to implement input double-datarate (DDR) registers. This feature is used by instantiating the IDDR primitive. There is only one clock input to the IDDR primitive. Falling edge data is clocked by a locally inverted version of the input clock. All clocks feeding into the I/O tile are fully multiplexed, i.e., there is no clock sharing between ILOGIC and OLOGIC blocks. The IDDR primitive supports the following modes of operation: OPPOSITE_EDGE mode SAME_EDGE mode SAME_EDGE_PIPELINED mode

The SAME_EDGE and SAME_EDGE_PIPELINED modes are the same as for the Virtex-4 architecture. These modes allow designers to transfer falling edge data to the rising edge domain within the ILOGIC block, saving CLB and clock resources, and increasing performance. These modes are implemented using the DDR_CLK_EDGE attribute. The following sections describe each of the modes in detail.

OPPOSITE_EDGE Mode
A traditional input DDR solution, or OPPOSITE_EDGE mode, is accomplished via a single input in the ILOGIC. The data is presented to the fabric via the output Q1 on the rising edge of the clock and via the output Q2 on the falling edge of the clock. This structure is similar to the Virtex-II, Virtex-II Pro, and Virtex-4 FPGA implementation. Figure 7-2 shows the timing diagram of the input DDR using the OPPOSITE_EDGE mode.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

319

Chapter 7: SelectIO Logic Resources

X-Ref Target - Figure 7-2

C CE D Q1 Q2 D0A D1A D2A D3A D4A D5A D6A D7A D8A D9A D10A D11A D12A D13A D0A D1A D2A D3A D4A D5A D6A D7A D8A D9A D10A D11A
ug190_7_02_041206

D12A

Figure 7-2:

Input DDR Timing in OPPOSITE_EDGE Mode

SAME_EDGE Mode
In the SAME_EDGE mode, the data is presented into the FPGA fabric on the same clock edge. However, the data pair to be separated by one clock cycle. This structure is similar to the Virtex-II, Virtex-II Pro, and Virtex-4 FPGA implementation. Figure 7-3 shows the timing diagram of the input DDR using SAME_EDGE mode. In the timing diagram, the output pairs Q1 and Q2 are no longer (0) and (1). Instead, the first pair presented is pair Q1 and Q2 (0) and (don't care) respectively, followed by pair (1) and (2) on the next clock cycle.
X-Ref Target - Figure 7-3

C CE D Q1 Q2 D0A D1A D2A D3A D4A D5A D6A D7A D8A D9A D10A D11A D0A Don't care D2A D1A D4A D3A D6A D5A D8A D7A D10A D9A D11A

ug190_7_03_041206

Figure 7-3:

Input DDR Timing in SAME_EDGE Mode

SAME_EDGE_PIPELINED Mode
In the SAME_EDGE_PIPELINED mode, the data is presented into the FPGA fabric on the same clock edge. Unlike the SAME_EDGE mode, the data pair is not separated by one clock cycle. However, an additional clock latency is required to remove the separated effect of the SAME_EDGE mode. Figure 7-4 shows the timing diagram of the input DDR using the SAME_EDGE_PIPELINED mode. The output pairs Q1 and Q2 are presented to the FPGA fabric at the same time.

320

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

ILOGIC Resources

X-Ref Target - Figure 7-4

C CE D Q1 Q2 D0A D1A D2A D3A D4A D5A D6A D7A D8A D9A D10A D11A D12A D13A D0A D1A D2A D3A D4A D5A D6A D7A D8A D9A D10A D11A

ug190_7_04_041206

Figure 7-4:

Input DDR Timing in SAME_EDGE_PIPELINED Mode

Input DDR Primitive (IDDR)

Figure 7-5 shows the block diagram of the IDDR primitive. Table 7-3 lists the IDDR port signals. Table 7-4 describes the various attributes available and default values for the IDDR primitive.
X-Ref Target - Figure 7-5

S D IDDR CE C Q1 Q2

R
ug190_7_05_062207

Figure 7-5: Table 7-3:

Port Name Q1 and Q2 C CE

IDDR Primitive Block Diagram

IDDR Port Signals

Function Data outputs Clock input port Clock enable port Description IDDR register outputs. The C pin represents the clock input pin. The enable pin affects the loading of data into the DDR flip-flop. When Low, clock transitions are ignored and new data is not loaded into the DDR flip-flop. CE must be High to load new data into the DDR flip-flop.

D R S

Data input (DDR) IDDR register input from IOB. Reset Set Synchronous/Asynchronous reset pin. Reset is asserted High. Synchronous/Asynchronous set pin. Set is asserted High.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

321

Chapter 7: SelectIO Logic Resources

Table 7-4:

IDDR Attributes
Description Sets the IDDR mode of operation with respect to clock edge Sets the initial value for Q1 port Sets the initial value for Q2 port Possible Values OPPOSITE_EDGE (default), SAME_EDGE, SAME_EDGE_PIPELINED 0 (default), 1 0 (default), 1

Attribute Name DDR_CLK_EDGE

INIT_Q1 INIT_Q2 SRTYPE

Set/Reset type with respect to clock (C) ASYNC (default), SYNC

IDDR VHDL and Verilog Templates

The Libraries Guide includes templates for instantiation of the IDDR primitive in VHDL and Verilog.

ILOGIC Timing Models

This section describes the timing associated with the various resources within the ILOGIC block.

ILOGIC Timing Characteristics

Figure 7-6 illustrates ILOGIC register timing. When IDELAY is used, TIDOCK is replaced by TIDOCKD.
X-Ref Target - Figure 7-6

CLK TIDOCK D TICE1CK CE1 TISRCK SR TICKQ Q1

ug190_7_06_041206

TICKQ

Figure 7-6:

ILOGIC Input Register Timing Characteristics

Clock Event 1
At time TICE1CK before Clock Event 1, the input clock enable signal becomes validHigh at the CE1 input of the input register, enabling the input register for incoming data. At time TIDOCK before Clock Event 1, the input signal becomes valid-High at the D input of the input register and is reflected on the Q1 output of the input register at time TICKQ after Clock Event 1.

322

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

ILOGIC Resources

Clock Event 4
At time TISRCK before Clock Event 4, the SR signal (configured as synchronous reset in this case) becomes valid-High resetting the input register and reflected at the Q1 output of the IOB at time TICKQ after Clock Event 4.

ILOGIC Timing Characteristics, DDR

Figure 7-7 illustrates the ILOGIC in IDDR mode timing characteristics. When IDELAY is used, TIDOCK is replaced by TIDOCKD. The example shown uses IDDR in OPPOSITE_EDGE mode. For other modes, add the appropriate latencies as shown in Figure 7-4, page 321.
X-Ref Target - Figure 7-7

1 CLK TIDOCK D

10

11

TIDOCK TICE1CK

CE1 TISRCK SR (Reset) TICKQ Q1 TICKQ Q2

UG190_7_07_041206

TICKQ TICKQ

Figure 7-7:

ILOGIC in IDDR Mode Timing Characteristics (OPPOSITE_EDGE Mode)

Clock Event 1
At time TICE1CK before Clock Event 1, the input clock enable signal becomes validHigh at the CE1 input of both of the DDR input registers, enabling them for incoming data. Since the CE1 and D signals are common to both DDR registers, care must be taken to toggle these signals between the rising edges and falling edges of CLK as well as meeting the register setup-time relative to both clocks. At time TIDOCK before Clock Event 1 (rising edge of CLK), the input signal becomes valid-High at the D input of both registers and is reflected on the Q1 output of input register 1 at time TICKQ after Clock Event 1.

Clock Event 2
At time TIDOCK before Clock Event 2 (falling edge of CLK), the input signal becomes valid-Low at the D input of both registers and is reflected on the Q2 output of input register 2 at time TICKQ after Clock Event 2 (no change in this case).

Clock Event 9
At time TISRCK before Clock Event 9, the SR signal (configured as synchronous reset in this case) becomes valid-High resetting Q1 at time TICKQ after Clock Event 9, and Q2 at time TICKQ after Clock Event 10.

Table 7-5 describes the function and control signals of the ILOGIC switching characteristics in the Virtex-5 FPGA Data Sheet.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

323

Chapter 7: SelectIO Logic Resources

Table 7-5:

ILOGIC Switching Characteristics

Description

Symbol Setup/Hold TICE1CK/TICKCE1 TISRCK/TICKSR TIDOCK/TIOCKD Combinatorial TIDI Sequential Delays TIDLO TICKQ TICE1Q TRQ
parameters.

CE1 pin Setup/Hold with respect to CLK SR/REV pin Setup/Hold with respect to CLK D pin Setup/Hold with respect to CLK

D pin to O pin propagation delay, no Delay

D pin to Q1 pin using flip-flop as a latch without Delay CLK to Q outputs CE1 pin to Q1 using flip-flop as a latch, propagation delay SR/REV pin to OQ/TQ out

Note: The DDLY timing diagrams and parameters are identical to the D timing diagrams and

324

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input/Output Delay Element (IODELAY)

Input/Output Delay Element (IODELAY)

Every I/O block contains a programmable absolute delay element called IODELAY. The IODELAY can be connected to an ILOGIC/ISERDES or OLOGIC/OSERDES block or both. IODELAY is a 64-tap, wraparound, delay element with a calibrated tap resolution. See the Virtex-5 FPGA Data Sheet. It can be applied to the combinatorial input path, registered input path, combinatorial output path, or registered output path. It can also be accessed directly in the fabric. IODELAY allows incoming signals to be delayed on an individual basis. The tap delay resolution is varied by selecting an IDELAYCTRL reference clock from the range specified in the Virtex-5 FPGA Data Sheet. The IODELAY resource can function as IDELAY, ODELAY, or bidirectional delay. When used as IDELAY, the data input comes from either IBUF or the fabric and the output goes to ILOGIC/ISERDES. There are three modes of operation available: Zero-hold time delay mode (IDELAY_TYPE = DEFAULT) This mode of operation allows backward compatibility for designs using the zero-hold time delay feature in Virtex-II, Virtex-II Pro and Virtex-4 devices. This delay element is used to provide non-positive hold times when global clocks are used without DCMs to capture data (pin-to-pin parameters). When used in this mode, the IDELAYCTRL primitive does not need to be instantiated. See IDELAYCTRL Usage and Design Guidelines for more details. Fixed delay mode (IDELAY_TYPE = FIXED) In the fixed delay mode, the delay value is preset at configuration to the tap number determined by the attribute IDELAY_VALUE. Once configured, this value cannot be changed. When used in this mode, the IDELAYCTRL primitive must be instantiated. See IDELAYCTRL Usage and Design Guidelines for more details. Variable delay mode (IDELAY_TYPE = VARIABLE) In the variable delay mode, the delay value can be changed after configuration by manipulating the control signals CE and INC. When used in this mode, the IDELAYCTRL primitive must be instantiated. See IDELAYCTRL Usage and Design Guidelines for more details. When used as ODELAY, the data input comes from OLOGIC/OSERDES and the data output goes to OBUF. There is a single mode of operation: Fixed delay output mode In the fixed delay output mode, the delay value is preset at configuration to the tap number determined by the attribute ODELAY_VALUE. Once configured, this value cannot be changed. When used in this mode, the IDELAYCTRL primitive must be instantiated. See IDELAYCTRL Usage and Design Guidelines for more details. When used as bidirectional delay, the IOB is configured in bidirectional mode. IODELAY alternately delays the data on the input path and output path. There are two modes of operation: Fixed IDELAY (IDELAY_TYPE = FIXED) and fixed ODELAY mode In this mode, both the values for IDELAY and ODELAY are preset at configuration and are determined by the IDELAY_VALUE and ODELAY_VALUE attributes. Once configured, this value cannot be changed. When used in this mode, the IDELAYCTRL primitive must be instantiated. See IDELAYCTRL Usage and Design Guidelines for more details.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

325

Chapter 7: SelectIO Logic Resources

Variable IDELAY (IDELAY_TYPE = VARIABLE) and fixed ODELAY mode In this mode, only the IDELAY value can be dynamically changed after configuration by manipulating the control signals CE and INC. The logic level of the T pin in the IODELAY primitive dynamically determines if the block is in IDELAY or ODELAY mode. When used in this mode, the IDELAYCTRL primitive must be instantiated. See IDELAYCTRL Usage and Design Guidelines for more details.

Figure 7-6 lists the supported IODELAY configurations. Table 7-6:

IODELAY Mode

IODELAY Configurations Supported

Direction of IODELAY I Input Pin Used in the IODELAY Element IDATAIN DATAIN O IBUF Fabric

Source

Destination

Supported Delay Modes

IDELAY ODELAY

ILOGIC/ISERDES/Fabric Default/Fixed/Variable Fixed/Variable Fixed

ODATAIN OLOGIC/OSERDES OBUF IDATAIN IBUF

Bidirectional I (when T = 1) Delay O (when T = 0)

ILOGIC/ISERDES/Fabric Fixed/Variable Fixed

ODATAIN OLOGIC/OSERDES OBUF

IODELAY Primitive
Figure 7-8 shows the IODELAY primitive.
X-Ref Target - Figure 7-8

IODELAY
ODATAIN IDATAIN T INC RST CE DATAIN C
ug190_7_08_041106

DATAOUT

Figure 7-8:

IODELAY Primitive

Table 7-7 lists the available ports in the IODELAY primitive. All ports are 1-bit wide. Table 7-7:
Port Name DATAOUT IDATAIN ODATAIN

IODELAY Primitive Ports

Direction Output Input Input Function Delayed data from one of three data input ports (IDATAIN, ODATAIN, DATAIN) Data input for IODELAY from the IOB. Data input for IODELAY from the OSERDES/OLOGIC

326

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input/Output Delay Element (IODELAY)

Table 7-7:
Port Name DATAIN T CE INC RST C

IODELAY Primitive Ports (Continued)

Direction Input Input Input Input Input Input Function Data input for IODELAY from the FPGA fabric 3-state input control port. This port determines dynamically if IODELAY is used as IDELAY or ODELAY. Enable increment/decrement function Increment/decrement number of tap delays Reset the IODELAY element to the pre-programmed value Clock input used in variable mode

IODELAY Ports
Data Input from the IOB - IDATAIN
The IDATAIN input is driven by its associated IOB. In IDELAY mode the data can be driven to either an ILOGIC/ISERDES block, directly into the FPGA fabric, or to both through the DATAOUT port with a delay set by the IDELAY_VALUE.

Data Input from the FPGA Fabric - ODATAIN

The ODATAIN input is driven by OLOGIC/OSERDES. In ODELAY mode, the ODATAIN drives the DATAOUT port which is connected to an IOB with a delay set by the ODELAY_VALUE.

Data Input for IODELAY from the FPGA Fabric - DATAIN

The DATAIN input is directly driven by the FPGA fabric providing a fabric logic accessible delay line. The data is driven back into the fabric through the DATAOUT port with a delay set by the IDELAY_VALUE. DATAIN can be locally inverted. The data cannot be driven to an IOB.

Data Output - DATAOUT

Delayed data from the three data input ports. DATAOUT connects to the fabric (IDELAY mode), or an IOB (ODELAY mode) or both (bidirectional delay mode). If used in the bidirectional delay mode, the T port dynamically switches between the IDATAIN and ODATAIN paths providing an alternating input/output delay based on the direction indicated by the 3-state signal T from the OLOGIC block.

3-state Input - T
This is the 3-state input control port. For bidirectional operation, the T pin signal also controls the T pin of the OBUFT.

Clock Input - C
All control inputs to IODELAY primitive (RST, CE, and INC) are synchronous to the clock input (C). A clock must be connected to this port when IODELAY is configured in variable mode. C can be locally inverted, and must be supplied by a global or regional clock buffer. This clock should be connected to the same clock in the SelectIO logic resources (when using ISERDES and OSERDES, C is connected to CLKDIV).

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

327

Chapter 7: SelectIO Logic Resources

Module Reset - RST

The IODELAY reset signal, RST, resets the delay element to a value set by the IDELAY_VALUE or ODELAY_VALUE attribute. If these attributes are not specified, a value of zero is assumed. The RST signal is an active-High reset and is synchronous to the input clock signal (C). The control pins are summarized in Table 7-8. Table 7-8:
Pin INC CE RST

Control Pin Descriptions

Type Input Input Input Value 1 1 1 Description Increment/decrement number of tap delays Enable increment/decrement function Reset delay element to pre-programmed value. If no value programmed, reset to 0

Increment/Decrement Signals - CE, INC

The increment/decrement is controlled by the enable signal (CE). This interface is only available for the IDELAY mode, when IDELAY_TYPE = VARIABLE. As long as CE remains High, IDELAY will increment or decrement by TIDELAYRESOLUTION every clock (C) cycle. The state of INC determines whether IDELAY will increment or decrement; INC = 1 increments, INC = 0 decrements, synchronously to the clock (C). If CE is Low the delay through IDELAY will not change regardless of the state of INC. When CE goes High, the increment/decrement operation begins on the next positive clock cycle. When CE goes Low, the increment/decrement operation ceases on the next positive clock cycle. IODELAY is a wrap-around programmable delay element. When the end of the delay element is reached (tap 63) a subsequent increment function will return to tap 0. The same applies to the decrement function: decrementing below zero moves to tap 63. The increment/decrement operation is summarized in Table 7-9. Table 7-9: Increment/Decrement Operations
Operation Reset to IDELAY_VALUE Increment tap count Decrement tap count No change
Notes:
1. RST takes precedence over CE and INC.

RST 1 0 0 0

CE x 1 1 0

INC x 1 0 x

328

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input/Output Delay Element (IODELAY)

IODELAY Attributes
Table 7-10 summarizes the IODELAY attributes. Table 7-10: IODELAY Attribute Summary
Attribute IDELAY_TYPE Value String: DEFAULT, FIXED, or VARIABLE Integer: 0 to 63 Default Value DEFAULT Description Sets the type of tap delay line. Default delay is used to guarantee zero hold times, fixed delay is used to set a static delay value, and variable delay is used to dynamically adjust the delay value. Specifies the fixed number of delay taps in fixed mode or the initial starting number of taps in variable mode (input path). Specifies the fixed number of delay taps (output path). When TRUE, this attribute reduces the output jitter. The difference in power consumption is quantified in the Xilinx Power Estimator tool. The SIGNAL_PATTERN attribute causes the timing analyzer to account for the appropriate amount of delay-chain jitter in the data or clock path. IDELAYCTRL reference clock frequency (MHz). I: IODELAY chain input is IDATAIN O: IODELAY chain input is ODATAIN IO: IODELAY chain input is IDATAIN and ODATAIN (controlled by T) DATAIN: IODELAY chain input is DATAIN

IDELAY_VALUE

ODELAY_VALUE

Integer: 0 to 63

0 TRUE

HIGH_PERFORMANCE_MODE Boolean: FALSE, TRUE SIGNAL_PATTERN String: DATA, CLOCK

DATA

REFCLK_FREQUENCY DELAY_SRC

Real: 190.0 to 210.0

200

String: I, O, IO, or DATAIN DATAIN

IDELAY_TYPE Attribute
The IDELAY_TYPE attribute sets the type of delay used. The attribute values are DEFAULT, FIXED, and VARIABLE. When set to DEFAULT, the zero-hold time delay element is selected. This delay element is used to guarantee non-positive hold times when global clocks are used without DCMs to capture data (pin-to-pin parameters). When set to FIXED, the tap-delay value is fixed at the number of taps determined by the IDELAY_VALUE attribute setting. This value is preset and cannot be changed after configuration. When set to VARIABLE, the variable tap delay element is selected. The tap delay can be incremented by setting CE = 1 and INC = 1, or decremented by CE = 1 and INC = 0. The increment/decrement operation is synchronous to C, the input clock signal.

IDELAY_VALUE Attribute
The IDELAY_VALUE attribute specifies the initial number of tap delays. The possible values are any integer from 0 to 63. The default value is zero. The value of the tap delay reverts to IDELAY_VALUE when the tap delay is reset. In variable mode this attribute determines the initial setting of the delay line.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

329

Chapter 7: SelectIO Logic Resources

ODELAY_VALUE Attribute
The ODELAY_VALUE attribute specifies tap delays. The possible values are any integer from 0 to 63. The default value is zero. The value of the tap delay reverts to ODELAY_VALUE when the tap delay is reset.

HIGH_PERFORMANCE_MODE Attribute
When TRUE, this attribute reduces the output jitter. This reduction results in a slight increase in power dissipation from the IODELAY element. When set to FALSE the IODELAY element consumes less power.

SIGNAL_PATTERN Attribute
Clock and data signals have different electrical profiles and therefore accumulate different amounts of jitter in the IODELAY chain. By setting the SIGNAL_PATTERN attribute, the user enables timing analyzer to account for jitter appropriately when calculating timing. A clock signal is periodic in nature and does not have long sequences of consecutive ones or zeroes, while data is random in nature and can have long and short sequences of ones and zeroes.

IODELAY Timing
Table 7-11 shows the IODELAY switching characteristics. Table 7-11: IODELAY Switching Characteristics
Symbol TIDELAYRESOLUTION TICECK/TICKCE TIINCCK/TICKINC TIRSTCK/TICKRST Description IDELAY tap resolution CE pin Setup/Hold with respect to C INC pin Setup/Hold with respect to C RST pin Setup/Hold with respect to C

Figure 7-9 shows an IDELAY timing diagram. It is assumed that IDELAY_VALUE = 0.

X-Ref Target - Figure 7-9

1 C RST CE INC DATAOUT Tap 0

Tap 1
UG190_7_09_100107

Figure 7-9:

IDELAY Timing Diagram

330

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input/Output Delay Element (IODELAY)

Clock Event 1
On the rising edge of C, a reset is detected, causing the output DATAOUT to select tap 0 as the output from the 64-tap chain (assuming IDELAY_VALUE = 0).

Clock Event 2
A pulse on CE and INC is captured on the rising edge of C. This indicates an increment operation. The output changes without glitches from tap 0 to tap 1. See Stability after an Increment/Decrement Operation.

Clock Event 3
CE and INC are no longer asserted, thus completing the increment operation. The output remains at tap 1 indefinitely until there is further activity on the RST, CE, or INC pins.

Stability after an Increment/Decrement Operation

Figure 7-9 shows a period of instability when the output is changing from one tap to another. Clearly, when the data value at tap 0 is different from the data value at tap 1, the output must change state. However, when the data values at tap 0 and tap 1 are the same (e.g., both 0 or both 1), then the transition from tap 0 to tap 1 causes no glitch or disruption on the output. This concept can be comprehended by imagining the receiver data signal in the IODELAY tap chain. If tap 0 and tap 1 are both near the center of the receiver data eye, then the data sampled at tap 0 should be no different than the data sampled at tap 1. In this case, the transition from tap 0 to tap 1 causes no change to the output. To ensure that this is the case, the increment/decrement operation of IODELAY is designed to be glitchless. The user can dynamically adjust the IODELAY tap setting in real-time while live user data is passing through the IODELAY element; the adjustments do not disrupt the live user data. The glitchless behavior also applies when an IODELAY element is used in the path of a clock signal. Adjusting the tap setting does not cause a glitch or disruption on the output. The tap setting of the IODELAY element in the clock path can be adjusted without disrupting state machines that could be running on that clock.

IODELAY VHDL and Verilog Instantiation Template

VHDL and Verilog instantiation templates are available in the Libraries Guide for all primitives and submodules. In VHDL, each template has a component declaration section and an architecture section. Each part of the template should be inserted within the VHDL design file. The port map of the architecture section should include the design signals names.

Fixed Delay Mode

The Libraries Guide includes templates showing how to instantiate the IODELAY module in fixed delay mode with a tap setting of 31. IDELAYCTRL must also be instantiated when operating in this mode. See IDELAYCTRL Overview, page 337.

Variable Delay Mode

The Libraries Guide shows how to instantiate the IODELAY module in variable delay mode. IDELAYCTRL must also be instantiated when operating in this mode. See IDELAYCTRL Overview, page 337.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

331

Chapter 7: SelectIO Logic Resources

IODELAY Turnaround Time Usage Model

When using IODELAY in bidirectional mode, the turnaround time needs to be considered. Figure 7-10 shows a simplified block diagram of the IODELAY in the Virtex-5 FPGA IOB that applies to one use of the bidirectional IODELAY functionality.
X-Ref Target - Figure 7-10

ODDR T1 T2 CLK ODDR D1 D2 ODATAIN

TSCONTROL

DATAOUT T ODATAIN IDATAIN MUX E CLK ODELAY_VALUE IDELAY_VALUE MUX F IBUF

IOB
OBUF PAD

IODELAY
IDDR Q1 Q2 Delay Chain

IODELAY_01_081407

Figure 7-10:

Basic Sections of Blocks Related to IODELAY Turnaround with Pertinent Paths Shown When DELAY_SRC = IO, MUXE and MUXF dynamically selects ODATAIN or IDATAIN and ODELAY_VALUE or IDELAY_VALUE inside the IODELAY block. The following Verilog code segment is used for demonstrating bidirectional IODELAY:
IDDR #( .DDR_CLK_EDGE ("SAME_EDGE"), .INIT_Q1 (1'b0), .INIT_Q2 (1'b0), .SRTYPE ("SYNC") )IDDR_INST ( .C(clk), .CE(1'b1), .D(DATAOUT), .R(1'b0), .S(1'b0), .Q1(Q1), .Q2(Q2) ); IOBUF #( .IOSTANDARD ("LVCMOS25") )IOBUF_INST ( .I(DATAOUT), .T(TSCONTROL), .O(IDATAIN), .IO(IOPAD_DATA) );

332

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input/Output Delay Element (IODELAY)

IODELAY #( .DELAY_SRC ("IO"), .IDELAY_TYPE ("FIXED"), .IDELAY_VALUE (12), .ODELAY_VALUE (12), .REFCLK_FREQUENCY (200.0) )IODELAY_INST ( .C(1'b0), .CE(1'b0), .DATAIN(1'b0), .IDATAIN(IDATAIN), .INC(1'b0), .ODATAIN(ODATAIN), .RST(1'b0), .T(TSCONTROL), .DATAOUT(DATAOUT) ); ODDR #( .DDR_CLK_EDGE ("SAME_EDGE"), .INIT (1'b0), .SRTYPE ("SYNC") )ODDR_INST ( .C(clk), .CE(1'b1), .D1(D1), .D2(D2), .R(1'b0), .S(1'b0), .Q(ODATAIN) ); ODDR #( .DDR_CLK_EDGE ("SAME_EDGE"), .INIT (1'b0), .SRTYPE ("SYNC") )TRI_ODDR_INST ( .C(clk), .CE(1'b1), .D1(T1), .D2(T2), .R(1'b0), .S(1'b0), .Q(TSCONTROL) ); IDELAYCTRL IDELAYCTRL_INST ( .REFCLK(refclk), .RST(RST), .RDY() );

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

333

Chapter 7: SelectIO Logic Resources

Two cases that use the bidirectional IODELAY functionality are important for a given I/O pin. The first case uses bidirectional IODELAY when the I/O is an output being switched to an input. Figure 7-11 shows the IOB and IODELAY moving toward the input mode as set by the TSCONTROL net coming from the ODDR flip-flop. This controls the selection of MUXes E and F for the IOB input path and IDELAY_VALUE, respectively. Additionally, the OBUF is 3-stated.
X-Ref Target - Figure 7-11

ODDR T1 T2 CLK ODDR D1 D2 ODATAIN

TSCONTROL

DATAOUT T ODATAIN IDATAIN MUX E CLK ODELAY_VALUE IDELAY_VALUE MUX F IBUF

IOB
OBUF PAD

IODELAY
IDDR Q1 Q2 Delay Chain

IODELAY_02_082107

Figure 7-11:

IODELAY and IOB in Input Mode when 3-state is Disabled

334

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input/Output Delay Element (IODELAY)

The timing diagram in Figure 7-12 shows the relevant signal timing for the case when the I/O is an output switching to an input using 3-state control. The switching characteristics shown in the diagram are specified in the Virtex-5 FPGA Data Sheet.
X-Ref Target - Figure 7-12

ODDR CLK
TOCKQ

TSCONTROL
TIOTP TIODDO_T ODDR CLK to 3-state deassertion time. Previous PAD Output Value ODDR CLK to IDELAY ready New PAD Input Value

PAD

IDDR CLK
Pad to IDDR Setup Time is: TIOPI + TIODDO_IDATAIN + TIDOCKD (where TIODDO_IDATAIN is a function of IDELAY_VALUE)
IODELAY_03_082107

Figure 7-12:

Relevant Timing Signals to Examine IODELAY Timing when the IOB Switches From an Output to an Input

The activities of the OBUFT pin are controlled by the propagation and state of the TSCONTROL signal from the ODDR flip-flop. The 3-state control data receipt on the OBUF and IDDR flip-flop from a PAD are in parallel with each other, depending on the IDELAY_VALUE setting the final value at the IDDR flip-flop input in response to a clock edge is valid before or after the pad is driven from the 3-state control. After the 3-state control propagates through to the PAD and the IODELAY has been switched to an input, the IDDR setup time is the sole determiner of timing based on the IDELAY_VALUE and other timing parameters defined in the Xilinx speed specification and represented in the ISE tools.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

335

Chapter 7: SelectIO Logic Resources

The second case uses bidirectional IODELAY when the I/O is an input switching to an output. Figure 7-13 shows the IOB and IODELAY moving toward the output mode as set by the 3-state TSCONTROL signal coming from the ODDR T flip-flop. This controls the selection of MUXes E and F for the output path and ODELAY_VALUE respectively. Additionally, the OBUF changes to not being 3-stated and starts to drive the PAD.
X-Ref Target - Figure 7-13

ODDR T1 T2 CLK ODDR D1 D2 ODATAIN

TSCONTROL

DATAOUT T ODATAIN IDATAIN MUX E CLK ODELAY_VALUE IDELAY_VALUE MUX F IBUF

IOB
OBUF PAD

IODELAY
IDDR Q1 Q2 Delay Chain

IODELAY_04_082107

Figure 7-13:

IODELAY and IOB in Output Mode when 3-state is Enabled

336

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input/Output Delay Element (IODELAY)

The timing diagram in Figure 7-14 shows the relevant signal timing for the case where the I/O switches from input to an output using 3-state control. The switching characteristics shown in the diagram are specified in the Virtex-5 FPGA Data Sheet.
X-Ref Target - Figure 7-14

Clock-to-Out with ODELAY_VALUE = 0 Clock-to-Out with ODELAY_VALUE = 63 TOCKQ + TIODDO_ODATAIN

ODDR CLK

DATAOUT

Clock to DATAOUT is variable based on internal timing the ODELAY_VALUE (0-63)

TSCONTROL

TIOTP TOCKQ

PAD

Previous PAD input value

Clock to PAD being driven or TOCKQ + TIODDO_ODATAIN + TIOOP

IODELAY_05_082107

Figure 7-14:

Relevant Timing Signals used to Examine IODELAY Timing when an IOB Changes from an Input to an Output

3-state control activities on the OBUF of the IOB and ODDR flip-flop to PAD timing are in parallel with each other, depending on the ODELAY_VALUE setting the final output value in response to a clock edge at the ODDR CLK pin is valid before or after the pad is driven from the 3-state control. After the 3-state control propagates through to the PAD and the IODELAY is turned around, the clock-to-output time of the ODDR flip-flop through the IODELAY element (with the ODELAY_VALUE setting) solely determines the clock-tooutput time to the pad.

IDELAYCTRL Overview
If the IODELAY or ISERDES primitive is instantiated with the IOBDELAY_TYPE attribute set to FIXED or VARIABLE, the IDELAYCTRL module must be instantiated. The IDELAYCTRL module continuously calibrates the individual delay elements (IODELAY) in its region (see Figure 7-17, page 340), to reduce the effects of process, voltage, and temperature variations. The IDELAYCTRL module calibrates IODELAY using the user supplied REFCLK.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

337

Chapter 7: SelectIO Logic Resources

IDELAYCTRL Primitive
Figure 7-15 shows the IDELAYCTRL primitive.
X-Ref Target - Figure 7-15

IDELAYCTRL
REFCLK RST RDY

ug190_7_10_041206

Figure 7-15:

IDELAYCTRL Primitive

IDELAYCTRL Ports
RST - Reset
The reset input pin (RST) is an active-High asynchronous reset. IDELAYCTRL must be reset after configuration (and the REFCLK signal has stabilized) to ensure proper IODELAY operation. A reset pulse width TIDELAYCTRL_RPW is required. IDELAYCTRL must be reset after configuration.

REFCLK - Reference Clock

The reference clock (REFCLK) provides a time reference to IDELAYCTRL to calibrate all IODELAY modules in the same region. This clock must be driven by a global clock buffer (BUFGCTRL). REFCLK must be FIDELAYCTRL_REF the specified ppm tolerance (IDELAYCTRL_REF_PRECISION) to guarantee a specified IODELAY resolution (TIDELAYRESOLUTION). REFCLK can be supplied directly from a user-supplied source, the PLL, or from the DCM, and must be routed on a global clock buffer.

RDY - Ready
The ready (RDY) signal indicates when the IODELAY modules in the specific region are calibrated. The RDY signal is deasserted if REFCLK is held High or Low for one clock period or more. If RDY is deasserted Low, the IDELAYCTRL module must be reset. The implementation tools allow RDY to be unconnected/ignored. Figure 7-16 illustrates the timing relationship between RDY and RST.

338

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input/Output Delay Element (IODELAY)

IDELAYCTRL Timing
Table 7-12 shows the IDELAYCTRL switching characteristics. Table 7-12: IDELAYCTRL Switching Characteristics
Symbol Description REFCLK frequency REFCLK precision Reset/Startup to Ready for IDELAYCTRL

FIDELAYCTRL_REF
IDELAYCTRL_REF_PRECISION

TIDELAYCTRLCO_RDY

As shown in Figure 7-16, the Virtex-5 FPGA RST is an edge-triggered signal.

X-Ref Target - Figure 7-16

REFCLK

RST
TIDELAYCTRLCO_RDY

RDY
ug190_7_11_041206

Figure 7-16:

Timing Relationship Between RST and RDY

IDELAYCTRL Locations
IDELAYCTRL modules exist in every I/O column in every clock region. An IDELAYCTRL module calibrates all the IDELAY modules within its clock region. See Global and Regional Clocks in Chapter 1 for the definition of a clock region. Figure 7-17 illustrates the relative locations of the IDELAYCTRL modules.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

339

Chapter 7: SelectIO Logic Resources

X-Ref Target - Figure 7-17

Left I/O Column

Center I/O Column

CMT

Right I/O Column

1 Clock Region

IDELAYCTRL

Configuration

CMT
ug190_7_12_041206

Figure 7-17:

Relative Locations of IDELAYCTRL Modules

IDELAYCTRL Usage and Design Guidelines

This section describes using the IDELAYCTRL modules, design guidelines, and recommended usage in Virtex-5 devices.

Instantiating IDELAYCTRL Without LOC Constraints

When instantiating IDELAYCTRL without LOC constraints, the user must instantiate only one instance of IDELAYCTRL in the HDL design code. The implementation tools autoreplicate IDELAYCTRL instances throughout the entire device. When IDELAYCTRL instances are replicated to clock regions but not used, the extra instances are trimmed out of the design automatically by the ISE software. The signals connected to the RST and REFCLK input ports of the instantiated IDELAYCTRL instance are connected to the corresponding input ports of the replicated IDELAYCTRL instances. There are two special cases: 1. When the RDY port is ignored, the RDY signals of all the replacement IDELAYCTRL instances are left unconnected. The VHDL and Verilog use models for instantiating an IDELAYCTRL primitive without LOC constraints leaving the RDY output port unconnected are provided in the Libraries Guide. The resulting circuitry after instantiating the IDELAYCTRL components is illustrated in Figure 7-18.

340

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input/Output Delay Element (IODELAY)

X-Ref Target - Figure 7-18

Instantiated by user

REFCLK RST

REFCLK RST

RDY

IDELAYCTRL

REFCLK

RDY

IDELAYCTRL
RST

RDY signal ignored

. . .

. . .

Replicated for . all IDELAYCTRL . sites

.
RDY

REFCLK

IDELAYCTRL
RST

Auto-generated by mapper tool

ug190_7_13_041206

Figure 7-18: 2.

Instantiate IDELAYCTRL Without LOC Constraints - RDY Unconnected

When RDY port is connected, an AND gate of width equal to the number of clock regions is instantiated and the RDY output ports from the instantiated and replicated IDELAYCTRL instances are connected to the inputs of the AND gate. The tools assign the signal name connected to the RDY port of the instantiated IDELAYCTRL instance to the output of the AND gate. The VHDL and Verilog use models for instantiating an IDELAYCTRL primitive without LOC constraints with the RDY port connected are provided in the Libraries Guide. The resulting circuitry after instantiating the IDELAYCTRL components is illustrated in Figure 7-19.

X-Ref Target - Figure 7-19

Instantiated by user

REFCLK RST

REFCLK RDY IDELAYCTRL RST

REFCLK RDY IDELAYCTRL RST

RDY

. . .

. . .

Replicated for all IDELAYCTRL . sites .

REFCLK RDY IDELAYCTRL RST

Auto-generated by mapper tool

ug190_7_14_041306

Figure 7-19:

Instantiate IDELAYCTRL Without LOC Constraints - RDY Connected

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

341

Chapter 7: SelectIO Logic Resources

Instantiating IDELAYCTRL with Location (LOC) Constraints

The most efficient way to use the IDELAYCTRL module is to define and lock down the placement of every IDELAYCTRL instance used in a design. This is done by instantiating the IDELAYCTRL instances with location (LOC) constraints. The user must define and lock placement of all ISERDES and IDELAY components using the delay element. (IDELAY_TYPE attribute set to FIXED or VARIABLE). Once completed, IDELAYCTRL sites can be chosen and LOC constraints assigned. Xilinx strongly recommends using IDELAYCTRL with a LOC constraint. When not using an IDELAY (with IDELAY_TYPE in FIXED or VARIABLE mode) do not assign a LOC constraint to the IDELAYCTRL for that clock region.

Location Constraints
Each IDELAYCTRL module has XY location coordinates (X:row, Y:column). To constrain placement, IDELAYCTRL instances can have LOC properties attached to them. The naming convention for IDELAYCTRL placement coordinates is different from the convention used in naming CLB locations. This allows LOC properties to transfer easily from array to array. There are two methods of attaching LOC properties to IDELAYCTRL instances. 1. 2. Insert LOC constraints in a UCF file Embed LOC constraints directly into HDL design files

Inserting LOC Constraints in a UCF File

The following syntax is used for inserting LOC constraints in a UCF file.
INST "instance_name" LOC=IDELAYCTRL_X#Y#;

Embedding LOC Constraints Directly into HDL Design Files

The following syntax is used to embed LOC constraints into a Verilog design file.
// synthesis attribute loc of instance_name is "IDELAYCTRL_X#Y0#";

In VHDL code, the LOC constraint is described with VHDL attributes. Before it can be used, the constraint must be declared with the following syntax:
attribute loc : string;

Once declared, the LOC constraint can be specified as:

attribute loc of instance_name:label is "IDELAYCTRL_X#Y0#";

The Libraries Guide includes VHDL and Verilog use model templates for instantiating IDELAYCTRL primitives with LOC constraints. The circuitry that results from instantiating the IDELAYCTRL components is shown in Figure 7-20.

342

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input/Output Delay Element (IODELAY)

X-Ref Target - Figure 7-20

REFCLK
rst_1

REFCLK

RDY

rdy_1

IDELAYCTRL_1 RST

REFCLK

RDY

rdy_2

rst_2

IDELAYCTRL_2 RST

. . .

. . .
REFCLK RDY IDELAYCTRL_n RST

. . .
rdy_n

rst_n

ug190_7_15_041306

Figure 7-20:

Instantiate IDELAYCTRL with LOC Constraint

Instantiating IDELAYCTRL With and Without LOC Constraints

There are cases where the user instantiates an IDELAYCTRL module with a LOC constraint but also instantiates an IDELAYCTRL module without a LOC constraint. In the case where an IP Core is instantiated with a non-location constrained IDELAYCTRL module and also wants to instantiate an IDELAYCTRL module without a LOC constraint for another part of the design, the implementation tools will perform the following: Instantiate the LOC IDELAYCTRL instances as described in the section Instantiating IDELAYCTRL with Location (LOC) Constraints. Replicate the non-location constrained IDELAYCTRL instance to populate with an IDELAYCTRL instance in every clock region without a location constrained IDELAYCTRL instance in place. The signals connected to the RST and REFCLK input ports of the non-location constrained IDELAYCTRL instance are connected to the corresponding input ports of the replicated IDELAYCTRL instances. If the RDY port of the non-location constrained IDELAYCTRL instance is ignored, then all the RDY signals of the replicated IDELAYCTRL instances are also ignored. If the RDY port of the non-location constrained IDELAYCTRL instance is connected, then the RDY port of the non-location constrained instance plus the RDY ports of the replicated instances are connected to an auto-generated AND gate. The implementation tools assign the signal name connected to the RDY port of the nonlocation constrained instance to the output of the AND gate. All the ports of the location constrained instances (RST, REFCLK, and RDY) are independent from each other and from the replicated instances.

The VHDL and Verilog use models for instantiating a mixed usage model are provided in the Libraries Guide. In the example, a user is instantiating a non-location constrained IDELAYCTRL instance with the RDY signal connected. This discussion is also valid when the RDY signal is ignored. The circuitry that results from instantiating the IDELAYCTRL components is illustrated in Figure 7-21.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

343

Chapter 7: SelectIO Logic Resources

X-Ref Target - Figure 7-21

Instantiated with LOC Constraint

REFCLK rst_1

REFCLK RST

RDY

rdy_1

IDELAYCTRL_1

REFCLK

RDY

rdy_2

IDELAYCTRL_2

rst_2
. . .

RST

. . .
REFCLK RDY

. . .

rdy_n

IDELAYCTRL_n

rst_n

RST

Instantiated without LOC Constraint

REFCLK RDY

RST_NOLOC

IDELAYCTRL_noloc
RST

REFCLK RST

RDY

RDY_NOLOC

IDELAYCTRL_noloc

. . .

. . .

Replicated for . all IDELAYCTRL . sites .

REFCLK RST RDY

IDELAYCTRL_noloc

Auto-generated by mapper tool

ug190_7_16_041306

Figure 7-21:

Mixed Instantiation of IDELAYCTRL Elements

Instantiating Multiple IDELAYCTRLs Without LOC Constraints

Instantiating multiple IDELAYCTRL instances without LOC properties is prohibited. If this occurs, an error is issued by the implementation tools.

OLOGIC Resources
OLOGIC consists of two major blocks, one to configure the output data path and the other to configure the 3-state control path. These two blocks have a common clock (CLK) but different enable signals, OCE and TCE. Both have asynchronous and synchronous set and reset (SR and REV signals) controlled by an independent SRVAL attribute as described in the Table 7-1 and Table 7-2.

344

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

OLOGIC Resources

The Output and the 3-State paths can be configured in one of the following modes independently. Edge triggered D type flip-flop DDR mode (SAME_EDGE or OPPOSITE_EDGE) Level Sensitive Latch Asynchronous/combinatorial

Figure 7-22 illustrates the various logic resources in the OLOGIC block.
X-Ref Target - Figure 7-22

T1 D1 T2 TCE CLK D2 CE CK SR D1 D1 D2 OCE D2 CE CK SR SR REV

ug190_7_17_041206

TQ

REV

OQ

REV

Figure 7-22:

OLOGIC Block Diagram

This section of the documentation discusses the various features available using the OLOGIC resources. All connections between the OLOGIC resources are managed in Xilinx software.

Combinatorial Output Data and 3-State Control Path

The combinatorial output paths create a direct connection from the FPGA fabric to the output driver or output driver control. These paths is used when: 1. 2. There is direct (unregistered) connection from logic resources in the FPGA fabric to the output data or 3-state control. The pack I/O register/latches into IOBs is set to OFF.

Output DDR Overview (ODDR)

Virtex-5 devices have dedicated registers in the OLOGIC to implement output DDR registers. This feature is accessed when instantiating the ODDR primitive. DDR multiplexing is automatic when using OLOGIC. No manual control of the mux-select is needed. This control is generated from the clock. There is only one clock input to the ODDR primitive. Falling edge data is clocked by a locally inverted version of the input clock. All clocks feeding into the I/O tile are fully multiplexed, i.e., there is no clock sharing between ILOGIC or OLOGIC blocks. The ODDR primitive supports the following modes of operation: OPPOSITE_EDGE mode SAME_EDGE mode

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

345

Chapter 7: SelectIO Logic Resources

The SAME_EDGE mode is the same as for the Virtex-4 architecture. This mode allows designers to present both data inputs to the ODDR primitive on the rising-edge of the ODDR clock, saving CLB and clock resources, and increasing performance. This mode is implemented using the DDR_CLK_EDGE attribute. It is supported for 3-state control as well. The following sections describe each of the modes in detail.

OPPOSITE_EDGE Mode
In OPPOSITE_EDGE mode, both the edges of the clock (CLK) are used to capture the data from the FPGA fabric at twice the throughput. This structure is similar to the Virtex-II Virtex-II Pro, and Virtex-4 FPGA implementation. Both outputs are presented to the data input or 3-state control input of the IOB. The timing diagram of the output DDR using the OPPOSITE_EDGE mode is shown in Figure 7-23.
X-Ref Target - Figure 7-23

CLK OCE D1 D2 OQ D1A D2A D1B D2B D1C D2C D1D D2D

D1A D2A D1B D2B D1C D2C D1D

ug190_7_18_041206

Figure 7-23: Output DDR Timing in OPPOSITE_EDGE Mode

SAME_EDGE Mode
In SAME_EDGE mode, data can be presented to the IOB on the same clock edge. Presenting the data to the IOB on the same clock edge avoids setup time violations and allows the user to perform higher DDR frequency with minimal register to register delay, as opposed to using the CLB registers. Figure 7-24 shows the timing diagram of the output DDR using the SAME_EDGE mode.
X-Ref Target - Figure 7-24

CLK OCE D1 D2 OQ
Figure 7-24:

D1A D2A

D1B D2B

D1C D2C

D1D D2D

D1A D2A D1B D2B D1C D2C D1D

ug190_7_19_041206

Output DDR Timing in SAME_EDGE Mode

346

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

OLOGIC Resources

Clock Forwarding
Output DDR can forward a copy of the clock to the output. This is useful for propagating a clock and DDR data with identical delays, and for multiple clock generation, where every clock load has a unique clock driver. This is accomplished by tying the D1 input of the ODDR primitive High, and the D2 input Low. Xilinx recommends using this scheme to forward clocks from the FPGA fabric to the output pins.

Output DDR Primitive (ODDR)

Figure 7-25 shows the ODDR primitive block diagram. Table 7-13 lists the ODDR port signals. Table 7-14 describes the various attributes available and default values for the ODDR primitive.
X-Ref Target - Figure 7-25

S D1 D2 CE C ODDR Q

R
ug190_7_20_012207

Figure 7-25: Table 7-13:

Port Name Q C CE D1 and D2 R S

ODDR Primitive Block Diagram

ODDR Port Signals

Function Data output (DDR) Clock input port Clock enable port Data inputs Reset Set Description ODDR register output. The CLK pin represents the clock input pin. CE represents the clock enable pin. When asserted Low, this port disables the output clock on port Q. ODDR register inputs. Synchronous/Asynchronous reset pin. Reset is asserted High. Synchronous/Asynchronous set pin. Set is asserted High.

Table 7-14:

ODDR Attributes
Description Sets the ODDR mode of operation with respect to clock edge Sets the initial value for Q port Set/Reset type with respect to clock (C) Possible Values OPPOSITE_EDGE (default), SAME_EDGE 0 (default), 1 ASYNC, SYNC (default)

Attribute Name DDR_CLK_EDGE INIT SRTYPE

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

347

Chapter 7: SelectIO Logic Resources

ODDR VHDL and Verilog Templates

The Libraries Guide includes templates for instantiation of the ODDR module in VHDL and Verilog.

OLOGIC Timing Models

This section discusses all timing models associated with the OLOGIC block. Table 7-15 describes the function and control signals of the OLOGIC switching characteristics in the Virtex-5 FPGA Data Sheet. Table 7-15: OLOGIC Switching Characteristics
Description

Symbol Setup/Hold TODCK/TOCKD TOOCECK/TOCKOCE TOSRCK/TOCKSR TOTCK/TOCKT TOTCECK/TOCKTCE Clock to Out TOCKQ TRQ CLK to OQ/TQ out

D1/D2 pins Setup/Hold with respect to CLK OCE pin Setup/Hold with respect to CLK SR/REV pin Setup/Hold with respect to CLK T1/T2 pins Setup/Hold with respect to CLK TCE pin Setup/Hold with respect to CLK

SR/REV pin to OQ/TQ out

Timing Characteristics
Figure 7-26 illustrates the OLOGIC output register timing.
X-Ref Target - Figure 7-26

CLK TODCK D1 TOOCECK OCE TOSRCK SR TOCKQ OQ

ug190_7_21_041206

Figure 7-26: OLOGIC Output Register Timing Characteristics

348

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

OLOGIC Resources

Clock Event 1
At time TOOCECK before Clock Event 1, the output clock enable signal becomes validHigh at the OCE input of the output register, enabling the output register for incoming data. At time TODCK before Clock Event 1, the output signal becomes valid-High at the D1 input of the output register and is reflected at the OQ output at time TOCKQ after Clock Event 1.

Clock Event 4
At time TOSRCK before Clock Event 4, the SR signal (configured as synchronous reset in this case) becomes valid-High, resetting the output register and reflected at the OQ output at time TRQ after Clock Event 4. Figure 7-27 illustrates the OLOGIC ODDR register timing.
X-Ref Target - Figure 7-27

1 CLK

10

11

TODCK D1 TODCK D2 TOOCECK OCE TOSRCK SR TOCKQ OQ TRQ

ug190_7_22_012407

Figure 7-27:

OLOGIC ODDR Register Timing Characteristics

Clock Event 1
At time TOOCECK before Clock Event 1, the ODDR clock enable signal becomes validHigh at the OCE input of the ODDR, enabling ODDR for incoming data. Care must be taken to toggle the OCE signal of the ODDR register between the rising edges and falling edges of CLK as well as meeting the register setup-time relative to both clock edges. At time TODCK before Clock Event 1 (rising edge of CLK), the data signal D1 becomes valid-High at the D1 input of ODDR register and is reflected on the OQ output at time TOCKQ after Clock Event 1.

Clock Event 2
At time TODCK before Clock Event 2 (falling edge of CLK), the data signal D2 becomes valid-High at the D2 input of ODDR register and is reflected on the OQ output at time TOCKQ after Clock Event 2 (no change at the OQ output in this case).

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

349

Chapter 7: SelectIO Logic Resources

Clock Event 9
At time TOSRCK before Clock Event 9 (rising edge of CLK), the SR signal (configured as synchronous reset in this case) becomes valid-High resetting ODDR register, reflected at the OQ output at time TRQ after Clock Event 9 (no change at the OQ output in this case) and resetting ODDR register, reflected at the OQ output at time TRQ after Clock Event 10 (no change at the OQ output in this case). Figure 7-28 illustrates the OLOGIC 3-state register timing.
X-Ref Target - Figure 7-28

1 CLK TOTCK T1 TOTCECK TCE

TOSRCK SR TOCKQ TQ
UG190_7_23_041106

TRQ

Figure 7-28:

OLOGIC 3-State Register Timing Characteristics

Clock Event 1
At time TOTCECK before Clock Event 1, the 3-state clock enable signal becomes validHigh at the TCE input of the 3-state register, enabling the 3-state register for incoming data. At time TOTCK before Clock Event 1 the 3-state signal becomes valid-High at the T input of the 3-state register, returning the pad to high-impedance at time TOCKQ after Clock Event 1.

Clock Event 2
At time TOSRCK before Clock Event 2, the SR signal (configured as synchronous reset in this case) becomes valid-High, resetting the 3-state register at time TRQ after Clock Event 2.

Figure 7-29 illustrates IOB DDR 3-state register timing. This example is shown using DDR in opposite edge mode. For other modes add the appropriate latencies as shown in Figure 7-4, page 321.

350

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

OLOGIC Resources

X-Ref Target - Figure 7-29

1 CLK

10

11

TOTCK T1 TOTCK T2 TOTCECK TCE TOSRCK SR TOCKQ TRQ

TQ

ug190_7_24_041106

Figure 7-29:

OLOGIC ODDR 3-State Register Timing Characteristics

Clock Event 1
At time TOTCECK before Clock Event 1, the 3-state clock enable signal becomes validHigh at the TCE input of the 3-state ODDR register, enabling them for incoming data. Care must be taken to toggle the TCE signal of the 3-state ODDR between the rising edges and falling edges of CLK as well as meeting the register setup-time relative to both clock edges. At time TOTCK before Clock Event 1 (rising edge of CLK), the 3-state signal T1 becomes valid-High at the T1 input of 3-state register and is reflected on the TQ output at time TOCKQ after Clock Event 1.

Clock Event 2
At time TOTCK before Clock Event 2 (falling edge of CLK), the 3-state signal T2 becomes valid-High at the T2 input of 3-state register and is reflected on the TQ output at time TOCKQ after Clock Event 2 (no change at the TQ output in this case).

Clock Event 9
At time TOSRCK before Clock Event 9 (rising edge of CLK), the SR signal (configured as synchronous reset in this case) becomes valid-High resetting 3-state Register, reflected at the TQ output at time TRQ after Clock Event 9 (no change at the TQ output in this case) and resetting 3-state Register, reflected at the TQ output at time TRQ after Clock Event 10 (no change at the TQ output in this case).

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

351

Chapter 7: SelectIO Logic Resources

352

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Chapter 8

Advanced SelectIO Logic Resources

Introduction
The I/O functionality in Virtex-5 FPGAs is described in Chapter 6 through Chapter 8 of this user guide. Chapter 6 covers the electrical characteristics of input receivers and output drivers, and their compliance with many industry standards. Chapter 7 describes the register structures dedicated for sending and receiving SDR or DDR data. This chapter covers additional resources: Input serial-to-parallel converters (ISERDES) and output parallel-to-serial converters (OSERDES) support very fast I/O data rates, and allow the internal logic to run up to 10 times slower than the I/O. The Bitslip submodule can re-align data to word boundaries, detected with the help of a training pattern.

Input Serial-to-Parallel Logic Resources (ISERDES)

The ISERDES in Virtex-5 FPGAs is a dedicated serial-to-parallel converter with specific clocking and logic features designed to facilitate the implementation of high-speed sourcesynchronous applications. The ISERDES avoids the additional timing complexities encountered when designing deserializers in the FPGA fabric. ISERDES features include: Dedicated Deserializer/Serial-to-Parallel Converter The ISERDES deserializer enables high-speed data transfer without requiring the FPGA fabric to match the input data frequency. This converter supports both single data rate (SDR) and double data rate (DDR) modes. In SDR mode, the serial-to-parallel converter creates a 2-, 3-, 4-, 5-, 6-, 7-, or 8-bit wide parallel word. In DDR mode, the serial-to-parallel converter creates a 4-, 6-, 8-, or 10-bit-wide parallel word. Bitslip Submodule The Bitslip submodule allows designers to reorder the sequence of the parallel data stream going into the FPGA fabric. This can be used for training source-synchronous interfaces that include a training pattern. Dedicated Support for Strobe-based Memory Interfaces ISERDES contains dedicated circuitry (including the OCLK input pin) to handle the strobe-to-FPGA clock domain crossover entirely within the ISERDES block. This allows for higher performance and a simplified implementation.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

353

Chapter 8: Advanced SelectIO Logic Resources

Dedicated support for Networking interfaces.

Figure 8-1 shows the block diagram of the ISERDES, highlighting all the major components and features of the block.
X-Ref Target - Figure 8-1

D CLKDIV

CE1 CE2 CE Module

Serial to Parallel Converter

SHIFTIN1/2

SHIFTOUT1/2

Q1 - Q6

OCLK CLK BITSLIP Module

RST Bitslip
ug190_8_01_050906

Figure 8-1:

ISERDES Block Diagram

ISERDES Primitive (ISERDES_NODELAY)

The ISERDES primitive in Virtex-5 devices (shown in Figure 8-2) is ISERDES_NODELAY.
X-Ref Target - Figure 8-2

BITSLIP Q1 CE1 Q2 CE2 Q3 CLK Q4 CLKB CLKDIV D OCLK SHIFTIN1 SHIFTIN2 RST
ug190_8_02_112607

Q5

ISERDES_NODELAY Primitive

Q6 SHIFTOUT1 SHIFTOUT2

Figure 8-2:

ISERDES_NODELAY Primitive

354

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input Serial-to-Parallel Logic Resources (ISERDES)

Table 8-1 lists the available ports in the ISERDES_NODELAY primitive. Table 8-1: ISERDES_NODELAY Port List and Definitions
Type Output Output Output Input Input Input Input Input Input Input Input Input Input Width 1 (each) 1 1 1 1 (each) 1 1 1 1 1 1 1 1 Description Registered outputs. See Registered Outputs - Q1 to Q6. Carry out for data width expansion. Connect to SHIFTIN1 of slave IOB. See ISERDES Width Expansion. Carry out for data width expansion. Connect to SHIFTIN2 of slave IOB. See ISERDES Width Expansion. Invokes the Bitslip operation. See Bitslip Operation - BITSLIP. Clock enable inputs. See Clock Enable Inputs - CE1 and CE2. High-speed clock input. Clocks serial input data stream. See High-Speed Clock Input - CLK. High-speed secondary clock input. Clocks serial input data stream. Always connect this CLK. Divided clock input. Clocks delay element, deserialized data, Bitslip submodule, and CE unit. See Divided Clock Input - CLKDIV. Serial input data from IOB. See Serial Input Data from IOB - D. High-speed clock input for memory applications. See High-Speed Clock for Strobe-Based Memory Interfaces - OCLK. Carry input for data width expansion. Connect to SHIFTOUT1 of master IOB. See ISERDES Width Expansion. Carry input for data width expansion. Connect to SHIFTOUT2 of master IOB. See ISERDES Width Expansion. Active High reset. See Reset Input - RST.

Port Name Q1 Q6 SHIFTOUT1 SHIFTOUT2 BITSLIP CE1 CE2 CLK CLKB CLKDIV D OCLK SHIFTIN1 SHIFTIN2 RST

ISERDES_NODELAY Ports
Registered Outputs - Q1 to Q6
The output ports Q1 to Q6 are the registered outputs of the ISERDES_NODELAY module. One ISERDES_NODELAY block can support up to six bits (i.e., a 1:6 deserialization). Bit widths greater than six (up to 10) can be supported. See ISERDES Width Expansion. The first data bit received appears on the highest order Q output. The bit ordering at the input of an OSERDES is the opposite of the bit ordering at the output of an ISERDES_NODELAY block, as shown in Figure 8-3. For example, the least significant bit A of the word FEDCBA is placed at the D1 input of an OSERDES, but the same bit A emerges from the ISERDES_NODELAY block at the Q6 output. In other words, D1 is the least significant input to the OSERDES, while Q6 is the least significant output of the ISERDES_NODELAY block. When width expansion is used, D1 of the master OSERDES is the least significant input, while Q4 of the slave ISERDES_NODELAY block is the least significant output.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

355

Chapter 8: Advanced SelectIO Logic Resources

X-Ref Target - Figure 8-3

OSERDES Data Bits A B C D E F D1 D2 D3 D4 D5 D6 Q F E D C B A

ISERDES D Q1 Q2 Q3 Q4 Q5 Q6 F E D C B A

CLKDIV_TX

CLK_TX

CLK_RX

CLKDIV_RX
UG190_8_03_100307

Figure 8-3:

Bit Ordering on Q1Q6 Outputs of ISERDES_NODELAY Ports

Bitslip Operation - BITSLIP

The BITSLIP pin performs a Bitslip operation synchronous to CLKDIV when asserted (active High). Subsequently, the data seen on the Q1 to Q6 output ports will shift, as in a barrel-shifter operation, one position every time Bitslip is invoked (DDR operation is different from SDR). See BITSLIP Submodule for more details.

Clock Enable Inputs - CE1 and CE2

Each ISERDES_NODELAY block contains an input clock enable module (Figure 8-4).
X-Ref Target - Figure 8-4

ICE CE1 RST CLKDIV NUM_CE 1 CE2 RST CLKDIV D AR Q CE2R 2 2 CLKDIV X 0 1 ICE CE1 CE2R CE1R
UG190_8_04_110707

D AR

(To ISERDES Input Registers) CE1R

Figure 8-4:

Input Clock Enable Module

When NUM_CE = 1, the CE2 input is not used, and the CE1 input is an active High clock enable connected directly to the input registers in the ISERDES_NODELAY. When NUM_CE = 2, the CE1 and CE2 inputs are both used, with CE1 enabling the ISERDES_NODELAY for of a CLKDIV cycle, and CE2 enabling the ISERDES_NODELAY for the other . The internal clock enable signal ICE shown in Figure 8-4 is derived from the CE1 and CE2 inputs. ICE drives the clock enable inputs of

356

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input Serial-to-Parallel Logic Resources (ISERDES)

registers FF0, FF1, FF2, and FF3 shown in Figure 8-12, page 368. The remaining registers in Figure 8-13, page 369 do not have clock enable inputs. The clock enable module functions as a 2:1 serial-to-parallel converter, clocked by CLKDIV. The clock enable module is needed specifically for bidirectional memory interfaces when ISERDES_NODELAY is configured for 1:4 deserialization in DDR mode. When the attribute NUM_CE = 2, the clock enable module is enabled and both CE1 and CE2 ports are available. When NUM_CE = 1, only CE1 is available and functions as a regular clock enable.

High-Speed Clock Input - CLK

The high-speed clock input (CLK) is used to clock in the input serial data stream.

High-Speed Clock Input - CLKB

The high-speed secondary clock input (CLKB) is used to clock in the input serial data stream. CLKB should be connected to CLK in both SDR and DDR mode.

Divided Clock Input - CLKDIV

The divided clock input (CLKDIV) is typically a divided version of CLK (depending on the width of the implemented deserialization). It drives the output of the serial-to-parallel converter, the Bitslip submodule, and the CE module.

Serial Input Data from IOB - D

The serial input data port (D) is the serial (high-speed) data input port of the ISERDES_NODELAY. This port works in conjunction with all the Virtex-5 FPGA I/O resources to accommodate the desired I/O standards.

High-Speed Clock for Strobe-Based Memory Interfaces - OCLK

The OCLK clock input synchronizes data transfer in strobe-based memory interfaces. The OCLK of the ISERDES_NODELAY shares the same routing as the CLK port of the OSERDES. The OCLK clock input is used to transfer strobe-based memory data onto a free-running clock domain. OCLK is a free-running FPGA clock at the same frequency as the strobe on the CLK input. The domain transfer from CLK to OCLK is shown in the Figure 8-5 block diagram. The timing of the domain transfer is set by the user by adjusting the delay of the strobe signal to the CLK input (e.g., using IDELAY). Examples of setting the timing of this domain transfer are given in several memory-related application notes, including XAPP858: High-Performance DDR2 SDRAM Interface in Virtex-5 Devices. When INTERFACE_TYPE is NETWORKING, this port is unused.

Reset Input - RST

The reset input causes the outputs of all data flip-flops in the CLK and CLKDIV domains to be driven Low asynchronously. ISERDES_NODELAY circuits running in the CLK domain where timing is critical use an internal, dedicated circuit to retime the RST input to produce a reset signal synchronous to the CLK domain. Similarly, there is a dedicated circuit to retime the RST input to produce a reset signal synchronous to the CLKDIV domain. Because there are ISERDES_NODELAY circuits that retime the RST input, the user is only required to provide a reset pulse to the RST input that meets timing on the CLKDIV

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

357

Chapter 8: Advanced SelectIO Logic Resources

frequency domain. Therefore, RST should be driven High for a minimum of one CLKDIV cycle. When building an interface consisting of multiple ISERDES_NODELAY ports, all ISERDES_NODELAY ports in the interface must be synchronized. The internal retiming of the RST input is designed so that all ISERDES_NODELAY blocks that receive the same reset pulse come out of reset synchronized with one another. The reset timing of multiple ISERDES_NODELAY ports is shown in Figure 8-9, page 365.

ISERDES_NODELAY Attributes
Table 8-2 summarizes all the applicable ISERDES_NODELAY attributes. A detailed description of each attribute follows the table. For more information on applying these attributes in UCF, VHDL, or Verilog code, refer to the Xilinx ISE Software Manual. Table 8-2: ISERDES_NODELAY Attributes
Description Value Default Value FALSE DDR

Attribute Name BITSLIP_ENABLE DATA_RATE

Allows the user to use the Bitslip submodule Boolean: TRUE or FALSE or bypass it. See BITSLIP_ENABLE Attribute. Enables incoming data stream to be processed as SDR or DDR data. See DATA_RATE Attribute. Defines the width of the serial-to-parallel converter. The legal value depends on the DATA_RATE attribute (SDR or DDR). See DATA_WIDTH Attribute. Chooses the ISERDES_NODELAY use model. See INTERFACE_TYPE Attribute. Defines the number of clock enables. See NUM_CE Attribute. Defines whether the ISERDES_NODELAY module is a master or slave when using width expansion. See SERDES_MODE Attribute. String: SDR or DDR

DATA_WIDTH

Integer: 2, 3, 4, 5, 6, 7, 8, or 10. If DATA_RATE = DDR, value is limited to 4, 6, 8, or 10. If DATA_RATE = SDR, value is limited to 2, 3, 4, 5, 6, 7, or 8. String: MEMORY or NETWORKING Integer: 1 or 2 String: MASTER or SLAVE

INTERFACE_TYPE NUM_CE SERDES_MODE

MEMORY 2 MASTER

BITSLIP_ENABLE Attribute
The BITSLIP_ENABLE attribute enables the Bitslip submodule. The possible values are TRUE and FALSE (default). BITSLIP_ENABLE must be set to TRUE when INTERFACE_TYPE is NETWORKING and FALSE when INTERFACE_TYPE is MEMORY. When set to TRUE, the Bitslip submodule responds to the BITSLIP signal. When set to FALSE, the Bitslip submodule is bypassed. See BITSLIP Submodule.

DATA_RATE Attribute
The DATA_RATE attribute defines whether the incoming data stream is processed as single data rate (SDR) or double data rate (DDR). The allowed values for this attribute are SDR and DDR. The default value is DDR.

358

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input Serial-to-Parallel Logic Resources (ISERDES)

DATA_WIDTH Attribute
The DATA_WIDTH attribute defines the parallel data output width of the serial-to-parallel converter. The possible values for this attribute depend on the INTERFACE_TYPE and DATA_RATE attributes. See Table 8-3 for recommended data widths. Table 8-3: Recommended Data Widths
DATA_RATE SDR DDR SDR DDR Recommended Data Widths 2, 3, 4, 5, 6, 7, 8 4, 6, 8, 10 None 4

INTERFACE_TYPE NETWORKING

MEMORY

When the DATA_WIDTH is set to widths larger than six, a pair of ISERDES_NODELAY must be configured into a master-slave configuration. See ISERDES Width Expansion. Width expansion is not allowed in memory mode.

INTERFACE_TYPE Attribute
The INTERFACE_TYPE attribute determines whether the ISERDES_NODELAY is configured in memory or networking mode. The allowed values for this attribute are MEMORY or NETWORKING. The default mode is MEMORY. When INTERFACE_TYPE is set to NETWORKING, the Bitslip submodule is available and the OCLK port is unused. BITSLIP_ENABLE must be set to TRUE, and the Bitslip port tied Low to disable Bitslip operation when the Bitslip module is not used in networking mode. When set to MEMORY, the Bitslip submodule is not available (BITSLIP_ENABLE must be set to FALSE), and the OCLK port can be used. Figure 8-5 illustrates the ISERDES_NODELAY internal connections when in Memory mode.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

359

Chapter 8: Advanced SelectIO Logic Resources

X-Ref Target - Figure 8-5

Q1

FF0
ICE

FF2
ICE

FF6

Q2

FF1
ICE

FF3
ICE

FF7

CLK

Q3

FF4

FF8

Q4

FF5
OCLK CLKDIV

FF9

ug190_8_05_100307

Figure 8-5:

Internal Connections of ISERDES_NODELAY When in Memory Mode

NUM_CE Attribute
The NUM_CE attribute defines the number of clock enables (CE1 and CE2) used. The possible values are 1 and 2 (default = 2).

SERDES_MODE Attribute
The SERDES_MODE attribute defines whether the ISERDES_NODELAY module is a master or slave when using width expansion. The possible values are MASTER and SLAVE. The default value is MASTER. See ISERDES Width Expansion.

ISERDES_NODELAY Clocking Methods

Networking Interface Type
The phase relationship of CLK and CLKDIV is important in the serial-to-parallel conversion process. CLK and CLKDIV are (ideally) phase-aligned within a tolerance. There are several clocking arrangements within the FPGA to help the design meet the phase relationship requirements of CLK and CLKDIV. The only valid clocking arrangements for the ISERDES_NODELAY block using the networking interface type are: CLK driven by BUFIO, CLKDIV driven by BUFR CLK driven by DCM, CLKDIV driven by the CLKDV output of the same DCM CLK driven by PLL, CLKDIV driven by CLKOUT[0:5] of same PLL

360

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input Serial-to-Parallel Logic Resources (ISERDES)

Memory Interface Type

The only valid clocking arrangements for the ISERDES_NODELAY block using the memory interface type are: CLK driven by BUFIO or BUFG OCLK driven by DCM and CLKDIV driven by CLKDV output of same DCM OCLK driven by PLL and CLKDIV driven by CLKOUT[0:5] of same PLL

The clocking arrangement using BUFIO and BUFR is shown in Figure 8-6. The CLK and CLKDIV inputs must be nominally phase-aligned. For example, if CLK and CLKDIV in Figure 8-6 were inverted by the designer at the ISERDES inputs, then although the clocking arrangement is a legal BUFIO/BUFR configuration, the clocks would still be out of phase. No phase relationship between CLK and OCLK is expected. Calibration must be performed for reliable data transfer from CLK to OCLK domain. High-Speed Clock for Strobe-Based Memory Interfaces - OCLK gives further information about transferring data between CLK and OCLK.
X-Ref Target - Figure 8-6

BUFIO Clock Input BUFR (X)

ISERDES_NODELAY
CLK

CLKDIV
UG190_8_06_110807

Figure 8-6:

Clocking Arrangement Using BUFIO and BUFR

ISERDES Width Expansion

Two ISERDES modules are used to build a serial-to-parallel converter larger than 1:6. In every I/O tile there are two ISERDES modules; one master and one slave. By connecting the SHIFTOUT ports of the master ISERDES to the SHIFTIN ports of the slave ISERDES the serial-to-parallel converter can be expanded to up to 1:10 (DDR) and 1:8 (SDR). Figure 8-7 illustrates a block diagram of a 1:10 DDR serial-to-parallel converter using the master and slave ISERDES modules. Ports Q3 - Q6 are used for the last four bits of the parallel interface on the slave ISERDES. For a differential input, the master ISERDES must be on the positive side of the differential input pair. When the input is not differential, the input buffer associated with the slave ISERDES is not available and can not be used.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

361

Chapter 8: Advanced SelectIO Logic Resources

X-Ref Target - Figure 8-7

SERDES_MODE=MASTER

Data Input

Q1 Q2 ISERDES Q3 Q4 (Master) Q5 Q6 SHIFTOUT1 SHIFTOUT2 SHIFTIN1 SHIFTIN2

Data_internal [0:5]

ISERDES (Slave)

Q1 Q2 Q3 Q4 Q5 Q6

Data_internal [6:9]

SERDES_MODE=SLAVE
ug190_8_07_100307

Figure 8-7:

Block Diagram of ISERDES Width Expansion

Guidelines for Expanding the Serial-to-Parallel Converter Bit Width

1. Both ISERDES modules must be adjacent master and slave pairs. Both ISERDES modules must be in NETWORKING mode because width expansion is not available in MEMORY mode. Set the SERDES_MODE attribute for the master ISERDES to MASTER and the slave ISERDES to SLAVE. See SERDES_MODE Attribute. The user must connect the SHIFTIN ports of the SLAVE to the SHIFTOUT ports of the MASTER. The SLAVE only uses the ports Q3 to Q6 as an input. DATA_WIDTH applies to both MASTER and SLAVE in Figure 8-7.

2. 3. 4. 5.

362

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input Serial-to-Parallel Logic Resources (ISERDES)

ISERDES Latencies
When the ISERDES interface type is MEMORY, the latency through the OCLK stage is one CLKDIV cycle. However, the total latency through the ISERDES depends on the phase relationship between the CLK and the OCLK clock inputs. When the ISERDES interface type is NETWORKING, the latency is two CLKDIV cycles. See Figure 8-12, page 368 and Figure 8-13, page 369 for a visualization of latency in networking mode. The extra CLKDIV cycle of latency in networking mode (compared to memory mode) is due to the Bitslip submodule.

ISERDES Timing Model and Parameters

Table 8-4 describes the function and control signals of the ISERDES switching characteristics in the Virtex-5 FPGA Data Sheet. Table 8-4: ISERDES Switching Characteristics
Symbol Setup/Hold for Control Lines TISCCK_BITSLIP/ TISCKC_BITSLIP TISCCK_CE /TISCKC_CE TISCCK_CE /TISCKC_CE Setup/Hold for Data Lines TISDCK_D / TISCKD_D D pin Setup/Hold with respect to CLK D pin Setup/Hold with respect to CLK D pin Setup/Hold with respect to CLK TISDCK_DDR / TISCKD_DDR D pin Setup/Hold with respect to CLK at DDR mode D pin Setup/Hold with respect to CLK at DDR mode D pin Setup/Hold with respect to CLK at DDR mode Sequential Delay TISCKO_Q CLKDIV to Out at Q pins BITSLIP pin Setup/Hold with respect to CLKDIV CE pin Setup/Hold with respect to CLK (for CE1) CE pin Setup/Hold with respect to CLKDIV (for CE2) Description

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

363

Chapter 8: Advanced SelectIO Logic Resources

Timing Characteristics
Figure 8-8 illustrates an ISERDES timing diagram for the input data to the ISERDES. The timing parameter names change for different modes (SDR/DDR). However, the names do not change when a different bus input width, including when two ISERDES are cascaded together to form 10 bits. In DDR mode, the data input (D) switches at every CLK edge (rising and falling).
X-Ref Target - Figure 8-8

1 CLK

TISCCK_CE CE TISDCK_D D
ug190_8_08_100307

Figure 8-8:

ISERDES Input Data Timing Diagram

Clock Event 1
At time TISCCK_CE, before Clock Event 1, the clock enable signal becomes valid-High and the ISERDES can sample data.

Clock Event 2
At time TISDCK_D, before Clock Event 2, the input data pin (D) becomes valid and is sampled at the next positive clock edge.

Reset Input Timing

Clock Event 1
As shown in Figure 8-9, the reset pulse is generated on the rising edge of CLKDIV. Because the pulse must take two different routes to get to ISERDES0 and ISERDES1, there are different propagation delays for both paths. The difference in propagation delay is emphasized. The path to ISERDES0 is very long and the path to ISERDES1 is very short, such that each ISERDES receives the reset pulse in a different CLK cycle. The internal resets for both CLK and CLKDIV are reset asynchronously when the RST input is asserted.

364

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input Serial-to-Parallel Logic Resources (ISERDES)

X-Ref Target - Figure 8-9

Clock Event 1 CLKDIV CLK ISERDES0 ISERDES1 ISERDES0 ISERDES1 ISERDES0 ISERDES1

Clock Event 2

Clock Clock Event 3 Event 4

Signal at RST Input

Internal Reset (CLKDIV)

Internal Reset (CLK)

UG190_8_09_110707

Figure 8-9:

Two ISERDES Coming Out of Reset Synchronously with One Another

Clock Event 2
The reset pulse is deasserted on the rising edge of CLKDIV. The difference in propagation delay between the two ISERDES causes the RST input to come out of reset on two different CLK cycles. Without internal retiming, ISERDES1 finishes reset one CLK cycle before ISERDES0 and both ISERDES are asynchronous.

Clock Event 3
The release of the reset signal at the RST input is retimed internally to CLKDIV. This synchronizes ISERDES0 and ISERDES1.

Clock Event 4
The release of the reset signal at the RST input is retimed internally to CLK.

ISERDES VHDL and Verilog Instantiation Template

VHDL and Verilog instantiation templates are available in the Libraries Guide for all primitives and submodules. In VHDL, each template has a component declaration section and an architecture section. Each part of the template should be inserted within the VHDL design file. The port map of the architecture section should include the design signal names.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

365

Chapter 8: Advanced SelectIO Logic Resources

BITSLIP Submodule
All ISERDES blocks in Virtex-5 devices contain a Bitslip submodule. This submodule is used for word-alignment purposes in source-synchronous networking-type applications. Bitslip reorders the parallel data in the ISERDES block, allowing every combination of a repeating serial pattern received by the deserializer to be presented to the FPGA fabric. This repeating serial pattern is typically called a training pattern (training patterns are supported by many networking and telecom standards).

Bitslip Operation
By asserting the Bitslip pin of the ISERDES block, the incoming serial data stream is reordered at the parallel side. This operation is repeated until the training pattern is seen. The tables in Figure 8-10 illustrate the effects of a Bitslip operation in SDR and DDR mode. For illustrative purposes the data width is eight. The Bitslip operation is synchronous to CLKDIV. In SDR mode, every Bitslip operation causes the output pattern to shift left by one. In DDR mode, every Bitslip operation causes the output pattern to alternate between a shift right by one and shift left by three. In this example, on the eighth Bitslip operation, the output pattern reverts to the initial pattern. This assumes that serial data is an eight bit repeating pattern.
X-Ref Target - Figure 8-10

Bitslip Operation in SDR Mode Bitslip Operations Executed Initial 1 2 3 4 5 6 7 Output Pattern (8:1) 10010011 00100111 01001110 10011100 00111001 01110010 11100100 11001001

Bitslip Operation in DDR Mode Bitslip Operations Executed Initial 1 2 3 4 5 6 7 Output Pattern (8:1) 00100111 10010011 10011100 01001110 01110010 00111001 11001001 11100100
ug190_8_10_100307

Figure 8-10:

Bitslip Operation Examples

366

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input Serial-to-Parallel Logic Resources (ISERDES)

Figure 8-11 illustrates the ISERDES configured in 1:8 SDR mode with Bitslip_ENABLE set to TRUE. Two ISERDES modules are in a master-slave configuration for a data width of eight.
X-Ref Target - Figure 8-11

IOB
SERDES_MODE=MASTER BITSLIP_ENABLE = TRUE 1001 0011
(Repeating Pattern)

1st 2nd 3th 4th 5th 6th 7th 8th Bitslip Initial Bitslip Bitslip Bitslip Bitslip Bitslip Bitslip Bitslip (Back to initial)
1 0 0 1 0 0 1 1 0 0 1 0 1 1 1 0 0 1 0 1 1 1 0 0 0 0 1 1 1 0 1 0 0 1 1 1 0 1 0 0 1 1 0 0 1 0 0 1 1 0 0 1 0 0

ISERDES (Master)

Q1 Q2 Q3 Q4 Q5 Q6 BITSLIP

SHIFTOUT1 SHIFTOUT2

SHIFTIN1

SHIFTIN2

ISERDES (Slave)

Q1 Q2 (Q7)Q3 (Q8)Q4 Q5 Q6 BITSLIP

1 1

0 1

0 0

1 0

0 1

0 0

1 0

1 1

1 1

Bitslip signal from system

SERDES_MODE=SLAVE BITSLIP_ENABLE = TRUE

ug190_8_11_100307

Figure 8-11:

Circuit Diagram for Bitslip Configuration in 1:8 SDR Mode

Guidelines for Using the Bitslip Submodule

Set the BITSLIP_ENABLE attribute to TRUE. When BITSLIP_ENABLE is set to FALSE, the Bitslip pin has no effect. In a master-slave configuration, the BITSLIP_ENABLE attribute in both modules must be set to TRUE. To invoke a Bitslip operation, the BITSLIP port must be asserted High for one CLKDIV cycle. In SDR mode, Bitslip cannot be asserted for two consecutive CLKDIV cycles; Bitslip must be deasserted for at least one CLKDIV cycle between two Bitslip assertions. In both SDR and DDR mode, the total latency from when the ISERDES captures the asserted Bitslip input to when the bit-slipped ISERDES outputs Q1Q6 are sampled into the FPGA logic by CLKDIV is two CLKDIV cycles.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

367

Chapter 8: Advanced SelectIO Logic Resources

Bitslip Timing Model and Parameters

This section discusses the timing models associated with the Bitslip controller in a 1:4 DDR configuration. Data (D) is a repeating, 4-bit training pattern ABCD. ABCD could appear at the parallel outputs Q1Q4 of the ISERDES in four possible ways: ABCD, BCDA, CDAB, and DABC. Only one of these four alignments of the parallel word makes sense to the user's downstream logic that reads the data from the Q1Q4 outputs of the ISERDES. In this case, ABCD is assumed to be the word alignment that makes sense. Asserting Bitslip allows the user to see all possible configurations of ABCD and then choose the expected alignment (ABCD). Figure 8-12 shows the timing of two Bitslip operations and the corresponding re-alignments of the ISERDES parallel outputs Q1Q4.
X-Ref Target - Figure 8-12

1 D

C D A B C D A B C D A B C D

CLK

BITSLIP

Bitslip1

Bitslip2

CLKDIV

Q4Q1

CDAB

BCDA

ABCD
ug190_8_12_100307

Figure 8-12:

Bitslip Timing Diagram

Clock Event 1
The entire first word CDAB has been sampled into the input side registers of the ISERDES. The Bitslip pin is not asserted; the word propagates through the ISERDES without any realignment.

Clock Event 2
The second word CDAB has been sampled into the input side registers of the ISERDES. The Bitslip pin is asserted, which causes the Bitslip controller to shift all bits internally by one bit to the right.

Clock Event 3
The third word CDAB has been sampled into the input side registers of the ISERDES. The Bitslip pin is asserted for a second time, which causes the Bitslip controller to shift all bits internally by three bits to the left. On this same edge of CLKDIV, the first word sampled is presented to Q1Q4 without any realignment. The actual bits from the input stream that appear at the Q1Q4 outputs during this cycle are shown in A of Figure 8-13.

368

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Input Serial-to-Parallel Logic Resources (ISERDES)

X-Ref Target - Figure 8-13

Q1Q4 During Clock Event 3 (No Bitslip)

C D A B C D A B C D A B C D

Q1Q4 During Clock Event 4 (1st Bitslip, Rotate 1 Bit to Right) Q1Q4 During Clock Event 5 (2nd Bitslip, Rotate 3 Bits to Left)

C D A B C D A B C D A B C D

C D A B C D A B C D A B C D
ug190_c8_13_100307

Figure 8-13:

Bits from Data Input Stream (D) of Figure 8-12

Clock Event 4
The first two bits of the fourth word CD have been sampled into the input side registers of the ISERDES. On this same edge of CLKDIV, the second word sampled is presented to Q1Q4 with one bit shifted to the right. The actual bits from the input stream that appear at the Q1Q4 outputs during this cycle are shown in B of Figure 8-13. The realigned bits on Q1Q4 are sampled into the FPGA logic on the CLKDIV domain. The total latency from when the ISERDES captures the asserted Bitslip input to when the realigned ISERDES outputs Q1Q4 are sampled by CLKDIV is two CLKDIV cycles.

Clock Event 5
The third word sampled is presented to Q1Q4 with three bits shifted to the left. The actual bits from the input stream that appear at the Q1Q4 outputs during this cycle are shown in C of Figure 8-13.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

369

Chapter 8: Advanced SelectIO Logic Resources

Output Parallel-to-Serial Logic Resources (OSERDES)

The OSERDES in Virtex-5 devices is a dedicated parallel-to-serial converter with specific clocking and logic resources designed to facilitate the implementation of high-speed source-synchronous interfaces. Every OSERDES module includes a dedicated serializer for data and 3-state control. Both Data and 3-state serializers can be configured in SDR and DDR mode. Data serialization can be up to 6:1 (10:1 if using OSERDES Width Expansion). 3-state serialization can be up to 4:1. Figure 8-14 shows a block diagram of the OSERDES, highlighting all the major components and features of the block.
X-Ref Target - Figure 8-14

T1 - T4 TCE

3-State Parallel-to-Serial Converter

IOB
TQ

CLK CLKDIV SR D1 - D6 OCE

Data Parallel-to-Serial Converter

OQ
Output Driver

ug190_8_14_100307

Figure 8-14: OSERDES Block Diagram

Data Parallel-to-Serial Converter

The data parallel-to-serial converter in one OSERDES blocks receives two to six bits of parallel data from the fabric (10:1 if using OSERDES Width Expansion), serializes the data, and presents it to the IOB via the OQ outputs. Parallel data is serialized from lowest order data input pin to highest (i.e., data on the D1 input pin is the first bit transmitted at the OQ pins). The data parallel-to-serial converter is available in two modes: single-data rate (SDR) and double-data rate (DDR). The OSERDES uses two clocks, CLK and CLKDIV, for data rate conversion. CLK is the high-speed serial clock, CLKDIV is the divided parallel clock. It is assumed that CLK and CLKDIV are phase aligned. Prior to use, a reset must be applied to the OSERDES. The OSERDES contains an internal counter that controls dataflow. Failure to synchronize the reset with the CLKDIV will produce an unexpected output. Table 8-5 describes the relationship between CLK and CLKDIV in all modes.

370

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Output Parallel-to-Serial Logic Resources (OSERDES)

Table 8-5:

CLK/CLKDIV Relationship of the Data Parallel-to-Serial Converter

CLK 2X 3X 4X 5X 6X 7X 8X CLKDIV X X X X X X X

Input Data Width Output in SDR Input Data Width Output in DDR Mode Mode 2 3 4 5 6 7 8 4 6 8 10

3-State Parallel-to-Serial Conversion

In addition to parallel-to-serial conversion of data, an OSERDES module also contains a parallel-to-serial converter for 3-state control of the IOB. Unlike data conversion, the 3-state converter can only serialize up to four bits of parallel 3-state signals. The 3-state converter cannot be cascaded.

OSERDES Primitive
The OSERDES primitive is shown in Figure 8-15.
X-Ref Target - Figure 8-15

CLK CLKDIV D1 D2 D3 D4 D5 D6 OCE

OSERDES Primitive
OQ SHIFTOUT1 SHIFTOUT2

SHIFTIN1 SHIFTIN2 SR T1 T2

TQ T3 T4 TCE
ug190_8_15_100307

Figure 8-15:

OSERDES Primitive

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

371

Chapter 8: Advanced SelectIO Logic Resources

OSERDES Ports
Table 8-6 lists the available ports in the OSERDES primitive. Table 8-6: OSERDES Port List and Definitions
Type Output Output Output Output Input Input Input Input Input Input Input Input Input Input Width 1 1 1 1 1 1 1 (each) 1 1 1 1 1 1 (each) 1 Description Data path output. See Data Path Output - OQ. Carry out for data width expansion. Connect to SHIFTIN1 of master OSERDES. See OSERDES Width Expansion. Carry out for data width expansion. Connect to SHIFTIN2 of master OSERDES. See OSERDES Width Expansion. 3-state control output. See 3-state Control Output - TQ. High-speed clock input. See High-Speed Clock Input - CLK. Divided clock input. Clocks delay element, deserialized data, Bitslip submodule, and CE unit. See Divided Clock Input - CLKDIV. Parallel data inputs. See Parallel Data Inputs - D1 to D6. Output data clock enable. See Output Data Clock Enable - OCE. Reverse SR pin. Not available in the OSERDES block. Carry input for data width expansion. Connect to SHIFTOUT1 of slave OSERDES. See OSERDES Width Expansion. Carry input for data width expansion. Connect to SHIFTOUT2 of slave OSERDES. See OSERDES Width Expansion. Active High reset. Parallel 3-state inputs. See Parallel 3-state Inputs - T1 to T4. 3-state clock enable. See 3-state Signal Clock Enable - TCE.

Port Name OQ SHIFTOUT1 SHIFTOUT2 TQ CLK CLKDIV D1 D6 OCE REV SHIFTIN1 SHIFTIN2 SR T1 to T4 TCE

Data Path Output - OQ

The OQ port is the data output port of the OSERDES module. Data at the input port D1 will appear first at OQ. This port connects the output of the data parallel-to-serial converter to the data input of the IOB.

3-state Control Output - TQ

This port is the 3-state control output of the OSERDES module. When used, this port connects the output of the 3-state parallel-to-serial converter to the control/3-state input of the IOB.

High-Speed Clock Input - CLK

This high-speed clock input drives the serial side of the parallel-to-serial converters.

Divided Clock Input - CLKDIV

This divided high-speed clock input drives the parallel side of the parallel-to-serial converters. This clock is the divided version of the clock connected to the CLK port.

372

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Output Parallel-to-Serial Logic Resources (OSERDES)

Parallel Data Inputs - D1 to D6

All incoming parallel data enters the OSERDES module through ports D1 to D6. These ports are connected to the FPGA fabric, and can be configured from two to six bits (i.e., a 6:1 serialization). Bit widths greater than six (up to 10) can be supported by using a second OSERDES in SLAVE mode. See OSERDES Width Expansion. Refer to Figure 8-3, page 356 for bit ordering at the inputs and output of the OSERDES along with the corresponding bit order of the ISERDES_NODELAY.

Output Data Clock Enable - OCE

OCE is an active High clock enable for the data path.

Parallel 3-state Inputs - T1 to T4

All parallel 3-state signals enter the OSERDES module through ports T1 to T4. The ports are connected to the FPGA fabric, and can be configured as one, two, or four bits.

3-state Signal Clock Enable - TCE

TCE is an active High clock enable for the 3-state control path.

Reset Input - SR
The reset input causes the outputs of all data flip-flops in the CLK and CLKDIV domains to be driven Low asynchronously. OSERDES circuits running in the CLK domain where timing is critical use an internal, dedicated circuit to retime the SR input to produce a reset signal synchronous to the CLK domain. Similarly, there is a dedicated circuit to retime the SR input to produce a reset signal synchronous to the CLKDIV domain. Because there are OSERDES circuits that retime the SR input, the user is only required to provide a reset pulse to the SR input that meets timing on the CLKDIV frequency domain (synchronous to CLKDIV). Therefore, SR should be driven High for a minimum of one CLKDIV cycle. When building an interface consisting of multiple OSERDES ports, all OSERDES ports must be synchronized. The internal retiming of the SR input is designed so that all OSERDES blocks that receive the same reset pulse come out of reset synchronized with one another. The reset timing of multiple OSERDES ports is shown in Figure 8-20, page 381.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

373

Chapter 8: Advanced SelectIO Logic Resources

OSERDES Attributes
Table 8-7 lists and describes the various attributes that are available for the OSERDES primitive. The table includes the default values. Table 8-7: OSERDES Attribute Summary
Description Defines whether data (OQ) changes at every clock edge or every positive clock edge with respect to CLK. Defines whether the 3-state (TQ) changes at every clock edge, every positive clock edge with respect to clock, or is set to buffer configuration. Defines the parallel-to-serial data converter width. This value also depends on the DATA_RATE_OQ value. Value String: SDR or DDR Default Value DDR

OSERDES Attribute DATA_RATE_OQ

DATA_RATE_TQ

String: BUF, SDR, or DDR

DDR

DATA_WIDTH

Integer: 2, 3, 4, 5, 6, 7, 8, or 10. If DATA_RATE_OQ = DDR, value is limited to 4, 6, 8, or 10. If DATA_RATE_OQ = SDR, value is limited to 2, 3, 4, 5, 6, 7, or 8.

SERDES_MODE TRISTATE_WIDTH

Defines whether the OSERDES module is a String: MASTER or SLAVE master or slave when using width expansion. Defines the parallel to serial 3-state converter width. Integer: 1 or 4 If DATA_RATE_TQ = DDR, DATA_WIDTH = 4, and DATA_RATE_OQ = DDR, value is limited to 4. For all other settings of DATA_RATE_TQ, DATA_WIDTH, and DATA_RATE_OQ, value is limited to 1.

MASTER 4

DATA_RATE_OQ Attribute
The DATA_RATE_OQ attribute defines whether data is processed as single data rate (SDR) or double data rate (DDR). The allowed values for this attribute are SDR and DDR. The default value is DDR.

DATA_RATE_TQ Attribute
The DATA_RATE_TQ attribute defines whether 3-state control is to be processed as single data rate (SDR) or double data rate (DDR). The allowed values for this attribute are SDR and DDR. The default value is DDR.

374

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Output Parallel-to-Serial Logic Resources (OSERDES)

DATA_WIDTH Attribute
The DATA_WIDTH attribute defines the parallel data input width of the parallel-to-serial converter. The possible values for this attribute depend on the DATA_RATE_OQ attribute. When DATA_RATE_OQ is set to SDR, the possible values for the DATA_WIDTH attribute are 2, 3, 4, 5, 6, 7, and 8. When DATA_RATE_OQ is set to DDR, the possible values for the DATA_WIDTH attribute are 4, 6, 8, and 10. When the DATA_WIDTH is set to widths larger than six, a pair of OSERDES must be configured into a master-slave configuration. See OSERDES Width Expansion.

SERDES_MODE Attribute
The SERDES_MODE attribute defines whether the OSERDES module is a master or slave when using width expansion. The possible values are MASTER and SLAVE. The default value is MASTER. See OSERDES Width Expansion.

TRISTATE_WIDTH Attribute
The TRISTATE_WIDTH attribute defines the parallel 3-state input width of the 3-state control parallel-to-serial converter. The possible values for this attribute depend on the DATA_RATE_TQ attribute. When DATA_RATE_TQ is set to SDR or BUF, the TRISTATE_WIDTH attribute can only be set to 1. When DATA_RATE_TQ is set to DDR, the possible values for the TRISTATE_WIDTH attribute is 4. TRISTATE_WIDTH cannot be set to widths larger than 4. When a DATA_WIDTH is larger than four, set the TRISTATE_WIDTH to 1.

OSERDES Clocking Methods

The phase relationship of CLK and CLKDIV is important in the parallel-to-serial conversion process. CLK and CLKDIV are (ideally) phase-aligned within a tolerance. There are several clocking arrangements within the FPGA to help the design meet the phase relationship requirements of CLK and CLKDIV. The only valid clocking arrangements for the OSERDES are: CLK driven by BUFIO, CLKDIV driven by BUFR CLK driven by DCM, CLKDIV driven by the CLKDV output of the same DCM CLK driven by PLL, CLKDIV driven by CLKOUT[0:5] of same PLL

OSERDES Width Expansion

Two OSERDES modules are used to build a parallel-to-serial converter larger than 6:1. In every I/O tile there are two OSERDES modules; one master and one slave. By connecting the SHIFTIN ports of the master OSERDES to the SHIFTOUT ports of the slave OSERDES, the parallel-to-serial converter can be expanded to up to 10:1(DDR) and 8:1 (SDR). For a differential output, the master OSERDES must be on the positive side of the differential output pair. When the output is not differential, the output buffer associated with the slave OSERDES is not available and can not be used. When using the OSERDES with width expansion, complementary single-ended standards (e.g., DIFF_HSTL and DIFF_SSTL) cannot be used. This is because both OLOGIC blocks in an I/O tile are used by the complementary single-ended standards to transmit both legs of the signal, leaving no OLOGIC blocks available for width expansion.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

375

Chapter 8: Advanced SelectIO Logic Resources

Figure 8-16 illustrates a block diagram of a 10:1 DDR parallel-to-serial converter using the master and slave OSERDES modules. Ports Q3-Q6 are used for the last four bits of the parallel interface on the slave OSERDES (LSB to MSB).
X-Ref Target - Figure 8-16

SERDES_MODE = MASTER
D1 D2 D3 D4 D5 D6 OQ

Data Out

Data Inputs[0:5]

OSERDES (Master)
SHIFTIN1 SHIFTIN2

Data Inputs[6:9]

SHIFTOUT1 SHIFTOUT2 OQ D1 D2 D3 OSERDES D4 (Slave) D5 D6

SERDES_MODE=SLAVE
ug190_8_16_100307

Figure 8-16:

Block Diagram of OSERDES Width Expansion

Table 8-8 lists the data width availability for SDR and DDR mode. Table 8-8: OSERDES SDR/DDR Data Width Availability
2, 3, 4, 5, 6, 7, 8 4, 6, 8, 10

SDR Data Widths DDR Data Widths

Guidelines for Expanding the Parallel-to-Serial Converter Bit Width

1. 2. 3. 4. 5. Both the OSERDES modules must be adjacent master and slave pairs. Set the SERDES_MODE attribute for the master OSERDES to MASTER and the slave OSERDES to SLAVE. See SERDES_MODE Attribute. The user must connect the SHIFTIN ports of the MASTER to the SHIFTOUT ports of the SLAVE. The SLAVE only uses the ports D3 to D6 as an input. DATA_WIDTH for Master and Slave are equal. See DATA_WIDTH Attribute.

The slave inputs used for data widths requiring width expansion are listed in Table 8-9. Table 8-9: Slave Inputs Used for Data Width Expansion
Slave Inputs Used D3 D3D4 D3D6

Data Width 7 8 10

376

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Output Parallel-to-Serial Logic Resources (OSERDES)

OSERDES Latencies
The input to output latencies of OSERDES blocks depend on the DATA_RATE and DATA_WIDTH attributes. Latency is defined as a period of time between the following two events: (a) when the rising edge of CLKDIV clocks the data at inputs D1D6 into the OSERDES, and (b) when the first bit of the serial stream appears at OQ. Table 8-10 summarizes the various OSERDES latency values. Table 8-10: OSERDES Latencies
DATA_WIDTH 2:1 3:1 4:1 SDR 5:1 6:1 7:1 8:1 4:1 DDR 6:1 8:1 10:1 1 CLK cycle 3 CLK cycles 4 CLK cycles 4 CLK cycles 5 CLK cycles 5 CLK cycles 6 CLK cycles 1 CLK cycle 3 CLK cycles 4 CLK cycles 4 CLK cycles Latency

DATA_RATE

OSERDES Timing Model and Parameters

This section discusses all timing models associated with the OSERDES primitive. Table 8-11 describes the function and control signals of the OSERDES switching characteristics in the Virtex-5 FPGA Data Sheet. Table 8-11: OSERDES Switching Characteristics
Description

Symbol Setup/Hold TOSDCK_D/TOSCKD_D TOSDCK_T/TOSCKD_T TOSDCK_T/TOSCKD_T TOSCCK_OCE/TOSCKC_OCE TOSCCK_TCE/TOSCKC_TCE Sequential Delays TOSCKO_OQ TOSCKO_TQ

D input Setup/Hold with respect to CLKDIV T input Setup/Hold with respect to CLK T input Setup/Hold with respect to CLKDIV OCE input Setup/Hold with respect to CLK TCE input Setup/Hold with respect to CLK

Clock to Out from CLK to OQ Clock to Out from CLK to TQ

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

377

Chapter 8: Advanced SelectIO Logic Resources

Table 8-11:

OSERDES Switching Characteristics (Continued)

Description

Symbol Combinatorial TOSCO_OQ TOSCO_TQ

Asynchronous Reset to OQ Asynchronous Reset to TQ

Timing Characteristics of 2:1 SDR Serialization

In Figure 8-17, the timing of a 2:1 SDR data serialization is illustrated.
X-Ref Target - Figure 8-17

Clock Event 1 CLKDIV CLK D1 D2 OQ

Clock Event 2

Clock Event 3

A B A

C D B C

E F D E F
UG190_8_17_100307

Figure 8-17:

OSERDES Data Flow and Latency in 2:1 SDR Mode

Clock Event 1
On the rising edge of CLKDIV, the word AB is driven from the FPGA logic to the D1 and D2 inputs of the OSERDES (after some propagation delay).

Clock Event 2
On the rising edge of CLKDIV, the word AB is sampled into the OSERDES from the D1 and D2 inputs.

Clock Event 3
The data bit A appears at OQ one CLK cycle after AB is sampled into the OSERDES. This latency is consistent with the Table 8-10 listing of a 2:1 SDR mode OSERDES latency of one CLK cycle.

378

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Output Parallel-to-Serial Logic Resources (OSERDES)

Timing Characteristics of 8:1 DDR Serialization

Figure 8-18 illustrates the timing of an 8:1 DDR data serialization. In contrast to the 2:1 SDR example, a second OSERDES is required to achieve an 8:1 serialization. The two OSERDES are connected and configured using the methods described in OSERDES Width Expansion, page 375. Six of the eight bits are connected to D1D6 of the master OSERDES while the remaining two bits are connected to D3D4 of the slave OSERDES.
X-Ref Target - Figure 8-18

Clock Event 1 Master.D1 Master.D2 Master.D3 Master.D4 Master.D5 Master.D6 Slave.D3 Slave.D4 CLKDIV CLK OQ A B

Clock Event 2 I J

Clock Event 3

Clock Event 4

C D E F G H

K L M N O P

A B C D E F G H I
UG190_8_18_100307

Figure 8-18:

OSERDES Data Flow and Latency in 8:1 DDR Mode

Clock Event 1
On the rising edge of CLKDIV, the word ABCDEFGH is driven from the FPGA logic to the D1D6 inputs of the master OSERDES and D3D4 of the slave OSERDES (after some propagation delay).

Clock Event 2
On the rising edge of CLKDIV, the word ABCDEFGH is sampled into the master and slave OSERDES from the D1D6 and D3D4 inputs, respectively.

Clock Event 3
The data bit A appears at OQ four CLK cycles after ABCDEFGH is sampled into the OSERDES. This latency is consistent with the Table 8-10 listing of a 8:1 DDR mode OSERDES latency of four CLK cycles.

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

379

Chapter 8: Advanced SelectIO Logic Resources

The second word IJKLMNOP is sampled into the master and slave OSERDES from the D1 D6 and D3D4 inputs, respectively.

Clock Event 4
Between Clock Events 3 and 4, the entire word ABCDEFGH is transmitted serially on OQ, a total of eight bits transmitted in one CLKDIV cycle. The data bit I appears at OQ four CLK cycles after IJKLMNOP is sampled into the OSERDES. This latency is consistent with the Table 8-10 listing of a 8:1 DDR mode OSERDES latency of four CLK cycles.

Timing Characteristics of 4:1 DDR 3-State Controller Serialization

The operation of a 3-State Controller is illustrated in Figure 8-19. The example is a 4:1 DDR case shown in a bidirectional system where the IOB must be frequently 3-stated.
X-Ref Target - Figure 8-19

Clock Event 1 D1 D2 D3 D4 CLKDIV CLK T1 T2 T3 T4 OQ TQ OBUFT.O 1 1 1 1 0 0 1 0 A B C D E F G H

Clock Event 2 I J K L

1 1 1 1

A B C D E F G H I J K L

E F

H
UG190_8_19_100307

Figure 8-19:

OSERDES Data Flow and Latency in 4:1 DDR Mode

380

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Output Parallel-to-Serial Logic Resources (OSERDES)

Clock Event 1
T1, T2, and T4 are driven Low to release the 3-state condition. The serialization paths of T1T4 and D1D4 in the OSERDES are identical (including latency), such that the bits EFGH are always aligned with the 0010 presented at the T1T4 pins during Clock Event 1.

Clock Event 2
The data bit E appears at OQ one CLK cycle after EFGH is sampled into the OSERDES. This latency is consistent with the Table 8-10 listing of a 4:1 DDR mode OSERDES latency of one CLK cycle. The 3-state bit 0 at T1 during Clock Event 1 appears at TQ one CLK cycle after 0010 is sampled into the OSERDES 3-state block. This latency is consistent with the Table 8-10 listing of a 4:1 DDR mode OSERDES latency of one CLK cycle.

Reset Output Timing

Clock Event 1
A reset pulse is generated on the rising edge of CLKDIV. Because the pulse must take two different routes to get to OSERDES0 and OSERDES1, there are different propagation delays for both paths. The difference in propagation delay is emphasized in Figure 8-20. The path to OSERDES0 is very long and the path to OSERDES1 is very short, such that each OSERDES receives the reset pulse in a different CLK cycle. The internal resets for both CLK and CLKDIV go into reset asynchronously when the SR input is asserted.
X-Ref Target - Figure 8-20

Clock Event 1 CLKDIV CLK OSERDES0 Signal at SR Input OSERDES1 OSERDES0 OSERDES1 OSERDES0 OSERDES1

Clock Event 2

Clock Clock Event 3 Event 4

Internal Reset (CLKDIV)

Internal Reset (CLK)

UG070_c8_20_100307

Figure 8-20:

Two OSERDES Coming Out of Reset Synchronously with One Another

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

381

Chapter 8: Advanced SelectIO Logic Resources

Clock Event 2
The reset pulse is deasserted on the rising edge of CLKDIV. The difference in propagation delay between the two OSERDES causes the SR input to come out of reset on two different CLK cycles. Without internal retiming, OSERDES1 finishes reset one CLK cycle before OSERDES0 and both OSERDES are asynchronous.

Clock Event 3
The release of the reset signal at the SR input is retimed internally to CLKDIV. This synchronizes OSERDES0 and OSERDES1.

Clock Event 4
The release of the reset signal at the SR input is retimed internally to CLK.

OSERDES VHDL and Verilog Instantiation Templates

The Libraries Guide includes instantiation templates of the OSERDES module in VHDL and Verilog.

382

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

Index
A
asynchronous clocking 119 distributed RAM 181 global set/reset 127 mux 36 set/reset in register or latch 180 slice description 174 SLICEL 174 SLICEM 174 CLK2X 55 CLKDV 55 CLKFB 52 CLKFX 55 clock capable I/O 40 clock forwarding 347 clock regions 39 clock tree 38 clocking wizard 83 clocks global clock buffers 26, 27 I/O clock buffer 41 regional clock buffers 40, 42 regions 38 resources 29 CMT 47 allocation in device 48 combinatorial input path 319 configuration DCM 65 See IDELAY 325 Differential 250 HSTL Class II 256 HSTL Class II (1.8V) 264, 267 LVPECL 297 SSTL Class II (1.8V) 286, 291 SSTL2 Class II (2.5V) 277, 281 differential termination 294 DIFF_TERM 237, 294

B
Bitslip 366 See ISERDES 353 guidelines for use 367 operation 366 timing 368 block RAM defined 115 asynchronous clocking 119 ECC 158 Primitive 161 ECC Port 162 operating modes NO_CHANGE 118 READ_FIRST 118 WRITE_FIRST 118 ports 125 synchronous clocking 119 BLVDS 296 BUFG 31 BUFGCE 32 BUFGCTRL 28 BUFGMUX 33 BUFGMUX_CTRL 35 with CE 37 BUFIO 41 BUFR 42

E
Error Correction Code (ECC) 158

F
FIFO 139 attributes 147 cascading 157 FWFT mode 144 operating modes 144 ports 143 primitive 142 standard mode 144 status flags 145 timing parameters 149

D
DCI 220 defined 220 DCLK 53 DCM 48 allocation in device 48 attributes 58, 61 clock deskew 48, 63 clocking wizard 83 configuration 65 DCM_ADV 51 DCM_BASE 50 design guidelines 63 deskew 67 dynamic reconfiguration 49, 73 frequency synthesis 49, 67 output ports 54 phase shifting 49, 68, 85 ports 51 timing models 84 DDR IDDR 319 delay element

G
GCLK 38 global clocks clock buffers 25, 26 clock I/O inputs 26 GSR defined 127 GTL 248 defined 248 GTL_DCI 248 GTLP 249 GTLP_DCI 249

C
CLB 173 array size by device 177 distributed RAM 180 maximum distributed RAM 177 number of flip-flops 177 number of LUTs by device 177 number of shift registers 177 register/latch configuration 179

H
HSTL 250 defined 250 class I 252 class I (1.8V) 263, 274 class II 254

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

383

class II (1.8V) 265 class III 259 class III (1.8V) 270 class IV 260 class IV (1.8V) 271 CSE differential HSTL class II 265 Differential HSTL class II 264, 267 differential HSTL class II 256 HyperTransport HT 296

primitive 338 REFCLK 337, 343 ILOGIC 217, 318 IDDR 319 SR 318 switching characteristics 324 timing 322 IOB 217 defined 218 IOBUF 234 PULLUP/PULLDOWN/KEEPER

M
multirate FIFO 115, 139

N
NO_CHANGE mode 118

O
OBUF 233 OBUFDS 235 OBUFT 234 PULLUP/PULLDOWN/KEEPER

I
I/O standards 218 bank rules 298 compatibility 299 differential I/O 218 single-ended I/O 218 I/O tile 217 ILOGIC 217 IOB 217 OLOGIC 217 IBUF 233 PULLUP/PULLDOWN/KEEPER

237
IOBUFDS 236 IODELAY 325 DATAIN 327 DATAOUT 327 IDATAIN 327 ODATAIN 327 ports 327 ISERDES 353 defined 353 attributes 358 bitslip 353, 356, 367 BITSLIP_ENABLE attribute

237
OBUFTDS 235 ODDR 345 clock forwarding 347 OPPOSITE_EDGE mode 346 ports 347 primitive 347 SAME_EDGE mode 346 OLOGIC 217, 344 timing 348 OSERDES 370 parallel-to-serial converter 370 switching characteristics 377 timing 377, 378

237 IBUFDS 234

IBUFDS_DIFF_OUT 235 IBUFG 26, 233 IBUFGDS 26, 234 IDDR 319 OPPOSITE_EDGE mode 319 ports 321 primitive 321 SAME_EDGE mode 320 SAME_EDGE_PIPELINED mode

358
IDELAY IDELAYCTRL 337 ports 355, 372 primitive 354 serial-to-parallel converter 353, 362 switching characteristics 363 timing models 363 width expansion 361

P
parallel-to-serial converter 370 DDR 370 SDR 370 PCI 247 PFDM 312 PLL allocation in device 48 PSCLK 52

320 IDELAY 325 defined 325 attributes 329

delay mode fixed 325 variable 325 zero-hold time 325 IDELAYCTRL 337 increment/decrement 328 primitive 326 switching characteristics 330 timing 330 IDELAYCTRL 337 instantiating 340, 342 RDY port 341 location 339

L
LDT See HyperTransport 296 LVCMOS 241 defined 241 LVDCI 243 defined 243 LVDCI_DV2 244 source termination 303 LVDS 294 defined 294 LVDS_25_DCI 295 LVPECL 297 defined 297 LVTTL 239 defined 239

R
READ_FIRST mode 118 REFCLK 338, 343 regional clock buffers 25, 40 regional clocks clock buffers 42 clock nets 46 REV 318 RSDS 296

384

www.xilinx.com

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

S
SelectIO IBUF 233 IBUFDS 234 IBUFDS_DIFF_OUT 235 IBUFG 233 IBUFGDS 234 IOBUF 234 IOBUFDS 236 OBUF 233 OBUFDS 235 OBUFT 234 OBUFTDS 235 Simultaneous Switching Output (SSO)

305
Slew Rate SLEW 237 SRHIGH 178 SRLOW 178 SSTL 274 Differential SSTL Class II (1.8V) 286,

291
Differential SSTL2 Class II (2.5V)

277, 281
SSTL18 Class I (1.8V) 285 SSTL18 Class II (1.8V) 288 SSTL2 Class I (2.5V) 276 SSTL2 Class II (2.5V) 279

W
WRITE_FIRST mode 118

Virtex-5 FPGA User Guide UG190 (v5.3) May 17, 2010

www.xilinx.com

385