Xilinx UG194 Virtex-5 FPGA Embedded Tri-Mode Ethernet MAC ...
Xilinx UG194 Virtex-5 FPGA Embedded Tri-Mode Ethernet MAC ...
Xilinx UG194 Virtex-5 FPGA Embedded Tri-Mode Ethernet MAC ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
R<br />
Normal Frame Transmission<br />
CLIENTE<strong>MAC</strong>#TXCLIENTCLKIN<br />
CLIENTE<strong>MAC</strong>#TXD[7:0]<br />
CLIENTE<strong>MAC</strong>#TXDVLD<br />
E<strong>MAC</strong>#CLIENTTXACK<br />
CLIENTE<strong>MAC</strong>#TXUNDERRUN<br />
E<strong>MAC</strong>#CLIENTTXCOLLISION<br />
E<strong>MAC</strong>#CLIENTTXRETRANSMIT<br />
Transmit (TX) Client: 8-Bit Interface (without Clock Enables)<br />
The timing of a normal outbound frame transfer is shown in Figure 3-1. When the client<br />
transmits a frame, the first column of data is placed on the CLIENTE<strong>MAC</strong>#TXD[7:0] port,<br />
and CLIENTE<strong>MAC</strong>#TXDVLD is asserted High. After the <strong>Ethernet</strong> <strong>MAC</strong> reads the first byte of<br />
data, it asserts the E<strong>MAC</strong>#CLIENTTXACK signal. On subsequent rising clock edges, the client<br />
must provide the rest of the frame data. CLIENTE<strong>MAC</strong>#TXDVLD is deasserted Low to signal<br />
an end-of-frame to the <strong>Ethernet</strong> <strong>MAC</strong>.<br />
In-Band Parameter Encoding<br />
Padding<br />
Figure 3-1: Normal Frame Transmission Across Client Interface<br />
The <strong>Ethernet</strong> <strong>MAC</strong> frame parameters, destination address, source address, length/type,<br />
and the FCS are encoded within the same data stream used to transfer the frame payload<br />
instead of separate ports. This provides the maximum flexibility in switching applications.<br />
The preamble, and optionally the FCS, are added to the frame by the <strong>Ethernet</strong> <strong>MAC</strong>.<br />
When fewer than 46 bytes of data are supplied by the client to the <strong>Ethernet</strong> <strong>MAC</strong>, the<br />
transmitter module adds padding – up to the minimum frame length. However, if the<br />
<strong>Ethernet</strong> <strong>MAC</strong> is configured for client-passed FCS, the client must also supply the padding<br />
to maintain the minimum frame length (see “Client-Supplied FCS Passing,” page 53).<br />
Client-Supplied FCS Passing<br />
DA SA L/T<br />
DATA<br />
<strong>UG194</strong>_3_01_072206<br />
In the transmission timing case shown in Figure 3-2, an <strong>Ethernet</strong> <strong>MAC</strong> is configured to<br />
have the FCS field passed in by the client (see “Configuration Registers,” page 88). The<br />
client must ensure that the frame meets the <strong>Ethernet</strong> minimum frame length requirements.<br />
If the frame does not meet these requirements, the <strong>Ethernet</strong> <strong>MAC</strong> pads the frame to the<br />
minimum frame length. Although this does not cause the transmitter statistics vector to<br />
indicate a bad frame, it will result in an errored frame as received by the link partner<br />
<strong>Ethernet</strong> <strong>MAC</strong>.<br />
TE<strong>MAC</strong> User Guide www.xilinx.com 53<br />
<strong>UG194</strong> (v1.10) February 14, 2011