
Agere Systems Inc.
127
Data Sheet
July 2001
T8302 Internet Protocol Telephone
Advanced RISC Machine (
ARM
)
11 10/100 2-Port Repeater and Backplane Segment Controller
(continued)
11.3.3 Collisions
In the transmit collision state, the repeater sends JAM. Transmit collision is entered because two or more ports on
the repeater slice are active at the same time. The repeater slice enters transmit collision state when collision is
asserted from the backplane. It is the responsibility of the external switch matrix to determine if two or more
repeater slice ports on a segment are active and drive the collision signal. The receive collision state is entered
due to a remote collision outside the repeater slice in question, causing a signal quality error (SQE) at the repeater
slice without any other ports being active. In other words, the repeater slice has only one port active and it is
receiving the
COL
from the PHY.
11.3.4 Partition and Isolate
The repeater slice has been designed to conform to the
IEEE
802.3 standard in terms of when a port is isolated or
partitioned. The device also has two optional features that may be used to enhance the basic functionality. These
features are isolated due to speed mismatch and unpartition on link invalid.
11.3.4.1 Partitioning
In both 10 Mbits/s and 100 Mbits/s modes, the partitioning will occur when 64 consecutive collisions have
occurred.
Note:
The repeater slice will not
count late collisions as consecutive collisions. In 10 Mbits/s mode, Tw6 is
1050—1125 bit times in duration. If a collision lasts longer than the Tw6 timer, the port will be partitioned in
10 Mbits/s mode. Once partitioned, the port will not pass data onto the backplane. The port will continue to
transmit data it sees on the backplane. Tw6 is not implemented for 100 Mbits/s.
A port will unpartition when a packet has been received or transmitted from the port for Tw5 = 512 bit times without
colliding. The partitioning state machine will be reset when the
DAP
bit in the
port configuration register
0
(see
Table 117 on page 136)
is set to 1.
11.3.4.2 MAU Jabber Lockup Protection (MJLP)
In 10 Mbits/s mode only, the repeater will interrupt an excessively long input by putting silence onto the backplane
for a short duration. The length of the excessive input must exceed the Tw3 timer value of 4 ms—7.5 ms for the
silence to be inserted. The silence is inserted for Tw4 = 97 bit times and the backplane is again driven if the exces-
sively long packet is still present. The cycle is repeated until the receive event stops.
For example, if a packet lasts for 25 ms, a single MJLP will be tallied in the event counter, but the backplane will
have three idle periods of Tw4 bit times inserted into the data.
The repeater slice does not implement MJLP from the backplane to the PHY interface. It is the responsibility of the
PHY to implement a watchdog timer (jabber timer) in the transmit direction.
11.3.4.3 Receive Jabber
MJLP is not implemented for 100 Mbits/s mode. Instead, the 100 Mbits/s mode implements a receive jabber (such
as the repeater slice device has implemented). The receive jabber handles an excessively long receive event by
simply cutting off the output to the backplane after 0.4 ms—0.75 ms. The repeater continues to keep the backplane
output for that port silent until the input has gone silent (
CRS
=
RX_DV
= 0) at which time it will again allow a new
receive event to pass on to the backplane.
Note:
The port does not repeat transmit data from the backplane when the receive jabber becomes active.