![Xilinx Virtex-4 RocketIO Скачать руководство пользователя страница 56](http://html1.mh-extra.com/html/xilinx/virtex-4-rocketio/virtex-4-rocketio_user-manual_3383739056.webp)
56
Embedded Tri-Mode Ethernet MAC User Guide
UG074 (v2.2) February 22, 2010
Chapter 3:
Client, Host, and MDIO Interfaces
R
Length/Type Field Error Checks
Length/Type Field Error checking is specified in IEEE Std 802.3. The Length/Type Field
Error checks consist of comparing the value in the Length/Type field with the actual size of
the data field received. This check is only performed when the value in the Length/Type
field is less than 1536 (
0x600
). This check does
not
perform any checks on the total length
of the frame. This functionality must be enabled to comply with this specification.
Disabling Length/Type checking is intended only for specific applications, such as when
using over a proprietary backplane.
Enabled
When Length/Type error checking is enabled (see
“Receiver Configuration Register (Word
), the following checks are made on frames with a value less than 1536 (
0x600
)
in the Length/Type field. (If either of these checks fails, EMAC#CLIENTRXBADFRAME is
asserted):
•
A value greater than or equal to decimal 46 but less than decimal 1536 (a length
interpretation) in the Length/Type field is checked against the actual data length
received.
•
A value less than decimal 46 in the Length/Type field is checked to ensure the data
field is padded to exactly 46 bytes.
Furthermore, if padding is indicated (the Length/Type field is less than decimal 46) and
client-supplied FCS passing is disabled, then the length value in the Length/Type field is
used to deassert EMAC#CLIENTRXDVLD after the indicated number of data bytes,
removing the padding bytes from the frame.
Disabled
When the Length/Type error checking is disabled (see
“Receiver Configuration Register
), the Length/Type error checks described above are not performed. A
frame containing only these errors causes EMAC#CLIENTRXGOODFRAME to be
asserted. Disabling this check does
not
disable total frame length checks. Any frame of less
than 64 total bytes (minimum frame size) or any frame exceeding the maximum frame size
checks (if enabled) will still cause EMAC#CLIENTRXBADFRAME to be asserted. Control
frames will still be marked bad if they are not exactly 64 bytes in total length.
Furthermore, if padding is indicated and client-supplied FCS passing is disabled, then a
length value in the Length/Type field is not used to deassert EMAC#CLIENTRXDVLD.
Instead EMAC#CLIENTRXDVLD is deasserted before the start of the FCS field; in this
way, any padding is not removed from the frame.
Receive (RX) Client – 16-bit Wide Interface
This optional configuration can only be used when the Ethernet MAC is configured in
1000BASE-X PCS/PMA mode. The frequency of the receive client clock is half the
frequency of the internal receive clock. The 16-bit client interface allows the Ethernet MAC
to run at an internal clock frequency of greater than 125 MHz. The interface allows the
Ethernet MAC to run at a line rate greater than 1 Gb/s as specified in IEEE Std 802.3.
Therefore, the interface should not be used for Ethernet compliant applications, but it can
be useful for customer’s backplane applications.
The PHYEMAC#RXCLK is used as the input clock port for the
CLIENTEMAC#RXCLIENTCLKOUT divided by two, as shown in the receive client block
diagram in
. Using a DCM with the receive client clock,
www.BDTIC.com/XILINX