4 stopping and starting the receiver, 5 receiver errors, Stopping and starting the receiver – SMSC LAN9312 User Manual
Page 136: Receiver errors, Section 9.9.4, "stopping and starting the receiver, Datasheet 9.9.4 stopping and starting the receiver
High Performance Two Port 10/100 Managed Ethernet Switch with 32-Bit Non-PCI CPU Interface
Datasheet
Revision 1.4 (08-19-08)
136
SMSC LAN9312
DATASHEET
9.9.4
Stopping and Starting the Receiver
To stop the receiver, the host must clear the RXEN bit in the
Host MAC Control Register (HMAC_CR)
When the receiver is halted, the RXSTOP_INT will be pulsed and reflected in the
. Once stopped, the host can optionally clear the RX Status and RX Data FIFOs.
The host must re-enable the receiver by setting the RXEN bit.
9.9.5
Receiver Errors
If the Receiver Error (RXE) flag is asserted in the
Interrupt Status Register (INT_STS)
for any reason,
the receiver will continue operation. RX Error (RXE) will be asserted under the following conditions:
A host underrun of RX Data FIFO
A host underrun of the RX Status FIFO
An overrun of the RX Status FIFO
It is the duty of the host to identify and resolve any error conditions.
7
Frame Too Long.
When set, this bit indicates that the frame length exceeds the maximum Ethernet
specification of 1518 bytes. This is only a frame too long indication and will not cause the frame
reception to be truncated.
6
Collision Seen.
When set, this bit indicates that the frame has seen a collision after the collision
window. This indicates that a late collision has occurred.
5
Frame Type.
When set, this bit indicates that the frame is an Ethernet-type frame (Length/Type field
in the frame is greater than 1500). When reset, it indicates the incoming frame was an 802.3 type
frame. This bit is not set for Runt frames less than 14 bytes.
4
Receive Watchdog time-out.
When set, this bit indicates that the incoming frame is greater than
2048 bytes through 2560 bytes, therefore expiring the Receive Watchdog Timer.
3
MII Error.
When set, this bit indicates that a receive error was detected during frame reception.
2
Dribbling Bit.
When set, this bit indicates that the frame contained a non-integer multiple of 8 bits.
This error is reported only if the number of dribbling bits in the last byte is at least 3 in the 10 Mbps
operating mode. This bit will not be set when the collision seen bit[6] is set. If set and the CRC error
bit is [1] reset, then the packet is considered to be valid.
1
CRC Error.
When set, this bit indicates that a CRC error was detected. This bit is also set when the
RX_ER pin is asserted during the reception of a frame even though the CRC may be correct. This bit
is not valid if the received frame is a Runt frame, or a late collision was detected or when the
Watchdog Time-out occurs.
0
Reserved.
These bits are reserved. Reads 0
BITS
DESCRIPTION