LogiCORE™ IP
Ethernet 1000BASE-X
PCS/PMA or SGMII v9.1
User Guide
UG155 March 24, 2008
R
R
Xilinx is disclosing this Specification to you solely for use in the development of designs to operate on Xilinx FPGAs. Except as stated herein,
none of the Specification 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 this Specification may violate copyright laws, trademark laws, the laws of privacy and publicity, and
communications regulations and statutes.
Xilinx does not assume any liability arising out of the application or use of the Specification; nor does Xilinx convey any license under its
patents, copyrights, or any rights of others. You are responsible for obtaining any rights you may require for your use or implementation of
the Specification. Xilinx reserves the right to make changes, at any time, to the Specification as deemed desirable in the sole discretion of
Xilinx. Xilinx assumes no obligation to correct any errors contained herein or to advise you of any correction if such be made. Xilinx will not
assume any liability for the accuracy or correctness of any engineering or technical support or assistance provided to you in connection with
the Specification.
THE SPECIFICATION IS PROVIDED “AS IS" WITH ALL FAULTS, AND THE ENTIRE RISK AS TO ITS FUNCTION AND
IMPLEMENTATION IS WITH YOU. YOU ACKNOWLEDGE AND AGREE THAT YOU HAVE NOT RELIED ON ANY ORAL OR WRITTEN
INFORMATION OR ADVICE, WHETHER GIVEN BY XILINX, OR ITS AGENTS OR EMPLOYEES. XILINX MAKES NO OTHER
WARRANTIES, WHETHER EXPRESS, IMPLIED, OR STATUTORY, REGARDING THE SPECIFICATION, INCLUDING ANY
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NONINFRINGEMENT OF THIRDPARTY RIGHTS.
IN NO EVENT WILL XILINX BE LIABLE FOR ANY CONSEQUENTIAL, INDIRECT, EXEMPLARY, SPECIAL, OR INCIDENTAL DAMAGES,
INCLUDING ANY LOST DATA AND LOST PROFITS, ARISING FROM OR RELATING TO YOUR USE OF THE SPECIFICATION, EVEN IF
YOU HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE TOTAL CUMULATIVE LIABILITY OF XILINX IN
CONNECTION WITH YOUR USE OF THE SPECIFICATION, WHETHER IN CONTRACT OR TORT OR OTHERWISE, WILL IN NO EVENT
EXCEED THE AMOUNT OF FEES PAID BY YOU TO XILINX HEREUNDER FOR USE OF THE SPECIFICATION. YOU ACKNOWLEDGE
THAT THE FEES, IF ANY, REFLECT THE ALLOCATION OF RISK SET FORTH IN THIS AGREEMENT AND THAT XILINX WOULD NOT
MAKE AVAILABLE THE SPECIFICATION TO YOU WITHOUT THESE LIMITATIONS OF LIABILITY.
The Specification is not designed or intended for use in the development of on-line control equipment in hazardous environments requiring
fail-safe controls, such as in the operation of nuclear facilities, aircraft navigation or communications systems, air traffic control, life support,
or weapons systems (“High-Risk Applications”). Xilinx specifically disclaims any express or implied warranties of fitness for such High-Risk
Applications. You represent that use of the Specification in such High-Risk Applications is fully at your risk.
www.xilinx.comEthernet 1000BASE-X PCS/PMA or SGMII v9.1
UG155 March 24, 2008
R
About This Guide
The LogiCORE™ IP Ethernet 1000BASE-X PCS/PMA or SGMII User Guide provides
information about generating a Xilinx Ethernet 1000BASE-X PCS/PMA or SGMII core,
customizing and simulating the core using the provided example design, and running the
design files through implementation using the Xilinx tools.
Guide Contents
This guide contains the following information.
•Preface, “About This Guide” introduces the organization and purpose of this guide
and defines the conventions used in this document.
•Chapter 1, “Introduction” describes the core and related information, including
recommended design experience, additional documentation resources, technical
support, and submitting feedback to Xilinx.
•Chapter 2, “Core Architecture” provides an overview of the core including all
interfaces and major functional blocks.
•Chapter 3, “Generating and Customizing the Core” describes the Graphical User
Interface (GUI) options used to generate and customize the core.
•Chapter 4, “Designing with the Core” provides general guidelines for creating
designs with the core.
•Chapter 5, “Using the Client-side GMII Data Path” provides general guidelines for
creating designs using client side GMII of the Ethernet 1000BASE-X PCS/PMA or
SGMII core.
•Chapter 6, “The Ten-Bit Interface” provides general design guidelines when using the
Ten-Bit Interface (TBI) as the Physical Side of the core.
•Chapter 7, “1000BASE-X with RocketIO Transceivers” provides general design
guidelines when using the 1000BASE-X standard with the RocketIO™ transceiver as
the physical side of the core.
•Chapter 8, “SGMII / Dynamic Standards Switching with RocketIO Transceivers”
provides general design guidelines when using either the SGMII standard, or the
Dynamic Switching option (between 1000BASE-X and SGMII standards). These
options always use a RocketIO as the physical interface.
•Chapter 9, “Configuration and Status” provides general guidelines for configuring
and monitoring the core, including a detailed description of the management registers
present in the core.
•Chapter 10, “Auto-Negotiation” provides guidelines for Auto-Negotiation function of
the core.
Preface
Ethernet 1000BASE-X PCS/PMA or SGMII v9.1www.xilinx.com17
UG155 March 24, 2008
R
•Chapter 11, “Dynamic Switching of 1000BASE-X and SGMII Standards” provides
general guidelines for using the core to perform dynamic standards switching
between 1000BASE-X and SGMII.
•Chapter 12, “Constraining the Core” defines the constraint requirements of the core.
•Chapter 13, “Interfacing to Other Cores” describes additional design considerations
associated with implementing the core with the 1-Gigabit Ethernet MAC and TriMode Ethernet MAC cores.
considerations associated with implementing the core.
•Chapter 15, “Implementing the Design”describes how to simulate and implement
your design containing the core.
•Appendix A, “Core Verification, Compliance, and Interoperability” describes how the
core was verified.
•Appendix B, “Core Latency” defines the latency of the core.
•Appendix C, “Calculating the DCM Fixed Phase Shift Value” instructs the user about
how to calculate the system timing requirements when using DCMs with the core.
•Appendix D, “1000BASE-X State Machines” serves as a reference for the basic
operation of the 1000BASE-X IEEE 802.3 clause 36 transmitter and receiver state
machines.
•Appendix E, “Rx Elastic Buffer Specifications” describes the depth of the Rx Elastic
Buffers which are available with the core. The size of the buffer is related to the
maximum frame size which the core can accommodate.
•Appendix F, “Debugging Guide” provides information for debugging the core within
a system.
Preface: About This Guide
Conventions
Typographical
This document uses the following conventions. An example illustrates each convention.
The following typographical conventions are used in this document.
ConventionMeaning or UseExample
Messages, prompts, and
Courier font
Courier bold
Italic font
Dark Shading
program files that the system
displays
Literal commands you enter in
a syntactical statement
References to other manualsSee the User Guide for details.
Emphasis in text
Items that are not supported
or reserved
speed grade: - 100
ngdbuild
If a wire is drawn so that it
overlaps the pin of a symbol,
the two nets are not connected.
This feature is not supported
design_name
18www.xilinx.comEthernet 1000BASE-X PCS/PMA or SGMII v9.1
UG155 March 24, 2008
Conventions
ConventionMeaning or UseExample
An optional entry or
Square brackets [ ]
parameter. However, in bus
specifications, such as
ngdbuild [
design_name
bus[7:0], they are required.
option_name
R
]
Braces { }
Vertical bar |
Vertical ellipsis
Horizontal ellipsis . . .
Notations
Online Document
The following conventions are used in this document.
A list of items from which you
must choose one or more
Separates items in a list of
choices
lowpwr ={on|off}
lowpwr ={on|off}
IOB #1: Name = QOUT’
.
.
Repetitive material that has
been omitted
.
Repetitive material that has
been omitted
The prefix ‘0x’ or the suffix ‘h’
indicate hexadecimal notation
A ‘_n’ means the signal is
active low
IOB #2: Name = CLKIN’
.
.
.
allow block
block_name
loc1 loc2 ... locn;
A read of address
0x00112975 returned
45524943h.
usr_teof_n is active low.
ConventionMeaning or UseExample
See the section “Additional
Resources” for details.
See “Title Formats” in
Blue text
Cross-reference link to a
location in the current
document
Chapter 1 for details.
Blue, underlined text
Hyperlink to a website (URL)
Go to w
latest speed files.
ww.xilinx.com for the
Ethernet 1000BASE-X PCS/PMA or SGMII v9.1www.xilinx.com19
UG155 March 24, 2008
R
Preface: About This Guide
20www.xilinx.comEthernet 1000BASE-X PCS/PMA or SGMII v9.1
UG155 March 24, 2008
R
Introduction
The Ethernet 1000BASE-X PCS/PMA or SGMII core is a fully verified solution that
supports Verilog HDL and VHDL. In addition, the example design provided with the core
supports both Verilog and VHDL.
This chapter introduces the Ethernet 1000BASE-X PCS/PMA or SGMII core and provides
related information, including recommended design experience, additional resources,
technical support, and methods for submitting feedback to Xilinx.
About the Core
The Ethernet 1000BASE-X PCS/PMA or SGMII core is a Xilinx CORE Generator™IP core,
included in the latest IP Update on the Xilinx IP Center. For detailed information about the
core, see the Ethernet 100BASE-X PCS/PMA product page
requirements and licensing options, see Chapter 2, “Licensing the Core,” in the Getting
Started Guide.
Chapter 1
.For information about system
Designs Using RocketIO Transceivers
RocketIO transceivers are defined by device family in the following way:
•For Virtex-II Pro and Virtex-4 devices, RocketIO Multi-Gigabit Transceivers (MGT)
Although the Ethernet 1000BASE-X PCS/PMA or SGMII core is a fully-verified solution,
the challenge associated with implementing a complete design varies depending on the
configuration and functionality of the application. For best results, previous experience
building high-performance, pipelined FPGA designs using Xilinx implementation
software and User Constraint Files (UCF) is recommended.
Contact your local Xilinx representative for a closer review and estimation for your specific
requirements.
Ethernet 1000BASE-X PCS/PMA or SGMII v9.1www.xilinx.com21
UG155 March 24, 2008
R
Additional Core Resources
For detailed information and updates about the Ethernet 1000BASE-X PCS/PMA or
SGMII core, see the following documents, located on the Xilinx Ethernet 100BASE-X
PCS/PMA product page
•Ethernet 1000BASE-X PCS/PMA or SGMII Data Sheet
•Ethernet 1000BASE-X PCS/PMA or SGMII Getting Started Guide
After generating the core, the following documents are available in the document
directory:
•Ethernet 1000BASE-X PCS/PMA or SGMII Release Notes
•Ethernet 1000BASE-X PCS/PMA or SGMIIUser Guide
Related Xilinx Ethernet Products and Services
For information about all Xilinx Ethernet solutions, see
To obtain technical support specific to the Ethernet 1000BASE-X PCS/PMA or SGMII core,
visit www.s
using the Ethernet 1000BASE-X PCS/PMA or SGMII core.
Xilinx provides technical support for use of this product as described in the Ethernet
1000BASE-X PCS/PMA or SGMII User Guide and the Ethernet 1000BASE-X PCS/PMA or
SGMII Getting Started Guide. Xilinx cannot guarantee timing, functionality, or support of
this product for designs that do not follow these guidelines.
Feedback
Xilinx welcomes comments and suggestions about the Ethernet 1000BASE-X PCS/PMA or
SGMII core and the documentation supplied with the core.
Ethernet 1000BASE-X PCS/PMA or SGMII Core
For comments or suggestions about the core, please submit a WebCase from
www.s
upport.xilinx.com/. Questions are routed to a team of engineers with expertise
upport.xilinx.com/. Be sure to include the following information:
•Product name
•Core version number
•Explanation of your comments
22www.xilinx.comEthernet 1000BASE-X PCS/PMA or SGMII v9.1
UG155 March 24, 2008
Feedback
Document
For comments or suggestions about this document, please submit a WebCase from
www.support.xilinx.com/
. Be sure to include the following information:
•Document title
•Document number
•Page number(s) to which your comments refer
•Explanation of your comments
R
Ethernet 1000BASE-X PCS/PMA or SGMII v9.1www.xilinx.com23
UG155 March 24, 2008
R
Chapter 1: Introduction
24www.xilinx.comEthernet 1000BASE-X PCS/PMA or SGMII v9.1
UG155 March 24, 2008
R
Core Architecture
This chapter describes the architecture of the Ethernet 1000BASE-X PCS/PMA or SGMII
core, including all interfaces and major functional blocks.
System Overview
Ethernet 1000BASE-X PCS/PMA or SGMII Using A RocketIO Transceiver
The Ethernet 1000BASE-X PCS/PMA or SGMII core provides the functionality to
implement the 1000BASE-X PCS and PMA sub-layers or used to provide a GMII to SGMII
bridge when used with a RocketIO transceiver. RocketIO transceivers are defined in the
following way:
Chapter 2
•For Virtex-II Pro and Virtex-4 devices, RocketIO Multi-Gigabit Transceivers (MGT)
The core interfaces to a RocketIO transceiver, providing some of the PCS layer
functionality such as 8B/10B encoding/decoding, the PMA SERDES, and clock recovery.
Figure 2-1 illustrates the remaining PCS sublayer functionality, and also shows the major
functional blocks of the core.
Ethernet 1000BASE-X PCS/PMA or SGMII v9.1www.xilinx.com23
UG155 March 24, 2008
R
r
LogiCORE Ethernet 1000BASE-X PCS/PMA or SGMII Core
PCS Transmit Engine
Chapter 2: Core Architecture
GMII
to MAC
MDIO
Interface
GMII Block
Optional PCS
Management
Optional
Auto-Negotiation
PCS Receive Engine
and Synchronization
RocketIO I/F Block
RocketIO Transeiver
Figure 2-1:Functional Block Diagram Using RocketIO Transceiver
GMII Block
A client-side GMII is provided with the core, which can be used as an internal interface for
connection to an embedded Media Access Controller (MAC) or other custom logic.
Alternatively, the GMII may be routed to device IOBs to provide an external (off chip)
GMII.
PCS Transmit Engine
The PCS transmit engine converts the GMII data octets into a sequence of ordered sets by
implementing the state diagrams of IEEE 802.3 (figures 36-5 and 36-6). See Appendix D,
“1000BASE-X State Machines.”
To PMD
Sublaye
PCS Receive Engine and Synchronization
The synchronization process implements the state diagram of IEEE 802.3 (figure 36-9). The
PCS receive engine converts the sequence of ordered sets to GMII data octets by
implementing the state diagrams of IEEE 802.3 (figures 36-7a and 36-7b). See Appendix D,
“1000BASE-X State Machines.”
Optional Auto-Negotiation Block
IEEE 802.3 clause 37 describes the 1000BASE-X Auto-Negotiation function that allows a
device to advertise the modes of operation that it supports to a device at the remote end of
a link segment (link partner), and to detect corresponding operational modes that the link
partner may be advertising.
Auto-Negotiation is controlled and monitored through the PCS Management Registers.
See Chapter 10, “Auto-Negotiation.”
24www.xilinx.comEthernet 1000BASE-X PCS/PMA or SGMII v9.1
UG155 March 24, 2008
System Overview
Ethernet 1000BASE-X PCS/PMA or SGMII with Ten-Bit-Interface
R
Optional PCS Management Registers
Configuration and status of the core, including access to and from the optional AutoNegotiation function, uses the 1000BASE-X PCS Management Registers defined in IEEE
802.3 clause 37. These registers are accessed through the serial Management Data
Input/Output Interface (MDIO), defined in IEEE 802.3 clause 22, as if it were an externally
connected PHY.
The PCS Management Registers may be omitted from the core when the core is performing
the 1000BASE-X standard. In this situation, configuration and status of the core is made
possible with the use of an alternative configuration vector and a status signal.
When the core is performing the SGMII standard, the PCS Management Registers become
mandatory and information in the registers takes on a different interpretation. For more
information, see “Management Registers” in Chapter 9.
RocketIO Interface Block
The RocketIO Interface Block enables the core to connect to a Virtex-II Pro, Virtex-4, or
Virtex-5 FPGA RocketIO transceiver.
The Ethernet 1000BASE-X PCS/PMA or SGMII core, when used with the Ten-Bit Interface
(TBI), allows you to implement only the 1000BASE-X PCS sublayer.
LogiCORE Ethernet 1000BASE-X PCS/PMA or SGMII Core
8B/10B
Encoder
8B/10B
Decoder
RX
Elastic
Buffer
TBI
IOBs
TBI Block
to PMA
Sublayer
GMII
to MAC
MDIO
Interface
GMII Block
Optional PCS
Management
PCS Transmit Engine
Optional
Atuo-negotiation
PCS Receive Engine
and Synchronization
Figure 2-2:Functional Block Diagram with a Ten-Bit Interface
The optional TBI can be used in place of the RocketIO transceiver to provide a parallel
interface for connection to an external PMA SERDES device. In this implementation,
additional logic blocks are required to replace some of the RocketIO transceiver
functionality. These are shown in the surrounded by the dotted line box in Figure 2-2 and
are described in the following sections. The other blocks are described previously in this
document.
Ethernet 1000BASE-X PCS/PMA or SGMII v9.1www.xilinx.com25
UG155 March 24, 2008
R
8B/10B Encoder
8B10B encoding, as defined in IEEE 802.3 (Tables 36-1a to 36-1e and Table 36-2), is
implemented in a block SelectRAM™, configured as ROM, and used as a large look-up
table.
8B/10B Decoder
8B10B decoding, as defined in IEEE 802.3 (Table 36-1a to 36-1e and Table 36-2), is
implemented in a block SelectRAM, configured as ROM, and used as a large look-up table.
Receiver Elastic Buffer
The Receiver Elastic Buffer enables the 10-bit parallel TBI data, received from the PMA
sublayer synchronously to the TBI receiver clocks, to be transferred onto the cores internal
125 MHz clock domain. It is an asynchronous FIFO implemented in internal RAM. The
Receiver Elastic Buffer attempts to maintain a constant occupancy by inserting or
removing Idle sequences as necessary. This causes no corruption to the frames of data.
TBI Block
The core provides a TBI interface that should be routed to device IOBs to provide an offchip TBI.
Chapter 2: Core Architecture
Core Interfaces
All ports of the core are internal connections in FPGA fabric. An HDL example design
(delivered with the core) connects the core, where appropriate, to a RocketIO transceiver,
and/or add IBUFs, OBUFs, and IOB flip-flops to the external signals of the GMII and TBI.
IOBs are added to the remaining unconnected ports to take the example design through
the Xilinx implementation software.
All clock management logic is placed in this example design, allowing you more flexibility
in implementation (such as designs using multiple cores). This example design is provided
in both VHDL and Verilog. For more information, see the Ethernet 1000BASE-X PCS/PMA or SGMII Getting Started Guide.
Figure 2-3 shows the pinout for the Ethernet 1000BASE-X PCS/PMA or SGMII core using
a RocketIO transceiver with the optional PCS Management Registers. The signals shown in
the Auto-Negotiation box included only when the core includes the Auto-Negotiation
26www.xilinx.comEthernet 1000BASE-X PCS/PMA or SGMII v9.1
UG155 March 24, 2008
Core Interfaces
R
functionality. For more information, see Chapter 3, “Generating and Customizing the
Figure 2-4:Component Pinout Using RocketIO Transceiver
without PCS Management Registers
28www.xilinx.comEthernet 1000BASE-X PCS/PMA or SGMII v9.1
UG155 March 24, 2008
Core Interfaces
R
Figure 2-5 shows the pinout for the Ethernet 1000BASE-X PCS/PMA or SGMII core when
using the TBI with optional PCS Management Registers. The signals shown in the AutoNegotiation box are included only when the core includes the Auto-Negotiation
functionality (see Chapter 3, “Generating and Customizing the Core”).
).
GMII
MDIO
Auto_Negotiation
gmii_txd[7:0]
gmii_tx_en
gmii_tx_er
gmii_rxd[7:0]
gmii_rx_dv
gmii_rx_er
gmii_isolate
mdc
mdio_in
mdio_out
mdio_tri
phyad[4:0]
reset
gtx_clk
an_interrupt
link_timer_value[8:0]
Ten-Bit Interface (TBI)
tx_code_group[9:0]
loc_ref
ewrap
en_cdet
rx_code_group0[9:0]
rx_code_group1[9:0]
pma_rx_clk0
pma_rx_clk1
signal_detect
status_vector[4:0]
Figure 2-5:Component Pinout Using the Ten-Bit Interface
with PCS Management Registers
Ethernet 1000BASE-X PCS/PMA or SGMII v9.1www.xilinx.com29
UG155 March 24, 2008
R
Chapter 2: Core Architecture
Figure 2-6 shows the pinout for the Ethernet 1000BASE-X PCS/PMA or SGMII core when
using a TBI without the optional PCS Management Registers.
GMII
MDIO Replacement
configuration_vector[3:0]
gmii_txd[7:0]
gmii_tx_en
gmii_tx_er
gmii_rxd[7:0]
gmii_rx_dv
gmii_rx_er
gmii_isolate
reset
gtx_clk
Ten-Bit Interface (TBI)
tx_code_group[9:0]
loc_ref
ewrap
en_cdet
rx_code_group0[9:0]
rx_code_group1[9:0]
pma_rx_clk0
pma_rx_clk1
signal_detect
status_vector[4:0]
Figure 2-6:Component Pinout Using Ten-Bit Interface
without PCS Management Registers
30www.xilinx.comEthernet 1000BASE-X PCS/PMA or SGMII v9.1
UG155 March 24, 2008
Loading...
+ 200 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.