DS537 Datasheet, PDF (93/148 Pages) Xilinx, Inc – LogiCORE IP XPS LL TEMAC

LogiCORE IP XPS LL TEMAC (v2.03a)
SGMII can carry Ethernet traffic at 10 Mb/S, 100 Mb/S, and 1 Gb/S.
The SGMII physical interface was defined by Cisco Systems. The data signals operate at a rate of 1.25 Gb/S.
Differential pairs are used to provide signal integrity and minimize noise. The sideband clock signals defined in the
specification are not implemented in the XPS_LL_TEMAC. Instead, the RocketIO MGT is used to transmit and
receive the differential data at the required rate using clock data recovery. For more information on SGMII, refer to
the Serial GMII Specification v1.7.
Please refer to UG368 Virtex-6 Embedded Tri-Mode Ethernet MAC User Guide for an equivalent diagram of the
clock management scheme when the XPS_LL_TEMAC parameter C_INCLUDE_IO = “1”. When the parameter
C_INCLUDE_IO = “0”, When the parameter C_INCLUDE_IO = “0”, MGTCLK_P connects directly to the Serial
Transceiver; hence the IBUFDS is not used.
Virtex 6 Hard TEMAC SGMII Constraints
Refer to Answer Record 32713 for constraint examples. Refer to UG625 for an overview of the various constraints
used.
SGMII Auto-Negotiation
The external SGMII capable PHY device performs auto negotiation with its link partner on the PHY Link (Ethernet
bus) resolving operational speed and duplex mode and then in turn performs a secondary auto negotiation with the
RocketIO transceiver across the SGMII Link. This transfers the results of the PHY with Link Partner auto
negotiation across the SGMII to the XPS_LL_TEMAC.
The results of the SGMII auto negotiation can be read from the SGMII Management Auto negotiation Link Partner
Ability Base Register (Table 79). The duplex mode and speed of the XPS_LL_TEMAC should then be set to match
(see TEMAC Receive Configuration Word 1 (RCW1) Registers, page 51, TEMAC Transmit Configuration (TC)
Registers, page 52, and TEMAC Ethernet MAC Mode Configuration (EMMC) Registers, page 54).
There are two methods that may be used to learn of the completion of an auto negotiation cycle:
By polling the auto negotiation complete bit of SGMII Management Status Register (Register 1, bit 5 Table 75).
By using the auto negotiation complete interrupt (Interrupt Status Registers (IS0 and IS1), page 29 and SGMII
Management Auto Negotiation Interrupt Control Register Table 84 on page 106.)
Loopback
There are two possible loopback positions:
• Loopback in the Hard TEMAC silicon component. When placed into loopback, data is routed from the
transmitter to the receiver path at the last possible point in the PCS/PMA sublayer. This is immediately before
the RocketIO transceiver interface. When placed into loopback, a constant stream of Idle code groups is
transmitted through the RocketIO transceiver. Loopback in this position allows test frames to be looped back
within the system without allowing them to be received by the link partner (the device connected on the other
end of the Ethernet. The transmission of Idles allows the link partner to remain in synchronization so that no
fault is reported.
• Loopback in the RocketIO transceiver. The RocketIO transceiver can be switched into loopback and will route
data from the transmitter path to the receiver path within the RocketIO transceiver. However, this data is also
transmitted out of the RocketIO transceiver and so any test frames used for a loopback test will be received by
the link partner.
www.xilinx.com
93