• Extensive configuration via 802.3-compliant MDC/MDIO
serial interface
• 8bit/10bit Encoding/Decoding per channel with selectable
parallel input/output data sizes
- Support optional 8b/10b encoder/decoder bypass
operation
• Integrated Equalization and Pre-emphasis
• De-skewing and channel-to-channel alignment options
• Low power, 250mW per channel typical
• Meets jitter requirements with significant margin
• Comma detection and synchronization, byte alignment
• Tx/Rx rate matching via IDLE insertion/deletion
FN7481.1
• Receive signal detect and 16 levels of transmission
medium equalization
• CML transmit outputs with four levels of pre-emphasis
• Loopback
- Per-channel serial Tx-to-Rx and Rx-to-Tx parallel
internal loopback modes
• Single-ended/differential input Reference clock
• Double Data-Rate (DDR) mode, also optional SDR (Single
Data Rate) on transmitter
• Support both source-centered and source-simultaneous
clocking
• Long Run Length (512 bit) frequency lock ideal for
proprietary encoding schemes Transmit byte clock
schemes
- One Transmit Byte Clock (TBC) for each channel, or
one TBC for all four channels
• Received clock schemes
- Receive data aligned to local reference clock, to
recovered clock for each channel, or to recovered clock
for Channel A only
• Supports Built-In Self Test (BIST) and IEEE 1149.1 JTAG
• On-chip 25Ω series output terminations (XGMII side)
• Standard 0.18µm 1.8V CMOS technology
• 3.3V tolerant I/O
Switch
Fabric
Switch Card
nPower BBT 3420
Transceiver
nPower BBT 3420
Transceiver
Interface
nPower BBT 3420
Transceiver
nPower BBT 3420
Transceiver
CAUTION: These devices are sensitive to electrostatic discharge; follow proper IC Handling Procedures.
1-888-INTERSIL or 1-888-468-3774
XGMII
XGMII
XAUI
Up to 40"
Backplane
XAUI
Up to 40"
FIGURE 1-1. EXAMPLE BACKPLANE AND LINE CARD APPLICATIONS
1
Serial 10 Gigabit
10GBASE-R
Custom ASIC
&
MAC Functions
WDM 10 Gigabit
10GBASE-LX4
Custom ASIC
&
MAC Functions
| Intersil (and design) is a registered trademark of Intersil Americas Inc.
All other trademarks mentioned are the property of their respective owners.
nPower BBT 3420
XGMII
XGMII
Copyright Intersil Americas Inc. 2004, 2005. All Rights Reserved
Transceiver
nPower BBT 3420
Transceiver
XAUI
XAUI
XAUI
XAUI
Optical
Transponder
WDM
Optical
Transponder
TDI
www.BDTIC.com/Intersil
TDO
BBT3420
MDIO
TRSTN
TMS
TCLK
MF[A:D]
RSTN
LPEN[A:D]
BISTEN
RSVN/
RETIMER
PADR[4:0]
MDC
RFCP
RFCN
TXAP
TXAN
RXAP
RXAN
TXBP
TXBN
RXBP
RXBN
JTAG
TAP
20X or 10X
Transmit Clock
Generator
HS_TX_CLK
REF_CLKTDA[9:0]
TX+
TX-
RX+
RX-
RFCN
SIGDET
HS_TX_CLK
REF_CLK
TX+
TX-
RX+
RX-
RFCN
SIGDET
MDIO Register File & Common Logic
SSTL or HSTL
Input
Reference
TD[9:0]
Channel A
Channel B
RD[9:0]
CODE
TD[9:0]
RD[9:0]
CODE
TBC
RBC
TBC
RBC
MDIO Protocol
Engine
Internal
Nodes
REFP(N.C.)
REFN(N.C.)
RREF(N.C.)
VREF
TCA
RDA[9:0]
RCA
TDB[9:0]
TCB
RDB[9:0]
RCB
TXCP
TXCN
RXCP
RXCN
TXDP
TXDN
RXDP
RXDN
SIG_DET
SIGNAL
DETECT
LOGIC
HS_TX_CLK
REF_CLK
TX+
TX-
RX+
RX-
RFCN
SIGDET
HS_TX_CLK
REF_CLK
TX+
TX-
RX+
RX-
RFCN
SIGDET
Channel C
Channel D
TD[9:0]
RD[9:0]
CODE
TD[9:0]
RD[9:0]
CODE
FIGURE 1-2. BBT3420 BLOCK DIAGRAM
TBC
RBC
TBC
RBC
TDC[9:0]
TCC
RDC[9:0]
RCC
TDD[9:0]
TCD
RDD[9:0]
RCD
PSYNC
CODE
2
HS_TX_CLK
www.BDTIC.com/Intersil
TX+
TX-
Pre-empahsis
Serializer
8B/10B
Encoder
&
AKR
Generator
BBT3420
TX FIFO
&
Error and
Orderset
Detector
BIST
Pattern
Generator
DDR
Input
Registers
CODE
BISTEN
PLP
TD[9:0]
TBC
Clock and
Data
Recovery
Deserializer &
RX+
RX-
SIGDET
SLP
REF_CLK
100 Ohm
Termination,
Equalizer,
Signal
Detect
FIGURE 1-3. FUNCTIONAL BLOCK DIAGRAM OF A SINGLE CHANNEL
2 General Description
The BBT3420 is a quad 8-bit/10-bit parallel-to-serial and
serial-to-parallel transceiver device ideal for high-bandwidth
interconnection between line cards, serial backplanes, or
optical modules, over interconnect media such as Printed
Circuit Board (PCB) FR-4 traces or copper cables.
Each independent transceiver channel in BBT3420 is
capable of operating at 2.488-3.1875Gbps at full-rate, and
1.244-1.59375Gbps at half-rate. The four on-chip
transceivers shown in Figure 1-2 can also be configured as
a single 10 Gigabit Attachment Unit Interface (XAUI), for
both 10G Ethernet and 10G Fiber Channel or proprietary
backplane interfaces, providing up to 12.75Gbps of data
throughput at full duplex. The BBT3420 also supports the 10
Gigabit Media Independent Interface (XGMII) on the parallel
interfaces. The device can be used as an XGMII Extended
Sublayer (XGXS) device to support longer PCB traces
between optical transceiver modules and switch fabrics, as
shown in Figure 1-1.
As shown in Figure 1-3, each transceiver channel in
BBT3420 contains a serializer, a deserializer, an 8b/10b
encoder and decoder, as well as elastic buffers that provide
the interface for serial data transmission and data recovery.
Both the receive equalization and the transmit pre-emphasis
are provided on each of the channels to maximize
performance. In addition, a programmable receive FIFO in
each channel aligns all incoming serial data to the local clock
domain, adding or removing IDLE sequences as needed.
This in return will eliminate the need for multiple clock
domains for the interfaced ASIC device to the transceiver.
Each transceiver channel can also be configured to operate
as a non-encoded 10-bit transceiver, allowing long strings of
consecutive 1's or 0's (up to 512 bits). This feature enables
RX FIFO
Comma
Detector
10B/8B
Decoder
Deskew
Logic
BIST
Pattern
Analyzer
DDR
Output
Registers
RD[9:0]
RBC
the BBT3420 to accommodate proprietary encoded data
links.
On each channel, the transmitter accepts up to 10-bit wide
parallel SSTL_2 or HSTL Class I/O (Figure 2-1) data, which
is then serialized into high-speed NRZ (Non-Return to Zero)
serial streams. The effective serial output impedance is
nominally 150Ω differential.
The BBT3420 transceiver can be configured via pins and
through the Management Data Input/Output (MDIO)
interface specified in IEEE 802.3 Clause 22 or Clause 45.
The device supports both the 5-bit PHY address for Clause
22 and the 5-bit port address for Clause 45. The four device
addresses for Clause 45 are user selectable. The device
also supports the Built-in Self Test (BIST) and IEEE 1149.1
(JTAG) for self-test purposes including serial and parallel
loopback under either external pin or MDIO control, and
Pseudo Random Bit Sequence (PRBS) generation and
verification.
The BBT3420 is assembled in a 289-pin 19mm x 19mm
HSBGA package. The device can operate with a single 1.8V
supply and dissipates only 250mW per channel.
VDDQ/2
VDDQ
Zo=50Ω
FIGURE 2-1. SSTL_2/HSTL CLASS I I/O
VTT=VDDQ/2
50Ω
VREF= VDDQ/2
VDDQ
3
BBT3420
www.BDTIC.com/Intersil
3.0 Detailed Functional Description
3.1 Transmit Parallel Input Modes
The parallel side of each of the channels in BBT3420 may
operate in either a 10-bit mode or a XGMII 9-bit mode. The
parallel input mode selection is controlled by the CODE pin
(Table 4-6) and the CODECENA bit in the MDIO register at
address 11’h in Clause 22 format (Table 3-16) and/or C000’h
in Clause 45 format (Table 3-32). In order to program the
device for XGMII 9-bit mode, the CODE pin should be set
HIGH and the CODECENA bit set to 1’b. For the 10-bit
Mode setting, either the CODE pin should be set to LOW or
the CODECENA bit should be set to 0’b.
3.1.1 10-BIT MODE
In the 10-bit mode the 8b/10b Codec is disabled, and the
externally encoded data are latched in the DDR input
registers in increments of 10 bits. In this case, the user is
responsible for generating and applying the proper input in
the form of ordered sets, data, and correct ‘comma’ group
signals, to ensure data coherence. The LSB (TDX[0]) is
shifted out first on the serial side, and the MSB (TDX[9]) is
shifted out last.
3.1.2 XGMII 9-BIT (8 BITS PLUS K CONTROL BIT) MODE
In the XGMII 9-bit mode, the unencoded data are latched in
the DDR input registers in 9 bits at a time. The lower 8 bits
(TD[A..D][7:0]) are byte-wide data or control values, and the
th
9
bit (TD[A..D][8]) is the "K" bit used to select special
control characters for link management. In this mode, the
th
10
bit (TD[A..D][9]) is used for disparity error or code
violation. The8b/10b Codec is enabled, and converts the
data and the valid control values.
The XGMII IDLE Code Register (Clause 22 Address 1B’h or
Clause 45 Address C003’h) controls the data pattern that
represents an IDLE character. The default value of this
register is 07’h. The register can be programmed to any 8-bit
value excluding the already defined (control) values shown
in Table 3-1.
When both the TRANS_EN bit (Clause 22 Address 10’h in
Table 3-15 or Clause 45 Address C001’h in Table 3-33) and
the AKR_EN bit (Clause 22 Address 1D’h in Table 3-28 or
Clause 45 Address C001’h in Table 3-33) are set to 1, or
when the XAUI_EN bit is set, the IDLE character data
pattern will be sequenced into /A/, /K/, and /R/ codes (IEEE
802.3ae-2002 specified). Alternatively, if neither of the
AKR_EN or XAUI_EN bits are set, the XGMII IDLE and the
/K/ code will both be transmitted as the XAUI /K/ code, and
the /A/ and /R/ control codes will be transmitted as XAUI /A/
and /R/ codes respectively. The 8b/10b encoding patterns
are described in Table 3-1. For valid operation, the XGMII
and XAUI Lane 0 signals should be connected to the
BBT3420 Channel A pins.
When the XAUI_EN bit is set to 1, if a local/remote fault is
received on the XAUI inputs, it will be passed as ||LF|| or
||RF|| Sequence Ordered_sets respectively, i.e.,
/K28.4/D0.0/D0.0/D1.0(D2.0)/. Local fault is declared when
any of the following conditions are detected:
1. No signal is detected in any one of four channels.
2. No valid comma is detected in any one or more of the four
channels.
3. When all the channels are not deskewed.
When the XAUI_EN bit is set to 1, if a local/remote fault
K28.4/D0.0/D0.0/D1.0(D2.0)/ is written to the XGMII transmit
interface for XAUI transmission, the ||LF|| or ||RF|| Sequence
Ordered_set is transmitted according to the IEEE 802.3ae2002 randomizing algorithm. Any other Sequence
Ordered_set will also be transmitted in the same way.
1. If the XAUI_EN bit is set, the BBT3420 acts as though both the TRANS_EN and AKR_EN bits are set.
2. The XGMII IDLE character is set by the XGMII IDLE register, address 1B’h/C003’h (see Table 3-26), default value 07’h, combined with the K
bit (XGMII value 107’h).
AKR_EN BIT
(Note 1)
SERIAL
CHARACTER
SERIAL
CODE
NOTES and
DESCRIPTIONK-BITTD DATA
3.2 Transmit Byte Clock
3.2.1 FULL- AND HALF-RATE MODE
Since the BBT3420 normally employs Double Data Rate
(DDR) timing, the local reference clock requirement is
lowered to 124.4-159.375MHz. The Transmit Byte Clock
(TBC) must be frequency-synchronous with the local
reference clock. For any channel set to Half-Rate Clock
Mode by the MDIO/MDC register 1F’h (for Clause 22) and/or
C008’h (for Clause 45), see Table 3-30, the TBC must be
provided at half the ref clock frequency, unless the TX_SDR
bit is set in the MDIO register C001’h (Clause 45, Table 3-
33) and/or 1D’h (Clause 22, Table 3-28).
3.2.2 SOURCE-CENTERED AND -SIMULTANEOUS
MODE
For ease of ASIC timing, the BBT3420 provides the option
for the TBC to be source-simultaneous or source-centered.
In source-simultaneous mode, the ASIC is not required to
adjust the TBC signal to the center of the data window. The
internal latch clock of the BBT3420 is set to +5 serial bit
times after the rising edge of the clock (TBC or RefClock)
when the chip is reset. In source-centered mode, the
BBT3420 expects stable data, with proper setup/hold time
with respect to the TBC from the ASIC. The specific clocking
mode is selectable by the MDIO/MDC register bit SC_TBC
at address 11’h in Clause 22 format, Table 3-16, and/or
C001’h in Clause 45 format, Table 3-33.
3.2.3 TRUNKING MODE
The TBC source for each channel is determined by the
trunking mode setting of the PSYNC pin. When trunking is
turned on (PSYNC high), all four channels are latched by the
Channel A TBC on pin TCA. In non-trunking mode, each
channel is latched with its corresponding TBC pin TC[A-D]
independently. Note that PSYNC will also force trunking of
the Receive Byte Clocks (see below). Alternatively, the
TC[A-D] inputs may be driven from a common source, such
as the local reference clock.
3.3 Transmit FIFO
A 4-byte-deep input FIFO is used to accommodate any TBC
or data drift. The initial pointer value is 2 bytes, which can
accommodate ±2 byte skew between channels, as well as
drift between the TBC and the reference clock. When the
FIFO depth is at one, the transmit data is ready for output on
the next TXC.
3.4 Serializer
The serializer accepts 10-bit transmission characters and
converts them from a parallel format to a serial bit stream at
2.488-3.1875Gbps. The system designer is expected to treat
such signals on the PCB as transmission lines and to use a
controlled impedance and suitable termination.
3.5 Pre-emphasis
In order to compensate for the loss of the high-frequency
signal components through PCB or cable, four levels of
programmable pre-emphasis have been added to all serial
transmit channels. This maximizes the data eye opening at
the receiver inputs and enhances the bit error rate
performance of the system. The MDIO Register at Address
1C’h (for Clause 22) and/or C005’h (for Clause 45) (see
Table 3-27) controls the level of pre-emphasis. Note that the
formula used to determine the pre-emphasis valuse is NOT
the same as that used in the IEEE 802.3ak-2004
specification for this parameter.
5
BBT3420
www.BDTIC.com/Intersil
TABLE 3-2. PRE-EMPHASIS CONTROL
CLAUSE 22
ADDRESS 1C’h OR
CLAUSE 45
ADDRESS C005’h
BIT 15
00No Pre-Emphasis
010.18
100.38
110.75
1
Bit
Time
FIGURE 3-1. PRE-EMPHASIS OUTPUT ILLUSTRATION
CLAUSE 22
ADDRESS 1C’h OR
CLAUSE 45
ADDRESS C005’h
BIT 14
1
Bit
Time
00
Bit
Time
PRE-EMPHASIS
VAL U E =
(V
PPOUT/VPP
)-1
VppoutVpp
3.6 Output Select – Serial Loopback
In normal mode, the serialized transmission TD[A..D][9..0]
data will be placed on TX[A..D]P/N. When serial loopback is
activated, Tx[AÖD] is internally looped back to Rx[AÖD]
respectively.
3.7 Receiver
The receiver detects and recovers the serial clock and data
from the received data stream. After acquiring bit
synchronization, the BBT3420 normally searches the serial
bit stream for the occurrence of a comma character to obtain
byte synchronization (byte alignment). The receiver then
performs channel alignment and clock compensation, as
desired. These are each discussed in the sections below.
3.7.1 Input Equalization and Transmission Line
Termination
An equalizer has been added to each receiver input buffer,
which boosts high-frequency edge response. The boost
factor can be selected from 0 to F’h through MDIO. The
MDIO register at address 1C’h (Clause 22), and/or C005’h
(Clause 45), see Table 3-27, controls the boost value of the
equalizer functions. A nominal 100Ω on-chip transmissionline termination resistor is integrated with the input equalizer,
eliminating the requirement of an external termination
resistor. This greatly improves the effectiveness of the
termination, providing the best possible signal integrity.
3.7.2 Loss of Signal (LOS)
Loss of signal is an indication of gross signal error
conditions. It is not an indication of signal coding health. It
may be caused by poor connections, insufficient voltage
swings, or out-of-range signal frequency. If any of these
conditions occurs, the SIG_DET pin will be de-asserted. In
addition, the MDIO MF_CTRL register bits (Address 10’h for
Clause 22 format, Table 3-15, and/or C001’h for Clause 45
format, Table 3-33) can be set to have the MF[A-D] pins
provide per-channel indication of Loss of Signal conditions,
the threshold being set by the MDIO LOS_CONTROL
register bits at Address 1D’h for Clause 22 format and/or
C001’h for Clause 45 format, Table 3-28 and/or Table 3-33
respectively. The LOS indication is also available directly in
the MDIO status registers, Address 01’h in Clause 22 format,
see Table 3-9, and/or Address C009’h in Clause 45 format,
see Table 3-31. The combination of all four drives the
SIG_DET pin (see Table 4-6), and contributes to the
RX_FAULT bit in the IEEE Status Register 2 at address
(00)08’h (Table 3-14) and the LOCAL_FLT bit in Register
0001’h, 1 in Table 3-10 (Clause 45 only).
As mentioned previously, LOS is designed as an indicator.
The listed LOS threshold is for reference only, it is not
designed to measure signal amplitude. Under nominal
operation conditions, the actual LOS threshold is at a signal
swing (single-ended peak-peak) lower or around the
datasheet specified threshold. For a low LOS threshold
setting, LOS may never be asserted due to noise.
3.7.3 Clock and Data Recovery
The line rate receive clock is extracted from the transitionrich 10-bit coded serial data stream independently on each
channel. The data rate of the received serial bit stream for
XAUI should be 3.125Gbps ±100ppm to guarantee proper
reception (and similarily for other data rates). The receive
clock locks to the input within 2µs after a valid input data
stream is applied. The received data is de-serialized and
byte-aligned.
The CDR unit will inherently acquire synchronization,
provided the signal level is adequate, and the frequency is
within the specified range of the local reference clock. If
synchronization is lost due to an invalid signal (e.g.
disconnect, out of range voltage swing, out of range
frequency, etc.), then the high-speed receive clock will free
run frequency-locked to the transmit clock.
3.7.4 Byte Alignment (code-group alignment)
Unless the CDET bits of the MDIO Register at address 10’h
(Table 3-15, Clause 22) and/or C000’h (Table 3-32, Clause
45) are turned off, the Byte Alignment Unit is activated. The
Byte Alignment Unit searches the coded incoming serial
stream for a sequence defined in IEEE 802.3-2002
subclause 36.2.4.8 as a “comma”. A comma is the sequence
“0011111” or “1100000” and is uniquely located in a valid
8b/10b coded data stream, appearing as the start of some
6
BBT3420
www.BDTIC.com/Intersil
control symbols, including the /K/ IDLE. Any proprietary
encoding scheme used should either incorporate these
codes, or arrange byte alignment differently. Comma
disparity action can be controlled via the CDET bits. Upon
detection of a comma, the Byte Alignment Unit shifts the
incoming data to align the received data properly in the 10bit character field. Two possible algorithms may be used for
byte alignment. The default is to byte-align on any comma
pattern. Although quick to align, and normally very reliable,
this method is susceptible to realignment on certain singlebit errors or on successive K28.7 characters. The alternative
algorithm is that specified in the IEEE802.3ae-2002 clause
48 specification, and is much less susceptible to error.
Algorithm selection is controlled via MDIO register bit
PCS_SYNC_EN at address 1D’h (Clause 22, Table 3-28)
and/or C000’h (Clause 45, Table 3-32), unless overridden by
the XAUI_EN bit in the same registers. The recovered
receive clocks may be stretched (never slivered) during byte
alignment, but up to a full code group may be deleted or
modified while aligning the "comma" code group correctly to
the edges of the RefClock.
3.7.5 Data Decoding
The serial bit stream must be ordered "abcdeifghj" with "a"
being the first bit received and "j" the last. With the 10b/8b
XGMII decoder enabled, the decoded data is ordered
"ABCDEFGHK" with "A" being the LSB. The decoding of
valid 10b patterns is shown in Table 3-3 below. If the
TRANS_EN bit or XAUI_EN bit (the MDIO Registers at
Clause 22 addresses 10’h and 1D’h, see Table 3-15 and
Table 3-28), and/or Clause 45 address C001’h, see Table 3-
33) are set, all incoming XAUI IDLE patterns will be
converted to the XGMII IDLE pattern set by the control
register at address 1B’h (Clause 22 format) and/or C003’h
(Clause 45 format), with a default value 107’h, the standard
XGMII IDLE code (see Table 3-26). If neither bit is set, the
incoming IDLE codes will all be decoded to the appropriate
XGMII control code values. The first full column of IDLEs
after any column containing a non-IDLE will be stored in the
elasticity FIFO, and all subsequent full IDLE columns will
repeat this pattern, until another column containing a nonIDLE is received.
If the BBT3420 XAUI_EN bit is set or the PCS_SYNC_EN
and DSKW_SM_EN bits are set, and the device has
detected a ‘Local Fault’ (see Table 3-10, Table 3-14, Table 328 and/or Table 3-32 & Table 3-33), the XGMII output will
consist of the Sequence control character in channel A
(XAUI lane 0) and data characters of 0x00 in channels B & C
(lanes 1 and 2) plus a data character of 0x01 in channel D
(lane 3), the IEEE-defined ||LF|| Sequence Ordered_Set.
Any otherX1= XGMII ERROR reg.(Note 3)Error Code, Default 1FF’h, see Table 3-19
NOTES:
1. First incoming IDLE only, subsequent IDLEs in that block repeat first received code.
2. If the XAUI_EN bit is set, the BBT3420 acts as though the TRANS_EN bit is set.
3. The XGMII IDLE character is set by the XGMII IDLE register, address 1B’h/C003’h (see Table 3-26), default value 07’h, combined with the K bit.
The XGMII ERROR code is similarly set by the XGMII ERROR register, address 16’h/C002’h (see Table 3-19)
3.8 Receive FIFO
The Receive FIFO performs two functions:
1. Channel Alignment
2. Clock Compensation
3.8.1 CHANNEL ALIGNMENT (DESKEW)
Trunking, also known as deskewing, means the alignment of
packet data across multiple channels. 8 byte of RXFIFO is
dedicated for channel alignment.
During high-speed transmission, different active and passive
elements in the links may impart varying delays in the four
channels. In trunking mode, multiple channels share the
same clock (local reference or recovered clock A), which is
used for outputting data on the parallel bus.
As defined by IEEE 802.3ae-2002, packets must start on
channel A (equivalent to Lane 0 in the IEEE 802.3ae-2002
specification). Deskewing is accomplished by monitoring the
contents of the FIFOs to detect the boundary between IDLE
sequences and any non-IDLE data (including data and the
/S/ code), which defines the beginning of the packet, or the
presence of the IEEE 802.3ae-defined /A/ character, for
channel alignment (controlled by MDIO Register 19’h in
Clause 22 format and/or C000’h in Clause 45 format, see
Table 3-24 and/or Table 3-32). When this alignment data is
detected in all four channels, the trunking channel-alignment
operation is performed, and will be held until another such
transition or /A/ character is detected again on any channel.
To maintain channel alignment, such transitions or /A/
characters should occur on all four channels simultaneously
(i.e. within the span of the FIFO). During channel
realignment, up to four code groups may be deleted,
repeated or garbled on any channel.
The deskew state machine is enabled by setting the
DSKW_SM_EN bit (Clause 22 Address 1D’h see Table 3-28;
Clause 45 Address C000’h see Table 3-32) to 1. The
deskew algorithm is implemented according to IEEE spec.
802.3ae. Note that when DSKW_SM_EN is set to 1, the
CAL_EN bit (Clause 22 Address 19’h see Table 3-24;
Clause 45 Address C000’h see Table 3-32) is ignored. When
8
BBT3420
www.BDTIC.com/Intersil
the DSKW_SM_EN bit is set to 0, channel deskew can still
be enabled by setting CAL_EN, but the deskew action will be
carried out without hysteresis.
The user has the option to disable trunking, or enable
trunking across 4 channels, under control of the PSYNC pin
(Table 4-6) and the RCLKMODE bits in the MDIO Registers
at address 18’h in Clause 22 format and/or C000’h in Clause
45 format (see Table 3-21 and/or Table 3-32). In trunking
mode, the channels may have phase differences, but they
are expected to be frequency synchronous. In non-trunking
mode, each received serial stream need only be within
±100ppm of 3.125Gbps (or 1.56125) Gbps. Note that
trunking mode is only possible if 8b/10b Coding is activated,
and all channels have the same half-rate setting (Table 3-
30).
3.8.2 CLOCK COMPENSATION
In addition to deskew, the Receive FIFO also compensates
for clock differences. Since the received serial stream can,
under worst-case conditions, be off by up to ±200ppm from
the local clock domain (both can be up to ±100ppm from
nominal), the received data must be adjusted to the local
frequency. The received data can be aligned in one of three
ways, under control of the PSYNC pin (Table 4-6) and the
RCLKMODE bits in MDIO Register 18’h in Clause 22 format
and/or C000’h in Clause 45 format (see Table 3-21 and/or
Table 3-32):
1. Local Reference Clock (trunking mode)
2. Recovered Clock for each channel (non-trunking mode)
3. Recovered Clock for Channel A (trunking mode)
Another 8 bytes of RXFIFO are dedicated for clock
compensation. The FIFOs achieve clock tolerance by
identifying any of the IDLE patterns in the XAUI input (/K/, /A/
or /R/ as defined by the IEEE 802.3ae-2002 standard) in the
received data and then adding or dropping IDLEs as
needed. The Receive FIFO does not store the actual IDLE
sequences received but generates the number of IDLEs
needed to compensate for clock tolerance differences. See
also Table 3-3 on page 8.
error or code error. In the event of a disparity error, the
decoded value is passed to the parallel output [8..0], and bit
9 is asserted to indicate the error. If it is a coding error, the
decoded value presented is a programmable error byte
(default=K30.7). Therefore the value for bit 0-8 is
1,1111,1110’b. Bit 9 is asserted to indicate the error.
This transceiver does not support the even/odd character
mode specific to 1000Base-X operations. Byte alignment
with comma is achieved with a 10-bit period. As a result, a
comma received at any odd or even byte location, but at the
proper byte boundary, will not cause any byte realignment.
3.10.2 10-BIT MODE
If the 8b/10b Codec is inactive, disparity error and coding
violation errors do not apply. System designers must ensure
that the data stream is DC-balanced and contains sufficient
transition density for proper operation, including
synchronization. The required density depends on the
frequency difference between the received data and the
local reference clock, and the incoming signal jitter tolerance
requirement. For a frequency difference of ±100ppm, and a
transition-free data pattern of 500 successive 1’s or 0’s, the
total build-up of CDR timing error is 0.1 UI. If this pattern is
followed by a pattern of normal density, the reduction of jitter
tolerance will usually be acceptable, though if such long notransition patterns are common, the jitter buildup could be
cumulative. In a fully synchronous system, where there are
no consistent frequency differences, these effects are of
course reduced.
3.10.3 OUTPUT SELECT – PARALLEL LOOPBACK
In normal mode, the serial input data RX[A..D]P/N data will
be placed on the parallel receive outputs RD[A..D][9..0].
When parallel loopback is activated, the internal parallel
output is routed to the parallel input (including clock) for
every channel. The RD[A..D][9..0] pins may be disabled if
desired, whether in parallel output mode or not, by using the
IPON bit of the MDIO Register at address 011’h (Clause 22
see Table 3-16) and/or address C001’h (Clause 45, see
Table 3-33).
3.9 Error Recovery
Errors in the high-speed links can be separated into two
types, Loss of Signal and Coding Error violations. These are
handled differently by the Error Recovery system in the
BBT3420.
3.10 Disparity Error & Coding Violation
3.10.1 XGMII 8 BIT MODE
If 8b/10b encoding/decoding is turned on, the BBT3420
expects to receive a properly encoded serial bit stream. If
the received data contains an error, the transceiver will
report it as described below:
The received bits 0-7 represent the 8b/10b decoded value,
bit 8 represents the K value and bit 9 indicates a disparity
9
BBT3420
www.BDTIC.com/Intersil
TABLE 3-4. MDIO MANAGEMENT FRAME FORMATS
Clause 22 Format (from Table 22-10 in IEEE Std 802.3-2002)
Opern PRESTOP PHYADREGAD TADATAIDLE
Read1....10110PPPPPRRRRRZ0DDDDDDDDDDDDDDDDZ
Write1....10101PPPPPRRRRR10DDDDDDDDDDDDDDDDZ
Clause 45 Format (from Table 45-64 in IEEE 802.3.ae-2002)
OpernPRESTOP PRTADDEVAD TAADDRESS/DATAIDLE
Addrs1....10000PPPPPDDDDD10AAAAAAAAAAAAAAAAZ
Write1....10001PPPPPDDDDD10DDDDDDDDDDDDDDDDZ
Read1....10011PPPPPDDDDDZ0DDDDDDDDDDDDDDDDZ
Read Inc1....10010PPPPPDDDDDZ0DDDDDDDDDDDDDDDDZ
3.11 Serial Management Interface
The BBT3420 implements both the Management Interface
defined in IEEE 802.3 Clause 22, and that defined in Clause
45. This two-pin interface allows serial read/write of the
internal control registers and consists of the MDC clock and
MDIO data terminals. The PADR[4..0] pins are used to select
the address to which a given BBT3420 device responds.
The remainder of the MDIO frame and access details
depend on the respective formats. The BBT3420
automatically detects which format is being used on a frameby-frame basis, based on the second START bit. The two
formats are shown in Table 3-4, together with the references
to the respective IEEE 802.3 specifications. The fields are as
follows:
• PRE, the Preamble field: at least 32 consecutive ‘1’ bits.
The BBT3420 will accept any number ≥32.
• ST, the Start of Frame; for Clause 22, <01>; for Clause 45,
<00>.
• OP, the Operation code; for Clause 22, Read and Write
operations are defined, all other values are invalid; for
Clause 45, additional operations to send the 16-bit
(indirect) register address, and to read data and (then)
increment the stored address are added.
• PHYAD/PRTAD; the PHYsical (Clause 22) or PoRT
(Clause 45) hardware ADdress; this 5-bit address must
match the PADR pins on the BBT3420.
• REGAD, REGister ADdress (Clause 22); this 5-bit address
specifies the register address. Replaced by the 16-bit
address value in Clause 45 format.
• DEVAD, DEVice ADdress (Clause 45); this 5-bit address
specifies which MMD at any given port is being
addressed. See Table 3-5 and section 3.13 for the
possible values the BBT3420 will respond to.
• TA, the TurnAround; allows time to avoid contention for a
read operation on the MDIO line.
• DATA; the 16 bit data values to be written to or being read
from the BBT3420.
• ADDRESS (Clause 45); this 16-bit address specifies the
register address for subsequent Clause 45 read or write
operations. A Read Increment operation will postincrement the value.
• IDLE; this condition flags the end of the frame. Since the
IEEE specification calls for a pullup on the MDIO line, this
effectively provides the MMD with a ‘1’ character, which
can be the beginning of the next PREamble.
TABLE 3-5. DEVAD DEVICE ADDRESS SETUP TABLE
DEVAD
MFDMFC
11DEVAD = 5
10DEVAD = 4
01DEVAD = 31
00DEVAD = 30
VAL UEDEFAULT
(000101’b)
(00100’b)
(11111’b)
(11110’b)
11’bDTE XS (XGXS
IEEE
DEFINITION
Device)
PHY XS (XGXS
Device)
Vendor Specific
Vendor Specific
3.12 Clause 22 PHY Addressing
The PADR[4..0] hardware address pins control the PHYAD
value, allowing use of up to 31 BBT3420 (or other
compatible) devices on any MDC/MDIO line pair. Each
device may contain up to 32 registers, some of which are
defined by the IEEE standard, the others being Vendordefined. The Clause 22-accessible registers are listed in
Table 3-6.
3.13 Clause 45 PHY Addressing
The PADR[4..0] hardware address pins control the PRTAD
(Port Address) value, each port normally consisting of a
series of MDIO Managed Devices (MMDs). Each of the up to
31 Ports may include up to 31 different devices, of which the
current specification defines 6 types, and allows vendor
specification of two others. The native-mode BBT3420
corresponds to two of the defined types; it can be either a
PHY XS (DEVAD = 4) or a DTE XS (DEVAD = 5), but may
also be used as part of another defined type, or as a
10
BBT3420
www.BDTIC.com/Intersil
RETIMER function. The device may be set to respond to any
one of four DEVAD values, (4, 5, 30 or 31) by controlling the
level on the MFC and MFD pins at the end of reset. These
pins are normally outputs, but become inputs when RSTN is
active, and so may be pulled to the desired value by
moderate value resistors (~5kΩ), which will not affect the
normal operation of the pins when outputs. The value on
these pins will be latched at the rising edge of RSTN. The
coding is shown in Table 3-5. A weak pullup is built into
these pins, so that if unwired, they will default to DEVAD = 5.
See Table 6-13 and Figure 6-9 for the timing of these
signals. The Clause 45-accessible registers are listed in
Table 3-7. These register addresses are independent of the
DEVAD value, including the ‘Vendor Defined’ DEVAD values
30 & 31; thus registers 30.8 & 31.8 include the RX_FAULT
and TX_FAULT bits.
Each individual device may have up to 2
16
(65,536)
registers for PHY XS and DTE XS devices (they may be
accessed identically through any of the implemented DEVAD
address values), and 11 of the 32k (2
15
) allowed Vendor
Specific registers. The latter have been placed in the block
beginning at C000’h so as to avoid the areas currently
defined as for use by the XENPAK module and similar MSA
devices, to facilitate use of the BBT3420 in systems using
such modules and/or devices.
In order to align the registers and bits as closely as possible
to the new IEEE Clause 45 standard, while maintaining
compatibility with previous versions of the part before the
Clause 45 interface was defined, which used only the
Clause 22 interface, the control and status bits are differently
distributed among the registers in the two formats. The
Clause 22 registers are listed in Table 3-6, and the Clause
45 registers in Table 3-7.
registers. The BBT3420 implements 11 of the IEEE-defined
TABLE 3-6. MDIO REGISTERS IN CLAUSE 22 FORMAT
MII REGISTERS
ADDRESSNAMEDESCRIPTIONDEFAULTR/WDETAILS
00’hControlReset, Enable serial loop back mode.2040’hR/WTable 3-8