
W89C880F FastMPR
Publication Release Date: January 1997
- 11 -
Revision A1
MII Data Error Handling
If a receive error occurs while the PHY controller is receiving data, the controller will issue a receive
error signal RXER to the FastMPR. The FastMPR will then repeat the data stream to all other ports
after a short delay. The FastMPR will also assert TXER at the location RXER to indicate that there is
a receive error at this location.
Frame
RXER
T
Frame
TXER
T
Figure 5
In the figure shown above, the upper timing diagram represents the receiving port, and the lower
diagram is a repeated frame with some hub latency. These two timing diagrams are similar and keep
the same T latency between the SFD (start of frame delimiter) and error signal (RXER, TXER).
MII Port Collision and Jam Generation
The FastMPR also monitors the input signals CRS0
10. If more than one carrier appears at the
same time, the FastMPR will issue a jamming pattern to all its output ports, while reporting the
collision status to the direct report pin XCOLRPT. After the collision has been detected, the FastMPR
will immediately append the jamming pattern to all the connected ports until all network nodes stop
transmitting data frames, only one node is active, or a power-on reset occurs. Figure 6 shows how the
FastMPR enters and leaves the collision state.
Auto Partition/Reconnection
The FastMPR implements an auto partition/reconnection function to protect the network from failure
caused by consecutive collisions from a specific port on the FastMPR. Each port on the FastMPR
implements an independent auto partition/reconnection state function. The port will automatically
partition itself when 64 or more consecutive collisions occur on the same port (the IEEE802.3
standard is greater than 60). A port will automatically recover to its active state after either
successfully transmitting more than 512 bits of data continuously without collision on the same port
(IEEE802.3 defines this figure to be between 450 and 560 bits) or after a power-on reset.
When a port is partitioned, the FastMPR does not allow any input messages to pass from the port, but
can accept output messages from the hub internal to the partitioned port.