
MD400177/B
84220
25
to have been terminated prematurely and abnormally.
When this premature end of packet condition is detected,
RXER remains asserted for the nibble associated with the
first /I/ symbol detected and then RXER and CRS and
RXDV are all deasserted.  Premature end of packet
condition is also indicated by setting the ESD error bit in
the MI serial port Channel Status Output register. 
2.13.2  10 Mbps
The end of packet for 10 Mbps mode is indicated  with the
SOI (Start of Idle) pulse.  The SOI pulse is a positive
double wide pulse containing a Manchester code violation
inserted at the end of every packet.
The transmit SOI pulse is generated by the TP  transmitter
and inserted  at the end of the data packet after TXEN is
deasserted.  The transmitted SOI output pulse at the TP
output is shaped by the transmit waveshaper to meet the
pulse template requirements specified in  IEEE 802.3
Clause 14 and shown in Figure 6.
The receive SOI pulse is detected by the TP receiver  by
sensing missing data transitions.  Once the SOI pulse is
detected, data reception is ended and CRS and RXDV are
deasserted.
2.14 LINK INTEGRITY & AUTONEGOTIATION
2.14.1  General
The 84220 can be configured to implement either the
standard link integrity algorithms or the AutoNegotiation
algorithm.
The standard link integrity algorithms are used solely to
establish an active link to and from a remote device.
There are different standard link integrity algorithms for 10
and 100 Mbps modes.  The AutoNegotiation algorithm is
used for two purposes:
 To automatically configure the device for either 10/100 
Mbps and Half/Full Duplex modes
 Establish an active link to and from a remote device
The standard link integrity and AutoNegotiation algorithms
are described below.
2.14.2  10Base-T Link Integrity Algorithm
The 84220 uses the same 10Base-T link integrity
algorithm that is defined in IEEE 802.3 clause 14.  This
algorithm uses normal link pulses, referred to as NLP’s
and transmitted during idle periods, to determine if a
device has successfully established a link with a remote
device (called Link Pass state).  The transmit link pulse
meets the template defined in IEEE 802.3 Clause 14 and
shown in Figure 7.  Refer to IEEE 802.3 Clause 14 for
more details if needed. 
2.14.3  100Base-TX Link Integrity Algorithm
Since 100Base-TX is defined to have an active idle signal,
then there is no need to have separate link pulses like
those defined for 10Base-T  The 84220 uses the squelch
criteria and descrambler synchronization algorithm on the
input data to determine if the device has successfully
established a link with a remote device (called Link Pass
state).  Refer to IEEE 802.3 for details on both algorithms.
2.14.4  AutoNegotiation Algorithm
As stated previously, the AutoNegotiation algorithm is
used for two purposes:
 To automatically configure the device for either 10/100 
Mbps and Half/Full Duplex modes
 To establish an active link to and from a remote device
The AutoNegotiation algorithm is the same algorithm that
is defined in IEEE 802.3 Clause 28.  AutoNegotiation uses
a burst of link pulses, called fast link pulses and referred to
as FLP’s, to pass up to 16 bits of signaling back and forth
between the 84220 and a remote device.  The transmit
FLP pulses meet the template specified in IEEE 802.3
and shown in Figure 7.  A timing diagram contrasting
NLP’s and FLP’s is shown in Figure 8.
The AutoNegotiation algorithm is initiated by any of the
following events:
 Powerup
 Device Reset
 AutoNegotiation Reset
 Entering the Link Fail state
Once a negotiation has been initiated, the 84220 first
determines if the remote device has AutoNegotiation
capability.  If the device is not AutoNegotiation capable
and is just transmitting either a 10Base-T or 100Base-TX
signal, the 84220 will sense that and place itself in the
correct mode.  If the 84220 detects FLP’s from the remote
device, then the remote device is determined to have
AutoNegotiation capability and  the device then uses the
contents 
of 
the 
MI 
serial 
Advertisement register and FLP’s to advertise it’s
capabilies to a remote device.  The remote device does
the same, and the capabilities read back from the remote
device are stored in the MI serial port AutoNegotiation
Remote End Capability register.  The 84220 negotiation
algorithm then matches it’s capabilities to the remote
devices capabilities and determines to what mode the
port 
AutoNegotiation