ZL50404
Lightly Managed/Unmanaged
5-Port 10/100M Ethernet Switch
Data Sheet
Features
•
•
•
•
•
August 2004
Integrated Single-Chip 10/100 Ethernet Switch
• Four 10/100 Mbps auto-negotiating Fast
Ethernet (FE) ports with RMII, MII, GPSI,
Reverse MII & Reverse GPSI interface options
• One 10/100 Mbps auto-negotiating port with
MII interface option, that can be used as a
WAN uplink or as a 9th port
Embedded 2 Mbits (256 KBytes) internal memory
• supports up to 4 K byte frames
L2 switching
• MAC address self learning, up to 4 K MAC
addresses using internal table
• Supports the following spanning standards
- IEEE 802.1D spanning tree
- IEEE 802.1w rapid spanning tree
• Supports Ethernet multicasting and
broadcasting and flooding control
VLAN Support
• Supports port-based VLAN
CPU access supports the following interface
options:
• Serial interface in lightly managed mode, or in
unmanaged mode with optional I2C EEPROM
interface
C
P
U
Serial
Ordering Information
ZL50404GDC
-40°C to +85°C
•
•
Failover Features
• Rapid link failure detection using
hardware-generated heartbeat packets
• link failover in less than 50 ms
Rate Control (both ingress and egress)
• Bandwidth rationing, Bandwidth on demand,
SLA (Service Level Agreement)
• Smooth out traffic to uplink port
• Ingress Rate Control
- Back pressure
- Flow Control
- WRED (Weighted Random Early Discard)
• Egress Rate Control
• Down to 16 kbps Rate Control granularity
ZL50404
MII
5-Port 10/100M
Ethernet Switch
EEPROM
208 Pin LBGΑ
10/100
PHY
I2C
RMII / MII / GPSI
Quad
10/100
PHY
Figure 1 - System Block Diagram
1
Zarlink Semiconductor Inc.
Zarlink, ZL and the Zarlink Semiconductor logo are trademarks of Zarlink Semiconductor Inc.
Copyright 2003-2004, Zarlink Semiconductor Inc. All Rights Reserved.
ZL50404
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Data Sheet
Per queue traffic shaper on uplink port
Packet Filtering and Port Security
• Static address filtering for source and/or destination MAC
• Static MAC address not subject to aging
• Secure mode freezes MAC address learning (each port may independently use this mode)
• Supports port authentication (IEEE 802.1x)
QoS Support
• Supports IEEE 802.1p/Q Quality of Service with 2 transmission priority queues (4 for uplink port), with
strict priority and/or WFQ service disciplines
• Provides 2 levels of dropping precedence with WRED mechanism
• User controls the WRED thresholds.
• Buffer management: per class and per port buffer reservations
• Port-based priority: VLAN priority in a tagged frame can be overwritten by the priority of Port VLAN ID
Supports per-system option to enable flow control for best effort frames even on QoS enabled ports
Classification based on:
• Port based priority
• VLAN Priority field in VLAN tagged frame
• DS/TOS field in IP packet
• UDP/TCP logical ports: 8 hard-wired and 8 programmable ports, including one programmable range
The precedence of the above classifications is programmable
Supports IEEE 802.3ad link aggregation
• 8 groups of up to 4 ports per group
• Supports load sharing among trunked ports based on:
- Source port
- Source and/or destination MAC address
Supports module hot swap on all ports
MIB Statistics counters for all ports
Full Duplex Ethernet IEEE 802.3x Flow Control
Backpressure flow control for Half Duplex ports
Hardware auto-negotiation through MII management interface (MDIO) for Ethernet ports
Built-in reset logic triggered by system malfunction
Built-In Self Test for internal SRAM
IEEE-1149.1 (JTAG) test port
2
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
Description
The ZL50404 is a low density, low cost, high performance, non-blocking Ethernet switch chip. A single chip
provides 4 ports at 10/100 Mbps, 1 uplink port at 10/100 Mbps, and a CPU interface for lightly managed and
unmanaged switch applications. The chip supports up to 4 K MAC addresses and port-based Virtual LANs
(VLANs).
With strict priority and/or WFQ transmission scheduling and WRED dropping schemes, the ZL50404 provides
powerful QoS functions for various multimedia and mission-critical applications. The chip provides 2 transmission
priorities (4 priorities for uplink port) and 2 levels of dropping precedence. Each packet is assigned a transmission
priority and dropping precedence based on the VLAN priority field in a VLAN tagged frame, or the DS/TOS field, or
the UDP/TCP logical port fields in IP packets. The ZL50404 recognizes a total of 16 UDP/TCP logical ports, 8
hard-wired and 8 programmable (including one programmable range).
The ZL50404 provides the ability to monitor a link, detect a simple link failure, and provide notification of the failure
to the CPU. The CPU can then failover that link to an alternate link.
The ZL50404 supports 8 groups of port trunking/load sharing. Each group can contain up to 4 ports. Port
trunking/load sharing can be used to group ports between interlinked switches to increase the effective network
bandwidth.
In half-duplex mode, all ports support backpressure flow control, to minimize the risk of losing data during long
activity bursts. In full-duplex mode, IEEE 802.3x flow control is provided. The ZL50404 also supports a per-system
option to enable flow control for best effort frames, even on QoS-enabled ports.
Statistical information for SNMP and the Remote Monitoring Management Information Base (RMON MIB) are
collected independently for all ports. Access to these statistical counters/registers is provided via the CPU interface.
SNMP Management frames can be received and transmitted via the CPU interface, creating a complete network
management solution.
The ZL50404 is fabricated using 0.18 micron technology. The ZL50404 is packaged in a 208-pin Ball Grid Array
package.
3
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
Table of Contents
1.0 BGA and Ball Signal Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1 BGA Views (Top-View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Power and Ground Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3 Ball Signal Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4 Signal Mapping and Internal Pull Up/Down Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.5 Bootstrap Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.0 Block Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.1 Internal Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.2 MAC Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.2.1 RMII MAC Module (RMAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.2.2 CPU MAC Module (CMAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2.3 MII MAC Module (MMAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2.4 PHY Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.3 Management Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.4 Frame Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.5 Search Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.6 Heartbeat Packet Generation and Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.7 Timeout Reset Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.8 JTAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.0 Management and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.1 Register Configuration, Frame Transmission, and Frame Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1.1 Register Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1.2 Rx/Tx of Standard Ethernet Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.1.3 Control Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.2 I2C Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.2.1 Start Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.2.2 Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.2.3 Data Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.2.4 Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.2.5 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.2.6 Stop Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.3 Synchronous Serial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.3.1 Write Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.3.2 Read Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.0 Data Forwarding Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.1 Unicast Data Frame Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2 Multicast Data Frame Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.3 Frame Forwarding To and From CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.0 Search Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.1 Search Engine Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.2 Basic Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.3 Search, Learning, and Aging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.3.1 MAC Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.3.2 Learning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.3.3 Aging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.4 MAC Address Filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.5 Protocol Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.6 Logical Port Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.7 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.8 Priority Classification Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.9 Port Based VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.0 Frame Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
Table of Contents
6.1 Data Forwarding Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.2 Frame Engine Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.2.1 FCB Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.2.2 Rx Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.2.3 RxDMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.2.4 TxQ Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.2.5 Port Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.2.6 TxDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.0 Quality of Service and Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.1 Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.2 Two QoS Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
7.2.1 Strict Priority. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
7.2.2 Weighted Fair Queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
7.3 WRED Drop Threshold Management Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
7.4 Shaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
7.5 Rate Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.6 Buffer Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
7.6.1 Dropping When Buffers Are Scarce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.7 Flow Control Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.7.1 Unicast Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.7.2 Multicast Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.8 Mapping to IETF Diffserv Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.9 Failover Backplane Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
8.0 Port Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
8.1 Features and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
8.2 Unicast Packet Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
8.3 Multicast Packet Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
9.0 Traffic Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
9.1 Mirroring Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
9.2 Using port mirroring for loop back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
10.0 GPSI (7WS) Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
10.1 GPSI connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
11.0 Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
11.1 Clock Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
11.1.1 System Clock (SCLK) speed requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
11.1.2 RMAC Reference Clock (M_CLK) speed requirement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
11.1.3 MMAC Reference Clock (REF_CLK) speed requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
11.1.4 JTAG Test Clock (TCK) speed requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
11.2 Clock Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
11.2.1 MDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
11.2.2 SCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
11.2.3 Ethernet Interface Clocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
12.0 Hardware Statistics Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
12.1 Hardware Statistics Counters List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
12.2 IEEE 802.3 HUB Management (RFC 1516) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
12.2.1 Event Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
12.2.1.1 ReadableOctet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
12.2.1.2 ReadableFrame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
12.2.1.3 FCSErrors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
12.2.1.4 AlignmentErrors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
12.2.1.5 FrameTooLongs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
Table of Contents
12.2.1.6 ShortEvents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
12.2.1.7 Runts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
12.2.1.8 Collisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
12.2.1.9 LateEvents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
12.2.1.10 VeryLongEvents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
12.2.1.11 DataRateMisatches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
12.2.1.12 AutoPartitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
12.2.1.13 TotalErrors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
12.3 IEEE 802.1 Bridge Management (RFC 1286) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
12.3.1 Event Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
12.3.1.1 InFrames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
12.3.1.2 OutFrames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
12.3.1.3 InDiscards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
12.3.1.4 DelayExceededDiscards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
12.3.1.5 MtuExceededDiscards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
12.4 RMON – Ethernet Statistic Group (RFC 1757) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
12.4.1 Event Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
12.4.1.1 Drop Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
12.4.1.2 Octets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
12.4.1.3 BroadcastPkts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
12.4.1.4 MulticastPkts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
12.4.1.5 CRCAlignErrors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
12.4.1.6 UndersizePkts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
12.4.1.7 OversizePkts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
12.4.1.8 Fragments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
12.4.1.9 Jabbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
12.4.1.10 Collisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
12.4.1.11 Packet Count for Different Size Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
12.5 Miscellaneous Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
13.0 Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
13.1 ZL50404 Register Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
13.2 Directly Accessed Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
13.2.1 INDEX_REG0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
13.2.2 DATA_FRAME_REG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
13.2.3 CONTROL_FRAME_REG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
13.2.4 COMMAND&STATUS Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
13.2.5 Interrupt Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
13.2.6 Control Command Frame Buffer1 Access Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
13.2.7 Control Command Frame Buffer2 Access Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
13.3 Indirectly Accessed Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
13.3.1 (Group 0 Address) MAC Ports Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
13.3.1.1 ECR1Pn: Port n Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
13.3.1.2 ECR2Pn: Port n Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
13.3.1.3 ECR3Pn: Port n Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
13.3.1.4 ECR4Pn: Port n Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
13.3.1.5 BUF_LIMIT – Frame Buffer Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
13.3.1.6 FCC – Flow Control Grant Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
13.3.2 (Group 1 Address) VLAN Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
13.3.2.1 AVTCL – VLAN Type Code Register Low . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
13.3.2.2 AVTCH – VLAN Type Code Register High. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
13.3.2.3 PVMAP00_0 – Port 0 Configuration Register 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
13.3.2.4 PVMAP00_1 – Port 0 Configuration Register 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
Table of Contents
13.3.2.5 PVMAP00_3 – Port 0 Configuration Register 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
13.3.2.6 PVMAPnn_0,1,3 – Ports 1~9 Configuration Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
13.3.2.7 PVMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
13.3.3 (Group 2 Address) Port Trunking Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
13.3.3.1 TRUNKn– Trunk Group 0~7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
13.3.3.2 TRUNKn_HASH10 – Trunk group 0~7 hash result 1/0 destination port number . . . . . . . . . 69
13.3.3.3 TRUNKn_HASH32 – Trunk group 0~7 hash result 3/2 destination port number . . . . . . . . . 69
13.3.3.4 TRUNKn_HASH54 – Trunk group 0~7 hash result 5/4 destination port number . . . . . . . . . 70
13.3.3.5 TRUNKn_HASH76 – Trunk group 0~7 hash result 7/6 destination port number . . . . . . . . . 70
Multicast Hash Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
13.3.3.6 MULTICAST_HASHn-0 – Multicast hash result 0~7 mask byte 0 . . . . . . . . . . . . . . . . . . . . 71
13.3.3.7 MULTICAST_HASHn-1 – Multicast hash result 0~7 mask byte 1 . . . . . . . . . . . . . . . . . . . . 71
13.3.4 (Group 3 Address) CPU Port Configuration Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
13.3.4.1 MAC0 – CPU MAC address byte 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
13.3.4.2 MAC1 – CPU MAC address byte 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
13.3.4.3 MAC2 – CPU MAC address byte 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
13.3.4.4 MAC3 – CPU MAC address byte 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
13.3.4.5 MAC4 – CPU MAC address byte 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
13.3.4.6 MAC5 – CPU MAC address byte 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
13.3.4.7 INT_MASK0 – Interrupt Mask. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
13.3.4.8 INTP_MASK0 – Interrupt Mask for MAC Port 0,1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
13.3.4.9 INTP_MASKn – Interrupt Mask for MAC Ports 2~9 Registers . . . . . . . . . . . . . . . . . . . . . . . 73
13.3.4.10 RQS – Receive Queue Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
13.3.4.11 RQSS – Receive Queue Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
13.3.4.12 MAC01 – Increment MAC port 0,1 address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
13.3.4.13 MAC23 – Increment MAC port 2,3 address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
13.3.4.14 MAC9 – Increment MAC port 9 address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
13.3.4.15 CPUQINS0 - CPUQINS6 – CPU Queue Insertion Command . . . . . . . . . . . . . . . . . . . . . . 75
13.3.4.16 CPUQINSRPT – CPU Queue Insertion Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
13.3.4.17 CPUGRNHDL0 - CPUGRNHDL1 – CPU Allocated Granule Pointer . . . . . . . . . . . . . . . . . 75
13.3.4.18 CPURLSINFO0 - CPURLSINFO4 – Receive Queue Status . . . . . . . . . . . . . . . . . . . . . . . 76
13.3.4.19 CPUGRNCTR – CPU Granule Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
13.3.5 (Group 4 Address) Search Engine Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
13.3.5.1 AGETIME_LOW – MAC address aging time Low . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
13.3.5.2 AGETIME_HIGH –MAC address aging time High . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
13.3.5.3 SE_OPMODE – Search Engine Operation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
13.3.6 (Group 5 Address) Buffer Control/QOS Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
13.3.6.1 QOSC – QOS Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
13.3.6.2 UCC – Unicast Congestion Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
13.3.6.3 MCC – Multicast Congestion Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
13.3.6.4 MCCTH – Multicast Threshold Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
13.3.6.5 RDRC0 – WRED Rate Control 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
13.3.6.6 RDRC1 – WRED Rate Control 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
13.3.6.7 RDRC2 – WRED Rate Control 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
13.3.6.8 SFCB – Share FCB Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
13.3.6.9 C1RS – Class 1 Reserve Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
13.3.6.10 C2RS – Class 2 Reserve Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
13.3.6.11 C3RS – Class 3 Reserve Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
13.3.6.12 AVPML – VLAN Tag Priority Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
13.3.6.13 AVPMM – VLAN Priority Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
13.3.6.14 AVPMH – VLAN Priority Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
13.3.6.15 AVDM – VLAN Discard Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
7
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
Table of Contents
13.3.6.16 TOSPML – TOS Priority Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
13.3.6.17 TOSPMM – TOS Priority Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
13.3.6.18 TOSPMH – TOS Priority Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
13.3.6.19 TOSDML – TOS Discard Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
13.3.6.20 USER_PROTOCOL_n – User Define Protocol 0~7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
13.3.6.21 USER_PROTOCOL_FORCE_DISCARD – User Define Protocol 0~7 Force Discard . . . . 83
User Defined Logical Ports and Well Known Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
13.3.6.22 WELL_KNOWN_PORT[1:0]_PRIORITY- Well Known Logic Port 1 and 0 Priority . . . . . . 84
13.3.6.23 WELL_KNOWN_PORT[3:2]_PRIORITY- Well Known Logic Port 3 and 2 Priority . . . . . . 84
13.3.6.24 WELL_KNOWN_PORT[5:4]_PRIORITY- Well Known Logic Port 5 and 4 Priority . . . . . . 84
13.3.6.25 WELL_KNOWN_PORT[7:6]_PRIORITY- Well Known Logic Port 7 and 6 Priority . . . . . . 85
13.3.6.26 WELL_KNOWN_PORT_ENABLE – Well Known Logic Port 0 to 7 Enables . . . . . . . . . . . 85
13.3.6.27 WELL_KNOWN_PORT_FORCE_DISCARD – Well Known Logic Port 0~7 Force Discard85
13.3.6.28 USER_PORT[7:0]_[LOW/HIGH] – User Define Logical Port 0~7 . . . . . . . . . . . . . . . . . . . 86
13.3.6.29 USER_PORT_[1:0]_PRIORITY - User Define Logic Port 1 and 0 Priority . . . . . . . . . . . . . 86
13.3.6.30 USER_PORT_[3:2]_PRIORITY - User Define Logic Port 3 and 2 Priority . . . . . . . . . . . . . 86
13.3.6.31 USER_PORT_[5:4]_PRIORITY - User Define Logic Port 5 and 4 Priority . . . . . . . . . . . . . 86
13.3.6.32 USER_PORT_[7:6]_PRIORITY - User Define Logic Port 7 and 6 Priority . . . . . . . . . . . . . 87
13.3.6.33 USER_PORT_ENABLE[7:0] – User Define Logic Port 0 to 7 Enables . . . . . . . . . . . . . . . 87
13.3.6.34 USER_PORT_FORCE_DISCARD[7:0] – User Define Logic Port 0~7 Force Discard . . . . 87
13.3.6.35 RLOWL – User Define Range Low Bit 7:0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
13.3.6.36 RLOWH – User Define Range Low Bit 15:8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
13.3.6.37 RHIGHL – User Define Range High Bit 7:0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
13.3.6.38 RHIGHH – User Define Range High Bit 15:8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
13.3.6.39 RPRIORITY – User Define Range Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
13.3.7 (Group 6 Address) MISC Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
13.3.7.1 MII_OP0 – MII Register Option 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
13.3.7.2 MII_OP1 – MII Register Option 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
13.3.7.3 FEN – Feature Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
13.3.7.4 MIIC0 – MII Command Register 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
13.3.7.5 MIIC1 – MII Command Register 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
13.3.7.6 MIIC2 – MII Command Register 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
13.3.7.7 MIIC3 – MII Command Register 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
13.3.7.8 MIID0 – MII Data Register 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
13.3.7.9 MIID1 – MII Data Register 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
13.3.7.10 USD – One Micro Second Divider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
13.3.7.11 DEVICE Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
13.3.7.12 CHECKSUM - EEPROM Checksum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
13.3.7.13 LHBTimer – Link Heart Beat Timeout Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
13.3.7.14 LHBReg0, LHBReg1 - Link Heart Beat OpCode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
13.3.7.15 fMACCReg0, fMACCReg1 - MAC Control Frame OpCode . . . . . . . . . . . . . . . . . . . . . . . . 93
13.3.7.16 FCB Base Address Register 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
13.3.7.17 FCB Base Address Register 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
13.3.7.18 FCB Base Address Register 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
13.3.8 (Group 7 Address) Port Mirroring Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
13.3.8.1 MIRROR CONTROL – Port Mirror Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
13.3.8.2 MIRROR_DEST_MAC[5:0] – Mirror Destination MAC Address 0~5 . . . . . . . . . . . . . . . . . . 94
13.3.8.3 MIRROR_SRC _MAC[5:0] – Mirror Source MAC Address 0~5 . . . . . . . . . . . . . . . . . . . . . . 94
13.3.8.4 RMAC_MIRROR0 – RMAC Mirror 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
13.3.8.5 RMAC_MIRROR1 – RMAC Mirror 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
13.3.9 (Group 8 Address) Per Port QOS Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
13.3.9.1 FCRn – Port 0~3,8,9 Flooding Control Register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
Table of Contents
13.3.9.2 BMRCn - Port 0~3,8,9 Broadcast/Multicast Rate Control. . . . . . . . . . . . . . . . . . . . . . . . . . . 95
13.3.9.3 PR100_n – Port 0~3 Reservation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
13.3.9.4 PR100_CPU – Port CPU Reservation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
13.3.9.5 PRM – Port MMAC Reservation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
13.3.9.6 PTH100_n – Port 0~3 Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
13.3.9.7 PTH100_CPU – Port CPU Threshold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
13.3.9.8 PTHG – Port MMAC Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
13.3.9.9 QOSC00, QOSC01 - Classes Byte Limit port 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
13.3.9.10 QOSC02, QOSC07 - Classes Byte Limit port 1-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
13.3.9.11 QOSC16 - QOSC21 - Classes Byte Limit CPU port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
13.3.9.12 QOSC22 - QOSC27 - Classes Byte Limit MMAC port . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
13.3.9.13 QOSC28 - QOSC31 - Classes WFQ Credit For MMAC. . . . . . . . . . . . . . . . . . . . . . . . . . . 97
13.3.9.14 QOSC36 - QOSC39 - Shaper Control Port MMAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
13.3.10 (Group E Address) System Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
13.3.10.1 DTSRL – Test Output Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
13.3.10.2 DTSRM – Test Output Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
13.3.10.3 TESTOUT0, TESTOUT1 – Testmux Output [7:0], [15:8] . . . . . . . . . . . . . . . . . . . . . . . . . . 98
13.3.10.4 MASK0-MASK4 – Timeout Reset Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
13.3.10.5 BOOTSTRAP0 – BOOTSTRAP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
13.3.10.6 PRTFSMST0~3,8,9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
13.3.10.7 PRTQOSST0-PRTQOSST3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
13.3.10.8 PRTQOSST8A, PRTQOSST8B (CPU port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
13.3.10.9 PRTQOSST9A, PRTQOSST9B (MMAC port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
13.3.10.10 CLASSQOSST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
13.3.10.11 PRTINTCTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
13.3.10.12 QMCTRL0~3,8,9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
13.3.10.13 QCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
13.3.10.14 BMBISTR0, BMBISTR1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
13.3.10.15 BMControl. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
13.3.10.16 BUFF_RST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
13.3.10.17 FCB_HEAD_PTR0, FCB_HEAD_PTR1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
13.3.10.18 FCB_TAIL_PTR0, FCB_TAIL_PTR1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
13.3.10.19 FCB_NUM0, FCB_NUM1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
13.3.10.20 BM_RLSFF_CTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
13.3.10.21 BM_RSLFF_INFO[5:0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
13.3.11 (Group F Address) CPU Access Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
13.3.11.1 GCR - Global Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
13.3.11.2 DCR - Device Status and Signature Register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
13.3.11.3 DCR1 - Device Status Register 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
13.3.11.4 DPST – Device Port Status Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
13.3.11.5 DTST – Data read back register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
13.3.11.6 DA – DA Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
14.0 Characteristics and Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
14.1 Absolute Maximum Ratings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
14.2 DC Electrical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
14.3 Recommended Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
14.4 AC Characteristics and Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
14.4.1 Typical Reset & Bootstrap Timing Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
14.4.2 Reduced Media Independent Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
14.4.3 Media Independent Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
14.4.4 General Purpose Serial Interface (7-wire) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
14.4.5 MDIO Input Setup and Hold Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
9
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
14.4.6 I²C Input Setup Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
14.4.7 Serial Interface Setup Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
14.4.8 JTAG (IEEE 1149.1-2001) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
15.0 Document Errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
15.1 July 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
15.2 November 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
15.3 February 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
15.4 August 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
10
Zarlink Semiconductor Inc.
ZL50404
1.0
BGA and Ball Signal Descriptions
1.1
BGA Views (Top-View)
1
2
3
4
5
6
7
8
9
Data Sheet
10
11
12
13
14
15
16
A
SCLK
DATAI
N
DATAO
UT
STRO
BE
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
REF_C
LK
RSVD
M9_M
TXCLK
M9_TX
EN
A
B
P_INT
#
SDA
SCL
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
TCK
TMS
RSVD
M9_RX
CK
B
C
RESET
OUT#
TSTO
UT1
TSTO
UT3
TSTO
UT5
TSTO
UT6
TSTO
UT7
TSTO
UT9
TSTO
UT11
TSTO
UT12
TSTO
UT14
TSTO
UT15
TRST#
TDI
RSVD
M9_C
RS
M9_C
OL
C
D
RESIN
#
TSTO
UT0
TSTO
UT2
TSTO
UT4
3.3V
SCAN_
EN
TSTO
UT8
TSTO
UT10
1.8V
TSTO
UT13
TDO
3.3V
RSVD
RSVD
M9_RX
DV
RSVD
D
E
M2_C
OL
M0_C
OL
M1_C
OL
3.3V
3.3V
RSVD
RSVD
RSVD
E
F
M_MD
C
M_MDI
O
M0_RX
D2
M0_RX
D3
M9_RX
D2
M9_RX
D3
RSVD
RSVD
F
G
M0_RX
D0
M0_RX
D1
M0_RX
CK
M0_TX
D3
GND
GND
GND
GND
M9_RX
D0
M9_RX
D1
M9_TX
D2
M9_TX
D3
G
H
M0_C
RS
M0_TX
EN
M0_TX
D2
1.8V
GND
GND
GND
GND
1.8V
RSVD
M9_TX
D0
M9_TX
D1
H
J
M0_TX
D0
M0_TX
D1
M0_TX
CK
M1_RX
D3
GND
GND
GND
GND
RSVD
RSVD
RSVD
RSVD
J
K
M1_RX
D0
M1_RX
D1
M1_RX
D2
M1_RX
CK
GND
GND
GND
GND
RSVD
RSVD
RSVD
RSVD
K
L
M1_C
RS
M1_TX
EN
M1_TX
D2
M1_TX
D3
RSVD
RSVD
RSVD
RSVD
L
M
M1_TX
D0
M1_TX
D1
M1_TX
CK
3.3V
3.3V
RSVD
RSVD
RSVD
M
N
M2_RX
D3
M2_TX
CK
M2_TX
D3
M3_RX
D3
3.3V
M3_TX
D3
1.8V
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
N
P
M2_RX
D2
M2_RX
CK
M2_TX
D2
M3_RX
D2
M3_RX
CK
M3_TX
D2
M3_C
OL
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
P
R
M2_RX
D1
M2_TX
EN
M2_TX
D1
M3_RX
D1
M3_TX
EN
M3_TX
D1
M_CLK
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
R
T
M2_RX
D0
M2_C
RS
M2_TX
D0
M3_RX
D0
M3_C
RS
M3_TX
D0
M3_TX
CK
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
RSVD
T
3
4
6
7
10
11
1
1.2
2
5
8
9
12
13
Power and Ground Distribution
G7-10, H7-10, J7-10, K7-10
GND
VSS
Ground
D5, D12, E4, E13, M4, M13,
N5
3.3V
VCC
I/O Power
D9, H4, H13, N7
1.8V
VDD
Core Power
11
Zarlink Semiconductor Inc.
14
15
16
ZL50404
1.3
Data Sheet
Ball Signal Descriptions
All pins are CMOS type; all Input Pins are 5 Volt tolerance; and all Output Pins are 3.3 CMOS drive.
Notes
#=
Active low signal
Input =
Input signal
Input-ST =
Input signal with Schmitt-Trigger
Output =
Output signal (Tri-State driver)
I/O-TS =
Input & Output signal with Tri-State driver
pull up =
Weak internal pull up (refer to Section 1.4 on page 17
as some internal pull ups are not enabled in certain
configurations)
pull down =
Weak internal pull down (refer to Section 1.4 on page
17 as some internal pull downs are not enabled in
certain configurations)
Ball Signal Description Table
Ball No(s)
Symbol
I/O
Description
I2C Interface - Unmanaged Mode Only (TSTOUT[3] bootstrap must be '1')
B3
SCL
Output
w/ pull up
I2C - Serial Clock Line
Unmanaged Mode Only
B2
SDA
I/O-TS
w/ pull up
I2C - Serial Data Line
Unmanaged Mode Only
Serial CPU Bus Interface
A4
STROBE
Input
w/ pull up
SSI - Clock Signal
A3
DATAOUT
Output
SSI - Data Out
A2
DATAIN
Input
w/ pull up
SSI - Data In
B1
P_INT#
Output
CPU Interrupt
Fast Ethernet Access Ports [3:0] MII
N4, P4, R4, T4, N1,
P1, R1, T1, J4, K3,
K2, K1, F4, F3, G2,
G1
M[3:0]_RXD[3:0]
Input
w/ pull up
Ports [3:0] – Receive Data Bit [3:0]
T5, T2, L1, H1
M[3:0]_CRS_DV
Input
w/ pull up
Ports [3:0] – Carrier Sense and Receive Data
Valid
R5, R2, L2, H2
M[3:0]_TXEN
Output, slew
Ports [3:0] – Transmit Enable
This pin also serves as a bootstrap pin.
12
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
Ball Signal Description Table (continued)
Ball No(s)
Symbol
I/O
Description
N6, P6, R6, T6, N3,
P3, R3, T3, L4, L3,
M2, M1, G4, H3, J2,
J1
M[3:0]_TXD[3:0]
Output, slew
Ports [3:0] – Transmit Data Bit [3:0]
P7, E1, E3, E2
M[3:0]_COL
Input
w/ pull down
Ports[3:0] – Collision
T7, N2, M3, J3
M[3:0]_TXCLK
Input or Output
w/ pull up
Ports[3:0] – Transmit Clock
This pin in an output if ECR4Pn[0]='1'
P5, P2, K4, G3
M[3:0]_RXCLK
Input or Output
w/ pull up
Ports[3:0] – Receive Clock
This pin in an output if ECR4Pn[1]='1'
Fast Ethernet Uplink Port MII
G16, G15, H16, H15
M9_TXD[3:0]
Output
Transmit Data Bit [3:0]
D15
M9_RXDV
Input
w/ pull up
Receive Data Valid
C15
M9_CRS
Input
w/ pull down
Carrier Sense
C16
M9_COL
Input
w/ pull down
Collision Detected
B16
M9_RXCLK
Input or Output
w/ pull up
Receive Clock
This pin in an output if ECR4P9[1]='1'
F14, F13, G14, G13
M9_RXD[3:0]
Input
w/ pull up
Receive Data Bit [3:0]
A16
M9_TXEN
Output
w/ pull up
Transmit Data Enable
A15
M9_MTXCLK
Input
w/ pull up
Transmit Clock
TSTOUT[15:0]
Output
[15:4] Reserved
[3] EEPROM checksum is good
[2] Initialization Completed
[1] Memory Self Test in progress
[0] Initialization started
Test Interface
C11, C10, D10, C9,
C8, D8, C7, D7, C6,
C5, C4, D4, C3, D3,
C2, D2
These pins also serve as bootstrap pins.
Test Facility
C13
TDI
Input
w/pull up
JTAG - Test Data In
13
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
Ball Signal Description Table (continued)
Ball No(s)
Symbol
I/O
Description
C12
TRST#
Input
w/pull up
JTAG - Test Reset
B13
TCK
Input
w/pull up
JTAG - Test Clock
B14
TMS
Input
w/pull up
JTAG - Test Mode State
D11
TDO
Output
JTAG - Test Data Out
D6
SCAN_EN
Input
Scan Enable. Manufacturing test option.
Must be externally
pulled-down
Should be externally pulled-down for proper
operation.
System Clock, Power, and Ground Pins
A1
SCLK
Input
System Clock. Based on system requirement,
SCLK needs to operate at difference
frequency.
SCLK requires 40/60% duty cycle clock.
D9, H4, H13, N7,
VDD
Power
+1.8 Volt DC Supply
D5, D12, E4, E13, M4,
M13, N5,
VCC
Power
+3.3 Volt DC Supply
G7-10, H7-10, J7-10,
K7-10
VSS
Power Ground
Ground
D1
RESIN#
Input
Reset Input
C1
RESETOUT#
Output
Reset PHY
F1
M_MDC
Output
MII Management Data Clock
F2
M_MDIO
I/O-TS
w/ pull up
MII Management Data I/O
R7
M_CLK
Input
RMAC Reference Clock
A13
REF_CLK
Input
w/ pull up
MMAC Reference Clock
Misc.
14
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
Ball Signal Description Table (continued)
Ball No(s)
A12, B12, A11, B11,
A10, B10, A9, B9, A8,
B8, A7, B7, A6, B6,
A5, B5, B4, L13, K14,
L15, L16, N14, P14,
R14, T14, N11, P11,
R11, T11, N8, P8, R8,
T8, K16, T15, T12, T9,
K15, R15, R12, R9,
J13, K13, J15, J16,
N16, P16, R16, T16,
N13, P13, R13, T13,
N10, P10, R10, T10,
H14, M14, M15, M16,
J14, N15, N12, N9,
L14, P15, P12, P9,
E16, E15, F16, F15,
D16, B15, A14
Symbol
RSVD
I/O
Description
N/A
Reserved. Leave unconnected.
Bootstrap Pins (1= pull up 0= pull down)1
D2
TSTOUT[0]
Input (Reset Only)
Enable Debounce of STROBE signal
Pullup – Enabled
Pulldown - Disabled
D3, C2
TSTOUT[2:1]
Input (Reset Only)
Reserved. Must be pulled up.
Must be externally
pulled-up
C3
TSTOUT[3]
Input (Reset Only)
Management interface operation mode:
Pulldown – Lightly Managed Serial. CPU can
transmit/receive frames with the serial
interface.
Pullup – Unmanaged Serial. No CPU packet
can be transmit or received with the serial
interface. EEPROM can be used to configure
the device at bootup.
A one (1) indicates pullup. A zero (0)
indicates pulldown.
C5, C4, D4
TSTOUT[6:4]
Input (Reset Only)
Device ID. Default address of the device for
serial interface. Up to 8 device can be sharing
the serial management bus with different
device ID.
A one (1) indicates pullup. A zero (0)
indicates pulldown. TSTOUT[4] is the Least
Significant Bit (LSB).
15
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
Ball Signal Description Table (continued)
Ball No(s)
Symbol
I/O
Description
C6
TSTOUT[7]
Input (Reset Only)
EEPROM not installed.
Pullup: Not installed
Pulldown: Installed
D7
TSTOUT[8]
Input (Reset Only)
Manufacturing Option. Must be pulled up.
Must be externally
pulled-up
C7
TSTOUT[9]
Input (Reset Only)
Module Detect
Pullup: Enable. In this mode, the device will
detect the existence of a PHY (for hot swap
purpose).
Pulldown: Disable
D8
TSTOUT[10]
Input (Reset Only)
Reserved. Must be pulled down.
Must be externally
pulled-down
C8
TSTOUT[11]
Input (Reset Only)
Power Saving
Pullup: Enable MAC power saving mode
Pulldown: Disable MAC power saving mode
C9
TSTOUT[12]
Input (Reset Only)
Timeout Reset Enable
Pullup: Enable
Pulldown: Disable
C11, C10, D10
TSTOUT[15:13]
Input (Reset Only)
Manufacturing Options. Must be pulled-up.
Must be externally
pulled-up
R5, R2, L2, H2
M[3:0]_TXEN
Input (Reset Only)
User Defined Bootstrap:
Usually used in conjuction with Module Detect
to determine what interface to use for the
inserted module. Can be read from
BOOTSTRAP2 register
1. External pull-up/down resistors are required on all bootstrap pins for proper operation. Recommend 10K for pull-ups and 1K for
pull-downs.
16
Zarlink Semiconductor Inc.
ZL50404
1.4
Data Sheet
Signal Mapping and Internal Pull Up/Down Configuration
The ZL50404 Fast Ethernet access ports (0-3) support 3 interface options: RMII, MII & GPSI. The table below
summarizes the interface signals required for each interface and how they relate back to the Pin Symbol name
shown in the “Ball Signal Description Table” on page 12. It also specifies whether the internal pull up/down resistor
is present for each pin in the specific operating mode.
Notes:
I – Input
O – Output
U – Pullup
D - Pulldown
Fast Ethernet
Access Ports
Pin Symbol
No
Module
(Bootstrap
TSTOUT9=’1’)
RMII Mode
MII Mode
GPSI Mode
(ECR4Pn[4:3]='11')
(ECR4Pn[4:3]='01')
(ECR4Pn[4:3]='00')
M[3:0]_RXD0
(U)
M[3:0]_RXD0 (I)
M[3:0]_RXD0 (I)
M[3:0]_RXD (I)
M[3:0]_RXD1
(U)
M[3:0]_RXD1 (I)
M[3:0]_RXD1 (I)
NC (U)
M[3:0]_RXD2
(U)
NC (U)
M[3:0]_RXD2 (I)
NC (U)
M[3:0]_RXD3
(U)
NC (U)
M[3:0]_RXD3 (I)
NC (U)
M[3:0]_TXEN
(O)
M[3:0]_TXEN (O)
M[3:0]_TXEN (O)
M[3:0]_TXEN (O)
M[3:0]_CRS_DV
(U)
M[3:0]_CRS_DV (I)
M[3:0]_DV (I)
M[3:0]_CRS (I)
M[3:0]_TXD0
(O)
M[3:0]_TXD0 (O)
M[3:0]_TXD0 (O)
M[3:0]_TXD (O)
M[3:0]_TXD1
(O)
M[3:0]_TXD1 (O)
M[3:0]_TXD1 (O)
NC (O)
M[3:0]_TXD2
(O)
NC (O)
M[3:0]_TXD2 (O)
NC (O)
M[3:0]_TXD3
(O)
NC (O)
M[3:0]_TXD3 (O)
NC (O)
M[3:0]_COL
(D)
NC (D)
M[3:0]_COL (I)
M[3:0]_COL (I)
M[3:0]_TXCLK
(U)
NC (U)
M[3:0]_TXCLK (IO)
M[3:0]_TXCLK (IO)
M[3:0]_RXCLK
(U)
NC (U)
M[3:0]_RXCLK (IO)
M[3:0]_RXCLK (IO)
Table 1 - Signal Mapping In Different Operation Mode
17
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
The ZL50404 Fast Ethernet uplink port (port 9) supports 1 interface option: MII. The table below summarizes the
interface signals required for each interface, and how they relate back to the Pin Symbol name shown in “Ball
Signal Description Table” on page 12.
Fast Ethernet
Uplink Port
Pin Symbol
No
Module
MII Mode
(ECR4P9[4:3]='11')
(Bootstrap
TSTOUT9=’1’)
M9_RXD0
(U)
M9_RXD0 (I)
M9_RXD1
(U)
M9_RXD1 (I)
M9_RXD2
(U)
M9_RXD2 (I)
M9_RXD3
(U)
M9_RXD3 (I)
M9_RXDV
(U)
M9_RXDV (I)
M9_CRS
(D)
M9_CRS (I)
M9_COL
(D)
M9_COL (I)
M9_RXCLK
(U)
M9_RXCLK (IO)
M9_TXD0
(O)
M9_TXD0 (O)
M9_TXD1
(O)
M9_TXD1 (O)
M9_TXD2
(O)
M9_TXD2 (O)
M9_TXD3
(O)
M9_TXD3 (O)
M9_TXEN
(U)
M9_TXEN (O)
REF_CLK
(U)
REF_CLK (I)
M9_MTXCLK
(U)
M9_MTXCLK (I)
Table 2 - Signal Mapping In Different Operation Mode
18
Zarlink Semiconductor Inc.
ZL50404
1.5
Data Sheet
Bootstrap Options
TSTOUT[15:0] and M[3:0]_TXEN pins serve as bootstrap pins during device power-up or reset. Please refer to
“Typical Reset & Bootstrap Timing Diagram” on page 111 for more information on when the bootstrap pins are
sampled. The bootstrap pins require external pull-up/down resistors for proper operation.
The table below summarizes the bootstrap options.
Feature
CPU Interface
Description
The ZL50404 allows the selection of 2 different management interfaces: serial
only and unmanaged serial with I2C EEPROM.
TSTOUT[3] is used to select the interface options mentioned above. If the
serial interface is selected, addition bootstrap options are required:
• TSTOUT[0] enables or disables the DEBOUNCE feature (refer to
“Synchronous Serial Interface” on page 26)
• TSTOUT[6:4] selects the device ID
Also, an optional I2C EEPROM can be used to configure the device at
power-up or reset. TSTOUT[7] selects the EEPROM option.
Ethernet Interface
The ZL50404 supports module hotswap on all it's ports. This is enabled via
TSTOUT[9]. When enabled, bootstrap pins M[3:0]_TXEN (ports 0-3) are used
to specify the module type to support multiple ethernet interfaces during
module hotswap.
Another feature is the MAC power savings mode. When enabled via
TSTOUT[11], each port's MAC will detect inactivity on the port and go into a
power savings state. Once activity is detected once again on the port, the MAC
will come out of this state.
Misc. Features
One other feature selected via bootstrap is Timeout Reset Enable
(TSTOUT[12]). This enables a monitoring block with the device which will
detect if any hardware state machine is in a non-idle state for more than 5
seconds.
Refer to section 2.7 for more details on this feature.
Table 3 - Bootstrap Features
19
Zarlink Semiconductor Inc.
ZL50404
2.0
Data Sheet
Block Functionality
RMAC X 4
8
GMAC
M
Frame Engine
Search Engine
Other Internal
Memory Block
Management
Module
Internal Memory
Figure 2 - Functional Block Diagram
2.1
Internal Memory
Two Megabit of internal memory is provided for ethernet Frame Data Buffering (FDB), storing of MAC Control Table
database (MCT), and the Network Management (NM) Database statistics counters and MIB.
The MCT is used for storing MAC addresses and their physical port number. The FDB is used for storing the
received frame data contents. The contents are stored in this memory until it is ready to be transmitted to the
egress port.
A memory arbiter is used to arbitrary the memory access requests from various sources. A Built In Self Test (BIST)
is used to detect any error in the memory array when the device is powered up. The BIST can also be requested by
the writing to the GCR register.
2.2
2.2.1
MAC Modules
RMII MAC Module (RMAC)
The RMII Media Access Control (RMAC) module provides the necessary buffers and control interface between the
Frame Engine (FE) and the external physical device (PHY). It has five interfaces: MII, RMII, GPSI (only for 10M),
Reverse MII, or Reverse GPSI (only for 10M).
The RMAC of the ZL50404 device meets the IEEE 802.3 specification. It is able to operate in either Half or Full
Duplex mode with a back pressure/flow control mechanism. In addition, it will automatically retransmit upon
collision for up to 16 total transmissions.
These four ports are denoted as ports 0 to 3. The PHY addresses for the PHY devices connected to the 4 RMAC
ports has to be from 08h (port 0) to 0Bh (port 3).
20
Zarlink Semiconductor Inc.
ZL50404
2.2.2
Data Sheet
CPU MAC Module (CMAC)
The CPU Media Access Control (CMAC) module provides the necessary buffers and control interface between the
Frame Engine (FE) and the external CPU device. It support a register access mechanism via the serial interface.
This port is denoted as port 8.
2.2.3
MII MAC Module (MMAC)
The MII Media Access Control (MMAC) module provides the necessary buffers and control interface between the
Frame Engine (FE) and the external physical device (PHY). The MMAC implements an MII interface.
The MMAC of the ZL50404 device meets the IEEE 802.3 specification. It is able to operate in 10M/100M either Half
or Full Duplex mode with a back pressure/flow control mechanism. Furthermore, it will automatically retransmit
upon collision for up to 16 total transmissions.
This port is denoted as port 9. The PHY address for the PHY device connected to the MMAC port has to be 10h.
2.2.4
PHY Addresses
The table below provides an overview of the PHY addresses required for each port in order for the MDIO
auto-negotiation to work between the ZL50404 MAC and the PHY device. If a different PHY address is used, then
the port must be manually brought up and the PHY will need to be polled for link status via the MIIC/D registers.
MAC Port
PHY Address
RMAC Port 0
0x08
RMAC Port 1
0x09
...
...
RMAC Port 3
0x0B
CMAC Port 8
NA
MMAC Port 9
0x10
Table 4 - PHY Addresses
2.3
Management Module
The CPU can send a control frame to access or configure the internal network management database. The
Management Module decodes the control frame and executes the functions requested by the CPU.
This module is only active in managed mode. In unmanaged mode, no control frame is accepted by the device.
2.4
Frame Engine
The main function of the frame engine is to forward a frame to its proper destination port or ports. When a frame
arrives, the frame engine parses the frame header (64 bytes) and formulates a switching request, sent to the
search engine, to resolve the destination port. The arriving frame is moved to the internal memory. After receiving a
switch response from the search engine, the frame engine performs transmission scheduling based on the frame’s
priority. The frame engine forwards the frame to the MAC module when the frame is ready to be sent.
2.5
Search Engine
The Search Engine resolves the frame’s destination port or ports according to the destination MAC address (L2) by
searching the database. It also performs MAC learning, priority assignment, and trunking functions.
21
Zarlink Semiconductor Inc.
ZL50404
2.6
Data Sheet
Heartbeat Packet Generation and Response
The ZL50404 provides the ability to monitor a link and detect a simple link failure. The Link Heart Beat (LHB) packet
generation module allows simultaneous tracking of all the RMAC ports.
Periodically, a LHB message will be sent for each link when inactivity is detected with in a programmable time
period, If a reply is not received in a specified amount of time, the failover detection module will identify a
point-to-point failure for that link. The failover detection module will then interrupt the CPU.
The LHB packet response module can also reply to LHB messages initiated by other ZL50404 devices in the
system, or by non-ZL50404 devices which use a conventional and recognizable LHB message format.
2.7
Timeout Reset Monitor
The ZL50404 supports a state machine monitoring block which can trigger a reset or interrupt if any state machine
is determined to be stuck in a non-idle state for more than 5 seconds. This feature is enabled via a bootstrap pin
(TSTOUT12). It also requires some register configuration via the CPU interface.
See Programming Timeout Reset application note, ZLAN-41, for more information.
2.8
JTAG
An IEEE1149.1 compliant test interface is provided for boundary scan.
3.0
Management and Configuration
One extra port is dedicated to the CPU via the CPU interface module. Two modes this port can operate: lightly
managed or unmanaged mode. The different between these modes is tx/rx Ethernet frame, tx/rx control frame and
receiving interrupt due to the lack of constant attention or processing power from the CPU.
Supported CPU interface modes are
Operation Mode
ISA Interface
Serial
MII
I²C
Lightly Managed Serial
NA
Yes
No
No
Unmanaged Serial
NA
Yes
No
Yes
Table 5 - Supported CPU interface modes
1. Lightly Managed Serial. Configuration registers access, Control frame and CPU transmit/receive packets are
sent through a synchronous serial interface (SSI) bus.
2. Unmanaged Serial. The device can be configured by EEPROM using an I²C interface at bootup, or via a synchronous serial interface (SSI) otherwise. All configuration registers and internal control blocks are accessible
by the interface. However, the CPU cannot receive or transmit frames nor will it receive any interrupt information.
The CPU interface provides for easy and effective management of the switching system.
Figure 3 on page 23 provides an overview of the SSI interface.
22
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
Processor
Serial Out
Serial In
Strobe Interrupt
Synchronous Serial Interface
3-bit Address Bus
16-bit Data Bus
Address
Index Reg 1
(Addr = 1)
Index Reg 0
(Addr = 0)
16-bit Address
Config Data
Reg
(Addr = 2)
8-bit Data Bus
Internal
Registers
Inderect
Access
INT CS W R
I/O Data MUX
Command/
Status Reg
(Addr = 4)
CPU Frame Reg
(Addr = 3)
Interrupt
Reg
(Addr = 5)
8/16-bit Data Bus
Control
Command 1 Reg
(Addr = 6)
Control
Command 2
Reg
(Addr = 7)
8/16-bit Data Bus
Control
Control Command 1
Command 1Transmit
Receive
FIFO
FIFO
CPU frame
Transmit
CPU frame
Receive FIFO
FIFO
Control
Command 2
Transmit
FIFO
Interrupt
Figure 3 - Overview of the SSI Interface
3.1
3.1.1
Register Configuration, Frame Transmission, and Frame Reception
Register Configuration
The ZL50404 has many programmable parameters, covering such functions as QoS weights, VLAN control, and
port mirroring setup. In managed mode, the CPU interface provides an easy way of configuring these parameters.
The parameters are contained in 8-bit configuration registers. The device allows indirect access to these registers,
as follows:
•
•
In serial mode, the address, command and data are shifted in serially. To access the configuration registers,
only one “index” register (addresses 000b) needs to be written with the configuration register address. The
desired data can be written into or read from the “data” register (address 010b).
• For example, if “XX” is required to be written to register “YY”, a write of “YY” is required to write to
address “000b” (Index register). Then, a write of “XX” is required to write to address “010b” (Data
Register). This completes the register write and register “YY” will contain the value of “XX”.
To indirectly configure the register addressed by the index register, a “data” register (address 010b) must be
written with the desired 8-bit data.
23
Zarlink Semiconductor Inc.
ZL50404
•
•
•
Data Sheet
The ZL50404 supports special register-write in serial mode. This allows CPU to write to two consecutive
configuration registers in a single write operation. By writing to bit[14] of configuration register address,
CPU can write 16-bit data to address 010b. Lower 8 bit of data is for the address specified in index
register and upper 8 bit of data is for the address + 1.
15
14
INC
R/W
SP
W
13
12
0
11
Reserved
12 Bit Register Address
Similarly, to read the value in the register addressed by the index register, the “data” register can now simply
be read.
The ZL50404 supports an incremental read/write. If CPU requires to read or write to the configuration
registers incrementally, CPU only has to write to index register once with the MSB of configuration register
address set and then CPU can continuously reading or writing to “data” register (010b).
In summary, access to the many internal registers is carried out simply by directly accessing only two registers –
one register to indicate the index of the desired parameter, and one register to read or write a value. Of course,
because there is only one bus master, there can never be any conflict between reading and writing the
configuration registers.
3.1.2
Rx/Tx of Standard Ethernet Frames
In serial only mode, the Ethernet frame is transmitted and received through the CPU interface. There is no ability to
send/receive Ethernet frames in unmanaged mode.
To transmit a frame from the CPU in serial only mode:
•
•
The CPU writes to the “data frame” register (address 011) with the frame size, destination port number, and
frame status. After writing all the transmitting status bytes, it then writes the data it wants to transmit
(minimum 64 bytes).
The ZL50404 forwards the Ethernet frame to the desired destination port, no longer distinguishing the fact
that the frame originated from the CPU.
To receive a frame into the CPU in serial only mode:
•
•
•
The CPU receives an interrupt when an Ethernet frame is available to be received.
Frame information arrives first in the data frame register. This includes source port number, frame size, and
VLAN tag.
The actual data follows the frame information. The CPU uses the frame size information to read the frame
out.
In summary, in serial only mode, receiving and transmitting frames to and from the CPU is a simple process that
uses one direct access register only.The details of sending an Ethernet Frame via the CPU interface is described in
the Processor Interface Application Note, ZLAN-26.
Although there is the ability to Tx/Rx Ethernet Frames via the serial interface in lightly managed mode, the ZL50404
is not meant to be used in a fully managed system. The speed of the serial interface limits management capability.
For example, if the system is trying to implement port security, it would require a faster interface between the CPU
and the ZL50404, such as the 8/16-bit interface or the serial + MII interface found on the managed device.
3.1.3
Control Frames
In addition to standard Ethernet frames described in the preceding section, the CPU is also called upon to handle
special “Control frames,” generated by the ZL50404 and sent to the CPU. These proprietary frames are related to
such tasks as statistics collection, MAC address learning, and aging, etc… All Control frames are up to 40 bytes
long. Transmitting and receiving these frames is similar to transmitting and receiving Ethernet frames, except that
the register accessed is the “Control frame data” register (address 111).
24
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
Specifically, there are the following types of control frames generated by the CPU and sent to the ZL50404:
•
•
•
•
•
•
•
•
Memory read request
Memory write request
Learn Unicast MAC address
Delete Unicast MAC address
Search Unicast MAC address
Learn Multicast MAC address
Delete Multicast MAC address
Search Multicast MAC address
Note: Memory read and write requests by the CPU may include all internal memories which include statistic
counters, MAC address control link table and the 2Mbit (256KB) memory block.
In addition, the following types of Control frames are generated by the ZL50404 and sent to the CPU:
•
•
•
•
•
•
•
Interrupt CPU when statistics counter rolls over
Response to memory read request from CPU
Learn Unicast MAC address
Delete Unicast MAC address
Delete Multicast MAC address
Response to search Unicast MAC address request from CPU
Response to search Multicast MAC address request from CPU
The format of the Control Frame is described in the Processor Interface application note, ZLAN-26.
Although there is the ability to Tx/Rx Control Frames via the serial interface in lightly managed mode, the ZL50404
is not meant to be used in a fully managed system. The speed of the serial interface limits management capability.
For example, if the system is trying to manage the MAC learning/deletion, it would require a faster interface
between the CPU and the ZL50404, such as the 8/16-bit interface found on the managed device.
I2C Interface
3.2
The I²C interface serves the function of configuring the ZL50404 at boot time. The master is the ZL50404, and the
slave is the EEPROM memory.
The I²C interface uses two bus lines, a serial data line (SDA) and a serial clock line (SCL). The SCL line carries the
control signals that facilitate the transfer of information from EEPROM to the switch. Data transfer is 8-bit serial and
bidirectional, at 50 Kbps. Data transfer is performed between master and slave IC using a request /
acknowledgment style of protocol. The master IC generates the timing signals and terminates data transfer. Figure
4 depicts the data transfer format. The slave address is the memory address of the EEPROM. Refer to “ZL50404
Register Description” on page 52 for I²C address for each register.
START
SLAVE ADDRESS
R/W
ACK
DATA 1 (8bits)
ACK
DATA 2
ACK
DATA M
ACK
STOP
Figure 4 - Data Transfer Format for I²C Interface
3.2.1
Start Condition
Generated by the master (in our case, the ZL50404). The bus is considered to be busy after the Start condition is
generated. The Start condition occurs if while the SCL line is High, there is a High-to-Low transition of the SDA line.
Other than in the Start condition (and Stop condition), the data on the SDA line must be stable during the High
period of SCL. The High or Low state of SDA can only change when SCL is Low. In addition, when the I²C bus is
free, both lines are High.
25
Zarlink Semiconductor Inc.
ZL50404
3.2.2
Data Sheet
Address
The first byte after the Start condition determines which slave the master will select. The slave in our case is the
EEPROM. The first seven bits of the first data byte make up the slave address.
3.2.3
Data Direction
The eighth bit in the first byte after the Start condition determines the direction (R/W) of the message. A master
transmitter sets this bit to W; a master receiver sets this bit to R.
3.2.4
Acknowledgment
Like all clock pulses, the acknowledgment-related clock pulse is generated by the master. However, the transmitter
releases the SDA line (High) during the acknowledgment clock pulse. Furthermore, the receiver must pull down the
SDA line during the acknowledge pulse so that it remains stable Low during the High period of this clock pulse. An
acknowledgment pulse follows every byte transfer.
If a slave receiver does not acknowledge after any byte, then the master generates a Stop condition and aborts the
transfer.
If a master receiver does not acknowledge after any byte, then the slave transmitter must release the SDA line to let
the master generate the Stop condition.
3.2.5
Data
After the first byte containing the address, all bytes that follow are data bytes. Each byte must be followed by an
acknowledge bit. Data is transferred MSB first.
3.2.6
Stop Condition
Generated by the master. The bus is considered to be free after the Stop condition is generated. The Stop condition
occurs if while the SCL line is High, there is a Low-to-High transition of the SDA line.
3.3
Synchronous Serial Interface
The synchronous serial interface (SSI) serves the function of configuring the ZL50404 not at boot time but via a PC.
The PC serves as master and the ZL50404 serves as slave. The protocol for the synchronous serial interface is
nearly identical to the I²C protocol. The main difference is that there is no acknowledgment bit after each byte of
data transferred. Debounce logic on the clock signal (STROBE) can be turned off to speedup command time.
3 ID bits are used to allow up to eight ZL50404 devices to share the same synchronous serial interface. The ID of
each device can be setup by bootstrap.
To reduce the number of signals required, the register address, command and data are shifted in serially through
the DATAIN pin. STROBE- pin is used as the shift clock. DATAOUT pin is used as data return path.
Each command consists of four parts.
•
•
•
•
START pulse
Register Address
Read or Write command
Data to be written or read back
Write operation can be aborted in the middle by sending an ABORT pulse to the ZL50404. Read operation can only
be aborted before issuing the read command to the ZL50404.
A START command is detected when DATAIN is sampled high when STROBE- rise and DATAIN is sampled low
when STROBE- fall.
26
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
An ABORT command is detected when DATAIN is sampled low when STROBE- rise and DATAIN is sampled high
when STROBE- fall.
3.3.1
Write Command
All registers in ZL50404 can be modified through this synchronous serial interface. Once the data has been sent,
two extra STOBE clocks must be generated to indicate the end of the write command. The DATAIN line should be
held high for these two pulses.
STROBE2 Extra clocks after last
transfer
DATAIN
D0
ID0
START
ID1
ID2
A0
ID
A1
A2
ADDR
W
D0 D1 D2
D3
CMD
...
D12
D13
D14
D15
DATA
Figure 5 - Serial Interface Write Command Functional Timing
3.3.2
Read Command
All registers in ZL50404 can be read through this synchronous serial interface.
STROBE-
DATAIN
D0
ID0
START
ID1
ID
ID2
A0 A1 A2
R
ADDR
CMD
DATAOUT
AUTOFD-
DATA
D0 D1 D2 ...
D12
D13
D14
D15
Figure 6 - Serial Interface Read Command Functional Timing
27
Zarlink Semiconductor Inc.
ZL50404
4.0
Data Forwarding Protocol
4.1
Unicast Data Frame Forwarding
Data Sheet
When a frame arrives, it is assigned a handle in memory by the Frame Control Buffer Manager (FCB Manager). An
FCB handle will always be available, because of advance buffer reservations.
The memory (SRAM) interface is a 64-bit bus, connected to internal memory block. The Receive DMA (RxDMA) is
responsible for multiplexing the data and the address. On a port’s “turn”, the RxDMA will move 8 bytes (or up to the
end-of-frame) from the port’s associated RxFIFO into memory (Frame Data Buffer, or FDB).
Once an entire frame has been moved to the FDB, and a good end-of-frame (EOF) has been received, the Rx
interface makes a switch request. The RxDMA arbitrates among multiple switch requests.
The switch request consists of the first 64 bytes of a frame, containing among other things, the source and
destination MAC addresses of the frame. The search engine places a switch response in the switch response
queue of the frame engine when done. Among other information, the search engine will have resolved the
destination port of the frame and will have determined that the frame is unicast.
After processing the switch response, the Transmission Queue Manager (TxQ manager) of the frame engine is
responsible for notifying the destination port that it has a frame to forward. But first, the TxQ manager has to decide
whether or not to drop the frame, based on global FDB reservations and usage, as well as TxQ occupancy at the
destination. If the frame is not dropped, then the TxQ manager links the frame’s FCB to the correct
per-port-per-class TxQ. The switch response will come with 8 classified results. The TxQ manager will map this
result into the per-port-per-class queue. Unicast TxQ’s are linked lists of transmission jobs, represented by their
associated frames’ FCB’s. There is one linked list for each transmission class for each port. There are 2
transmission classes for each of the 4 RMAC ports, and 4 classes for the MMAC and CPU ports – a total of 16
unicast queues.
The TxQ manager is responsible for scheduling transmission among the queues representing different classes for
a port. When the port control module determines that there is room in the MAC Transmission FIFO (TxFIFO) for
another frame, it requests the handle of a new frame from the TxQ manager. The TxQ manager chooses among
the head-of-line (HOL) frames from the per-class queues for that port, using a Zarlink Semiconductor scheduling
algorithm.
The Transmission DMA (TxDMA) is responsible for multiplexing the data and the address. On a port’s turn, the
TxDMA will move 8 bytes (or up to the EOF) from memory into the port’s associated TxFIFO. After reading the
EOF, the port control requests a FCB release for that frame. The TxDMA arbitrates among multiple buffer release
requests.
The frame is transmitted from the TxFIFO to the line.
4.2
Multicast Data Frame Forwarding
After receiving the switch response, the TxQ manager has to make the dropping decision. A global decision to drop
can be made, based on global FDB utilization and reservations. If so, then the FCB is released and the frame is
dropped. In addition, a selective decision to drop can be made, based on the TxQ occupancy at some subset of
the multicast packet’s destinations. If so, then the frame is dropped at some destinations but not others, and the
FCB is not released.
If the frame is not dropped at a particular destination port, then the TxQ manager formats an entry in the multicast
queue for that port and class. Multicast queues are physical queues (unlike the linked lists for unicast frames).
There are 2 multicast queues for each of the 4 RMAC ports. There are 4 multicast queues for the MMAC and CPU
ports. The mapping from the classified result to the priority queue is the same as the unicast traffic. By default, for
the RMAC ports to map the 8 transmit priorities into 2 multicast queues, the 2 LSB are discarded. For the MMAC
and CPU ports, to map the 8 transmit priorities into 4 multicast queues, the LSB is discarded. The priority mapping
can be modified through memory configuration command. The multicast queue that is in FIFO format shares the
space in the internal memory block. The size and starting address can also be programmed through memory
configuration command.
28
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
During scheduling, the TxQ manager treats the unicast queue and the multicast queue of the same class as one
logical queue. The older head of line of the two queues is forwarded first. The port control requests a FCB release
only after the EOF for the multicast frame has been read by all ports to which the frame is destined.
4.3
Frame Forwarding To and From CPU
Frame forwarding from the CPU port to a regular transmission port is nearly the same as forwarding between
transmission ports. The only difference is that the physical destination port must be indicated in addition to the
destination MAC address.
Frame forwarding to the CPU port is nearly the same as forwarding to a regular transmission port. The only
difference is in frame scheduling.
Instead of using the patent-pending Zarlink Semiconductor scheduling
algorithms, scheduling for the CPU port is simply based on strict priority. That is, a frame in a high priority queue will
always be transmitted before a frame in a lower priority queue. There are four output queues to the CPU and one
receive queue.
5.0
Search Engine
5.1
Search Engine Overview
The ZL50404 search engine is optimized for high throughput searching, with enhanced features to support:
•
•
•
•
•
•
•
Up to 4 K of Unicast/Multicast MAC addresses
8 groups of port trunking
Traffic classification into 2 (or 4 for MMAC) transmission priorities, and 2 drop precedence levels
Packet filtering based on MAC address, Protocol or Logical Port number
Security
Individual Flooding, Broadcast, Multicast Storm Control
MAC address learning and aging
5.2
Basic Flow
Shortly after a frame enters the ZL50404 and is written to the Frame Data Buffer (FDB), the frame engine generates
a Switch Request, which is sent to the search engine. The switch request consists of the first 64 bytes of the frame,
which contain all the necessary information for the search engine to perform its task. When the search engine is
done, it writes to the Switch Response Queue, and the frame engine uses the information provided in that queue for
scheduling and forwarding.
In performing its task, the search engine extracts and compresses the useful information from the 64-byte switch
request. Among the information extracted are the source and destination MAC addresses, the packet’s VLAN ID,
and whether the frame is unicast or multicast or broadcast. Requests are sent to the SRAM to locate the associated
entries in the MCT table.
When all the information has been collected from the SRAM, the search engine has to compare the MAC address
on the current entry with the MAC address for which it is searching. If it is not a match, the process is repeated on
the internal MCT Table. All MCT entries other than the first of each linked list are maintained internal to the chip. If
the desired MAC address is still not found, then the result is either learning (source MAC address unknown) or
flooding (destination MAC address unknown).
If the destination MAC address belongs to a port trunk, then the trunk number is retrieved instead of the port
number. But on which port of the trunk will the frame be transmitted? This is easily computed using a hash of the
source and destination MAC addresses.
When all the information is compiled, the switch response is generated, as stated earlier. The search engine also
interacts with the CPU with regard to learning and aging.
29
Zarlink Semiconductor Inc.
ZL50404
5.3
5.3.1
Data Sheet
Search, Learning, and Aging
MAC Search
The search block performs source MAC address and destination MAC address searching. As we indicated earlier,
if a match is not found, then the next entry in the linked list must be examined, and so on until a match is found or
the end of the list is reached.
In port based VLAN mode, a bitmap is used to determine whether the frame should be forwarded to the outgoing
port. The main difference in this mode is that the bitmap is not dynamic. Ports cannot enter and exit groups
because of real-time learning made by a CPU.
The MAC search block is also responsible for updating the source MAC address timestamp used for aging.
5.3.2
Learning
The learning module learns new MAC addresses and performs port change operations on the MCT database. The
goal of learning is to update this database as the networking environment changes over time.
When CPU reporting is enabled, learning and port change will be performed when the CPU request queue has
room, and a “Learn MAC Address” message is sent to the CPU.
5.3.3
Aging
Aging time is controlled by register 400h and 401h.
The aging module scans and ages MCT entries based on a programmable “age out” time interval. As we indicated
earlier, the search module updates the source MAC address timestamps for each frame it processes. When an
entry is ready to be aged, the entry is removed from the table, and a “Delete MAC Address” message is sent to
inform the CPU.
Supported MAC entry types are: dynamic, static, source filter, destination filter, source and destination filter, secure
and multicast MAC address. Only dynamic entries can be aged; all others are static. The MAC entry type is stored
in the “status” field of the MCT data structure.
5.4
MAC Address Filtering
The ZL50404's implementation of intelligent traffic switching provides filters for source and destination MAC
addresses. This feature filters unnecessary traffic, thereby providing intelligent control over traffic flows and
broadcast traffic.
MAC address filtering allows the ZL50404 to block an incoming packet to an interface when it sees a specified MAC
address in either the source address or destination address of the incoming packet. For example, if your network is
congested because of high utilization from a MAC address, you can filter all traffic transmitted from that address
and restore network flow, while you troubleshoot the problem.
5.5
Protocol Filtering
Packet filtering can be performed based on protocol type field in the packets. Up to eight protocols can be
programmed to filter or allow packet to pass through the switch.
5.6
Logical Port Filtering
Similar to protocol filtering, if the packet’s logical ports match the programmable registers, the packet can be filtered
or passed through the switch. Up to eight programmable ports and one ranges can be assigned.
30
Zarlink Semiconductor Inc.
ZL50404
5.7
Data Sheet
Quality of Service
Quality of Service (QoS) refers to the ability of a network to provide better service to selected network traffic over
various technologies. Primary goals of QoS include dedicated bandwidth, controlled jitter and latency (required by
some real-time and interactive traffic), and improved loss characteristics.
Traditional Ethernet networks have had no prioritization of traffic. Without a protocol to prioritize or differentiate
traffic, a service level known as “best effort” attempts to get all the packets to their intended destinations with
minimum delay; however, there are no guarantees. In a congested network or when a low-performance
switch/router is overloaded, “best effort” becomes unsuitable for delay-sensitive traffic and mission-critical data
transmission.
The advent of QoS for packet-based systems accommodates the integration of delay-sensitive video and
multimedia traffic onto any existing Ethernet network. It also alleviates the congestion issues that have previously
plagued such “best effort” networking systems. QoS provides Ethernet networks with the breakthrough technology
to prioritize traffic and ensure that a certain transmission will have a guaranteed minimum amount of bandwidth.
Extensive core QoS mechanisms are built into the ZL50404 architecture to ensure policy enforcement and
buffering of the ingress port, as well as weighted fair-queue (WFQ) scheduling at the egress port.
In the ZL50404, QoS-based policies sort traffic into a small number of classes and mark the packets accordingly.
The QoS identifier provides specific treatment to traffic in different classes, so that different quality of service is
provided to each class. Frame and packet scheduling and discarding policies are determined by the class to which
the frames and packets belong. For example, the overall service given to frames and packets in the premium class
will be better than that given to the standard class; the premium class is expected to experience lower loss rate or
delay.
The ZL50404 supports the following QoS techniques:
•
•
•
•
In a port-based setup, any station connected to the same physical port of the switch will have the same
transmit priority.
In a tag-based setup, a 3-bit field in the VLAN tag provides the priority of the packet. This priority can be
mapped to different queues in the switch to provide QoS.
In a TOS/DS-based set up, TOS stands for “Type of Service” that may include “minimize delay,” “maximize
throughput,” or “maximize reliability.” Network nodes may select routing paths or forwarding behaviours that
are suitably engineered to satisfy the service request.
In a logical port-based set up, a logical port provides the application information of the packet. Certain
applications are more sensitive to delays than others; using logical ports to classify packets can help speed
up delay sensitive applications, such as VoIP.
31
Zarlink Semiconductor Inc.
ZL50404
5.8
Data Sheet
Priority Classification Rule
Figure 7 shows the ZL50404 priority classification rule.
Fix Port Priority?
Yes
Use Default port settings
No
TOS Precedence over VLAN?
(QOSC Register bit 5)
Yes
No
Use VLAN
priority
Yes
No
VLAN Tag?
IP Frame?
No
IP Frame?
Yes
Yes
Use Logical Port?
No
No
Use TOS
Yes
Use Default port settings
Use logical port
Figure 7 - Priority Classification Rule
5.9
Port Based VLAN
An administrator can use the PVMAP Registers to configure the ZL50404 for port-based VLAN (see “Register
Definition” on page 52). For example, ports 1-3 might be assigned to the Marketing VLAN, ports 4-6 to the
Engineering VLAN, and ports 7-9 to the Administrative VLAN. The ZL50404 determines the VLAN membership of
each packet by noting the port on which it arrives. From there, the ZL50404 determines which outgoing port(s)
is/are eligible to transmit each packet, or whether the packet should be discarded.
Destination Port Numbers Bit Map
Port Registers
9
Register for Port #0
PVMAP00_0[7:0] to PVMAP00_1[1:0]
…
2
1
0
0
1
1
0
Register for Port #1
PVMAP01_0[7:0] to PVMAP01_1[1:0]
0
1
0
1
Register for Port #2
PVMAP02_0[7:0] to PVMAP02_1[1:0]
0
0
0
0
0
0
0
0
…
Register for Port #9
PVMAP09_0[7:0] to PVMAP09_1[1:0]
Table 6 - Port-Based VLAN Mapping
32
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
For example, in the above table a 1 denotes that an outgoing port is eligible to receive a packet from an incoming
port. A 0 (zero) denotes that an outgoing port is not eligible to receive a packet from an incoming port.
In this example:
•
•
•
Data packets received at port #0 are eligible to be sent to outgoing ports 1 and 2.
Data packets received at port #1 are eligible to be sent to outgoing ports 0 and 2.
Data packets received at port #2 are NOT eligible to be sent to ports 0 and 1.
6.0
Frame Engine
6.1
Data Forwarding Summary
When a frame enters the device at the RxMAC, the RxDMA will move the data from the MAC RxFIFO to the FDB.
Data is moved in 8-byte granules in conjunction with the scheme for the SRAM interface.
A switch request is sent to the Search Engine. The Search Engine processes the switch request.
A switch response is sent back to the Frame Engine and indicates whether the frame is unicast or multicast, and its
destination port or ports. On receiving the response, the Frame Engine will check all the QoS related information
and decide if this frame can be forwarded.
A Transmission Scheduling Request is sent in the form of a signal notifying the TxQ manager. Upon receiving a
Transmission Scheduling Request, the device will format an entry in the appropriate Transmission Scheduling
Queue (TxSch Q) or Queues. There are 2 TxSch Q for each RMAC port (and 4 per MMAC and CPU ports), one
for each priority. Creation of a queue entry either involves linking a new job to the appropriate linked list if unicast,
or adding an entry to a physical queue if multicast.
When the port is ready to accept the next frame, the TxQ manager will get the head-of-line (HOL) entry of one of
the TxSch Qs, according to the transmission scheduling algorithm (so as to ensure per-class quality of service).
(The unicast linked list and the multicast queue for the same port-class pair are treated as one logical queue. The
older HOL between the two queues goes first.
The TxDMA will pull frame data from the memory and forward it granule-by-granule to the MAC TxFIFO of the
destination port.
6.2
Frame Engine Details
This section briefly describes the functions of each of the modules of the ZL50404 frame engine.
6.2.1
FCB Manager
The FCB manager allocates FCB handles to incoming frames, and releases FCB handles upon frame departure.
The FCB manager is also responsible for enforcing buffer reservations and limits that will be used for QoS control
and source port flow control. The default values can be determined by referring to Section 7.6 on page 38. The
frame buffer is managed in a 128bytes block unit. During initialization, this block will link all the available blocks in a
free buffer list. When each port is ready to receive, this module hands the buffer handle to each requesting port.
The FCB manager will also link the released buffer back into the free buffer list.
The maximum buffer size can be increased from the standard 1518 bytes (1522 with VLAN tag) to up to 4 K bytes.
This is done using BUF_LIMIT, and is enabled on a per port basis via bit [1] in ECR3Pn. See Buffer Allocation
application note, ZLAN-47, for more information.
6.2.2
Rx Interface
The Rx interface is mainly responsible for communicating with the RxMAC. It keeps track of the start and end of
frame and frame status (good or bad). Upon receiving an end of frame that is good, the Rx interface makes a switch
request.
33
Zarlink Semiconductor Inc.
ZL50404
6.2.3
Data Sheet
RxDMA
The RxDMA arbitrates among switch requests from each Rx interface. It also buffers the first 64 bytes of each
frame for use by the search engine when the switch request has been made.
6.2.4
TxQ Manager
First, the TxQ manager checks the per-class queue status and global reserved resource situation, and using this
information, makes the frame dropping decision after receiving a switch response. The dropping decision includes
the head-of-link blocking avoidance if the source port is not flow control enabled. If the decision is not to drop, the
TxQ manager links the unicast frame’s FCB to the correct per-port-per-class TxQ and updates the FCB information.
If multicast, the TxQ manager writes to the multicast queue for that port and class and also update the FCB
information including the duplicate count for this multicast frame. The TxQ manager can also trigger source port
flow control for the incoming frame’s source if that port is flow control enabled. Second, the TxQ manager handles
transmission scheduling; it schedules transmission among the queues representing different classes for a port.
Once a frame has been scheduled, the TxQ manager reads the FCB information and writes to the correct port
control module. The detail of the QoS decision guideline is described in chapter 5.
6.2.5
Port Control
The port control module calculates the SRAM read address for the frame currently being transmitted. It also writes
start of frame information and an end of frame flag to the MAC TxFIFO. When transmission is done, the port control
module requests that the buffer be released.
6.2.6
TxDMA
The TxDMA multiplexes data and address from port control, and arbitrates among buffer release requests from the
port control modules.
7.0
Quality of Service and Flow Control
7.1
Model
Quality of service is an all-encompassing term for which different people have different interpretations. In general,
the approach to quality of service described here assumes that we do not know the offered traffic pattern. We also
assume that the incoming traffic is not policed or shaped. Furthermore, we assume that the network manager
knows his applications, such as voice, file transfer, or web browsing, and their relative importance. The manager
can then subdivide the applications into classes and set up a service contract with each. The contract may consist
of bandwidth or latency assurances per class. Sometimes it may even reflect an estimate of the traffic mix offered
to the switch. As an added bonus, although we do not assume anything about the arrival pattern, if the incoming
traffic is policed or shaped, we may be able to provide additional assurances about our switch’s performance.
Table 7 shows examples of QoS applications with three transmission priorities, but best effort (P0) traffic may form
a fourth class with no bandwidth or latency assurances. MMAC port actually has four total transmission priorities.
34
Zarlink Semiconductor Inc.
ZL50404
Goals
TotalAssured
Bandwidth
(user defined)
Data Sheet
Low Drop Probability
(low-drop)
High Drop Probability
(high-drop)
Highest
transmission
priority, P3
50 Mbps
Apps: phone calls, circuit
emulation.
Latency: < 1 ms.
Drop: No drop if P3 not
oversubscribed.
Apps: training video.
Latency: < 1 ms.
Drop: No drop if P3 not
oversubscribed; first P3 to drop
otherwise.
Middle
transmission
priority, P2
37.5 Mbps
Apps: interactive apps, Web
business.
Latency: < 4-5 ms.
Drop: No drop if P2 not
oversubscribed.
Apps: non-critical interactive apps.
Latency: < 4-5 ms.
Drop: No drop if P2 not
oversubscribed; firstP2 to drop
otherwise.
Low transmission
priority, P1
12.5 Mbps
Apps: emails, file backups.
Latency: < 16 ms desired, but
not critical.
Drop: No drop if P1 not
oversubscribed.
Apps: casual web browsing.
Latency: < 16 ms desired, but not
critical.
Drop: No drop if P1 not
oversubscribed; first to drop
otherwise.
Total
100 Mbps
Table 7 - Two-dimensional World Traffic
A class is capable of offering traffic that exceeds the contracted bandwidth. A well-behaved class offers traffic at a
rate no greater than the agreed-upon rate. By contrast, a misbehaving class offers traffic that exceeds the
agreed-upon rate. A misbehaving class is formed from an aggregation of misbehaving microflows. To achieve high
link utilization, a misbehaving class is allowed to use any idle bandwidth. However, such leniency must not degrade
the quality of service (QoS) received by well-behaved classes.
As Table 7 illustrates, the six traffic types may each have their own distinct properties and applications. As shown,
classes may receive bandwidth assurances or latency bounds. In the table, P3, the highest transmission class,
requires that all frames be transmitted within 1 ms, and receives 50% of the 100 Mbps of bandwidth at that port.
Best-effort (P0) traffic forms a fourth class that only receives bandwidth when none of the other classes have any
traffic to offer. It is also possible to add a fourth class that has strict priority over the other three; if this class has
even one frame to transmit, then it goes first. In the ZL50404, each RMAC port will support two total classes, and
the MMAC port will support four classes. We will discuss the various modes of scheduling these classes in the next
section.
In addition, each transmission class has two subclasses, high-drop and low-drop. Well-behaved users should rarely
lose packets. But poorly behaved users–users who send frames at too high a rate – will encounter frame loss, and
the first to be discarded will be high-drop. Of course, if this is insufficient to resolve the congestion, eventually some
low-drop frames are dropped, and then all frames in the worst case.
Table 7 shows that different types of applications may be placed in different boxes in the traffic table. For example,
casual web browsing fits into the category of high-loss, high-latency-tolerant traffic, whereas VoIP fits into the
category of low-loss, low-latency traffic.
7.2
Two QoS Configurations
There are two basic pieces to QoS scheduling in the MMAC port of ZL50404: strict priority (SP) or weighted fair
queuing (WFQ). The only configuration for a RMAC and CPU port is strict priority between the queues.
35
Zarlink Semiconductor Inc.
ZL50404
7.2.1
Data Sheet
Strict Priority
When strict priority is part of the scheduling algorithm, if a queue has any frame to transmit, it goes first. For RMAC
ports, this is an easy way to provide the different service. For all recognizable traffic, the bandwidth is guaranteed to
100% of the line rate. This scheme works as long as the overall high priority bandwidth is not over the line rate and
the latency on all the low priority traffic is don’t care. The strict priority queue in the MMAC and CPU ports is similar
to RMAC ports other than having 4 queues instead of 2 queues. The priority queue P0 can be scheduled only if the
priority queue P1 is empty, so as to priority queues P2 and P3. The lowest priority queue is treated as best effort
queue.
Because we do not provide any assurances for best effort traffic, we do not enforce latency by dropping best effort
traffic. Furthermore, because we assume that strict priority traffic is carefully controlled before entering the
ZL50404, we do not enforce a fair bandwidth partition by dropping strict priority traffic. To summarize, dropping to
enforce bandwidth or delay does not apply to strict priority or best effort queues. We only drop frames from best
effort and strict priority queues when queue size is too long or global / class buffer resources become scarce.
7.2.2
Weighted Fair Queuing
In some environments – for example, in an environment in which delay assurances are not required, but precise
bandwidth partitioning on small time scales is essential, WFQ may be preferable to a strict assurance scheduling
discipline. The ZL50404 provides this kind of scheduling algorithm on MMAC port only. The user sets four WFQ
“weights” such that all weights are whole numbers and sum to 64. This provides per-class bandwidth partitioning
with granular within 2%.
In WFQ mode, though we do not assure frame latency, the ZL50404 still retains a set of dropping rules that helps to
prevent congestion and trigger higher level protocol end-to-end flow control.
7.3
WRED Drop Threshold Management Support
To avoid congestion, the Weighted Random Early Detection (WRED) logic drops packets according to specified
parameters. The following table summarizes the behavior of the WRED logic.
Px > WRED_L1
Px > WRED_L2
BM Reject
High Drop
X%
100%
100%
Low Drop
Y%
Z%
100%
Table 8 - WRED Logic Behaviour
Px is the total byte count, in the priority queue x, can be the strict priority queue of RMAC ports and higher 3 priority
queues for MMAC port. The WRED logic has two drop levels, depending on the value of Px. Each drop level has
defined high-drop and low-drop percentages, which indicate the minimum and maximum percentages of the data
that can be discarded. The X, Y Z percent can be programmed by the register RDRC0, RDRC1. All packets will be
dropped only if the system runs out of the specific buffer resource, per class buffer or per source port buffer. The
WRED thresholds of each queue can be programmed by the QOS control registers (refer to the register group 8).
See Programming QoS Registers application note, ZLAN-42, for more information.
7.4
Shaper
Although traffic shaping is not a primary function of the ZL50404, the chip does implement a shaper for every queue
in the MMAC port. Our goal in shaping is to control the average rate of traffic exiting the ZL50404. If shaper is
enabled, strict priority will be applied to that queue. The priority between two shaped queue is the same as in strict
priority scheduling.
Traffic rate is set using a programmable whole number, no greater than 64. For example, if the setting is 32, then
the traffic rate transmit out of the shaped queue is 32/64 * 1000 Mbps = 500 Mbps. See Programming QoS Register
application note, ZLAN-42, for more information.
36
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
Also, when shaping is enabled, it is possible for a queue to explode in length if fed by a greedy source. The reason
is that a shaper is by definition not work-conserving; that is, it may hold back from sending a packet even if the line
is idle. Though we do have global resource management, we do nothing other than per port WRED to prevent this
situation locally. We assume the traffic is policed at a prior stage to the ZL50404 or WRED dropping is fine and shall
restrain this situation.
7.5
Rate Control
The ZL50404 provides a rate control function on its RMAC ports. This rate control function applies to both the
incoming and outgoing traffic aggregate on each RMAC port. It provides a way of reducing the average rate below
full wire speed. Note that the rate control function does not shape or manipulate any particular traffic class.
Furthermore, though the average rate of the port can be controlled with this function, the peak rate will still be full
line rate.
Two principal parameters are used to control the average rate for a RMAC port. A port’s rate is controlled by
allowing, on average, M bytes to be transmitted every N microseconds. Both of these values are programmable.
The user can program the number of bytes in 8-byte increments, and the time may be set in units of 10us or 1ms.
The value of M/N will, of course, equal the average data rate of the traffic aggregate on the given RMAC port.
Although there are many (M,N) pairs that will provide the same average data rate performance, the smaller the time
interval N, the “smoother” the output pattern will appear.
In addition to controlling the average data rate on a RMAC port, the rate control function also manages the
maximum burst size at wire speed. The maximum burst size can be considered the memory of the rate control
mechanism; if the line has been idle for a long time, to what extent can the port “make up for lost time” by
transmitting a large burst? This value is also programmable, measured in 8-byte increments.
Example: Suppose that the user wants to restrict Fast Ethernet port P’s average departure rate to 32 Mbps – 32%
of line rate – when the average is taken over a period of 10 ms. In an interval of 10 ms, exactly 40000 bytes can be
transmitted at an average rate of 32 Mbps.
So how do we set the parameters?
The rate control parameters are contained in an internal RAM block
accessible through the CPU port (See Rate Control application note, ZLAN-33). The data format is shown below.
63:40
39:32
31:16
15:0
0
Time interval
Maximum burst size
Number of bytes
As we indicated earlier, the number of bytes is measured in 8-byte increments, so the 16-bit field “Number of bytes”
should be set to 40000/8, or 5000. In addition, the time interval has to be set to 10 in units of 1 ms. Though we want
the average data rate on port P to be 32 Mbps when measured over an interval of 10 ms, we can also adjust the
maximum number of bytes that can be transmitted at full line rate in any single burst. Suppose we wish this limit to
be 12 kilobytes. The number of bytes is measured in 8-byte increments, so the 16-bit field “Maximum burst size” is
set to 12000/8, or 1500.
The action on the incoming traffic and outgoing traffic when credit is not available are different. For the outgoing
traffic, the queued frames will be held in the queue until the credit become available. The consequence of this
holding is the exploding queue size that may cause dropping on the receiving side. The capability of ZL50404 on
this perspective is quite limited due to the small frame buffer on chip. The actions on the incoming traffic depending
on the flow control state of that port. If the ingress port flow control is turned on, the XOFF flow control will be
triggered when the credit is running lower than half of the maximum burst size. The XON will be triggered when the
available credit is increased to above the threshold. If the port flow control is disabled, the received traffic will
subject to WRED depending on the credit availability. If the none of the credit is available, all received frame will be
dropped. If only a quarter of maximum burst credits are available, the frame that been marked as high drop will be
drop 100%, the low drop frame will be dropped at ra%, If half of the maximum burst credits are available, high drop
frame will be dropped at rb%. The ra% and rb% can be programmed by RDRC2 register.
37
Zarlink Semiconductor Inc.
ZL50404
7.6
Data Sheet
Buffer Management
Because the number of FDB slots is a scarce resource, and because we want to ensure that one misbehaving
source port or class cannot harm the performance of a well-behaved source port or class, we introduce the concept
of buffer management into the ZL50404. Our buffer management scheme is designed to divide the total buffer
space into numerous reserved regions and one shared pool, as shown in Figure 8 on page 38.
As shown in the figure, the FDB pool is divided into several parts. A reserved region for temporary frames stores
frames prior to receiving a switch response. Such a temporary region is necessary, because when the frame first
enters the ZL50404, its destination port and class are as yet unknown, and so the decision to drop or not needs to
be temporarily postponed. This ensures that every frame can be received first before subjecting them to the frame
drop discipline after classifying.
Three priority sections, one for each pair of the first six priority classes, ensure a programmable number of FDB
slots per class. The lowest two classes do not receive any buffer reservation. Furthermore, a frame is stored in the
region of the FDB corresponding to its class. As we have indicated, the eight classes use only two transmission
scheduling queues for RMAC ports (four queues for the MMAC & CPU ports), but as far as buffer usage is
concerned, there are still eight distinguishable classes.
Another segment of the FDB reserves space for each of the 6 ports — 5 ports for Ethernet and one CPU port (port
number 8). Each port has it’s own programmable source port reservation. These 6 reserved regions make sure that
no well-behaved source port can be blocked by another misbehaving source port.
In addition, there is a shared pool, which can store any type of frame. The frame engine allocates the frames first in
the three priority sections. When the priority section is full or the packet has priority 1 or 0, the frame is allocated in
the shared pool. Once the shared pool is full the frames are allocated in the section reserved for the source port.
The following registers define the size of each section of the Frame data Buffer:
-
PR100_N - Port Reservation for RMAC Ports
PR100_CPU - Port Reservation for CPU Port
PRM - Port Reservation for MMAC Port
SFCB - Share FCB Size
C1RS - Class 1 Reserve Size (priority 2 & 3)
C2RS - Class 2 Reserve Size (priority 4 & 5)
C3RS - Class 3 Reserve Size (priority 6 & 7)
Temporary reservation
Per Class
Reservation
Per Source Port
Reservation
Rpri1
Rp0
Rpri2
Rp1
Rpri3
Rp2
Rp3
Shared Pool S
Rp8
(CPU)
Figure 8 - Buffer Partition Scheme
See Buffer Allocation application note, ZLAN-47, for more information.
38
Zarlink Semiconductor Inc.
Rp9
ZL50404
7.6.1
Data Sheet
Dropping When Buffers Are Scarce
As already discussed, the WRED mechanism may drop frames on output queue status. In addition to these
reasons for dropping, we also drop frames when global buffer space becomes scarce. The function of buffer
management is to make sure that such dropping causes as little blocking as possible. If a received frame is
dispatched to the best effort queue, the buffer management will check on the overall buffer situation plus the output
queue status to decide the frame drop condition. If the source port has not enough buffer for it, the frame will be
dropped. If the output queue reach the UCC (unicast congest control) and the shared buffer has run out, the frame
will be dropped by b%. If the output queue reach the UCC and the source port reservation is lower than the buffer
low threshold, the frame will be dropped. All the dropping functions are disabled if the source port is flow control
capable.
7.7
Flow Control Basics
Because frame loss is unacceptable for some applications, the ZL50404 provides a flow control option. When flow
control is enabled, scarcity of source port buffer space may trigger a flow control signal; this signal tells a source
port sending a packet to this switch, to temporarily hold off.
While flow control offers the clear benefit of no packet loss, it also introduces a problem for quality of service. When
a source port receives an Ethernet flow control signal, all microflows originating at that port, well-behaved or not,
are halted. A single packet destined for a congested output can block other packets destined for un-congested
outputs. The resulting head-of-line blocking phenomenon means that quality of service cannot be assured with high
confidence when flow control is enabled.
On the other hand, the ZL50404 will still prioritize the received frame disregarding the outgoing port flow control
capability. If a frame is classified as high priority, it is still subjected to the WRED, which means the no-loss on the
high priority queue is not guaranteed. To resolve this situation, the user may set the output port WRED threshold so
high that may never be reached, or program the priority mapping table in the queue manager to map all the traffic to
best effort queue on the flow control capable port. The first method has side impact on the global resource
management since the port may hold too much per class resource that is scarce in the system. The second
method, by nature, lost the benefit of prioritization.
See Programming Flow Control Registers application note, ZLAN-44, for more information.
7.7.1
Unicast Flow Control
For unicast frames, flow control is triggered by source port resource availability. Recall that the ZL50404’s buffer
management scheme allocates a reserved number of FDB slots for each source port. If a programmed number of a
source port’s reserved FDB slots have been used, then flow control Xoff is triggered.
Xon is triggered when a port is currently being flow controlled, and all of that port’s reserved FDB slots have been
released.
Note that the ZL50404’s per-source-port FDB reservations assure that a source port that sends a single frame to a
congested destination will not be flow controlled.
7.7.2
Multicast Flow Control
Flow control for multicast frames is triggered by a global buffer counter. When the system exceeds a programmable
threshold of multicast packets, Xoff is triggered. Xon is triggered when the system returns below this threshold.
Note: If per-port flow control is on, QoS performance will be affected.
7.8
Mapping to IETF Diffserv Classes
The mapping between priority classes discussed in this chapter and elsewhere is shown below.
39
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
ZL50404
P3
P2
P1
P0
IETF
NM+EF
AF0
AF1
BE
Table 9 - Mapping to IETF Diffserv Classes for MMAC & CPU Ports
As the table illustrates, the classes of Table 9 are merged in pairs— P3 is used for network management (NM) and
expedited forwarding service (EF) frames. Classes P2 and P1 correspond to an assured forwarding (AF) group of
size 2. Finally, P0 is for best effort (BE) class.
Features of the ZL50404 that correspond to the requirements of their associated IETF classes are summarized in
the table below.
Network management (NM) and
Expedited forwarding (EF)
Global buffer reservation for NM and EF
Shaper for traffic on uplink port
No dropping if admission controlled
Assured forwarding (AF)
Global buffer reservation for two AF classes
Shaper for traffic on uplink port
Random early discard, with programmable levels
Best effort (BE)
Service only when other queues are idle means that QoS not
adversely affected
Shaper for traffic on uplink port
Random early discard, with programmable levels
Traffic from flow control enabled ports automatically classified as BE
Table 10 - ZL50404 Features Enabling IETF Diffserv Standards
7.9
Failover Backplane Feature
The ZL50404 implements a hardware assisted link failure detection mechanism utilizing a Link Heart Beat (LHB)
packet. The LHB packet format is defined as a 64-byte MAC control frame with a user defined opcode. The packet
format is illustrated below:
01-80-c2-00-00-01
xx-xx-xx-xx-xx-xx
88-08
yy-yy
00-00-...
CRC
Where “xx-xx-...” is the source port MAC address and “yy-yy” is the special opcode defined by register setup
(LHBReg0,1). The opcode “00-01” is reserved for the flow control packet. We recommend opcode “00-12” for the
LHB packet.
The LHB is done between two compatible MACs providing this function. A timer parameter will be set for both the
receiver and transmitter (LHBTimer).
On the transmission side, the MAC will monitor the transmission activities. If there is no activity for more than the
set period, a LHB packet will be sent to its link partner. Therefore, there should always be at least one packet
transmitted from the MAC for every period specified.
On the receiving side, the MAC will also monitor the activity. If there is no good packet received for more than 2X
the set period, an alarm will be raised to the CPU. The LHB packet is only used by the ZL50404 to reset the timeout
counter, it is ignored otherwise (i.e. not passed on within the system).
See the Failover Protection Application Note, ZLAN-43, for more information.
40
Zarlink Semiconductor Inc.
ZL50404
8.0
Data Sheet
Port Trunking
See Port Trunking application note, ZLAN-48, for more information.
8.1
Features and Restrictions
A port group (i.e. trunk) can include up to 4 physical ports to form a fault tolerant link. There are eight trunk groups
total.
Load distribution among the ports in a trunk for unicast is performed using hashing based on source MAC address
and destination MAC address. Three other options include source MAC address only, destination MAC address
only, and source port (in bidirectional ring mode only). Load distribution for multicast is performed similarly.
The ZL50404 also provides a safe fail-over mode for port trunking automatically. If one of the ports in the trunking
group goes down, the ZL50404 can redistribute the traffic over to the remaining ports in the trunk with software
assistance.
8.2
Unicast Packet Forwarding
The search engine finds the destination MCT entry, and if the status field says that the destination port found
belongs to a trunk, then the trunk group number is retrieved.
The source port of the packet is checked against the destination trunk group. If the source port belongs to the
destination trunk group, the packet is discarded.
A hash key, based on some combination of the source and destination MAC addresses for the current packet,
selects the appropriate forwarding port, as specified in the Trunk_Hash registers. Each trunk has eight trunk_hash
registers which selects one of the potential eight outgoing ports. The hash key provides a pseudo flow identifier
which force the same flow to the same destination flow. As a result, the packet will always arrive in order.
8.3
Multicast Packet Forwarding
For multicast packet forwarding, the device must determine the proper set of ports from which to transmit the
packet based on the hash key.
Three functions are required in order to distribute multicast packets to the appropriate destination ports in a port
trunking environment.
•
•
The source port/group must be excluded from the forwarding.
Select one port per trunk group to forward the packet to. This selection is based on hash key described in
previous section.
For example, port 0,1 and 2 belong to trunk group 0 and port 3 and 4 belong to trunk group 1. A single VLAN is
established in this system with port 0,1,2,3,4,5 and 6 as the members in the VLAN. When a multicast packet is sent
in from port 3, the ZL50404 select port 0,1,2,3,4,5 and 6 as potential destination based on the VLAN. Then port 3
and 4 are removed because they belong to the source port group (trunk group 1). Two ports from trunk group 0 will
be removed based on the hash key. In this example, we assume port 0 and 1 are removed. As a result, port 2,5 and
6 are the only outgoing ports for this multicast packet.
9.0
Traffic Mirroring
See Traffic Mirroring application note, ZLAN-50, for more information.
9.1
Mirroring Features
Packets can be mirrored (duplicated) for network monitor purpose and/or network debug purpose. Three types of
mirroring is available in ZL50404.
41
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
1. Source or Destination MAC address based
2. Flow based
3. Port based
In source or destination mac address based mirroring, the “M” bit of the mirroring MAC address in the MCT is set.
Also, the user need to specify the mirroring MAC address is source or destination of the packet. If source is
selected, any packet received with the mirroring MAC address as source MAC address will be copied to the
mirrored port. In the same way, if destination is selected, any packet received with mirroring MAC address as
destination MAC address will be copied to the mirrored port.
In flow based mirroring, a flow is established based on the source and destination mac address pair. When
enabled, a packet with source and destination address match the pre-programmed source and destination mac
address pair will be copied to the mirrored port. In reverse direction (source and destination match pre programmed
destination and source), the flow can also be enabled and the frame will be copied to the mirrored port.
In port based mirroring, traffic from any RMAC port can be mirrored to any RMAC port. The traffic from the source
port can be either ingress or egress traffic. Up to two ports can be setup as mirrored ports. As a result, the traffic
(both ingress and egress) of a specific port can be monitored by setting up both mirrored ports. Once a port is setup
as mirrored port, it cannot be used for regular traffic.
The mirrored port can be any port in the ZL50404.
9.2
Using port mirroring for loop back
To perform remote loop back test, port mirroring can be used to bounce back the packet to the source port to check
the data path.
The CPU needs to setup the remote device through the command channel to enable port mirroring in the remote
device. A CPU packet is send to the port in test in Device A. The packet will be forwarded to the test port, external
cable, the destination port in Device B, and loop back to itself, back to the cable and go back to Device A and the
CPU. This way, the whole channel can be tested.
CPU
DEVICE B
DEVICE A
Figure 9 - Remote Loopback Test
10.0
GPSI (7WS) Interface
10.1
GPSI connection
The RMAC ethernet port can function in GPSI (7WS) mode. In this mode, the TXD[0], RXD[0] serve as TX data, RX
data and respectively. The link and duplex of the port can be controlled by programming the ECR register. Only
port-based VLAN is supported with GPSI interface.
42
Zarlink Semiconductor Inc.
ZL50404
11.0
Clocks
11.1
Clock Requirements
11.1.1
Data Sheet
System Clock (SCLK) speed requirement
SCLK is the primary clock for the ZL50404 device. The speed requirement is based on the system configuration.
Below is a table for a few configuration.
Minimum SCLK speed
required
Configuration
1-5 ports 10/100M
25 Mhz
Table 11 - SCLK Speed Requirements
11.1.2
RMAC Reference Clock (M_CLK) speed requirement
M_CLK is a 50 MHz clock used for the RMAC ports (ports 0-3).
If none of the RMAC ports are configured in RMII mode or Reverse MII mode, a different clock frequency can be
applied to M_CLK, as long as it's less than 50 MHz. In this case, register USD must be set to provide an internal
1usec timing.
11.1.3
MMAC Reference Clock (REF_CLK) speed requirement
REF_CLK is a reference clock required for the MMAC port (port 9).
If the device is in a 9 port 10/100 configuration only, REF_CLK can be a lower frequency clock and can be
connected to M_CLK to reduce the number of clock sources.
If port 9 is not being used, REF_CLK can be left unconnected.
11.1.4
JTAG Test Clock (TCK) speed requirements
TCK is a clock used for the JTAG port. The frequency on this clock can vary. Refer to “JTAG (IEEE 1149.1-2001)”
on page 118 for the frequency range.
11.2
11.2.1
Clock Generation
MDC
MDC is used for the MII Management Interface and clocks data on MDIO. It is generated by the device from
M_CLK and is equal to 500 kHz (M_CLK/100). If a different speed clock other than 50MHz is used on M_CLK, the
USD register must be programmed to reset MDC.
11.2.2
SCL
SCL is used for the I2C interface and clocks data on SDA. It is generated by the device from M_CLK and is equal
to 50kHz (M_CLK/1000). If a different speed clock other than 50MHz is used on M_CLK, the USD register must be
programmed to reset SCL.
11.2.3
Ethernet Interface Clocks
If the RMAC ports are configured in Reverse MII mode, TXCLK and RXCLK are generated from M_CLK and are
equal to M_CLK/2 for 100M mode or M_CLK/20 for 10M mode. M_CLK needs to be a 50 MHz clock in this mode.
43
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
If the RMAC ports are configured in Reverse GPSI mode, TXCLK and RXCLK are generated from M_CLK and are
equal to M_CLK/2 for 10M mode. M_CLK needs to be a 20 MHz clock in this mode and USD must be programmed
accordingly.
If the MMAC port is configured in Reverse MII mode, RXCLK is generated from REF_CLK and is equal to
REF_CLK/2 for 100M mode (no support for 10M Reverse MII mode). REF_CLK needs to be a 50 MHz clock in this
mode.
12.0
Hardware Statistics Counters
12.1
Hardware Statistics Counters List
ZL50404 hardware provides a full set of statistics counters for each Ethernet port. The CPU accesses these
counters through the CPU interface. All hardware counters are rollover counters. When a counter rolls over, the
CPU is interrupted, so that long-term statistics may be kept. The MAC detects all statistics, except for the delay
exceed discard counter (detected by buffer manager) and the filtering counter (detected by queue manager). The
following is the wrapped signal sent to the CPU through the command block.
63
30
Other Status Bits
29
0
Status Wrapped Signal
B[0]
0-d
Bytes Sent (D)
B[1]
1-L
Unicast Frame Sent
B[2]
1-U
Frame Send Fail
B[3]
2-I
Flow Control Frames Sent
B[4]
2-u
Non-Unicast Frames Sent
B[5]
3-d
Bytes Received (Good and Bad) (D)
B[6]
4-d
Frames Received (Good and Bad) (D)
B[7]
5-d
Total Bytes Received (D)
B[8]
6-L
Total Frames Received
B9]
6-U
Flow Control Frames Received
B[10]
7-l
Multicast Frames Received
B[11]
7-u
Broadcast Frames Received
B[12]
8-L
Frames with Length of 64 Bytes
B[13]
8-U
Jabber Frames
B[14]
9-L
Frames with Length Between 65-127 Bytes
B[15]
9-U
Oversize Frames
44
Zarlink Semiconductor Inc.
ZL50404
B[16]
A-l
Frames with Length Between 128-255 Bytes
B[17]
A-u
Frames with Length Between 256-511 Bytes
B[18]
B-l
Frames with Length Between 512-1023 Bytes
B[19]
B-u
Frames with Length Between 1024-1528 Bytes
B[20]
C-l
Fragments
B[21]
C-U1
Alignment Error
B[22]
C-U
Undersize Frames
B[23]
D-l
CRC
B[24]
D-u
Short Event
B[25]
E-l
Collision
B[26]
E-u
Drop
B[27]
F-l
Filtering Counter
B[28]
F-U1
Delay Exceed Discard Counter
B[29]
F-U
Late Collision
Notation: X-Y
X:
Address in the contain memory
Y:
Size and bits for the counter
d:
D Word counter
L:
24 bits counter bit [23:0]
U:
8 bits counter bit [31:24]
U1:
8 bits counter bit [23:16]
l:
16 bits counter bit [15:0]
u:
16 bits counter bit [31:16]
45
Zarlink Semiconductor Inc.
Data Sheet
ZL50404
12.2
Data Sheet
IEEE 802.3 HUB Management (RFC 1516)
12.2.1
12.2.1.1
Event Counters
ReadableOctet
Counts number of bytes (i.e. octets) contained in good valid frames received.
Frame size:
> 64 bytes,
< 1522 bytes if VLAN Tagged;
(< 1518 bytes if not VLAN Tagged)
No FCS (i.e. checksum) error
No collisions
12.2.1.2
ReadableFrame
Counts number of good valid frames received.
Frame size:
> 64 bytes,
< 1522 bytes if VLAN Tagged;
(< 1518 bytes if not VLAN Tagged)
No FCS error
No collisions
12.2.1.3
FCSErrors
Counts number of valid frames received with bad FCS.
Frame size:
> 64 bytes,
< 1522 bytes if VLAN Tagged;
(< 1518 bytes if not VLAN Tagged)
No framing error
No collisions
12.2.1.4
AlignmentErrors
Counts number of valid frames received with bad alignment (not byte-aligned).
Frame size:
> 64 bytes,
< 1522 bytes if VLAN Tagged;
(< 1518 bytes if not VLAN Tagged)
No framing error
No collisions
46
Zarlink Semiconductor Inc.
ZL50404
12.2.1.5
Data Sheet
FrameTooLongs
Counts number of frames received with size exceeding the maximum allowable frame size.
Frame size:
> 64 bytes,
> 1522 bytes if VLAN Tagged;
(> 1518 bytes if not VLAN Tagged)
FCS error:
don’t care
Framing error:
don’t care
No collisions
12.2.1.6
ShortEvents
Counts number of frames received with size less than the length of a short event.
Frame size:
< 10 bytes
FCS error:
don’t care
Framing error:
don’t care
No collisions
12.2.1.7
Runts
Counts number of frames received with size under 64 bytes, but greater than the length of a short event.
Frame size:
> 10 bytes,
FCS error:
don’t care
Framing error:
don’t care
< 64 bytes
No collisions
12.2.1.8
Collisions
Counts number of collision events.
Frame size:
12.2.1.9
any size
LateEvents
Counts number of collision events that occurred late (after LateEventThreshold = 64 bytes).
Frame size:
any size
Events are also counted by collision counter
47
Zarlink Semiconductor Inc.
ZL50404
12.2.1.10
Data Sheet
VeryLongEvents
Counts number of frames received with size larger than Jabber Lockup Protection Timer (TW3).
Frame size:
12.2.1.11
> Jabber
DataRateMisatches
For repeaters or HUB application only.
12.2.1.12
AutoPartitions
For repeaters or HUB application only.
12.2.1.13
TotalErrors
Sum of the following errors:
•
•
•
•
•
•
•
FCSErrors
AlignmentErrors
FrameTooLong
ShortEvents
LateEvents
VeryLongEvents
DataRateMisatches
12.3
IEEE 802.1 Bridge Management (RFC 1286)
12.3.1
12.3.1.1
Event Counters
InFrames
Counts number of frames received by this port or segment.
Note: A frame received by this port is only counted by this counter if and only if it is for a protocol being processed
by the local bridge function.
12.3.1.2
OutFrames
Counts number of frames transmitted by this port.
Note: A frame transmitted by this port is only counted by this counter if and only if it is for a protocol being
processed by the local bridge function.
12.3.1.3
InDiscards
Counts number of valid frames received which were discarded (i.e., filtered) by the forwarding process.
12.3.1.4
DelayExceededDiscards
Counts number of frames discarded due to excessive transmit delay through the bridge.
12.3.1.5
MtuExceededDiscards
Counts number of frames discarded due to excessive size.
48
Zarlink Semiconductor Inc.
ZL50404
12.4
Data Sheet
RMON – Ethernet Statistic Group (RFC 1757)
12.4.1
12.4.1.1
Event Counters
Drop Events
Counts number of times a packet is dropped, because of lack of available resources. DOES NOT include all packet
dropping -- for example, random early drop for quality of service support.
12.4.1.2
Octets
Counts the total number of octets (i.e. bytes) in any frames received.
12.4.1.3
BroadcastPkts
Counts the number of good frames received and forwarded with broadcast address.
Does not include non-broadcast multicast frames.
12.4.1.4
MulticastPkts
Counts the number of good frames received and forwarded with multicast address.
Does not include broadcast frames.
12.4.1.5
CRCAlignErrors
Counts number of frames received with FCS or alignment errors
Frame size:
> 64 bytes,
< 1522 bytes if VLAN Tagged;
(< 1518 bytes if not VLAN Tagged)
No collisions:
12.4.1.6
UndersizePkts
Counts number of frames received with size less than 64 bytes.
Frame size:
< 64 bytes,
No FCS error
No framing error
No collisions
49
Zarlink Semiconductor Inc.
ZL50404
12.4.1.7
Data Sheet
OversizePkts
Counts number of frames received with size exceeding the maximum allowable frame size.
Frame size:
> 1522 bytes if VLAN Tagged;
(> 1518 bytes if not VLAN Tagged)
FCS error
don’t care
Framing error
don’t care
No collisions
12.4.1.8
Fragments
Counts number of frames received with size less than 64 bytes and with bad FCS.
Frame size:
< 64 bytes
Framing error
don’t care
No collisions
12.4.1.9
Jabbers
Counts number of frames received with size exceeding maximum frame size and with bad FCS.
Frame size:
> 1522 bytes if VLAN Tagged;
(> 1518 bytes if not VLAN Tagged)
Framing error
don’t care
No collisions
12.4.1.10
Collisions
Counts number of collision events detected.
Only a best estimate since collisions can only be detected while in transmit mode, but not while in receive mode.
Frame size:
12.4.1.11
any size
Packet Count for Different Size Groups
Six different size groups – one counter for each:
Pkts64Octets
for any packet with size = 64 bytes
Pkts65to127Octets
for any packet with size from 65 bytes to 127 bytes
Pkts128to255Octets
or any packet with size from 128 bytes to 255 bytes
Pkts256to511Octets
for any packet with size from 256 bytes to 511 bytes
Pkts512to1023Octets
for any packet with size from 512 bytes to 1023 bytes
50
Zarlink Semiconductor Inc.
ZL50404
Pkts1024to1518Octets
Data Sheet
for any packet with size from 1024 bytes to 1518 bytes
Counts both good and bad packets.
12.5
Miscellaneous Counters
In addition to the statistics groups defined in previous sections, the ZL50404 has other statistics counters for its own
purposes. We have two counters for flow control – one counting the number of flow control frames received, and
another counting the number of flow control frames sent. We also have two counters, one for unicast frames sent,
and one for non-unicast frames sent. A broadcast or multicast frame qualifies as non-unicast. Furthermore, we
have a counter called “frame send fail.” This keeps track of FIFO under-runs, late collisions, and collisions that have
occurred 16 times.
51
Zarlink Semiconductor Inc.
ZL50404
13.0
Register Definition
13.1
ZL50404 Register Description
Register
Data Sheet
CPU Addr
(Hex)
Description
R/W
I²C
Addr
(Hex)
Default
0. ETHERNET Port Control Registers (Substitute [n] with Port number (0..3,8,9))
ECR1Pn
Port Control Register 1 for
Port n
000+2n
R/W
000+n
0C0
ECR2Pn
Port Control Register 2 for
Port n
001+2n
R/W
00A+n
000
ECR3Pn
Port Control Register 3 for
Port n
080+2n
R/W
014+n
000
ECR4Pn
Port Control Register 4 for
Port n
081+2n
R/W
01E+n
018
BUF_LIMIT
Frame Buffer Limit
036
R/W
NA
040
FCC
Flow Control Grant Period
037
R/W
NA
003
1. VLAN Control Registers (Substitute [n] with Port number (0..3,8,9))
AVTCL
VLAN Type Code Register
Low
100
R/W
028
000
AVTCH
VLAN Type Code Register
High
101
R/W
029
081
PVMAPn_0
Port n Configuration
Register 0
102+4n
R/W
02A+n
0FF
PVMAPn_1
Port n Configuration
Register 1
103+4n
R/W
034+n
0FF
PVMAPn_3
Port n Configuration
Register 3
105+4n
R/W
03E+n
000
PVMODE
VLAN Operating Mode
170
R/W
048
000
2. TRUNK Control Registers (Substitute [n] with Trunk Group number (0..7))
TRUNKn
Trunk Group n
200+n
R/W
NA
000
TRUNKn_HASH10
Trunk Group n Hash 10
Destination Port
208+4n
R/W
NA
000
TRUNKn_HASH32
Trunk Group n Hash 32
Destination Port
209+4n
R/W
NA
000
TRUNKn_HASH54
Trunk Group n Hash 54
Destination Port
20A+4n
R/W
NA
000
TRUNKn_HASH76
Trunk Group n Hash 76
Destination Port
20B+4n
R/W
NA
000
MULTICAST_HASHn-0
Multicast hash result n
mask byte 0
228+2n
R/W
NA
0FF
Table 12 - Register Description
52
Zarlink Semiconductor Inc.
Notes
ZL50404
Register
MULTICAST_HASHn-1
Description
Multicast hash result n
mask byte 1
Data Sheet
CPU Addr
(Hex)
R/W
I²C
Addr
(Hex)
Default
229+2n
R/W
NA
0FF
Notes
3. CPU Port Configuration
MAC0
CPU MAC Address byte 0
300
R/W
NA
000
MAC1
CPU MAC Address byte 1
301
R/W
NA
000
MAC2
CPU MAC Address byte 2
302
R/W
NA
000
MAC3
CPU MAC Address byte 3
303
R/W
NA
000
MAC4
CPU MAC Address byte 4
304
R/W
NA
000
MAC5
CPU MAC Address byte 5
305
R/W
NA
000
INT_MASK0
Interrupt Mask 0
306
R/W
NA
000
INTP_MASKn
Interrupt Mask for MAC
Port 2n, 2n+1
310+n
R/W
NA
000
RQS
Receive Queue Select
323
R/W
NA
000
RQSS
Receive Queue Status
324
RO
NA
NA
MAC01
Increment MAC port 0,1
address
325
R/W
NA
000
MAC23
Increment MAC port 2,3
address
326
R/W
NA
000
MAC9
Port 9 MAC address byte 5
329
R/W
NA
000
CPUQINS[6:0]
330-336
R/W
NA
000
CPUQINSRPT
337
RO
NA
NA
CPUGRNHDL[1:0]
338-339
RO
NA
NA
CPURLSINFO[4:0]
33A-33E
R/W
NA
000
33F
R/W
NA
000
CPUGRNCTR
4. Search Engine Configurations
AGETIME_LOW
MAC Address Aging Time
Low
400
R/W
049
05C
AGETIME_HIGH
MAC Address Aging Time
High
401
R/W
04A
000
SE_OPMODE
Search Engine Operating
Mode
403
R/W
NA
000
QOSC
QOS Control
500
R/W
04B
000
UCC
Unicast Congestion Control
510
R/W
068
006
5. Global QOS Control
Table 12 - Register Description (continued)
53
Zarlink Semiconductor Inc.
(n=0..4)
ZL50404
Register
Description
Data Sheet
CPU Addr
(Hex)
R/W
I²C
Addr
(Hex)
Default
MCC
Multicast Congestion
Control
511
R/W
069
006
MCCTH
Multicast Congestion
Threshold
512
R/W
NA
003
RDRC0
WRED Drop Rate Control 0
513
R/W
090
000
RDRC1
WRED Drop Rate Control 1
514
R/W
091
000
RDRC2
WRED Drop Rate Control 2
515
R/W
NA
000
SFCB
Share FCB Size
518
R/W
074
000
C1RS
Class 1 Reserve Size
519
R/W
075
000
C2RS
Class 2 Reserve Size
51A
R/W
076
000
C3RS
Class 3 Reserve Size
51B
R/W
077
000
AVPML
VLAN Priority Map Low
530
R/W
056
000
AVPMM
VLAN Priority Map Middle
531
R/W
057
000
AVPMH
VLAN Priority Map High
532
R/W
058
000
AVDM
VLAN Discard Map
533
R/W
05C
000
TOSPML
TOS Priority Map Low
540
R/W
059
000
TOSPMM
TOS Priority Map Middle
541
R/W
05A
000
TOSPMH
TOS Priority Map High
542
R/W
05B
000
TOSDML
TOS Discard Map
543
R/W
05D
000
USER_PROTOCOL_n
User Define Protocol n
550+n
R/W
0B3+n
000
USER_PROTOCOL_
FORCE_DISCARD
User Define Protocol 0 To 7
Force Discard Enable
558
R/W
0BB
000
WLPP10
Well Known Logic Port 0
and 1 Priority
560
R/W
0A8
000
WLPP32
Well Known Logic Port 2
and 3 Priority
561
R/W
0A9
000
WLPP54
Well Known Logic Port 4
and 5 Priority
562
R/W
0AA
000
WLPP76
Well Known Logic Port 6
and 7 Priority
563
R/W
0AB
000
WLPE
Well Known Logic Port 0 To
7 Enable
564
R/W
0AC
000
WLPFD
Well Known Logic Port 0 To
7 Force Discard Enable
565
R/W
0AD
000
Table 12 - Register Description (continued)
54
Zarlink Semiconductor Inc.
Notes
(n=0..7)
ZL50404
Register
Description
Data Sheet
CPU Addr
(Hex)
R/W
I²C
Addr
(Hex)
Default
Notes
(n=0..7)
USER_PORTn_LOW
User Define Logical Port n
Low
570+2n
R/W
092+n
000
USER_PORTn_HIGH
User Define Logical Port n
High
571+2n
R/W
09A+n
000
USER_PORT1:0_
PRIORITY
User Define Logic Port 0
and 1 Priority
590
R/W
0A2
000
USER_PORT3:2_
PRIORITY
User Define Logic Port 2
and 3 Priority
591
R/W
0A3
000
USER_PORT5:4_
PRIORITY
User Define Logic Port 4
and 5 Priority
592
R/W
0A4
000
USER_PORT7:6_
PRI ORITY
User Define Logic Port 6
and 7 Priority
593
R/W
0A5
000
USER_PORT_
ENABLE[7:0]
User Define Logic Port 0 To
7 Enable
594
R/W
0A6
000
USER_PORT_
FORCE_DISCARD[7:0]
User Define Logic Port 0 To
7 Force Discard Enable
595
R/W
0A7
000
RLOWL
User Define Range Low Bit
[7:0]
5A0
R/W
0AE
000
RLOWH
User Define Range Low Bit
[15:8]
5A1
R/W
0AF
000
RHIGHL
User Define Range High Bit
[7:0]
5A2
R/W
0B0
000
RHIGHH
User Define Range High Bit
[15:8]
5A3
R/W
0B1
000
RPRIORITY
User Define Range Priority
5A4
R/W
0B2
000
6. MISC Configuration Register
MII_OP0
MII Register Option 0
600
R/W
0BC
000
MII_OP1
MII Register Option 1
601
R/W
0BD
000
FEN
Feature Registers
602
R/W
0BE
010
MIIC0
MII Command Register 0
603
R/W
NA
000
MIIC1
MII Command Register 1
604
R/W
NA
000
MIIC2
MII Command Register 2
605
R/W
NA
000
MIIC3
MII Command Register 3
606
R/W
NA
000
MIID0
MII Data Register 0
607
RO
NA
NA
MIID1
MII Data Register 1
608
RO
NA
NA
USD
One micro second divider
609
R/W
NA
000
Table 12 - Register Description (continued)
55
Zarlink Semiconductor Inc.
ZL50404
Register
Description
Data Sheet
CPU Addr
(Hex)
R/W
I²C
Addr
(Hex)
Default
DEVICE
Device id and test
60A
R/W
NA
002
SUM
EEPROM Checksum
Register
60B
R/W
0FF
000
LHBTimer
Link heart beat time out
timer
610
R/W
NA
000
LHBReg0
LHB control field value[7:0]
611
R/W
NA
000
LHBReg1
LHB control field value
[15:8]
612
R/W
NA
000
fMACCReg0
Forced MAC control field
value [7:0]
613
R/W
NA
000
fMACCReg1
Forced MAC control field
value [15:8]
614
R/W
NA
000
FCB_BASE_ADDR0
FCB Base Address
Register 0
620
R/W
0BF
000
FCB_BASE_ADDR1
FCB Base Address
Register 1
621
R/W
0C0
060
FCB_BASE_ADDR2
FCB Base Address
Register 2
622
R/W
0C1
000
7. Port Mirroring Controls
MIRROR_DEST_MAC0
Mirror Destination MAC
Address 0
700
R/W
NA
000
MIRROR_DEST_MAC1
Mirror Destination MAC
Address 1
701
R/W
NA
000
MIRROR_DEST_MAC2
Mirror Destination MAC
Address 2
702
R/W
NA
000
MIRROR_DEST_MAC3
Mirror Destination MAC
Address 3
703
R/W
NA
000
MIRROR_DEST_MAC4
Mirror Destination MAC
Address 4
704
R/W
NA
000
MIRROR_DEST_MAC5
Mirror Destination MAC
Address 5
705
R/W
NA
000
MIRROR_SRC_MAC0
Mirror Source MAC
Address 0
706
R/W
NA
000
MIRROR_SRC_MAC1
Mirror Source MAC
Address 1
707
R/W
NA
000
MIRROR_SRC_MAC2
Mirror Source MAC
Address 2
708
R/W
NA
000
MIRROR_SRC_MAC3
Mirror Source MAC
Address 3
709
R/W
NA
000
Table 12 - Register Description (continued)
56
Zarlink Semiconductor Inc.
Notes
ZL50404
Register
Description
Data Sheet
CPU Addr
(Hex)
R/W
I²C
Addr
(Hex)
Default
MIRROR_SRC_MAC4
Mirror Source MAC
Address 4
70A
R/W
NA
000
MIRROR_SRC_MAC5
Mirror Source MAC
Address 5
70B
R/W
NA
000
MIRROR_CONTROL
Port Mirror Control Register
70C
R/W
NA
000
RMAC_MIRROR0
RMAC Mirror 0
710
R/W
NA
000
RMAC_MIRROR1
RMAC Mirror 1
711
R/W
NA
000
Notes
8. Per Port QOS Control
FCRn
Flooding Control Register n
800+n
R/W
04C+n
000
BMRCn
Broadcast/Multicast Rate
Control n
820+n
R/W
05E+n
000
PR100_n
Port Reservation for RMAC
Ports (n=0..3)
840+n
R/W
06A+n
006
‘d1536/1
6=‘d96,
‘d96>>4=
’h6
PR100_CPU
Port Reservation for CPU
Port
848
R/W
073
006
‘d96
PRM
Port Reservation for MMAC
Port
849
R/W
072
024
‘d96x6=‘
d576,
‘d576>>4
=’h24
PTH100_n
Port Threshold for RMAC
Ports (n=0..3)
860+n
R/W
0C2+n
003
½
PTH100_CPU
Port Threshold for CPU
Port
868
R/W
0CB
003
½
PTHM
Port Threshold for MMAC
Port
869
R/W
0CA
012
½
QOSCn
QOS Control n
880+n
R/W
078-08F
000
(n=0..39)
NA
E. System Diagnostic
DTSRL
Test Register Low
E00
R/W
NA
000
DTSRM
Test Register Medium
E01
R/W
NA
001
TESTOUT0
Testmux Output [7:0]
E02
R/O
NA
NA
TESTOUT1
Testmux Output [15:8]
E03
R/O
NA
NA
MASK0
MASK Timeout 0
E10
R/W
0F6
000
MASK1
MASK Timeout 1
E11
R/W
0F7
000
Table 12 - Register Description (continued)
57
Zarlink Semiconductor Inc.
(n=0..3,8,
9)
ZL50404
Register
Description
Data Sheet
CPU Addr
(Hex)
R/W
I²C
Addr
(Hex)
Default
Notes
MASK2
MASK Timeout 2
E12
R/W
0F8
000
MASK3
MASK Timeout 3
E13
R/W
0F9
000
MASK4
MASK Timeout 4
E14
R/W
0FA
000
BOOTSTRAP[2:0]
BOOTSTRAP Read Back
E80-E82
RO
NA
NA
PRTFSMSTn
Ethernet Port n Status
Read Back
E90+n
RO
NA
NA
(n=0..3,8,
9)
PRTQOSSTn
RMAC Port n QOS and
Queue Status
EA0+n
RO
NA
NA
(n=0..3)
PRTQOSST8A
CPU Port QOS and Queue
Status A
EA8
RO
NA
NA
PRTQOSST8B
CPU Port QOS and Queue
Status B
EA9
RO
NA
NA
PRTQOSST9A
MMAC Port QOS and
Queue Status A
EAA
RO
NA
NA
PRTQUSST9B
MMAC Port QOS and
Queue Status B
EAB
RO
NA
NA
CLASSQOSST
Class Buffer Status
EAC
RO
NA
NA
PRTINTCTR
Buffer Interrupt Status
EAD
R/W
NA
000
QMCTRLn
Ports Queue Control Status
EB0+n
R/W
NA
000
QCTRL
Ports Queue Control
EBA
R/W
NA
000
BMBISTR0
Memory bist result
EBB
R/O
NA
NA
BMBISTR1
Memory bist result
EBC
R/O
NA
NA
BMControl
Memory control
EBD
R/W
NA
00F
BUFF_RST
Buffer Reset Pool
EC0
R/W
NA
000
FCBHEADPTR0
FCB Head Pointer [7:0]
EC1
R/W
NA
000
FCB_HEAD_PTR1
FCB Head Pointer [15:8]
EC2
R/W
NA
000
FCB_TAIL_PTR0
FCB Tail Pointer [7:0]
EC3
R/W
NA
000
FCB_TAIL_PTR1
FCB Tail Pointer [15:8]
EC4
R/W
NA
000
FCB_NUM0
FCB Number [7:0]
EC5
R/W
NA
000
FCB_NUM1
FCB Init Start and FCB
Number [14:8]
EC6
R/W
NA
006
BM_RLSFF_CTRL
Read control register
EC7
R/W
NA
000
BM_RLSFF_INFO0
Bm_rlsfifo_info[7:0]
EC8
RO
NA
NA
BM_RLSFF_INFO1
Bm_rlsfifo_info[15:8]
EC9
RO
NA
NA
Table 12 - Register Description (continued)
58
Zarlink Semiconductor Inc.
(n=0..3,8,
9)
ZL50404
Register
Description
Data Sheet
CPU Addr
(Hex)
R/W
I²C
Addr
(Hex)
Default
BM_RLSFF_INFO2
Bm_rlsfifo_info[23:16]
ECA
RO
NA
NA
BM_RLSFF_INFO3
Bm_rlsfifo_info[31:24]
ECB
RO
NA
NA
BM_RLSFF_INFO4
Bm_rlsfifo_info[39:32]
ECC
RO
NA
NA
BM_RLSFF_INFO5
Fifo_cnt[2:0],Bm_rlsfifo_inf
o[44:40]
ECD
RO
NA
NA
GCR
Global Control Register
F00
R/W
NA
000
DCR
Device Control Register
F01
RO
NA
NA
DCR1
Device Control Register 1
F02
RO
NA
NA
DPST
Device Port Status Register
F03
R/W
NA
000
DTST
Data read back register
F04
RO
NA
NA
DA
DA Register
FFF
RO
NA
0DA
F. System Control
Table 12 - Register Description (continued)
59
Zarlink Semiconductor Inc.
Notes
ZL50404
13.2
Directly Accessed Registers
13.2.1
•
•
DATA_FRAME_REG
Data of indirectly accessed registers (8 bits)
Address = 2 (read/write)
13.2.3
•
•
•
INDEX_REG0
Address for indirectly accessed register addresses (16 bits)
Address = 0 (write only)
13.2.2
•
•
Data Sheet
CONTROL_FRAME_REG
CPU transmit/receive switch frames (16 bits)
Address = 3 (read/write)
Format:
8-byte of Frame status (Frame size, Source port #, VLAN tag)
Frame Data (size should be in multiple of 8-byte)
13.2.4
•
•
•
COMMAND&STATUS Register
CPU interface commands and status (8 bits)
Address = 4 (read/write)
When the CPU writes to this register
Bit [0]:
Set Control Frame Receive buffer ready, after CPU writes a complete frame into the buffer. This
bit is self-cleared.
Bit [1]:
Set Control Frame Transmit buffer1 ready, after CPU reads out a complete frame from the buffer.
This bit is self-cleared.
Bit [2]:
Set Control Frame Transmit buffer2 ready, after CPU reads out a complete frame from the buffer.
This bit is self-cleared.
Bit [3]:
Set this bit to indicate CPU received a whole frame (transmit FIFO frame receive done), and
flushed the rest of frame fragment, If occurs. This bit will be self-cleared.
Bit [4]:
Set this bit to indicate that the following Write to the Receive FIFO is the last one (EOF). This bit
will be self-cleared.
Bit [5]:
Set this bit to re-start the data that is sent from the CPU to Receive FIFO (re-align). This feature
can be used for software debug. For normal operation must be '0'.
Bit [7:6]:
Reserved. Must be '0'
60
Zarlink Semiconductor Inc.
ZL50404
•
When the CPU reads this register:
Bit [0]:
Control Frame receive buffer ready, CPU can write a new frame
1 – CPU can write a new control command 1
0 – CPU has to wait until this bit is 1 to write a new control command 1
Bit [1]:
Control Frame transmit buffer1 ready for CPU to read
1 – CPU can read a new control command 1
0 – CPU has to wait until this bit is 1 to read a new control command
Bit [2]:
Control Frame transmit buffer2 ready for CPU to read
1 – CPU can read a new control command 1
0 – CPU has to wait until this bit is 1 to read a new control command
Bit [3]:
Transmit FIFO has data for CPU to read (TXFIFO_RDY)
Bit [4]:
Receive FIFO has space for incoming CPU frame (RXFIFO_SPOK)
Bit [5]:
Transmit FIFO End Of Frame (TXFIFO_EOF)
Bit [7:6]:
Reserved
13.2.5
•
•
Data Sheet
Interrupt Register
Interrupt sources (8 bits)
Address = 5 (read/write)
Bit [0]:
CPU frame interrupt
Bit [1]:
Control Frame 1 interrupt. Control Frame receive buffer1 has data for CPU to read
Bit [2]:
Control Frame 2 interrupt. Control Frame receive buffer2 has data for CPU to read
Bit [6:3]:
Reserved
Bit [7]:
Device Timeout Detected interrupt
Note: This bit is not self-cleared. After reading, the CPU has to clear the bit writing 0 to it.
13.2.6
•
•
•
Control Command Frame Buffer1 Access Register
CPU transmit/receive control frames (16 bits)
Address = 6 (read/write)
When CPU writes to this register:
Data is written to the Control Command Frame Receive Buffer
•
When CPU reads this register:
Data is read from the Control Command Frame Transmit Buffer1
13.2.7
•
•
•
Control Command Frame Buffer2 Access Register
CPU receive control frames (16 bits)
Address = 7 (read only)
When CPU reads this register:
Data is read from the Control Command Frame Transmit Buffer2
61
Zarlink Semiconductor Inc.
ZL50404
13.3
Data Sheet
Indirectly Accessed Registers
13.3.1
13.3.1.1
(Group 0 Address) MAC Ports Group
ECR1Pn: Port n Control Register
I²C Address 000+n; CPU Address:0000+2n (n = port number)
Accessed by CPU and I²C (R/W)
Bit [0]
1 - Flow Control Off
0 - Flow Control On (Default)
When Flow Control On:
• In half duplex mode, the MAC transmitter applies back pressure for flow
control.
• In full duplex mode, the MAC transmitter sends Flow Control frames when
necessary. The MAC receiver interprets and processes incoming flow
control frames. The Flow Control Frame Received counter is incremented
whenever a flow control is received.
When Flow Control Off:
• In half duplex mode, the MAC transmitter does not assert flow control by
sending flow control frame or jamming collision.
• In full duplex mode, the MAC transmitter does not send flow control frames.
The MAC receiver does not interpret or process the flow control frames. The
Flow Control Frame Received counter is not incremented.
Bit [1]
1 - Half Duplex - Only in 10/100 mode
0 - Full Duplex (Default)
Bit [2]
1 - 10 Mbps
0 - 100 Mbps (Default)
Bit [4:3]
00 - Enable Auto-Negotiation
This enables hardware state machine for auto-negotiation. (Default)
01 - Limited Disable Auto-Negotiation
This disables hardware state machine for speed auto-negotiation (use
ECR1Pn[2:0] for configuration). Hardware will still poll PHY for link status.
10 - Force Link Down
Disable the port. Hardware does not talk to PHY.
11 - Force Link Up
The configuration in ECR1Pn[2:0] is used for (speed/duplex/flow control)
setup. Hardware does not talk to PHY.
Bit [5]
Asymmetric Flow Control Enable.
0 – Disable asymmetric flow control (Default)
1 – Enable Asymmetric flow control
When this bit is set and flow control is on (bit [0] = 0), the device does not send out
flow control frames, but it’s receiver interprets and processes flow control frames.
Bit [7:6]
SS - Spanning tree state (IEEE 802.1D spanning tree protocol)
00 - Blocking:
Frame is dropped
01 - Listening:
Frame is dropped
10 - Learning:
Frame is dropped. Source MAC address is learned.
11 - Forwarding: Frame is forwarded. Source MAC address is learned. (Default)
62
Zarlink Semiconductor Inc.
ZL50404
13.3.1.2
Data Sheet
ECR2Pn: Port n Control Register
I²C Address: 00A+n; CPU Address:0001+2n (n = port number)
Accessed by CPU and I²C (R/W)
Bit [0]:
Filter untagged frame
0: Disable (Default)
1: All untagged frames from this port are discarded or follow security option when
security is enable
Bit [1]:
Filter Tag frame
0: Disable (Default)
1: All tagged frames from this port are discarded or follow security option when
security is enable
Bit [2]:
Learning Disable
0: Learning is enabled on this port (Default)
1: Learning is disabled on this port
Bit [3]:
Rate control timer select
0: 10 microsecond refreshing time (Default)
1: 1 millisecond refreshing time
Bit [5:4]
Reserved, Must be 0.
Bit [7:6]
Security Enable. The ZL50404 checks the incoming data for one of the following
conditions:
• If the source MAC address of the incoming packet is in the MAC table and is
defined as secure address but the ingress port is not the same as the port
associated with the MAC address in the MAC table.
• A MAC address is defined as secure when its entry at MAC table has
static status and bit 0 is set to 1. MAC address bit 0 (the first bit
transmitted) indicates whether the address is unicast or multicast. As
source addresses are always unicast bit 0 is not used (always 0).
ZL50404 uses this bit to define secure MAC addresses.
• If the port is set as learning disable and the source MAC address of the
incoming packet is not defined in the MAC address table or the MAC
address is not associated to the ingress port.
If any one of the conditions is met, the packet is forwarded based on these setting.
00 – Disable port security, forward packets as usual. (Default)
01 – Discard violating packets
10 – Forward violating packets as usual and also to the CPU for inspection
11 – Forward violating packets to the CPU for inspection
It also checks for one of the following additional conditions:
• If the port is configured to filter untagged frames and an untagged frame
arrives, or
• If the port is configured to filter tagged frames and a tagged frame arrives, or
• If the packet has the source mac address on the source mac address filter
list, or
• If the packet has the destination mac address on the destination mac
address filter list
If any one of the conditions is met, the packet will be handled according to:
0X – Discard violating packets
1X – Forward violating packets to CPU for inspection
63
Zarlink Semiconductor Inc.
ZL50404
13.3.1.3
Data Sheet
ECR3Pn: Port n Control Register
I²C Address: 014+n; CPU Address:0080+2n (n = port number)
Accessed by CPU and I²C (R/W)
13.3.1.4
Bit [0]:
Enable receiving short frame < 64B
0: Disable (Default)
1: Allow receiving short frame with correct CRC.
Bit [1]:
Enable receiving long frame > 1522
0: Disable (Default)
1: Allow receiving long frame that are <= BUF_LIMIT value
Bit [2]:
Enable pad frame to 64B when transmitted
1: Disable
0: Allow padding to 64B (Default)
Bit [3]:
Enable compress preamble
1: Only one byte preamble+SFD
0: Send standard preamble (Default)
Bit [6:4]
Number of bytes removed from the IFG. (Default 0)
Bit [7]
Link Heart Beat Transmit (RMAC ports only)
0: Disable (Default)
1: Enable
ECR4Pn: Port n Control Register
I²C Address: 01E+n; CPU Address:0081+2n (n = port number)
Accessed by CPU and I²C (R/W)
Port 0 – 3: (RMAC Ports)
Bit [0]:
Enable TXCLK output. Active high
0: Disable (Default)
1: Mn_TXCLK pin becomes output in GPSI or MII mode
Bit [1]:
Enable RXCLK output. Active high
0: Disable (Default)
1: Mn_RXCLK pin becomes output in GPSI or MII mode
Bit [2]:
Internal loopback.
0: Disable (Default)
1: Enable
In this mode, the packet is looped back in the MAC layer before going out of the
chip. You must force linkup at full duplex as well.
External loopback is another level of system diagnostic which involves the PHY
device to loopback the packet.
Bit [4:3]:
Interface mode:
00 - GPSI mode
01 - MII mode
10 - Reserved
11 - RMII mode (Default)
64
Zarlink Semiconductor Inc.
ZL50404
Bit [5]:
Data Sheet
Frame loopback.
0: Disable frame from sending back to its source port. (Default)
1: Allow frame to send back to its source port
In a regular ethernet switch, a packet should never be receive and forwarded to
the same port. Setting the bit allows it to happen.
This is not the same as an ingress MAC loopback. The destination MAC address
has to be stored (learned) in the MCT and associated with the originating source
port. The frame loopback will only work for unicast packets.
Bit [6]:
Link Heart Beat Receive
0: Disable (Default). Also clears all MAC LHB status.
1: Enable
Bit [7]:
Soft reset.
0: Normal operation (Default)
1: Reset. Not self clearing.
Port 8: (CPU Port)
Bit [1:0]:
Reserved
Bit [2]:
Enable special write to 2 registers in a single write operation.
0: Disable (Default)
1: Enable
Bit[4:3]:
Reserved
Bit [5]:
Frame loopback.
0: Disable frame from sending back to its source port. (Default)
1: Allow frame to send back to its source port
In a regular ethernet switch, a packet should never be receive and forwarded to
the same port. Setting the bit allows it to happen.
This is not the same as an ingress MAC loopback. The destination MAC address
has to be stored (learned) in the MCT and associated with the originating source
port. The frame loopback will only work for unicast packets.
Bit [6]:
Reserved
Bit [7]:
Soft reset.
0: Normal operation (Default)
1: Reset. Not self clearing.
Port 9: (MMAC Port)
Bit [0]:
Reserved
Bit [1]:
Enable RXCLK output. Active high
0: Disable (Default)
1: M9_RXCLK pin becomes output in MII mode
Note: To configure port 9 with the device providing the interface clocks, you need
to tie M9_RXCLK to M9_MTXCLK externally as M9_MTXCLK is not a bidirectional
clock.
65
Zarlink Semiconductor Inc.
ZL50404
Bit [2]:
Data Sheet
Internal loopback.
0: Disable (Default)
1: Enable
In this mode, the packet is looped back in the MAC layer before going out of the
chip. You must force linkup at full duplex as well.
External loopback is another level of system diagnostic which involves the PHY
device to loopback the packet.
Bit [4:3]:
Interface mode:
11 - MII mode (Default)
Bit [5]:
Frame loopback.
0: Disable frame from sending back to its source port. (Default)
1: Allow frame to send back to its source port
In a regular ethernet switch, a packet should never be receive and forwarded to
the same port. Setting the bit allows it to happen.
This is not the same as an ingress MAC loopback. The destination MAC address
has to be stored (learned) in the MCT and associated with the originating source
port. The frame loopback will only work for unicast packets.
13.3.1.5
Bit [6]:
Reserved
Bit [7]:
Soft reset.
0: Normal operation (Default)
1: Reset. Not self clearing.
BUF_LIMIT – Frame Buffer Limit
CPU Address:h036
Accessed by CPU (R/W)
13.3.1.6
Bit [6:0]:
Frame Buffer Limit (max 4 KB). Multiple of 64 bytes (Default 0x40)
Bit [7]:
Reserved
FCC – Flow Control Grant Period
CPU Address:h037
Accessed by CPU (R/W)
Bit [2:0]:
Flow Control Grant Period (Default 0x3)
Bit [7:3]:
Reserved
66
Zarlink Semiconductor Inc.
ZL50404
13.3.2
13.3.2.1
Data Sheet
(Group 1 Address) VLAN Group
AVTCL – VLAN Type Code Register Low
I²C Address 028; CPU Address:h100
Accessed by CPU and I²C (R/W)
Bit [7:0]:
13.3.2.2
VLANType_LOW: Lower 8 bits of the VLAN type code (Default 0)
AVTCH – VLAN Type Code Register High
I²C Address 029; CPU Address:h101
Accessed by CPU and I²C (R/W)
Bit [7:0]:
13.3.2.3
VLANType_HIGH: Upper 8 bits of the VLAN type code (Default is 0x81)
PVMAP00_0 – Port 0 Configuration Register 0
I²C Address 02A, CPU Address:h102
Accessed by CPU and I²C (R/W)
Bit [3:0]:
VLAN Mask for port 0 (Default 0xF)
Bit[7:4]:
Reserved (Default 0xF)
This register indicates the legal egress ports. A “1” on bit 3 means that the packet can be sent to port 3. A “0” on bit
3 means that any packet destined to port 3 will be discarded. This register works with registers 1 to form a 10 bit
mask to all egress ports.
13.3.2.4
PVMAP00_1 – Port 0 Configuration Register 1
I²C Address h34, CPU Address:h103
Accessed by CPU and I²C (R/W)
13.3.2.5
Bit [1:0]:
VLAN Mask for ports 9 to 8 (Default 0x3)
Bit [7:2]:
Reserved (Default 0x3F)
PVMAP00_3 – Port 0 Configuration Register 3
I²C Address h3E, CPU Address:h105
Accessed by CPU and I²C (R/W)
Bit [2:0]:
Reserved
Bit [5:3]:
Default Transmit priority. Used when Bit [7]=1 (Default 0)
Transmit Priority Level 0 (Lowest)
Transmit Priority Level 1
Transmit Priority Level 2
Transmit Priority Level 3 (Highest)
67
Zarlink Semiconductor Inc.
ZL50404
13.3.2.6
Data Sheet
Bit [6]:
Default Discard priority. Used when Bit [7]=1
0 – Discard Priority Level 0 (Lowest) (Default)
1 – Discard Priority Level 1(Highest)
Bit [7]:
Enable Fix Priority (Default 0)
0 - Disable. All frames are analysed. Transmit Priority and Discard Priority are
based on VLAN Tag, TOS or Logical Port.
1 - Enable. Transmit Priority and Discard Priority are based on values
programmed in bit [6:3]
PVMAPnn_0,1,3 – Ports 1~9 Configuration Registers
PVMAP01_0,1,3 I²C Address h2B,35,3F; CPU Address:h106,107,109 (Port 1)
PVMAP02_0,1,3 I²C Address h2C,36,40; CPU Address:h10A, 10B, 10D (Port 2)
PVMAP03_0,1,3 I²C Address h2D,37,41; CPU Address:h10E, 10F, 111 (Port 3)
PVMAP08_0,1,3 I²C Address h32,3C,46; CPU Address:h122, 123, 125 (Port CPU)
PVMAP09_0,1,3 I²C Address h33,3D,47; CPU Address:h126, 127, 129 (Port MMAC)
13.3.2.7
PVMODE
I²C Address: h048, CPU Address:h170
Accessed by CPU and I²C (R/W)
Bit [0]:
Reserved. Must be 0.
Bit [1]:
Slow learning (Default = 0)
Same function as SE_OP MODE bit [7]. Either bit can enable the function; both need to
be turned off to disable the feature.
Bit [2]:
Disable dropping of frames with destination MAC addresses 0180C2000001 to
0180C200000F.
0: Drop all frames in this range (Default)
1: Disable dropping of frames in this range
Bit [3]:
Flooding control in secure mode
0: Enable - Learning disabled port will not receive any flooding packets (Default)
1: Disable
Bit [4]:
Support MAC address 0
0: MAC address 0 is not learned. (Default)
1: MAC address 0 is learned.
Bit [5]:
Disable IEEE multicast control frame (0180C2000000 to 0180C20000FF) to CPU in
managed mode.
0: Packet is forwarded to CPU (Default)
1: Packet is forwarded as multicast
Bit [6]:
Reserved. Must be 0.
68
Zarlink Semiconductor Inc.
ZL50404
Bit [7]:
13.3.3
Data Sheet
Enable logical port match in secure mode
0: Disable (Default)
1: Enable - When Well Known or User Define logical port force discard enabled, force
any IP packet with logical port number matching logical port numbers to CPU.
(Group 2 Address) Port Trunking Groups
Trunk Group – Up to four RMAC ports can be selected for each trunk group.
13.3.3.1
TRUNKn– Trunk Group 0~7
CPU Address:h200+n (n = trunk group)
Accessed by CPU (R/W)
Bit [3:0] Port 3-0 bit map of trunk n. (Default 0)
B
i
t
3
B
i
t
0
TRUNK0
P
o
r
t
3
13.3.3.2
P
o
r
t
0
TRUNKn_HASH10 – Trunk group 0~7 hash result 1/0 destination port number
CPU Address:h208+4n (n = trunk group)
Accessed by CPU (R/W)
13.3.3.3
Bit [3:0]
Hash result 0 destination port number (Default 0)
Bit [7:4]
Hash result 1 destination port number (Default 0)
TRUNKn_HASH32 – Trunk group 0~7 hash result 3/2 destination port number
CPU Address:h209+4n (n = trunk group)
Accessed by CPU (R/W)
Bit [3:0]
Hash result 2 destination port number (Default 0)
Bit [7:4]
Hash result 3 destination port number (Default 0)
69
Zarlink Semiconductor Inc.
ZL50404
13.3.3.4
Data Sheet
TRUNKn_HASH54 – Trunk group 0~7 hash result 5/4 destination port number
CPU Address:h20A+4n (n = trunk group)
Accessed by CPU (R/W)
13.3.3.5
Bit [3:0]
Hash result 4 destination port number (Default 0)
Bit [7:4]
Hash result 5 destination port number (Default 0)
TRUNKn_HASH76 – Trunk group 0~7 hash result 7/6 destination port number
CPU Address:h20B+4n (n = trunk group)
Accessed by CPU (R/W)
Bit [3:0]
Hash result 6 destination port number (Default 0)
Bit [7:4]
Hash result 7 destination port number (Default 0)
Multicast Hash Registers
Multicast Hash registers are used to distribute multicast traffic. 16 registers are used to form a 8-entry array; each
entry has 10 bits, with each bit representing one port. Any port not belonging to a trunk group should be
programmed with 1. Ports belonging to the same trunk group should only have a single port set to “1” per entry. The
port set to “1” is picked to transmit the multicast frame when the hash value is met.
Hash Value =0
HASH0-1
HASH0-0
Hash Value =1
HASH1-1
HASH1-0
Hash Value =2
HASH2-1
HASH2-0
Hash Value =3
HASH3-1
HASH3-0
Hash Value =4
HASH4-1
HASH4-0
Hash Value =5
HASH5-1
HASH5-0
Hash Value =6
HASH6-1
HASH6-0
Hash Value =7
HASH7-1
HASH7-0
P
o
r
t
9
P
o
r
t
8
70
Zarlink Semiconductor Inc.
P
o
r
t
3
P
o
r
t
0
ZL50404
13.3.3.6
Data Sheet
MULTICAST_HASHn-0 – Multicast hash result 0~7 mask byte 0
CPU Address:h228+2n (n = hash value)
Accessed by CPU (R/W)
13.3.3.7
Bit [3:0]:
Port 3-0 bit map for multicast hash. (Default 0xF)
Bit[7:4]:
Reserved. (Default 0xF)
MULTICAST_HASHn-1 – Multicast hash result 0~7 mask byte 1
CPU Address:h229+2n (n = hash value)
Accessed by CPU (R/W)
Bit [1:0]:
Port 9-8 bit map for multicast hash. (Default 0x3)
Bit [5:2]:
Reserved (Default 0xF)
Bit [7:6]:
MULTICAST_HASH0-1
Hash Select. The hash algorithm selected is valid for all trunks (Default 00)
00 - Use Source and Destination MAC Address for hashing
01 - Use Source MAC Address for hashing
10 - Use Destination MAC Address for hashing
11 - Use Source Port Number for hashing
MULTICAST_HASH[7:1]-1
Reserved (Default 0x3)
13.3.4
(Group 3 Address) CPU Port Configuration Group
5
MAC5
0
MAC4
MAC3
MAC2
MAC1
(MC bit)
MAC0
MAC5 to MAC0 registers form the CPU MAC address. When a packet with destination MAC address match MAC
[5:0], the packet is forwarded to the CPU.
13.3.4.1
MAC0 – CPU MAC address byte 0
CPU Address:h300
Accessed by CPU (R/W)
Bit [7:0]:
Byte 0 of the CPU MAC address (Default 0)
71
Zarlink Semiconductor Inc.
ZL50404
13.3.4.2
Data Sheet
MAC1 – CPU MAC address byte 1
CPU Address:h301
Accessed by CPU (R/W)
Bit [7:0]:
13.3.4.3
Byte 1 of the CPU MAC address (Default 0)
MAC2 – CPU MAC address byte 2
CPU Address:h302
Accessed by CPU (R/W)
Bit [7:0]:
13.3.4.4
Byte 2 of the CPU MAC address (Default 0)
MAC3 – CPU MAC address byte 3
CPU Address:h303
Accessed by CPU (R/W)
Bit [7:0]:
13.3.4.5
Byte 3 of the CPU MAC address (Default 0)
MAC4 – CPU MAC address byte 4
CPU Address:h304
Accessed by CPU (R/W)
Bit [7:0]:
13.3.4.6
Byte 4 of the CPU MAC address (Default 0)
MAC5 – CPU MAC address byte 5
CPU Address:h305
Accessed by CPU (R/W)
Bit [7:0]:
13.3.4.7
Byte 5 of the CPU MAC address (Default 0)
INT_MASK0 – Interrupt Mask
CPU Address:h306
Accessed by CPU (R/W)
The CPU can dynamically mask the interrupt when it is busy and doesn’t want to be interrupted. (Default 0x00)
-
1: Mask the interrupt
0: Unmask the interrupt (Enable interrupt)
Bit [0]:
CPU frame interrupt. CPU frame buffer has data for CPU to read
Bit [1]:
Control Command 1 interrupt. Control Command Frame buffer1 has data for CPU to read
72
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
Bit [2]:
Control Command 2 interrupt. Control command Frame buffer2 has data for CPU to read
Bit [6:3]:
Reserved
Bit [7]:
Device Timeout Detected interrupt
13.3.4.8
INTP_MASK0 – Interrupt Mask for MAC Port 0,1
CPU Address:h310
Accessed by CPU (R/W)
The CPU can dynamically mask the interrupt when it is busy and doesn’t want to be interrupted (Default 0x00)
-
1: Mask the interrupt
0: Unmask the interrupt
Bit [0]:
Port 0 statistic counter wrap around interrupt mask. An Interrupt is generated when a statistic
counter wraps around. Refer to hardware statistic counter for interrupt sources
Bit [1]:
Port 0 link change mask
Bit [2]:
Port 0 module detect mask
Bit [3]:
Reserved
Bit [4]:
Port 1 statistic counter wrap around interrupt mask. An interrupt is generated when a statistic
counter wraps around. Refer to hardware statistic counter for interrupt sources.
Bit [5]:
Port 1 link change mask
Bit [6]:
Port 1 module detect mask
Bit [7]
Reserved
13.3.4.9
INTP_MASKn – Interrupt Mask for MAC Ports 2~9 Registers
INTP_MASK1 CPU Address:h311 (Ports 2,3)
INTP_MASK4 CPU Address:h314 (Port CPU,MMAC)
13.3.4.10
RQS – Receive Queue Select
CPU Address:h323
Accessed by CPU (RW)
Select which receive queue is used.
Bit [0]:
Select Queue 0
Bit [1]:
Select Queue 1
Bit [2]:
Select Queue 2
Bit [3]:
Select Queue 3
Bit [4]:
Select Multicast Queue 0
Bit [5]:
Select Multicast Queue 1
73
Zarlink Semiconductor Inc.
ZL50404
Bit [6]:
Select Multicast Queue 2
Bit [7]:
Select Multicast Queue 3
Data Sheet
Note: Strict priority applies between different selected queues (UQ3>UQ2>UQ1>UQ0>MQ3>MQ2>MQ1>MQ0).
13.3.4.11
RQSS – Receive Queue Status
CPU Address:h324
Accessed by CPU (RO)
CPU receive queue status
Bit [3:0]:
Unicast Queue 3 to 0 not empty
Bit [7:4]:
Multicast Queue 3 to 0 not empty
13.3.4.12
MAC01 – Increment MAC port 0,1 address
CPU Address:h325
Accessed by CPU (RW)
Bit [2:0]:
Bit [42:40] of Port 0 MAC address
Bit [3]:
Reserved
Bit [6:4]:
Bit [42:40] of Port 1 MAC address
Bit [7]:
Reserved
13.3.4.13
MAC23 – Increment MAC port 2,3 address
CPU Address:h326
Accessed by CPU (RW)
Bit [2:0]:
Bit [42:40] of Port 2 MAC address
Bit [3]:
Reserved
Bit [6:4]:
Bit [42:40] of Port 3 MAC address
Bit [7]:
Reserved
13.3.4.14
MAC9 – Increment MAC port 9 address
CPU Address:h329
Accessed by CPU (RW)
Bit [7:0]:
Bit [47:40] of Port 9 MAC address
74
Zarlink Semiconductor Inc.
ZL50404
13.3.4.15
Data Sheet
CPUQINS0 - CPUQINS6 – CPU Queue Insertion Command
CPU Address:h330-336
Accessed by CPU, (R/W)
55
0
CQ6
CQ5
CQ4
CQ3
CQ2
CQ1
CQ0
CPU Queue insertion command
Bit[3:0]:
Destination Map (port 3-0).
Bit[7:4]:
Reserved. Must be 0.
Bit[9:8]:
Destination Map (MMAC, CPU).
Bit [13:10]
Priority
Bit [20:14]
Number of granules for the frame
Bit [35:21]
Tail pointer
Bit [50:36]
Header Pointer
Bit [51]
Multicast frame (has to be one if more than one destination port)
Bit [54:52]
Reserved
Bit [55]
Command valid (will be processed on the rising edge of the signal)
13.3.4.16
CPUQINSRPT – CPU Queue Insertion Report
CPU Address:h337
Accessed by CPU, (RO)
CPU command queue status
Bit [0]:
The command is under processing.
Bit [1]:
Insertion Fail (May be due to queue full, WRED or filtering)
13.3.4.17
CPUGRNHDL0 - CPUGRNHDL1 – CPU Allocated Granule Pointer
CPU Address:h338-339
Accessed by CPU, (RO)
15
CG1
0
CG0
75
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
CPU Queue insertion command
Bit [14:0]:
Granule pointer.
Bit [15]:
Pointer valid
13.3.4.18
CPURLSINFO0 - CPURLSINFO4 – Receive Queue Status
CPU Address:h33A-33E
Accessed by CPU, (R/W)
0
CR4
CR3
CR2
CR1
CR0
CPU Queue insertion command
Bit [14:0]:
Header pointer
Bit [30:15]
Tail pointer
Bit [38:32]
Number of granules for the release
13.3.4.19
CPUGRNCTR – CPU Granule Control
CPU Address:h33f
Accessed by CPU, (R/W)
CPU receive queue status
13.3.5
13.3.5.1
Bit [0]:
Allocate granule to the CPU if set to one. Otherwise, do not allocate any resource.
Bit [1]:
Read allocated granule (at rising edge only)
Bit [2]:
Release info valid (will be processed at rising edge only)
(Group 4 Address) Search Engine Group
AGETIME_LOW – MAC address aging time Low
I²C Address h049; CPU Address:h400
Accessed by CPU and I²C (R/W)
Used in conjuction with AGETIME_HIGH. The ZL50404 removes the MAC address from the data base and sends a
Delete MAC Address Control Command to the CPU.
Bit [7:0]:
Low byte of the MAC address aging timer (Default 0x5C)
76
Zarlink Semiconductor Inc.
ZL50404
13.3.5.2
Data Sheet
AGETIME_HIGH –MAC address aging time High
I²C Address h04A; CPU Address h401
Accessed by CPU and I²C (R/W)
Bit [7:0]:
High byte of the MAC address aging timer (Default 0)
The default setting of AGETIME_LOW/HIGH provides 300 seconds aging time. Aging time is based on the
following equation:
{AGETIME_HIGH,AGETIME_LOW} X (# of MAC entries in the memory X 800 µsec). Number of MAC entries = 4 K.
13.3.5.3
SE_OPMODE – Search Engine Operation Mode
CPU Address:h403
Accessed by CPU (R/W)
Note: ECR2[2] enable/disable learning for each port.
Bit [0]:
Reserved. Must be 0.
Bit [1]:
Protocol filtering mode
0 – Inclusive (Default)
1 – Exclusive
Bit [2]:
Report control
1 – Disable report MAC address deletion
0 – Report MAC address deletion (MAC address is deleted from MCT after
aging time) (Default)
Bit [3]:
Delete Control
1 – Disable aging logic from removing MAC during aging
0 – MAC address entry is removed when it is old enough to be aged (Default)
However, a report is still sent to the CPU in both cases, when bit [2] = 0
Bit [4]:
Reserved. Must be 0.
Bit [5]
1 - Report ARP packet to CPU
0 - No ARP packet reporting (Default)
Bit [6]:
Disable MCT speed-up aging
1 – Disable speed-up aging when MCT resource is low.
0 – Enable speed-up aging when MCT resource is low. (Default)
Bit [7]:
Slow Learning
1– Enable slow learning. Learning is temporary disabled when search
demand is high
0 – Learning is performed independent of search demand (Default)
77
Zarlink Semiconductor Inc.
ZL50404
13.3.6
13.3.6.1
Data Sheet
(Group 5 Address) Buffer Control/QOS Group
QOSC – QOS Control
I²C Address h04B; CPU Address:h500
Accessed by CPU and I2C (R/W)
13.3.6.2
Bit [0]:
Enable TX rate control (on RMAC ports only)
1 – Enable
0 – Disable (Default)
Bit [1]:
Enable RX rate control (on RMAC ports only)
1 – Enable
0 – Disable (Default)
Bit [4:2]:
Reserved
Bit [5]:
Select VLAN tag or TOS (IP packets) to be preferentially picked to map
transmit priority and drop priority
0 – Select VLAN Tag priority field over TOS (Default)
1 – Select TOS over VLAN tag priority field
Bit [6]:
Select TOS bits for Priority
0 – Use TOS [4:2] bits to map the transmit priority (Default)
1 – Use TOS [7:5] bits to map the transmit priority
Bit [7]:
Select TOS bits for Drop priority
0 – Use TOS [4:2] bits to map the drop priority (Default)
1 – Use TOS [7:5] bits to map the drop priority
UCC – Unicast Congestion Control
I2C Address h068, CPU Address: 510
Accessed by CPU and I2C (R/W)
Bit [7:0]:
13.3.6.3
Number of frame count. Used for best effort dropping at B% when destination
port’s best effort queue reaches UCC threshold and shared pool is all in use.
Granularity is 16 granule (Default 0x6)
MCC – Multicast Congestion Control
I²C Address h069, CPU Address: 511
Accessed by CPU and I²C (R/W)
Bit [7:0]:
In multiples of 16 granules (granularity). Used for triggering MC flow control
when destination port’s multicast best effort queue reaches MCC threshold.
(Default 0x6)
78
Zarlink Semiconductor Inc.
ZL50404
13.3.6.4
Data Sheet
MCCTH – Multicast Threshold Control
CPU Address: 512
Accessed by CPU (R/W)
Bit [7:0]:
13.3.6.5
Threshold on the multicast granule count. Exceeding the threshold consider as
multicast resource low and the new multicast will be dropped at B% or flow control is triggered if enabled. (Default: 0x3)
RDRC0 – WRED Rate Control 0
I²C Address 090, CPU Address 513
Accessed by CPU and I2C (R/W)
Bits[3:0]:
Corresponds to the frame drop percentage Y% for WRED. Granularity
6.25%.
Bits[7:4]:
Corresponds to the frame drop percentage X% for WRED. Granularity
6.25%.
See Programming QoS Registers application note, ZLAN-42, for more information
13.3.6.6
RDRC1 – WRED Rate Control 1
I²C Address 091, CPU Address 514
Accessed by CPU and I²C (R/W)
Bits[3:0]:
Corresponds to the best effort frame drop percentage B%, when shared pool
is all in use and destination port best effort queue reaches UCC. Granularity
6.25%.
Bits[7:4]:
Corresponds to the frame drop percentage Z% for WRED. Granularity
6.25%.
See Programming QoS Registers application note, ZLAN-42, for more information
13.3.6.7
RDRC2 – WRED Rate Control 2
CPU Address 515
Accessed by CPU (R/W)
Bits[3:0]:
Corresponds to the frame drop percentage RB%, for rate control. Granularity
6.25%.
Bits[7:4]:
Corresponds to the frame drop percentage RA% for rate control. Granularity
6.25%.
79
Zarlink Semiconductor Inc.
ZL50404
13.3.6.8
Data Sheet
SFCB – Share FCB Size
I²C Address h074, CPU Address 518
Accessed by CPU and I²C (R/W)
Bits [7:0]:
13.3.6.9
Expressed in multiples of 16 granules. Buffer reservation for shared pool.
C1RS – Class 1 Reserve Size
I²C Address h075, CPU Address 519
Accessed by CPU and I²C (R/W)
Bits [7:0]:
Class 1 FCB Reservation
Buffer reservation for class 1. Granularity 16 granules. (Default 0)
13.3.6.10
C2RS – Class 2 Reserve Size
I²C Address h076, CPU Address 51A
Accessed by CPU and I²C (R/W)
Bits [7:0]:
Class 2 FCB Reservation
Buffer reservation for class 2. Granularity 16 granules. (Default 0)
13.3.6.11
C3RS – Class 3 Reserve Size
I²C Address h077, CPU Address 51B
Accessed by CPU and I²C (R/W)
Bits [7:0]:
Class 3 FCB Reservation
Buffer reservation for class 3. Granularity 16 granules. (Default 0)
13.3.6.12
AVPML – VLAN Tag Priority Map
I²C Address h056; CPU Address:h530
Accessed by CPU and I²C (R/W)
Registers AVPML, AVPMM, and AVPMH allow the eight VLAN Tag priorities to map into eight Internal level
transmit priorities. Under the Internal transmit priority, seven is the highest priority where as zero is the lowest. This
feature allows the user the flexibility of redefining the VLAN priority field. For example, programming a value of 7
into bit 2:0 of the AVPML register would map packet VLAN priority 0 into Internal transmit priority 7. The new priority
is used inside the ZL50404. When the packet goes out it carries the original priority.
Bit [2:0]:
Priority when the VLAN tag priority field is 0 (Default 0)
Bit [5:3]:
Priority when the VLAN tag priority field is 1 (Default 0)
Bit [7:6]:
Priority when the VLAN tag priority field is 2 (Default 0)
80
Zarlink Semiconductor Inc.
ZL50404
13.3.6.13
AVPMM – VLAN Priority Map
I²C Address h057, CPU Address:h531
Accessed by CPU and I²C (R/W)
Map VLAN priority into eight level transmit priorities:
Bit [0]:
Priority when the VLAN tag priority field is 2 (Default 0)
Bit [3:1]:
Priority when the VLAN tag priority field is 3 (Default 0)
Bit [6:4]:
Priority when the VLAN tag priority field is 4 (Default 0)
Bit [7]:
Priority when the VLAN tag priority field is 5 (Default 0)
13.3.6.14
AVPMH – VLAN Priority Map
I²C Address h058, CPU Address:h532
Accessed by CPU and I²C (R/W)
Map VLAN priority into eight level transmit priorities:
Bit [1:0]:
Priority when the VLAN tag priority field is 5 (Default 0)
Bit [4:2]:
Priority when the VLAN tag priority field is 6 (Default 0)
Bit [7:5]:
Priority when the VLAN tag priority field is 7 (Default 0)
13.3.6.15
AVDM – VLAN Discard Map
I²C Address h05C, CPU Address:h533
Accessed by CPU and I²C (R/W)
Map VLAN priority into frame discard when low priority buffer usage is above threshold
Bit [0]:
Frame drop priority when VLAN Tag priority field is 0 (Default 0)
Bit [1]:
Frame drop priority when VLAN Tag priority field is 1 (Default 0)
Bit [2]:
Frame drop priority when VLAN Tag priority field is 2 (Default 0)
Bit [3]:
Frame drop priority when VLAN Tag priority field is 3 (Default 0)
Bit [4]:
Frame drop priority when VLAN Tag priority field is 4 (Default 0)
Bit [5]:
Frame drop priority when VLAN Tag priority field is 5 (Default 0)
Bit [6]:
Frame drop priority when VLAN Tag priority field is 6 (Default 0)
Bit [7]:
Frame drop priority when VLAN Tag priority field is 7 (Default 0)
81
Zarlink Semiconductor Inc.
Data Sheet
ZL50404
13.3.6.16
TOSPML – TOS Priority Map
I²C Address h059, CPU Address:h540
Accessed by CPU and I²C (R/W)
Map TOS field in IP packet into eight level transmit priorities
Bit [2:0]:
Priority when the TOS field is 0 (Default 0)
Bit [5:3]:
Priority when the TOS field is 1 (Default 0)
Bit [7:6]:
Priority when the TOS field is 2 (Default 0)
13.3.6.17
TOSPMM – TOS Priority Map
I²C Address h05A, CPU Address:h541
Accessed by CPU and I²C (R/W)
Map TOS field in IP packet into eight level transmit priorities
Bit [0]:
Priority when the TOS field is 2 (Default 0)
Bit [3:1]:
Priority when the TOS field is 3 (Default 0)
Bit [6:4]:
Priority when the TOS field is 4 (Default 0)
Bit [7]:
Priority when the TOS field is 5 (Default 0)
13.3.6.18
TOSPMH – TOS Priority Map
I²C Address h05B, CPU Address:h542
Accessed by CPU and I²C (R/W)
Map TOS field in IP packet into eight level transmit priorities:
Bit [1:0]:
Priority when the TOS field is 5 (Default 0)
Bit [4:2]:
Priority when the TOS field is 6 (Default 0)
Bit [7:5]:
Priority when the TOS field is 7 (Default 0)
13.3.6.19
TOSDML – TOS Discard Map
I²C Address h05D, CPU Address:h543
Accessed by CPU and I²C (R/W)
Map TOS into frame discard when low priority buffer usage is above threshold
Bit [0]:
Frame drop priority when TOS field is 0 (Default 0)
Bit [1]:
Frame drop priority when TOS field is 1 (Default 0)
Bit [2]:
Frame drop priority when TOS field is 2 (Default 0)
82
Zarlink Semiconductor Inc.
Data Sheet
ZL50404
Bit [3]:
Frame drop priority when TOS field is 3 (Default 0)
Bit [4]:
Frame drop priority when TOS field is 4 (Default 0)
Bit [5]:
Frame drop priority when TOS field is 5 (Default 0)
Bit [6]:
Frame drop priority when TOS field is 6 (Default 0)
Bit [7]:
Frame drop priority when TOS field is 7 (Default 0)
13.3.6.20
Data Sheet
USER_PROTOCOL_n – User Define Protocol 0~7
I²C Address h0B3+n, CPU Address:h550+n
Accessed by CPU and I²C (R/W)
(Default 00) This register is duplicated eight times from PROTOCOL 0~7 and allows the CPU to define eight
separate protocols.
Bits[7:0]:
13.3.6.21
User Define Protocol
USER_PROTOCOL_FORCE_DISCARD – User Define Protocol 0~7 Force Discard
I²C Address h0BB, CPU Address 558
Accessed by CPU and I²C (R/W)
Bits[0]:
Enable Protocol 0 Force Discard
1 – Enable
0 – Disable
Bits[1]:
Enable Protocol 1 Force Discard
Bits[2]:
Enable Protocol 2 Force Discard
Bits[3]:
Enable Protocol 3 Force Discard
Bits[4]:
Enable Protocol 4 Force Discard
Bits[5]:
Enable Protocol 5 Force Discard
Bits[6]:
Enable Protocol 6 Force Discard
Bits[7]:
Enable Protocol 7 Force Discard
User Defined Logical Ports and Well Known Ports
The ZL50404 supports classifying packet priority through layer 4 logical port information. It can be setup by 8 Well
Known Ports, 8 User Defined Logical Ports, and 1 User Defined Range. The 8 Well Known Ports supported are:
•
•
•
•
•
•
•
•
23
512
6000
443
111
22555
22
554
83
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
Their respective priority can be programmed via Well_Known_Port [7:0] priority register. Well_Known_Port_Enable
can individually turn on/off each Well Known Port if desired.
Similarly, the User Defined Logical Port provides the user programmability to the priority, plus the flexibility to select
specific logical ports to fit the applications. The 8 User Logical Ports can be programmed via User_Port 0-7
registers. Two registers are required to be programmed for the logical port number. The respective priority can be
programmed to the User_Port [7:0] priority register. The port priority can be individually enabled/disabled via
User_Port_Enable register.
The User Defined Range provides a range of logical port numbers with the same priority level. Programming is
similar to the User Defined Logical Port. Instead of programming a fixed port number, an upper and lower limit need
to be programmed, they are: {RHIGHH, RHIGHL} and {RLOWH, RLOWL} respectively. If the value in the upper
limit is smaller or equal to the lower limit, the function is disabled. Any IP packet with a logical port that is less than
the upper limit and more than the lower limit will use the priority specified in RPRIORITY.
13.3.6.22
WELL_KNOWN_PORT[1:0]_PRIORITY- Well Known Logic Port 1 and 0 Priority
I²C Address h0A8, CPU Address 560
Accessed by CPU and I²C (R/W)
Bits[3:0]:
Priority setting, transmission + dropping, for Well known port 0 (23 for telnet)
Bits[7:4]:
Priority setting, transmission + dropping, for Well known port 1 (512 for
TCP/UDP)
13.3.6.23
WELL_KNOWN_PORT[3:2]_PRIORITY- Well Known Logic Port 3 and 2 Priority
I²C Address h0A9, CPU Address 561
Accessed by CPU and I²C (R/W)
Bits[3:0]:
Priority setting, transmission + dropping, for Well known port 2 (6000 for
XWIN)
Bits[7:4]:
Priority setting, transmission + dropping, for Well known port 3 (443 for HTTP
sec)
13.3.6.24
WELL_KNOWN_PORT[5:4]_PRIORITY- Well Known Logic Port 5 and 4 Priority
I²C Address h0AA, CPU Address 562
Accessed by CPU and I²C (R/W)
Bits[3:0]:
Priority setting, transmission + dropping, for Well known port 4 (111 for sun
remote procedure call)
Bits[7:4]:
Priority setting, transmission + dropping, for Well known port 5 (22555 for IP
Phone call setup)
84
Zarlink Semiconductor Inc.
ZL50404
13.3.6.25
Data Sheet
WELL_KNOWN_PORT[7:6]_PRIORITY- Well Known Logic Port 7 and 6 Priority
I²C Address h0AB, CPU Address 563
Accessed by CPU and I²C (R/W)
Bits[3:0]:
Priority setting, transmission + dropping, for Well known port 6 (22 for ssh)
Bits[7:4]:
Priority setting, transmission + dropping, for Well known port 7 (554 for rtsp)
13.3.6.26
WELL_KNOWN_PORT_ENABLE – Well Known Logic Port 0 to 7 Enables
I²C Address h0AC, CPU Address 564
Accessed by CPU and I²C (R/W)
Bits[0]:
Enable Well Known Port 0 Priority
1 – Enable
0 – Disable
Bits[1]:
Enable Well Known Port 1 Priority
Bits[2]:
Enable Well Known Port 2 Priority
Bits[3]:
Enable Well Known Port 3 Priority
Bits[4]:
Enable Well Known Port 4 Priority
Bits[5]:
Enable Well Known Port 5 Priority
Bits[6]:
Enable Well Known Port 6 Priority
Bits[7]:
Enable Well Known Port 7 Priority
13.3.6.27
Discard
WELL_KNOWN_PORT_FORCE_DISCARD – Well Known Logic Port 0~7 Force
I²C Address h0AD, CPU Address 565
Accessed by CPU and I²C (R/W)
Bits[0]:
Enable Well Known Port 0 Force Discard
1 – Enable
0 – Disable
Bits[1]:
Enable Well Known Port 1 Force Discard
Bits[2]:
Enable Well Known Port 2 Force Discard
Bits[3]:
Enable Well Known Port 3 Force Discard
Bits[4]:
Enable Well Known Port 4 Force Discard
Bits[5]:
Enable Well Known Port 5 Force Discard
Bits[6]:
Enable Well Known Port 6 Force Discard
Bits[7]:
Enable Well Known Port 7 Force Discard
85
Zarlink Semiconductor Inc.
ZL50404
13.3.6.28
Data Sheet
USER_PORT[7:0]_[LOW/HIGH] – User Define Logical Port 0~7
I²C Address h092+n(Low); CPU Address 570+2n(Low) (n = logical port number)
I²C Address h09A+n(High); CPU Address 571+2n(High)
Accessed by CPU and I²C (R/W)
(Default 00) This register is duplicated eight times from PORT 0 through PORT 7 and allows the CPU to define
eight separate ports.
7
0
TCP/UDP Logic Port Low
7
0
TCP/UDP Logic Port High
13.3.6.29
USER_PORT_[1:0]_PRIORITY - User Define Logic Port 1 and 0 Priority
I²C Address h0A2, CPU Address 590
Accessed by CPU and I²C (R/W)
The chip allows the CPU to define the priority
Bits[3:0]:
Priority setting, transmission + dropping, for logic port 0
Bits[7:4]:
Priority setting, transmission + dropping, for logic port 1 (Default 00)
13.3.6.30
USER_PORT_[3:2]_PRIORITY - User Define Logic Port 3 and 2 Priority
I²C Address h0A3, CPU Address 591
Accessed by CPU and I²C (R/W)
Bits[3:0]:
Priority setting, transmission + dropping, for logic port 2
Bits[7:4]:
Priority setting, transmission + dropping, for logic port 3 (Default 00)
13.3.6.31
USER_PORT_[5:4]_PRIORITY - User Define Logic Port 5 and 4 Priority
I²C Address h0A4, CPU Address 592
Accessed by CPU and I²C (R/W)
Bits[3:0]:
Priority setting, transmission + dropping, for logic port 4
Bits[7:4]:
Priority setting, transmission + dropping, for logic port 5 (Default 00)
86
Zarlink Semiconductor Inc.
ZL50404
13.3.6.32
Data Sheet
USER_PORT_[7:6]_PRIORITY - User Define Logic Port 7 and 6 Priority
I²C Address h0A5, CPU Address 593
Accessed by CPU and I²C (R/W)
Bits[3:0]:
Priority setting, transmission + dropping, for logic port 6
Bits[7:4]:
Priority setting, transmission + dropping, for logic port 7 (Default 00)
13.3.6.33
USER_PORT_ENABLE[7:0] – User Define Logic Port 0 to 7 Enables
I²C Address h0A6, CPU Address 594
Accessed by CPU and I²C (R/W)
Bits[0]:
Enable User Port 0 Priority
1 – Enable
0 – Disable
Bits[1]:
Enable User Port 1 Priority
Bits[2]:
Enable User Port 2 Priority
Bits[3]:
Enable User Port 3 Priority
Bits[4]:
Enable User Port 4 Priority
Bits[5]:
Enable User Port 5 Priority
Bits[6]:
Enable User Port 6 Priority
Bits[7]:
Enable User Port 7 Priority
13.3.6.34
USER_PORT_FORCE_DISCARD[7:0] – User Define Logic Port 0~7 Force Discard
I²C Address h0A7, CPU Address 595
Accessed by CPU and I²C (R/W)
Bits[0]:
Enable User Port 0 Force Discard
1 – Enable
0 – Disable
Bits[1]:
Enable User Port 1 Force Discard
Bits[2]:
Enable User Port 2 Force Discard
Bits[3]:
Enable User Port 3 Force Discard
Bits[4]:
Enable User Port 4 Force Discard
Bits[5]:
Enable User Port 5 Force Discard
Bits[6]:
Enable User Port 6 Force Discard
Bits[7]:
Enable User Port 7 Force Discard
87
Zarlink Semiconductor Inc.
ZL50404
13.3.6.35
Data Sheet
RLOWL – User Define Range Low Bit 7:0
I²C Address h0AE, CPU Address: 5A0
Accessed by CPU and I²C (R/W)
Bits[7:0]:
13.3.6.36
Lower 8 bit of the User Define Logical Port Low Range
RLOWH – User Define Range Low Bit 15:8
I²C Address h0AF, CPU Address: 5A1
Accessed by CPU and I²C (R/W)
Bits[7:0]:
13.3.6.37
Upper 8 bit of the User Define Logical Port Low Range
RHIGHL – User Define Range High Bit 7:0
I²C Address h0B0, CPU Address: 5A2
Accessed by CPU and I²C (R/W)
Bits[7:0]:
13.3.6.38
Lower 8 bit of the User Define Logical Port High Range
RHIGHH – User Define Range High Bit 15:8
I²C Address h0B1, CPU Address: 5A3
Accessed by CPU and I²C (R/W)
Bits[7:0]:
13.3.6.39
Upper 8 bit of the User Define Logical Port High Range
RPRIORITY – User Define Range Priority
I²C Address h0B2, CPU Address: 5A4
Accessed by CPU and I²C (R/W)
RLOW and RHIGH form a range for logical ports to be classified with priority specified in RPRIORITY.
Bits[0]:
Drop Priority (inclusive only)
Bit [3:1]
Transmit Priority (inclusive only)
Bit [5:4]
Reserved
Bit [7:6]
00 - No Filtering
01 - Exclusive Filtering (x<=RLOW or x>=RHIGH)
10 - Inclusive Filtering (RLOW<x<RHIGH)
11 - Invalid
88
Zarlink Semiconductor Inc.
ZL50404
13.3.7
13.3.7.1
Data Sheet
(Group 6 Address) MISC Group
MII_OP0 – MII Register Option 0
I²C Address 0BC, CPU Address:h600
Accessed by CPU and I²C (R/W)
Bit [4:0]:
Vendor specified link status register address (null value means don’t use it)
(Default 00). This is used if the Linkup bit position in the PHY is non-standard
Bit [6:5]
Reserved
Bits [7]:
Half duplex flow control feature
0 = Half duplex flow control always enable
1 = Half duplex flow control by negotiation
13.3.7.2
MII_OP1 – MII Register Option 1
I²C Address 0BD, CPU Address:h601
Accessed by CPU and I²C (R/W)
Bits[3:0]:
Duplex bit location in vendor specified register
Bits[7:4]:
Speed bit location in vendor specified register
(Default 00)
13.3.7.3
FEN – Feature Register
I²C Address 0BE, CPU Address:h602)
Accessed by CPU and I²C (R/W)
Bits [0]:
Statistic Counter
0 – Disable (Default)
1 – Enable (all ports)
When statistic counter is enable, an interrupt control frame is generated to
the CPU, every time a counter wraps around. This feature requires an
external CPU.
Bits[1]:
Reserved. Must be 0.
Bit [2]:
Support DS EF Code.
0 – Disable (Default)
1 – Enable (all ports)
When 101110 is detected in DS field (TOS[7:2]), the frame priority is set for
110 and drop is set for 0.
Bit [3]:
Reserved. Must be 0.
Bit [4]:
Reserved. Must be 1.
89
Zarlink Semiconductor Inc.
ZL50404
Bit [5]:
Data Sheet
Report to CPU
0 – Disable (Default)
1 – Enable
When disable new MAC address report or aging reports are disable for all
ports. When enable, register SE_OPMODE is used to enable/disable
selectively each function.
13.3.7.4
Bit [6]:
MII Management State Machine
0: Enable (Default)
1: Disable
This bit must be set so that there is no contention on the MDIO bus between
MII Management state machine and MIIC & MIID PHY register accesses.
Bit [7]:
MCT Link List structure
0 – Enable (Default)
1 – Disable
MIIC0 – MII Command Register 0
CPU Address:h603
Accessed by CPU (R/W)
Bits[7:0]:
MII Command Data [7:0]
Note: Before programming MII command: set FEN[6], check MIIC3, making sure no RDY, and no VALID; then
program MII command.
13.3.7.5
MIIC1 – MII Command Register 1
CPU Address:h604
Accessed by CPU (R/W)
Bits[7:0]:
MII Command Data [15:8]
Note: Before programming MII command: set FEN[6], check MIIC3, making sure no RDY and no VALID; then
program MII command.
13.3.7.6
MIIC2 – MII Command Register 2
CPU Address:h605
Accessed by CPU (R/W)
Bit [4:0]
REG_AD – Register PHY Address
Bit [6:5]
OP – Operation code “10” for read command and “01” for write command
Bit [7]
Reserved
Note: Before programming MII command: set FEN[6], check MIIC3, making sure no RDY and no VALID; then
program MII command.
90
Zarlink Semiconductor Inc.
ZL50404
13.3.7.7
Data Sheet
MIIC3 – MII Command Register 3
CPU Address:h606
Accessed by CPU (R/W)
Bits [4:0]
PHY_AD – 5 Bit PHY Address
Bit [5]
Reserved
Bit [6]
VALID – Data Valid from PHY (Read Only)
Bit [7]
RDY – Data is returned from PHY (Read Only)
Note: Before programming MII command: set FEN[6], check MIIC3, making sure no RDY and no VALID; then
program MII command. Writing this register will initiate a serial management cycle to the MII management
interface.
13.3.7.8
MIID0 – MII Data Register 0
CPU Address:h607
Accessed by CPU (RO)
Bits[7:0]:
13.3.7.9
MII Data [7:0]
MIID1 – MII Data Register 1
CPU Address:h608
Accessed by CPU (RO)
Bits[7:0]:
13.3.7.10
MII Data [15:8]
USD – One Micro Second Divider
CPU Address:h609
Accessed by CPU (R/W)
Bits[5:0]:
Divider to get one micro second from M_CLK (only used when not in standard RMII mode)
In a MII or GPSI system, a 50MHz M_CLK may not be available. The system designer can
decide to use another frequency on the M_CLK signal. To compensate for this, this register
is required to be programmed.
For example. If 20MHz is used on M_CLK, to compensate for the difference, this register is
programmed with 20 to provide 1usec for internal reference.
Bits[7:6]:
Reserved
91
Zarlink Semiconductor Inc.
ZL50404
13.3.7.11
Data Sheet
DEVICE Mode
CPU Address:h60A
Accessed by CPU (R/W)
Bit [0]:
Reserved
Bit [1]:
CPU Interrupt Polarity
0: Negative Polarity
1: Positive Polarity (Default)
Bit [7:2]:
Reserved
13.3.7.12
CHECKSUM - EEPROM Checksum
I²C Address 0FF, CPU Address:h60B
Accessed by CPU and I²C (R/W)
Bit [7:0]:
Checksum content (Default 0)
This register is used in unmanaged mode only. Before requesting that the ZL50404 updates the EEPROM device,
the correct checksum needs to be calculated and written into this checksum register.
The checksum formula is:
FF
Σ
I²C register = 0
i=0
When the ZL50404 boots from the EEPROM the checksum is calculated and the value must be zero. If the
checksum is not zeroed the ZL50404 does not start and pin CHECKSUM_OK is set to zero.
13.3.7.13
LHBTimer – Link Heart Beat Timeout Timer
CPU Address:h610
Accessed by CPU (R/W)
In slot time (512 bit time). LHB packet will be sent out to the remote device if no other packet is transmitted in half
this period. The receiver will trigger LHB timeout interrupt if not receiving any good packet in this period.
13.3.7.14
LHBReg0, LHBReg1 - Link Heart Beat OpCode
CPU Address:h611, h612
Accessed by CPU (R/W)
The LHB frame uses MAC control frame format (same as flow control frame.) The register here defines the
operation code (we recommend h00-12).
92
Zarlink Semiconductor Inc.
ZL50404
13.3.7.15
fMACCReg0, fMACCReg1 - MAC Control Frame OpCode
CPU Address:h613, h614
Accessed by CPU (R/W)
The registers define the operation code if MAC control frame is forced out by processor.
13.3.7.16
FCB Base Address Register 0
I²C Address 0BF, CPU Address:h620
Accessed by CPU and I²C (R/W)
Bit [7:0]
13.3.7.17
FCB Base address bit 7:0 (Default 0)
FCB Base Address Register 1
I²C Address 0C0, CPU Address:h621
Accessed by CPU and I²C (R/W)
Bit [7:0]
13.3.7.18
FCB Base address bit 15:8 (Default 0x60)
FCB Base Address Register 2
I²C Address 0C1, CPU Address:h622
Accessed by CPU and I²C (R/W)
Bit [7:0]
13.3.8
13.3.8.1
FCB Base address bit 23:16 (Default 0)
(Group 7 Address) Port Mirroring Group
MIRROR CONTROL – Port Mirror Control Register
CPU Address 70C
Accessed by CPU (R/W) (Default 00)
Bit [3:0]:
Destination port to be mirrored to.
Bit [4]
Mirror Flow from MIRROR_SRC_MAC[5:0] to MIRROR_DEST_MAC[5:0]
Bit [5]
Mirror Flow from MIRROR_DEST_MAC[5:0] to MIRROR_SRC_MAC[5:0]
Bit [6]:
Mirror when address is destination
Bit [7]:
Mirror when address is source
93
Zarlink Semiconductor Inc.
Data Sheet
ZL50404
13.3.8.2
Data Sheet
MIRROR_DEST_MAC[5:0] – Mirror Destination MAC Address 0~5
CPU Address 700-705
Accessed by CPU (R/W)
13.3.8.3
DEST_MAC5
DEST_MAC4
DEST_MAC3
DEST_MAC2
DEST_MAC1
DEST_MAC0
[47:40]
(Default 00)
[39:32]
(Default 00)
[31:24]
(Default 00)
[23:16]
(Default 00)
[15:8]
(Default 00)
[7:0]
(Default 00)
MIRROR_SRC _MAC[5:0] – Mirror Source MAC Address 0~5
CPU Address 706-70B
Accessed by CPU (R/W)
13.3.8.4
SRC_MAC5
SRC_MAC4
SRC_MAC3
SRC_MAC2
SRC_MAC1
SRC_MAC0
[47:40]
(Default 00)
[39:32]
(Default 00)
[31:24]
(Default 00)
[23:16]
(Default 00)
[15:8]
(Default 00)
[7:0]
(Default 00)
RMAC_MIRROR0 – RMAC Mirror 0
CPU Address 710
Accessed by CPU (R/W)
13.3.8.5
Bit [2:0]:
Source port to be mirrored
Bit [3]:
Mirror path
0: Receive
1: Transmit
Bit [6:4]:
Destination port for mirrored traffic
Bit [7]:
Mirror enable
RMAC_MIRROR1 – RMAC Mirror 1
CPU Address 711
Accessed by CPU (R/W)
Bit [2:0]:
Source port to be mirrored
Bit [3]:
Mirror path
0: Receive
1: Transmit
Bit [6:4]:
Destination port for mirrored traffic
Bit [7]:
Mirror enable
94
Zarlink Semiconductor Inc.
ZL50404
13.3.9
13.3.9.1
Data Sheet
(Group 8 Address) Per Port QOS Control
FCRn – Port 0~3,8,9 Flooding Control Register
I²C Address h04C+n; CPU Address:h800+n (n = port number)
Accessed by CPU and I²C (R/W)
13.3.9.2
Bit [3:0]:
U2MR: Unicast to Multicast Rate. Units in terms of time base defined in bits
[6:4]. This is used to limit the amount of flooding traffic from Port n. The value
in U2MR specifies how many packets are allowed to flood within the time
specified by bit [6:4]. To disable this function, program U2MR to 0.
(Default = 0)
Bit [6:4]:
Time Base for Unicast to Multicast, Multicast and Broadcast rate control of
Port n: (Default = 000)
000 = 100us
001 = 200us
010 = 400us
011 = 800us
100 = 1.6ms
101 = 3.2ms
110 = 6.4ms
111 = 12.8ms
Bit [7]:
Reserved
BMRCn - Port 0~3,8,9 Broadcast/Multicast Rate Control
I²C Address h05E+n, CPU Address:h820+n (n = port number)
Accessed by CPU and I²C (R/W)
This broadcast and multicast rate defines for Port n, the number of packets allowed to be forwarded within a
specified time. Once the packet rate is reached, packets will be dropped. To turn off the rate limit, program the
field to 0. Time base is based on register FCR0 [6:4]
13.3.9.3
Bit [3:0]:
Multicast Rate Control. Number of multicast packets allowed within the time defined in
bits 6 to 4 of the Flooding Control Register (FCRn). (Default 0).
Bit [7:4]:
Broadcast Rate Control. Number of broadcast packets allowed within the time defined
in bits 6 to 4 of the Flooding Control Register (FCRn). (Default 0)
PR100_n – Port 0~3 Reservation
I²C Address h06A+n, CPU Address 840+n (n = port number)
Accessed by CPU and I²C (R/W)
Expressed in multiples of 16 granules. (Default 0x6)
95
Zarlink Semiconductor Inc.
ZL50404
13.3.9.4
Data Sheet
PR100_CPU – Port CPU Reservation
I²C Address h073, CPU Address 848
Accessed by CPU and I²C (R/W)
Expressed in multiples of 16 granules. (Default 0x6)
13.3.9.5
PRM – Port MMAC Reservation
I²C Address h072, CPU Address 849
Accessed by CPU and I²C (R/W)
Expressed in multiples of 16 granules. (Default 0x24)
13.3.9.6
PTH100_n – Port 0~3 Threshold
I²C Address h0C2+n, CPU Address 860+n (n = port number)
Accessed by CPU and I²C (R/W)
Expressed in multiples of 16 granules. More than this number used on a source port will trigger either random drop
or flow control (Default 0x3)
13.3.9.7
PTH100_CPU – Port CPU Threshold
I²C Address h0CB, CPU Address 868
Accessed by CPU and I²C (R/W)
Expressed in multiples of 16 granules. More than this number used on a source port will trigger either random drop
or flow control (Default 0x3)
13.3.9.8
PTHG – Port MMAC Threshold
I²C Address h0CA, CPU Address 869
Accessed by CPU and I²C (R/W)
Expressed in multiples of 16 granules. More than this number used on a source port will trigger either random drop
or flow control (Default 0x12)
13.3.9.9
QOSC00, QOSC01 - Classes Byte Limit port 0
Accessed by CPU and I²C (R/W)
•
•
QOSC00 – BYTE_L1 (I²C Address h078, CPU Address 880)
QOSC01 – BYTE_L2 (I²C Address h079, CPU Address 881)
Multiple of 16 granules. The two numbers set the two level for WRED on the high priority queue. When the queue
size exceeds the L1 threshold, received frame will subject to X% (high drop) or Y% (low drop) WRED. When the
queue size exceeds L2 threshold, received frame will either be filtered (high drop) or subject to Z% WRED.
13.3.9.10
QOSC02, QOSC07 - Classes Byte Limit port 1-3
I²C Address 07A-07F, CPU Address:h882-887
Accessed by CPU and I²C (R/W)
Same as QOSC00, QOSC01
96
Zarlink Semiconductor Inc.
ZL50404
13.3.9.11
Data Sheet
QOSC16 - QOSC21 - Classes Byte Limit CPU port
Accessed by CPU and I2C (R/W):
•
•
•
•
•
•
QOSC16
QOSC17
QOSC18
QOSC19
QOSC20
QOSC21
–
–
–
–
–
–
BYTE_L11 Level 1 for queue 1 (I2C Address h088, CPU Address 890)
BYTE_L21 Level 2 for queue 1 (I2C Address h089, CPU Address 891)
BYTE_L12 Level 1 for queue 2 (I2C Address h08A, CPU Address 892)
BYTE_L22 Level 2 for queue 2 (I2C Address h08B, CPU Address 893)
BYTE_L13 Level 1 for queue 3 (I2C Address h08C, CPU Address 894)
BYTE_L23 Level 2 for queue 3 (I2C Address h08D, CPU Address 895)
Multiple of 16 granules. The two numbers set the two level for WRED on the high priority queue. When the queue
size exceeds the L1 threshold, received frame will subject to X% (high drop) or Y% (low drop) WRED. When the
queue size exceeds L2 threshold, received frame will either be filtered (high drop) or subject to Z% WRED.
13.3.9.12
QOSC22 - QOSC27 - Classes Byte Limit MMAC port
Accessed by CPU and I²C (R/W)
•
•
•
•
•
•
QOSC22
QOSC23
QOSC24
QOSC25
QOSC26
QOSC27
–
–
–
–
–
–
BYTE_L11 Level 1 for queue 1 (I²C Address h08E, CPU Address 896)
BYTE_L21 Level 2 for queue 1 (I²C Address h08F, CPU Address 897)
BYTE_L12 Level 1 for queue 2 (CPU Address 898)
BYTE_L22 Level 2 for queue 2 (CPU Address 899)
BYTE_L13 Level 1 for queue 3 (CPU Address 89A)
BYTE_L23 Level 2 for queue 3 (CPU Address 89B)
Multiple of 16 granules. The two numbers set the two level for WRED on the high priority queue. When the queue
size exceeds the L1 threshold, received frame will subject to X% (high drop) or Y% (low drop) WRED. When the
queue size exceeds L2 threshold, received frame will either be filtered (high drop) or subject to Z% WRED.
13.3.9.13
QOSC28 - QOSC31 - Classes WFQ Credit For MMAC
Accessed by CPU (R/W)
W0 – QOSC28[5:0] – CREDIT_C00 (CPU Address 89C)
W1 – QOSC29[5:0] – CREDIT_C01 (CPU Address 89D)
W2 – QOSC30[5:0] – CREDIT_C02 (CPU Address 89E)
W3 – QOSC31[5:0] – CREDIT_C03 (CPU Address 89F)
QOSC28 through QOSC31 represents one set of WFQ parameters for MMAC port. The granularity of the numbers
is 1, and their sum must be 64. QOSC31 corresponds to W3 that is the highest priority, and QOSC27 corresponds
to W0. Default scheduling method will be strict priority across all queues. Only when the bit 7 in the class is set, the
queue will be scheduled as WFQ. The credit number also works as shaper credit if bit 6 is set. The queue with
shaper enabled will be scheduled by strict priority when the token is available. The shaper setting override the NS
setting.
Bit [5:0]:
Class scheduling credit
Bit [6]:
Shaper enable
Bit [7]:
Not strict priority apply
97
Zarlink Semiconductor Inc.
ZL50404
13.3.9.14
Data Sheet
QOSC36 - QOSC39 - Shaper Control Port MMAC
Accessed by CPU (R/W)
W0 – QOSC36[7:0] – TOKEN_LIMIT_C00 (CPU Address 8A4)
W1 – QOSC37[7:0] – TOKEN_LIMIT_C01 (CPU Address 8A5)
W2 – QOSC38[7:0] – TOKEN_LIMIT_C02 (CPU Address 8A6)
W3 – QOSC39[7:0] – TOKEN_LIMIT_C03 (CPU Address 8A7)
QOSC36 through QOSC39 represents one set of token limit on the shaper of MMAC port. The granularity of the
numbers is 64 bytes. The shaper is implemented as leaky bucket and the limit here works as bucket size. Since the
hardware implementation can keep negative number, the limit can be as small as one and still can transmit
oversized frame, as long as one byte token is available.
13.3.10
(Group E Address) System Diagnostic
NOTE: Device Manufacturing test registers.
13.3.10.1
DTSRL – Test Output Selection
CPU Address E00
Accessed by CPU (R/W)
Test group selection for testout[7:0].
13.3.10.2
DTSRM – Test Output Selection
CPU Address E01
Accessed by CPU (R/W)
Test group selection for testout[15:8].
13.3.10.3
TESTOUT0, TESTOUT1 – Testmux Output [7:0], [15:8]
CPU Address E02, E03
Accessed by CPU (RO)
13.3.10.4
MASK0-MASK4 – Timeout Reset Mask
CPU Address E10-E14
Accessed by CPU (R/W)
Disable timeout reset on selected state machine status.
See Programming Timeout Reset application note, ZLAN-41, for more information.
98
Zarlink Semiconductor Inc.
ZL50404
13.3.10.5
Data Sheet
BOOTSTRAP0 – BOOTSTRAP3
CPU Address E80-E83
Accessed by CPU (RO)
31
23
BT3
13.3.10.6
15
BT2
0
BT1
BT0
Bit [15:0]:
Bootstrap value from TSTOUT[15:0]:
Bit [6:0]: TSTOUT[6:0]
Bit [8:7]: Invert of TSTOUT[8:7]
Bit [9]: TSTOUT[11]
Bit [10]: TSTOUT[9]
Bit [11]: TSTOUT[10]
Bit [14:12]: TSTOUT[14:12]
Bit [15]: Always 0
Bit [23:16]:
Bootstrap value from M[3:0]_TXEN
Bit [16]: M0_TXEN
Bit [17]: M1_TXEN
...
Bit [19]: M3_TXEN
Bit [31:20]:
Reserved
PRTFSMST0~3,8,9
CPU Address E90+n
Accessed by CPU (RO)
Bit [0]:
TX FSM NOT idle for 5 sec
Bit [1]:
TX FIFO control NOT idle for 5 sec
Bit [2]:
RX SFD detection NOT idle for 5 sec
Bit [3]:
RXINF NOT idle for 5 sec
Bit [4]:
PTCTL NOT idle for 5 sec
Bit [5]:
Reserved
Bit [6]
LHB frame detected
Bit [7]:
LHB receiving timeout
99
Zarlink Semiconductor Inc.
ZL50404
13.3.10.7
PRTQOSST0-PRTQOSST3
CPU Address EA0+n
Accessed by CPU (RO)
13.3.10.8
Bit [0]:
Source port reservation low
Bit [1]:
No source port buffer left
Bit [2]:
Unicast congestion detected on best effort queue
Bit [3]:
Reserved
Bit [4]:
High priority queue reach L1 WRED level
Bit [5]:
High priority queue reach L2 WRED level
Bit [6]:
Low priority MC queue full
Bit [7]:
High priority MC queue full
PRTQOSST8A, PRTQOSST8B (CPU port)
CPU Address EA8 – EA9
Accessed by CPU (RO)
0
15
PQSTB
PQSTA
Bit [0]:
Source port reservation low
Bit [1]:
No source port buffer left
Bit [2]:
Unicast congestion detected on best effort queue
Bit [3]:
Reserved
Bit [4]:
priority queue 1 reach L1 WRED level
Bit [5]:
priority queue 1 reach L2 WRED level
Bit [6]:
priority queue 2 reach L1 WRED level
Bit [7]:
priority queue 2 reach L2 WRED level
Bit [8]:
priority queue 3 reach L1 WRED level
Bit [9]:
priority queue 3 reach L2 WRED level
Bit [10]:
priority 0 MC queue full
Bit [11]:
priority 1 MC queue full
Bit [12]:
priority 2 MC queue full
Bit [13]:
Priority 3 MC queue full
Bit [15:14]:
Reserved
100
Zarlink Semiconductor Inc.
Data Sheet
ZL50404
13.3.10.9
PRTQOSST9A, PRTQOSST9B (MMAC port)
CPU Address EAA – EAB
Accessed by CPU (RO)
0
15
PQSTB
PQSTA
Bit [0]:
Source port reservation low
Bit [1]:
No source port buffer left
Bit [2]:
Unicast congestion detected on best effort queue
Bit [3]:
Reserved
Bit [4]:
Priority queue 1 reach L1 WRED level
Bit [5]:
Priority queue 1 reach L2 WRED level
Bit [6]:
Priority queue 2 reach L1 WRED level
Bit [7]:
Priority queue 2 reach L2 WRED level
Bit [8]:
Priority queue 3 reach L1 WRED level
Bit [9]:
Priority queue 3 reach L2 WRED level
Bit [10]:
Priority 0 MC queue full
Bit [11]:
Priority 1 MC queue full
Bit [12]:
Priority 2 MC queue full
Bit [13]:
Priority 3 MC queue full
Bit [15:14]:
Reserved
101
Zarlink Semiconductor Inc.
Data Sheet
ZL50404
13.3.10.10
CLASSQOSST
CPU Address EAC
Accessed by CPU (RO)
13.3.10.11
Bit [0]:
No share buffer
Bit [1]:
No class 1 buffer
Bit [2]:
No class 2 buffer
Bit [3]:
No class 3 buffer
Bit [7:4]:
Reserved
PRTINTCTR
CPU Address EAD
Accessed by CPU (R/W)
13.3.10.12
Bit [0]:
Interrupt when source buffer low
Bit [1]:
Interrupt when no source buffer
Bit [2]:
Interrupt when UC congest
Bit [3]:
Interrupt when L1 WRED level
Bit [4]:
Interrupt when L2 WRED level
Bit [5]:
Interrupt when MC queue full
Bit [6]:
Interrupt when LHB timeout
Bit [7]:
Interrupt when no class buffer
QMCTRL0~3,8,9
CPU Address EB0+n
Accessed by CPU (R/W)
Bit [0]:
Suspend port scheduling (no departure)
Bit [1]:
Reset queue
Bit [4:2]:
Reserved
Bit [5]:
Force out MAC control frame
Bit [6]:
Force out XOFF flow control frame
Bit [7]:
Force out XON flow control frame
102
Zarlink Semiconductor Inc.
Data Sheet
ZL50404
13.3.10.13
QCTRL
CPU Address EBA
Accessed by CPU (R/W)
13.3.10.14
Bit [0]:
Stop QM FSM at idle
Bit [1]:
Stop MCQ FSM at idle
Bit [2]:
Stop new granule grant to any source
Bit [3]:
Stop release granule from any source
Bit [7:4]:
Reserved
BMBISTR0, BMBISTR1
CPU Address EBB, EBC
Accessed by CPU (RO)
13.3.10.15
BMControl
CPU Address EBD
Accessed by CPU (R/W)
13.3.10.16
Bit [3:0]:
Block Memory redundancy control
0: Use hardware detected value
All others: Overwrite the hardware detected memory swap map
Bit [7:4]:
Reserved
BUFF_RST
CPU Address EC0
Accessed by CPU (R/W)
Bit [3:0]
Assign a value that the pool to be reset
0: port 0 pool
1: port 1 pool
2: port 2 pool
3: port 3 pool
7-4: rsvd
8: port MMAC pool
9: shared pool
10: class 1 pool
11: class 2 pool
12: class 3 pool
13: multicast pool
14: cpu pool
15: reserved
Bit [4]
If this bit is 1, then all the pools are assigned
103
Zarlink Semiconductor Inc.
Data Sheet
ZL50404
Bit [5]
Set 1 to reset the pools that are assigned
Bit [7:6]
Reserved
Data Sheet
If CPU wants to reset pools again, CPU has to clear bit 5 and then set bit 5.
Note: Before CPU doing so, CPU should set QCTRL (CPU Address EBA) bit 2 and bit 3 to one. After reset the
pools, CPU shall reprogram free granule link list (CPU address EC1, EC2, EC3, EC4, EC5, EC6). Then clear
QCTRL (EBA).
13.3.10.17
FCB_HEAD_PTR0, FCB_HEAD_PTR1
CPU address EC1
Accessed by CPU (R/W)
Bit [7:0]
Fcb_head_ptr[7:0]. The head pointer of free granule link that CPU assigns.
CPU address EC2
Accessed by CPU (R/W)
Bit [6:0]
Fcb_head_ptr[14:8]. The head pointer of free granule link that CPU assigns.
Bit [7]
Set 1 to write
If CPU wants to write again, CPU has to clear bit 15 and then set bit 15.
13.3.10.18
FCB_TAIL_PTR0, FCB_TAIL_PTR1
CPU address EC3
Accessed by CPU (R/W)
Bit [7:0]
Fcb_tail_ptr[7:0]. The tail pointer of free granule link that CPU assigns.
CPU address EC4
Accessed by CPU (R/W)
Bit [6:0]
Fcb_tail_ptr[14:8]. The tail pointer of free granule link that CPU assigns.
Bit [7]
Set 1 to write
If CPU wants to write again, CPU has to clear bit 15 and then set bit 15.
13.3.10.19
FCB_NUM0, FCB_NUM1
CPU address EC5
Accessed by CPU (R/W)
Bit [7:0]
Fcb_number[7:0]. The total number of granules that CPU assigns.
104
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
CPU address EC6
Accessed by CPU (R/W)
Bit [6:0]
Fcb_number[14:8]. The total number of granules that CPU assigns.
Bit [7]
Set 1 to write
If CPU wants to write again, CPU has to clear bit 15 and then set bit 15.
Note: There are two ways to reprogram the free granules.
1. CPU links all the granules: CPU writes memory directly, at last write head pointer (address EC1, EC2), tail
pointer (address EC3, EC4) and granule number (address EC5, EC6).
2. CPU tells Buffer Manager to link: CPU clear head pointer (address EC1, EC2), clear tail pointer (address EC3,
EC4), then write granule number that tells Buffer Manager to link (address EC5, EC6).
13.3.10.20
BM_RLSFF_CTRL
CPU address EC7
Accessed by CPU (R/W)
Bit [0]
Read BM release FIFO.
Bit [7:1]
Reserved
The information of BM release FIFO is relocated to registers BM_RLSFF_INFO (address ECD, ECC, ECB, ECA,
EC9 and EC8). If the FIFO is not empty, CPU can read out the next by setting the bit 0. Read only happens when
bit 0 is changing from 0 to 1.
13.3.10.21
BM_RSLFF_INFO[5:0]
CPU address EC8
Accessed by CPU (RO)
Bit [7:0]
Rls_head_ptr[7:0].
CPU address EC9
Accessed by CPU (RO)
Bit [6:0]
Rls_head_ptr[14:8].
Bit [7]
Rls_tail_ptr[0]
CPU address ECA
Accessed by CPU (RO)
Bit [7:0]
Rls_tail_ptr[8:1]
105
Zarlink Semiconductor Inc.
ZL50404
Data Sheet
CPU address ECB
Accessed by CPU (RO)
Bit [5:0]
Rls_tail_ptr[14:9]
Bit [7:6]
Rls_count[1:0]
CPU address ECC
Accessed by CPU (RO)
Bit [4:0]
Rls_count[6:2]
Bit [5]
If 1, then It is multicast packet.
Bit [7:6]
Rls_src_port[1:0[
CPU address ECD
Accessed by CPU (RO)
Bit [1:0]
Rls_src_port[3:2]
Bit [3:2]
Class[1:0]
Bit [4]
This release request is from QM directly.
Bit [7:5]
Entries count in release FIFO, 0 means FIFO is empty
13.3.11
(Group F Address) CPU Access Group
13.3.11.1
GCR - Global Control Register
CPU Address: hF00
Accessed by CPU (R/W)
Bit [0]:
Store configuration (Default = 0)
Write ‘1’ followed by ‘0’ to store configuration into external EEPROM
Bit [1]:
Store configuration and reset (Default = 0)
Write ‘1’ to store configuration into external EEPROM and reset chip
Bit [2]:
Start BIST (Default = 0)
Write ‘1’ followed by ‘0’ to start the device’s built-in self-test. The result is
found in the DCR register.
Bit [3]:
Soft Reset (Default = 0)
Write ‘1’ to reset chip
106
Zarlink Semiconductor Inc.
ZL50404
Bit [4]:
Data Sheet
Initialization Completed (Default = 0)
This bit is reserved in unmanaged mode.
In managed mode, the CPU writes this bit with ‘1’ to indicate initialization is
completed and ready to forward packets. The ‘0' to '1' transition will toggle
TSTOUT[2] from low to high.
Bit [7:5]:
13.3.11.2
Reserved
DCR - Device Status and Signature Register
CPU Address: hF01
Accessed by CPU (RO)
Bit [0]:
1: Busy writing configuration to I²C
0: Not busy (not writing configuration to I²C)
Bit [1]:
1: Busy reading configuration from I²C
0: Not busy (not reading configuration from I²C)
Bit [2]:
1: BIST in progress
0: BIST not running
Bit [3]:
1: RAM Error
0: RAM OK
Bit [5:4]:
Device Signature
10: ZL50404 device
Bit [7:6]:
Revision
00: Initial Silicon
01: Second Silicon
13.3.11.3
DCR1 - Device Status Register 1
CPU Address: hF02
Accessed by CPU (RO)
Bit [6:0]
Reserved
Bit [7]
Chip initialization completed
107
Zarlink Semiconductor Inc.
ZL50404
13.3.11.4
Data Sheet
DPST – Device Port Status Register
CPU Address:hF03
Accessed by CPU (R/W)
Bit [4:0]:
Read back index register. This is used for selecting what to read back from
DTST. (Default 00)
- 5’b00000 - Port 0 Operating mode and Negotiation status
- 5’b00001 - Port 1 Operating mode and Negotiation status
- 5’b00010 - Port 2 Operating mode and Negotiation status
- 5’b00011 - Port 3 Operating mode and Negotiation status
- 5’b001xx - Reserved
- 5’b01000 - Port CPU Operating mode and Negotiation status
- 5’b01001 - Port MMAC Operating mode and Negotiation status
Bit [7:5]:
Reserved
13.3.11.5
DTST – Data read back register
CPU Address: hF04
Accessed by CPU (RO)
This register provides various internal information as selected in DPST bit [4:0]. Refer to the PHY Port Control
Application Note, ZLAN-37.
Bit [0]
Flow control enable
Bit [1]
Full duplex port
Bit [2]
Fast Ethernet port
Bit [3]
Link is down
Bit [4]
Auto negotiation enabled
1: Disable
0: Enable
Bit [5]
Reserved
Bit [6]
Reserved
Bit [7]
Module deleted (for hot swap purpose)
13.3.11.6
DA – DA Register
CPU Address: hFFF
Accessed by CPU (RO)
Always return 8’h DA. Indicate the CPU interface or serial port connection is good.
Bit [7:0]
Always return DA
108
Zarlink Semiconductor Inc.
ZL50404
14.0
Characteristics and Timing
14.1
Absolute Maximum Ratings
Storage Temperature
-65°C to +150°C
Operating Temperature
-40°C to +85°C
Maximum Junction Temperature
+125°C
Supply Voltage VCC with Respect to VSS
+2.95 V to +3.65 V
Supply Voltage VDD with Respect to VSS
+1.60 V to +2.00 V
Voltage on 5 V Tolerant Input Pins
-0.5 V to (VCC + 2.5 V)
Voltage on Other Pins
-0.5 V to (VDD + 0.3 V)
Data Sheet
Caution: Stress above those listed may damage the device. Exposure to the Absolute Maximum Ratings for
extended periods may affect device reliability. Functionality at or above these limits is not implied.
14.2
DC Electrical Characteristics
VCC = 3.3 V +/- 10%
TAMBIENT = -40 C to +85 C
VDD = 1.8 V +/- 5%
109
Zarlink Semiconductor Inc.
ZL50404
14.3
Data Sheet
Recommended Operating Conditions
Symbol
Parameter Description
Min.
Typ.
Max.
Unit
25
100
MHz
fosc
Frequency of Operation (SCLK)
ICC
VCC Supply Current – @ 25 MHz (full line rate)
45
mA
IDD
VDD Supply Current – @ 25 MHz (full line rate)
160
mA
VOH
Output High Voltage (CMOS)
VOL
Output Low Voltage (CMOS)
VIH
Input High Voltage (TTL 5 V tolerant)
VIL
2.4
V
0.4
V
VCC + 2.0
V
Input Low Voltage (TTL 5 V tolerant)
0.8
V
IIL
Input Leakage Current (0.1 V < VIN < VCC)
(all pins except those with internal
pull-up/pull-down resistors)
10
µA
IOL
Output Leakage Current (0.1 V < VOUT < VCC)
10
µA
CIN
Input Capacitance
5
pF
COUT
Output Capacitance
5
pF
CI/O
I/O Capacitance
7
pF
θja
Thermal resistance with 0 air flow
24.3
C/W
θja
Thermal resistance with 1 m/s air flow
20.0
C/W
θja
Thermal resistance with 2 m/s air flow
18.1
C/W
θjc
Thermal resistance between junction and case
4.6
C/W
2.0
110
Zarlink Semiconductor Inc.
ZL50404
14.4
14.4.1
Data Sheet
AC Characteristics and Timing
Typical Reset & Bootstrap Timing Diagram
RESIN#
RESETOUT#
Tri-Stated
R1
R3
Bootstrap Pins
Outputs
Inputs
Outputs
R2
Figure 10 - Typical Reset & Bootstrap Timing Diagram
Symbol
Parameter
Min.
R1
Delay until RESETOUT# is tri-stated
R2
Bootstrap stabilization
R3
RESETOUT# assertion
1 µs
Typ.
Note:
10 ns
RESETOUT# state is then determined by
the external pull-up/down resistor
10 µs
Bootstrap pins sampled on rising edge of
RESIN#
2 ms
Table 13 - Reset & Bootstrap Timing
111
Zarlink Semiconductor Inc.
ZL50404
14.4.2
Data Sheet
Reduced Media Independent Interface
M_CLK
M6-max
M6-min
Mn_TXEN
M7-max
M7-min
Mn_TXD[1:0]
Figure 11 - AC Characteristics – Reduced media independent Interface (TX)
M_CLK
M2
Mn_RXD
M3
M4
Mn_CRS_DV
M5
Figure 12 - AC Characteristics – Reduced Media Independent Interface (RX)
M_CLK=50 MHz
Symbol
Parameter
Note:
Min. (ns)
Max. (ns)
M2
M[3:0]_RXD[1:0] Input Setup Time
4
M3
M[3:0]_RXD[1:0] Input Hold Time
2
M4
M[3:0]_CRS_DV Input Setup Time
4
M5
M[3:0]_CRS_DV Input Hold Time
3
M6
M[3:0]_TXEN Output Delay Time
2
11
CL = 20 pF
M7
M[3:0]_TXD[1:0] Output Delay Time
2
11
CL = 20 pF
Table 14 - AC Characteristics – Reduced Media Independent Interface
112
Zarlink Semiconductor Inc.
ZL50404
14.4.3
Data Sheet
Media Independent Interface
Mn_TXCLK
MM6-max
MM6-min
Mn_TXEN
MM7-max
MM7-min
Mn _TXD[3:0]
Figure 13 - AC Characteristics – Media independent Interface (TX)
Mn_RXCLK
MM2
Mn_RXD[3:0]
MM4
Mn_CRS_DV
MM
3
MM
5
Figure 14 - AC Characteristics – Media Independent Interface (RX)
25 MHz
Symbol
Parameter
Note:
Min. (ns)
Max. (ns)
MM2
M[9,3:0]_RXD[3:0] Input Setup Time
4
MM3
Mn_RXD[3:0] Input Hold Time
2
MM4
M[9,3:0]_CRS_DV Input Setup Time
4
MM5
Mn_CRS_DV Input Hold Time
2
MM6
Mn_TXEN Output Delay Time
2
14
CL = 20 pF
MM7
Mn_TXD[3:0] Output Delay Time
2
14
CL = 20 pF
Table 15 - AC Characteristics –Media Independent Interface
113
Zarlink Semiconductor Inc.
ZL50404
14.4.4
Data Sheet
General Purpose Serial Interface (7-wire)
Mn_ TXCLK
SM6-max
SM6-min
Mn_TXEN
SM7-max
SM7-min
Mn_TXD
Figure 15 - AC Characteristics – General Purpose Serial Interface (TX)
Mn_RXCLK
SM2
Mn_RXD
SM3
SM4
Mn_CRS_DV
SM5
Figure 16 - AC Characteristics – General Purpose Serial Interface (RX)
10 MHz
Symbol
Parameter
Note:
Min. (ns)
Max. (ns)
SM2
M[3:0]_RXD Input Setup Time
4
SM3
M[3:0]_RXD Input Hold Time
2
SM4
M[3:0]_CRS_DV Input Setup Time
4
SM5
M[3:0]_CRS_DV Input Hold Time
2
SM6
M[3:0]_TXEN Output Delay Time
2
14
CL = 20 pF
SM7
M[3:0]_TXD Output Delay Time
2
14
CL = 20 pF
Table 16 - AC Characteristics –General Purpose Serial Interface
114
Zarlink Semiconductor Inc.
ZL50404
14.4.5
Data Sheet
MDIO Input Setup and Hold Timing
MDC
D1
D2
MDIO
Figure 17 - MDIO Input Setup and Hold Timing
MDC
D3-max
D3-min
MDIO
Figure 18 - MDIO Output Delay Timing
MDC=500 KHz
Symbol
Parameter
Note:
Min. (ns)
D1
MDIO input setup time
10
D2
MDIO input hold time
2
D3
MDIO output delay time
1
Table 17 - MDIO Timing
115
Zarlink Semiconductor Inc.
Max. (ns)
20
CL = 50 pf
ZL50404
14.4.6
Data Sheet
I²C Input Setup Timing
SCL
S2
S1
SDA
Figure 19 - I²C Input Setup Timing
SCL
SDA
S3-max
S3-min
Figure 20 - I²C Output Delay Timing
SCL=50 KHz
Symbol
Parameter
Note:
Min. (ns)
S1
SDA input setup time
20
S2
SDA input hold time
1
S3*
SDA output delay time
4 usec
Max. (ns)
6 usec
* Open Drain Output. Low to High transistor is controlled by external pullup resistor.
Table 18 - I²C Timing
116
Zarlink Semiconductor Inc.
CL = 30 pf
ZL50404
14.4.7
Data Sheet
Serial Interface Setup Timing
STROBE
D4
D1
Datain
D5
D2
D1
D2
Figure 21 - Serial Interface Setup Timing
STROBE
Dataout
D3-max
D3-min
Figure 22 - Serial Interface Output Delay Timing
Symbol
Parameter
Min. (ns)
Max. (ns)
Note:
D1
DATAIN setup time
20
D2
DATAIN hold time
3 µs
Debounce on
20 ns
Debounce off
D3
DATAOUT output delay time
D4
STROBE low time
D5
1
STROBE high time
50
CL = 100 pf
5 µs
Debounce on
50 ns
Debounce off
5 µs
Debounce on
50 ns
Debounce off
Table 19 - Serial Interface Timing
117
Zarlink Semiconductor Inc.
ZL50404
14.4.8
Data Sheet
JTAG (IEEE 1149.1-2001)
TCK
TMS, TDI
J1
J2
J3-max
TDO
J3-min
Figure 23 - JTAG Timing Diagram
Symbol
Parameter
Min.
Typ.
Max.
Units
TCK frequency of operation
0
10
50
MHz
TCK cycle time
20
ns
TCK clock pulse width
10
ns
TRST# assert time
20
J1
TMS, TDI data setup time
3
ns
J2
TMS, TDI data hold time
7
ns
J3
TCK to TDO data valid
0
Table 20 - JTAG Timing
118
Zarlink Semiconductor Inc.
-
15
ns
ns
Note:
TRST is an
asynchronous signal
ZL50404
15.0
Document Errata
15.1
July 2003
•
Initial Release
15.2
•
•
•
•
•
•
•
•
•
•
•
•
•
February 2004
Added the following to the Feature List:
• 4K jumbo frames
• IEEE 802.3ad support
• Reverse MII/GPSI
Added section on PHY addresses
• Clarified that they are hard-coded
Fixed error in DS on sending Ethernet Frames via serial interface.
• The Status Bytes is sent before the frame, for both Tx and Rx
Added more cross-references to available AppNotes
Added more clock descriptions to “Clocks” on page 43
INT_MASK and INTP_MASK registers should state that the default register value is 0x00
15.4
•
•
•
November 2003
Updated Ball Signal Description Table:
• clarified the ball signal I/O description for Mn_TXCLK & Mn_RXCLK showing these signals are either
inputs OR outputs
• clarified that M9_MTXCLK is an input only
• ball assignments for the Fast Ethernet Access Ports [3:0] MII signals were incorrect
Updated Section 1.4 on page 17 to indicate operation of the internal pull up/down resistors in different
modes
Clarified Section 11.1.3 on page 43 on usage of REF_CLK
Clarified PVMODE register bit description for bits [2] & [5]
Updated ECR4Pn register description as port 9 (uplink) operates differently than the RMAC ports for MII
bi-directional clocking (bits [1:0])
I2C address mapping was corrected for QOSCn registers
Added Maximum Junction Temperature to Section 14.1 on page 109
Updated I/O voltage levels to use TTL spec values rather than % of Vcc
15.3
•
Data Sheet
August 2004
Added Errata List to document
Added section on SCL clock generation
Interrupt Register was incorrectly identified as read only, should be read/write
• Clarified that only bit [7] is not self-clearing
119
Zarlink Semiconductor Inc.
BOTTOM VIEW
TOP VIEW
MIN
MAX
Dimension
1.40
A
A1
0.30
0.50
0.53 REF
A2
D
16.90
17.10
16.90
17.10
E
0.40
0.60
b
1.00
e
N
208
Conforms to JEDEC MO-192
b
SIDE VIEW
Package Code
c Zarlink Semiconductor 2002 All rights reserved.
ISSUE
1
ACN
213730
DATE
14Nov02
APPRD.
Previous package codes
For more information about all Zarlink products
visit our Web Site at
www.zarlink.com
Information relating to products and services furnished herein by Zarlink Semiconductor Inc. or its subsidiaries (collectively “Zarlink”) is believed to be reliable.
However, Zarlink assumes no liability for errors that may appear in this publication, or for liability otherwise arising from the application or use of any such
information, product or service or for any infringement of patents or other intellectual property rights owned by third parties which may result from such application or
use. Neither the supply of such information or purchase of product or service conveys any license, either express or implied, under patents or other intellectual
property rights owned by Zarlink or licensed from third parties by Zarlink, whatsoever. Purchasers of products are also hereby notified that the use of product in
certain ways or in combination with Zarlink, or non-Zarlink furnished goods or services may infringe patents or other intellectual property rights owned by Zarlink.
This publication is issued to provide information only and (unless agreed by Zarlink in writing) may not be used, applied or reproduced for any purpose nor form part
of any order or contract nor to be regarded as a representation relating to the products or services concerned. The products, their specifications, services and other
information appearing in this publication are subject to change by Zarlink without notice. No warranty or guarantee express or implied is made regarding the
capability, performance or suitability of any product or service. Information concerning possible methods of use is provided as a guide only and does not constitute
any guarantee that such methods of use will be satisfactory in a specific piece of equipment. It is the user’s responsibility to fully determine the performance and
suitability of any equipment using such information and to ensure that any publication or data used is up to date and has not been superseded. Manufacturing does
not necessarily include testing of all functions or parameters. These products are not suitable for use in any medical products whose failure to perform may result in
significant injury or death to the user. All products and materials are sold and services provided subject to Zarlink’s conditions of sale which are available on request.
Purchase of Zarlink’s I2C components conveys a licence under the Philips I2C Patent rights to use these components in and I2C System, provided that the system
conforms to the I2C Standard Specification as defined by Philips.
Zarlink, ZL and the Zarlink Semiconductor logo are trademarks of Zarlink Semiconductor Inc.
Copyright Zarlink Semiconductor Inc. All Rights Reserved.
TECHNICAL DOCUMENTATION - NOT FOR RESALE