
MD400184/A
19
84221
The transmit SSD is generated by the 4B5B encoder and
the /J/K/ symbols are inserted by the 4B5B encoder at the
beginning of the transmit data packet in place of the first
two 5B symbols of the preamble, as shown in Figure 2.
The  receive pattern is detected by the 4B5B decoder by
examining groups of 10 consecutive code bits (two 5B
words) from the descrambler. Between packets, the
receiver will be detecting the idle pattern, which is 5B /I/
symbols. While in the idle state, CRS_DV is deasserted.
If the receiver is in the idle state and 10 consecutive code
bits from the receiver consist of the /J/K/ symbols, the start
of packet is detected, data reception is begun, CRS_DV  is
asserted, and /5/5/ symbols are substituted in place of the
/J/K/ symbols.
If the receiver is in the idle state and 10 consecutive code
bits from the receiver consist of a pattern that is neither /I/
I/ nor /J/K/ symbols but contains at least 2 non-contiguous
0's, then activity is detected but the start of packet is
considered to be faulty and a False Carrier Indication (also
referred to as bad SSD)  is signalled to the controller
interface.  When False Carrier is detected while CRS_DV
is asserted, RXD[1:0]=11, 10 for two di-bits while RXER is
asserted.  Once a False Carrier Event is detected, the idle
pattern (two /I/I/ symbols) must be detected before any
new SSD’s can be sensed.
If the receiver is in the idle state and 10 consecutive code
bits from the receiver consist of a pattern that is neither /I/
I/ nor /J/K/ symbols but does not contain at least 2 non
contiguous 0's, the data is ignored and the receiver stays
in the idle state.
2.11.2 10 Mbps
Since the idle period in 10 Mbps mode is defined to be no
data on the TP inputs, then the start of packet for 10 Mbps
mode is detected when valid data is detected by the TP
squelch circuit.  When start of packet is detected, CRS is
asserted as described in the Controller Interface Section.
Refer to the TP Squelch - 10 Mbps Section for the
algorithm for valid data detection.
2.12  END OF PACKET
2.12.1  100 Mbps
End of packet for 100 Mbps mode is indicated by  an End
of Stream Delimiter (referred to as ESD). The ESD pattern
consists of the two /T/R/ 4B5B symbols inserted after the
end of the packet, as defined in IEEE 802.3 Clause 24 and
shown in Table 2 and Figure 2.
The transmit ESD is generated by the 4B5B encoder and
the /T/R/ symbols are inserted by the 4B5B encoder after
the end of the transmit data packet, as shown in Figure 2.
The  receive ESD pattern is detected by the  4B5B
decoder by examining groups of 10 consecutive code bits
(two 5B words) from the descrambler during valid packet
reception to determine whether there is an ESD.
If the 10 consecutive code bits from the receiver during
valid packet reception consist of the /T/R/ symbols, the
end of packet is detected, data reception is terminated,
CRS_DV is deasserted, and /I/I/ symbols are substituted
in place of the /T/R/ symbols.
If 10 consecutive code bits from the receiver during valid
packet reception do not consist of /T/R/ symbols, but
consist of  /I/I/ symbols instead, the packet is considered
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_DV are
all deasserted.  
2.12.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.13 LINK INTEGRITY & AUTONEGOTIATION
2.13.1  General
The 84221 can be configured to implement either the
standard link integrity algorithms or the AutoNegotiation
algorithm.