Texas Instruments TMS320DM646x User Manual page 126

Ethernet Media Access Controller (EMAC) Registers
See Section 2.5.5
statistic.
5.50.8 Receive Jabber Frames Register (RXJABBER)
The total number of jabber frames received on the EMAC. A jabber frame is defined as having all of the
following:
Was any data or MAC control frame that matched a unicast, broadcast, or multicast address, or
matched due to promiscuous mode
Was greater than RXMAXLEN bytes long
Had a CRC error, alignment error, or code error
See Section 2.5.5
statistic.
5.50.9 Receive Undersized Frames Register (RXUNDERSIZED)
The total number of undersized frames received on the EMAC. An undersized frame is defined as
having all of the following:
Was any data frame that matched a unicast, broadcast, or multicast address, or matched due to
promiscuous mode
Was less than 64 bytes long
Had no CRC error, alignment error, or code error
See Section 2.5.5
statistic.
5.50.10 Receive Frame Fragments Register (RXFRAGMENTS)
The total number of frame fragments received on the EMAC. A frame fragment is defined as having all
of the following:
Any data frame (address matching does not matter)
Was less than 64 bytes long
Had a CRC error, alignment error, or code error
Was not the result of a collision caused by half duplex, collision based flow control
See Section 2.5.5
statistic.
5.50.11 Filtered Receive Frames Register (RXFILTERED)
The total number of frames received on the EMAC that the EMAC address matching process indicated
should be discarded. Such a frame is defined as having all of the following:
Was any data frame (not MAC control frame) destined for any unicast, broadcast, or multicast
address
Did not experience any CRC error, alignment error, code error
The address matching process decided that the frame should be discarded (filtered) because it did
not match the unicast, broadcast, or multicast address, and it did not match due to promiscuous
mode.
126 Ethernet Media Access Controller (EMAC)/Management Data Input/Output (MDIO)
for definitions of alignment, code, and CRC errors. Overruns have no effect on this
for definitions of alignment, code, and CRC errors. Overruns have no effect on this
for definitions of alignment, code, and CRC errors. Overruns have no effect on this
for definitions of alignment, code, and CRC errors. Overruns have no effect on this
www.ti.com
SPRUEQ6 – December 2007
Submit Documentation Feedback