Xilinx LogiCORE 1000BASE-X User Manual page 175

Required Constraints
timing which is achieved after place-and-route is reported in the datasheet section of the
TRCE report (created by the implement script).
For customers fixing their own pinout, the setup and hold figures reported in the TRCE
report can be used to initially setup the approximate DCM phase shift.
"Calculating the DCM Fixed Phase Shift Value"
fixing the phase shift by using hardware measurement of a unique PCB design.
Virtex-4 devices
Figure 5-16
4 family. IODELAY elements are instantiated on the GMII data input path as illustrated:
the number of tap delays is currently set to zero. This can be modified in the UCF file, if
desired, to de-skew the bus for PCB routing.
A fixed tap delay is applied to delay the gmii_tx_clk clock so that it correctly samples
the GMII data at the IOB flip-flop, thereby meeting GMII setup and hold timing.
The tap delays are applied using the following UCF syntax.
The value of
example designs to meet the setup and hold constraints for the example GMII pinout in the
particular device. The setup/hold timing which is achieved after place-and-route is
reported in the datasheet section of the TRCE report (created by the implement script). See
"Understanding Timing Reports for Setup/Hold Timing."
Virtex-5 devices
Figure 5-17
5 family. IODELAY elements are instantiated on the GMII data input path as illustrated:
the number of tap delays is currently set to zero. This can be modified in the UCF file, if
desired, to de-skew the bus for PCB routing.
A fixed tap delay is applied to delay the gmii_tx_clk clock so that it correctly samples
the GMII data at the IOB flip-flop, thereby meeting GMII setup and hold timing.
The tap delays are applied using the following UCF syntax.
Ethernet 1000BASE-X PCS/PMA or SGMII v9.1
UG155 March 24, 2008
illustrates the GMII input logic provided by the example design for the Virtex-
#-----------------------------------------------------------
# To Adjust GMII Tx Input Setup/Hold Timing
#-----------------------------------------------------------
INST "delay_gmii_tx_en"
INST "delay_gmii_tx_er"
INST "gmii_data_bus[7].delay_gmii_txd"
INST "gmii_data_bus[6].delay_gmii_txd"
INST "gmii_data_bus[5].delay_gmii_txd"
INST "gmii_data_bus[4].delay_gmii_txd"
INST "gmii_data_bus[3].delay_gmii_txd"
INST "gmii_data_bus[2].delay_gmii_txd"
INST "gmii_data_bus[1].delay_gmii_txd"
INST "gmii_data_bus[0].delay_gmii_txd"
IOBDELAY_VALUE
illustrates the GMII input logic provided by the example design for the Virtex-
#-----------------------------------------------------------
# To Adjust GMII Tx Input Setup/Hold Timing
#-----------------------------------------------------------
INST "delay_gmii_tx_en"
INST "delay_gmii_tx_er"
INST "gmii_data_bus[7].delay_gmii_txd"
www.xilinx.com
describes a more accurate method for
IOBDELAY_VALUE = "53";
IOBDELAY_VALUE = "53";
IOBDELAY_VALUE = "53";
IOBDELAY_VALUE = "53";
IOBDELAY_VALUE = "53";
IOBDELAY_VALUE = "53";
IOBDELAY_VALUE = "53";
IOBDELAY_VALUE = "53";
IOBDELAY_VALUE = "53";
IOBDELAY_VALUE = "53";
for the gmii_tx_clk clock is preconfigured in the
IDELAY_VALUE = "33";
IDELAY_VALUE = "33";
IDELAY_VALUE = "33";
R
Appendix C,
-
-
175