DS33W11 DS33X82
DS33W11 DS33X82
DS33W11 DS33X82
DS33X162/DS33X161/DS33X82/DS33X81/
DS33X42/DS33X41/DS33X11/DS33W41/DS33W11
Ethernet Over PDH Mapping Devices
TRAFFIC
GFP/
Table of Contents
1. DETAILED DESCRIPTION .............................................................................................................. 9
2. FEATURE HIGHLIGHTS................................................................................................................ 10
2.1 GENERAL ...................................................................................................................................... 10
2.2 VCAT/LCAS LINK AGGREGATION (INVERSE MULTIPLEXING) ..........................................................10
2.3 HDLC........................................................................................................................................... 10
2.3.1 cHDLC.................................................................................................................................................. 10
2.4 GFP-F.......................................................................................................................................... 11
2.5 X.86 SUPPORT .............................................................................................................................11
2.6 DDR SDRAM INTERFACE .............................................................................................................11
2.7 MAC INTERFACES .........................................................................................................................11
2.7.1 Ethernet Bridging for 10/100 ................................................................................................................ 12
2.7.2 Ethernet Traffic Classification .............................................................................................................. 12
2.7.3 Ethernet Bandwidth Policing ................................................................................................................ 12
2.7.4 Ethernet Traffic Scheduling.................................................................................................................. 12
2.7.5 Connection Endpoints .......................................................................................................................... 12
2.7.6 Virtual Connection................................................................................................................................ 12
2.7.7 Connection and Aggregation ............................................................................................................... 12
2.7.8 Ethernet Control Frame Processing..................................................................................................... 12
2.7.9 Q-in-Q .................................................................................................................................................. 12
2.8 SERIAL PORTS ..............................................................................................................................13
2.8.1 Voice Ports........................................................................................................................................... 13
2.9 MICROPROCESSOR INTERFACE ......................................................................................................13
2.10 SLAVE SERIAL PERIPHERAL INTERFACE (SPI) FEATURES ............................................................13
2.11 TEST AND DIAGNOSTICS .............................................................................................................13
2.12 SPECIFICATIONS COMPLIANCE....................................................................................................13
3. APPLICABLE EQUIPMENT TYPES..............................................................................................14
4. ACRONYMS & GLOSSARY ..........................................................................................................17
5. DESIGNING WITH THE DS33X162 FAMILY OF DEVICES..........................................................18
5.1 IDENTIFICATION OF APPLICATION REQUIREMENTS ..........................................................................18
5.2 DEVICE SELECTION .......................................................................................................................18
5.3 ANCILLARY DEVICE SELECTION......................................................................................................19
5.4 CIRCUIT DESIGN............................................................................................................................19
5.5 BOARD LAYOUT .............................................................................................................................19
5.6 SOFTWARE DEVELOPMENT ............................................................................................................19
6. BLOCK DIAGRAMS ...................................................................................................................... 20
7. PIN DESCRIPTIONS ...................................................................................................................... 21
7.1 PIN FUNCTIONAL DESCRIPTION ......................................................................................................21
8. FUNCTIONAL DESCRIPTION .......................................................................................................34
8.1 PARALLEL PROCESSOR INTERFACE................................................................................................35
8.1.1 Read-Write/Data Strobe Modes........................................................................................................... 35
8.1.2 Clear on Read ...................................................................................................................................... 35
8.1.3 Interrupt and Pin Modes....................................................................................................................... 35
8.1.4 Multiplexed Bus Operation................................................................................................................... 35
8.2 SPI SERIAL PROCESSOR INTERFACE .............................................................................................36
8.3 CLOCK STRUCTURE.......................................................................................................................37
8.3.1 Serial Interface Clock Modes ............................................................................................................... 39
8.3.2 Ethernet Interface Clock Modes........................................................................................................... 39
Rev: 063008 2 of 375
________________________________________________ DS33X162/X161/X82/X81/X42/X41/X11/W41/W11
List of Figures
Figure 3-1. Standardized Ethernet Transport over Multiple T1/E1 Lines .................................................................. 14
Figure 3-2. Standardized Ethernet Transport over a Single T1/E1 Line ................................................................... 15
Figure 3-3. Remote IP DSLAM T1/E1 Trunk Card .................................................................................................... 16
Figure 6-1. Simplified Logical Block Diagram............................................................................................................ 20
Figure 7-1. 256-Ball, 17mm x 17mm CSBGA Pinout (DS33X162/X161/X82/X81/X42/X41) .................................... 31
Figure 7-2. 256-Ball, 17mm x 17mm CSBGA Pinout (DS33W41/DS33W11)........................................................... 32
Figure 7-3. 144-Ball, 10mm x 10mm, CSBGA Pinout (DS33X11) ............................................................................ 33
Figure 8-1. Clocking Diagram .................................................................................................................................... 38
Figure 8-2. Device Interrupt Information Flow Diagram ............................................................................................ 42
Figure 8-3. Forwarding Mode 1: Single Ethernet Port with Priority Forwarding ........................................................ 44
Figure 8-4. Forwarding Mode 2: One or Two Ethernet Port Forwarding with Scheduling......................................... 45
Figure 8-5. Forwarding Mode 3: Single Ethernet Port with LAN-VLAN Forwarding.................................................. 46
Figure 8-6. Forwarding Mode 4: 1 Ethernet port with Port ID and LAN-VLAN Forwarding....................................... 47
Figure 8-7. Forwarding Mode 5: Full LAN-to-WAN and WAN-to-LAN VLAN Forwarding ......................................... 48
Figure 8-8. IEEE 802.3 Ethernet Frame .................................................................................................................... 60
Figure 8-9. Example Configuration of GMII Interface (DTE Mode Only)................................................................... 62
Figure 8-10. Example Configuration as DTE connected to an Ethernet PHY in MII Mode ....................................... 63
Figure 8-11. Example Configuration as a DCE in MII Mode ..................................................................................... 65
Figure 8-12. RMII Interface (DTE Mode Only)........................................................................................................... 66
Figure 8-13. IEEE 802.1Q and 802.1p Field Format ................................................................................................. 69
Figure 8-14. VLAN Q-in-Q Field Format.................................................................................................................... 70
Figure 8-15. Differentiated Services Code Point (DSCP) Header Information.......................................................... 71
Figure 8-16. Supported Trapped Ethernet Frame Types .......................................................................................... 75
Figure 8-17. MII Management Frame ........................................................................................................................ 83
Figure 8-18. GFP-F NULL Encapsulated Frame Format .......................................................................................... 91
Figure 8-19. GFP-F LINEAR EXTENSION Encapsulated Frame Format................................................................. 93
Figure 8-20. LAPS / X.86 Encapsulated Frame Format ............................................................................................ 94
Figure 8-21. HDCL Encapsulated Frame Format...................................................................................................... 97
Figure 8-22. cHDLC Encapsulated Frame Format .................................................................................................... 98
Figure 9-1. Interfacing with T1/E1 Transceivers...................................................................................................... 101
Figure 9-2. Example Functional Timing: DS2155 E1 Transmit-Side Boundary Timing .......................................... 101
Figure 9-3. Example Functional Timing: DS2155 T1 Transmit-Side Boundary Timing........................................... 102
Figure 9-4. Example Functional Timing: DS2155 E1 Receive-Side Boundary Timing ........................................... 102
Figure 9-5. Example Functional Timing: DS2155 T1 Receive-Side Boundary Timing............................................ 102
Figure 9-6. Interfacing with T3/E3 Transceivers...................................................................................................... 103
Figure 9-7. Example Functional Timing: DS3170 DS3 Transmit-Side Boundary Timing........................................ 103
Figure 9-8. Example Functional Timing: DS3170 DS3 Receive-Side Boundary Timing......................................... 104
Figure 11-1. SPI Serial Port Access For Read Mode, SPI_CPOL=0, SPI_CPHA = 0 ............................................ 330
Figure 11-2. SPI Serial Port Access For Read Mode, SPI_CPOL = 1, SPI_CPHA = 0 .......................................... 330
Figure 11-3. SPI Serial Port Access For Read Mode, SPI_CPOL = 0, SPI_CPHA = 1 .......................................... 331
Figure 11-4. SPI Serial Port Access For Read Mode, SPI_CPOL = 1, SPI_CPHA = 1 .......................................... 331
Figure 11-5. SPI Serial Port Access For Write Mode, SPI_CPOL = 0, SPI_CPHA = 0 .......................................... 331
Figure 11-6. SPI Serial Port Access For Write Mode, SPI_CPOL = 1, SPI_CPHA = 0 .......................................... 331
Figure 11-7. SPI Serial Port Access For Write Mode, SPI_CPOL = 0, SPI_CPHA = 1 .......................................... 332
Figure 11-8. SPI Serial Port Access For Write Mode, SPI_CPOL = 1, SPI_CPHA = 1 .......................................... 332
Figure 11-9. Transmit Serial Port Interface, without VCAT ..................................................................................... 333
Figure 11-10. Transmit Serial Port Interface with VCAT ......................................................................................... 333
Figure 11-11. Transmit Serial Port Interface, with Gapped Clock ........................................................................... 333
Figure 11-12. Transmit Serial Port Interface with VCAT, early TSYNC (2 cycles).................................................. 334
Figure 11-13. Receive Serial Port Interface, without VCAT, rising edge sampling ................................................. 334
Figure 11-14. Receive Serial Port Interface with VCAT, rising edge sampling ....................................................... 334
Figure 11-15. Receive Serial Port Interface with Gapped Clock (T1) ..................................................................... 334
Figure 11-16. Transmit Voice Port Interface with PCM Octets................................................................................ 335
Figure 11-17. Receive Voice Port Interface with PCM Octets................................................................................. 335
Figure 11-18. GMII Transmit Interface Functional Timing ....................................................................................... 336
List of Tables
Table 1-1. Product Selection Matrix............................................................................................................................. 9
Table 7-1. Detailed Pin Descriptions ......................................................................................................................... 21
Table 8-1. Clocking Options for the Ethernet Interface ............................................................................................. 37
Table 8-2. Software Reset Functions ........................................................................................................................ 39
Table 8-3. Block Enable Functions ............................................................................................................................ 40
Table 8-4. Forwarding Modes Supported by Device ................................................................................................. 49
Table 8-5. Maximum Number of T3/E3 Lines Per Encapsulator (DS33X162 and DS33X82 Only) .......................... 51
Table 8-6. VCAT/LCAS Control Frame for T1/E1...................................................................................................... 53
Table 8-7. VCAT/LCAS Control Frame for T3/E3...................................................................................................... 54
Table 8-8. Configuration Recommendations for Maximum Frame Length................................................................ 61
Table 8-9. Selection of MAC Interface Modes for Port 1 ........................................................................................... 61
Table 8-10. Selection of MAC Interface Modes for Port 2......................................................................................... 61
Table 8-11. MII Mode Options ................................................................................................................................... 64
Table 8-12. Example Priority Table Configuration for DSCP .................................................................................... 72
Table 8-13. Example Priority Table Configuration for PCP ....................................................................................... 73
Table 8-14. MAC Control Registers........................................................................................................................... 81
Table 8-15. MAC Status Registers ............................................................................................................................ 81
Table 8-16. MAC Counter Registers.......................................................................................................................... 82
Table 8-17. GFP Type/tHEC Field (Payload Header) Definition ............................................................................... 89
Table 8-18. GFP UPI Definitions ............................................................................................................................... 89
Table 8-19. Example GFP Type + tHEC Values ....................................................................................................... 90
Table 8-20. GFP CID/Spare/eHEC (Extension Header) Field Definition................................................................... 92
Table 8-21. Example CID + Spare + eHEC Values................................................................................................... 92
Table 8-22. Credit Threshold Settings with Resulting Bandwidths.......................................................................... 100
Table 10-1. Register Address Map .......................................................................................................................... 105
Table 10-2. Global Register Bit Map........................................................................................................................ 106
Table 10-3. MAC Indirect Register Bit Map ............................................................................................................. 131
Table 10-4. Default GL.IDR Values ......................................................................................................................... 141
Table 10-5. Valid Conditions for MPL > 2048.......................................................................................................... 182
Table 12-1. Recommended DC Operating Conditions ............................................................................................ 339
Table 12-2. DC Electrical Characteristics................................................................................................................ 340
Table 12-3. Thermal Characteristics........................................................................................................................ 341
Table 12-4. Transmit GMII Interface........................................................................................................................ 342
Table 12-5. Receive GMII Interface......................................................................................................................... 343
Table 12-6. Transmit MII Interface........................................................................................................................... 344
Table 12-7. Receive MII Interface............................................................................................................................ 345
Table 12-8. Transmit RMII Interface ........................................................................................................................ 346
Table 12-9. Receive RMII Interface ......................................................................................................................... 347
Table 12-10. MDIO Interface ................................................................................................................................... 348
Table 12-11. Transmit WAN Interface ..................................................................................................................... 349
Table 12-12. Receive WAN Interface ...................................................................................................................... 350
Table 12-13. Transmit Voice Port Interface............................................................................................................. 351
Table 12-14. Receive Voice Port Interface.............................................................................................................. 352
Table 12-15. DDR SDRAM Interface....................................................................................................................... 353
Table 12-16. Parallel Microprocessor Bus............................................................................................................... 355
Table 12-17. Multiplexed Microprocessor Bus ........................................................................................................ 358
Table 12-18. SPI Microprocessor Bus Mode........................................................................................................... 361
Table 12-19. JTAG Interface ................................................................................................................................... 362
Table 13-1. Instruction Codes for IEEE 1149.1 Architecture................................................................................... 367
Table 13-2. ID Code Structure................................................................................................................................. 368
1. Detailed Description
The DS33X162 family of devices provide interconnection and mapping functionality between Ethernet Systems and
WAN Time-Division Multiplexed (TDM) systems such as T1/E1/J1, HDSL, T3/E3, and SONET/SDH. The device is
composed of up to two 10/100/1000 Ethernet MACs, up to 16 Serial Ports, a Arbiter, GFP-F /HDLC/cHDLC/X.86
(LAPS) Mappers, a DDR SDRAM interface, and control ports. Ethernet traffic is encapsulated with GFP-F, HDLC,
cHDLC, or X.86 (LAPS) to be transmitted over the WAN Serial Interfaces. The WAN Serial Interfaces also receive
encapsulated Ethernet frames and transmit the extracted frames over the Ethernet ports. The LAN frame interface
consists of Ethernet interfaces using one of two physical layer protocols. It can be configured with up to two
10/100Mbps MII/RMII ports or a single GbE GMII port. The WAN Serial Interface can be configured for up to eight
serial data streams at up to 52Mbps each, or 16 serial data streams at up to 2.5Mbps each. The Serial Interfaces
can be seamlessly connected to the Maxim T1/E1/J1 Framers, Line Interface Units (LIUs), and Single-Chip
Transceivers (SCTs). The WAN interfaces can also be seamlessly connected to the Maxim T3/E3/STS-1 Framers,
LIUs, and SCTs to provide T3, E3, or STS1 connectivity.
Microprocessor control can be accomplished through a 8-bit Micro controller port or SPI Bus. The device has a
125MHz DDR SDRAM controller and interfaces to a 32-bit wide 256Mb DDR SDRAM via a 16-bit data bus. The
DDR SDRAM is used to buffer data from the Ethernet and WAN ports for transport.
The power supplies consist of a 1.8V core supply, a 2.5V DDR SDRAM supply, and 3.3V I/O supply. The DDR
interface also requires a 1.25V reference voltage that can be obtained through a resistor-divider network.
2. Feature Highlights
2.1 General
• 17mm 256 pin CSBGA Package (DS33X162/X161/X82/X81/X41/W41/W11)
• 10mm 144 pin CSBGA Package (DS33X11)
• 1.8V, 2.5V, 3.3V supplies
• IEEE 1149.1 JTAG boundary scan
• Software access to device ID and silicon revision
• Development support includes evaluation kit, driver source code, and reference designs
2.3 HDLC
• Up to 4 HDLC Controller Engines
• Compatible with polled or interrupt driven environments
• Supports Bit stuffing/destuffing without Address/Control/PID fields
• Programmable FCS insertion and extraction, with removal of payload FCS
• 16-bit or 32-bit FCS, with support for FCS error insertion
• Programmable frame size limits (Minimum 64 bytes and maximum 2016 bytes)
• Selectable self-synchronizing X43+1 frame scrambling/descrambling
• Separate valid and invalid frame counters
• Programmable inter-frame fill for transmit HDLC
• Supports Transparency Processing and Abort Sequence
• Programmable frame filtering for FCS errors, aborts, or frame length errors
2.3.1 cHDLC
• Bit stuffing with Address/Control/PID/FCS fields
• Programmable Interframe fill length.
• Transparency processing
• Counters: Number of received valid frames and erred frames
• Incoming Frame Discard due to FCS error, abort or frame length longer than preset max.
• The default maximum frame length is associated with the maximum PDU length of MAC frame
• Extract SLARP for external processor interpretation
2.4 GFP-F
• GFP Frame mode per ITU-T G.7041
• GFP idle frame insertion and extraction
• Supports Null and Linear headers
• cHEC based frame delineation
• X43 +1 payload and Barker Sequence scrambling/descrambling
• CSF frame generation and detection
• Error detection over core header and type headers
• Programmable CRC-32 generation and verification
2.7.9 Q-in-Q
• Programmable Carrier VLAN tag insertion.
Other: RMII: Industry Implementation Agreement for “Reduced MII Interface,” Sept 1997
DS26521 E1/T1 #1
MAGNETICS
10/100/
10/100/1000
1000
DS33X162 T1/E1
ETHERNET ETHERNET-TO-SERIAL SCT #1
PHY MII, CONVERSION, QoS,
RMII, VCAT/LCAS DS26521 E1/T1 #2
MAGNETICS
GMII AGGREGATION,
10/100 10/100/ BRIDGING & FILTERING, T1/E1
ETHERNET PHY BUFFERING, RATE SCT #2
MATCHING, ERROR •
DETECTION, STATISTICS
GATHERING, • E1/T1 #16
DS26521
MAGNETICS
DDR OAM EXTRACT/INSERT
SDRAM
T1/E1
SCT #16
MAX3232e
RS-232 DS80C320 μC FOR
CONFIG MAX809L CONFIGURATION
μC RESET
SOLUTION ADVANTAGES:
DS33X11 E1/T1
10/100/1000 MII, DS26521
ETHERNET-TO-SERIAL
ETHERNET RMII, CONVERSION, QoS, T1/E1
10/100/ GMII BRIDGING & FILTERING, SCT #1
1000 BUFFERING, RATE
PHY MATCHING, ERROR
DETECTION, STATISTICS
GATHERING, OAM PROGRAMMABLE
DDR EXTRACT/INSERT GAPPED CLOCK,
DATA, AND
SDRAM FRAME SYNC
MAX3232
RS-232 DS80C320 μC
CONFIG MAX809L FOR CONFIGURATION
μC RESET
SOLUTION ADVANTAGES:
• Ethernet Transport Over Single or Fractional E1/T1 with QoS and Ethernet OAM Capability!
• Flexible Fractional E1/T1 (Nx64kbps in Any DS0s) Support, Using DS26521 Channel Blocking
• No Data Path Code Development Required!
• GFP, HDLC, LAPS, or cHDLC Encapsulation
• Solution Extends Easily to DS3/E3
8 AGGREGATED
T1/E1/J1s
xDSL LINE CARD
MII/
RMII/
DS33X81
xDSL LINE CARD GMII ETHERNET-TO-
SERIAL LINK DS26528
10/100/GbE
TO
SUBSCRIBERS
SDRAM DS80C320 μC
1000BASE-LX
GbE TRANSCEIVER
xDSL LINE CARD
SOLUTION ADVANTAGES:
6. Block Diagrams
SPI_MISO
SPI_MOSI
SPI_CLK
A0-A10
D0-D7
INT
WR
RD
CS
SPI μP Port
TCLK1 CLAD
TRANSMIT SERIAL SYSCLKI
TDATA1
SCHEDULING
PORT 1
ENCAPSULATORS
TSYNC1
(MII MODE)
PRIORITY
4 x VCAT/LCAS
TCLK2 TRANSMIT SERIAL 4 x GFP/HDLC RXD[0:4]
QoS
TDATA2 RX_CLK
PORT 2
ETHERNET MAC1
TSYNC2
RX_CRS
RX_ERR
CIR/CBS
COL1
TMCLK4 TX_CLK
TRANSMIT SERIAL
TDATA16 TX_EN
TMSYNC4 PORT 16
TXD[0:4]
BRDIGE/FILTER
MDC
MDIO
ARBITER/ Add/Drop
BUFFER MANAGER OAM Frames (MII MODE)
ETHERNET MAC2(X162/82/42)
RXD[0:4]
RX_CLK
RCLK1 RX_CRS
RDATA1 RECEIVE SERIAL
RX_ERR
CIR/CBS
PORT 1
DECAPSULATORS
RSYNC1
COL2
4 x VCAT/LCAS
4 x GFP/HDLC
SDATA[0:15]
TVDATA
TVCLK
RVDATA
RVCLK
SD_LDM
SD_UDM
SDA[0:12]
SD_LDQS
SD_UDQS
SD_CLK
SWE
SDCS
SRAS
SCAS
TVSYNC
TVDEN
RVSYNC
RVDEN
SD_CLK
JTAG Pins
SDCLKEN
7. Pin Descriptions
A10 G11 — I Address Bit 10. Address bit 10 of the microprocessor interface.
PACKAGE PINS
NAME TYPE FUNCTION
256 144
Data Bit 5. Bi-directional data bit 5 of the microprocessor interface. Not
driven when CS=1 or RST=0.
SPI_SWAP (SPI_SEL=1). Controls the address and data bit order of the
SPI interface. The R/W and B bit positions do not change.
0 = LSB is transmitted and received first. The resulting bit order is:
D5/ R/W, A7, A8, A9, A10, A11, A12, A13,
L8 J5 IOz
SPI_SWAP A0, A1, A2, A3, A4, A5, A6, Burst,
D0, D1, D2, D3, D4, D5, D6, D7...
1 = MSB is transmitted and received first. The resulting bit order is:
R/W, A13, A12, A11, A10, A9, A8, A7,
A6, A5, A4, A3, A2, A1, A0, Burst,
D7, D6, D5, D4, D3, D2, D1, D0…
Data Bit 6. Bi-directional data bit 6 of the microprocessor interface. Not
driven when CS=1 or RST=0.
D6/
K9 K5 IOz SPI_CPHA (SPI_SEL=1). When in SPI mode, setting this bit to 1 inverts
SPI_CPHA
the phase of the clock signal on SPICK. See Section 2.10 for detailed
timing and functionality information. Default setting is low.
Data Bit 7. Bi-directional data bit 7 of the microprocessor interface. Not
driven when CS=1 or RST=0.
D7/
M9 L5 IOz SPI_CPOL (SPI_SEL=1). When in SPI mode, setting this bit to 1 inverts
SPI_CPOL
the clock signal on SPICK. See Section 2.10 for detailed timing and
functionality information. Default setting is low.
Chip Select. This pin must be taken low for read/write operations. When
CS J8 J3 I
CS is high, the RD/DS and WR signals are ignored.
Read Data Strobe (Intel Mode). The device drives the data bus with the
contents of the addressed register while RD and CS are both low.
RD/DS J9 — I Data Strobe (Motorola Mode). Used to latch data through the
microprocessor interface. DS must be low during read and write
operations.
Write (Intel Mode). The device captures the contents of the data bus on
the rising edge of WR and writes them to the addressed register location.
CS must be held low during write operations.
WR/RW J10 — I Read Write (Motorola Mode). Used to indicate read or write operation.
RW must be set high for a register read cycle and low for a register write
cycle.
Address Latch Enable. This signal is used to internally latch an address,
allowing multiplexing of the parallel interface address and data lines.
When ALE is high, the values of the A[10:0] pins are used for read/write
ALE J7 — I operations. On the falling edge of ALE, the values of the A[10:0] pins are
latched internally, and the latched value is used for read/write operations
until the next rising edge of ALE. ALE should be tied high for non-
multiplexed address systems.
Mode. Selects RD/WR or DS strobe mode.
MODE J12 — I 0 = Read/Write Strobe Mode
1 = Data Strobe Mode
PACKAGE PINS
NAME TYPE FUNCTION
256 144
GMII/MII/RMII PORT
Transmit Data 0 through 7(GMII Mode). TXD[0:7] is presented
synchronously with the rising edge of TX_CLK1. TXD[0] is the least
significant bit of the data. When TX_EN1 is low the data on TXD should
be ignored.
MAC 1 Transmit Data 0 through 3(MII Mode – TXD1[0:3]). Four bits of
TXD[0]/TXD1[0], J13, J8, data TXD1[0:3] presented synchronously with the rising edge of
TXD[1]/TXD1[1], K15, J9, TX_CLK1.
TXD[2]/TXD1[2], J15, H8, MAC 1 Transmit Data 0 through 1(RMII Mode – TXD1[0:1]). Two bits of
TXD[3]/TXD1[3], H13, H9, data TXD1[0:1] presented synchronously with the rising edge of
O
TXD[4]/TXD2[0], N15, L8, TX_CLK1.
TXD[5]/TXD2[1], P15, K8, MAC 2 Transmit Data 0 through 3(MII Mode– TXD2[0:3]).Four bits of
TXD[6]/TXD2[2], R15, L9, data TXD2[0:3] presented synchronously with the rising edge of
TXD[7]/TXD2[3] T15 K9 TX_CLK2. Note that TXD2[0:3] is only available on devices with two
Ethernet ports.
MAC 2 Transmit Data 0 through 1(RMII Mode– TXD2[0:1]). Two bits of
data TXD2[0:1] presented synchronously with the rising edge of
TX_CLK2. Note that TXD2[0:1] is only available on devices with two
Ethernet ports.
MAC 1 Receive Data 0 through 7(GMII Mode). Eight bits of received
data, sampled synchronously with the rising edge of RX_CLK. For every
clock cycle, the PHY transfers 8 bits to the device. RXD[0] is the least
significant bit of the data. Data is not considered valid when RX_DV is
low.
RXD[0]/RXD1[0], G14, J10, MAC 1 Receive Data 0 through 3(MII Mode – RXD1[0:3]). Four bits of
RXD[1]/RXD1[1], F13, J11, received data, sampled synchronously with RX_CLK1. Accepted when
RXD[2]/RXD1[2], F14, H10, RX_CRS1 is asserted.
RXD[3]/RXD1[3], H14, H11,
I MAC 1 Receive Data 0 through 1(RMII Mode – RXD1[0:1]). Two bits of
RXD[4]/RXD2[0], N16, L10,
received data, sampled synchronously with RX_CLK1. Accepted when
RXD[5]/RXD2[1], M16, L11,
RX_CRS1 is asserted.
RXD[6]/RXD2[2], L15, K10,
RXD[7]/RXD2[3] K16 K11 MAC 2 Receive Data 0 through 3(MII Mode – RXD2[0:3]): Four bits of
received data, sampled synchronously with RX_CLK2. Accepted when
RX_CRS2 is asserted.
MAC 2 Receive Data 0 through 1(RMII Mode – RXD2[0:1]). Two bits of
received data, sampled synchronously with RX_CLK2. Accepted when
RX_CRS2 is asserted.
Receive Clock 1 (GMII). 125MHz clock. This clock is used to sample the
RXD[7:0] data.
Receive Clock 1 (MII). Timing reference for RX_DV, RX_ERR and
RXD[3:0], which are clocked on the rising edge. RX_CLK frequency is
25MHz for 100Mbps operation and 2.5MHz for 10Mbps operation. In DTE
RX_CLK1, G16,
J12 IO mode, this is a clock input provided by the PHY.
RX_CLK2 N13
Receive Clock 2 (MII Only). Timing reference for RX_DV2, RX_ERR2 and
RXD2[3:0], which are clocked on the rising edge. RX_CLK2 frequency is
25MHz for 100Mbps operation and 2.5MHz for 10Mbps operation. In DTE
mode, this is a clock input provided by the PHY. Note that RX_CLK2 is
only available on devices with two Ethernet ports.
Transmit Clock 1 (MII). Timing reference for TX_EN1 and TXD1[3:0].
The TX_CLK1 frequency is 25MHz for 100Mbps operation and 2.5MHz
for 10Mbps operation. In DTE mode, this is a clock input provided by the
PHY. Sourced from REF_CLK Input.
TX_CLK1, M15,
L12 IO Transmit Clock 2 (MII Only). Timing reference for TX_EN2 and TXD2[3:0].
TX_CLK2 T16
The TX_CLK2 frequency is 25MHz for 100Mbps operation and 2.5MHz
for 10Mbps operation. In DTE mode, this is a clock input provided by the
PHY. Note that TX_CLK2 is only available on devices with two Ethernet
ports. Sourced from REF_CLK Input.
PACKAGE PINS
NAME TYPE FUNCTION
256 144
Transmit Enable 1(GMII). When this signal is asserted, the data on
TXD[7:0] is valid.
Transmit Enable 1, 2 (MII/RMII). In MII mode, this pin is asserted high
when data TXD[3:0] is being provided by the device. In RMII mode, this
TX_EN1, K14, pin is asserted high when data TXD[1:0] is being provided by the device.
F8 O The signal is deasserted prior to the first nibble of the next frame. This
TX_EN2 P16
signal is synchronous with the rising edge TX_CLK. It is asserted with the
first bit of the preamble.
Note that TX_EN2 is only available on devices with two Ethernet ports.
Unused output pins should not be connected.
Receive Data Valid 1 (GMII). This signal is synchronous to the RX_CLK1
and provides a valid signal for the RXD[7:0].
Receive Data Valid 1, 2 (MII/RMII). This active-high signal indicates valid
RX_DV1, G15, data from the PHY. In MII mode the data RXD[3:0] is ignored if RX_DV is
F9 I
RX_DV2 M11 not asserted high. In RMII mode the data RXD[1:0] is ignored if RX_DV is
not asserted high.
Note that RX_DV2 is only available on devices with two Ethernet ports.
Receive Carrier Sense 1 (GMII). This signal is asserted (high) when data
is valid from the PHY. This signal is asserted by the PHY when either
transmit or receive medium is active. This signal is not synchronous to
RX_CRS1, E13, any of the clocks.
G12 I Receive Carrier Sense 1, 2 (MII). This signal is asserted by the PHY when
RX_CRS2 J14
either transmit or receive medium is active. This signal is not synchronous
to any of the clocks.
Note that RX_CRS2 is only available on devices with two Ethernet ports.
Receive Error 1 (GMII). This signal indicates a receive error or a carrier
extension in the GMII Mode.
Receive Error 1, 2 (MII). Asserted by the MAC PHY for one or more
RX_ERR1, H15, RX_CLK periods indicating that an error has occurred. Active High
G9 I indicates Receive code group is invalid. If RX_CRS is low, RX_ERR has
RX_ERR2 M12
no effect. This is synchronous with RX_CLK. In DCE mode, this signal
must be grounded.
Note that RX_ERR2 is only available on devices with two Ethernet ports.
Transmit Error 1(GMII). When this signal is asserted, the PHY will
respond by sending one or more code groups in error.
TX_ERR1, L14, Transmit Error 1, 2(GMII, MII). When this signal is asserted, the PHY will
G8 O
TX_ERR2 R16 respond by sending one or more code groups in error.
Note that TX_ERR2 is only available on devices with two Ethernet ports.
PACKAGE PINS
NAME TYPE FUNCTION
256 144
Reference Clock Input. REF_CLK must be 125MHz for GMII operation.
REF_CLK T13 M8 I REF_CLK must be 25MHz for MII DCE operation. REF_CLK must be
50MHz for RMII operation.
GbE Transmit Clock Output (GMII). 125MHz clock output available for
GTX_CLK R14 M10 O
GMII operation. This clock is sourced from the 125MHz REF_CLK input.
PHY MANAGEMENT BUS
Management Data Clock. Clocks management data to and from the PHY.
MDC F15 H5 O The clock is derived from SYSCLKI, with a maximum frequency is
1.67MHz.
MII Management Data IO. Data path for control information between the
device and the PHY. Pull to logic high externally through a 1.5 kΩ resistor.
MDIO G13 H4 IO The MDC and MDIO pins are used to write or read up to 32 Control and
Status Registers in PHY Controllers. This port can also be used to initiate
Auto-Negotiation for the PHY.
SDRAM CONTROLLER
SDATA[0] C16 A11
SDATA[1] B16 B11
SDATA[2] B15 D11
SDATA[3] C15 C11
SDATA[4] A14 A10
SDATA[5] C12 B10
SDATA[6] A13 D10
SDATA[7] B13 C10 SDRAM Data Bus Bits 0 through 15. The 16 pins of the SDRAM data
IOz bus are inputs for read operations and outputs for write operations. At all
SDATA[8] D9 C8 other times, these pins are high impedance.
SDATA[9] C9 D8
SDATA[10] D12 B8
SDATA[11] C10 E9
SDATA[12] B10 C9
SDATA[13] B11 D9
SDATA[14] C11 B9
SDATA[15] B12 A9
SDA[0] C3 A3
SDA[1] C2 D2
SDA[2] B2 B2
SDA[3] A2 D1
SDA[4] D3 C1 SDRAM Address Bus 0 through 12. The 13 pins of the SDRAM address
SDA[5] D4 E1 bus output the row address first, followed by the column address. The row
SDA[6] B5 C2 O address is determined by SDA[0] to SDA[12] at the rising edge of clock.
SDA[7] C5 E2 Column address is determined by SDA[0]-SDA[9] and SDA[11] at the
rising edge of the clock. SDA[10] is used as an auto-precharge signal.
SDA[8] D5 B3
SDA[9] B6 A4
SDA[10] A3 C3
SDA[11] C6 B4
SDA[12] A5 D3
SBA[0], SDRAM Bank Select. These 2 bits select 1 of 4 banks for the
B4, B3 D4, C4 I
SBA[1] read/write/precharge operations.
SDRAM Chip Select.All commands are masked when SDCS is registered
SDCS A4 A5 O high. SDCS provides for external bank selection on systems with multiple
banks. SDCS is considered part of the command code.
PACKAGE PINS
NAME TYPE FUNCTION
256 144
SDRAM Row Address Strobe. Active-low output, used to latch the row
SRAS A6 B5 O address on rising edge of SD_CLK. It is used with commands for Bank
Activate, Precharge, and Mode Register Write.
SDRAM Column Address Strobe. Active low output, used to latch the
SCAS B7 D5 O column address on the rising edge of SD_CLK. It is used with commands
for Bank Activate, Precharge, and Mode Register Write.
SDRAM Write Enable. This active low output enables write operation and
SWE A7 C5 O
auto precharge.
SDRAM Upper Data Mask. SD_UDM is an active high output mask
SD_UDM D7 E7 O signal for write data. SD_UDM is updated on both edges of SD_UDQS.
SD_UDM corresponds to data on SDATA15-SDATA8.
SDRAM Lower Data Mask. SD_LDM is an active high output mask signal
SD_LDM D13 E6 O for write data. SD_LDM is updated on both edges of SD_LDQS. SD_LDM
corresponds to data on SDATA7-SDATA0.
Lower Data Strobe. Output with write data, input with read data.
SD_LDQS C13 E8 IOz
SD_LDQS corresponds to data on SDATA7-SDATA0.
Upper Data Strobe. Output with write data, input with read data.
SD_UDQS D8 D7 IOz
SD_UDQS corresponds to data on SDATA15-SDATA8.
SDRAM Clock. SD_CLK and SD_CLK are differential clock outputs. All
address and control input signals are sampled on the crossing of the
SD_CLK A8 A8 O positive edge of SD_CLK and negative edge of SD_CLK. Output (write)
data is referenced to the crossings of SD_CLK and SD_CLK (both
directions of crossing).
SDRAM Clock (Inverted). SD_CLK and SD_CLK are differential clock
outputs. All address and control input signals are sampled on the crossing
SD_CLK A9 A7 O of the positive edge of SD_CLK and negative edge of SD_CLK. Output
(write) data is referenced to the crossings of SD_CLK and SD_CLK (both
directions of crossing).
SDRAM Clock Enable. Active High. SD_CLKEN must be active
SD_CLKEN C4 E5 O
throughout DDR SDRAM READ and WRITE accesses.
SERIAL INTERFACE IO PINS
TDATA1 T6 L3
TDATA2 T7 —
TDATA3 P6 —
TDATA4 N9 —
TDATA5 M5 —
TDATA6 N6 — Transmit Serial Data Output. Output on the rising edge of TCLK. The
TDATA7 N7 — maximum data rate is 52Mbps.
TDATA8 R9 — Not all serial port signals are available on all products in the device family.
O
TDATA9 N10 — Unused output pins should not be connected.
TDATA10 R11 — DS33X41/X42/W41/W11: TDATA5 – TDATA16 not used.
TDATA11 N11 — DS33X81/X82: TDATA9 – TDATA16 not used.
TDATA12 R12 —
TDATA13 P14 —
TDATA14 P12 —
TDATA15 N12 —
TDATA16 P11 —
TCLK1/TMCLK1 R5 M3 I Serial Interface Transmit Clock Input (TCLK[1:8]).The clock reference
for TDATA, which is output on the rising edge of the clock. TCLK supports
TCLK2 P5 — gapped clocking, up to a maximum frequency of 52MHz.
TCLK3 R8 — Note that TCLK1 is also TMCLK1, TCLK5 is also TMCLK2. TMCLK3
and TMCLK4 are stand-alone pins.
TCLK4 P9 —
PACKAGE PINS
NAME TYPE FUNCTION
256 144
TCLK5/TMCLK2 M7 — Transmit Master Clock (TMCLK[1:4]). Input clock that TDATA is
TCLK6 P10 — referenced to. This clock may be gapped. Maximum clock speed is
52MHz. This clock can be inverted.
TCLK7 T10 —
Not all serial port signals are available on all products in the device family.
TCLK8 R10 — Unused input pins should be tied to VSS.
TMCLK3 T11 — DS33X41/X42/W41/W11: TCLK5 – TCLK8 not used.
TMCLK4 M10 —
TSYNC1/
R6 M4
TMSYNC1
TSYNC2 T8 —
Transmit Synchronization Input (TSYNC[1:8]). Input that indicates
TSYNC3 M6 — frame boundaries on TDATA, referenced to TCLK. This signal may be a
frame or multiframe sync. It must be a multiframe sync for VCAT
TSYNC4 P7 — applications. Data is octet aligned to this signal.
Note that TSYNC1 is also TMSYNC1, TSYNC5 is also TMSYNC2.
TSYNC5/
R7 — TMSYNC3 and TMSYNC4 are stand-alone pins.
TMSYNC2
I
Transmit Master Sync (TMSYNC[1:4]). This input indicates frame
TSYNC6 P8 — boundaries on TDATA if selected via LI.TCR.TD_SEL, referenced to
TMCLK1.
TSYNC7 N8 —
Not all serial port signals are available on all products in the device family.
Unused input pins should be tied to VSS.
TSYNC8 T9 —
DS33X41/X42/W41/W11: TSYNC5 – TTSYNC8 not used.
TMSYNC3 T12 —
TMSYNC4 N14 —
RDATA1 D1 J2
RDATA2 G8 —
RDATA3 G4 —
RDATA4 H2 —
RDATA5 F3 —
RDATA6 F2 — Receive Serial Data Input (RDATA[1:16]). Receive Serial data from a
RDATA7 K1 — T1/E1/T3/E3/xDSL Framer. Data input on the rising edge of RCLK.
RDATA8 L1 — Not all serial port signals are available on all products in the device family.
I
RDATA9 K2 — Unused input pins should be tied to VSS.
RDATA10 K3 — DS33X41/X42/W41/W11: RDATA5 – RDATA16 not used.
RDATA11 N1 — DS33X81/X82: RDATA9 – RDATA16 not used.
RDATA12 L4 —
RDATA13 P2 —
RDATA14 R1 —
RDATA15 N3 —
RDATA16 N4 —
PACKAGE PINS
NAME TYPE FUNCTION
256 144
RCLK1 E1 G1
RCLK2 G7 —
RCLK3 G1 —
RCLK4 H4 —
RCLK5 F4 —
Serial Interface Receive Clock Input (RCLK[1:16]). Reference clock for
RCLK6 J1 — receive serial data on RDATA. Gapped clocking is supported, up to the
RCLK7 J5 — maximum RCLK frequency of 52MHz.
RCLK8 J4 —
I Not all serial port signals are available on all products in the device family.
RCLK9 J3 — Unused input pins should be tied to VSS.
RCLK10 J2 —
RCLK11 M2 — DS33X41/X42/W41/W11: RCLK5 – RCLK16 not used.
DS33X81/X82: RCLK9 – RCLK16 not used.
RCLK12 N2 —
RCLK13 L5 —
RCLK14 T1 —
RCLK15 T4 —
RCLK16 R3 —
RSYNC1 F1 J1
RSYNC2 H7 —
RSYNC3 G2 —
RSYNC4 H1 —
RSYNC5 G3 — Receive Frame/Multiframe Synchronization Input (RSYNC[1:16]).
RSYNC6 H3 — Receive Sync that indicates frame boundaries or multiframe boundaries
RSYNC7 N5 — for T1/E1/T3/E3 signals present on RDATA. It must be a multiframe sync
for VCAT applications.
RSYNC8 L2 —
I
RSYNC9 K4 — Not all serial port signals are available on all products in the device family.
RSYNC10 M1 — Unused input pins should be tied to VSS.
RSYNC11 L3 — DS33X41/X42/W41/W11: RSYNC5 – RSYNC16 not used.
RSYNC12 P1 — DS33X81/X82: RSYNC9 – RSYNC16 not used.
RSYNC13 M4 —
RSYNC14 R2 —
RSYNC15 P3 —
RSYNC16 T3 —
VOICE INTERFACE IO PINS - DS33W41 AND DS33W11 ONLY
Transmit Voice Data Input. Input voice data stream containing multiple
TVDATA M5 — I DS0s. Referenced to TVCLK. Disabled when TVDEN is high. This signal
is only available on the DS33W41 and DS33W11.
Transmit Voice Clock Input. Input clock that times TVDATA. May be
TVCLK M7 — I gapped. Maximum clock speed 52MHz. This signal is only available on
the DS33W41 and DS33W11.
Transmit Voice Synchronization Input. Input signal that indicates frame
boundaries on voice data stream (TVDATA), sampled by TVCLK,
TVSYNC R7 — I
frequency of 8 kHz. This signal is only available on the DS33W41 and
DS33W11.
Transmit Voice Data Enable. May be used in place of a gapped TVCLK.
If low, TVDATA is valid. If a gapped TVCLK is used and this signal is not
TVDEN N6 — I
used, tie this input low. This signal is only available on the DS33W41 and
DS33W11.
Receive Voice Data Output. Outputs voice data stream from internal
FIFO using RVCLK. Maximum DS0s is dependent on WAN data rate (T1
RVDATA F2 — O max is 24, E1 is 31). This is a tri-state output, high impedance when
RVDEN is high. This signal is only available on the DS33W41 and
DS33W11.
Receive Voice Clock Input. Receive clock that times RVDATA signal.
RVCLK F3 — I May be gapped. Maximum clock speed 52MHz. This signal is only
available on the DS33W41 and DS33W11.
PACKAGE PINS
NAME TYPE FUNCTION
256 144
Receive Voice Synchronization Input. Receive sync that indicates
RVSYNC F4 — I frame boundaries present on RVDATA – referenced to RVCLK, frequency
of 8 kHz. This signal is only available on the DS33W41 and DS33W11.
Receive Voice Data Enable: May be used in place of a gapped RVCLK.
If low, RVDATA is valid. If gapped RVCLK is used and this signal is not
RVDEN G3 — I
used, tie this input low. This signal is only available on the DS33W41 and
DS33W11.
HARDWARE AND STATUS PINS
High-Impedance Test Enable (Active Low). This signal puts all digital
output and bi-directional pins in the high impedance state when it is low
HIZ H16 F10 I
and JTRST is low. For normal operation tie high. This is an asynchronous
input.
Reset (Active Low). An active low signal on this pin resets the internal
registers and logic. While this pin is held low, the microprocessor interface
RST E8 F2 I
is kept in a high-impedance state. This pin should remain low until power
is stable and then set high for normal operation.
SYSTEM CLOCKS
SYSCLKI E16 E12 I System Clock In: 125MHz, ±100ppm System Clock input.
JTAG INTERFACE
JTAG Reset (Active Low). JTRST is used to asynchronously reset the
test access port controller. After power-up, a rising edge on JTRST will
reset the test port and cause the device I/O to enter the JTAG DEVICE ID
JTRST B1 G4 Ipu
mode. Pulling JTRST low restores normal device operation. JTRST is
pulled HIGH internally via a 10kΩ resistor operation. If boundary scan is
not used, this pin should be held low.
JTAG Clock. This signal is used to shift data into JTDI on the rising edge
JTCLK A1 G3 Ipu
and out of JTDO on the falling edge.
JTAG Data Out. Test instructions and data are clocked out of this pin on
JTDO E2 H2 Oz
the falling edge of JTCLK. If not used, this pin should be left unconnected.
JTAG Data In. Test instructions and data are clocked into this pin on the
JTDI D2 H3 Ipu
rising edge of JTCLK. This pin has a 10kΩ pullup resistor.
JTAG Mode Select. This pin is sampled on the rising edge of JTCLK and
JTMS C1 G2 Ipu is used to place the test access port into the various defined IEEE 1149.1
states. This pin has a 10kΩ pullup resistor.
POWER SUPPLIES
E10, F3,
E12, F11,
E9, F7, H1,
G5, H6,
VDD3.3 I Connect to 3.3V Power Supply
K5, H7,
M8, K12,
P4, M2,
T14 M7
D11,
F1,
E3, E4,
G6,
F12,
G7,
G12,
VDD1.8 H12, I Connect to 1.8V Power Supply
H11,
L1,
H12,
M5,
M3,
M11
R13
PACKAGE PINS
NAME TYPE FUNCTION
256 144
A10,
C7, F6,
F8, F9, F6, F7,
F10, F12,
F11, G11,
F16, J6, J7,
G6, K1, K2, Ground Connection for 3.3V and 1.8V Supplies. Connect to the
VSS I
G9, K6, L6, common supply ground.
H5, M1,
H9, M6,
H10, M9,
M13, M12
R4,
T5
AVDD F5 D12 I Analog PLL Power. Connect to a 1.8V power supply.
AVSS E11 C12 I Analog PLL Ground
B8, E5,
VDD2.5 B1, C6 I SDRAM Digital Power. Connect to a 2.5V power supply.
E7
A11,
A12, A2,
A15, B12,
VDDQ A16, C7, I SDRAM Digital DQ Power. Connect to a 2.5V (±0.2V) .
C14, E4,
D10, E10
D14
B14,
C8, A1, A6,
D6, A12,
VSSQ D15, B6, B7, I SDRAM Digital Ground.
D16, E3,
E15, E11
E6
SDRAM SSTL_2 Reference Voltage for SDRAM. Must equal one-half
VREF B9 D6 I
VDDQ. Can be derived from a resistor-divider.
H6,
F4, F5,
DNC H8, J6, — Do Not Connect. Do not connect these pins.
K3, L2
T2
Notes:
I = Input
Oz = Output, with tri-state
O = Output
IO = Bi-directional pin
Ipu = Input, with pullup
IOz = Bi-directional pin, with tri-state
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
A JTCLK SDA[3] SDA[10] SDCS SDA[12] SRAS SWE SD_CLK SD_CLK VSS VDDQ VDDQ SDATA[6] SDATA[4] VDDQ VDDQ
B JTRST SDA[2] SBA[1] SBA[0] SDA[6] SDA[9] SCAS VDD2.5 VREF SDATA[12] SDATA[13] SDATA[15] SDATA[7] VSSQ SDATA[2] SDATA[1]
SD_CLKE
C JTMS SDA[1] SDA[0] SDA[7] SDA[11] VSS VSSQ SDATA[9] SDATA[11] SDATA[14] SDATA[5] SD_LDQS VDDQ SDATA[3] SDATA[0]
N
D RDATA1 JTDI SDA[4] SDA[5] SDA[8] VSSQ SD_UDM SD_UDQS SDATA[8] VDDQ VDD1.8 SDATA[10] SD_LDM VDDQ VSSQ VSSQ
E RCLK1 JTDO VDD1.8 VDD1.8 VDD2.5 VSSQ VDD2.5 RST VDD3.3 VDD3.3 AVSS VDD3.3 RX_CRS1 COL1 VSSQ SYSCLKI
RXD[1] / RXD[2] /
F RSYNC1 RDATA6 RDATA5 RCLK5 AVDD VSS VDD3.3 VSS VSS VSS VSS VDD1.8 MDC VSS
RXD1[1] RXD1[2]
RXD[0] /
G RCLK3 RSYNC3 RSYNC5 RDATA3 VDD3.3 VSS RCLK2 RDATA2 VSS A8 A10 VDD1.8 MDIO RX_DV1 RX_CLK1
RXD1[0]
TXD[3] / RXD[3] /
H RSYNC4 RDATA4 RSYNC6 RCLK4 VSS DNC RSYNC2 DNC VSS VSS VDD1.8 VDD1.8 RX_ERR1 HIZ
TXD1[3] RXD1[3]
TXD[0] / TXD[2] /
J RCLK6 RCLK10 RCLK9 RCLK8 RCLK7 DNC ALE CS RD / DS WR / RW INT MODE RX_CRS2 SPI_SEL
TXD1[0] TXD1[2]
D0 / D2 / D6 / TXD[1] / RXD[7] /
K RDATA7 RDATA9 RDATA10 RSYNC9 VDD3.3 D4 A0 A2 A6 A4 TX_EN1
SPI_MISO SPI_CLK SPI_CPHA TXD1[1] RXD2[3]
D1 / D5 /SPI_ RXD[6] /
L RDATA8 RSYNC8 RSYNC11 RDATA12 RCLK13 D3 A1 A3 A5 A7 A9 TX_ERR1 COL2
SPI_MOSI SWAP RXD2[2]
D7 / RXD[5] /
M RSYNC10 RCLK11 VDD1.8 RSYNC13 TDATA5 TSYNC3 TCLK5 VDD3.3 TMCLK4 RX_DV2 RX_ERR2 VSS RMII_SEL TX_CLK1
SPI_CPOL RXD2[1]
TXD[4] / RXD[4] /
N RDATA11 RCLK12 RDATA15 RDATA16 RSYNC7 TDATA6 TDATA7 TSYNC7 TDATA4 TDATA9 TDATA11 TDATA15 RX_CLK2 TMSYNC4
TXD2[0] RXD2[0]
TXD[5] /
P RSYNC12 RDATA13 RSYNC15 VDD3.3 TCLK2 TDATA3 TSYNC4 TSYNC6 TCLK4 TCLK6 TDATA16 TDATA14 DCEDTES TDATA13 TX_EN2
TXD2[1]
TXD[6] /
R RDATA14 RSYNC14 RCLK16 VSS TCLK1 TSYNC1 TSYNC5 TCLK3 TDATA8 TCLK8 TDATA10 TDATA12 VDD1.8 GTX_CLK TX_ERR2
TXD2[2]
TXD[7] /
T RCLK14 DNC RSYNC16 RCLK15 VSS TDATA1 TDATA2 TSYNC2 TSYNC8 TCLK7 TMCLK3 TMSYNC3 REF_CLK VDD3.3 TX_CLK2
TXD2[3]
Note: Shaded pins do not apply to all devices in the product family. See the pin listing for specific pin availability. In the high port
count devices, the shaded input pins DO NOT HAVE PULLUP/PUL-DOWN resistors. Consideration must be taken during board
design to bias the inputs appropriately, and to float output pins (TDATA5-TDATA16, TX_EN2, TX_ERR2) if lower port count
designs are to be potentially stuffed with higher port count devices.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
A JTCLK SDA[3] SDA[10] SDCS SDA[12] SRAS SWE SD_CLK SD_CLK VSS VDDQ VDDQ SDATA[6] SDATA[4] VDDQ VDDQ
B JTRST SDA[2] SBA[1] SBA[0] SDA[6] SDA[9] SCAS VDD2.5 VREF SDATA[12] SDATA[13] SDATA[15] SDATA[7] VSSQ SDATA[2] SDATA[1]
SD_CLKE
C JTMS SDA[1] SDA[0] SDA[7] SDA[11] VSS VSSQ SDATA[9] SDATA[11] SDATA[14] SDATA[5] SD_LDQS VDDQ SDATA[3] SDATA[0]
N
D RDATA1 JTDI SDA[4] SDA[5] SDA[8] VSSQ SD_UDM SD_UDQS SDATA[8] VDDQ VDD1.8 SDATA[10] SD_LDM VDDQ VSSQ VSSQ
E RCLK1 JTDO VDD1.8 VDD1.8 VDD2.5 VSSQ VDD2.5 RST VDD3.3 VDD3.3 AVSS VDD3.3 RX_CRS1 COL1 VSSQ SYSCLKI
RXD[1] / RXD[2] /
F RSYNC1 RVDATA RVCLK RVSYNC AVDD VSS VDD3.3 VSS VSS VSS VSS VDD1.8 MDC VSS
RXD1[1] RXD1[2]
RXD[0] /
G RCLK3 RSYNC3 RVDEN RDATA3 VDD3.3 VSS RCLK2 RDATA2 VSS A8 A10 VDD1.8 MDIO RX_DV1 RX_CLK1
RXD1[0]
TXD[3] / RXD[3] /
H RSYNC4 RDATA4 RCLK4 VSS DNC RSYNC2 DNC VSS VSS VDD1.8 VDD1.8 RX_ERR1 HIZ
TXD1[3] RXD1[3]
TXD[0] / TXD[2] /
J DNC ALE CS RD / DS WR / RW INT MODE SPI_SEL
TXD1[0] TXD1[2]
D0 / D2 / D6 / TXD[1] / RXD[7] /
K VDD3.3 D4 A0 A2 A6 A4 TX_EN1
SPI_MISO SPI_CLK SPI_CPHA TXD1[1] RXD2[3]
D1 / D5 /SPI_ RXD[6] /
L D3 A1 A3 A5 A7 A9 TX_ERR1
SPI_MOSI SWAP RXD2[2]
D7 / RXD[5] /
M VDD1.8 TVDATA TSYNC3 TVCLK VDD3.3 VSS RMII_SEL TX_CLK1
SPI_CPOL RXD2[1]
TXD[4] / RXD[4] /
N TVDEN TDATA4
TXD2[0] RXD2[0]
TXD[5] /
P VDD3.3 TCLK2 TDATA3 TSYNC4 TCLK4 DCEDTES
TXD2[1]
TXD[6] /
R VSS TCLK1 TSYNC1 TVSYNC TCLK3 VDD1.8 GTX_CLK
TXD2[2]
TXD[7] /
T DNC RCLK15 VSS TDATA1 TDATA2 TSYNC2 REF_CLK VDD3.3
TXD2[3]
Note 1: Shaded pins do not apply to all devices in the product family. See the pin listing for specific pin availability.
Note 2: The TVDEN pin is an input on the DS33W41/DS33W11, and is an output pin on other devices in the product family.
1 2 3 4 5 6 7 8 9 10 11 12
A VSS VDDQ SDA[0] SDA[9] SDCS VSS SD_CLK SD_CLK SDATA[15] SDATA[4] SDATA[0] VSS
B VDD2.5 SDA[2] SDA[8] SDA[11] SRAS VSS VSS SDATA[10] SDATA[14] SDATA[5] SDATA[1] VDDQ
C SDA[4] SDA[6] SDA[10] SBA[1] SWE VDD2.5 VDDQ SDATA[8] SDATA[12] SDATA[7] SDATA[3] AVSS
D SDA[3] SDA[1] SDA[12] SBA[0] SCAS VREF SD_UDQS SDATA[9] SDATA[13] SDATA[6] SDATA[2] AVDD
E SDA[5] SDA[7] VSS VDDQ SD_CLKEN SD_LDM SD_UDM SD_LDQS SDATA[11] VDDQ VSS SYSCLKI
F VDD1.8 RST VDD3.3 DNC DNC VSS VSS TX_EN1 RX_DV1 HIZ VDD3.3 VSS
G RCLK1 JTMS JTCLK JTRST INT VDD1.8 VDD1.8 TX_ERR1 RX_ERR1 COL1 VSS RX_CRS1
H VDD3.3 JTDO JTDI MDIO MDC VDD3.3 VDD3.3 TXD[2] TXD[3] RXD[2] RXD[3] VDD1.8
J RSYNC1 RDATA1 CS SPI_MISO SPI_SWAP VSS VSS TXD[0] TXD[1] RXD[0] RXD[1] RX_CLK1
K VSS VSS DNC SPI_MOSI SPI_CPHA VSS RMII_SEL TXD[5] TXD[7] RXD[6] RXD[7] VDD3.3
L VDD1.8 DNC TDATA1 SPI_CLK SPI_CPOL VSS DCEDTES TXD[4] TXD[6] RXD[4] RXD[5] TX_CLK1
M VSS VDD3.3 TCLK1 TSYNC1 VDD1.8 VSS VDD3.3 REF_CLK VSS GTX_CLK VDD1.8 VSS
Note that the parallel bus is not available in the 144-pin DS33X11, and the SPI slave port must be used for processor control.
8. Functional Description
The DS33X162 family of devices provide interconnection and mapping functionality between Ethernet Systems and
WAN Time-Division Multiplexed (TDM) systems such as T1/E1/J1, HDSL, T3/E3, and SONET/SDH. The device is
composed of up to two 10/100/1000 Ethernet MACs, up to 16 Serial Ports, a Arbiter, GFP/HDLC/cHDLC/X.86
(LAPS) Mappers, a DDR SDRAM interface, and control ports.
Ethernet traffic is encapsulated with GFP-F, HDLC, cHDLC, or X.86 (LAPS) to be transmitted over the WAN Serial
Interfaces. The WAN Serial Interfaces also receive encapsulated Ethernet frames and transmit the extracted
frames over the Ethernet ports.
The LAN interface consists of Ethernet MACs using one of two physical layer protocols. The interface can be
configured with up to two 10/100Mbps MII/RMII ports or a single GbE GMII port. The MII/RMII and GMII interfaces
allow connection to commercially available Ethernet PHY and MAC devices.
The WAN physical interface supports 8 serial data streams up to 52Mbps each. The DS33X162 and DS33X161
support an additional 8 serial data streams with data rates up to 2.5Mbps each. The WAN serial interfaces receive
encapsulated Ethernet frames and transmit the extracted frames over the Ethernet ports. The WAN serial ports can
operate with a gapped clock, and can be connected to a framer, electrical LIU, optical transceiver, or T/E-Carrier
transceiver for transmission to the WAN. The Serial Interfaces can be seamlessly connected to the Maxim
T1/E1/J1 Framers, Line Interface Units (LIUs), and Single-Chip Transceivers (SCTs). The WAN interfaces can also
be seamlessly connected to the Maxim T3/E3/STS-1 Framers, LIUs, and SCTs to provide T3, E3, and STS1
connectivity.
Ethernet frames are queued and stored in an external 32-bit DDR SDRAM. The DDR SDRAM controller enables
connection to a 256Mb SDRAM without external glue logic, at clock frequencies up to 125MHz. The SDRAM is
used for the LAN Data, WAN Data, Frame Extraction, and Frame Insertion Queues. The user can program a “near
full threshold” (watermark) for the LAN and WAN queues that can be used to initiate automatic flow control. The
43
device also provides the capability for X +1 payload and Barker sequence scrambling.
Microprocessor control can be accomplished through a 8-bit Micro controller port or SPI Bus. The device has a
125MHz DDR SDRAM controller and interfaces to a 32-bit wide 256Mb DDR SDRAM via a 16-bit data bus. The
DDR SDRAM is used to buffer data from the Ethernet and WAN ports for transport.
The power supplies consist of a 1.8V core supply, a 2.5V DDR SDRAM supply, and 3.3V I/O supply.
The processor interface can operate in either read-write strobe mode or data strobe mode. When MODE = 0 the
read-write strobe mode is enabled and a negative pulse on RD performs a read cycle, and a negative pulse on WR
performs a write cycle. When MODE pin = 1, the data strobe mode is enabled and a negative pulse on DS when
RW is high performs a read cycle, and a negative pulse on DS when RW is low performs a write cycle. The read-
write strobe mode is commonly called the “Intel” mode, and the data strobe mode is commonly called the
“Motorola” mode.
The latched status registers will clear on a read access. It is important to note that in a multi-task software
environment, the user should handle all status conditions of each register at the same time to avoid inadvertently
clearing status conditions. The latched status register bits are carefully designed so that an event occurrence
cannot collide with a user read access.
The interrupt (INT) pin is configurable to drive high or float when not active. The GL.CR2.INTM bit controls the pin
configuration, when it is set to 1, the INT pin will drive high when inactive. After reset, the INT pin is in high
impedance mode until an interrupt source is active and enabled to drive the interrupt pin.
An address latch enable [ALE] pin is provided to allow for multiplexing of the data and address signals. For
multiplexed operation, each of the eight data lines (D0-D7) must be externally connected to each of the lower eight
address lines (A0-A7). The remaining address lines (A8-A10) are connected as normal. Address inputs are latched
upon the falling edge of the ALE signal. ALE must remain low until the read or write operation is complete.
SPI_CLK
SPI μP Port
CLAD
SYSCLKI
TCLK1
TRANSMIT SERIAL
CONTROLLER
(MII MODE)
PORT 1
CIR/CBS
QoS
HDLC/cHDLC
TCLK2 TRANSMIT SERIAL RX_CLK
VCAT/LCAS
ETHERNET MAC1
GFP/X.86/
BRDIGE/FILTER
PORT 2
ETHERNET
TX_CLK
TMCLK4 TRANSMIT SERIAL
PORT 16
MDC
ARBITER/ Add/Drop
BUFFER MANAGER OAM Frames (MII MODE)
ETHERNET MAC2(X162/82/42)
RCLK1 RX_CLK
RECEIVE SERIAL
BRDIGE/FILTER
ETHERNET
PORT 1
HDLC/cHDLC
VCAT/LCAS
TX_CLK
PORT 2
MDC
RCLK16 RECEIVE SERIAL
PORT 16
JTAG
RVCLK
SD_CLK
SD_CLK
Serial Interface timing is determined by the line clocks. Both the transmit and receive clocks (TCLK and RCLK) are
inputs, and can be gapped.
The Ethernet interfaces can be configured for MII, RMII, or GMII operation with the GL.CR1.P1SPD,
GL.CR1.P2SPD, SU.MACCR.GMIIMIIS bits and the RMII_SEL input pin. See Table 8-1 for details of the clock
requirements for the various Ethernet Interface configurations.
There are several features included to reduce power consumption. The reset bits of the LI.RCR1.RFRST,
LI.RVPCR.RVRST, LI.TVPCR.TVFRST, and VCAT.RCR4.RFRST registers also place the associated circuitry in a
low-power mode. Additionally, the RST pin may be held low indefinitely to keep the entire device in a low-power
mode. Note that exiting the low-power condition requires re-initialization and configuration.
Block Enables
SU.LP1C.LP1E LAN Port 1 Enable
SU.LP2C.LP2E LAN Port 2 Enable
VCAT.TCR1.TVBLKEN Transmit VCAT Enable
VCAT.RCR1.RVBLKEN Receive VCAT Enable (Global)
VCAT.RCR1.RVEN1-RVEN4 Receive VCAT Enable (Per WAN Group)
LI.TVPCR.TPE Transmit Voice Port Enable
LI.RVPCR.RPE Receive Voice Port Enable
SU.BFC.BFE Bridge Filter Enable
SU.LP1C
MAC 1 SU.MMCRSR SU.MMCRIM
(MAC1) (MAC1)
Status / Interrupt Register /
Source Bit Name
RCV LAN 2 SU.LIQOS
SU.LP2C
Interrupt Enable/ Register /
MAC 2 SU.MMCRSR SU.MMCRIM Mask Registers Bit Name
(MAC2) (MAC2)
ENCAPSULATOR
PP.ESMLS[1-4] PP.ESMIE[1-4]
DECAPSULATOR PP.DMLSR[1-4] PP.DMLSIE[1-4]
0 RXLANIS
XMT SERIAL LI.TVFLSR LI.TVFSRIE 1 TXLANIS
2 ECIS1
3 DECIS1
ARBITER AR.LQOS AR.LQOIM 4 TSPIS
Interrupt Pin
AR.WQOS AR.WQOIM 5 -
AR.BMIS
GL.ISR
GL.IER
7 -
AR.WQNFS AR.WQNFIM
8 RVCATIS
AR.EQOS AR.EQOIM 9 ECIS2
10 ECIS3
RCV VCAT VCAT.RSLSR[1-16] VCAT.RSIE[1-16] VCAT.RISR 11 ECIS4
12 DECIS2
VCAT.RRLSR VCAT.RRSIE
13 DECIS3
14 DECIS4
MICROPORT GL.MLSR3 GL.MSIER3 15 MICIS
The set of rules that determine the route of frames between the Ethernet Interface(s) and WAN data stream(s) is
called the Forwarding Mode. The forwarding mode is selected in the GL.CR1 register. The five Forwarding Modes
are listed below. The connections between the Serial (WAN) Interfaces and the logical WAN data streams
described below are independent of these Forwarding Modes and will be described later. See Table 8-4 for
forwarding modes supported by each device.
Mode 1 - Single Ethernet Port with Priority Forwarding
Mode 2 - Per-Ethernet-Port Forwarding with Priority Scheduling
Mode 3 - Single Ethernet Port with VLAN Forwarding and Priority Scheduling
Mode 4 - Per-Ethernet-Port Forwarding, with VLAN Forwarding and Priority Scheduling within each VLAN group
Mode 5 – Full VLAN Forwarding in both the LAN-to-WAN and WAN-to-LAN directions.
Forwarding Mode 1 is Single Ethernet Port with Priority Forwarding. In this mode, Ethernet frames are segregated
into up to four priority queues and transmitted in separate WAN data streams. One example application is an
Ethernet Switch that forwards its traffic according to each frame’s priority encoding, as in an IP DSLAM or ISAM
that has a WAN connection with a VoIP Gateway on WAN Interface #1, a Video Stream device on WAN Interface
#2, and an internet POP on WAN Interface #3.
Forwarding Mode 2 is Per-Ethernet-Port Forwarding with Priority Scheduling. In this mode, frames from each
Ethernet port are forwarded to their own group of four priority queues, generating two separate WAN data streams
with priority scheduled traffic. One example application is a Leased Line Service for two independent Ethernet
subscribers. Each subscriber pays its own leased line fee and is guaranteed the full bandwidth of the WAN line
from end to end. This is the only mode that supports 1000Mbps Jumbo Frames (must use single Ethernet port
operation).
Forwarding Mode 3 is Single Ethernet Port with VLAN Forwarding and Priority Scheduling. In this mode, Ethernet
frames are forwarded by VLAN tag (VID) into up to four groups of four priority queues (WAN Groups) each. Each
WAN Group forms a separate WAN data stream with priority scheduled traffic. One example application is an
Service Router that is connected to four IP DSLAMs via DS3s. In the LAN-to-WAN direction, VLAN IDs are used to
distinguish the forwarding path while Priority coding is used to schedule the selection of frames within a Queue
Group.
Forwarding Mode 4 is Per-Ethernet-Port Forwarding, with VLAN Forwarding and Priority Scheduling within each
VLAN Group. In this mode, Ethernet frames from each Ethernet port are forwarded separately, by VLAN tag, into
two sets of four priority queues (WAN Groups) each. The two WAN Groups form separate WAN data streams with
priority scheduled traffic. One example application is 2 Leased Lines for 2 independent Ethernet subscribers (one
route might go to Chicago and the other to Santa Clara). VLAN tagging is used to segregate the traffic bound for
each route, and Priority coding can be used to provide prioritized scheduling within a VLAN group.
Forwarding Mode 5 is Full VLAN Forwarding in both the LAN-to-WAN and WAN-to-LAN directions. In this mode,
Ethernet frames from both ports can be forwarded by VLAN tag (VID) to one of two shared WAN groups. Within
each shared WAN group, there are two sets of four strict priority queues. The two sets of strict priority queues are
serviced with a round-robin algorithm. Frames are then encapsulated by Encapsulator #1 or #3. Frames received
from the WAN side can be forwarded by VLAN tag to either Ethernet port. The LAN-to-WAN and WAN-to-LAN
mappings are independent and can be configured separately. One example application is Central Office traffic
grooming where the time sensitive voice and video are segregated from a network and combined with other data
streams of similar priority.
Figure 8-3. Forwarding Mode 1: Single Ethernet Port with Priority Forwarding
Encapsulator 1
WAN Ports LAN Queue 1
Priority 1
Serial
Port 1 WAN
Encapsulator 2
Serial LAN Queue 5 Frames from the
Port 3 Priority 2 Ethernet Interface LAN Ports
Serial WAN are forwarded to
Port 4 the LAN Queues
Group 2
Serial based on Priority
Port 5 (802.1p or DSCP).
Encapsulator 3
LAN Queue 9
Serial
Ethernet MAC 1
Priority 3
Port 6 TRANSMIT:
Serial The 16 Serial Ports WAN
Port 7 are assigned to the Group 3
Serial four Encapsulator
Encapsulator 4
Bridge / Filter
Serial VCAT.TCR3.TVGS Priority 4
LAN Trap
Port 9
WAN
QoS
Serial
RECEIVE: Group 4
Port 10
Serial The 16 Serial Ports
Port 11 are assigned to the Priority Lookup Table
LAN Insert
four Decapsulator Queue
Serial Frames toward
WAN Groups with WAN Insert LAN Extract
Port 12 the Ethernet
Queue Queue
Serial VCAT.RCR4.RVGS Interface
Port 13 are forwarded
Serial based on the
Port 14 WAN Extract order of
Queue receipt.
Serial
Port 15
Serial
Port 16 Decapsulator #1 WAN Trap
VCAT/LCAS
Processor
Figure 8-4. Forwarding Mode 2: One or Two Ethernet Port Forwarding with Scheduling
Encapsulator 1
WAN Ports LAN Queue 1
QoS
Priority 1
Serial LAN Queue 2-P2
Port 1 WAN
Bridge / Filter
Port 4
LAN Trap
Serial
Port 5
Encapsulator 3
QoS
Serial Ethernet Interfaces
Ethernet MAC 1
Priority 1
Port 6 TRANSMIT: are forwarded to
LAN Queue 10-P2
Serial The 16 Serial Ports WAN LAN Queue 11-P3 the WAN groups
Port 7 are assigned to the Group 3 LAN Queue 12-P4 based on physical
Serial four Encapsulator port, then
Port 8 WAN Groups with scheduled by
Serial VCAT.TCR3.TVGS Priority (802.1p
Port 9 or DSCP).
Serial
Port 10 RECEIVE:
Serial The 16 Serial Ports
Port 11 are assigned to the Priority Lookup Table
LAN Insert
four Decapsulator Queue
Serial
WAN Groups with WAN Insert LAN Extract
Port 12 Queue Queue
Serial VCAT.RCR4.RVGS
Port 13
Serial
Ethernet MAC 2
Port 14 WAN Extract Frames toward
Serial Queue the Ethernet
Port 15 Interface are
Serial forwarded based
Port 16 Decapsulator #1 WAN Trap on the physical
port.
VCAT/LCAS
Processor
Receive
* Note that Forwarding Mode 2 is the only forwarding mode available in the DS33X11.
Figure 8-5. Forwarding Mode 3: Single Ethernet Port with LAN-VLAN Forwarding
Encapsulator 1
WAN Ports LAN Queue 1
QoS
Priority 1
Serial LAN Queue 2-P2
Port 1 WAN
Encapsulator 2
Serial LAN Queue 5
QoS
Port 3 Priority 1
LAN Ports
Serial WAN
LAN Queue 6-P2
LAN Queue 7-P3
Port 4
Group 2 LAN Queue 8-P4
Serial
Port 5
Encapsulator 3
LAN Queue 9
Serial
Ethernet MAC 1
QoS
Priority 1 Frames from the
Port 6 TRANSMIT:
Serial The 16 Serial Ports WAN
LAN Queue 10-P2 Ethernet Interface
LAN Queue 11-P3
Port 7 are assigned to the Group 3 LAN Queue 12-P4 are forwarded to
four Encapsulator the WAN groups
VLAN Processing
Serial
based on VLAN
Encapsulator 4
Bridge / Filter
VCAT.TCR3.TVGS Priority 1 Tag, then
Serial
LAN Trap
scheduled by
Port 9 LAN Queue 14-P2
WAN LAN Queue 15-P3
QoS
Priority
Serial
RECEIVE: Group 4 LAN Queue 16-P4
Port 10
Serial The 16 Serial Ports
Port 11 are assigned to the Priority Lookup Table
LAN Insert
four Decapsulator Queue
Serial
WAN Groups with WAN Insert LAN Extract
Port 12 Queue Queue
Serial VCAT.RCR4.RVGS
Port 13 VLAN (VID)
Serial
Lookup Table Frames
Port 14 WAN Extract toward the
Serial Queue Ethernet
Port 15 Interface are
Serial forwarded based
Port 16 Decapsulator #1 WAN Trap on the order of
VLAN Processing
receipt.
VCAT/LCAS
Processor
Figure 8-6. Forwarding Mode 4: 1 Ethernet port with Port ID and LAN-VLAN Forwarding
Encapsulator 1
WAN Ports LAN Queue 1
QoS
Priority 1
Serial LAN Queue 2-P2
Port 1 WAN
Encapsulator 2
Serial LAN Queue 5
QoS
Port 3 Priority 1
LAN Ports
Serial WAN
LAN Queue 6-P2
Port 4 LAN Queue 7-P3 Frames
Group 2 LAN Queue 8-P4
from the Ethernet
Serial
Port 5 Interfaces are
Encapsulator 3
LAN Queue 9
Serial forwarded to the
QoS
Ethernet MAC 1
Priority 1
Port 6 TRANSMIT: WAN groups based
LAN Queue 10-P2
Serial The 16 Serial Ports WAN LAN Queue 11-P3
on physical port,
Port 7 are assigned to the Group 3 LAN Queue 12-P4 then by VLAN Tag,
four Encapsulator and are scheduled
VLAN Processing
Serial
Encapsulator 4
Bridge / Filter
Serial VCAT.TCR3.TVGS Priority 1 (802.1p or
LAN Trap
Port 9 LAN Queue 14-P2 DSCP).
WAN LAN Queue 15-P3 QoS
Serial
RECEIVE: Group 4 LAN Queue 16-P4
Port 10
Serial The 16 Serial Ports
Port 11 are assigned to the Priority Lookup Table
LAN Insert
four Decapsulator Queue
Serial
WAN Groups with WAN Insert LAN Extract
Port 12 Queue Queue
Serial VCAT.RCR4.RVGS
Port 13 VLAN (VID)
Lookup Table
Serial
Ethernet MAC 2
Port 14 WAN Extract Frames
Queue toward
Serial
Port 15 the Ethernet
Serial Interface are
Port 16 Decapsulator #1 WAN Trap forwarded based
VLAN Processing
VCAT/LCAS
on physical port, in
Processor
order of receipt.
Decapsulator #3 WAN Trap
Figure 8-7. Forwarding Mode 5: Full LAN-to-WAN and WAN-to-LAN VLAN Forwarding
QoS
Priority 1
Serial each pair of WAN
groups are LAN Queue 2-P2
Encapsulator 1
Port 1 WAN
QoS
Port 3 Priority 1
LAN Ports
Serial WAN
LAN Queue 6-P2
LAN Queue 7-P3
Port 4
Group 3 LAN Queue 8-P4 Frames from
Serial
Port 5 MAC 1 are sent to
LAN Queue 9 WAN groups 1 or 2
Serial
QoS
Ethernet MAC 1
Priority 1 based on VID.
Port 6 TRANSMIT:
LAN Queue 10-P2 Frames from MAC 2
Encapsulator 3
VLAN Processing
Serial
Port 8 WAN Groups with LAN Queue 13 are scheduled
Bridge / Filter
VCAT.TCR3.TVGS Priority 1 by Priority
Serial
LAN Trap
Port 9 LAN Queue 14-P2
(802.1p or
WAN LAN Queue 15-P3 DSCP)
Serial QoS
RECEIVE: Group 4 LAN Queue 16-P4
Port 10
Serial The 16 Serial Ports
Port 11 are assigned to the Priority Lookup Table
LAN Insert
four Decapsulator Queue
Serial
WAN Groups with WAN Insert LAN Extract
Port 12 Queue Queue
Serial VCAT.RCR4.RVGS
Port 13 VLAN (VID)
Lookup Table
Serial
Ethernet MAC 2
Port 14 WAN Extract
Queue Frames
Serial
toward
Port 15
the Ethernet
Serial
Interface are
Port 16 Decapsulator #1 WAN Trap
VLAN Processing
forwarded based
VCAT/LCAS
Processor
The user may choose to disable unused features in a forwarding mode. In the forwarding modes with Priority
Forwarding or Priority Scheduling, both 802.1p VLAN PCP and DSCP are supported. The user-programmable
Priority Table is accessed through the SU.PTC, SU.PTAA, SU.PTWD, SU.PTRD, and SU.PTSA registers. The
Priority and Quality of Service (QoS) features of the device are discussed further in Section 8.16. Gigabit Ethernet
applications may only use Forwarding modes that support 1 Ethernet Port (modes 1, 2, or 3). In all forwarding
modes, VCAT/LCAS can be used to aggregate multiple physical serial ports for each WAN Group’s data stream,
except on the devices in the product family that do not support VCAT/LCAS. More information on the use of
VCAT/LCAS for link aggregation can be found in Section 8.12.
In the forwarding modes that use VLAN VID tags, the device references a user-programmable lookup table to
make forwarding decisions. Through the SU.VTC, SU.VTAA, SU.VTWD, and SU.VTRD registers, the user must
program a lookup table that maps up to 4096 VLAN VID tags each to one of the four WAN Groups in the LAN-to-
WAN direction, and from the WAN Groups to the two Ethernet Interfaces in the WAN-to-LAN direction. More
information on VLAN mapping can be found in Section 8.16. Within each WAN Queue group, 802.1p VLAN Priority
coding or DSCP Priority Coding can be used to assign traffic to 4 different priority queues. More information on
priority forwarding and scheduling for quality of service can be found in Section 8.16.
Each Serial (WAN) Interface is mapped to a WAN Group through the VCAT.TCR3(1-16) and VCAT.RCR4(1-16)
registers. A WAN interface can only be assigned to one WAN Group. In devices in the product family that support
VCAT operation, if enabled, more than one WAN interface can be assigned to a WAN Group. Whenever a WAN
Group has more than one member, VCAT must be enabled for that group. A VCAT enabled WAN Group can
include up to 16 WAN Interfaces. More information on the use of VCAT/LCAS for link aggregation can be found in
Section 8.12.
The starting and ending locations for each queue in DDR SDRAM are user-configured. The address space of a 256
Mbit DDR SDRAM is 24-bits, providing an address range covering 16M 16-bit words. To reduce the complexity of
the user interface, only the upper 10 bits of each start/end queue address are user-configured. This provides a
minimum queue size granularity of 16K 16-bit words, or 32 Kbytes. The 10-bit values programmed into the queue
configuration registers can be multiplied by 32,768 in order to convert to bytes.
Each Serial (WAN) interface has an associated receive WAN Queue in external DDR SDRAM. The WAN Queues
receive data from the WAN interfaces and buffer it for processing. The user configures the size and location of
these queues through control registers in the Arbiter. Starting WAN queue addresses are configured in
AR.WQ1SA-AR.WQ16SA, and ending addresses in AR.WQ1EA-AR.WQ16EA. When using VCAT/LCAS, the
WAN queues are also used for differential delay compensation between members of a VCG. The user-configured
depth of these queues should provide for approximately 200 ms of data at the WAN line rate. This translates to
approximately 10Mb at a 52Mbps rate, and 300kb at 1.544Mbps. While it is possible to configure larger WAN
queues, note that limitations of the VCAT protocol only allow the resolution of 200ms at the line rate, and aliasing
may occur at larger WAN queue depths.
Data from the LAN interface is received into an internal buffer monitored by the SU.LIQOS.LIQOS bits. It is then
immediately processed and placed into one of 16 LAN Queues in external SDRAM, based on the forwarding mode
and information within the frame. Starting WAN queue addresses are configures in AR.LQ1SA-AR.WQ16SA and
ending addresses are configured in AR.LQ1EA-AR.LQ16EA.
The user defines a LAN queue threshold (watermark) that is used to trigger Ethernet flow control or device
interrupts in the AR.LQW register. Because WAN standards do not have a method for interactive flow-control, the
WAN queues do not have user-programmable watermark. The device provides overflow status for the WAN
queues in AR.WQOS and for the LAN queues in AR.LQOS. The device provides an indication that frame
discarding has been triggered due to the level of the WAN queues in AR.WQNFS. The interrupt operation related
to these functions is further defined in Section 8.8.
There are also four special-purpose external SDRAM queues used for frame insertion and extraction. The user
configures the size and location of these through control registers in the Arbiter. The LAN Insert queue is defined
by AR.LIQSA and AR.LIQEA. The LAN Extract Queue is defined by AR.LEQSA and AR.LEQEA. The WAN insert
queue is defined by AR.WIQSA and AR.WIQEA. The WAN Extract queue is defined by AR.WEQSA and
AR.WEQEA. Overflow status for the extraction queues is provided in AR.EQOS
An additional portion of the external SDRAM must be allocated for the Bridge/Filter function when in use. The 4k x
6-byte table used for DA lookup operations will be constructed at the location in the AR.BFTOA register.
The device does not provide error indication if the user creates a connection and queue that overwrites
data for another connection queue. The user must take care in setting the queue sizes.
The LAN and WAN queue pointers must be reset before traffic flow can begin. If this procedure is not followed,
incorrect data may be transmitted. The proper procedure for setting up a connection follows:
• Set up the queue sizes for both LAN and WAN queues.
• Set up the LAN Queue threshold and associated interrupt enables if desired.
• Reset the pointers for the associated queues
• Enable the associated ports.
• If a port is disconnected, reset the queue pointer after the disconnection.
Each queue can be individually reset as needed through the starting address register for that queue. All queue
pointers can be reset simultaneously through the AR.MQC register. This register also configures the behavior of
the WAN frame insertion.
Two scheduling algorithms can be used for prioritizing traffic to be transmitted from the LAN queues to the WAN
interface: Strict Priority and Weighted Round-Robin (WRR). WRR scheduling is available only in Forwarding Mode
2, with one Ethernet port. This is configured in the AR.LQSC register.
Table 8-5. Maximum Number of T3/E3 Lines Per Encapsulator (DS33X162 and DS33X82 Only)
Attempting operation of the DS33X162 or DS33X82 outside of these constraints may cause data loss. If the user
wishes to operate outside of the device’s designed capabilities, it is recommended that the user evaluate the
device performance under the specific application conditions and determine if the measured performance is
acceptable.
Note that the WAN Groups support the following rates:
• Maximum data rate for WAN Groups 1 and 2 = up to 416Mbps total (Group 1 + Group 2 ≤ 418Mbps)
• Maximum data rate for WAN Groups 3 and 4 = 180Mbps each
Note that the individual WAN ports support the following rates:
• Maximum line rate for WAN ports 1-8 = 52Mbps each
• Maximum line rate for WAN ports 9-16 = 2.044Mbps each
Voice demuxing is done on Frame Sync boundaries, with a programmable number of octets (with a maximum of
16) to be demuxed to the Voice FIFO. These are the octets immediately following the Frame Sync boundary. Voice
octets are read from Voice FIFO one frame later after written to FIFO.
Voice Muxing occurs on Frame Sync boundaries and a programmable number of octets(with a maximum of 16) are
read from the Voice FIFO. These octets will appear on TDATA immediately following the TMSYNC/TSYNC signal.
C5 C6 C7 C8 0 1 1 1
C5 C6 C7 C8 0 1 1 1
VCAT/LCAS setup requires an external Micro to issue an instruction to setup and tear down the IMUX function.
The microprocessor can turn off links that are not participating. Once any changes to the transmit VCAT
configuration are made, a zero-to-one transition on VCAT.TCR1.TLOAD is required in order to load the updated
configuration.
The Link Capacity Adjustment Scheme (LCAS) provides the capability to add and remove members from a VCAT
VCG. If LCAS is enabled viaVCAT.RCR2.LE[3:0], the receive LCAS block will extract all LCAS frame information
from the VCAT overhead. The LCAS status registers report the CTRL, GID, RS-ACK, and MST fields of the VCAT
frame. The LCAS CTRL field communicates the intent to add or remove a member from the group. The device
coordinates the addition or removal of links from the group of active members so that changes are hitless.
The transmit MST values are automatically controlled by the device by default. Optionally, this function can be
controlled by user software via the VCAT.TLCR3–VCAT.TLCR6 registers. The Transmit MST field communicates
the condition of the line (e.g., an LOM alarm), the reception of an Add command (and subsequent successful
alignment to the VCG), and the reception of a Remove command.
To enable Transmit LCAS, follow the initialization steps outlined in Section 8.12.2.2. Note that the
VCAT.TLCR8.CTRL[3:0] bits should be initialized with a CTRL command of IDLE. All changes to the CTRL[3:0]
register bits must be followed with a zero-to-one transition on VCAT.TCR1.TLOAD for the change to take effect.
1. Initial CTRL command of IDLE, SQ value = max (16 for T1/E1, 8 for T3/E3)
2. Addition of Member:
a. Send ADD command, Change SQ value to 1+ SQ value(active link with the highest SQ)
b. Wait for MST=OK on Receive LCAS (VCAT.RLSR1 register)
c. Send EOS on this port; Port that was sending EOS now sends NORM
3. Removal of Member
a. Change command from NORM/EOS to IDLE; Change SQ value to max; Reorder other active
members’ SQ; If change was from EOS to IDLE, then next highest member changes from NORM
to EOS
4. Response to Receive LCAS reporting MST=FAIL
a. If the Receive LCAS reports that a MST value changed from OK to FAIL, the Transmit LCAS
should send DNU on that port.
b. The SQ value remains the same.
c. If the member that changes to DNU was EOS, EOS must be assigned to the member next in line.
The latched status bits for the VCAT/LCAS sequence (VCAT.RSLSR.SQL), control (VCAT.RSLSR.CTRL) and
RS-Ack (VCAT.RSLSR.RSACKL) bits can be used to generate device interrupts on a change of state.
The latched Loss of Multiframe Sync (VCAT.RSLSR.LOML), Realign (VCAT.RRLSR.REALIGN[1-4]) and
Differential Delay (VCAT.RRLSR.DDE[1-4]) bits can be used to generate an interrupt upon transition from the
inactive (normal) to the active (alarm) state. If the user’s application requires an indication of the transition from the
active to inactive condition, the host processor should poll the (non-latched) status bits to determine when the
alarm becomes inactive.
Automatic flow control is governed by the LAN Queue high watermark in AR.LQW, and is enabled per LAN Queue
in the SU.LQXPC register. This allows the user to enable or disable flow control for each of the four mapped
PCP/DSCP priorities. When the LAN queue threshold is exceeded on which flow control is enabled, the device will
send a pause frame with the timer value programmed in SU.MACFCR.PT[15:0] when in full duplex, or a jamming
signal in half duplex. More information on configuring the queues, see Section 8.9.3. Also see the SU.MACFCR
register definition for recommended flow control settings.
The pause frame causes the distant transmitter to “pause for a time” before starting transmission again. The device
will send a pause frame as the queue has crossed the threshold defined in AR.LQW. The pause control frame is
retransmitted every 16.4us, 164us, or 1.64ms, depending on the settings in SU.MACFCR.PLT. The receive queue
could keep growing if the round trip delay is greater than the Pause time. Pause control will only take care of
temporary congestion it does not take care of systems where the traffic throughput is too high for the queue sizes
selected. If the flow control is not effective the receive queue will eventually overflow. This is indicated in
SU.LIQOS. If the receive queue is overflowed any new frames will not be received until the overflow condition is
corrected..
The user has the option of not enabling automatic flow control. In this case the thresholds and corresponding
interrupt mechanism to send pause frame by writing to the FCB bit in the MAC flow control register SU.MACFCR.
This allows the user to set not only the watermarks but also to decide when to send a pause frame or not based on
watermark crossings.
On the receive side the user has control over whether to respond to the pause frame sent by the distant end
(SU.MACFCR.RFE bit). On the Transmit queue the user has the option of setting high and low thresholds and
corresponding interrupts. There is no automatic flow control mechanism for data received from the Serial
side waiting for transmission over the Ethernet interface during times of heavy Ethernet congestion.
Half duplex flow control functions like Full Duplex flow control, but a jamming sequence is used to exert
backpressure on the transmitting node rather than Pause control frames. The receiving node jams the first 4 bytes
of a frame that are received from the MAC in order to cause a collision detection at the distant end. In both
100Mbps and 10Mbps MII/RMII modes, 4 bytes are jammed upon reception of a new frame. Note that the jamming
mechanism does not jam the frame that is being received during the watermark crossing, but will wait to jam the
next frame after the AR.LQW is crossed. If the queue remains above the threshold, received frames will continue
to be jammed. This jam sequence is stopped when the queue falls below the threshold in AR.LQW.
Type /
Preamble SFD Destination Adrs Source Address Data CRC32
Length
7 1 6 6 2 46-1500 4
The distant end will normally reject the sent frames if jabber timeout, loss of carrier, excessive deferral, late
collisions, excessive collisions, under run, deferred or collision errors occur. Transmission of a frame under any of
these errors will be logged by the MAC management counters. The device provides user the option to not
automatically retransmit the frame if any of the errors have occurred through the MAC’s SU.MACCR.DRTY bit.
Frames received with errors are usually rejected by the device. More information on the Ethernet MAC functions
can be found in Section 8.19.
GMII interface operates synchronously from the external 125MHz reference, and 23 signals are required. The
following figure shows the GMII architecture. Note that DCE mode is not supported for GMII mode and that GMII is
valid only for full duplex operation.
TXD[7:0]
TX_EN1
Transmit
GTX_CLK
TX_ERR1
RXD[7:0]
RX_CRS1
RX_DV1
Receive
RX_ERR1
RX_CLK1
MDC
Control MDIO
The Ethernet interface can be configured for RMII operation by setting the hardware pin RMIIMIIS low. MII interface
operates synchronously from the external 25MHz reference (REF_CLK). The following figure shows the MII
architecture.
Figure 8-10. Example Configuration as DTE connected to an Ethernet PHY in MII Mode
Rx Ethernet Phy
Rx
RXD[3:0] RXD[3:0]
DTE DCE
RXDV RXDV
RX_CLK RX_CLK
RX_ERR RX_ERR
Arbiter RX_CRS RX_CRS
WAN MAC
COL_DET COL_DET
TXD[3:0] TXD[3:0]
Tx
Tx TX_CLK TX_CLK
TX_EN TX_EN
MDIO
MDIO
MDC MDC
Mode/Speed Functions
10Mbps full duplex DTE Mode with While in full duplex, MII DTE Mode, both the receive and transmit MII
no flow control clocks are inputs.
100Mbps full duplex, DTE Mode In full duplex DTE Mode the clocks are expected from the PHY. The flow
with flow control control for a full duplex operation is using control frames. If the MAC
receives a pause command the Transmitter is disabled for the time
specified in the pause command. The pause command has a multicast
address 01-80-62-00-00-01. The MAC can also initiate a pause control
frame with SU.MACFCR.FCB. The duration field in the pause control
frame is determined by settings in the MAC Flow control Register
100Mbps full duplex, DTE Mode —
with no flow control
100Mbps full duplex DCE Mode with In full duplex DCE Mode, the clocks are provided by the device. The flow
flow control control for a full duplex operation is using control frames. If the MAC
receives a pause command the Transmitter is disabled for the time
specified in the pause command. The pause command has a multicast
address 01-80-62-00-00-01. The MAC can also initiate a pause control
frame with SU.MACFCR.FCB. The duration field in the pause control
frame is determined by settings in the MAC Flow control Register
When in 10/100 mode, the Ethernet MII interface(s) can be configured for DCE or DTE Mode. When configured in
DTE Mode, direct connection can be made to Ethernet PHYs. In DCE mode, the MII interface can be connected to
MII MAC devices other than an Ethernet PHY, such as Ethernet Switch devices. The DTE/DCE connections in MII
mode are shown in the following 2 figures.
In DCE Mode, the transmitter is connected to an external receiver and receiver is connected to an external MAC
transmitter. The selection of DTE or DCE mode is done by the hardware pin DCEDTES. DCE mode is not valid for
GbE (GMII) operation.
DCE DTE
Rx Tx
RXD[3:0] TXD[3:0]
RXDV TX_EN
RX_CLK TX_CLK
RX_ERR TX_ERR
RX_CRS RX_CRS
WAN MAC MAC
Arbiter COL_DET COL_DET
TXD[3:0] RXD[3:0]
Tx
Rx
TX_CLK RX_CLK
TX_EN RXDV
MDIO MDIO
MDC MDC
The Ethernet interface can be configured for RMII operation by setting the hardware pin RMIIMIIS high. RMII
interface operates synchronously from the external 50MHz reference (REF_CLK). Only 7 signals are required. The
following figure shows the RMII architecture. Note that DCE mode is not supported for RMII mode and RMII is valid
only for full duplex operation.
TX_EN
TXD[1:0]
TXD[3:0]
Transmit TX_EN
MAC TX_ERR
TX_CLK
CRS
CRS_DV RX_DV
Receive
MAC RXD[1:0] RXD[3:0]
REF_CLK RX_ER
RX_CLK
The VLAN ID (VID) is a 12-bit field that is found beginning in the 15th byte of VLAN tagged Ethernet frames. The
format of the IEEE 802.1Q VLAN tagged frame is shown in Figure 8-13. The device uses a 4 kilobyte user-
configured “VLAN Table” to translate VLAN tag information into forwarding, trapping, or discarding decisions. For
more details on VLAN Table programming, see Section 8.16.2.
All frames received on the Ethernet interfaces are inspected for a VLAN ID (LAN-VLAN ID) value. The VLAN table
settings for each of the 4096 LAN-VLAN IDs are used to forward each frame to one of the four WAN groups, to
discard the frame, or to extract (trap) the frame. Only when operating in forwarding modes 3, 4, and 5 (as defined
in Section 8.9), can frames be forwarded to one of the four WAN Groups as assigned in the VLAN table. All 12-bit
LAN-VLAN IDs that are translated to the same WAN Group are considered part of the same LAN-VLAN Group.
Note that LAN-VLAN ID trapping must be assigned to an Ethernet Port with the SU.LPM.LEEPS bit, and enabled
with the SU.LPM.LEVIT bit.
All frames received on the WAN interfaces are inspected for a VLAN ID (WAN-VLAN ID) value. ). The VLAN table
settings for each of the 4096 WAN-VLAN IDs are used to forward each frame to one of the Ethernet ports, to
discard the frame, or to extract (trap) the frame. Only when operating in forwarding mode 5 (as defined in Section
8.9), can frames be forward to one of the Ethernet ports by their VLAN ID value. All 12-bit LAN-VLAN IDs that are
translated to the same Ethernet interface are considered part of the same WAN-VLAN Group. Note that WAN-
VLAN forwarding is only applicable when operating in forwarding mode 5. Also note that WAN-VLAN ID trapping
must be assigned to a specific WAN Group with the SU.WEM.WEDS bits and enabled with the SU.WEM.WEVIT
bit.
The LAN-VLAN configuration, used to specify the actions for VLAN ID values in frames received on the Ethernet
interfaces (LAN-to-WAN direction), may be unrelated to the WAN-VLAN configuration, used to specify the actions
for VLAN ID values for frames received on the WAN interface (WAN-to-LAN direction). Although there may be
VLAN tags in both data stream directions (LAN-to-WAN and WAN-to-LAN), the functionality of the device does not
require a symmetrical VLAN function. The LAN-VLAN forwarding and the WAN-VLAN forwarding may be used
independently of each other.
A 4 kilobyte user-configured “VLAN Table” is used to translate VLAN tag information from each received frame into
forwarding, trapping (frame extraction), or discarding decisions. Each address in the table corresponds to a
specific VLAN ID (VID) value from 0 to 4095, and the bit settings at each address relate to actions taken when a
frame containing the corresponding VLAN ID value is detected. The VLAN Table is configured through the
SU.VTC, SU.VTAA, SU.VTWD, and SU.VTRD registers.
Within each address location in the VLAN table, two bits of data determine the actions taken for frames received on
the WAN interfaces with VLAN IDs matching the table address value, and four bits determine actions taken on
frames received on the LAN interfaces with VLAN IDs matching the table address value. The 4K x 2 bit space used
for WAN functions is referred to as the WAN-VLAN table. The 4 K x 4 bit space used for LAN functions is referred
to as the LAN-VLAN table.
The user can also configure a default “No VLAN detected” value in the SU.LNFC register to indicate what should
be done with frames that do not have a VLAN tags. The user may indicate the same forwarding location as one of
the other VLAN Groups, or it can be used to indicate an independent process or location. For example, the user
may indicate to discard untagged frames, while VLAN tags 0 through 4094 are forwarded to the 4 WAN Groups
and VLAN tag 4095 is forwarded to the LAN Extract queue.
To Reset the VLAN Table:
1) Write SU.VTC = 05h to ensure a 0-1 transition on SU.VTC.CI and enable the VLAN Table.
2) Write SU.VTC = 07h.
3) Read SU.VTSA.VTIS until = 1.
The IEEE 802.1Q VLAN tagging standard allocated room for a priority code that was later defined by the IEEE
802.1p standard. IEEE 802.1p eventually became part of IEEE 802.1D.
With Priority Scheduling or Priority Forwarding enabled, the priority value is inspected as each frame arrives on the
Ethernet Interfaces. For IEEE 802.1p priority coding, the priority is located in the 15th byte of the Ethernet frame.
The format of the IEEE 802.1p VLAN tagged frame is shown in Figure 8-13. A user-programmed Priority Table is
used to translate the 3-bit 802.1p Priority value into one of four Priority Levels for each Ethernet Interface. The
received PCP value is used as the address for the Priority Table lookup operation. The Priority Levels correspond
to four separate queues. In Priority Forwarding (Forwarding Mode 1), the four queues are in separate WAN
Groups. In Priority Scheduling operation, each WAN Group contains a set of four priority queues. These queues
are collectively referred to as LAN Queues in other portions of this document.
The priority mode (802.1p, DSCP, or none) for each Ethernet port can be independently selected using the
SU.LP1C and SU.LP2C registers. See Section 8.16.6 for more information on programming the priority table.
Device operation with multiple VLAN tags is similar to operation with a single VLAN tag. The Ethernet Q-in-Q
format is similar to the case outlined above, except that a second VLAN tag is inserted after the Ethernet SA field.
The format of the VLAN Q-in-Q tagged frame is shown in Figure 8-14. Both VLAN tags include a PCP (User
Priority) value and a VLAN ID. The device only makes forwarding and scheduling decisions using the “outer-most”
VLAN tag located in Ethernet bytes # 13-16, and ignores additional tags. The user can configure an alternate
WAN-VLAN Q-in-Q or VLAN Tag Protocol ID (TPID) that is used instead of the default value of 8100 in the
SU.WETPID register. The user can configure an alternate LAN-VLAN Q-in-Q or VLAN Tag Protocol ID (TPID) that
is used instead of the default value of 8100h in the SU.LQTPID register. Some additional common TPIDs are 9100,
9200 and 88A8. See Section 8.16.6 for more information on programming the priority table.
The IETF RFC2474 (Differentiated Services) defines a Layer-3 alternate to 802.1p priority coding, known as
Differentiated Services Code Point (DSCP). DSCP is composed of a 6-bit value located in the second byte of the IP
header. When Priority Scheduling or Priority Forwarding are enabled, the priority value is inspected as each frame
arrives on the Ethernet Interfaces. The format of the DSCP tagged frame is shown in Figure 8-15. The device
supports DSCP priority carried in IPv4 or IPv6 packets. A user-programmed Priority Table is used to translate the
6-bit DSCP Priority into one of four Priority Levels for each Ethernet Interface. The received PCP value is used as
the address for the Priority Table lookup operation. The Priority Levels correspond to four separate queues. In
Priority Forwarding (Forwarding Mode 1), the four queues are in separate WAN Groups. In Priority Scheduling
operation, each WAN Group contains a set of four priority queues. These queues are collectively referred to as
LAN Queues in other portions of this document.
The priority mode (802.1p, DSCP, or none) for each Ethernet port can be independently selected using the
SU.LP1C and SU.LP2C registers. The DSCP function is a simple enable/disable function, with all of the other
parameters (Ethernet Frame Format, and Ethernet Type) being discovered by the device. See Section 8.16.6 for
more information on programming the priority table.
The user-programmable Priority Table is accessed indirectly through the SU.PTC, SU.PTAA, SU.PTWD,
SU.PTRD, and SU.PTSA registers. The device contains a single table, with the MSB of the table address
(SU.PTAA.PTAA) used to distinguish the LAN port in multi-port devices. When a frame is received, the PCP or
DSCP value in the received frame is the address used to look up the user-programmed priority level in the Priority
Table.
The device does not require that the priority mapping be linear or monotonic. Arbitrary assignments are allowed.
Note that while the DSCP/PCP protocol definitions use a higher value to indicate a higher priority, the device uses
a lower value to indicate a higher priority. As an example, for the values PCP = 000b and DSCP = 00000b (as
defined by their protocol definitions as lowest priority) most users will choose to assign the associated priority table
address location (SU.PTAA.PTAA[6:1]=000000b) a value of 11b, indicating the lowest possible priority. Similarly
for the values PCP = 111b and DSCP = 111111b, typically the associated Priority Table address will be assigned a
value of 00b. Example Priority Table configurations for a single port are shown in the tables below.
SU.PTWD/
PTAA[6:1]
SU.PTRD
000000 11
000001 11
000010 10
000011 10
000100 01
000101 01
000110 01
000111 00
Frames from the LAN interface can be trapped by VLAN ID, Ethernet Type, Broadcast Address, Management
Multicast Address (01:80:C2:xx:xx:xx), Destination Address, or a range of Destination Addresses. Frames from the
WAN interface can be trapped by VLAN ID, Ethernet Type, Broadcast Address, Management Multicast Address
(01:80:C2:xx:xx:xx), Destination Address, a range of destination addresses, or by a user-programmable header
comparison. LAN trapping is enabled in the SU.LPM register. WAN trapping is enabled in the SU.WEM register.
The LAN Trap can only be user configured to monitor one Ethernet port. The selection of LAN port to be monitored
is done with the SU.LPM.LEEP bit. The WAN Trap can only monitor for WAN Extract conditions on one (of the four
possible) Decapsulator (WAN Group) data streams. The selection of the WAN Group to monitor is done with
SU.WEM.WEDS[1:0]. The maximum frame size that may be trapped is 2Kbytes.
8.17.1.1LAN-VLAN Trapping
When trapping frames received on the LAN interface by VLAN ID, the user configures the VLAN IDs (VIDs) to be
trapped using the LAN-VLAN Table. Trapping is then enabled or disabled with the SU.LPM.LEVIT bit. See Section
8.16 for more information on VLAN configuration. Only one LAN Port can be allowed to forward frames to the LAN
Extract Queue (which of the two ports is determined by user configuration). If VLAN Forwarding is enabled, and the
4-bit value returned from the LAN-VLAN Table indicates “Extract”, but the port that the frame is associated with has
not been configured to forward to the LAN Extract queue, then the “Extract” status returned from the VLAN Table is
ignored. For more details on LAN-VLAN Table programming, see Section 8.16.2.
When trapping frames received on the LAN interface by Ethernet Type, the user can configure and 2-byte Ethernet
Type Field to be trapped in the SU.LEET register. Trapping is then enabled or disabled with the SU.LPM.LEETT
bit. Ethernet Type trapping enables the capture of ARP, BPDU, and other management traffic.
When trapping frames received on the LAN interface by Unicast Destination Address, the user programs the
Destination Address for extraction into the SU.LEDAL, SU.LEDAM, and SU.LEDAH registers. By using a mask for
the lower two bytes of the DA in the SU.LEDAX register, all of the addresses within a range can be forwarded to
the LAN Extract queue. Trapping is then enabled or disabled with the SU.LPM.LEDAT bit.
When trapping frames received on the LAN interface by management multicast address (01:80:C2:xx:xx:xx), the
user simply enables extraction with the SU.LPM.LMGMTT bit. All trapped frames will be forwarded to the LAN
extract queue.
When trapping frames received on the LAN interface by broadcast address (FF:FF:FF:FF:FF:FF), the user simply
enables extraction with the SU.LPM.LBAT bit. All trapped frames will be forwarded to the LAN extract queue.
When trapping frames received on the WAN interface by Unicast Destination Address (DA), the user programs the
Destination Address for extraction into the SU.WEDAL, SU.WEDAM, and SU.WEDAH registers. By using a mask
for the lower two bytes of the DA in the SU.WEDAX register, all of the management addresses within a range can
be forwarded to the WAN Extract queue. Trapping is then enabled or disabled with the SU.WEM.WEDAT bit.
When trapping frames received on the WAN interface by management multicast address (01:80:C2:xx:xx:xx), the
user simply enables extraction with the SU.WEM.WMGMTT bit. All trapped frames will be forwarded to the WAN
extract queue.
When trapping frames received on the WAN interface by broadcast address (FF:FF:FF:FF:FF:FF), the user simply
enables extraction with the SU.WEM.WBAT bit. All trapped frames will be forwarded to the WAN extract queue.
8.17.1.5WAN-VLAN Trapping
When trapping frames received on the WAN interface by VLAN ID, the user configures the VLAN IDs (VIDs) to be
trapped using the WAN-VLAN Table. Trapping is then enabled or disabled with the SU.WEM.WEVIT bit. See
Section 8.16 for more information on VLAN configuration. Only one WAN Group Decapsulator can be allowed to
forward frames to the WAN Extract Queue at a time (determined by user configuration). If VLAN Trapping is
enabled, and the 4-bit value returned from the WAN-VLAN Table indicates “Extract”, but the port that the frame is
associated with has not been configured to forward to the WAN Extract queue, then the “Extract” status returned
from the WAN-VLAN Table is ignored. For more details on WAN-VLAN Table programming, see Section 8.16.2.
When trapping frames received on the WAN interface by Ethernet Type, the user can configure and 2-byte
Ethernet Type Field to be trapped in the SU.WEET register. Trapping is then enabled or disabled with the
SU.WEM.WEETT bit. The WAN Ethernet Type trap is valid only with frame formats in which the Ethernet Type
occurs in the first 32 bytes. Thus, the WAN Ethernet Type trap is not valid with the following frame types:
• 4-byte Encapsulation Header with Q-in-Q & std VLAN & LLC/SNAP (HDLC or GFP-Null)
• 8-byte Encapsulation Header with Q-in-Q & std VLAN & LLC/SNAP (HDLC or GFP-Linear)
• 8-byte Encapsulation Header with std VLAN & LLC/SNAP (HDLC or GFP-Linear)
Trapping can also be performed on any two consecutive bytes within the first 8 bytes of frames received from the
WAN interface. When trapping frames received on the WAN interface by header, the user configures a 2-byte
value to be trapped in the SU.WEHT register. The offset is configured in the SU.WEHTP register. Trapping is then
enabled or disabled with the SU.WEM.WEHT bit.
Extraction of trapped frames through the microport is done one byte at a time, with the beginning of the frame
being read first. The device must be configured to properly trap frames as described in Section 8.17.1. The user
may enable an interrupt to alert the host processor that a frame is available for extraction via the GL.MSIER3
interrupt enable register. A latched status register (GL.MLSR3) may also be used as indication that a frame is
available for extraction. When a trapped frame is available, the user must select the correct FIFO with the
GL.MCR1 register. The user must then read the length of the frame from GL.MSR1 or GL.MSR2 in order to know
how many bytes to extract. The user then reads one byte at a time from the FIFO read access register
(GL.MFARR) to extract the entire frame. When the entire frame has been read, the user indicates that the frame
may be discarded from the FIFO with the GL.MFAWR.RD_DN bit.
Steps for Frame Extraction:
1. Read the GL.MSR3 LAN/WAN FIFO Extraction Available Status bit to verify FIFO has a frame to be read.
2. Select the corresponding FIFO via GL.MCR1.
3. Read the size of frame in bytes from GL.MSR1 or GL.MSR2.
4. Read the frame from the GL.MFARR register one byte at a time.
5. Write a 0-to-1 transition to GL.MFAWR.RD_DN.
6. Repeat step 1.
Insertion of a frame through the host microport is done one byte at a time, with the beginning of the frame written
first. The user must first configure the LAN insertion settings and enable insertion via the SU.LIM register, or
configure the WAN insertion settings and enable insertion via the AR.MQC register. The correct FIFO must then be
selected with the GL.MCR1 register. The length of the frame to be inserted must then be written into GL.MCR2 or
GL.MCR3. The user proceeds to write one byte of the frame at a time to the FIFO access register, GL.MFAWR,
beginning with the first byte of the frame. Each write to this address automatically increments the pointer of the
selected FIFO. When the entire frame has been written, the GL.MFAWR.WR_DN bit is used to indicate that the
frame is ready for transmission.
Steps for Frame Insertion:
1. Configure the LAN insertion settings in the SU.LIM register, or WAN insertion settings in AR.MQC.
2. Read the GL.MSR3 LAN/WAN Queue Empty Status bit to verify FIFO is empty.
Rev: 063008 77 of 375
________________________________________________ DS33X162/X161/X82/X81/X42/X41/X11/W41/W11
The WAN Insert Queue can be user assigned to be multiplexed with only one LAN Queue Group. The Group
Scheduler for the assigned LAN Queue Group multiplexes the WAN Insert data with the data from the LAN Queue
Group.
The device can be configured to directly trap broadcast, management multicast (01:80:C2:xx:xx:xx), and unicast
frames by Ethernet Destination Addresses for extraction by a microprocessor. The host microprocessor can be
user-programmed for parsing, interpreting, and responding to OAM messages.
When a node on the network first tries to send a management frame to the device, the transmitting node would
normally broadcast an ARP request for the unknown IP address, asking for the network to resolve the IP address
to a physical MAC address. The device is able to trap ARP request using the Broadcast address trap. The user
software should examine each ARP request, and when appropriate, insert a frame in response to the ARP request
that will associate the device's management MAC address with the desired IP address. The network then transmits
frames with the DA value of the physical MAC address in the ARP response. The device would then trap the follow-
on frames by MAC (DA) address.
The device can be configured to trap frames with any number of user-programmed VLAN IDs in the VLAN table.
The VLAN table is accessed indirectly through the SU.VTC, SU.VTAA, and SU.VTWD registers. The
SU.VTWD.LVDW bit is used to indicate a VLAN ID (VID) value is to be extracted if received on the LAN interface.
The SU.VTWD.WVQFW bit is used to indicate a VLAN ID (VID) value is to be extracted if received on the WAN
interface. Note that VLAN trapping must also be enabled with the SU.WEM or SU.LPM registers.
The device can be configured to trap unicast frames for extraction by the microprocessor. The host microprocessor
can be user-programmed for parsing, interpreting, and responding to SNMP messages. Hardware counters are
provided for supporting portions of RFC2819 (RMON), and portions of RFC1213 (MIB-II). See Section 8.19.2 for
more information on the MAC Management counters used for this purpose.
The Bridge Filter Table Reset function is used to clear all of the Bridge Table entries. This function is automatically
triggered at power-up and can be manually triggered by the user by setting SU.BFC.BFTR to 1. During the Bridge
Filter Table Reset operation, traffic will be processed as normal. The user has the option of disabling the LAN Ports
so that there is no traffic during the Bridge Filter Table Reset process or allowing traffic to continue flowing at the
same time as the Bridge Filter Table Reset process. If the user does not disable traffic, then the table may learn
some new entries before the complete table has been reset. The Bridge Filter Table Reset function takes
approximately 64 ms to complete.
The MII Management Block allows for the host to control up to 32 PHYs, each with 32 registers. The MII block
communicates with the external PHY using 2-wire serial interface composed of MDC (serial clock) and MDIO for
data. The MDIO data is valid on the rising edge of the MDC clock. The Frame format for the MII Management
Interface is shown Figure 8-17. The read/write control of the MII Management is accomplished through the indirect
SU.GMIIA MII Management Address Register and data is passed through the indirect SU.GMIID Data Register.
These indirect registers are accessed through the MAC Control Registers defined in Table 8-14. The MDC clock is
internally generated and runs at 1.67MHz. Note that the device provides a single MII Management port, and all
control registers for this function are located in MAC 1.
Opco Turn
Preamble Start Phy Adrs Phy Reg Aroun Data Idle
de
d 16 1
32 bits 2 bits 2 bits 5 bits 5 bits 2 bits
bits Bit
In addition to the automatic learning and filtering features described in Section 8.18, the Ethernet MAC has the
capability to filter frames by MAC Destination Address. This feature is available at all data rates. The user may
program up to 16 destination addresses that may be allowed or disallowed.
The following pseudo code is an example enabling static MAC address filter 0 to allow frames with a DA of
12:34:56:78:9A:BC to pass.
Traffic
MPLS / VLAN Tagging Mgmt
VCAT
The data from each WAN Group is processed by the Transmit Packet Processor (or Encapsulator) before being
transmitted on the Serial interfaces. The Encapsulator performs bit reordering, FCS processing, frame error
insertion, stuffing, frame abort sequence insertion, inter-frame padding, VLAN tag insertion, MPLS tag insertion,
PPP Headers, LAPS Headers, octet removal, and frame scrambling. Each WAN Group’s encapsulation settings
can be independently configured with the PP.EMCR(1-4) registers.
The Encapsulator automatically inserts the inter-frame fill and flag characters based on the selection of
HDLC/cHDLC/LAPS or GFP in PP.EMCR.EPRTSEL. A Line Header Insertion function (in PP.ELHHR and
PP.ELHLR) allows the user to insert Address, Control, and Protocol bytes for HDLC/cHDLC/X.86, or Type and
tHEC bytes for GFP. The Tag 1 Insertion function (in PP.ET1DHR and PP.ET1DLR) allows the user to insert a 4-
byte MPLS tag immediately before the Destination Address (DA). The Tag 2 Insertion function (in PP.ET2DHR and
PP.ET2DLR) allows the user to insert a 4-byte VLAN tag immediately after the Source Address (SA). Any existing
VLAN tags are “pushed” lower in the frame.
HDLC processing can be disabled. Disabling HDLC processing disables FCS processing, frame error insertion,
stuffing, frame abort sequence insertion, and inter-frame fill/padding. Only bit reordering and frame scrambling are
not disabled.
Bit reordering changes the bit order of each byte. If bit reordering is disabled, the outgoing 8-bit data stream
DT[1:8] with DT[1] being the MSB and DT[8] being the LSB is output from the Transmit FIFO with the MSB in
TFD[7] (or 15, 23, or 31) and the LSB in TFD[0] (or 8, 16, or 24) of the transmit FIFO data TFD[7:0] 15:8, 23:16, or
31:24). If bit reordering is enabled, the outgoing 8-bit data stream DT[1:8] is output from the Transmit FIFO with the
MSB in TFD[0] and the LSB in TFD[7] of the transmit FIFO data TFD[7:0]. In bit synchronous mode, DT [1] is the
first bit transmitted. Bit reordering is configured using the PP.EMCR.TBRE bit. Note that bit reordering is not
available in the A1 device revision (GL.IDR.REVn=000).
FCS processing, when enabled in PP.EMCR(1-4), appends a calculated FCS to the frame. The polynomial used
for FCS-16 is x16 + x12 + x5 + 1. The polynomial used for FCS-32 is x32 + x26 + x23 + x22 + x16 + x12 + x11 + x10 + x8 +
x7 + x5 + x4 + x2 + x + 1. The FCS is inverted after calculation. If packet processing is disabled, FCS processing is
not performed.
Frame error insertion inserts errors into the GFP PLI, data unit, or FCS bytes. A single bit is corrupted in each
errored frame. The location of the corrupted bit is user-programmable. Error insertion is controlled by the PP.EEIR
register.
Rev: 063008 86 of 375
________________________________________________ DS33X162/X161/X82/X81/X42/X41/X11/W41/W11
In HDLC/cHDLC/LAPS(X.86) mode, the inter-frame fill is selectable per WAN group with PP.EMCR.EIIS. If packet
processing is disabled, inter-frame padding is not performed. The frame scrambler is a x43 + 1 scrambler that
scrambles the entire frame data stream. Frame scrambling is selectable per WAN group with PP.EMCR.ECFCRD.
To optimize WAN bandwidth in point-to-point applications, the Ethernet header information may be removed from
the datagram prior to encapsulation. The Encapsulator can be configured to remove either 14 or 18 bytes from
each incoming frame using the PP.EMCR.ERE[1:0] bits. Byte removal starts with the DA field. Removing 14 bytes
will remove the DA, SA, and Length/Type fields. Removing 18 bytes will remove the DA, SA, Length/Type, and
VLAN Tag fields. Once all packet processing has been completed, the serial data stream is forwarded.
Note that some devices in the product family have less than four encapsulators. The DS33X11 contains only
Encapsulator #1. The DS33W41 and DS33X42 contain only encapsulators #1 and #3.
The Receive Packet Processor accepts data from the Receive Serial Interface performs frame descrambling, frame
delineation, inter-frame fill filtering, frame abort detection, destuffing, frame size checking, FCS error monitoring,
FCS byte extraction, and bit reordering. Frame delineation determines the frame boundary by identifying a frame
start or end flag. Receive packet processing can be disabled. Disabling packet processing disables frame
delineation, inter-frame fill filtering, frame abort detection, destuffing, frame size checking, FCS error monitoring,
and FCS byte extraction. Only frame descrambling and bit reordering are not disabled. The frame descrambler is a
self-synchronizing x43 + 1 descrambler.
Inter-frame fill filtering removes the inter-frame fill between frames. When a frame end flag is detected, all data is
discarded until a frame start flag is detected. The inter-frame fill can be flags or all 1s. The number of 1s between
flags does not need to be an integer number of bytes, and if at least seven 1s are detected in the first 16 bits after a
flag, all data after the flag is discarded until a start flag is detected.
Frame abort detection searches for a frame abort sequence between the frame start flag and a frame end flag, if an
abort sequence is detected, the frame is marked with an abort indication, the aborted frame count is incremented,
and all subsequent data is discarded until a valid frame start flag is detected.
Destuffing removes the extra data inserted to prevent data from mimicking a HDLC/cHDLC/X.86 flag or an abort
sequence. A start flag is detected, destuffing is performed until an end flag is detected. The start and end flags are
discarded. In bit synchronous mode, bit destuffing is performed. Bit destuffing consists of discarding any '0' that
directly follows five contiguous 1s. After destuffing is completed, the serial bit stream is forwarded.
Frame size validation checks each frame for a programmable maximum size. As the frame data comes in, the total
number of bytes is counted. If the frame length is below the minimum size limit, the frame is marked with an
aborted indication, and the frame size violation count is incremented. If the frame length is above the maximum
size limit, the frame is marked with an aborted indication, the frame size violation count is incremented, and all
frame data is discarded until a frame start is received. The minimum and maximum lengths include the FCS bytes,
and are determined after destuffing has occurred.
FCS error monitoring checks the FCS and aborts errored frames. If an FCS error is detected, the FCS errored
frame count is incremented and the frame is marked with an aborted indication. If an FCS error is not detected, the
receive frame count is incremented. The FCS type (16-bit or 32-bit) is programmable.
FCS byte extraction discards the FCS bytes. If FCS extraction is enabled, the FCS bytes are extracted from the
frame and discarded. If FCS extraction is disabled, the FCS bytes are stored in the receive FIFO with the frame.
Bit reordering changes the bit order of each byte. Normally, the first bit of each byte in the received data stream is
assumed to be the MSB. If bit reordering is enabled, the first bit of each byte in is assumed to be the LSB. Once all
of the packet processing has been completed, the data stream is passed to the WAN Queues. Bit reordering is
configured using the PP.DMCR.RBRE bit. Note that bit reordering is not available in the A1 device revision
(GL.IDR.REVn=000).
The Decapsulator collects 2 statistics; the number of good frames and number of errored frames due any errors.
These statistics are latched bit counters and are cleared when read by the user.
The Decapsulator must be configured to remove the 4-byte encapsulation line header information if it is present.
The 4-byte removal function is selected using the PP.DMCR.DR1E control bit. When enabled, 4 bytes are removed
immediately after the cHEC bytes when in GFP mode or after the start flag when in HDLC mode. This bit should be
set to 1 for X.86, cHDLC and GFP transport. This bit should be equal to 0 for HDLC traffic with no headers.
The Decapsulator can be configured to remove a MPLS tag prior to forwarding to the LAN interface. The 4-byte
removal function used for this purpose is enabled using the PP.DMCR.DR2E control bit. When enabled, 4 bytes
are removed after the first remove (DR1E) function. Note that PP.DMCR.DR1E must be properly configured for this
function to operate correctly.
The Decapsulator can be configured to remove a VLAN tag prior to forwarding to the LAN interface. The 4-byte
removal function used for this purpose is enabled using the PP.DMCR.DR3E control bit. When enabled, 12 bytes
are skipped (Ethernet DA/SA) and the following 4 bytes are removed. This function is performed after the
Decapsulator Remove Function 1 and/or Decapsulator Remove Function 2 have been performed. When
Decapsulator Remove Functions 1 and 2 are disabled, 12 bytes are skipped from the beginning of the Ethernet
frame.
To optimize WAN bandwidth in point-to-point applications, Ethernet header information may be removed from the
datagram during WAN transport. The Decapsulator can be configured to replace the missing Ethernet header
information prior to forwarding to the LAN interface, by inserting a 14 or 18 byte values to each incoming frame.
This function is enabled using the PP.DMCR.DAE[1:0] control bits. When enabled, a 14-byte value from the
PP.DA1DR through PP.DA7DR registers or a 18-byte value from the PP.DA1DR through PP.DA9DR registers will
be inserted after the cHEC bytes in GFP mode, or after the HDLC header/flag when in HDLC mode. Once all
packet processing is performed by the Decapsulator, the Ethernet frames are forwarded to the MAC for
transmission on the LAN interface.
Note that some devices in the product family have less than four Decapsulators. The DS33X11 contains only
Decapsulator #1. The DS33W41 and DS33X42 contain only Decapsulators #1 and #3.
The GFP-F protocol provides a method for encapsulating Ethernet Frames over point-to-point serial links. The
device expects a frame or multiframe synchronization signal to provide the byte boundary. This is provided by the
RSYNC and TSYNC pins. The receive functional timing is shown Figure 11-13. The transmit functional timing is
shown in Figure 11-9.
GFP-F Encapsulation is selected with the EPRTSEL register bit. However, there are two types of GFP-F: Null and
Linear Extension Mode. The device allows the selection of GFP Linear Extension through a user-configured “GFP
CRC Mode“ bit for each Encapsulator and Decapsulator (PP.EMCR.EGCM and PP.DMCR.DGCM). For each
mode, several additional register settings are required as outlined in the following sections.
In both GFP modes, the Line Header Insertion function (in PP.ELHHR and PP.ELHLR) must be programmed by
the user to insert the required GFP Type and tHEC fields. This structure, which is also known as the GFP Payload
Header, indicates the contents of the encapsulated payload. The Type field consists of sub fields that are used to
indicate the payload type (PTI), Payload FCS Indicator (PFI) Extension Header Identifier (EXI) and User Payload
Identifier (UPI).
The final two bytes of the TYPE/tHEC field are used to perform header validation. The tHEC calculation is a CRC-
16 operation in which the two byte PLI is multiplied by X16 and divided (modulo 2) by the polynomial X16+X12+X5+1.
Another common representation for this polynomial is 0x1021. The initialization value for the operation is 0x0000.
The MSB of the PLI is bit 16, and the resulting remainder of the operation is the tHEC. To avoid requiring this
algorithm implementation in the user’s software, some common Type and the corresponding tHEC values are
provided in the table below.
8.20.3.1GFP-F NULL
When configured for GFP Null operation, no additional header information is required. The Encapsulator’s Tag 1
Insertion function (in PP.ET1DHR and PP.ET1DLR) is available to insert a 4-byte MPLS tag immediately before the
Ethernet Destination Address (DA), and the Tag 2 Insertion function (in PP.ET2DHR and PP.ET2DLR) is available
to insert a 4-byte VLAN tag immediately after the Source Address (SA). Any existing VLAN tags are “pushed” lower
in the frame. The resulting encapsulated frame format is shown below. Note that when enabled in this mode, the
pFCS calculation begins with the 9th byte of the frame.
Bytes
GFP cHEC 2
PAD (optional)
MSB LSB
When configured for GFP Linear Extension mode, an additional header is required. The Encapsultor’s Tag 1
Insertion function (in PP.ET1DHR and PP.ET1DLR, enabled with PP.EMCR.ET1E) is used to insert the 4-byte
GFP Extension Header value. If receiving GFP Linear Extension frames from the WAN, the PP.DMCR.DR2E bit
should be set to 1 in order to remove the incoming GFP CID, Spare, and eHEC bytes from the data stream.
The Encapsulator’s Tag 2 Insertion function (in PP.ET2DHR and PP.ET2DLR) is available to insert a 4-byte VLAN
tag immediately after the Source Address (SA). Any existing VLAN tags are “pushed” lower in the frame. The
resulting encapsulated frame format is shown below. Note that when in this mode, the pFCS calculation begins
with the 13th byte of the frame. The received eHEC value is verified by the Decapsulator. While in Linear mode, if
the eHEC verification fails, the received WAN packet is discarded.
Bytes
GFP cHEC 2
Length / EtherType 2
PAD (optional)
MSB LSB
X.86 protocol provides a method for encapsulating Ethernet Frame for eventual transport on a SONET or SDH
network. LAPS provides a byte-synchronous HDLC-like framing structure for encapsulation of Ethernet frames, but
is not as susceptible to dynamic bandwidth expansion as bit-stuffed HDLC. LAPS encapsulated frames can be
used to send data onto a SONET/SDH network. The device expects a byte synchronization signal to provide the
byte boundary for the X.86 receiver. This is provided by the RSYNC pin. The functional timing is shown Figure
11-13. The X.86 transmitter provides a byte boundary indicator with the signal TSYNC. The functional timing is
shown in Figure 11-9.
A Line Header Insertion function (in PP.ELHHR and PP.ELHLR) allows the user to insert Address, Control, and
SAPI bytes. The Tag 1 Insertion function (in PP.ET1DHR and PP.ET1DLR) allows the user to insert a 4-byte MPLS
tag immediately before the Destination Address (DA). The Tag 2 Insertion function (in PP.ET2DHR and
PP.ET2DLR) allows the user to insert a 4-byte VLAN tag immediately after the Source Address (SA). Any existing
VLAN tags are “pushed” lower in the frame.
Bytes
Flag(0x7E) 1
Address(0x04) 1
Control(0x03) 1
Length / EtherType 2
PAD (optional)
Flag(0x7E) 1
MSB LSB
The device will encode the MAC Frame with X.86 / LAPS encapsulation on a complete serial stream if configured
for X.86 mode in the register PP.EMCR. The device provides the following functions:
• 32 bit FCS
• X43+1 Scrambling/Descrambling
• Transparency Processing
• Rate Adaptation Removal.
Received frames are aborted if:
• If 7d,7E is detected. This is an abort frame sequence in X.86
• Invalid FCS is detected
• The received frame has less than 6 octets
• Control, SAPI and address field are mismatched to the programmed value
• Octet 7D and octet other than 5D,5E,7E or DD is detected
When in X.86 mode, the device encapsulates frames with a Start Flag (7Eh), Address, Control and SAPI field,
followed by the frame and a 32-bit FCS. A X43+1 scrambler scrambles the data. Between the Start and Stop flags,
data bytes matching the start/abort flag is replaced with a 2-byte escape sequence. Figure 8-20 shows a frame
Encapsulated in a LAPS Frame. Options for MPLS and VLAN and Q-in-Q information bytes are user configured. In
the receive direction, rate adaptation octets are removed. In the transmit direction, idle code fill is used, and rate
adaptation is not performed. The Encapsulator performs transparency processing or octet stuffing to ensure that
the data does not mimic flags. For transparency processing, 7Eh is translated to 7D 5Eh and 7Dh is translated to
7D 5Dh. Byte stuffing consists of detecting bytes that mimic flag and escape sequence bytes (7Eh and 7Dh), and
replacing the mimic bytes with an escape sequence (7Dh) followed by the mimic byte exclusive 'OR'ed with 20h.
The HDLC protocol provides a simple method for encapsulating Ethernet Frames over point-to-point serial links.
HDLC Encapsulation can be bit or byte synchronous. In byte synchronous mode, byte stuffing is performed. Byte
stuffing consists of detecting bytes that mimic flag and escape sequence bytes (7Eh and 7Dh), and replacing them
with an escape sequence (7Dh) followed by the byte ‘exclusive-OR’ed’ with 20h. In Bit Synchronous HDLC, 5
consecutive ones must always be followed by a 0 to avoid mimicking a start or stop flag. Note that the 5
consecutive ones can straddle any 2 consecutive bytes. HDLC frame Encapsulation of the frame is shown in
Figure 8-21.
A Line Header Insertion function (in PP.ELHHR and PP.ELHLR) allows the user to insert Address, Control, and
Protocol bytes. The Tag 1 Insertion function (in PP.ET1DHR and PP.ET1DLR) allows the user to insert a 4-byte
MPLS tag immediately before the Destination Address (DA). The Tag 2 Insertion function (in PP.ET2DHR and
PP.ET2DLR) allows the user to insert a 4-byte VLAN tag immediately after the Source Address (SA). Any existing
VLAN tags are “pushed” lower in the frame.
The device provides the following HDLC functions.
• Insertion of HDLC flags
• Performs HDLC bit and byte stuffing
• Insertion of Payload FCS (32 bit / 16 bit)
• Selectable X43+1 scrambling
• Selectable Idle: All Ones or Flag insertion
HDLC Receive Compatibility:
• HDLC with no line headers and encapsulated Ethernet Frames.
• HDLC with LAPS Headers.
• HDLC with Cisco HDLC Headers.
• HDLC Encapsulated Ethernet Frames with VLAN Tags .
• HDLC Encapsulated Ethernet Frames with MPLS Headers.
• Bit or Byte Synchronous Stuffed HDLC
• HDLC FCS lengths of 0, 16, or 32 bits.
• Interframe fill can be 7Eh or all 1s.
• X43+1 scrambled frame.
Bytes
Flag(0x7E) 1
Address (optional) 1
Control (optional) 1
Length / EtherType 2
PAD (optional)
Flag(0x7E) 1
MSB LSB
The cHDLC protocol provides a simple method for encapsulating Ethernet Frames over point-to-point serial links.
A Line Header Insertion function (in PP.ELHHR and PP.ELHLR) allows the user to insert Address, Control, and
Protocol bytes. The Tag 1 Insertion function (in PP.ET1DHR and PP.ET1DLR) allows the user to insert a 4-byte
MPLS tag immediately before the Destination Address (DA). The Tag 2 Insertion function (in PP.ET2DHR and
PP.ET2DLR) allows the user to insert a 4-byte VLAN tag immediately after the Source Address (SA). Any existing
VLAN tags are “pushed” lower in the frame.
Bytes
Flag(0x7E) 1
Address (0x0F) 1
Control (0x00) 1
Length / EtherType 2
PAD (optional)
Flag(0x7E) 1
MSB LSB
9. Applications Information
TSER(I) TDATA(O)
TCHCLK(O) TCLK(I)
TSYNC(O) TSYNC(I)
MAXIM
DS33X162/X82/X81
T1/E1 Transceiver
/X42/X41/X11/W41
/W11
RSER(O)
RCHCLK(O) RDATA(I)
RSYNC(O) RCLK(I)
RSYNC(I)
TCLK
TCHCLK
FRAMING BYTE / CHANNEL 0 CHANNEL 1
TSER LSB MSB LSB MSB LSB MSB
TSYNC
TCLK
TCHCLK
TIME SLOT 1 TIME SLOT 2
TSER LSB X MSB LSB MSB LSB MSB
TSYNC
RCLK
RCHCLK
RSYNC
RCLK
RCHCLK
RSYNC
TSER(I) TDATA(O)
TGCLK(O) TCLK(I)
TSOFO(O) TSYNC(I)
Dallas
DS33X162/X82/X81
Semiconductor
/X42/X41/X11/W41
T3/E3 Transceiver
/W11
RSER(O) RDATA(I)
RGCLK(O) RCLK(I)
RSOFO(O) RSYNC(I)
Figure 9-7. Example Functional Timing: DS3170 DS3 Transmit-Side Boundary Timing
Figure 9-8. Example Functional Timing: DS3170 DS3 Receive-Side Boundary Timing
RCLKO or
RCLKI
RSOFO
DS3 RGCLK
DS3 RSER X1
DS3 RDEN
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Because the third gapped transmit clock input edge after the transmit sync pulse is coincident with the start of the
first byte of user data, the transmit sync setup control bits must be configured for a sync pulse that arrives three
clock cycles early ( LI.TCR.TS_SETUP[1:0] = 11).
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
GLOBAL REGISTERS
000h WP4 WP3 WP2 WP1 WP0 GBE MP1 MP0
GL.IDR
001h REV2 REV1 REV0 SPIS VC2 VC1 VC0 VCAT
002h - - - - - FMC-2 FMC-1 FMC-0
GL.CR1
003h - - P2SPD0 - P1SPD - - -
004h - - - - INTM ENDEL - RST
GL.CR2
005h - - - - - - - -
008h - BUFIS - TSPIS DECIS1 ECIS1 TXLANIS RXLANIS
GL.ISR
009h MICIS DECIS4 DECIS3 DECIS2 ECIS4 ECIS3 ECIS2 RVCATIS
00Ah - BUFIE - TSPIE DECIE1 ECIE1 TXLANIE RXLANIE
GL.IER
00Bh MICIE DECIE4 DECIE3 DECIE2 ECIE4 ECIE3 ECIE2 RVCATIE
00Ch - - - - - - - -
GL.MBSR
00Dh - - - - DLOCK PLOCK - -
MICROPORT REGISTERS
020h - - - - - - FIFO1 FIFO0
GL.MCR1
021h - - - - - - - -
022h WILEN7 WILEN6 WILEN5 WILEN4 WILEN3 WILEN2 WILEN1 WILEN0
GL.MCR2
023h - - - - WILEN11 WILEN10 WILEN9 WILEN8
024h LILEN7 LILEN6 LILEN5 LILEN4 LILEN3 LILEN2 LILEN1 LILEN0
GL.MCR3
025h - - - - LILEN11 LILEN10 LILEN9 LILEN8
026h WELEN7 WELEN6 WELEN5 WELEN4 WELEN3 WELEN2 WELEN1 WELEN0
GL.MSR1
027h - - - - WELEN11 WELEN10 WELEN9 WELEN8
028h LELEN7 LELEN6 LELEN5 LELEN4 LELEN3 LELEN2 LELEN1 LELEN0
GL.MSR2
029h - - - - LELEN11 LELEN10 LELEN9 LELEN8
02Ah - - - - LANEA LANIE WANEA WANIE
GL.MSR3
02Bh - - - - - - - -
02Ch - - - - LANEAL LANIEL WANEAL WANIEL
GL.MLSR3
02Dh - - - - - - - -
02Eh - - - - LANEAIE LANIEIE WANEAIE WANIEIE
GL.MSIER3
02Fh - - - - - - - -
030h WPKT7 WPKT6 WPKT5 WPKT4 WPKT3 WPKT2 WPKT1 WPKT0
GL.MFAWR
031h - - - - - - RD_DN WR_DN
032h RPKT7 RPKT6 RPKT5 RPKT4 RPKT3 RPKT2 RPKT1 RPKT0
GL.MFARR
033h - - - - - - - -
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
MAC 1 INTERFACE PORT
040h SU.MAC1RADL MACRA7 MACRA6 MACRA5 MACRA4 MACRA3 MACRA2 MACRA1 MACRA0
041h SU.MAC1RADH MACRA15 MACRA14 MACRA13 MACRA12 MACRA11 MACRA10 MACRA9 MACRA8
042h SU.MAC1RD0 MACRD7 MACRD6 MACRD5 MACRD4 MACRD3 MACRD2 MACRD1 MACRD0
043h SU.MAC1RD1 MACRD15 MACRD14 MACRD13 MACRD12 MACRD11 MACRD10 MACRD9 MACRD8
044h SU.MAC1RD2 MACRD23 MACRD22 MACRD21 MACRD20 MACRD19 MACRD18 MACRD17 MACRD16
045h SU.MAC1RD3 MACRD31 MACRD30 MACRD29 MACRD28 MACRD27 MACRD26 MACRD25 MACRD24
046h SU.MAC1WD0 MACWD7 MACWD6 MACWD5 MACWD4 MACWD3 MACWD2 MACWD1 MACWD0
047h SU.MAC1WD1 MACWD15 MACWD14 MACWD13 MACWD12 MACWD11 MACWD10 MACWD09 MACWD08
048h SU.MAC1WD2 MACWD23 MACWD22 MACWD21 MACWD20 MACWD19 MACWD18 MACWD17 MACWD16
049h SU.MAC1WD3 MACD31 MACD30 MACD29 MACD28 MACD27 MACD26 MACD25 MACD24
04Ah SU.MAC1AWL MACAW7 MACAW6 MACAW5 MACAW4 MACAW3 MACAW2 MACAW1 MACAW0
04Bh SU.MAC1AWH MACAW15 MACAW14 MACAW13 MACAW12 MACAW11 MACAW10 MACAW9 MACAW8
04Ch SU.MAC1RWC - - - - - - MCRW MCS
MAC 2 INTERFACE PORT
060h SU.MAC2RADL MACRA7 MACRA6 MACRA5 MACRA4 MACRA3 MACRA2 MACRA1 MACRA0
061h SU.MAC2RADH MACRA15 MACRA14 MACRA13 MACRA12 MACRA11 MACRA10 MACRA9 MACRA8
062h SU.MAC2RD0 MACRD7 MACRD6 MACRD5 MACRD4 MACRD3 MACRD2 MACRD1 MACRD0
063h SU.MAC2RD1 MACRD15 MACRD14 MACRD13 MACRD12 MACRD11 MACRD10 MACRD9 MACRD8
064h SU.MAC2RD2 MACRD23 MACRD22 MACRD21 MACRD20 MACRD19 MACRD18 MACRD17 MACRD16
065h SU.MAC2RD3 MACRD31 MACRD30 MACRD29 MACRD28 MACRD27 MACRD26 MACRD25 MACRD24
066h SU.MAC2WD0 MACWD7 MACWD6 MACWD5 MACWD4 MACWD3 MACWD2 MACWD1 MACWD0
067h SU.MAC2WD1 MACWD15 MACWD14 MACWD13 MACWD12 MACWD11 MACWD10 MACWD09 MACWD08
068h SU.MAC2WD2 MACWD23 MACWD22 MACWD21 MACWD20 MACWD19 MACWD18 MACWD17 MACWD16
069h SU.MAC2WD3 MACD31 MACD30 MACD29 MACD28 MACD27 MACD26 MACD25 MACD24
06Ah SU.MAC2AWL MACAW7 MACAW6 MACAW5 MACAW4 MACAW3 MACAW2 MACAW1 MACAW0
06Bh SU.MAC2AWH MACAW15 MACAW14 MACAW13 MACAW12 MACAW11 MACAW10 MACAW9 MACAW8
06Ch SU.MAC2RWC - - - - - - MCRW MCS
COMMON VLAN TABLE CONTROL
080h - - - - - CTE CI CAIM
SU.VTC
081h - - - - - - - -
082h VTAA8 VTAA7 VTAA6 VTAA5 VTAA4 VTAA3 VTAA2 VTAA1
SU.VTAA
083h - - - - VTAA12 VTAA11 VTAA10 VTAA9
084h - - WVEFW WVQFW LVDW LVEFW LVQFW2 LVQFW1
SU.VTWD
085h - - - - - - - -
086h - - WVEFR WVQFR LVDR LVEFR LVQFR2 LVQFR1
SU.VTRD
087h - - - - - - - -
088h VTSA8 VTSA7 VTSA6 VTSA5 VTSA4 VTSA3 VTSA2 VTSA1
SU.VTSA
089h - - - VTIS VTSA12 VTSA11 VTSA10 VTSA9
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
TRANSMIT LAN AND WAN EXTRACTION
0A0h WNVDF WEFR WEDS2 WEDS1 WEVIT WEETT WEDAT WEHT
SU.WEM
0A1h - - - - - - WMGMTT WBAT
0A2h - - - WEHTH WEHTL WEHTP3 WEHTP2 WEHTP1
SU.WEHTP
0A3h - - - - - - - -
0A4h WEHT8 WEHT7 WEHT6 WEHT5 WEHT4 WEHT3 WEHT2 WEHT1
SU.WEHT
0A5h WEHT16 WEHT15 WEHT14 WEHT13 WEHT12 WEHT11 WEHT10 WEHT9
0A6h WEDAL8 WEDAL7 WEDAL6 WEDAL5 WEDAL4 WEDAL3 WEDAL2 WEDAL1
SU.WEDAL
0A7h WEDAL16 WEDAL15 WEDAL14 WEDAL13 WEDAL12 WEDAL11 WEDAL10 WEDAL9
0A8h WEDAM8 WEDAM7 WEDAM6 WEDAM5 WEDAM4 WEDAM3 WEDAM2 WEDAM1
SU.WEDAM
0A9h WEDAM16 WEDAM15 WEDAM14 WEDAM13 WEDAM12 WEDAM11 WEDAM10 WEDAM9
0AAh WEDAH8 WEDAH7 WEDAH6 WEDAH5 WEDAH4 WEDAH3 WEDAH2 WEDAH1
SU.WEDAH
0ABh WEDAH16 WEDAH15 WEDAH14 WEDAH13 WEDAH12 WEDAH11 WEDAH10 WEDAH9
0ACh WEDAX8 WEDAX7 WEDAX6 WEDAX5 WEDAX4 WEDAX3 WEDAX2 WEDAX1
SU.WEDAX
0ADh - - - - - - - -
0AEh WEET8 WEET7 WEET6 WEET5 WEET4 WEET3 WEET2 WEET1
SU.WEET
0AFh WEET16 WEET15 WEET14 WEET13 WEET12 WEET11 WEET10 WEET9
0B2h WETPID8 WETPID7 WETPID6 WETPID5 WETPID4 WETPID3 WETPID2 WETPID1
SU.WETPID
0B3h WETPID16 WETPID15 WETPID14 WETPID13 WETPID12 WETPID11 WETPID10 WETPID9
0B4h - - - - - - - WEOS
SU.WOS
0B5h - - - - - - - -
0B6h - - - LIFR LIIP2 LIIP1 LIP LIE
SU.LIM
0B7h - - - - LP2R LP1R LP2CE LP1CE
0B8h - - - - - - - WEOM
SU.WOM
0B9h - - - - - - - -
0BAh - LTCC3 LTCC2 LTCC1 LTCC0 LTEXD LTUFE LTDEF
SU.LP1XS
0BBh LTED LTJTO LTFF - LTLOC LTNCP LTLC LTEC
0BCh - LTCC3 LTCC2 LTCC1 LTCC0 LTEXD LTUFE LTDEF
SU.LP2XS
0BDh LTED LTJTO LTFF - LTLOC LTNCP LTLC LTEC
RECEIVE LAN REGISTERS
0C0h - - - LEEPS LEVIT LEETT LEDAT LPM
SU.LPM
0C1h - - - - - - LMGMTT LBAT
0C2h LEDAL7 LEDAL6 LEDAL5 LEDAL4 LEDAL3 LEDAL2 LEDAL1 LEDAL0
SU.LEDAL
0C3h LEDAL15 LEDAL14 LEDAL13 LEDAL12 LEDAL11 LEDAL10 LEDAL9 LEDAL8
0C4h LEDAM7 LEDAM6 LEDAM5 LEDAM4 LEDAM3 LEDAM2 LEDAM1 LEDAM0
SU.LEDAM
0C5h LEDAM15 LEDAM14 LEDAM13 LEDAM12 LEDAM11 LEDAM10 LEDAM9 LEDAM8
0C6h LEDAH7 LEDAH6 LEDAH5 LEDAH4 LEDAH3 LEDAH2 LEDAH1 LEDAH0
SU.LEDAH
0C7h LEDAH15 LEDAH14 LEDAH13 LEDAH12 LEDAH11 LEDAH10 LEDAH9 LEDAH8
0C8h LEDAX7 LEDAX6 LEDAX5 LEDAX4 LEDAX3 LEDAX2 LEDAX1 LEDAX0
SU.LEDAX
0C9h - - - - - - - -
0CAh SU.LEET LEET7 LEET6 LEET5 LEET4 LEET3 LEET2 LEET1 LEET0
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
0CBh LEET15 LEET14 LEET13 LEET12 LEET11 LEET10 LEET9 LEET8
0CCh LP1MIM LP1QOM LP1FR LP1PF2 LP1PF1 LP1ETF2 LP1ETF1 LP1E
SU.LP1C
0CDh - - - - - - - -
0CEh LP2MIM LP2QOM LP2FR LP2PF2 LP2PF1 LP2ETF2 LP2ETF1 LP2E
SU.LP2C
0CFh - - - - - - - -
0D0h - - LNPDF2 LNPDF1 LNETDF4 LNETDF3 LNETDF2 LNETDF1
SU.LNFC
0D1h - - - - - - - -
0D2h LQXPC8 LQXPC7 LQXPC6 LQXPC5 LQXPC4 LQXPC3 LQXPC2 LQXPC1
SU.LQXPC
0D3h LQXPC16 LQXPC15 LQXPC14 LQXPC13 LQXPC12 LQXPC11 LQXPC10 LQXPC9
0D4h LQTPID8 LQTPID7 LQTPID6 LQTPID5 LQTPID4 LQTPID3 LQTPID2 LQTPID1
SU.LQTPID
0D5h LQTPID16 LQTPID15 LQTPID14 LQTPID13 LQTPID12 LQTPID11 LQTPID10 LQTPID9
0D6h - - - - LP2I LP1I LIQOS2 LIQOS1
SU.LIQOS
0D7h - - - - - - - -
0D8h MPL8 MPL7 MPL6 MPL5 MPL4 MPL3 MPL2 MPL1
SU.MPL
0D9h - - MPL14 MPL13 MPL12 MPL11 MPL10 MPL9
0DAh L1PCT8 L1PCT7 L1PCT6 L1PCT5 L1PCT4 L1PCT3 L1PCT2 L1PCT1
SU.L1PP
0DBh CBSS - - - L1PM2 L1PM1 L1PCR2 L1PCR1
0DCh L2PCT8 L2PCT7 L2PCT6 L2PCT5 L2PCT4 L2PCT3 L2PCT2 L2PCT1
SU.L2PP
0DDh CBSS - - - L2PM2 L2PM1 L2PCR2 L2PCR1
0DEh - - - - - - PTE PTAIM
SU.PTC
0DFh - - - - - - - -
0E0h - PTPAA PTAA6 PTAA5 PTAA4 PTAA3 PTAA2 PTAA1
SU.PTAA
0E1h - - - - - - - -
0E2h - - - - - - LPQFW2 LPQFW1
SU.PTWD
0E3h - - - - - - - -
0E4h - - - - - - LPQFR2 LPQFR1
SU.PTRD
0E5h - - - - - - - -
0E6h PTIS PTPSA PTSA6 PTSA5 PTSA4 PTSA3 PTSA2 PTSA1
SU.PTSA
0E7h - - - - - - - -
0E8h BFAP8 BFAP7 BFAP6 BFAP5 BFAP4 BFAP3 BFAP2 BFAP1
SU.BFC
0E9h - - - - - BFTR BFE BFAP9
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
BUFFER MANAGER (ARBITER) REGISTERS
100h LQ1SA-8 LQ1SA-7 LQ1SA-6 LQ1SA-5 LQ1SA-4 LQ1SA-3 LQ1SA-2 LQ1SA-1
AR.LQ1SA
101h - - - - - LQ1QPR LQ1SA-10 LQ1SA-9
102h LQ2SA-8 LQ2SA-7 LQ2SA-6 LQ2SA-5 LQ2SA-4 LQ2SA-3 LQ2SA-2 LQ2SA-1
AR.LQ2SA
103h - - - - - LQ2QPR LQ2SA-10 LQ2SA-9
104h LQ3SA-8 LQ3SA-7 LQ3SA-6 LQ3SA-5 LQ3SA-4 LQ3SA-3 LQ3SA-2 LQ3SA-1
AR.LQ3SA
105h - - - - - LQ3QPR LQ3SA-10 LQ3SA-9
106h LQ4SA-8 LQ4SA-7 LQ4SA-6 LQ4SA-5 LQ4SA-4 LQ4SA-3 LQ4SA-2 LQ4SA-1
AR.LQ4SA
107h - - - - - LQ4QPR LQ4SA-10 LQ4SA-9
108h LQ5SA-8 LQ5SA-7 LQ5SA-6 LQ5SA-5 LQ5SA-4 LQ5SA-3 LQ5SA-2 LQ5SA-1
AR.LQ5SA
109h - - - - - LQ5QPR LQ5SA-10 LQ5SA-9
10Ah LQ6SA-8 LQ6SA-7 LQ6SA-6 LQ6SA-5 LQ6SA-4 LQ6SA-3 LQ6SA-2 LQ6SA-1
AR.LQ6SA
10Bh - - - - - LQ6QPR LQ6SA-10 LQ6SA-9
10Ch LQ7SA-8 LQ7SA-7 LQ7SA-6 LQ7SA-5 LQ7SA-4 LQ7SA-3 LQ7SA-2 LQ7SA-1
AR.LQ7SA
10Dh - - - - - LQ7QPR LQ7SA-10 LQ7SA-9
10Eh LQ8SA-8 LQ8SA-7 LQ8SA-6 LQ8SA-5 LQ8SA-4 LQ8SA-3 LQ8SA-2 LQ8SA-1
AR.LQ8SA
10Fh - - - - - LQ8QPR LQ8SA-10 LQ8SA-9
110h LQ9SA-8 LQ9SA-7 LQ9SA-6 LQ9SA-5 LQ9SA-4 LQ9SA-3 LQ9SA-2 LQ9SA-1
AR.LQ9SA
111h - - - - - LQ9QPR LQ9SA-10 LQ9SA-9
112h LQ10SA-8 LQ10SA-7 LQ10SA-6 LQ10SA-5 LQ10SA-4 LQ10SA-3 LQ10SA-2 LQ10SA-1
AR.LQ10SA
113h - - - - - LQ10QPR LQ10SA-10 LQ10SA-9
114h LQ11SA-8 LQ11SA-7 LQ11SA-6 LQ11SA-5 LQ11SA-4 LQ11SA-3 LQ11SA-2 LQ11SA-1
AR.LQ11SA
115h - - - - - LQ11QPR LQ11SA-10 LQ11SA-9
116h LQ12SA-8 LQ12SA-7 LQ12SA-6 LQ12SA-5 LQ12SA-4 LQ12SA-3 LQ12SA-2 LQ12SA-1
AR.LQ12SA
117h - - - - - LQ12QPR LQ12SA-10 LQ12SA-9
118h LQ13SA-8 LQ13SA-7 LQ13SA-6 LQ13SA-5 LQ13SA-4 LQ13SA-3 LQ13SA-2 LQ13SA-1
AR.LQ13SA
119h - - - - - LQ13QPR LQ13SA-10 LQ13SA-9
11Ah LQ14SA-8 LQ14SA-7 LQ14SA-6 LQ14SA-5 LQ14SA-4 LQ14SA-3 LQ14SA-2 LQ14SA-1
AR.LQ14SA
11Bh - - - - - LQ14QPR LQ14SA-10 LQ14SA-9
11Ch LQ15SA-8 LQ15SA-7 LQ15SA-6 LQ15SA-5 LQ15SA-4 LQ15SA-3 LQ15SA-2 LQ15SA-1
AR.LQ15SA
11Dh - - - - - LQ15QPR LQ15SA-10 LQ15SA-9
11Eh LQ16SA-8 LQ16SA-7 LQ16SA-6 LQ16SA-5 LQ16SA-4 LQ16SA-3 LQ16SA-2 LQ16SA-1
AR.LQ16SA
11Fh - - - - - LQ16QPR LQ16SA-10 LQ16SA-9
120h LQ1EA-8 LQ1EA-7 LQ1EA-6 LQ1EA-5 LQ1EA-4 LQ1EA-3 LQ1EA-2 LQ1EA-1
AR.LQ1EA
121h - - - - - - LQ1EA-10 LQ1EA-9
122h LQ2EA-8 LQ2EA-7 LQ2EA-6 LQ2EA-5 LQ2EA-4 LQ2EA-3 LQ2EA-2 LQ2EA-1
AR.LQ2EA
123h - - - - - - LQ2EA-10 LQ2EA-9
124h LQ3EA-8 LQ3EA-7 LQ3EA-6 LQ3EA-5 LQ3EA-4 LQ3EA-3 LQ3EA-2 LQ3EA-1
AR.LQ3EA
125h - - - - - - LQ3EA-10 LQ3EA-9
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
126h LQ4EA-8 LQ4EA-7 LQ4EA-6 LQ4EA-5 LQ4EA-4 LQ4EA-3 LQ4EA-2 LQ4EA-1
AR.LQ4EA
127h - - - - - - LQ4EA-10 LQ4EA-9
128h LQ5EA-8 LQ5EA-7 LQ5EA-6 LQ5EA-5 LQ5EA-4 LQ5EA-3 LQ5EA-2 LQ5EA-1
AR.LQ5EA
129h - - - - - - LQ5EA-10 LQ5EA-9
12Ah LQ6EA-8 LQ6EA-7 LQ6EA-6 LQ6EA-5 LQ6EA-4 LQ6EA-3 LQ6EA-2 LQ6EA-1
AR.LQ6EA
12Bh - - - - - - LQ6EA-10 LQ6EA-9
12Ch LQ7EA-8 LQ7EA-7 LQ7EA-6 LQ7EA-5 LQ7EA-4 LQ7EA-3 LQ7EA-2 LQ7EA-1
AR.LQ7EA
12Dh - - - - - - LQ7EA-10 LQ7EA-9
12Eh LQ8EA-8 LQ8EA-7 LQ8EA-6 LQ8EA-5 LQ8EA-4 LQ8EA-3 LQ8EA-2 LQ8EA-1
AR.LQ8EA
12Fh - - - - - - LQ8EA-10 LQ8EA-9
130h LQ9EA-8 LQ9EA-7 LQ9EA-6 LQ9EA-5 LQ9EA-4 LQ9EA-3 LQ9EA-2 LQ9EA-1
AR.LQ9EA
131h - - - - - - LQ9EA-10 LQ9EA-9
132h LQ10EA-8 LQ10EA-7 LQ10EA-6 LQ10EA-5 LQ10EA-4 LQ10EA-3 LQ10EA-2 LQ10EA-1
AR.LQ10EA
133h - - - - - - LQ10EA-10 LQ10EA-9
134h LQ11EA-8 LQ11EA-7 LQ11EA-6 LQ11EA-5 LQ11EA-4 LQ11EA-3 LQ11EA-2 LQ11EA-1
AR.LQ11EA
135h - - - - - - LQ11EA-10 LQ11EA-9
136h LQ12EA-8 LQ12EA-7 LQ12EA-6 LQ12EA-5 LQ12EA-4 LQ12EA-3 LQ12EA-2 LQ12EA-1
AR.LQ12EA
137h - - - - - - LQ12EA-10 LQ12EA-9
138h LQ13EA-8 LQ13EA-7 LQ13EA-6 LQ13EA-5 LQ13EA-4 LQ13EA-3 LQ13EA-2 LQ13EA-1
AR.LQ13EA
139h - - - - - - LQ13EA-10 LQ13EA-9
13Ah LQ14EA-8 LQ14EA-7 LQ14EA-6 LQ14EA-5 LQ14EA-4 LQ14EA-3 LQ14EA-2 LQ14EA-1
AR.LQ14EA
13Bh - - - - - - LQ14EA-10 LQ14EA-9
13Ch LQ15EA-8 LQ15EA-7 LQ15EA-6 LQ15EA-5 LQ15EA-4 LQ15EA-3 LQ15EA-2 LQ15EA-1
AR.LQ15EA
13Dh - - - - - - LQ15EA-10 LQ15EA-9
13Eh LQ16EA-8 LQ16EA-7 LQ16EA-6 LQ16EA-5 LQ16EA-4 LQ16EA-3 LQ16EA-2 LQ16EA-1
AR.LQ16EA
13Fh - - - - - - LQ16EA-10 LQ16EA-9
140h WQ1SA-8 WQ1SA-7 WQ1SA-6 WQ1SA-5 WQ1SA-4 WQ1SA-3 WQ1SA-2 WQ1SA-1
AR.WQ1SA
141h - - - - - WQ1QPR WQ1SA-10 WQ1SA-9
142h WQ2SA-8 WQ2SA-7 WQ2SA-6 WQ2SA-5 WQ2SA-4 WQ2SA-3 WQ2SA-2 WQ2SA-1
AR.WQ2SA
143h - - - - - WQ2QPR WQ2SA-10 WQ2SA-9
144h WQ3SA-8 WQ3SA-7 WQ3SA-6 WQ3SA-5 WQ3SA-4 WQ3SA-3 WQ3SA-2 WQ3SA-1
AR.WQ3SA
145h - - - - - WQ3QPR WQ3SA-10 WQ3SA-9
146h WQ4SA-8 WQ4SA-7 WQ4SA-6 WQ4SA-5 WQ4SA-4 WQ4SA-3 WQ4SA-2 WQ4SA-1
AR.WQ4SA
147h - - - - - WQ4QPR WQ4SA-10 WQ4SA-9
148h WQ5SA-8 WQ5SA-7 WQ5SA-6 WQ5SA-5 WQ5SA-4 WQ5SA-3 WQ5SA-2 WQ5SA-1
AR.WQ5SA
149h - - - - - WQ5QPR WQ5SA-10 WQ5SA-9
14Ah WQ6SA-8 WQ6SA-7 WQ6SA-6 WQ6SA-5 WQ6SA-4 WQ6SA-3 WQ6SA-2 WQ6SA-1
AR.WQ6SA
14Bh - - - - - WQ6QPR WQ6SA-10 WQ6SA-9
14Ch WQ7SA-8 WQ7SA-7 WQ7SA-6 WQ7SA-5 WQ7SA-4 WQ7SA-3 WQ7SA-2 WQ7SA-1
AR.WQ7SA
14Dh - - - - - WQ7QPR WQ7SA-10 WQ7SA-9
14Eh AR.WQ8SA WQ8SA-8 WQ8SA-7 WQ8SA-6 WQ8SA-5 WQ8SA-4 WQ8SA-3 WQ8SA-2 WQ8SA-1
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
14Fh - - - - - WQ8QPR WQ8SA-10 WQ8SA-9
150h WQ9SA-8 WQ9SA-7 WQ9SA-6 WQ9SA-5 WQ9SA-4 WQ9SA-3 WQ9SA-2 WQ9SA-1
AR.WQ9SA
151h - - - - - WQ9QPR WQ9SA-10 WQ9SA-9
152h WQ10SA-8 WQ10SA-7 WQ10SA-6 WQ10SA-5 WQ10SA-4 WQ10SA-3 WQ10SA-2 WQ10SA-1
AR.WQ10SA
153h - - - - - WQ10QPR WQ10SA-10 WQ10SA-9
154h WQ11SA-8 WQ11SA-7 WQ11SA-6 WQ11SA-5 WQ11SA-4 WQ11SA-3 WQ11SA-2 WQ11SA-1
AR.WQ11SA
155h - - - - - WQ11QPR WQ11SA-10 WQ11SA-9
156h WQ12SA-8 WQ12SA-7 WQ12SA-6 WQ12SA-5 WQ12SA-4 WQ12SA-3 WQ12SA-2 WQ12SA-1
AR.WQ12SA
157h - - - - - WQ12QPR WQ12SA-10 WQ12SA-9
158h WQ13SA-8 WQ13SA-7 WQ13SA-6 WQ13SA-5 WQ13SA-4 WQ13SA-3 WQ13SA-2 WQ13SA-1
AR.WQ13SA
159h - - - - - WQ13QPR WQ13SA-10 WQ13SA-9
15Ah WQ14SA-8 WQ14SA-7 WQ14SA-6 WQ14SA-5 WQ14SA-4 WQ14SA-3 WQ14SA-2 WQ14SA-1
AR.WQ14SA
15Bh - - - - - WQ14QPR WQ14SA-10 WQ14SA-9
15Ch WQ15SA-8 WQ15SA-7 WQ15SA-6 WQ15SA-5 WQ15SA-4 WQ15SA-3 WQ15SA-2 WQ15SA-1
AR.WQ15SA
15Dh - - - - - WQ15QPR WQ15SA-10 WQ15SA-9
15Eh WQ16SA-8 WQ16SA-7 WQ16SA-6 WQ16SA-5 WQ16SA-4 WQ16SA-3 WQ16SA-2 WQ16SA-1
AR.WQ16SA
15Fh - - - - - WQ16QPR WQ16SA-10 WQ16SA-9
160h WQ1EA-8 WQ1EA-7 WQ1EA-6 WQ1EA-5 WQ1EA-4 WQ1EA-3 WQ1EA-2 WQ1EA-1
AR.WQ1EA
161h - - - - - - WQ1EA-10 WQ1EA-9
162h WQ2EA-8 WQ2EA-7 WQ2EA-6 WQ2EA-5 WQ2EA-4 WQ2EA-3 WQ2EA-2 WQ2EA-1
AR.WQ2EA
163h - - - - - - WQ2EA-10 WQ2EA-9
164h WQ3EA-8 WQ3EA-7 WQ3EA-6 WQ3EA-5 WQ3EA-4 WQ3EA-3 WQ3EA-2 WQ3EA-1
AR.WQ3EA
165h - - - - - - WQ3EA-10 WQ3EA-9
166h WQ4EA-8 WQ4EA-7 WQ4EA-6 WQ4EA-5 WQ4EA-4 WQ4EA-3 WQ4EA-2 WQ4EA-1
AR.WQ4EA
167h - - - - - - WQ4EA-10 WQ4EA-9
168h WQ5EA-8 WQ5EA-7 WQ5EA-6 WQ5EA-5 WQ5EA-4 WQ5EA-3 WQ5EA-2 WQ5EA-1
AR.WQ5EA
169h - - - - - - WQ5EA-10 WQ5EA-9
16Ah WQ6EA-8 WQ6EA-7 WQ6EA-6 WQ6EA-5 WQ6EA-4 WQ6EA-3 WQ6EA-2 WQ6EA-1
AR.WQ6EA
16Bh - - - - - - WQ6EA-10 WQ6EA-9
16Ch WQ7EA-8 WQ7EA-7 WQ7EA-6 WQ7EA-5 WQ7EA-4 WQ7EA-3 WQ7EA-2 WQ7EA-1
AR.WQ7EA
16Dh - - - - - - WQ7EA-10 WQ7EA-9
16Eh WQ8EA-8 WQ8EA-7 WQ8EA-6 WQ8EA-5 WQ8EA-4 WQ8EA-3 WQ8EA-2 WQ8EA-1
AR.WQ8EA
16Fh - - - - - - WQ8EA-10 WQ8EA-9
170h WQ9EA-8 WQ9EA-7 WQ9EA-6 WQ9EA-5 WQ9EA-4 WQ9EA-3 WQ9EA-2 WQ9EA-1
AR.WQ9EA
171h - - - - - - WQ9EA-10 WQ9EA-9
172h WQ10EA-8 WQ10EA-7 WQ10EA-6 WQ10EA-5 WQ10EA-4 WQ10EA-3 WQ10EA-2 WQ10EA-1
AR.WQ10EA
173h - - - - - - WQ10EA-10 WQ10EA-9
174h WQ11EA-8 WQ11EA-7 WQ11EA-6 WQ11EA-5 WQ11EA-4 WQ11EA-3 WQ11EA-2 WQ11EA-1
AR.WQ11EA
175h - - - - - - WQ11EA-10 WQ11EA-9
176h WQ12EA-8 WQ12EA-7 WQ12EA-6 WQ12EA-5 WQ12EA-4 WQ12EA-3 WQ12EA-2 WQ12EA-1
AR.WQ12EA
177h - - - - - - WQ12EA-10 WQ12EA-9
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
178h WQ13EA-8 WQ13EA-7 WQ13EA-6 WQ13EA-5 WQ13EA-4 WQ13EA-3 WQ13EA-2 WQ13EA-1
AR.WQ13EA
179h - - - - - - WQ13EA-10 WQ13EA-9
17Ah WQ14EA-8 WQ14EA-7 WQ14EA-6 WQ14EA-5 WQ14EA-4 WQ14EA-3 WQ14EA-2 WQ14EA-1
AR.WQ14EA
17Bh - - - - - - WQ14EA-10 WQ14EA-9
17Ch WQ15EA-8 WQ15EA-7 WQ15EA-6 WQ15EA-5 WQ15EA-4 WQ15EA-3 WQ15EA-2 WQ15EA-1
AR.WQ15EA
17Dh - - - - - - WQ15EA-10 WQ15EA-9
17Eh WQ16EA-8 WQ16EA-7 WQ16EA-6 WQ16EA-5 WQ16EA-4 WQ16EA-3 WQ16EA-2 WQ16EA-1
AR.WQ16EA
17Fh - - - - - - WQ16EA-10 WQ16EA-9
180h LIQSA-8 LIQSA-7 LIQSA-6 LIQSA-5 LIQSA-4 LIQSA-3 LIQSA-2 LIQSA-1
AR.LIQSA
181h - - - - - LIQPR LIQSA-10 LIQSA-9
182h LIQEA-8 LIQEA-7 LIQEA-6 LIQEA-5 LIQEA-4 LIQEA-3 LIQEA-2 LIQEA-1
AR.LIQEA
183h - - - - - - LIQEA-10 LIQEA-9
184h LEQSA-8 LEQSA-7 LEQSA-6 LEQSA-5 LEQSA-4 LEQSA-3 LEQSA-2 LEQSA-1
AR.LEQSA
185h - - - - - LEQPR LEQSA-10 LEQSA-9
186h LEQEA-8 LEQEA-7 LEQEA-6 LEQEA-5 LEQEA-4 LEQEA-3 LEQEA-2 LEQEA-1
AR.LEQEA
187h - - - - - - LEQEA-10 LEQEA-9
188h WIQSA-8 WIQSA-7 WIQSA-6 WIQSA-5 WIQSA-4 WIQSA-3 WIQSA-2 WIQSA-1
AR.WIQSA
189h - - - - - WIQPR WIQSA-10 WIQSA-9
18Ah WIQEA-8 WIQEA-7 WIQEA-6 WIQEA-5 WIQEA-4 WIQEA-3 WIQEA-2 WIQEA-1
AR.WIQEA
18Bh - - - - - - WIQEA-10 WIQEA-9
18Ch WEQSA-8 WEQSA-7 WEQSA-6 WEQSA-5 WEQSA-4 WEQSA-3 WEQSA-2 WEQSA-1
AR.WEQSA
18Dh - - - - - WEQPR WEQSA-10 WEQSA-9
18Eh WEQEA-8 WEQEA-7 WEQEA-6 WEQEA-5 WEQEA-4 WEQEA-3 WEQEA-2 WEQEA-1
AR.WEQEA
18Fh - - - - - - WEQEA-10 WEQEA-9
190h LQW-8 LQW-7 LQW-6 LQW-5 LQW-4 LQW-3 LQW-2 LQW-1
AR.LQW
191h - - - LQW-13 LQW-12 LQW-11 LQW-10 LQW-9
192h WIRRW2 WIRRW1 WIENC2 WIENC-1 WISPL WIENA WQPD ASQPR
AR.MQC
193h - - - - - - FPEPD WQODE
194h LQ4RRW-2 LQ4RRW-1 LQ3RRW-2 LQ3RRW -1 LQ2RRW-2 LQ2RRW-1 LQ1RRW-2 LQ1RRW-1
AR.LQSC
195h - - - - - - - LQSM
196h BFTOA-8 BFTOA-7 BFTOA-6 BFTOA-5 BFTOA-4 BFTOA-3 BFTOA-2 BFTOA-1
AR.BFTOA
197h - - - - - - BFTOA-10 BFTOA-9
198h LQOS-8 LQOS-7 LQOS-6 LQOS-5 LQOS-4 LQOS-3 LQOS-2 LQOS-1
AR.LQOS
199h LQOS-16 LQOS-15 LQOS-14 LQOS-13 LQOS-12 LQOS-11 LQOS-10 LQOS-9
19Ah LQOIM-8 LQOIM-7 LQOIM-6 LQOIM-5 LQOIM-4 LQOIM-3 LQOIM-2 LQOIM-1
AR.LQOIM
19Bh LQOIM-16 LQOIM-15 LQOIM-14 LQOIM-13 LQOIM-12 LQOIM-11 LQOIM-10 LQOIM-9
19Ch LQNFS-8 LQNFS-7 LQNFS-6 LQNFS-5 LQNFS-4 LQNFS-3 LQNFS-2 LQNFS-1
AR.LQNFS
19Dh LQNFS-16 LQNFS-15 LQNFS-14 LQNFS-13 LQNFS-12 LQNFS-11 LQNFS-10 LQNFS-9
19Eh LQNFIM-8 LQNFIM-7 LQNFIM-6 LQNFIM-5 LQNFIM-4 LQNFIM-3 LQNFIM-2 LQNFIM-1
AR.LQNFIM
19Fh LQNFIM-16 LQNFIM-15 LQNFIM-14 LQNFIM-13 LQNFIM-12 LQNFIM-11 LQNFIM-10 LQNFIM-9
1A0h AR.WQOS WQOS-8 WQOS-7 WQOS-6 WQOS-5 WQOS-4 WQOS-3 WQOS-2 WQOS-1
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
1A1h WQOS-16 WQOS-15 WQOS-14 WQOS-13 WQOS-12 WQOS-11 WQOS-10 WQOS-9
1A2h WQOIM-8 WQOIM-7 WQOIM-6 WQOIM-5 WQOIM-4 WQOIM-3 WQOIM-2 WQOIM-1
AR.WQOIM
1A3h WQOIM-16 WQOIM-15 WQOIM-14 WQOIM-13 WQOIM-12 WQOIM-11 WQOIM-10 WQOIM-9
1A4h WQNFS-8 WQNFS-7 WQNFS-6 WQNFS-5 WQNFS-4 WQNFS-3 WQNFS-2 WQNFS-1
AR.WQNFS
1A5h WQNFS-16 WQNFS-15 WQNFS-14 WQNFS-13 WQNFS-12 WQNFS-11 WQNFS-10 WQNFS-9
1A6h WQNFIM-8 WQNFIM-7 WQNFIM-6 WQNFIM-5 WQNFIM-4 WQNFIM-3 WQNFIM-2 WQNFIM-1
AR.WQNFIM
1A7h WQNFIM-16 WQNFIM-15 WQNFIM-14 WQNFIM-13 WQNFIM-12 WQNFIM-11 WQNFIM-10 WQNFIM-9
1A8h - - - - - - WEQOS LEQOS
AR.EQOS
1A9h - - - - - - - -
1AAh - - - - - - WEQOIM LEQOIM
AR.EQOIM
1ABh - - - - - - - -
1ACh - - - EQOI WQNFI WQOI LCNFI LQOI
AR.BMIS
1ADh - - - - - - - -
Packet Processor 1(Encapsulator 1)
200h EIIS ELHDE ET1E ET2E ERE1 ERE0 TBRE EHCBO
PP.EMCR
201h EGCM EPRTSEL EFCSAD ECFCRD EFCS3216S - EFCSB EBBYS
202h ELHD23 ELHD22 ELHD21 ELHD20 ELHD19 ELHD18 ELHD17 ELHD16
PP.ELHHR
203h ELHD31 ELHD30 ELHD29 ELHD28 ELHD27 ELHD26 ELHD25 ELHD24
204h ELHD7 ELHD6 ELHD5 ELHD4 ELHD3 ELHD2 ELHD1 ELHD0
PP.ELHLR
205h ELHD15 ELHD14 ELHD13 ELHD12 ELHD11 ELHD10 ELHD9 ELHD8
206h ET1D23 ET1D22 ET1D21 ET1D20 ET1D19 ET1D18 ET1D17 ET1D16
PP.ET1DHR
207h ET1D31 ET1D30 ET1D29 ET1D28 ET1D27 ET1D26 ET1D25 ET1D24
208h ET1D7 ET1D6 ET1D5 ET1D4 ET1D3 ET1D2 ET1D1 ET1D0
PP.ET1DLR
209h ET1D15 ET1D14 ET1D13 ET1D12 ET1D11 ET1D10 ET1D9 ET1D8
20Ah ET2D23 ET2D22 ET2D21 ET2D20 ET2D19 ET2D18 ET2D17 ET2D16
PP.ET2DHR
20Bh ET2D31 ET2D30 ET2D29 ET2D28 ET2D27 ET2D26 ET2D25 ET2D24
20Ch ET2D7 ET2D6 ET2D5 ET2D4 ET2D3 ET2D2 ET2D1 ET2D0
PP.ET2DLR
20Dh ET2D15 ET2D14 ET2D13 ET2D12 ET2D11 ET2D10 ET2D9 ET2D8
20Eh EEI5 EEI4 EEI3 EEI2 EEI1 EEI0 ESEI -
PP.EEIR
20Fh EPLIEIE EDEIE EEFCSEIE EFCFEIE EBDEC1 EBDEC0 EEI7 EEI6
210h EFCNT7 EFCNT6 EFCNT5 EFCNT4 EFCNT3 EFCNT2 EFCNT1 EFCNT0
PP.EFCLSR
211h EFCNT15 EFCNT14 EFCNT13 EFCNT12 EFCNT11 EFCNT10 EFCNT9 EFCNT8
21Eh EOPLE EOPSE - FUF FOVF FLOK FF FE
PP.ESMLS
21Fh - - - - SOPLE SOPSE COPLE COPSE
220h EOPLEIE EOPSEIE - FUFIE FOVFIE FLOKIE FFIE FEIE
PP.ESMIE
221h - - - - SOPLEIE SOPSEIE COPLEIE COPSEIE
226h EHFL7 EHFL6 EHFL5 EHFL4 EHFL3 EHFL2 EHFL1 EHFL0
PP.EHFL
227h - - - - - - - -
Packet Processor 2(Encapsulator 2)
240h EIIS ELHDE ET1E ET2E ERE1 ERE0 TBRE EHCBO
PP.EMCR
241h EGCM EPRTSEL EFCSAD ECFCRD EFCS16EN - EFCSB EBBYS
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
242h ELHD23 ELHD22 ELHD21 ELHD20 ELHD19 ELHD18 ELHD17 ELHD16
PP.ELHHR
243h ELHD31 ELHD30 ELHD29 ELHD28 ELHD27 ELHD26 ELHD25 ELHD24
244h ELHD7 ELHD6 ELHD5 ELHD4 ELHD3 ELHD2 ELHD1 ELHD0
PP.ELHLR
245h ELHD15 ELHD14 ELHD13 ELHD12 ELHD11 ELHD10 ELHD9 ELHD8
246h ET1D23 ET1D22 ET1D21 ET1D20 ET1D19 ET1D18 ET1D17 ET1D16
PP.ET1DHR
247h ET1D31 ET1D30 ET1D29 ET1D28 ET1D27 ET1D26 ET1D25 ET1D24
248h ET1D7 ET1D6 ET1D5 ET1D4 ET1D3 ET1D2 ET1D1 ET1D0
PP.ET1DLR
249h ET1D15 ET1D14 ET1D13 ET1D12 ET1D11 ET1D10 ET1D9 ET1D8
24Ah ET2D23 ET2D22 ET2D21 ET2D20 ET2D19 ET2D18 ET2D17 ET2D16
PP.ET2DHR
24Bh ET2D31 ET2D30 ET2D29 ET2D28 ET2D27 ET2D26 ET2D25 ET2D24
24Ch ET2D7 ET2D6 ET2D5 ET2D4 ET2D3 ET2D2 ET2D1 ET2D0
PP.ET2DLR
24Dh ET2D15 ET2D14 ET2D13 ET2D12 ET2D11 ET2D10 ET2D9 ET2D8
24Eh EEI5 EEI4 EEI3 EEI2 EEI1 EEI0 ESEI -
PP.EEIR
24Fh EPLIEIE EDEIE EEFCSEIE EFCFEIE EBDEC1 EBDEC0 EEI7 EEI6
250h EFCNT7 EFCNT6 EFCNT5 EFCNT4 EFCNT3 EFCNT2 EFCNT1 EFCNT0
PP.EFCLSR
251h EFCNT15 EFCNT14 EFCNT13 EFCNT12 EFCNT11 EFCNT10 EFCNT9 EFCNT8
25Eh EOPLE EOPSE - FUF FOVF FLOK FF FE
PP.ESMLS
25Fh - - - - SOPLE SOPSE COPLE COPSE
260h EOPLEIE EOPSEIE - FUFIE FOVFIE FLOKIE FFIE FEIE
PP.ESMIE
261h - - - - SOPLEIE SOPSEIE COPLEIE COPSEIE
266h EHFL7 EHFL6 EHFL5 EHFL4 EHFL3 EHFL2 EHFL1 EHFL0
PP.EHFL
267h - - - - - - - -
Packet Processor 3 (Encapsulator 3)
280h EIIS ELHDE ET1E ET2E ERE1 ERE0 TBRE EHCBO
PP.EMCR
281h EGCM EPRTSEL EFCSAD ECFCRD EFCS16EN - EFCSB EBBYS
282h ELHD23 ELHD22 ELHD21 ELHD20 ELHD19 ELHD18 ELHD17 ELHD16
PP.ELHHR
283h ELHD31 ELHD30 ELHD29 ELHD28 ELHD27 ELHD26 ELHD25 ELHD24
284h ELHD7 ELHD6 ELHD5 ELHD4 ELHD3 ELHD2 ELHD1 ELHD0
PP.ELHLR
285h ELHD15 ELHD14 ELHD13 ELHD12 ELHD11 ELHD10 ELHD9 ELHD8
286h ET1D23 ET1D22 ET1D21 ET1D20 ET1D19 ET1D18 ET1D17 ET1D16
PP.ET1DHR
287h ET1D31 ET1D30 ET1D29 ET1D28 ET1D27 ET1D26 ET1D25 ET1D24
288h ET1D7 ET1D6 ET1D5 ET1D4 ET1D3 ET1D2 ET1D1 ET1D0
PP.ET1DLR
289h ET1D15 ET1D14 ET1D13 ET1D12 ET1D11 ET1D10 ET1D9 ET1D8
28Ah ET2D23 ET2D22 ET2D21 ET2D20 ET2D19 ET2D18 ET2D17 ET2D16
PP.ET2DHR
28Bh ET2D31 ET2D30 ET2D29 ET2D28 ET2D27 ET2D26 ET2D25 ET2D24
28Ch ET2D7 ET2D6 ET2D5 ET2D4 ET2D3 ET2D2 ET2D1 ET2D0
PP.ET2DLR
28Dh ET2D15 ET2D14 ET2D13 ET2D12 ET2D11 ET2D10 ET2D9 ET2D8
28Eh EEI5 EEI4 EEI3 EEI2 EEI1 EEI0 ESEI -
PP.EEIR
28Fh EPLIEIE EDEIE EEFCSEIE EFCFEIE EBDEC1 EBDEC0 EEI7 EEI6
290h EFCNT7 EFCNT6 EFCNT5 EFCNT4 EFCNT3 EFCNT2 EFCNT1 EFCNT0
PP.EFCLSR
291h EFCNT15 EFCNT14 EFCNT13 EFCNT12 EFCNT11 EFCNT10 EFCNT9 EFCNT8
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
29Eh EOPLE EOPSE - FUF FOVF FLOK FF FE
PP.ESMLS
29Fh - - - - SOPLE SOPSE COPLE COPSE
2A0h EOPLEIE EOPSEIE - FUFIE FOVFIE FLOKIE FFIE FEIE
PP.ESMIE
2A1h - - - - SOPLEIE SOPSEIE COPLEIE COPSEIE
2A6h EHFL7 EHFL6 EHFL5 EHFL4 EHFL3 EHFL2 EHFL1 EHFL0
PP.EHFL
2A7h - - - - - - - -
Packet Processor 4(Encapsulator 4)
2C0h EIIS ELHDE ET1E ET2E ERE1 ERE0 TBRE EHCBO
PP.EMCR
2C1h EGCM EPRTSEL EFCSAD ECFCRD EFCS16EN - EFCSB EBBYS
2C2h ELHD23 ELHD22 ELHD21 ELHD20 ELHD19 ELHD18 ELHD17 ELHD16
PP.ELHHR
2C3h ELHD31 ELHD30 ELHD29 ELHD28 ELHD27 ELHD26 ELHD25 ELHD24
2C4h ELHD7 ELHD6 ELHD5 ELHD4 ELHD3 ELHD2 ELHD1 ELHD0
PP.ELHLR
2C5h ELHD15 ELHD14 ELHD13 ELHD12 ELHD11 ELHD10 ELHD9 ELHD8
2C6h ET1D23 ET1D22 ET1D21 ET1D20 ET1D19 ET1D18 ET1D17 ET1D16
PP.ET1DHR
2C7h ET1D31 ET1D30 ET1D29 ET1D28 ET1D27 ET1D26 ET1D25 ET1D24
2C8h ET1D7 ET1D6 ET1D5 ET1D4 ET1D3 ET1D2 ET1D1 ET1D0
PP.ET1DLR
2C9h ET1D15 ET1D14 ET1D13 ET1D12 ET1D11 ET1D10 ET1D9 ET1D8
2CAh ET2D23 ET2D22 ET2D21 ET2D20 ET2D19 ET2D18 ET2D17 ET2D16
PP.ET2DHR
2CBh ET2D31 ET2D30 ET2D29 ET2D28 ET2D27 ET2D26 ET2D25 ET2D24
2CCh ET2D7 ET2D6 ET2D5 ET2D4 ET2D3 ET2D2 ET2D1 ET2D0
PP.ET2DLR
2CDh ET2D15 ET2D14 ET2D13 ET2D12 ET2D11 ET2D10 ET2D9 ET2D8
2CEh EEI5 EEI4 EEI3 EEI2 EEI1 EEI0 ESEI -
PP.EEIR
2CFh EPLIEIE EDEIE EEFCSEIE EFCFEIE EBDEC1 EBDEC0 EEI7 EEI6
2D0h EFCNT7 EFCNT6 EFCNT5 EFCNT4 EFCNT3 EFCNT2 EFCNT1 EFCNT0
PP.EFCLSR
2D1h EFCNT15 EFCNT14 EFCNT13 EFCNT12 EFCNT11 EFCNT10 EFCNT9 EFCNT8
2DEh EOPLE EOPSE - FUF FOVF FLOK FF FE
PP.ESMLS
2DFh - - - - SOPLE SOPSE COPLE COPSE
2E0h EOPLEIE EOPSEIE - FUFIE FOVFIE FLOKIE FFIE FEIE
PP.ESMIE
2E1h - - - - SOPLEIE SOPSEIE COPLEIE COPSEIE
2E6h EHFL7 EHFL6 EHFL5 EHFL4 EHFL3 EHFL2 EHFL1 EHFL0
PP.EHFL
2E7h - - - - - - - -
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
Packet Processor 1(Decapsulator 1)
300h DR1E DR2E DR3E DAE1 DAE0 DGSC DHRAE DHCBO
PP.DMCR
301h DGCM DPRTSEL DFCSAD DCFCRD DFCS16EN - DBBS RBRE
302h D1D7D D1D6D D1D5D D1D4D D1D3D D1D2D D1D1D D1D0D
PP.DA1DR
303h D1D15D D1D14D D1D13D D1D12D D1D11D D1D10D D1D9D D1D8D
304h D2D7D D2D6D D2D5D D2D4D D2D3D D2D2D D2D1D D2D0D
PP.DA2DR
305h D2D15D D2D14D D2D13D D2D12D D2D11D D2D10D D2D9D D2D8D
306h D3D7D D3D6D D3D5D D3D4D D3D3D D3D2D D3D1D D3D0D
PP.DA3DR
307h D3D15D D3D14D D3D13D D3D12D D3D11D D3D10D D3D9D D3D8D
308h D4D7D D4D6D D4D5D D4D4D D4D3D D4D2D D4D1D D4D0D
PP.DA4DR
309h D4D15D D4D14D D4D13D D4D12D D4D11D D4D10D D4D9D D4D8D
30Ah D5D7D D5D6D D5D5D D5D4D D5D3D D5D2D D5D1D D5D0D
PP.DA5DR
30Bh D5D15D D5D14D D5D13D D5D12D D5D11D D5D10D D5D9D D5D8D
30Ch D6D7D D6D6D D6D5D D6D4D D6D3D D6D2D D6D1D D6D0D
PP.DA6DR
30Dh D6D15D D6D14D D6D13D D6D12D D6D11D D6D10D D6D9D D6D8D
30Eh D7D7D D7D6D D7D5D D7D4D D7D3D D7D2D D7D1D D7D0D
PP.DA7DR
30Fh D7D15D D7D14D D7D13D D7D12D D7D11D D7D10D D7D9D D7D8D
310h D8D7D D8D6D D8D5D D8D4D D8D3D D8D2D D8D1D D8D0D
PP.DA8DR
311h D8D15D D8D14D D8D13D D8D12D D8D11D D8D10D D8D9D D8D8D
312h D9D7D D9D6D D9D5D D9D4D D9D3D D9D2D D9D1D D9D0D
PP.DA9DR
313h D9D15D D9D14D D9D13D D9D12D D9D11D D9D10D D9D9D D9D8D
314h DFUR DFOVF - - - - - -
PP.DMLSR
315h DGSLS DGSLLS DGLCLS DGLCSLS DFFLS - DCHECFLS DTCHECFLS
316h DFURIE DFOVFIE - - - - - -
PP.DMLSIE
317h DGSIE DGSLIE DGLCIE DGLCSIE DFFIE - DCHECFIE DTCHECFIE
318h DGPLC7 DGPLC6 DGPLC5 DGPLC4 DGPLC3 DGPLC2 DGPLC1 DGPLC0
PP.DGPLC
319h DGPLC15 DGPLC14 DGPLC13 DGPLC12 DGPLC11 DGPLC10 DGPLC9 DGPLC8
31Ah DBPLC7 DBPLC6 DBPLC5 DBPLC4 DBPLC3 DBPLC2 DBPLC1 DBPLC0
PP.DGBLC
31Bh DBPLC15 DBPLC14 DBPLC13 DBPLC12 DBPLC11 DBPLC10 DBPLC9 DBPLC8
31Ch - - - - - DGSYNC DGPSYNC DGHUNT
PP.DSSR
31Dh - - - - - - - -
31Eh DHSR23 DHSR22 DHSR21 DHSR20 DHSR19 DHSR18 DHSR17 DHSR16
PP.DHHSR
31Fh DHSR31 DHSR30 DHSR29 DHSR28 DHSR27 DHSR26 DHSR25 DHSR24
320h DHSR7 DHSR6 DHSR5 DHSR4 DHSR3 DHSR2 DHSR1 DHSR0
PP.DHLSR
321h DHSR15 DHSR14 DHSR13 DHSR12 DHSR11 DHSR10 DHSR9 DHSR8
322h - - - DEM DSMRE DEPRE DFSRPWC
PP.DFSCR
323h - - - - - - - -
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
Packet Processor 2 (Decapsulator 2)
340h DR1E DR2E DR3E DAE1 DAE0 DGSC DHRAE DHCBO
PP.DMCR
341h DGCM DPRTSEL DFCSAD DCFCRD DFCS16EN - DBBS RBRE
342h D1D7D D1D6D D1D5D D1D4D D1D3D D1D2D D1D1D D1D0D
PP.DA1DR
343h D1D15D D1D14D D1D13D D1D12D D1D11D D1D10D D1D9D D1D8D
344h D2D7D D2D6D D2D5D D2D4D D2D3D D2D2D D2D1D D2D0D
PP.DA2DR
345h D2D15D D2D14D D2D13D D2D12D D2D11D D2D10D D2D9D D2D8D
346h D3D7D D3D6D D3D5D D3D4D D3D3D D3D2D D3D1D D3D0D
PP.DA3DR
347h D3D15D D3D14D D3D13D D3D12D D3D11D D3D10D D3D9D D3D8D
348h D4D7D D4D6D D4D5D D4D4D D4D3D D4D2D D4D1D D4D0D
PP.DA4DR
349h D4D15D D4D14D D4D13D D4D12D D4D11D D4D10D D4D9D D4D8D
34Ah D5D7D D5D6D D5D5D D5D4D D5D3D D5D2D D5D1D D5D0D
PP.DA5DR
34Bh D5D15D D5D14D D5D13D D5D12D D5D11D D5D10D D5D9D D5D8D
34Ch D6D7D D6D6D D6D5D D6D4D D6D3D D6D2D D6D1D D6D0D
PP.DA6DR
34Dh D6D15D D6D14D D6D13D D6D12D D6D11D D6D10D D6D9D D6D8D
34Eh D7D7D D7D6D D7D5D D7D4D D7D3D D7D2D D7D1D D7D0D
PP.DA7DR
34Fh D7D15D D7D14D D7D13D D7D12D D7D11D D7D10D D7D9D D7D8D
350h D8D7D D8D6D D8D5D D8D4D D8D3D D8D2D D8D1D D8D0D
PP.DA8DR
351h D8D15D D8D14D D8D13D D8D12D D8D11D D8D10D D8D9D D8D8D
352h D9D7D D9D6D D9D5D D9D4D D9D3D D9D2D D9D1D D9D0D
PP.DA9DR
353h D9D15D D9D14D D9D13D D9D12D D9D11D D9D10D D9D9D D9D8D
354h DFUR DFOVF - - - - - -
PP.DMLSR
355h DGSLS DGSLLS DGLCLS DGLCSLS DFFLS - DCHECFLS DTCHECFLS
356h DFURIE DFOVFIE - - - - - -
PP.DMLSIE DCHECFI
357h DGSIE DGSLIE DGLCIE DGLCSIE DFFIE - DTCHECFIE
E
358h DGPLC7 DGPLC6 DGPLC5 DGPLC4 DGPLC3 DGPLC2 DGPLC1 DGPLC0
PP.DGPLC
359h DGPLC15 DGPLC14 DGPLC13 DGPLC12 DGPLC11 DGPLC10 DGPLC9 DGPLC8
35Ah DBPLC7 DBPLC6 DBPLC5 DBPLC4 DBPLC3 DBPLC2 DBPLC1 DBPLC0
PP.DGBLC
35Bh DBPLC15 DBPLC14 DBPLC13 DBPLC12 DBPLC11 DBPLC10 DBPLC9 DBPLC8
35Ch - - - - - DGSYNC DGPSYNC DGHUNT
PP.DSSR
35Dh - - - - - - - -
35Eh DHSR23 DHSR22 DHSR21 DHSR20 DHSR19 DHSR18 DHSR17 DHSR16
PP.DHHSR
35Fh DHSR31 DHSR30 DHSR29 DHSR28 DHSR27 DHSR26 DHSR25 DHSR24
360h DHSR7 DHSR6 DHSR5 DHSR4 DHSR3 DHSR2 DHSR1 DHSR0
PP.DHLSR
361h DHSR15 DHSR14 DHSR13 DHSR12 DHSR11 DHSR10 DHSR9 DHSR8
362h - - - - DEM DSMRE DEPRE DFSRPWC
PP.DFSCR
363h - - - - - - - -
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
Packet Processor 3(Decapsulator 3)
380h DR1E DR2E DR3E DAE1 DAE0 DGSC DHRAE DHCBO
PP.DMCR
381h DGCM DPRTSEL DFCSAD DCFCRD DFCS16EN - DBBS RBRE
382h D1D7D D1D6D D1D5D D1D4D D1D3D D1D2D D1D1D D1D0D
PP.DA1DR
383h D1D15D D1D14D D1D13D D1D12D D1D11D D1D10D D1D9D D1D8D
384h D2D7D D2D6D D2D5D D2D4D D2D3D D2D2D D2D1D D2D0D
PP.DA2DR
385h D2D15D D2D14D D2D13D D2D12D D2D11D D2D10D D2D9D D2D8D
386h D3D7D D3D6D D3D5D D3D4D D3D3D D3D2D D3D1D D3D0D
PP.DA3DR
387h D3D15D D3D14D D3D13D D3D12D D3D11D D3D10D D3D9D D3D8D
388h D4D7D D4D6D D4D5D D4D4D D4D3D D4D2D D4D1D D4D0D
PP.DA4DR
389h D4D15D D4D14D D4D13D D4D12D D4D11D D4D10D D4D9D D4D8D
38Ah D5D7D D5D6D D5D5D D5D4D D5D3D D5D2D D5D1D D5D0D
PP.DA5DR
38Bh D5D15D D5D14D D5D13D D5D12D D5D11D D5D10D D5D9D D5D8D
38Ch D6D7D D6D6D D6D5D D6D4D D6D3D D6D2D D6D1D D6D0D
PP.DA6DR
38Dh D6D15D D6D14D D6D13D D6D12D D6D11D D6D10D D6D9D D6D8D
38Eh D7D7D D7D6D D7D5D D7D4D D7D3D D7D2D D7D1D D7D0D
PP.DA7DR
38Fh D7D15D D7D14D D7D13D D7D12D D7D11D D7D10D D7D9D D7D8D
390h D8D7D D8D6D D8D5D D8D4D D8D3D D8D2D D8D1D D8D0D
PP.DA8DR
391h D8D15D D8D14D D8D13D D8D12D D8D11D D8D10D D8D9D D8D8D
392h D9D7D D9D6D D9D5D D9D4D D9D3D D9D2D D9D1D D9D0D
PP.DA9DR
393h D9D15D D9D14D D9D13D D9D12D D9D11D D9D10D D9D9D D9D8D
394h DFUR DFOVF - - - - - -
PP.DMLSR
395h DGSLS DGSLLS DGLCLS DGLCSLS DFFLS - DCHECFLS DTCHECFLS
396h DFURIE DFOVFIE - - - - - -
PP.DMLSIE DCHECFI
397h DGSIE DGSLIE DGLCIE DGLCSIE DFFIE - DTCHECFIE
E
398h DGPLC7 DGPLC6 DGPLC5 DGPLC4 DGPLC3 DGPLC2 DGPLC1 DGPLC0
PP.DGPLC
399h DGPLC15 DGPLC14 DGPLC13 DGPLC12 DGPLC11 DGPLC10 DGPLC9 DGPLC8
39Ah DBPLC7 DBPLC6 DBPLC5 DBPLC4 DBPLC3 DBPLC2 DBPLC1 DBPLC0
PP.DGBLC
39Bh DBPLC15 DBPLC14 DBPLC13 DBPLC12 DBPLC11 DBPLC10 DBPLC9 DBPLC8
39Ch - - - - - DGSYNC DGPSYNC DGHUNT
PP.DSSR
39Dh - - - - - - - -
39Eh DHSR23 DHSR22 DHSR21 DHSR20 DHSR19 DHSR18 DHSR17 DHSR16
PP.DHHSR
39Fh DHSR31 DHSR30 DHSR29 DHSR28 DHSR27 DHSR26 DHSR25 DHSR24
3A0h DHSR7 DHSR6 DHSR5 DHSR4 DHSR3 DHSR2 DHSR1 DHSR0
PP.DHLSR
3A1h DHSR15 DHSR14 DHSR13 DHSR12 DHSR11 DHSR10 DHSR9 DHSR8
3A2h - - - - DEM DSMRE DEPRE DFSRPWC
PP.DFSCR
3A3h - - - - - - - -
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
Packet Processor 4(Decapsulator 4)
3C0h DR1E DR2E DR3E DAE1 DAE0 DGSC DHRAE DHCBO
PP.DMCR
3C1h DGCM DPRTSEL DFCSAD DCFCRD DFCS16EN - DBBS RBRE
3C2h D1D7D D1D6D D1D5D D1D4D D1D3D D1D2D D1D1D D1D0D
PP.DA1DR
3C3h D1D15D D1D14D D1D13D D1D12D D1D11D D1D10D D1D9D D1D8D
3C4h D2D7D D2D6D D2D5D D2D4D D2D3D D2D2D D2D1D D2D0D
PP.DA2DR
3C5h D2D15D D2D14D D2D13D D2D12D D2D11D D2D10D D2D9D D2D8D
3C6h D3D7D D3D6D D3D5D D3D4D D3D3D D3D2D D3D1D D3D0D
PP.DA3DR
3C7h D3D15D D3D14D D3D13D D3D12D D3D11D D3D10D D3D9D D3D8D
3C8h D4D7D D4D6D D4D5D D4D4D D4D3D D4D2D D4D1D D4D0D
PP.DA4DR
3C9h D4D15D D4D14D D4D13D D4D12D D4D11D D4D10D D4D9D D4D8D
3CAh D5D7D D5D6D D5D5D D5D4D D5D3D D5D2D D5D1D D5D0D
PP.DA5DR
3CBh D5D15D D5D14D D5D13D D5D12D D5D11D D5D10D D5D9D D5D8D
3CCh D6D7D D6D6D D6D5D D6D4D D6D3D D6D2D D6D1D D6D0D
PP.DA6DR
3CDh D6D15D D6D14D D6D13D D6D12D D6D11D D6D10D D6D9D D6D8D
3CEh D7D7D D7D6D D7D5D D7D4D D7D3D D7D2D D7D1D D7D0D
PP.DA7DR
3CFh D7D15D D7D14D D7D13D D7D12D D7D11D D7D10D D7D9D D7D8D
3D0h D8D7D D8D6D D8D5D D8D4D D8D3D D8D2D D8D1D D8D0D
PP.DA8DR
3D1h D8D15D D8D14D D8D13D D8D12D D8D11D D8D10D D8D9D D8D8D
3D2h D9D7D D9D6D D9D5D D9D4D D9D3D D9D2D D9D1D D9D0D
PP.DA9DR
3D3h D9D15D D9D14D D9D13D D9D12D D9D11D D9D10D D9D9D D9D8D
3D4h DFUR DFOVF - - - - - -
PP.DMLSR
3D5h DGSLS DGSLLS DGLCLS DGLCSLS DFFLS - DCHECFLS DTCHECFLS
3D6h DFURIE DFOVFIE - - - - - -
PP.DMLSIE DCHECFI
3D7h DGSIE DGSLIE DGLCIE DGLCSIE DFFIE - DTCHECFIE
E
3D8h DGPLC7 DGPLC6 DGPLC5 DGPLC4 DGPLC3 DGPLC2 DGPLC1 DGPLC0
PP.DGPLC
3D9h DGPLC15 DGPLC14 DGPLC13 DGPLC12 DGPLC11 DGPLC10 DGPLC9 DGPLC8
3DAh DBPLC7 DBPLC6 DBPLC5 DBPLC4 DBPLC3 DBPLC2 DBPLC1 DBPLC0
PP.DGBLC
3DBh DBPLC15 DBPLC14 DBPLC13 DBPLC12 DBPLC11 DBPLC10 DBPLC9 DBPLC8
3DCh - - - - - DGSYNC DGPSYNC DGHUNT
PP.DSSR
3DDh - - - - - - - -
3DEh DHSR23 DHSR22 DHSR21 DHSR20 DHSR19 DHSR18 DHSR17 DHSR16
PP.DHHSR
3DFh DHSR31 DHSR30 DHSR29 DHSR28 DHSR27 DHSR26 DHSR25 DHSR24
3E0h DHSR7 DHSR6 DHSR5 DHSR4 DHSR3 DHSR2 DHSR1 DHSR0
PP.DHLSR
3E1h DHSR15 DHSR14 DHSR13 DHSR12 DHSR11 DHSR10 DHSR9 DHSR8
3E2h - - - - DEM DSMRE DEPRE DFSRPWC
PP.DFSCR
3E3h - - - - - - - -
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
VCAT / LCAS TRANSMIT REGISTERS
400h V4FM1 V4FM0 V3FM1 V3FM0 V2FM1 V2FM0 V1FM1 V1FM0
VCAT.TCR1
401h - - - - TGIDBC TGIDM TLOAD TVBLKEN
402h TV2MC3 TV2MC2 TV2MC1 TV2MC0 TV1MC3 TV1MC2 TV1MC1 TV1MC0
VCAT.TCR2
403h TV4MC3 TV4MC2 TV4MC1 TV4MC0 TV3MC3 TV3MC2 TV3MC1 TV3MC0
406h - - - - RSACK4 RSACK3 RSACK2 RSACK1
VCAT.TLCR1
407h - - - - - - - -
408h - - - - ATMSTD4 ATMSTD3 ATMSTD2 ATMSTD1
VCAT.TLCR2
409h - - - - - - - -
40Ah V1MST7 V1MST6 V1MST5 V1MST4 V1MST3 V1MST2 V1MST1 V1MST0
VCAT.TLCR3
40Bh V1MST15 V1MST14 V1MST13 V1MST12 V1MST11 V1MST10 V1MST9 V1MST8
40Ch V2MST7 V2MST6 V2MST5 V2MST4 V2MST3 V2MST2 V2MST1 V2MST0
VCAT.TLCR4
40Dh V2MST15 V2MST14 V2MST13 V2MST12 V2MST11 V2MST10 V2MST9 V2MST8
40Eh V3MST7 V3MST6 V3MST5 V3MST4 V3MST3 V3MST2 V3MST1 V3MST0
VCAT.TLCR5
40Fh V3MST15 V3MST14 V3MST13 V3MST12 V3MST11 V3MST10 V3MST9 V3MST8
410h V4MST7 V4MST6 V4MST5 V4MST4 V4MST3 V4MST2 V4MST1 V4MST0
VCAT.TLCR6
411h V4MST15 V4MST14 V4MST13 V4MST12 V4MST11 V4MST10 V4MST9 V4MST8
420h - - - TNVCGC TVGS2 TVGS1 TVGS0 TPA
VCAT.TCR3(1)
421h - - - - TVSQ3 TVSQ2 TVSQ1 TVSQ0
422h - - - TNVCGC TVGS2 TVGS1 TVGS0 TPA
VCAT.TCR3(2)
423h - - - - TVSQ3 TVSQ2 TVSQ1 TVSQ0
424h - - - TNVCGC TVGS2 TVGS1 TVGS0 TPA
VCAT.TCR3(3)
425h - - - - TVSQ3 TVSQ2 TVSQ1 TVSQ0
426h - - - TNVCGC TVGS2 TVGS1 TVGS0 TPA
VCAT.TCR3(4)
427h - - - - TVSQ3 TVSQ2 TVSQ1 TVSQ0
428h - - - TNVCGC TVGS2 TVGS1 TVGS0 TPA
VCAT.TCR3(5)
429h - - - - TVSQ3 TVSQ2 TVSQ1 TVSQ0
42Ah - - - TNVCGC TVGS2 TVGS1 TVGS0 TPA
VCAT.TCR3(6)
42Bh - - - - TVSQ3 TVSQ2 TVSQ1 TVSQ0
42Ch - - - TNVCGC TVGS2 TVGS1 TVGS0 TPA
VCAT.TCR3(7)
42Dh - - - - TVSQ3 TVSQ2 TVSQ1 TVSQ0
42Eh - - - TNVCGC TVGS2 TVGS1 TVGS0 TPA
VCAT.TCR3(8)
42Fh - - - - TVSQ3 TVSQ2 TVSQ1 TVSQ0
430h - - - TNVCGC TVGS2 TVGS1 TVGS0 TPA
VCAT.TCR3(9)
431h - - - - TVSQ3 TVSQ2 TVSQ1 TVSQ0
432h - - - TNVCGC TVGS2 TVGS1 TVGS0 TPA
VCAT.TCR3(10)
433h - - - - TVSQ3 TVSQ2 TVSQ1 TVSQ0
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
434h - - - TNVCGC TVGS2 TVGS1 TVGS0 TPA
VCAT.TCR3(11)
435h - - - - TVSQ3 TVSQ2 TVSQ1 TVSQ0
436h - - - TNVCGC TVGS2 TVGS1 TVGS0 TPA
VCAT.TCR3(12)
437h - - - - TVSQ3 TVSQ2 TVSQ1 TVSQ0
438h - - - TNVCGC TVGS2 TVGS1 TVGS0 TPA
VCAT.TCR3(13)
439h - - - - TVSQ3 TVSQ2 TVSQ1 TVSQ0
43Ah - - - TNVCGC TVGS2 TVGS1 TVGS0 TPA
VCAT.TCR3(14)
43Bh - - - - TVSQ3 TVSQ2 TVSQ1 TVSQ0
43Ch - - - TNVCGC TVGS2 TVGS1 TVGS0 TPA
VCAT.TCR3(15)
43Dh - - - - TVSQ3 TVSQ2 TVSQ1 TVSQ0
43Eh - - - TNVCGC TVGS2 TVGS1 TVGS0 TPA
VCAT.TCR3(16)
43Fh - - - - TVSQ3 TVSQ2 TVSQ1 TVSQ0
440h - - - - CTRL3 CTRL2 CTRL1 CTRL0
VCAT.TLCR8(1)
441h - - - - - - - -
442h - - - - CTRL3 CTRL2 CTRL1 CTRL0
VCAT.TLCR8(2)
443h - - - - - - - -
444h - - - - CTRL3 CTRL2 CTRL1 CTRL0
VCAT.TLCR8(3)
445h - - - - - - - -
446h - - - - CTRL3 CTRL2 CTRL1 CTRL0
VCAT.TLCR8(4)
447h - - - - - - - -
448h - - - - CTRL3 CTRL2 CTRL1 CTRL0
VCAT.TLCR8(5)
449h - - - - - - - -
44Ah - - - - CTRL3 CTRL2 CTRL1 CTRL0
VCAT.TLCR8(6)
44Bh - - - - - - - -
44Ch - - - - CTRL3 CTRL2 CTRL1 CTRL0
VCAT.TLCR8(7)
44Dh - - - - - - - -
44Eh - - - - CTRL3 CTRL2 CTRL1 CTRL0
VCAT.TLCR8(8)
44Fh - - - - - - - -
450h - - - - CTRL3 CTRL2 CTRL1 CTRL0
VCAT.TLCR8(9)
451h - - - - - - - -
452h - - - - CTRL3 CTRL2 CTRL1 CTRL0
VCAT.TLCR8(10)
453h - - - - - - - -
454h - - - - CTRL3 CTRL2 CTRL1 CTRL0
VCAT.TLCR8(11)
455h - - - - - - - -
456h - - - - CTRL3 CTRL2 CTRL1 CTRL0
VCAT.TLCR8(12)
457h - - - - - - - -
458h - - - - CTRL3 CTRL2 CTRL1 CTRL0
VCAT.TLCR8(13)
459h - - - - - - - -
45Ah - - - - CTRL3 CTRL2 CTRL1 CTRL0
VCAT.TLCR8(14)
45Bh - - - - - - - -
45Ch VCAT.TLCR8(15) - - - - CTRL3 CTRL2 CTRL1 CTRL0
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
45Dh - - - - - - - -
45Eh - - - - CTRL3 CTRL2 CTRL1 CTRL0
VCAT.TLCR8(16)
45Fh - - - - - - - -
480h TGID7 TGID6 TGID5 TGID4 TGID3 TGID2 TGID1 TGID0
VCAT.TCR4(1)
481h TGID15 TGID14 TGID13 TGID12 TGID11 TGID10 TGID9 TGID8
482h TGID7 TGID6 TGID5 TGID4 TGID3 TGID2 TGID1 TGID0
VCAT.TCR4(2)
483h TGID15 TGID14 TGID13 TGID12 TGID11 TGID10 TGID9 TGID8
484h TGID7 TGID6 TGID5 TGID4 TGID3 TGID2 TGID1 TGID0
VCAT.TCR4(3)
485h TGID15 TGID14 TGID13 TGID12 TGID11 TGID10 TGID9 TGID8
486h TGID7 TGID6 TGID5 TGID4 TGID3 TGID2 TGID1 TGID0
VCAT.TCR4(4)
487h TGID15 TGID14 TGID13 TGID12 TGID11 TGID10 TGID9 TGID8
VCAT / LCAS RECEIVE REGISTERS
500h - - SVINTD T3T1WG4 T3T1WG3 T3T1WG2 T3T1WG1 RVBLKEN
VCAT.RCR1
501h - - - RVEN4 RGIDBC RVEN3 RVEN2 RVEN1
502h LE4 LE3 LE2 LE1 REALIGN4 REALIGN3 REALIGN2 REALIGN1
VCAT.RCR2
503h - - - - - - - -
504h RV2MC3 RV2MC2 RV2MC1 RV2MC0 RV1MC3 RV1MC2 RV1MC1 RV1MC0
VCAT.RCR3
505h RV4MC3 RV4MC2 RV4MC1 RV4MC0 RV3MC3 RV3MC2 RV3MC1 RV3MC0
508h PISR8 PISR7 PISR6 PISR5 PISR4 PISR3 PISR2 PISR1
VCAT.RISR
509h PISR16 PISR15 PISR14 PISR13 PISR12 PISR11 PISR10 PISR9
50Ah V1MST7 V1MST6 V1MST5 V1MST4 V1MST3 V1MST2 V1MST1 V1MST0
VCAT.RLSR1
50Bh V1MST15 V1MST14 V1MST13 V1MST12 V1MST11 V1MST10 V1MST9 V1MST8
50Ch V2MST7 V2MST6 V2MST5 V2MST4 V2MST3 V2MST2 V2MST1 V2MST0
VCAT.RLSR2
50Dh V2MST15 V2MST14 V2MST13 V2MST12 V2MST11 V2MST10 V2MST9 V2MST8
50Eh V3MST7 V3MST6 V3MST5 V3MST4 V3MST3 V3MST2 V3MST1 V3MST0
VCAT.RLSR3
50Fh V3MST15 V3MST14 V3MST13 V3MST12 V3MST11 V3MST10 V3MST9 V3MST8
510h V4MST7 V4MST6 V4MST5 V4MST4 V4MST3 V4MST2 V4MST1 V4MST0
VCAT.RLSR4
511h V4MST15 V4MST14 V4MST13 V4MST12 V4MST11 V4MST10 V4MST9 V4MST8
512h DDE4 DDE3 DDE2 DDE1 REALIGNL4 REALIGNL3 REALIGNL2 REALIGNL1
VCAT.RRLSR
513h - - - - VMSTC4 VMSTC3 VMSTC2 VMSTC1
514h VDDEIE4 VDDEIE3 VDDEIE2 VDDEIE1 REALIGNIE4 REALIGNIE3 REALIGNIE2 REALIGNIE1
VCAT.RRSIE
515h - - - - VMSTCIE4 VMSTCIE3 VMSTCIE2 VMSTCIE1
530h RFM - - RNVCGC RVGS2 RVGS1 RVGS0 RPA
VCAT.RCR4(1)
531h RFRST - - - - - - -
532h RFM - - RNVCGC RVGS2 RVGS1 RVGS0 RPA
VCAT.RCR4(2)
533h RFRST - - - - - - -
534h RFM - - RNVCGC RVGS2 RVGS1 RVGS0 RPA
VCAT.RCR4(3)
535h RFRST - - - - - - -
536h RFM - - RNVCGC RVGS2 RVGS1 RVGS0 RPA
VCAT.RCR4(4)
537h RFRST - - - - - - -
538h VCAT.RCR4(5) RFM - - RNVCGC RVGS2 RVGS1 RVGS0 RPA
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
539h RFRST - - - - - - -
53Ah RFM - - RNVCGC RVGS2 RVGS1 RVGS0 RPA
VCAT.RCR4(6)
53Bh RFRST - - - - - - -
53Ch RFM - - RNVCGC RVGS2 RVGS1 RVGS0 RPA
VCAT.RCR4(7)
53Dh RFRST - - - - - - -
53Eh RFM - - RNVCGC RVGS2 RVGS1 RVGS0 RPA
VCAT.RCR4(8)
53Fh RFRST - - - - - - -
540h RFM - - RNVCGC RVGS2 RVGS1 RVGS0 RPA
VCAT.RCR4(9)
541h RFRST - - - - - - -
542h RFM - - RNVCGC RVGS2 RVGS1 RVGS0 RPA
VCAT.RCR4(10)
543h RFRST - - - - - - -
544h RFM - - RNVCGC RVGS2 RVGS1 RVGS0 RPA
VCAT.RCR4(11)
545h RFRST - - - - - - -
546h RFM - - RNVCGC RVGS2 RVGS1 RVGS0 RPA
VCAT.RCR4(12)
547h RFRST - - - - - - -
548h RFM - - RNVCGC RVGS2 RVGS1 RVGS0 RPA
VCAT.RCR4(13)
549h RFRST - - - - - - -
54Ah RFM - - RNVCGC RVGS2 RVGS1 RVGS0 RPA
VCAT.RCR4(14)
54Bh RFRST - - - - - - -
54Ch RFM - - RNVCGC RVGS2 RVGS1 RVGS0 RPA
VCAT.RCR4(15)
54Dh RFRST - - - - - - -
54Eh RFM - - RNVCGC RVGS2 RVGS1 RVGS0 RPA
VCAT.RCR4(16)
54Fh RFRST - - - - - - -
550h - - - RSACK - - - LOM
VCAT.RSR1(1)
551h RVSQ3 RVSQ2 RVSQ1 RVSQ0 CTRL3 CTRL2 CTRL1 CTRL0
552h - - - RSACK - - - LOM
VCAT.RSR1(2)
553h RVSQ3 RVSQ2 RVSQ1 RVSQ0 CTRL3 CTRL2 CTRL1 CTRL0
554h - - - RSACK - - - LOM
VCAT.RSR1(3)
555h RVSQ3 RVSQ2 RVSQ1 RVSQ0 CTRL3 CTRL2 CTRL1 CTRL0
556h - - - RSACK - - - LOM
VCAT.RSR1(4)
557h RVSQ3 RVSQ2 RVSQ1 RVSQ0 CTRL3 CTRL2 CTRL1 CTRL0
558h - - - RSACK - - - LOM
VCAT.RSR1(5)
559h RVSQ3 RVSQ2 RVSQ1 RVSQ0 CTRL3 CTRL2 CTRL1 CTRL0
55Ah - - - RSACK - - - LOM
VCAT.RSR1(6)
55Bh RVSQ3 RVSQ2 RVSQ1 RVSQ0 CTRL3 CTRL2 CTRL1 CTRL0
55Ch - - - RSACK - - - LOM
VCAT.RSR1(7)
55Dh RVSQ3 RVSQ2 RVSQ1 RVSQ0 CTRL3 CTRL2 CTRL1 CTRL0
55Eh - - - RSACK - - - LOM
VCAT.RSR1(8)
55Fh RVSQ3 RVSQ2 RVSQ1 RVSQ0 CTRL3 CTRL2 CTRL1 CTRL0
560h - - - RSACK - - - LOM
VCAT.RSR1(9)
561h RVSQ3 RVSQ2 RVSQ1 RVSQ0 CTRL3 CTRL2 CTRL1 CTRL0
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
562h - - - RSACK - - - LOM
VCAT.RSR1(10)
563h RVSQ3 RVSQ2 RVSQ1 RVSQ0 CTRL3 CTRL2 CTRL1 CTRL0
564h - - - RSACK - - - LOM
VCAT.RSR1(11)
565h RVSQ3 RVSQ2 RVSQ1 RVSQ0 CTRL3 CTRL2 CTRL1 CTRL0
566h - - - RSACK - - - LOM
VCAT.RSR1(12)
567h RVSQ3 RVSQ2 RVSQ1 RVSQ0 CTRL3 CTRL2 CTRL1 CTRL0
568h - - - RSACK - - - LOM
VCAT.RSR1(13)
569h RVSQ3 RVSQ2 RVSQ1 RVSQ0 CTRL3 CTRL2 CTRL1 CTRL0
56Ah - - - RSACK - - - LOM
VCAT.RSR1(14)
56Bh RVSQ3 RVSQ2 RVSQ1 RVSQ0 CTRL3 CTRL2 CTRL1 CTRL0
56Ch - - - RSACK - - - LOM
VCAT.RSR1(15)
56Dh RVSQ3 RVSQ2 RVSQ1 RVSQ0 CTRL3 CTRL2 CTRL1 CTRL0
56Eh - - - RSACK - - - LOM
VCAT.RSR1(16)
56Fh RVSQ3 RVSQ2 RVSQ1 RVSQ0 CTRL3 CTRL2 CTRL1 CTRL0
570h - - - - CRCE GID SEMF EMF
VCAT.RSR2(1)
571h - - - - - - - -
572h - - - - CRCE GID SEMF EMF
VCAT.RSR2(2)
573h - - - - - - - -
574h - - - - CRCE GID SEMF EMF
VCAT.RSR2(3)
575h - - - - - - - -
576h - - - - CRCE GID SEMF EMF
VCAT.RSR2(4)
577h - - - - - - - -
578h - - - - CRCE GID SEMF EMF
VCAT.RSR2(5)
579h - - - - - - - -
57Ah - - - - CRCE GID SEMF EMF
VCAT.RSR2(6)
57Bh - - - - - - - -
57Ch - - - - CRCE GID SEMF EMF
VCAT.RSR2(7)
57Dh - - - - - - - -
57Eh - - - - CRCE GID SEMF EMF
VCAT.RSR2(8)
57Fh - - - - - - - -
580h - - - - CRCE GID SEMF EMF
VCAT.RSR2(9)
581h - - - - - - - -
582h - - - - CRCE GID SEMF EMF
VCAT.RSR2(10)
583h - - - - - - - -
584h - - - - CRCE GID SEMF EMF
VCAT.RSR2(11)
585h - - - - - - - -
586h - - - - CRCE GID SEMF EMF
VCAT.RSR2(12)
587h - - - - - - - -
588h - - - - CRCE GID SEMF EMF
VCAT.RSR2(13)
589h - - - - - - - -
58Ah VCAT.RSR2(14) - - - - CRCE GID SEMF EMF
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
58Bh - - - - - - - -
58Ch - - - - CRCE GID SEMF EMF
VCAT.RSR2(15)
58Dh - - - - - - - -
58Eh - - - - CRCE GID SEMF EMF
VCAT.RSR2(16)
58Fh - - - - - - - -
590h - - - RSACKL SQL CTRL - LOML
VCAT.RSLSR(1)
591h - - - - - - - -
592h - - - RSACKL SQL CTRL - LOML
VCAT.RSLSR(2)
593h - - - - - - - -
594h - - - RSACKL SQL CTRL - LOML
VCAT.RSLSR(3)
595h - - - - - - - -
596h - - - RSACKL SQL CTRL - LOML
VCAT.RSLSR(4)
597h - - - - - - - -
598h - - - RSACKL SQL CTRL - LOML
VCAT.RSLSR(5)
599h - - - - - - - -
59Ah - - - RSACKL SQL CTRL - LOML
VCAT.RSLSR(6)
59Bh - - - - - - - -
59Ch - - - RSACKL SQL CTRL - LOML
VCAT.RSLSR(7)
59Dh - - - - - - - -
59Eh - - - RSACKL SQL CTRL - LOML
VCAT.RSLSR(8)
59Fh - - - - - - - -
5A0h - - - RSACKL SQL CTRL - LOML
VCAT.RSLSR(9)
5A1h - - - - - - - -
5A2h - - - RSACKL SQL CTRL - LOML
VCAT.RSLSR(10)
5A3h - - - - - - - -
5A4h - - - RSACKL SQL CTRL - LOML
VCAT.RSLSR(11)
5A5h - - - - - - - -
5A6h - - - RSACKL SQL CTRL - LOML
VCAT.RSLSR(12)
5A7h - - - - - - - -
5A8h - - - RSACKL SQL CTRL - LOML
VCAT.RSLSR(13)
5A9h - - - - - - - -
5AAh - - - RSACKL SQL CTRL - LOML
VCAT.RSLSR(14)
5ABh - - - - - - - -
5ACh - - - RSACKL SQL CTRL - LOML
VCAT.RSLSR(15)
5ADh - - - - - - - -
5AEh - - - RSACKL SQL CTRL - LOML
VCAT.RSLSR(16)
5AFh - - - - - - - -
5B0h - - - RSACKIE SQIE CTRIE - LOMIE
VCAT.RSIE(1)
5B1h - - - - - - - -
5B2h - - - RSACKIE SQIE CTRIE - LOMIE
VCAT.RSIE(2)
5B3h - - - - - - - -
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
5B4h - - - RSACKIE SQIE CTRIE - LOMIE
VCAT.RSIE(3)
5B5h - - - - - - - -
5B6h - - - RSACKIE SQIE CTRIE - LOMIE
VCAT.RSIE(4)
5B7h - - - - - - - -
5B8h - - - RSACKIE SQIE CTRIE - LOMIE
VCAT.RSIE(5)
5B9h - - - - - - - -
5BAh - - - RSACKIE SQIE CTRIE - LOMIE
VCAT.RSIE(6)
5BBh - - - - - - - -
5BCh - - - RSACKIE SQIE CTRIE - LOMIE
VCAT.RSIE(7)
5BDh - - - - - - - -
5BEh - - - RSACKIE SQIE CTRIE - LOMIE
VCAT.RSIE(8)
5BFh - - - - - - - -
5C0h - - - RSACKIE SQIE CTRIE - LOMIE
VCAT.RSIE(9)
5C1h - - - - - - - -
5C2h - - - RSACKIE SQIE CTRIE - LOMIE
VCAT.RSIE(10)
5C3h - - - - - - - -
5C4h - - - RSACKIE SQIE CTRIE - LOMIE
VCAT.RSIE(11)
5C5h - - - - - - - -
5C6h - - - RSACKIE SQIE CTRIE - LOMIE
VCAT.RSIE(12)
5C7h - - - - - - - -
5C8h - - - RSACKIE SQIE CTRIE - LOMIE
VCAT.RSIE(13)
5C9h - - - - - - - -
5CAh - - - RSACKIE SQIE CTRIE - LOMIE
VCAT.RSIE(14)
5CBh - - - - - - - -
5CCh - - - RSACKIE SQIE CTRIE - LOMIE
VCAT.RSIE(15)
5CDh - - - - - - - -
5CEh - - - RSACKIE SQIE CTRIE - LOMIE
VCAT.RSIE(16)
5CFh - - - - - - - -
5D0h RGID7 RGID6 RGID5 RGID4 RGID3 RGID2 RGID1 RGID0
VCAT.RSR3(1)
5D1h RGID15 RGID14 RGID13 RGID12 RGID11 RGID10 RGID9 RGID8
5D2h RGID7 RGID6 RGID5 RGID4 RGID3 RGID2 RGID1 RGID0
VCAT.RSR3(2)
5D3h RGID15 RGID14 RGID13 RGID12 RGID11 RGID10 RGID9 RGID8
5D4h RGID7 RGID6 RGID5 RGID4 RGID3 RGID2 RGID1 RGID0
VCAT.RSR3(3)
5D5h RGID15 RGID14 RGID13 RGID12 RGID11 RGID10 RGID9 RGID8
5D6h RGID7 RGID6 RGID5 RGID4 RGID3 RGID2 RGID1 RGID0
VCAT.RSR3(4)
5D7h RGID15 RGID14 RGID13 RGID12 RGID11 RGID10 RGID9 RGID8
5D8h RGID7 RGID6 RGID5 RGID4 RGID3 RGID2 RGID1 RGID0
VCAT.RSR3(5)
5D9h RGID15 RGID14 RGID13 RGID12 RGID11 RGID10 RGID9 RGID8
5DAh RGID7 RGID6 RGID5 RGID4 RGID3 RGID2 RGID1 RGID0
VCAT.RSR3(6)
5DBh RGID15 RGID14 RGID13 RGID12 RGID11 RGID10 RGID9 RGID8
5DCh VCAT.RSR3(7) RGID7 RGID6 RGID5 RGID4 RGID3 RGID2 RGID1 RGID0
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
5DDh RGID15 RGID14 RGID13 RGID12 RGID11 RGID10 RGID9 RGID8
5DEh RGID7 RGID6 RGID5 RGID4 RGID3 RGID2 RGID1 RGID0
VCAT.RSR3(8)
5DFh RGID15 RGID14 RGID13 RGID12 RGID11 RGID10 RGID9 RGID8
5E0h RGID7 RGID6 RGID5 RGID4 RGID3 RGID2 RGID1 RGID0
VCAT.RSR3(9)
5E1h RGID15 RGID14 RGID13 RGID12 RGID11 RGID10 RGID9 RGID8
5E2h RGID7 RGID6 RGID5 RGID4 RGID3 RGID2 RGID1 RGID0
VCAT.RSR3(10)
5E3h RGID15 RGID14 RGID13 RGID12 RGID11 RGID10 RGID9 RGID8
5E4h RGID7 RGID6 RGID5 RGID4 RGID3 RGID2 RGID1 RGID0
VCAT.RSR3(11)
5E5h RGID15 RGID14 RGID13 RGID12 RGID11 RGID10 RGID9 RGID8
5E6h RGID7 RGID6 RGID5 RGID4 RGID3 RGID2 RGID1 RGID0
VCAT.RSR3(12)
5E7h RGID15 RGID14 RGID13 RGID12 RGID11 RGID10 RGID9 RGID8
5E8h RGID7 RGID6 RGID5 RGID4 RGID3 RGID2 RGID1 RGID0
VCAT.RSR3(13)
5E9h RGID15 RGID14 RGID13 RGID12 RGID11 RGID10 RGID9 RGID8
5EAh RGID7 RGID6 RGID5 RGID4 RGID3 RGID2 RGID1 RGID0
VCAT.RSR3(14)
5EBh RGID15 RGID14 RGID13 RGID12 RGID11 RGID10 RGID9 RGID8
5ECh RGID7 RGID6 RGID5 RGID4 RGID3 RGID2 RGID1 RGID0
VCAT.RSR3(15)
5EDh RGID15 RGID14 RGID13 RGID12 RGID11 RGID10 RGID9 RGID8
5EEh RGID7 RGID6 RGID5 RGID4 RGID3 RGID2 RGID1 RGID0
VCAT.RSR3(16)
5EFh RGID15 RGID14 RGID13 RGID12 RGID11 RGID10 RGID9 RGID8
SERIAL INTERFACE GLOBAL
600h LLB8 LLB7 LLB6 LLB5 LLB4 LLB3 LLB2 LLB1
LI.LCR1
601h LLB16 LLB15 LLB14 LLB13 LLB12 LLB11 LLB10 LLB9
602h TLB8 TLB7 TLB6 TLB5 TLB4 TLB3 TLB2 TLB1
LI.LCR2
603h TLB16 TLB15 TLB14 TLB13 TLB12 TLB11 TLB10 TLB9
604h TCLKA8 TCLKA7 TCLKA6 TCLKA5 TCLKA4 TCLKA3 TCLKA2 TCLKA1
LI.TCSR
605h - - - TMCLKA4 - - - TMCLKA3
606h - - - - - - - TVCLKA1
LI.TVCSR
607h - - - - - - - -
608h RCLKA8 RCLKA7 RCLKA6 RCLKA5 RCLKA4 RCLKA3 RCLKA2 RCLKA1
LI.RCSR
609h RCLKA16 RCLKA15 RCLKA14 RCLKA13 RCLKA12 RCLKA11 RCLKA10 RCLKA9
60Ah - - - - - - - RVCLKA1
LI.RVCSR
60Bh - - - - - - - -
TRANSMIT SERIAL PER-PORT
640h - - - TCLKINV - TS_SETUP1 TS_SETUP0 TD_SEL
LI.TCR(1)
641h - - - - - - - -
648h - - - TCLKINV - TS_SETUP1 TS_SETUP0 TD_SEL
LI.TCR(2)
649h - - - - - - - -
650h - - - TCLKINV - TS_SETUP1 TS_SETUP0 TD_SEL
LI.TCR(3)
651h - - - - - - - -
658h - - - TCLKINV - TS_SETUP1 TS_SETUP0 TD_SEL
LI.TCR(4)
659h - - - - - - - -
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
660h - - - TCLKINV - TS_SETUP1 TS_SETUP0 TD_SEL
LI.TCR(5)
661h - - - - - - - -
668h - - - TCLKINV - TS_SETUP1 TS_SETUP0 TD_SEL
LI.TCR(6)
669h - - - - - - - -
670h - - - TCLKINV - TS_SETUP1 TS_SETUP0 TD_SEL
LI.TCR(7)
671h - - - - - - - -
678h - - - TCLKINV - TS_SETUP1 TS_SETUP0 TD_SEL
LI.TCR(8)
679h - - - - - - - -
680h - - - TCLKINV - TS_SETUP1 TS_SETUP0 -
LI.TCR(9)
681h - - - - - - - -
688h - - - TCLKINV - TS_SETUP1 TS_SETUP0 -
LI.TCR(10)
689h - - - - - - - -
690h - - - TCLKINV - TS_SETUP1 TS_SETUP0 -
LI.TCR(11)
691h - - - - - - - -
698h - - - TCLKINV - TS_SETUP1 TS_SETUP0 -
LI.TCR(12)
699h - - - - - - - -
6A0h - - - TCLKINV - TS_SETUP1 TS_SETUP0 -
LI.TCR(13)
6A1h - - - - - - - -
6A8h - - - TCLKINV - TS_SETUP1 TS_SETUP0 -
LI.TCR(14)
6A9h - - - - - - - -
6B0h - - - TCLKINV - TS_SETUP1 TS_SETUP0 -
LI.TCR(15)
6B1h - - - - - - - -
6B8h - - - TCLKINV - TS_SETUP1 TS_SETUP0 -
LI.TCR(16)
6B9h - - - - - - - -
6C0h TVOPF4 TVOPF3 TVOPF2 TVOPF1 TVOPF0 TSYNCC PC TPE
LI.TVPCR
6C1h - - - - - - TVFRST TVCLKI
6C2h - - - - - - TVFU TVFO
LI.TVFSR
6C3h - - - - - - - -
6C4h - - - - - - TVFUL TVFOL
LI.TVFLSR
6C5h - - - - - - - -
6C6h - - - - - - TVFULIE TVFOLIE
LI.TVFSRIE
6C7h - - - - - - - -
ADDR Name BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
RECEIVE SERIAL PER-PORT
740h - - - RCLKINV - - RFRST -
LI.RCR1(1)
741h - - - - - - - -
748h - - - RCLKINV - - RFRST -
LI.RCR1(2)
749h - - - - - - - -
750h - - - RCLKINV - - RFRST -
LI.RCR1(3)
751h - - - - - - - -
758h - - - RCLKINV - - RFRST -
LI.RCR1(4)
759h - - - - - - - -
760h - - - RCLKINV - - RFRST -
LI.RCR1(5)
761h - - - - - - - -
768h - - - RCLKINV - - RFRST -
LI.RCR1(6)
769h - - - - - - - -
770h - - - RCLKINV - - RFRST -
LI.RCR1(7)
771h - - - - - - - -
778h - - - RCLKINV - - RFRST -
LI.RCR1(8)
779h - - - - - - - -
780h - - - RCLKINV - - RFRST -
LI.RCR1(9)
781h - - - - - - - -
788h - - - RCLKINV - - RFRST -
LI.RCR1(10)
789h - - - - - - - -
790h - - - RCLKINV - - RFRST -
LI.RCR1(11)
791h - - - - - - - -
798h - - - RCLKINV - - RFRST -
LI.RCR1(12)
799h - - - - - - - -
7A0h - - - RCLKINV - - RFRST -
LI.RCR1(13)
7A1h - - - - - - - -
7A8h - - - RCLKINV - - RFRST -
LI.RCR1(14)
7A9h - - - - - - - -
7B0h - - - RCLKINV - - RFRST -
LI.RCR1(15)
7B1h - - - - - - - -
7B8h - - - RCLKINV - - RFRST -
LI.RCR1(16)
7B9h - - - - - - - -
7C0h RVOPF4 RVOPF3 RVOPF2 RVOPF1 RVOPF0 RSYNCC PC RPE
LI.RVPCR
7C1h - - - - - - RVFRST RVCLKI
ADDR NAME BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
SU.MACCR
0000h 31:24 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved
23:16 WDD JD FBE JFE Reserved Reserved Reserved Reserved
15:8 GMIIMIIS EM DRO LM DM Reserved DRTY APST
7:0 ACST BOLMT1 BOLMT0 DC TE RE Reserved Reserved
SU.MACFFR
0004h 31:24 RAF Reserved Reserved Reserved Reserved Reserved Reserved Reserved
23:16 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved
15:8 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved
7:0 PCF Reserved DBF PAM INVF HFUF HFMF PM
SU.MACHTHR
0008h 31:24 HTH[31] HTH[30] HTH[29] HTH[28] HTH[27] HTH[26] HTH[25] HTH[24]
23:16 HTH[23] HTH[22] HTH[21] HTH[20] HTH[19] HTH[18] HTH[17] HTH[16]
15:8 HTH[15] HTH[14] HTH[13] HTH[12] HTH[11] HTH[10] HTH[9] HTH[8]
7:0 HTH[7] HTH[6] HTH[5] HTH[4] HTH[3] HTH[2] HTH[1] HTH[0]
SU.MACHTLR
000Ch 31:24 HTL[31] HTL[30] HTL[29] HTL[28] HTL[27] HTL[26] HTL[25] HTL[24]
23:16 HTL[23] HTL[22] HTL[21] HTL[20] HTL[19] HTL[18] HTL[17] HTL[16]
15:8 HTL[15] HTL[14] HTL[13] HTL[12] HTL[11] HTL[10] HTL[9] HTL[8]
7:0 HTL[7] HTL[6] HTL[5] HTL[4] HTL[3] HTL[2] HTL[1] HTL[0]
SU.GMIIA
0010h 31:24 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved
23:16 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved
15:8 PPA[4] PPA[3] PPA[2] PPA[1] PPA[0] GM[4] GM[3] GM[2]
7:0 GM[1] GM[0] Reserved Reserved CR[1] CR[0] GW GB
SU.GMIID
0014h 31:24 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved
23:16 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved
15:8 GD[15] GD[14] GD[13] GD[12] GD[11] GD[10] GD[9] GD[8]
7:0 GD[7] GD[6] GD[5] GD[4] GD[3] GD[2] GD[1] GD[0]
SU.MACFCR
0018h 31:24 PT[15] PT[14] PT[13] PT[12] PT[11] PT[10] PT[9] PT[8]
23:16 PT[7] PT[6] PT[5] PT[4] PT[3] PT[2] PT[1] PT[0]
15:8 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved
7:0 Reserved Reserved Reserved PLT UP RFE TFE FCB
SU.VLANTR
001Ch 31:24
- - - - - - - -
23:16 - - - - - - - -
15:8 VLTID[15] VLTID[14] VLTID[13] VLTID[12] VLTID[11] VLTID[10] VLTID[9] VLTID[8]
7:0 VLTID[7] VLTID[6] VLTID[5] VLTID[4] VLTID[3] VLTID[2] VLTID[1] VLTID[0]
SU.ADDR0H
0040h 31:24
MADDR0AE - - - - - - -
23:16 - - - - - - - -
15:8 MADDR0[47] MADDR0[46] MADDR0[45] MADDR0[44] MADDR0[43] MADDR0[42] MADDR0[41] MADDR0[40]
7:0 MADDR0[39] MADDR0[38] MADDR0[37] MADDR0[36] MADDR0[35] MADDR0[34] MADDR0[33] MADDR0[32]
SU.ADDR0L
0044h 31:24
MADDR0[31] MADDR0[30] MADDR0[29] MADDR0[28] MADDR0[27] MADDR0[26] MADDR0[25] MADDR0[24]
ADDR NAME BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
SU.ADDR1H
0048h 31:24
MADDR1AE - - - - - - -
23:16 - - - - - - - -
15:8 MADDR1[47] MADDR1[46] MADDR1[45] MADDR1[44] MADDR1[43] MADDR1[42] MADDR1[41] MADDR1[40]
7:0 MADDR1[39] MADDR1[38] MADDR1[37] MADDR1[36] MADDR1[35] MADDR1[34] MADDR1[33] MADDR1[32]
SU.ADDR1L
004Ch 31:24
MADDR1[31] MADDR1[30] MADDR1[29] MADDR1[28] MADDR1[27] MADDR1[26] MADDR1[25] MADDR1[24]
ADDR NAME BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
23:16 - - - - - - - -
15:8 MADDR6[47] MADDR6[46] MADDR6[45] MADDR6[44] MADDR6[43] MADDR6[42] MADDR6[41] MADDR6[40]
7:0 MADDR6[39] MADDR6[38] MADDR6[37] MADDR6[36] MADDR6[35] MADDR6[34] MADDR6[33] MADDR6[32]
SU.ADDR6L
0074h 31:24
MADDR6[31] MADDR6[30] MADDR6[29] MADDR6[28] MADDR6[27] MADDR6[26] MADDR6[25] MADDR6[24]
ADDR NAME BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
15:8 MADDR11[47] MADDR11[46] MADDR11[45] MADDR11[44] MADDR11[43] MADDR11[42] MADDR11[41] MADDR11[40]
7:0 MADDR11[39] MADDR11[38] MADDR11[37] MADDR11[36] MADDR11[35] MADDR11[34] MADDR11[33] MADDR11[32]
SU.ADDR11L
009Ch 31:24
MADDR11[31] MADDR11[30] MADDR11[29] MADDR11[28] MADDR11[27] MADDR11[26] MADDR11[25] MADDR11[24]
ADDR NAME BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
7:0 - - - - - - - -
SU.ANSR
00C4h 31:24
- - - - - - - -
23:16 - - - - - - - -
15:8 - - - - - - - ES
7:0 - - ANC - ANA LS - -
SU.LSR
00D8h 31:24
- - - - - - - -
23:16 - - - - - - - -
15:8 - - - - - - - -
7:0 - - - - LINKUP LNKSPD[1] LNKSPD[0] LINKM
SU.MMCCTRL
0100h 31:24
- - - - - - - -
23:16 - - - - - - - -
15:8 - - - - - - - -
7:0 - - - - - ROR CSR CRST
SU.MMCRSR
0104h 31:24
- - - - - - - -
23:16 RXWDOG RXVLAN RXOVFL RXPAUSE RXRANGE RXLNERR RXUCAST RX1K_MAX
15:8 RX512_1K RX256_511 RX128_255 RX65_127 RX0_64 RXOVRSZ RXUNRSZ RXJBBR
7:0 RXRUNT RXALGN RXCRC RXMFC RXGBFC RXBCG RXBCGB RXFC
SU.MMCTSR
0108h 31:24
- - - - - - - TXVLAN
23:16 TXPAUSE TXXCSVDF TXFCNT TXBCNT TXCERR TXXCSVCL TXLTCL TXDFRD
15:8 TXMLTICL TXSNGLCL TXUFE TXBFC TXMFC TXUCAST TX1K_MAX TX512_1K
7:0 TX256_511 TX128_255 TX65_127 TX0_64 TXGMFC TXGBFC TXFC TXBC
SU.MMCRIM
010Ch 31:24
- - - - - - - -
23:16 RXWDOG RXVLAN RXOVFL RXPAUSE RXRANGE RXLNERR RXUCAST RX1K_MAX
15:8 RX512_1K RX256_511 RX128_255 RX65_127 RX0_64 RXOVRSZ RXUNRSZ RXJBBR
7:0 RXRUNT RXALGN RXCRC RXMFC RXGBFC RXBCG RXBCGB RXFC
SU.MMCTIM
0110h 31:24
- - - - - - - TXVLAN
23:16 TXPAUSE TXXCSVDF TXFCNT TXBCNT TXCERR TXXCSVCL TXLTCL TXDFRD
15:8 TXMLTICL TXSNGLCL TXUFE TXBFC TXMFC TXUCAST TX1K_MAX TX512_1K
7:0 TX256_511 TX128_255 TX65_127 TX0_64 TXGMFC TXGBFC TXFC TXBC
SU.TXBC
0114h 31:24
TXBC[31] TXBC[30] TXBC[29] TXBC[28] TXBC[27] TXBC[26] TXBC[25] TXBC[24]
23:16 TXBC[23] TXBC[22] TXBC[21] TXBC[20] TXBC[19] TXBC[18] TXBC[17] TXBC[16]
15:8 TXBC[15] TXBC[14] TXBC[13] TXBC[12] TXBC[11] TXBC[10] TXBC[9] TXBC[8]
7:0 TXBC[7] TXBC[6] TXBC[5] TXBC[4] TXBC[3] TXBC[2] TXBC[1] TXBC[0]
SU.TXFC
0118h 31:24
TXFC[31] TXFC[30] TXFC[29] TXFC[28] TXFC[27] TXFC[26] TXFC[25] TXFC[24]
23:16 TXFC[23] TXFC[22] TXFC[21] TXFC[20] TXFC[19] TXFC[18] TXFC[17] TXFC[16]
15:8 TXFC[15] TXFC[14] TXFC[13] TXFC[12] TXFC[11] TXFC[10] TXFC[9] TXFC[8]
7:0 TXFC[7] TXFC[6] TXFC[5] TXFC[4] TXFC[3] TXFC[2] TXFC[1] TXFC[0]
SU.TXGBFC
011Ch 31:24
TXGBFC[31] TXGBFC[30] TXGBFC[29] TXGBFC[28] TXGBFC[27] TXGBFC[26] TXGBFC[25] TXGBFC[24]
23:16 TXGBFC[23] TXGBFC[22] TXGBFC[21] TXGBFC[20] TXGBFC[19] TXGBFC[18] TXGBFC[17] TXGBFC[16]
ADDR NAME BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
15:8 TXGBFC[15] TXGBFC[14] TXGBFC[13] TXGBFC[12] TXGBFC[11] TXGBFC[10] TXGBFC[9] TXGBFC[8]
7:0 TXGBFC[7] TXGBFC[6] TXGBFC[5] TXGBFC[4] TXGBFC[3] TXGBFC[2] TXGBFC[1] TXGBFC[0]
SU.TXGMFC
0120h 31:24
TXGMFC[31] TXGMFC[30] TXGMFC[29] TXGMFC[28] TXGMFC[27] TXGMFC[26] TXGMFC[25] TXGMFC[24]
SU.TX256_511
0130h 31:24
TX256_511[31] TX256_511[30] TX256_511[29] TX256_511[28] TX256_511[27] TX256_511[26] TX256_511[25] TX256_511[24]
SU.TX512_1K
0134h 31:24
TX512_1K[31] TX512_1K[30] TX512_1K[29] TX512_1K[28] TX512_1K[27] TX512_1K[26] TX512_1K[25] TX512_1K[24]
SU.TX1K_MAX
0138h 31:24
TX1K_MAX[31] TX1K_MAX[30] TX1K_MAX[29] TX1K_MAX[28] TX1K_MAX[27] TX1K_MAX[26] TX1K_MAX[25] TX1K_MAX[24]
SU.TXUCAST
013Ch 31:24
TXUCAST[31] TXUCAST[30] TXUCAST[29] TXUCAST[28] TXUCAST[27] TXUCAST[26] TXUCAST[25] TXUCAST[24]
ADDR NAME BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
SU.TXUFE
0148h 31:24
TXUFE[31] TXUFE[30] TXUFE[29] TXUFE[28] TXUFE[27] TXUFE[26] TXUFE[25] TXUFE[24]
SU.TXMLTICL
0150h 31:24
TXMLTICL[31] TXMLTICL[30] TXMLTICL[29] TXMLTICL[28] TXMLTICL[27] TXMLTICL[26] TXMLTICL[25] TXMLTICL[24]
SU.TXDFRD
0154h 31:24
TXDFRD[31] TXDFRD[30] TXDFRD[29] TXDFRD[28] TXDFRD[27] TXDFRD[26] TXDFRD[25] TXDFRD[24]
SU.TXCRERR
0160h 31:24
TXCRERR[31] TXCRERR[30] TXCRERR[29] TXCRERR[28] TXCRERR[27] TXCRERR[26] TXCRERR[25] TXCRERR[24]
SU.TXPAUSE
0170h 31:24
TXPAUSE[31] TXPAUSE[30] TXPAUSE[29] TXPAUSE[28] TXPAUSE[27] TXPAUSE[26] TXPAUSE[25] TXPAUSE[24]
ADDR NAME BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
15:8 TXPAUSE[15] TXPAUSE[14] TXPAUSE[13] TXPAUSE[12] TXPAUSE[11] TXPAUSE[10] TXPAUSE[9] TXPAUSE[8]
7:0 TXPAUSE[7] TXPAUSE[6] TXPAUSE[5] TXPAUSE[4] TXPAUSE[3] TXPAUSE[2] TXPAUSE[1] TXPAUSE[0]
SU.TXVLANF
0174h 31:24
TXVLANF[31] TXVLANF[30] TXVLANF[29] TXVLANF[28] TXVLANF[27] TXVLANF[26] TXVLANF[25] TXVLANF[24]
ADDR NAME BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
23:16 RXALGN[23] RXALGN[22] RXALGN[21] RXALGN[20] RXALGN[19] RXALGN[18] RXALGN[17] RXALGN[16]
15:8 RXALGN[15] RXALGN[14] RXALGN[13] RXALGN[12] RXALGN[11] RXALGN[10] RXALGN[9] RXALGN[8]
7:0 RXALGN[7] RXALGN[6] RXALGN[5] RXALGN[4] RXALGN[3] RXALGN[2] RXALGN[1] RXALGN[0]
SU.RXRUNT RXRUNT[31 RXRUNT[30 RXRUNT[29 RXRUNT[28 RXRUNT[27 RXRUNT[26 RXRUNT[25 RXRUNT[24
019Ch 31:24 ] ] ] ] ] ] ] ]
23:16 RXRUNT[23 RXRUNT[22 RXRUNT[21 RXRUNT[20 RXRUNT[19 RXRUNT[18 RXRUNT[17 RXRUNT[16
] ] ] ] ] ] ] ]
15:8 RXRUNT[15 RXRUNT[14 RXRUNT[13 RXRUNT[12 RXRUNT[11 RXRUNT[10
RXRUNT[9] RXRUNT[8]
] ] ] ] ] ]
7:0 RXRUNT[7] RXRUNT[6] RXRUNT[5] RXRUNT[4] RXRUNT[3] RXRUNT[2] RXRUNT[1] RXRUNT[0]
SU.RXJBBR
01A0h 31:24
RXJBBR[31] RXJBBR[30] RXJBBR[29] RXJBBR[28] RXJBBR[27] RXJBBR[26] RXJBBR[25] RXJBBR[24]
23:16 RXJBBR[23] RXJBBR[22] RXJBBR[21] RXJBBR[20] RXJBBR[19] RXJBBR[18] RXJBBR[17] RXJBBR[16]
15:8 RXJBBR[15] RXJBBR[14] RXJBBR[13] RXJBBR[12] RXJBBR[11] RXJBBR[10] RXJBBR[9] RXJBBR[8]
7:0 RXJBBR[7] RXJBBR[6] RXJBBR[5] RXJBBR[4] RXJBBR[3] RXJBBR[2] RXJBBR[1] RXJBBR[0]
SU.RXUNDRSZ
01A4h 31:24
RXUNDRSZ[31] RXUNDRSZ[30] RXUNDRSZ[29] RXUNDRSZ[28] RXUNDRSZ[27] RXUNDRSZ[26] RXUNDRSZ[25] RXUNDRSZ[24]
SU.RXOVRSZ
01A8h 31:24
RXOVRSZ[31] RXOVRSZ[30] RXOVRSZ[29] RXOVRSZ[28] RXOVRSZ[27] RXOVRSZ[26] RXOVRSZ[25] RXOVRSZ[24]
SU.RX256_511
01B8h 31:24
RX256_511[31] RX256_511[30] RX256_511[29] RX256_511[28] RX256_511[27] RX256_511[26] RX256_511[25] RX256_511[24]
SU.RX512_1K
01BCh 31:24
RX512_1K[31] RX512_1K[30] RX512_1K[29] RX512_1K[28] RX512_1K[27] RX512_1K[26] RX512_1K[25] RX512_1K[24]
SU.RX1K_MAX
01C0h 31:24
RX1K_MAX[31] RX1K_MAX[30] RX1K_MAX[29] RX1K_MAX[28] RX1K_MAX[27] RX1K_MAX[26] RX1K_MAX[25] RX1K_MAX[24]
ADDR NAME BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
23:16 RX1K_MAX[23] RX1K_MAX[22] RX1K_MAX[21] RX1K_MAX[20] RX1K_MAX[19] RX1K_MAX[18] RX1K_MAX[17] RX1K_MAX[16]
SU.RXUFC
01C4h 31:24
RXUFC[31] RXUFC[30] RXUFC[29] RXUFC[28] RXUFC[27] RXUFC[26] RXUFC[25] RXUFC[24]
23:16 - - - FTF - - - -
15:8 - - - - - - - -
7:0 - - - - - - - -
Note that the addresses in the table above are the indirect addresses that must be provided to the SU.MAC1AWH and SU.MAC1AWL. All
unused and reserved locations must be initialized to zero for proper operation unless specifically noted otherwise.
Bits 13-15: Revision Number (REV[2:0]) Contains a sequential number that is related to, but not equal to, the
device revision on the top brand. Silicon revision numbering begins at 000.
Bit 12: SPI Slave (SPIS) If this bit is set to 1, the device only supports a SPI Slave microprocessor port.
Bits 9-11: Voice Channels (VC[2:0]) This contains the number of voice channels supported.
Bit 8: VCAT (VCAT) If this bit is set to 1, the device has VCAT functionality.
Bits 3-7: Serial WAN Ports (WP[4:0]) These bits contain the number of WAN ports in the device.
Bit 3: Gigabit Ethernet Support (GBE) If this bit is set, the device support GbE.
Bits 0-1: Ethernet LAN Ports (MP[1:0]) These bits contain the number of MAC ports in the device.
In all forwarding modes, VCAT/LCAS can be used to aggregate multiple physical serial ports for each WAN
Group’s data stream, except on devices that do not support VCAT/LCAS.
Bit 3: Interrupt Mode (INTM) When this bit is set to 1, the inactive state of the INT pin will be high-impedance.
When this bit is equal to 0, the inactive state of the INT pin will be a driven logic high.
Bit 2: Encap/Decap Loopback (ENDEL) When this bit is set to 1, the WAN-side output data from Encapsulator #1
is looped back to the WAN input of Decapsulator #1.
Bit 0: Global Reset (RST) When this bit is set, all of the internal data path, status, and control registers (except the
RST bit), on all ports, will be reset to the default state. This bit must remain set to 1 for a minimum of 100ns to
initiate the reset operation. The bit should be cleared to 0 for normal operation to resume. Note that setting this bit
does not tri-state output pins. When using a revision A1 (GL.IDR.REVn=000) device in SPI mode, the individual
block reset bits or the hardware reset pin should be used instead of this bit.
Bit 15: Microprocessor Interrupt Status (MICIS) This bit is set if the Microport has an active, enabled interrupt
condition. Normally, this condition is caused by the presence of a trapped frame for extraction and processing.
Bit 14: Decapsulation Interrupt Status 4 (DECIS4) This bit is set if Decapsulator 4 has an active, enabled
interrupt condition.
Bit 13: Decapsulation Interrupt Status 3 (DECIS3) This bit is set if Decapsulator 3 has an active, enabled
interrupt condition.
Bit 12: Decapsulation Interrupt Status 2 (DECIS2) This bit is set if Decapsulator 2 has an active, enabled
interrupt condition.
Bit 11: Encapsulation Interrupt Status 4 (ECIS4) This bit is set if Encapsulator 4 has an active, enabled interrupt
condition.
Bit 10: Encapsulation Interrupt Status 3 (ECIS3) This bit is set if Encapsulator 3 has an active, enabled interrupt
condition.
Bit 9: Encapsulation Interrupt Status 2 (ECIS2) This bit is set if Encapsulator 2 has an active, enabled interrupt
condition.
Bit 8: Receive VCAT Interrupt Status (RVCATIS) This bit is set if the receive VCAT has an active, enabled
interrupt condition.
Bit 6: Buffer Manager (Arbiter) Interrupt Status (BUFIS) This bit is set if the buffer manager has an active,
enabled interrupt condition.
Bit 4: Transmit WAN Serial Port Interrupt Status (TSPIS) This bit is set if the transmit serial WAN port has an
active, enabled interrupt condition.
Bit 3: Decapsulation Interrupt Status 1 (DECIS1) This bit is set if Decapsulator 1 has an active, enabled interrupt
condition.
Bit 2: Encapsulation Interrupt Status 1 (ECIS1) This bit is set if Encapsulator 1 has an active, enabled interrupt
condition.
Bit 1: Transmit LAN Interrupt Status (TXLANIS) This bit is set if a transmit Ethernet LAN port has an active,
enabled interrupt condition.
Bit 0: Receive LAN and Bridge Filter Interrupt Status (RXLANIS) This bit is set if either of the receive Ethernet
LAN MAC(s) or the LAN Queue Overflows have an active, enabled interrupt condition.
Bit 15: Microport Interrupt Enable (MICIE) When this bit is set to 1, MICIS will generate an interrupt.
Bit 14: Decapsulation Interrupt Enable 4 (DECIE4) When this bit is set to 1, DECIS4 will generate an interrupt.
Bit 13: Decapsulation Interrupt Enable 3 (DECIE3) When this bit is set to 1, DECIS3 will generate an interrupt.
Bit 12: Decapsulation Interrupt Enable 2 (DECIE2) When this bit is set to 1, DECIS2 will generate an interrupt.
Bit 11: Encapsulation Interrupt Enable 4 (ECIE4) When this bit is set to 1, ECIS4 will generate an interrupt.
Bit 10: Encapsulation Interrupt Enable 3 (ECIE3) When this bit is set to 1, ECIS3 will generate an interrupt.
Bit 9: Encapsulation Interrupt Enable 2 (ECIE2) When this bit is set to 1, ECIS2 will generate an interrupt.
Bit 8: Receive VCAT Interrupt Enable (RVCATIE) When this bit is set to 1, RVCATIS will generate an interrupt.
Bit 6: Buffer Manager (Arbiter) Interrupt Enable (BUFIE) When this bit is set to 1, BUFIS will generate an
interrupt.
Bit 4: Transmit WAN Serial Port Interrupt Enable (TSPIE) When this bit is set to 1, TSPIS will generate an
interrupt.
Bit 3: Decapsulation Interrupt Enable 1 (DECIE1) When this bit is set to 1, DECIS1 will generate an interrupt.
Bit 2: Encapsulation Interrupt Enable 1 (ECIE1) When this bit is set to 1, ECIS1 will generate an interrupt.
Bit 1: Transmit LAN Interrupt Enable (TXLANIE) When this bit is set to 1, TXLANIS will generate an interrupt.
Bit 0: Receive LAN and Bridge Filter Interrupt Enable (RXLANIE) When this bit is set to 1, RXLANIS will
generate an interrupt.
Bit 11: DPLL Lock (DLOCK) This bit is set to 1 if the DPLL has achieved lock.
Bit 10: PLL Lock (PLOCK) This bit is set to 1 if PLL has achieved lock.
Bits 0-1: FIFO[1:0] FIFO Selection These bits select which FIFO will be accessed for reading or writing.
00 = WAN Insertion FIFO
01 = WAN Extraction FIFO
10 = LAN Insertion FIFO
11 = LAN Extraction FIFO
Bits 0-11: WAN Insertion Frame Length (WILEN[11:0]) These bits determine the number of bytes of the frame to
be written to FIFO selected (Insertion FIFOs only). Maximum size frame is 2048 bytes.
Bits 0-11: LAN Insertion Frame Length (LILEN[11:0])These bits determine the number of bytes of the frame to
be written to FIFO selected (Insertion FIFOs only). Maximum size frame is 2048 bytes.
Bits 0-11: WAN Extraction Frame Length (WELEN[11:0]) These bits report the size of the frame in bytes
available in the WAN Extraction FIFO. Maximum size frame is 2048 bytes. This value is updated when a complete
frame is received in the WAN Extraction FIFO.
Bits 0-11: LAN Extraction Frame Length (LELEN[11:0]) These bits report the size of the frame in bytes available
in the LAN Extraction FIFO. Maximum size frame is 2048 bytes. This value is updated when a complete frame is
received in the LAN Extraction FIFO.
Bit 3: LAN Extraction Available (LANEA) Set when the LAN Extraction FIFO has a frame available to read.
Clears when the first byte is read from the FIFO.
Bit 2: LAN Insertion Queue Empty (LANIE) Set when the LAN Insertion FIFO is empty.
Bit 1: WAN Extraction Available (WANEA) Set when the WAN Extraction FIFO has a frame available to read.
Clears when the first byte is read from the FIFO
Bit 0: WAN Insertion Queue Empty (WANIE) Set when the WAN Insertion FIFO is empty.
Bit 3: LAN Extraction Available - Latched (LANEAL) Set when the LAN Extraction FIFO has a frame available to
read. Clears when the first byte is read from the FIFO.
Bit 2: LAN Insertion Empty - Latched (LANIEL) Set when the LAN Insertion FIFO is empty.
Bit 1: WAN Extraction Available - Latched (WANEAL) Set when the WAN Extraction FIFO has a frame available
to read. Clears when the first byte is read from the FIFO.
Bit 0: WAN Insertion Empty - Latched (WANIEL) Set when the WAN Insertion FIFO is empty.
Bit 3: LAN Extraction Available Interrupt Enable (LANEAIE) This bit enables LANEAL to cause an interrupt.
0 = interrupt disabled
1 = interrupt enabled
Bit 2: LAN Insertion Empty Interrupt Enable (LANIEIE) This bit enables an interrupt if the LANIEL bit is set.
0 = interrupt disabled
1 = interrupt enabled
Bit 1: WAN Extraction Available Interrupt Enable (WANEAIE) This bit enables WANEAL to cause an interrupt.
0 = interrupt disabled
1 = interrupt enabled
Bit 0: WAN Insertion Empty Interrupt Enable (WANIEIE) This bit enables an interrupt if the WANIEL bit is set.
0 = interrupt disabled
1 = interrupt enabled
Bit 9: Read Byte (RD_DN) A zero-to-one transition is required after the last byte of the frame has been read from
the MFAWR Register. This signals the associated FIFO (WAN Extract or LAN Extract) to reset its pointers.
Bit 8: Write Byte (WR_DN) A zero-to-one transition is required after the last byte of the frame has been written to
MFAWR Register. This transition signals that the frame is ready to be transferred.
Bits 0-7: Packet Write Byte (WPKT[7:0]) If an Insertion FIFO is selected, this register inserts a byte of frame data
into the FIFO selected by MCR2. The beginning of the frame to be transmitted is written first. Each write
automatically increments the FIFO pointer. If an Extraction FIFO is selected, this register reports a byte of frame
data from the FIFO selected by MCR2. The beginning of the frame to be transmitted is read first. Each read
automatically increments the FIFO pointer.
Bits 0-7: Packet Read Byte (RPKT[7:0]) If an Extraction FIFO is selected, this register reports a byte of frame
data from the FIFO selected by MCR1. The beginning of the frame to be transmitted is read first. Each read
automatically increments the FIFO pointer.
Bits 0 – 7: MAC Read Address (MACRA0-7) - Low byte of the MAC address. Used only for read operations.
Bits 0 – 7: MAC Read Address (MACRA8-15) - High byte of the MAC address. Used only for read operations.
Bits 0 – 7: MAC Read Data 0 (MACRD0-7): One of four bytes of data read from the MAC. Valid after a read
command has been issued and the SU.MAC1RWC.MCS bit is zero.
Bits 0 - 7: MAC Read Data 1 (MACRD8-15) - One of four bytes of data read from the MAC. Valid after a read
command has been issued and the SU.MAC1RWC.MCS bit is zero.
Bits 0 – 7: MAC Read Data 2 (MACRD16-23) - One of four bytes of data read from the MAC. Valid after a read
command has been issued and the SU.MAC1RWC.MCS bit is zero.
Bits 0 – 7: MAC Read Data 3 (MACRD24-31) - One of four bytes of data read from the MAC. Valid after a read
command has been issued and the SU.MAC1RWC.MCS bit is zero.
Bits 0 – 7: MAC Write Data 0 (MACWD0-7) - One of four bytes of data to be written to the MAC. Data has been
written after a write command has been issued and the SU.MAC1RWC.MCS bit is zero.
Bits 0 – 7: MAC Write Data 1 (MACWD8-15) - One of four bytes of data to be written to the MAC. Data has been
written after a write command has been issued and the SU.MAC1RWC.MCS bit is zero.
Bits 0 - 7: MAC Write Data 2 (MACWD16-23) - One of four bytes of data to be written to the MAC. Data has been
written after a write command has been issued and the SU.MAC1RWC.MCS bit is zero.
Bits 0 – 7: MAC Write Data 3 (MACD24-31) - One of four bytes of data to be written to the MAC. Data has been
written after a write command has been issued and the SU.MAC1RWC.MCS bit is zero.
Bits 0 -7: MAC Write Address (MACAW0-7) - Low byte of the MAC address. Used only for write operations.
Bits 0 – 7: MAC Write Address (MACAW8-15) - High byte of the MAC address. Used only for write operations.
Bit 1: MAC Command RW – If this bit is written to 1, a read is performed from the MAC. If this bit is written to 0, a
write operation is performed. Address information for write operations must be located in SU.MAC1AWH and
SU.MAC1AWL. Address information for read operations must be located in SU.MAC1RADH and SU.MAC1RADL.
The user must also write a 1 to the MCS bit, and the device will clear MCS when the operation is complete.
Bit 0: MAC Command Status – Setting MCS in conjunction with MCRW will initiate a read or write to the MAC
registers. Upon completion of the read or write this bit is cleared. Once a read or write command has been initiated
the host must poll this bit to see when the operation is complete.
Bits 0 – 7: MAC Read Address (MACRA0-7) - Low byte of the MAC address. Used only for read operations.
Bits 0 – 7: MAC Read Address (MACRA8-15) - High byte of the MAC address. Used only for read operations.
Bits 0 – 7: MAC Read Data 0 (MACRD0-7): One of four bytes of data read from the MAC. Valid after a read
command has been issued and the SU.MAC1RWC.MCS bit is zero.
Bits 0 - 7: MAC Read Data 1 (MACRD8-15) - One of four bytes of data read from the MAC. Valid after a read
command has been issued and the SU.MAC1RWC.MCS bit is zero.
Bits 0 – 7: MAC Read Data 2 (MACRD16-23) - One of four bytes of data read from the MAC. Valid after a read
command has been issued and the SU.MAC1RWC.MCS bit is zero.
Bits 0 – 7: MAC Read Data 3 (MACRD24-31) - One of four bytes of data read from the MAC. Valid after a read
command has been issued and the SU.MAC1RWC.MCS bit is zero.
Bits 0 – 7: MAC Write Data 0 (MACWD0-7) - One of four bytes of data to be written to the MAC. Data has been
written after a write command has been issued and the SU.MAC1RWC.MCS bit is zero.
Bits 0 – 7: MAC Write Data 1 (MACWD8-15) - One of four bytes of data to be written to the MAC. Data has been
written after a write command has been issued and the SU.MAC1RWC.MCS bit is zero.
Bits 0 - 7: MAC Write Data 2 (MACWD16-23) - One of four bytes of data to be written to the MAC. Data has been
written after a write command has been issued and the SU.MAC1RWC.MCS bit is zero.
Bits 0 – 7: MAC Write Data 3 (MACD24-31) - One of four bytes of data to be written to the MAC. Data has been
written after a write command has been issued and the SU.MAC1RWC.MCS bit is zero.
Bits 0 -7: MAC Write Address (MACAW0-7) - Low byte of the MAC address. Used only for write operations.
Bits 0 – 7: MAC Write Address (MACAW8-15) - High byte of the MAC address. Used only for write operations.
Bit 1: MAC Command RW – If this bit is written to 1, a read is performed from the MAC. If this bit is written to 0, a
write operation is performed. Address information for write operations must be located in SU.MAC1AWH and
SU.MAC1AWL. Address information for read operations must be located in SU.MAC1RADH and SU.MAC1RADL.
The user must also write a 1 to the MCS bit, and the device will clear MCS when the operation is complete.
Bit 0: MAC Command Status – Setting MCS in conjunction with MCRW will initiate a read or write to the MAC
registers. Upon completion of the read or write this bit is cleared. Once a read or write command has been initiated
the host must poll this bit to see when the operation is complete.
This register is used to control the VLAN Table. The Initialization function resets all of the 4096 entries in the VLAN
Table to their default value.
Bit 2: Control Table Enable (CTE) When equal to zero, the VLAN Table is fully enabled. When set to 1, the VLAN
Table is only enabled as required by the LAN Extract (LAN-VLAN Trap), WAN Extract (WAN-VLAN Trap), or
microprocessor operations.
Bit 1: Control Initialization (CI). A transition from zero to one starts the VLAN Table initialization by resetting all
VLAN table addresses to their default values. A device reset will also trigger a VLAN Table initialization.
Bit 0: Control Auto Increment Mode (CAIM). When set to 1, the VLAN Table Address in SU.VTAA is
automatically incremented with each read or write of the SU.VTWD or SU.VTRD registers.
The data that is stored at the specified VLAN Table address is automatically loaded into the read register for this
configuration register address. This is true whether the user is performing a read or write function. The user may
choose to read the data (for the read operation) or disregard the data (for the write operation).
Bits 0-11: VLAN Table Access Address (VTAA [12:1]). This register provides the VLAN Table Address for a uP
Read or Write operation.
Whenever a write is performed to this configuration register address the data is stored in the VLAN Table at the
address specified by the SU.VTAA register (i.e. the VTAA value must be provided in advance of the VTWD data).
VLAN Forwarding, Extracting (Trapping), or Discarding. Each address (SU.VTAA) in the VLAN table
corresponds to a specific VLAN ID (VID) value from 0 to 4095, and the bit settings at each address relate to
actions taken when a frame containing the corresponding VLAN ID value is detected. These values are used to
translate VLAN tag information from each received frame into forwarding, trapping (frame extraction), or discarding
decisions. The user may configure any or all of the 4096 VLAN IDs values in the VLAN table. The data written to
this register is stored in the VLAN Table at the specified VLAN Table Address.
NOTE:
LAN Extract forwarding takes precedence over LAN Queue forwarding.
LAN Discard takes precedence over LAN Extract forwarding (trapping).
WAN Extract forwarding (trapping) takes precedence over WAN Queue forwarding.
Whenever a read operation is performed on this configuration register, the data stored in the VLAN Table at the
address specified by the SU.VTAA register is read. The VTAA value must be initialized prior to the read operation.
VLAN Forwarding. These values determine whether to forward a frame to an extract or forwarding queue or (in
the LAN to WAN direction) whether to discard the frame, There are 4096 VLAN IDs. The user may configure any
number of these 4096 VLAN IDs. The data in this register provides the read data that was retrieved from a VLAN
Table Read operation.
NOTE:
LAN Extract forwarding takes precedence over LAN Queue forwarding.
LAN Discard takes precedence over LAN Extract forwarding (trapping).
WAN Extract forwarding (trapping) takes precedence over WAN Queue forwarding.
Bit 12: VLAN Table Initialization Status (VTIS): This bit is set to 1 when the VLAN Table initialization has been
completed. Occurs upon reset.
Bits 0-11: VLAN Table Shadow Address (VTSA [12:1]) This register interfaces directly to the VLAN Table
memory block to provide the selected VLAN Table Address that is to be used for each VLAN Table operation (LAN
Trap, WAN Trap or uP Read/Write). When SU.VTC.CAIM = 1, the Shadow Address automatically increments for
each Read and/or Write VLAN Table Access.
WAN Extract Modes. This register determines which set of WAN Trap modes have been enabled. The WAN Trap
modes can be unrelated to the LAN Trap modes in the opposite direction. Any combination of these Traps can be
enabled. If any enabled Trap Modes overlap so that the WAN Trap indicates that a frame should be forwarded to
an Ethernet Port and to the WAN Extract, the frame is to be only forwarded to the WAN Extract (e.g. the user might
have configured the WAN Trap to forward the frame’s VLAN ID to Ethernet Port 1, but the frame’s DA might also
indicate that the frame is to be sent to the WAN Extract). WAN VLAN/Q-in-Q Forwarding is enabled through the
Forwarding Mode (not through these registers). The default setting is all Modes disabled.
To configure the X162 for VLAN or Q-in-Q, WAN to LAN forwarding, the Forwarding Mode must be set to 5, and
the WETPID register must be configured (or use the configuration register default values).
Bit 4: WAN Extract Header Trap High Byte (WEHTH). This value indicates whether the most significant byte of
the WEHT is to be used when performing the WAN Extract Header Trap
0 = Most significant byte is masked.
1 = Most significant byte is tested (not masked).
Bit 3: WAN Extract Header Trap Low Byte (WEHTL). This value indicates whether the least significant byte of
the WEHT is to be used when performing the WAN Extract Header Trap
0 = Least significant byte is masked.
1 = Least significant byte is tested (not masked).
Bits 0-2: WAN Header Extract Trap Position (WEHTP[3:1]) This value indicates the beginning byte position
within the WAN frame, for where the WAN Header Extract Trap is to be tested. Only binary values 0-6 are valid. A
value “0” indicates that the test is to begin on the first byte of the frame. The WAN Header Trap enables trapping
on SLARP, GFP PTI/UPI, GFP CID or Shim Tag.
Bits 0-15: WAN Header Trap (WEHT [16:1]) This value provides the first and second bytes of the WAN
Header Extract Trap (least significant bytes of the Trap Header). Any binary value is possible. The least significant
of these two bytes is in bit positions 0 – 7.
Bits 0-15: WAN Extract Destination Address Low (WEDAL [16:1]) This value provides the first and second
bytes of the WAN Extract Destination Address (least significant bytes of the address). This value in combination
with WEDAM and WEDAH make up the WAN Extract Destination Address. Any binary value is possible. The least
significant of these two bytes is in bit positions 0 – 7. The byte position of the DA within the WAN frame is derived
from the Decap, which knows whether 0, 4 or 8 WAN Header bytes will be removed.
Bits 0-15: WAN Extract Destination Address Mid (WEDAM [16:1]) This value provides the third and fourth
bytes of the WAN Extract Destination Address. This value in combination with WEDAL and WEDAH make up the
WAN Extract Destination Address. Any binary value is possible. The least significant of these two bytes is in bit
positions 0 – 7.
Bits 0-15: WAN Extract Destination Address High (WEDAH [16:1]) This value provides the fifth and sixth
bytes of the WAN Extract Destination Address. This value in combination with WEDAL and WEDAM make up the
WAN Extract Destination Address. Any binary value is possible. The least significant of these two bytes is in bit
positions 0 – 7.
Bits 0-7: WAN Extract Destination Address Mask (WEDAX [8:1]) This value provides a Mask for the Least
Significant byte of the WAN Extract Destination Address (bits 0 - 7 of WEDA0). This mask allows the device to Trap
on multiple DAs (e.g. Bridge Group Address 01-80-C2-00-00-00, Slow Protocols 01-80-C2-00-00-01 and Bridge
Management 01-80-C2-00-00-10). The default setting is all bit positions = 0.
0 = bit mask disabled.
1 = bit mask enabled (this bit of the WAN Extract Destination Address is “don’t care”).
Bits 0-15: WAN Extract Ethernet Type (WEET [16:1]). This value defines the 2-byte Ethernet Protocol Type
that the WAN Trap is to monitor for. Bits 0 to 7 are used to define the least significant byte. One example setting is
08-06 (hex) for Ethernet Type = ARP. Note that WAN Extract Ethernet Type trapping is not available for frame
formats in which the Ethernet Type field is more than 32 bytes into the frame. Thus, Ethernet Type trapping is not
applicable on WAN frames in the LLC/SNAP frame format with 4/8 byte frame headers plus dual VLAN Tags.
WAN Ethernet Tag Protocol ID (WETPID [16:1]). This register specifies the Ethernet Tag Protocol ID that is used
to denote WAN-VLAN frames. Four example settings are 8100 (standard), 9100 and 9200 (Juniper and Foundry)
and 88A8 (Extreme). Only applicable in Forwarding Mode 5.
NOTE: This is a real-time status register. Usefulness is limited to single frame transmissions for system
debugging. Most applications will be better served by monitoring the MAC Management Counter (MMC)
registers rather than polling these bits.
Bit 15: LAN Transmit Error Detected (LTED) This real-time status bit is set to 1 when the transmit MAC
encounters an error during a transmission attempt. Indicates Jaber Timeout, Frame Flushed, Loss of Carrier, No
Carrier, Late Collision, Excessive Collisions, or Excessive Deferral.
Bit 14: LAN Transmit Jabber Timeout (LTJTO) This real-time status bit is set to 1 when the transmit MAC
encounters an error during a transmission due to Jaber Timeout.
Bit 13: LAN Transmit Frame Flushed (LTFF) This real-time status bit is set to 1 when the transmit MAC
encounters an error during a transmission due to the frame being flushed by a software reset.
Bit 11: LAN Transmit Loss of Carrier (LTLOC) This real-time status bit is set to 1 when the transmit MAC
encounters an error during a transmission due to Loss of Carrier.
Bit 10: LAN Transmit No Carrier Present (LTNCP) This real-time status bit is set to 1 when the transmit MAC
encounters an error during a transmission due to the lack of a Carrier.
Bit 9: LAN Transmit Late Collision (LTLC) This real-time status bit is set to 1 when the transmit MAC encounters
an error during a transmission due to a Late Collision.
Bit 8: LAN Transmit Excessive Collisions (LTEC) This real-time status bit is set to 1 when the transmit MAC
encounters an error during a transmission due to Excessive (>16) Collisions.
Bits 3-6: LAN Transmit Collision Count (LTCC[3:0]) These real-time status bits indicate the number collisions
encountered while attempting to transmit the current frame.
Bit 2: LAN Transmit Excessive Deferral (LTEXD) This real-time status bit is set to 1 when the transmit MAC
encounters an error during a transmission due to Excessive Deferral.
Bit 1: LAN Transmit Underflow Error (LTUFE) This real-time status bit is set to 1 when the transmit MAC
encounters an error during a transmission due to data underflow.
Bit 0: LAN Transmit Deferred (LTDEF) This real-time status bit is set to 1 when the transmit MAC is deferring
transmission due to carrier availability. Only valid in half-duplex mode.
NOTE: This is a real-time status register. Usefulness is limited to single frame transmissions for system
debugging. Most applications will be better served by monitoring the MAC Management Counter (MMC)
registers rather than polling these bits.
Bit 15: LAN Transmit Error Detected (LTED) This real-time status bit is set to 1 when the transmit MAC
encounters an error during a transmission attempt. Indicates Jaber Timeout, Frame Flushed, Loss of Carrier, No
Carrier, Late Collision, Excessive Collisions, or Excessive Deferral.
Bit 14: LAN Transmit Jabber Timeout (LTJTO) This real-time status bit is set to 1 when the transmit MAC
encounters an error during a transmission due to Jaber Timeout.
Bit 13: LAN Transmit Frame Flushed (LTFF) This real-time status bit is set to 1 when the transmit MAC
encounters an error during a transmission due to the frame being flushed by a software reset.
Bit 11: LAN Transmit Loss of Carrier (LTLOC) This real-time status bit is set to 1 when the transmit MAC
encounters an error during a transmission due to Loss of Carrier.
Bit 10: LAN Transmit No Carrier Present (LTNCP) This real-time status bit is set to 1 when the transmit MAC
encounters an error during a transmission due to the lack of a Carrier.
Bit 9: LAN Transmit Late Collision (LTLC) This real-time status bit is set to 1 when the transmit MAC encounters
an error during a transmission due to a Late Collision.
Bit 8: LAN Transmit Excessive Collisions (LTEC) This real-time status bit is set to 1 when the transmit MAC
encounters an error during a transmission due to Excessive (>16) Collisions.
Bits 3-6: LAN Transmit Collision Count (LTCC[3:0]) These real-time status bits indicate the number collisions
encountered while attempting to transmit the current frame.
Bit 2: LAN Transmit Excessive Deferral (LTEXD) This real-time status bit is set to 1 when the transmit MAC
encounters an error during a transmission due to Excessive Deferral.
Bit 1: LAN Transmit Underflow Error (LTUFE) This real-time status bit is set to 1 when the transmit MAC
encounters an error during a transmission due to data underflow.
Bit 0: LAN Transmit Deferred (LTDEF) This real-time status bit is set to 1 when the transmit MAC is deferring
transmission due to carrier availability. Only valid in half-duplex mode.
This register determines which set of LAN Trap modes have been enabled and whether the device is being used in
a single or dual LAN Port application. The LAN Trap modes can be unrelated to the WAN Trap modes in the
opposite direction. Any combination of these Traps can be enabled. If any enabled Trap Modes overlap so that the
LAN Trap indicates that a frame should be forwarded to a LAN Queue and to the LAN Extract, the frame is to be
only forwarded to the LAN Extract (e.g. the user might have configured the LAN Trap to forward the frame’s VLAN
ID to LAN Queue 1, but the frame’s DA might also indicate that the frame is to be sent to the LAN Extract). LAN
VLAN/Q-in-Q Forwarding is enabled through the device’s Forwarding Mode (Common Control Registers; not
through these registers).
Bits 0-15: LAN Extract Destination Address Low (LEDAL[16:1]). This value provides the first and second
bytes of the LAN Extract Destination Address (least significant bytes of the address). This value in combination with
LEDAM and LEDAH make up the LAN Extract Destination Address. Any binary value is possible. The least
significant of these two bytes is in bit positions 0-7.
Bits 0-15: LAN Extract Destination Address Middle (LEDAM[16:1]). This value provides the third and fourth
bytes of the LAN Extract Destination Address. This value in combination with LEDAL and LEDAH make up the LAN
Extract Destination Address. Any binary value is possible. The least significant of these two bytes is in bit positions
0-7.
Bits 0-15: LAN Extract Destination Address High (LEDAH[16:1]) This value provides the fifth and sixth
bytes of the LAN Extract Destination Address. This value in combination with LEDAL and LEDAM make up the
LAN Extract Destination Address. Any binary value is possible. The least significant of these two bytes is in bit
positions 0-7.
Bits 0-7: LAN Extract Destination Address Mask (LEDAX [8:1]). This value provides a Mask for the Least
Significant byte of the LAN Extract Destination Address (bits 0 - 7 of LEDA0). This mask allows the device to Trap
on multiple DAs (e.g. Bridge Group Address 01-80-C2-00-00-00, Slow Protocols 01-80-C2-00-00-01 and Bridge
Management 01-80-C2-00-00-10).
0 = bit mask disabled
1 = bit mask enabled (this bit of the LAN Extract Destination Address is “does not care”)
Bits 0-15: LAN Extract Ethernet Type (LEET[16:1]). This value defines the 2-byte Ethernet Protocol Type
that the LAN Trap is to monitor for. Bits 0 to 7 are used to define the least significant byte. One example setting is
08-06 (hex) for Ethernet Type = ARP.
Bit 1-2: LAN Port 1 Ethernet VLAN Tag Function Enable(LP1ETF[2:1]). The Ethernet VLAN Tag functions
are not required to be enabled for Priority Scheduling (LP1PF = 01/10).
00 = LAN Ethernet VLAN Tag Functions Disabled
01 = LAN Ethernet VLAN Tag Extract, Forwarding/Scheduling, Discarding Functions Enabled
10 = Reserved
11 = Reserved
Bit 2-1: LAN Port 2 Ethernet VLAN Tag Function Enable (LP2ETF[2:1]). The Ethernet VLAN Tag functions
are not required to be enabled for Priority Scheduling (LP1PF = 01/10).
00 = LAN Ethernet VLAN Tag Functions Disabled
01 = LAN Ethernet VLAN Tag Extract, Forwarding/Scheduling, Discarding Functions Enabled
10 = Reserved
11 = Reserved
The L2PE = 1 (Enabled) is only valid when LPM = 1 (Dual Port) and when in Forwarding Modes 2, 4, or 5.
Otherwise, the device should be configured to L2PE =0 (Disabled).
When LAN Port 2 Priority Forwarding or Priority Scheduling has been enabled, the user must also configure the
Priority Table and No Priority Detected registers.
When LAN Port 2 Ethernet Tag Forwarding has been enabled, the user must also configure the Ethernet Tag Table
and No Ethernet Tag Detected registers.
Bit 4-5: LAN No Priority Tag Detected Forwarding (LNPDF[2:1]). Enabled for each port with SU.LP1C.LP1PF
or SU.LP2C.LP2PF. Controls how frames are handled when the received frame does not contain DSCP, does not
contain a VLAN Tag, or the 13th and 14th bytes of the frame do not match the value in SU.LQTPID. The same
action is applied to both Ethernet ports.
00 = Forward to LAN Priority Queue 1
01 = Forward to LAN Priority Queue 2
10 = Forward to LAN Priority Queue 3
11 = Forward to LAN Priority Queue 4
Bit 0-3: LAN No VLAN Tag Detected Forwarding (LNVDF[4:1]). Enabled for each port with SU.LP1C.LP1ETF or
SU.LP2C.LP2ETF. Controls how frames are handled when the received frame does not contain a VLAN tag or the
13th and 14th bytes of the frame do no match the value in SU.LQTPID. The same action is applied to both Ethernet
ports.
0000 = Forward to WAN Group 1
0001 = Forward to WAN Group 2
0010 = Forward to WAN Group 3
0011 = Forward to WAN Group 4
01xx = Forward this frame to the LAN Extract Queue
1xxx = Discard this frame
Bits 0-15: LAN Queue Watermark Xmt Pause Control (LQXPC [16-1]) One bit is provided for each of the 16
LAN Queues. When set to one, a pause frame will be transmitted when the associated queue has exceeded the
watermark defined in AR.LQW.
0 = LAN Queue Watermark Xmt Pause Control Disabled
1 = LAN Queue Watermark Xmt Pause Control Enabled
Bits 0-15: LAN Q-in-Q Tag Protocol ID (LQTPID [16:1]) This register specifies the Ethernet Tag Protocol ID that
is used to denote LAN-VLAN and Q-in-Q frames. Four example settings are 8100 (standard), 9100 and 9200
(Juniper and Foundry) and 88A8 (Extreme). The default setting is for 8100.
The LAN Queue Overflow Status register bits are set when a frame has been discarded due to Transmit LAN
Queue overflow and are reset following a read of this register.
Bits 0-13: Maximum Packet Length (MPL [14:1]) Maximum frame length, in bytes. The receive MAC discards
Ethernet frame received from the LAN interface that have a frame length greater than the user configured MPL
value. This value is applied to both Ethernet ports. If the device has been configured to discard the Ethernet FCS
then the byte count up to the FCS is used. If the FCS is retained, then the count includes 4 bytes for the FCS. The
maximum valid value for this register is 10240 bytes. Note that frames between 9018 and 10240 bytes may be
counted as “giant frames” by the MAC.
LAN 1 Policing Parameters . This register determines the Policing function setting for Ethernet port 1. The
Policing function is used to control the rate at which frames are forwarded to Serial Interfaces. The Policing function
can be configured to send Explicit Back Pressure Flow Control to the Ethernet Sending equipment (Ethernet Pause
Control) or can be used to enable a frame discarding mechanism that restrict the rate at which frame are accepted.
Bit 15: Committed Burst Size Selection (CBSS) This bit function is not available in device revision A1
(GL.IDR.REVn = 000).
0 = Default condition. CBS is 4096 bytes.
1 = CBS is 12288 bytes. Only valid in Policing Discard mode.
Bits 0-7: LAN 1 Policing Credit Threshold (L1PCT[8:1]). This register specifies the Credit Threshold setting of
the Policing function. Only values between 8 to 255 are supported.
LAN 2 Policing Parameters. This register determines the Policing function setting for Ethernet port 2. The Policing
function is used to control the rate at which frames are forwarded to Serial Interfaces. The Policing function can be
configured to send Explicit Back Pressure Flow Control to the Ethernet Sending equipment (Ethernet Pause
Control) or can be used to enable a frame discarding mechanism that restrict the rate at which frame are accepted.
Bit 15: Committed Burst Size Selection (CBSS) This bit function is not available in device revision A1
(GL.IDR.REVn=000).
0 = Default condition. CBS is 4096 bytes.
1 = CBS is 12288 bytes. Only valid in Policing Discard mode.
Bits 0-7: LAN 2 Policing Credit Threshold (L2PCT[8:1]). This register specifies the Credit Threshold setting of
the Policing function. Only values between 8 to 255 are supported.
Priority Table Control This register is used to initialize and specify the operating mode of the Priority Table. The
Initialization function causes each entry of the Priority Table to be populated with the Priority Table Write Data
default value. The configuration of this table is similar to that of the VLAN Table. However, although this table
provides an automated self-init at power-up, it does not allow the user to request a new initialization ”at will”.
Bit 1: Priority Table Enable (PTE) When equal to zero, the Priority Table is enabled. When set to 1, the Priority
Table does not affect the forwarding of frames.
Bit 0: Priority Table Auto Increment Mode (PTAIM) When set, the Priority Table Address in SU.PTAA is
automatically with each read or write of the SU.PTWD or SU.PTRD registers.
Bit 6: Priority Table Port Access Address (PTPAA). This bit is an extension of the PTAA[6:1] bits, but is used to
divide between Priority lookups for Ethernet (LAN) Port 1 (PTPAA = 0) and Ethernet (LAN) Port 2 (PTPAA = 1). Not
valid for devices with only one Ethernet port.
Bits 0-5: Priority Table Access Address (PTAA [6:1]). These bits provide the Priority Table Address for a uP
Read or Write operation. The address into the priority table is used to resolve VLAN 802.1p PCP and DSCP to the
four priority levels. When using PCP priority mode, only addresses PTAA[3:1] are used. The priority mode for each
Ethernet port can be independently selected using the SU.LP1C and SU.LP2C registers.
Note that LAN-VLAN Discarding and LAN Extraction takes precedence over Priority Forwarding.
Bit 7: Priority Table Initialization Status (PTIS): This bit is set when the Priority Table initialization has been
completed.
Bit 6: Priority Table Port Shadow Address (PTSAA). This bit is an extension of the PTSA [6:1] bits, but is used
to divide between Priority lookups for LAN Port 1 (PTSAA = 0) and LAN Port 2 (PTSAA = 1).
Bits 0-5: Priority Table Shadow Address (PTSA [6:1]). This register interfaces directly to the Priority Table
memory block to provide the selected Priority Table Address that is to be used for each Priority Table operation
(LAN Trap, WAN Trap or uP Read/Write). When PTAIM = 1, the Shadow Address automatically increments for
each updated Read and/or Write Priority Table Access Address.
Bit 10: Bridge Filter Table Reset (BFTR). When the user configures this bit to BFTR = 1, the Bridge Filter
automatically steps through each of the 4096 Bridge Filter Table addresses, aging all Table entries so that the table
is reset (one-time event each time the user writes BFTR = 1).
0 = No Bridge Filter Table Reset
1 = One-time Bridge Filter Table Reset
Bits 8-0: Bridge Filter Aging Period (BFAP[1-9]). These bits provide the binary coded value for the Aging Period.
The valid equivalent decimal values for this variable are 1 to 300. Values larger than 300 will not increase the aging
period above 300 seconds. The default is set to 300 sec.
Bits 0-9: LAN Queue 1 Start Address [10-1] This register specifies the Start Address for the LAN Queue 1. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 2 Start Address [10-1] This register specifies the Start Address for the LAN Queue 2. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 3 Start Address [10-1] This register specifies the Start Address for the LAN Queue 3. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 4 Start Address [10-1] This register specifies the Start Address for the LAN Queue 4. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 5 Start Address [10-1] This register specifies the Start Address for the LAN Queue 5. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 6 Start Address [10-1] This register specifies the Start Address for the LAN Queue 6. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 7 Start Address [10-1] This register specifies the Start Address for the LAN Queue 7. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 8 Start Address [10-1]. This register specifies the Start Address for the LAN Queue 8. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 9 Start Address [10-1]. This register specifies the Start Address for the LAN Queue 9. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 10 Start Address [10-1] This register specifies the Start Address for the LAN Queue 10.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: LAN Queue 11 Start Address [10-1]. This register specifies the Start Address for the LAN Queue 11.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: LAN Queue 12 Start Address [10-1] This register specifies the Start Address for the LAN Queue 12.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: LAN Queue 13 Start Address [10-1] This register specifies the Start Address for the LAN Queue 13.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: LAN Queue 15 Start Address [10-1]. This register specifies the Start Address for the LAN Queue 15.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: LAN Queue 16 Start Address [10-1]. This register specifies the Start Address for the LAN Queue 16.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: LAN Queue 1 End Address [10-1] This register specifies the End Address for the LAN Queue 1. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 2 End Address [10-1] This register specifies the End Address for the LAN Queue 2. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 3 End Address [10-1]. This register specifies the End Address for the LAN Queue 3. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 4 End Address [10-1] This register specifies the End Address for the LAN Queue 4. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 5 End Address [10-1] This register specifies the End Address for the LAN Queue 5. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 6 End Address [10-1] This register specifies the End Address for the LAN Queue 6. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 7 End Address [10-1] This register specifies the End Address for the LAN Queue 7. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 8 End Address [10-1] This register specifies the End Address for the LAN Queue 8. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 9 End Address [10-1] This register specifies the End Address for the LAN Queue 9. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: LAN Queue 10 End Address [10-1]. This register specifies the End Address for the LAN Queue 10. The
value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: LAN Queue 11 End Address [10-1] This register specifies the End Address for the LAN Queue 11. The
value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: LAN Queue 12 End Address [10-1] This register specifies the End Address for the LAN Queue 12. The
value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: LAN Queue 13 End Address [10-1] This register specifies the End Address for the LAN Queue 13. The
value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: LAN Queue 14 End Address [10-1] This register specifies the End Address for the LAN Queue 14. The
value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: LAN Queue 15 End Address [10-1] This register specifies the End Address for the LAN Queue 15. The
value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: LAN Queue 16 End Address [10-1]. This register specifies the End Address for the LAN Queue 16. The
value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 1 Start Address [10-1] This register specifies the Start Address for the WAN Queue 1.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 2 Start Address [10-1] This register specifies the Start Address for the WAN Queue 2.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 3 Start Address [10-1]. This register specifies the Start Address for the WAN Queue 3.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 4 Start Address [10-1] This register specifies the Start Address for the WAN Queue 4.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 5 Start Address [10-1] This register specifies the Start Address for the WAN Queue 5.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 6 Start Address [10-1] This register specifies the Start Address for the WAN Queue 6.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 7 Start Address [10-1] This register specifies the Start Address for the WAN Queue 7.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 8 Start Address [10-1]. This register specifies the Start Address for the WAN Queue 8.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 9 Start Address [10-1] This register specifies the Start Address for the WAN Queue 9.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 10 Start Address [10-1]. This register specifies the Start Address for the WAN Queue 10.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 11 Start Address [10-1] This register specifies the Start Address for the WAN Queue 11.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 12 Start Address [10-1]. This register specifies the Start Address for the WAN Queue 12.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 13 Start Address [10-1] This register specifies the Start Address for the WAN Queue 13.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 14 Start Address [10-1] This register specifies the Start Address for the WAN Queue 14.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 15 Start Address [10-1] This register specifies the Start Address for the WAN Queue 15.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 16 Start Address [10-1] This register specifies the Start Address for the WAN Queue 16.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 1 End Address [10-1] This register specifies the End Address for the WAN Queue 1. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: WAN Queue 2 End Address [10-1] This register specifies the End Address for the WAN Queue 2. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: WAN Queue 3 End Address [10-1] This register specifies the End Address for the WAN Queue 3. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: WAN Queue 4 End Address [10-1] This register specifies the End Address for the WAN Queue 4. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: WAN Queue 5 End Address [10-1] This register specifies the End Address for the WAN Queue 5. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: WAN Queue 6 End Address [10-1] This register specifies the End Address for the WAN Queue 6. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: WAN Queue 7 End Address [10-1] This register specifies the End Address for the WAN Queue 7. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: WAN Queue 8 End Address [10-1] This register specifies the End Address for the WAN Queue 8. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: WAN Queue 9 End Address [10-1] This register specifies the End Address for the WAN Queue 9. The
value specifies the most significant 10 bits of the SDRAM absolute address.
Bits 0-9: WAN Queue 10 End Address [10-1] This register specifies the End Address for the WAN Queue 10.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 11 End Address [10-1] This register specifies the End Address for the WAN Queue 11.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 12 End Address [10-1]. This register specifies the End Address for the WAN Queue 12.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 13 End Address [10-1] This register specifies the End Address for the WAN Queue 13.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 14 End Address [10-1] This register specifies the End Address for the WAN Queue 14.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 15 End Address [10-1] This register specifies the End Address for the WAN Queue 15.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: WAN Queue 16 End Address [10-1] This register specifies the End Address for the WAN Queue 16.
The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity of 32,768
bytes per LSB.
Bits 0-9: LAN Insert Queue Start Address [10-1] This register specifies the Start Address for the LAN Insert
Queue. The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity
of 32,768 bytes per LSB.
Bits 0-9: LAN Insert Queue End Address [10-1] This register specifies the End Address for the LAN Insert
Queue. The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity
of 32,768 bytes per LSB.
Bits 0-9: LAN Extract Queue Start Address [10-1] This register specifies the Start Address for the LAN Extract
Queue. The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity
of 32,768 bytes per LSB.
Bits 0-9: LAN Extract Queue End Address [10-1]. This register specifies the End Address for the LAN Extract
Queue. The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity
of 32,768 bytes per LSB.
Bits 0-9: WAN Insert Queue Start Address [10-1] This register specifies the Start Address for the WAN Insert
Queue. The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity
of 32,768 bytes per LSB.
Bits 0-9: WAN Insert Queue End Address [10-1] This register specifies the End Address for the WAN Insert
Queue. The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity
of 32,768 bytes per LSB.
Bits 9-0: WAN Extract Queue Start Address [10-1] This register specifies the Start Address for the WAN Extract
Queue. The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity
of 32,768 bytes per LSB.
Bits 0-9: WAN Extract Queue End Address [10-1] This register specifies the End Address for the WAN Extract
Queue. The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a granularity
of 32,768 bytes per LSB.
Bits 0-12: LAN Queue Watermark [LQW 13-1] This register specifies the Watermark Threshold that is used to
trigger a LAN Pause control frame. One value is used for all 16 queues (each queue is independently enabled and
tested). The value from this register is multiplied by 64 to determine the minimum number of bytes available in each
DDR SDRAM LAN Queue after Flow Control (or LAN Queue Watermark Interrupt) is triggered. The maximum valid
value is decimal 8191, which designates that a minimum of 8191 x 64 bytes = 524,224 bytes can be stored after
the watermark is reached. The lowest valid setting is decimal 3, or a minimum of 192 bytes available when flow
control is triggered.
The purpose of the LQW setting is to prevent data loss due to queue overflow. The LQW setting is independent of
the CIR Policing function that monitors the rate at which data is received irrespective of the fill level of the queue.
For applications with maximum packet Length < 2049 and with a short Ethernet PHY transmission distance (< 25
meters) it is recommended that the LQW be set to a minimum value of 57.
For applications that include a long Ethernet PHY transmission distance the LQW setting can be increased. For
GbE applications the LQW value can be increased by 1 for each additional 88 meters (up to LQW = 8191 or
715km). For 100Mbps each incremental step will support 880 meters (at 100Mbps there is less/slower data on the
transmission line). For 10Mbps each incremental step will support 8,800 meters. It is recommended that the user
verify the LQW setting in long Ethernet transmission line applications.
Bit 8: WAN Queue Overflow Discard Enable (WQODE) Setting used for all 16 WAN Queues.
0 = Overflow Discard Enabled.
1 = Overflow Discard Disabled.
This setting is used for all 16 WAN Queues. When WQODE = 0 and an overflow condition occurs on a WAN
queue, that entire queue is discarded. This bit setting is independent of the Preemptive Discard (WQPD).
Bits 0-9: Bridge Filter Table Offset Address (BFTOA[10-1]) This register specifies the Offset Address for the
Bridge Table. The value specifies the most significant 10 bits of the SDRAM absolute address, resulting in a
granularity of 32,768 bytes per LSB.
Bits 0-15: LAN Queue Overflow Status (LQOS[16-1]) This register indicates whether an overflow condition has
occurred on any of the LAN Queues since the last read of this register (one status bit per LAN Queue). This
register is reset each time it is read.
0 = No overflow condition detected
1 = At least one overflow condition detected since last read
Bits 0-15: LAN Queue Overflow Interrupt Mask (LQOIM[16-1]) This register provides an interrupt bit mask to
filter out unwanted interrupts.
0 = Bit mask disabled
1 = Bit mask enabled
Bits 0-15: LAN Queue Near Full Status (LQNFS[16-1]) This register indicates whether any of the LAN Queues
have exceeded the LAN Queue Watermark defined in AR.LQW since the last read of this register (one status bit
per LAN Queue). This register is reset each time it is read.
0 = No Near Full condition detected
1 = At least one Near Full condition detected since last read
Bits 0-15: LAN Queue Near Full Interrupt Mask (LQNFIM[16-1]) This register provides an interrupt bit mask to
filter out unwanted interrupts.
0 = Bit mask disabled
1 = Bit mask enabled
Bits 0-15: WAN Queue Overflow Status (WQOS[16-1]) This register indicates whether an overflow condition has
occurred on any of the WAN Queues since the last read of this register (one status bit per WAN Queue). This
register is reset each time it is read.
0 = No overflow condition detected
1 = At least one overflow condition detected since last read
Bits 0-15: WAN Queue Overflow Interrupt Mask (WQOIM[16-1]) This register provides an interrupt bit mask to
filter out unwanted interrupts.
0 = Bit mask disabled
1 = Bit mask enabled
Bits 0-15: WAN Queue Near Full Status (WQNFS[16-1]) This register indicates whether an impending overflow
condition has occurred on a WAN Queue, and the device initiated the discarding of incoming frames on a WAN
interface. This condition can occur if the transmit LAN interface is disabled, if the MAC has received excessive
pause flow control frames and completely filled the buffers for the transmit LAN while responding to the pause
requests, or if operating in half duplex mode with heavy LAN network congestion. This register is cleared each time
it is read.
0 = Normal operation
1 = At least one “Near Full” condition detected since last read, frames may have been discarded.
Bits 0-15: WAN Queue Near Full Interrupt Mask (WQNFIM[16-1]) This register provides an interrupt bit mask to
filter interrupts based on the status conditions in the AR.WQNFS register.
0 = Bit mask disabled
1 = Bit mask enabled
Bit 1: WAN Extract Queue Overflow Status [WEQOS] This bit indicates whether an overflow condition has
occurred on the LAN Extract Queue since the last read of this register. This register is reset each time it is read.
0 = No Overflow condition detected
1 = At least one Overflow condition detected since last read
Bit 0: LAN Extract Queue Overflow Status [LEQOS] This bit indicates whether an overflow condition has
occurred on the LAN Extract Queue since the last read of this register. This register is reset each time it is read.
0 = No Overflow condition detected
1 = At least one Overflow condition detected since last read
Bit 1: WAN Extract Queue Overflow Interrupt Mask [WEQOIM] This bit provides an interrupt bit mask to filter
out unwanted interrupts.
0 = Bit mask disabled
1 = Bit mask enabled
Bit 0: LAN Extract Queue Overflow Interrupt Mask [LEQOIM] This bit provides an interrupt bit mask to filter
out unwanted interrupts.
0 = Bit mask disabled
1 = Bit mask enabled
Bit 4: Extract Queue Overflow Interrupt [EQOI] This bit provides an indication of whether this is an active
interrupt. This bit should not be latched, but should provide a logical OR of the Extract Queue Overflow Status
register bits (any “1” generates an interrupt).
0 = No active Interrupt
1 = Active Interrupt
Bit 3: WAN Queue Near Full Interrupt [WQNFI] This bit provides an indication of whether this is an active
interrupt. This bit should not be latched, but should provide a logical OR of the WAN Queue Near Full Status
register bits (any “1” generates an interrupt).
0 = No active Interrupt
1 = Active Interrupt
Bit 2: WAN Queue Overflow Interrupt [WQOI] This bit provides an indication of whether this is an active
interrupt. This bit should not be latched, but should provide a logical OR of the WAN Queue Overflow Status
register bits (any “1” generates an interrupt).
0 = No active Interrupt
1 = Active Interrupt
Bit 1: LAN Queue Near Full Interrupt [LQNFI] This bit provides an indication of whether this is an active
interrupt. This bit should not be latched, but should provide a logical OR of the LAN Queue Near Full Status
register bits (any “1” generates an interrupt).
0 = No active Interrupt
1 = Active Interrupt
Bit 0: LAN Queue Overflow Interrupt [LQOI] This bit provides an indication of whether this is an active
interrupt. This bit should not be latched, but should provide a logical OR of the LAN Queue Overflow Status register
bits (any “1” generates an interrupt).
0 = No active Interrupt
1 = Active Interrupt
Bit 0: Encapsulator HDLC CRC Bit Reorder (EHCBO) Controls the endian order of the HDLC CRC calculation.
This bit function is not available in device revision A1 (GL.IDR.REVn=000).
0 = HDLC CRC will be calculated MSB-first. Default operation.
1 = HDLC CRC will be calculated LSB-first.
Bits 0-15: Encapsulator Line Header Data (ELHD[31:16]) These 2 bytes provide the most significant bytes of the
Line Header, when enabled with ELHDE. ELDH[31:25] is inserted first, followed by ELHD[23:16].
Bits 0-15: Encapsulator Line Header Data (ELHD[15:0]) These 2 bytes provide the least significant bytes of the
Line Header, when enabled with ELHDE. ELDH[15:8] is inserted first, followed by ELHD[7:0].
Bits 0-15: Encapsulator Tag 1 Data (ET1D[31:16]) These 2 bytes provide the most significant bytes of Tag 1,
when enabled with ET1E. ET1D[31:25] is inserted first, followed by ET1D[23:16].
Bits 0-15: Encapsulator Tag 1 Data (ET1D[15:0]) These 2 bytes provide the least significant bytes of Tag 1,
when enabled with ET1E. ET1D[15:8] is inserted first, followed by ET1D[7:0].
Bits 0-15: Encapsulator Tag 2 Data (ET2D[31:16]) These 2 bytes provide the most significant bytes of Tag 2,
when enabled with ET2E. ET2D[31:25] is inserted first, followed by ET2D[23:16].
Bits 0-15: Encapsulator Tag 2 Data (ET2D[15:0]) These 2 bytes provide the least significant bytes of Tag 2,
when enabled with ET2E. ET2D[15:8] is inserted first, followed by ET2D[7:0].
Bit 15: Encapsulator PLI Error Insert Enable (EPLIEIE) When set to 1, a single-bit error insertion is enabled for
the PLI field. This includes the 2 PLI Header bits and the corresponding CHEC.
Bit 14: Encapsulator Data Error Insert Enable (EDEIE) When set to 1, a single-bit error insertion is enabled for
the data field. Errors can only be inserted in the first byte of the payload data. Hence the EBD bit setting has no
effect for inserting payload errors.
Bit 13: Encapsulator Ethernet FCS Error Insert Enable (EFCSEIE) When set to 1, a single-bit error insertion is
enabled for the Ethernet FCS field.
Bit 12: Encapsulator FCS Error Insert Enable (EPLIEIE) When set to 1, a single-bit error insertion is enabled for
the encapsulation FCS field.
Bits 10-11: Encapsulator Byte Decode (EBD[1:0]) These bits determine which of the 4 bytes need error insertion
for the PLI, Ethernet FCS, and Encapsulation FCS fields. These bits have no effect on data error insertion.
Bits 2-9: Encapsulator Error Insert (EIE[7:0]) These 8 bits determine the bit location of the error insertion in the
selected field. Only one error is inserted for each transition of ESEI.
Bit 1: Encapsulator Single Error Insert (ESEI) Changing this bit from a 0 to a 1 causes a single error insertion.
For a second error insertion, the user must first clear this bit.
Bits 0-15: Encapsulator Frame Count (EFCNT[15:0]) This counter provides the number of frames that have
been encapsulated. The counter is reset upon being read by the microprocessor.
Bit 11: (SOPLE) This bit is set upon detection of an internal error.
Bit 10: (SOPSE) This bit is set upon detection of an internal error.
Bit 9: (COPLE) This bit is set upon detection of an internal error.
Bit 8: (COPSE) This bit is set upon detection of an internal error.
Bit 7: (EOPLE) This bit is set upon detection of an internal error.
Bit 6: (EOPSE) This bit is set upon detection of an internal error.
Bit 4: (FUF) This bit is set if the encapsulator FIFO has underflowed.
Bit 3: (FOVF) This bit is set if the encapsulator FIFO has overflowed.
Bit 2: (FLOK) This bit is set if the encapsulator FIFO is ok to accept more data. Cleared on read.
Bit 1: (FF) This bit is set if the encapsulator FIFO is full. Cleared on read.
Bit 0: (FE) This bit is set if the encapsulator FIFO is empty. Cleared on read.
Bit 11: (SOPLEIE) This bit enables an interrupt on the SOPLE condition.
Bit 10: (SOPSEIE) This bit enables an interrupt on the SOPSE condition.
Bit 9: (COPLEIE) This bit enables an interrupt on the COPLE condition.
Bit 8: (COPSEIE) This bit enables an interrupt on the COPSE condition.
Bit 7: (EOPLEIE) This bit enables an interrupt on the EOPLE condition.
Bit 6: (EOPSEIE) This bit enables an interrupt on the EOPSE condition.
Bit 4: (FUFIE) This bit enables an interrupt on the FUF condition.
Bit 3: (FOVFIE) This bit enables an interrupt on the FOVF condition.
Bit 2: (FLOKIE) This bit enables an interrupt on the FLOK condition.
Bit 1: (FFIE) This bit enables an interrupt on the FF condition.
Bit 0: (FEIE) This bit enables an interrupt on the FE condition.
Bits 0-15: Encapsulator HDLC Fill Length (EHFL[7:0]) Used to set the minimum number of HDLC Fill flags to be
inserted after the end of each frame. Only valid when HDLC encapsulation is used.
Bits 3-4: Decapsulator Add Enable (DAE[1:0]) Controls the insertion of additional bytes by the decapsulator.
00 = Normal operation.
01 = The 18 byte value from the PP.DA1DR through PP.DA9DR registers will be inserted after the
cHEC bytes in GFP mode, or after the HDLC header/flag when in HDLC mode.
10 = The 14 byte value from the PP.DA1DR through PP.DA7DR registers will be inserted after the
cHEC bytes in GFP mode, or after the HDLC header/flag when in HDLC mode.
11 = Reserved.
Bit 2: Decapsulator GFP Synchronization Control (DGSC) When set, “triple synchronization” is selected. Three
consecutive PLIs and respective cHEC must be correct to enter the Synchronization State. If equal to zero, two
consecutive correct PLIs and cHECs are required. Only applicable to GFP Mode.
Bit 1: Decapsulator HDLC Rate Adaptation (DHRAE)
0= Disabled. Default for non-X.86 (LAPS) modes.
1= Enabled. “7D DD” sequence removed from data stream. For use in X.86 (LAPS) mode.
Bit 0: Decapsulator HDLC CRC Bit Order (DHCBO) Controls the endian order of the HDLC CRC calculation.
This bit function is not available in device revision A1 (GL.IDR.REVn=000).
0 = HDLC CRC will be calculated MSB-first. Default operation.
1 = HDLC CRC will be calculated LSB-first.
Bits 0-15: Decapsulator 1 Data High (D1D [15:0]) These 2 bytes provide the data if the addition is enabled with
PP.DMCR.DAE[1:0].
Bits 0-15: Decapsulator 2 Data (D2D [15:0]) These 2 bytes provide the data if the addition is enabled with
PP.DMCR.DAE[1:0].
Bits 0-15: Decapsulator 3 Data (D3D [15:0]) These 2 bytes provide the data if the addition is enabled with
PP.DMCR.DAE[1:0].
Bits 0-15: Decapsulator 4 Data (D4D [15:0]) These 2 bytes provide the data if the addition is enabled with
PP.DMCR.DAE[1:0].
Bits 0-15: Decapsulator 5 Data (D5D [15:0]) These 2 bytes provide the data if the addition is enabled with
PP.DMCR.DAE[1:0].
Bits 0-15: Decapsulator 6 Data (D6D [15:0]) These 2 bytes provide the data if the addition is enabled with
PP.DMCR.DAE[1:0].
Bits 0-15: Decapsulator 7 Data High (D7D [15:0]) These 2 bytes provide the data if the addition is enabled
PP.DMCR.DAE[1:0].
Bits 0-15: Decapsulator 8 Data (D8D [15:0]) These 2 bytes provide the data if the addition is enabled with
PP.DMCR.DAE[1:0].
Bits 0-15: Decapsulator 9 Data High (D9D [15:0]) These 2 bytes provide the data if the addition is enabled with
PP.DMCR.DAE[1:0].
Bit 15: Decapsulator GFP Sync Latched Status (DGSLS) When Set the GFP has achieved Synchronization
Latched Status. This bit is cleared upon a read.
Bit 14: Decapsulator GFP Sync Loss Latched Status (DGSLLS) When Set indicates that the GFP has lost
synchronization. This bit is cleared upon a read.
Bit 13: Decapsulator GFP Loss of Client Signal Latched Status (DGLCLS) When Set indicates that the GFP
Loss of Client Signal Management Frame has arrived. This bit is cleared upon a read.
Bit 12: Decapsulator GFP Loss of Client Synchronization Latched Status (DGLCSLS) When Set indicates that
the GFP Loss of Client Synchronization Management Frame has arrived. This bit is cleared upon a read.
Bit 11: Decapsulator FCS Fail Latched Status (DFFLS) When set indicates that the FCS has failed. This bit is
cleared upon a read.
Bit 9: Decapsulator Extension Header eHEC Fail Latched Status (DCHECFLS) When set indicates that the
Extension HEC has failed. This bit is cleared upon a read.
Bit 8: Decapsulator Type HEC Fail Latched Status (DTCHECFLS) When set indicates Type HEC has failed.
Bit 7: Decapsulator FIFO Under run Latched Status (DFUR) When set indicates that the FIFO has under run.
Bit 6: Decapsulator FIFO Overflow Latched Status (DFOVF) When set indicates that the FIFO has overflowed.
Bit 15-0/ Decapsulator Good Packet Low Latched Counter(DGPLC 15:0) – This bits provide the low word of the
good Frame Counter. This counter is cleared upon a read.
Bit 8-15: Decapsulator Bad Packet Latched Counter(DBPLC 7:0) These bits provide the bad frame counter
latched value. The counter is cleared upon a read. The following are counted: Aborts, Runt, FCS Errors, Type
CHEC failures.
Bit 2: Decapsulator GFP Sync Status (DGSYNC) This bit is set when GFP is Synchronized. This bit can be read
after the transition of DFSRWPC.
Bit 1: Decapsulator GFP Pre Sync Status (DGPSYNC) This bit is set when GFP Synchronization Machine is in
the Pre-Synchronized state. This bit can be read after the transition of DFSRWPC.
Bit 0: Decapsulator GFP Hunt Status (DHUNT) This bit is set when GFP Synchronization Machine is in the Hunt
state. This bit can be read after the transition of DFSRWPC.
Bit 15-0: Decapsulator Header High Status (DHSR31:16) – These bits provide the high word of the Header
Bytes that have been received. These are the first 2 bytes after the HDLC start flag and The first 2 bytes after the
GFP PLI and GFP cHEC.
Bit 15-0: Decapsulator Header Low Status (DHSR15:0) – These bits provide the low word of the Header Bytes
that have been received. These are the bytes 3 and 4 after the HDLC start flag and bytes 3 and 4 after the GFP
PLI and GFP cHEC.
Bit 3: Decapsulator Error Mode (DEM) When set to 1, errored frames are forwarded. Normally they are
discarded. This bit function was located in DMCR bit 0 in device revision A1 (GL.IDR.REVn=000).
Bit 2: Decapsulator State Machine Reset (DSMRE) If this bit is set and DFSRWPC transitions, The
Decapsulator State Machine will be reset.
Bit 1: Decapsulator FIFO Pointer reset Enable (DFPRE) - Setting this bit to a 1 will enable the FIFO to be reset.
The FIFO Read and Write pointer will be reset if DFSRWPC transitions and this bit is set.
Bit 0: Decapsulator FIFO and State Read, Write, and PMU Control (DFSRWPC)- A 0 to 1 transition enables the
FIFO Read and Write Addresses, Status Registers to be read by the processor. The user must wait 4 system
clocks before the reads can be done. This bit is used to control resetting of the FIFO Read and Write Pointers and
the Decapsulator State Machine. This bit is also used as a PMU update for all decapsulator latched counters.
Bit 11: Transmit GID Bit Convention (TGIDBC) Controls all 4 VCGs. This bit is only used when TGIDM = 1
0 = bit 15 of the TGIDx register is transmitted first.
1 = bit 0 of TGIDx register is transmitted first.
Bit 9: Transmit Configuration Change Load (TLOAD). When all WAN transmit ports have been configured with
the correct SQ assignments, CTRL commands, member count (TCR1.VnMC[3:0]), VCG assignments, and LCAS
Enable (LE[4:1]), a 0-to-1 transition on this bit will load the new configuration on the next VCAT Start of Frame
(SOF). This register will update all VCGs.
Bits 12-15: Transmit VCG4 Member Count (TV4MC[3:0]) These bits indicate to the device the number of
members assigned to VCG4
0000 = 1 Member
0001 = 2 Members
0010 = 3 members
…..
1111 = 16 members
Bits 8-11: Transmit VCG3 Member Count (TV3MC[3:0]) These bits indicate to the device the number of
members assigned to VCG3
0000 = 1 Member
0001 = 2 Members
0010 = 3 members
…..
1111 = 16 members
Bits 4-7: Transmit VCG2 Member Count (TV2MC[3:0]) These bits indicate to the device the number of members
assigned to VCG2
0000 = 1 Member
0001 = 2 Members
0010 = 3 members
…..
1111 = 16 members
Bits 0-3: Transmit VCG1 Member Count (TV1MC[3:0]) These bits indicate to the device the number of members
assigned to VCG1
0000 = 1 Member
0001 = 2 Members
0010 = 3 members
…..
1111 = 16 members
Note: If more than one member is assigned to a WAN group, VCAT must be enabled for that group. Updates to this
register take effect after VCGCR.TLOAD transitions.
Bits 8-11: Transmit VCAT Sequence Mapping (TVSQ[3:0]) These four bits are a BCD number that is used in the
“SQ” field of the VCAT MFI on that port. When LCAS is enabled, the internal LCAS engine controls the transmit
sequence number and reading these bits provides the current assigned sequence number for a given port. The
user should take care to not overwrite these bits when LCAS is enabled. When LCAS is not enabled, the user
can write a value to specifically assign a port’s sequence in a VCG. Note that in T3/E3 operation, only sequence
numbers 0-7 are valid.
Bits 12-15: Transmit GID Value (TGID[15:0]) These bits contain a user-programmed value to be transmitted
through the VCAT GID. One value is used for all members of each WAN Group. Only used when
VCAT.TCR1.TGIDM = 1.
Bit 12: Receive VCAT and Data Path Enable for VCG 4 (RVEN4) Data path reset and enable. This bit function is
not available in device revision A1 (GL.IDR.REVn=000).
0 = VCAT Block is disabled and held in reset; data path is disabled for receive WAN Group #4
1 = VCAT Block is enabled; data path is enabled for receive WAN Group #4
Note: This bit must be set to enable the data path, even when operating in Non-VCG modes
Bit 11: Receive GID Bit Convention (RGIDBC) Controls all 4 VCGs. This bit is only used when TGIDM = 1
0 = bit 15 of the RGIDx register is received first.
1 = bit 0 of RGIDx register is received first.
Bit 10: Receive VCAT and Data Path Enable for VCG 3 (RVEN3) Data path Reset disable. This bit function is not
available in device revision A1 (GL.IDR.REVn=000).
0 = VCAT Block is disabled and held in reset; data path is disabled for receive WAN Group #3
1 = VCAT Block is enabled; data path is enabled for receive WAN Group #3
Note: This bit must be set to enable the data path, even when operating in Non-VCG modes
Bit 9: Receive VCAT and Data Path Enable for VCG 2 (RVEN2) Data path Reset disable. This bit function is not
available in device revision A1 (GL.IDR.REVn=000).
0 = VCAT Block is disabled and held in reset; data path is disabled for receive WAN Group #2
1 = VCAT Block is enabled; data path is enabled for receive WAN Group #2
Note: This bit must be set to enable the data path, even when operating in Non-VCG modes
Bit 8: Receive VCAT and Data Path Enable for VCG 1 (RVEN1) Data path Reset disable. This bit function is not
available in device revision A1 (GL.IDR.REVn=000).
0 = VCAT Block is disabled and held in reset; data path is disabled for receive WAN Group #1
1 = VCAT Block is enabled; data path is enabled for receive WAN Group #1
Note: This bit must be set to enable the data path, even when operating in Non-VCG modes
Bit 5: Sequence Value Integration Disable (SVINTD) Integration of sequence values applies to non-LCAS
operation only.
0 = Sequence value integrated is enabled.
1 = Sequence value integration is disabled.
Bit 0: Receive VCAT Block Enable (RVBLKEN) Data path Reset disable.
0 = VCAT Block is disabled; data path is disabled
1 = VCAT Block is enabled; data path is enabled
Note: This bit must be set even in Non-VCG modes
Bits 0-3: Manual Re-alignment of VCAT Members for VCGn (REALIGN[4:1]) A 0-to-1 transition of
this bit causes the Re-alignment state machine for VCGn to restart.
Bits 12-15: Receive VCG4 Member Count (RV4MC[3:0]) These bits indicate to the device the number of
members assigned to VCG4.
0000 = 1 Member
0001 = 2 Members
0010 = 3 members
…..
1111 = 16 members
Note: This count represents all members of a VCG, active or not.
Bits 8-11: Receive VCG3 Member Count (RV3MC[3:0]) These bits indicate to the device the number of members
assigned to VCG3.
0000 = 1 Member
0001 = 2 Members
0010 = 3 members
…..
1111 = 16 members
Note: This count represents all members of a VCG, active or not.
Bits 4-7: Receive VCG2 Member Count (RV2MC[3:0]) These bits indicate to the device the number of members
assigned to VCG2.
0000 = 1 Member
0001 = 2 Members
0010 = 3 members
…..
1111 = 16 members
Note: This count represents all members of a VCG, active or not.
Bits 0-3: Receive VCG1 Member Count (RV1MC[3:0]) These bits indicate to the device the number of members
assigned to VCG1.
0000 = 1 Member
0001 = 2 Members
0010 = 3 members
…..
1111 = 16 members
Note: This count represents all members of a VCG, active or not.
Bits 0-15: VCAT Port Interrupt Status (PISR[16:1]) This bit is set when the corresponding serial port’s Receive
Serial Status Latched Register (VCAT.RSLSR[1-16]) has one or more bits set and its corresponding Interrupt
Enable bit is also set.
Bits 8-11: MST Change on VCGn (VMSTC[4:1] This bit is set when any of the 16 MST bits associated with VCGn
have changed value.
Bits 4-7: Differential Delay Exceeded on VCGn This bit is set when the delay between members of the
corresponding VCG has exceeded the tolerance. When set, WAN traffic from the VCG will not be forwarded to the
LAN port.
Bits 0-3: Receive Re-Alignment of VCGn (REALIGNL[4:1]) This bit is set when the corresponding realignment
state machine completes successfully.
Bit 11: VCG4 MSTC Change Interrupt Enable (VMSTCIE4) This bit enables an interrupt if VMSTC4 is set.
Bit 10: VCG3 MSTC Change Interrupt Enable (VMSTCIE3) This bit enables an interrupt if VMSTC3 is set.
Bit 9: VCG2 MSTC Change Interrupt Enable (VMSTCIE2) This bit enables an interrupt if VMSTC2 is set.
Bit 8: VCG1 MSTC Change Interrupt Enable (VMSTCIE1) This bit enables an interrupt if VMSTC1 is set.
Bit 7: VCG4 Differential Delay Exceeded Interrupt Enable (DDEIE4). This bit enables an interrupt for DDE4.
Bit 6: VCG3 Differential Delay Exceeded Interrupt Enable (DDEIE3). This bit enables an interrupt for DDE3.
Bit 5: VCG2 Differential Delay Exceeded Interrupt Enable (DDEIE2). This bit enables an interrupt for DDE2.
Bit 4: VCG1 Differential Delay Exceeded Interrupt Enable (DDEIE1). This bit enables an interrupt for DDE1.
Bits 0-3: Receive Re-Alignment of VCGn Interrupt Enable (REALIGNIE[4:1]) This bit enables an interrupt
if the corresponding REALIGNLn bit is set.
0 = interrupt disabled
1 = interrupt enabled
Bit 7: Remove and Reframe (RFM) A zero-to-one transition of this bit forces the associated line into the
“removed” state, which is held as long as the bit remains a 1. A one-to-zero transition on this bit causes the
associated receive port to reframe on the VCAT overhead.
Note: Only a single WAN port may be assigned to a WAN Group in which VCAT is disabled.
Bits 12-15: Port n Receive Sequence (RVSQ[3:0]) These bits are updated every VCAT Frame on SOF
boundaries. These bits report the previous frame’s Sequence value. (LCAS only)
Bits 8-11: Port n Control Word (CTRL[3:0]) These bits are updated every VCAT Frame on SOF boundaries.
These bits report the previous frame’s Control Word. (LCAS only)
Bit 0: Loss of Multiframe Sync (LOM) – This bit corresponds to the Receive VCAT Framer status of the WAN
port.
0 = No LOM for port n
1 = LOM active for port n
Bit 3: CRC Error (CRCE) This status bit is set if there was a CRC error in the previous VCAT frame. (LCAS only)
Bit 2: GID Alarm (GID) This status bit is set if the GID of port n does not match the VCG’s GID value.
Bit 1: Severely Errored Multiframe (SEMF) This status bit is set if there were 4 or more MFI errors in the previous
multiframe. Updated on Multiframe boundaries.
Bit 0: Errored Multiframe (EMF) This status bit is set if there was at least one MFI error in the previous
multiframe. Updated on Multiframe boundaries.
Bit 4: RS-ACK Change Latched (RSACKL) Set when the corresponding RSACK status bit changes state.
Bit 3: SQ Change Latched (SQL) Set when the SQ[3:0] status bits change.
Bit 2: CTRL Code Change Latched (CTRLL) Set when the CTRL[3:0] status bits change.
Bit 0: Loss of Multiframe Sync Change Latched (LOML) Set when the corresponding LOM bit changes from an
inactive (0) to an active (1) state. The user should poll LOM to determine when the LOM condition is cleared.
Bit 4: RSACK Change Interrupt Enable (RSACKIE) This bit enables an interrupt if the RSACKL bit is set.
0 = Interrupt for port n is Masked
1 = Interrupt for port n is Enabled
Bit 3: SQ Change Interrupt Enable (SQIE) This bit enables an interrupt if the SQL bit is set.
0 = Interrupt for port n is Masked
1 = Interrupt for port n is Enabled
Bit 2: CTRL Change Interrupt Enable (CTRIE) This bit enables an interrupt if the CTRLL bit is set.
0 = Interrupt for port n is Masked
1 = Interrupt for port n is Enabled
Bit 0: Loss of Multiframe Sync Change Interrupt Enable (LOMIE[16:1]) This bit enables an interrupt if the
LOML bit is set.
0 = Interrupt for port n is Masked
1 = Interrupt for port n is Enabled
Bits 0 -15: Receive GID (RGID[15:0]) These bits provide the received 16-bit GID value for each of the 16 WAN
Lines. Latches the first bit when MFI2 = XXXX_0000. Bit order is reversed if RGIDBC=1.
Serial Interface Transmit Registers are used to control the transmitter associated with each Serial Interface. The
register map is shown in the following Table. Note that throughout this document the HDLC Processor is also
referred to as a “packet processor”.
Bits 0-15: Line Loopback Enable (LLB[15:0]) Data received on RDATAn will be looped to the Transmit
Serial Port, replacing the data on TDATAn. (Note: TCLKn must be the same clock as RCLKn).
0 = Line Loopback is Disabled
1 = Line Loopback is Enabled
Bits 0-15: Terminal Loopback Enable(TLB[16:1]). Data transmitted on TDATAn will be internally looped to the
Receive Serial Port and data on RDATAn will be ignored and TCLKn will replace RCLKn.
0 = Terminal Loopback is Disabled
1 = Terminal Loopback is Enabled
Note: This real-time status bit reports whether TMCLK4 has transitioned since the last
read of this register.
Note: This real-time status bit reports whether TMCLK4 has transitioned since the last
read of this register.
Note: This real-time status bit reports whether TMCLKm/TCLKn has transitioned since the last
read of this register.
Note: This real-time status bit reports whether TVCLKA1 has transitioned since the last read of this register.
Note: This real-time status bit reports whether RCLKn has transitioned since the last read of this register.
Bits 1-2: TSYNC Setup (TS_SETUP[1:0]). These two bits accommodate a TSYNC signal that arrives earlier
than the start of frame.
* Note: For serial ports 9-16, the TD_SEL bit is not available. Ports 9-16 must use TMCLKn and TMSYNCn.
Bits 3-7: Transmit Voice Octets Per Frame (TVOPF[4:0]). Controls the number of octets that are used for voice
traffic per frame. Note: Max. number of octets allowed to be used for voice is 16.
00001 = 1st byte after Frame sync is a voice channel.
00010 = 1st two bytes after Frame sync are voice channels
Bit 2: TSYNC Control (TSYNCC) This setting is necessary only if voice ports are enabled. TVSYNC MUST be a
frame sync.
0 = TSYNC is a frame sync. Voice bytes output to TDATA from Voice FIFO after every TSYNC.
1 = TSYNC is a multiframe sync. Voice output to TDATA from Voice FIFO based on PC bit.
Bit 1: Port Configuration (PC) Used to divide down multiframe sync to frame sync.
0 = Port is configured for T1.
1 = Port is configured for E1.
Bit 1: Transmit Voice FIFO Underflow (TVFU) This bit is set during a Transmit Voice FIFO underflow. An
underflow condition results in a loss of data. This bit remains set as long as the underflow condition exists.
Bit 0: Transmit Voice FIFO Overflow (TVFO) – This bit is set during a Transmit Voice FIFO overflow. An overflow
condition results in a loss of data. This bit remains set as long as the overflow condition exists.
Bit 1: Transmit Voice FIFO Underflow Latched (TVFUL) This bit is set when a Transmit Voice FIFO underflow
condition occurs. An underflow condition results in a loss of data. This bit remains set as long as the underflow
condition exists.
Bit 0: Transmit Voice FIFO Overflow Latched (TVFOL) This bit is set when a Transmit Voice FIFO overflow
condition occurs. An overflow condition results in a loss of data. This bit remains set as long as the overflow
condition exists.
Bit 1: Transmit Voice FIFO Underflow Interrupt Enable (TVFULIE) This bit enables an interrupt if the TVFUL bit
is set.
0 = interrupt disabled
1 = interrupt enabled
Bit 0: Transmit Voice FIFO Overflow Interrupt Enable (TVFOLIE) – This bit enables an interrupt if the TVFOL bit
is set .
0 = interrupt disabled
1 = interrupt enabled
Bits 3-7: Receive Voice Octets Per Frame (RVOPF[4:0]). Controls the number of octets that are used for voice
traffic per frame. Note: Max. number of octets allowed to be used for voice is 16.
00001 = 1st byte after Frame sync is a voice channel.
00010 = 1st two bytes after Frame sync are voice channels…
Bit 2: RSYNC Control (RSYNCC). This setting is necessary only if voice ports are enabled. RVSYNC MUST be a
frame sync.
0 = RSYNC is a frame sync. Voice bytes inserted into Voice FIFO after every RSYNC.
1 = RSYNC is a multiframe sync. Voice bytes inserted into Voice FIFO based on PC register bit.
Bit 1: Port Configuration (PC). Used to divide down multiframe sync to frame sync.
0 = Port is configured for T1.
1 = Port is configured for E1.
The control registers related to the control of the individual MACs are shown in the following Table. The device
keeps statistics for the packet traffic sent and received. Note that the addresses listed are the indirect addresses
that must be provided to SU.MAC1RADH/SU.MAC1RADL or SU.MAC1AWH/SU.MAC1AWL.
Bit 23: Watchdog Disable (WDD) - When set to 1, the watchdog timer on the receiver is disabled. When equal to
0, the MAC allows only 2048 bytes of data per frame.
Bit 22: Jabber Disable (JD) - When set to 1, the transmitter’s jabber timer is disabled. When equal to 0, the MAC
allows only 2048 bytes to be transmitter per frame.
Bit 21: Frame Burst Enable (FBE) – When set to 1, the MAC allows frame bursting during transmission in half-
duplex mode.
Bit 20: Jumbo Frame Enable (JFE) - When set to 1, the MAC allows the reception of frames up to 9018 bytes in
length without reporting a giant frame error in the receive frame status register. Frames between 9018 and 10240
bytes in length are passed with a giant frame error indication. Jabber Disable and Watchdog Disable bits should be
set to 1 to transmit and receive jumbo frames. This bit should be cleared when operating in full-duplex mode.
Bit 14: Endian Mode (EM) - When set to 1, the MAC operates in Big-Endian Mode. When equal to 0, the MAC
operates in Little-Endian Mode. The Endian mode selection is applicable only for the transmit and receive data
paths.
Bit 13: Disable Receive Own (DRO) - When set to 1, the MAC disables the reception of frames while TX_EN is
asserted. When this bit equals zero, transmitted frames are also received by the MAC. This bit should be cleared
when operating in full-duplex mode.
Bit 12: Loopback Mode (LM) - When set to 1, all frames destined for the transmit GMII/MII/RMII interface are
internally transferred to the receive GMII/MII/RMII. Frames received on the GMII/MII/RMII are not transferred to the
transmit GMII/MII/RMII interface. Note that there is no SA/DA swapping performed. If SA/DA swapping of LAN
traffic is required, the LAN extract/insertion functions must be used.
Bit 11: Duplex Mode (DM) - When set to 1, the MAC transmits and receives simultaneously (full-duplex).
Bit 9: Disable Retry (DRTY) - When set to 1, the MAC makes only a single attempt to transmit each frame. If a
collision occurs, the MAC ignores the current frame, reports a Frame Abort, reports an excessive collision error,
and proceeds to the next frame. When this bit equals 0, the MAC will retry collided frames based on the settings in
the Backoff Limit bits before signaling a retry error. This bit is applicable to half-duplex mode only.
Bit 8: Automatic Pad Stripping (APST) - When set to 1, all incoming frames with less than 46 byte length are
automatically stripped of the pad characters and FCS. When equal to zero, all frames are received unmodified.
Bit 7: Automatic CRC Stripping (ACST) - When set to 1, the MAC will strip the FCS field on incoming frames only
if the length field is less than or equal to 1500 bytes. All received frames with length field greater than 1500 bytes
will be passed to the receiver without stripping of the FCS field. When equal to zero, all frames are received
unmodified. For most applications of this device, this bit should equal 0.
Bits 5 - 6: Back-Off Limit (BOLMT[1:0])- These two bits allow the user to set the back-off limit used for the
maximum retransmission delay for collided frames. Default operation limits the maximum delay for retransmission
to a countdown of 10 bits from a random number generator. The user can reduce the maximum number of counter
bits as described in the table below. See IEEE 802.3 for details of the back-off algorithm.
Bit 4: Deferral Check (DC) - When set to 1, the MAC will abort frame transmission if it has deferred for more than
24,288 bit times. The deferral counter starts when the transmitter is ready to transmit a frame, but is prevented
from transmission because RX_CRS is active. If the MAC begins transmission but a collision occurs after the
beginning of transmission, the deferral counter is reset again. If this bit is equal to zero, then the MAC will defer
indefinitely.
Bit 3: Transmitter Enable (TE) - When set to 1, frame transmission is enabled. When equal to zero, transmission
is disabled.
Bit 2: Receiver Enable (RE) - When set to 1, frame reception is enabled. When equal to zero, frames are not
received.
Bit 31: Receive All Frames (RAF) - When set to 1, the receiver forwards all frames to the device, even if they do
not pass the destination address filter. When equal to zero, the receiver only forwards those frames that pass the
destination address filter.
Bit 7: Pass Pause Control Frames (PCF) - When set to 1, the receiver forwards all special multicast PAUSE
control frames to the device. The MAC also decodes the PAUSE control frame and disables the transmitter for the
specified amount of time. When equal to zero, the MAC decodes the PAUSE control frame and disables the
transmitter for the specified amount of time, but does not forward the PAUSE frame to the device.
Bit 5: Disable Broadcast Frames (DBF) - When set to 1, the MAC filters all incoming Broadcast frames. When
equal to zero, all broadcast frames are forwarded to the device.
st
Bit 4: Pass All Multicast (PAM) - When set to 1, all received multicast frames (1 bit of DA = “1”) are forwarded,
irrespective of the settings of the Hash filter and Inverse Filtering bits.
Bit 3: Inverse Filtering (INVF) - When set to 1, the programmable DA filter operates in inverse filtering mode. The
result of the filtering operations by the Hash HFUF/HFMF bits is inverted. When equal to zero, filtering is
determined by the HFUF/HFMF bits.
Bit 2: Hash Mode for Unicast Frames (HFUF) - When set to 1, address filtering operates in the imperfect (hash)
address filtering mode for unicast frames, according to the hash table. When equal to zero, perfect address filtering
is performed on unicast frames using the addresses specified in the MAC address filter registers.
Bit 1: Hash Mode for Multicast Frames (HFMF) - When set to 1, address filtering operates in the imperfect (hash)
address filtering mode for multicast frames, according to the hash table. When this bit equals zero, perfect address
filtering is performed on multicast frames using the addresses specified in the MAC address filter registers.
Bit 0: Promiscuous Mode (PM) – When set to 1, all non-control frames are allowed to pass, including broadcast
frames, regardless of destination address.
Bits 0-31: Hash Table High (HTH[31:0]) - Contains the upper 32 bits of the Hash table used for group address
filtering.
Bits 0-31: Hash Table Low (HTL[31:0]) - Contains the upper 32 bits of the Hash table used for group address
filtering.
Bits 10-15: PHY Physical Layer Address (PPA[4:0]) - Contains the address of the PHY to be accessed.
Bits 6-9: PHY MDIO Register (GM[4:0]) - Contains the address of register within the PHY to be accessed.
Bit 1: PHY MDIO Write (GW) - When set to 1, a write operation will be performed. When equal to zero, a read
operation will be performed.
Bit 0: PHY GMII Busy (GB) - This bit should be set to 1 when writing to SU.GMIIA. The MAC will clear the bit
when it is no longer busy. Do not write to GMIIA or GMIID while this bit is still set to 1. During read operations,
the data in SU.GMIID is invalid until this bit is equal to 0.
Bits 0-15: MDIO Data (GD[15:0]) - Contains the 16-bit value read from the PHY after a management read
operation, or the 16-bit value to be written during a write operation.
Bits 16-31: Pause Time (PT[15:0]) - Contains the 16-bit value to be used in the time field in transmitted PAUSE
control frames.
Bit 4: Pause Low Threshold (PLT) - Set to 1 for 1000Mbps operation. Should equal 0 for 10/100Mbps operation.
Notes: “slots” are defined by the IEEE as the amount of time that it takes to transmit 64 bytes for 10/100Mbps and 512
bytes for 1000Mbps. Only the 10/100Mbps applications are applicable for the Port 2 MAC.
Bit 3: Unicast Pause Frame Detect (UP) - When set to 1, the MAC will detect Pause control frames with the
device’s unicast address, in addition to detecting Pause control frames with a multicast address. When equal to
zero, the MAC will only detect Pause control frames with the unique multicast address as specified in the 802.3x
standard.
Bit 2: Receive Flow Control Enable (RFE) - When set to 1, the MAC will receive Pause control frames and
disable the transmitter for the specified pause time. When this bit is equal to zero, the device will not respond to
Pause control frames.
Bit 1: Transmit Flow Control Enable (TFE) - When operating in Full-Duplex mode, if this bit is set, the MAC will
transmit Pause control frames as needed. When equal to zero, the MAC will not transmit Pause control frames.
Bit 0: Flow Control Busy (FCB) - This bit is equal to 1 when the transmission of a Pause control frame is in
progress. If the user writes a “1” to this bit, the device will transmit one Pause control frame.
Bits 0-15: VLAN Tag ID (VLTID[15:0]) - Potentially not needed. Duplicated in other areas.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bit 31: MAC Address Filter 0 Enable (MADDR0AE) - Must be set to 1 if address filtering is enabled.
Bits 0-15: MAC Address Filter 0 (MADDR0[47:32]) - Highest two bytes of MAC Filter Address 0.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-31: MAC Address Filter 0 (MADDR0[31:0]) - Lowest four bytes of MAC Filter Address 0.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-15: MAC Address Filter 1 (MADDR1[47:32]) - Highest two bytes of MAC Filter Address 1.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-31: MAC Address Filter 1 (MADDR1[31:0]) - Lowest four bytes of MAC Filter Address 1.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-15: MAC Address Filter 2 (MADDR2[47:32]) - Highest two bytes of MAC Filter Address 2.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-31: MAC Address Filter 2 (MADDR2[31:0]) - Lowest four bytes of MAC Filter Address 2.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-15: MAC Address Filter 3 (MADDR3[47:32]) - Highest two bytes of MAC Filter Address 3.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-31: MAC Address Filter 3 (MADDR3[31:0]) - Lowest four bytes of MAC Filter Address 3.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-15: MAC Address Filter 4 (MADDR4[47:32]) - Highest two bytes of MAC Filter Address 4.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-31: MAC Address Filter 4 (MADDR4[31:0]) - Lowest four bytes of MAC Filter Address 4.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-15: MAC Address Filter 5 (MADDR5[47:32]) - Highest two bytes of MAC Filter Address 5.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-31: MAC Address Filter 5 (MADDR5[31:0]) - Lowest four bytes of MAC Filter Address 5.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-15: MAC Address Filter 6 (MADDR6[47:32]) - Highest two bytes of MAC Filter Address 6.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-31: MAC Address Filter 6 (MADDR6[31:0]) - Lowest four bytes of MAC Filter Address 6.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-15: MAC Address Filter 7 (MADDR7[47:32]) - Highest two bytes of MAC Filter Address 7.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-31: MAC Address Filter 7 (MADDR7[31:0]) - Lowest four bytes of MAC Filter Address 7.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-15: MAC Address Filter 8 (MADDR8[47:32]) - Highest two bytes of MAC Filter Address 8.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-31: MAC Address Filter 8 (MADDR8[31:0]) - Lowest four bytes of MAC Filter Address 8.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-15: MAC Address Filter 9 (MADDR9[47:32]) - Highest two bytes of MAC Filter Address 9.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-31: MAC Address Filter 9 (MADDR9[31:0]) - Lowest four bytes of MAC Filter Address 9.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-15: MAC Address Filter 10 (MADDR10[47:32]) - Highest two bytes of MAC Filter Address 10.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-31: MAC Address Filter 10 (MADDR10[31:0]) - Lowest four bytes of MAC Filter Address 10.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-15: MAC Address Filter 11 (MADDR11[47:32]) - Highest two bytes of MAC Filter Address 11.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-31: MAC Address Filter 11 (MADDR11[31:0]) - Lowest four bytes of MAC Filter Address 11.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-15: MAC Address Filter 12 (MADDR12[47:32]) - Highest two bytes of MAC Filter Address 12.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-31: MAC Address Filter 12 (MADDR12[31:0]) - Lowest four bytes of MAC Filter Address 12.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-15: MAC Address Filter 13 (MADDR13[47:32]) - Highest two bytes of MAC Filter Address 13.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-31: MAC Address Filter 13 (MADDR13[31:0]) - Lowest four bytes of MAC Filter Address 13.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-15: MAC Address Filter 14 (MADDR14[47:32]) - Highest two bytes of MAC Filter Address 14.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-31: MAC Address Filter 14 (MADDR14[31:0]) - Lowest four bytes of MAC Filter Address 14.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-15: MAC Address Filter 15 (MADDR15[47:32]) - Highest two bytes of MAC Filter Address 15.
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Default 0 0 0 0 0 0 0 0
Bits 0-31: MAC Address Filter 15 (MADDR15[31:0]) - Lowest four bytes of MAC Filter Address 15.
This register configures and initiates auto-negotiation of the external PHY device. It also enables PHY loopback.
Bit 16: Enable Comma Detect (ECD) - When set to 1, the MAC is enabled for comma detection and word
resynchronization.
Bit 14: External Loopback Enable (ELE) - When set to 1, causes the external PHY to loopback the transmit data
to the receiver.
Bit 13: Auto-Negotiation Enable (ANE) - When set to 1, the MAC will automatically negotiate the link speed with
the remote node. When equal to zero, auto-negotiation is disabled.
Bit 9: Restart Auto-Negotiation (RAN) - When set to 1 and ANE=1, the MAC will initiate auto-negotiation. This bit
will clear itself after auto-negotiation is started. Should be equal to zero during normal operation.
Bit 8: MAC Extended Status Support (ES) - This bit is always set to 1, to indicate that the MAC supports
extended status information.
Bit 5: Auto-Negotiation Complete (ANC) - This bit is set to 1 when auto-negotiation is complete. The bit is equal
to zero after auto-negotiation is initiated, and remains zero until completion of auto-negotiation.
Bit 3: Auto-Negotiation Support (ANS) - This bit is always set to 1, to indicate that the MAC supports extended
auto-negotiation.
Bit 2: Link Status (LS) - When set to 1, this bit indicates that the Ethernet link is connected. This bit is only
updated after a read operation. In order to see the current status, the bit must be read twice.
Bit 3: MII/RMII/GMII Link Status (LINKUP) – When equal to 1, the link is communicating. When equal to zero, the
link is not operational.
Bits 1-2: Link Speed (LNKSPD[1:0]) – Indicates the current link speed.
00 = 2.5MHz
01 = 25MHz
10 = 125MHz
Bit 2: Reset on Read (ROR) – When set to 1, each management counter will reset to zero after a read access of
the least-significant byte. When equal to zero, the counters will only be reset by the CRST bit.
Bit 1: Counter Stop Rollover (CSR) – When set to 1, each counter will saturate at the maximum value and not roll
over. When equal to zero, each counter can rollover to zero after the maximum value is exceeded.
Bit 0: Counter Reset (CRST) – Set to 1 to initiate a reset of all management counters. Set to zero for normal
operation.
0 = Normal operation.
1 = Reset all management counters.
Bits 1-23: Receive Counter Half-Full Status – Each bit is set to 1 when the corresponding MAC MMC counter
reaches half of the maximum value.
Bits 1-24: Transmit Counter Half-Full Status – Each bit is set to 1 when the corresponding MAC MMC counter
reaches half of the maximum value.
Bits 1-31: Transmit Byte Counter (TXBC[31:0]) – Contains the number of bytes (octets) transmitted, exclusive of
both preamble and retried bytes, in both good and bad frames.
Bits 1-31: Transmit Frame Counter (TXFC[31:0]) – Contains the number of frames transmitted, including both
good and bad frames.
Bits 1-31: Transmit Good Broadcast Frames Counter (TXGBFC[31:0]) – Contains the number of good
broadcast frames transmitted, exclusive of both preamble and retried bytes. Does not contain bad frames.
Bits 1-31: Transmit Good Multicast Frames Counter (TXGMFC[31:0]) – Contains the number of good multicast
frames transmitted.
Bits 1-31: Transmit 0-64 Byte Frames Counter (TX0_64[31:0]) – Contains the number of frames transmitted with
sizes of 64 bytes or less. Includes both good and bad frames.
Bits 1-31: Transmit 65-127 Byte Frames Counter (TX65_127[31:0]) – Contains the number of frames
transmitted with sizes of 65 to 127 bytes. Includes both good and bad frames.
Bits 1-31: Transmit 128-255 Byte Frames Counter (TX128_255[31:0]) – Contains the number of frames
transmitted with sizes of 128 to 255 bytes. Includes both good and bad frames.
Bits 1-31: Transmit 256-511 Byte Frames Counter (TX256_511[31:0]) – Contains the number of frames
transmitted with sizes of 256 to 511 bytes. Includes both good and bad frames.
Bits 1-31: Transmit 512-1023 Byte Frames Counter (TX512_1K[31:0]) – Contains the number of frames
transmitted with sizes of 512 to 1023 bytes. Includes both good and bad frames.
Bits 1-31: Transmit 1024-MAX Byte Frames Counter (TX1K_MAX[31:0]) – Contains the number of frames
transmitted with sizes of 1024 to the maximum allowed bytes. Includes both good and bad frames.
Bits 1-31: Transmit Unicast Frames Counter (TXUCAST[31:0]) – Contains the number of frames transmitted
with a unicast address. Includes both good and bad frames.
Bits 1-31: Transmit Multicast Frames Counter (TXMFC[31:0]) – Contains the number of frames transmitted with
a multicast address. Includes both good and bad frames.
Bits 1-31: Transmit Broadcast Frames Counter (TXBFC[31:0]) – Contains the number of frames transmitted
with a broadcast address. Includes both good and bad frames.
Bits 1-31: Transmit Underflow Frames Counter (TXUFE[31:0]) – Contains the number of frames aborted due to
underflow errors.
Bits 1-31: Transmit Single Collision Frames Counter (TXSNGLCL[31:0]) – Contains the number of frames
successfully transmitted after a single collision. Applicable in half-duplex mode only.
Bits 1-31: Transmit Multiple Collision Frames Counter (TXMLTICL[31:0]) – Contains the number of frames
successfully transmitted after multiple collisions. Applicable in half-duplex mode only.
Bits 1-31: Transmit Deferred Frames Counter (TXDFRD[31:0]) – Contains the number of frames successfully
transmitted after deferral. Applicable in half-duplex mode only.
Bits 1-31: Transmit Late Collision Frames Counter (TXLTCL[31:0]) – Contains the number of frames aborted
due to late collisions. Applicable in half-duplex mode only.
Bits 1-31: Transmit Excessive Collision Counter (TXXCSVCL[31:0]) – Contains the number of frames aborted
due to excessive collisions. Applicable in half-duplex mode only.
Bits 1-31: Transmit Carrier Error Counter (TXCRERR[31:0]) – Contains the number of frames aborted due to
carrier error (no carrier or loss of carrier).
Bits 1-31: Transmit Good Byte Counter (TXGBC[31:0]) – Contains the number of transmitted bytes in good
frames, exclusive of preamble bytes.
Bits 1-31: Transmit Good Frame Counter (TXGFC[31:0]) – Contains the number of good frames transmitted.
Bits 1-31: Transmit Excessive Deferral Counter (TXXCSVDF[31:0]) – Contains the number of frames aborted
due to excessive deferral. Applicable in half-duplex mode only.
Bits 1-31: Transmit Pause Frame Counter (TXPAUSE[31:0]) – Contains the number of good Pause frames
transmitted.
Bits 1-31: Transmit VLAN Frame Counter (TXVLANF[31:0]) – Contains the number of good VLAN frames
transmitted.
Bits 1-31: Receive Frame Counter (RXFC[31:0]) – Contains the number of frames received, both good and bad
frames included.
Bits 1-31: Receive Byte Counter (RXBC[31:0]) – Contains the number of good and bad bytes received, exclusive
of preamble bytes.
Bits 1-31: Receive Good Byte Counter (RXGBC[31:0]) – Contains the number of bytes received in good frames,
exclusive of preamble bytes.
Bits 1-31: Receive Good Broadcast Frame Counter (RXGBFC[31:0]) – Contains the number of good broadcast
frames received.
Bits 1-31: Receive Good Multicast Frame Counter (RXMFC[31:0]) – Contains the number of good Multicast
frames received.
Bits 1-31: Receive CRC Error Counter (RXCRC[31:0]) – Contains the number of frames received with CRC
errors.
Bits 1-31: Receive Alignment Error Counter (RXALGN[31:0]) – Contains the number of frames received with
alignment (dribble) errors.
Bits 1-31: Receive Runt Error Counter (RXRUNT[31:0]) – Contains the number of runt frames received.
Bits 1-31: Receive Jabber Error Counter (RXJBBR[31:0]) – Contains the number of frames received with length
greater 1518 (including the CRC) and with CRC errors.
Bits 1-31: Receive Undersize Frame Counter (RXUNDRSZ[31:0]) – Contains the number of frames received
with a size less than 64 bytes and a good CRC.
Bits 1-31: Receive Oversize Frame Counter (RXOVRSZ[31:0]) – Contains the number of frames received with
length greater than the maximum size with a valid CRC.
Bits 1-31: Receive 0-64 Byte Frames Counter (RX0_64[31:0]) – Contains the number of frames received with
sizes of 64 bytes or less. Includes both good and bad frames.
Bits 1-31: Receive 65-127 Byte Frames Counter (RX65_127[31:0]) – Contains the number of frames received
with sizes of 65 to 127 bytes. Includes both good and bad frames.
Bits 1-31: Receive 128-255 Byte Frames Counter (RX128_255[31:0]) – Contains the number of frames received
with sizes of 128 to 255 bytes. Includes both good and bad frames.
Bits 1-31: Receive 256-511 Byte Frames Counter (RX256_511[31:0]) – Contains the number of frames received
with sizes of 256 to 511 bytes. Includes both good and bad frames.
Bits 1-31: Receive 512-1023 Byte Frames Counter (RX512_1K[31:0]) – Contains the number of frames received
with sizes of 512 to 1023 bytes. Includes both good and bad frames.
Bits 1-31: Receive 1024-MAX Byte Frames Counter (RX1K_MAX[31:0]) – Contains the number of frames
received with sizes of 1024 to the maximum bytes. Includes both good and bad frames.
Bits 1-31: Receive Unicast Frame Counter (RXUFC[31:0]) – Contains the number of good unicast frames
received.
Bits 1-31: Receive Length Error Counter (RXLNERR[31:0]) – Contains the number of frames received with
length errors.
Bits 1-31: Receive Out of Range Counter (RXRANGE[31:0]) – Contains the number of frames received with an
invalid Ethernet Length/Type field.
Bits 1-31: Receive Pause Frame Counter (RXPAUSE[31:0]) – Contains the number of good Pause frames
received.
Bits 1-31: Receive Overflow Counter (RXOVFL[31:0]) – Contains the number of frames discarded due to a
receive FIFO overflow.
Bits 1-31: Receive VLAN Frame Counter (RXVLAN[31:0]) – Contains the number of good and bad VLAN frames
received.
Bits 1-31: Receive Watchdog Error Counter (RXWDOG[31:0]) – Contains the number of frames discarded due
to a receive watchdog timer error.
Note – the SU.RXWDOG register may be unnecessary and thus may be removed.
Bit 20: Flush Transmit FIFO (FTF) When this bit is written to 1, the MAC transmit FIFO is reset and cleared. This
bit automatically resets to zero when the reset operation is complete. Transmission should be disabled during the
flush transmit FIFO operation. Typically, the user will want to flush the transmit FIFO prior to enabling transmission
to avoid transmitting possible frame fragments that may be in the FIFO.
When SPI_CPHA = 0, CS may be de-asserted between accesses. An access is defined as one or two control
bytes followed by a data byte. CS cannot be de-asserted between the control bytes, or between the last control
byte and the data byte. When SPI_CPHA = 0, CS may also remain asserted between accesses. If it remains
asserted and the BURST bit is set, no additional control bytes are expected after the first control byte(s) and data
are transferred. If the BURST bit is set, the address will be incremented for each additional byte of data transferred
until CS is de-asserted. If CS remains asserted and the BURST bit is not set, a control byte(s) is expected following
the data byte, and the address for the next access will be received from that. Anytime CS is de-asserted, the
BURST access is terminated.
When SPI_CPHA = 1, CS may remain asserted for more than one access without being toggled high and then low
again between accesses. If the BURST bit is set, the address should increment and no additional control bytes are
expected. If the BURST bit is not set, each data byte will be followed by the control byte(s) for the next access.
Additionally, CS may also be de-asserted between accesses when SPI_CPHA =1. In the case, any BURST access
is terminated, and the next byte received when CS is re-asserted will be a control byte.
The following diagrams describe the functionality of the SPI port for the four combinations of SPI_CPOL and
SPI_CPHA. They indicate the clock edge that samples the data and the level of the clock during no-transfer events
(high or low). Since the SPI port acts as a slave device, the master device provides the clock. The user must
configure the SPI_CPOL and SPI_CPHA pins to describe which type of clock that the master device is providing.
Note that due to the address space of the device, the unused bits A13, A12, and A11 should always be zero.
Figure 11-1. SPI Serial Port Access For Read Mode, SPI_CPOL=0, SPI_CPHA = 0
SCK
SPI_CLK
CS*
CS
SPI_MOSI
MOSI 1 A13 A12 A11 A10 A9 A8 A7 A6 A5 A4 A3 A2 A1 A0 B
MSB LSB MSB LSB
SPI_MISO
MISO D7 D6 D5 D4 D3 D2 D1 D0
MSB LSB
Figure 11-2. SPI Serial Port Access For Read Mode, SPI_CPOL = 1, SPI_CPHA = 0
SCK
SPI_CLK
CS*
CS
SPI_MOSI
MOSI 1 A13 A12 A11 A10 A9 A8 A7 A6 A5 A4 A3 A2 A1 A0 B
MSB LSB MSB LSB
SPI_MISO
MISO D7 D6 D5 D4 D3 D2 D1 D0
MSB LSB
Figure 11-3. SPI Serial Port Access For Read Mode, SPI_CPOL = 0, SPI_CPHA = 1
SCK
SPI_CLK
CS*
CS
SPI_MOSI
MOSI 1 A13 A12 A11 A10 A9 A8 A7 A6 A5 A4 A3 A2 A1 A0 B
MSB LSB MSB LSB
SPI_MISO
MISO D7 D6 D5 D4 D3 D2 D1 D0
MSB LSB
Figure 11-4. SPI Serial Port Access For Read Mode, SPI_CPOL = 1, SPI_CPHA = 1
SCK
SPI_CLK
CS
CS*
SPI_MOSI
MOSI 1 A13 A12 A11 A10 A9 A8 A7 A6 A5 A4 A3 A2 A1 A0 B
MSB LSB MSB LSB
SPI_MISO
MISO D7 D6 D5 D4 D3 D2 D1 D0
MSB LSB
Figure 11-5. SPI Serial Port Access For Write Mode, SPI_CPOL = 0, SPI_CPHA = 0
SCK
SPI_CLK
CS*
CS
SPI_MOSI
MOSI 0 A13 A12 A11 A10 A9 A8 A7 A6 A5 A4 A3 A2 A1 A0 B D7 D6 D5 D4 D3 D2 D1 D0
Figure 11-6. SPI Serial Port Access For Write Mode, SPI_CPOL = 1, SPI_CPHA = 0
SPI_CLK
SCK
CS
CS*
SPI_MOSI
MOSI 0 A13 A12 A11 A10 A9 A8 A7 A6 A5 A4 A3 A2 A1 A0 B D7 D6 D5 D4 D3 D2 D1 D0
Figure 11-7. SPI Serial Port Access For Write Mode, SPI_CPOL = 0, SPI_CPHA = 1
SCK
SPI_CLK
CS*
CS
SPI_MOSI
MOSI 0 A13 A12 A11 A10 A9 A8 A7 A6 A5 A4 A3 A2 A1 A0 B D7 D6 D5 D4 D3 D2 D1 D0
Figure 11-8. SPI Serial Port Access For Write Mode, SPI_CPOL = 1, SPI_CPHA = 1
SCK
SPI_CLK
CS*
CS
SPI_MOSI
MOSI 0 A13 A12 A11 A10 A9 A8 A7 A6 A5 A4 A3 A2 A1 A0 B D7 D6 D5 D4 D3 D2 D1 D0
TCLK
TSYNC
TDATA MSB Encapsulated Ethernet Data MSB Encapsulated Ethernet Data MSB Encapsulated Ethernet Data
TCLK
TSYNC
TDATA MSB VCAT OH MSB Encapsulated Ethernet Data MSB Encapsulated Ethernet Data
TCLK
TSYNC
TDATA LSB..... MSB Encapsulated Ethernet Data MSB Encapsulated Ethernet Data MSB Encapsulated Ethernet
The figure below demonstrates the TSYNC pulse configured to arrive 2 clock cycles before the byte boundary
through the use of the LI.TCR register.
Figure 11-12. Transmit Serial Port Interface with VCAT, early TSYNC (2 cycles)
TCLK
TSYNC
TDATA MSB VCAT OH MSB Encapsulated Ethernet Data MSB Encapsulated Ethernet
Figure 11-13 shows the basic functional timing relationship for the receive serial port interface. RCLK may be
gapped during Framing Overhead positions or to support Fractional T1/E1/T3/E3, as shown in Figure 11-15. The
RSYNC signal must be provided to the device as a frame, multiframe, or byte boundary indication. VCAT
applications require a multiframe boundary. The expected position of the RSYNC pulse is not programmable, and
must be provided as indicated. Note that the first clock after the RSYNC will sample the LSB of the last byte of the
previous frame.
Figure 11-13. Receive Serial Port Interface, without VCAT, rising edge sampling
RCLK
RSYNC
RDATA LSB MSB Encapsulated Ethernet Data MSB Encapsulated Ethernet Data MSB Encapsulated Ethernet Data
Figure 11-14. Receive Serial Port Interface with VCAT, rising edge sampling
RCLK
RSYNC
RDATA LSB MSB VCAT OH MSB Encapsulated Ethernet Data MSB Encapsulated Ethernet Data
Figure 11-15. Receive Serial Port Interface with Gapped Clock (T1)
RCLK
RSYNC
RDATA LSB Fbit MSB Encapsulated Ethernet Data MSB Encapsulated Ethernet Data MSB Encapsulated Ethernet
TCLK(I)
TSYNC(I)
TDATA(O) LSB MSB PCM OCTET 1(prev frame) PCM OCTET 2 ETHERNET DATA 1
TVCLK(I)
TVSYNC(I)
TVDEN(I)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
Figure 11-17 shows the receive serial port timing relationship when the data stream contains PCM octets. This
example shows two PCM octets being demuxed from the Ethernet data. RVSYNC is minimum one clock period
wide, but may be high multiple clock periods. Note that the PCM octets output on RVDATA are buffered for one
RVSYNC period, i.e. the PCM octets are delayed one frame. Voice data may be output at any point between frame
syncs, output when RVDEN is low.
RCLK(I)
RSYNC(I)
RDATA(I) LSB MSB PCM OCTET 1 PCM OCTET 2 ETHERNET DATA 1
RVCLK(I)
RVSYNC(I)
RVDEN(I)
RVDATA(O) PCM OCTET 1(prev frame) PCM OCTET 2
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
REF_CLK
TXD[1:0
P R E A M B L E F C S
]
TX_E
N
GMII Receive data on RXD[1:0] is expected to be synchronous with the rising edge of ______. The data is only
valid if RX_CRS is high. The external PHY asynchronously drives RX_CRS low during carrier loss.
Figure 11-19. GMII Receive Interface Functional Timing
REF_CLK
RXD[1:0] P R E A M B L E F C S
RX_CRS
Each MII Interface Transmit Port has its own TX_CLK and data interface. The data TXD [3:0] operates
synchronously with TX_CLK. The LSB is presented first. TX_CLK should be 2.5MHz for 10Mbps operation and
25MHz for 100Mbps operation. TX_EN is valid at the same time as the first byte of the preamble. In DTE Mode
TX_CLK is input from the external PHY. In DCE Mode, the device provides TX_CLK, derived from an external
reference (SYSCLKI).
In Half-Duplex (DTE) Mode, the device supports RX_CRS and COL signals. RX_CRS is active when the PHY
detects transmit or receive activity. If there is a collision as indicated by the COL input, the device will replace the
data nibbles with jam nibbles. After a “random“ time interval, the frame is retransmitted. The MAC will try to send
the frame a maximum of 16 times. The jam sequence consists of 55555555h. Note that the COL signal and
RX_CRS can be asynchronous to the TX_CLK and are only valid in half duplex mode.
TX_CLK
TXD[3:0] P R E A E M B L E F C S
TX_EN
Figure 11-21. MII Transmit Half Duplex with a Collision Functional Timing
TX_CLK
TXD[3:0] P R E A M B L E J J J J J J J J
TX_EN
RX_CRS
COL
Receive Data (RXD[3:0]) is clocked from the external PHY synchronously with RX_CLK. The RX_CLK signal is
2.5MHz for 10Mbps operation and 25MHz for 100Mbps operation. RX_DV is asserted by the PHY from the first
Nibble of the preamble in 100Mbps operation or first nibble of SFD for 10Mbps operation. The data on RXD[3:0] is
not accepted by the MAC if RX_DV is low or RX_ERR is high (in DTE mode). RX_ERR should be tied low when in
DCE Mode.
RX_CLK
RXD[3:0] P R E A E M B L E F C S
RX_CRS
In RMII Mode, TX_EN is high with the first bit of the preamble. The TXD[1:0] is synchronous with the 50MHz
REF_CLK. For 10Mbps operation, the data bit outputs are updated every 10 clocks.
REF_CLK
TXD[1:0] P R E A M B L E F C S
TX_EN
RMII Receive data on RXD[1:0] is expected to be synchronous with the rising edge of the 50MHz REF_CLK. The
data is only valid if RX_CRS is high. The external PHY asynchronously drives RX_CRS low during carrier loss.
REF_CLK
RXD[1:0] P R E A M B L E F C S
RX_CRS
*Ambient Operating Temperature Range is assuming the device is mounted on a JEDEC standard test board in a convection cooled JEDEC
test enclosure.
Note: The “typ” values listed in this document are not production tested.
Note: All A/C timing parameters are guaranteed by design.
Note 1: Typical total power consumption for the DS33X162 at 400Mbps is approximately 1W.
Note 2: All outputs loaded with rated capacitance; all inputs between VDD and VSS; inputs with pullups connected to VDD.
Note 3: All disable and power-down bits set, RST held low, outputs not loaded.
t1
t2
GTX_CLK t3
t4
TXD[1:0]n
t4
TX_ENn
t5
t7
RX_CLKn t6
t8 t9
RXD[3:0]n
t8 t9
RX_DVn
t1
t2
TX_CLKn t3
t4
TXD[3:0]n
t4
TX_ENn
t5
t7
RX_CLKn t6
t8 t9
RXD[3:0]n
t8 t9
RX_DVn
t1
t2
REF_CLK t3
t4
TXD[1:0]
t4
TX_EN
t5
t7
REF_CLK t6
t8 t9
RXD[3:0]
t8 t9
RX_CRS
t1
t2
MDC t3
t4
MDIO
MDC
t5 t6
MDIO
t1
t2
TCLKn t3
t4
TDATAn
t5
TSYNCn
t6
t1
t2
RCLKn t3
t4 t5
RDATAn
t4 t5
RSYNCn
t4 t5
t1
t2
TVCLK t3
t4 t5
TVDATA
t4 t5
TVDEN
t4 t5
TVSYNC
t1
t2
RVCLK t3
t4
RVDATA
t5 t6
RVSYNC
RVDEN
P0 P1 P2 P3
SD_CLK
SD_CLK
WRITE t1 t2 t3
t4
Address /
Control
t5 t6
SDATA
SD_UDQS t7 t14 t8
t13
SD_LDQS
SD_UDM t9
SD_LDM
t10
READ
SD_CLK
SD_CLK
SD_UDQS
SD_LDQS
t12
SDATA
t11
t5
WR t1
CS
t2 t3 t4
RD t10
t9
DATA[7:0]
t7 t8
RD t1
CS
t2 t6 t4
WR t10
t9
t5
RW t1
CS
t2 t3 t4
DS t10
t9
DATA[7:0]
t7 t8
t1
RW
CS
t2 t6 t4
DS t10
ADDR[12:0]
DATA[7:0] Address Valid Data Valid
t5
WR t1
CS
t2 t3 t4
RD t11 t9
t10
ALE
ADDR[12:0]
DATA[7:0] Address Valid Data Valid
t7 t8
RD t1
CS
t2 t3 t4
WR t11 t9 t10
ALE
ADDR[12:0]
DATA[7:0] Address Valid Data Valid
t5
RW t1
CS
t2 t3 t4
DS t11 t9
t10
ALE
ADDR[12:0]
DATA[7:0] Address Valid Data Valid
t7 t8
RW
t1
CS
t2 t3 t4
DS t11 t9 t10
ALE
CS T3
T2 T1
SPI_CLK
T4 T5
T9 T8
T6 T7
SPI_MOSI MSB BIT 15 BITS 13 - 0
t1
t2 t3
JTCLK
t4 t5
JTDI, JTMS,
JTRST
t6
t7
JTD0
t8
JTRST
BOUNDRY SCAN
REGISTER
IDENTIFICATION
REGISTER
MUX
BYPASS
REGISTER
INSTRUCTION
REGISTER
The TAP controller is a finite state machine that responds to the logic level at JTMS on the rising edge of JTCLK.
See Figure 13-2 for a diagram of the state machine operation.
13.1.1.1Test-Logic-Reset
Upon power-up, the TAP Controller is in the Test-Logic-Reset state. The Instruction register will contain the
IDCODE instruction. All system logic of the device will operate normally.
13.1.1.2Run-Test-Idle
The Run-Test-Idle is used between scan operations or during specific tests. The Instruction register and test
registers will remain idle.
13.1.1.3Select-DR-Scan
All test registers retain their previous state. With JTMS LOW, a rising edge of JTCLK moves the controller into the
Capture-DR state and will initiate a scan sequence. JTMS HIGH during a rising edge on JTCLK moves the
controller to the Select-IR-Scan state.
13.1.1.4Capture-DR
Data may be parallel-loaded into the test data registers selected by the current instruction. If the instruction does
not call for a parallel load or the selected register does not allow parallel loads, the test register will remain at its
current value. On the rising edge of JTCLK, the controller will go to the Shift-DR state if JTMS is LOW or it will go to
the Exit1-DR state if JTMS is HIGH.
13.1.1.5Shift-DR
The test data register selected by the current instruction is connected between JTDI and JTDO and will shift data
one stage towards its serial output on each rising edge of JTCLK. If a test register selected by the current
instruction is not placed in the serial path, it will maintain its previous state.
13.1.1.6Exit1-DR
While in this state, a rising edge on JTCLK will put the controller in the Update-DR state, which terminates the
scanning process, if JTMS is HIGH. A rising edge on JTCLK with JTMS LOW will put the controller in the Pause-
DR state.
13.1.1.7Pause-DR
Shifting of the test registers is halted while in this state. All test registers selected by the current instruction will
retain their previous state. The controller will remain in this state while JTMS is LOW. A rising edge on JTCLK with
JTMS HIGH will put the controller in the Exit2-DR state.
13.1.1.8Exit2-DR
A rising edge on JTCLK with JTMS HIGH while in this state will put the controller in the Update-DR state and
terminate the scanning process. A rising edge on JTCLK with JTMS LOW will enter the Shift-DR state.
13.1.1.9Update-DR
A falling edge on JTCLK while in the Update-DR state will latch the data from the shift register path of the test
registers into the data output latches. This prevents changes at the parallel output due to changes in the shift
register.
13.1.1.10Select-IR-Scan
All test registers retain their previous state. The instruction register will remain unchanged during this state. With
JTMS LOW, a rising edge on JTCLK moves the controller into the Capture-IR state and will initiate a scan
sequence for the instruction register. JTMS HIGH during a rising edge on JTCLK puts the controller back into the
Test-Logic-Reset state.
13.1.1.11Capture-IR
The Capture-IR state is used to load the shift register in the instruction register with a fixed value. This value is
loaded on the rising edge of JTCLK. If JTMS is HIGH on the rising edge of JTCLK, the controller will enter the
Exit1-IR state. If JTMS is LOW on the rising edge of JTCLK, the controller will enter the Shift-IR state.
13.1.1.12Shift-IR
In this state, the shift register in the instruction register is connected between JTDI and JTDO and shifts data one
stage for every rising edge of JTCLK towards the serial output. The parallel register, as well as all test registers,
remains at their previous states. A rising edge on JTCLK with JTMS HIGH will move the controller to the Exit1-IR
state. A rising edge on JTCLK with JTMS LOW will keep the controller in the Shift-IR state while moving data one
stage thorough the instruction shift register.
13.1.1.13Exit1-IR
A rising edge on JTCLK with JTMS LOW will put the controller in the Pause-IR state. If JTMS is HIGH on the rising
edge of JTCLK, the controller will enter the Update-IR state and terminate the scanning process.
13.1.1.14Pause-IR
Shifting of the instruction shift register is halted temporarily. With JTMS HIGH, a rising edge on JTCLK will put the
controller in the Exit2-IR state. The controller will remain in the Pause-IR state if JTMS is LOW during a rising edge
on JTCLK.
13.1.1.15Exit2-IR
A rising edge on JTCLK with JTMS LOW will put the controller in the Update-IR state. The controller will loop back
to Shift-IR if JTMS is HIGH during a rising edge of JTCLK in this state.
13.1.1.16Update-IR
The instruction code shifted into the instruction shift register is latched into the parallel output on the falling edge of
JTCLK as the controller enters this state. Once latched, this instruction becomes the current instruction. A rising
edge on JTCLK with JTMS held low will put the controller in the Run-Test-Idle state. With JTMS HIGH, the
controller will enter the Select-DR-Scan state.
Test Logic
1 Reset
0
Run Test/ 1 Select 1 Select 1
0 Idle DR-Scan IR-Scan
0 0
1 1
Capture DR Capture IR
0 0
Shift DR 0 Shift IR 0
1 1
1 1
Exit DR Exit IR
0 0
Pause DR 0 Pause IR 0
1 1
0 0
Exit2 DR Exit2 IR
1 1
Update DR Update IR
1 0 1 0
13.2.1 SAMPLE:PRELOAD
This is a mandatory instruction for the IEEE 1149.1 specification. This instruction supports two functions. The
digital I/Os of the device can be sampled at the boundary scan register without interfering with the normal operation
of the device by using the Capture-DR state. SAMPLE:PRELOAD also allows the device to shift data into the
boundary scan register via JTDI using the Shift-DR state.
13.2.2 BYPASS
When the BYPASS instruction is latched into the parallel instruction register, JTDI connects to JTDO through the
one-bit bypass test register. This allows data to pass from JTDI to JTDO not affecting the device’s normal
operation.
13.2.3 EXTEST
This allows testing of all interconnections to the device. When the EXTEST instruction is latched in the instruction
register, the following actions occur. Once enabled via the Update-IR state, the parallel outputs of all digital output
pins are driven. The boundary scan register is connected between JTDI and JTDO. The Capture-DR will sample all
digital inputs into the boundary scan register.
13.2.4 CLAMP
All digital outputs of the device will output data from the boundary scan parallel output while connecting the bypass
register between JTDI and JTDO. The outputs will not change during the CLAMP instruction.
13.2.5 HIGHZ
All digital outputs of the device are placed in a high-impedance state. The BYPASS register is connected between
JTDI and JTDO.
13.2.6 IDCODE
When the IDCODE instruction is latched into the parallel instruction register, the identification test register is
selected. The device identification code is loaded into the identification register on the rising edge of JTCLK
following entry into the Capture-DR state. Shift-DR can be used to shift the identification code out serially via
JTDO. During Test-Logic-Reset, the identification code is forced into the instruction register’s parallel output. The
Rev: 063008 367 of 375
________________________________________________ DS33X162/X161/X82/X81/X42/X41/X11/W41/W11
ID code will always have a 1 in the LSB position. The next 11 bits identify the manufacturer’s JEDEC number and
number of continuation bytes followed by 16 bits for the device and 4 bits for the version.
This register contains both a shift register path and a latched parallel output for all control cells and digital I/O cells
and is n bits in length.
This is a single one-bit shift register used in conjunction with the BYPASS, CLAMP, and HIGHZ instructions, which
provides a short path between JTDI and JTDO.
The identification register contains a 32-bit shift register and a 32-bit latched parallel output. This register is
selected during the IDCODE instruction and when the TAP controller is in the Test-Logic-Reset state.
Run Test Select DR Capture Exit1 Update Select DR Select IR Capture Shift IR Exit1 Update Select DR Capture Shift Test
(STATE) Reset
Idle Scan DR
Shift
DR DR DR Scan Scan IR IR IR Scan DR DR Logic Idle
JTCLK
JTRST
JTMS X X
JTDI X X X
JTDO
X
Output
Pin Output pin level change if in "EXTEST" instruction mode
A JTCLK SDA[3] SDA[10] SDCS SDA[12] SRAS SWE SD_CLK SD_CLK VSS VDDQ VDDQ SDATA[6] SDATA[4] VDDQ VDDQ
B JTRST SDA[2] SBA[1] SBA[0] SDA[6] SDA[9] SCAS VDD2.5 VREF SDATA[12] SDATA[13] SDATA[15] SDATA[7] VSSQ SDATA[2] SDATA[1]
SD_CLKE
C JTMS SDA[1] SDA[0] SDA[7] SDA[11] VSS VSSQ SDATA[9] SDATA[11] SDATA[14] SDATA[5] SD_LDQS VDDQ SDATA[3] SDATA[0]
N
D RDATA1 JTDI SDA[4] SDA[5] SDA[8] VSSQ SD_UDM SD_UDQS SDATA[8] VDDQ VDD1.8 SDATA[10] SD_LDM VDDQ VSSQ VSSQ
E RCLK1 JTDO VDD1.8 VDD1.8 VDD2.5 VSSQ VDD2.5 RST VDD3.3 VDD3.3 AVSS VDD3.3 RX_CRS1 COL1 VSSQ SYSCLKI
RXD[1] / RXD[2] /
F RSYNC1 RDATA6 RDATA5 RCLK5 AVDD VSS VDD3.3 VSS VSS VSS VSS VDD1.8 MDC VSS
RXD1[1] RXD1[2]
RXD[0] /
G RCLK3 RSYNC3 RSYNC5 RDATA3 VDD3.3 VSS RCLK2 RDATA2 VSS A8 A10 VDD1.8 MDIO RX_DV1 RX_CLK1
RXD1[0]
TXD[3] / RXD[3] /
H RSYNC4 RDATA4 RSYNC6 RCLK4 VSS DNC RSYNC2 DNC VSS VSS VDD1.8 VDD1.8 RX_ERR1 HIZ
TXD1[3] RXD1[3]
TXD[0] / TXD[2] /
J RCLK6 RCLK10 RCLK9 RCLK8 RCLK7 DNC ALE CS RD / DS WR / RW INT MODE RX_CRS2 SPI_SEL
TXD1[0] TXD1[2]
D0 / D2 / D6 / TXD[1] / RXD[7] /
K RDATA7 RDATA9 RDATA10 RSYNC9 VDD3.3 D4 A0 A2 A6 A4 TX_EN1
SPI_MISO SPI_CLK SPI_CPHA TXD1[1] RXD2[3]
D1 / D5 /SPI_ RXD[6] /
L RDATA8 RSYNC8 RSYNC11 RDATA12 RCLK13 D3 A1 A3 A5 A7 A9 TX_ERR1 COL2
SPI_MOSI SWAP RXD2[2]
D7 / RXD[5] /
M RSYNC10 RCLK11 VDD1.8 RSYNC13 TDATA5 TSYNC3 TCLK5 VDD3.3 TMCLK4 RX_DV2 RX_ERR2 VSS RMII_SEL TX_CLK1
SPI_CPOL RXD2[1]
TXD[4] / RXD[4] /
N RDATA11 RCLK12 RDATA15 RDATA16 RSYNC7 TDATA6 TDATA7 TSYNC7 TDATA4 TDATA9 TDATA11 TDATA15 RX_CLK2 TMSYNC4
TXD2[0] RXD2[0]
TXD[5] /
P RSYNC12 RDATA13 RSYNC15 VDD3.3 TCLK2 TDATA3 TSYNC4 TSYNC6 TCLK4 TCLK6 TDATA16 TDATA14 DCEDTES TDATA13 TX_EN2
TXD2[1]
TXD[6] /
R RDATA14 RSYNC14 RCLK16 VSS TCLK1 TSYNC1 TSYNC5 TCLK3 TDATA8 TCLK8 TDATA10 TDATA12 VDD1.8 GTX_CLK TX_ERR2
TXD2[2]
TXD[7] /
T RCLK14 DNC RSYNC16 RCLK15 VSS TDATA1 TDATA2 TSYNC2 TSYNC8 TCLK7 TMCLK3 TMSYNC3 REF_CLK VDD3.3 TX_CLK2
TXD2[3]
Note: Shaded pins do not apply to all devices in the product family. See the pin listing for specific pin availability. In the high port
count devices, the shaded input pins DO NOT HAVE PULLUP/PULLDOWN resistors. Consideration must be taken during
board design to bias the inputs appropriately, and to float output pins (TDATA5-TDATA16, TX_EN2, TX_ERR2) if lower port
count designs are to be potentially stuffed with higher port count devices.
A JTCLK SDA[3] SDA[10] SDCS SDA[12] SRAS SWE SD_CLK SD_CLK VSS VDDQ VDDQ SDATA[6] SDATA[4] VDDQ VDDQ
B JTRST SDA[2] SBA[1] SBA[0] SDA[6] SDA[9] SCAS VDD2.5 VREF SDATA[12] SDATA[13] SDATA[15] SDATA[7] VSSQ SDATA[2] SDATA[1]
SD_CLKE
C JTMS SDA[1] SDA[0] SDA[7] SDA[11] VSS VSSQ SDATA[9] SDATA[11] SDATA[14] SDATA[5] SD_LDQS VDDQ SDATA[3] SDATA[0]
N
D RDATA1 JTDI SDA[4] SDA[5] SDA[8] VSSQ SD_UDM SD_UDQS SDATA[8] VDDQ VDD1.8 SDATA[10] SD_LDM VDDQ VSSQ VSSQ
E RCLK1 JTDO VDD1.8 VDD1.8 VDD2.5 VSSQ VDD2.5 RST VDD3.3 VDD3.3 AVSS VDD3.3 RX_CRS1 COL1 VSSQ SYSCLKI
RXD[1] / RXD[2] /
F RSYNC1 RVDATA RVCLK RVSYNC AVDD VSS VDD3.3 VSS VSS VSS VSS VDD1.8 MDC VSS
RXD1[1] RXD1[2]
RXD[0] /
G RCLK3 RSYNC3 RVDEN RDATA3 VDD3.3 VSS RCLK2 RDATA2 VSS A8 A10 VDD1.8 MDIO RX_DV1 RX_CLK1
RXD1[0]
TXD[3] / RXD[3] /
H RSYNC4 RDATA4 RCLK4 VSS DNC RSYNC2 DNC VSS VSS VDD1.8 VDD1.8 RX_ERR1 HIZ
TXD1[3] RXD1[3]
TXD[0] / TXD[2] /
J DNC ALE CS RD / DS WR / RW INT MODE SPI_SEL
TXD1[0] TXD1[2]
D0 / D2 / D6 / TXD[1] / RXD[7] /
K VDD3.3 D4 A0 A2 A6 A4 TX_EN1
SPI_MISO SPI_CLK SPI_CPHA TXD1[1] RXD2[3]
D1 / D5 /SPI_ RXD[6] /
L D3 A1 A3 A5 A7 A9 TX_ERR1
SPI_MOSI SWAP RXD2[2]
D7 / RXD[5] /
M VDD1.8 TVDATA TSYNC3 TVCLK VDD3.3 VSS RMII_SEL TX_CLK1
SPI_CPOL RXD2[1]
TXD[4] / RXD[4] /
N TVDEN TDATA4
TXD2[0] RXD2[0]
TXD[5] /
P VDD3.3 TCLK2 TDATA3 TSYNC4 TCLK4 DCEDTES
TXD2[1]
TXD[6] /
R VSS TCLK1 TSYNC1 TVSYNC TCLK3 VDD1.8 GTX_CLK
TXD2[2]
TXD[7] /
T DNC RCLK15 VSS TDATA1 TDATA2 TSYNC2 REF_CLK VDD3.3
TXD2[3]
Note 1: Shaded pins do not apply to the DS33W11. See the pin listing for specific pin availability.
Note 2: The TVDEN pin is an input on the DS33W41/DS33W11, and is an output pin on other devices in the product family.
B VDD2.5 SDA[2] SDA[8] SDA[11] SRAS VSS VSS SDATA[10] SDATA[14] SDATA[5] SDATA[1] VDDQ
C SDA[4] SDA[6] SDA[10] SBA[1] SWE VDD2.5 VDDQ SDATA[8] SDATA[12] SDATA[7] SDATA[3] AVSS
D SDA[3] SDA[1] SDA[12] SBA[0] SCAS VREF SD_UDQS SDATA[9] SDATA[13] SDATA[6] SDATA[2] AVDD
E SDA[5] SDA[7] VSS VDDQ SD_CLKEN SD_LDM SD_UDM SD_LDQS SDATA[11] VDDQ VSS SYSCLKI
F VDD1.8 RST VDD3.3 DNC DNC VSS VSS TX_EN1 RX_DV1 HIZ VDD3.3 VSS
G RCLK1 JTMS JTCLK JTRST INT VDD1.8 VDD1.8 TX_ERR1 RX_ERR1 COL1 VSS RX_CRS1
H VDD3.3 JTDO JTDI MDIO MDC VDD3.3 VDD3.3 TXD[2] TXD[3] RXD[2] RXD[3] VDD1.8
J RSYNC1 RDATA1 CS SPI_MISO SPI_SWAP VSS VSS TXD[0] TXD[1] RXD[0] RXD[1] RX_CLK1
K VSS VSS DNC SPI_MOSI SPI_CPHA VSS RMII_SEL TXD[5] TXD[7] RXD[6] RXD[7] VDD3.3
L VDD1.8 DNC TDATA1 SPI_CLK SPI_CPOL VSS DCEDTES TXD[4] TXD[6] RXD[4] RXD[5] TX_CLK1
M VSS VDD3.3 TCLK1 TSYNC1 VDD1.8 VSS VDD3.3 REF_CLK VSS GTX_CLK VDD1.8 VSS
Note that the parallel bus is not available in the 144-pin DS33X11, and the SPI slave port must be used for processor control.
050808 Clarified LP2PF[2:1] and LP2ETF[2:1] bit definitions (SU.LP2C, bits 4:1). 179
Corrected AR.WQ1EA bits 15:8 names to correctly match the register bit map in
210
Table 10-2.
Clarified WISPL bit definition (AR.MQC, bit 3). 221
Updated EBBYS bit definition (PP.EMCR, bit 8). 230
Updated DBBS bit definition (PP.DMCR, bit 9). 236
Clarified LM bit definition (SU.MACCR, bit 12). 276
Added PM bit definition (SU.MACFFR, bit 0). 277
060508 Removed future status from DS33W11 in the Ordering Information table. 1
Removed future status from DS33W41, DS33X41, DS33X42, DS33X82, and
063008 1
DS33X161 in the Ordering Information table.