R
Client-Supplied FCS Passing
The transmission timing depicted in
the FCS field passed in by the client. In this case, it is the responsibility of the client to
ensure that the frame meets the Ethernet minimum frame length requirements as the
GEMAC core will not perform any padding of the payload. See
on page
tx_data_valid
tx_underrun
Client Underrun
Figure 5-8
FIFO connected to the client interface that empties before a frame transfer is complete.
When the client asserts tx_underrun during a frame transmission, the GEMAC core
inserts an error code to corrupt the current frame, and then falls back to idle transmission.
It is the responsibility of the client to re-queue the aborted frame for transmission.
When an underrun occurs, tx_data_valid may be asserted on the clock cycle after the
tx_underrun assertion to request a new transmission.
48
-- DISCONTINUED PRODUCT --
78.
gtx_clk
tx_data[7:0]
DA
tx_ack
Figure 5-7: Frame Transmission with Client-supplied FCS
illustrates the timing of an aborted transfer. An example of this situation is a
gtx_clk
tx_data[7:0]
tx_data_valid
tx_ack
tx_underrun
Figure 5-8: Frame Transmission with Underrun
www.xilinx.com
Chapter 5: Using the Client Side Data Path
Figure 5-7
shows the GEMAC core configured to have
SA
L/T
DA
SA
L/T
1-Gigabit Ethernet MAC v8.5 User Guide
"Configuration Registers,"
DATA
FCS
DATA
UG144 April 24, 2009