7 receive oversized frames register (rxoversized), 8 receive jabber frames register (rxjabber), 10 receive frame fragments register (rxfragments) – Texas Instruments TMS320TCI6486 User Manual

Page 150: Section 5.50.7, Section 5.50.8, Section 5.50.9, Section 5.50.10

Advertising
background image

EMAC Port Registers

www.ti.com

5.50.7

Receive Oversized Frames Register (RXOVERSIZED)

The total number of oversized frames received on the EMAC. An oversized 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 in bytes

Had no CRC error, alignment error, or code error

See

Section 2.5.5

for definitions of alignment, code/CRC errors. Overruns have no effect on this 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

for definitions of alignment, code, and CRC errors. Overruns have no effect on this

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

for definitions of alignment, code, and CRC errors. Overruns have no effect on this

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

for definitions of alignment, code, and CRC errors. Overruns have no effect on this

statistic.

150

C6472/TCI6486 EMAC/MDIO

SPRUEF8F – March 2006 – Revised November 2010

Submit Documentation Feedback

Copyright © 2006–2010, Texas Instruments Incorporated

Advertising