Table of Contents
Advertisement
Chapter 3: Client, Host, and MDIO Interfaces
•
Client-Supplied FCS Passing
Figure 3-20
the FCS field to the client (see
padding inserted into the frame to meet Ethernet minimum frame length specifications is
left intact and passed to the client.
Even though the FCS is passed up to the client, it is also verified by the Ethernet MAC, and
EMAC#CLIENTRXBADFRAME is asserted if the FCS check fails.
www.BDTIC.com/XILINX
54
•
VLAN frames of length 1519 to 1522 are received when VLAN frames are not
enabled.
•
Jumbo frames are received when jumbo frames are not enabled.
•
A value of 0x0000 to 0x002D is in the type/length field. In this situation, the
frame should be padded to the minimum length. If not padded to exactly the
minimum frame length, the frame is marked as bad (when length/type checking
is enabled).
•
A value of 0x002E to 0x0600 is in the type/length field, but the real length of the
received frame does not match this value (when length/type checking is
enabled).
•
Any control frame that is received is not exactly the minimum frame length
(64 bytes).
•
PHYEMAC#RXER is asserted at any point during frame reception.
•
An error code is received in the 1-Gb frame extension field.
•
A valid pause frame, addressed to the Ethernet MAC, is received when flow
control is enabled.
Refer to
"Flow Control Block," page 61
1000BASE-X/SGMII Specific Conditions:
When in 1000BASE-X or SGMII mode, these errors can also cause a frame to be marked
as bad:
•
Unrecognized 8B/10B code group received during the packet.
•
8B/10B running disparity errors occurred during the packet.
•
Unexpected K characters or sequences appeared in the wrong order/byte
position.
shows the handling of the case where the Ethernet MAC is configured to pass
www.xilinx.com
for more information.
"Configuration Registers," page
Embedded Tri-Mode Ethernet MAC User Guide
74). In this case, any
UG074 (v2.2) February 22, 2010
R
Advertisement
Table of Contents
