“Xilinx” and the Xilinx logo shown above are registered trademarks of Xilinx, Inc. Any rights not expressly granted herein are reserved.
CoolRunner, RocketChips, Rocket IP, Spartan, StateBENCH, StateCAD, Virtex, XACT, XC2064, XC3090, XC4005, and XC5210 are
registered trademarks of Xilinx, Inc.
The shadow X shown above is a trademark of Xilinx, Inc.
ACE Controller, ACE Flash, A.K.A. Speed, Alliance Series, AllianceCORE, Bencher, ChipScope, Configurable Logic Cell, CORE Generator,
CoreLINX, Dual Block, EZTag, Fast CLK, Fast CONNECT, Fast FLASH, FastMap, Fast Zero Power, Foundation, Gigabit Speeds...and
Beyond!, HardWire, HDL Bencher, IRL, J Drive, JBits, LCA, LogiBLOX, Logic Cell, LogiCORE, LogicProfessor, MicroBlaze, MicroVia,
MultiLINX, NanoBlaze, PicoBlaze, PLUSASM, PowerGuide, PowerMaze, QPro, Real-PCI, RocketIO, SelectIO, SelectRAM, SelectRAM+,
Silicon Xpresso, Smartguide, Smart-IP, SmartSearch, SMARTswitch, System ACE, Testbench In A Minute, TrueMap, UIM, VectorMaze,
VersaBlock, VersaRing, Virtex-II Pro, Virtex-II EasyPath, Wave Table, WebFITTER, WebPACK, WebPOWERED, XABEL, XACTFloorplanner, XACT-Performance, XACTstep Advanced, XACTstep Foundry, XAM, XAPP, X-BLOX +, XC designated products, XChecker,
XDM, XEPLD, Xilinx Foundation Series, Xilinx XDTV, Xinfo, XSI, XtremeDSP and ZERO+ are trademarks of Xilinx, Inc.
The Programmable Logic Company is a service mark of Xilinx, Inc.
All other trademarks are the property of their respective owners.
Xilinx, Inc. does not assume any liability arising out of the application or use of any product described or shown herein; nor does it convey
any license under its patents, copyrights, or maskwork rights or any rights of others. Xilinx, Inc. reserves the right to make changes, at any
time, in order to improve reliability, function or design and to supply the best product possible. Xilinx, Inc. will not assume responsibility for
the use of any circuitry described herein other than circuitry entirely embodied in its products. Xilinx provides any design, code, or
information shown or described herein “as is.” By providing the design, code, or information as one possible implementation of a feature,
application, or standard, Xilinx makes no representation that such implementation is free from any claims of infringement. You are
responsible for obtaining any rights you may require for your implementation. Xilinx expressly disclaims any warranty whatsoever with
respect to the adequacy of any such implementation, including but not limited to any warranties or representations that the implementation
is free from claims of infringement, as well as any implied warranties of merchantability or fitness for a particular purpose. Xilinx, Inc. devices
and products are protected under U.S. Patents. Other U.S. and foreign patents pending. Xilinx, Inc. does not represent that devices shown
or products described herein are free from patent infringement or from any other third party right. Xilinx, Inc. assumes no obligation to
correct any errors contained herein or to advise any user of this text of any correction if such be made. Xilinx, Inc. will not assume any liability
for the accuracy or correctness of any engineering or software support or assistance provided to a user.
Xilinx products are not intended for use in life support appliances, devices, or systems. Use of a Xilinx product in such applications without
the written consent of the appropriate Xilinx officer is prohibited.
The contents of this manual are owned and copyrighted by Xilinx. Copyright 2001–2007 Xilinx, Inc. All Rights Reserved. Except as stated
herein, none of the material may be copied, reproduced, distributed, republished, downloaded, displayed, posted, or transmitted 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. Any unauthorized use of any material contained in this manual may violate copyright laws, trademark laws, the laws of privacy and
publicity, and communications regulations and statutes.
RocketIO™ Transceiver User Guidewww.xilinx.comUG024 (v3.0) February 22, 2007
Product Not Recommendedfor NewDesigns
RocketIO™ Transceiver User Guide
UG024 (v3.0) February 22, 2007
The following table shows the revision history for this document.
DateVersionRevision
11/20/011.0• Initial Xilinx release.
01/23/021.1• Updated for typographical and other errors found during review.
02/25/021.2• Part of Virtex-II Pro™ Developer’s Kit (March 2002 Release)
07/11/021.3• Updated “PCB Design Requirements”. Added Appendix A, “RocketIO Transceiver
Timing Model.” Changed Cell Models to Appendix B.
09/27/021.4• Added additional IMPORTANT NOTE regarding ISE revisions at the beginning of
Chapter 1
• Added material in section “CRC (Cyclic Redundancy Check).”
• Added section “Other Important Design Notes.”
• New pre-emphasis eye diagrams in section “Pre-emphasis Techniques.”
• Numerous parameter additions previously shown as “TBD” in “MGT Package Pins.”
10/16/021.5• Corrected pinouts for FF1152 package, device column 2VP20/30, LOC Constraints
rows GT_X0_Y0 and GT_X0_Y1.
• Corrected section “CRC Latency” and Ta bl e 2- 20 to express latency in terms of
TXUSRCLK and RXUSRCLK cycles.
• Corrected sequence of packet elements in Figure 2-30.
11/20/021.6• Ta bl e 1 -2 : Added support for XAUI Fibre Channel.
• Corrected max PCB drive distance to 40 inches.
• Reorganized content sequence in Chapter 2, “Digital Design Considerations.”
• Ta bl e 1- 5: Additional information in RXCOMMADET definition.
• Code corrections in VHDL Clock templates.
• “Data Path Latency” section expanded and reformatted.
• Corrections in clocking scheme drawings. Addition of drawings showing clocking
schemes without using DCM.
• Ta bl e B- 1: Corrections in Valid Data Characters.
• Ta bl e 3- 4: Data added.
• Corrections made to power regulator schematic, Figure 3-7.
• Ta bl e 2- 23 : Data added/corrected.
12/12/021.6.1• Added clarifying text regarding trace length vs. width.
03/25/032.0• Reorganized existing content
• Added new content
• Added Appendix C, “Related Online Documents”
• Added “Index”
UG024 (v3.0) February 22, 2007www.xilinx.comRocketIO™ Transceiver User Guide
Product Not Recommendedfor NewDesigns
DateVersionRevision
06/12/032.1• Ta bl e 1 -2 : Added qualifying footnote to XAUI 10GFC.
• Ta bl e 1- 5: Corrected definition of RXRECCLK.
• Section “RocketIO Transceiver Instantiations” in Chapter 1: added text briefly
explaining what the Instantiation Wizard does.
• Ta bl e 2- 14 : Changed numerics from exact values to rounded-off approximations
(nearest 5,000), and added footnote calling attention to this.
• Section “Clocking” in Chapter 2: added text recommending use of an IBUFGDS for
reference clock input to FPGA fabric.
• Section “RXRECCLK” in Chapter 2: Deleted references to SERDES_10B attribute and
to divide-by-10. (RXRECCLK is always 1/20th the data rate.).
• Section “CRC_FORMAT” in Chapter 2: Corrected minimum data length for
USER_MODE to “greater than 20”.
• Ta bl e 3- 5: Clarified the significance of the V
• Section “AC and DC Coupling” in Chapter 3: Explanatory material added regarding
V
TRX/VTTX
settings when AC or DC coupling is used.
• Ta bl e 4- 1: Corrected pinouts for FG256 and FG456.
• Ta bl e 4- 3: Corrected pinouts for FF1517 (XC2VP70).
TTX/VTRX
voltages shown in this table.
11/07/032.2• Section “Clock Signals” in Chapter 2: Added material that states:
♦ the reference clock must be provided at all times.
♦ any added jitter on the reference clock will be reflected on the RX/TX I/O.
• Figure 2-3: Added a BUFG after the IBUFGDS reference clock buffer.
• Section “RX_BUFFER_USE” in Chapter 2: Corrected erroneous “USRCLK2” to
“RXUSRCLK/RXUSRCLK2”.
• Ta bl e 2- 20 : Added footnotes qualifying the maximum receive-side latency parameters
given in the table.
• Section “FIBRE_CHAN” in Chapter 2: Added specification for minimum data length
(24 bytes not including CRC placeholder).
• Section “ETHERNET” in Chapter 2: Added note indicating that Gigabit Ethernet 802.3
frame specifications must be adhered to.
• Ta bl e 2- 23 : Corrected “External” to “Internal” loopback. Improved explanation of
Parallel Mode loopback.
• Added Figure 2-28, “Serial and Parallel Loopback Logic.”
• Section “Clock and Data Recovery” in Chapter 3: Corrected text to make clear that
RXRECCLK is always 1/20th the incoming data rate, and that CDR requires a
minimum number of transitions to achieve and maintain a lock on the received data.
• Section “Voltage Regulation” in Chapter 3: Added material defining voltage regulator
requirements when a device other than the LT1963 is used.
• Section “AC and DC Coupling” in Chapter 3: Added footnote to Ta bl e 3- 8 clarifying
V
TRX/VTTX
voltage compliance.
• Figure 3-17 and section “Epson EG-2121CA 2.5V (LVPECL Outputs)” in Chapter 3:
Added material specifying the optional use of an LVPECL buffer as an alternative to
the LVDS buffer previously specified.
• Ta bl e 4- 2: Added pinouts for FG676 package, XC2VP20 and XC2VP30.
• Ta bl e A- 5: Added BREFCLK parameters T
BREFPWH
and T
BREFPWL
• Section “Application Notes” in Appendix C: Included new Xilinx Application Notes
XAPP648, XAPP669, and XAPP670.
• Various non-technical edits and corrections.
.
RocketIO™ Transceiver User Guidewww.xilinx.comUG024 (v3.0) February 22, 2007
Product Not Recommendedfor NewDesigns
DateVersionRevision
02/24/042.3• Tabl e 2- 3, p age 41: Added FG676 row to BREFCLK Pin Numbers.
The RocketIO Transceiver User Guide provides the product designer with the detailed
technical information needed to successfully implement the RocketIO™ multi-gigabit
transceiver in Virtex-II Pro Platform FPGA designs.
RocketIO Features
The RocketIO transceiver’s flexible, programmable features allow a multi-gigabit serial
transceiver to be easily integrated into any Virtex-II Pro design:
Preface
•Variable-speed, full-duplex transceiver, allowing 600 Mb/s to 3.125 Gb/s baud
•Monolithic clock synthesis and clock recovery system, eliminating the need for
•Automatic lock-to-reference function
•Five levels of programmable serial output differential swing (800 mV to 1600 mV
•Four levels of programmable pre-emphasis
•AC and DC coupling
•Programmable 50Ω/75Ω on-chip termination, eliminating the need for external
•Serial and parallel TX-to-RX internal loopback modes for testing operability
•Programmable comma detection to allow for any protocol and detection of any 10-bit
Guide Contents
The RocketIO Transceiver User Guide contains these sections:
•Preface, “About This Guide” — This section.
•Chapter 1, “RocketIO Transceiver Overview” — An overview of the transceiver’s
•Chapter 2, “Digital Design Considerations” — Ports and attributes for the six
•Chapter 3, “Analog Design Considerations” — RocketIO serial overview; pre-
transfer rates
external components
peak-peak), allowing compatibility with other serial system voltage levels
termination resistors
character.
capabilities and how it works.
provided communications protocol primitives; VHDL/Verilog code examples for
clocking and reset schemes; transceiver instantiation; 8B/10B encoding; CRC; channel
bonding.
•Chapter 4, “Simulation and Implementation” — Simulation models; implementation
tools; debugging and diagnostics.
•Appendix A, “RocketIO Transceiver Timing Model” — Timing parameters associated
with the RocketIO transceiver core.
•Appendix B, “8B/10B Valid Characters” — Valid data and K-characters.
•Appendix C, “Related Online Documents” — Bibliography of online Application
Notes, Characterization Reports, and White Papers.
For More Information
For a complete menu of online information resources available on the Xilinx website, visit
http://www.xilinx.com/virtex2pro/
Documents.”
For a comprehensive listing of available tutorials and resources on network technologies
and communications protocols, visit http://www.iol.unh.edu/training/
Additional Resources
Preface: About This Guide
or refer to Appendix C, “Related Online
.
For additional information, go to http://support.xilinx.com. The following table lists
some of the resources you can access from this website. You can also directly access these
resources using the provided URLs.
ResourceDescription/URL
TutorialsTutorials covering Xilinx design flows, from design entry to
This document uses the following conventions. An example illustrates each typographical
and online convention.
Input and output ports of the RocketIO transceiver primitives are denoted in upper-case
letters. Attributes of the RocketIO transceiver are denoted in upper-case letters with
underscores. Trailing numbers in primitive names denote the byte width of the data path.
These values are preset and not modifiable. When assumed to be the same frequency,
RXUSRCLK and TXUSRCLK are referred to as USRCLK and can be used interchangeably.
This also holds true for RXUSRCLK2, TXUSRCLK2, and USRCLK2.
Comma Definition
A comma is a “K-character” used by the transceiver to align the serial data on a
byte/half-word boundary (depending on the protocol used), so that the serial data is
correctly decoded into parallel data.
Typographical
The following typographical conventions are used in this document:
Courier font
Courier bold
Helvetica bold
Italic font
ConventionMeaning or UseExample
Messages, prompts, and
program files that the system
displays
Literal commands that you
enter in a syntactical statement
Commands that you select
from a menu
Keyboard shortcutsCtrl+C
Variables in a syntax
statement for which you must
supply values
References to other manuals
Emphasis in text
speed grade: - 100
ngdbuilddesign_name
File → Open
ngdbuild design_name
See the Development System
Reference Guide for more
information.
If a wire is drawn so that it
overlaps the pin of a symbol,
the two nets are not connected.
An optional entry or
Square brackets [ ]
Braces { }
RocketIO™ Transceiver User Guidewww.xilinx.com19
UG024 (v3.0) February 22, 2007
parameter. However, in bus
specifications, such as
bus[7:0], they are required.
A list of items from which you
must choose one or more
ngdbuild [ option_name]
design_name
lowpwr ={on|off}
Product Not Recommendedfor NewDesigns
R
ConventionMeaning or UseExample
Preface: About This Guide
Vertical bar |
Vertical ellipsis
Horizontal ellipsis . . .
Online Document
The following conventions are used in this document:
ConventionMeaning or UseExample
Blue text
Red text
Separates items in a list of
choices
.
.
.
Repetitive material that has
been omitted
Repetitive material that has
been omitted
Cross-reference link to a
location in the current
document
Cross-reference link to a
location in another document
lowpwr ={on|off}
IOB #1: Name = QOUT’
IOB #2: Name = CLKIN’
.
.
.
allow block block_name
loc1 loc2 ... locn;
See the section “Additional
Resources” for details.
Refer to “Title Formats” in
Chapter 1 for details.
See Figure 2-5 in the Virtex-II
Handbook.
Blue, underlined text
Hyperlink to a website (URL)
Go to http://www.xilinx.com
for the latest speed files.
20www.xilinx.comRocketIO™ Transceiver User Guide
UG024 (v3.0) February 22, 2007
Product Not Recommendedfor NewDesigns
R
RocketIO Transceiver Overview
Basic Architecture and Capabilities
The RocketIO transceiver is based on Mindspeed’s SkyRail™ technology. Figure 1-1,
page 22, depicts an overall block diagram of the transceiver. Up to 20 transceiver modules
are available on a single Virtex-II Pro FPGA, depending on the part being used. Tab le 1-1
shows the RocketIO cores available by device.
Table 1-1: Number of RocketIO Cores per Device Type
DeviceRocketIO CoresDeviceRocketIO Cores
XC2VP24XC2VP400 or 12
XC2VP44XC2VP500 or 16
XC2VP78XC2VP7016 or 20
XC2VP208XC2VP1000 or 20
XC2VP308
Chapter 1
The transceiver module is designed to operate at any serial bit rate in the range of
600 Mb/s to 3.125 Gb/s per channel, including the specific bit rates used by the
communications standards listed in Tabl e 1 -2. The serial bit rate need not be configured in
the transceiver, as the operating frequency is implied by the received data, the reference
clock applied, and the SERDES_10B attribute (see Ta bl e 1 -3 ).
Table 1-2: Communications Standards Supported by RocketIO Transceiver
1. One channel is considered to be one transceiver.
2. Out-of-Band (OOB) signals are not supported with the transceiver.
3. Supported with the GT_CUSTOM primitive. Certain attributes must be modified to comply with the XAUI 10GFC specifications,
including but not limited to CLK_COR_SEQ and CHAN_BOND_SEQ.
4. Bit rate is possible with the following topology specification: maximum 6" FR4 and one Molex 74441 connector.
(2)
(3)
Channels
(Lanes)
(1)
12.5
43.1875
I/O Bit Rate
(Gb/s)
1.06
2.12
(4)
RocketIO™ Transceiver User Guidewww.xilinx.com21
UG024 (v3.0) February 22, 2007
R
PACKAGE
PINS
Product Not Recommendedfor NewDesigns
Chapter 1: RocketIO Transceiver Overview
Table 1-3: Serial Baud Rates and the SERDES_10B Attribute
Tab le 1 -4 lists the sixteen gigabit transceiver primitives provided. These primitives carry
attributes set to default values for the communications protocols listed in Ta bl e 1 -2 . Data
widths of one, two, and four bytes are selectable for each protocol.
There are two ways to modify the RocketIO transceiver:
•Static properties can be set through attributes in the HDL code. Use of attributes are
covered in detail in “Primitive Attributes,” page 29.
•Dynamic changes can be made by the ports of the primitives
Fully customizable
by user
Fibre Channel,
1-byte data path
Fibre Channel,
2-byte data path
Fibre Channel,
4-byte data path
Gigabit Ethernet,
1-byte data path
Gigabit Ethernet,
2-byte data path
Gigabit Ethernet,
4-byte data path
10-Gb Ethernet,
1-byte data path
GT_XAUI_2
GT_XAUI_4
GT_INFINIBAND_1
GT_INFINIBAND_2
GT_INFINIBAND_4
GT_AURORA_1
GT_AURORA_2
GT_AURORA_4
10-Gb Ethernet,
2-byte data path
10-Gb Ethernet,
4-byte data path
Infiniband, 1-byte
data path
Infiniband, 2-byte
data path
Infiniband, 4-byte
data path
Xilinx protocol,
1-byte data path
Xilinx protocol,
2-byte data path
Xilinx protocol,
4-byte data path
The RocketIO transceiver consists of the Physical Media Attachment (PMA) and Physical
Coding Sublayer (PCS). The PMA contains the serializer/deserializer (SERDES), TX and
RX buffers, clock generator, and clock recovery circuitry. The PCS contains the 8B/10B
encoder/decoder and the elastic buffer supporting channel bonding and clock correction.
The PCS also handles Cyclic Redundancy Check (CRC). Refer again to Figure 1-1, showing
the RocketIO transceiver top-level block diagram and FPGA interface signals.
RocketIO Transceiver Instantiations
For the different clocking schemes, several things must change, including the clock
frequency for USRCLK and USRCLK2 discussed in “Digital Clock Manager (DCM)
Examples” in Chapter 2. The data and control ports for GT_CUSTOM must also reflect this
change in data width by concatenating zeros onto inputs and wires for outputs for Verilog
designs, and by setting outputs to open and concatenating zeros on unused input bits for
VHDL designs.
HDL Code Examples
Please use the Architecture Wizard to create instantiation templates. This wizard creates
code and instantiation templates that define the attributes for a specific application.
RocketIO™ Transceiver User Guidewww.xilinx.com23
UG024 (v3.0) February 22, 2007
Product Not Recommendedfor NewDesigns
R
List of Available Ports
The RocketIO transceiver primitives contain 50 ports, with the exception of the 46-port
GT_ETHERNET and GT_FIBRE_CHAN primitives. The differential serial data ports
(RXN, RXP, TXN, and TXP) are connected directly to external pads; the remaining 46 ports
are all accessible from the FPGA logic (42 ports for GT_ETHERNET and
GT_FIBRE_CHAN).
Tab le 1 -5 contains the port descriptions of all primitives.
Chapter 1: RocketIO Transceiver Overview
Table 1-5: GT_CUSTOM
(1)
, GT_AURORA, GT_FIBRE_CHAN
(2)
, GT_ETHERNET
(2)
,
GT_INFINIBAND, and GT_XAUI Primitive Ports
PortI/O
Port
Size
Definition
BREFCLKI1This high-quality reference clock uses dedicated routing to improve
jitter for serial speeds of 2.5 Gb/s or greater. See Tab le 2 - 2, p a ge 4 0 for
usage cases.
BREFCLK2I1Alternative to BREFCLK. Can be selected by REFCLKSEL.
CHBONDDONE
(2)
O1Indicates a receiver has successfully completed channel bonding when
asserted High.
CHBONDI
(2)
I4The channel bonding control that is used only by “slaves” which is
driven by a transceiver's CHBONDO port.
CHBONDO
(2)
O4Channel bonding control that passes channel bonding and clock
correction control to other transceivers.
CONFIGENABLEI1Reconfiguration enable input (unused). Should be set to logic 0.
CONFIGINI1Data input for reconfiguring transceiver (unused). Should be set to
logic 0.
CONFIGOUTO1Data output for configuration readback (unused). Should be left
unconnected.
ENCHANSYNC
(2)
I1Comes from the core to the transceiver and enables the transceiver to
perform channel bonding
ENMCOMMAALIGNI1Selects realignment of incoming serial bitstream on minus-comma.
High realigns serial bitstream byte boundary when minus-comma is
detected.
ENPCOMMAALIGNI1Selects realignment of incoming serial bitstream on plus-comma. High
realigns serial bitstream byte boundary when plus-comma is detected.
LOOPBACKI2Selects the two loopback test modes. Bit 1 is for serial loopback and bit 0
is for internal parallel loopback.
POWERDOWNI1Shuts down both the receiver and transmitter sides of the transceiver
when asserted High. This decreases the power consumption while the
transceiver is shut down. This input is asynchronous.
24www.xilinx.comRocketIO™ Transceiver User Guide
UG024 (v3.0) February 22, 2007
Product Not Recommendedfor NewDesigns
List of Available Ports
R
Table 1-5: GT_CUSTOM
(1)
, GT_AURORA, GT_FIBRE_CHAN
(2)
, GT_ETHERNET
(2)
,
GT_INFINIBAND, and GT_XAUI Primitive Ports (Continued)
and multiplied for parallel/serial conversion) and clock recovery.
REFCLK frequency is accurate to ±100 ppm. When running an
asynchronous system, this accuracy must be met by both reference
clocks. This clock originates off the device, is routed through fabric
interconnect, and is selected by REFCLKSEL.
REFCLK2I1An alternative to REFCLK. Can be selected by REFCLKSEL.
REFCLKSELI1Selects the reference clock to use:
Low = selects REFCLK if REF_CLK_V_SEL = 0
selects BREFCLK if REF_CLK_V_SEL = 1
High = selects REFCLK2 if REF_CLK_V_SEL = 0
selects BREFCLK2 if REF_CLK_V_SEL = 1
See “REF_CLK_V_SEL,” page 32.
RXBUFSTATUSO2Receiver elastic buffer status. Bit 1 indicates if an overflow/underflow
error has occurred when asserted High. Bit 0 indicates that the buffer is
at least half-full when asserted High.
(3)
RXCHARISCOMMA
RXCHARISK
(3)
O1, 2, 4Similar to RXCHARISK except that the data is a comma.
O1, 2, 4If 8B/10B decoding is enabled, it indicates that the received data is a
K-character when asserted High. Included in Byte-mapping. If 8B/10B
decoding is bypassed, it remains as the first bit received (Bit “a”) of the
10-bit encoded data (see Figure 2-14, page 65).
RXCHECKINGCRCO1CRC status for the receiver. Asserts High to indicate that the receiver
has recognized the end of a data packet. Only meaningful if
RX_CRC_USE = TRUE.
RXCLKCORCNTO3Status that denotes occurrence of clock correction or channel bonding.
This status is synchronized on the incoming RXDATA. See
“RXCLKCORCNT,” page 76.
RXCOMMADETO1Signals that a comma has been detected in the data stream.
To assure signal is reliably brought out to the fabric for different data
paths, this signal may remain High for more than one
USRCLK/USRCLK2 cycle.
RXCRCERRO1Indicates if the CRC code is incorrect when asserted High. Only
meaningful if RX_CRC_USE = TRUE.
RXDATA
(3)
O8, 16, 32 Up to four bytes of decoded (8B/10B encoding) or encoded (8B/10B
bypassed) receive data.
RXDISPERR
(3)
O1, 2, 4If 8B/10B encoding is enabled it indicates whether a disparity error has
occurred on the serial line. Included in Byte-mapping scheme.
RocketIO™ Transceiver User Guidewww.xilinx.com25
UG024 (v3.0) February 22, 2007
Product Not Recommendedfor NewDesigns
R
Chapter 1: RocketIO Transceiver Overview
Table 1-5: GT_CUSTOM
(1)
, GT_AURORA, GT_FIBRE_CHAN
(2)
, GT_ETHERNET
(2)
,
GT_INFINIBAND, and GT_XAUI Primitive Ports (Continued)
PortI/O
Port
Size
Definition
RXLOSSOFSYNCO2Status related to byte-stream synchronization
(RX_LOSS_OF_SYNC_FSM)
If RX_LOSS_OF_SYNC_FSM = TRUE, RXLOSSOFSYNC indicates the
state of the FSM:
Bit 1 = Loss of sync (High)
Bit 0 = Resync state (High)
If RX_LOSS_OF_SYNC_FSM = FALSE, RXLOSSOFSYNC indicates:
Bit 1 = Received data invalid (High)
Bit 0 = Channel bonding sequence recognized (High)
(4)
RXN
RXNOTINTABLE
(3)
I1Serial differential port (FPGA external)
O1,2,4Status of encoded data when the data is not a valid character when
asserted High. Applies to the byte-mapping scheme.
RXP
(4)
I1Serial differential port (FPGA external)
RXPOLARITYI1Similar to TXPOLARITY, but for RXN and RXP. When de-asserted,
assumes regular polarity. When asserted, reverses polarity.
RXREALIGNO1Signal from the PMA denoting that the byte alignment with the serial
data stream changed due to a comma detection. Asserted High when
alignment occurs.
RXRECCLKO1Clock recovered from the data stream by dividing its speed by 20.
RXRESETI1Synchronous RX system reset that “recenters” the receive elastic buffer.
It also resets 8B/10B decoder, comma detect, channel bonding, clock
correction logic, and other internal receive registers. It does not reset the
receiver PLL.
RXRUNDISP
(3)
O1, 2, 4Signals the running disparity (0 = negative, 1 = positive) in the received
serial data. If 8B/10B encoding is bypassed, it remains as the second bit
received (Bit “b”) of the 10-bit encoded data (see Figure 2-14, page 65).
RXUSRCLKI1Clock from a DCM or a BUFG that is used for reading the RX elastic
buffer. It also clocks CHBONDI and CHBONDO in and out of the
transceiver. Typically, the same as TXUSRCLK.
RXUSRCLK2I1Clock output from a DCM that clocks the receiver data and status
between the transceiver and the FPGA core. Typically the same as
TXUSRCLK2. The relationship between RXUSRCLK and RXUSRCLK2
depends on the width of RXDATA.
TXBUFERRO1Provides status of the transmission FIFO. If asserted High, an
overflow/underflow has occurred. When this bit becomes set, it can
only be reset by asserting TXRESET.
TXBYPASS8B10B
(3)
I1, 2, 4This control signal determines whether the 8B/10B encoding is enabled
or bypassed. If the signal is asserted High, the encoding is bypassed.
This creates a 10-bit interface to the FPGA core. See the 8B/10B section
for more details.
26www.xilinx.comRocketIO™ Transceiver User Guide
UG024 (v3.0) February 22, 2007
Product Not Recommendedfor NewDesigns
List of Available Ports
R
Table 1-5: GT_CUSTOM
(1)
, GT_AURORA, GT_FIBRE_CHAN
(2)
, GT_ETHERNET
(2)
,
GT_INFINIBAND, and GT_XAUI Primitive Ports (Continued)
PortI/O
TXCHARDISPMODE
(3)
Port
Size
Definition
I1, 2, 4If 8B/10B encoding is enabled, this bus determines what mode of
disparity is to be sent. When 8B/10B is bypassed, this becomes the first
bit transmitted (Bit “a”) of the 10-bit encoded TXDATA bus section (see
Figure 2-13, page 65) for each byte specified by the byte-mapping.
TXCHARDISPVAL
(3)
I1,2,4If 8B/10B encoding is enabled, this bus determines what type of
disparity is to be sent. When 8B/10B is bypassed, this becomes the
second bit transmitted (Bit “b”) of the 10-bit encoded TXDATA bus
section (see Figure 2-13, page 65) for each byte specified by the bytemapping section.
TXCHARISK
(3)
I1, 2, 4If 8B/10B encoding is enabled, this control bus determines if the
transmitted data is a K-character or a Data character. A logic High
indicates a K-character.
TXDATA
(3)
I8, 16,32Transmit data that can be 1, 2, or 4 bytes wide, depending on the
primitive used. TXDATA [7:0] is always the last byte transmitted. The
position of the first byte depends on selected TX data path width.
TXFORCECRCERRI1Specifies whether to insert error in computed CRC.
When TXFORCECRCERR = TRUE, the transmitter corrupts the
correctly computed CRC value by XORing with the bits specified in
attribute TX_CRC_FORCE_VALUE. This input can be used to test
detection of CRC errors at the receiver.
TXINHIBITI1If a logic High, the TX differential pairs are forced to be a constant 1/0.
TXN = 1, TXP = 0
TXKERR
(3)
O1,2,4If 8B/10B encoding is enabled, this signal indicates (High) when the
K-character to be transmitted is not a valid K-character. Bits correspond
to the byte-mapping scheme.
TXN
TXP
(4)
(4)
O1Transmit differential port (FPGA external)
O1Transmit differential port (FPGA external)
TXPOLARITYI1Specifies whether or not to invert the final transmitter output. Able to
reverse the polarity on the TXN and TXP lines. Deasserted sets regular
polarity. Asserted reverses polarity.
TXRESETI1Synchronous TX system reset that “recenters” the transmit elastic
buffer. It also resets 8B/10B encoder and other internal transmission
registers. It does not reset the transmission PLL.
TXRUNDISP
(3)
O1, 2, 4Signals the running disparity after this byte is encoded. Low indicates
negative disparity, High indicates positive disparity.
TXUSRCLKI1Clock output from a DCM or a BUFG that is clocked with a reference
clock. This clock is used for writing the TX buffer and is frequencylocked to the reference clock.
RocketIO™ Transceiver User Guidewww.xilinx.com27
UG024 (v3.0) February 22, 2007
Product Not Recommendedfor NewDesigns
R
Chapter 1: RocketIO Transceiver Overview
Table 1-5: GT_CUSTOM
(1)
, GT_AURORA, GT_FIBRE_CHAN
(2)
, GT_ETHERNET
(2)
,
GT_INFINIBAND, and GT_XAUI Primitive Ports (Continued)
PortI/O
Port
Size
Definition
TXUSRCLK2I1Clock output from a DCM that clocks transmission data and status and
reconfiguration data between the transceiver an the FPGA core. The
ratio between TXUSRCLK and TXUSRCLK2 depends on the width of
TXDATA.
Notes:
1. The GT_CUSTOM ports are always the maximum port size.
2. GT_FIBRE_CHAN and GT_ETHERNET ports do not have the three CHBOND** or ENCHANSYNC ports.
3. The port size changes with relation to the primitive selected, and also correlates to the byte mapping.
4. External ports only accessible from package pins.
28www.xilinx.comRocketIO™ Transceiver User Guide
UG024 (v3.0) February 22, 2007
Product Not Recommendedfor NewDesigns
Primitive Attributes
Primitive Attributes
The primitives also contain attributes set by default to specific values controlling each
specific primitive’s protocol parameters. Included are channel-bonding settings (for
primitives supporting channel bonding), clock correction sequences, and CRC. Tab le 1 -6
shows a brief description of each attribute. Tab le 1 - 7 and Ta bl e 1 -8 have the default values
of each primitive.
Table 1-6: RocketIO Transceiver Attributes
AttributeDescription
ALIGN_COMMA_MSBTRUE/FALSE controls the alignment of detected commas within the
transceiver’s 2-byte-wide data path.
FALSE: Align commas within a 10-bit alignment range. As a result the
comma is aligned to either RXDATA[15:8} byte or RXDATA [7:0] byte in
the transceivers internal data path.
TRUE: Aligns comma with 20-bit alignment range.
As a result aligns on the RXDATA[15:8] byte.
Notes:
1. If protocols (like Gigabit Ethernet) are oriented in byte pairs with commas always in
even (first) byte formation, this can be set to TRUE. Otherwise, it should be set to
FALSE.
2. For 32-bit data path primitives, see “32-bit Alignment Design,” page 95.
3. This attribute is only modifiable in the GT_CUSTOM primitive.
R
CHAN_BOND_LIMITInteger 1-31 that defines maximum number of bytes a slave receiver can read
following a channel bonding sequence and still successfully align to that
sequence.
CHAN_BOND_MODESTRING
OFF, MASTER, SLAVE_1_HOP, SLAVE_2_HOPS
OFF: No channel bonding involving this transceiver.
MASTER: This transceiver is master for channel bonding. Its CHBONDO
port directly drives CHBONDI ports on one or more SLAVE_1_HOP
transceivers.
SLAVE_1_HOP: This transceiver is a slave for channel bonding.
SLAVE_1_HOP’s CHBONDI is directly driven by a MASTER transceiver
CHBONDO port. SLAVE_1_HOP’s CHBONDO port can directly drive
CHBONDI ports on one or more SLAVE_2_HOPS transceivers.
SLAVE_2_HOPS: This transceiver is a slave for channel bonding.
SLAVE_2_HOPS CHBONDI is directly driven by a SLAVE_1_HOP
CHBONDO port.
CHAN_BOND_OFFSETInteger 0-15 that defines offset (in bytes) from channel bonding sequence for
realignment. It specifies the first elastic buffer read address that all channelbonded transceivers have immediately after channel bonding.
CHAN_BOND_WAIT specifies the number of bytes that the master
transceiver passes to RXDATA, starting with the channel bonding sequence,
before the transceiver executes channel bonding (alignment) across all
channel-bonded transceivers.
CHAN_BOND_OFFSET specifies the first elastic buffer read address that all
channel-bonded transceivers have immediately after channel bonding
(alignment), as a positive offset from the beginning of the matched channel
bonding sequence in each transceiver.
For optimal performance of the elastic buffer, CHAN_BOND_WAIT and
CHAN_BOND_OFFSET should be set to the same value (typically 8).
CHAN_BOND_ONE_SHOTTRUE/FALSE that controls repeated execution of channel bonding.
FALSE: Master transceiver initiates channel bonding whenever possible
(whenever channel-bonding sequence is detected in the input) as long as
input ENCHANSYNC is High and RXRESET is Low.
TRUE: Master transceiver initiates channel bonding only the first time it
is possible (channel bonding sequence is detected in input) following
negated RXRESET and asserted ENCHANSYNC. After channel-bonding
alignment is done, it does not occur again until RXRESET is asserted and
negated, or until ENCHANSYNC is negated and reasserted.
Always set Slave transceivers CHAN_BOND_ONE_SHOT to FALSE.
Chapter 1: RocketIO Transceiver Overview
CHAN_BOND_SEQ_*_*11-bit vectors that define the channel bonding sequence. The usage of these
vectors also depends on CHAN_BOND_SEQ_LEN and
CHAN_BOND_SEQ_2_USE. See “Receiving Vitesse Channel Bonding
Sequence,” page 65, for format.
CHAN_BOND_SEQ_2_USEControls use of second channel bonding sequence.
FALSE: Channel bonding uses only one channel bonding sequence
defined by CHAN_BOND_SEQ_1_1...4.
TRUE: Channel bonding uses two channel bonding sequences defined
by:
CHAN_BOND_SEQ_1_1...4 and
CHAN_BOND_SEQ_2_1...4
as further constrained by CHAN_BOND_SEQ_LEN.
CHAN_BOND_SEQ_LENInteger 1-4 defines length in bytes of channel bonding sequence. This
defines the length of the sequence the transceiver matches to detect
opportunities for channel bonding.
CHAN_BOND_WAITInteger 1-15 that defines the length of wait (in bytes) after seeing channel
bonding sequence before executing channel bonding.
30www.xilinx.comRocketIO™ Transceiver User Guide
UG024 (v3.0) February 22, 2007
Loading...
+ 126 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.