BCM53128

Data Sheet
BCM53128
Multiport Gigabit Ethernet Switches
GENERAL DESCRIPTION
The Broadcom® BCM53128 is a highly integrated, • Port-based VLAN
cost-effective unmanaged-smart gigabit switch. The • IEEE 802.1Q-based VLAN with 4K entries
switch design is based on the field-proven, industry- • MAC-based trunking with automatic link failover
leading ROBO architecture. This device combines • Port-based rate control
all the functions of a high-speed switch system
• Port mirroring
including packet buffers, PHY transceivers, media
access controllers (MACs), address management, • BroadSync® HD for IEEE 802.1AS support
port-based rate control, and a non-blocking switch – Timestamp tagging at MAC interface
fabric into a single 65-nm CMOS device. Designed – Time-aware egress scheduler
to be fully compliant with the IEEE 802.3™ and • DOS attack prevention
l
tia
IEEE 802.3x specifications, including the MAC- – Support IPv6
control PAUSE frame, the BCM53128 provides
• IGMP snooping, MLD snooping support
compatibility with all industry-standard Ethernet,
en
Fast Ethernet, and Gigabit Ethernet (GbE) devices. • Green mode support
• Spanning tree support (multiple spanning trees–
The BCM53128 has a rich feature set suitable for
not only standard GbE connectivity for desktop and
laptop PCs, but also for next-generation gaming • fid
up to eight)
Loop detection for unmanaged configurations
with Broadcom’s patented LoopDTech™
on
consoles, set-top boxes, networked DVD players,
and home theater receivers. It is also specifically technology
designed for next generation SOHO/SMB routers • CableChecker™ with unmanaged mode support
C
and gateways. • Double tagging/QinQ

The BCM53128 contains eight full-duplex 10/100/ • IEEE 802.az EEE (Energy Efficient Ethernet)
om
1000BASE-TX Ethernet transceivers. support

The BCM53128 provides 70+ on-chip MIB counters • IEEE 802.3as support
to collect receive and transmit statistics for each • IEEE 802.3x programmable per-port flow control
dc
port. and backpressure, with IEEE 802.1x support for

The BCM53128 is available in commercial secure user authentication
oa
temperature (C-Temp) and industrial temperature (I- • EEPROM, MDC/MDIO, and SPI Interfaces
Temp) rated packages. The BCM53128 is provided • Serial Flash Interface for accessing embedded
Br
in a 256-pin eLQFP (28 mm x 28 mm) package. 8051 processor

• 4K entry MAC address table with automatic
FEATURES learning and aging
• 192 KB packet buffer
• Nine 10/100/1000 media access controllers • 256 multicast group support
• Eight port 10/100/1000BASE-T/Tx transceivers • Jumbo frame support up to 9720 bytes
• One GMII/RGMII/MII/RvMII/TMII/RvTMII • Serial and parallel LED interface
interface for an in-band management port (IMP)
• 1.2V for core and 3.3V for I/O
for connection to a CPU/management entity
without PHY • JTAG support
• IEEE 802.1p, MAC, Port, TOS, and DiffServ QoS • 256 eLQFP
for four queues, plus two time sensitive queues
53128-DS07-R
Corporate Headquarters: San Jose, CA April 6, 2016

Figure 1: Functional Block Diagram
l
tia
en
fid
on
C
om
dc
oa
Br
© 2016 by Broadcom. All rights reserved.

Broadcom®, the pulse logo, Connecting everything®, the Connecting everything logo, and Avago
Technologies are among the trademarks of Broadcom and/or its affiliates in the United States, certain other
countries and/or the EU. Any other trademarks or trade names mentioned are the property of their respective
owners.
Broadcom reserves the right to make changes without further notice to any products or data herein to improve
reliability, function, or design.
Information furnished by Broadcom is believed to be accurate and reliable. However, Broadcom does not
assume any liability arising out of the application or use of this information, nor the application or use of any
product or circuit described herein, neither does it convey any license under its patent rights nor the rights of
others.
This data sheet (including, without limitation, the Broadcom component(s) identified herein) is not designed,
intended, or certified for use in any military, nuclear, medical, mass transportation, aviation, navigations,
pollution control, hazardous substances management, or other high-risk application. BROADCOM
PROVIDES THIS DATA SHEET “AS-IS,” WITHOUT WARRANTY OF ANY KIND. BROADCOM DISCLAIMS
ALL WARRANTIES, EXPRESSED AND IMPLIED, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-
INFRINGEMENT.
BCM53128 Data Sheet Revision History
Revision History
Change Description Customer Impact Action Items

Revision: 53128-DS07-R
Date: 04/06/16
Updated:
• “Transmit Output Port Queues” on Corrected typo for entries No action required.
page 90 number.
• Table 291: “EEE GLB Congst TH Corrected typo for entries No action required.
Register (Page 92h: Address C4h),” on number.
page 293
• Table 293: “EEE TXQ Cong TH Register Corrected typo for entries No action required.
(Page 92h: Address C6h),” on page 293 number.
l
Added:
tia
• Table 324: “BCM53128IQLE Package – No action required.
with Heat Sink, 4-layer Board, P=3.1W,”
en
on page 315
Date: 06/02/14
fid
on
Updated:
• Table 324: “Ordering Information,” on Added ordering information for No action required.
C
page 318 part number

BCM53128IQLE(G)
om
Date: 02/18/13
dc
Updated:
• Default bits 13, 12, 8, and 6 in Table 128
oa
on page 197.
• Default bits 11, 10, 8, 7, 6, and 5 in
Br
Table 132 on page 200.

• Default bits 12, 11, 10, 9, and 8 in
Table 137 on page 205.
• Table 321: “Ordering Information,” on
page 319.
Date: 07/21/11
Updated:
• General Description Updated the general No action required.
description.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 3
BROADCOM CONFIDENTIAL

• Section 12: “Ordering Information,” on Added ordering information for No action required.
page 319 part number
BCM53128VIQLE(G)
Date: 12/13/10
Updated:
• “IGMP Snooping” on page 49 None. No action required.
• “Loop Detection” on page 52 Updated referenced document. No action required.
• “Address Resolution and Frame Edited the forward field. Corrected typo.
Forwarding” on page 59
• “Multicast Addresses” on page 61 Removed reference to No action required.
IP_MULTICAST bit.
l
• Table 8: “Multicast Forward Field Replaced IP_MULTICAST No action required.
tia
Definitions,” on page 61 column with UNICAST/
MULTICAST column and
en
updated the forwarding field.
• Table 9: “Address Table Entry for Replaced IPMCO with No action required.
Multicast Address,” on page 61 FWD_PRT_MAP.
• “Energy Efficient Ethernet Mode” on
page 66
fid
Updated referenced document. No action required.
on
• “Serial Flash Interface” on page 95 Updated SRAM value. No action required.
• Figure 44: “Write Access to the Register Changed Read MII Register 27 Corrected typo.
C
Set Using the PseudoPHY (PHYAD = to Write Register 27.

11110) MDC/MDIO Path,” on page 119
om
• Table 29: “Signal Type Definitions,” on Updated XTALO signal No action required.
page 126 description and added GPIO
pins.
dc
• Section 6: “Pin Assignment,” on page Updated pin assignments to New feature option available.
139 include GPIO pins.
oa
• “BCM53128KQLE Pin List by Ball Updated pin list to include GPIO New feature option available.
Name” on page 141 pins
• Table 31: “Control Registers (Page Added addresses B0h-B7h and No action required.
Br
00h),” on page 145 B8h-BFh to table.

• “PHY Identifier Register (Page 10h–17h: Edited binary OUI. Corrected typo.
Address 04h)” on page 199
• Table 170: “Expansion Register 45h: Added addresses B8h-BBh and No action required.
Transmit CRC,” on page 233 BCh-BFh
• Table 295: “Absolute Maximum Updated maximum value for Corrected typo.
Ratings,” on page 299 electrostatic discharge (VESD)
• Table 297: “Electrical Characteristics,” Updated XTALI minimum and No action required.
on page 300 maximum.
• Figure 64: “SPI Timings, SS Asserted Updated figure. No action required.
During SCK High,” on page 313
• Table 316: “SPI Timings,” on page 313 Added time interval rows No action required.
Added:
Broadcom®
April 6, 2016 • 53128-DS07-R Page 4

“GPIO ” on page 95 New feature option available.
Date: 09/08/10
Updated:
• “Deep Green Mode” on page 66. None. No action required.
• Figure 45: “LED Interface Register Correct editing errors. No action required.
Structure Diagram,” on page 121.
• Table 29: “Signal Type Definitions,” on Power interface description Suggest a review of the
page 125. update to change core power schematics.
from 1.1V to 1.2V.
• Table 82: “Aging Time Control Register Descriptions updated. Typo correction.
(Page 02h: Address 06h–09h),” on
l
page 169.
tia
• “Absolute Maximum Ratings” on Updated core value absolute Suggest a review of the
page 297. maximum rating value. schematics.
en
• “Recommended Operating Conditions” Updated core voltage 1.2V Suggest a review of the
on page 297. minimum and maximum value schematics.
of recommended operating
•
conditions.
fid
“Electrical Characteristics” on page 298. Updated maximum power Suggest a review of the
on
consumption by core 1.2V and schematics.
IO 3.3V.
C
• Section 11: “Mechanical Information,” on Correct editing errors. No action required.

page 316.
om
Document Number Date Change Description

dc
53128-DS01-R 04/02/10 Updated:

• Table 3: “Bucket Bit Rate,” on page 44.
oa
• Section 6: “Pin Assignment,” on page 137.

• Section 7: “Register Definitions,” on page 141.
• Section 8: “Electrical Characteristics,” on page 296.
Br
• Section 9: “Timing Characteristics,” on page 298.

• Section 10: “Thermal Characteristics,” on page 313.
Added:
• “TMII (Turbo MII) and RvTMII (Reverse TMII) Interface” on
page 91.
• “Signal Descriptions” on page 124.
• “LED Control Register (Page 00h: Address 1Ch)” on page 152.
• “IMP RGMII Control Register (Page 00h: Address 60h)” on
page 160.
• “Page 03h: Interrupt Control Register” on page 175.
• “Page 92h: EEE Control Register” on page 287.
53128-DS00-R 12/17/09 Initial release.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 5
BCM53128 Data Sheet Table of Contents
Table of Contents
About This Document ................................................................................................................................ 30
Purpose and Audience .......................................................................................................................... 30
Acronyms and Abbreviations................................................................................................................. 30
Document Conventions ......................................................................................................................... 30
References ............................................................................................................................................ 31
Technical Support ...................................................................................................................................... 31
Section 1: Introduction ..................................................................................................... 32
Overview...................................................................................................................................................... 32
Section 2: Features and Operation .................................................................................. 33
Overview of Features and Operation........................................................................................................ 33
l
tia
Quality of Service ....................................................................................................................................... 34
Egress Transmit Queues....................................................................................................................... 35
en
Port-Based QoS .................................................................................................................................... 35
IEEE 802.1p QoS .................................................................................................................................. 35
fid
MACDA-Based QoS.............................................................................................................................. 36
TOS/DSCP QoS.................................................................................................................................... 36
on
TC Decision Tree .................................................................................................................................. 36
Non-BroadSync HD Frame ............................................................................................................ 36
C
BroadSync HD Frame .................................................................................................................... 37

om
Queuing Class (COS) Determination .................................................................................................... 37

Port-Based VLAN........................................................................................................................................ 38
IEEE 802.1Q VLAN...................................................................................................................................... 39
dc
IEEE 802.1Q VLAN Table Organization................................................................................................ 39

oa
Programming the VLAN Table................................................................................................................... 40

Double-Tagging .......................................................................................................................................... 41
Br
ISP Port ................................................................................................................................................. 42

Customer Port ....................................................................................................................................... 42
Uplink Traffic (from Customer Port to ISP)............................................................................................ 43
Downlink Traffic (from ISP to Customer Port) ....................................................................................... 43
Jumbo Frame Support ............................................................................................................................... 44
Port Trunking/Aggregation........................................................................................................................ 44
WAN Port..................................................................................................................................................... 45
Rate Control ................................................................................................................................................ 45
Ingress Rate Control ............................................................................................................................. 45
Two-Bucket System .............................................................................................................................. 46
Egress Rate Control .............................................................................................................................. 46
Broadcom®
April 6, 2016 • 53128-DS07-R Page 6
Bucket Bit Rate...................................................................................................................................... 47

IMP Port Egress Rate Control ............................................................................................................... 47
Protected Ports........................................................................................................................................... 47
Port Mirroring.............................................................................................................................................. 48
Enabling Port Mirroring.......................................................................................................................... 48
Capture Port .......................................................................................................................................... 48
Mirror Filtering Rules ............................................................................................................................. 48
Port Mask Filter .............................................................................................................................. 48
Packet Address Filter ..................................................................................................................... 49
Packet Divider Filter ....................................................................................................................... 49
IGMP Snooping........................................................................................................................................... 49
MLD Snooping ............................................................................................................................................ 50
l
IEEE 802.1x Port-Based Security .............................................................................................................. 50
tia
DoS Attack Prevention............................................................................................................................... 51
en
MSTP Multiple Spanning Tree ................................................................................................................... 52
Software Reset............................................................................................................................................ 52
fid
Loop Detection ........................................................................................................................................... 52
BroadSync HD ............................................................................................................................................ 53
on
Time Base and Slot Generation ............................................................................................................ 53
Transmission Shaping and Scheduling ................................................................................................. 54
C
BroadSync HD Class 5 Media Traffic............................................................................................. 54

BroadSync HD Class 4 Media Traffic............................................................................................. 55
om
CableChecker™ .......................................................................................................................................... 56
Egress PCP Remarking.............................................................................................................................. 57
dc
Address Management ................................................................................................................................ 57

Address Table Organization.................................................................................................................. 58
oa
Address Learning .................................................................................................................................. 59

Address Resolution and Frame Forwarding.......................................................................................... 59
Br
Unicast Addresses ......................................................................................................................... 59

Multicast Addresses ....................................................................................................................... 61
Reserved Multicast Addresses....................................................................................................... 62
Static Address Entries ........................................................................................................................... 63
Accessing the ARL Table Entries.......................................................................................................... 63
Reading an ARL Entry ................................................................................................................... 63
Writing an ARL Entry...................................................................................................................... 63
Searching the ARL Table ............................................................................................................... 64
Address Aging ....................................................................................................................................... 64
Fast Aging ............................................................................................................................................. 65
Using the Multiport Addresses .............................................................................................................. 65
Broadcom®
April 6, 2016 • 53128-DS07-R Page 7
Power Savings Modes................................................................................................................................ 65

Auto Power Down Mode........................................................................................................................ 66
Energy Efficient Ethernet Mode............................................................................................................. 66
Short Cable Mode (Green Mode) .......................................................................................................... 66
Deep Green Mode................................................................................................................................. 67
Section 3: System Functional Blocks.............................................................................. 68
Overview of System Functional Blocks ................................................................................................... 68
Media Access Controller............................................................................................................................ 68
Receive Function................................................................................................................................... 68
Transmit Function.................................................................................................................................. 69
Flow Control .......................................................................................................................................... 69
10/100 Mbps Half-Duplex............................................................................................................... 69
l
tia
10/100/1000 Mbps Full-Duplex ...................................................................................................... 69
Integrated 10/100/1000 PHY....................................................................................................................... 70
en
Encoder ................................................................................................................................................. 70
Decoder................................................................................................................................................. 71
fid
Link Monitor........................................................................................................................................... 71
Digital Adaptive Equalizer ..................................................................................................................... 72
on
Echo Canceler....................................................................................................................................... 72
Cross Talk Canceler.............................................................................................................................. 72
C
Analog-to-Digital Converter ................................................................................................................... 72

Clock Recovery/Generator .................................................................................................................... 73
om
Baseline Wander Correction ................................................................................................................. 73

Multimode TX Digital-to-Analog Converter............................................................................................ 73
dc
Stream Cipher ....................................................................................................................................... 73

Wire Map and Pair Skew Correction ..................................................................................................... 74
oa
Automatic MDI Crossover ..................................................................................................................... 74

10/100BASE-TX Forced Mode Auto-MDIX ........................................................................................... 75
Br
Resetting the PHY................................................................................................................................. 75

PHY Address......................................................................................................................................... 76
Super Isolate Mode ............................................................................................................................... 76
Standby Power-Down Mode.................................................................................................................. 76
Auto Power-Down Mode ....................................................................................................................... 77
External Loopback Mode....................................................................................................................... 77
Full-Duplex Mode .................................................................................................................................. 78
Copper Mode ................................................................................................................................. 78
Master/Slave Configuration ................................................................................................................... 79
Next Page Exchange............................................................................................................................. 79
Frame Management.................................................................................................................................... 79
Broadcom®
April 6, 2016 • 53128-DS07-R Page 8
In-Band Management Port .................................................................................................................... 79

Broadcom Tag Format for Egress Packet Transfer............................................................................... 81
Broadcom Tag Format for Ingress Packet Transfer .............................................................................. 82
MIB Engine .................................................................................................................................................. 83
MIB Counters Per Port .......................................................................................................................... 83
Receive Only Counter (19) Description of Counter........................................................................ 83
Transmit Counters Only (19) Description of Counter ..................................................................... 85
Transmit or Receive Counters (10) Description of Counter ........................................................... 86
Integrated High-Performance Memory ..................................................................................................... 90
Switch Controller........................................................................................................................................ 90
Buffer Management............................................................................................................................... 90
Memory Arbitration ................................................................................................................................ 90
l
Transmit Output Port Queues ............................................................................................................... 90
tia
Section 4: System Interfaces............................................................................................ 92
en
Overview of System Interfaces ................................................................................................................. 92
Copper Interface ......................................................................................................................................... 92
fid
Auto-Negotiation.................................................................................................................................... 92
Line-side (Remote) Loopback Mode ..................................................................................................... 93
on
Frame Management Port Interface............................................................................................................ 93
MII Interface .......................................................................................................................................... 93
C
TMII (Turbo MII) and RvTMII (Reverse TMII) Interface......................................................................... 93

Reverse MII Port (RvMII)....................................................................................................................... 93
om
GMII Port ............................................................................................................................................... 94

RGMII Port ............................................................................................................................................ 94
dc
Configuration Pins ..................................................................................................................................... 94

Programming Interfaces ............................................................................................................................ 95
oa
Serial Flash Interface ............................................................................................................................ 95

GPIO ..................................................................................................................................................... 95
Br
SPI-Compatible Programming Interface................................................................................................ 96

SS: Slave Select ............................................................................................................................ 96
SCK: Serial Clock........................................................................................................................... 96
MOSI: Master Output Slave Input .................................................................................................. 96
MISO: Master Input Slave Output .................................................................................................. 97
Without External PHY .................................................................................................................... 98
External PHY Registers ................................................................................................................. 99
Reading and Writing BCM53128 Registers Using SPI .................................................................. 99
Normal Read Operation ............................................................................................................... 100
Fast Read Operation.................................................................................................................... 104
Normal Write Operation ............................................................................................................... 107
Broadcom®
April 6, 2016 • 53128-DS07-R Page 9
EEPROM Interface.............................................................................................................................. 110

EEPROM Format ......................................................................................................................... 110
MDC/MDIO Interface ................................................................................................................................. 112
MDC/MDIO Interface Register Programming...................................................................................... 112
PseudoPHY......................................................................................................................................... 113
LED Interfaces .......................................................................................................................................... 119
Dual Input Configuration/LED Output Function ................................................................................... 123
Section 5: Hardware Signal Definition Table ................................................................ 124
I/O Signal Types........................................................................................................................................ 124
Signal Descriptions .................................................................................................................................. 125
Section 6: Pin Assignment ............................................................................................. 138
BCM53128KQLE Pin List by Signal Name.............................................................................................. 138
l
tia
BCM53128KQLE Pin List by Ball Number .............................................................................................. 140
Section 7: Register Definitions ...................................................................................... 142
en
Register Definition.................................................................................................................................... 142
Register Notations.................................................................................................................................... 142
fid
Global Page Register ............................................................................................................................... 142
on
Page 00h: Control Registers ................................................................................................................... 144
Port Traffic Control Register (Page 00h: Address 00h)....................................................................... 146
C
IMP Port Control Register (Page 00h: Address 08h) .......................................................................... 147
Switch Mode Register (Page 00h: Address 0Bh) ................................................................................ 148
om
IMP Port State Override Register (Page 00h: Address 0Eh) .............................................................. 148
LED Control Register (Page 00h: Address 0Fh–1Bh)......................................................................... 149
dc
LED Refresh Register (Page 00h: Address 0Fh) ................................................................................ 149

LED Function 0 Control Register (Page 00h: Address 10h)................................................................ 150
oa
LED Function 1 Control Register (Page 00h: Address 12h)................................................................ 151

LED Function Map Register (Page 00h: Address 14h–15h) ............................................................... 151
Br
LED Enable Map Register (Page 00h: Address 16h–17h).................................................................. 152

LED Mode Map 0 Register (Page 00h: Address 18h–19h) ................................................................. 152
LED Mode Map 1 Register (Page 00h: Address 1Ah–1Bh) ................................................................ 152
LED Control Register (Page 00h: Address 1Ch)................................................................................. 153
PHY LED Control Register (Page 00h: Address 1Dh) ........................................................................ 153
Port Forward Control Register (Page 00h: Address 21h).................................................................... 154
Protected Port Selection Register (Page 00h: Address 24h–25h) ...................................................... 155
WAN Port Select Register (Page 00h: Address 26h–27h) .................................................................. 155
Pause Capability Register (Page 00h: Address 28h–2Bh).................................................................. 155
Reserved Multicast Control Register (Page 00h: Address 2Fh).......................................................... 156
Unicast Lookup Failed Forward Map Register (Page 00h: Address 32h) ........................................... 157
Broadcom®
April 6, 2016 • 53128-DS07-R Page 10
Multicast Lookup Failed Forward Map Register (Page 00h: Address 34h–35h) ................................. 157
MLF IPMC Forward Map Register (Page 00h: Address 36h–37h)...................................................... 158
Pause Pass Through for RX Register (Page 00h: Address 38h–39h) ................................................ 158
Pause Pass Through for TX Register (Page 00h: Address 3Ah–3Bh)................................................ 158
Disable Learning Register (Page 00h: Address 3Ch–3Dh)................................................................. 159
Software Learning Register (Page 00h: Address 3Eh–3Fh) ............................................................... 159
Port State Override Register (Page 00h: Address 58h) ...................................................................... 160
IMP RGMII Control Register (Page 00h: Address 60h)....................................................................... 161
MDIO IMP Port Address Register (Page 00h: Address 78h) .............................................................. 161
Software Reset Control Register (Page 00h: Address 79h)................................................................ 161
Pause Frame Detection Control Register (Page 00h: Address 80h)................................................... 162
Fast-Aging Control Register (Page 00h: Address 88h) ....................................................................... 162
l
Fast-Aging Port Control Register (Page 00h: Address 89h) ............................................................... 162
tia
Fast-Aging VID Control Register (Page 00h: Address 8Ah–8Bh) ....................................................... 163
en
CPU Data 0 Share Register (Page 00h: Address B0h-B7h) ............................................................... 163
CPU Data 1 Share Register (Page 00h: Address B8h-BFh) .............................................................. 163
fid
Page 01h: Status Registers ..................................................................................................................... 164
Link Status Summary (Page 01h: Address 00h) ................................................................................. 164
on
Link Status Change (Page 01h: Address 02h) .................................................................................... 165
Port Speed Summary (Page 01h: Address 04h) ................................................................................. 165
C
Duplex Status Summary (Page 01h: Address 08h)............................................................................. 166

Pause Status Summary (Page 01h: Address 0Ah) ............................................................................. 166
om
Source Address Change Register (Page 01h: Address 0Eh) ............................................................. 167
Last Source Address Register (Page 01h: Address 10h).................................................................... 167
dc
Page 02h: Management/Mirroring Registers ......................................................................................... 168

Global Management Configuration Register (Page 02h: Address 00h) .............................................. 169
oa
IMP Port ID Register (Page 02h: Address 01h) .................................................................................. 169

Broadcom Header Control Register (Page 02h: Address 03h) ........................................................... 170
Br
RMON MIB Steering Register (Page 02h: Address 04h) .................................................................... 170
Aging Time Control Register (Page 02h: Address 06h) ...................................................................... 170
Mirror Capture Control Register (Page 02h: Address 10h) ................................................................. 171
Ingress Mirror Control Register (Page 02h: Address 12h) .................................................................. 171
Ingress Mirror Divider Register (Page 02h: Address 14h)................................................................... 172
Ingress Mirror MAC Address Register (Page 02h: Address 16h)........................................................ 172
Egress Mirror Control Register (Page 02h: Address 1Ch) .................................................................. 173
Egress Mirror Divider Register (Page 02h: Address 1Eh)................................................................... 174
Egress Mirror MAC Address Register (Page 02h: Address 20h) ........................................................ 174
Device ID Register (Page 02h: Address 30h–33h) ............................................................................. 174
Revision Number Register (Page 02h: Address 40h) ......................................................................... 174
Broadcom®
April 6, 2016 • 53128-DS07-R Page 11
High-Level Protocol Control Register (Page 02h: Address 50h–53h) ................................................. 175
Page 03h: Interrupt Control Register...................................................................................................... 177
Interrupt Status Register (Page 03h: Address 00h) ............................................................................ 177
Interrupt Enable Register (Page 03h: Address 08h) ........................................................................... 177
IMP Sleep Timer Register (Page 03h: Address 10h) .......................................................................... 178
Sleep Status Register (Page 03h: Address 18h)................................................................................. 178
External CPU Interrupt Trigger Register (Page 03h: Address 20h) .................................................... 178
Page 04h: ARL Control Register ............................................................................................................. 179
Global ARL Configuration Register (Page 04h: Address 00h) ............................................................ 180
BPDU Multicast Address Register (Page 04h: Address 04h).............................................................. 180
Multiport Control Register (Page 04h: Address 0Eh–0Fh) .................................................................. 181
Multiport Address N (N=0–5) Register (Page 04h: Address 10h) ....................................................... 182
l
Multiport Vector N (N = 0–5) Register (Page 04h: Address 18h) ........................................................ 183
tia
Page 05h: ARL/VTBL Access Registers................................................................................................. 184
en
ARL Table Read/Write Control Register (Page 05h: Address 00h) .................................................... 185
MAC Address Index Register (Page 05h: Address 02h) ..................................................................... 185
fid
VLAN ID Index Register (Page 05h: Address 08h) ............................................................................. 186
ARL Table MAC/VID Entry N (N=0-3) Register (Page 05h: Address 10h).......................................... 186
on
ARL Table Data Entry N (N = 0–3) Register (Page 05h: Address 18h) .............................................. 187
ARL Table Search Control Register (Page 05h: Address 50h) ........................................................... 188
C
ARL Search Address Register (Page 05h: Address 51h) ................................................................... 189
ARL Table Search MAC/VID Result N (N=0-1) Register (Page 05h: Address 60h) ........................... 189
om
ARL Table Search Data Result N (N = 0-1) Register (Page 05h: Address 68h) ................................. 190
VLAN Table Read/Write/Clear Control Register (Page 05h: Address 80h) ........................................ 191
dc
VLAN Table Address Index Register (Page 05h: Address 81h).......................................................... 192
VLAN Table Entry Register (Page 05h: Address 83h–86h) ................................................................ 192
oa
Page 10h–17h: Internal GPHY MII Registers.......................................................................................... 194

MII Control Register (Page 10h–17h: Address 00h–01h) ................................................................... 196
Br
MII Status Register (Page 10h–17h: Address 02h)............................................................................. 197

PHY Identifier Register (Page 10h–17h: Address 04h)....................................................................... 198
Auto-Negotiation Advertisement Register (Page 10h–17h: Address 08h) .......................................... 199
Auto-Negotiation Link Partner Ability Register (Page 10h–17h: Address 0Ah)................................... 200
Next Page .................................................................................................................................... 201
Acknowledge................................................................................................................................ 201
Auto-Negotiation Expansion Register (Page 10h–17h: Address 0Ch)................................................ 201
Next Page Transmit Register (Page 10h–17h: Address 0Eh)............................................................. 202
Link Partner Received Next Page Register (Page 10h–17h: Address 10h)........................................ 203
1000BASE-T Control Register (Page 10h–17h: Address 12h) ........................................................... 204
Test Mode .................................................................................................................................... 204
Broadcom®
April 6, 2016 • 53128-DS07-R Page 12
Master/Slave Configuration Enable.............................................................................................. 205

1000BASE-T Status Register (Page 10h–17h: Address 14h)............................................................. 205
IEEE Extended Status Register (Page 10h–17h: Address 1Eh) ......................................................... 206
PHY Extended Control Register (Page 10h–17h: Address 20h)......................................................... 207
PHY Extended Status Register (Page 10h–17h: Address 22h) .......................................................... 208
Receive Error Counter Register (Page 10h–17h: Address 24h) ......................................................... 209
Copper Receive Error Counter..................................................................................................... 209
False Carrier Sense Counter Register (Page 10h–17h: Address 26h) ............................................... 209
Copper False Carrier Sense Counter........................................................................................... 209
10BASE-T/100BASE-TX/1000BASE-T Packets Received with Transmit Error Codes Counter......... 210
Packets Received with Transmit Error Codes Counter................................................................ 210
Receiver NOT_OK Counter Register (Page 10h–17h: Address 28h) ................................................. 210
l
Copper Local Receiver NOT_OK Counter ................................................................................... 210
tia
Copper Remote Receiver NOT_OK Counter ............................................................................... 210
en
Receive CRC Counter Register (Page 10h–17h: Address 28h) ......................................................... 211
Copper CRC Counter................................................................................................................... 211
fid
Expansion Register Access Register (Page 10h–17h: Address 2Eh)................................................. 211
Expansion Register Select ........................................................................................................... 211
on
Expansion Register Accessed ..................................................................................................... 212
Auxiliary Control Shadow Value Access Register (Page 10h–17h: Address 30h) .............................. 212
C
External Loopback ....................................................................................................................... 213

Receive Extended Packet Length ................................................................................................ 214
om
Edge Rate Control (1000BASE-T) ............................................................................................... 214

Edge Rate Control (100BASE-TX)............................................................................................... 214
dc
Shadow Register Select............................................................................................................... 214

10BASE-T Register ............................................................................................................................. 214
oa
Power/MII Control Register (Page 10h–17h: Address 30h) ................................................................ 215

Super Isolate (Copper Only) ........................................................................................................ 215
Br
Shadow Register Select............................................................................................................... 216

Miscellaneous Test Register (Page 10h–17h: Address 30h) .............................................................. 216
Miscellaneous Control Register (Page 10h–17h: Address 30h).......................................................... 217
Auxiliary Status Summary Register (Page 10h–17h: Address 32h).................................................... 218
Interrupt Status Register (Page 10h–17h: Address 34h) .................................................................... 219
Interrupt Mask Register (Page 10h–17h: Address 36h) ...................................................................... 220
Interrupt Mask Vector................................................................................................................... 220
10BASE-T/100BASE-TX/1000BASE-T Register 38h Access ............................................................. 221
Spare Control 2 Register (Page 10h–17h: Address 38h).................................................................... 221
Auto Power-Down Register (Page 10h–17h: Address 38h) ................................................................ 222
LED Selector 2 Register (Page 10h–17h: Address 38h)..................................................................... 223
Broadcom®
April 6, 2016 • 53128-DS07-R Page 13
Mode Control Register (Page 10h–17h: Address 38h) ....................................................................... 225

Master/Slave Seed Register (Page 10h–17h: Address 3Ah) .............................................................. 226
HCD Status Register (Page 10h–17h: Address 3Ah).......................................................................... 227
Test Register 1 (Page 10h–17h: Address 3Ch) .................................................................................. 228
Expansion Registers ................................................................................................................................ 229
Expansion Register 00h: Receive/Transmit Packet Counter .............................................................. 229
Packet Counter (Copper Only)..................................................................................................... 229
Expansion Register 01h: Expansion Interrupt Status.......................................................................... 229
Transmit CRC Error ..................................................................................................................... 229
Expansion Register 45h: Transmit CRC Enable ................................................................................. 230
Transmit CRC Checker ................................................................................................................ 230
Page 20h–28h: Port MIB Registers ......................................................................................................... 230
l
Page 30h: QoS Registers......................................................................................................................... 235
tia
QoS Global Control Register (Page 30h: Address 00h)...................................................................... 236
en
QoS IEEE 802.1p Enable Register (Page 30h: Address 04h) ............................................................ 236
QoS DiffServ Enable Register (Page 30h: Address 06h).................................................................... 237
fid
Port N (N = 0-7, 8) PCP_To_TC Register (Page 30h: Address 10h) .................................................. 237
DiffServ Priority Map 0 Register (Page 30h: Address 40h) ................................................................. 238
on
DiffServ Priority Map 2 Register (Page 30h: Address 4Ch) ................................................................ 239
C
TC_To_COS Mapping Register (Page 30h: Address 62h–63h) ......................................................... 241
om
CPU_To_COS Map Register (Page 30h: Address 64h–67h) ............................................................. 242

TX Queue Control Register (Page 30h: Address 80h) ........................................................................ 243
dc
TX Queue Weight Register (Page 30h: Address 81h) ........................................................................ 243

COS4 Service Weight Register (Page 30h: Address 85h–86h) .......................................................... 244
oa
Page 31h: Port-Based VLAN Registers .................................................................................................. 245

Port-Based VLAN Control Register (Page 31h: Address 00h) ............................................................ 245
Br
Page 32h: Trunking Registers................................................................................................................. 246

MAC Trunking Control Register (Page 32h: Address 00h) ................................................................. 246
Trunking Group 0 Register (Page 32h: Address 10h) ......................................................................... 247
Trunking Group 1 Register (Page 32h: Address 12h) ......................................................................... 247
Page 34h: IEEE 802.1Q VLAN Registers ................................................................................................ 248
Global IEEE 802.1Q Register (Pages 34h: Address 00h)................................................................... 248
Global IEEE 802.1Q VLAN Control 1 Register (Page 34h: Address 01h)........................................... 250
Global VLAN Control 2 Register (Page 34h: Address 02h)................................................................. 251
Broadcom®
April 6, 2016 • 53128-DS07-R Page 14
VLAN Multiport Address Control Register (Page 34h: Address 0Ah–0Bh) ......................................... 254
Default IEEE 802.1Q Tag Register (Page 34h: Address 10h) ............................................................ 255
Double Tagging TPID Register (Page 34h: Address 30h–31h) .......................................................... 256
ISP Port Selection Portmap Register (Page 34h: Address 32h–33h) ................................................. 256
Page 36h: DOS Prevent Register ............................................................................................................ 257
DOS Control Register (Page 36h: Address 00h–03h)......................................................................... 257
Minimum TCP Header Size Register (Page 36h: Address 04h) ......................................................... 259
Maximum ICMPv4 Size Register (Page 36h: Address 08h–0Bh) ....................................................... 259
Maximum ICMPv6 Size Register (Page 36h: Address 0Ch–0Fh)....................................................... 259
DOS Disable Learn Register (Page 36h: Address 10h) ...................................................................... 259
Page 40h: Jumbo Frame Control Register............................................................................................. 260
Jumbo Frame Port Mask Register (Page 40h: Address 01h).............................................................. 260
l
Standard Max Frame Size Register (Page 40h: Address 05h) ........................................................... 261
tia
Page 41h: Broadcast Storm Suppression Register .............................................................................. 262
en
Ingress Rate Control Configuration Register (Page 41h: Address 00h).............................................. 262
Port Receive Rate Control Register (Page 41h: Address 10h) ........................................................... 264
fid
Port Egress Rate Control Configuration Register (Page 41h: Address 80h–91h)............................... 266
IMP Port Egress Rate Control Configuration Register (Page 41h: Address C0h)............................... 267
on
Page 42h: EAP Register........................................................................................................................... 268
EAP Global Control Register (Page 42h: Address 00h)...................................................................... 269
C
EAP Multiport Address Control Register (Page 42h: Address 01h) .................................................... 269
EAP Destination IP Register 0 (Page 42h: Address 02h) ................................................................... 270
om
EAP Destination IP Register 1 (Page 42h: Address 0Ah) ................................................................... 270

Port EAP Configuration Register (Page 42h: Address 20h)................................................................ 271
dc
Page 43h: MSPT Register ........................................................................................................................ 272

MSPT Control Register (Page 43h: Address 00h) .............................................................................. 272
oa
MSPT Aging Control Register (Page 43h: Address 02h) .................................................................... 272
MSPT Table Register (Page 43h: Address 10h) ................................................................................. 273
Br
SPT Multiport Address Bypass Control Register (Page 43h: Address 50h–51h)................................ 274
Page 70h: MIB Snapshot Control Register ............................................................................................ 275
MIB Snapshot Control Register (Page 70h: Address 00h).................................................................. 275
Page 71h: Port Snapshot MIB Control Register .................................................................................... 275
Page 72h: Loop Detection Register ........................................................................................................ 276
Loop Detection Control Register (Page 72h: Address 00h) ................................................................ 276
Discovery Frame Timer Control Register (Page 72h: Address 02h) ................................................... 276
LED Warning Port Map Register (Page 72h: Address 03h) ................................................................ 277
Module ID 0 Register (Page 72h: Address 05h).................................................................................. 277
Module ID 1 Register (Page 72h: Address 0Bh) ................................................................................. 278
Loop Detect Source Address Register (Page 72h: Address 11h) ....................................................... 278
Broadcom®
April 6, 2016 • 53128-DS07-R Page 15
Page 88h: IMP Port External PHY MII Registers Page Summary ......................................................... 278
Page 90h: BroadSync HD Register ......................................................................................................... 279
BroadSync HD Enable Control Register (Page 90h: Address 00h–01h) ............................................ 280
BroadSync HD Time Stamp Report Control Register (Page 90h: Address 02h) ................................ 280
BroadSync HD PCP Value Control Register (Page 90h: Address 03h) .............................................. 280
BroadSync HD Max Packet Size Register (Page 90h: Address 04h) ................................................. 281
BroadSync HD Time Base Register (Page 90h: Address 10h–13h) ................................................... 281
BroadSync HD Time Base Adjustment Register (Page 90h: Address 14h–17) .................................. 281
BroadSync HD Slot Number and Tick Counter Register (Page 90h: Address 18h–1Bh) ................... 282
BroadSync HD Slot Adjustment Register (Page 90h: Address 1Ch–1Fh) .......................................... 282
BroadSync HD Class 5 Bandwidth Control Register (Page 90h: Address 30h).................................. 283
BroadSync HD Class 4 Bandwidth Control Register (Page 90h: Address 60h).................................. 283
l
BroadSync HD Egress Time Stamp Register (Page 90h: Address 90h)............................................. 284
tia
BroadSync HD Egress Time Stamp Status Register (Page 90h: Address D0h)................................. 284
en
BroadSync HD Link Status Register (Page 90h: Address E0h–E1h).................................................. 285
Page 91h: Traffic Remarking Register.................................................................................................... 286
fid
Traffic Remarking Control Register (Page 91h: Address 00h) ............................................................ 286
Egress Non-BroadSync HD Packet TC to PCP Mapping Register (Page 91h: Address 10h) ............ 287
on
Page 92h: EEE Control Register ............................................................................................................. 288
EEE Enable Control Register (Page 92h: Address 00h) ..................................................................... 288
C
EEE LPI Assert Register (Page 92h: Address 02h) ............................................................................ 289
EEE LPI Indicate Register (Page 92h: Address 04h).......................................................................... 289
om
EEE RX Idle Symbol Register (Page 92h: Address 06h) .................................................................... 289
EEE Pipeline Timer Register (Page 92h: Address 0Ch) ..................................................................... 290
dc
EEE Sleep Timer Gig Register (Page 92h: Address 10h)................................................................... 290
EEE Sleep Timer FE Register (Page 92h: Address 34h).................................................................... 291
oa
EEE Min LP Timer Gig Register (Page 92h: Address 58h)................................................................. 291
EEE Min LP Timer FE Register (Page 92h: Address 7Ch) ................................................................. 292
Br
EEE Wake Timer Gig Register (Page 92h: Address A0h) .................................................................. 292
EEE Wake Timer FE Register (Page 92h: Address B2h) ................................................................... 293
EEE GLB Congst TH Register (Page 92h: Address C4h)................................................................... 293
EEE TXQ Cong TH Register (Page 92h: Address C6h) ..................................................................... 293
Global Registers ....................................................................................................................................... 295
SPI Data I/O Register (Global, Address F0h)...................................................................................... 295
SPI Status Register (Global, Address FEh) ........................................................................................ 295
Page Register (Global, Address FFh) ................................................................................................. 296
Section 8: Electrical Characteristics ............................................................................. 297
Absolute Maximum Ratings .................................................................................................................... 297
Recommended Operating Conditions .................................................................................................... 297
Broadcom®
April 6, 2016 • 53128-DS07-R Page 16
Electrical Characteristics......................................................................................................................... 298

Section 9: Timing Characteristics.................................................................................. 299
Reset and Clock Timing........................................................................................................................... 299
MII Interface Timing.................................................................................................................................. 300
MII Input Timing................................................................................................................................... 300
MII Output Timing................................................................................................................................ 300
TMII Interface Timing................................................................................................................................ 301
TMII Input Timing ................................................................................................................................ 301
TMII Output Timing.............................................................................................................................. 302
Reverse MII/TMII Interface Timing........................................................................................................... 302
Reverse MII/TMII Input Timing ............................................................................................................ 302
Reverse MII Output Timing ................................................................................................................. 303
l
tia
RGMII Interface Timing ............................................................................................................................ 304
RGMII Output Timing (Normal Mode) ................................................................................................. 304
en
RGMII Output Timing (Delayed Mode)................................................................................................ 305
RGMII Input Timing (Normal Mode) .................................................................................................... 306
fid
RGMII Input Timing (Delayed Mode)................................................................................................... 307
GMII Interface Timing ............................................................................................................................... 308
on
GMII Interface Output Timing .............................................................................................................. 308
GMII Interface Input Timing................................................................................................................. 308
C
MDC/MDIO Timing .................................................................................................................................... 309

Serial LED Interface Timing..................................................................................................................... 310
om
SPI Timings ............................................................................................................................................... 311

EEPROM Timing ....................................................................................................................................... 312
dc
Serial Flash Timing................................................................................................................................... 313

Section 10: Thermal Characteristics ............................................................................. 314
oa
Section 11: Mechanical Information .............................................................................. 316

Br
Section 12: Ordering Information .................................................................................. 317
Broadcom®
April 6, 2016 • 53128-DS07-R Page 17
BCM53128 Data Sheet List of Figures
List of Figures
Figure 1: Functional Block Diagram ................................................................................................................... 2
Figure 2: QoS Program Flow ........................................................................................................................... 34
Figure 3: VLAN Table Organization ................................................................................................................. 39
Figure 4: ISP Tag Diagram .............................................................................................................................. 41
Figure 5: Trunking............................................................................................................................................ 44
Figure 6: Bucket Flow ...................................................................................................................................... 45
Figure 7: Mirror Filter Flow ............................................................................................................................... 48
Figure 8: BroadSync HD Shaping and Scheduling .......................................................................................... 54
Figure 9: Address Table Organization ............................................................................................................. 58
Figure 10: IMP Packet Encapsulation Format ................................................................................................. 80
l
tia
Figure 11: TXQ and Buffer Tag Structure ........................................................................................................ 91
Figure 12: RvMII Port Connection.................................................................................................................... 94
en
Figure 13: Normal SPI Command Byte............................................................................................................ 97
Figure 14: Fast SPI Command Byte ................................................................................................................ 97
fid
Figure 15: SPI Serial Interface Write Operation............................................................................................... 98
on
Figure 16: SPI Serial Interface Read Operation .............................................................................................. 98
Figure 17: SPI Interface Without External PHY Device ................................................................................... 98
C
Figure 18: Accessing External PHY Registers................................................................................................. 99

Figure 19: Normal Read Operation ................................................................................................................ 101
om
Figure 20: Normal Read Mode to Check the SPIF Bit of SPI Status Register ............................................... 102
Figure 21: Normal Read Mode to Setup the Accessed Register Page Value................................................ 102
dc
Figure 22: Normal Read Mode to Setup the Accessed Register Address Value (Dummy Read).................. 103
Figure 23: Normal Read Mode to Check the SPI Status for Completion of Read ......................................... 103
oa
Figure 24: Normal Read Mode to Obtain the Register Content ..................................................................... 104
Br
Figure 25: Fast Read Operation .................................................................................................................... 105

Figure 27: Fast Read Mode to Setup New Page Value ................................................................................. 106
Figure 28: Fast Read to Read the Register ................................................................................................... 107
Figure 29: Normal Write Operation ................................................................................................................ 108
Figure 31: Normal Write to Setup the Register Page Value .......................................................................... 109
Figure 32: Normal Write to Write the Register Address Followed by Written Data........................................ 109
Figure 33: Serial EEPROM Connection ......................................................................................................... 110
Figure 34: EEPROM Programming Example................................................................................................. 111
Figure 35: PseudoPHY MII Register Definitions ............................................................................................ 113
Broadcom®
April 6, 2016 • 53128-DS07-R Page 18
BCM53128 Data Sheet List of Figures
Figure 36: PseudoPHY MII Register 16: Register Set Access Control Bit Definition..................................... 114
Figure 37: PseudoPHY MII Register 17: Register Set Read/Write Control Bit Definition .............................. 114
Figure 38: PseudoPHY MII Register 18: Register Access Status Bit Definition ............................................ 115
Figure 39: PseudoPHY MII Register 24: Access Register Bit Definition........................................................ 115
Figure 43: Read Access to the Register Set Using the PseudoPHY (PHYAD = 11110) MDC/MDIO Path ... 117
Figure 44: Write Access to the Register Set Using the PseudoPHY (PHYAD = 11110) MDC/MDIO Path ... 118
Figure 45: LED Interface Register Structure Diagram ................................................................................... 121
Figure 46: LED Interface Block Diagram ....................................................................................................... 122
Figure 47: Dual LED Usage Example ............................................................................................................ 122
l
tia
Figure 48: LED Circuit for Dual Input Configuration/LED Output Pins ........................................................... 123
Figure 49: Reset and Clock Timing................................................................................................................ 299
en
Figure 50: MII Input........................................................................................................................................ 300
fid
Figure 51: MII Output Timing ......................................................................................................................... 300
Figure 52: TMII Input...................................................................................................................................... 301
on
Figure 53: TMII Output Timing ....................................................................................................................... 302
Figure 54: Reverse MII Input Timing.............................................................................................................. 302
C
Figure 55: Reverse MII Output Timing ........................................................................................................... 303

Figure 56: RGMII Output Timing (Normal Mode) ........................................................................................... 304
om
Figure 57: RGMII Output Timing (Delayed Mode) ......................................................................................... 305

Figure 58: RGMII Input Timing (Normal Mode).............................................................................................. 306
dc
Figure 59: RGMII Input Timing (Delayed Mode) ............................................................................................ 307

oa
Figure 60: GMII Output Timings..................................................................................................................... 308

Figure 61: GMII Input Timings ....................................................................................................................... 308
Br
Figure 62: MDC/MDIO Timing (Slave Mode) ................................................................................................. 309

Figure 63: Serial LED Interface Timing .......................................................................................................... 310
Figure 64: SPI Timings, SS Asserted During SCK High ................................................................................ 311
Figure 65: EEPROM Timing .......................................................................................................................... 312
Figure 66: Serial Flash Timing ....................................................................................................................... 313
Figure 67: BCM53128 Mechanical Specifications ......................................................................................... 316
Broadcom®
April 6, 2016 • 53128-DS07-R Page 19
BCM53128 Data Sheet List of Tables
List of Tables
Table 1: TC Decision Tree Summary............................................................................................................... 36
Table 2: Reasons to Forward a Packet to the CPU ......................................................................................... 38
Table 3: Bucket Bit Rate .................................................................................................................................. 47
Table 4: DoS Attacks Detected by BCM53128 ................................................................................................ 51
Table 5: Cable Diagnostic Output .................................................................................................................... 56
Table 6: Unicast Forward Field Definitions ...................................................................................................... 60
Table 7: Address Table Entry for Unicast Address .......................................................................................... 60
Table 8: Multicast Forward Field Definitions .................................................................................................... 61
Table 9: Address Table Entry for Multicast Address ........................................................................................ 61
Table 10: Behavior for Reserved Multicast Addresses .................................................................................... 62
l
tia
Table 11: Flow Control Modes ......................................................................................................................... 70
Table 12: 1000BASE-T External Loopback with External Loopback Plug ....................................................... 77
en
Table 13: 1000BASE-T External Loopback Without External Loopback Plug ................................................. 77
Table 14: 100BASE-TX External Loopback with External Loopback Plug ...................................................... 78
fid
Table 15: 100BASE-TX External Loopback Without External Loopback Plug................................................. 78
on
Table 16: 10BASE-T External Loopback with External Loopback Plug ........................................................... 78
Table 17: 10BASE-T External Loopback Without External Loopback Plug ..................................................... 78
C
Table 18: Egress Broadcom Tag Format (IMP to CPU) .................................................................................. 81

Table 19: Ingress BRCM Tag (CPU to IMP) .................................................................................................... 82
om
Table 20: Receive Only Counter (19) Description of Counter.......................................................................... 83

Table 21: Transmit Counters Only (19) Description of Counter ....................................................................... 85
dc
Table 22: Transmit or Receive Counters (10) Description of Counter ............................................................. 86

Table 23: Directly Supported MIB Counters .................................................................................................... 86
oa
Table 24: Indirectly Supported MIB Counters .................................................................................................. 88

Br
Table 25: BCM53128 Supported MIB Extensions ........................................................................................... 89

Table 26: EEPROM_TYPE[1:0] Settings ....................................................................................................... 110
Table 27: EEPROM Header Format .............................................................................................................. 111
Table 28: EEPROM Contents ........................................................................................................................ 111
Table 29: MII Management Frame Format .................................................................................................... 119
Table 30: LED Output Pins Per Port .............................................................................................................. 120
Table 31: I/O Signal Type Definitions ............................................................................................................ 124
Table 32: Signal Type Definitions .................................................................................................................. 125
Table 33: Global Page Register Map............................................................................................................. 142
Table 34: Control Registers (Page 00h) ........................................................................................................ 144
Table 35: Port Traffic Control Register Address Summary ............................................................................ 146
Broadcom®
April 6, 2016 • 53128-DS07-R Page 20
Table 36: Port Control Register (Page 00h: Address 00h–07h) .................................................................... 146
Table 37: IMP Port Control Register (Page 00h: Address 08h) ..................................................................... 147
Table 38: Switch Mode Register (Page 00h: Address 0Bh)........................................................................... 148
Table 39: IMP Port State Override Register (Page 00h: Address 0Eh) ......................................................... 148
Table 40: LED Control Register Address Summary ...................................................................................... 149
Table 41: LED Refresh Register (Page 00h: Address 0Fh) ........................................................................... 149
Table 42: LED Function 0 Control Register (Page 00h: Address 10h–11h) .................................................. 150
Table 43: LED Function 1 Control Register (Page 00h: Address 12h–13h) .................................................. 151
Table 44: LED Function Map Register (Page 00h: Address 14h–15h) .......................................................... 151
Table 45: LED Enable Map Register (Page 00h: Address 16h–17h) ............................................................ 152
Table 46: LED Mode Map 0 Register (Page 00h: Address 18h–19h)............................................................ 152
Table 47: LED Function Map 1 Control Register (Page 00h: Address 1Ah–1Bh) ......................................... 152
l
tia
Table 48: LED Control Register (Page 00h: Address 1Ch) ........................................................................... 153
Table 49: PHY LED Control Register (Page 00h: Address 1Dh) ................................................................... 153
en
Table 50: Port Forward Control Register (Page 00h: Address 21h) .............................................................. 154
fid
Table 51: Protected Port Selection Register (Page 00h: Address 24h–25h) ................................................. 155
Table 52: WAN Port Select Register (Page 00h: Address 26h–27h)............................................................. 155
on
Table 53: Pause Capability Register (Page 00h: Address 28h–2Bh) ............................................................ 155
Table 54: Reserved Multicast Control Register (Page 00h: Address 2Fh) .................................................... 156
C
Table 55: Unicast Lookup Failed Forward Map Register (Page 00h: Address 32h–33h) .............................. 157
Table 56: Multicast Lookup Failed Forward Map Register (Page 00h: Address 34h–35h)............................ 157
om
Table 57: MLF IMPC Forward Map Register (Page 00h: Address 36h–37h) ................................................ 158
Table 58: Pause Pass Through for RX Register (Page 00h: Address 38h–39h) ........................................... 158
dc
Table 59: Pause Pass Through for TX Register (Page 00h: Address 3Ah–3Bh) .......................................... 158
oa
Table 60: Disable Learning Register (Page 00h: Address 3Ch–3Dh) ........................................................... 159
Table 61: Software Learning Control Register (Page 00h: Address 3Eh–3Fh) ............................................. 159
Br
Table 62: Port State Override Register Address Summary ........................................................................... 160
Table 63: Port State Override Register (Page 00h: Address 58h–5Fh)......................................................... 160
Table 64: IMP RGMII Control Register (Page 00h: Address 60h) ................................................................. 161
Table 65: MDIO IMP PORT Address Register (Page 00h: Address 78h)...................................................... 161
Table 66: Software Reset Control Register (Page 00h: Address 79h) .......................................................... 161
Table 67: Pause Frame Detection Control Register (Page 00h: Address 80h) ............................................. 162
Table 68: Fast-Aging Control Register (Page 00h: Address 88h).................................................................. 162
Table 69: Fast-Aging Port Control Register (Page 00h: Address 89h) .......................................................... 162
Table 70: Fast-Aging VID Control Register (Page 00h: Address 8Ah–8Bh) .................................................. 163
Table 71: CPU Data 0 Share Register (Page 00h: Address B0h–B7h) ......................................................... 163
Table 72: CPU Data 1 Share Register (Page 00h: Address B8h–BFh) ......................................................... 163
Broadcom®
April 6, 2016 • 53128-DS07-R Page 21
Table 73: Status Registers (Page 01h).......................................................................................................... 164

Table 74: Link Status Summary Register (Page 01h: Address 00h–01h) ..................................................... 164
Table 75: Link Status Change Register (Page 01h: Address 02h–03h) ........................................................ 165
Table 76: Port Speed Summary Register (Page 01h: Address 04h–07h) ..................................................... 165
Table 77: Duplex Status Summary Register (Page 01h: Address 08h–09h) ................................................. 166
Table 78: PAUSE Status Summary Register (Page 01h: Address 0Ah–0Dh) ............................................... 166
Table 79: Source Address Change Register (Page 01h: Address 0Eh–0Fh) ................................................ 167
Table 80: Last Source Address Register Address Summary......................................................................... 167
Table 81: Last Source Address (Page 01h: Address 10h–45h)..................................................................... 167
Table 82: Aging/Mirroring Registers (Page 02h)............................................................................................ 168
Table 83: Global Management Configuration Register (Page 02h: Address 00h) ......................................... 169
Table 84: IMP Port ID Register (Page 02h: Address 01h) ............................................................................. 169
l
tia
Table 85: Broadcom Tag Control Register (Page 02h: Address 03h) ........................................................... 170
Table 86: RMON MIB Steering Register (Page 02h: Address 04h–05h) ....................................................... 170
en
Table 87: Aging Time Control Register (Page 02h: Address 06h–09h) ......................................................... 170
fid
Table 88: Mirror Capture Control Register (Page 02h: Address 10h–11h) .................................................... 171
Table 89: Ingress Mirror Control Register (Page 02h: Address 12h–13h) ..................................................... 171
on
Table 90: Ingress Mirror Divider Register (Page 02h: Address 14h–15h) ..................................................... 172
Table 91: Ingress Mirror MAC Address Register (Page 02h: Address 16h–1Bh) .......................................... 172
C
Table 92: Egress Mirror Control Register (Page 02h: Address 1Ch–1Dh) .................................................... 173
Table 93: Egress Mirror Divider Register (Page 02h: Address 1Eh–1Fh) ..................................................... 174
om
Table 94: Egress Mirror MAC Address Register (Page 02h: Address 20h–25h) ........................................... 174
Table 95: Device ID Register (Page 02h: Address 30h–33h) ........................................................................ 174
dc
Table 96: Egress Mirror MAC Address Register (Page 02h: Address 40h) ................................................... 174
oa
Table 97: High-Level Protocol Control Register (Page 02h: Address 50h–53h)............................................ 175
Table 98: Page 03h: Interrupt Control Register ............................................................................................. 177
Br
Table 99: Interrupt Status Register (Page 03h: Address 00h) ....................................................................... 177
Table 100: Interrupt Enable Register (Page 03h: Address 08h) .................................................................... 177
Table 101: IMP Sleep Timer Register (Page 03h: Address 10h) ................................................................... 178
Table 102: Sleep Status Register (Page 03h: Address 18h) ......................................................................... 178
Table 103: External CPU Interrupt Trigger Register (Page 03h: Address 20h) ............................................. 178
Table 104: ARL Control Registers (Page 04h) .............................................................................................. 179
Table 105: Global ARL Configuration Register (Page 04h: Address 00h) ..................................................... 180
Table 106: BPDU Multicast Address Register (Page 04h: Address 04h–09h) .............................................. 180
Table 107: Multiport Control Register (Page 04h: Address 0Eh–0Fh)........................................................... 181
Table 108: Multiport Address Register Address Summary ............................................................................ 182
Table 109: Multiport Address Register (Page 04h: Address 10h–17h, 20h–27h, 30h–37h, 40h–47h, 50h–57h,
Broadcom®
April 6, 2016 • 53128-DS07-R Page 22
60h–67h)....................................................................................................................................... 182
Table 110: Multiport Vector Register Address Summary ............................................................................... 183
Table 111: Multiport Vector Register (Page 04h: Address 18h–1Bh, 28h–2Bh, 38h–3Bh, 48h–4Bh, 58h–5Bh,
68h–6Bh) ...................................................................................................................................... 183
Table 112: ARL/VTBL Access Registers (Page 05h) .................................................................................... 184
Table 113: ARL Table Read/Write Control Register (Page 05h: Address 00h) ............................................. 185
Table 114: MAC Address Index Register (Page 05h: Address 02h–07h)...................................................... 185
Table 115: VLAN ID Index Register (Page 05h: Address 08h–09h) .............................................................. 186
Table 116: ARL Table MAC/VID Entry N (N=0-3) Register Address Summary............................................. 186
Table 117: ARL Table MAC/VID Entry N (N=0-3) Register (Page 05h: Address 10h–17h, 20h–27h, 30h–37h,
40h–47h)....................................................................................................................................... 186
Table 118: ARL Table Data Entry N (N=0-3) Register Address Summary .................................................... 187
l
tia
Table 119: ARL Table Data Entry N (N=0-3) Register (Page 05h: Address 18h–1Bh, 28h–2Bh, 38h–3Bh, 48h–
4Bh) .............................................................................................................................................. 187
en
Table 120: ARL Table Search Control Register (Page 05h: Address 50h).................................................... 188
Table 121: ARL Search Address Register (Page 05h: Address 51h–52h) .................................................... 189
fid
Table 122: ARL Table Search MAC/VID Result N (N=0-1) Register Address Summary............................... 189
Table 123: ARL Table Search MAC/VID Result N (N=0-1) Register (Page 05h: Address 60h–67h,
on
70h–77h)....................................................................................................................................... 189
Table 124: ARL Table Search Data Result N (N=0-1) Register Address Summary ...................................... 190
C
Table 125: ARL Table Search Data Result N (N=0-1) Register (Page 05h: Address 68h–6Bh, 78h–7Bh)... 190
om
Table 126: VLAN Table Read/Write/Clear Control Register (Page 05h: Address 80h) ................................. 191
Table 127: VLAN Table Address Index Register (Page 05h: Address 81h–82h) .......................................... 192
Table 128: VLAN Table Entry Register (Page 05h: Address 83h–86h) ......................................................... 192
dc
Table 129: 10/100/1000 PHY Page Summary............................................................................................... 194

oa
Table 130: Register Map (Page 10h–17h)..................................................................................................... 194

Table 131: MII Control Register (Page 10h–17h: Address 00h–01h) ............................................................ 196
Br
Table 132: MII Status Register (Page 10h–17h: Address 02h–03h) ............................................................. 197
Table 133: PHY Identifier Register MSB (Page 10h–17h: Address 04–07h)................................................. 198
Table 134: PHY Identifier Register LSB (Page 10h–17h: Address 06h–07h)................................................ 198
Table 135: Auto-Negotiation Advertisement Register (Page 10h–17h: Address 08h–09h) ........................... 199
Table 136: Auto-Negotiation Link Partner Ability Register (Page 10h–17h: Address 0Ah–0Bh) ................... 200
Table 137: Auto-Negotiation Expansion Register (Page 10h–17h: Address 0Ch–0Dh) ................................ 201
Table 138: Next Page Transmit Register (Page 10h–17h: Address 0Eh–0Fh) ............................................. 202
Table 139: Link Partner Received Next Page Register (Page 10h–17h: Address 10h–11h) ........................ 203
Table 140: 1000BASE-T Control Register (Page 10h–17h: Address 12h–13h) ............................................ 204
Table 141: 1000BASE-T Status Register (Page 10h–17h: Address 14h–15h) ............................................. 205
Broadcom®
April 6, 2016 • 53128-DS07-R Page 23
Table 142: IEEE Extended Status Register (Page 10h–17h: Address 1Eh–1Fh) ......................................... 206
Table 143: PHY Extended Control Register (Page 10h–17h: Address 20h–21h) ......................................... 207
Table 144: PHY Extended Status Register (Page 10h–17h: Address 22h–23h) ........................................... 208
Table 145: Receive Error Counter Register (Page 10h–17h: Address 24h–25h) .......................................... 209
Table 146: False Carrier Sense Counter Register (Page 10h–17h: Address 26h–27h) ................................ 209
Table 147: 10BASE-T/100BASE-TX/1000BASE-T Transmit Error Code Counter Register (Address 13h) .. 210
Table 148: Receiver NOT_OK Counter Register (Page 10h–17h: Address 28h–29h) .................................. 210
Table 149: CRC Counter Register (Page 10h–17h: Address 28h–29h) ........................................................ 211
Table 150: Expansion Register Access Register (Page 10h–17h: Address 2Eh–2Fh) ................................. 211
Table 151: Expansion Register Select Values ............................................................................................... 212
Table 152: Auxiliary Control Shadow Values Access Register (Page 10h–17h: Address 30h) ..................... 212
Table 153: Reading Register 30h .................................................................................................................. 212
l
tia
Table 154: Writing Register 30h .................................................................................................................... 213
Table 155: Auxiliary Control Register (Page 10h–17h: Address 30h, Shadow Value 000) ........................... 213
en
Table 156: 10BASE-T Register (Page 10h–17h: Address 30h, Shadow Value 001) .................................... 214
fid
Table 157: Power/MII Control Register (Page 10h–17h: Address 30h, Shadow Value 010)......................... 215
Table 158: Miscellaneous Test Register (Page 10h–17h: Address 30h, Shadow Value 100)....................... 216
on
Table 159: Miscellaneous Control Register (Page 10h–17h: Address 30h, Shadow Value 111) .................. 217
Table 160: Auxiliary Status Summary Register (Page 10h–17h: Address 32h–33h) .................................... 218
C
Table 161: Interrupt Status Register (Page 10h–17h: Address 34h–35h) ..................................................... 219
Table 162: Interrupt Mask Register (Page 10h–17h: Address 36h)............................................................... 220
om
Table 163: 10BASE-T/100BASE-TX/1000BASE-T Register 38h Shadow Values ........................................ 221

Table 164: Spare Control 2 Register (Page 10h–17h: Address 38h, Shadow Value 00100) ........................ 221
dc
Table 165: Auto Power-Down Register (Page 10h–17h: Address 38h, Shadow Value 01010) .................... 222
oa
Table 166: LED Selector 2 Register (Page 10h–17h: Address 38h, Shadow Value 01110) ......................... 223
Table 167: Mode Control Register (Page 10h–17h: Address 38h, Shadow Value 11111) ............................ 225
Br
Table 168: Master/Slave Seed Register (Page 10h–17h: Address 3Ah–3Bh) Bit 15 = 0 .............................. 226
Table 169: HCD Status Register (Page 10h–17h: Address 3Ah–3Bh) Bit 15 = 1.......................................... 227
Table 170: Test Register 1 (Page 10h–17h: Address 3C–3Dh) .................................................................... 228
Table 171: Expansion Register 00h: Receive/Transmit Packet Counter ....................................................... 229
Table 172: Expansion Register 01h: Expansion Interrupt Status .................................................................. 229
Table 173: Expansion Register 45h: Transmit CRC ...................................................................................... 230
Table 174: Port MIB Registers Page Summary ............................................................................................. 230
Table 175: Page 20h–28h Port MIB Registers .............................................................................................. 230
Table 176: Page 30h QoS Registers ............................................................................................................. 235
Table 177: QoS Global Control Register (Page 30h: Address 00h) .............................................................. 236
Table 178: QoS.1P Enable Register (Page 30h: Address 04h–05h) ............................................................. 236
Broadcom®
April 6, 2016 • 53128-DS07-R Page 24
Table 179: QoS DiffServ Enable Register (Page 30h: Address 06h–07h) .................................................... 237
Table 180: Port N (N=0-7,8) PCP_To_TC Register Address Summary ........................................................ 237
Table 181: Port N (N=0-7,8) PCP_To_TC Register (Page 30h: Address 10h–33h)...................................... 237
Table 182: DiffServ Priority Map 0 Register (Page 30h: Address 40h–45h).................................................. 238
Table 183: DiffServ Priority Map 1 Register (Page 30h: Address 46h–4Bh) ................................................. 239
Table 184: DiffServ Priority Map 2 Register (Page 30h: Address 4Ch–51h) ................................................. 239
Table 185: DiffServ Priority Map 3 Register (Page 30h: Address 52h–57h).................................................. 240
Table 186: TC_To_COS Mapping Register (Page 30h: Address 62h–63h) .................................................. 241
Table 187: CPU_To_COS Map Register (Page 30h: Address 64h–67h) ...................................................... 242
Table 188: TX Queue Control Register (Page 30h: Address 80h)................................................................. 243
Table 189: TX Queue Weight Register Queue[0:3] (Page 30h: Address 81h–84h) ...................................... 243
Table 190: COS4 Service Weight Register (Page 30h: Address 85h–86h)................................................... 244
l
tia
Table 191: Page 31h VLAN Registers ........................................................................................................... 245
Table 192: Port-Based VLAN Control Register Address Summary ............................................................... 245
en
Table 193: Port VLAN Control Register (Page 31h: Address 00h–11h) ........................................................ 245
fid
Table 194: Page 32h Trunking Registers ...................................................................................................... 246
Table 195: MAC Trunk Control Register (Page 32h: Address 00h) ............................................................... 246
on
Table 196: Trunk Group 0 Register (Page 32h: Address 10h–11h) .............................................................. 247
Table 197: Trunk Group 1 Register (Page 32h: Address 12h–13h) .............................................................. 247
C
Table 198: Page 34h IEEE 802.1Q VLAN Registers ..................................................................................... 248
Table 199: Global IEEE 802.1Q Register (Pages 34h: Address 00h) ........................................................... 248
om
Table 200: Global VLAN Control 1 Register (Page 34h: Address 01h) ......................................................... 250
dc
Table 202: Global VLAN Control 3 Register (Page 34h: Address 03h–04h) ................................................. 251
oa
Br
Table 205: VLAN Multiport Address Control Register (Page 34h: Address 0Ah–0Bh) .................................. 254
Table 206: Default IEEE 802.1Q Tag Register Address Summary ............................................................... 255
Table 207: Default IEEE 802.1Q Tag Register (Page 34h: Address 10h–21h) ............................................. 255
Table 208: Double Tagging TPID Register (Page 34h: Address 30h–31h) ................................................... 256
Table 209: ISP Port Selection Portmap Register (Page 34h: Address 32h–33h) .......................................... 256
Table 210: DOS Prevent Register ................................................................................................................. 257
Table 211: DOS Control Register (Page 36h: Address 00h–03h) ................................................................. 257
Table 212: Minimum TCP Header Size Register (Page 36h: Address 04h) .................................................. 259
Table 213: Maximum ICMPv4 Size Register (Page 36h: Address 08h-0Bh)................................................. 259
Table 214: Maximum ICMPv6 Size Register (Page 36h: Address 0Ch-0Fh) ................................................ 259
Table 215: DOS Disable Learn Register (Page 36h: Address 08h-0Bh) ....................................................... 259
Broadcom®
April 6, 2016 • 53128-DS07-R Page 25
Table 216: Page 40h Jumbo Frame Control Register ................................................................................... 260
Table 217: Jumbo Frame Port Mask Registers (Page 40h: Address 01h–04h) ............................................ 260
Table 218: Standard Max Frame Size Registers (Page 40h: Address 05h–06h) .......................................... 261
Table 219: Broadcast Storm Suppression Register (Page 41h) .................................................................... 262
Table 220: Ingress Rate Control Configuration Register (Page 41h: Address 00h–03h) .............................. 262
Table 221: Port Rate Control Register Address Summary ............................................................................ 264
Table 222: Port Rate Control Register (Page 41h: Address 10h–33h) .......................................................... 264
Table 223: Port Egress Rate Control Configuration Register Address Summary.......................................... 266
Table 224: Port Egress Rate Control Configuration Registers (Page 41h: Address 80h–91h) ..................... 266
Table 225: IMP Port Egress Rate Control Configuration Register Address Summary .................................. 267
Table 226: IMP Port Egress Rate Control Configuration Registers (Page 41h: Address C0h) ..................... 267
Table 227: Using Rate_Index to Configure Different Egress Rates for IMP in pps ....................................... 268
l
tia
Table 229: EAP Global Control Registers (Page 42h: Address 00h)............................................................. 269
en
Table 230: EAP Multiport Address Control Register (Page 42h: Address 01h) ............................................. 269
fid
Table 231: EAP Destination IP Registers 0 (Page 42h: Address 02h–09h) .................................................. 270
Table 232: EAP Destination IP Registers 1 (Page 42h: Address 0Ah–12h) .................................................. 270
on
Table 233: Port EAP Configuration Register Address Summary ................................................................... 271
Table 234: Port EAP Configuration Registers (Page 42h: Address 20h–47h)............................................... 271
C
Table 236: MSPT Control Registers (Page 43h: Address 00h–01h) ............................................................. 272
om
Table 237: MSPT Aging Control Registers (Page 43h: Address 02h–05h) ................................................... 272
Table 238: MSPT Table Register Address Summary .................................................................................... 273
dc
Table 239: MSPT Table Registers (Page 43h: Address 10h–2Fh)................................................................ 273
oa
Table 240: SPT Multiport Address Bypass Control Register (Page 43h: Address 50h–51h) ........................ 274
Table 241: MIB Snapshot Control Register ................................................................................................... 275
Br
Table 242: MIB Snapshot Control Register (Page 70h: Address 00h) .......................................................... 275
Table 243: Port Snapshot MIB Control Register ............................................................................................ 275
Table 244: Loop Detection Control Register (Page 72h) ............................................................................... 276
Table 245: Loop Detection Control Registers (Page 72h: Address 00h–01h) ............................................... 276
Table 246: Discovery Frame Timer Control Registers (Page 72h: Address 02h) .......................................... 276
Table 247: LED Warning Port Map Registers (Page 72h: Address 03h–04h) ............................................... 277
Table 248: Module ID 0 Registers (Page 72h: Address 05h–0Ah) ................................................................ 277
Table 249: Module ID 1 Registers (Page 72h: Address 0Bh–10h) ................................................................ 278
Table 250: Loop Detect Source Address Registers (Page 72h: Address 11h–16h) ...................................... 278
Table 251: IMP Port External PHY MII Registers Page Summary ................................................................ 278
Table 252: BroadSync HD Register ............................................................................................................... 279
Broadcom®
April 6, 2016 • 53128-DS07-R Page 26
Table 253: BroadSync HD Enable Control Register (Page 90h: Address 00h–01h) ..................................... 280
Table 254: BroadSync HD Time Stamp Report Control Register (Page 90h: Address 02h) ......................... 280
Table 255: BroadSync HD PCP Value Control Register (Page 90h: Address 03h)....................................... 280
Table 256: BroadSync HD Max Packet Size Register (Page 90h: Address 04h) .......................................... 281
Table 257: BroadSync HD Time Base Register (Page 90h: Address 10h–13h)............................................ 281
Table 258: BroadSync HD Time Base Adjustment Register (Page 90h: Address 14h–17h)......................... 281
Table 259: BroadSync HD Slot Number and Tick Counter Register (Page 90h: Address 18h–1Bh) ............ 282
Table 260: BroadSync HD Slot Adjustment Register (Page 90h: Address 1Ch–1Fh) ................................... 282
Table 261: BroadSync HD Class 5 Bandwidth Control Register Address Summary ..................................... 283
Table 262: BroadSync HD Class 5 Bandwidth Control Register (Page 90h: Address 30h–31h, 32h–33h, 34h–
35h, 36h–37h, 38h–39h)............................................................................................................... 283
Table 263: BroadSync HD Class 4 Bandwidth Control Register Address Summary ..................................... 283
l
tia
Table 264: BroadSync HD Class 4 Bandwidth Control Register (Page 90h: Address 60h–61h, 62h–63h, 64h–
65h, 66h–67h, 68h–69h)............................................................................................................... 284
en
Table 265: BroadSync HD Egress Time Stamp Register Address Summary................................................ 284
Table 266: BroadSync HD Egress Time Stamp Register (Page 90h: Address 90h–93h, 94h–97h, 98h–9Bh,
fid
9Ch–9Fh, A0h–A3h, A4h–A7h) .................................................................................................... 284
Table 267: BroadSync HD Egress Time Stamp Status Register (Page 90h: Address D0h) ......................... 284
on
Table 268: BroadSync HD Link Status Register (Page 90h: Address E0h–E1h) ......................................... 285
Table 269: Traffic Remarking Register .......................................................................................................... 286
C
Table 270: Traffic Remarking Control Register (Page 91h: Address 00h)..................................................... 286
om
Table 271: Egress Non-BroadSync HD Packet TC to PCP Mapping Register Address Summary ............... 287
Table 272: Egress Non-BroadSync HD Packet TC to PCP Mapping Register (Page 91h: Address 10h–17h,
18h–1Fh, 20h–27h, 28h–2Fh, 30h–37h, 38h–3Fh, 50h-57h)....................................................... 287
dc
Table 273: Page 92h: EEE Control Register ................................................................................................. 288

oa
Table 274: EEE Enable Control Register (Page 92h: Address 00h).............................................................. 288
Table 275: EEE LPI Assert Register (Page 92h: Address 02h) ..................................................................... 289
Br
Table 276: EEE LPI Indicate Register (Page 92h: Address 04h) .................................................................. 289
Table 277: EEE RX Idle Symbol Register (Page 92h: Address 06h)............................................................. 289
Table 278: EEE Pipeline Timer Register (Page 92h: Address 0Ch) .............................................................. 290
Table 279: EEE Sleep Timer Gig Register (Page 92h: Address 10h) ........................................................... 290
Table 280: EEE Sleep Timer Gig Register (Page 92h: Address 10h) ........................................................... 290
Table 281: EEE Sleep Timer FE Register (Page 92h: Address 34h) ............................................................ 290
Table 282: EEE Sleep Timer FE Register (Page 92h: Address 34h) ............................................................ 291
Table 283: EEE Min LP Timer Gig Register (Page 92h: Address 58h) ......................................................... 291
Table 284: EEE Min LP Timer Gig Register (Page 92h: Address 58h) ......................................................... 291
Table 285: EEE Min LP Timer FE Register (Page 92h: Address 7Ch) .......................................................... 291
Broadcom®
April 6, 2016 • 53128-DS07-R Page 27
Table 286: EEE Min LP Timer FE Register (Page 92h: Address 7Ch) .......................................................... 292
Table 287: EEE Wake Timer Gig Register (Page 92h: Address A0h) ........................................................... 292
Table 288: EEE Wake Timer Gig Register (Page 92h: Address A0h) ........................................................... 292
Table 289: EEE Wake Timer FE Register (Page 92h: Address B2h) ............................................................ 292
Table 290: EEE Wake Timer FE Register (Page 92h: Address B2h) ............................................................ 293
Table 291: EEE GLB Congst TH Register (Page 92h: Address C4h) ........................................................... 293
Table 292: EEE TXQ CONG TH Register (Page 92h: Address C6h) ............................................................ 293
Table 293: EEE TXQ Cong TH Register (Page 92h: Address C6h) .............................................................. 293
Table 294: Global Registers (Maps to All Pages) ......................................................................................... 295
Table 295: SPI Data I/O Register (Maps to All Registers, Address F0h–F7h) .............................................. 295
Table 296: SPI Status Register (Maps to All Registers, Address FEh) ......................................................... 295
Table 297: Page Register (Maps to All Registers, Address FFh) .................................................................. 296
l
tia
Table 298: Absolute Maximum Ratings ......................................................................................................... 297
Table 299: Recommended Operating Conditions .......................................................................................... 297
en
Table 300: Electrical Characteristics.............................................................................................................. 298
fid
Table 301: Reset and Clock Timing ............................................................................................................... 299
Table 302: MII Input Timing ........................................................................................................................... 300
on
Table 303: MII Output Timing ........................................................................................................................ 301
Table 304: TMII Input Timing ......................................................................................................................... 301
C
Table 305: TMII Output Timing ...................................................................................................................... 302

Table 306: Reverse MII Input Timing ............................................................................................................. 302
om
Table 307: Reverse TMII Input Timing........................................................................................................... 303

Table 308: Reverse MII Output Timing .......................................................................................................... 303
dc
Table 309: Reverse TMII Output Timing ........................................................................................................ 303

oa
Table 310: RGMII Output Timing (Normal Mode) .......................................................................................... 304

Table 311: RGMII Output Timing (Delayed Mode) ........................................................................................ 305
Br
Table 312: RGMII Input Timing (Normal Mode) ............................................................................................. 306

Table 313: RGMII Input Timing (Delayed Mode) ........................................................................................... 307
Table 314: GMII Output Timing...................................................................................................................... 308
Table 315: GMII Input Timing ........................................................................................................................ 309
Table 316: MDC/MDIO Timing (Slave Mode) ................................................................................................ 309
Table 317: MDC/MDIO Timing (Master Mode) .............................................................................................. 309
Table 318: Serial LED Interface Timing ......................................................................................................... 310
Table 319: SPI Timings.................................................................................................................................. 311
Table 320: EEPROM Timing.......................................................................................................................... 312
Table 321: Serial Flash Timing ...................................................................................................................... 313
Table 322: BCM53128KQLE Package without Heat Sink, 4-Layer Board, P = 3.1W.................................... 314
Broadcom®
April 6, 2016 • 53128-DS07-R Page 28
Table 323: BCM53128KQLE Package with Heat Sink, 2-Layer Board, P = 3.1W......................................... 314
Table 324: BCM53128IQLE Package with Heat Sink, 4-layer Board, P=3.1W ............................................. 315
Table 325: Ordering Information .................................................................................................................... 317
l
tia
en
fid
on
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 29
BCM53128 Data Sheet About This Document
About This Document
Purpose and Audience

This document is for designers interested in integrating the BCM53128 switches into their hardware designs and
for others who need specific data about the physical characteristics and operation of the BCM53128 switches.
Acronyms and Abbreviations

In most cases, acronyms and abbreviations are defined on first use.
For a comprehensive list of acronyms and other terms used in Broadcom documents, go to:
http://www.broadcom.com/press/glossary.php.
l
tia
Document Conventions
en
The following notational conventions are used in this document:
• Signal names are shown in uppercase letters (such as DATA).
•
•
fid
A bar over a signal name indicates that it is active low (such as CE).
In register and signal descriptions, [n:m] indicates a range from bit n to bit m (such as [7:0] indicates bits 7
on
through 0, inclusive).
• The use of R or Reserved indicates that a bit or a field is reserved by Broadcom for future use. Typically, R
C
is used for individual bits and Reserved is used for fields.

• Numerical modifiers such as K or M follow traditional usage (for example, 1 KB means 1,024 bytes,
om
100 Mbps [referring to fast Ethernet speed] means 100,000,000 bps, and 133 MHz means 133,000,000
Hz).
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 30
BCM53128 Data Sheet Technical Support
References
The references in this section may be used in conjunction with this document.
Note: Broadcom provides customer access to technical documentation and software through its
Customer Support Portal (CSP) and Downloads and Support site (see Technical Support).
For Broadcom documents, replace the “xx” in the document number with the largest number available in the
repository to ensure that you have the most current version of the document.
Document (or Item) Name Number Source

Broadcom Items
[1] Layout and Design Guide 53128-AN1xx-R CSP
l
[2] BCM53128 Programmer's Reference Guide 53128-PG1xx-R CSP
tia
en
Technical Support
fid
Broadcom provides customer access to a wide range of information, including technical documentation,
schematic diagrams, product bill of materials, PCB layout information, and software updates through its
on
customer support portal (https://support.broadcom.com). For a CSP account, contact your Sales or Engineering
support representative.
C
In addition, Broadcom provides other product support through its Downloads and Support site
(http://www.broadcom.com/support/).
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 31
BCM53128 Data Sheet Introduction
Section 1: Introduction
Overview
The BCM53128 is a single-chip, 9-port Gigabit Ethernet (GbE) switch device. It provides:
• A 9-port nonblocking 10/100/1000-Mbps switch controller
• Eight ports with 10/100/1000BASE-TX-compatible transceivers
• Nine integrated Gigabit MACs (GMACs)
• One GMII/RGMII/MII/RvMII/TMII/RvTMII port for PHY-less connection to the management agent
• An integrated Motorola SPI-compatible interface
• High performance, integrated packet buffer memory
l
tia
• An address resolution engine
• A set of management information base (MIB) statistics registers
en
The GMACs support full-duplex and half-duplex modes for 10 Mbps and 100 Mbps and full-duplex for
1000 Mbps. Flow control is supported in the half-duplex mode with backpressure. In full-duplex mode, IEEE
fid
802.3x frame-based flow control is supported. The GMACs are IEEE 802.3-compliant and support maximum
frame sizes of 9720 bytes.
on
An integrated address management engine provides address learning and recognition functions at maximum
frame rates. The address table provides capacity for learning up to 4K unicast addresses. Addresses are added
C
to the table after receiving an error-free packet.

om
The MIB statistics registers collect receive and transmit statistics for each port and provide direct hardware
support for the Ether-like MIB, MIB II (interfaces), and the first four groups of the RMON MIB. All nine groups of
RMON can be supported by using additional capabilities, such as port mirroring/snooping, together with an
dc
external microcontroller to process some MIB attributes. The MIB registers can be accessed through the Serial
Peripheral Interface Port by an external microcontroller.
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 32
BCM53128 Data Sheet Features and Operation
Section 2: Features and Operation
Overview of Features and Operation

The BCM53128 switches include the following features:
• “Quality of Service” on page 34
• “Port-Based VLAN” on page 38
• “IEEE 802.1Q VLAN” on page 39
• “Programming the VLAN Table” on page 40
• “Double-Tagging” on page 41
• “Jumbo Frame Support” on page 44
l
tia
• “Port Trunking/Aggregation” on page 44
• “WAN Port” on page 45
en
• “Rate Control” on page 45
• “Protected Ports” on page 47
•
•
“Port Mirroring” on page 48
“IGMP Snooping” on page 49
fid
on
• “MLD Snooping” on page 50
• “IEEE 802.1x Port-Based Security” on page 50
C
• “DoS Attack Prevention” on page 51

om
• “MSTP Multiple Spanning Tree” on page 52

• “Software Reset” on page 52
• “Loop Detection” on page 52
dc
• “BroadSync HD” on page 53

oa
• “CableChecker™” on page 56
• “Egress PCP Remarking” on page 57
Br
• “Address Management” on page 57

• “Power Savings Modes” on page 65
The following sections discuss each feature in more detail.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 33
BCM53128 Data Sheet Quality of Service
Quality of Service
The Quality of Service (QoS) feature provides up to six internal queues per port to support six different traffic
classes (TC). The traffic classes can be programmed so that higher-priority TC in the switch experiences less
delay than lower-priority TC under congested conditions. This can be important in minimizing latency for delay-
sensitive traffic. The BCM53128 switches can assign the packet to one of the six egress transmit queues
according to information in:
• “Port-Based QoS” on page 35 (ingress port ID)
• “IEEE 802.1p QoS” on page 35
• “MACDA-Based QoS” on page 36
• “TOS/DSCP QoS” on page 36
The “TC Decision Tree” on page 36 decides which priority system is used based on three programmable register
bits detailed in Table 1: “TC Decision Tree Summary,” on page 36. The corresponding traffic class is then
l
tia
assigned to one of the six queues on a port-by-port basis.
Figure 2: QoS Program Flow
en
fid
Port -Based Traffic Class Mapping
on
IEEE 802.1p Traffic Class Mapping
C
Incoming MACDA-Based Traffic Class Mapping TC Decision

Packet Tree
om
TOS/DSCP Based Traffic Class Mapping

dc
oa
COS 5
Br
BroadSync HD Traffic Class

traffic only
COS 4
BroadSync HD
traffic only
SP/WRR Algorithm
COS 3
Outgoing COS
PCP/DSCP
Queue
Packet Remarking
ID
COS 2 COS Mapping
COS 1
COS 0
Broadcom®
April 6, 2016 • 53128-DS07-R Page 34
Egress Transmit Queues

Each Ethernet egress port has six transmit queues (COS0–COS5). The COS4 and COS5 are dedicated to
BroadSync® HD traffic only and can not be shared with other traffic. Each COS queue has its own dedicated
counter to measure the buffer occupancy of the queue for congestion management purpose. Every Ethernet
(ingress) port has its own set of counters to measure the buffer occupancy and the arrival rate related to the
traffic received from the port.
The IMP (egress) port serves four queues (COS0–COS3) and the traffic generated by the Local Management
Packet Generator which generate management report messages back to CPU, e.g., the Time Sync TX time
stamp packets.
Each COS queue has its own dedicated counter to measure the buffer occupancy of the queue for congestion
management purpose. The IMP (ingress) port also has its own set of counters to measure the buffer occupancy
and the arrival rated to the traffic received from the port, but should be used only if it is configured as a regular
Ethernet port.
l
tia
All incoming frames are assigned to an egress transmit queue depending on their assigned TC. Each egress
transmit queue is a list specifying an order for packet transmission. The corresponding egress port transmits
en
packets from each of the queues according to a programmable algorithm, with the higher TC queues being given
greater access than the lower TC queues. Queue 0 is the lowest-TC queue.
fid
The COS0–COS3 queues are dedicated to non-BroadSync HD traffic only and as programmed in the TX Queue
Control register. The BCM53128 uses strict priority (SP) and weighted round robin (WRR) algorithm for COS0–
on
COS3 queues scheduling. The scheduling is configurable using the TX Queue Control register as one of
following combinations of SP and WRR; 4SP, 4WRR, 1SP and 3WRR, 2SP and 2WRR The WRR algorithm
C
weights for each queue can be programmed using the TX Queue Weight register.
om
Port-Based QoS
The TC of a packet received from an Ethernet (or IMP) port is assigned with the TC configured for the
dc
corresponding port. The mapping mechanism is globally enabled/disabled by programming the QoS Global
Control register; the mapping entry is also per-port configured using the Default IEEE 802.1Q Tag register.
oa
When disabled, the TC that results from this mapping is 000.

Br
IEEE 802.1p QoS

The TC of a packet received from an Ethernet (or IMP) port is assigned with TC-configured for the corresponding
IEEE 802.1p priority code point (PCP). The mapping mechanism is per port enabled/disabled using QoS IEEE
802.1p Enable register, the mapping entries are per-port configured by Port N (N = 0–7, 8) PCP_To_TC register.
When disabled or if the incoming packet is not tagged, the TC that results from this mapping is 000.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 35
MACDA-Based QoS
MACDA-Based QoS is enabled when the IEEE 802.1p QoS is disabled using the 802_1P_EN bit in the QoS
IEEE 802.1p Enable register. When using MACDA-based QoS, the destination address and VLAN ID is used
to index the ARL table as described in “Address Management” on page 57. The matching ARL entry contains a
3-bit TC field as shown in Table 7 on page 60. These bits set the MACDA-based TC for the frame. The MACDA-
based TC is assigned to the TC bits depending upon the result shown in Table 1. The TC for the frame is
mapped to one of the egress transmit queues base on the ingress port using the TC_To_COS Mapping register.
The TC bits for a learned ARL entry default to 0. To change the default, an ARL entry is written to the ARL table
as described in the “Writing an ARL Entry” on page 63. For more information about the egress transmit queues,
see “Egress Transmit Queues” on page 35.
TOS/DSCP QoS
The TC of a packet received from an Ethernet (or IMP) port is assigned with TC configured for the corresponding
l
IP TOS/DSCP. The mapping mechanism is per port enabled/disabled using QoS DiffServ Enable register, the
tia
mapping entries are globally configured by DiffServ Priority Map 0 register through DiffServ Priority Map 3
register. When disabled or the incoming packet is not of IPv4/v6 type, the TC resulted from this mapping is 000.
en
TC Decision Tree
fid
on
Non-BroadSync HD Frame
The TC decision tree determines which priority system is assigned to TC-mapping bits for the given frame. As
C
summarized above, the TC bits for the frame can be determined according to the ingress port-based TC, IEEE
802.1p TC, MACDA-based TC, DiffServ TC or MACSA-based TC information. The decision on which TC
om
mapping to use is based on the Port_QoS_En bit and the QoS_Layer_Sel bits of the QoS Global Control
register. Table 1 summarizes how these programmable bits affect the derived TC. The DiffServ and IEEE 802.1p
QoS TC are only available if the respective QoS is enabled, and the received packet has the appropriate
dc
tagging.
oa
Table 1: TC Decision Tree Summary

Br
Port_QoS QoS_Layer
_En _Sel Value of TC Bits
0 00 IEEE 802.1p TC mapping if available; otherwise, MACDA-based TC mapping.
0 01 DiffServ TC mapping if available; otherwise, TC = 000.
0 10 DiffServ TC mapping for IP frame; otherwise, IEEE 802.1p TC mapping if
available; otherwise, MACDA-based TC mapping.
0 11 The highest available TC of the following: IEEE 802.1p TC mapping, DiffServ
TC mapping, MACDA-based TC mapping or MACSA-based TC mapping.
1 00 MACSA-based TC mapping if available; otherwise, Port-based TC mapping.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 36
Table 1: TC Decision Tree Summary (Cont.)
Port_QoS QoS_Layer
_En _Sel Value of TC Bits
1 11 The highest available TC of the following: Port-based TC mapping, MACSA-
based TC mapping, IEEE 802.1p TC mapping, DiffServ TC mapping or
MACDA-based TC mapping.
BroadSync HD Frame
For the BroadSync HD packet from an Ethernet port, the TC is determined directly from the explicit IEEE
802.1Q/P tag carried in the BroadSync HD packets (BroadSync HD packets are expected to always be tagged),
which is independent of Table 1 on page 36 TC mapping.
The conditions deciding whether an incoming packet is BroadSync HD are:

1. The port from which the packet is received is configured as BroadSync HD-enabled.
l
tia
2. The packet received is either VLAN tagged or priority tagged, with PCP = 4 or 5.
3. The MACDA is of multicast type and can be found through ARL table search.
en
fid
Note: BroadSync HD cannot be received from the IMP port.
on
Queuing Class (COS) Determination
C
The BCM53128 supports the COS mapping through the mapping mechanisms listed below.
om
• TC to COS mapping: The queuing class to forward a packet to an Ethernet port is mapped from the TC
determined for the packet. The mapping entries are globally configured using TC_To_COS Mapping
register.
dc
• BroadSync HD to COS mapping: The queuing class to forward a BroadSync HD packet to a BroadSync
HD-enabled Ethernet port is mapped from the PCP carried by the packet. PCP5 is mapped to COS5 and
oa
PCP4 is mapped to COS4.

• CPU to COS mapping: The queuing class to forward a packet to the external CPU through the IMP port is
Br
determined based on the reasons to forward (copy or trap) the packet to CPU. The mapping entries are
globally configured using CPU_To_COS Map register.
Note: When the BCM53128 is configured in the aggregation mode where the IMP operates as the
uplink port to the upstream network processor, the COS is decided from the TC based on the normal
packet classification flow. Otherwise, the IMP operates as the interface to the management CPU, and
the COS is decided based on the reasons for forwarding the packet to the CPU.
Table 2 shows the reasons for forwarding a packet to the CPU. The ToCPU COS values listed are the default
setting and are configurable. In order to prevent out of order delivery of the same packet flow to the CPU, the
COS for the mirroring and SA learning reasons must be programmed with a value that is lower than or equal to
the value of the other reasons.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 37
BCM53128 Data Sheet Port-Based VLAN
Table 2: Reasons to Forward a Packet to the CPU
ToCPU Reason Description ToCPU COS

Mirroring The packet is forwarded (copied) through the IMP port because it 0
needs to be mirrored to the CPU as the capturing device.
SA Learning The packet is forwarded (copied) through the IMP port because its SA 0
needs to be learned by the CPU.
Switching /Flooding The packet is forwarded through the IMP port either because the CPU 0
is one of the intended destination hosts of the packet or because the
switch makes the flooding decision to reach all potential destinations.
Protocol Termination The packet is forwarded (trapped) through the IMP port because it 0
implies an IEEE 802.1 defined L2 protocol that needs to be
terminated by the CPU.
Protocol Snooping The packet is forwarded (copied) through the IMP port because it 0
implies an L3 or application level protocol that needs to be monitored
by the CPU for network security or operation efficiency.
l
tia
Exception Processing The packet is forwarded (trapped) through the IMP port for some 0
special processing even though the CPU is not the intended
en
destination.
fid
A packet could be forwarded to the CPU for more than one reason, therefore the COS selection is based on the
highest COS values among all the reasons for the packet.
on
C
Port-Based VLAN
om
The port-based virtual LAN (VLAN) feature partitions the switching ports into virtual private domains designated
on a per port basis. Data switching outside of the port’s private domain is not allowed. The BCM53128 provide
flexible VLAN configuration for each ingress (receiving) port.
dc
The port-based VLAN feature works as a filter, filtering out traffic destined to nonprivate domain ports. The
private domain ports are selected for each ingress port using Port-Based VLAN Control register. For each
oa
received packet, the ARL resolves the DA and obtains a forwarding vector (list of ports to which the frame will
be forwarded). The ARL then applies the VLAN filter to the forwarding vector, effectively masking out the
Br
nonprivate domain ports. The frame is only forwarded to those ports that meet the ARL table criteria, as well as
the port-based VLAN criteria.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 38
BCM53128 Data Sheet IEEE 802.1Q VLAN
IEEE 802.1Q VLAN

The BCM53128 support IEEE 802.1Q VLAN and up to approximately 4000 VLAN table entries that reside in the
internal embedded memory. Once the VLAN table is programmed and maintained by the microcontroller, the
BCM53128 autonomously handle all operations of the protocol. These actions include the stripping or adding of
the IEEE 802.1Q tag, depending on the requirements of the individual transmitting port. It also performs all the
necessary VLAN lookups in addition to MAC L2 lookups.
IEEE 802.1Q VLAN Table Organization

Each VLAN table entry, also referred to as a VLAN ID, an Untag map, and a Forward map.
• The Untag map controls whether the egress packet is tagged or untagged.
• The Forward map defines the membership within a VLAN domain.
l
• If the Ingress port is an ISP port in double-tag mode, the FWD_MODE indicates whether the packet
tia
forwarding should be based on VLAN membership or based on ARL flow.
en
The Untag map and Forward map include bit-wise representation of all the ports.
Figure 3: VLAN Table Organization
fid
on
Entry 0 FWD_MODE MSTP_Index UNTAG_MAP[8:0] FORWARD_ MAP[8 :0]
Entry 1
Entry 2
C
om
dc
oa
Entry 4095
Br
Note: When the IEEE 802.1Q feature is enabled, frames sent using the CPU must be tagged. If the
MII port is configured as a management port, then the tag is not stripped even if the untag bit is set.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 39
BCM53128 Data Sheet Programming the VLAN Table
Programming the VLAN Table

The IEEE 802.1Q VLAN feature can be enabled by writing to the Enable IEEE 802.1Q bit in the Global IEEE
802.1Q register. The default priority and VID can be assigned to each port in the Default IEEE 802.1Q Tag
register. These are necessary when tagging a previously untagged frame. The Hashing algorithm uses either
[VID, MAC] or [MAC] for the ARL index key, depending on the VLAN Learning Mode bits in the Global IEEE
802.1Q register. If both the VID and MAC address are used, a single MAC address is able to be a member of
multiple VLANs simultaneously.
The VLAN table can be written using the following steps:

1. Use the VLAN Table Entry register to define the ports that are part of the VLAN group and the ports that
should be untagged.
2. Use the VLAN Table Address Index register to define the VLAN ID of the VLAN group.
l
tia
Note: VLAN ID 0xFFF is reserved. However VID = 0xFFF can be forwarded if the VID_FFF_Fwding
bit is set in the Global VLAN Control 5 register.
en
3. Set bit [1:0] = 00 of the VLAN Table Read/Write/Clear Control register to indicate a write operation.
fid
4. Set bit 7 of the VLAN Table Read/Write/Clear Control register to 1, starting the write operation. This bit
returns to 0 when the write is complete.
on
The VLAN table can be read using the following steps:
C
1. Use the VLAN Table Address Index register to define from which VLAN group to read the data.
2. Set bit [1:0] = 01 of the VLAN Table Read/Write/Clear Control register to indicate a read operation.
om
3. Set bit 7 of the VLAN Table Read/Write/Clear Control register to 1 to start the read operation. This bit returns
to 0 when the read is complete.
dc
4. Read the VLAN Table Entry register to obtain the VLAN table entry information.
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 40
BCM53128 Data Sheet Double-Tagging
Double-Tagging
The BCM53128 provide the double tagging feature, which is useful for ISP applications. When the ISP
aggregates incoming traffic from each individual customer, the extra tag (double tag) can provide an additional
layer of tagging to the existing IEEE 802.1Q VLAN. The ISP tag (extra tag) is a way of separating individual
customers from other customers. Using the IEEE 802.1Q VLAN tag, the individual customer’s traffic can be
separated.
When the double-tagging feature is enabled using the Global VLAN Control 4 register and the Enable IEEE
802.1Q (bit7) of the Global IEEE 802.1Q register, users can expect two VLAN tags in a frame: the tag close to
MAC_SA is the ISP tag, and the one following is the customer tag as shown in Figure 4.
Figure 4: ISP Tag Diagram
l
tia
MAC_DA MAC_SA ISP_TAG Customer_ tag Ty/Len Payload
en
TPID VID
fid
The switch uses the ISP tag for ARL and VLAN table accesses and the customer tag as an IEEE 802.1Q tag.
on
There is a per chip programmable register Double Tagging TPID register for ISP tag (default = 9100'h). All ISP
tags will be qualified by this Tag Protocol ID (TPID) value.
C
When the double-tagging feature is enabled, all switch ports are separated into two groups, ISP ports and
customer ports. The BCM53128 performs the normalization process for all ingress frames, whether from the ISP
om
port or customer port. The normalization process is to insert an ISP tag, customer tag, or ISP + customer tag
(depending whether the ingress frame is without tags or with one tag) to allow all ingress frames with a double
tag. But if the ingress frames are with a double tag (ISP + customer tag), and the ISP tag TPID matches the
dc
TPID specified in the Double Tagging TPID register, it does not perform the normalization process. The ISP ports
are defined in the ISP Port Selection Portmap register. When the port (s) corresponding bit(s) are set, that port
oa
(s) should be connected ISP, and otherwise connected to customers. Each switch device can have multiple ports
assigned as ISP ports, and each ISP is uniquely identified using different VLAN forward maps or the port-based
VLAN feature.
Br
If the ingress frame is an untagged frame, the IEEE 802.1Q tag which can be configured by the Default IEEE
802.1Q Tag Register (Page 34h: Address 10h) will add to an incoming untagged frame. If the ingress frame is
tagged with the 802.1p tag, the default VID which can be configured by the Default IEEE 802.1Q Tag Register
(Page 34h: Address 10h) will be tagged the incoming 802.1p frame.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 41
ISP Port
It is possible for ISP port to receive three different types of frames: untagged, ISP-tagged, and ISP+Customer-
tagged frames.
When the double-tagging feature is enabled and the received frame is untagged (or the TPID does not match
with ISP TPID specified in Double Tagging TPID register, the default ISP tag and customer tag are added, and
VLAN ID of ISP tag receives it from the port default VID. The frames are forwarded according to the VLAN table.
However, if the Port-Based VLAN Control register is enabled, the egress ports specified in the port-VLAN control
register override the VLAN table settings. If the received frame is ISP tagged (TPID matches with the ISP tag
VLAN ID specified in the double-tagging TPID register), the default customer tag (8100 + default PVID) is added,
the ISP VID is used to access the ARL table, and the ISP tag can be stripped on the way out according to the
untagged bit setting in the VLAN table. In addition, ISP port frame can forward to the destination port directly
based on forward port map of VLAN table by setting FWD_MODE bit to 1 of VLAN Table Entry register.
The VLAN ID is generated from the ISP tag, and TC is generated from the ingress frame outer tag.
l
tia
Customer Port
en
It is also possible for Customer port to receive two different types of frames: untagged and Customer-tagged
frames.
fid
When the double-tagging feature is enabled, all the ingress frames preform the normalization process to insert
on
a ISP tag or ISP + Customer tag (depending whether the ingress frame is without tags or with one tag) to allow
all ingress frames with a double tag. The VLAN ID of ISP tag receives it from the port default VID.
C
The VLAN ID is generated from the ISP tag, and the TC is generated from the ingress frame outer tag.
om
Note: It is illegal to strip out the ISP tag on the ISP egress port by using the untagged bit setting in
the VLAN table.
dc
Only the VLAN tagged or untagged packets are expected for the ingress of the customer ports. The
customer do not add the ISP tags.
oa
There are two possible traffic scenarios; one from a customer port to an ISP port, and one from an ISP port to
Br
a customer port.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 42
Uplink Traffic (from Customer Port to ISP)

Data traffic is traffic received from the customer port without tags or a customer tag, and the frame is destined
for an ISP port. The customer ingress port performs a normalization process to allow ingress frames with double
tags (ISP + Customer tag), and the ISP tag VID is based on the port default VID tag.
However, if the ingress frame is with an 802.1p tag, the VID of 802.1p tag is changed by the VID of port default
VID tag after the customer port normalization process. The TC do not change.
Control traffic frames can be forwarded to the CPU first and then the CPU forwards to the ISP port if the switch
management mode is enabled and if the RESV_MCAST_FLOOD bit=0 in the Global VLAN Control 4 register.
In this case, the control frame adds an ISP tag by ingress port and forward to the CPU. The CPU can then
forward it to the ISP port with or without the ISP tag by using the egress-direct feature.
Downlink Traffic (from ISP to Customer Port)
l
tia
Data traffic frame received from ISP port may or may not have ISP tag attached. When the received frame does
not have an ISP tag and customer tag, the ISP ingress port does a normalization process to insert double tags
en
(ISP + Customer tag), and the ISP tag VID is based on the port default VID tag. All ARL and VID table access
should be based on the new tag. The traffic is then forwarded to the customer port through proper VLAN
configuration. Usually, the software configures so the customer Egress port continuously removes the ISP tag.
However, it is based on how the untagged map is configured.
fid
on
Moreover, if the ingress frame is with an 802.1p tag, the VID of 802.1p tag is changed by the VID of port default
VID tag after the ISP port normalization process. The TC will not change.
C
The Control traffic is forwarded to the CPU when the switch management mode is enable and if the
RESV_MCAST_FLOOD bit=0 in the Global VLAN Control 4 register. The BCM53128 can also support multiple
om
ISP port configurations by enabled the FWD_MODE bit of VLAN Table Entry register. There are also two ways
to separate traffic that belongs to two different ISP customers:
dc
1. Each group (ISP, and customer) is assigned to the same VLAN group, so that traffic does not leak to other
ISP.
oa
2. Use the Port-based VLAN to separate traffic that belongs to a different ISP.
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 43
BCM53128 Data Sheet Jumbo Frame Support
Jumbo Frame Support

The BCM53128 can receive and transmit frames of extended length on ports linked at gigabit speed. Referred
to as jumbo frames, these packets are longer than standard maximum size which is defined using the Standard
Max Frame Size register, but shorter than 9720 bytes. Jumbo packets can only be received or forwarded to
1000BASE-T linked ports that are jumbo-frame enabled. Up to 38 buffer memory pages are required for storing
the longest allowed jumbo frame. While there is no physical limitation to the number of ports that can be jumbo
enabled, it is recommended that no more than two be enabled simultaneously to ensure system performance.
There is no performance penalty for enabling additional jumbo ports beyond the potential strain on memory
resources that can occur due to accumulated jumbo packets at multiple ports.
Port Trunking/Aggregation
l
tia
The BCM53128 support MAC-based trunking. The trunking feature allows up to four ports to be grouped
together as a single-link connection between two switch devices. This increases the effective bandwidth through
en
a link and provides redundancy. The BCM53128 allow up to two trunk groups. Trunks are composed of
predetermined ports and can be enabled using Trunking Group 0 register. Ports within a trunk group must be of
the same linked speed. By performing a dynamic hashing algorithm on the MAC address, each packet destined
fid
for the trunk is forwarded to one of the valid ports within the trunk group. This method has several key
advantages. By dynamically performing this function, the traffic patterns can be more balanced across the ports
on
within a trunk. In addition, the MAC-based algorithm provides dynamic failover. If a port within a trunking group
fails, the other port within the trunk automatically assumes all traffic designated for the trunk. It allows for a
C
seamless, automatic redundancy scheme. This hashing function can be performed on either the DA, SA, or DA/
SA, depending on the Trunk Hash Selector bit of MAC Trunking Control register.
om
Figure 5: Trunking
dc
Switch 1 Switch 2
oa
Port X Port 0
Frame Z Frame Y Frame X
Br
Port Y One Pipe Port 1

Port Z Port 2
Broadcom®
April 6, 2016 • 53128-DS07-R Page 44
BCM53128 Data Sheet WAN Port
WAN Port
The BCM53128 offers a programmable WAN port feature: it has a WAN Port Select register. Select a port as a
WAN port, then all of that port’s traffic is forwarded to the CPU port only. The non-WAN port traffic from all other
local ports does not flood to the WAN port.
Rate Control
Ingress Rate Control

Forwarding broadcast traffic consumes switch resources, which can negatively impact the forwarding of other
traffic. The rate-based broadcast storm suppression mechanism is used to protect regular traffic from an
l
tia
overabundance of broadcast or multicast traffic. This feature monitors the rate of ingressed traffic of
programmable packet types. If the rates of these packet types exceed the programmable maximum rate, the
en
packets are dropped. To enable the Broadcast Storm Suppression, pull the BC_SUPP_EN high during power-
on/reset. Alternatively, the feature can be activated in the Port Receive Rate Control register.
fid
The broadcast storm suppression mechanism works on a credit-based rate system that figuratively uses a
bucket to track the bandwidth of each port (see the figure below). Credit is continually added to the bucket at a
on
programmable bucket bit rate. Credit is decremented from the bucket whenever one of the programmable
packet types is ingressed at the port. If no packets are ingressed for a considerable length of time, the bucket
credit continues to increase up to a programmable-maximum bucket size. If a heavy burst of traffic is suddenly
C
ingressed at the port, the bucket credit becomes drained. When the bucket is emptied, incoming traffic is
constrained to the bucket bit rate (the rate at which credit is added to the bucket). At this point, excess packets
om
are either dropped or deterred using flow control, depending upon the Suppression Drop mode in the Ingress
Rate Control Configuration register.
dc
Figure 6: Bucket Flow

oa
Ingress Packet Rate Ingress Packet Rate

assigned to Bucket 1 assigned to Bucket 2
Br
Bucket 1 Bit Rate Bucket 2 Bit Rate
Accumulated Credit
Accumulated Credit
BUCKET 1 BUCKET 2
If there is no accumulated credit available,

the switch does not accept input packets .
Broadcom®
April 6, 2016 • 53128-DS07-R Page 45
BCM53128 Data Sheet Rate Control
Two-Bucket System
For added flexibility, the BCM53128 employ two buckets to track the rate of ingressed packets. Each of the two
buckets (Bucket 0 and Bucket 1) can be programmed to monitor different packet types. For example, Bucket 0
could monitor broadcast packets, while Bucket 1 monitors multicast packets. Multiple packet types can be
monitored by each bucket, and a packet type can be monitored by both buckets.
The rates of each bucket can be individually programmed (see “Bucket Bit Rate”). For example, the broadcast
packets of Bucket 0 could have a maximum rate of 3 Mbps, whereas the multicast packets of Bucket 1 could be
allowed up to 80 Mbps. The size of each bucket can be programmed using the Suppressed Packet Type Mask
of the Ingress Rate Control Configuration register. This determines the maximum credit than can accumulate in
each bucket. The Rate Count and Bucket Size can be individually programmed for each port, providing another
level of flexibility. Suppression control can be enabled or disabled on a per-port basis Ingress Rate Control
Configuration register. This system allows the user to control dual packet-type rates on a per-port basis.
l
Egress Rate Control
tia
The BCM53128 monitor the rate of egress traffic per port. Unlike the Ingress traffic rate control, the Egress Rate
en
Control provides only the per port rate control regardless of traffic types. This feature only uses one bucket to
track the rate of egressed packets. The Egress Rate Control feature can be enabled in the Port Egress Rate
fid
Control Configuration register and the output rate per port can be controlled by setting the bucket size and
Refresh Count in the same register. The Egress Rate Control feature only support absolute bit rate mode (Bit
Rate Mode = 0) and the bucket bit rate calculation is shown in Table 3.
on
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 46
BCM53128 Data Sheet Protected Ports
Bucket Bit Rate

The relative ingress rates of each bucket can be programmed Port Receive Rate Control register on a per port
basis. Each port has a programmable Rate Count value for Bucket 0 and Bucket 1. Additionally, the bit rate
mode is programmed Ingress Rate Control Configuration register on a chip basis. If this bit is 1, the packet rate
is automatically scaled according to the port link speed. Ports operating at 1000 Mbps would be allotted a 100
times higher ingress rate than ports linked at 10 Mbps. Together, the Rate Count value and the bit rate mode
determine the bucket bit rate, which is a reflection of how quickly data can be ingressed (Kbps) at the given port
for a given bucket. The Rate Count values are specified in the following table. Values outside these ranges are
not valid entries.
Table 3: Bucket Bit Rate
Approximate Computed
Bit Rate Bucket Bit Rate Bucket Bit Rate
Rate Count (RC) Mode Link Speed Equation Values (As a function of RC)
l
tia
1–28 0 Any = (RC x 8 x 1M) / 125 64 KB, 128 KB, 192 KB,..., 1.792 MB
29–127 0 Any = (RC – 27) x 1M 2 MB, 3 MB, 4 MB,..., 100 MB
en
128–240 0 Any = (RC – 115) x 1M x 8 104 MB, 112 MB, 120 MB,..., 1000 MB
1–125 1 10 Mbps = (RC x 8 x 1M) / 100 0.08 MB, 0.16 MB, 0.24 MB,... 10 MB
1–125
1–125
1
1
100 Mbps
200 Mbps fid
= (RC x 8 x 1M) / 10
= (RC x 8 x 1M) / 5
0.8 MB, 1.6 MB, 2.4 MB,..., 100 MB
1.6 MB, 3.2 MB, 4.8 MB,..., 200 MB
on
1–125 1 1000 Mbps = RC x 8 x 1M 8 MB, 16 MB, 24 MB,... 1000 MB
Note: 1M represents 1 x 106.
C
IMP Port Egress Rate Control

om
The IMP port egress is configurable of rate limiting at packet-per-second (PPS) granularity, in addition to bits-
per-second (BPS) granularity. It can be configured using the IMP Port Egress Rate Control Configuration
dc
register.
oa
Protected Ports
Br
The Protected Ports feature allows certain ports to be designated as protected Protected Port Selection register.
All other ports are unprotected. Traffic between protected port group members is blocked. However, protected
ports are able to send traffic to unprotected ports. Unprotected ports can send traffic to any port. Several
applications that can benefit from protected ports:
• Aggregator: For example, all the available ports are designated as protected ports except a single
aggregator port. No traffic incoming to the protected ports is sent within the protected ports group. Any
flooded traffic is forwarded only to the aggregator port.
• To prevent nonsecured ports from monitoring important information on a server port, the server port and
nonsecured ports are designated as protected. The nonsecured ports will not be able to receive traffic from
the server port.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 47
BCM53128 Data Sheet Port Mirroring
Port Mirroring
The BCM53128 support Port Mirroring, allowing ingress and/or egress traffic to be monitored by a single port
designated as the mirror capture port. The BCM53128 can be configured to mirror the ingress traffic and/or
egress traffic of any other port (s). Mirroring multiple ports is possible, but can create congestion at the mirror
capture port. Several filters are used to decrease congestion.
Enabling Port Mirroring

Port Mirroring is enabled by setting the Mirror Enable bit in the Mirror Capture Control register.
Figure 7: Mirror Filter Flow
Port mask filter Port address filter Port divider filter
l
tia
Ingress mirror mask Ingress mirror filter Ingress mirror divider
en
Capture port
fid
on
All packets Egress mirror mask Egress mirror filter Egress mirror divider
C
om
Destination port(s)
Capture Port
dc
The capture port is capable of monitoring other specified ports. Frames transmitted and received at the other
oa
ports are forwarded to the Capture port according to the mirror filtering rules discussed below. The Capture port
is specified by the Capture Port bits of the Mirror Capture Control register.
Br
Mirror Filtering Rules

Mirror filtering rules consist of a set of three filter operations (Port Mask, Packet Address, and Packet Divider)
that are applied to traffic ingressed and/or egressed at a switch port.
Port Mask Filter

The IN_MIRROR_MASK bits in the Ingress Mirror Control register define the receive ports that are monitored.
The OUT_MIRROR_MASK bits in the Egress Mirror Control register define the transmit ports that are
monitored.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 48
BCM53128 Data Sheet IGMP Snooping
Any number of ingress/egress ports can be programmed to be mirrored, but bandwidth restrictions on the one-
mirror capture port should be taken into account to avoid congestion or packet loss.
Packet Address Filter

The Ingress Mirror Control register is used to set the type of filtering that is applied to frames received on the
mirrored ports. The IN_MIRROR_FILTER bits select among the following:
• Mirror all received frames
• Mirror received frames with DA = x
• Mirror received frames with SA = x
where x is the 48-bit MAC address programmed into the Ingress Mirror MAC Address register. Likewise, the
Egress Mirror Control register is used to set the type of filtering that is applied to frames transmitted on the
egressed mirrored ports. The filtering MAC address is specified in the Egress Mirror MAC Address register.
l
tia
Packet Divider Filter
en
The IN_DIV_EN bit in the Ingress Mirror Control register allows further statistical sampling. When IN_DIV_EN
= 1, the receive frames passing the initial filter are divided by the value IN_MIRROR_DIV, which is a 10-bit value
stored in the Ingress Mirror Divider register. Only one out of every n frames is forwarded to the mirror capture
• Mirror every nth received frame

fid
port, where n = IN_MIRROR_DIV +1. This allows the following additional capabilities:
on
• Mirror every nth received frame with DA = x
• Mirror every nth received frame with SA = x
C
Similarly, the Egress Mirror Divide function is controlled by the Egress Mirror Control register and the Egress
om
Mirror Divider register.

dc
Note: When multiple ingress ports have been enabled in the IN_MIRROR_MASK, the cumulative total
packet count received from all ingress ports is divided by the value of IN_MIRROR_DIV to deliver the
nth receive frame to the mirror capture port. Egressed frames are governed by the
oa
OUT_MIRROR_MASK bit and the OUT_MIRROR_DIV bit.

Br
IGMP Snooping
The BCM53128 supports IP layer IGMP Snooping which includes IGMP unknown, query, report, and leave
messages using the High-Level Protocol Control register.
A frame with a value of 2 in the IP header protocol field and IGMP frames are forwarded to the CPU port. The
management CPU can then determine, from the IGMP control packets which port should participate in the
multigroup session. The management CPU proactively programs the multicast address in the ARL table or the
multiport address entries. If the IGMP_FWD_EN in the High-Level Protocol Control register is enabled, IGMP
frames will be trapped to the CPU port only.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 49
BCM53128 Data Sheet MLD Snooping
MLD Snooping
The BCM53128 supports IP layer MLD Snooping including MLD query, report, and done messages using the
High-Level Protocol Control register.
IEEE 802.1x Port-Based Security

IEEE 802.1x is a port-based authentication protocol. By receiving and extracting special frames, the CPU can
control whether the ingress and egress ports should forward packets or not. If a user port wants service from
another port (authenticator), it must get approved by the authenticator. EAPOL is the protocol used by the
authentication process. The BCM53128 detect EAPOL frames by checking the destination address of the frame.
The Destination addresses should be either a multicast address as defined in IEEE 802.1x (01-80-C2-00-00-
03) or a user-predefined MAC (unicast or multicast) address. Once EAPOL frames are detected, the frames are
l
tia
forwarded to the CPU so it can send the frames to the authenticator server. Eventually, the CPU determines
whether the requestor is qualified or not based on its MAC_Source addresses, and frames are either accepted
en
or dropped. The per-port EAP can be programmed in the register.
BCM53128 provides three modes for implementing the IEEE 802.1x feature. Each mode can be selected by
setting the appropriate bits in the register.
fid
on
The Basic Mode (when EAP Mode = 00'b) is the standard mode, the EAP_BLK_MODE bit would be set before
authentication to block all of the incoming packets, upon authentication, the EAP_BLK_MODE bit would be
cleared to allow all the incoming packets. In this mode, the Source Address of incoming packets is not checked.
C
The second mode is Extended Mode (when EAP Mode = 10'b), where an extra filtering mechanism is
om
implemented after the port is authenticated. If the Source MAC address is unknown, the incoming packets would
be dropped and the unknown SA would not be learned. However if the incoming packet is IEEE 802.1x packet,
or special frames, the incoming packets will be forwarded. The definition of the Unknown SA in this case is when
dc
the switch cannot match the incoming Source MAC address to any of the addresses in ARL table, or the
incoming Source MAC address matches the address in ARL table, but the port number is mismatched. The third
oa
mode is Simplified Mode (when EAP Mode = 11'b). In this mode, the unknown Source MAC address packets
would be forwarded to CPU rather than dropped. Otherwise, it is same as the Extended Mode operation.
Br
Note: The BCM53128 checks only the destination addresses to qualify EAPOL frames. Ethernet type
fields, packet type fields, or non-IEEE 802.1Q frames are not checked.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 50
BCM53128 Data Sheet DoS Attack Prevention
DoS Attack Prevention

The BCM53128 supports the detection of the following DoS (Denial of Service) attack types based on a register
setting, which can be programmed to drop or not to drop each type of DoS packet, respectively.
Table 4: DoS Attacks Detected by BCM53128
DoS Attack Type Description

IP_LAND IPDA = IPSA in an IPv4/IPv6 datagram
TCP_BLAT DPort = SPort in a TCP header carried in an unfragmented IP datagram or in the first
fragment of a fragmented IP datagram
UDP_BLAT DPort = SPort in a UDP header carried in an unfragmented IP datagram or in the first
fragment of a fragmented IP datagram
TCP_NULLScan Seq_Num = 0 and all TCP_FLAGs = 0 in a TCP header carried in an unfragmented IP
datagram or in the first fragment of a fragmented IP datagram
l
tia
TCP_XMASScan Seq_Num = 0, FIN = 1, URG = 1, and PSH = 1 in a TCP header carried in an
unfragmented IP datagram or in the first fragment of a fragmented IP datagram
en
TCP_SYNFINScan SYN = 1 and FIN = 1 in a TCP header carried in an unfragmented IP datagram or in the
first fragment of a fragmented IP datagram
TCP_SYNError
TCP_ShortHDR
fid
SYN = 1, ACK = 0, and SRC_Port < 1024 in a TCP header carried in an unfragmented
IP datagram or in the first fragment of a fragmented IP datagram
The length of a TCP header carried in an unfragmented IP datagram or the first
on
fragment of a fragmented IP datagram is less than MIN_TCP_Header_Size
TCP_FragError The Fragment_Offset = 1 in any fragment of a fragmented IP datagram carrying part of
C
TCP data
ICMPv4_Fragment The ICMPv4 protocol data unit carried in a fragmented IPv4 datagram
om
ICMPv6_Fragment The ICMPv6 protocol data unit carried in a fragmented IPv6 datagram
ICMPv4_LongPing The ICMPv4 ping (echo request) protocol data unit carried in an unfragmented IPv4
datagram with its Total Length indicating a value greater than the MAX_ICMPv4_Size +
dc
size of IPv4 header

ICMPv6_LongPing The ICMPv6 ping (echo request) protocol data unit carried in an unfragmented IPv6
oa
datagram with its payload length indicating a value greater than the MAX_ICMPv6_Size
Br
• MIN_TCP_Header_Size is programmable between 0 and 255 bytes, inclusive. The default value is set to
20 bytes (TCP header without options).
• MAX_ICMPv4_Size is programmable between 0 and 9.6 KB, inclusive. The default value is set to 512
bytes.
• MIN_TCP_Header_Size is programmable between 0 and 9.6 KB, inclusive. The default value is set to 512
bytes.
• The default control setting for all types of DoS attacks is not to drop the DoS attack packet.
• It is globally configurable whether to perform the SA learning operation with the received packets of the
DoS attack type defined in the registers, regardless of the individual DoS attack types.
• Once a packet is detected as a DoS attack type that must be dropped, the packet is dropped regardless of
ARL forwarding decisions, but its forwarding based on mirroring function is not affected.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 51
BCM53128 Data Sheet MSTP Multiple Spanning Tree
MSTP Multiple Spanning Tree

The BCM53128 supports up to eight multiple spanning trees. When the EN_RX_BPDU bit = 1, the BCM53128
forwards BPDU packets to the management port only.
Software Reset
The BCM53128 provide Software Resets. Software Resets can be triggered by programming the Software
Reset Control register.
Loop Detection
l
tia
The BCM53128 provide the Loop Detection feature for unmanaged environments (that is, those without a
en
management CPU). When the Loop Detection feature is enabled and activated, the switch generates Broadcom
proprietary tag frames (Loop Discovery Frames) at a programmed interval, and when it detects a loop, it gives
a loop detected warning with a blinking LED or with a sound produced by a speaker. This feature does not repair
the loop, but only issues a warning.
fid
on
The Discovery Frame is a broadcast frame, and the switch ensures the forwarding of the frame by providing
special priority for the frame by giving it a higher priority over other broadcast frames, assigning highest queue
automatically and overwriting the pause condition. The control/options over this feature are provided beginning
C
with the Loop Detection Control register.

om
The Loop Discovery frame uses a default multicast address (01-80-C2-00-00-01) in the Loop Detect Source
Address register as a source address. Using a multicast address as a source address is illegal in the IEEE
standard; however, since this is only intended to be used in the ROBO environment only, it should be allowed.
dc
This address scheme is used to avoid a possible disruption in forwarding decision by using a regular random
Source Address.
oa
The Loop Discovery frame also uses the Module ID 0 register along with the Module ID 1 register to identify the
origin of the Discovery frame. These registers are used to define a Source Chip ID and Source Port ID to
Br
distinguish the Discovery Frames from other ROBO chips.
The implementation example for the Loop Detect feature is described in the Layout and Design Guide
(document number 53128-AN1xx-R).
Broadcom®
April 6, 2016 • 53128-DS07-R Page 52
BCM53128 Data Sheet BroadSync HD
BroadSync HD
BroadSync HD is the enhancement to IEEE 802.3 MAC and IEEE 802.1D bridges to support the kind of low-
latency isochronous services and guaranteed quality of service (QoS) that is required for many consumer
electronics applications.
The BCM53128 provides the BroadSync HD feature through the BroadSync HD Enable Control register. The
BCM53128 always forwards BPDU, MRP packets to CPU for BroadSync HD applications, and handles the IEEE
802.1 Time Sync Protocol.
The BCM53128 can identify a packet as a BroadSync HD packet if the MAC DA matches a MAC address in the
ARL table. The PCP equals four or five and the ingress port is BroadSync HD-enabled. There are two dedicated
queues for BroadSync HD Class 5 and Class 4 traffic per egress port. BCM53128 enhances shaping and
scheduling for BroadSync HD operation.
l
tia
Time Base and Slot Generation
en
For BroadSync HD applications, the BCM53128 maintains a time base (32-bit counter) running at a granularity
of 1 ns, which can be adjusted by CPU for synchronization with the BroadSync HD time master unit (Switch or
Host) through the IEEE 802.1 Time Synchronized (TS) protocol (to be standardized). The TS protocol is
•
fid
implemented by the CPU which requires the BCM53128 to perform the following operations.
A received TS protocol packet is time stamped at the ingress port when the first byte (of MACDA) arrives,
on
and is transferred along with the receiving time stamp to the CPU.
• A TS protocol packet initiated by the CPU (to be transmitted at an egress port) is time stamped at the
C
egress port when the first byte (of MACDA) is transmitted, and the transmit time stamp recorded at the
egress port is reported back to CPU.
om
It is required that the time synchronization point peers over an Ethernet link is chosen such that the link delay
is perceived as constant, and the protocol exchange occurs at least every 10 ms over every link.
dc
The CPU may be required to speed up or slow down the time base maintained in BCM53128 based on the TS
protocol execution. The BCM53128 provides the time base adjustment mechanism for graceful time changes
oa
based on CPU instructions.

Br
In addition, the BCM53128 maintains counter mechanism to generate time Slot for BroadSync HD traffic
scheduling.
• A Slot is defined as 125 s, it is used to pace the BroadSync HD Class 5 traffic which has tight jitter
requirements;
• A MacroSlot is configurable as 1 ms, 2 ms, or 4 ms (binary number of Slots) using the BroadSync HD Slot
Adjustment register. It is used to pace the BroadSync HD Class 4 traffic which has relaxed jitter
requirements.
The CPU may be required to make the Slot wider or narrower based on the TS protocol execution. The
BCM53128 provides the Slot adjustment mechanism for graceful Slot width changes based on CPU
instructions.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 53
Transmission Shaping and Scheduling

Packets queued at each Ethernet (egress) port is subject to the scheduling behavior as shown in Figure 8.
Figure 8: BroadSync HD Shaping and Scheduling
Shaper
COS5
A
SP/
Shaper WRR
COS4
B
COS3
l
Shaper
tia
COS2 SP/WRR C
A
COS1
en
COS0
BroadSync HD Class 5 Media Traffic

fid
on
The COS5 queue is dedicated for BroadSync HD Class 5 traffic only, and a COS5 packet is always the highest
C
priority to be scheduled for transmission, if it is allowed by the Shaper A that operates as follows.
• The Shaper A is an emulation of fixed bandwidth pipe for Class 5 BroadSync HD traffic with tight jitter
om
adaptively to handle interference from non-BroadSync HD or Class 4 BroadSync HD traffic. Note that the
preamble and IPG transmission are not taken into account for the pipe operation.
• Tunable parameters for the Shaper A are listed as follows:
dc
– MaxAVPacketSize indicates the maximum packet size allowed on a BroadSync HD-enabled port. It is a
global setting using the BroadSync HD Max Packet Size register.
oa
– Class5_BW indicates the reserved bandwidth for Class 5 BroadSync HD traffic at granularity of Byte
(per Slot, 125 s). It is a per-port setting using BroadSync HD Class 5 Bandwidth Control register.
Br
– Class5_Window indicates the jitter control for Class 5 BroadSync HD transmission. It is a per-port
setting using BroadSync HD Class 5 Bandwidth Control register.
• At the start of each Slot,
– Reset the credit in the shaping bucket to Class5_BW, if the queue is empty.
– Reset the credit in the shaping bucket to Class5_BW, if the queue is not empty and Class5_Window is
set to 0.
– Reset the credit in the shaping bucket to Class5_BW, if the queue is not empty, Class5_Window is set
to 1, and the credit remained in the shaping bucket is greater than MaxAVPacketSize.
– Add Class5_BW to the credit in the shaping bucket, if the queue is not empty, Class5_Window is set to
1, and the credit remained in the shaping bucket is less than or equal to MaxAVPacketSize.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 54
• The credit in the shaping bucket decrements for every byte transmitted for the Class 5 BroadSync HD
traffic through the port.
– If the credit reaches 0 before the end of the current Slot while transmitting a Class 5 BroadSync HD
packet, the ongoing packet transmission is not interrupted, and the credit stays at 0 until being reset at
the start of next Slot.
– The credit decrements resumes at the next Slot if the ongoing transmission continues.
As long as the credits in the shaping bucket is greater than 0, a Class 5 BroadSync HD packet is allowed to be
scheduled for transmission.
BroadSync HD Class 4 Media Traffic

The COS4 queue is dedicated for BroadSync HD Class 4 traffic only, and a COS4 packet always yield to COS5
traffic (if allowed to be scheduled), but takes precedence over the traffic from COS0~COS3 queues or follow the
weight ratio between COS4 and COS0~COS3 for transmission scheduling, if it is allowed by the Shaper B that
l
operates as follows.
tia
• The Shaper B is an emulation of fixed bandwidth pipe for Class 4 BroadSync HD traffic with relaxed jitter
adaptively to handle interference from non-BroadSync HD or Class 5 BroadSync HD traffic. It also
en
statistically levels the Class 4 BroadSync HD transmission bursts towards the next hop switch to reduce the
buffering requirements, by using Slot (instead of MacroSlot) as the pacing mechanism. The preamble and
• fid
IPG transmission are not accounted for in the pipe operation.
Tunable parameters for the Shaper B are listed as follows:
on
– MacroSlot_Period indicates the periodic cycle time to shape the Class 4 traffic. It is a global setting
using BroadSync HD Slot Adjustment register to indicate 1 ms, 2 ms, or 4 ms.
C
– MaxAVPacketSize indicates the maximum packet size allowed on a BroadSync HD-enabled port. It is a
global setting. (same as for BroadSync HD Class 5 setting)
om
– Class4_BW indicates the evenly divided bandwidth share per Slot, which is derived from dividing the
reserved bandwidth for Class 4 BroadSync HD traffic at granularity of Byte (per MacroSlot) by the
number of Slots within a MacroSlot. It is a per-port setting using BroadSync HD Class 4 Bandwidth
dc
Control register.
• At the start of each Slot,
oa
– If the Slot is the first one for the current MacroSlot, reset the credit bucket to
Class4_BW+MaxAVPacketSize; (MaxAVPacketSize is used as the deficit base)
Br
– Otherwise, add Class4_BW to the credit in the shaping bucket.

• The shaping credit bucket decrements for every byte transmitted for the Class 4 BroadSync HD traffic.
As long as the credits in the shaping bucket is greater than or equal to MaxAVPacketSize, a Class 4 BroadSync
HD packet is allowed to be scheduled for transmission.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 55
BCM53128 Data Sheet CableChecker™
CableChecker™
The BCM53128 provide the cable diagnostic capabilities for unmanaged environments. The actual cable
diagnostic feature lies in the PHY functional block. The BCM53128 devices let the user monitor the cable
diagnostic results through LED display by setting the appropriate bits in the LED refresh registers.
The BCM53128 uses the existing LED display (which is already assigned to various functions) to indicate the
cable diagnostic results. The table below shows the cable diagnostic result output for each LED function where
1 and 0 represent the LED indication pin status; 1 indicates active and 0 indicates nonactive.
Note:
• The best way for a user to visualize the cable diagnostic test result through LEDs is to bring out
the LINK status bit to the LED display along with other functions to be displayed per port. In this
way, the user can observe the cable diagnostic result from the flashing (or lit) LED of other
l
functions while LINK LED is off. The switch will turn off the LINK status LED during the cable
tia
diagnostic mode.
• The cable diagnostic is expected to be most effective when the user cannot establish the link with
en
the partner.
fid
Table 5: Cable Diagnostic Output
on
LED Function in LED Function Register Cable Diagnostic Output
C
Reserved –
LNK No output during the cable diagnostic mode
om
DPX 1: Passed
0: Failed
ACT 1: Passed
dc
0: Failed
COL 1: Passed
oa
0: Failed
LNK/ACT No output during the cable diagnostic mode
Br
DPX/COL 1: Passed
0: Failed
SPD10M 1: Failed
0: Passed
SPD100M In LED function0 map
1: Cable diagnostic passed
0: Failed
In LED function1 map
1: Cable diagnostic failed
0: Passed
SPD1G 1: Passed
0: Failed
Broadcom®
April 6, 2016 • 53128-DS07-R Page 56
BCM53128 Data Sheet Egress PCP Remarking
Table 5: Cable Diagnostic Output (Cont.)
LED Function in LED Function Register Cable Diagnostic Output

10M/ACT 1: Failed
0: Passed
100M/ACT In LED function0 map
1: Cable diagnostic passed
0: Failed
In LED function1 map
1: Cable diagnostic failed
0: Passed
10–100M/ACT 1: Failed
0: Passed
1G/ACT 1: Passed
l
0: Failed
tia
Reserved –
en
Egress PCP Remarking
fid
The BCM53128 provides an egress PCP remarking feature of the outer tag at each egress port which includes
on
the PCP field modification based on the internal generated TC. The Egress PCP remarking process applies to
Ethernet ports only and can be enabled by Traffic Remarking Control register. Each Ethernet port can provide
C
a 8-entry mapping table indexed by TC to map to the {New PCP} field for the outgoing packet using Egress Non-
BroadSync HD Packet TC to PCP Mapping register.
om
Note: For the BroadSync HD-enabled egress port, the egress PCP for the non-BroadSync HD class
of traffic must never be programmed with values of 100 and 101.
dc
oa
Address Management
Br
The BCM53128 Address Resolution Logic contains the following features:

• Four bins per bucket address table configuration.
• Hashing of the MAC/VID address to generate the address table point.
The address management unit of the BCM53128 provides wire speed learning and recognition functions. The
address table supports 4K unicast/multicast addresses using on-chip memory.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 57
BCM53128 Data Sheet Address Management
Address Table Organization

The MAC addresses are stored in embedded SRAM. Each bucket contains four entries or bins. The address
table has 1K buckets with four entries in each bucket. This allows up to four different MAC addresses with the
same hashed index bits to be simultaneously mapped into the address table. In the ARL DA/SA lookup process,
it hashes a 10-bit search index and read out bin0 and bin1 in the first cycle, and read out bin2 and bin3 in the
second cycle. These four entries are used for ARL routing and learning.
Figure 9: Address Table Organization
MAC Address [47:0]

HASH
Function
VID [11:0]
l
tia
Hash Index [9:0]
en
4K ARL Table
000000 bin0 bin1 Four bins per index
bin2 bin3
fid
on
Unicast Address
V S A TC CON Rsvd PortID VID[11:0] MACADDR

C
om
Multicast Address
dc
V S A TC CON MCAST MAP VID[11:0] MACADDR

0003FF
oa
The index to the address table is computed using a hash algorithm based on the MAC address and the VLAN
Br
ID (VID) if enabled.
Note: In the Enable IEEE 802.1Q and VLAN Learning Mode both the MAC address and the VLAN ID
(VID) are used to compute the hashed index. See “IEEE 802.1Q VLAN” on page 39 for more information.
The hash algorithm uses the CRC-CCITT polynomial. The input to the hash is reduced to a 16-bit CRC hash
value. Bits[9:0] of the hash are used as an index to the approximately 4K locations of the address table.
The CRC-CCITT polynomial is:

x16+x12+x5+1
Broadcom®
April 6, 2016 • 53128-DS07-R Page 58
Address Learning
Information is gathered from received unicast packets and learned or stored for the future purpose of forwarding
frames addressed to the receiving port. During the receive process, the frame information (such as the Source
Address [SA] and VID) is saved until completion of the packet. An entry is created in the ARL table memory if
the following conditions are met:
• The packet has been received without error.
• The packet is of legal length.
• The packet has a unicast SA.
• If using IEEE 802.1Q VLAN, the packet is from an SA that belongs to the indicated VLAN domain.
• The packet does not have a reserved multicast destination address. The Multicast Learning bit of the
Reserved Multicast Control register can disable this condition.
• There is free space available in memory to which the hashed index points.
When unicast packets are dynamically learned, the VALID bit is set, the AGE bit is set, and the STATIC bit is
l
tia
cleared in the entry. See Table 7 on page 60 for a description of a unicast ARL entry.
Multicast addresses are not learned into the ARL table, but must be written using one of the “Programming
en
Interfaces” on page 95. See “Writing an ARL Entry” on page 63 and Table 9 on page 61 for more information.
Address Resolution and Frame Forwarding fid

on
Received packets are forwarded based on the information learned or written into the ARL table. Address
resolution is the process of locating this information and assigning a forwarding destination to the packet. The
C
destination address (DA) and VID of the received packet are used to calculate a hashed index to the ARL table.
The hashed index key is used by the address resolution function to locate a matching ARL entry. The frame is
om
assigned a destination based on the forward field (PORTID or FWD_PRT_MAP) of the ARL entry. If the address
resolution function fails to return a matching ARL entry, the packet is flooded to all appropriate ports. The
following two sections describe the specifics of address resolution and frame forwarding for “Unicast Addresses”
dc
on page 59 and “Multicast Addresses” on page 61.

oa
Unicast Addresses
Br
Frames containing a unicast destination address are assigned a forwarding field corresponding to a single port.
Listed below is the unicast address-resolution algorithm:
• If the multiport addressing feature is enabled and the DA matches one of the programmed multiport
addresses, then it is forwarded accordingly. See “Using the Multiport Addresses” on page 65.
• The lower 10 bits of the hashed index key are used as a pointer into the address table memory, and the
entry is retrieved.
• If the valid indicator is set and the address stored at one of the locations matches the index key of the
packet received, the forwarding field port ID is assigned to the destination port of the packet.
– If the destination port matches the source port, the packet is not forwarded.
• If the address resolution function fails to return a matching valid ARL entry and the unicast DLF forward bit
is set, the frame is forwarded according to the port map in the Unicast Lookup Failed Forward Map register.
• Otherwise, the packet is flooded to all appropriate ports.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 59
See Table 6 for definitions of the unicast index key and the assigned forwarding field. The forwarding field for a
unicast packet is the port ID contained in the matching ARL entry. See Table 7 for a description of a unicast ARL
entry.
Table 6: Unicast Forward Field Definitions
EN_1QVLAN Index Key Forwarding Field

1 DA and VID Port ID
0 DA Port ID
Table 7: Address Table Entry for Unicast Address
Field Description
VID VLAN ID associated with the MAC address.
l
VALID 1 = Entry is valid.
tia
0 = Entry is empty.
STATIC 1 = Entry is static—Should not be aged out and is written and updated by software.
en
0 = Entry is dynamically learned and aged.
AGE 1 = Entry has been accessed or learned since last aging process.
TC fid
0 = Entry has not been accessed since last aging process.
MACDA-based TC (only valid for static entries). See “Quality of Service” on page 34 for
on
more information.
Reserved –
C
Reserved Only 00 is valid.

PORTID Port identifier. The port associated with the MAC address.
om
MAC ADDRESS 48-bit MAC address.

dc
Note: The fields described in Table 7 can be written using the ARL Table MAC/VID Entry N (N=0-3)
register and the ARL Table Data Entry N (N = 0–3) register.
oa
Br
Multicast ARL table entries are described in Table 9 on page 61.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 60
Multicast Addresses
Frames containing a multicast destination address are assigned a forwarding field corresponding to multiple
ports specified in a port map. Multicast frames are assigned a forwarding field corresponding to a multicast port
map from the matching ARL entry (see “Address Management” on page 57). If no matching ARL entry is found,
the packet is flooded to all appropriate ports. Listed below is the multicast address resolution algorithm:
• If the DA matches one of the globally assigned reserved addresses between 01-80-C2-00-00-00 and 01-
80-C2-00-00-2F, the packet is handled as described in Table 10 on page 62.
• If the multiport addressing feature is enabled and the DA matches one of the programmed Multiport
Addresses, then it is forwarded accordingly. See “Using the Multiport Addresses” on page 65.
• Otherwise, the lower 10 bits of the hashed index key are used as a pointer into the ARL table memory, and
the entry is retrieved.
• If the valid indicator is set, and the address stored at the entry locations matches the index key of the
packet received, the forwarding field port map is assigned to the destination port of the packet.
• If the address resolution function fails to return a matching valid ARL entry and the multicast DLF forward
l
tia
bit is set (see “Address Management” on page 57), the frame is forwarded according to the port map in the
Multicast Lookup Failed Forward Map register.
en
• Otherwise, all other multicast and broadcast packets are flooded to all appropriate ports.
See Table 8 for definitions of the multicast index key and the assigned forwarding field. The forwarding field for
fid
a multicast packet is the port map contained in the matching ARL entry. See Table 9 for a description of a
multicast ARL entry. See “Accessing the ARL Table Entries” on page 63 for more information.
on
Table 8: Multicast Forward Field Definitions
C
EN_1QVLAN Unicast/Multicast Index Key Forwarding Field

om
1 Unicast DA and VID Port ID

0 Unicast DA Port ID
1 Multicast DA and VID FWD_PRT_MAP
dc
0 Multicast DA FWD_PRT_MAP
oa
Table 9: Address Table Entry for Multicast Address

Br
Field Description
VID VLAN ID associated with the MAC address.
VALID 1 = Entry is valid.
0 = Entry is empty.
STATIC 1 = Entry is static—This entry is not aged out and is written and updated by software.
0 = Not defined.
AGE The AGE bit is ignored for static ARL table entries.
TC MACDA-based TC (only valid for static entries). See “Quality of Service” on page 34 for more
information.
Reserved –
Broadcom®
April 6, 2016 • 53128-DS07-R Page 61
Table 9: Address Table Entry for Multicast Address (Cont.)
Field Description
FWD_PRT_MAP Multicast forwarding mask.
[8:0] 1 = Forwarding enable.
0 = Forwarding disable.
MAC ADDRESS 48-bit MAC address.
Note: The fields described in Table 9 on page 61 can be written using the ARL Table MAC/VID Entry N
(N = 0-3) register and the ARL Table Data Entry N (N = 0–3) register.
Unicast ARL table entries are described in Table 7 on page 60.
l
tia
Reserved Multicast Addresses
Table 10 summarizes the actions taken for specific reserved multicast addresses. Packets identified with these
en
destination addresses are handled uniquely since they are designed for special functions. Bits[4:0] of the
Reserved Multicast Control register program groups of these addresses to be dropped or forwarded. Writing to
fid
these bits can change the default action of Unmanaged mode summarized in the following table.
on
Table 10: Behavior for Reserved Multicast Addresses
IEEE 802.1 Unmanaged

C
MAC Address Function Specified Action Mode Action Managed Mode Action
01-80-C2-00-00-00 Bridge group Drop frame Flood frame Forward frame to IMP only
om
address
01-80-C2-00-00-01 IEEE 802.3x MAC Drop frame Receive MAC Receive MAC determines
control frame determines if it is a if valid pause frame and
dc
valid pause frame acts accordingly.

and then acts
accordingly
oa
01-80-C2-00-00-02 Reserved Drop frame Drop frame Forward to frame

management port only
Br
01-80-C2-00-00-03 IEEE 802.1x port- Drop frame Drop frame Forward frame to
based network management port only
access control
01-80-C2-00-00-04– Reserved Drop frame Drop frame Forward frame to
01-80-C2-00-00-0F management port only
01-80-C2-00-00-10 All LANs bridge Forward frame Flood frame Forward frame to all ports
management group including management
address port
01-80-C2-00-00-11– Reserved Forward frame Flood frame Forward frame to all ports
01-80-C2-00-00-1F excluding management
port
01-80-C2-00-00-20 GMRP address Forward frame Flood frame Forward frame to all ports
excluding management
port
Broadcom®
April 6, 2016 • 53128-DS07-R Page 62
Table 10: Behavior for Reserved Multicast Addresses (Cont.)
IEEE 802.1 Unmanaged

MAC Address Function Specified Action Mode Action Managed Mode Action
01-80-C2-00-00-21 GVRP address Forward frame Flood frame Forward frame to all ports
excluding management
port
01-80-C2-00-00-22– Reserved Forward frame Flood framea Forward frame to all ports
01-80-C2-00-00-2F excluding management
port
a. Frames flood to all ports. Certain exclusions apply, such as VLAN restrictions.
Static Address Entries

The BCM53128 supports static ARL table entries that are created and updated using one of the “Programming
l
Interfaces” on page 95. These entries can contain either unicast or multicast destinations. The entries are
tia
created by writing the entry location using the Page 05h: ARL/VTBL Access registers and setting the STATIC
bit. The AGE bit is ignored. Static entries do not automatically learn MAC addresses or port associations and
en
are not aged out by the automatic internal aging process. See “Writing an ARL Entry” on page 63 for details.
Accessing the ARL Table Entries fid

on
ARL table entries are accessed by one of two mechanisms. The first mechanism uses the ARL read/write
control, which allows an address-entry location to be read, modified, or written based on the value of a known
C
MAC address. The second mechanism searches the ARL table sequentially, returning all valid entries.
om
Reading an ARL Entry

To read an ARL entry:
dc
1. Set the MAC address in the MAC Address Index register.

oa
2. Set the VLAN ID in the VLAN ID Index register. This is necessary only if the VID is used in the index key.
3. Set the ARL_R/W bit to 1 in the ARL Table Read/Write Control register.
Br
4. Set the START/DONE bit to 1 in the ARL Table Read/Write Control register. This initiates the read operation.
The MAC address and VID are used to calculate the hashed index to the ARL table. The matching ARL entry is
read. The contents of entry are stored in the ARL Table MAC/VID Entry N (N = 0-3) register and the ARL Table
Data Entry N (N = 0–3) register.
Entries that do not have the VALID bit set should be ignored. The contents of the MAC/VID registers must be
compared against the known MAC address and VID. Entries that do not match may be a valid entry, but are not
a valid match for the index key. All other read entries are considered valid ARL entries.
Writing an ARL Entry

To write an ARL entry:
Broadcom®
April 6, 2016 • 53128-DS07-R Page 63
1. Follow the steps in “Reading an ARL Entry” on page 63 to read the ARL entry matching the MAC address
and VID that are written to the table.
2. Keep the values that remain from the previous read operation.
• MAC Address Index register
• VLAN ID Index register
• ARL Table MAC/VID Entry N (N = 0-3) register
• ARL Table Data Entry N (N = 0–3) register
3. Modify the correct entry as necessary. Set the STATIC bit so that the entry is not aged out.
4. Set the ARL_R/W bit to 0 in the ARL Table Read/Write Control register.
5. Set the START/DONE bit to 1 in the ARL Table Read/Write Control register. This initiates the write operation.
The MAC address and VID are used to calculate the hashed index to the ARL table.
l
tia
Searching the ARL Table
The second method to access the ARL table is through the ARL search control. The entire ARL table is searched
en
sequentially, revealing each valid ARL entry. Setting the Start/Done bit in the ARL Table Search Control register
begins the search from the top of the ARL table. This bit is cleared when the search is complete. During the ARL
fid
search, the Search Valid bit indicates when a found valid entry is available in the ARL Table Search MAC/VID
Result N (N = 0–1) register and the ARL Table Search Data Result N (N = 0–1) register. When the host reads
on
the contents of the ARL Table Search Data Result 1 register which located in Page 05h: Address 78h, the search
process automatically continues to seek the next valid entry in the address table. Invalid address entries are
C
skipped, providing the host with an efficient way of searching the entire address table.
The ARL search and ARL read/write operations execute in parallel with other register accesses. This allows the
om
host processor to start a read, write, or search process and then read/write other registers, returning periodically
to see if the operation has completed.
dc
Address Aging
oa
The aging process periodically removes dynamically learned addresses from the ARL table. When an ARL entry
is learned or referenced, the AGE bit is set to 1. The aging process scans the ARL table at regular intervals,
Br
aging out entries not accessed during the previous one to two aging intervals. The aging interval is
programmable using the Aging Enable and AGE TIME bit in the Aging Time Control register.
Entries that are written and updated using one of the “Programming Interfaces” on page 95, should have the
STATIC bit set. Thus, they are not affected by the aging process.
For each entry in the ARL table, the aging process performs the following:
• If the VALID bit is not set, no further action is required.
• If the VALID bit is set and the STATIC is set, no further action is required.
• If the VALID bit is set, the STATIC bit is not set, and the AGE bit is set, then clear the AGE bit. This keeps
the entry in the table, but marks it so that it is removed if it is not accessed before the subsequent aging
scan.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 64
BCM53128 Data Sheet Power Savings Modes
• If the VALID bit is set, the STATIC bit is not set, and the AGE bit is reset, then reset the VALID bit. This
effectively deletes the entry from the ARL table. The entry has been aged out.
Fast Aging
The fast aging function can be enabled per port or VLAN ID:
The port fast aging can be enabled by setting the Start/Done of the Fast-Aging Control register, the Fast Age All
Ports bit of the Fast-Aging Port Control register, and the appropriate port bits in the Fast-Aging Port Control
register.
The VLAN ID fast aging can be enabled by setting the Start/Done of the Fast-Aging Control register, the Fast
Age All VID bit of the Fast-Aging VID Control register, and the appropriate VLAN ID bits of the Fast-Aging VID
Control register.
l
Using the Multiport Addresses
tia
The Multiport Address N (N = 0–5) register can be used to forward a given MAC address and Ether Type to
en
multiple ports. Packets with a corresponding DA are forwarded to the port map contained in the Multiport Vector
N (N = 0–5) register. These registers must be controlled using Multiport Control register.
fid
Note: The Multiport Address N (N = 0–5) register is the only mechanism for TS Protocol qualification for
on
the BroadSync HD application. It can be enabled by Multiport Control register.
C
om
Power Savings Modes

The BCM53128 offers different power savings modes for different operating states. All the power saving scheme
dc
are implemented without any external CPU requirement. The various power savings modes are:
• Auto Power Down Mode: This is a stand alone PHY feature which is enabled by a register bit setting. The
oa
PHY shuts off the analog portion of the circuitry when cable is not connected or the link partner power is
down.
Br
• Energy Efficient Ethernet (EEE) Mode: Energy Efficient Ethernet is IEEE802.1az, an extension of the
IEEE802.3 standard. IEEE defines support for the PHY to operate in Low Power Idle (LPI) mode. When
enabled, this mode supports QUIET times during low link utilization, allowing the both sides of link to
disable portions of each PHY's operating circuitry and save power.
• Short Cable Mode (Green Mode): This mode requires the CPU to run the cable diagnostics, and the CPU
enables power savings mode based on the cable length measurement result.
• Deep Green Mode: This mode also requires the CPU to recognize the long period power down time and
shut off the PHY power and the PLL to the PHY core. The BCM53128 enters normal operation and
establishes a link when a signal is detected at the PHY input.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 65
Auto Power Down Mode

Auto Power Down mode saves PHY power consumption while the link is down. When the user enables the Auto
Power Down mode through a PHY register bit setting, the PHY goes into the power savings mode automatically
whenever it is in linkdown state. During the Power Down state, the PHY wakes up every 2.7 or 5.4 seconds,
depending on the register settings, and checks for a link signal. If no link signal is detected, then the PHY goes
back to Power Down state, or the PHY wakes up and resumes the link process.
Automatic Power Down mode applies to the following conditions:

1. Cable is plugged in, but the link partner is shut down (for example, when a PC is off), so the port is in link
down state.
2. Cable is unplugged, so the port is in link down state.
Energy Efficient Ethernet Mode
l
tia
Energy Efficient Ethernet power savings mode saves PHY consumption while the link is up but when extended
idle periods may exist between packet traffic. In EEE power savings mode PHY power consumption is scalable
en
to the actual bandwidth utilization. The PHY can go in to “Quiet” mode (low-power idle mode) when there is no
data to be transmitted. This feature is based on the latest IEEE 802.3az standard. The EEE supporting capability
of the link partner is a must for this feature to work, and the discovery of the capability is during auto-negotiation
fid
through Link Layer Discovery Protocol (LLDP). This EEE feature is an embedded PHY feature and no external
CPU is required.
on
In this mode, the MAC determines when to enter low power mode by examining the state of the transmit queues
C
associated with each MAC. Four simple adjustments (settings) are used to trigger (optimize) the behavior of
EEE control policy. These adjustments are:
om
• Global Buffer occupancy threshold

• Two-part sleep delay timer
• Minimum low-power idle duration timer
dc
• Wake transition timer

oa
The two-way communication between the PHY and its link partner is required for the PHY to achieve the power
savings on both sides. The transmit PHY sends a sleep symbol to the link partner, and the link partner enters
Br
low power state. When the transmit PHY sends a wake symbol, the regular packet transfer mode resumes. For
details on how the mode works and how to set up the conditions, please refer to the Layout and Design Guide
(document number 53128-AN1xx-R).
Short Cable Mode (Green Mode)

The Short Cable Power Savings mode (called Green mode) requires a CPU. In the BCM53128, a dedicated
embedded 8051 processor is used to implement this feature. Software running in the 8051 triggers the cable
diagnostic routine on a schedule programmed by the user (for example, upon every power up or every new link-
up). The diagnostic routine obtains the length of the cable connected to the port. Then, the CPU reduces the
PHY receiver power based on the measured cable length. It is for the Giga link only and the maximum supported
cable length is 30m.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 66
Deep Green Mode

The Deep Green Power Savings mode is a step deeper than the Auto Power Down Power Savings mode. The
Deep Green Power Savings mode can be enabled through the internal 8051 microcontroller by setting the
En_Green strap pin high. The Auto Power Down Power Savings mode is per port, but the Deep Green Power
Savings mode is per PHY core base with a common PLL. When the ports that are sharing a PLL are linked
down, the Auto Power Down mode is enabled (Register Page 10h – 17h, Address 38h, Shadow 01010b), and
the DLL Auto Power-Down mode is enabled (Register Page 10h – 17h, Address 38h, Shadow 00101b), then
the PHYs enter the Deep Green Power Savings mode. In this mode, all the PHY circuits are powered down
except the energy detection circuit, and the energy detection circuit constantly monitors the energy on the line.
Upon signal energy detection, the BCM53128 enters normal operation and establishes a link if energy is
detected. The Deep Green Power Savings mode is most effective when the user expects no activities on the
line for a long period of time.
l
tia
en
fid
on
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 67
BCM53128 Data Sheet System Functional Blocks
Section 3: System Functional Blocks
Overview of System Functional Blocks

The BCM53128 include the following blocks:
• “Media Access Controller”
• “Integrated 10/100/1000 PHY” on page 70
• “Frame Management” on page 79
• “MIB Engine” on page 83
• “Integrated High-Performance Memory” on page 90
• “Switch Controller” on page 90
l
tia
Each of these is discussed in more detail in the following sections.
en
Media Access Controller
The BCM53128 contains six 10/100/1000 GMACs, and one MAC.
fid
on
The MAC automatically selects the appropriate speed (CSMA/CD or full-duplex) based on the PHY auto-
C
negotiation result. In full-duplex mode, IEEE 802.3x PAUSE frame-based flow control is also determined
through auto-negotiation. The MAC is IEEE 802.3-, IEEE 802.3u-, and IEEE 802.3x-compliant.
om
Receive Function
dc
The MAC initiates frame reception following the assertion of receive data valid indication from the physical layer.
The MAC monitors the frame for the following error conditions:
oa
• Receive error indication from the PHY

• Runt frame error if frame is fewer than 64 bytes
Br
• CRC error
• Long frame error if frame is greater than the standard maximum frame size or 9,720 bytes for jumbo-
enabled ports.
Note: Frames longer than standard max frame size which configured using Standard Max Frame Size
register are considered oversized frames. When jumbo-frame mode is enabled, only the frames longer
than 9,720 bytes are bad frames and dropped.
If no errors are detected, the frame is processed by the switch controller. Frames with errors are discarded.
Receive functions can be disabled by writing to Port Traffic Control register.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 68
BCM53128 Data Sheet Media Access Controller
Transmit Function
Frame transmission begins with the switch controller queuing a frame to the MAC transmitter. The frame data
is transmitted as received from the switch controller. The transmit controller is responsible for preamble
insertion, carrier deferral, collision backoff, and inter-packet gap enforcement.
In 10/100 Mbps half-duplex mode, when a frame is queued for transmission, the transmit controller behaves as
specified by the IEEE 802.3 requirements for frame deferral. Following deferral, the transmitter adds 8 bytes of
preamble and SFD to the frame data received from the switch controller. If, during frame transmission, a collision
is observed and the collision window timer has not expired, the transmit controller asserts jam and then executes
the backoff algorithm. The frame is retransmitted when appropriate. On the 16th consecutive collision, the
backoff algorithm starts over at the initial state, the collision counter is reset and attempts to transmit the current
frame continue. Following a late collision, the frame is aborted, and the switch controller is allowed to queue the
next frame for transmission.
While in full-duplex mode, the transmit controller ignores carrier activity and collision indication. Transmission
l
begins after the switch controller queues the frame, and the 96-bit times of IPG have been observed. Transmit
tia
functions can be disabled by writing to Port Traffic Control register.
en
Flow Control
fid
The BCM53128 implement an intelligent flow-control algorithm to minimize the system impact resulting from
traffic congestion. Buffer memory allocation is adaptive to the status of each port’s speed and duplex mode,
on
providing an optimal balance between flow management and per-port memory depth. The BCM53128 initiate
flow control in response to buffer memory conditions on a per-port basis.
C
The MACs are capable of flow control in both full-and half-duplex modes.
om
10/100 Mbps Half-Duplex

dc
In 10/100 half-duplex mode, the MAC back-pressures a receiving port by transmitting a 96-bit time jam packet
to the port. A single jam packet is asserted for each received packet for the duration of the time the port is in the
flow-control state.
oa
Br
10/100/1000 Mbps Full-Duplex

Flow control in full-duplex mode functions as specified by the IEEE 802.3x requirements. In the receiver, MAC
flow-control frames are recognized and, when properly received, set the flow-control pause time for the transmit
controller. The pause time is assigned from the 2-byte pause time field following the pause opcode. MAC control
PAUSE frames are not forwarded from the receiver to the switch controller.
When the switch controller requests flow control, the transmit controller transmits a MAC control PAUSE frame
with the pause time set to maximum. When the condition that caused the flow control state is no longer present,
a second MAC control PAUSE frame is sent with the pause time field set to 0.
The flow control capabilities of the BCM53128 are enabled based on the results of auto-negotiation and the state
of the ENFDXFLOW and ENHDXFLOW control signals loaded during reset. Flow control in half-duplex mode
is independent of the state of the link partner flow control (IEEE 802.3x) capability. See Table 11 for detailed
information.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 69
BCM53128 Data Sheet Integrated 10/100/1000 PHY
Table 11: Flow Control Modes
Link Partner Flow

Control (IEEE Control Input Control Input Auto-negotiated
802.3x) ENFDXFLOW ENHDXFLOW Link Speed Flow Control Mode
X X 0 Half-duplex Disabled
X X 1 Half-duplex Jam pattern
0 0 X Full-duplex Disabled
1 1 X Full-duplex IEEE 802.3x flow control
Integrated 10/100/1000 PHY
l
tia
There are eight integrated PHY blocks in the BCM53128. For more information see “Copper Interface” on
en
page 92. The following sections describe the operations of the internal PHY block.
Encoder
fid
on
There are eight integrated PHY blocks in the BCM53128. The PHY is the Ethernet transceiver that appropriately
processes data presented by the MAC into an analog data stream to be transmitted at the MDI interface, which
performs the reverse process on data received at the MDI interface. The registers of the PHY are read using
C
the “Programming Interfaces” on page 95. The following sections describe the operations of the internal PHY
block. For more information, see “Copper Interface” on page 92.
om
In 10BASE-T mode, Manchester encoding is performed on the data stream that is transmitted on the twisted-
pair cable. The multimode transmit digital-to-analog converter (DAC) performs preequalization for 100m of
dc
Category 3 cabling.
In 100BASE-TX mode, the BCM53128 transmits a continuous data stream over the twisted-pair cable. The
oa
transmit packet is encapsulated by replacing the first two nibbles of preamble with a start-of-stream delimiter (/
J/K codes) and appending an end-of-stream delimiter (/T/R codes) to the end of the packet. The transmitter
Br
repeatedly sends the idle code group between packets. The encoded data stream is serialized and then
scrambled by the stream cipher block, as described in “Stream Cipher” on page 73. The scrambled data is then
encoded into MLT3 signal levels.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 70
In 1000BASE-T mode, the BCM53128 simultaneously transmits and receives a continuous data stream on all
4 pairs of the Category 5 cable. Byte-wide data from the transmit data pins is scrambled when the transmit
enable is asserted, and the trellis (a PAM5 symbol on each of the four twisted-pairs) is encoded into a four-
dimensional code group and then inserted into the transmit data stream. The transmit packet is encapsulated
by replacing the first 2 bytes of the preamble with a start-of-stream delimiter, and appending an end-of-stream
delimiter to the end of the packet. When the transmit error input is asserted during a packet transmission, a
transmit error code group is sent in place of the corresponding data code group. The transmitter sends idle code
groups or carrier extend code groups between packets. Carrier extension is used by the MAC to separate
packets within a multiple-packet burst and is indicated by asserting the transmit error signal and placing 0Fh on
the transmit data pins while the transmit enable is low. A carrier extend error is indicated by replacing the
transmit data input with 1Fh during carrier extension.
The encoding complies with IEEE standard IEEE 802.3ab and is fully compatible with previous versions of the
Broadcom 1000BASE-T PHYs.
l
Decoder
tia
In 10BASE-T mode, Manchester decoding is performed on the data stream.
en
In 100BASE-TX mode, following equalization and clock recovery, the receive data stream is converted from
MLT3 to serial nonreturn-to-zero (NRZ) data. The NRZ data is descrambled by the stream cipher block, as
fid
described later in this document. The descrambled data is then deserialized and aligned into 5-bit code groups.
The 5-bit code groups are decoded into 4-bit data nibbles. The start-of-stream delimiter is replaced with
on
preamble nibbles, and the end-of-stream delimiter and idle codes are replaced with 0h. The decoded data is
driven onto the MII receive data pins. When an invalid code group is detected in the data stream, the BCM53128
C
asserts the MII receive error (RX_ER) signal. RX_ER is also asserted when the link fails, or when the
descrambler loses lock during packet reception.
om
In 1000BASE-T mode, the receive data stream is:

• Passed through the Viterbi decoder
dc
• Descrambled
• Translated back into byte-wide data
oa
The start-of-stream delimiter is replaced with preamble bytes, and the end-of-stream delimiter and idle codes
are replaced with 00h. Carrier extend codes are replaced with 0Fh or 1Fh. Decoding complies with IEEE
Br
standard IEEE 802.3ab and is fully compatible with previous versions of Broadcom 1000BASE-T PHYs.
Link Monitor
In 10BASE-T mode, a link-pulse detection circuit constantly monitors the TRD pins for the presence of valid link
pulses.
In 100BASE-TX mode, receive signal energy is detected by monitoring the receive pair for transitions in the
signal level. Signal levels are qualified using squelch detect circuits. When no signal is detected on the receive
pair, the link monitor enters the Link Fail state and the transmission and reception of data packets is disabled.
When a valid signal is detected on the receive pair for a minimum of 1 ms, the link monitor enters the Link Pass
state, and the transmit and receive functions are enabled.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 71
Following auto-negotiation in 1000BASE-T mode, the master transceiver begins sending data on the media.
The slave transceiver also begins transmitting when it has recovered the master transceiver’s timing. Each end
of the link continuously monitors its local receiver status. When the local receiver status has been good for at
least 1 microsecond, the link monitor enters the Link Pass state, and the transmission and reception of data
packets are enabled. When the local receiver status is bad for more than 750 ms, the link monitor enters the
Link Fail state and the transmission and reception of data packets are disabled.
Digital Adaptive Equalizer

The digital adaptive equalizer removes intersymbol interference (ISI) created by the transmission channel
media. The equalizer accepts sampled unequalized data from the analog-to-digital converter (ADC) on each
channel and produces equalized data. The BCM53128 achieves an optimum signal-to-noise ratio by using a
combination of feed forward equalization (FFE) and decision feedback equalization (DFE) techniques. Under
harsh noise environments, these powerful techniques achieve a bit error rate (BER) of less than 1 x 10–12 for
transmissions up to 100m on Category 5 twisted-pair cabling (100m on Category 3 UTP cable for 10BASE-T
l
tia
mode). The all-digital nature of the design makes the performance very tolerant to noise. The filter coefficients
are self-adapting to accommodate varying conditions of cable quality and cable length.
en
Echo Canceler
fid
Because of the bidirectional nature of the channel in 1000BASE-T mode, an echo impairment is caused by each
transmitter. The output of the echo filter is added to the FFE output to remove the transmitted signal impairment
on
from the incoming receive signal. The echo canceler coefficients are self-adapting to manage the varying echo
impulse responses caused by different channels, transmitters, and environmental conditions.
C
Cross Talk Canceler

om
The BCM53128 transmits and receives a continuous data stream on four channels. For a given channel, the
signals sent by the other three local transmitters cause impairments on the received signal because of near-end
dc
crosstalk (NEXT) between the pairs. It is possible to cancel the effect because each receiver has access to the
data for the other three pairs that cause this interference. The output of the adaptive NEXT canceling filters is
oa
added to the FFE output to cancel the NEXT impairment.

Br
Analog-to-Digital Converter
Each receive channel has its own 125-MHz analog-to-digital converter (ADC) that samples the incoming data
on the receive channel and feeds the output to the digital adaptive equalizer. Advanced analog circuit techniques
achieve the following results:
• Low offset
• High power-supply noise rejection
• Fast settling time
• Low bit error rate
Broadcom®
April 6, 2016 • 53128-DS07-R Page 72
Clock Recovery/Generator
The clock recovery and generator block creates the transmit and receive clocks for 1000BASE-T, 100BASE-TX,
and 10BASE-T operation.
In 10BASE-T or 100BASE-TX mode, the transmit clock is locked to the 25-MHz crystal input, and the receive
clock is locked to the incoming data stream.
In 1000BASE-T mode, the two ends of the link perform loop timing. One end of the link is configured as the
master, and the other is configured as the slave. The master transmit and receive clocks are locked to the 25-
MHz crystal input. The slave transmit and receive clocks are locked to the incoming receive data stream. Loop
timing allows for the cancellation of echo and NEXT impairments by ensuring that the transmitter and receiver
at each end of the link are operating at the same frequency.
Baseline Wander Correction
l
tia
1000BASE-T and 100BASE-TX data streams are not always DC-balanced. Because the receive signal must
pass through a transformer, the DC offset of the differential receive input can vary with data content. This effect,
en
which is known as baseline wander, can greatly reduce the noise immunity of the receiver. The BCM53128
automatically compensates for baseline wander by removing the DC offset from the input signal, thereby
significantly reducing the probability of a receive symbol error.
fid
In 10BASE-T mode, baseline wander correction is not performed because the Manchester coding provides a
on
perfect DC balance.
C
Multimode TX Digital-to-Analog Converter

om
The multimode transmit digital-to-analog converter (DAC) transmits PAM5, MLT3, and Manchester coded
symbols. The transmit DAC performs signal wave shaping that decreases the unwanted high frequency signal
components, reducing electromagnetic interference (EMI). The transmit DAC uses a voltage driven output with
dc
internal terminations and hence, does not require external components or magnetic supply for operation thus
reducing system complexity for routing and bill of materials.
oa
Stream Cipher
Br
In 1000BASE-T and 100BASE-TX modes, the transmit data stream is scrambled to reduce radiated emissions
and to ensure that there are adequate transitions within the data stream. The 1000BASE-T scrambler also
ensures that there is no correlation among symbols on the four different wire pairs and in the transmit and
receive data streams. The scrambler reduces peak emissions by randomly spreading the signal energy over the
transmit frequency range and eliminating peaks at certain frequencies. The randomization of the data stream
also assists the digital adaptive equalizers and echo/crosstalk cancelers. The algorithms in these circuits require
there to be no sequential or cross-channel correlation among symbols in the various data streams.
In 100BASE-TX mode, the transmit data stream is scrambled by exclusive ORing the encoded serial data
stream. This is done with the output of an 11-bit wide linear feedback shift register (LFSR), producing a 2047-
bit nonrepeating sequence.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 73
In 1000BASE-T mode, the transmit data stream is scrambled by exclusive ORing the input data byte with an 8-
bit wide cipher text word. The cipher text word generates each symbol period from eight uncorrelated maximal
length data sequences that are produced by linear remapping of the output of a 33-bit wide LFSR. After the
scrambled data bytes are encoded, the sign of each transmitted symbol is again randomized by a 4-bit wide
cipher text word that is generated in the same manner as the 8-bit word. The master and slave transmitters use
different scrambler sequences to generate the cipher text words. For repeater or switch applications, where all
ports can transmit the same data simultaneously, signal energy is randomized further by using a unique seed
to initialize the scrambler sequence for each PHY.
The receiver descrambles the incoming data stream by exclusive ORing it with the same sequence generated
at the transmitter. The descrambler detects the state of the transmit LFSR by looking for a sequence
representing consecutive idle code groups. The descrambler locks to the scrambler state after detecting a
sufficient number of consecutive idle codes. The BCM53128 enables transmission and reception of packet data
only when the descrambler is locked. The receiver continually monitors the input data stream to ensure that it
has not lost synchronization by checking that inter-packet gaps containing idles or frame extensions are
received at expected intervals. When the BCM53128 detects loss of synchronization, it notifies the remote PHY
l
tia
of the inability to receive packets (1000BASE-T mode only) and attempts to resynchronize to the received data
stream. If the descrambler is unable to resynchronize for a period of 750 ms, the BCM53128 is forced into the
Link Fail state.
en
In 10BASE-T mode, scrambling is not required to reduce radiated emissions.
Wire Map and Pair Skew Correction

fid
on
During 1000BASE-T operation, the BCM53128 has the ability to automatically detect and correct some UTP
C
cable wiring errors. The symbol decoder detects and compensates for (internal to the BCM53128) the following
errors:
om
• Wiring errors caused by the swapping of pairs within the UTP cable.
• Polarity errors caused by the swapping of wires within a pair.
dc
The BCM53128 also automatically compensates for differences in the arrival times of symbols on the four pairs
of the UTP cable. The varying arrival times are caused by differing propagation delays (commonly referred to
oa
as delay skew) between the wire pairs. The BCM53128 can tolerate delay skews of up to 64 ns long. Auto-
negotiation must be enabled to take advantage of the wire map correction.
Br
During 10/100 Mbps operation, pair swaps are corrected. Delay skew is not an issue though, because only one
pair of wires is used in each direction.
Automatic MDI Crossover

During copper auto-negotiation, one end of the link needs to perform an MDI crossover so that each
transceiver’s transmitter is connected to the other receiver. The BCM53128 can perform an automatic media-
dependent interface (MDI) crossover, eliminating the need for crossover cables or cross-wired (MDIX) ports.
During auto-negotiation, the BCM53128 normally transmits and receives on the TRD pins.
When connecting to another device that does not perform MDI crossover, the BCM53128 automatically switches
its TRD in pairs when necessary to communicate with the remote device. When connecting to another device
that does have MDI crossover capability, an algorithm determines which end performs the crossover function.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 74
During 1000BASE-T operation, the BCM53128 swaps the transmit symbols on pairs 0 and 1 and pairs 2 and 3
if auto-negotiation completes in the MDI crossover state. The 1000BASE-T receiver automatically detects pair
swaps on the receive inputs and aligns the symbols properly within the decoder. The automatic MDI crossover
function cannot be disabled when in 1000BASE-T mode. During 10BASE-TX and 100BASE-T operation, pair
swaps automatically occur within the device and do not require user intervention. The automatic MDI crossover
function by default only works when auto-negotiation is enabled. This function can be disabled during auto-
negotiation by writing 1 to bit 14 of the PHY Extended Control register.
Note: This function only operates when the copper auto-negotiation is enabled.
10/100BASE-TX Forced Mode Auto-MDIX

The automatic MDI crossover function can also be enabled when in forced 10BASE-T or forced 100BASE-TX
mode. This feature allows the user to disable the copper auto-negotiation in either 10BASE-T or 100BASE-TX
l
tia
and still take advantage of the automatic MDI crossover function. Whenever the forced link is down for at least
4 seconds, then auto-negotiation is internally enabled with its automatic MDI crossover function until link pulses
en
or 100Tx idles are detected. Once detected, the PHY returns to forced mode operation.
The user should set the same speed in register 0 and the auto-negotiation advertisement register 4.
fid
Note: This function only operates when the copper auto-negotiation is disabled.
on
C
Resetting the PHY

om
The BCM53128 provides a hardware reset pin, RESET, which resets all internal nodes to a known state.
Hardware reset is accomplished by holding the RESET pin low for at least 1 ms. Once RESET is brought high,
the PHY will complete its reset sequence within 5 ms. All outputs will be inactive until the PHY has completed
dc
its reset sequence. The PHY will keep the inputs inactive for 5 ms after the deassertion of hardware reset. The
hardware configuration pins and the PHY address pins will be read on the deassertion of hardware reset.
oa
The BCM53128 also has a software reset capability. To enable the software reset, a 1 must be written to the bit.
This bit is self-clearing, meaning that a second write operation is not necessary to end the reset. There is no
Br
effect if 0 is written to this bit. Mode pins that are labelled sample on reset (SOR) are latched during hardware
reset. Similarly, software resets also latch new values for the SOR mode pins.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 75
PHY Address
The BCM53128 has eight unique PHY addresses for MII management of the internal PHYs. The PHY
addresses for each port are as follows,
• PHY address for Port 0 is 0
l
Super Isolate Mode
tia
When in Super Isolate mode, the transmit and receive functions on the Copper Media Dependent Interface are
en
disabled (No link will be established with the PHY’s copper link partner). Any data received from the switch will
be ignored by the BCM53128 and no data will be sent from the BCM53128.
Standby Power-Down Mode

fid
on
The BCM53128 can be placed into standby power-down mode using software commands. In this mode, all PHY
C
functions except for the serial management interface are disabled. To enter standby power-down mode, set MII
Control register (Page 10h–17h: Address 00h), bit 11 = 1. There are three ways to exit standby power-down
om
mode:
• Clear MII Control register (address 00h), bit 11 = 0.
• Set the software RESET bit 15, MII Control register (Page 10h–17h: Address 00h).
dc
• Assert the hardware RESET pin.

oa
Read or write operations to any MII register, other than MII Control register, while the device is in the standby
power-down mode returns unpredictable results. Upon exiting standby power-down mode, the BCM53128
Br
remains in an internal reset state for 40 µs and then resumes normal operation.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 76
Auto Power-Down Mode

The BCM53128 can be placed into auto power-down mode. Auto power-down mode reduces device power
when the signal from the copper link partner is not present. The auto power-down mode works whether the
device is in Auto-negotiation Enabled or Forced mode. This mode is enabled by setting bit 5 =1 of Auto Power-
Down register. When auto power-down mode is enabled, the BCM53128 automatically enters the low-power
mode when energy on the line is lost, and it resumes normal operation when energy is detected. When the
BCM53128 is in auto power-down mode, it wakes up after 2.7s or 5.4s, which determined by bit 4 of Auto Power-
Down register, and sends link pulses while monitoring for energy from the link partner. The BCM53128 enters
normal operation and establishes a link if energy is detected, otherwise the wake-up mode continues for a
duration of 84 ms to 1260 ms. This is determined by the timer bits [3:0] of Auto Power-Down register. before
going back to low-power mode.
External Loopback Mode
l
The External Loopback mode allows in-circuit testing of the BCM53128 as well as the transmit path through the
tia
magnetics and the RJ-45 connector. External loopback can be performed with and without a jumper block.
External loopback with a jumper block tests the path through the magnetics and RJ-45 connector. External
en
loopback without the jumper block only tests the BCM53128’s transmit and receive circuitry. In 1000BASE-T,
100BASE-TX, and 10BASE-T modes, a jumper block must be inserted into the RJ-45 connector to support
fid
external loopback. The jumper block should have the following RJ-45 pins connected together:
1------------3
on
2------------6
4------------7
C
5------------8
Table 12 to Table 17 on page 78 describe how the external loopback is enabled for 1000BASE-T, 100BASE-TX,
om
and 10BASE-T modes with and without a jumper block.
Table 12: 1000BASE-T External Loopback with External Loopback Plug

dc
Register Writes Comments

oa
Write 1800h to 1000BASE-T Control register Enable 1000BASE-T Master Mode

Write 0040h to MII Control register Enable Force 1000BASE-T
Br
Write 8400h to Auxiliary Control register Enable External Loopback Mode with external loopback
plug
Table 13: 1000BASE-T External Loopback Without External Loopback Plug

Write 1800h to 1000BASE-T Control register Enable 1000BASE-T Master Mode
Write 0040h to MII Control register Enable Force 1000BASE-T
Write 8400h to Auxiliary Control register Enable External Loopback Mode
Write 0014h to Auxiliary Control register Enable External Loopback Mode without external loopback
plug
Broadcom®
April 6, 2016 • 53128-DS07-R Page 77
Table 14: 100BASE-TX External Loopback with External Loopback Plug

Write 2100h to MII Control register Enable Force 100BASE-TX full-duplex mode
Table 15: 100BASE-TX External Loopback Without External Loopback Plug
Register Writes Comment

Write 2100h to MII Control register Enable Force 100BASE-TX full-duplex mode
Write 0014h to Auxiliary Control register Enable external loopback mode without external loopback
plug
Table 16: 10BASE-T External Loopback with External Loopback Plug
l
tia
Write 0100h to MII Control register Enable Force 10BASE-T full-duplex mode
en
Register Writes
fid
Table 17: 10BASE-T External Loopback Without External Loopback Plug
Comments
on
Write 0100h to MII Control register Enable Force 10BASE-T full-duplex mode
Write 0014h to Auxiliary Control register Enable external loopback mode without external loopback
C
plug
om
Note: To exit the External Loopback mode, a software or hardware reset is recommended.
dc
oa
Full-Duplex Mode
Br
The BCM53128 supports full-duplex operation. While in full-duplex mode, a transceiver can simultaneously
transmit and receive packets on the cable.
Copper Mode
When auto-negotiation is disabled, full-duplex operation can be enabled by setting bit 8 of MII Control register.
When auto-negotiation is enabled, the full-duplex capability is advertised for:

• 10BASE-T when bit 6 of Auto-Negotiation Advertisement register is set.
• 100BASE-T when bit 8 Auto-Negotiation Advertisement register is set.
• 1000BASE-T when bit 9 of 1000BASE-T Control register is set.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 78
BCM53128 Data Sheet Frame Management
Master/Slave Configuration
In 1000BASE-T mode, the BCM53128 and its link partner perform loop timing. One end of the link must be
configured as the timing master, and the other end as the slave. Master/slave configuration is performed by the
auto-negotiation function. The auto-negotiation function first looks at the manual master/slave configuration bits
advertised by the local PHY and the link partner. If neither PHY requests manual configuration, then the auto-
negotiation function looks at the advertised repeater/DTE settings. If one PHY is advertised as a repeater port
and the other is advertised as a DTE port, then the repeater port is configured as the master and the DTE port
as the slave. Each end generates an 11-bit random seed if the two settings are equal, and the end with the
higher seed is configured as the master. If the local PHY and the link partner generate the same random seed,
then auto-negotiation is restarted.
If both ends of the link attempt to force the same manual configuration (both master or both slave), or the random
seeds match seven consecutive times, then the BCM53128 sets the Master/Slave Configuration Fault bit in the
1000BASE-T Status register, and auto-negotiation is restarted. This is used to set the BCM53128 to manual
master/slave configuration or to set the advertised repeater/DTE configuration.
l
tia
Next Page Exchange
en
The 1000BASE-T configuration requires the exchange of three auto-negotiation next pages between the
fid
BCM53128 and its link partner. Exchange of 1000BASE-T Next Page information takes place automatically
when the BCM53128 is configured to advertise 1000BASE-T capability.
on
The BCM53128 also supports software controlled Next Page exchanges. This includes the three 1000BASE-T
Next Pages, which are always sent first. The BCM53128 automatically generates the appropriate message code
C
field for the 1000BASE-T pages. When the BCM53128 is not configured to advertise 1000BASE-T capability,
the 1000BASE-T Next Pages are not sent.
om
When the BCM53128 is not configured to advertise 1000BASE-T capability and bit 15 of the Auto-Negotiation
Advertisement register is set, the BCM53128 does not advertise Next Page ability.
dc
oa
Frame Management
Br
The BCM53128 provides a Frame Management block that works in conjunction with one of the GMII ports
operate in IMP mode as the full duplex packet streaming interface to the external CPU, with in-band messaging
mechanism for management purpose.
In-Band Management Port

The GMII port can be configured as the management port, using the Frame Management Port bits in the Global
Management Configuration register. When the GMII port is defined as the Frame Management Port, it is referred
to as the in-band management port (IMP).
The IMP can be used as a full-duplex 10/100/1000-Mbps port, which can be used to forward management
information to the external management agent, such as BPDUs, mirrored frames, or frames addressed to other
static address entries that have been identified as a special interest to the management system.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 79
As IMP is defined as the frame management port, normal frame data is forwarded to the port based on the state
of the RX_UCST_EN, RX_MCST_EN and RX_BCST_EN bits in the IMP Port Control register. If these bits are
cleared, no frame data will be forwarded to the Frame Management Port, with the exception that frames meeting
the mirror ingress/egress rules criteria, will always be forwarded to the designated frame management port.
Packets transferred over the IMP port are tagged with the Broadcom proprietary header to carry the necessary
information which is of interest to the management entity running on the CPU, as shown below, except for the
PAUSE frame. The IMP port must support normal Ethernet pause based flow control mechanism.
Figure 10: IMP Packet Encapsulation Format
l
tia
en
fid
on
C
om
The BRCM tag is designed for asymmetric operation across the IMP port. The information carried from the
switching device to the CPU is different from the information carried from the CPU to the switching device.
dc
Similarly, the host system must insert the BRCM tag fields into frames it wished to send into the management
port, to be routed to specific egress ports. The OPCODE within the tag field determines how the frame is
handled, and allows frames to be forwarded using the normal address lookup using a port ID designation within
oa
the tag.
Br
The BRCM tag are transmitted with the convention of highest significant octet first, followed by the next lowest
significant octet, and so on, with the least significant bit of each octet transmitted out from the MAC first. So, for
the BRCM tag field in Table 18 on page 81 the most significant octet would be transmitted first (bits [24:31]), with
bit 24 being the first bit transmitted.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 80
Broadcom Tag Format for Egress Packet Transfer

When a packet is forwarded by the switching device to the external CPU for processing, the BRCM tag is
formatted as shown in Table 18.
Table 18: Egress Broadcom Tag Format (IMP to CPU)
31–29 28–24 23–16 15–8 7–5 4–0

OPCODE = Reserved Reserved REASON_CODE[7: TC[2:0] SRC_PID[4:0
000 0] ]
63–61 60–38 37 36–32
OPCODE = Reserved T/R T/R_PID[4:0]
001
31–0
l
tia
TIME_STAMP[31:0]
en
• OPCODE 000
This indicates the packet transfer with explicit reasons to help the external CPU to direct the packet for the
•
appropriate packet processing entities.
REASON_CODE [7:0] fid
on
This indicates the reasons why the packet is forwarded to the external CPU so that the CPU can identify the
appropriate software routines for packet processing.
C
– Bit [0] indicates mirroring

– Bit [1] indicates SA learning
om
– Bit [2] indicates switching

– Bit [3] indicates protocol termination
dc
– Bit [4] indicates protocol snooping

– Bit [5] indicates flooding/exception processing
oa
– Bit [6] and Bit[7] are reserved

• TC [2:0]
Br
This indicates the traffic class classified by the switching device when forwarding the packet to the CPU.
• SRC_PID [4:0]
This indicates the ingress port of the switching device where the packet is received.
• OPCODE 001
This indicates a packet transfer with explicit time stamp recorded at the port where it was transmitted or
received (indicated by the T/R_PID) for IEEE 802.1as protocol implementation.
• T/R
This indicates the type of time stamp. 0 indicates the time stamp recorded when the packet was received
through the port (indicated by the T/R_PID); 1 indicates the time stamp recorded when the packet was
transmitted through the port (indicated by the T/R_PID).
Broadcom®
April 6, 2016 • 53128-DS07-R Page 81
• T/R_PID [4:0]
This indicates the port through which the packet was transmitted when T/R = 1, or the port through which
the packet was received when T/R = 0.
• TIME_STAMP [31:0]
This carries the time stamp value recorded at the ingress port for a received TS protocol packet.
Broadcom Tag Format for Ingress Packet Transfer

For packet transfer from the external CPU to the switching device, the BRCM tag is formatted as shown below.
Table 19: Ingress BRCM Tag (CPU to IMP)
31–29 28–26 25–24 23–0

OPCODE = 000 TC[2:0] TE[1:0] Reserved
l
31–29 28–26 25–24 23 22–0
tia
OPCODE = 001 TC[2:0] TE[1:0] TS DST_MAP[22:0]
en
• OPCODE 000
fid
It indicates that the external CPU is not dictating how the packet is forwarded, and the packet is forwarded
by the switching device based on the original Ethernet packet information.
on
• OPCODE 001
This indicates the packet is forwarded to multiple (or single) egress ports by the switching device based on
C
the explicit direction of the external CPU.

• DST_MAP [22:0]
om
This indicates the egress port bit map to which the external CPU intends to forward the packet.
• TC [2:0]
dc
This indicates the traffic class with which the external CPU intends to forward the packet.
• TS (time stamp request)
oa
This indicates whether the transmit time stamped at the egress port should be reported back to the external
CPU.
Br
• TE (tag enforcement)
This indicates the 802.1Q/P tagging/untagging encapsulation enforcement for the packet transmission.
00: No enforcement (follow VLAN untag mask rules)
01: Untag enforcement
10: Tag enforcement
11: Reserved
Broadcom®
April 6, 2016 • 53128-DS07-R Page 82
BCM53128 Data Sheet MIB Engine
MIB Engine
The MIB Engine is responsible for processing status words received from each port. Based on whether it is a
receive status or transmit status, appropriate MIB counters are updated. The BCM53128 implement 70-plus MIB
counters on a per-port basis. MIB counters can be categorized into three groups: receive-only counters,
transmit-only counters, and receive or transmit counters. This latter group can, as a group, be selectively
steered to the receive or transmit process on a per-port basis. The section below describes each individual
counter.
The BCM53128 offers the MIB snapshot feature per port enabled. A snapshot of a selected port MIB registers
can be captured and available to the users while MIB counters are continuing to count.
MIB Counters Per Port
l
tia
Receive Only Counter (19) Description of Counter
en
Table 20: Receive Only Counter (19) Description of Counter
Field Description
RxDropPkts (32 bit)
fid
The number of good packets received by a port that were dropped due to a
lack of resources (e.g., lack of input buffers) or were dropped due to a lack of
on
resources before a determination of the validity of the packet was able to be
made (e.g., receive FIFO overflow). The counter is only incremented if the
receive error was not counted by the RxExcessSizeDisc, the
C
RxAlignmentErrors, or the RxFCSErrors counters.

RxOctets (64 bit) The number of data bytes received by a port (excluding preamble, but
om
including FCS), including bad packets.

RxBroadcastPkts (32 bit) The number of good packets received by a port that are directed to the
broadcast address. This counter does not include errored broadcast packets
dc
or valid multicast packets. The maximum packet size can be programmed.

RxMulticastPkts (32 bit) The number of good packets received by a port that are directed to a multicast
oa
address. This counter does not include errored multicast packets or valid
broadcast packets. The maximum packet size can be programmed.
Br
RxSAChanges (32 bit) The number of times the SA of good receive packets has changed from the
previous value. A count greater than 1 generally indicates the port is
connected to a repeater-based network. The maximum packet size can be
programmed.
RxUndersizePkts (32 bit) The number of good packets received by a port that are less than 64 bytes
long (excluding framing bits, but including the FCS).
RxOversizePkts (32 bit) The number of good packets received by a port that are greater than standard
max frame size. The maximum packet size can be programmed.
RxFragments (32 bit) The number of packets received by a port that are less than 64 bytes
(excluding framing bits) and have either an FCS error or an alignment error.
RxJabbers (32 bit) The number of packets received by a port that are longer than 1522 bytes and
have either an FCS error or an alignment error.
RxUnicastPkts (32 bit) The number of good packets received by a port that are addressed to a
unicast address. The maximum packet size can be programmed.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 83
Table 20: Receive Only Counter (19) Description of Counter (Cont.)
Field Description
RxAlignmentErrors (32 bit) The number of packets received by a port that have a length (excluding
framing bits, but including FCS) between 64 and standard max frame size,
inclusive, and have a bad FCS with a nonintegral number of bytes.
RxFCSErrors (32 bit) The number of packets received by a port that have a length (excluding
framing bits, but including FCS) between 64 and standard max frame size,
inclusive, and have a bad FCS with an integral number of bytes.
RxGoodOctets (64 bit) The total number of bytes in all good packets received by a port (excluding
framing bits, but including FCS). The maximum packet size can be
programmed.
JumboPktCount (32 bit) The number of good packets received by a port that are greater than the
standard maximum size and less than or equal to the jumbo packet size,
regardless of CRC or alignment errors.
RxPausePkts (32 bit) The number of PAUSE frames received by a port. The PAUSE frame must
l
have a valid MAC Control Frame EtherType field (88–08h), have a destination
tia
MAC address of either the MAC Control frame reserved multicast address
(01-80-C2-00-00-01) or the unique MAC address associated with the specific
en
port, a valid PAUSE opcode (00–01), be a minimum of 64 bytes in length
(excluding preamble but including FCS), and have a valid CRC. Although an
IEEE 802.3-compliant MAC is only permitted to transmit PAUSE frames when
fid
in full-duplex mode with flow control enabled and with the transfer of PAUSE
frames determined by the result of auto-negotiation, an IEEE 802.3 MAC
receiver is required to count all received PAUSE frames, regardless of its half/
on
full-duplex status. An indication that a MAC is in half-duplex with the
RxPausePkts incrementing indicates a noncompliant transmitting device on
the network.
C
RxSymbolErrors (32 bit The total number of times a valid-length packet was received at a port and
at least one invalid data symbol was detected. The counter only increments
om
once per carrier event and does not increment on detection of a collision
during the carrier event.
RxDiscard (32 bit) The number of good packets received by a port that were discarded by the
dc
Forwarding Process.
InRangeErrors (32 bit) The number of packets received with good CRC and one of the following: (1)
oa
The value of length/type field is between 46 and 1500 inclusive, and does not
match the number of (MAC client data + PAD) data octets received, OR (2)
The value of length/type field is less than 46, and the number of data octets
Br
received is greater than 46 (which does not require padding).

OutOfRangeErrors (32 bit) The number of packets received with good CRC and the value of length/type
field is greater than 1500 and less than 1536.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 84
Transmit Counters Only (19) Description of Counter

Table 21: Transmit Counters Only (19) Description of Counter
Field Description
TxDropPkts (32 bit) This counter is incremented every time a transmit packet is dropped due to
lack of resources (e.g., transmit FIFO underflow), or an internal MAC sublayer
transmit error not counted by either the TxLateCollision or the
TxExcessiveCollision counters.
TxOctets (64 bit) The total number of good bytes of data transmitted by a port (excluding
preamble but including FCS).
TxBroadcastPkts (32 bit) The number of good packets transmitted by a port that are directed to a
broadcast address. This counter does not include errored broadcast packets
or valid multicast packets.
TxMulticastPkts (32 bit) The number of good packets transmitted by a port that are directed to a
multicast address. This counter does not include errored multicast packets or
l
valid broadcast packets.
tia
TxCollisions (32 bit) The number of collisions experienced by a port during packet transmissions.
TxUnicastPkts (32 bit) The number of good packets transmitted by a port that are addressed to a
en
unicast address.
TxSingleCollision (32 bit) The number of packets successfully transmitted by a port that have
TxMultipleCollision (32 bit) fid

experienced exactly one collision.
The number of packets successfully transmitted by a port that have
on
experienced more than one collision.
TxDeferredTransmit (32 bit) The number of packets transmitted by a port for which the first transmission
attempt is delayed because the medium is busy. This only applies to the Half
C
Duplex mode, while the Carrier Sensor Busy.

TxLateCollision (32 bit) The number of times that a collision is detected later than 512 bit-times into
om
the transmission of a packet.

TxExcessiveCollision (32 bit) The number of packets that are not transmitted from a port because the
packet experienced 16 transmission attempts.
dc
TxPausePkts (32 bit) The number of PAUSE events at each port.

TxFrameInDisc (32 bit) The number of valid packets received which are discarded by the forwarding
oa
process due to lack of space on an output queue (not maintained or reported

in the MIB counters). Located in the Congestion Management registers (Page
0Ah). This attribute only increments if a network device is not acting in
Br
compliance with a flow control request, or the BCM53128 internal flow-control/

buffering scheme has been configured incorrectly.
TxQ0PKT(32 bit) The total number of good packets transmitted on COS0, which is specified in
MIB queue select register when QoS is enabled.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 85
Table 21: Transmit Counters Only (19) Description of Counter (Cont.)
Field Description
Transmit or Receive Counters (10) Description of Counter

Table 22: Transmit or Receive Counters (10) Description of Counter
Field Description
Pkts64Octets (32 bit) The number of packets (including error packets) that are 64 bytes long.
Pkts65to127Octets (32 bit) The number of packets (including error packets) that are between 65 and 127
bytes long.
Pkts128to255Octets (32 bit) The number of packets (including error packets) that are between 128 and
l
255 bytes long.
tia
Pkts256to511Octets (32 bit) The number of packets (including error packets) that are between 256 and 511
bytes long.
en
Pkts512to1023Octets (32 bit) The number of packets (including error packets) that are between 512 and
1023 bytes long.
Pkts1024toMaxPktOctets (32
bit)
fid
The number of packets that (include error packets) are between 1024 and the
standard maximum packet size inclusive.
on
The total number of counters per port is 43.
C
Table 23 identifies the mapping of the BCM53128 MIB counters and their generic mnemonics to the specific
counters and mnemonics for each of the key IETF MIBs that are supported. Direct mappings are defined.
om
However, there are several additional statistics counters, which are indirectly supported that make up the full
complement of the counters required to fully support each MIB. These are shown in Table 24 on page 88.
dc
Finally, Table 25 on page 89 identifies the additional counters supported by the BCM53128 and references the
specific standard or reason for the inclusion of the counter.
oa
Table 23: Directly Supported MIB Counters

Br
Ethernet-Like MIB Bridge MIB MIB II Interface RMON MIB

BCM53128 MIB RFC 1643 RFC 1493 RFC 1213/1573 RFC 1757
RxDropPkts dot3StatsInternalM dot1dTpPortInDiscards ifInDiscards –
ACReceiveErrors
RxOctets – – ifInOctets etherStatsOctets
RxBroadcastPkts – – ifInBroadcastPkts etherStatsBroadcast
Pkts
RxMulticastPkts – – ifInMulticastPkts etherStatsMulticast
Pkts
RxSAChanges Note 2 Note 2 Note 2 Note 2
RxUndersizePkts – – – etherStatsUndersize
Pkts
Broadcom®
April 6, 2016 • 53128-DS07-R Page 86
Table 23: Directly Supported MIB Counters (Cont.)

RxOversizePkts dot3StatsFrameToo – – etherStatsOverrsize
Longs Pkts
RxFragments – – – eytherStatsFragment
s
RxJabbers – – – etherStatsJabbers
RxUnicastPkts – – ifInUcastPkts –
RxAlignmentErrors dot3StatsAlignment – – –
Errors
RxFCSErrors dot3StatsFCSErrors – – –
RxGoodOctets – – – –
RxExcessSizeDisc Note 2 Note 2 Note 2 Note 2
l
tia
RxPausePkts Note 2 Note 2 Note 2 Note 2
RxSymbolErrors Note 2 Note 2 Note 2 Note 2
en
Note 1 – – ifInErrors –
Note 1 – – ifInUnknownProtos –
Note 1
TxDropPkts
–
dot3StatsInternal
MACTransmitErrors
– fid
dot1dTpPortInFrames –
ifOutDiscards
–
–
on
TxOctets – – ifOutOctets –
Note 3
C
Note 1 – dot1dTpPortOutFrame – –
s
om
TxBroadcastPkts – – ifOutBroadcastPkts –
TxMulticastPkts – – ifOutMulticastPkts –
dc
TxCollisions – – – etherStatsCollisions
TxUnicastPkts – – ifOutUcastPkts –
oa
TxSingleCollision dot3StatsSingle – – –
CollisionFrames
TxMultipleCollision dot3StatsMultiple – – –
Br
CollisionFrames
TxDeferredTransmit dot3StatsDeferred – – –
Transmissions
TxLateCollision dot3StatsLate – – –
Collision
TxExcessiveCollision dot3StatsExcessive – – –
Collision
TxFrameInDisc Note 2 Note 2 Note 2 Note 2
TxPausePkts Note 2 Note 2 Note 2 Note 2
Note 4 dot3StatsCarrier – – –
SenseErrors
Note 1 – – ifOutErrors –
Broadcom®
April 6, 2016 • 53128-DS07-R Page 87
Table 23: Directly Supported MIB Counters (Cont.)

Pkts64Octets – – – etherStatsPkt64
Octets
Pkts65to127Octets – – – etherStatsPkt65to
127Octets
255Octets
511Octets
1023Octets
Pkts1024toMaxPkt – – – etherStatsPkt1024to
Octets MaxPktOctets
l
tia
Note 1 – – – etherStatsDrop
Events
en
Note 1 – – – etherStatsPkts
Note 1 – – – etherStatsCRCAlign
Errors
Note 4 dot3StatsSQETest –
Errors fid – –
on
Note 1: Derived by summing two or more of the supported counters. See Table 24 for specific details.
C
Note 2: Extensions required by recent standards developments or BCM53128 operation specifics.

Note 3: The MIB II interfaces specification for if OutOctets includes preamble/SFD and errored bytes. Because
IEEE 802.3-compliant MACs have no requirement to keep track of the number of transmit bytes in an errored
om
frame, this count is impossible to maintain. The TxOctets counter maintained by the BCM53128 is consistent
with good bytes transmitted, excluding preamble, but including FCS. The count can be adjusted to more closely
match the if OutOctets definition by adding the preamble for TxGoodPkts and possibly an estimate of the octets
dc
involved in TxCollisions and TxLateCollision.

Note 4: The attributes TxCarrierSenseErrors and TxSQETestErrors are not supported in the BCM53128. These
attributes were originally defined to support coax-based AUI transceivers. The BCM53128 integrated
oa
transceiver design means these error conditions are eliminated. MIBs intending to support such counters should
return a value of 0 (not supported).
Br
Table 24: Indirectly Supported MIB Counters

RxErrorPkts = – – ifInErrors –
RxAlignmentErrors +
RxFCSErrors +
RxFragments +
RxOversizePkts +
RxJabbers
– – ifInUnknownProtos –
Broadcom®
April 6, 2016 • 53128-DS07-R Page 88
Table 24: Indirectly Supported MIB Counters (Cont.)

RxGoodPkts = – dot1dTpPortIn – –
RxUnicastPkts + Frames
RxMulticastPkts +
RxBroadcastPkts
DropEvents = – – – etherStatsDrop
RxDropPkts + Events
TxDropPkts
RxTotalPkts = – – – etherStatsPkts
RxGoodPkts +
RxErrorPkts
RxCRCAlignErrors = – – – etherStatsCRCAlign
RxCRCErrors + Errors
l
tia
RxAlignmentErrors
– dot3StatsSQETest – – –
Errors
en
RxFramesTooLong = dot3StatsFrameToo – – –
RxOversizePkts + Longs
RxJabber
TxGoodPkts = – dot1dTpPortOut fid – –
on
TxUnicastPkts + Frames
TxMulticastPkts +
TxBroadcastPkts
C
TxErrorPkts = – – ifOutErrors –
TxExcessiveCollision
om
+
TxLateCollision
Note 1
dc
Note 1: The number of packets transmitted from a port that experienced a late collision or excessive collisions.
oa
While some media types operate in half-duplex mode, frames that experience carrier sense errors are also
summed in this counter. The BCM53128 integrated design means this error condition is eliminated.
Br
Table 25: BCM53128 Supported MIB Extensions
BCM53128 MIB Appropriate Standards Reference

RxSAChanges IEEE 802.3u Clause 30—Repeater Port Managed Object Class
a SourceAddressChanges.
RxExcessSizeDisc The BCM53128 cannot store packets in excess of 1536 bytes (excluding preamble/
SFD, but inclusive of FCS). This counter indicates packets that were discarded by
the BCM53128 due to excessive length.
RxPausePkts IEEE 802.3x Clause 30—PAUSE Entity Managed Object Class
aPAUSEMACCtrlFramesReceived.
RxSymbolErrors IEEE 802.3u Clause 30—Repeater Port Managed Object Class
aSymbolErrorDuringPacket.
TxFrameInDisc Internal diagnostic use for optimization of flow control and buffer allocation
algorithm.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 89
BCM53128 Data Sheet Integrated High-Performance Memory
Table 25: BCM53128 Supported MIB Extensions (Cont.)
BCM53128 MIB Appropriate Standards Reference

TxPausePkts The number of PAUSE events at a given port.
Integrated High-Performance Memory

The BCM53128 embed a 192 KB high-performance SRAM for storing packet data. This eliminates the need for
external memory and allows for the implementation of extremely low-cost systems.
The internal RAM controller efficiently executes memory transfers and achieves nonblocking performance for
stand-alone 8-port applications.
l
tia
Switch Controller
en
The core of the BCM53128 devices is a cost-effective and high-performance switch controller. The controller
manages packet forwarding between the MAC receive and transmit ports through the frame buffer memory with
fid
a store and forward architecture. The switch controller encompasses the functions of buffer management,
memory arbitration, and transmit descriptor queueing.
on
Buffer Management
C
The frame buffer memory is divided into pages (units of data consisting of 256 bytes each). Each received
om
packet may be allocated more than one page. For example, six pages are required to store a 1522-byte frame.
Frame data is stored in the buffer memory as the packet is received. After reception, the frame is queued to the
egress port(s) transmit queue. This list tracks the transmission of the packet. After successful packet
dc
transmission, the buffer memory is released to the free buffer pool.

oa
Memory Arbitration
Br
Processes requesting access to the internal memory include the receive and transmit frame data handlers,
address resolution, the VLAN lookup, learning and aging functions, egress descriptor update, and output-port
queue managers. These processes are arbitrated to provide fair access to the memory and minimize the latency
of critical processes to provide a fully nonblocking solution.
Transmit Output Port Queues

Frames are maintained in the egress port using a linked list. Two levels of linked lists are used to maintain one
output queue (see the figure below). The first level is the TXQ linked list, and the second level is the buffer tag
linked list. The TXQ linked list is used to maintain frame TC order for each port. For each frame, the buffer tag
linked list is used to maintain the order of the buffer pages corresponding to each frame.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 90
BCM53128 Data Sheet Switch Controller
Each egress port supports up to six transmit queues for servicing Quality of Service (QoS). All six transmit
queues share the 768 entries of the TXQ table. The TXQ table is maintained as a linked list, and each node in
the TXQ uses one entry in the TXQ table. The TXQ size for each priority can be programmed to up to 768
entries.
When the QoS function has been turned off, the switch controller maintains one output queue for each egress
port. The TXQ table is maintained in a per-port individual internal memory. Each node in the queue represents
a pointer that points to a frame buffer tag. Each buffer tag includes frame information and a pointer to the next
buffer tag. Each buffer tag has an associated page allocated in the frame buffer. For a packet with a frame size
larger than 256 bytes, multiple buffer tags are required. For instance, a 9720-byte jumbo frame requires 38
buffer tags for handling the frame.
Figure 11: TXQ and Buffer Tag Structure
TXQ Buffer Tag Data Buffer
l
tia
Frame 0,0 Page 0,0,0 256B
en
Priority 0 Frame 0,2 Page 0,2,0 256B
Empty Page 0,1,1 256B
fid
Priority 1
Priority 2 Frame 3,0 Page 3,0,0 256B
Priority 3
on
Empty Page 3,1,1 256B
C
Empty Empty 256B

om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 91
BCM53128 Data Sheet System Interfaces
Section 4: System Interfaces
Overview of System Interfaces

The BCM53128 include the following interfaces:
• “Copper Interface”
• “Frame Management Port Interface” on page 93
• “Configuration Pins” on page 94
• “Programming Interfaces” on page 95
• “MDC/MDIO Interface” on page 112
• “LED Interfaces” on page 119
l
tia
Each interface is discussed in detail in these sections.
en
Copper Interface
fid
The internal PHYs transmit and receive data using the analog copper interface. This section discusses the
on
following topics:
• “Auto-Negotiation” on page 92
C
• “Line-side (Remote) Loopback Mode” on page 93

om
• “Reverse MII Port (RvMII)” on page 93

• “GMII Port” on page 94
• “RGMII Port” on page 94
dc
• “SPI-Compatible Programming Interface” on page 96

oa
• “EEPROM Interface” on page 110

• “MDC/MDIO Interface Register Programming” on page 112
Br
• “PseudoPHY” on page 113
Auto-Negotiation
The BCM53128 negotiate a mode of operation over the copper media using the auto-negotiation mechanism
defined in the IEEE 802.3u and IEEE 802.3ab specifications. When the auto-negotiation function is enabled, the
BCM53128 automatically choose the mode of operation by advertising its abilities and comparing them with
those received from its link partner. The BCM53128 can be configured to advertise the following modes:
• 1000BASE-T full-duplex and/or half-duplex
• 100BASE-TX full-duplex and/or half-duplex
• 10BASE-T full-duplex and/or half-duplex
Broadcom®
April 6, 2016 • 53128-DS07-R Page 92
BCM53128 Data Sheet Frame Management Port Interface
The transceiver negotiates with its link partner and chooses the highest common operating speed and duplex
mode, commonly referred to as highest common denominator (HCD). Auto-negotiation can be disabled by
software control, but is required for 1000BASE-T operation.
Line-side (Remote) Loopback Mode

The line-side loopback mode allows the testing of the copper interface from the link partner. This mode is
enabled by setting bit 15 of the Miscellaneous Test register. The MDI receive packet is passed through the PCS
and sent back out as the MDI transmit packet. The PCS receive data appears on the internal MAC interface.
Frame Management Port Interface

The dedicated frame management port provides high-speed connection to transfer management packets to an
l
external management agent. For more information about frame management, see “Frame Management” on
tia
page 79. The port is configurable to Reverse MII (RvMII), GMII, or RGMII using strap pins or software
configuration.
en
MII Interface
fid
The Media Independent Interface (MII) serves as a digital data interface between the BCM53128 and an
on
external 10/100 Mbps management entity or a PHY entity. The BCM53128 provides a fully IEEE 802.3u-
compatible MII interface.
C
TMII (Turbo MII) and RvTMII (Reverse TMII) Interface

om
The TMII and RvTMII interfaces use the same hardware interface signals as the MII interface. The TMII mode
requires the SPEED setting bits in the IMP Port States Override Register (Page 00h: Address 0Eh) bits[3:2] to
dc
be set. The TMII mode supports 200 Mbps data rate over the existing MII interface by running the interface at
(up to) 50 MHz. The original MII timing is designed such that it can support 50 MHz clocking over the existing
oa
design.
Br
Reverse MII Port (RvMII)

The media independent interface (MII) serves as a digital data interface between the BCM53128 and an external
10/100 Mbps management entity. Reverse MII notation reflects the MII port interfacing to a MAC-based external
agent. The RvMII contains all the signals required to transmit and receive data at 100 Mbps and 10 Mbps for
both full-duplex and half-duplex operation. See Figure 12 on page 94 for connection information.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 93
BCM53128 Data Sheet Configuration Pins
Figure 12: RvMII Port Connection
MII-Compliant MAC Reverse MII Port
RXD[3:0] TXD[3:0]
RXC TXC
RXDV TXEN
CRS NC TXER
RXER and COL
TXD[3:0] RXD[3:0]
TXC RXC
l
tia
TXEN RXDV
TXER NC
en
RXER
fid
on
GMII Port
C
The Gigabit Media Independent Interface (GMII) serves as a digital data interface between the BCM53128 and
an external gigabit management entity. Transmit and receive data is clocked on the rising edge of the clocks.
om
The GMII transmits data synchronously using the TXD[7:0] and RXD[7:0] data signals.
dc
RGMII Port
The Reduced Gigabit Media Independent Interface (RGMII) serves as a digital data interface between the
oa
BCM53128 and an external gigabit management entity. Transmit and receive data is clocked on the rising and
falling edge of the clocks. This reduces the number of data signals crossing the MAC interface without affecting
Br
the data transmission rate. The RGMII transmits data synchronously using the TXD[3:0] and RXD[3:0] data
signals.
Configuration Pins
Initial configuration of the BCM53128 takes place during power-on/reset by loading internal control values from
hardware strap pins. The value of the pin is loaded when the reset sequence completes, and the pin transitions
to normal operation. Pull-up or pull-down resistors can be added to these pins to control the device
configuration. If the pins are left floating, the default value is determined based on the internal pull-up or pull-
down configuration. See “Signal Descriptions” on page 125 for more information.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 94
BCM53128 Data Sheet Programming Interfaces
Programming Interfaces
The BCM53128 can be programmed using the SPI interface or the EEPROM interface. The interfaces share a
common pin set that is configured using the CPU_EPROM_SEL strap pin. The “SPI-Compatible Programming
Interface” provides access for a general-purpose microcontroller, allowing read and write access to the internal
BCM53128 register space. It is configured to be compatible with the Motorola Serial Peripheral Interface (SPI)
protocol. Alternatively, the “EEPROM Interface” on page 110 can be connected to an external EEPROM for
writing register values upon power-up initialization.
The internal address space of the BCM53128 devices is broken into a number of pages. Each page groups a
logical set of registers associated with a specific function. Each page provides a logical address space of 256
bytes, although, in general, only a small portion of the address space in each page is utilized.
An explanation follows for using the serial interface with an SPI-compatible CPU (“SPI-Compatible
Programming Interface” on page 96) or an EEPROM (“EEPROM Interface” on page 110). Either mode can be
l
selected with the strap pin, CPU_EPROM_SEL. Either mode has access to the same register space.
tia
en
Serial Flash Interface
The BCM53128 offers a serial flash interface to store program code for the internal microcontroller (8051
fid
processor). The BCM53128 detects a flash memory device automatically and downloads the memory contents
upon power-up. The main purpose of the stored code is to configure and run the power savings mode, such as
on
Green mode or any application that the user wishes to run that can fit in the internal 8051 memory. The
embedded 8051 microcontroller has 128 KB of SRAM and 64 KB of ROM, supports receiving and transmitting
C
packets, and supports interleaved ROM/RAM access. The interface comprises four signal pins: chip select
(FCS), Flash clock (FCLK), Flash Serial Out (FSO), and Flash Serial In (FSI).
om
GPIO
dc
BCM53128 supports up to 8 GPIO pins. These GPIO pins can be used to connect to various external devices.
Upon power-up and reset, these pins become tristated. Enable GPIO pins through the GPIO Enable Register
oa
in 8051 Memory-Mapped Registers. They can be programmed to be either input or output pins via the GPIO
registers in 8051 Memory-Mapped Registers. The internal pull-up/pull-down of GPIOs is user-configurable
Br
through GPIO registers setting in 8051 Memory-Mapped Registers. Refer to the BCM53128 Programmer's
Reference Guide (document number 53128-PG1xx-R) for 8051 Memory-Mapped Registers detail information.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 95
SPI-Compatible Programming Interface

One way to access the BCM53128 internal registers is to use the serial peripheral interconnect (SPI) compatible
interface. This four-pin interface is designed to support a fully functional, bi-directional Motorola serial peripheral
interface (SPI) for register read/write accesses. The maximum speed of operation is 25 MHz. The SPI interface
shares pins with the EEPROM interface. To select the SPI interface, pull up or float the CPU_EPROM_SEL pin.
(The internal pull-up resistor defaults SPI interface over EEPROM interface.)
The SPI is a four-pin interface consisting of:

• Device select (SS: slave select, input to BCM53128)
• Device clock (SCK: which operates at speeds up to 25 MHz, input to BCM53128)
• Data write line (MOSI: Master Out/Slave In, input to BCM53128)
• Data read line (MISO: Master In/Slave Out, output from BCM53128)
Note: All the RoboSwitch™ SPI interfaces are designed to operate in slave mode. Therefore, the SCK
l
tia
and SS signals are driven by the external master host device when accessing the BCM53128
registers. For more detailed descriptions reader may refer to the Motorola SPI spec MC68HC08AS20-
en
Rev. 4.0.
SS: Slave Select

fid
on
The SS signal is used to select a slave device and to indicate the beginning of transmission. The BCM53128
SPI interface operates in the clock phase one (CPHA = 1) transmission format. In this format, the SS signal is
driven active low while the SCK signal is high, and remains low throughout the transmission including multiple-
C
byte transfers. The minimum time requirement between SS operation is 200 ns.
om
SCK: Serial Clock

The serial clock SCK maximum operating frequency is 25 MHz for the BCM53128 family of devices. The SCK
dc
is used to clock data into and out of the Slave ROBO device. The SCK signal is expected to remain high when
the interface is idle. This is because the BCM53128 SPI design is based on CPOL = 1 (Clock Polarity = 1). This
oa
is not programmable on BCM53128. The BCM53128 is designed so that data is driving by the falling edge and
sampling by the rising edge of the SCK clock. This clock is not a free-running clock, it is generated only during
Br
a data transaction, and remains high when the clock is idle.
MOSI: Master Output Slave Input

The MOSI signal is used by the master device to transmit the data to the slave device. The data is put on the
bus and is expected to be clocked in by a rising edge of the SCK clock signal. This line is used to issue a
command and to set the register page and address value of read/write operations.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 96
MISO: Master Input Slave Output

The MISO signal is used by the Slave device to output the data to the master device. The data is put on the bus
and is expected to be clocked out by a rising edge of the SCK clock signal. This line is used to transmit the status
and the content of the register of read operation.
A layer of protocol is added to the basic SPI definition to facilitate transfers from the BCM53128. This protocol
establishes the definition of the first 2 bytes issued by the master to the BCM53128 slave during an SPI transfer.
The first byte issued from the SPI master in any transaction is defined as a command byte, which is always
followed by a register address byte, and any additional bytes are data bytes.
The SPI mode supports two different access mechanisms, normal SPI and fast SPI, determined by the content
of the command byte. Figure 13 shows the normal SPI command byte, and Figure 14 on page 97 shows the
Fast SPI command byte. These two mechanisms should not be mixed in an implementation; the CPU should
always initiate transfers consistently with only one of the two mechanisms.
l
Figure 13: Normal SPI Command Byte
tia
0 1 1 MODE = 0 CHIP ID 2 CHIP ID 1 CHIP ID 0 Read/Write
(MSB) (LSB) (0/1)
en
Figure 14: Fast SPI Command Byte
Byte Offset Byte Offset Byte Offset MODE = 1 fid
CHIP ID 2 CHIP ID 1 CHIP ID 0 Read/Write
on
(MSB) (LSB) (MSB) (LSB) (0/1)
C
The MODE bit (bit 4) of the command byte determines the meaning of bits 7:5. If bit 4 is a 0, it is a normal SPI
command byte, and bits 7:5 should be defined as 011b. If bit 4 is a 1, bits 7:5 indicate a fast SPI command byte,
om
and bits 7:5 indicate the byte offset into the register that the BCM53128 starts to read from (byte offsets are not
supported for write operations).
In command bytes, bits[3:1] indicate the CHIP ID to be accessed. Because the BCM53128 operates as a single-
dc
chip system, the CHIP ID is 000.

oa
Note: The SS signal must also be active for any BCM53128 device to recognize that it is being
accessed.
Br
Bit 0 of the command byte is the R/W signal (0 = Read, 1 = Write) and determines the transmission direction of
the data.
The byte following the command byte is an 8-bit register address. Initially, this sets the page address, followed
by another command byte that contains the register base address in that page, which is used as the location to
store the next byte of data received in the case of a write operation, or the next address from which to retrieve
data in the case of a read operation. This base address increments as each byte of data is transmitted/received,
allowing a contiguous block data from a register to be stored/read in a single transmission. When the fast SPI
command byte mode is used, the actual start location of a read operation can be modified by the offset contained
in bits 7:5 of the command byte. Reading/writing data from/to separate registers, even if those registers are
contiguous in the current page, must be performed by supplying a new command byte and register address for
each register, with the address as defined in the appropriate page register map.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 97
Noncontiguous blocks are also stored/read through the use of multiple transmissions, which allow a new
command byte and register base address to be specified. The SS signal must remain low for the entire read or
write transaction, as shown in the following figures, with the transaction terminated by the deassertion of the SS
line by the master.
Figure 15: SPI Serial Interface Write Operation
Figure 16: SPI Serial Interface Read Operation
l
tia
en
fid
on
Figure 17 and Figure 18 on page 99 show the typical connection block diagram for SPI interface with/without
C
external PHY devices.

om
Without External PHY

dc
Figure 17: SPI Interface Without External PHY Device

oa
Slave
Br
Master
MOSI MOSI
RoboSwitch MISO MISO SPI
SCK SCK
Device
SS# SS#
Broadcom®
April 6, 2016 • 53128-DS07-R Page 98
External PHY Registers

The BCM53128 also uses the MDIO/MDC interface for polling registers of an external PHY. In this case, the
MDIO/MDC interface polls the external PHY registers pulling the data internal to the BCM53128. Then, the
external PHYs and retrieved from the register data using the SPI interface. The MDIO/MDC interface is not used
as a method to access internal PHY registers. This must be done using the SPI interface.
Figure 18: Accessing External PHY Registers
RoboSwitch
Slave Master
Switch MOSI MOSI
Internal MISO MISO SPI
Registers
Switch SCK SCK Device
l
SS# SS#
tia
Includes polled
registers of
Ext PHY
en
MDC MDIO
fid
External PHY registers are accessed
on
by the SPI comaptible device via the
Slave
SPI access to the switch registers
.
Ext
C
PHY
om
dc
Reading and Writing BCM53128 Registers Using SPI

oa
BCM53128 internal register read and write operations are executed by issuing a command followed by multiple
accesses of the SPI registers in the BCM53128. There are three SPI interface registers in the BCM53128 that
are used by the master device to access the internal switch registers. The SPI interface registers are:
Br
• SPI Page register (page: global, address: FFh): used to specify the value of the specific register pages.
• SPI Data I/O register (page: global, address: F0h): used to write and read the specific register’s content.
• SPI Status Register (page: global, address: FEh): used to check for an operation completion.
– Bit 7: SPIF, SPI read/write complete flag
– Bit 6: Reserved
– Bit 5: RACK, SPI read data ready acknowledgement
– Bit 4:3: Reserved
– Bit 2: MDIO_Start, Start/Done MDC/MDIO operation
– Bit 1: Reserved
– Bit 0: Reserved
Broadcom®
April 6, 2016 • 53128-DS07-R Page 99
The BCM53128 SPI interface supports the following operating modes.

• Normal read mode
• Fast read mode
• Normal write mode
Note: The RoboSwitch family does not support fast-write mode.
The details of each modes are described in the following paragraphs.
Normal Read Operation

Normal Read operation consists of five transactions (five SS operations):
l
1. Issue a Normal Read Command (opcode = 0x60) to poll the SPIF bit in the SPI Status register (0xFE) to
tia
determine the operation can start.
2. Issue a Normal Write command (opcode = 0x61) to write the register page value into the SPI Page register
en
0xFF.
3. Issue a Normal Read command (opcode = 0x60) to setup the required RoboSwitch register address.
fid
4. Issue a Normal Read command (opcode = 0x60) to poll the RACK bit in the SPI status register(0xFE) to
on
determine the completion of read (register content gets loaded in SPI Data I/O register).
5. Issue a Normal Read command (opcode = 0x60) to read the specific registers' content placed in the SPI
C
Data I/O register (0xF0).

om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 100
Figure 19: Normal Read Operation
Normal Read Mode

Start
Step 1
Issue Normal Read Command
(opcode=60) to poll data from
SPI Status Register (0xFE)
No
No Software Yes
SPIF (bit 7) =0?
Timeout ?
Yes
l
tia
Is accessed Yes
Register page same as
previous?
en
No
Step 2
Issue Normal Write Command
(opcode=61) to write the
fid
on
accessed register page value
into SPI Page Register (0xFF)
C
Step 3
om

(opcode=60) to setup the
accessed register address
dc
Step 4
oa
(opcode=60) to poll data from

SPI Status Register (0xFE)
No
Br
No Software
RACK (bit 5) =1?
Timeout ?
Yes
Yes
Step 5 Issue Normal Write Command
Issue Normal Read Command (opcode=61) to write the
(opcode=60) to read data from accessed register page value
SPI Data I/O Register (0xF0) into SPI Page Register (0xFF)
[MSB first, continute if more
bytes]
Done Task Abort
Broadcom®
April 6, 2016 • 53128-DS07-R Page 101
Example: Read from 1000BASE-T Control register (Page 10h, Offset 12h).
1. Issue a Normal Read command (opcode = 0x60) to check the SPIF bit in the SPI Status register (0xFE).
• Assert SS while SCK is high idle state
• Clock in a Normal Read Command Byte: 0 1 1 0 0 0 0 0 (opcode = 0x60)
• Clock in the SPI Status register address (0xFE)
• Clock out the SPI Status register value: 0 0 0 0 0 0 0 0 (SPIF bit 7=0)
• Deassert SS while SCK is high idle state
Figure 20: Normal Read Mode to Check the SPIF Bit of SPI Status Register
l
tia
en
fid
2. Issue a Normal Write command (opcode = 0x61) and write the accessed register page value of 0x10 into
SPI Page Reigster(0xFF)—this step is required only if previous read/write was not to/from Page 10h.
on
• Clock in a Normal Write Command Byte: 0 1 1 0 0 0 0 1 (opcode = 0x61)
C
• Clock in offset of Page register (0xFF)

• Clock in the accessed register page value,: 0 0 0 1 0 0 0 0 (Page register: 0x10)
om
Figure 21: Normal Read Mode to Setup the Accessed Register Page Value
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 102
3. Issue a Normal Read command (opcode = 0x60) and write the accessed register address value 0x12, and
clock out 8 bits to complete the read cycle, but discard result (this is where the state machine triggers a
internal data transfer from Address 0x12 to the SPI Data I/O register)
• Clock in the address of accessed register address value (0x12)
• Clock out eight clocks for the dummy read, and discard results on MISO
Figure 22: Normal Read Mode to Setup the Accessed Register Address Value (Dummy Read)
l
tia
en
fid
Note: This dummy read is always eight clock cycles, whether or not it is an 8-bit register.
on
C
4. Issue a Normal Read command (opcode = 0x60) to read the SPI Status to check the RACK bit for completion
of the register content transfer to the SPI Data I/O register.(this step may be repeated until the proper bit set
om
is read.)
dc

• Clock in offset for SPI Status Register (0xFE): 1 1 1 1 1 1 1 0
oa
• Clock out the content of SPI Status bits

• Repeat the polling until the content of SPI Status Register value: 0 0 1 0 0 0 0 0 (RACK bit 5= 1)
Br
Figure 23: Normal Read Mode to Check the SPI Status for Completion of Read
Broadcom®
April 6, 2016 • 53128-DS07-R Page 103
5. Issue a Normal Read command (opcode = 0x60) to read the data from the SPI Data I/O register:
• Clock in Command Byte: 0 1 1 0 0 0 0 0 (opcode = 0x60)
• Clock in offset of SPI Data I/O Register (0xF0)
• Clock out first data byte on MISO line: 0 0 0 0 0 0 0 0 (Byte 0: Bit 7 to Bit 0: MSB to LSB)
• Clock out next byte (in this case, last) on MISO line: 0 0 0 0 1 1 1 0 (Byte 1: Bit 15 to Bit 8)
• [Continue if more bytes]
Figure 24: Normal Read Mode to Obtain the Register Content
l
tia
en
Fast Read Operation fid
on
Fast Read operation consists of 3 transactions (three SS operations)
C
1. Issue a Normal Read Command (opcode = 0x60) to poll the SPIF bit in the SPI Status Register (0xFE) to
om
2. Issue a Fast Read command (opcode = 0x10) to setup the accessed Register Page value into the Page
register (0xFF).
dc
3. Issue a Fast Read command (opcode = 0x10) to setup the accessed register address value, to trigger an
actual read, and retrieve the accessed register content till the completion
oa
Fast Read mode process is different from Normal Read mode, once the switch receives a fast read command
followed by the register page and address information, the status and the data (register content) will be put on
Br
the MISO line without going through the SPI Status register or SPI Data I/O register. Once RACK bit of the bytes
following the Fast Read command with Address information is recognized the register content will be put on
MISO line immediately following the byte with RACK bit set. The Fast Read process is described in the following
paragraphs with a flowchart followed by a step by step description.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 104
Figure 25: Fast Read Operation
Fast Read Mode

Start
Step 1
Issue a Normal Read
Command (opcode=60) to poll
data from SPI Status Register
(0xFE)
No
No Software Yes
SPIF (bit 7) =0?
Timeout ?
Yes
l
tia
Is accessed Yes
en
previous?
No
Step 2
Issue a Normal Write fid
on
Command (opcode=61) to
write the accessed register
page value into SPI Page
Register (0xFF)
C
Step 3
om
Issue a Fast Read Command

(opcode=10) to setup the
accessed register address
dc
value to trigger an actual read

oa
Retrieve the first byte data to

check RACK is ready
Br
No
No Software
RACK=1
Timeout ?
Yes Yes
Retrieve the data starting Issue a Normal Write

from the lowest byte Command (opcode=61) to
Done Register (0xFF)
Task Abort
Broadcom®
April 6, 2016 • 53128-DS07-R Page 105
Example: Read from 1000BASE-T Control register (Page 10h, Offset 12h).
• Clock in a Normal Read Command Byte: 0 1 1 0 0 0 0 0(opcode = 0x60)
• Clock in the accessed register page value: 0 0 0 0 0 0 0 0 (SPIF bit 7=0)
l
tia
en
fid
2. Issue a Normal Write command (opcode = 0x61) and write the accessed register page value of 0x10 in to
SPI Page Reigster(0xFF) —this step is required only if previous read/write was not to/from Page 10h.
on
• Clock in a Fast Read Command Byte: 0 11 0 0 0 0 0 1 (opcode = 0x61)
C

• Clock in the accessed register page value: 0 0 0 1 0 0 0 0 (Page register: 0x10)
om
Figure 27: Fast Read Mode to Setup New Page Value

dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 106
3. Issue a Fast Read command (opcode = 0x10), followed by the Address of the accessed register (0x12),
check for a read completion by checking the RACK bit in the SPI Status register, and finally clock out the
read data.
• Clock in a Fast Read Command Byte: 0 0 0 1 0 0 0 0 0 (opcode = 0x10)
• Clock in the Address of accessed register (0x12)
• Clock out Bytes Until Bit 0 or Bit 1 = 1 : 0 0 0 0 0 0 0 1 (RACK bit 0=1)
• Clock out first data byte: 0 0 0 0 0 0 0 0 (Byte 0: Bit 7 to Bit 0)
• Clock out next data (in this case, last) byte: 0 0 0 0 1 1 1 0 (Byte 1: Bit 15 to Bit 8)
Figure 28: Fast Read to Read the Register
l
tia
en
fid
on
Note: There is an errata on the RACK output timing in Fast Read mode. The RACK (bit 0) must be
C
sampled prior to toggling the clock to shift out the bit 0.

om
Normal Write Operation

Normal Write operation consists of 3 transactions (three SS operations)
dc
1. Issue a Normal Read Command (opcode = 0x60) to poll the SPIF bit in the SPI Status register (0xFE) to
oa

2. Issue a Normal Write command (opcode = 0x61) to setup the accessed register page value into the page
Br
register (0xFF).
3. Issue a Normal Write command (opcode = 0x61) to setup the accessed register address value, followed by
the write content starting from a lower byte.
The Normal Write Mode process is described in the following paragraphs with a flowchart followed by a step by
step description.
Note: The RoboSwitch does not support Fast Write Mode.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 107
Figure 29: Normal Write Operation
Normal Write Mode

Start
Step 1
Issue a Normal Read
Command (opcode=60) to poll
data from SPI Status Register
(0xFE)
No
No Software
SPIF=0?
Timeout ?
l
Yes Yes
tia
Is accessed
en
Yes
previous?
No
Step 2
fid
on
Issue a Normal Write
Issue a Normal Write Command (opcode=61) to
Command (opcode=61) to write the accessed register
C

page value into SPI Page Register (0xFF)
Register (0xFF)
om
Step 3
dc
Issue a Normal Write

Command (opcode=61) to
setup the accessed register
oa
address, followed by the write

content starting from the
lowest byte
Br
Task Abort
Done
Example: 0x1600h is written to 1000BASE-T Control Register (Page 0x10, Offset 0x12).
• Clock in the accessed register page value,: 0 0 0 0 0 0 0 0 (SPIF bit 7=0)
Broadcom®
April 6, 2016 • 53128-DS07-R Page 108
2. Issue a Normal Write command (opcode = 0x61) and write the accessed register page value of 0x10 into
SPI Page register (0xFF)—this step is required only if previous read/write was not from/to Page 0x10.
l
tia
• Clock in 1 byte of the accessed register page value (Page register 0x10)
en
Figure 31: Normal Write to Setup the Register Page Value
fid
on
C
om
3. Issue a Normal Write command (opcode = 0x61) and write the Address of the accessed register followed by
dc
the write content starting from a lower byte.

oa

• Clock in Offset of Address of accessed register (0x12)
Br
• Clock in lower data byte first: 0 0 0 0 0 0 0 0 (Byte 0: Bit 7 to Bit 0)

• Clock in upper data byte next: 0 0 0 1 0 1 1 0 (Byte 1: Bit 15 to Bit 8)
Figure 32: Normal Write to Write the Register Address Followed by Written Data
Broadcom®
April 6, 2016 • 53128-DS07-R Page 109
EEPROM Interface
The BCM53128 can be connected using the serial interface to a low-cost external serial EEPROM, enabling it
to download register-programming instructions during power-on initialization. For each programming instruction
fetched from the EEPROM, the instruction executes immediately and affects the register file.
During the chip-initialization phase, the data is sequentially read-in from the EEPROM after the internal memory
has been cleared. The first data read-in is the HEADER and it matches a predefined magic code. In the case
where the HEADER data does not match the instruction fetch, the process stops, and the EEPROM controller
treats it as if no EEPROM exists. If the magic code matches, the fetch instruction process continues until it
reaches the instruction length defined in the HEADER.
Due to the different access cycles of different capacity EEPROMs, the strap pins EEPROM_TYPE[1:0] are used
to support the various EEPROM devices according to Table 26.
Table 26: EEPROM_TYPE[1:0] Settings
l
tia
EEPROM_TYPE[1:0] EEPROM
00 93C46
en
01 93C56
10 93C66
11 93C86
fid
on
Figure 33: Serial EEPROM Connection
C
BCM53128 93C46/56/66/86
SS
om
CS
SCK SK
MOSI DI
dc
MISO DO
oa
Br
EEPROM Format
The EEPROM should be configured to x16 word format. The header contains key and length information as
shown in Table 27. The actual data stored in the EEPROM is byte-swapped as shown in Table 28.
• Upper 5 bits are magic code 15h, which indicates that valid data follows.
• Bit 10 is for speed indication. A 0 means normal speed. A 1 indicates speedup. The default is 0.
• Lower 10 bits indicate the total length of all entries. For example:
– 93C46 up to 64 words
Broadcom®
April 6, 2016 • 53128-DS07-R Page 110
Table 27: EEPROM Header Format
Bits [15:11} Bit 10 Bits [9:0]

Magic code, 15h Speed Total entry number
93C46: 0 ~ 63
93C56: 0 ~ 127
93C66: 0 ~ 255
93C86: 0 ~ 1023
Table 28: EEPROM Contents
Bits [7:0] Bits [15:11] Bit 10 Bits [9:8]

Total entry number Magic code, 15h Speed Total entry number
l
tia
Figure 34 shows an EEPROM programming example.
en
Figure 34: EEPROM Programming Example
00
15 7
101010101
101010001
6
0
5
000000
000010
0
A890 fid
Page:10'h
Write
Offset :30'h Data:013C’h
on
01 Page:11'h Offset :30'h Data:013C’h
FF
FF 01 FF01
02
C
00 10
02 0010 MCMC
: 101010101
: S : 0 (Normal) TOTAL
TOTAL ENTRY
ENTRY NUM
NUM : 08 'h
03 30
06 01 3001
om
Address FF’h (Page) Data Entry Num . # 01

04 01
43 21
3C 013C
Page # 00'h Page # 10'h
05
dc
FF 01 FF01
Offset 30’h Data Entry Num . # 01
06 00
22 11 0011
oa
Data 01'h Data 3C'h

07 30 01 3001
Address FF’h (Page) Data Entry Num . # 01
Br
08 01
66 3C 013C
Page # 00'h Page # 11'h
. . .
. . . Offset 30’h Data Entry Num . # 01
Data 01'h Data 3C'h

3F
EEPROM Serial Stream: 90 A8 01 FF 10 00 01 30 3C 01 01 FF 11 00 01 30 3C 01
Broadcom®
April 6, 2016 • 53128-DS07-R Page 111
BCM53128 Data Sheet MDC/MDIO Interface
MDC/MDIO Interface
BCM53128 offers an MDC/MDIO interface for accessing the switch registers as well as the PHY registers. An
external management entity can access the switch registers through this interface when the SPI interface is not
used. (i.e., when the SPI clock is in idle mode.) The switch registers are accessed through the Pseudo PHY
interface, and the PHY registers are accessed directly by using PHY addresses.
External PHY can be connected to GMII interface of IMP port. Through the SPI interface, by accessing the Page
88h, the external PHY MII registers can be accessed. The actual PHY address can be assigned through the
MDIO IMP Port Address register.
Note: The PHY registers are not accessible through the Pseudo PHY operation.
l
tia
MDC/MDIO Interface Register Programming
The BCM53128 are designed to be fully compliant with the MII clause of the IEEE 802.3u Ethernet specification.
en
The MDC pin of the BCM53128 sources a 2.5-MHz clock. Serial bidirectional data transmitted using the MDIO
pin is synchronized with the MDC clock. Each MII read or write instruction is initiated by the BCM53128 and
contains the following:
• fid
Preamble (PRE). To signal the beginning of an MII instruction after reset, at least 32 consecutive 1-bits
on
must be written to the MDIO pin. A preamble of 32 1-bits is required only for the first read or write following
reset. A preamble of fewer than 32 1-bits causes the remainder of the instruction to be ignored.
C
• Start of Frame (ST). A 01 pattern indicates that the start of the instruction follows.
• Operation Code (OP). A read instruction is indicated by 10, while a write instruction is indicated by 01.
om
• PHY Address (PHYAD). A 5-bit PHY address follows, with the MSB transmitted first. The PHY address
allows a single MDIO bus to access multiple PHY chips.
dc
• Register Address (REGAD). A 5-bit register address follows, with the MSB transmitted first.
• Turnaround (TA). The next bit times are used to avoid contention on the MDIO pin when a read operation
oa
is performed. When a write operation is being performed, 10 must be sent by the BCM53128 chip during
these two bit times. When a read operation is being performed, the MDIO pin of the BCM53128 must be
put in a high-impedance state during these bit times. The external PHY drives the MDIO pin to 0 during the
Br
second bit time.

• Data. The last 16 bits of the Instruction are the actual data bits. During a write operation, these bits are
written to the MDIO pin with the most significant bit (MSB) transmitted first by the BCM53128. During a
read operation, the data bits are driven by the external PHY with the MSB transmitted first.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 112
PseudoPHY
The MDC/MDIO can be used by an external management entity to read/write register values internal to the
BCM53128. This mode offers an alternative programming interface to the chip. The BCM53128 operate in slave
mode with a PHY address of 30d. The following figures show the register setup flow chart for accessing the
registers using the MDC/MDIO interface.
Figure 35: PseudoPHY MII Register Definitions
Reg 0
IEEE Reserved
l
tia
Reg 15
en
Page Number Reserved A Reg 16
Register Address
fid
Reserved OP Reg 17
on
Access Status Reg 18
C
Reserved
om
Access register bits [15:0] Reg 24

dc

oa

Br
Reserved
Reg 31
Broadcom®
April 6, 2016 • 53128-DS07-R Page 113
Figure 36: PseudoPHY MII Register 16: Register Set Access Control Bit Definition
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Bit #
Page Number Reserved A Reg 16
Bits [15:8] => Page number (RW)

Bits [71] => Reserved
Bit 0 => Register set MDC/MDIO access enable (RW)
l
tia
Note: The bit 0 (MDC/MDIO Access Enable) in register 16 should be released (set to 0) after a
transaction is completed. This allows the SPI interface to access the switch register if required.
en
Figure 37: PseudoPHY MII Register 17: Register Set Read/Write Control Bit Definition
15 14 13 12 11 10 9 8 7 6 5 fid 4 3 2 1 0 Bit #
on
C
Register Address Reserved OP Reg 17

om
Bits [15:8] => Register address (RW)

dc
Bits [7:2] => Reserved

Bits [1:0] => OP code (RW/SC),00 = No operation
01 = Write operation
oa
10 = Read operation
11 = Reserved
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 114
Figure 38: PseudoPHY MII Register 18: Register Access Status Bit Definition
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Bit #
Reserved E P Reg 18
Bits [15:1] => Reserved

Bit 1 => Operation Error (RO/LH), when op_code = 2'b11, this bit is set to show operation error.
Bit 0 => Prohibit Access (RO/LH), for Page Number = 8'h1X, which are PHY MII registers.
Figure 39: PseudoPHY MII Register 24: Access Register Bit Definition
l
tia
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Bit #
en
fid
on
Bits [15:0] => Access register bits [15:0] (RW)
C
om
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Bit #
dc
oa

Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 115
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Bit #
l
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Bit #
tia
en
fid
on
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 116
Figure 43: Read Access to the Register Set Using the PseudoPHY (PHYAD = 11110) MDC/MDIO Path
Write MII register 16:

Set bit 0 as 1
Set Page Number to bits [15:8]

Set Operation Code as 10
Set register address to bits [15:8]
Read MII register 17: No

Check op_code = 00?
l
tia
en
Yes
fid
Read MII register 24:
for Access register bits [15:0]
on
C

om
dc

oa
Br

No New Page Access?
Yes
Broadcom®
April 6, 2016 • 53128-DS07-R Page 117
Figure 44: Write Access to the Register Set Using the PseudoPHY (PHYAD = 11110) MDC/MDIO Path

Set bit 0 as 1
Set Page Number to bits [15:8]


l
tia
en
fid
on
C

Set Operation Code as 01
Set register address to bits [15:8]
om
dc
oa
Read MII register 17: No

Check op_code = 00?
Br
Yes
No New Page Access?
Yes
Broadcom®
April 6, 2016 • 53128-DS07-R Page 118
BCM53128 Data Sheet LED Interfaces
Table 29 summarizes the complete management frame format.
Table 29: MII Management Frame Format
Operation PRE ST OP PHYAD REGAD TA Data Direction

Read 1 ... 1 01 10 AAAAA RRRRR ZZ Z ... Z Driven by master
Z0 D ... D Driven by slave
Write 1 ... 1 01 01 AAAAA RRRRR 10 D ... D Driven to master
See “MDC/MDIO Interface” on page 112 for more information regarding the timing requirements.
LED Interfaces
l
The BCM53128 provides flexible visibility per-port status of various functions. The LED Interface offers an option
tia
to display different functions for each port given the number of LED bits available. The BCM53128 provides a
total of 32 LED pins. In a 5-port switch application, these are dedicated as four LED pins per port as shown in
en
Table 30 on page 120. If one or more ports are not used in an application and are disabled using LED Enable
Map register (Page 00h: Address 16h), and no more than four LED pins are to be used per port, the locations
fid
of the pins for the enabled ports are the same as if all eight ports were used, with four pins reserved per port,
regardless of whether the port is enabled.
on
For example, if Port7~2 LED displays are disabled (value of register page 00h, address 16h = 0003), Port0 and
Port1 LED display are still from LED pins LEDP28~31 (Port0), LEDP24~27 (Port1), just as if all eight ports were
C
used. If Port1 and Port0 LED displays are disabled (value of register page 00h, address 16h = 00FC), Port5,
Port6, and Port7 are still from LED pins LEDP8~11 (Port5), LEDP4~7 (Port6), and LEDP0~3 (Port7), also just
om
as if all eight ports were used.
To set up the LED interface, configure strap pins LED_MODE[1:0] or select the desired display the functions in
dc
the LED Function 0 Control register/LED Function 1 Control register. The per-port LED display is fixed with four
functions.
oa
• To configure the strap pins, set the predefined functions to be displayed by setting the strap pins
LED_MODE[1:0]. The predefined functions are described in “Signal Descriptions” on page 125. Per-port
LED display is fixed four functions and occupy four LED pins.
Br
• To configure LED display function in the two LED Function Control registers, assign each port to one of the
LED Function 0 Control register and LED Function 1 Control register by enabling the bits in the LED
Function Map register. The LED interface shifts out the status of the selected functions for ports enabled in
the LED Enable Map register.
Only four or less than four functions can be selected, and the per-port LED display occupies four LED pins (fixed
four functions). For example, if LED display function using LED Function 1 Control register is configured and the
value is set to 0324h (four LED functions) or 0320h (three LED functions), the per-port LED display has four
fixed functions and occupies four LED pins per port, Port7 (LEDP0~3), Port6 (LEDP4~7), ....Port0
(LEDP28~31).
The status of enabled ports is sent out from a higher port number to the lowest port number. The output order
that is in the shift out is from LEDP[0], LEDP[1], LEDP[2],…..LEDP[31]. The output port order for LED is from
high port number to low port number, and the output bit order within the port LED is form MSB to LSB.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 119
The LED MODE MAP 0 and 1 registers can be set to select:

• LED to blinking,
• LED on, or
• LED auto mode.
Bit 7, LED_EN, of the LED Refresh register is default enabled. When this bit 7 is enabled, the LED display of
each port status is normal and truly reflects each port link up/link down status. If bit 7 is disabled, the LED status
is latched in its current state.
LED signals are active low, and for the dual function LEDs, LNK, DPX, and Speed state are active low. The ACT
(activity) indicator is indicated by blinking.
Table 30: LED Output Pins Per Port
Port LED Output Pins

Port 7 LEDP [0:3]
l
tia
Port 6 LEDP [4:7]
Port 5 LEDP [8:11]
en
Port 4 LEDP [12:15]
Port 3 LEDP [16: 19]
Port 2
Port 1 fid
LEDP [20:23]
LEDP [24:27]
on
Port 0 LEDP [28: 31]
C
Figure 45 shows the LED Interface register structure.

om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 120
Figure 45: LED Interface Register Structure Diagram
LED Function Control Register 0 LED Function Control Register 1
Available Functions Selected Functions Available Functions Selected Functions
15 : Reserved 15 : Reserved
14 : BroadSync HD Link 14 : BroadSync HD Link
13 : 1G/ACT 13 : 1G/ACT
12 : 10 /100 M/ACT 12 : 10/100 M/ACT
11 : 100M/ACT 11 : 100M/ACT
10 : 10M/ACT 1G/ACT 10 : 10M/ACT
9 : SPD1G LNKL/ACTG 9 : SPD1G
8 : SPDI00M DPX/COL 8 : SPDI00M
7 : SPD10M LNK 7 : SPD10M LNKG/ACTL
6 : DPX/COL 6 : DPX/COL SPD100M
5 : LNK/ACT 5 : LNK/ACT
4 : COL 4 : COL
l
tia
3 : ACT 3 : ACT
2 : DPX 2 : DPX
1 : LNK 1 : LNK
en
0 : Reserved 0 : Reserved
fid
on
Reserved 0 0 1 0 1 1 0 0 LED Function Map Register
C
Reserved 1 1 1 1 1 1 0 0 LED Enable Map Register

om
1 1 1 0 1 0 1 1 Port Mode Map 0 Register 0 1 0 1

dc
Reserved
1 0 0 1 1 1 0 0 Port Mode Map 1 Register 0 0 1 1
LED AUTO
oa
7 6 5 4 3 2 1 0 Port / Bit # LED BLINK

LED ON
LED OFF
Br
The BCM53128 offers two LED Interfaces, Parallel LED Interface and Serial Interface. As shown in Figure 46
on page 122, the source of LED status stream is the same for both interfaces; the status bit stream is based on
the programmed register settings. The Parallel LED Interface provides all the shifting and storing of the status
internally, so that it does not require any external shift registers, but it requires more I/O pins to be connected
on the part.
The Serial LED Interface is being output through two pins (LEDDATA, LEDCLK). It saves the number of I/O pins,
but it requires the user to design in the external shift registers.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 121
Figure 46: LED Interface Block Diagram
LED I/O Block

LED Control Block
LEDCLK
LEDDATA
LED[0] Q D
LED[1] Q D
l
tia
LED[3] Q D
en
fid
on
LED[31] Q D
C
om
dc
Dual LED is used for displaying more than one status using one LED cell. By packing two different colors LED
oa
into one holder, dual LED can display more than two states in one cell. Figure 47 shows a typical dual LED
usage. Green LED is to display LNKG/ACT status, while Yellow LED is to display LNKF/ACT status.
Br
Figure 47: Dual LED Usage Example
LNKF/ACT Green LED LNKG/ACT
Yellow LED
Broadcom®
April 6, 2016 • 53128-DS07-R Page 122
Dual Input Configuration/LED Output Function

There are LED pins that have secondary functions. These pins serve as input pins during the power-on/reset
sequence. The logic level of the pin is sampled at reset and configures the secondary function. After the reset
process is completed, the pin acts as an output LED during normal operation. The polarity of the output LED is
determined based on the latched input value at reset. For example, if the value at the pin is high during reset,
the LED output during normal operation is active-low. The user must first decide, based on the individual
application, the values of the input configuration pin shown in the following table to provide the correct device
configuration. The LED circuit must then be configured to accommodate either an active-low or active-high LED
output (see Figure 48).
Figure 48: LED Circuit for Dual Input Configuration/LED Output Pins
l
tia
en
fid
on
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 123
BCM53128 Data Sheet Hardware Signal Definition Table
Section 5: Hardware Signal Definition

Table
I/O Signal Types

The following conventions are used to identify the I/O types shown in Table 31. The I/O pin type is useful in
referencing the DC-pin characteristics.
Table 31: I/O Signal Type Definitions
Abbreviation Description
XYZ Active low signal
l
tia
A Analog pin type
B Bias pin type
en
CS Continuously sampled
D Digital pin type
DNC
GND fid
Do not connect
Ground
on
I Input
I/O Bidirectional
C
IPU Input with internal pull-up

O3S Tristated Signal
om
ODO Open-drain output

O Output
dc
OPU Output with internal pull-up

OPD Output with internal pull-down
oa
PD Internal pull-down
SOR Sample on reset
Br
PWR Power pin supply

PU Internal pull-up
XT Crystal pin type
Broadcom®
April 6, 2016 • 53128-DS07-R Page 124
BCM53128 Data Sheet Signal Descriptions
Signal Descriptions
Table 32: Signal Type Definitions
Signal Name Type Description

Serial Interface
TRD0_0+/- IA/OA Transmit/Receive Pairs. In TRD [pair number]_[port number]±
TRD1_0+/- 1000BASE-T mode, differential data from the media is transmitted and
received on all four signal pairs. In auto-negotiation and 10BASE-T and
TRD2_0+/- 100BASE-TX modes, the BCM53128 normally transmits on
TRD3_0+/- TRD[0]_[port number]± and receives on TRD[1]_{port number}±.
TRD0_1+/- Auto-MDIX operation can reverse the pairs TRD[0]_{7:0}± and
TRD1_1+/- TRD[1]_{7:0}±
TRD2_1+/-
l
TRD3_1+/-
tia
TRD0_2+/-
TRD1_2+/-
en
TRD2_2+/-
TRD3_2+/-
TRD0_3+/-
TRD1_3+/- fid
on
TRD2_3+/-
TRD3_3+/-
C
TRD0_4+/-
TRD1_4+/-
om
TRD2_4+/-
TRD3_4+/-
TRD0_5+/-
dc
TRD1_5+/-
TRD2_5+/-
oa
TRD3_5+/-
TRD0_6+/-
Br
TRD1_6+/-
TRD2_6+/-
TRD3_6+/-
TRD0_7+/-
TRD1_7+/-
TRD2_7+/-
TRD3_7+/-
Clock/Reset
RESET IPU Hardware Reset Input. Active low Schmitt-triggered input. Resets the
BCM53128.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 125
Table 32: Signal Type Definitions (Cont.)

XTALI IXT 25 MHz Crystal Oscillator Input/Output. A continuous 25 MHz
XTALO OXT reference clock must be supplied to the BCM53128 by connecting a 25
MHz crystal between these two pins or by driving XTALI with an external
25 MHz oscillator clock. When using a crystal, connect a loading
capacitor from each pin to GND. When using an oscillator, leave XTALO
unconnected.
IMP Interface
IMP_TXCLK I/O MII/TMII Transmit Clock. This is an input pin in MII mode, or GMII mode
but speed is 100Mbps/10Mbps. It synchronizes the TXD[3:0] and
connects to the PHY Entity TXC. In 100 Mbps mode, this is 25 MHz, and
in 10 Mbps mode, this is 2.5 MHz. In 200 Mbps mode (TMII), this is 50
MHz.
RvMII/RvTMII Receive Clock. This is an output pin in RvMII mode. It
l
synchronizes the TXD[3:0] in RvMII mode and connects to the MAC/
tia
Management Entity RXC. In 100 Mbps mode, this is 25 MHz, and in 10
Mbps mode, this is 2.5 MHz. In 200 Mbps mode (RvTMII), this is 50
MHz. This output pin has an internal 25 -series termination resistor.
en
This clock is not use in the other conditions.
IMP_TXD[3:0] O GMII Transmit Data Output (first nibble). Data bits TXD[3:0] are
fid
clocked on the rising edge of TXCLK.
RGMII Transmit Data Output. For 1000 Mbps operation, data bits
on
TXD[3:0] are clocked on the rising edge of TXCLK, and data bits
TXD[7:4] are clocked on the falling edge of TXCLK. For 10 Mbps and
100 Mbps, data bits TXD[3:0] are clocked on the rising edge of TXCLK.
C
RvMII/RvTMII Receive Data Output. Clocked on the rising edge of

TXCLK and connected to the RXD pins of the external MAC/
om
Management entity.
MII/TMII Transmit Data Output. Clocked on the rising edge of TXCLK
supplied by MAC/Management entity.
dc
These output pins have internal 25 -series termination resistor.

IMP_TXD[7:4] O GMII Transmit Data Output (second nibble). Data bits [7:4] are
oa
clocked on the rising edge of TXCLK. These output pins have internal
25 -series termination resistor.
IMP_TXEN O GMII/MII/TMII Transmit Enable. Active high. TXEN indicates the data
Br
on the TXD pins are encoded and transmitted.

RGMII Transmit Control. On the rising edge of TXCLK, TXEN indicates
that a transmit frame is in progress, and the data present on the
TXD[3:0] output pins is valid. On the falling edge of TXCLK, TXEN is a
derivative of GMII mode TXEN and TXER signals.
RvMII/RvTMII Receive Data Valid. Active high. Connected to RXDV pin
of MAC/Management entity. Indicates that a receive frame is in
progress, and the data present on the TXD[3:0] output pins is valid.
This output pin has an internal 25 -series termination resistor.
IMP_TXER O GMII/MII/TMII Transmit Error. Active high. Asserting TXER when TXEN
is high indicates a transmission error. TXER is also used to indicate
Carrier Extension when operating in half-duplex mode. This output pin
has an internal 25 -series termination resistor.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 126

IMP_RXCLK I GMII Receive Clock. 125 MHz for 1000 Mbps operation.
RGMII Receive Clock. 125 MHz for 1000 Mbps operation, 25 MHz for
100 Mbps operation, and 2.5 MHz for 10 Mbps operation. Data bits
RXD[3:0] are clocked in on the rising edge of the RXCLK, and data bits
RXD[7:4] are clocked in on the falling edge of the RXCLK.
MII Receive Clock. 25 MHz for 100 Mbps operation, and 2.5 MHz for 10
Mbps operation.
TMII Receive Clock. 50 MHz for 200 Mbps operation.
O RvMII/RvTMII Transmit Clock. Synchronizes the RXD[3:0] in RvMII/
RvTMII mode and connects to the MAC/Management entity TXC.
RvMII Transmit Clock. 25 MHz for 100 Mbps mode, and 2.5 MHz for 10
Mbps mode.
RvTMII Transmit Clock. 50 MHz for 200 Mbps operation.
l
tia
This output pin has an internal 25-series termination resistor.
IMP_RXD[3:0] I GMII Receive Data Inputs (first nibble). Data bits RXD[3:0] are
clocked on the rising edge of RXCLK.
en
RGMII Receive Data Inputs. For 1000 Mbps operation, data bits
RXD[3:0] are clocked-out on the rising edge of RXCLK, and data bits
fid
RXD[7:4] are clocked on the falling edge of RXCLK. In 10 Mbps and 100
Mbps modes, data bits
on
RXD[3:0] are clocked on the rising edge of RXCLK.
RvMII/RvTMII Transmit Data Inputs. Clocked on the rising edge of
RXCLK and connected to the TXD pins of the external MAC/
C
Management entity.
MII/TMII Receive Data Input. Data bits RXD[3:0] are clocked on the
om
rising edge of RXCLK.

IMP_RXD[7:4] I GMII Receive Data Inputs (second nibble). Data bits RXD[7:4] are
clocked out on the rising edge of RXCLK.
dc
IMP_RXDV I GMII/MII/TMII Receive Data Valid. Active high. RXDV indicates that a
receive frame is in progress, and the data present on the RXD output
oa
pins is valid.
RGMII Receive Data Valid. Functional equivalent of GMII RXDV on the
rising edge of RXCLK and functional equivalent of a logical derivative of
Br
GMII RXDV and RXER on the falling edge of RXCLK.

RvMII/RvTMII Transmit Enable. Active high. Indicates the data on the
RXD[3:0] pins are encoded and transmitted. Connects to the TXEN of
the external MAC/Management entity.
IMP_RXER I GMII/MII/TMII Receive Error. Indicates an error during the receive
frame.
IMP_CRS I Carrier Sense. Active-high, indicates traffic on link
IMP_COL I Collision Detect. In half-duplex mode, active-high input indicates that a
collision has occurred. In full-duplex mode, COL remains low. COL is an
asynchronous input signal.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 127

IMP_GTX_CLK O GMII Transmit clock. This clock is driven to synchronize the transmit
data in 1000 Mbps speed in GMII mode.
RGMII Transmit Clock. This clock is driven to synchronize the transmit
data in RGMII mode(125 MHz for 1000 Mbps operation, 25 MHz for 100
Mbps operation, and 2.5 MHz for 10 Mbps operation). In RGMII mode,
both edges of the clock are used to align with TXD[3:0].
IMP_GTX_CLK is used in RGMII and 1000 Mbps speed in GMII mode.
IMP_TXCLK is used for MII mode, and 10/100 Mbps speed in GMII
mode. This output pin has an internal 25 -series termination resistor.
MDC/MDIO Interface
MDIO I/OPD Management Data I/O. In master mode, this serial input/output data
signal is used to read from and write to the MII registers of the external
transceivers. In slave mode, it is used by an external entity to read/write
l
tia
to the switch registers via the Pseudo-PHY. See the MDC/MDIO
interface for more information.
MDC I/OPD Management Data Clock. In master mode, this 2.5 MHz clock sourced
en
by BCM53128 to the external PHY device. In slave mode, it is sourced
by an external entity.
fid
on
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 128

Test Interface
TCK IPU JTAG Test Clock Input. Clock Input used to synchronize JTAG control
and data transfers. If unused, may be left unconnected.
TDI IPU JTAG Test Data Input. Serial data input to the JTAG TAP Controller.
Sampled on the rising edge of TCK. If unused, may be left unconnected.
Shared with MOSI.
TDO O JTAG Test Data Output.
TMS IPU JTAG Mode Select Input.
TRST IPU JTAG Test Reset. Active low. Resets the JTAG controller. This signal
must be pulled low during normal operation.
Configuration/GPIO Pins
l
CLK_FREQ1/GPIO1 IPD, SOR CLK_FREQ1 or GPIO bit 1
tia
CLK_FREQ0/GPIO0 IPU, SOR CLK_FREQ0 or GPIO bit 0
System Clock Selection. Determines rate of system clock via
en
CLK_FREQ[1:0] value.
00 = 83 MHz
fid
01 = 91 MHZ (normal operation)
10 = 100 MHz
on
11 = 111 MHz
CPU_EEPROM_SEL IPU, SOR CPU or EEPROM Interface Selection.
CPU_EEPROM_SEL = 0: Enable EEPROM interface.
C
CPU_EEPROM_SEL = 1: Enable SPI Interface, The SPI interface has

to be enabled (CPU_EEPROM_SEL = 1) for Pseudo-PHY accesses
om
through the MDC/MDIO Interface.

See ““Programming Interfaces” on page 95 for more information.
HW_FWDG_EN/ IPD, SOR HW_FWDG_EN or GPIO bit7
dc
GPIO7 HW_FWDG_EN. Forwarding Enable. Active high. If this pin is pulled low
at power-up, frame forwarding is disabled.
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 129

LED MODE[1]/GPIO4 Bit 0: IPD, The following are LED Mode descriptions.
LED MODE[0]/GPIO3 Bit 1: IPU, LED Mode[1] or GPIO bit4, LED_MODE[0] or GPIO bit3
SOR LED Mode. Users can select predefined functions to be displayed for
each port by setting the bits accordingly.
When LED MODE[1:0] = 00
FE configuration
SPD100M
LNK/ACT
PHYLED4
GbE configuration
SPD1G
SPD100M
l
tia
LNK/ACT
PHYLED4
en
FE configuration
100M/ACT
10M/ACT
DPX/COL
fid
on
PHYLED4
GbE configuration
C
1G/ACT
10/100M/ACT
om
DPX/COL
PHYLED4
dc

FE configuration
SPD100M
oa
LNK/ACT
DPX
Br
GbE configuration
SPD1G
SPD100M
LNK/ACT
DPX
Broadcom®
April 6, 2016 • 53128-DS07-R Page 130

LED MODE[1]/GPIO4 When LED MODE[1:0] = 11
LED MODE[0]/GPIO3 FE configuration
(continued from 100M/ACT
previous page) 10M/ACT
DPX
GbE configuration
1G/ACT
100M/ACT
10M/ACT
DPX
IMP_SPD_SEL[1:0] Bit 0: IPD, IMP Port Speed Select.
Bit 1: IPU 00 = 10 Mbps
l
tia
01 = 100 Mbps
10 = 1000 Mbps (default)
en
11 = 200 Mbps
IMP_MODE[1]/GPIO6 Bit 0: IPU, IMP Mode[1] or GPIO bit6, IMP_MODE[0] or GPIO bit5
IMP_MODE[0]/GPIO5 Bit 1: IPU
SOR fid
IMP Port Mode. Sets the mode of the IMP port based on the value of
the pins IMP_MODE[1:0] at power-on reset.
on
00 = RGMII mode
01 = MII/TMII mode
10 = RvMII/RvTMII mode
C
11 = GMII mode
IMP_DUPLEX IPU IMP Port Duplex Mode.
om
0 = IMP in half-duplex mode

1 = IMP in full-duplex mode
dc
IMP_LINK IPD IMP Port Link.

0 = IMP link-down
oa
1 = IMP link-up
IMP_PAUSE_CAP_RX IPU Enable IMP Port Pause Capable in RX.
Br
0 = Disable Pause capable

1 = Enable Pause capable
IMP_PAUSE_CAP_TX IPU Enable IMP Port Pause Capable in TX.
0 = Disable Pause capable
1 = Enable Pause capable
IMP_VOL_SEL[1:0] IPD IMP Interface Voltage Control. RGMII needs to be set to 01 for 2.5V or
1x for 1.5V. GMII/MII/TMII/RvMII/RvTMII needs to be set to 00 for 3.3V.
00: 3.3V
01: 2.5V
10 or 11: 1.5V
Broadcom®
April 6, 2016 • 53128-DS07-R Page 131

EN_CLK25_OUT/ O, IPD, SOR Enable CLK25 Out and CLK_25 Output. En_CLK25_Out is a strap pin
CLK25_OUT function.
0 = Disable clock out
1 = Enable clock out
EN_CLK50_OUT/ O, IPD, SOR Enable CLK50 Out and CLK_50 Output. En_CLK50_Out is a strap pin
CLK50_OUT function.
0 = Disable clock out
1 = Enable clock out
ACT_LOOP_DET IPD Loop Detection Feature Activation.
0 = Disable
1 = Enable
LOOP_DETECTED OPD Loop Found. This signal is to indicate there is a loop detected in the
l
local network connection.
tia
0 = Not detected
1 = Loop detected
en
EN_EEE IPU EN_EEE (Energy Efficient Ethernet). Enables EN_EEE feature for
switch MAC.
0 = Disable
1 = Enable fid
on
EN_8051_TxRx IPD EN_8051_TxRx. Enables 8051 transmitting and receiving packets
capability.
C
0 = Disable
1 = Enable
om
GPIO2 I/O GPIO bit 2

dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 132

LED Interface
LEDP0 O Port 7 Parallel LED Indicators. Active low.
LEDP2 O Port 7 Parallel LED Indicators. Active high.
LEDP3/En_Green O, IPD, SOR This is a dual function pin:
Port 7 Parallel LED Indicators. Polarity determined at reset. See “Dual
Input Configuration/LED Output Function” on page 123.
Green Mode Enable. Sampled on reset.
1= Enable Green mode
0= Disable Green mode
LEDP4 O Port 6 parallel LED Indicators. Active low.
l
tia
LEDP7 O Port 6 parallel LED Indicators. Active high.
en
LEDP10/
EEPROM_TYPE0
fid
O, IPD, SOR This is a dual function pin.
on
Extended EEPROM Interface Selection. Sampled on reset.
C
EEPROM_TYPE[1:0] = 00: Supports 93C46 EEPROM

om

LEDP11/ O, IPD, SOR This is a dual function pin.
dc
EEPROM_TYPE1 Port 5 Parallel LED Indicators. Polarity determined at reset. See “Dual
oa
Extended EEPROM Interface Selection. Sampled on reset.

EEPROM_TYPE [1:0] = 00: Supports 93C46 EEPROM
Br

LOOP_DET_EN Port 4 Parallel LED Indicators. Polarity determined at reset. See “Dual
Enable Loop Detection Mode. Sampled on reset.
0 = Disable
1 = Enable
Broadcom®
April 6, 2016 • 53128-DS07-R Page 133

LOOP_IMP_SEL Port 4 Parallel LED Indicators. Polarity determined at reset. See “Dual
Exclude IMP Port in Loop Detection Function. Sampled on reset.
0 = Exclude IMP port from loop detection function
1 = Include IMP port in loop detection function
BC_SUPP_EN Port 3 Parallel LED Indicators. Polarity determined at reset. “Dual
Broadcast Suppression Enable. Sampled on reset. See “Rate
l
Control” on page 45 for more information.
tia
0=Disable rate-based broadcast suppression.
1=Enable rate-based broadcast suppression.
en
LEDP19 O Port 3 Parallel LED Indicators. Active high.
LEDP21
LEDP22/ DIS_IMP
O
fid
Port 2 Parallel LED Indicators. Active low.
O, IPD, SOR This is a dual function pin.
on
C
Disables IMP Port. Sampled on reset.

0 = Enable IMP port
om
1 = Disable IMP port, and external pull-up resister is required.

IMP_DUMB_FWDG_E Port 2 Parallel LED Indicators. Polarity determined at reset. See “Dual
dc
N Input Configuration/LED Output Function” on page 123.

IMP Port in Blocking State for Unmanaged Mode. Sampled on reset.
oa
When this pin is pulled up, the IMP port is not in management mode, the
IMP port is in a regular port.
Br
0 = Blocking for dumb mode

1 = Forwarding for dumb mode
LEDP26/ ENFDXFLOW O, IPU, SOR This is a dual function pin.
Port 1 Parallel LED Indicators.
Polarity determined at reset. See “Dual Input Configuration/LED Output
Function” on page 123.
Enable Automatic Full-Duplex Flow Control. Sampled on reset.
In combination with the results of auto-negotiation, sets the flow control
mode. See “Flow Control” on page 69 for more information.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 134

LEDP27/ O, IPU, SOR This is a dual function pin.
ENHDXFLOW Port 1 Parallel LED Indicators.
Polarity determined at reset. See “Dual Input Configuration/LED Output
Function” on page 123.
Enable Automatic Backpressure. Sampled on reset.
When this pin is pulled high, it enables half-duplex backpressure flow
control when a port is configured to half-duplex. See “Flow Control” on
page 69.
IMP_TXC_DELAY Port 0 Parallel LED Indicators. Polarity determined at reset. See “Dual
l
tia
TXCLK Clock Timing Delay. Sampled on reset. Active high. This pin
enables the TXCLK to data timing delay in RGMII mode. See “RGMII
en
Interface Timing” on page 304.
IMP_RXC_DELAY
fid
RXCLK Clock Timing Delay. Sampled on reset. Active high. This pin
on
enables the RXCLK to data-sampling timing delay. See “RGMII Interface
Timing” on page 304.
C
LEDCLK OPD LED Shift Clock. This clock is periodically active to enable LEDDATA to
shift into external registers.
om
LEDDATA OPD Serial LED Data Output. Serial LED data for all ports is shifted out when
LEDCLK is active. LEDMODE[1:0] pins set the serial data content. See
“LED Interface” on page 133 for a functional description of this signal.
dc
Programming Interfaces
SCK IPD SPI Serial Clock. The clock input to the BCM53128 SPI interface is
oa
supplied by the SPI master, which supports up to 2 MHz, and is enabled

if CPU_EPROM_SEL is high during power-on reset.
OPD EEPROM Serial Clock. The clock output to an external EEPROM
Br
device, and is enabled if CPU_EPROM_SEL is low during power-on

reset. See the programming interfaces for more information.
SS/CS IPU SPI Slave Select. Active low signal which enables an SPI interface read
or write operation. Enable if CPU_EPROM_SEL is high during power-on
reset.
OPU EEPROM Chip Select. Active high control signal that enables a read
operation from an external EEPROM device. Enable if
CPU_EPROM_SEL is low during power-on reset. See the programming
interfaces for more information.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 135

MOSI/DI IPU SPI Master-Out/Slave-in. Input signal which receives control and
address information for the SPI interface, as well as serial data during
write operations. Enabled if CPU_EPROM_SEL is high during power-on
reset.
OPU EEPROM Data In. Serial data input of an external EEPROM device.
Enabled if CPU_EPROM_SEL is low during power-on reset. See the
programming interfaces for more information.
MISO/DO OPU SPI Master-In/Slave-Out. Output signal which transmits serial data
during an SPI interface read operations. Enabled if CPU_EPROM_SEL
is high during power-on reset.
IPU EEPROM Data Out. Serial data output of an external EEPROM device.
Enable if CPU_EPROM_SEL is low during power-on reset. See the
programming interfaces for more information.
l
Serial Flash Interfaces
tia
FSO OPD Serial Data Output.
en
FCSB OPD Chip Select.
FCLK O Clock Output.
FSI
Interrupt Pin
IPD Serial Data Input.
fid
on
INT O3S Interrupt. This interrupt pin generates an interrupt based on the
configuration of the Interrupt Enable Register and the Interrupt Status
Register.
C
Bias
om
GPHY1_RDAC B A 1.24-k resistor to GND is required.

GPHY2_RDAC B A 1.24-k resistor to GND is required.
Power Interfaces
dc
AVDDH PWR 3.3V Analog I/O Power.

oa
AVDDL PWR 1.2V Analog Core Power.

DVDD PWR 1.2V Digital Core Power.
Br
OVDD PWR Power for GMII/RGMII/MII/RvMII/TMII/RvTMII of IMP. Depends on

IMP_VOL_SEL[1:0] configuration.
00 = 3.3V if IMP_VOL_SEL[1:0]
01 = 2.5V if IMP_VOL_SEL[1:0]
10 or 11 = 1.5V if IMP_VOL_SEL[1:0]
OVDD2 PWR 3.3V Digital I/O Power.
GPHY1_BAVDD PWR 3.3V Analog Power.
GPHY2_BAVDD PWR 3.3V Analog Power.
PLL_AVDD PWR 1.2V Analog Power.
GPHY1_PLLDVDD PWR 1.2V Analog Power.
GPHY2_PLLDVDD PWR 1.2V Analog Power.
XTAL_AVDD PWR 3.3V Analog Power.
IMP_VOL_REF PWR IMP Interface Reference Power. Connect this pin to ground.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 136

PLL_AVSS GND Shared Digital Ground.
XTAL_AVSS GND Shared Digital Ground.
EXPOSEPAD GND Ground.
No Connect
NC DNC Do not connect.
l
tia
en
fid
on
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 137
BCM53128 Data Sheet Pin Assignment
Section 6: Pin Assignment
BCM53128KQLE Pin List by Signal Name

Signal Ball Signal Ball Signal Ball Signal Ball
ACT_LOOP_DETEC 59 CPU_EEPROM_SEL 18 IMP_PAUSECAP_T 56 LEDP6 176
T X
DVDD 16 LEDP7 177
AVDDH 74 IMP_RXCLK 144
DVDD 27 LEDP8 178
AVDDH 80 IMP_RXD0 150
DVDD 31 LEDP9 179
DVDD 40 LEDP10/ 181
AVDDH 92 IMP_RXD2 152 EPROM_TYPE0
DVDD 53
AVDDH 103 IMP_RXD3 154 LEDP11/ 182
DVDD 135
EPROM_TYPE1
l
DVDD 148
tia
LEDP12 184
DVDD 162
LEDP13 185
DVDD 169
en
LEDP14/ 186
DVDD 183 LOOP_DETECT_EN
AVDDH 209 IMP_RXDV 149
EN_8051_TxRx 47 LEDP15/ 188
fid
AVDDH 215 IMP_RXER 147 LOOP_IMP_SEL
EN_CLK25_OUT/ 26
AVDDH 221 CLK25_OUT IMP_SPEED0 51 LEDP16 189
AVDDH 232 EN_CLK50_OUT/ 21 IMP_SPEED1 50 LEDP17 190
on
CLK50_OUT
AVDDH 238 IMP_TXCLK 141 LEDP18/ 191
EN_EEE 38 BC_SUPP_EN
AVDDH 244 IMP_TXD0 137
C
EXPOSEPAD H LEDP19 192

AVDDH 250 IMP_TXD1 136
FCSB 65 LEDP20 194
AVDDL 71 IMP_TXD2 134
om
FSCLK 66 LEDP21 195

FSI 67 LEDP22/DIS_IMP 196
FSO 64 LEDP23/ 197
IMP_DUMB_FWDG_
dc
GPHY1_BVDD 227
AVDDL 95 IMP_TXD6 127 EN
GPHY1_PLLVDD 226
AVDDL 100 IMP_TXD7 126 LEDP24 198
GPHY1_RDAC 228
oa
AVDDL 106 IMP_TXEN 139 LEDP25 199

GPHY2_BVDD 97
AVDDL 112 IMP_TXER 140 LEDP26/ 254
GPHY2_PLLVDD 98 ENFDXFLOW
IMP_VOL_REF 146
Br
AVDDL 118
GPHY2_RDAC 96 LEDP27/ 255
AVDDL 124 IMP_VOL_SEL0 49
GPIO2 10 ENHDXFLOW
AVDDL 200 IMP_VOL_SEL1 48
HW_FWDG_EN/ 9 LEDP28 256
AVDDL 206 INTR_B 60
GPIO7 LEDP29 1
AVDDL 212 LEDCLK 167
IMP_COL 159 LEDP30/ 2
AVDDL 218 LEDDATA 166 IMP_TXC_DELAY
IMP_CRS 143
AVDDL 224 LEDMODE0/GPIO3 12 LEDP31/ 4
IMP_DUPLEX 52
AVDDL 229 LEDMODE1/GPIO4 13 IMP_RXC_DELAY
IMP_GTXCLK 132
AVDDL 235 LEDP0 168 LOOP_DETECTED 58
IMP_LINK 54
AVDDL 241 LEDP1 170 MDC 62
IMP_MODE0/GPIO5 7
AVDDL 247 LEDP2 171 MDIO 61
IMP_MODE1/GPIO6 8
AVDDL 253 LEDP3/EN_GREEN 172 MISO 161
IMP_PAUSECAP_R 55
CLK_FREQ0/GPIO0 14 X LEDP4 174 MOSI 164
CLK_FREQ1/GPIO1 15 LEDP5 175 NC 5
Broadcom®
April 6, 2016 • 53128-DS07-R Page 138
BCM53128 Data Sheet BCM53128KQLE Pin List by Signal Name
Signal Ball Signal Ball Signal Ball

NC 6 TRD[0]+{5} 94 TRD[3]+{4} 82
NC 20 TRD[0]+{6} 101 TRD[3]+{5} 84
NC 28 TRD[0]+{7} 123 TRD[3]+{6} 111
NC 37 TRD[0]-{0} 202 TRD[3]+{7} 113
NC 39 TRD[0]-{1} 222 TRD[3]-{0} 210
NC 41 TRD[0]-{2} 231 TRD[3]-{1} 214
NC 42 TRD[0]-{3} 251 TRD[3]-{2} 239
NC 45 TRD[0]-{4} 73 TRD[3]-{3} 243
NC 46 TRD[0]-{5} 93 TRD[3]-{4} 81
NC 69 TRD[0]-{6} 102 TRD[3]-{5} 85
NC 70 TRD[0]-{7} 122 TRD[3]-{6} 110
NC 99 TRD[1]+{0} 205 TRD[3]-{7} 114
NC 225 TRD[1]+{1} 219 TRST 36
OVDD 125 TRD[1]+{2} 234 XTALI 34
l
tia
OVDD 129 TRD[1]+{3} 248 XTALO 33
OVDD 133 TRD[1]+{4} 76 XTAL_AVDD 35
en
OVDD 138 TRD[1]+{5} 90 XTAL_AVSS 32
OVDD 142 TRD[1]+{6} 105
OVDD 145 TRD[1]+{7} 119
OVDD
OVDD2
153
3
TRD[1]-{0}
TRD[1]-{1}
204
220 fid
on
OVDD2 11 TRD[1]-{2} 233
OVDD2 19 TRD[1]-{3} 249
C
OVDD2 43 TRD[1]-{4} 75
OVDD2 44 TRD[1]-{5} 91
om
OVDD2 57 TRD[1]-{6} 104

OVDD2 63 TRD[1]-{7} 120
OVDD2 68 TRD[2]+{0} 207
dc
OVDD2 165 TRD[2]+{1} 217

OVDD2 173 TRD[2]+{2} 236
OVDD2 180 TRD[2]+{3} 246
oa
OVDD2 187 TRD[2]+{4} 78

OVDD2 193 TRD[2]+{5} 88
Br
PLL_AVDD 29 TRD[2]+{6} 107

PLL_AVSS 30 TRD[2]+{7} 117
RESET 17 TRD[2]-{0} 208
SCK 163 TRD[2]-{1} 216
SS 160 TRD[2]-{2} 237
TCK 24 TRD[2]-{3} 245
TDI 23 TRD[2]-{4} 79
TDO 22 TRD[2]-{5} 87
TMS 25 TRD[2]-{6} 108
TRD[0]+{0} 201 TRD[2]-{7} 116
TRD[0]+{1} 223 TRD[3]+{0} 211
TRD[0]+{2} 230 TRD[3]+{1} 213
TRD[0]+{3} 252 TRD[3]+{2} 240
TRD[0]+{4} 72 TRD[3]+{3} 242
Broadcom®
April 6, 2016 • 53128-DS07-R Page 139
BCM53128 Data Sheet BCM53128KQLE Pin List by Ball Number
BCM53128KQLE Pin List by Ball Number

Ball Signal Ball Signal Ball Signal Ball Signal
1 LEDP29 41 NC 83 AVDDL 127 IMP_TXD6
2 LEDP30/ 42 NC 84 TRD[3]+{5} 128 IMP_TXD5
IMP_TXC_DELAY 43 OVDD2 85 TRD[3]-{5} 129 OVDD
3 OVDD2 44 OVDD2 86 AVDDH 130 IMP_TXD4
4 LEDP31/ 45 NC 87 TRD[2]-{5} 131 IMP_TXD3
IMP_RXC_DELAY
46 NC 88 TRD[2]+{5} 132 IMP_GTXCLK
5 NC
47 EN_8051_TxRx 89 AVDDL 133 OVDD
6 NC
48 IMP_VOL_SEL1 90 TRD[1]+{5} 134 IMP_TXD2
7 IMP_MODE0/GPIO5
49 IMP_VOL_SEL0 91 TRD[1]-{5} 135 DVDD
8 IMP_MODE1/GPIO6
50 IMP_SPEED1 92 AVDDH 136 IMP_TXD1
9 HW_FWDG_EN/
GPIO7 51 IMP_SPEED0 93 TRD[0]-{5} 137 IMP_TXD0
l
10 GPIO2 52 IMP_DUPLEX 94 TRD[0]+{5} 138 OVDD
tia
11 OVDD2 53 DVDD 95 AVDDL 139 IMP_TXEN
12 LEDMODE0/GPIO3 54 IMP_LINK 96 GPHY2_RDAC 140 IMP_TXER
en
13 LEDMODE1/GPIO4 55 IMP_PAUSECAP_R 97 GPHY2_BVDD 141 IMP_TXCLK
X
14 CLK_FREQ0/GPIO0 98 GPHY2_PLLVDD 142 OVDD
56 IMP_PAUSECAP_T
fid
15 CLK_FREQ1/GPIO1 99 NC 143 IMP_CRS
X
16 DVDD 100 AVDDL 144 IMP_RXCLK
57 OVDD2
101 TRD[0]+{6} 145 OVDD
on
17 RESET 58 LOOP_DETECTED
18 CPU_EEPROM_SEL 102 TRD[0]-{6} 146 IMP_VOL_REF
59 ACT_LOOP_DETEC
19 OVDD2 T 103 AVDDH 147 IMP_RXER
C
20 NC 60 INTR_B 104 TRD[1]-{6} 148 DVDD
21 EN_CLK50_OUT/ 61 MDIO 105 TRD[1]+{6} 149 IMP_RXDV

om
CLK50_OUT 62 MDC 106 AVDDL 150 IMP_RXD0

22 TDO 63 OVDD2 107 TRD[2]+{6} 151 IMP_RXD1
23 TDI 64 FSO 108 TRD[2]-{6} 152 IMP_RXD2
dc
24 TCK 65 FCSB 109 AVDDH 153 OVDD

25 TMS 66 FSCLK 110 TRD[3]-{6} 154 IMP_RXD3
oa
26 EN_CLK25_OUT/ 67 FSI 111 TRD[3]+{6} 155 IMP_RXD4

CLK25_OUT
68 OVDD2 112 AVDDL 156 IMP_RXD5
27 DVDD
113 TRD[3]+{7} 157 IMP_RXD6
Br
69 NC
28 NC
70 NC 114 TRD[3]-{7} 158 IMP_RXD7
29 PLL_AVDD
71 AVDDL 115 AVDDH 159 IMP_COL
30 PLL_AVSS
72 TRD[0]+{4} 116 TRD[2]-{7} 160 SS
31 DVDD
73 TRD[0]-{4} 117 TRD[2]+{7} 161 MISO
32 XTAL_AVSS
74 AVDDH 118 AVDDL 162 DVDD
33 XTALO
75 TRD[1]-{4} 119 TRD[1]+{7} 163 SCK
34 XTALI
76 TRD[1]+{4} 120 TRD[1]-{7} 164 MOSI
35 XTAL_AVDD
77 AVDDL 121 AVDDH 165 OVDD2
36 TRST
78 TRD[2]+{4} 122 TRD[0]-{7} 166 LEDDATA
37 NC
79 TRD[2]-{4} 123 TRD[0]+{7} 167 LEDCLK
38 EN_EEE
80 AVDDH 124 AVDDL 168 LEDP0
39 NC
81 TRD[3]-{4} 125 OVDD 169 DVDD
40 DVDD
82 TRD[3]+{4} 126 IMP_TXD7 170 LEDP1
Broadcom®
April 6, 2016 • 53128-DS07-R Page 140
BCM53128 Data Sheet BCM53128KQLE Pin List by Ball Number
Ball Signal Ball Signal

171 LEDP2 213 TRD[3]+{1}
172 LEDP3/EN_GREEN 214 TRD[3]-{1}
173 OVDD2 215 AVDDH
174 LEDP4 216 TRD[2]-{1}
175 LEDP5 217 TRD[2]+{1}
176 LEDP6 218 AVDDL
177 LEDP7 219 TRD[1]+{1}
178 LEDP8 220 TRD[1]-{1}
179 LEDP9 221 AVDDH
180 OVDD2 222 TRD[0]-{1}
181 LEDP10/ 223 TRD[0]+{1}
EPROM_TYPE0 224 AVDDL
182 LEDP11/ 225 NC
EPROM_TYPE1
226 GPHY1_PLLVDD
l
183 DVDD
tia
227 GPHY1_BVDD
184 LEDP12
228 GPHY1_RDAC
185 LEDP13
en
229 AVDDL
186 LEDP14/
LOOP_DETECT_EN 230 TRD[0]+{2}
187 OVDD2 231 TRD[0]-{2}
188 LEDP15/
LOOP_IMP_SEL
232
233
AVDDH
TRD[1]-{2} fid
on
189 LEDP16 234 TRD[1]+{2}
190 LEDP17 235 AVDDL
191 LEDP18/
C
236 TRD[2]+{2}
BC_SUPP_EN
237 TRD[2]-{2}
192 LEDP19
om
238 AVDDH
193 OVDD2
239 TRD[3]-{2}
194 LEDP20
240 TRD[3]+{2}
195 LEDP21
dc
241 AVDDL
196 LEDP22/DIS_IMP
242 TRD[3]+{3}
197 LEDP23/
243 TRD[3]-{3}
oa
IMP_DUMB_FWDG_
EN 244 AVDDH
198 LEDP24 245 TRD[2]-{3}
Br
199 LEDP25 246 TRD[2]+{3}

200 AVDDL 247 AVDDL
201 TRD[0]+{0} 248 TRD[1]+{3}
202 TRD[0]-{0} 249 TRD[1]-{3}
203 AVDDH 250 AVDDH
204 TRD[1]-{0} 251 TRD[0]-{3}
205 TRD[1]+{0} 252 TRD[0]+{3}
206 AVDDL 253 AVDDL
207 TRD[2]+{0} 254 LEDP26/
208 TRD[2]-{0} ENFDXFLOW
209 AVDDH 255 LEDP27/
ENHDXFLOW
210 TRD[3]-{0}
256 LEDP28
211 TRD[3]+{0}
H EXPOSEPAD
212 AVDDL
Broadcom®
April 6, 2016 • 53128-DS07-R Page 141
BCM53128 Data Sheet Register Definitions
Section 7: Register Definitions
Register Definition
BCM53128 register sets can be accessed through the programming interfaces described on page 95. The
register space is organized into pages, each containing a certain set of registers. Table 33 lists the pages
defined in the BCM53128. To access a page, the page register (0xFF) is written with the page value. The
registers contained in the page can then be accessed by their addresses. See “Programming Interfaces” on
page 95 for more information.
l
Register Notations
tia
In the register description tables, the following notation in the R/W column is used to describe the ability to read
en
or to write:
• R/W = Read or write
•
•
RO = Read only
LH = Latched high fid
on
• LL = Latched low
• H = Fixed high
C
• L = Fixed low
om
• SC = Clear on read
Reserved bits must be written as the default value and ignored when read.
dc
oa
Global Page Register

Br
Table 33: Global Page Register Map
Page Description
00h “Page 00h: Control Registers” on page 144
01h “Page 01h: Status Registers” on page 164
02h “Page 02h: Management/Mirroring Registers” on page 168
03h “Page 03h: Interrupt Control Register” on page 177
04h “Page 03h: Interrupt Control Register” on page 177
05h “Page 05h: ARL/VTBL Access Registers” on page 184
06h, 07h Reserved
08h Reserved
09h Reserved
Broadcom®
April 6, 2016 • 53128-DS07-R Page 142
BCM53128 Data Sheet Global Page Register
Table 33: Global Page Register Map (Cont.)
Page Description
0Ah Reserved
0Bh–0Fh Reserved
10h–17h “Page 10h–17h: Internal GPHY MII Registers” on page 194
18h–1Fh Reserved
20h–28h “Page 20h–28h: Port MIB Registers” on page 230
29h–2Fh Reserved
30h “Page 30h: QoS Registers” on page 235
31h “Page 31h: Port-Based VLAN Registers” on page 245
32h “Page 32h: Trunking Registers” on page 246
33h Reserved
34h “Page 34h: IEEE 802.1Q VLAN Registers” on page 248
l
tia
35h Reserved
36h “Page 36h: DOS Prevent Register” on page 257
en
37h–3Fh Reserved
40h “Page 40h: Jumbo Frame Control Register” on page 260
41h
fid
“Page 41h: Broadcast Storm Suppression Register” on
page 262
on
42h “Page 42h: EAP Register” on page 268
43h “Page 43h: MSPT Register” on page 272
44h–6Fh Reserved
C
70h “Page 70h: MIB Snapshot Control Register” on page 275

om
71h “Page 71h: Port Snapshot MIB Control Register” on

page 275
72h “Page 72h: Loop Detection Register” on page 276
dc
73h–7Fh Reserved
80h–83h Reserved
oa
84h Reserved
85h Reserved
Br
86h–87h Reserved
88h “Page 88h: IMP Port External PHY MII Registers Page
Summary” on page 278
90h “Page 90h: BroadSync HD Register” on page 279
91h “Page 91h: Traffic Remarking Register” on page 286
92h “Page 92h: EEE Control Register” on page 288
93h-A0h Reserved
A1h Reserved
A2h–EFh Reserved
Maps to all pages “Global Registers” on page 295
Broadcom®
April 6, 2016 • 53128-DS07-R Page 143
BCM53128 Data Sheet Page 00h: Control Registers
Page 00h: Control Registers

Table 34: Control Registers (Page 00h)
Address Bits Register Name

00h–07h 8/port “Port Traffic Control Register (Page 00h: Address 00h)” on page 146
08h 8 “IMP Port Control Register (Page 00h: Address 08h)” on page 147
09h–0Ah 8 Reserved
0Bh 8 “Switch Mode Register (Page 00h: Address 0Bh)” on page 148
0Ch–0Dh 16 Reserved
0Eh 8 “IMP Port State Override Register (Page 00h: Address 0Eh)” on page 148
0Fh 8 “LED Refresh Register (Page 00h: Address 0Fh)” on page 149
10h–11h 16 “LED Function 0 Control Register (Page 00h: Address 10h)” on page 150
l
tia
12h–13h 16 “LED Function 1 Control Register (Page 00h: Address 12h)” on page 151
14h–15h 16 “LED Function Map Register (Page 00h: Address 14h–15h)” on page 151
en
16h–17h 16 “LED Enable Map Register (Page 00h: Address 16h–17h)” on page 152
18h–19h 16 “LED Mode Map 0 Register (Page 00h: Address 18h–19h)” on page 152
1Ah–1Bh
1Ch
16
– fid
“LED Mode Map 1 Register (Page 00h: Address 1Ah–1Bh)” on page 152
“LED Control Register (Page 00h: Address 1Ch)” on page 153
on
1Dh 8 “PHY LED Control Register (Page 00h: Address 1Dh)” on page 153
1Eh – Reserved
C
1Fh 8 Reserved
20h – Reserved
om
21h 8 “Port Forward Control Register (Page 00h: Address 21h)” on page 154
22h–23h – Reserved
24h–25h 16 “Protected Port Selection Register (Page 00h: Address 24h–25h)” on page 155
dc
26h–27h 16 “WAN Port Select Register (Page 00h: Address 26h–27h)” on page 155
28h–2Bh 32 “Pause Capability Register (Page 00h: Address 28h–2Bh)” on page 155
oa
2Ch–2Eh – Reserved
2Fh 8 “Reserved Multicast Control Register (Page 00h: Address 2Fh)” on page 156
Br
30h – Reserved
31h 8 Reserved
32h–33h 16 “Unicast Lookup Failed Forward Map Register (Page 00h: Address 32h)” on
page 157
34h–35h 16 “Multicast Lookup Failed Forward Map Register (Page 00h: Address 34h–35h)” on
page 157
36h–37h 16 “MLF IPMC Forward Map Register (Page 00h: Address 36h–37h)” on page 158
38h–39h 16 “Pause Pass Through for RX Register (Page 00h: Address 38h–39h)” on page 158
3Ah–3Bh 16 “Pause Pass Through for TX Register (Page 00h: Address 3Ah–3Bh)” on page 158
3Ch–3Dh 16 “Disable Learning Register (Page 00h: Address 3Ch–3Dh)” on page 159
3Eh–3Fh 16 “Software Learning Register (Page 00h: Address 3Eh–3Fh)” on page 159
Broadcom®
April 6, 2016 • 53128-DS07-R Page 144
Table 34: Control Registers (Page 00h) (Cont.)

4Ah–4Bh – Reserved
4Ch–57h – Reserved
58h–5Fh 8/port “Port State Override Register (Page 00h: Address 58h)” on page 160
60h 8 “IMP RGMII Control Register (Page 00h: Address 60h)” on page 161
75h – Reserved
78h 8 “MDIO IMP Port Address Register (Page 00h: Address 78h)” on page 161
79h 8 “Software Reset Control Register (Page 00h: Address 79h)” on page 161
7Ah–7Fh – Reserved
80h 8 “Pause Frame Detection Control Register (Page 00h: Address 80h)” on page 162
l
tia
88h 8 “Fast-Aging Control Register (Page 00h: Address 88h)” on page 162
89h 8 “Fast-Aging Port Control Register (Page 00h: Address 89h)” on page 162
en
8Ah–8Bh 16 “Fast-Aging VID Control Register (Page 00h: Address 8Ah–8Bh)” on page 163
B0h-B7h 64 “CPU Data 0 Share Register (Page 00h: Address B0h-B7h)” on page 163
B8h-BFh
F0h–F7h
64
8 fid
“CPU Data 1 Share Register (Page 00h: Address B8h-BFh) ” on page 163
“SPI Data I/O Register (Global, Address F0h)” on page 295, bytes 0-7
on
F8h–FDh – Reserved
8Ch–EFh – Reserved
C
FEh 8 “SPI Status Register (Global, Address FEh)” on page 295

FFh 8 “Page Register (Global, Address FFh)” on page 296
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 145
Port Traffic Control Register (Page 00h: Address 00h)

.
Table 35: Port Traffic Control Register Address Summary
Address Description
00h Port 0
01h Port 1
02h Port 2
03h Port 3
04h Port 4
05h Port 5
06h Port 6
07h Port 7
l
tia
Table 36: Port Control Register (Page 00h: Address 00h–07h)
en
BIt Name R/W Description Default
7:5 STP_STATE[2:0] R/W CPU writes the current computed states of its ~ HW_FWDG_EN
spanning tree algorithm for a given port.
fid
000 = No spanning tree (default for unmanaged
mode)
on
001 = Disabled state (default for managed mode)
010 = Blocking state
C
011 = Listening state

100 = Learning state
om
101 = Forwarding state

110–111 = Reserved
4:2 Reserved – – 000
dc
1 TX_DISABLE R/W 0 = Enable the transmit function of the port at the MAC 0
level.
oa
1 = Disable the transmit function of the port at the

MAC level.
Br
0 RX_DISABLE R/W 0 = Enable the receive function of the port at the MAC 0
level.
1 = Disable the receive function of the port at the MAC
level.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 146
IMP Port Control Register (Page 00h: Address 08h)

Table 37: IMP Port Control Register (Page 00h: Address 08h)
Bit Name R/W Description Default

7:5 Reserved R/W – –
4 RX_UCST_EN R/W Receive unicast enable 0
Allow unicast frames to be forwarded to the IMP, when
the IMP is configured as the frame management port,
and the frame was matching address table entry.
When cleared, unicast frames that meet the mirror
ingress/egress rules are forwarded to the frame
management port. Ignored if the IMP is not selected
as the Frame Management Port.
3 RX_MCST_EN R/W Receive multicast enable 0
Allow multicast frames to be forwarded to the IMP,
l
tia
when the IMP is configured as the Frame
Management Port, and the frame was flooded due to
no matching address table entry.
en
When cleared, multicast frames that meet the mirror
2 RX_BCST_EN R/W
management port.
fid
Receive broadcast enable 0
on
Allow broadcast frames to be forwarded to the IMP,
when the IMP is configured as the Frame
Management Port.
C
When cleared, multicast frames that meet the mirror

om
management port.
1:0 Reserved R/W – 0
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 147
Switch Mode Register (Page 00h: Address 0Bh)

Table 38: Switch Mode Register (Page 00h: Address 0Bh)

7:2 Reserved RO – 000001
1 SW_FWDG_EN R/W Software forwarding enable HW_FWDG_EN
SW_FWDG_EN = 1: Frame forwarding is enabled.
SW_FWDG_EN = 0: Frame forwarding is disabled.
Managed switch implementations should be
configured to disable forwarding on power-on to
allow the processor to configure the internal
address table and other parameters before frame
forwarding is enabled.
0 SW_FWDG_MODE R/W Software forwarding mode ~HW_FWDG_EN
l
0 = Unmanaged mode.
tia
1 = Managed mode.
The ARL treats reserved multicast addresses
en
differently depending on this selection.
IMP Port State Override Register (Page 00h: Address 0Eh)

fid
on
Table 39: IMP Port State Override Register (Page 00h: Address 0Eh)

C
7 MII_SW_OR R/W MII software override 0

om
0 = Use MII hardware pin status.

1 = Use contents of this register.
6 Reserved R/W Reserved 0
dc
5 Tx Flow Control Capability RO Link partner flow control capability 0

0 = Not PAUSE capable
oa
1 = PAUSE capable
4 Rx Flow Control Capability R/W Link partner flow control capability 0
Br
0 = Not PAUSE-capable
1 = PAUSE-capable
3:2 SPEED R/W Speed 10
00 = 10 Mbps
01 = 100 Mbps
10 = 1000 Mbps
11 = 200 Mbps
1 FDX R/W Full-duplex 1
0 = Half-duplex
1 = Full-duplex
Broadcom®
April 6, 2016 • 53128-DS07-R Page 148
Table 39: IMP Port State Override Register (Page 00h: Address 0Eh) (Cont.)

0 LINK R/W Link status 0
0 = Link fail
1 = Link pass
LED Control Register (Page 00h: Address 0Fh–1Bh)

Table 40: LED Control Register Address Summary
Address Description
0Fh LED refresh control register
10h–11h LED function 0 control register
l
12h–13h LED function 1 control register
tia
14h–15h LED function map control register
16h–17h LED enable map register
en
18h–19h LED mode map 0 register
1Ah–1Bh LED mode map 1 register
LED Refresh Register (Page 00h: Address 0Fh)

fid
on
Table 41: LED Refresh Register (Page 00h: Address 0Fh)
C

om
7 LED_EN R/W Enable LED 1

6 POST_EXEC R/W Write 1 to re-start POST. 0
dc
5 POST_PSCAN_EN R/W When enabled, switch scans the port during the 0
POST period.
4 POSt_Cable_diag_en R/W Enable cable diagnostics display during POST 0
oa
3 Normal_Cable_diag_en R/W Enable cable diagnostics display in normal 0

mode
Br
2:0 LED_Refresh_rate R/W LED refresh count register (i.e., LED blinking 3h
rate)
Refresh time = (N+1) * 10 ms
• 000: Reserved
• 001: 20 ms/25 Hz
• 010: 30 ms/16 Hz
• 011: 40 ms/12 Hz
• 100: 50 ms/10 Hz
• 101: 60 ms/8 Hz
• 110: 70 ms/7 Hz
• 111: 80 ms/6 Hz
Broadcom®
April 6, 2016 • 53128-DS07-R Page 149
LED Function 0 Control Register (Page 00h: Address 10h)

Table 42: LED Function 0 Control Register (Page 00h: Address 10h–11h)

15:0 LED_FUNCTION R/W The following is the list of functions assigned LED MODE[1:0] = 00:
to each bit: 16'h0120
15: Reserved LED MODE[1:0] = 01:
14: BroadSync HD Link 16'h0C40
13: 1G/ACT LED MODE[1:0] = 10:
16'h0124
12: 10/100M/ACT
LED MODE[1:0] = 11:
11: 100M/ACT 16'h0C04
10: 10M/ACT
9: SPD1G
8: SPD100M
l
tia
7: SPD10M
6: DPX/COL
en
5: LNK/ACT
4: COL
3: ACT
2: DPX
1: LNK
fid
on
0: Reserved
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 150
LED Function 1 Control Register (Page 00h: Address 12h)

Table 43: LED Function 1 Control Register (Page 00h: Address 12h–13h)

15:0 LED_FUNCTION R/W The following is the list of functions assigned to LED MODE[1:0] = 00:
each bit: 16'h0320
15: Reserved LED MODE[1:0] = 01:
14: BroadSync HD Link 16'h3040
13: 1G/ACT LED MODE[1:0] = 10:
16'h0324
12: 10/100M/ACT
LED MODE[1:0] = 11:
11: 100M/ACT 16'h2C04
10: 10M/ACT
9: SPD1G
8: SPD100M
l
tia
7: SPD10M
6: DPX/COL
en
5: LNK/ACT
4: COL
3: ACT
2: DPX
1: LNK
fid
on
0: Reserved
C
LED Function Map Register (Page 00h: Address 14h–15h)

om
Table 44: LED Function Map Register (Page 00h: Address 14h–15h)

dc

oa
8:0 LED_FUNC_MAP R/W Per port select function bit. Each port LED 1FFh
follows the function table specified for each port.
1: Select Function 1.
Br
0: Select Function 0.
Bits [7:0] correspond to ports [7:0].
Broadcom®
April 6, 2016 • 53128-DS07-R Page 151
LED Enable Map Register (Page 00h: Address 16h–17h)

Table 45: LED Enable Map Register (Page 00h: Address 16h–17h)

8:0 LED_EN_MAP R/W Per port enable bit 1FFh
1: Enable
0: Disable
LED Mode Map 0 Register (Page 00h: Address 18h–19h)

Table 46: LED Mode Map 0 Register (Page 00h: Address 18h–19h)
l
tia
en
8:0 LED_MODE_MAP0 R/W Combine with LED_MODE_MAP1 to decide 1FFh
per port LED output mode.
fid
on
LED Mode Map 1 Register (Page 00h: Address 1Ah–1Bh)
C
Table 47: LED Function Map 1 Control Register (Page 00h: Address 1Ah–1Bh)

om

8:0 LED_MODE_MAP1 R/W Per port select function bit 1FFh
dc
LED_FUNC_MAP[1:0]
00: LED off
oa
01: LED on
10: LED blinking
Br
11: LED auto
See “LED Interfaces” on page 119 for more information.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 152
LED Control Register (Page 00h: Address 1Ch)

Table 48: LED Control Register (Page 00h: Address 1Ch)

7:4 POST_LED_CTRL R/W Post LED Control 0xF
The four bits control the LED ON/OFF state during POST to
allow dual-color LED to be tested.
Bits[7:4] control each port four LED pins as below.
Port 0 LEDP[31:28]
Port 1 LEDP[27:24]
Port 2 LEDP[23:20]
Port 3 LEDP[19:16]
Port 4 LEDP[15:12]
Port 5 LEDP[11:8]
l
tia
Port 6 LEDP[7:4]
Port 7 LEDP[3:0]
en
1: The LED pin is activated during POST.
0: The LED pin is deactivated during POST.
3 DUAL_LED_CTRL R/W Dual-color LED Test Control 0x0
fid
1: One side of the dual-color LED, which corresponding
POST_LED_CTRL bit = 1, will be tested during POST firstly,
on
and then test the other side of the dual-color LED, which
corresponding POST_LED_CTRL bit = 0.
C
0: Only one side of the dual-color LED, which corresponding

POST_LED_CTRL bit = 1, will be tested during POST.
om
2:0 Reserved R/W Reserved 0x0
PHY LED Control Register (Page 00h: Address 1Dh)

dc
Table 49: PHY LED Control Register (Page 00h: Address 1Dh)
oa

Br
7:4 PHY_LED_FUNC1 R/W Bit 7: PHYLED4 of LED Function 1 LED Mode[1:0] = 00: 8'h88
Bit 6: PHYLED3 of LED Function 1 LED Mode[1:0] = 01: 8'h88
Bit 5: PHYLED2 of LED Function 1
3:0 PHY_LED_FUNC0 R/W Bit 3: PHYLED4 of LED Function 0 LED Mode[1:0] = 10: 8''h00
Bit 2: PHYLED3 of LED Function 0 LED Mode[1:0] = 11: 8'h00
Broadcom®
April 6, 2016 • 53128-DS07-R Page 153
Port Forward Control Register (Page 00h: Address 21h)

Table 50: Port Forward Control Register (Page 00h: Address 21h)

7 MCST_DLF_FWD_EN R/W 1 = Forward multicast lookup failed frames according 0
to multicast lookup failed forward map register (Page
00h: Address 34h)
0 = Flood multicast packet if fail ARL table lookup
6 UCST_DLF_FWD_EN R/W 1 = Forward unicast lookup failed frames according 0h
to Unicast Lookup failed forward map register (Page
00h: Address 32h)
0 = Flood unicast packet if fail ARL table lookup
5:3 Reserved R/W Reserved 0
2 INRANGE_ERR_DIS R/W In-Range Error Discard. When bit = 1, the ingress 0
port will discard the frames with Length field
l
tia
mismatch the frame length.
The following is the definition of InRangeErrors.
en
In-Range Errors Frames: The frames received with
good CRC and one of the following”
• The value of Length/Type field is between 46 and
fid
1500 inclusive and does not match the number of
(MAC Client Data + PAD) data octets received.
on
or
• The value of Length/Type field is less than 46,
and the number of data octets received is greater
C
than 46 (which does not require padding).

1 OUTRANGE_ERR-DIS R/W Out of Range Error Discard. When bit = 1, the 0
om
ingress port will discard the frames with length field

between 1500 and 1536 (exclude 1500 and 1536)
and with good CRC. This option only controls the
dc
length field checking, but not the frame length

checking.
oa

Br
See “Egress PCP Remarking” on page 57 for more information.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 154
Protected Port Selection Register (Page 00h: Address 24h–25h)

Table 51: Protected Port Selection Register (Page 00h: Address 24h–25h)

15:9 Reserved RO Reserved 0
8:0 PORT_SELECT R/W Protected port selection 0
Bit 8: IMP port
Bits [7:0] correspond to ports [7:0], respectively.
1 = Port protected. Cannot send/receive to other protected
ports.
0 = Port is not protected.
See “Protected Ports” on page 47 for more information.
l
tia
WAN Port Select Register (Page 00h: Address 26h–27h)
en
Table 52: WAN Port Select Register (Page 00h: Address 26h–27h)
BIt
15:10
Name
Reserved
R/W
RO
Description
Reserved fid Default
0
on
C
7:0 WAN_PORT_MAP R/W Set assigned WAN port to 1. 0

om
Pause Capability Register (Page 00h: Address 28h–2Bh)

dc
Table 53: Pause Capability Register (Page 00h: Address 28h–2Bh)

oa

Br
23 EN_OVERIDE R/W Forces the content of this register setting to be used 0

over the auto-negotiation result.
17:9 EN_RX_PAUSE_CAP R/W Enabling the receive pause capability. 0h
Bit 17: IMP port
8:0 EN_TX_PAUSE_CAP R/W Enables the transmit pause capability. 0h
Bit 8: IMP port
Broadcom®
April 6, 2016 • 53128-DS07-R Page 155
Reserved Multicast Control Register (Page 00h: Address 2Fh)

Table 54: Reserved Multicast Control Register (Page 00h: Address 2Fh)

7 Multicast Learning R/W Multicast learning enable 0
0 = Do not learn unicast source addresses of frames
that have a reserved multicast destination address.
1 = Learn unicast source addresses even from frames
that have a reserved multicast destination address.
See “Address Management” on page 57 for more
information.
4 En_Mul_4 R/W Specifies if packets with the destination addresses in 0
the below range are to be forwarded to the appropriate
port or dropped when operating in unmanaged mode.
l
tia
01-80-C2-00-00-20 ~ 01-80-C2-00-00-2F
0 = Forward
en
1 = Drop
3 En_Mul_3 R/W Specifies if packets with the destination addresses in 0
fid
01-80-C2-00-00-11 ~ 01-80-C2-00-00-1F
on
0 = Forward
1 = Drop
C
2 En_Mul_2 R/W Specifies if packets with the destination address below 0

are to be forwarded to the appropriate port or dropped
om
when operating in unmanaged mode.

01-80-C2-00-00-10
0 = Forward
dc
1 = Drop
1 En_mul_1 R/W Specifies if packets with the destination addresses in 1
oa

Br
01-80-C2-00-00-02 ~ 01-80-C2-00-00-0F
0 = Forward
1 = Drop
0 En_Mul_0 R/W Specifies if packets with the destination address below 0
are to be forwarded to the appropriate port or dropped
when operating in unmanaged mode.
01-80-C2-00-00-00
0 = Forward
1 = Drop
See “Multicast Addresses” on page 61 for more information.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 156
Unicast Lookup Failed Forward Map Register (Page 00h: Address

32h)
Table 55: Unicast Lookup Failed Forward Map Register (Page 00h: Address 32h–33h)

8:0 UNI_DLF_MAP R/W Unicast lookup failed forward map 0
Bit 8: IMP port
When the UCST_DLF_FWD_EN bit in “Port Forward
Control Register (Page 00h: Address 21h)” on page 154 is
enabled and a unicast lookup failure occurs, the ARL table
forwards the frame according to the contents of this
register. If this register remains in default value, the frame
is dropped.
l
tia
0 = Do not forward a unicast lookup failure to this port.
1 = Forward a unicast lookup failure to this port.
en
See “Unicast Addresses” on page 59 for more information.
fid
Multicast Lookup Failed Forward Map Register (Page 00h: Address
on
34h–35h)
C
Table 56: Multicast Lookup Failed Forward Map Register (Page 00h: Address 34h–35h)
om

8:0 MCST_DLF_MAP R/W Multicast lookup failed forward map 0
dc
Bit 8: IMP port

oa
When the MCST_DLF_FWD_EN bit in port forward

control register (Page 00h:Address 21h) is enabled and
Br
a multicast lookup failure occurs, the ARL table

forwards the frame according to the contents of this
register. If this register remains in default value, the
frame is dropped.
0 = Do not forward a multicast lookup failure to this port.
1 = Forward a multicast lookup failure to this port.
See “Multicast Addresses” on page 61 for more information.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 157
MLF IPMC Forward Map Register (Page 00h: Address 36h–37h)

Table 57: MLF IMPC Forward Map Register (Page 00h: Address 36h–37h)

8:0 MLF_IPMC_FWD_MAP R/W IPMC forward map 0
Bit 8: IMP port
Pause Pass Through for RX Register (Page 00h: Address 38h–39h)

Table 58: Pause Pass Through for RX Register (Page 00h: Address 38h–39h)
l
tia
7:0 IGNORE_PAUSE FRAME R/W RX pause pass through map 0
en
_RX 1: Ignore IEEE 802.3x
0: Comply with IEEE 802.3x pause frame
fid
receiving.
Bits [7:0] correspond to ports [7:0],
respectively.
on
C
Pause Pass Through for TX Register (Page 00h: Address 3Ah–3Bh)

om
Table 59: Pause Pass Through for TX Register (Page 00h: Address 3Ah–3Bh)

dc

8:0 IGNORE_PAUSE FRAME R/W TX pause pass through map 0
oa
_TX 1: Ignore IEEE 802.3x.

0: Comply with IEEE 802.3x pause frame
receiving
Br
Bit 8: IMP port

Broadcom®
April 6, 2016 • 53128-DS07-R Page 158
Disable Learning Register (Page 00h: Address 3Ch–3Dh)

Table 60: Disable Learning Register (Page 00h: Address 3Ch–3Dh)

8:0 DIS_LEARNING R/W 1 = Disable learning 0
0 = Enable learning
Bit 8: IMP port
Software Learning Register (Page 00h: Address 3Eh–3Fh)

Table 61: Software Learning Control Register (Page 00h: Address 3Eh–3Fh)
l
tia
15:9 Reserved RO Reserved –
en
8:0 SW_LEARN_CNTL R/W 1: Software learning control enabled. 0
The behaviors are as follows.
fid
• Forwarding behavior: Incoming packet with
unknown SA will be copied to CPU port.
on
• Learning behavior: Allow S/W to decide
whether incoming packet learn or not. In S/
W learning mode, the H/W learning
C
mechanism will be disabled automatically.

• Refreshed behavior: Allow refreshed
om
mechanism to operate properly even

through the H/W learning had been disabled.
0: Software learning control disabled.
dc
Forwarding/Learning/Refreshed behavior to
keep hardware operation.
Bit 8: IMP port
oa
Bits [7:0] correspond to ports [7:0]

Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 159
Port State Override Register (Page 00h: Address 58h)

Table 62: Port State Override Register Address Summary
Address Description
58h Port 0
59h Port 1
5Ah Port 2
5Bh Port 3
5Ch Port 4
5Dh Port 5
5Eh Port 6
5Fh Port 7
l
tia
Table 63: Port State Override Register (Page 00h: Address 58h–5Fh)
en
7 Reserved R/W Reserved –
6 Software Override R/W
fid
Writing 1 to this bit allows the values of the bits [7:0]
to be written to the external PHY. Writing 0 to this
bit prevents these values from overriding the
0
on
present external PHY conditions.
5 TXFlow Control Enable R/W The value of this bit overrides the existing 0
C
conditions of the external PHY port if bit 6 is written

to 1.
om
0 = Flow control disabled for transmit traffic.

1 = Flow control enabled for transmit traffic.
4 RX Flow Control Enable R/W The value of this bit overrides the existing 0
dc

to 1.
0 = Flow control disabled for receive traffic.
oa
1 = Flow control enabled for receive traffic.

3:2 Speed R/W The value of this bit overrides the existing 10
Br

to 1.
00 = 10 Mbps
01 = 100 Mbps
10 = 1000 Mbps
11 = Illegal state
1 Duplex Mode R/W The value of this bit overrides the existing 1
to 1.
0 = Half-duplex
1 = Full-duplex
Broadcom®
April 6, 2016 • 53128-DS07-R Page 160
Table 63: Port State Override Register (Page 00h: Address 58h–5Fh) (Cont.)

0 Link State R/W The value of this bit overrides the existing 1
1.
1 = Link-up
0 = Link-down
IMP RGMII Control Register (Page 00h: Address 60h)

Table 64: IMP RGMII Control Register (Page 00h: Address 60h)

7:2 Reserved R/W Write as default. Ignore on read. 0
l
tia
1 RGMII_DLL_RXC_ENABL R/W 1 = RGMII RXC clock delay by DLL is enabled Strap pin
E (delay mode) IMP_RXC_DELA
0 = RGMII RXC clock delay by DLL is disabled Y
en
(normal mode)
0 RGMII_DLL_TXC_ENABL R/W 1 = RGMII TXC clock delay by DLL is enabled Strap pin
E (delay mode)
fid
0 = RGMII TXC clock delay by DLL is disabled
IMP_TXC_DELA
Y
on
(normal mode)
C
MDIO IMP Port Address Register (Page 00h: Address 78h)

om
Table 65: MDIO IMP PORT Address Register (Page 00h: Address 78h)

dc

4:0 IMP_MDIO_ADDRESS R/W IMP PORT MDIO address 18h
oa
Software Reset Control Register (Page 00h: Address 79h)

Br
Table 66: Software Reset Control Register (Page 00h: Address 79h)

7 SW_RST R/W Software reset (Bit4 “EN_SW_RST” MUST be 0
enabled as well). Software reset, write “1” to activate
a RESET, “0” to clear the reset state.
1 = Activate reset.
0 = Clear reset.
6:5 Reserved R/O Reserved 0
4 EN_SW_RST R/W Enable software reset. 0
Broadcom®
April 6, 2016 • 53128-DS07-R Page 161
Pause Frame Detection Control Register (Page 00h: Address 80h)

Table 67: Pause Frame Detection Control Register (Page 00h: Address 80h)

0 PAUSE_IGNORE_DA R/W 0 = Check DA field on pause frame detection. 0
1 = Ignore DA field on pause frame detection.
Fast-Aging Control Register (Page 00h: Address 88h)

Table 68: Fast-Aging Control Register (Page 00h: Address 88h)
l
7 Fast_Age_Start/Done R/W Set bit to 1 triggers the fast aging process. 0
tia
When the fast aging process is done, this bit is
cleared to 0.
en
5 EN_AGE_MCAST R/W Enable Aging Multicast Entry 0
fid
1: Aging multicast Entries in ARL Table
0: Disable Aging Multicast Entries in ARL Table
on
Note: The EN_AGE_MCAST and the EN_AGE_Port
can not enable (set to 1) at the same time.
4 EN_AGE_SPT R/W When set, check spanning tree ID. 0
C
3 EN_AGE_VLAN R/W When set, check VLAN ID. 0

om
2 EN_AGE_Port R/W When set, check port ID. 0

1 EN_AGE_Dynamic R/W When set, age out dynamic entry. 1
0 EN_AGE_Static R/W When set, age out static entry. 0
dc
Fast-Aging Port Control Register (Page 00h: Address 89h)

oa
Table 69: Fast-Aging Port Control Register (Page 00h: Address 89h)
Br

3:0 Fast Age Single Port R/W Fast age single port select 0
Writing bits [3:0] selects the port to be fast-aged.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 162
Fast-Aging VID Control Register (Page 00h: Address 8Ah–8Bh)

Table 70: Fast-Aging VID Control Register (Page 00h: Address 8Ah–8Bh)

11:0 Fast Age Single VID R/W Fast age single VID select 0
Writing bits [11:0] selects the VID to be fast-aged.
CPU Data 0 Share Register (Page 00h: Address B0h-B7h)

Table 71: CPU Data 0 Share Register (Page 00h: Address B0h–B7h)
l
63:0 CPU_DATA_SHARE R/W Data to be shared by internal 8051 and external 0x0
tia
CPU
en
.
CPU Data 1 Share Register (Page 00h: Address B8h-BFh)fid

on
Table 72: CPU Data 1 Share Register (Page 00h: Address B8h–BFh)
C

63:0 CPU_DATA_SHARE R/W Data to be shared by internal 8051 and external 0x0
om
CPU
.
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 163
BCM53128 Data Sheet Page 01h: Status Registers
Page 01h: Status Registers

Table 73: Status Registers (Page 01h)

00h–01h 16 “Link Status Summary (Page 01h: Address 00h)” on page 164
02h–03h 16 “Link Status Change (Page 01h: Address 02h)” on page 165
04h–07h 32 “Port Speed Summary (Page 01h: Address 04h)” on page 165
08h–09h 16 “Duplex Status Summary (Page 01h: Address 08h)” on page 166
0Ah–0Dh 32 “Pause Status Summary (Page 01h: Address 0Ah)” on page 166
0Eh–0Fh 16 “Source Address Change Register (Page 01h: Address 0Eh)” on
page 167
10h–45h 48/port “Last Source Address Register (Page 01h: Address 10h)” on page 167
l
46h–EFh – Reserved
tia
F0h–F7h 8 “SPI Data I/O Register (Global, Address F0h)” on page 295, bytes 0–7
en
fid
on
Link Status Summary (Page 01h: Address 00h)
Table 74: Link Status Summary Register (Page 01h: Address 00h–01h)
C

om

8:0 LINK_STATUS RO Link status 0
dc
Bit 8: IMP port

oa
0 = Link fail
1 = Link pass
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 164
Link Status Change (Page 01h: Address 02h)

Table 75: Link Status Change Register (Page 01h: Address 02h–03h)

8:0 LINK_STATUS_CHANGE RO Link status change. 0x1FF
Bit 8: IMP port
Upon change of link status, a bit remains set until
cleared by a read operation.
0 = Link status constant.
1 = Link status change.
Port Speed Summary (Page 01h: Address 04h)
l
tia
Table 76: Port Speed Summary Register (Page 01h: Address 04h–07h)
en
31:18
17:0
Reserved
PORT_SPEED
PO
RO
Reserved
Port speed fid 0
0x2AAAA
on
The speed of each port is reported based on the mapping
below:
• Bits [17:16] = IMP port
C
• Bits [15:14] = Port 7

• Bits [13:12] = Port 6
om
• Bits [11:10] = Port 5

• Bits [9:8] = Port 4
dc
• Bits [7:6] = Port 3

• Bits [5:4] = Port 2
oa
• Bits [3:2] = Port 1

• Bits [1:0] = Port 0
The value of the bits are:
Br
• 00 = 10 Mbps
• 01 = 100 Mbps
• 10 = 1000 Mbps
• 11 = 200 Mbps (for IMP port only)
Broadcom®
April 6, 2016 • 53128-DS07-R Page 165
Duplex Status Summary (Page 01h: Address 08h)

Table 77: Duplex Status Summary Register (Page 01h: Address 08h–09h)

8:0 DUPLEX_STATE RO Duplex state 0x1FF
Bit 8: IMP port
0 = Half-duplex
1 = Full-duplex
Pause Status Summary (Page 01h: Address 0Ah)
l
Table 78: PAUSE Status Summary Register (Page 01h: Address 0Ah–0Dh)
tia
en
17:9 RECEIVE_PAUSE_STATE RO Pause state. Receive pause capability 0x100
fid
Bit 17: IMP port
on
0 = Disabled
1 = Enabled
C
8:0 TRANSMIT_PAUSE_STAT RO Transmit pause capability 0x100

E Bit 8: IMP port
om

0 = Disabled
1 = Enabled
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 166
Source Address Change Register (Page 01h: Address 0Eh)

Table 79: Source Address Change Register (Page 01h: Address 0Eh–0Fh)

8:0 SRC_ADDR_CHANGE RC Source address change 0
Bit 8: IMP port
The value of this bit is 1 if a change in the source
address is detected on the given port.
The bit remains set until cleared by a read
operation.
0 = No change in source address since last read.
1 = Source address has changed since last read.
l
tia
Last Source Address Register (Page 01h: Address 10h)
en
.
Table 80: Last Source Address Register Address Summary
Address
10h–15h
fid
Description
Port 0
on
16h–1Bh Port 1
1Ch–21h Port 2
C
22h–27h Port 3
om
28h–2Dh Port 4
2Eh–33h Port 5
34h–39h Port 6
dc
3Ah–3Fh Port 7
40h–45h IMP port
oa
Br
Table 81: Last Source Address (Page 01h: Address 10h–45h)

47:0 LAST_SOURCE_ADD RO The 48-bit source address detected on the last 0
packet ingressed.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 167
BCM53128 Data Sheet Page 02h: Management/Mirroring Registers
Page 02h: Management/Mirroring Registers

Table 82: Aging/Mirroring Registers (Page 02h)

00h 8 “Global Management Configuration Register (Page 02h: Address 00h)”
on page 169
01h 8 “IMP Port ID Register (Page 02h: Address 01h)” on page 169
02h 8 Reserved
03h 8 “IMP Port ID Register (Page 02h: Address 01h)” on page 169
04h–05h 16 “RMON MIB Steering Register (Page 02h: Address 04h)” on page 170
06h–09h 32 “Aging Time Control Register (Page 02h: Address 06h)” on page 170
l
10h–11h 16 “Mirror Capture Control Register (Page 02h: Address 10h)” on page 171
tia
12h–13h 16 “Ingress Mirror Control Register (Page 02h: Address 12h)” on page 171
14h–15h 16 “Ingress Mirror Divider Register (Page 02h: Address 14h)” on page 172
en
16h–1Bh 48 “Ingress Mirror MAC Address Register (Page 02h: Address 16h)” on
page 172
1Ch–1Dh
1Eh–1Fh
16
16 fid
“Egress Mirror Control Register (Page 02h: Address 1Ch)” on page 173
“Egress Mirror Divider Register (Page 02h: Address 1Eh)” on page 174
on
20h–25h 48 “Egress Mirror MAC Address Register (Page 02h: Address 20h)” on
page 174
C
30h–33h 8 Device ID number
om
34h–3Fh – Reserved
40h 8 Revision ID number
dc
50h–53h 32 “High-Level Protocol Control Register (Page 02h: Address 50h–53h)” on

page 175
oa
Br

Broadcom®
April 6, 2016 • 53128-DS07-R Page 168
Global Management Configuration Register (Page 02h: Address 00h)

Table 83: Global Management Configuration Register (Page 02h: Address 00h)

7:6 En_IMP_Port R/W IMP port enable 00
00 = No frame management port.
01 = Reserved
10 = Enable IMP port only. All traffic to CPU from LAN
and WAN ports will be forwarded to IMP port.
11 = Reserved
These bits are ignored when SW_FWD_MODE =
Unmanaged in the “Switch Mode Register (Page 00h:
Address 0Bh)” on page 148.
l
tia
1 En_Rx_BPDU R/W Receive BPDU enable 0
en
Enables all ports to receive BPDUs and forwards to the
IMP port. This bit must be set to globally allow BPDUs
0 Reset MIB R/W

to be received.
fid
Reset MIB counters 0
on
Resets all MIB counters for all ports to 0 (pages 20h–
28h). This bit must be set and then cleared in
successive write cycles to activate the reset operation.
C
om
IMP Port ID Register (Page 02h: Address 01h)

Table 84: IMP Port ID Register (Page 02h: Address 01h)
dc

oa
7:4 Reserved RO Reserved 0x0

3:0 IMP_PRT_ID RO IMP Port ID 0x8
Br
The field specifies the port ID of the IMP port. The

BCM53128 IMP is fixed at Port 8.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 169
Broadcom Header Control Register (Page 02h: Address 03h)

Table 85: Broadcom Tag Control Register (Page 02h: Address 03h)

0 BRCM_HDR_EN R/W Broadcom Tag enable for IMP. Enable Broadcom header for 1
IMP port.
1 = Additional header information is inserted into the original
frame, between original SA field and Type/Length fields.
The tag includes the Broadcom Tag field.
0 = Without additional header information.
RMON MIB Steering Register (Page 02h: Address 04h)
l
tia
Table 86: RMON MIB Steering Register (Page 02h: Address 04h–05h)
en
8:0 Override RMON R/W Override RMON receive 0
Receive
fid
Forces the RMON packet size bucket counters from the
normal default of snooping on the receive side of the MAC
on
to the transmit side. This allows the RMON bucket counters
to snoop either transmit or receive, allowing full-duplex
MAC support.
C
Bit 8: IMP port

om
Aging Time Control Register (Page 02h: Address 06h)

dc
Table 87: Aging Time Control Register (Page 02h: Address 06h–09h)
oa

Br
20 Age Change R/W Age change enable 0

1 = Set age time via bits [19:0] immediately.
0 = Age time will be changed by the new value specified
in bit[19:0], after the original age time value in bit[19:0]
times up.
19:0 AGE_TIME R/W Specifies the aging time in seconds for dynamically 300d
learned addresses. Maximum age time is 1,048,575s.
Setting the AGE_TIME to 0 disables the aging process.
For more information on ARL table aging, see “Address
Aging” on page 64.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 170
Mirror Capture Control Register (Page 02h: Address 10h)

Table 88: Mirror Capture Control Register (Page 02h: Address 10h–11h)

15 Mirror Enable R/W Global mirror enable 0
0 = Disable mirror capture feature
1 = Enable mirror capture feature
14 BLK_NOT_MIR R/W When enabled, all traffic to MIRROR_CAPTURE_PORT 0
is blocked, except for mirror traffic. Nonmirror traffic is
disabled.
0 = No traffic blocking on mirror capture port
1 = Traffic to mirror capture port blocked unless mirror
traffic
l
tia
3:0 Capture Port R/W Mirror capture port ID 0
Binary value identifies the single unique port that is
en
designated as the port where all ingress and/or egress
traffic is mirrored.
fid
For additional information about port mirroring, see “Port Mirroring” on page 48.
on
Ingress Mirror Control Register (Page 02h: Address 12h)
C
Table 89: Ingress Mirror Control Register (Page 02h: Address 12h–13h)
om

15:14 IN_MIRROR_FILTER R/W Ingress mirror filter 0
dc
Filters frames to be forwarded to the mirror capture port,

specified in “Mirror Capture Control Register (Page 02h:
oa
Address 10h)” on page 171.

00 = Mirror all ingress frames.
Br
01 = Mirror all ingress frames with DA =

IN_MIRROR_MAC.
10 = Mirror all ingress frames with SA =
IN_MIRROR_MAC.
11 = Reserved
IN_MIRROR_MAC is specified in “Ingress Mirror MAC
Address Register (Page 02h: Address 16h)” on page 172.
13 IN_DIV_EN R/W Ingress divider enable 0
The ingress divider mirrors every nth ingress frame that
has passed through the IN_MIRROR_FILTER (n
represents the IN_MIRROR_DIV defined in “Ingress Mirror
Divider Register (Page 02h: Address 14h)” on page 172).
0 = Disable ingress divider feature.
1 = Enable ingress divider feature.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 171
Table 89: Ingress Mirror Control Register (Page 02h: Address 12h–13h) (Cont.)

8:0 IN_MIRROR_MASK R/W Ingress mirror port mask 0
Bit 8: IMP port
Ports with the corresponding bit set to 1 have ingress
frames mirrored to the MIRROR_CAPTURE_PORT. While
multiple ports can be set as an Ingress Mirror port, severe
congestion and/or frame loss may occur if excessive
bandwidth from the ingress mirrored port (s) is directed to
the MIRROR_CAPTURE_PORT. Setting a mirror filter via
bits [15:14] or divider via bit 13 may be helpful.
l
tia
Ingress Mirror Divider Register (Page 02h: Address 14h)
en
Table 90: Ingress Mirror Divider Register (Page 02h: Address 14h–15h)
BIt Name R/W Description

fid Default
on
9:0 IN_MIRROR_DIV R/W Ingress mirror divider 0
C
Receive frames that have passed the

IN_MIRROR_FILTER rule can further be pruned to
reduce the overall number of frames returned to the
om
MIRROR_CAPTURE_PORT. When the IN_DIV_EN bit

in the “Ingress Mirror Control Register (Page 02h:
Address 12h)” on page 171 is set, frames that pass the
dc
IN_MIRROR_FILTER rule are further divided by n,

where n = IN_MIRROR_DIV + 1.
oa
Br
Ingress Mirror MAC Address Register (Page 02h: Address 16h)

Table 91: Ingress Mirror MAC Address Register (Page 02h: Address 16h–1Bh)

47:0 IN_MIRROR_MAC R/W Ingress mirror MAC address 0
MAC address that is compared against ingress
frames in accordance with the
IN_MIRROR_FILTER rules in “Ingress Mirror
Control Register (Page 02h: Address 12h)” on
page 171.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 172
Egress Mirror Control Register (Page 02h: Address 1Ch)

Table 92: Egress Mirror Control Register (Page 02h: Address 1Ch–1Dh)

15:14 OUT_MIRROR_FILTE R/W Egress mirror filter 0
R Filters egress frames that are forwarded to the mirror
capture port, specified in “Mirror Capture Control
Register (Page 02h: Address 10h)” on page 171.
00 = Mirror all egress frames.
01 = Mirror all egress frames with DA =
OUT_MIRROR_MAC.
10 = Mirror all egress frames with SA =
OUT_MIRROR_MAC.
11 = Reserved.
OUT_MIRROR_MAC is specified in “Egress Mirror MAC
l
tia
Address Register (Page 02h: Address 20h)” on
page 174.
en
13 OUT_DIV_EN R/W Egress divider enable 0
The egress divider mirrors every nth egress frame that
has passed through the OUT_MIRROR_FILTER (n
fid
represents the OUT_MIRROR_DIV defined in “Egress
Mirror Divider Register (Page 02h: Address 1Eh)” on
on
page 174).
0 = Disable egress divider feature.
C
1 = Enable egress divider feature.

om
8:0 OUT_MIRROR_MASK R/W Egress mirror port mask 0

Bit 8: IMP port
dc
Ports with the corresponding bit set to 1 have egress

frames mirrored to the MIRROR_CAPTURE_PORT.
oa
While multiple ports can be set as an egress mirror port,

severe congestion and/or frame loss may occur if
excessive bandwidth from the egress mirrored port (s) is
Br
directed to the MIRROR_CAPTURE_PORT. Setting a

mirror filter via bits [15:14] or a divider via bit 13 may be
helpful.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 173
Egress Mirror Divider Register (Page 02h: Address 1Eh)

Table 93: Egress Mirror Divider Register (Page 02h: Address 1Eh–1Fh)

9:0 OUT_MIRROR_DIV R/W Egress mirror divider 0
Egressed frames that have passed the
OUT_MIRROR_FILTER rule can further be pruned to
reduce the overall number of frames returned to the
MIRROR_CAPTURE_PORT. When the
OUT_DIV_EN bit in the “Egress Mirror Control
Register (Page 02h: Address 1Ch)” on page 173 is
set, frames that pass the OUT_MIRROR_FILTER
rule are further divided by n, where
n = OUT_MIRROR_DIV + 1.
l
tia
en
Egress Mirror MAC Address Register (Page 02h: Address 20h)
fid
Table 94: Egress Mirror MAC Address Register (Page 02h: Address 20h–25h)
on
47:0 OUT_MIRROR_MAC R/W Egress mirror MAC address 0
C
MAC address that is compared against egress

frames in accordance with the
om
OUT_MIRROR_FILTER rules defined in “Egress

Mirror Control Register (Page 02h: Address
1Ch)” on page 173.
dc
oa
Device ID Register (Page 02h: Address 30h–33h)

Br
Table 95: Device ID Register (Page 02h: Address 30h–33h)

31:0 Device_ID RO Device ID 32'0005_3128
Revision Number Register (Page 02h: Address 40h)

Table 96: Egress Mirror MAC Address Register (Page 02h: Address 40h)

7:0 Revision_ID RO Revision number 0
Broadcom®
April 6, 2016 • 53128-DS07-R Page 174
High-Level Protocol Control Register (Page 02h: Address 50h–53h)

Table 97: High-Level Protocol Control Register (Page 02h: Address 50h–53h)

31:19 Reserved R/W Reserved –
18 MLD_QRY_FWD_MODE R/W MLD Query Message Forwarding Mode 0
1: MLD Query message frames will be trapped to
CPU port only.
0: MLD Query message frames will be forwarded
by L2 result and also copied to CPU.
17 MLD_QRY_EN R/W MLD Query Message Snooping/Redirect Enable 0
1: Enable MLD query message snooping/
redirect
0: Disable
l
16 MLD_RPTDONE_FWD_MO R/W MLDReport/DoneMessageForwardingMode 0
tia
DE 1: MLD report/done message frames will be
trapped to CPU port only
en
0: MLD report/done message frames will be
forwarded by L2 result and also copied to CPU
15 MLD_RPTDONE_EN R/W
fid
MLD Report/Done Message Snooping/Redirect 0
Enable
on
1: Enable MLD report/done message snooping/
redirect
0: Disable
C
14 IGMP_UKN_FWD_MODE R/W IGMP Unknown Message Forwarding Mode 0

1: IGMP unknown message frames will be
om

0: IGMP unknown message frames will be
dc
13 IGMP_UKN_EN R/W IGMP Unknown Message Snooping/Redirect 0

Enable
oa
1: Enable IGMP unknown message snooping/

redirect
Br
0: Disable
12 IGMP_QRY_FWD_MODE R/W IGMP Query Message Forwarding Mode 0
1: IGMP query message frames will be trapped
to CPU port only
0: IGMP query message frames will be
11 IGMP_QRY_EN R/W IGMP Query Message Snooping/Redirect 0
Enable
1: Enable IGMP query message Snooping/
Redirect
0: Disable
Broadcom®
April 6, 2016 • 53128-DS07-R Page 175
Table 97: High-Level Protocol Control Register (Page 02h: Address 50h–53h) (Cont.)

10 IGMP_RPTLVE_FWD_MOD R/W IGMP Report/Leave Message Forwarding Mode 0
E 1: IGMP report/leave message frames will be
0: IGMP report/leave message frames will be
9 IGMP_RPTLVE_EN R/W IGMP Report/Leave Message Snooping/ 0
Redirect Enable
1: Enable IGMP report/leave message
Snooping/Redirect
0: Disable
8 IGMP_DIP_EN R/W IGMP L3 DIP checking Enable 0
In addition to the IP datagram with a protocol
value of 2, IGMP will be classified by matching its
l
tia
DIP with the Class D IP
address(224.0.0.0~239.255.255.255).
en
5 ICMPv6_FWD_MODE R/W ICMPv6 (exclude MLD) Forwarding Mode 0
1: ICMPv6 frames will be trapped to CPU port
only.
fid
0: ICMPv6 frames will be forwarded by L2 result
on
and also copied to CPU.
4 ICMPv6_EN R/W ICMPv6 (exclude MLD) Snooping/Redirect 0
C
Enable
ICMPv6, with a next header value of 58, will be
classified by IPv6 datagram.
om
3 ICMPv4_EN R/W ICMPv4 Snooping Enable 0

ICMPv6, with a next header value of 0 and
dc
extension header next header value of 58, will be

classified by IPv6 datagram.
1: ICMPv4 frames will be forwarded by L2 result
oa

0: ICMPv4 frames will be forwarded by L2 result.
Br
2 DHCP_EN R/W DHCP Snooping Enable 0

1: DHCP frames will be forwarded by L2 result
0: DHCP frames will be forwarded by L2 result.
1 RARP_EN R/W RARP Snooping Enable 0
1: RARP frames will be forwarded by L2 result
0: RAPR frames will be forwarded by L2 result.
0 ARP_EN R/W ARP Snooping Enable 0
1: ARP frames will be forwarded by L2 result and
also copied to CPU.
0: ARP frames will be forwarded by L2 result.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 176
BCM53128 Data Sheet Page 03h: Interrupt Control Register
Page 03h: Interrupt Control Register

Table 98: Page 03h: Interrupt Control Register

00h-03h 32 “Interrupt Status Register (Page 03h: Address 00h)”
08h-0Bh 32 “Interrupt Enable Register (Page 03h: Address 08h)”
10h-11h 16 “IMP Sleep Timer Register (Page 03h: Address 10h)” on page 178
18h 8 “Sleep Status Register (Page 03h: Address 18h)” on page 178
20h 8 “External CPU Interrupt Trigger Register (Page 03h: Address 20h)” on
page 178
Interrupt Status Register (Page 03h: Address 00h)
l
tia
Table 99: Interrupt Status Register (Page 03h: Address 00h)
en
24:16 Link Status Change
Interrupt
R/W
fid
Each bit is set when the corresponding port status is
changed.
–
on
0 = No link status change
1 = Link status change
C
Bit [24]: IMP port

Bits [23:16]: Port[7:0]
om

0 IMP_Sleep_Timer_Run R/W Indicates the IMP port timer has been triggered. –
dc
Interrupt Enable Register (Page 03h: Address 08h)

oa
Table 100: Interrupt Enable Register (Page 03h: Address 08h)

Br

24:16 Link Status Change R/W Each bit is set when the corresponding port status is –
Interrupt Enable changed.
0 = Disable interrupt
1 = Enable interrupt
Bit [24]: IMP port
Bits [23:16]: Port[7:0]
0 IMP_Sleep_Timer_Run R/W Indicates the IMP port timer has been triggered. –
_Enable
Broadcom®
April 6, 2016 • 53128-DS07-R Page 177
BCM53128 Data Sheet Page 03h: Interrupt Control Register
IMP Sleep Timer Register (Page 03h: Address 10h)

Table 101: IMP Sleep Timer Register (Page 03h: Address 10h)

15:13 Reserved R/W Reserved 0x0
12:0 IMP Sleep Timer R/W The configuration value of IMP port sleep timer to indicate 0x0
the desired sleep recovery time (i.e., wake-up time). When
the timer is set by the CPU to a non-zero value, it puts the
IMP port to sleep. The wake-up time is the set value
decrease 1. The unit is in 1 sec.
Sleep Status Register (Page 03h: Address 18h)

Table 102: Sleep Status Register (Page 03h: Address 18h)
l
tia
en
0 IMP_Port_Sleep_ST RO IMP Port Sleep Status. 0x0
S 0 = IMP port is not in IMP_Sleep mode, whenever either
fid
the reset or the counter of IMP Sleep Timer is equal to
zero.
on
Note: The port is in IMP_SLEEP INIT state.
1 = IMP port is in IMP_Sleep mode, when the counter of
IMP Sleep Timer is not equal zero.
C
Note: The port is not in IMP_SLEEP INIT state.

om
External CPU Interrupt Trigger Register (Page 03h: Address 20h)

dc
Table 103: External CPU Interrupt Trigger Register (Page 03h: Address 20h)

oa

Br
0 EXT_CPU_INT R/W External CPU to internal 8051 Interrupt Trigger. 0x0

The External CPU trigger is an interrupt to the internal
8051 by setting the bit to 1.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 178
BCM53128 Data Sheet Page 04h: ARL Control Register
Page 04h: ARL Control Register

Table 104: ARL Control Registers (Page 04h)

00h 8 “Global ARL Configuration Register (Page 04h: Address 00h)” on
page 180
04h–09h 48 “BPDU Multicast Address Register (Page 04h: Address 04h)” on
page 180
0Ah–0Dh – Reserved
0Eh–0Fh 16 “Multiport Control Register (Page 04h: Address 0Eh–0Fh)” on page 181
10h–17h 64 “Multiport Address N (N=0–5) Register (Page 04h: Address 10h)” on
page 182
l
tia
18h–1Bh 32 “Multiport Vector N (N = 0–5) Register (Page 04h: Address 18h)” on
page 183
en
1Ch–1Fh – Reserved
page 182
28h–2Bh 32
fid
“Multiport Vector N (N = 0–5) Register (Page 04h: Address 18h)” on
page 183
on
C
page 182
om
page 183
dc
page 182
oa
page 183
Br

page 182
page 183
page 182
page 183
6Ch–FEh – Reserved
Broadcom®
April 6, 2016 • 53128-DS07-R Page 179
Table 104: ARL Control Registers (Page 04h) (Cont.)

Global ARL Configuration Register (Page 04h: Address 00h)

Table 105: Global ARL Configuration Register (Page 04h: Address 00h)

4 Reserved – Reserved 0
3 Reserved RO Reserved 0
2 AGE_Accelerate R/W When enabled, the aging time is reduced by 1/128. 0
l
1 = Accelerate the aging 128 times
tia
0 = Keep the original age process
1 Reserved RO – 1
en
0 Hash Disable R/W Hash function disable 0
Disables the hash function of the ARL table so that
fid
entries are directly mapped to the table instead of
being hashed to an index.
on
1 = Disable hash function
0 = Enable hash function
For more information see “Address Table
C
Organization” on page 58.

om
BPDU Multicast Address Register (Page 04h: Address 04h)

dc
Table 106: BPDU Multicast Address Register (Page 04h: Address 04h–09h)

oa
47:0 BPDU_MC_ADDR R/W BPDU multicast address 1 01-80-c2-

Defaults to the IEEE 802.1 defined reserved 00-00-00
Br
multicast address for the bridge group address.

Programming to an alternate value allows support
of proprietary protocols in place of the normal
spanning tree protocol. Frames with a matching DA
to this address are forwarded to the designated
management port.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 180
Multiport Control Register (Page 04h: Address 0Eh–0Fh)

Table 107: Multiport Control Register (Page 04h: Address 0Eh–0Fh)

15 MPORT0_TS-EN R/W Mport 0 Time Sync Enable 0
1: Packet will be time-stamped if forwarded to CPU.
MPORT_VECTOR0 should be programmed to CPU
only if this bit is set.
0: Packet will not be time-stamped
11:10 MPORT_CTRL5 R/W Multiport 5 Control 00
00: Disable Multiport 5 Forward.
10: Compare MPORT_ADD5 only; Forward based
on MPORT_Vector 5 if matched.
l
tia
01: Compare MPORT_ETYPE5 only; Forward
based on MPORT_Vector 5 if matched.
11: Compare MPORT_ETYPE5 and
en
MPORT_ADD5; Forward based on MPORT_Vector
5 if matched.
9:8 MPORT_CTRL4 R/W
fid
Multiport 4 Control
00
on
C

om

4 if matched.
dc

oa
Br

3 if matched.
2 if matched.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 181
Table 107: Multiport Control Register (Page 04h: Address 0Eh–0Fh) (Cont.)

1 if matched.
l
tia
en
0 if matched.
fid
Multiport Address N (N=0–5) Register (Page 04h: Address 10h)
on
.
Table 108: Multiport Address Register Address Summary
C
Address Description
om
10h–17h Multiport ETYPE Address 0

dc

oa

Br
Table 109: Multiport Address Register (Page 04h: Address 10h–17h, 20h–27h, 30h–37h, 40h–47h, 50h–
57h, 60h–67h)

64:48 MPORT_ETYPE R/W Multiport Ethernet Type 0000
Allows a frames with a matching MPORT_ETYPE to this
Length Type field to be forwarded to any programmable
group of ports on the chip, as defined in the bit map in the
Multiport Vector Register.
Must be enabled using the MPORT_CTRL bit in the
Multiport Control Register.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 182
Table 109: Multiport Address Register (Page 04h: Address 10h–17h, 20h–27h, 30h–37h, 40h–47h, 50h–
57h, 60h–67h) (Cont.)

47:0 MPORT_ADDR R/W Multiport Address 0000000
Allows a frames with a matching DA to this address to be 00000
forwarded to any programmable group of ports on the chip,
as defined in the bit map in the Multiport Vector Register.
Must be enabled using the MPORT_CTRL bit in the
Multiport Control Register.
Multiport Vector N (N = 0–5) Register (Page 04h: Address 18h)

.
Table 110: Multiport Vector Register Address Summary
Address Description
l
tia
18h–1Bh Multiport Vector 0
en
58h–5Bh
68h–6Bh
fid
Multiport Vector 4
Multiport Vector 5
on
C
Table 111: Multiport Vector Register (Page 04h: Address 18h–1Bh, 28h–2Bh, 38h–3Bh, 48h–4Bh, 58h–
5Bh, 68h–6Bh)
om

dc
8:0 MPORT_VCTR_N R/W Multiport Vector 0

A bit mask corresponding to the physical ports on
oa
the chip.
A frame with a DA matching the content of the
Multiport Address Register will be forwarded to
Br
each port with a bit set in the Multiport Vector bit

map.
Bits[7:0] correspond to ports[7:0]
Bit 8: Management Port (MII Management)
Broadcom®
April 6, 2016 • 53128-DS07-R Page 183
BCM53128 Data Sheet Page 05h: ARL/VTBL Access Registers
Page 05h: ARL/VTBL Access Registers

Table 112: ARL/VTBL Access Registers (Page 05h)

00h 8 “ARL Table Read/Write Control Register (Page 05h: Address 00h)” on
page 185
02h–07h 48 “MAC Address Index Register (Page 05h: Address 02h)” on page 185
08h–09h 16 “VLAN ID Index Register (Page 05h: Address 08h)” on page 186
10h–17h 64 “ARL Table MAC/VID Entry N (N=0-3) Register (Page 05h: Address 10h)” on
page 186
18h–1Bh 16 “ARL Table Data Entry N (N = 0–3) Register (Page 05h: Address 18h)” on
l
tia
page 187
en
20h-27h 64 “ARL Table MAC/VID Entry N (N=0-3) Register (Page 05h: Address 10h)” on
page 186
fid
28h-2Bh 32 “ARL Table Data Entry N (N = 0–3) Register (Page 05h: Address 18h)” on
page 187
2Ch-2Fh – Reserved
on
page 186
C
page 187
om
page 186
dc
page 187
oa
50h 8 “ARL Table Search Control Register (Page 05h: Address 50h)” on page 188
Br
51h–52h 16 ARL Search Address

60h–77h 64 “ARL Table Search MAC/VID Result N (N=0-1) Register (Page 05h: Address
60h)” on page 189
68h–7Bh 32 “ARL Table Search Data Result N (N = 0-1) Register (Page 05h: Address 68h)”
on page 190
80h 8 “VLAN Table Read/Write/Clear Control Register (Page 05h: Address 80h)” on
page 191
81h–82h 16 “VLAN Table Address Index Register (Page 05h: Address 81h)” on page 192
83h–86h 32 “VLAN Table Entry Register (Page 05h: Address 83h–86h)” on page 192
Broadcom®
April 6, 2016 • 53128-DS07-R Page 184
Table 112: ARL/VTBL Access Registers (Page 05h) (Cont.)

ARL Table Read/Write Control Register (Page 05h: Address 00h)

Table 113: ARL Table Read/Write Control Register (Page 05h: Address 00h)

7 START/DONE R/W Start/done command 0
(SC) Write as 1 to initiate a read/write command to the
ARL table. The bit returns to 0 to indicate that a read/
l
tia
write operation is complete.
en
0 ARL_R/W R/W ARL table read/write bit 0
Specifies whether the ARL command is a read or
write operation.
1 = Read
0 = Write
fid
on
For more information, see “Accessing the ARL Table Entries” on page 63.
C
om
MAC Address Index Register (Page 05h: Address 02h)

Table 114: MAC Address Index Register (Page 05h: Address 02h–07h)
dc

oa
47:0 MAC_ADDR_INDX R/W MAC address index 0

The ARL table read/write command uses this 48-bit
address to index the ARL table. When IEEE 802.1Q
Br
is enabled, the ARL table is indexed by a combined

hash of the MAC_ADDR_INDX and the
VID_TBL_INDX, defined in the “VLAN ID Index
Register (Page 05h: Address 08h)” on page 186.
For more information, see “Accessing the ARL Table
Entries” on page 63.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 185
VLAN ID Index Register (Page 05h: Address 08h)

Table 115: VLAN ID Index Register (Page 05h: Address 08h–09h)

11:0 VID_INDX R/W VLAN ID index 0
When IEEE 802.1Q is enabled, the VLAN ID Index
is used with the MAC_ADDR_INDX, defined in the
“MAC Address Index Register (Page 05h: Address
02h)” on page 185, to form the hash index for
which status is to be read or written.
For more information, see “Accessing the ARL
Table Entries” on page 63.
l
ARL Table MAC/VID Entry N (N=0-3) Register (Page 05h: Address
tia
10h)
en
.
Table 116: ARL Table MAC/VID Entry N (N=0-3) Register Address Summary
Address
10h–17h fid
Description
ARL Table MAC/VID Entry 0
on
20h–27h ARL Table MAC/VID Entry 1
C

om
Table 117: ARL Table MAC/VID Entry N (N=0-3) Register (Page 05h: Address 10h–17h, 20h–27h, 30h–
37h, 40h–47h)
dc

oa

59:48 VID_N R/W VID entry N 0
Br
The VID field is either read from or written to the

ARL table entry N.
The VID is a “don’t-care” field when IEEE 802.1Q
is disabled.
47:0 MACADDR_N R/W MAC address entry N 0
The 48-bit MAC Address field to be either read
from or written to the ARL table entry N.
Note: Together, the “ARL Table MAC/VID Entry N (N=0-3) Register (Page 05h: Address 10h)” on
page 186 and the “ARL Table Data Entry N (N = 0–3) Register (Page 05h: Address 18h)” on page 187
compose a complete entry in the ARL table. For more information, see “Accessing the ARL Table Entries”
on page 63.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 186
ARL Table Data Entry N (N = 0–3) Register (Page 05h: Address 18h)
.
Table 118: ARL Table Data Entry N (N=0-3) Register Address Summary
Address Description
18h–1Bh ARL Table Data Entry 0
Table 119: ARL Table Data Entry N (N=0-3) Register (Page 05h: Address 18h–1Bh, 28h–2Bh, 38h–3Bh,
48h–4Bh)
l
tia
16 VALID_N R/W Valid bit entry N 0
en
Write this bit to 1 to indicate that a valid MAC
address is stored in the MACADDR_N field
defined in the “ARL Table MAC/VID Entry N
fid
(N=0-3) Register (Page 05h: Address 10h)” on
page 186, and that the entry has not aged out.
Reset when an entry is empty.
on
This information is read from or written to the
ARL table during a read/write command.
C
15 STATIC_N RW Static bit entry N 0

Write this bit to 1 to indicate that the entry is
om
controlled by the external register control. When

cleared, the internal learning and aging process
controls the validity of the entry.
dc

14 AGE_N R/W Age bit entry N 0
oa
Write this bit to 1 to indicate that an address entry

has been learned or accessed. This bit is set to
Br
0 by the internal aging algorithm. If the internal

aging process detects that a valid entry has
remained unused for the period set by the
AGE_TIME (defined in the “Aging Time Control
Register (Page 02h: Address 06h)” on page 170)
and the entry has not been marked as static, the
entry has the valid bit cleared.
The age bit is ignored if the entry has been
marked as Static.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 187
Table 119: ARL Table Data Entry N (N=0-3) Register (Page 05h: Address 18h–1Bh, 28h–2Bh, 38h–3Bh,
48h–4Bh) (Cont.)

13:11 TC_N R/W TC bit for MAC-based QoS entry N 0
These bits define the TC field for MAC-based
QoS packets.
8:0 FWD_PRT_MAP_N R/W Multicast Group Forward portmap entry N 0
For multicast entries, these bits define the
forward port map.
Bit 8: CPU port/MII port
l
PORTID_N Unicast Forward PortID entry N 0
tia
For unicast entries, these bits define the port
number associated with the entry of the ARL
en
table.
Bits [8:4]: Reserved
fid
Bits [3:0]: Port ID/Port Number which identifies
where the station with unique MACADDR_N is
connected.
on
ARL Table Search Control Register (Page 05h: Address 50h)
C
Table 120: ARL Table Search Control Register (Page 05h: Address 50h)
om

7 START/DONE R/W Start/done 0
dc
(SC) Write as 1 to initiate a sequential search of the ARL table.

Each entry found by the search is returned to the “ARL Table
oa
Search Data Result N (N = 0-1) Register (Page 05h: Address

68h)” on page 190 and the “ARL Table Search MAC/VID
Result N (N=0-1) Register (Page 05h: Address 60h)” on
Br
page 189. Reading the “ARL Table Search Data Result N (N =

0-1) Register (Page 05h: Address 68h)” on page 190 allows
the ARL table search to continue.
BCM53128 clears this bit when the ARL table search is
complete.
0 ARL_SR_VALID RC ARL search result valid 0
Set by BCM53128 to indicate that an ARL entry is found by the
ARL table search. The found entry is available in the “ARL
Table Search Data Result N (N = 0-1) Register (Page 05h:
Address 68h)” on page 190.
This bit automatically returns to 0 after the ARL Search Result
register is read.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 188
ARL Search Address Register (Page 05h: Address 51h)

Table 121: ARL Search Address Register (Page 05h: Address 51h–52h)

15 ARL_ADDR_VALI RO ARL address valid 0
D Indicates the lower 15 bits of this register contain a valid
internal representation of the ARL entry that is currently
being accessed. Intended for factory test/diagnostic use
only.
14:0 ARL_ADDR RO ARL address 0
14-bit internal representation of the address of the ARL
entry currently being accessed by the ARL search routine.
l
This is not a direct address of the ARL location and is
tia
intended for factory test/diagnostic use only.
en
ARL Table Search MAC/VID Result N (N=0-1) Register (Page 05h:
Address 60h)
. fid
Table 122: ARL Table Search MAC/VID Result N (N=0-1) Register Address Summary
on
Address Description
C
60h–67h ARL Table Search MAC/VID Result 0

70h–77h ARL Table Search MAC/VID Result 1
om
Table 123: ARL Table Search MAC/VID Result N (N=0-1) Register (Page 05h: Address 60h–67h, 70h–77h)
dc

oa

59:48 ARL_SR_VID_N RO ARL search VID result 0
Br
These bits store the VID of the ARL table entry

found by the ARL table search function.
47:0 ARL_SR_MAC_N RO ARL search MAC address result. 0
These bits store the MAC address of the ARL
table entry found by the ARL table search
function.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 189
ARL Table Search Data Result N (N = 0-1) Register (Page 05h:

Address 68h)
Table 124: ARL Table Search Data Result N (N=0-1) Register Address Summary
Address Description
68h–6Bh ARL Table Search Data Result 0
78h–7Bh ARL Table Search Data Result 1
Table 125: ARL Table Search Data Result N (N=0-1) Register (Page 05h: Address 68h–6Bh, 78h–7Bh)

16 ARL_SR_VALID_N RO ARL search valid bit result. 0
l
tia
This bit stores the valid bit of the ARL table entry
found by the ARL table search function. Reading
this register clears the data from the register and
en
allows the ARL table search function to continue
searching.
15 ARL_SR_STATIC_N RO
fid
ARL search static bit result.
This bit stores the static bit of the ARL table entry
0
on
C
searching.
14 ARL_SR_AGE_N RO ARL search age bit result. 0
om
This bit stores the Age bit of the ARL table entry
dc
searching.
13:11 ARL_SR_TC_N RO ARL search TC bits result. 0
oa
These bits store the TC bits of the ARL table

entry found by the ARL table search function.
Br
Reading this register clears the data from the

register and allows the ARL table search function
to continue searching.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 190
Table 125: ARL Table Search Data Result N (N=0-1) Register (Page 05h: Address 68h–6Bh, 78h–7Bh)

8:0 FWD_PRT_MAP_N R/W Multicast Group Forward portmap entry N 0
For multicast entries, these bits define the
forward port map.
Bit 8: CPU port/MII port
PORTID_N Unicast Forward PortID entry N 0
For unicast entries, these bits define the port
number associated with the entry of the ARL
table.
Bits [8:4]: Reserved
Bits [3:0]: Port ID/Port Number which identifies
where the station with unique MACADDR_N is
connected.
l
tia
en
VLAN Table Read/Write/Clear Control Register (Page 05h: Address
80h) fid
on
Table 126: VLAN Table Read/Write/Clear Control Register (Page 05h: Address 80h)
C

7 START/DONE R/W Start/done command 0
om
(SC) Write as 1 to initiate a read or write or clear-table

command to the VLAN table. The bit returns to 0 to
indicate that the read or write or clear-table operation is
dc
complete.
oa
1:0 VTBL_R/W/Clr R/W Read/Write/Clear-table 0

Specifies whether the current VLAN table read/write/
clear-table
Br
command is a read or write or clear-table operation.

11 = Reserved
10 = Clear-table
01 = Read
00 = Write
See “Programming the VLAN Table” on page 40 for more information.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 191
VLAN Table Address Index Register (Page 05h: Address 81h)

Table 127: VLAN Table Address Index Register (Page 05h: Address 81h–82h)

11:0 VTBL_ADDR_INDX R/W VLAN table address index 0
The current VLAN table read/write uses this 12-bit
address to index the VLAN table.
VLAN Table Entry Register (Page 05h: Address 83h–86h)
l
tia
Table 128: VLAN Table Entry Register (Page 05h: Address 83h–86h)
en
21 FWD_MODE R/W This indicates whether the packet forwarding 0
fid
should be based on VLAN membership or based
on ARL flow.
on
1: Based on VLAN membership (excluding
Ingress port)
C
0: Based on ARL flow.

Note that the VLAN membership based
forwarding mode is only used for certain ISP
om
Tagged packets received from ISP port when

BCM53128 is operating in Double Tag Mode.
20:18 MSPT_INDEX R/W Index for 8 Spanning Trees 0
dc
17:9 UNTAG_MAP R/W Untagged Port Map 0

Bit 17: CPU Port/ MII Port
oa

Ports written to 1 are designated as untagged
Br
VLAN ports.
VLAN-tagged frames destined for these ports
are untagged before they are forwarded.
When the IEEE 802.1Q feature is enabled,
frames sent via the CPU (MII port configured as
a management port) are tagged.
Note that the packet forwarded to IMP port
should always be VLAN tagged.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 192
Table 128: VLAN Table Entry Register (Page 05h: Address 83h–86h) (Cont.)

8:0 FWD_MAP R/W Forward Port Map 0
The VLAN-tagged Frame is allowed to be
forwarded to the destination ports corresponding
bits set in the Map Ports written to 1 are
designated as capable of receiving VLAN-tagged
frames.
Bit 8: CPU Port/ MII Port
Bits [7:0] correspond to Ports [7:0], respectively.
l
tia
en
fid
on
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 193
BCM53128 Data Sheet Page 10h–17h: Internal GPHY MII Registers
Page 10h–17h: Internal GPHY MII Registers

Table 129: 10/100/1000 PHY Page Summary
Page Description
10h Port 0 Internal PHY MII Registers
l
tia
Table 130: Register Map (Page 10h–17h)
en
SPI Offset MII Number
Address Address of Bits Register Table
10BASE-T/100BASE-TX/1000BASE-T Registers fid
on
00h 00h 16 Table 131: “MII Control Register (Page 10h–17h: Address 00h–01h),” on
page 196
02h 01h 16 Table 132: “MII Status Register (Page 10h–17h: Address 02h–03h),” on
C
page 197
04h–06h 02h 32 Table 133: “PHY Identifier Register MSB (Page 10h–17h: Address 04–07h),”
om
on page 198
08h 04h 16 Table 135: “Auto-Negotiation Advertisement Register (Page 10h–17h:
Address 08h–09h),” on page 199
dc
0Ah 05h 16 Table 136: “Auto-Negotiation Link Partner Ability Register (Page 10h–17h:
Address 0Ah–0Bh),” on page 200
oa
0Ch 06h 16 Table 136: “Auto-Negotiation Link Partner Ability Register (Page 10h–17h:
Address 0Ah–0Bh),” on page 200
Br
0Eh 07h 16 Table 138: “Next Page Transmit Register (Page 10h–17h: Address 0Eh–0Fh),”
on page 202
10h 08h 16 Table 139: “Link Partner Received Next Page Register (Page 10h–17h:
Address 10h–11h),” on page 203
12h 09h 16 Table 140: “1000BASE-T Control Register (Page 10h–17h: Address 12h–
13h),” on page 204
14h 0Ah 16 Table 141: “1000BASE-T Status Register (Page 10h–17h: Address 14h–15h),”
on page 205
16h–1Dh – 16 Reserved (Do not read from or write to a reserved register.)
1Eh 0Fh 16 Table 142: “IEEE Extended Status Register (Page 10h–17h: Address 1Eh–
1Fh),” on page 206
20h 10h 16 Table 143: “PHY Extended Control Register (Page 10h–17h: Address 20h–
21h),” on page 207
Broadcom®
April 6, 2016 • 53128-DS07-R Page 194
Table 130: Register Map (Page 10h–17h) (Cont.)

22h 11h 16 Table 144: “PHY Extended Status Register (Page 10h–17h: Address 22h–
23h),” on page 208
24h 12h 16 Table 145: “Receive Error Counter Register (Page 10h–17h: Address 24h–
25h),” on page 209
26h 13h 16 Table 146: “False Carrier Sense Counter Register (Page 10h–17h: Address
26h–27h),” on page 209
28h 14h 16 Table 148: “Receiver NOT_OK Counter Register (Page 10h–17h: Address
28h–29h),” on page 210
2Ah–2Ch 15h–16h Reserved (Do not read from or write to a reserved register except for accessing
the Expansion registers through register 15h.)
2Eh 17h 16 Table 150: “Expansion Register Access Register (Page 10h–17h: Address
2Eh–2Fh),” on page 211
l
tia
30h 18h 16 Table 155: “Auxiliary Control Register (Page 10h–17h: Address 30h, Shadow
Value 000),” on page 213
en
Table 156: “10BASE-T Register (Page 10h–17h: Address 30h, Shadow Value
001),” on page 214
Table 157: “Power/MII Control Register (Page 10h–17h: Address 30h, Shadow
fid
Table 158: “Miscellaneous Test Register (Page 10h–17h: Address 30h,
on
Shadow Value 100),” on page 216
Table 159: “Miscellaneous Control Register (Page 10h–17h: Address 30h,
Shadow Value 111),” on page 217
C
32h 19h 16 Table 160: “Auxiliary Status Summary Register (Page 10h–17h: Address 32h–
33h),” on page 218
om
34h 1Ah 16 Table 161: “Interrupt Status Register (Page 10h–17h: Address 34h–35h),” on
page 219
36h 1Bh 16 Table 162: “Interrupt Mask Register (Page 10h–17h: Address 36h),” on
dc
page 220
38h 1Ch 16 Table 164: “Spare Control 2 Register (Page 10h–17h: Address 38h, Shadow
oa

Table 164: “Spare Control 2 Register (Page 10h–17h: Address 38h, Shadow
Br

Table 165: “Auto Power-Down Register (Page 10h–17h: Address 38h, Shadow
Table 167: “Mode Control Register (Page 10h–17h: Address 38h, Shadow
3Ah 1Dh 16 Table 168: “Master/Slave Seed Register (Page 10h–17h: Address 3Ah–3Bh)
Bit 15 = 0,” on page 226
Table 169: “HCD Status Register (Page 10h–17h: Address 3Ah–3Bh) Bit 15 =
1,” on page 227
3Ch 1Eh 16 Table 170: “Test Register 1 (Page 10h–17h: Address 3C–3Dh),” on page 228
3Eh 1Fh 16 Reserved (Do not read from or write to a reserved register.)
Broadcom®
April 6, 2016 • 53128-DS07-R Page 195
Table 130: Register Map (Page 10h–17h) (Cont.)

Expansion Registers: Read/Write through Register 2Ah (Accessed by Writing to Register 2Eh, Bits
[11:0] = 1111 + Expansion Register Number)
00h – – Table 171: “Expansion Register 00h: Receive/Transmit Packet Counter,” on
page 229
01h – – Table 172: “Expansion Register 01h: Expansion Interrupt Status,” on page 229
04h – – –
05h – – –
07h – – –
45h – – Table 173: “Expansion Register 45h: Transmit CRC,” on page 230
l
MII Control Register (Page 10h–17h: Address 00h–01h)
tia
Table 131: MII Control Register (Page 10h–17h: Address 00h–01h)
en
15 Reset R/W
SC fid
1 = PHY reset
0 = Normal operation
0
on
14 Internal Loopback R/W 1 = Loopback mode 0
C
13 Speed Selection (LSB) R/W Bits [6,13]: 0

11 = Reserved
om
10 = 1000 Mbps
01 = 100 Mbps
00 = 10 Mbps
dc
12 Auto-negotiation Enable R/W 1 = Auto-negotiation is enabled. 1

0 = Auto-negotiation is disabled.
oa
11 Power Down R/W 1 = Power-down 0

Br
10 Isolate R/W 1 = Electrically isolate PHY from GMII. 0

9 Restart Auto-negotiation R/W 1 = Restarting auto-negotiation 0
SC 0 = Auto-negotiation restart is complete.
8 Duplex Mode R/W 1 = Full-duplex 1
0 = Half-duplex
7 Collision Test Enable R/W 1 = Enable the collision test mode. 0
0 = Disable the collision test mode.
6 Speed Selection (MSB) R/W Works in conjunction with bit 13 1
5 Reserved R/W Write as 0, ignore on read. 0
4 Reserved R/W Write as 0 ignore on read 0
Broadcom®
April 6, 2016 • 53128-DS07-R Page 196
Table 131: MII Control Register (Page 10h–17h: Address 00h–01h) (Cont.)

MII Status Register (Page 10h–17h: Address 02h)

Table 132: MII Status Register (Page 10h–17h: Address 02h–03h)

15 100BASE-T4 Capable RO 1 = 100BASE-T4 capable 0
L 0 = Not 100BASE-T4 capable
l
14 100BASE-X Full-Duplex RO 1 = 100BASE-X full-duplex capable 1
tia
Capable H 0 = Not 100BASE-X full-duplex capable
13 100BASE-X Half-Duplex RO 1 = 100BASE-X half-duplex capable 1
en
Capable H 0 = Not 100BASE-X half-duplex capable
12 10BASE-T Full-Duplex RO 1 = 10BASE-T full-duplex capable 1
11
Capable
10BASE-T Half-Duplex
H
RO fid
0 = Not 10BASE-T full-duplex capable
1 = 10BASE-T half-duplex capable 1
on
Capable H 0 = Not 10BASE-T half-duplex capable
10 100BASE-T2 Full-Duplex RO 1 = 100BASE-T2 full-duplex capable 0
C
Capable L 0 = Not 100BASE-T2 full-duplex capable

9 100BASE-T2 Half-Duplex RO 1 = 100BASE-T2 half-duplex capable 0
om
Capable L 0 = Not 100BASE-T2 half-duplex capable

8 Extended Status RO 1 = Extended status information in reg 0Fh 1
H 0 = No extended status information in reg 0Fh
dc
7 Reserved RO Ignore on read. 0

oa
6 Management Frames RO 1 = Preamble can be suppressed. 1

Preamble Suppression H 0 = Preamble always required
5 Auto-negotiation Complete RO 1 = Auto-negotiation is complete. 0
Br
0 = Auto-negotiation is in progress.
4 Remote Fault RO 1 = Remote fault detected. 0
LH 0 = No remote fault detected.
3 Auto-negotiation Ability RO 1 = Auto-negotiation capable 1
H 0 = Not auto-negotiation capable
2 Link Status RO 1 = Link is up (link pass state). 0
LL 0 = Link is down (link fail state).
1 Jabber Detect RO 1 = Jabber condition detected. 0
LH 0 = No jabber condition detected.
0 Extended Capability RO 1 = Extended register capabilities 1
H 0 = No extended register capabilities
Broadcom®
April 6, 2016 • 53128-DS07-R Page 197
PHY Identifier Register (Page 10h–17h: Address 04h)

Table 133: PHY Identifier Register MSB (Page 10h–17h: Address 04–07h)

15:0 OUI RO Bits 3:18 of organizationally unique identifier 0362
Table 134: PHY Identifier Register LSB (Page 10h–17h: Address 06h–07h)

15:10 OUI RO Bits 19:24 of organizationally unique 010111
identifier
9:4 MODEL RO Device model number 100001
3:0 REVISION RO Device revision number na (hex)
l
tia
a. The revision number (n) changes with each silicon revision.
en
The IEEE has issued an Organizationally Unique Identifier (OUI) to Broadcom Corporation. This 24-bit number
allows devices developed by Broadcom to be distinguished from all other manufacturers. The OUI combined
fid
with model numbers and revision numbers assigned by Broadcom precisely identifies a device manufactured
by Broadcom.
on
The [15:0] bits of MII register 02h (PHYID HIGH) contain OUI bits [3:18]. The [15:0] bits of MII register 03h
(PHYID LOW) contain the most significant OUI bits [19:24], six manufacturer’s model number bits, and four
C
revision number bits. The two

least significant OUI binary bits are not used.
om
Broadcom Corporation's OUI is 00-1B-E9, expressed as hexadecimal values. The binary OUI is 0000-0000-
0001-1011-1110-1001. The model number for the BCM53128 is 21H. Revision numbers start with 0h and
increment by 1 for each chip modification.
dc
• PHYID HIGH[15:0] = OUI[3:18]

oa
• PHYID LOW[15:0] = OUI[19:24] + Model[5:0] + Revision [3:0]

Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 198
Auto-Negotiation Advertisement Register (Page 10h–17h: Address

08h)
Table 135: Auto-Negotiation Advertisement Register (Page 10h–17h: Address 08h–09h)

15 Next Page R/W 1 = Next page ability is supported. 0
0 = Next page ability is not supported.
13 Remote Fault R/W 1 = Advertise remote fault is detected. 0
0 = Advertise no remote fault is detected.
12 Reserved Technology R/W Write as 0, ignore on read. 0
11 Asymmetric Pause R/W 1 = Advertise asymmetric pause 1
0 = Advertise no asymmetric pause
l
10 Pause Capable R/W 1 = Capable of full-duplex pause operation 1
tia
0 = Not capable of pause operation
9 100BASE-T4 Capable R/W 1 = 100BASE-T4 capable 0
en
0 = Not 100BASE-T4 capable
8 100BASE-TX Full- R/W 1 = 100BASE-TX full-duplex capable 1
7
Duplex Capable
100BASE-TX Half- R/W
fid
0 = Not 100BASE-TX full-duplex capable
1 = 100BASE-TX half-duplex capable 1
on
Duplex Capable 0 = Not 100BASE-TX half-duplex capable
6 10BASE-T Full-Duplex R/W 1 = 10BASE-T full-duplex capable 1
C
Capable 0 = Not 10BASE-T full-duplex capable

5 10BASE-T Half-Duplex R/W 1 = 10BASE-T half-duplex capable 1
om
Capable 0 = Not 10BASE-T half-duplex capable

4 Protocol Selector Field R/W Bits [4:0] = 00001 indicates 0
IEEE 802.3 CSMA/CD
dc
3 R/W 0
oa
2 R/W 0
1 R/W 0
Br
0 R/W 1
Broadcom®
April 6, 2016 • 53128-DS07-R Page 199
Auto-Negotiation Link Partner Ability Register (Page 10h–17h:

Address 0Ah)
Table 136: Auto-Negotiation Link Partner Ability Register (Page 10h–17h: Address 0Ah–0Bh)

15 Next Page RO 1 = Link partner has next page ability. 0
0 = Link partner does not have next page ability.
14 Acknowledge RO 1 = Link partner has received link code word. 0
0 = Link partner has not received link code word.
13 Remote Fault RO 1 = Link partner has detected remote fault. 0
0 = Link partner has not detected remote fault.
12 Reserved Technology RO Write as 0, ignore on read. 0
11 Link Partner Asymmetric Pause RO 1 = Link partner wants asymmetric pause. 0
l
0 = Link partner does not want asymmetric pause.
tia
10 Pause Capable RO 1 = Link partner is capable of pause operation. 0
0 = Link partner is not capable of pause operation.
en
9 100BASE-T4 Capable RO 1 = Link partner is 100BASE-T4 capable. 0
0 = Link partner is not 100BASE-T4 capable.
8 100BASE-TX Full-Duplex
Capable
RO
fid
1 = Link partner is 100BASE-TX full-duplex capable. 0
0 = Link partner is not 100BASE-TX full-duplex
on
capable.
7 100BASE-TX Half-Duplex RO 1 = Link partner is 100BASE-TX half-duplex capable. 0
C
Capable 0 = Link partner not 100BASE-TX half-duplex

capable.
om
6 10BASE-T Full-Duplex Capable RO 1 = Link partner is 10BASE-T full-duplex capable. 0

0 = Link partner is not 10BASE-T full-duplex capable.
5 10BASE-T Half-Duplex Capable RO 1 = Link partner is 10BASE-T half-duplex capable. 0
dc
0 = Link partner is not 10BASE-T half-duplex

capable.
oa
4 Protocol Selector Field RO Link partner protocol selector field 0

3 RO 0
Br
2 RO 0
1 RO 0
0 RO 0
Note: As indicated by bit 5 of the 10BASE-T/100BASE-TX/1000BASE-T MII Status register, the values
contained in the 10BASE-T/100BASE-TX/1000BASE-T Auto-negotiation Link Partner Ability register are
only guaranteed to be valid after auto-negotiation has successfully completed.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 200
Next Page
BCM53128 returns a 1 in bit 15 when the link partner wants to transmit Next Page information.
Acknowledge
BCM53128 returns a 1 in bit 14 when the link partner has acknowledged reception of the link code word;
otherwise, BCM53128 returns a 0.
Auto-Negotiation Expansion Register (Page 10h–17h: Address 0Ch)

Table 137: Auto-Negotiation Expansion Register (Page 10h–17h: Address 0Ch–0Dh)

15 Reserved R0 Ignore on read. 0
l
tia
en
10
9
Reserved
Reserved
R0
R0 fid
Ignore on read.
Ignore on read.
0
0
on
C
6 Next Page Receive Location R/W 1 = Bit 5 in register 06h determines next page 1
Able receive location.
om
0 = Bit 5 in register 06h does not determine next

page receive location.
5 Next Page Receive Location R/W 1 = Next pages stored in register 08h. 1
dc
0 = Next pages stored in register 05h.

4 Parallel Detection Fault RO 1 = Parallel link fault is detected. 0
oa
LH 0 = Parallel link fault is not detected.

3 Link Partner Next Page Ability RO 1 = Link partner has next page capability. 0
Br
0 = Link partner does not have next page capability.

2 Next Page Capable RO 1 = BCM53128 is next page capable. 1
H 0 = BCM53128 is not next page capable.
1 Page Received RO 1 = New page has been received from link partner. 0
LH 0 = New page has not been received.
0 Link Partner Auto-negotiation RO 1 = Link partner has auto-negotiation capability. 0
Ability 0 = Link partner does not have auto-negotiation.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 201
Next Page Transmit Register (Page 10h–17h: Address 0Eh)

Table 138: Next Page Transmit Register (Page 10h–17h: Address 0Eh–0Fh)

15 Next Page R/W 1 = Additional next pages follow. 0
0 = Sending last next page.
13 Message Page R/W 1 = Formatted page 1
0 = Unformatted page
12 Acknowledge2 R/W 1 = Complies with message. 0
0 = Cannot comply with message.
Note: Not used with 1000BASE-T next
pages.
11 Toggle RO Toggles between exchanges of different next 0
l
tia
pages.
10 Message/Unformatted Code R/W Next page message code or unformatted 0
en
9 Field R/W data 0
8 R/W 0
7
6
R/W
R/W fid 0
0
on
5 R/W 0
4 R/W 0
C
3 R/W 0
2 R/W 0
om
1 R/W 0
0 R/W 1
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 202
Link Partner Received Next Page Register (Page 10h–17h: Address

10h)
Table 139: Link Partner Received Next Page Register (Page 10h–17h: Address 10h–11h)

15 Next Page RO 1 = Additional next pages follow. 0
0 = Sending last next page.
14 Acknowledge RO 1 = Acknowledge 0
0 = No acknowledge
13 Message Page RO 1 = Formatted page 0
0 = Unformatted page
12 Acknowledge2 RO 1 = Complies with message. 0
0 = Cannot comply with message.
l
Note: Not used with 1000BASE-T next pages.
tia
11 Toggle RO Toggles between exchanges of different next pages. 0
10 Message Code field RO Next page message code or unformatted data 0
en
9 RO 0
8 RO 0
7
6
RO
RO
fid 0
0
on
5 RO 0
4 RO 0
C
3 RO 0
om
2 RO 0
1 RO 0
0 RO 0
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 203
1000BASE-T Control Register (Page 10h–17h: Address 12h)

Table 140: 1000BASE-T Control Register (Page 10h–17h: Address 12h–13h)

15 Test Mode R/W 1 X X = Test mode 4—Transmitter distortion test. 0
14 R/W 0 1 1 = Test mode 3—Slave transmit jitter test. 0
13 R/W 0 1 0 = Test mode 2—Master transmit jitter test. 0
0 0 1 = Test mode 1—Transmit waveform test.
0 0 0 = Normal operation
12 Master/Slave R/W 1 = Enable master/slave manual configuration 0
Configuration Enable value.
0 = Automatic master/slave configuration
11 Master/Slave R/W 1 = Configure PHY as master. 1
Configuration Value 0 = Configure PHY as slave.
l
tia
10 Repeater/DTE R/W 1 = Repeater/switch device port 1
0 = DTE device
en
9 Advertise 1000BASE- R/W 1 = Advertise 1000BASE-T full-duplex capability. 1
T 0 = Advertise no 1000BASE-T full-duplex
Full-Duplex Capability capability.
8 Advertise 1000BASE- R/W
T
fid
1 = Advertise 1000BASE-T half-duplex
capability.
1
on
Half-Duplex Capability 0 = Advertise no 1000BASE-T half-duplex
capability.
C

om

dc

oa

Br
Test Mode
The BCM53128 can be placed in 1 of 4 transmit test modes by writing bits [15:13] of the 1000BASE-T Control
register. The transmit test modes are defined in IEEE 802.3ab. When read, these bits return the last value
written. For test modes 1, 2, and 4, the PHY must have auto-negotiation disabled and forced to 1000BASE-T
mode and Auto-MDIX disabled.
• Disable auto-negotiation and force to 1000BASE-T mode (write to register 00h = 0x0040)
• Disable Auto-MDIX (write to register 18h, shadow value 111, bit 9 = 0)
• Enter test modes (write to register 09h, bits [15:13] = the desired test mode)
Broadcom®
April 6, 2016 • 53128-DS07-R Page 204
Master/Slave Configuration Enable

When bit 12 is set = 1, the BCM53128 master/slave mode is configured using the manual master/slave
configuration value. When the bit is cleared, the master/slave mode is configured using the automatic resolution
function. This bit returns a 1 when manual master/slave configuration is enabled; otherwise, it returns a 0.
1000BASE-T Status Register (Page 10h–17h: Address 14h)

Table 141: 1000BASE-T Status Register (Page 10h–17h: Address 14h–15h)

15 Master/Slave Configuration Fault RO 1 = Master/slave configuration fault detected. 0
LH 0 = No master/slave configuration fault detected.
14 Master/Slave Configuration RO 1 = Local transmitter is master. 0
Resolution 0 = Local transmitter is slave.
l
tia
13 Local Receiver Status RO 1 = Local receiver is OK. 0
0 = Local receiver is not OK.
en
12 Remote Receiver Status RO 1 = Remote receiver is OK. 0
0 = Remote receiver is not OK.
11 Link Partner 1000BASE-T
Full-Duplex Capability
RO
fid
1 = Link partner is 1000BASE-T full-duplex
capable.
0
on
0 = Link partner is not 1000BASE-T full-duplex
capable.
10 Link Partner 1000BASE-T RO 1 = Link partner is 1000BASE-T half-duplex 0
C
Half-Duplex Capability capable.

0 = Link partner is not 1000BASE-T half-duplex
om
capable.
dc
7 Idle Error Count RO Number of idle errors since last read 0

CR
oa
6 RO 0
CR
Br
5 RO 0
CR
4 RO 0
CR
3 RO 0
CR
2 RO 0
CR
1 RO 0
CR
0 RO 0
CR
Broadcom®
April 6, 2016 • 53128-DS07-R Page 205
Note: As indicated by bit 5 of the MII Status register (0h), the values contained in bits 14, 11, and 10 of
the 1000BASE-T Status register are guaranteed to be valid only after auto-negotiation has successfully
completed.
IEEE Extended Status Register (Page 10h–17h: Address 1Eh)

Table 142: IEEE Extended Status Register (Page 10h–17h: Address 1Eh–1Fh)

15 1000BASE-X Full-Duplex RO 1 = 1000BASE-X full-duplex capable 0
Capable L 0 = Not 1000BASE-X full-duplex capable
14 1000BASE-X Half-Duplex RO 1 = 1000BASE-X half-duplex capable 0
Capable L 0 = Not 1000BASE-X half-duplex capable
l
13 1000BASE-T Full-Duplex RO 1 = 1000BASE-T full-duplex capable 1
tia
Capable H 0 = Not 1000BASE-T full-duplex capable
12 1000BASE-T Half-Duplex RO 1 = 1000BASE-T half-duplex capable 1
en
Capable H 0 = Not 1000BASE-T half-duplex capable
10
9
Reserved
Reserved
RO
RO
fid
Ignore on read.
Ignore on read.
0
0
on
C

om

dc

oa

Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 206
PHY Extended Control Register (Page 10h–17h: Address 20h)

Table 143: PHY Extended Control Register (Page 10h–17h: Address 20h–21h)

14 Disable Automatic MDI R/W 1 = Automatic MDI crossover is disabled. 0
Crossover 0 = Automatic MDI crossover is enabled.
13 Transmit Disable R/W 1 = Transmitter outputs are disabled. 0
12:11 Reserved – – –
10 Bypass 4B/5B Encoder/ R/W 1 = Transmit and receive 5B codes over MII 0
Decoder (100BASE-T) pins.
0 = Normal MII
9 Bypass Scrambler/Descrambler R/W 1 = Scrambler and descrambler are disabled. 0
l
tia
(100BASE-T) 0 = Scrambler and descrambler are enabled.
8 Bypass NRZI/MLT3 Encoder/ R/W 1 = Bypass NRZI/MLT3 encoder and decoder. 0
en
Decoder (100BASE-T) 0 = Normal operation
7 Bypass Receive Symbol R/W 1 = The 5B receive symbols are not aligned. 0
6
Alignment (100BASE-T)
Reset Scrambler (100BASE-T) R/W fid
0 = Receive symbols aligned to 5B boundaries
1 = Reset scrambler to initial state. 0
on
SC 0 = Normal scrambler operation
C

om
0 1000 Mbps PCS Transmit FIFO R/W 1 = High latency 0

Elasticity 0 = Low latency
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 207
PHY Extended Status Register (Page 10h–17h: Address 22h)

Table 144: PHY Extended Status Register (Page 10h–17h: Address 22h–23h)

15 Auto-negotiation Base Page RO 1 = Link partner base page selector field 0
Selector Field Mismatch LH mismatched advertised selector field since last
read.
0 = No mismatch detected since last read.
14 Ethernet@WireSpeed RO 1 = Auto-negotiation advertised speed downgraded 0
Downgrade 0 = No advertised speed downgrade
13 MDI Crossover State RO 1 = Crossover MDI mode 0
0 = Normal MDI mode
12 Interrupt Status RO 1 = Unmasked interrupt is currently active. 0
0 = Interrupt is cleared.
l
tia
11 Remote Receiver Status RO 1 = Remote receiver is OK. 0
LL 0 = Remote receiver is not OK since last read
en
10 Local Receiver Status RO 1 = Local receiver is OK. 0
LL 0 = Local receiver is not OK since last read.
9 Locked RO
fid
1 = Descrambler is locked.
0 = Descrambler is unlocked.
0
on
8 Link Status RO 1 = Link pass 0
0 = Link fail
C
7 CRC Error Detected RO 1 = CRC error detected. 0

LH 0 = No CRC error since last read.
om
6 Carrier Extension Error RO 1 = Carrier extension error detected since last read. 0
Detected LH 0 = No carrier extension error since last read.
5 Bad SSD Detected RO 1 = Bad SSD error detected since last read. 0
dc
(False Carrier) LH 0 = No bad SSD error since last read.

4 Bad ESD Detected RO 1 = Bad ESD error detected since last read. 0
oa
(Premature End) LH 0 = No bad ESD error since last read.

3 Receive Error Detected RO 1 = Receive error detected since last read. 0
Br
LH 0 = No receive error since last read.

2 Transmit Error Detected RO 1 = Transmit error code received since last read. 0
LH 0 = No transmit error code received since last read.
1 Lock Error Detected RO 1 = Lock error detected since last read. 0
LH 0 = No lock error since last read.
0 MLT3 Code Error Detected RO 1 = MLT3 code error detected since last read. 0
LH 0 = No MLT3 code error since last read.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 208
Receive Error Counter Register (Page 10h–17h: Address 24h)

Table 145: Receive Error Counter Register (Page 10h–17h: Address 24h–25h)a

15:0 Receive Error Counter R/W The number of noncollision packets with receive 0000h
CR errors since last read
a. Bits 15:0 of this register become the 10BASE-T, 100BASE-TX, 1000BASE-T Receive Error Counter when
register 38h, shadow value11011, bit 9 = 0.
Copper Receive Error Counter

When bit 9 = 0 in register 38h, shadow value 11011, this counter increments each time BCM53128 receives a
10BASE-T, 100BASE-TX, 1000BASE-T noncollision packet containing at least one receive error. This counter
freezes at the maximum value of FFFFh. The counter automatically clears when read.
l
tia
False Carrier Sense Counter Register (Page 10h–17h: Address 26h)
en
Table 146: False Carrier Sense Counter Register (Page 10h–17h: Address 26h–27h)a
Bit
15:8
Name
Reserved RO
R/W
fid
Description
Ignore on read.
Default
00h
on
7:0 False Carrier Sense Counter R/W The number of false carrier sense events since last 00h
CR read.
C
a. Bits 7:0 of this register become the 10BASE-T/100BASE-TX/1000BASE-T Carrier Sense Counter when
register 38h, shadow 11011, bit 9 = 0 and register 3Ch, bit 14 = 0.
om
Copper False Carrier Sense Counter

dc
When bit 9 = 0 in register 1Ch, shadow value 11011 and bit 14 = 0 in register 3Ch, the False Carrier Sense
Counter increments each time the BCM53128 detects a 10BASE-T, 100BASE-TX, 1000BASE-T false carrier
oa
sense on the receive input. This counter freezes at the maximum value of FFh. The counter automatically clears
when read.
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 209
10BASE-T/100BASE-TX/1000BASE-T Packets Received with

Transmit Error Codes Counter
Table 147: 10BASE-T/100BASE-TX/1000BASE-T Transmit Error Code Counter Register (Address 13h)a

15:8 Reserved RO Write as 0, ignore on read. 00h
7:0 Transmit Error Code Counter R/W The number of packets received with transmit error 00h
CR codes since last read.
a. Bits 7:0 of this register become the 10BASE-T/100BASE-TX/1000BASE-T packets received with transmit
error codes counter when register 38h, shadow 11011, bit 9 = 0 and register 3Ch, bit 14 = 1.
Packets Received with Transmit Error Codes Counter

The BCM53128 detects a 10BASE-T/100BASE-TX/1000BASE-T packet with a transmit error code violation
l
tia
when bit 9 = 0 in register 38h, shadow value 11011, and when bit 14 = 1 in register 1Eh, Packets Received with
Transmit Error Codes Counter increments each time. This counter freezes at the maximum value of FFh. The
en
counter automatically clears when read.
Receiver NOT_OK Counter Register (Page 10h–17h: Address 28h)

fid
on
Table 148: Receiver NOT_OK Counter Register (Page 10h–17h: Address 28h–29h)a

C
15:8 Local Receiver NOT_OK R/W The number of times local receiver was NOT_OK 00h
Counter CR since last read.
om
7:0 Remote Receiver NOT_OK R/W The number of times BCM53128 detected that the 00h
Counter CR remote receiver was NOT_OK since last read.
dc
a. Bits 15:0 of this register become the 10BASE-T, 100BASE-TX, or 1000BASE-T Receiver NOT_OK Counter
when register 38h, shadow 11011, bit 9 = 0 and register 3Ch bit 15 = 0.
oa
Copper Local Receiver NOT_OK Counter

Br
When bit 9 = 0 in register 38h, shadow value 11011 and bit 15 = 0 in register 3Ch, this counter increments each
time the 10BASE-T, 100BASE-TX, or 1000BASE-T local receiver enters the NOT_OK state. This counter
freezes at the maximum value of FFh. The counter automatically clears when read.
Copper Remote Receiver NOT_OK Counter

time the 1000BASE-T, 100BASE-TX, or 10BASE-T remote receiver enters the NOT_OK state. This counter
freezes at the maximum value of FFh. The counter automatically clears when read.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 210
Receive CRC Counter Register (Page 10h–17h: Address 28h)

Table 149: CRC Counter Register (Page 10h–17h: Address 28h–29h)a

15:0 Receive CRC Counter R/W The number of times receive CRC errors were 00h
CR detected.
a. Bits 15:0 of this register become the 10BASE-T, 100BASE-TX, or 1000BASE-T Receive CRC Counter when
register 38h, shadow 11011, bit 9 = 0 and register 3Ch bit 15 = 1.
Copper CRC Counter

time the 10BASE-T, 100BASE-TX, or 1000BASE-T detects a receive CRC error. This counter freezes at the
maximum value of FFh. The counter automatically clears when read.
l
tia
Expansion Register Access Register (Page 10h–17h: Address 2Eh)
en
Table 150: Expansion Register Access Register (Page 10h–17h: Address 2Eh–2Fh)
Bit
15
Name
Reserved
R/W
R/W
fid
Description
Write as 0, ignore on read.
Default
0
on
C

om
11 Expansion Register Select R/W 1111 = Expansion register is selected. 0

10 R/W 0000 = Expansion register is not selected. 0
9 R/W 0
dc
8 R/W All others = Reserved (Do not use) 0

7 Expansion Register Accessed R/W Sets the expansion register number accessed 0
oa
6 R/W when read/write to register 2Ah. 0

5 R/W 0
Br
4 R/W 0
3 R/W 0
2 R/W 0
1 R/W 0
0 R/W 0
Expansion Register Select

Setting bits [11:8] to 1111 enables the reading from and writing to the Expansion registers in conjunction with
register 2Ah. These bits should be cleared after the Expansion registers are accessed or when the Expansion
registers are not being accessed. See “Expansion Registers” on page 229 for Expansion register detail.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 211
Expansion Register Accessed

The Expansion registers can be accessed through register 2Ah when bits [11:8] of this register are set to 1111.
The available expansion registers are listed in Table 151.
Table 151: Expansion Register Select Values
Expansion Register Register Name

00h “Expansion Register 01h: Expansion Interrupt Status”
Auxiliary Control Shadow Value Access Register (Page 10h–17h:

Address 30h)
Available 30h registers are listed in the Table 152.
l
Table 152: Auxiliary Control Shadow Values Access Register (Page 10h–17h: Address 30h)
tia
Shadow Value Register Name
en
000 ”Auxiliary Control Shadow Values Access Register (Page 10h–17h: Address 30h)” on page
212
001
010 fid
”10BASE-T Register (Page 10h–17h: Address 30h, Shadow Value 001)” on page 214
”Power/MII Control Register (Page 10h–17h: Address 30h, Shadow Value 010)” on page
on
215
100 ”Miscellaneous Test Register (Page 10h–17h: Address 30h, Shadow Value 100)” on page
216
C
111 ”Miscellaneous Control Register (Page 10h–17h: Address 30h, Shadow Value 111)” on
page 217
om
Read from register 30h, shadow value zzz.

dc
Table 153: Reading Register 30h

oa
Register Reads/Writes Description

Write register 30h, bits [2:0] = 111 This selects the miscellaneous control register, shadow value 111.
Br
All reads must be done through the miscellaneous control register.

Bit 15 = 0 This allows only bits [14:12] and bits [2:0] to be written.
Bits [14:12] = zzz This selects shadow value register zzz to be read.
Bits [11: 3] = <don't care> When bit 15 = 0, these bits will be ignored.
Bits [2:0] = 111 This sets the shadow register select to 111 (miscellaneous control
register).
Read register 30h Data read back is the value from shadow register zzz.
Write to register 30h, shadow value yyy.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 212
Table 154: Writing Register 30h
Register Writes Description

Set Bits [15:3] = Preferred write values Bits [15:3] contain the values to which the desired bits are written.
Set Bits [2:0] = yyy This enables shadow value register yyy to be written. For shadow
value 111, bit 15 must also be written.
Table 155: Auxiliary Control Register (Page 10h–17h: Address 30h, Shadow Value 000)

15 External Loopback R/W 1 = External Loopback is enabled 0
14 Receive Extended R/W 1 = Allow reception of extended length packets. 0
Packet Length 0 = Allow reception of normal length Ethernet packets
l
tia
only.
13 Edge Rate Control R/W 00 = 4.0 ns 0
(1000BASE-T)
en
12 R/W 01 = 5.0 ns 0
10 = 3.0 ns
11 = 0.0 ns
11 Reserved R/W fid
Write as 0, ignore on read. 0
on
C

om

5 Edge Rate Control R/W 00 = 4.0 ns 0
4 (100BASE-TX) R/W 01 = 5.0 ns 0
dc
10 = 3.0 ns
11 = 0.0 ns
oa
3 Reserved R/W Write as 0, ignore on read 0

2 Shadow Register Select R/W 000 = Auxiliary control register 0
Br
1 R/W 001 = 10BASE-T register 0

0 R/W 010 = Power/MII control register 0
100 = Miscellaneous test register
111 = Miscellaneous control register
External Loopback
When bit 15 = 1, external loopback operation is enabled. When the bit is cleared, normal operation resumes.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 213
Receive Extended Packet Length

When bit 14 = 1, BCM53128 can receive packets up to 9720 bytes in length when in SGMII mode.
When the bit is cleared, the BCM53128 only receives packets up to standard maximum size in length.
Edge Rate Control (1000BASE-T)

Bits [13:12] control the edge rate of the 1000BASE-T transmit DAC output waveform.
Edge Rate Control (100BASE-TX)

Bits [5:4] control the edge rate of the 100BASE-TX transmit DAC output waveform.
Shadow Register Select
l
tia
See the note on “Auxiliary Control Shadow Values Access Register (Page 10h–17h: Address 30h)” on page 212
describing reading from and writing to register 18h.
en
The register set shown above is that for normal operation obtained when the lower 3 bits are 000.
10BASE-T Register fid

on
Table 156: 10BASE-T Register (Page 10h–17h: Address 30h, Shadow Value 001)
C

om
15 Manchester Code Error RO 1 = Manchester code error (10BASE-T) 0

LH 0 = No Manchester code error
14 EOF Error RO 1 = EOF error is detected (10BASE-T). 0
dc
LH 0 = No EOF error is detected.

13 Polarity Error RO 1 = Channel polarity is inverted. 0
oa
0 = Channel polarity is correct.

12 Block RX_DV Extension (IPG) R/W 1 = Block RX_DV for four additional RXC cycles for 0
Br
IPG.
11 10BASE-T TXC Invert Mode R/W 1 = Invert TXC output. 0
10 Reserved R/W Write as 0, ignore on read 0
9 Jabber Disable R/W 1 = Jabber function is disabled. 0
0 = Jabber function is enabled
6 10BASE-T Echo Mode R/W 1 = Echo transmit data to receive data 0
Broadcom®
April 6, 2016 • 53128-DS07-R Page 214
Table 156: 10BASE-T Register (Page 10h–17h: Address 30h, Shadow Value 001) (Cont.)

5 SQE Enable Mode R/W 1 = Enable SQE. 0
0 = Disable SQE.
4 10BASE-T No Dribble R/W 1 = Correct 10BASE-T dribble nibble. 0
l
Power/MII Control Register (Page 10h–17h: Address 30h)
tia
Table 157: Power/MII Control Register (Page 10h–17h: Address 30h, Shadow Value 010)
en
15
14
Reserved
Reserved
R/W
R/W fid
0
0
on
C

om

5 Super Isolate (Copper Only) R/W 1 = Isolate mode with no link pulses 1
transmitted.
dc
oa

Br

Super Isolate (Copper Only)

Setting bit 5 = 1, places the BCM53128 into the super isolate mode.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 215
Shadow Register Select

See the note on “Auxiliary Control Shadow Values Access Register (Page 10h–17h: Address 30h)” on page 212
describing reading from and writing to register 30h.
Miscellaneous Test Register (Page 10h–17h: Address 30h)

Table 158: Miscellaneous Test Register (Page 10h–17h: Address 30h, Shadow Value 100)

15 Line-side [Remote] R/W 1 = Enable line-side [remote] loopback. 0
Loopback Enable 0 = Disable loopback.
l
tia
en
7
6
Reserved
Reserved
R/W
R/W
fid
0
0
on
4 Swap RX MDIX R/W 1 = RX and TX operate on same pair. 0
C
3 10BASE-T Halfout R/W 1 = Transmit 10BASE-T at half amplitude. 0
om
dc

oa

Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 216
Miscellaneous Control Register (Page 10h–17h: Address 30h)

Table 159: Miscellaneous Control Register (Page 10h–17h: Address 30h, Shadow Value 111)

15 Write Enable R/W 1 = Write bits [14:3] 0
SC 0 = Only write bits [14:12]
14 Shadow Register Read R/W These bits are written when bit 15 is not set. This 0
13 Selector R/W sets the shadow value for address 18h register 0
read.
12 R/W 0
001 = 10BASE-T register
010 = Power control register
l
tia
11 Packet Counter Mode R/W 1 = Receive packet counter. 0
0 = Transmit packet counter.
en
9 Force Auto-MDIX Mode R/W 1 = Auto-MDIX is enabled when auto-negotiation 0
is disabled.
fid
0 = Auto-MDIX is disabled when auto-negotiation
is disabled.
on
C

om
4 Ethernet@WireSpeed Enable R/W 1 = Enable Ethernet@WireSpeed 1

0 = Disable Ethernet@WireSpeed
dc
3 MDIO All PHY Select R/W 1 = The PHY ports accepts MDIO writes to PHY 0
address = 00000.
oa

Br

Broadcom®
April 6, 2016 • 53128-DS07-R Page 217
Auxiliary Status Summary Register (Page 10h–17h: Address 32h)

Table 160: Auxiliary Status Summary Register (Page 10h–17h: Address 32h–33h)

15 Auto-negotiation Complete RO 1 = Auto-negotiation is complete. 0
0 = Auto-negotiation is in progress.
14 Auto-negotiation Complete RO 1 = Entered auto-negotiation link is good check state. 0
Acknowledge LH 0 = State not entered since last read.
13 Auto-negotiation Acknowledge RO 1 = Entered auto-negotiation acknowledge detect 0
Detect LH state.
0 = State not entered since last read
12 Auto-negotiation Ability Detect RO 1 = Entered auto-negotiation ability detect state. 0
LH 0 = State not entered since last read.
11 Auto-negotiation Next Page RO 1 = Entered auto-negotiation next page wait state. 0
l
tia
Wait LH 0 = State not entered since last read.
10 Auto-negotiation HCD RO 111 = 1000BASE-T full-duplexa 0
en
9 Current Operating Speed and RO 0
110 = 1000BASE-T half-duplexa
8 Duplex Mode RO 0
101 = 100BASE-TX full-duplexa
fid
100 = 100BASE-T4
011 = 100BASE-TX half-duplexa
on
010 = 10BASE-T full-duplexa
C
001 = 10BASE-T half-duplexa

000 = No highest common denominator or
om
auto-negotiation is incomplete.
7 Parallel Detection Fault RO 1 = Parallel link fault is detected. 0
LH 0 = Parallel link fault is not detected.
dc
6 Remote Fault RO 1 = Link partner has detected a remote fault. 0

0 = Link partner has not detected a remote fault.
oa
5 Auto-negotiation Page RO 1 = New page has been received from the link partner. 0
Received LH 0 = New page has not been received.
Br
4 Link Partner Auto-negotiation RO 1 = Link partner has auto-negotiation capability. 0

Ability 0 = Link partner does not perform auto-negotiation.
3 Link Partner Next Page Ability RO 1 = Link partner has next page capability. 0
0 = Link partner does not have next page capability.
2 Link Status RO 1 = Link is up (link pass state). 0
0 = Link is down (link fail state).
1 Pause Resolution—Receive RO 1 = Enable pause receive. 0
Direction 0 = Disable pause receive.
0 Pause Resolution—Transmit RO 1 = Enable pause transmit. 0
Direction 0 = Disable pause transmit.
a. Indicates the negotiated HCD when Auto-negotiation Enable = 1, or indicates the manually selected speed
and duplex mode when Auto-negotiation Enable = 0.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 218
Interrupt Status Register (Page 10h–17h: Address 34h)

Table 161: Interrupt Status Register (Page 10h–17h: Address 34h–35h)

15 Energy Detect Change RO 1 = Energy detect change since last read (enabled 0
LH by register 1Ch, shadow 00101, bit 5 = 1).
0 = Interrupt cleared.
14 Illegal Pair Swap RO 1 = Illegal pair swap is detected. 0
LH 0 = Interrupt cleared.
13 MDIX Status Change RO 1 = MDIX status changed since last read. 0
12 Exceeded High Counter Threshold RO 1 = Value in one or more counters is above 32K. 0
0 = All counters below are 32K.
11 Exceeded Low Counter Threshold RO 1 = Value in one or more counters is above 128K. 0
l
tia
0 = All counters below are 128K.
10 Auto-negotiation Page Received RO 1 = Page received since last read. 0
en
9 No HCD Link RO 1 = Negotiated HCD, did not establish link. 0
8 No HCD
LH
RO fid
1 = Auto-negotiation returned HCD = none. 0
on
7 Negotiated Unsupported HCD RO 1 = Auto-negotiation HCD is not supported by 0
C
LH BCM53128.
om
6 Scrambler Synchronization Error RO 1 = Scrambler synchronization error occurred 0

LH since last read.
dc
5 Remote Receiver Status Change RO 1 = Remote receiver status changed since last 0
LH read.
oa
4 Local Receiver Status Change RO 1 = Local receiver status changed since last read. 0
Br
3 Duplex Mode Change RO 1 = Duplex mode changed since last read. 0

2 Link Speed Change RO 1 = Link speed changed since last read. 0
1 Link Status Change RO 1 = Link status changed since last read. 0
0 Receive CRC Error RO 1 = Receive CRC error occurred since last read. 0
The INTR LED output is asserted when any bit in 10BASE-T/100BASE-TX/1000BASE-T interrupt status register
is set and the corresponding bit in the 10BASE-T/100BASE-TX/1000BASE-T interrupt mask register is cleared.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 219
Interrupt Mask Register (Page 10h–17h: Address 36h)

Table 162: Interrupt Mask Register (Page 10h–17h: Address 36h)

15 Signal Detect/Energy Detect R/W 1 = Interrupt masked, status bits operate normally. 1
Change (enabled by register 1Ch, 0 = Interrupt enabled, status bits operate normally.
shadow 05h, bit 5 = 1)
14 Illegal Pair Swap R/W 1 = Interrupt masked, status bits operate normally. 1
0 = Interrupt enabled, status bits operate normally.
13 MDIX Status Change R/W 1 = Interrupt masked, status bits operate normally. 1
12 Exceeded High Counter Threshold R/W 1 = Interrupt masked, status bits operate normally. 1
11 MDIX Status Change R/W 1 = Interrupt masked, status bits operate normally. 1
l
tia
10 Exceeded High Counter Threshold R/W 1 = Interrupt masked, status bits operate normally. 1
en
9 HCD No Link R/W 1 = Interrupt masked, status bits operate normally. 1
8 No HCD R/W fid

1 = Interrupt masked, status bits operate normally. 1
on
7 Negotiated Unsupported HCD R/W 1 = Interrupt masked, status bits operate normally. 1
C

6 Scrambler Synchronization Error R/W 1 = Interrupt masked, status bits operate normally. 1
om

5 Remote Receiver Status Change R/W 1 = Interrupt masked, status bits operate normally. 1
dc
4 Local Receive Status Change R/W 1 = Interrupt masked, status bits operate normally. 1
oa
3 Duplex Mode Change R/W 1 = Interrupt masked, status bits operate normally. 1
Br
2 Link Speed Change R/W 1 = Interrupt masked, status bits operate normally. 1
1 Link Status Change R/W 1 = Interrupt masked, status bits operate normally. 1
0 CRC Error R/W 1 = Interrupt masked, status bits operate normally. 1
Interrupt Mask Vector

When bit n of the Interrupt Mask register is written to 1, the interrupt corresponding to the same bit in the Interrupt
Status register is masked. The status bits still operate normally when the interrupt is masked, but do not
generate an interrupt output. When this bit is written to 0, the interrupt is unmasked.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 220
10BASE-T/100BASE-TX/1000BASE-T Register 38h Access

Reading from and writing to 10BASE-T/100BASE-TX/1000BASE-T register 38h is though register 38h bits
[15:10]. The bits [14:10] set the shadow value of register 38h, and bit 15 enables the writing of the bits [9:0].
Setting bit 15 allows writing to bits [9:0] of register 38h. Before reading register 38h shadow zzzzz, writes to
register 38h should be set with bit 15 = 0, and bits [14:10] to zzzzz. The subsequent register read from register
38h contains the shadow zzzzz register value. Table 163 lists all the register 38h shadow values.
Table 163: 10BASE-T/100BASE-TX/1000BASE-T Register 38h Shadow Values
Shadow Value Register Name

00100 ”Spare Control 2 Register (Page 10h–17h: Address 38h, Shadow Value 00100)” on page
221
00101 –
01000 –
l
01001 –
tia
01010 ”Auto Power-Down Register (Page 10h–17h: Address 38h, Shadow Value 01010)” on page
222
en
01101 –
01110 ”LED Selector 2 Register (Page 10h–17h: Address 38h, Shadow Value 01110)” on page 223
11111
fid
”Mode Control Register (Page 10h–17h: Address 38h, Shadow Value 11111)” on page 225
on
Spare Control 2 Register (Page 10h–17h: Address 38h)
C
Table 164: Spare Control 2 Register (Page 10h–17h: Address 38h, Shadow Value 00100)
om

0 = Read bits [9:0]
dc
14 Shadow Register R/W 00100 = Spare control 2 register 0

13 Selector R/W 0
oa
12 R/W 1
11 R/W 0
Br
10 R/W 0
9 Reserved R/W Write as 0, ignore when read. 0
8 Reserved – – –
Broadcom®
April 6, 2016 • 53128-DS07-R Page 221
Table 164: Spare Control 2 Register (Page 10h–17h: Address 38h, Shadow Value 00100) (Cont.)

4 Ethernet@WireSpeed RO 000 = Downgrade after 2 failed auto-negotiation attempts. 0
3 Retry Limit 001 = Downgrade after 3 failed auto-negotiation attempts. 1
2 010 = Downgrade after 4 failed auto-negotiation attempts. 1
011 = Downgrade after 5 failed auto-negotiation attempts.
1 Energy Detect on INTR R/W 1 = Routes energy detect to interrupt signal. Use LED 0
LED Pin selectors (register 38h shadow 01101 and 01110) and
program to INTR mode.
0 = INTR LED pin performs the Interrupt function.
l
tia
en
Auto Power-Down Register (Page 10h–17h: Address 38h)
Bit Name R/W Description fid

Table 165: Auto Power-Down Register (Page 10h–17h: Address 38h, Shadow Value 01010)
Default
on
0 = Read bits [9:0]
C
14 Shadow Register Selector R/W 01010 = Auto power-down register 0

13 R/W 1
om
12 R/W 0
11 R/W 1
dc
10 R/W 0
oa

Br

5 Auto Power-Down Mode R/W 1 = Auto power-down mode is enabled. 0
0 = Auto power-down mode is disabled.
4 Sleep Timer Select R/W 1 = Sleep timer is 5.4 seconds. 0
0 = Sleep timer is 2.7 seconds.
3 Wake-up Timer Select R/W Counter for wake-up timer in units of 84 ms 0
2 R/W 0001 = 84 ms 0
1 R/W 0010 = 168 ms 0
0 R/W ... 1
1111 = 1.26 sec.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 222
LED Selector 2 Register (Page 10h–17h: Address 38h)

Table 166: LED Selector 2 Register (Page 10h–17h: Address 38h, Shadow Value 01110)

0 = Read bits [9:0]
14 Shadow Register Selector R/W 01110 = LED status register 0
13 R/W 1
12 R/W 1
11 R/W 1
10 R/W 0
l
7 LED4 Selector R/W 0000 = LINKSPD[1] 0
tia
6 R/W 0001 = LINKSPD[2] 1
0010 = XMITLED
en
5 R/W 1
4 R/W 0011 = ACTIVITY 0
0100 = FDXLED
fid
0101 = SLAVE
0110 = INTR
on
0111 = QUALITY
1000 = RCVLED
C
1001 = WIRESPD_DOWNGRADE
1010 = MULTICOLOR[2]
om
1011 = CABLE DIAGNOSTIC OPEN/SHORT

1100 = RESERVED
1101 = CRS (SGMII mode)
dc
1110 = Off (high)

1111 = On (low)
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 223
Table 166: LED Selector 2 Register (Page 10h–17h: Address 38h, Shadow Value 01110) (Cont.)

3 LED3 Selector R/W 0000 = LINKSPD[1] 0
2 R/W 0001 = LINKSPD[2] 0
1 R/W 0010 = XMITLED 1
0 R/W 0011 = ACTIVITY 1
0100 = FDXLED
0101 = SLAVE
0110 = INTR
0111 = QUALITY
1000 = RCVLED
1001 = WIRESPD_DOWNGRADE
1010 = MULTICOLOR[1]
1011 = CABLE DIAGNOSTIC OPEN/SHORT
l
tia
1100 = RESERVED
1101 = CRS (SGMII mode)
en
1110 = Off (high)
1111 = On (low)
fid
on
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 224
Mode Control Register (Page 10h–17h: Address 38h)

Table 167: Mode Control Register (Page 10h–17h: Address 38h, Shadow Value 11111)

0 = Read bits [9:0]
14 Shadow Register Selector R/W 11111 = LED status register 1
13 R/W 1
12 R/W 1
11 R/W 1
10 R/W 1
l
7 Copper Link RO 1 = Link is good on the copper interface. 0
tia
0 = Copper link is down.
en
5 Copper Energy Detect RO 1 = Energy detected on the copper interface. 0
0 = Energy not detected on the copper interface.
4
3
Reserved
Reserved
RO
RO
fid
Ignore on read.
Ignore on read.
0
1
on
2 Mode Select R/W 00 = GMII 0
1 01 = Reserved 0
C
10 = Reserved
11 = Reserved
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 225
Master/Slave Seed Register (Page 10h–17h: Address 3Ah)

Table 168: Master/Slave Seed Register (Page 10h–17h: Address 3Ah–3Bh) Bit 15 = 0

15 Enable Shadow Register R/W 1 = Select shadow register. 0
Writes to the selected register are done on a single
cycle.
14 Master/Slave Seed Match RO 1 = Seeds match. 0
LH 0 = Seeds do not match.
13 Link Partner Repeater/DTE Bit RO 1 = Link partner is a repeater/switch device. 0
0 = Link partner is a DTE device.
12 Link Partner Manual Master/ RO 1 = Link partner is configured as master. 0
Slave Configuration Value 0 = Link partner is configured as slave.
l
tia
11 Link Partner Manual Master/ RO 1 = Link partner manual master/slave configuration 0
Slave Configuration Enable is enabled.
0 = Link partner manual master/slave configuration
en
is disabled.
10 Local Master/Slave Seed R/W Returns the automatically generated master/slave 0
9
8
Value R/W
R/W
fid
random seed. 0
0
on
7 R/W 0
6 R/W 0
C
5 R/W 0
4 R/W 0
om
3 R/W 0
2 R/W 0
dc
1 R/W 0
0 R/W 0
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 226
HCD Status Register (Page 10h–17h: Address 3Ah)

Table 169: HCD Status Register (Page 10h–17h: Address 3Ah–3Bh) Bit 15 = 1

15 Enable Shadow Register R/W 1 = Select Shadow register. 0
14 Ethernet@WireSpeed RO 1 = Disable advertising gigabit. 0
Disable Gigabit 0 = Advertise gigabit based on register 09h.
Advertising
13 Ethernet@WireSpeed RO 1 = Disable advertising 100TX. 0
Disable 100TX 0 = Advertise 100TX based on register 04h.
Advertising
12 Ethernet@WireSpeed RO 1 = Ethernet@WireSpeed downgrade occurred since last 0
Downgrade LH read.
0 = Ethernet@WireSpeed downgrade cleared.
l
tia
11 HCD 1000BASE-T RO 1 = Gigabit full-duplex occurred since last read. 0
Full-Duplex LH 0 = HCD cleared.
en
10 HCD 1000BASE-T RO 1 = Gigabit half-duplex occurred since last read. 0
Half-Duplex LH 0 = HCD cleared.
9 HCD 100BASE-TX
Full-Duplex
RO
LH fid
1 = 100BASE-TX full-duplex occurred since last read.
0 = HCD cleared.
0
on
8 HCD 100BASE-T RO 1 = 100BASE-TX half-duplex occurred since last read. 0
C
7 HCD 10BASE-T RO 1 = 10BASE-T full-duplex occurred since last read 0

Full-Duplex LH 0 = HCD cleared.
om
6 HCD 10BASE-T RO 1 = 10BASE-T half-duplex occurred since last read. 0

5 HCD 1000BASE-T RO 1 = Gigabit full-duplex HCD and link never came up occurred 0
dc
Full-Duplex LH since the last read.

(Link Never Came Up) 0 = HCD cleared.
oa
4 HCD 1000BASE-T RO 1 = Gigabit half-duplex HCD and link never came up occurred 0
Half-Duplex LH since the last read.
Br

3 HCD 100BASE-TX RO 1 = 100BASE-TX full-duplex HCD and link never came up 0
Full-Duplex LH occurred since the last read.
2 HCD 100BASE-T RO 1 = 100BASE-TX half-duplex HCD and link never came up 0
Half-Duplex LH occurred since the last read.
1 HCD 10BASE-T RO 1 = 10BASE-T full-duplex HCD and link never came up 0
Full-Duplex LH occurred since the last read.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 227
Table 169: HCD Status Register (Page 10h–17h: Address 3Ah–3Bh) Bit 15 = 1 (Cont.)

0 HCD 10BASE-T RO 1 = 10BASE-T half-duplex HCD and link never came up 0
Half-Duplex LH occurred since the last read.
Note: Bits [12:0] are also cleared when auto-negotiation is disabled via MII register 00h, bit 12 = 1, or
restarted via MII register 00h, bit 9 = 1.
Test Register 1 (Page 10h–17h: Address 3Ch)

Table 170: Test Register 1 (Page 10h–17h: Address 3C–3Dh)
l
tia
15 CRC Error Counter R/W 1 = Receiver NOT_OK counters (register 14h) becomes 16 bit CRC 0
en
Selector error counter (CRC errors are counted only after this bit is set).
14
Visibility
fid
Transmit Error Code R/W 1 = False carrier sense counters (register 13h) counts packets
received with transmit error codes.
0
on
12 Force Link R/W 1 = Force link state machine into link pass state. 0
C
10/100/1000BASE-T 0 = Normal operation

om

dc

7 Manual Swap MDI R/W 1 = Manually swap MDI state. 0
oa
State 0 = Normal operation

Note: To change the MDI state when in forced 100BASE-TX mode,
the PHY must first be put into a nonlink condition, then set bit 7 = 1
Br
and finally set the PHY into force 100BASE-TX mode.

Note: Preamble is still required on the first read or write. Preamble suppression cannot be disabled.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 228
BCM53128 Data Sheet Expansion Registers
Expansion Registers
Expansion Register 00h: Receive/Transmit Packet Counter

Expansion register 00h is enabled by writing to “Expansion Register Access Register (Page 10h–17h: Address
2Eh–2Fh)” bits [11:0] = ‘F00’h, and read/write access is through register 2Ah.
Table 171: Expansion Register 00h: Receive/Transmit Packet Counter

15:0 Packet Counter R/W Returns the transmitted and received packet count. 0000h
(Copper Only) CR
l
Packet Counter (Copper Only)
tia
The mode of this counter is set by bit 11 of “Miscellaneous Control Register (Page 10h–17h: Address 30h,
en
Shadow Value 111)”. When bit 11 =1, then receive packets (both good and bad CRC error packets) are counted.
When bit 11 = 0, then transmit packets (both good and bad CRC error packets) are counted. This counter is
cleared on read and freezes at FFFFh.
fid
on
Expansion Register 01h: Expansion Interrupt Status
C
om
Table 172: Expansion Register 01h: Expansion Interrupt Status

dc
15:1 Reserved RO Write as 0, ignore on read 0

0 Transmit CRC Error RO 1 = Transmit CRC error detected since last read. 0
oa
LH 0 = No transmit CRC error detected.

Br
Transmit CRC Error

This bit indicates that a transmit CRC error has been detected since the last read.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 229
BCM53128 Data Sheet Page 20h–28h: Port MIB Registers
Expansion Register 45h: Transmit CRC Enable

Table 173: Expansion Register 45h: Transmit CRC

15:13 Reserved R/W Write as 0, ignore on read. 000
12 Transmit CRC enable R/W 1 = Enable transmit CRC checker. 0
0 = Disable transmit CRC checker.
Register 18h, shadow value 100, bit 15 must be set to
a 1.
11:0 Reserved R/W Write as 0, ignore on read. 0
l
Transmit CRC Checker
tia
When register 30h, Shadow Value 100, bit 15 = 1 and Expansion Register 45h, bit 12 = 1, the transmit CRC
en
checker is enabled. When a transmit CRC error occurs, Expansion Register 01h, bit 0 = 1.
Page 20h–28h: Port MIB Registers

fid
on
Table 174: Port MIB Registers Page Summary
C
Page Description
om
20h Port 0
21h Port 1
dc
22h Port 2
23h Port 3
oa
24h Port 4
25h Port 5
Br
26h Port 6
27h Port 7
28h IMP port
Table 175: Page 20h–28h Port MIB Registers
ADDR Bits Name Description

00h–07h 64 TxOctets The total number of good bytes of data transmitted by a port
(excluding preamble, but including FCS).
Broadcom®
April 6, 2016 • 53128-DS07-R Page 230
Table 175: Page 20h–28h Port MIB Registers (Cont.)

08h–0Bh 32 TxDropPkts This counter is incremented every time a transmit packet is
dropped due to lack of resources (e.g., transmit FIFO
underflow), or an internal MAC sublayer transmit error not
counted by either the TxLateCollision or the
TxExcessiveCollision counters.
0Ch–0Fh 32 TxQ0PKT The total number of good packets transmitted on COS0, which
is specified in MIB queue select register when QoS is enabled.
10h–13h 32 TxBroadcastPkts The number of good packets transmitted by a port that are
directed to a broadcast address. This counter does not include
errored broadcast packets or valid multicast packets.
14h–17h 32 TxMulticastPkts The number of good packets transmitted by a port that are
directed to a multicast address. This counter does not include
errored multicast packets or valid broadcast packets.
l
18h–1Bh 32 TxUnicastPkts The number of good packets transmitted by a port that are
tia
addressed to a unicast address.
1Ch–1Fh 32 TxCollisions The number of collisions experienced by a port during packet
en
transmissions.
20h–23h 32 TxSingleCollision The number of packets successfully transmitted by a port that
experienced exactly one collision.
24h–27h 32 TxMultiple Collision fid
The number of packets successfully transmitted by a port that
experienced more than one collision.
on
28h–2Bh 32 TxDeferredTransmit The number of packets transmitted by a port for which the first
transmission attempt is delayed because the medium is busy.
C
2Ch–2Fh 32 TxLateCollision The number of times that a collision is detected later than 512
bit-times into the transmission of a packet.
om
30h–33h 32 TxExcessiveCollision The number of packets that are not transmitted from a port
because the packet experienced 16 transmission attempts.
34h–37h 32 TxFrameInDisc The number of valid packets received that are discarded by
dc
the forwarding process due to lack of space on an output

queue. (Not maintained or reported in the MIB counters and
located in the congestion management registers [Page 0Ah].)
oa
This attribute only increments if a network device is not acting

in compliance with a flow-control request, or the BCM53128
Br
internal flow control/buffering scheme has been

misconfigured.
38h–3Bh 32 TxPausePkts The number of PAUSE events on a given port.
40h–43h 32 TxQ2PKT The total number of good packets transmitted on COS2, which
44h–47h 32 TxQ3PKT The total number of good packets transmitted on COS3, which
48h–4Bh 32 TxQ4PKT The total number of good packets transmitted on COS4, which
Broadcom®
April 6, 2016 • 53128-DS07-R Page 231

50h–57h 64 RxOctets The number of bytes of data received by a port (excluding
preamble, but including FCS), including bad packets.
58h–5Bh 32 RxUndersizePkts The number of good packets received by a port that are less
than 64 bytes long (excluding framing bits, but including the
FCS).
5Ch–5Fh 32 RxPausePkts The number of PAUSE frames received by a port. The PAUSE
frame must have a valid MAC control frame EtherType field
(88–08h), have a destination MAC address of either the MAC
control frame reserved multicast address (01-80-C2-00-00-
01) or the unique MAC address associated with the specific
port, a valid PAUSE Opcode (00–01), be a minimum of 64
bytes in length (excluding preamble but including FCS), and
have a valid CRC. Although an IEEE 802.3-compliant MAC is
only permitted to transmit PAUSE frames when in full-duplex
l
mode with flow control enabled and with the transfer of
tia
PAUSE frames determined by the result of auto-negotiation,
an IEEE 802.3 MAC receiver is required to count all received
en
PAUSE frames, regardless of its half/full-duplex status. An
indication that a MAC is in half-duplex with the RxPausePkts
incrementing indicates a noncompliant transmitting device on
60h–63h 32 Pkts64Octets
the network.
fid
The number of packets (including error packets) that are 64
on
bytes long.
64h–67h 32 Pkts65to127Octets The number of packets (including error packets) that are
between 65 and 127 bytes long.
C
68h–6Bh 32 Pkts128to255Octets The number of packets (including error packets) that are
om
6Ch–6Fh 32 Pkts256to511Octets The number of packets (including error packets) that are
dc
70h–73h 32 Pkts512to1023Octets The number of packets (including error packets) that are
74h–77h 32 Pkts1024toMaxPktOct The number of packets (including error packets) that are
oa
ets between 1024 and MaxPacket bytes long.

78h–7Bh 32 RxOversizePkts The number of good packets received by a port that are
Br
greater than standard max frame size.

7Ch–7Fh 32 RxJabbers The number of packets received by a port that are longer than
1522 bytes and have either an FCS error or an alignment
error.
80h–83h 32 RxAlignmentErrors The number of packets received by a port that have a length
(excluding framing bits, but including FCS) between 64 and
standard max frame size, inclusive, and have a bad FCS with
a nonintegral number of bytes.
84h–87h 32 RxFCSErrors The number of packets received by a port that have a length
(excluding framing bits, but including FCS) between 64 and
standard max frame size, inclusive, and have a bad FCS with
an integral number of bytes.
88h–8Fh 64 RxGoodOctets The total number of bytes in all good packets received by a
port (excluding framing bits but including FCS).
Broadcom®
April 6, 2016 • 53128-DS07-R Page 232

90h–93h 32 RxDropPkts The number of good packets received by a port that were
dropped due to lack of resources (e.g., lack of input buffers) or
were dropped due to lack of resources before a determination
of the validity of the packet was able to be made (e.g., receive
FIFO overflow). The counter is only incremented if the receive
error was not counted by the RxAlignmentErrors or the
RxFCSErrors counters.
94h–97h 32 RxUnicastPkts The number of good packets received by a port that are
addressed to a unicast address.
98h–9Bh 32 RxMulticastPkts The number of good packets received by a port that are
directed to a multicast address. This counter does not include
errored multicast packets or valid broadcast packets.
9Ch–9Fh 32 RxBroadcastPkts The number of good packets received by a port that are
directed to the broadcast address. This counter does not
l
tia
include errored broadcast packets or valid multicast packets.
A0h–A3h 32 RxSAChanges The number of times the SA of good receive packets has
en
changed from the previous value. A count greater than 1
generally indicates the port is connected to a repeater-based
network.
A4h–A7h 32 RxFragments
fid
The number of packets received by a port that are less than 64
bytes (excluding framing bits) and have either an FCS error or
on
an alignment error.
A8h–ABh 32 JumboPkt The number of frames received with frame size greater than
the Standard Maximum Size and less than or equal to the
C
Jumbo Frame Size, regardless of CRC or Alignment errors.

Note: InFrame count should count "the JumboPkt count with
om
good CRC."
ACh–AFh 32 RXSymbolError The total number of times a valid length packet was received
at a port and at least one invalid data symbol was detected.
dc
Counter only increments once per carrier event and does not
increment on detection of collision during the carrier event.
oa
B0h–B3h 32 InRangeErrors The number of frames received with good CRC and the
following conditions.
The value of Length/Type field is between 46 and 1500
Br
inclusive, and does not match the number or (MAC Client Data
+ PAD) data octets received,
OR
The value of Length/Type field is less than 46, and the number
of data octets received is greater than 46 (which does not
require padding).
B4h–B7h 32 OutOfRangeErrors The number of frames received with good CRC and the value
of Length/Type field is greater than 1500 and less than 1536.
B8h-BBh 32 EEE Low-Power Idle In asymmetric mode, this is simply a count of the number of
Event times that the lowPowerAssert control signal has been
asserted for each MAC. In symmetric mode, this is the count
of the number of times both lowPowerAssert and the
lowPowerIndicate (from the receive path) are asserted
simultaneously.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 233

BCh-BFh 32 EEE Low-Power This counter accumulates the number of microseconds that
Duration the associated MAC/PHY is in the low-power idle state. The
unit is 1 used.
C0h–C3h 32 RxDiscard The number of good packets received by a port that were
discarded by the Forwarding Process.
F0h–F7h 64 “SPI Data I/O Register –
(Global, Address F0h)”
on page 295, bytes 0–
7
F8h–FDh – Reserved –
FEh 8 “SPI Status Register –
(Global, Address FEh)”
on page 295
l
tia
FFh 8 “Page Register –
(Global, Address FFh)”
on page 296
en
fid
on
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 234
BCM53128 Data Sheet Page 30h: QoS Registers
Page 30h: QoS Registers

Table 176: Page 30h QoS Registers
Address Bits Description

00h 8 “QoS Global Control Register (Page 30h: Address 00h)” on page 236
01h–02h 16 Reserved
03h – Reserved
04h–05h 16 “QoS IEEE 802.1p Enable Register (Page 30h: Address 04h)” on
page 236
06h–07h 16 “QoS DiffServ Enable Register (Page 30h: Address 06h)” on page 237
10h–33h 32/port “Port N (N = 0-7, 8) PCP_To_TC Register (Page 30h: Address 10h)” on
page 237
l
tia
40h–45h 48 “DiffServ Priority Map 0 Register (Page 30h: Address 40h)” on page 238
en
46h–4Bh 48 “DiffServ Priority Map 1 Register (Page 30h: Address 46h)” on page 239
4Ch–51h 48 “DiffServ Priority Map 2 Register (Page 30h: Address 4Ch)” on page 239
52h–57h
48h–61h
48
– fid
“DiffServ Priority Map 3 Register (Page 30h: Address 52h)” on page 240
Reserved
on
62h–63h 16 “TC_To_COS Mapping Register (Page 30h: Address 62h–63h)” on
page 241
C
64h–67h 32 “CPU_To_COS Map Register (Page 30h: Address 64h–67h)” on

page 242
om
80h 8 “TX Queue Control Register (Page 30h: Address 80h)” on page 243
81h 8 “TX Queue Weight Register (Page 30h: Address 81h)” on page 243,
dc
Queue 0
oa
Queue 1
Queue 2
Br
Queue 3
85h–86h 16 “COS4 Service Weight Register (Page 30h: Address 85h–86h)” on
page 244
A0h – Reserved
A1h – Reserved
A2h–EFh – Reserved
Broadcom®
April 6, 2016 • 53128-DS07-R Page 235
QoS Global Control Register (Page 30h: Address 00h)

Table 177: QoS Global Control Register (Page 30h: Address 00h)

7 Aggregation Mode R/W When enable this bit, the IMP operated as the uplink port to 0
the upstream network processor and the COS is decided
from the TC based on the normal packet classification flow.
Otherwise, the IMP operated as the interface to the
management CPU, and the COS is decided based on the
reasons for forwarding the packet to the CPU.
6 PORT_QOS_EN R/W Port-based QoS enable 0
When port-based QoS is enabled, ingress frames are
assigned a priority ID value based on the PORT_QOS_PRI
bits in the “Default IEEE 802.1Q Tag Register (Page 34h:
Address 10h)” on page 255. IEEE 802.1p and DiffServ
l
priorities are disregarded.
tia
0 = Disable port-based QoS.
1 = Enable port-based QoS.
en
See “Quality of Service” on page 34 for more information.
3:2 QOS_LAYER_SEL R/W
fid
QoS priority selection
These bits determine which QoS priority scheme is
0
on
associated with the frame. See Table 1 on page 36 for more
information.
C

om
QoS IEEE 802.1p Enable Register (Page 30h: Address 04h)

Table 178: QoS.1P Enable Register (Page 30h: Address 04h–05h)
dc

oa

8:0 802_1P_EN R/W QoS IEEE 802.1p port mask 0
Br
Bit 8: IMP port

0 = Disable IEEE 802.1p priority for individual ports.
1 = Enable IEEE 802.1p priority for individual ports.
See “IEEE 802.1Q VLAN” on page 39 for more information.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 236
QoS DiffServ Enable Register (Page 30h: Address 06h)

Table 179: QoS DiffServ Enable Register (Page 30h: Address 06h–07h)

8:0 DIFFSERV_EN R/W DiffServ port mask 0
Bit 8: IMP port
0 = Disable DiffServ priority for individual ports.
1 = Enable DiffServ priority for individual ports.
l
Port N (N = 0-7, 8) PCP_To_TC Register (Page 30h: Address 10h)
tia
.
Table 180: Port N (N=0-7,8) PCP_To_TC Register Address Summary
en
Address Description
10h–13h
14h–17h
Port 0
Port 1fid
on
18h–1Bh Port 2
1Ch–1Fh Port 3
C
20h–23h Port 4
24h–27h Port 5
om
28h–2Bh Port 6
2Ch–2Fh Port 7
dc
30h–33h IMP Port

oa
These bits map the IEEE 802.1p priority level to one of the eight priority ID levels in the “TC_To_COS Mapping
Register (Page 30h: Address 62h–63h)” on page 241.
Br
Table 181: Port N (N=0-7,8) PCP_To_TC Register (Page 30h: Address 10h–33h)

23:21 1P_111_MAP R/W IEEE 802.1p priority tag field 111 111
Broadcom®
April 6, 2016 • 53128-DS07-R Page 237
DiffServ Priority Map 0 Register (Page 30h: Address 40h)

These bits map the DiffServ priority level to one of the eight Priority ID levels in the “TC_To_COS Mapping
Table 182: DiffServ Priority Map 0 Register (Page 30h: Address 40h–45h)

47:45 DIFFSERV_ 001111_MAP R/W DiffServ DSCP priority tag field 001111 0
l
tia
en
20:18
17:15
DIFFSERV_ 000110_MAP
R/W
R/W
fid
DiffServ DSCP priority tag field 000110
0
0
on
C
om
dc

oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 238

These bits map the DiffServ priority level to one of the eight Priority ID levels in the “TC_To_COS Mapping
Table 183: DiffServ Priority Map 1 Register (Page 30h: Address 46h–4Bh)

l
tia
en
14:12
11:9
R/W
R/W fid
0
0
on
C
om

dc
DiffServ Priority Map 2 Register (Page 30h: Address 4Ch)

oa
These bits map the DiffServ priority level to one of the eight priority ID levels in the “TC_To_COS Mapping
Br
Table 184: DiffServ Priority Map 2 Register (Page 30h: Address 4Ch–51h)

Broadcom®
April 6, 2016 • 53128-DS07-R Page 239
Table 184: DiffServ Priority Map 2 Register (Page 30h: Address 4Ch–51h) (Cont.)

l
tia
These bits map the DiffServ priority level to one of the eight priority ID levels in the “TC_To_COS Mapping
en
Table 185: DiffServ Priority Map 3 Register (Page 30h: Address 52h–57h)
Bit Name R/W Description fid Default

on
47:45 DIFFSERV_111111_MAP R/W DiffServ DSCP priority tag field 111111 0
44:42 DIFFSERV_111110_MAP R/W DiffServ DSCP priority tag field 111110 0
C
41:39 DIFFSERV_ R/W DiffServ DSCP priority tag field 111101 0

111101_MAP
om

111100_MAP
dc
111011_MAP
111010_MAP
oa

111001_MAP
Br

111000_MAP
110111_MAP
110110_MAP
100101_MAP
110100_MAP
110011_MAP
Broadcom®
April 6, 2016 • 53128-DS07-R Page 240
Table 185: DiffServ Priority Map 3 Register (Page 30h: Address 52h–57h) (Cont.)

110010_MAP
110001_MAP
110000_MAP
TC_To_COS Mapping Register (Page 30h: Address 62h–63h)

All the bits in Table 186 map the priority ID to one of the TX queues.
l
tia
Table 186: TC_To_COS Mapping Register (Page 30h: Address 62h–63h)
en
15:14 PRI_111_QID R/W Priority ID 111 mapped to TX Queue ID 00
13:12
11:10
PRI_110_QID
PRI_101_QID
R/W
R/W fid
Priority ID 110 mapped to TX Queue ID
Priority ID 101 mapped to TX Queue ID
00
00
on
C

om

dc

oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 241
CPU_To_COS Map Register (Page 30h: Address 64h–67h)

Table 187: CPU_To_COS Map Register (Page 30h: Address 64h–67h)

31:18 Reserved RO – 0
17:15 Exception/Flooding R/W The packet forwarded to the CPU for Exception 0
Processing to CPU COS Map Processing/Flooding reason.
The COS selection is based on the highest COS
values among all the reasons for the packet.
14:12 Protocol Snooping to CPU R/W The packet forwarded to the CPU for Protocol 0
COS Map Snooping reason.
11:9 Protocol Termination to CPU R/W The packet forwarded to the CPU for Protocol 0
COS Map Termination reason.
l
tia
en
8:6 Switching to CPU COS Map R/W The packet forwarded to the CPU for Switching 0
reason.
5:3 SA Learning to CPU COS R/W

fid
The packet forwarded to the CPU for SA 0
on
Map Learning reason.
C
among all the reasons for the packet.

2:0 Mirror to CPU COS Map R/W The packet forwarded to the CPU for mirroring 0
om
reason.
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 242
TX Queue Control Register (Page 30h: Address 80h)

Table 188: TX Queue Control Register (Page 30h: Address 80h)

1:0 QOS_PRIORITY_ R/W Best Effort Queues Priority Control 00
CTRL This field controls the best effort queues’ scheduling priority. It
doesn’t affect the behavior of COS4 and COS5.
00: all queues are weighted round robin
01: COS3 is strict priority, COS2-COS0 are weighted round
robin.
10: COS3 and COS2 is strict priority, COS1-COS0 are
weighted round robin.
l
11: COS3, COS2, COS1 and COS0 are in strict priority.
tia
Strict priority: When it is in strict priority, the priority is COS3 >
COS2 > COS1 > COS0.
en
The G_TXPORT will always serve the higher queue first if it is
not empty.
fid
In this mode, the service weight are don’t care.
Weighted round robin: When it is in weighted round robin
mode, the queues are scheduled in a round robin
on
way according to the service weight of each queue.
C

om
TX Queue Weight Register (Page 30h: Address 81h)

dc
Table 189: TX Queue Weight Register Queue[0:3] (Page 30h: Address 81h–84h)
oa

7:0 QSERV_WEIGHT R/W Queue weight register Queue:
Br
The binary value of these bits sets the service weight of 0: 0001
the given queue. The value of 1 allows the queue to send 1: 0010
one packet for every round; the value of 4 allows the
2: 0100
queue to send four packets for every round. It is suggested
that the weight of each queue be Q3 > Q2 > Q1 > Q0 > 0. 3: 1000
Note: The maximum allowable transmit queue weight is
31h. Programming a higher weight than 31h can yield
unexpected results. This field must not be programmed as
zero.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 243
COS4 Service Weight Register (Page 30h: Address 85h–86h)

Table 190: COS4 Service Weight Register (Page 30h: Address 85h–86h)

8 COS4 Strict Priority R/W COS4 Strict Priority 1
When this field is set to ‘1’, the C4 service weight
is don’t care and Class 4 is in strict priority over
the best effort queues (COS3–COS0).
7:0 COS4 Weight R/W COS4 Service Weight 1
This field defines the service weight between
Class 4 traffic and the Best Effort COS3-COS0.
When this field is N, it means Class-4:Best-Effort
= N:1
l
When in weighted round robin mode, it is
tia
meaningless to set this field as zero.
en
fid
on
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 244
BCM53128 Data Sheet Page 31h: Port-Based VLAN Registers
Page 31h: Port-Based VLAN Registers

Table 191: Page 31h VLAN Registers

00h–11h 16/port “Port-Based VLAN Control Register (Page 31h: Address 00h)”
1Fh–EFh – Reserved
Port-Based VLAN Control Register (Page 31h: Address 00h)
l
tia
Table 192: Port-Based VLAN Control Register Address Summary
en
Address Description
00h–01h Port 0
02h–03h
04h–05h
Port 1
Port 2
fid
on
06h–07h Port 3
08h–09h Port 4
C
0Ah–0Bh Port 5
0Ch–0Dh Port 6
om
0Eh–0Fh Port 7
10h–11h IMP port
dc
oa
Table 193: Port VLAN Control Register (Page 31h: Address 00h–11h)

Br

8:0 FORWARD_MASK R/W VLAN forwarding mask 1FFh
Bit 8: IMP port
0 = Disable VLAN forwarding to egress port.
1 = Enable VLAN forwarding to egress port.
For more information, see “Port-Based VLAN” on page 38.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 245
BCM53128 Data Sheet Page 32h: Trunking Registers
Page 32h: Trunking Registers

Table 194: Page 32h Trunking Registers

00h 8 “MAC Trunking Control Register (Page 32h: Address 00h)”
10h–11h 16 Trunk group 0 register
12h–13h 16 Trunk group 1 register
l
tia
en
MAC Trunking Control Register (Page 32h: Address 00h)

fid
on
Table 195: MAC Trunk Control Register (Page 32h: Address 00h)

C

3 MAC_BASE_TRNK_E R/W Enable MAC base trunking 0
om
N
dc
1:0 TRK_HASH_INDX R/W Trunk hash index selector 0

00 = Use hash [DA,SA] to generate index.
oa
01 = Use hash [DA] to generate index.

10 = Use hash [SA] to generate index.
11 = Illegal state
Br
See “Port Trunking/Aggregation” on page 44 for more information.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 246
BCM53128 Data Sheet Page 32h: Trunking Registers
Trunking Group 0 Register (Page 32h: Address 10h)

Table 196: Trunk Group 0 Register (Page 32h: Address 10h–11h)

8:0 Trunk Group Enable R/W Trunk group enable 0
1 = Enable trunk group.
0 = Disable trunk group.
Bit 8: IMP port
See “Port Trunking/Aggregation” on page 44 for more information.
l
Trunking Group 1 Register (Page 32h: Address 12h)
tia
Table 197: Trunk Group 1 Register (Page 32h: Address 12h–13h)
en
15:9
8:0
Reserved
Trunk Group Enable
R/W
R/W
Reserved
fid
Trunk group enable
0
0
on
1 = Enable trunk group.
0 = Disable trunk group.
C
Bit 8: IMP port

om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 247
BCM53128 Data Sheet Page 34h: IEEE 802.1Q VLAN Registers
Page 34h: IEEE 802.1Q VLAN Registers

Table 198: Page 34h IEEE 802.1Q VLAN Registers

00h 8 “Global IEEE 802.1Q Register (Pages 34h: Address 00h)” on page 248
01h 8 “Global IEEE 802.1Q VLAN Control 1 Register (Page 34h: Address 01h)” on
page 250
02h 8 “Global VLAN Control 2 Register (Page 34h: Address 02h)” on page 251
03h–04h 16 “Global VLAN Control 3 Register (Page 34h: Address 03h)” on page 251
07h 8 Reserved
l
0Ah–0Bh 16 “” on page 254
tia
Reserved 32 Reserved
10h–21h 16/port “Default IEEE 802.1Q Tag Register (Page 34h: Address 10h)” on page 255
en
30h–31h 16 “Double Tagging TPID Register (Page 34h: Address 30h–31h)” on page 256
32h–33h 16
fid
“ISP Port Selection Portmap Register (Page 34h: Address 32h–33h)” on
page 256
on
C
49h–EFh – –
om
dc

oa
Global IEEE 802.1Q Register (Pages 34h: Address 00h)

Br
Table 199: Global IEEE 802.1Q Register (Pages 34h: Address 00h)

7 Enable IEEE 802.1Q R/W Enable IEEE 802.1Q VLAN 0
0 = Disable IEEE 802.1Q VLAN.
1 = Enable IEEE 802.1Q VLAN.
See “Programming the VLAN Table” on page 40 for
more information.
Note: This bit must be set if double tagging mode
enable in “Global VLAN Control 4 Register (Page
34h: Address 05h)” on page 252.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 248
Table 199: Global IEEE 802.1Q Register (Pages 34h: Address 00h) (Cont.)

6:5 VLAN Learning Mode R/W VLAN learning mode 11
00 = SVL (Shared VLAN learning mode) (MAC hash
ARL table)
11 = IVL (Individual VLAN learning mode) (MAC and
VID hash ARL table)
10 = Illegal setting
01 = Illegal setting
Note: Applied to 802.1Q enable and DT_Mode.
3 Change_1Q_VID R/W Change 1Q VID to PVID 0
1=
• For a single tag frame with VID not = 0, change
l
tia
the VID to PVID.
• For a double tag frame with outer VID not = 0,
en
change outer VID to PVID.
0 = No change for 1Q/ISP tag if VID is not 0.
2
1
Reserved
Reserved
R/W
R/W
Reserved
Reserved fid 0
1
on
C
See “IEEE 802.1Q VLAN” on page 39 for more information.

om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 249
Global IEEE 802.1Q VLAN Control 1 Register (Page 34h: Address

01h)
Table 200: Global VLAN Control 1 Register (Page 34h: Address 01h)

6 Multicast Untag Check R/W Multicast VLAN untagged map check bypass 0
1 = Multicast frames are not checked against the
VLAN untagged map.
0 = Multicast frames are checked against the VLAN
untagged map. Does not apply to the frame
management port.
5 Multicast Forward Check R/W Multicast VLAN forward map check bypass 0
1 = Multicast frames are not checked against the
l
VLAN forward map.
tia
0 = Multicast frames are checked against the VLAN
forward map.
en
4 Reserved R/W It is illegal to set 1. 0
3 Reserved Multicast
Untag Check
R/W
fid
Reserved multicast (except GMRP and GVRP) VLAN 0
untagged map check bit
on
1 = Reserved multicast (except GMRP and GVRP)
frames are checked against the VLAN untagged map.
C
frames are not checked against the VLAN untagged

map. Does not apply to the frame management port.
om
2 Reserved Multicast R/W Reserved multicast (except GMRP and GVRP) VLAN 0
Forward Check forward map check bit
dc
frames are checked against the VLAN forward map.

oa
frames are not checked against the VLAN forward

map.
Br
1 Reserved R/W It is illegal to set 0. 1

For more information, see “IEEE 802.1Q VLAN” on page 39.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 250
Global VLAN Control 2 Register (Page 34h: Address 02h)


6 GMRP/GVRP Untag R/W GMRP or GVRP VLAN untag map check bit 0
Check 1 = GMRP or GVRP frames are checked against the
VLAN untagged map.
0 = GMRP or GVRP frames are not checked against
the VLAN untagged map.
Note: Does not apply to the frame management port.
5 GMRP/GVRP Forward R/W GMRP or GVRP VLAN forward map check bit 0
Check 1 = GMRP or GVRP frames are checked against the
VLAN forward map.
l
0 = GMRP or GVRP frames are not checked against
tia
the VLAN forward map.
Note: Does not apply to the frame management port.
en
Applied to 802.1Q enable and DT_Mode.
3
2
Reserved
IMP Frame Forward
R/W
R/W
Reserved
fid
IMP Frame VLAN forward map check bit
0
0
on
Bypass 1 = IMP frames are not checked against the VLAN
forward map.
0 = IMP frames are checked against the VLAN
C
forward map.
om

dc

oa

Br
Table 202: Global VLAN Control 3 Register (Page 34h: Address 03h–04h)

15:9 Reserved RO – –
7:0 Drop Non1Q Frames R/W Drop non1Q frames 0
When enabled, any frame without an IEEE 802.1Q tag
is dropped by this port.
This field does not apply to IMP port.
Bit 8: IMP port
Broadcom®
April 6, 2016 • 53128-DS07-R Page 251


7:6 Source Membership R/W Source membership check bit 11
Check Frames with a VID matching a corresponding entry in
the VLAN table can be checked for source
membership. The source is a member only when the
source address of the frame is included as a member
in the corresponding VLAN entry.
00 = Forward frame, but do not learn the SA into the
ARL table.
01 = Drop frame.
10 = Forward frame, and learn the SA into the ARL
table.
l
tia
11 = Forward frame to IMP, but not learn.
Note: Does not apply to IMP port.
en
5 Forward GVRP to R/W Forward all GVRP frames to the frame management 0
Management port bit.
1 = GVRP frames are forwarded to the management
port.
fid
0 = GVRP frames are not forwarded to the
on
management port.
4 Forward GMRP to R/W Forward All GMRP Frames to the frame management 0
Management port bit.
C
1 = GMRP frames are forwarded to the management

port.
om
0 = GMRP frames are not forwarded to the

management port.
3:2 En_DT_Mode R/W 00 = Disable double tagging mode 2'b00
dc
01 = Enable DT_Mode (double tagging mode)

10 = Reserved
oa
11 = Reserved
1 RSV_MCAST_FLOO R/W When the BCM53128 is configured to operate in
Br
D double tag feature management mode.

1 = Flood (including all data port and CPU), reserved
mcast is based on the VLAN rule.
0 = Trap reserved mcast to CPU.
Reserved mcast include: 01-80-C2-00-00-
(00,02~2F)
Broadcom®
April 6, 2016 • 53128-DS07-R Page 252


6 Tag Status Preserve R/W IEEE 802.1Q tag/untag status preserved at egress. 0
1 = Regardless of untag map in VLAN table, non-1Q
frames (including 802.1p frames) will not be changed
at TX (egress).
This field has no effect in double tagging mode
(DT_Mode).
4 Trunk Check Bypass R/W Trunk check bypass 1
1 = Egress directed frames issued from the IMP port
l
bypass trunk checking.
tia
0 = Egress directed frames issued from the IMP port
are subject to trunk checking and redirection.
en
3 Drop Invalid VID R/W Drop frames with invalid VID. 0
Frames with an invalid VID do not have a
fid
corresponding entry in the VLAN table.
1 = Ingress frames with invalid VID are dropped.
on
0 = Ingress frames with invalid VID are forwarded to
the IMP port.
2 VID_FFF_Fwding R/W Enable VID FFF forward 0
C
1 = Forward frame
0 = Comply with standard, drop frame
om

0 Management CRC R/W Bypass CRC check at the frame management port. 0
dc
Check Bypass 1 = Ignore CRC check

0 = Check CRC
oa

Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 253
VLAN Multiport Address Control Register (Page 34h: Address 0Ah–

0Bh)
Table 205: VLAN Multiport Address Control Register (Page 34h: Address 0Ah–0Bh)

11 EN_MPORT5_untagmap R/W When set to 1, MPORT_ADD5 is checked by 0
VLAN untag map.
Note: Does not apply to the frame management
port.
10 EN_MPORT5 _fwdmap R/W When set to 1, MPORT_ADD5 is checked by 0
VLAN forward map.
port.
l
9 EN_MPORT4_untagmap R/W When set to 1, MPORT_ADD4 will be checked 0
tia
by VLAN untag map.
en
port.
8 EN_MPORT4 _fwdmap R/W When set to 1, MPORT_ADD4 will be checked 0
fid
by VLAN forward map.
port.
on
by VLAN untag map.
C

port.
om

dc
port.
oa
by VLAN untag map.

port.
Br

port.
by VLAN untag map.
port.
port.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 254
Table 205: VLAN Multiport Address Control Register (Page 34h: Address 0Ah–0Bh) (Cont.)

by VLAN untag map.
port.
port.
Default IEEE 802.1Q Tag Register (Page 34h: Address 10h)

Table 206: Default IEEE 802.1Q Tag Register Address Summary
l
tia
Address Description
10h–11h Port 0
en
12h–13h Port 1
14h–15h Port 2
16h–17h
18h–19h
Port 3
Port 4 fid
on
1Ah–1Bh Port 5
1Ch–1Dh Port 6
C
1Eh–1Fh Port 7
20h–21h IMP port
om
Table 207: Default IEEE 802.1Q Tag Register (Page 34h: Address 10h–21h)
dc

oa
15:13 DEFAULT_PRI/ R/W Default IEEE 802.1Q priority 000

PORT_QOS_PRI If an IEEE 802.1Q tag is added to an incoming
Br
untagged frame (IEEE 802.1Q VLAN or Double-

Tagging enabled), these bits are the default priority
value for the new tag. See “IEEE 802.1Q VLAN” on
page 39 and “Double-Tagging” on page 41 for more
information.
Port-based QoS priority map bits
When port-based QoS is enabled in the Table : “QoS
Global Control Register (Page 30h: Address 00h),” on
page 236, these bits represent the TC for the ingress
port. The TC determines the TX queue for each frame
based on the “TC_To_COS Mapping Register (Page
30h: Address 62h–63h)” on page 241.
12 CFI R/W Conical form indicator 0
Broadcom®
April 6, 2016 • 53128-DS07-R Page 255
Table 207: Default IEEE 802.1Q Tag Register (Page 34h: Address 10h–21h) (Cont.)

11:0 DEFAULT_VID R/W Default IEEE 802.1Q VLAN ID 001
If an IEEE 802.1Q tag is tagged to an incoming non-
IEEE 802.1Q frame (IEEE 802.1Q VLAN or Double-
Tagging enabled), then these bits are the default VID
for the new tag. See “IEEE 802.1Q VLAN” on page 39
and “Double-Tagging” on page 41 for more information.
Double Tagging TPID Register (Page 34h: Address 30h–31h)

Table 208: Double Tagging TPID Register (Page 34h: Address 30h–31h)
l
15:0 ISP_TPID R/W The TPID used to identify double tagged frame. 9100
tia
ISP Port Selection Portmap Register (Page 34h: Address 32h–33h)
en
Table 209: ISP Port Selection Portmap Register (Page 34h: Address 32h–33h)
Bit Name R/W Description fid Default

on
15:9 RESERVED RO Reserved 0
8:0 ISP_Portmap R/W Bitmap that defines which port is designated as the ISP 0
C
port.
Bit 8: IMP port
om

0 = Indicates that it is not an ISP port.
1 = Indicates that it is an ISP port.
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 256
BCM53128 Data Sheet Page 36h: DOS Prevent Register
Page 36h: DOS Prevent Register

Table 210: DOS Prevent Register

00h–03h 32 “DOS Control Register (Page 36h: Address 00h–03h)”
04h 8 “Minimum TCP Header Size Register (Page 36h: Address 04h)” on page 259
08h–0Bh 32 “Maximum ICMPv4 Size Register (Page 36h: Address 08h–0Bh)” on page 259
0Ch–0Fh 32 “Maximum ICMPv6 Size Register (Page 36h: Address 0Ch–0Fh)” on page 259
10h 8 “DOS Disable Learn Register (Page 36h: Address 10h)” on page 259
F0h–F7h 8 “SPI Data I/O Register (Global, Address F0h)” on page 295
l
tia
en
DOS Control Register (Page 36h: Address 00h–03h)
Bit Name R/W fid

Table 211: DOS Control Register (Page 36h: Address 00h–03h)
Description Default
on
13 ICMPv6_LongPing_DROP_EN R/W The ICMPv6 ping (echo request) protocol 0
C
data unit carried in an unfragmented IPv6

datagram with its payload length indicating
om
a value greater than the

MAX_ICMPv6_Size.
1= Drop
dc
0= Do not drop
12 ICMPv4_LongPing_DROP_EN R/W The ICMPv4 ping (echo request) protocol 0
oa
data unit carried in an unfragmented IPv4

datagram with its Total Length indicating a
value greater than the MAX_ICMPv4_Size
Br
+ size of IPv4 header.

1= Drop
0= Do not drop
11 ICMPv6_Fragment_DROP_EN R/W The ICMPv6 protocol data unit carried in a 0
fragmented IPv6 datagram.
1= Drop
0= Do not drop
10 ICMPv4_Fragment_DROP_EN R/W The ICMPv4 protocol data unit carried in a 0
fragmented IPv4 datagram.
1= Drop
0= Do not drop
Broadcom®
April 6, 2016 • 53128-DS07-R Page 257
Table 211: DOS Control Register (Page 36h: Address 00h–03h) (Cont.)

9 TCP_FragError_DROP_EN R/W The Fragment_Offset = 1 in any fragment of 00
a fragmented IP datagram carrying part of
TCP data.
1 = Drop
0 = Do not drop
8 TCP_ShortHDR_DROP_EN R/W The length of a TCP header carried in an 00
unfragmented IP datagram or the first
fragment of a fragmented IP datagram is
less than MIN_TCP_Header_Size.
1 = Drop
0 = Do not drop
7 TCP_SYNError_DROP_EN R/W SYN = 1, ACK = 0, and SRC_Port<1024 in 0
a TCP header carried in an unfragmented
l
tia
IP datagram or in the first fragment of a
fragmented IP datagram.
1= Drop
en
0= Do not drop
6 TCP_SYNFINScan_DROP_EN R/W SYN = 1 and FIN = 1 in a TCP header 0
fid
carried in an unfragmented IP datagram or
in the first fragment of a fragmented IP
datagram.
on
1= Drop
0= Do not drop
C
5 TCP_XMASScan_DROP_EN R/W Seq_Num = 0, FIN = 1, URG = 1, and PSH 0

= 1 in a TCP header carried in an
om
unfragmented IP datagram or in the first

fragment of a fragmented IP datagram.
1 = Drop
dc
0 = Do not drop
4 TCP_NULLScan_DROP_EN R/W Seq_Num = 0 and all TCP_FLAGs = 0 in a 0
oa
TCP header carried in an unfragmented IP

datagram or in the first fragment of a
fragmented IP datagram.
Br
1= Drop
0= Do not drop
3 UDP_BLAT_DROP_EN R/W DPort = SPort in a UDP header carried in an 0
1= Drop
0= Do not drop
2 TCP_BLAT_DROP_EN R/W DPort = SPort in a TCP header carried in an 0
1= Drop
0= Do not drop
Broadcom®
April 6, 2016 • 53128-DS07-R Page 258
Table 211: DOS Control Register (Page 36h: Address 00h–03h) (Cont.)

1 IP_LAN_DRIP_EN R/W IPDA = IPSA in an IPv4/v6 datagram. 0
1=Drop
0=Do not drop
0 RESERVED R/W Reserved 1
Minimum TCP Header Size Register (Page 36h: Address 04h)

Table 212: Minimum TCP Header Size Register (Page 36h: Address 04h)

7:0 MIN_TCP_HDR_SZ R/W Minimum TCP header size allowed (0–256 bytes). 8'h14
l
tia
Maximum ICMPv4 Size Register (Page 36h: Address 08h–0Bh)
en
Table 213: Maximum ICMPv4 Size Register (Page 36h: Address 08h-0Bh)
Bit
31:0
Name
MAX_ICMPv4_SIZE
R/W
R/W fid
Description
Max ICMPv4 size allowed (0–9.6K bytes).
Default
32'd512
on
Maximum ICMPv6 Size Register (Page 36h: Address 0Ch–0Fh)
C
Table 214: Maximum ICMPv6 Size Register (Page 36h: Address 0Ch-0Fh)
om

31:0 MAX_ICMPv6_SIZE R/W Max ICMPv6 size allowed (0–9.6K bytes). 32'd512
dc
DOS Disable Learn Register (Page 36h: Address 10h)

oa
Table 215: DOS Disable Learn Register (Page 36h: Address 08h-0Bh)
Br

7:1 RESERVED R/W Reserved –
0 DOS Disable Lrn R/W When this bit enabled, all frames dropped by DOS 0
prevent will not be learned.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 259
BCM53128 Data Sheet Page 40h: Jumbo Frame Control Register
Page 40h: Jumbo Frame Control Register

Table 216: Page 40h Jumbo Frame Control Register

00h – Reserved
01h–04h 32 “Jumbo Frame Port Mask Register (Page 40h: Address 01h)”
05h–06h 16 “Standard Max Frame Size Register (Page 40h: Address 05h)” on
page 261
l
tia
en
Jumbo Frame Port Mask Register (Page 40h: Address 01h)
Table 217: Jumbo Frame Port Mask Registers (Page 40h: Address 01h–04h)
BIt Name R/W Description fid Default

on
C
8:0 JUMBO_PORT_MASK R/W Jumbo frame port mask 0

Bit 8: IMP port
om

0 = Disable jumbo frame capability on the port.
1 = Enable jumbo frame capability on the port.
dc
Jumbo frames can be ingressed and egressed only to the

ports enabled via this port mask. Jumbo frame port mask
oa
has no effect on the traffic of normal sized frames. See

“Jumbo Frame Support” on page 44 for more information.
Br
Note: When the Jumbo Frame feature is enabled, the assigned Weight value for the WRR scheduling
cannot be applied fairly over the queues. This is due to the internal Packet Buffer Memory size
limitation.
Note: The Jumbo Frame feature is only supported in 1000 Mbps mode.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 260
BCM53128 Data Sheet Page 40h: Jumbo Frame Control Register
Standard Max Frame Size Register (Page 40h: Address 05h)

Table 218: Standard Max Frame Size Registers (Page 40h: Address 05h–06h)

13:0 Standard Max Frame R/W Standard Max Frame Size ‘d2000
Size Defines the standard maximum frame size for MAC
and MIB counter.
This register only allowed to be configured as
14'd1518 or 14'd2000. When jumbo is disabled, the
content of this register is used to define good frame
length.
• If it is configured as 1518, the tagged frames will
be dropped if the frame length is larger than 1522
bytes; and the untagged frames will be dropped
l
if the frame length is larger than 1518 bytes.
tia
• If it is configured as 2000, both tagged and
untagged frames will be dropped if the frame
en
length is larger than 2000 bytes.
When jumbo is enabled, all frames will be dropped if
fid
the frame length is larger than 9720 bytes.
The register setting affects the following MIB
parameters:
on
• RxSAChange
• RxGoodOctets
C
• RxUnicastPkts
• RxMulticastPkts
om
• RxBroadcastPkts
• RxOverSizePkts
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 261
BCM53128 Data Sheet Page 41h: Broadcast Storm Suppression Register
Page 41h: Broadcast Storm Suppression Register

Table 219: Broadcast Storm Suppression Register (Page 41h)

00h–03h 32 “Ingress Rate Control Configuration Register (Page 41h: Address 00h)”
10h–33h 32/port “Port Receive Rate Control Register (Page 41h: Address 10h)” on page 264
80h–91h 16/port “Port Egress Rate Control Configuration Register (Page 41h: Address 80h–
91h)” on page 266
l
92h–BFh – Reserved
tia
C0h 8 “IMP Port Egress Rate Control Configuration Register (Page 41h: Address
C0h)” on page 267
en
C2h–EFh – Reserved
F8h–FDh
FEh
–
8
Reserved
fid
“SPI Status Register (Global, Address FEh)” on page 295
on
C
Ingress Rate Control Configuration Register (Page 41h: Address 00h)

om
Table 220: Ingress Rate Control Configuration Register (Page 41h: Address 00h–03h)

dc

18 XLENEN R/W Packet Length Selection 0
oa
0 = RX rate excludes IPG.

1 = RX rate includes IPG (and Preamble + SFD).
Br
17 BUCK1_ R/W Bit rate mode selection 0

BRM_SEL 0 = Absolute bit rate mode—The rate count in the “Port
Receive Rate Control Register (Page 41h: Address 10h)” on
page 264 represents the incoming bit rate as an absolute
data rate.
1 = Bit rate normalized to link speed mode—The rate count
in the “Port Receive Rate Control Register (Page 41h:
Address 10h)” on page 264 represents the incoming bit rate
normalized with respect to the link speed mode.
See “Rate Control” on page 45 for more details.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 262
Table 220: Ingress Rate Control Configuration Register (Page 41h: Address 00h–03h) (Cont.)

15:9 BUCK1_PACKET_ R/W Suppressed packet type mask. 0
TYPE This bit mask determines the type of packets to be monitored
by bucket 1.
0 = Disable suppression for the corresponding packet type.
1 = Enable suppression for the corresponding packet type.
The bits in this bit field are defined as follows:
Bit 9: Unicast lookup hit
Bit 10: Multicast lookup hit
Bit 11: Reserved MAC Address Frame
Bit 12: Broadcast
Bit 13: Multicast lookup failure
Bit 14: Unicast lookup failure
l
tia
Bit 15: Reserved
en
8 BUCK0_ R/W Bit rate mode selection BC_SUPP_EN
BRM_SEL 0 = Absolute bit rate mode—The rate count in the “Port
Receive Rate Control Register (Page 41h: Address 10h)” on
fid
page 264 represents the incoming bit rate as an absolute
data rate.
on
1 = Bit rate normalized to link speed mode—The rate count
in the “Port Receive Rate Control Register (Page 41h:
Address 10h)” on page 264 represents the incoming bit rate
C
normalized with respect to the link speed mode.

om

6 XLENEN_EG R/W Packet length selection for egress rate control. 0
0 = TX Rate Exclude IPG
dc
1 = TX Rate Include IPG (and Preamble + SFD)

5:0 BUCK0_PACKET_ R/W Suppressed packet type mask. BC_SUPP_EN:
oa
TYPE This bit mask determines the type of packets to be monitored 1: 001000
by bucket 0. 0: 000000
Br
0 = Disable suppression for the corresponding packet type.

1 = Enable suppression for the corresponding packet type.
The bits in this bit field are defined as follows:
Bit 0: Unicast lookup hit
Bit 1: Multicast lookup hit
Bit 2: Reserved MAC address frame
Bit 3: Broadcast
Bit 4: Multicast lookup failure
Bit 5: Unicast lookup failure
Broadcom®
April 6, 2016 • 53128-DS07-R Page 263
Port Receive Rate Control Register (Page 41h: Address 10h)

Table 221: Port Rate Control Register Address Summary
Address Description
10h–13h Port 0
14h–17h Port 1
18h–1Bh Port 2
1Ch–1Fh Port 3
20h–23h Port 4
24h–27h Port 5
28h–2Bh Port 6
2Ch–2Fh Port 7
30h–33h IMP port for BCM53128
l
tia
Table 222: Port Rate Control Register (Page 41h: Address 10h–33h)
en
31:29
28
Reserved
STRM_SUPR_EN
RO
R/W
Reserved
fid
Enable storm suppression (Supported by bucket1).
0
Reflects the
on
0 = Disable strap pin
BC_SUPP_
1 = Enable EN
C
27 RsvMC_SUPR_EN R/W Enable reserved mulitcast storm suppression. 0

0 = Disable
om
1 = Enable
26 BC_SUPR_EN R/W Enable broadcast storm suppression. 0
0 = Disable
dc
1 = Enable
25 MC_SUPR_EN R/W Enable multicast storm suppression. 0
oa
0 = Disable
1 = Enable
Br
24 DLF_SUPR_EN R/W Enable DLF storm suppression. 0

0 = Disable
1 = Enable
23 Enable Bucket1 R/W Enable rate control of the ingress port, bucket 1. 0
0 = Disable
1 = Enable
22 Enable Bucket0 R/W Enable rate control of the ingress port, bucket 0. Reflects the
0 = Disable strap pin
BC_SUPP_
1 = Enable EN
Broadcom®
April 6, 2016 • 53128-DS07-R Page 264
Table 222: Port Rate Control Register (Page 41h: Address 10h–33h) (Cont.)

21:19 BUCK1_SIZE R/W Bucket size 000
This bit determines the maximum size of bucket 1. This is
specified on a per port basis.
000 = 4 KB
001 = 8 KB
010 = 16 KB
011 = 32 KB
100 = 64 KB
101 = 500 KB
110 = 500 KB
111 = 500 KB
l
tia
18:11 BUCK1_Rate_Cnt R/W Rate count 10h
The rate count is an integer that increments the rate at
which traffic can ingress the given port without being
en
suppressed. This value is specified on a per port basis.
The programmed values of the rate count and the bit rate
fid
mode of the “Ingress Rate Control Configuration Register
(Page 41h: Address 00h)” on page 262 determine the
bucket bit rate in kilobytes. The bucket bit rate represents
on
the average upper limit for incoming packets selected in
the suppressed packet type mask in the “Ingress Rate
Control Configuration Register (Page 41h: Address 00h)”
C
on page 262. See “Rate Control” on page 45 for more

details.
om
Values written to these bits must be with the ranges

specified by Table 3 on page 47. Values outside these
ranges are not valid.
dc
10:8 BUCK0_SIZE R/W Bucket size 000

oa

000 = 4 KB
001 = 8 KB
Br
010 = 16 KB
011 = 32 KB
100 = 64 KB
101 = 500 KB
110 = 500 KB
111 = 500 KB
Broadcom®
April 6, 2016 • 53128-DS07-R Page 265
Table 222: Port Rate Control Register (Page 41h: Address 10h–33h) (Cont.)

7:0 BUCK0_Rate_Cnt R/W Rate count 10h
The rate count is an integer that increments the rate at
which traffic can ingress the given port without being
suppressed. This value is specified on a per port basis.
The programmed values of the rate count and the bit rate
mode of the “Ingress Rate Control Configuration Register
(Page 41h: Address 00h)” on page 262 determine the
bucket bit rate in kilobytes. The bucket bit rate represents
the average upper limit for incoming packets selected in
the Suppressed packet type mask in the “Ingress Rate
Control Configuration Register (Page 41h: Address 00h)”
on page 262. See “Rate Control” on page 45 for more
details.
l
tia
Port Egress Rate Control Configuration Register (Page 41h: Address
80h–91h)
en
Table 223: Port Egress Rate Control Configuration Register Address Summary
Address
80h–81h
fid
Description
Port 0
on
82h–83h Port 1
84h–85h Port 2
C
86h–87h Port 3
om
88h–89h Port 4
8Ah–8Bh Port 5
8Ch–8Dh Port 6
dc
8Eh–8Fh Port 7
90h–91h IMP port
oa
Br
Table 224: Port Egress Rate Control Configuration Registers (Page 41h: Address 80h–91h)
Defaul
BIt Name R/W Description t
11 ERC_EN R/W Egress rate control enable ((Absolute Bit Rate) 0
Broadcom®
April 6, 2016 • 53128-DS07-R Page 266
Table 224: Port Egress Rate Control Configuration Registers (Page 41h: Address 80h–91h) (Cont.)
Defaul
10:8 BKT_SZE R/W Bucket size 0
000 = 4 KB
001 = 8 KB
010 = 16 KB
011 = 32 KB
100 = 64 KB
101 = 500 KB
110 = 500 KB
111 = 500 KB
l
tia
7:0 RATE_CNT R/W Rate count for bucket 0
en
IMP Port Egress Rate Control Configuration Register (Page 41h:
Address C0h)
fid
on
Table 225: IMP Port Egress Rate Control Configuration Register Address Summary
Address Description
C
C0h IMP Port

om
Table 226: IMP Port Egress Rate Control Configuration Registers (Page 41h: Address C0h)
dc
Defaul
oa
7:6 RESERVED RO Reserved 0

5:0 Rate_Index R/W Rate_Index is used to configure different egress rates for IMP in 6'd63
Br
packet per second (pps). See Table 227: “Using Rate_Index to

Configure Different Egress Rates for IMP in pps,” on page 268.
When set to 0, the egress rate is limited to a maximum of 384 pps.
When set to 63, the egress rate control function is disabled and all
packets are transmitted at wire-speed.
Note: If the Rate_Index is configured as a certain value, the
egress rate is limited to the corresponding speed whether the
switch is running at 10 Mbps, 100 Mbps, or 1 Gbps.
Note: The Rate_Index should be a reasonable value under the
corresponding network speed configuration. It does not make
sense to set a value of 63 with the network configuration at 10
Mbps. In that case, the egress rate is limited up to 10 Mbps.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 267
BCM53128 Data Sheet Page 42h: EAP Register
Table 227: Using Rate_Index to Configure Different Egress Rates for IMP in pps
Rate_Index pps Rate_Index pps Rate_Index pps Rate_Index pps

0 384 16 5376 32 25354 48 357143
1 512 17 5887 33 27382 49 423729
2 639 18 6400 34 29446 50 500000
3 768 19 6911 35 31486 51 568182
4 1024 20 7936 36 35561 52 641026
5 1280 21 8960 37 39682 53 714286
6 1536 22 9984 38 42589 54 781250
7 1791 23 11008 39 56818 55 862069
8 2048 24 12030 40 71023 56 925926
9 2303 25 13054 41 85324 57 1000000
l
10 2559 26 14076 42 99602 58 1086957
tia
11 2815 27 15105 43 113636 59 1136364
12 3328 28 17146 44 127551 60 1190476
en
13 3840 29 19201 45 142045 61 1250000
14 4352 30 21240 46 213675 62 1315789
15 4863 31 23299 47
fid 284091 63 1388889
on
Page 42h: EAP Register
C
om

dc
00h 8 “EAP Global Control Register (Page 42h: Address 00h)” on page 269
01h 8 “EAP Multiport Address Control Register (Page 42h: Address 01h)” on page 269
oa
02h–09h 64 “EAP Destination IP Register 0 (Page 42h: Address 02h)” on page 270
0Ah–12h 64 “EAP Destination IP Register 1 (Page 42h: Address 0Ah)” on page 270
Br
20h–5Fh 64 “Port EAP Configuration Register (Page 42h: Address 20h)” on page 271
Broadcom®
April 6, 2016 • 53128-DS07-R Page 268
EAP Global Control Register (Page 42h: Address 00h)

Table 229: EAP Global Control Registers (Page 42h: Address 00h)
Defaul
6 EN_RARP R/W When EAP_BLK_MODE is set: 0
1: Allow RARP to pass.
0: Drop RARP
5 EN_BPDU R/W When EAP_BLK_MODE is set: 0
1: BPDU Addresses are allowed to pass.
0: Drop
4 EN_RMC R/W When EAP_BLK_MODE is set: 0
1: Allows DA = 01-80-C2-00-00-02, 04~0F to pass.
l
tia
0: Drop DA = 01-80-C2-00-00-02, 04~0F to pass.
3 EN_DHCP R/W When EAP_BLK_MODE is set: 0
en
1: Allows DHCP to pass
0: Drop DHCP
2 EN_ARP R/W
fid
When EAP_BLK_MODE is set:
1: Allows ARP to pass
0
on
0: Drop ARP
1 EN_2DIP R/W When EAP_BLK_MODE bit is set: 0
C
1: Two subnet IP addresses defined in EAP destination IP

registers 0 and 1 are allowed to pass.
0: Drop
om

dc
EAP Multiport Address Control Register (Page 42h: Address 01h)

oa
Table 230: EAP Multiport Address Control Register (Page 42h: Address 01h)
Br

5 EN_MPORT5 R/W 1: Allow Multiport ETYPE Address 5 define at “Multiport 0
Address N (N=0–5) Register (Page 04h: Address 10h)”
on page 182 to pass.
0: Drop
0: Drop
0: Drop
Broadcom®
April 6, 2016 • 53128-DS07-R Page 269
Table 230: EAP Multiport Address Control Register (Page 42h: Address 01h) (Cont.)

0: Drop
0: Drop
0: Drop
l
tia
EAP Destination IP Register 0 (Page 42h: Address 02h)
en
Table 231: EAP Destination IP Registers 0 (Page 42h: Address 02h–09h)

63:32 DIP_SUB 0 R/W fid
EAP destination IP subnet register 0 0
on
31: 0 DIP_MSK 0 R/W EAP destination IP mask register 0 0
C
EAP Destination IP Register 1 (Page 42h: Address 0Ah)

om
Table 232: EAP Destination IP Registers 1 (Page 42h: Address 0Ah–12h)

dc
63:32 DIP_SUB 1 R/W EAP destination IP subnet register 1 0

31:0 DIP_MSK 1 R/W EAP destination IP mask register 1 0
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 270
Port EAP Configuration Register (Page 42h: Address 20h)

Table 233: Port EAP Configuration Register Address Summary
Address Description
20h–27h Port 0
28h–2Fh Port 1
30h–37h Port 2
38h–3Fh Port 3
40h–47h Port 4
48h–4Fh Port 5
50h–57h Port 6
58h–5Fh Port 7
l
tia
Table 234: Port EAP Configuration Registers (Page 42h: Address 20h–47h)
en
52:51 EAP_MODE R/W
fid
00 = Basic mode, do not check SA.
01 = Reserved
0
on
10 = Extend mode, check SA and port number, drop if SA
is unknown.
11 = Simplified mode, check SA and port number trap to
C
management port if SA is unknown.

50:49 EAP_BLK_MODE R/W 00: Do not check EAP_BLK_MODE. 0
om
01: To check EAP_BLK MODE on ingress port, only the

frame defined in EAP_GCFG will be forwarded.
Otherwise, the frame will be dropped.
dc
10: reserved
11: To check EAP_BLK MODE on both ingress and egress
oa
port, only the frame defined in EAP_GCFG will be

forwarded. The forwarding process will verify that each
egress port is at block mode.
Br
48 EAP_EN_DA R/W Enable EAP frame with DA 0

47:0 EAP_DA R/W EAP frame DA register 00-00-00-
00-00-00
Broadcom®
April 6, 2016 • 53128-DS07-R Page 271
BCM53128 Data Sheet Page 43h: MSPT Register
Page 43h: MSPT Register


00h 8 “MSPT Control Register (Page 43h: Address 00h)”
01h – Reserved
02h–05h 32 “MSPT Aging Control Register (Page 43h: Address 02h)”
10h–2Fh 32 “MSPT Table Register (Page 43h: Address 10h)” on page 273
30h–4Ah – Reserved
50h–51h 16 “SPT Multiport Address Bypass Control Register (Page 43h: Address
50h–51h)” on page 274
l
tia
en
fid
on
MSPT Control Register (Page 43h: Address 00h)
Table 236: MSPT Control Registers (Page 43h: Address 00h–01h)
C
Defaul
om

0 EN_802.1S R/W 0: Disable 0
dc
1: Enable
oa
MSPT Aging Control Register (Page 43h: Address 02h)

Br
Table 237: MSPT Aging Control Registers (Page 43h: Address 02h–05h)
Defaul
7: 0 MSPT_AGE_MAP R/W Per spanning tree aging enable 0
Broadcom®
April 6, 2016 • 53128-DS07-R Page 272
MSPT Table Register (Page 43h: Address 10h)

Table 238: MSPT Table Register Address Summary
Address Description
10h–13h MSPT 0
14h–17h MSPT 1
18h–1Bh MSPT 2
1Ch–1Fh MSPT 3
20h–23h MSPT 4
24h–27h MSPT 5
28h–2Bh MSPT 6
2Ch–2Fh MSPT 7
l
tia
Table 239: MSPT Table Registers (Page 43h: Address 10h–2Fh)
en
Defaul
26:24 Reserved R/W Reserved
fid 0
on
23:21 Reserved R/W Spanning tree state for port 7 0
20:18 Reserved R/W Spanning tree state for port 6 0
17:15 SPT_STA5 R/W Spanning tree state for port 5 0
C

om
000 = No spanning tree

001 = Disabled
010 = Blocking
dc
011 = Listening
100 = Learning
oa
101 = Forwarding
Br

Broadcom®
April 6, 2016 • 53128-DS07-R Page 273
SPT Multiport Address Bypass Control Register (Page 43h: Address

50h–51h)
Table 240: SPT Multiport Address Bypass Control Register (Page 43h: Address 50h–51h)

5 EN_MPORT5_BYPASS_SP R/W 1: The MPORT_ADD_5 of “Multiport Address N –
T (N=0–5) Register (Page 04h: Address 10h)” on
page 182 is not checked by SPT status.
0: The MPORT_ADD_5 is checked by SPT status.
0: The MPORT_ADD_4 will be checked by SPT
l
status.
tia
en
2 EN_MPORT2_BYPASS_SP R/W
T
fid
1: The MPORT_ADD_2 of “Multiport Address N
(N=0–5) Register (Page 04h: Address 10h)” on
–
on
C

om

0 EN_MPORT0_BYPASS_SP R/W 1: The MPORT_ADD_0 of “Multiport Address N 0
dc

oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 274
BCM53128 Data Sheet Page 70h: MIB Snapshot Control Register
Page 70h: MIB Snapshot Control Register

Table 241: MIB Snapshot Control Register

00h 8 “MIB Snapshot Control Register (Page 70h: Address 00h)”
F0h–F7h 8 “SPI Data I/O Register (Global, Address F0h)” on page 295 bytes 0-7
MIB Snapshot Control Register (Page 70h: Address 00h)
l
tia
Table 242: MIB Snapshot Control Register (Page 70h: Address 00h)
en
7 SNAPSHOT_START/ R/W Write 1'b1 to initiate MIB snapshot access, clear to 0
6
DONE
SNAPSHOT_MIRROR
SC
R/W fid
1'b0 when MIB snapshot access is done
1'b1: enable read address to port MIB, but data 0
on
from MIB snapshot memory.
1'b0: enable to read from port MIB memory
C

3:0 SNAPSHOT_PORT R/W Port Number for MIB snapshot function 0
om
dc
Page 71h: Port Snapshot MIB Control Register

oa
Table 243: Port Snapshot MIB Control Register

Br
71h – The Port Snapshot MIB Registers are same as registers in “MII Control
Register (Page 10h–17h: Address 00h–01h)” on page 196
Broadcom®
April 6, 2016 • 53128-DS07-R Page 275
BCM53128 Data Sheet Page 72h: Loop Detection Register
Page 72h: Loop Detection Register

Table 244: Loop Detection Control Register (Page 72h)

00h–01h 16 “Loop Detection Control Register (Page 72h: Address 00h)”
02h 8 “Discovery Frame Timer Control Register (Page 72h: Address 02h)” on page 276
03h–04h 16 “LED Warning Port Map Register (Page 72h: Address 03h)” on page 277
05h–0Ah 48 Module ID 0
0Bh–10h 48 Module ID 1
11h– 16h 48 Loop detect frame SA
l
tia
en
Loop Detection Control Register (Page 72h: Address 00h)

fid
on
Table 245: Loop Detection Control Registers (Page 72h: Address 00h–01h)

C

12 EN_LOOP_DETECT R/W Enable loop detection feature. Strap
om
0 = Disable
1 = Enable
dc
11 LOOP_IMP_SEL R/W Enable IMP loop detection feature. Strap

0 = Disable
oa
1 = Enable
10:3 LED_RST_TIMR_CTR R/W Number of missed discovery time before LED warning 0x4
L portmap to be reset.
Br
2 OV_PAUSE_ON R/W 1 = Transmit frame in highest queue even the port is in 0x1
pause on state.
0 = Transmit frame follow the pause state rule.
1:0 DISCOVERY_FRAME R/W Specifies which queue to be put for the received discovery 0x1
_QUEUE_SEL frame.
Discovery Frame Timer Control Register (Page 72h: Address 02h)

Table 246: Discovery Frame Timer Control Registers (Page 72h: Address 02h)

Broadcom®
April 6, 2016 • 53128-DS07-R Page 276
BCM53128 Data Sheet Page 72h: Loop Detection Register
Table 246: Discovery Frame Timer Control Registers (Page 72h: Address 02h)

3:0 Discover_Frame_Timer R/W From 1 second (default) to 15 seconds. Scale = 1s. 0
0000 = 1s
0001 = 2s
0002 = 3s
.
.
.
1110 = 15s
LED Warning Port Map Register (Page 72h: Address 03h)
l
Table 247: LED Warning Port Map Registers (Page 72h: Address 03h–04h)
tia
Defaul
en
8:0 LED_WARNING_POR R/O
TMAP
Bit 8: IMP port
fid
0
on
Each bit shows the status of Loop Detected on the
corresponding port.
C
Module ID 0 Register (Page 72h: Address 05h)

om
Table 248: Module ID 0 Registers (Page 72h: Address 05h–0Ah)

dc
47:0 Module_ID_SA RO – 0
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 277
BCM53128 Data Sheet Page 88h: IMP Port External PHY MII Registers Page Summary
Module ID 1 Register (Page 72h: Address 0Bh)

Table 249: Module ID 1 Registers (Page 72h: Address 0Bh–10h)

47 Module_ID_AVAILABLE RO Module ID is available when the first packet is received. 0
0 = Unavailable
1 = Available
39:32 MODULE_ID_PORT_N RO This is an 8-bit port number for module ID. 0
O
31:0 MODULE_ID_CRC RO This is an 32-bit CRC for module ID. 0
Loop Detect Source Address Register (Page 72h: Address 11h)
l
tia
Table 250: Loop Detect Source Address Registers (Page 72h: Address 11h–16h)
en
47:0 LD_SA R/W Loop detection frame SA 01-80-C2-00-00-01
fid
on
Page 88h: IMP Port External PHY MII Registers Page Summary
C
Table 251: IMP Port External PHY MII Registers Page Summary
om

88h – MII address from 00h to 0Ah are IEEE standard registers and the descriptions for the
registers are “Page 10h–17h: Internal GPHY MII Registers” on page 194
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 278
BCM53128 Data Sheet Page 90h: BroadSync HD Register
Page 90h: BroadSync HD Register

Table 252: BroadSync HD Register

00h–01h 16 “BroadSync HD Enable Control Register (Page 90h: Address 00h–01h)” on
page 280
02h 8 “BroadSync HD Time Stamp Report Control Register (Page 90h: Address 02h)”
on page 280
03h 8 “BroadSync HD PCP Value Control Register (Page 90h: Address 03h)” on
page 280
04h–05h 8 “BroadSync HD Max Packet Size Register (Page 90h: Address 04h)” on
page 281
l
10h–13h 32 “BroadSync HD Time Base Register (Page 90h: Address 10h–13h)” on
tia
page 281
14h–17h 32 “BroadSync HD Time Base Adjustment Register (Page 90h: Address 14h–17)”
en
on page 281
18h–1Bh 32 “BroadSync HD Slot Number and Tick Counter Register (Page 90h: Address
1Ch–1Fh 32
18h–1Bh)” on page 282
fid
“BroadSync HD Slot Adjustment Register (Page 90h: Address 1Ch–1Fh)” on
on
page 282
30h–3Fh 16 “BroadSync HD Class 5 Bandwidth Control Register (Page 90h: Address 30h)”
C
on page 283
om
60h–6Fh 16 “BroadSync HD Class 4 Bandwidth Control Register (Page 90h: Address 60h)”
on page 283
dc
90h–AFh 32 “BroadSync HD Egress Time Stamp Register (Page 90h: Address 90h)” on
page 284
oa
B0h–CFh – Reserved
D0h 8 “BroadSync HD Egress Time Stamp Status Register (Page 90h: Address D0h)”
Br
on page 284
D1h–DFh – Reserved
E0h–E1h 16 “BroadSync HD Link Status Register (Page 90h: Address E0h–E1h)” on
page 285
B2h–EFh – Reserved
F0h–F7h 8 “SPI Data I/O Register (Global, Address F0h)” on page 295 bytes 0-7
Broadcom®
April 6, 2016 • 53128-DS07-R Page 279
BroadSync HD Enable Control Register (Page 90h: Address 00h–01h)

Table 253: BroadSync HD Enable Control Register (Page 90h: Address 00h–01h)

7:0 BroadSync HD Enable R/W BroadSync HD enable. 0
BroadSync HD Time Stamp Report Control Register (Page 90h:

Address 02h)
Table 254: BroadSync HD Time Stamp Report Control Register (Page 90h: Address 02h)
l
tia
0 TSRPT_PKT_EN R/W This field is to allow the Time Stamp Reporting 0
en
Packet to IMP port when the time
synchronization packet transmitted on egress
port.
fid
on
BroadSync HD PCP Value Control Register (Page 90h: Address 03h)
C
Table 255: BroadSync HD PCP Value Control Register (Page 90h: Address 03h)

om

5:3 ClassB_PCP R/W BroadSync HD Class B PCP value. 3'd4
dc
This field is used to qualify the PCP value of

BroadSync HD packet. This BroadSync HD
packet will be sent to Queue4.
oa
2:0 ClassA_PCP R/W BroadSync HD Class A PCP value. 3'd5

This field is used to qualify the PCP value of
Br
BroadSync HD packet. This BroadSync HD

packet will be sent to Queue5.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 280
BroadSync HD Max Packet Size Register (Page 90h: Address 04h)

Table 256: BroadSync HD Max Packet Size Register (Page 90h: Address 04h)

11:0 MAX_BroadSync R/W This field is to define the max packet size of BroadSync 12’d1518
HD_PACKET_SIZE HD. The ingress port uses it to qualify if the packet is
allowed to pass through a BroadSync HD link.
The egress prot uses it to perform shaping gate.
BroadSync HD Time Base Register (Page 90h: Address 10h–13h)

Table 257: BroadSync HD Time Base Register (Page 90h: Address 10h–13h)
l
tia
31:0 TIME BASE RO Time Base 0
en
This is a 32-bit free running clock (running at 25 MHz) for
BroadSync HD time base. Ingress port and Egress port use it
for Time Synchronization Packet Time Stamp.
fid
BroadSync HD Time Base Adjustment Register (Page 90h: Address
on
14h–17)
C
Table 258: BroadSync HD Time Base Adjustment Register (Page 90h: Address 14h–17h)
om

11:8 TIME ADJUST PERIOD R/W Time Adjust Period 41. 4’h0
dc
This field defines the tick numbers to apply the

adjusted Time Increment (when Time Increment does
oa
not equal to 40).

For example, to increment the Time Base for 10 ticks
Br
with 41 ns per tick, Time Adjust Period is 10, and Time

Increment is 41.
5:0 TIME INCREMENT R/W Time Increment 6’d40
This field defines the value to add into Time Base in
each 25-MHz tick.
Default is 40.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 281
BroadSync HD Slot Number and Tick Counter Register (Page 90h:

Address 18h–1Bh)
Table 259: BroadSync HD Slot Number and Tick Counter Register (Page 90h: Address 18h–1Bh)

27:16 TICK COUNTER R/W Tick Counter 12’h0
This is the tick counter which defines when will
Slot Number increment. It runs from 1 to 3125 (or
3124, or 3126, depends on “BroadSync HD Slot
Number and Tick Counter Register (Page 90h:
Address 18h–1Bh)” on page 282 setting) under
25 MHz.
l
4:0 SLOT NUMBER R/W This field specifies the Slot Number for 8’h0
tia
BroadSync HD.
en
BroadSync HD Slot Adjustment Register (Page 90h: Address 1Ch–
1Fh)
fid
Table 260: BroadSync HD Slot Adjustment Register (Page 90h: Address 1Ch–1Fh)
on
C

17:16 MACRO SLOT PERIOD R/W Macro Slot Period 2’h0
om
This field defines the slot time of a macro slot for

Class 4 traffic.
00 = 1 ms
dc
01 = 2 ms
10 = 4 ms
oa
11 = Reserved
Class 5 traffic slot time is always 125s period.
Br

11:8 SLOT ADJUST PERIOD R/W Slot Adjust Period 8’h0
This field defines the number of slots to apply the
alterable slot adjustment.
1:0 SLOT ADJUSTMENT R/W Slot Adjustment 2’h0
This field defines when the slot number counter
increment by 1. Default is 40.
00 = Slot Number increased by 1 when tick
counter rolls over 3125.
01 = 3126
10 = 3124
11 = Reserved
Broadcom®
April 6, 2016 • 53128-DS07-R Page 282
BroadSync HD Class 5 Bandwidth Control Register (Page 90h:

Address 30h)
.
Table 261: BroadSync HD Class 5 Bandwidth Control Register Address Summary
Address Description
30h–31h Port 0
32h–33h Port 1
34h–35h Port 2
36h–37h Port 3
38h–39h Port 4
3Ah-3Bh Port 5
3Ch–3Dh Port 6
3Eh-3Fh Port 7
l
tia
Table 262: BroadSync HD Class 5 Bandwidth Control Register (Page 90h: Address 30h–31h, 32h–33h,
en
34h–35h, 36h–37h, 38h–39h)

15 C5_WINDOW R/W fid
The purpose is to control the credit carry-over under
different link speed. For a 100M link, the 125-s slot is too
1’b0
on
small such that BroadSync HD packet could easily “slip
slot”, so the credit carry-over should be allowed. For a 1G
C
link, 125-s slot is reasonably big such that the BW

reservation could be done in a conservative way to prevent
“slot slipping”, so credit carry-over is not needed.
om
13:0 C5_BANDWIDTH R/W This field defines the byte count allowed for Class 5 traffic 14’h0
transmission within a slot time.
dc
oa
BroadSync HD Class 4 Bandwidth Control Register (Page 90h:

Address 60h)
Br
.
Table 263: BroadSync HD Class 4 Bandwidth Control Register Address Summary
Address Description
60h–61h Port 0
62h–63h Port 1
64h–65h Port 2
66h–67h Port 3
68h–69h Port 4
6Ah-6Bh Port 5
6Ch–6Dh Port 6
6Eh-6Fh Port 7
Broadcom®
April 6, 2016 • 53128-DS07-R Page 283
Table 264: BroadSync HD Class 4 Bandwidth Control Register (Page 90h: Address 60h–61h, 62h–63h,
64h–65h, 66h–67h, 68h–69h)

13:0 C4_BANDWIDTH R/W This field defines the byte count allowed for 14’h0
Class 4 traffic transmission within a slot time.
BroadSync HD Egress Time Stamp Register (Page 90h: Address 90h)

.
Table 265: BroadSync HD Egress Time Stamp Register Address Summary
Address Description
90h–93h Port 0
l
94h–97h Port 1
tia
98h–9Bh Port 2
en
9Ch–9Fh Port 3
A0h–A3h Port 4
A4h-A7h Port 5
A8h–ABh fid
Port 6
on
ACh-AFh Port 7
C
Table 266: BroadSync HD Egress Time Stamp Register (Page 90h: Address 90h–93h, 94h–97h, 98h–9Bh,
9Ch–9Fh, A0h–A3h, A4h–A7h)
om

31:0 EGRESS_TS R Egress Time Synchronous Packet Time Stamp 32’h0
dc
This field reports the time stamp of egress time synchronous

packet.
oa
It uses 32-bit time base as time stamping. The time between the
departure of first byte of MAC DA and the time stamping point
should be constant.
Br
BroadSync HD Egress Time Stamp Status Register (Page 90h:

Address D0h)
Table 267: BroadSync HD Egress Time Stamp Status Register (Page 90h: Address D0h)

7:0 VALID STATUS RO Valid Status 8’h0
8-bit field indicating the valid status for each “BroadSync HD
Egress Time Stamp Register (Page 90h: Address 90h)” on
page 284. When “BroadSync HD Egress Time Stamp Register
(Page 90h: Address 90h)” is read out by SPI, the valid status will
be cleared, respectively.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 284
BroadSync HD Link Status Register (Page 90h: Address E0h–E1h)

Table 268: BroadSync HD Link Status Register (Page 90h: Address E0h–E1h)

8:0 Port BroadSync HD Link R/W BroadSync HD Link Status 9'h0
Status When software writes the port BroadSync HD link
status and select bit 14 in LED Function Control
Register. The BroadSync HD link status is shown
on the LED.
l
tia
en
fid
on
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 285
BCM53128 Data Sheet Page 91h: Traffic Remarking Register
Page 91h: Traffic Remarking Register

Table 269: Traffic Remarking Register

00h–03h 32 “Traffic Remarking Control Register (Page 91h: Address 00h)”
10h-57h 32 “Egress Non-BroadSync HD Packet TC to PCP Mapping Register (Page 91h:
Address 10h)” on page 287
l
tia
en
Traffic Remarking Control Register (Page 91h: Address 00h)
Table 270: Traffic Remarking Control Register (Page 91h: Address 00h)
BIt Name R/W fid

Description Default
on
24:16 PCP_REMARKING_EN R/W PCP Remarking Enable 0
C
Bit 24: IMP port

Bits[23:16] correspond to ports [7:0], respectively
om

dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 286
BCM53128 Data Sheet Page 91h: Traffic Remarking Register
Egress Non-BroadSync HD Packet TC to PCP Mapping Register

(Page 91h: Address 10h)
Table 271: Egress Non-BroadSync HD Packet TC to PCP Mapping Register Address Summary
Address Description
10h-17h Port 0
18h-1Fh Port 1
20h-27h Port 2
28h-2Fh Port 3
30h-37h Port 4
38h-3Fh Port 5
40h-47h Port 6
48h-4Fh Port 7
l
tia
50h-57h IMP
en
Table 272: Egress Non-BroadSync HD Packet TC to PCP Mapping Register (Page 91h: Address 10h–
17h, 18h–1Fh, 20h–27h, 28h–2Fh, 30h–37h, 38h–3Fh, 50h-57h)
Bit Name R/W fid

Description Default
on
63:32 Reserved R/W Reserved 4'b1111
31:28 {CFI,PCP} for TC = 7 R/W The {CFI,PCP} field for TC = 7 4'b0111
C

om

dc

oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 287
BCM53128 Data Sheet Page 92h: EEE Control Register
Page 92h: EEE Control Register

Table 273: Page 92h: EEE Control Register

00h-01h 16 “EEE Enable Control Register (Page 92h: Address 00h)”
02h-03h 16 “EEE LPI Assert Register (Page 92h: Address 02h)” on page 289
04h-05h 16 “EEE LPI Indicate Register (Page 92h: Address 04h)” on page 289
06h-07h 16 “EEE RX Idle Symbol Register (Page 92h: Address 06h)” on page 289
0Ch-0Fh 32 “EEE Pipeline Timer Register (Page 92h: Address 0Ch)” on page 290
10h-30h 32 “EEE Sleep Timer Gig Register (Page 92h: Address 10h)” on page 290
34h-54h 32 “EEE Sleep Timer FE Register (Page 92h: Address 34h)” on page 291
58h-78h 32 “EEE Min LP Timer Gig Register (Page 92h: Address 58h)” on page 291
l
tia
7Ch-9Ch 32 “EEE Min LP Timer FE Register (Page 92h: Address 7Ch)” on page 292
A0h-B0h 16 “EEE Wake Timer Gig Register (Page 92h: Address A0h)” on page 292
en
B2h-C2h 16 “EEE Wake Timer FE Register (Page 92h: Address B2h)” on page 293
C4h 16 “EEE GLB Congst TH Register (Page 92h: Address C4h)” on page 293
C6h-D0h 16
fid
“EEE TXQ Cong TH Register (Page 92h: Address C6h)” on page 293
on
EEE Enable Control Register (Page 92h: Address 00h)
C
Table 274: EEE Enable Control Register (Page 92h: Address 00h)

om

8:0 EN_EEE R/W Enables EEE function per port –
dc
1 = Enable EEE
0 = Disable EEE
oa
Bit[8]: IMP port

Bits [7 :0]: Ports [7:0]
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 288
EEE LPI Assert Register (Page 92h: Address 02h)

Table 275: EEE LPI Assert Register (Page 92h: Address 02h)

8:0 LPI_Assert_Status RO Low Power assert input signal status. 0x0
1 = Low Power asserted
0 = Low Power deasserted
Bit [8]: IMP port
Bits [7:0]: Ports [7:0]
Each bit indicates that LowPowerAssert input signal
that commands the transmit MAC to generate low-
power idle symbols to the PHY after the transmit MAC
completes transmitting inprocess packet data.
l
tia
EEE LPI Indicate Register (Page 92h: Address 04h)
en
Table 276: EEE LPI Indicate Register (Page 92h: Address 04h)
Bit
15:9
Name
Reserved
R/W
RO
Description
Reserved fid Default
0x033
on
8:0 LPI_Indicate RO Low Power Indicate output signal status. 0x0
1 = Low Power Indicate asserted
C
0 = Low Power Indicate deasserted

Bit [8]: IMP port
om
Bits [7:0]: Ports [7:0]

Each bit indicates that LowPowerIndicate output
signal is asserted whenever the receive PHY is
dc
sending low-power idle symbols to the receive MAC.

oa
EEE RX Idle Symbol Register (Page 92h: Address 06h)

Br
Table 277: EEE RX Idle Symbol Register (Page 92h: Address 06h)

8:0 Rx_Idle_Symbol RO Receiving IdleSymbols output signal status. 0x0
1 = Idle Symbol output asserted
0 = Idle Symbol output deasserted
Bit [8]: IMP port
Bits [7:0]: Ports [7:0]
Each bit indicates that receiving IdleSymbols output
signal is asserted whenever the received PHY is
sending normal idle symbols to the received MAC.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 289
EEE Pipeline Timer Register (Page 92h: Address 0Ch)

Table 278: EEE Pipeline Timer Register (Page 92h: Address 0Ch)

31:0 Pipeline Timer R/W EEE pipeline delay timer load value. 0x20
The unit is system clock rate (e.g., if system clock =
100 MHz, unit = 10 nsec).
Table 279: EEE Sleep Timer Gig Register (Page 92h: Address 10h)
Address Description
10h – 13h Port 0
14h – 17h Port 1
l
18h – 1Bh Port 2
tia
1Ch – 1Fh Port 3
20h – 23h Port 4
en
24h – 27h Port 5
28h – 2Bh Port 6
2Ch – 2Fh
30h – 33h
Port 7
IMP
fid
on
C
EEE Sleep Timer Gig Register (Page 92h: Address 10h)

om
Table 280: EEE Sleep Timer Gig Register (Page 92h: Address 10h)

dc
31:0 Sleep Timer Gig R/W EEE sleep delay timer load value for 1G operation. 0x4
The unit is 1 sec.
oa
Table 281: EEE Sleep Timer FE Register (Page 92h: Address 34h)
Br
Address Description
34h – 37h Port 0
38h – 3Bh Port 1
3Ch – 3Fh Port 2
40h – 43h Port 3
44h – 47h Port 4
48h – 4Bh Port 5
4Ch – 4Fh Port 6
50h – 53h Port 7
54h – 57h IMP
Broadcom®
April 6, 2016 • 53128-DS07-R Page 290
EEE Sleep Timer FE Register (Page 92h: Address 34h)

Table 282: EEE Sleep Timer FE Register (Page 92h: Address 34h)

31:0 Sleep Timer FE R/W EEE sleep delay timer load value for 100M operation. 0x28
The unit is 1 sec.
Table 283: EEE Min LP Timer Gig Register (Page 92h: Address 58h)
Address Description
58h – 5Bh Port 0
5Ch – 5Fh Port 1
60h – 63h Port 2
l
tia
64h – 67h Port 3
68h – 6Bh Port 4
en
6Ch – 6Fh Port 5
70h – 73h Port 6
74h – 77h
78h – 7Bh
Port 7
IMP fid
on
EEE Min LP Timer Gig Register (Page 92h: Address 58h)
C
Table 284: EEE Min LP Timer Gig Register (Page 92h: Address 58h)
om

31:0 Min LP Timer G R/W EEE minimum low-power duration delay timer load 0x32
dc
value for 1G operation. The unit is 1 sec.

oa
Table 285: EEE Min LP Timer FE Register (Page 92h: Address 7Ch)
Br
Address Description
7Ch – 7Fh Port 0
80h – 83h Port 1
84h – 87h Port 2
88h – 8Bh Port 3
8Ch – 8Fh Port 4
90h – 93h Port 5
94h – 97h Port 6
98h – 9Bh Port 7
9Ch – 9Fh IMP
Broadcom®
April 6, 2016 • 53128-DS07-R Page 291
EEE Min LP Timer FE Register (Page 92h: Address 7Ch)

Table 286: EEE Min LP Timer FE Register (Page 92h: Address 7Ch)

31:0 Min LP Timer FE R/W EEE minimum low-power duration delay timer load 0x1F4
value for 100M operation. The unit is 1 sec.
Table 287: EEE Wake Timer Gig Register (Page 92h: Address A0h)
Address Description
A0h – A1h Port 0
A2h – A3h Port 1
A4h – A5h Port 2
l
A6h – A7h Port 3
tia
A8h – A9h Port 4
AAh – ABh Port 5
en
ACh – ADh Port 6
AEh – AFh Port 7
B0h – B1h IMP
fid
on
EEE Wake Timer Gig Register (Page 92h: Address A0h)
C
Table 288: EEE Wake Timer Gig Register (Page 92h: Address A0h)
om

15:0 Wake Timer Gig R/W EEE wake transition delay timer load value for 1G 0x11
operation. The unit is 1 sec.
dc
oa
Table 289: EEE Wake Timer FE Register (Page 92h: Address B2h)
Br
Address Description
B2h – B3h Port 0
B4h – B5h Port 1
B6h – B7h Port 2
B8h – B9h Port 3
BAh – BBh Port 4
BCh – BDh Port 5
BEh – BFh Port 6
C0h – C1h Port 7
C2h – C3h IMP
Broadcom®
April 6, 2016 • 53128-DS07-R Page 292
EEE Wake Timer FE Register (Page 92h: Address B2h)

Table 290: EEE Wake Timer FE Register (Page 92h: Address B2h)

15:0 Wake Timer FE R/W EEE wake transition delay timer load value for 100M 0x24
operation. The unit is 1 sec.
EEE GLB Congst TH Register (Page 92h: Address C4h)

Table 291: EEE GLB Congst TH Register (Page 92h: Address C4h)

10:0 GLB_CONG_TH R/W EEE Global packet buffer congestion threshold. If this 0x1a0
l
tia
threshold is set to zero, then EEE is effectively
disabled. If this threshold is set equal to or greater
than 768 (the number of cells implemented in the
en
packet buffer), then protections against packet loss
are disable.
fid
The unit is “Buffer Cell Size”: 256-byte cell.
on
Table 292: EEE TXQ CONG TH Register (Page 92h: Address C6h)
C
Address Description
C6h C7hEEE TXQ 0 CONG TH Register
om
C8h C9hEEE TXQ 1 CONG TH Register

CAh CBhEEE TXQ 2 CONG TH Register
CCh CDhEEE TXQ 3 CONG TH Register
dc
CEh CFhEEE TXQ 4 CONG TH Register

D0h D1hEEE TXQ 5 CONG TH Register
oa
Br
EEE TXQ Cong TH Register (Page 92h: Address C6h)

Table 293: EEE TXQ Cong TH Register (Page 92h: Address C6h)

Broadcom®
April 6, 2016 • 53128-DS07-R Page 293
Table 293: EEE TXQ Cong TH Register (Page 92h: Address C6h)

10:0 GLB_CONG_TH R/W EEE TXQ packet buffer congestion threshold.
• If this threshold is set to zero, then EEE for queue
N is effectively disabled.
• If this threshold is set equal to or greater than 768
(the number of cells implemented in the packet
buffer), then protections against packet loss are
disabled.
The unit is “Buffer Cell Size”: 256-byte cell.
EEE TXQ0: 0x64
EEE TXQ1: 0x64
EEE TXQ2: 0x64
EEE TXQ3: 0x1
EEE TXQ4: 0x1
l
tia
EEE TXQ5: 0x1
en
fid
on
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 294
BCM53128 Data Sheet Global Registers
Global Registers
Table 294: Global Registers (Maps to All Pages)

F0h 8 “SPI Data I/O Register (Global, Address F0h)”, 0
F1h 8 “SPI Data I/O Register (Global, Address F0h)”, 1
F2h 8 “SPI Data I/O Register (Global, Address F0h)” on page 295, 2
l
tia
F8–FDh – Reserved
en
SPI Data I/O Register (Global, Address F0h)

fid
on
Table 295: SPI Data I/O Register (Maps to All Registers, Address F0h–F7h)

C
7:0 SPI Data I/O R/W SPI data bytes [7:0] 0

om
SPI Status Register (Global, Address FEh)

dc
Table 296: SPI Status Register (Maps to All Registers, Address FEh)
oa

7 SPIF RO SPI read/write complete flag 0
Br
5 RACK RO SPI read data ready acknowledgement (self-clearing) 0
(SC)
Broadcom®
April 6, 2016 • 53128-DS07-R Page 295
BCM53128 Data Sheet Global Registers
Page Register (Global, Address FFh)

Table 297: Page Register (Maps to All Registers, Address FFh)

7:0 PAGE_REG R/W The binary value determines the value of the accessed 0
register page.
l
tia
en
fid
on
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 296
BCM53128 Data Sheet Electrical Characteristics
Section 8: Electrical Characteristics
Absolute Maximum Ratings

Table 298: Absolute Maximum Ratings
Symbol Parameter and Pins Minimum Maximum Units

– Supply voltage: PLL_AVDD, DVDD, AVDDL GND–0.3 1.32 V
– Supply voltage: OVDD2, AVDDH, OVDD, XTAL_AVDD GND–0.3 3.63 V
II Input current – – mA
TSTG Storage temperature –40 +125 C
l
VESD Electrostatic discharge – 2000 V
tia
– Input voltage: digital input pins – – V
en
Note: These specifications indicate levels where permanent damage to the device may occur. Functional
operation is not guaranteed under these conditions. Operation at absolute maximum conditions for extended
periods may adversely affect long-term reliability of the device.
fid
on
Recommended Operating Conditions
C
Table 299: Recommended Operating Conditions

om
Symbol Parameter Pins Minimum Maximum Units

VDD Supply voltage AVDDL, DVDD, PLL_AVDD 1.14 1.26 V
dc
OVDD2, AVDDH, XTAL_AVDD 3.14 3.47 V

– – – V
oa
– – – V
VIH High-level input voltage All digital inputs 2.0 – V
Br
VIL Low-level input voltage All digital inputs – 0.8 V

TA Ambient operating – 0 70 C
temperature
Broadcom®
April 6, 2016 • 53128-DS07-R Page 297
BCM53128 Data Sheet Electrical Characteristics
Electrical Characteristics
Table 300: Electrical Characteristics
Symbo
l Parameter Pins Conditions Minimum Typical Maximum Units
IDD Maximum supply 1.2V power rail Estimated – 1130 – mA
current (for GMII/ 3.3V power rail Estimated – 496 – mA
RvMII/MII OVDD (3.3V for GMII/ Estimated – 36 – mA
operation) RvMII/MII)
IDD Maximum supply 1.2V power rail Estimated – 1130 – mA
current (for RGMII 3.3V power rail Estimated – 496 – mA
operation) 2.5V power rail Estimated – 26 – mA
1.5V power rail – – – – mA
l
tia
VOH High-level Digital output pins at 3.3V IOH = 8 mA 2.1 – – V
output voltage
Digital output pins at 2.5V IOH = 8 mA 2.0 – – V
en
Digital output pins at 1.5V IOH = 8 mA 1.1 – – V
VOL Low-level Digital output pins at 3.3V IOL = 8 mA – – 0.5 V
output voltage
fid
Digital output pins at 2.5V IOL = 8 mA – – 0.4 V
on
Digital output pins at 1.5V IOL = 8 mA – – 0.4 V
VIH High-level Digital input pins at 3.3V – 1.7 – – V
C
input voltage and 2.5V

Digital input pins at 1.5V – 0.85 – – V
om
XTALI – 2.0 – – V
VIL Low-level Digital input pins at 3.3V – – – 0.9 V
input voltage Digital input pins at 2.5V – – – 0.7 V
dc
Digital input pins at 1.5V – – – 0.65 V

XTALI – – – 0.8 V
oa
II Input current Digital inputs – – – – µA

w/ pull-up resistors
Br
Digital inputs – – – – µA
w/ pull-up resistors
w/ pull-down resistors
w/ pull-down resistors
All other digital inputs – – – – µA
Broadcom®
April 6, 2016 • 53128-DS07-R Page 298
BCM53128 Data Sheet Timing Characteristics
Section 9: Timing Characteristics
Reset and Clock Timing

Figure 49: Reset and Clock Timing
Power
t104 t106
Rails
t101 t103
XTALI
t102
t107 t108
l
tia
RESET
t105
t109
en
Configuration
Strap Signals Valid
fid
on
Table 301: Reset and Clock Timing
Description Parameter Minimum Typical Maximum

C
XTALI period t101 39.998 ns 40 ns 40.002 ns

om
XTALI high time t102 18 ns – 22 ns

XTALI low time t103 18 ns – 22 ns
RESET low pulse duration t104 80 ms 100 ms –
dc
RESET rise time t105 – – 25 ns

Configuration valid setup to RESET rising t107 100 ns – –
oa
Configuration valid hold from RESET rising t108 – – 100 ns

Hardware initialization is complete. All the strap pin t109 5 ms before the registers can be accessed
Br
values are clocked in, and the internal registers can

be accessed.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 299
BCM53128 Data Sheet MII Interface Timing
MII Interface Timing

The following specifies timing information regarding the MII Interface pins.
MII Input Timing

Figure 50: MII Input
t402
t401 t403 t404
RXC
(Input)
RXDV
l
tia
RXD
en
Parameter Description
fid
Table 302: MII Input Timing
Min Typ Max

on
t401 RXDV, RXD, to RXC rising setup time 10 ns – –
t402 RXC clock period (10BASE-T mode) – 400 ns –
C
RXC clock period (100BASE-TX mode) – 40 ns –

om
t403 RXC high/low time (10BASE-T mode) 160 ns – 240 ns

RXC high/low time (100BASE-TX mode) 16 ns – 24 ns
t404 RXDV, RXD, to RXC rising hold time 10 ns – –
dc
– Duty cycle – – –
oa
MII Output Timing

Br
Figure 51: MII Output Timing
t406
t405
TXC
OpP
TXEN
TXD
Broadcom®
April 6, 2016 • 53128-DS07-R Page 300
BCM53128 Data Sheet TMII Interface Timing
Table 303: MII Output Timing
Parameter Description Min Typ Max

t405 TXC high to TXEN, TXD valid 0 ns – 25 ns
t406 TXC high to TXEN, TXD invalid (hold) 0 ns – –
TMII Interface Timing

The following specifies timing information regarding the TMII Interface pins.
TMII Input Timing
l
Figure 52: TMII Input
tia
en
t402
t401 t403 t404
RXC
(Input)
fid
on
RXDV
RXD
C
om
Table 304: TMII Input Timing

dc
t401 RXDV, RXD, to RXC rising setup time 5 ns – –

oa
t402 RXC clock period (100BASE-TX mode) – 20 ns –

t403 RXC high/low time (100BASE-TX mode) 8 ns – 12 ns
Br
t404 RXDV, RXD, to RXC rising hold time 5 ns – –

– Duty cycle – – –
Broadcom®
April 6, 2016 • 53128-DS07-R Page 301
BCM53128 Data Sheet Reverse MII/TMII Interface Timing
TMII Output Timing

Figure 53: TMII Output Timing
t406
t405
TXC
OpP
TXEN
TXD
l
tia
Table 305: TMII Output Timing
en
t405 TXC high to TXEN, TXD valid 0 ns – 12.5 ns
t406 TXC high to TXEN, TXD invalid (hold) 0 ns – –
fid
on
Reverse MII/TMII Interface Timing
C
The following specifies timing information regarding the Reverse MII/TMII Interface pins.
om
Reverse MII/TMII Input Timing

dc
Figure 54: Reverse MII Input Timing

oa
t402y
t404y
Br
t401y t403y
RXC
(Output )
RXDV
RXD
Table 306: Reverse MII Input Timing
Description Parameter Min Typ Max Units

RXDV, RXD to RXC rising setup time t401R 10 – – ns
Broadcom®
April 6, 2016 • 53128-DS07-R Page 302
BCM53128 Data Sheet Reverse MII/TMII Interface Timing
Table 306: Reverse MII Input Timing

RXC (output) clock period (10BASE-T mode) t402R – 400 – ns
RXC clock period (100BASE-TX mode) – 40 – ns
RXC high/low time (10BASE-T mode) t403R 160 – 240 ns
RXC high/low time (100BASE-TX mode) 16 – 24 ns
RXDV, RXD to RXC rising hold time t404R 0 – – ns
Table 307: Reverse TMII Input Timing

RXDV, RXD to RXC rising setup time t401R 7.5 – – ns
RXC (output) clock period t402R – 20 – ns
l
tia
RXC high/low time (10BASE-T mode) t403R 8 – 12 ns
RXDV, RXD to RXC rising hold time t404R 0 – – ns
en
Reverse MII Output Timing
fid
Figure 55: Reverse MII Output Timing
on
t405 R t407 R
C
t408 R t406R
TXC
(Output )
om
TXEN
dc
TXD
oa
Br
Table 308: Reverse MII Output Timing

Output (TXD, TX_EN) setup to TXC rising t405R 15 – 25 ns
Output (TXD, TX_EN) hold from TXC rising t406R 11 – – ns
TXC clock period t407R – 40 – ns
TXC high/low time t408R 15 – 22 ns
Table 309: Reverse TMII Output Timing

Output (TXD, TX_EN) setup to TXC rising t405R 5 – – ns
Broadcom®
April 6, 2016 • 53128-DS07-R Page 303
BCM53128 Data Sheet RGMII Interface Timing
Table 309: Reverse TMII Output Timing

Output (TXD, TX_EN) hold from TXC rising t406R 5 – – ns
TXC clock period t407R – 20 – ns
TXC high/low time t408R 7.5 – 11 ns
RGMII Interface Timing

The following specifies timing information regarding the IMP interface pins when configured in RGMII mode.
RGMII Output Timing (Normal Mode)
l
tia
Figure 56: RGMII Output Timing (Normal Mode)
en
GTX_CLK
(at source)
fid
on
TXD [3:0]
TX_CTL
C
t201 t201
om
Table 310: RGMII Output Timing (Normal Mode)

dc

oa
GTX_CLK clock period (1000M mode) – 7.2 8 8.8 ns

GTX_CLK clock period (100M mode) – 36 40 44 ns
Br

TskewT: data to clock output skew t201 –500 (1000M) 0 +500 (1000M) ps
Duty cycle for 1000M (GE) – 45 50 55 %
Duty cycle for 10/100M (FE) – 40 50 60 %
Note: The output timing in 10/100M operation is always as specified in the delayed mode.
Broadcom®
April 6, 2016 • 53128-DS07-R Page 304
RGMII Output Timing (Delayed Mode)

RGMII output timing defaults to the delayed mode when the TXC_DELAY pin is pulled high at power-on reset.
Figure 57: RGMII Output Timing (Delayed Mode)
GTX_CLK
(internal)
Delayed
GTX_CLK
(actual output
at source)
t201D t202D
TXD [3:0]
l
TX_CTRL
tia
t202D
t201D
en
fid
Table 311: RGMII Output Timing (Delayed Mode)
on
C

om
TsetupT t201D 1.2 2.0 – ns

Data valid to clock transition: (all speeds)
dc
Available setup time at the output source (delayed

mode)
TholdT t202D 1.2 2.0 – ns
oa
Clock transition to data valid:

Available hold time at the output source (delayed
Br
mode)
Broadcom®
April 6, 2016 • 53128-DS07-R Page 305
RGMII Input Timing (Normal Mode)

Figure 58: RGMII Input Timing (Normal Mode)
RXCLK
t301 t302
t302 t301
RXD[3:0]
RX_CTRL
Table 312: RGMII Input Timing (Normal Mode)
l
tia
en
RXCLK clock period (1000M mode) – 7.2 8 8.8 ns
RXCLK clock period (100M mode) – 36 40 44 ns
RXCLK clock period (10M mode)
TsetupR
Input setup time: valid data to clock
–
t301 fid 360
1.0
400
2.0
440
–
ns
ns
on
TholdR t302 1.0 2.0 – ns
Input hold time: clock to valid data
C

om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 306
RGMII Input Timing (Delayed Mode)

RGMII Input Timing defaults to the delayed mode when the RXC_DELAY pin is pulled high at power-on reset.
Figure 59: RGMII Input Timing (Delayed Mode)
R XCLK
Delayed RXCLK
(Actual destination) t302D
t302D
t301D
RXD [3:0]
l
RX_CTRL
tia
t301D
en
Table 313: RGMII Input Timing (Delayed Mode)
Description Parameterfid Min Typ Max Units

on
TsetupR t301D –1.0 (1000M) – – ns
Input setup time (delayed mode) –1.0 (10/100M) – – ns
C
TholdR t302D 3.0 (1000M) – – ns

Input hold time (delayed mode) 9.0 (10/100M) – – ns
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 307
BCM53128 Data Sheet GMII Interface Timing
GMII Interface Timing

The following specifies timing information regarding the IMP interface pins when configured in GMII mode.
GMII Interface Output Timing

Figure 60: GMII Output Timings
t 502
GTX_CLK
TXEN
t501
l
tia
TXD
en
fid
Table 314: GMII Output Timing
on
C
Output (TXD, TX_EN) setup to GTX_CLK t501 2.5 – – ns

rising
om
Output (TXD, TX_EN) hold from GTX_CLK t502 0.5 – 5.5 ns

rising
dc
GMII Interface Input Timing

oa
Figure 61: GMII Input Timings

Br
t503
t504
RXCLK
RXDV
RXD
Broadcom®
April 6, 2016 • 53128-DS07-R Page 308
BCM53128 Data Sheet MDC/MDIO Timing
Table 315: GMII Input Timing

RXCLK clock period (1000M mode) – – 8 – ns
(RXD, RX_DV) Setup to RX_CLK rising t503 2.0 – – ns
(RXD, RX_DV) Hold from RX_CLK t504 0.0 – – ns
rising
MDC/MDIO Timing
The following specifies timing information regarding the MDC/MDIO interface pins.
Figure 62: MDC/MDIO Timing (Slave Mode)
l
tia
t401 t402
en
MDC
t402
MDIO
(Into PHY)
t403
fid
on
t404
C
MDIO
(From PHY)
om
t405
dc
Table 316: MDC/MDIO Timing (Slave Mode)

oa
Description Parameter Minimum Typical Maximum Unit

MDC cycle time t401 80 – – ns
Br
MDC high/low – 30 – – ns
MDC rise/fall time t402 – – 10 ns
MDIO input setup time to MDC rising t403 7.5 – – ns
MDIO input hold time from MDC rising t404 7.5 – – ns
MDIO output delay from MDC rising t405 0 – 45 ns
Table 317: MDC/MDIO Timing (Master Mode)

MDC cycle time t401 400 – – ns
MDC high/low – 160 – 240 ns
Broadcom®
April 6, 2016 • 53128-DS07-R Page 309
BCM53128 Data Sheet Serial LED Interface Timing
Table 317: MDC/MDIO Timing (Master Mode)

MDC rise/fall time t402 – – 10 ns
MDIO input setup time to MDC rising t403 80 – – ns
MDIO input hold time from MDC rising t404 0 – – ns
MDIO output delay from MDC rising t405 15 – 90 ns
Serial LED Interface Timing

The following specifies timing information regarding the LED interface pins.
Figure 63: Serial LED Interface Timing
l
tia
t301
t302
en
t304
t303
LEDCLK fid
on
LEDDATA S0 S1 S2 SN S0
C
t305
om
Table 318: Serial LED Interface Timing

dc

LED update cycle period t301 – 42 – ms
oa
LEDCLK period t302 – 320 – ns

LEDCLK high-pulse width t303 150 – 170 ns
Br
LEDCLK low-pulse width t304 150 – 170 ns

LEDCLK to LEDDATA output time t305 140 – 180 ns
Broadcom®
April 6, 2016 • 53128-DS07-R Page 310
BCM53128 Data Sheet SPI Timings
SPI Timings
Figure 64: SPI Timings, SS Asserted During SCK High
t601
t603 t604
t602
SCK
t608 = 20 ns
SS t607 = 10 ns
MOSI
l
t605 t606
tia
MISO
en
fid
Note: Advanced timing extracted from statistical data. It may or may not reflect the true timing of the
device.
on
C
Table 319: SPI Timings

om

SCK clock period t601 40 ns 500 ns –
SCK high/low time t602 20 ns – –
dc
MOSI to SCK setup time t603 5 ns – –

MOSI to SCK hold time t604 5 ns – –
oa
SCK to MISO valid t605 – – 13 ns

/SS to MISO invalid t606 – – 10 ns
Br
Time interval from assert of /SS to t607 10 ns – –

beginning the operation of SCK
Time interval from operation end of SCK to t608 20 ns – –
de-assert of /SS
Broadcom®
April 6, 2016 • 53128-DS07-R Page 311
BCM53128 Data Sheet EEPROM Timing
EEPROM Timing
Figure 65: EEPROM Timing
t701
t702
SCK
SS t703 t704
MISO
t705 t706
l
MOSI
tia
en
Table 320: EEPROM Timing
Description Parameter
fid
Minimum Typical Maximum
on
SCK clock frequency t701 – 200 kHz –
SCK high/low time t702 – 2.5 s –
C
MISO to SCK rising setup time t703 50 ns – –

MISO to SCK rising hold time t704 10 ns – –
om
SCK low to SS, MOSI valid time t705 30 ns – 100 ns

SCK low to SS, MOSI invalid time t706 30 ns – –
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 312
BCM53128 Data Sheet Serial Flash Timing
Serial Flash Timing

Figure 66: Serial Flash Timing
l
tia
en
fid
on
C
om
Table 321: Serial Flash Timing

dc
FSCLK clock frequency t801 – 22.72 MHz 50 MHz

FSI to FSCLK rising setup time t802 10 ns – –
oa
FSI to FSCLK rising hold time t803 0 ns – –

FSCLK to FSO delay t804 5 ns – FSCLK cycle
Br
time - 5 ns
The falling edge of FCSB to first rising edge t805 5 ns – –
of FSCLK
The last rising edge of FSCLK to rising edge t806 5 ns – –
of FCSB
Broadcom®
April 6, 2016 • 53128-DS07-R Page 313
BCM53128 Data Sheet Thermal Characteristics
Section 10: Thermal Characteristics
Note: The maximum allowed junction temperature is 125 ºC. Table 322 and Table 323 on page 314
show the estimated junction temperature with heat sink.
Table 322: BCM53128KQLE Package without Heat Sink, 4-Layer Board, P = 3.1W
Device power dissipation, P (W) 3.1

Ambient air temperature Ta (ºC) 70
JA is still air (ºC/W) 17.48
JB (ºC/W) 0.98
l
tia
JC (ºC/W) 14.12
Package Thermal Performance Data
en
Air Velocity TJ_max TT JA ȞJT ȞJB
m/s
0
ft/min
0
(ºC)
124.19
(ºC)
122.86 fid
(ºC/W)
17.48
(ºC/W)
0.43
(ºC/W)
9.35
on
0.508 100 118.59 117.26 15.67 0.43 9.38
1.016 200 115.70 114.25 14.74 0.47 9.44
C
2.032 400 112.74 111.07 13.79 0.54 9.46

3.048 600 111.10 109.01 13.26 0.68 9.40
om
Table 323: BCM53128KQLE Package with Heat Sink, 2-Layer Board, P = 3.1W
dc

oa

Br
JB (ºC/W) 0.98
JC (ºC/W) 14.12
External heat sink Heat sink: 28 mm x 28 mm x 15 mm, k = 180 (W/m*k), aluminium blade-fin.
Thermal interface: Loctite 384, 0.1 mm thick, k = 0.757 W/m-k
m/s ft/min (ºC) (ºC) (ºC/W) (ºC/W) (ºC/W)

0 0 120.29 96.93 16.22 7.53 10.10
0.508 100 112.94 88.80 13.85 7.79 9.89
1.016 200 111.07 86.80 13.25 7.83 9.85
2.032 400 109.30 85.00 12.68 7.84 9.85
Broadcom®
April 6, 2016 • 53128-DS07-R Page 314
BCM53128 Data Sheet Thermal Characteristics
Table 323: BCM53128KQLE Package with Heat Sink, 2-Layer Board, P = 3.1W
3.048 600 108.40 84.00 12.39 7.87 9.82
Table 324: BCM53128IQLE Package with Heat Sink, 4-layer Board, P=3.1W

JB (ºC/W) 0.98
JC (ºC/W) 14.12
External heat sink Heat sink: 28 mm x 28 mm x 15 mm, k = 180 (W/m*k), aluminium blade-fin.
Thermal interface: Loctite 384, 0.1 mm thick, k = 0.757 W/m-k
l
tia
m/s ft/min (ºC) (ºC) (ºC/W) (ºC/W) (ºC/W)
en
0 0 124.07 106.76 12.6 5.58 7.16
0.508 100 118.36 100.33 10.76 5.81 7.03
1.016
2.032
200
400
116.69
114.97
98.55
96.84
fid
10.22
9.67
5.85
5.85
7.03
7.03
on
3.048 600 114.25 96.12 9.43 5.85 7.02
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 315
BCM53128 Data Sheet Mechanical Information
Section 11: Mechanical Information

Figure 67: BCM53128 Mechanical Specifications
l
tia
en
fid
on
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 316
BCM53128 Data Sheet Ordering Information
Section 12: Ordering Information
Table 325: Ordering Information
Part Number Package Ambient Temperature

BCM53128KQLE(G) 256 eLQFP 0°C to 70°C
BCM53128IQLE(G) 256 eLQFP –45°C to 85°C
Note: (G) represents the lead-free package option.
l
tia
en
fid
on
C
om
dc
oa
Br
Broadcom®
April 6, 2016 • 53128-DS07-R Page 317
BCM53128 Data Sheet
l
tia
en
fid
on
C
om
dc
oa
Br
Broadcom® reserves the right to make changes without further notice to any products or data herein to improve reliability,
function, or design.
Information furnished by Broadcom is believed to be accurate and reliable. However, Broadcom does not assume any liability
arising out of the application or use of this information, nor the application or use of any product or circuit described herein,
neither does it convey any license under its patent rights nor the rights of others.
Broadcom
Web: www.broadcom.com
Corporate Headquarters: San Jose, CA
© 2016 by Broadcom. All rights reserved.
53128-DS07-R April 6, 2016

BCM53128

Uploaded by

Copyright:

BCM53128

Uploaded by

Document Information

Copyright

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

BCM53128

Uploaded by

Copyright:

Data Sheet

and gateways. • Double tagging/QinQ

1000BASE-TX Ethernet transceivers. support

port. and backpressure, with IEEE 802.1x support for

in a 256-pin eLQFP (28 mm x 28 mm) package. 8051 processor

Corporate Headquarters: San Jose, CA April 6, 2016

© 2016 by Broadcom. All rights reserved.

Change Description Customer Impact Action Items

page 318 part number

Table 132 on page 200.

Change Description Customer Impact Action Items

Set Using the PseudoPHY (PHYAD = to Write Register 27.

00h),” on page 145 B8h-BFh to table.

Change Description Customer Impact Action Items

• Section 11: “Mechanical Information,” on Correct editing errors. No action required.

Document Number Date Change Description

53128-DS01-R 04/02/10 Updated:

• Section 6: “Pin Assignment,” on page 137.

• Section 9: “Timing Characteristics,” on page 298.

BroadSync HD Frame .................................................................................................................... 37

Queuing Class (COS) Determination .................................................................................................... 37

IEEE 802.1Q VLAN Table Organization................................................................................................ 39

Programming the VLAN Table................................................................................................................... 40

ISP Port ................................................................................................................................................. 42

Bucket Bit Rate...................................................................................................................................... 47

BroadSync HD Class 5 Media Traffic............................................................................................. 54

Address Management ................................................................................................................................ 57

Address Learning .................................................................................................................................. 59

Unicast Addresses ......................................................................................................................... 59

Power Savings Modes................................................................................................................................ 65

Analog-to-Digital Converter ................................................................................................................... 72

Baseline Wander Correction ................................................................................................................. 73

Stream Cipher ....................................................................................................................................... 73

Automatic MDI Crossover ..................................................................................................................... 74

Resetting the PHY................................................................................................................................. 75

In-Band Management Port .................................................................................................................... 79

TMII (Turbo MII) and RvTMII (Reverse TMII) Interface......................................................................... 93

GMII Port ............................................................................................................................................... 94

Configuration Pins ..................................................................................................................................... 94

Serial Flash Interface ............................................................................................................................ 95

SPI-Compatible Programming Interface................................................................................................ 96

EEPROM Interface.............................................................................................................................. 110

LED Refresh Register (Page 00h: Address 0Fh) ................................................................................ 149

LED Function 1 Control Register (Page 00h: Address 12h)................................................................ 151

LED Enable Map Register (Page 00h: Address 16h–17h).................................................................. 152

Duplex Status Summary (Page 01h: Address 08h)............................................................................. 166

Page 02h: Management/Mirroring Registers ......................................................................................... 168

IMP Port ID Register (Page 02h: Address 01h) .................................................................................. 169

Page 10h–17h: Internal GPHY MII Registers.......................................................................................... 194

MII Status Register (Page 10h–17h: Address 02h)............................................................................. 197

Master/Slave Configuration Enable.............................................................................................. 205

External Loopback ....................................................................................................................... 213

Edge Rate Control (1000BASE-T) ............................................................................................... 214

Shadow Register Select............................................................................................................... 214

Power/MII Control Register (Page 10h–17h: Address 30h) ................................................................ 215

Shadow Register Select............................................................................................................... 216

Mode Control Register (Page 10h–17h: Address 38h) ....................................................................... 225

CPU_To_COS Map Register (Page 30h: Address 64h–67h) ............................................................. 242

TX Queue Weight Register (Page 30h: Address 81h) ........................................................................ 243

Page 31h: Port-Based VLAN Registers .................................................................................................. 245

Page 32h: Trunking Registers................................................................................................................. 246

EAP Destination IP Register 1 (Page 42h: Address 0Ah) ................................................................... 270

Page 43h: MSPT Register ........................................................................................................................ 272

Electrical Characteristics......................................................................................................................... 298