Functional Description
•
Any data or MAC control frame which matched a unicast, broadcast or multicast address, or matched
due to promiscuous mode
•
Any length (including less than 64 bytes and greater than rx_maxlen bytes)
•
The CPDMA had a start of frame overrun or the packet was dropped due to FIFO resource limitations
14.3.2.20.1.12 Rx Middle of Frame Overruns (Offset = 88h)
The total number of frames received on the port that had a CPDMA middle of frame (MOF) overrun. MOF
overrun frame is defined to be:
•
Any data or MAC control frame which matched a unicast, broadcast or multicast address, or matched
due to promiscuous mode
•
Any length (including less than 64 bytes and greater than rx_maxlen bytes)
•
The CPDMA had a middle of frame overrun
14.3.2.20.1.13 Rx DMA Overruns (Offset = 8Ch)
The total number of frames received on the port that had either a DMA start of frame (SOF) overrun or a
DMA MOF overrun. An Rx DMA overrun frame is defined to be:
•
Any data or MAC control frame which matched a unicast, broadcast or multicast address, or matched
due to promiscuous mode
•
Any length (including less than 64 bytes and greater than rx_maxlen bytes)
•
The CPGMAC_SL was unable to receive it because it did not have the DMA buffer resources to
receive it (zero head descriptor pointer at the start or during the middle of the frame reception)
CRC errors, alignment errors and code errors have no effect upon this statistic.
14.3.2.20.1.14 Rx Octets (Offset = 30h)
The total number of bytes in all good frames received on the port. A good frame is defined to be:
•
Any data or MAC control frame which matched a unicast, broadcast or multicast address, or matched
due to promiscuous mode
•
Of length 64 to rx_maxlen bytes inclusive
•
Had no CRC error, alignment error or code error
See the Rx Align/Code Errors and Rx CRC errors statistic descriptions for definitions of alignment, code
and CRC errors. Overruns have no effect upon this statistic.
14.3.2.20.1.15 Net Octets (Offset = 80h)
The total number of bytes of frame data received and transmitted on the port. Each frame counted:
•
was any data or MAC control frame destined for any unicast, broadcast or multicast address (address
match does not matter)
•
Any length (including less than 64 bytes and greater than rx_maxlen bytes)
Also counted in this statistic is:
•
Every byte transmitted before a carrier-loss was experienced
•
Every byte transmitted before each collision was experienced, (i.e. multiple retries are counted each
time)
•
Every byte received if the port is in half-duplex mode until a jam sequence was transmitted to initiate
flow control. (The jam sequence was not counted to prevent double-counting)
Error conditions such as alignment errors, CRC errors, code errors, overruns and underruns do not affect
the recording of bytes by this statistic.
The objective of this statistic is to give a reasonable indication of ethernet utilization
1214
Ethernet Subsystem
SPRUH73H – October 2011 – Revised April 2013
Copyright © 2011–2013, Texas Instruments Incorporated