• Provides on-chip data recovery and clock synthesis.
• Supports dual IEEE 802.3 -1998 GMII interfaces for connection to copper Gigabit
Ethernet physical layer devices.
• Provides dual standard IEEE 802.3 Gigabit Ethernet MACs for frame verification.
• Enables frame filtering on 8 unicast or 64 multicast entries.
• Internal 16k byte egress and 64k byte ingress FIFOs per channel to accommodate
system latencies.
• Incorporates SATURN POS-PHY Level 3 32-bit System Interface clocked up to
104 MHz (32 bit mode only).
• Line side loopback capability for system level diagnostic capability.
• Includes 16 bit generic microprocessor interface for device initialization, control,
register and per port statistics access.
• Provides a standard 5 signal P1149.1 JTAG test port for boundary scan board test
purposes.
• Low power 1.8V CMOS device with 3.3V TTL compatible digital inputs (5V TTL
compatible microprocessor inputs) and 3.3V CMOS/TTL compatible digital outputs
within a 352 pin 27mm by 27mm UBGA package.
• Industrial temperature range (-40°C to +85°C).
2.2 Line Side Interface
• SERDES interface provides 2 differential pairs at 1250 MHz for connection to
electrical optical modules.
• GMII interface provides 8 bit wide TX & RX data interfaces at 125 MHz with control
signals for connection to copper Gigabit Ethernet physical layer devices.
• Allows selection between SERDES and GMII interface on a per channel basis.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The PM3386 S/UNI-2xGE is applicable to equipment implementing high density
Gigabit Ethernet interfaces. The PM3386 is a dual channel SERDES and GMAC
with embedded FIFOs that provides a high density and low power Gigabit
Ethernet solution for direct connection to electrical optical modules. Alternatively,
a GMII interface is provided for connection to copper Gigabit Ethernet physical
layer devices.
On the system side, the POS-PHY Level 3 (32 bit synchronous FIFO style
interface clocked up to 104 MHz) allows a common connection to higher layer
devices. A common system interface simplifies multi-service equipment utilizing
some or all of the following physical layer options:
• OC-48 POS/ATM
• 4xOC-12 POS/ATM
• 16xOC-3 POS/ATM
• Channelized POS/ATM
• High density DS3
• Gigabit Ethernet
The PM3386 is particularly suited for the following applications:
• Core Routers
• Edge Routers
• Enterprise Edge Routers
• Multi-Service Switches/Routers
• SONET/SDH Transport Muxes
These applications require various interfaces (Gigabit Ethernet, ATM, POS, DS3)
which use the POS-PHY Level 3 interface. Service cards for various physical
layer options can re-use upper layer devices and board design to improve timeto market. The use of Gigabit Ethernet within Internet points of presence
(POPs), Super POPs and Transport POPs is increasing due to the requirement
of inexpensive high-speed Layer 2 interconnect. Thus, connections between
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
Edge Routers and Core Routers within a POP are provided via Gigabit Ethernet.
Co-located server clusters are also connected via Gigabit Ethernet to POP
routers. Similarly, Gigabit Ethernet is becoming the choice for connection
between Enterprise Routers and Multi-Service switches. Transport equipment is
looking to provide Ethernet directly over SONET/SDH for wide area transparent
bridging.
In a typical application the S/UNI-2xGE performs data recovery on the Gigabit
Ethernet stream, MAC level frame checks and sends the frame to an upper layer
device (such as an IP processor) for forwarding via the POS-PHY level 3
interface. The S/UNI-2xGE maintains extensive statistics for SNMP and RMON
applications. On egress, frames are formatted into physical frames with the
proper inter-frame gap, preamble and start of frame delimiter. The physical
packet is then serialized for transmission over an external electrical optical
module. The initial configuration and ongoing control and monitoring of the
S/UNI-2xGE are provided via a generic microprocessor interface. The following
diagram shows a typical multi-service card application for the PM3386 S/UNI2xGE with similar cards for OC48 and Quad OC-12 ports.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The PM3386 is a monolithic integrated circuit that implements a two port full
duplex 1000 Mbit/s Gigabit Ethernet MAC data transport device. The PM3386
provides line interface connectivity provided by an on-chip SERDES and GMII
functions and data transport to the up stream device via the industry standard
POS-PHY Level 3 interface.
Serializer-Deserializer (SERDES)
The PM3386 has two internal serializer-deserializer transceivers. The SERDES
are IEEE 802.3-1998 Gigabit Ethernet compatible supporting gigabit data
transfer flows. The SERDES is based on the X3T11 10 Bit specification. The
PM3386 receives and transmits Gigabit Ethernet streams using a bit serial
interface for direct connection to optical transceiver devices. The SERDES
performs data recovery and serial to parallel conversion for connection to the
Enhanced Gigabit Media Access Control block.
Gigabit Media Independent Interface (GMII)
For Gigabit Ethernet over copper support, the PM3386 provides dual standard
GMII interfaces. A copper Gigabit Ethernet physical layer device can be
connected to the PM3386 via this interface.
Enhanced Gigabit Media Access Control (EGMAC)
The Enhanced Gigabit Media Access Control (EGMAC) block provides an
integrated IEEE 802.3-1998 Gigabit Ethernet Media Access Control (MAC)
supporting high performance 1000Base capability. The EGMAC has line side
interfaces for connection to internal (SERDES) and external Gigabit PHY via
GMII on each Gigabit Ethernet port. The Enhanced Gigabit MAC (EGMAC)
incorporates all of the Gigabit Ethernet MAC functions including AutoNegotiation, statistics, and the MAC Control Sub-layer that adheres to IEEE
802.3-1998 providing support for PAUSE control frames. The EGMAC provides
basic frame integrity checks to validate incoming frames. The EGMAC also
provides simple line rate ingress address filtering support via 8 exact-match MAC
address and VID unicast filters, one 64-bin hash-based multicast filter, and the
ability to filter or accept matched frames on a per instance programmable
fashion. All inquires for filtering are done at line rate with no system latency
introduced for look up cycles.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The PM3386 also incorporates a rich set of per port RMON, SNMP, and Etherlike
Management Information Base counters. Deep statistical counters are used for
management counts providing a minimum rollover time of greater than 58
minutes. All counts are easily managed via the Management Statistics (MSTAT)
block.
POS-PHY Level 3 Interface (PL3)
The PM3386 can connect to a single upper layer device through a POS-PHY
Level 3 Interface. The POS-PHY Level 3 interface is a 32-bit wide interface with
a clock rate from 60 to 104 MHz. POS-PHY Level 3 was developed with the
cooperation of the SATURN Development Group to cover all application bit rates
up to and including 3.2 Gbit/s. This interface provides standards support for
interoperation between the PM3386, a multiple PHY layer device, connecting to
one Link Layer device. The interface stresses simplicity of operation to allow
forward migration to more elaborate PHY and Link Layer devices. The POSPHY interface contains 64KB receive and 16KB transmit FIFOs per channel.
These FIFOs contain programmable thresholds specifying full and empty
conditions.
Receive Direction
In the receive direction, the PM3386 can be configured to use the internal
SERDES or the GMII interface on a per channel basis. For SERDES operation,
a Gigabit Ethernet bit stream is received from an external optical transceiver.
The data is recovered and converted from serial to parallel data for connection to
the EGMAC block. The EGMAC terminates the 8B/10B line codes and performs
frame integrity checks (frame length, FCS etc). For GMII operation, the physical
packet is sourced from an external copper physical layer device to the PM3386
via the GMII interface (8 bits clocked at 125 MHz). The EGMAC accepts the 8 bit
data and performs frame integrity checks once the complete frame is received.
The EGMAC can optionally filter erred frames.
Statistics are updated and the frame is sent to the POS-PHY Level 3 interface.
The FIFO’s in the POS-PHY interface accommodate system latencies and allows
for loss-less flow control up to 9.6k bytes. The received frames are then read
through the POS-PHY Level 3 (32 bits clocked from 60-104 MHz) system side
interface.
Transmit Direction
In the transmit direction, packets to be transmitted are written into the POS-PHY
TX FIFO through the POS-PHY Level 3 interface (32 bits clocked from 60-104
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
MHz) from the upper layer device. The channel is selected by the upper layer
device and is indicated in-band on the POS-PHY interface. The EGMAC builds a
properly formatted Ethernet physical packet (padding to minimum size and
inserting the preamble, start of frame delimiter (SFD) and the inter-packet gap
(IPG)). Statistics are updated and the physical packet is sent to the SERDES or
the GMII interface.
For SERDES operation, the EGMAC encodes the physical packet using 8B/10B
encoding and passes the physical packet to the SERDES block. The SERDES
performs parallel to serial conversion using an internally synthesized 1250 MHz
clock. The bit stream is sent to an external optical transceiver for transmission
over fiber cable. For GMII operation, the EGMAC sends the physical packet byte
by byte across the GMII interface (8 bits clocked at 125 MHz) to an external
copper Gigabit Ethernet physical layer device. The copper Gigabit Ethernet
physical layer device then transmits the physical packet over copper cable.
Flow Control
Flow control is handled in the EGMAC block. When a PAUSE control frame is
received, the PM3386 will optionally terminate transmission (after the current
frame is sent) and assert the appropriate channel side band flow control output
to indicate the paused condition. The received PAUSE control frame can be
optionally filtered or passed to the link layer device via the POS-PHY Level 3
interface.
PAUSE control frames are transmitted either under link layer control using
channel side band flow control inputs, under link layer control transparent to the
PM3386, host based PAUSE frame control or under internal control based on
receive FIFO levels. All four methods can provide for loss-less flow control.
General
The PM3386 is configured, controlled and monitored via a generic 16-bit
microprocessor bus interface. The PM3386 also provides a standard 5 signal
IEEE 1149.1 JTAG test port for boundary scan board test purposes.
The PM3386 is implemented in low power, +1.8 Volt, CMOS technology with 5V
TTL compatible digital inputs and 3.3V TTL/CMOS compatible digital outputs.
The PM3386 is packaged in a 352-pin UBGA package.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
125 MHz reference clock used to generate
GTX_CLK0 or GTX_CLK1 during GMII
mode. The Clock Synthesis Unit uses this
clock as it’s input reference during
SERDES mode.
Please refer to the Operations section for a
discussion of clock mode selection
interfacing issues.
Receive Differential Data (Port 0)
These PECL inputs (RXD0+/-) contain the
8B/10B bit serial receive stream. The
receive data is recovered from the RXD0+/bit stream.
Receive Signal Detect (Port 0)
RXSD0 indicates the presence of valid
receive signal power from the Optical
Physical Medium Dependent Device. A
logic level high indicates the presence of
valid data. A logic low indicates a loss of
signal.
RXD1+
RXD1-
Differential
PECL
Input
K26
K25
Receive Differential Data (Port 1)
The PECL inputs RXD1+/- contain the
8B/10B bit serial receive stream. The
receive data is recovered from the RXD1+/bit stream.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
RXSD1 indicates the presence of valid
receive signal power from the Optical
Physical Medium Dependent Device. A
logic level high indicates the presence of
valid data. A logic low indicates a loss of
signal.
Transmit Differential Data (Port 0)
The PECL outputs TXD0+/- contain the
1.25 Gbit/s transmit stream. The TXD0+/outputs are driven using the CSU clock.
Transmit Differential Data (Port 1)
The PECL outputs TXD1+/- contain the
1.25 Gbit/s transmit stream. The TXD1+/outputs are driven using the CSU clock.
Receive and Transmit Analog Test Ports
The ATP[1:0] pins are used for
manufacturing testing only and should be
tied to analog ground.
Table 3-Gigabit Media Independent Interface (GMII)
Signal NameDirectionPin No.Function
GTX_CLK0OutputAD22
GMII Transmit Clock (Port 0)
125 MHz reference clock supplied by the
PM3386.
TXD0[0]
TXD0[1]
TXD0[2]
TXD0[3]
TXD0[4]
TXD0[5]
TXD0[6]
TXD0[7]
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
OutputW24
W23
W25
W26
Y24
Y25
AA24
AA25
GMII Transmit Data (Port 0)
Byte-wide transmit data is output on these
pins synchronously to the PHY device.
The least significant bit, TXD0[0] is the first
bit transferred on the line.
This signal is updated on the rising edge of
GTX_CLK0.
When in GMII mode this signal is an active
high signal asserted when valid data is
present on the TXD0[7:0] and TX_ER0
pins. This signal is updated on the rising
edge of GTX_CLK0.
When in SERDES mode this signal
enables operation of the external
transmitter. When asserted (default active
low) it indicates the potential presence of
valid transmit data. When de-asserted
indicates the absence of valid transmit
data. Note that while in SERDES mode
the polarity of this signal is programmable
to support interoperability with differing
optical transmitters.
GMII Transmit Coding Error (Port 0)
Active high signal asserted when an error
is detected during transmission. Please
refer to the Operations section for a full
listing of error conditions reported by the
PM3386 using the TX_ER0 output.
This signal is updated on the rising edge of
GTX_CLK0.
RX_CLK0Schmitt
Input
AC21
GMII Receive Clock (Port 0)
125 MHz GMII reference clock received
from the PHY device.
RXD0[0]
RXD0[1]
RXD0[2]
RXD0[3]
RXD0[4]
RXD0[5]
RXD0[6]
RXD0[7]
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
InputAF20
AD19
AE20
AF21
AD20
AE21
AF22
AD21
GMII Receive Data (Port 0)
Byte-wide receive data is input on these
pins synchronously from the PHY device.
The least significant bit, RXD0[0] is
expected to contain the first bit received on
the line.
When in GMII mode this signal is an active
high signal asserted when valid data is
present on the TXD1[7:0] and TX_ER1
pins. This signal is updated on the rising
edge of GTX_CLK1.
When in SERDES mode this signal
enables operation of the external
transmitter. When asserted (default active
low) it indicates the potential presence of
valid transmit data. When de-asserted
indicates the absence of valid transmit
data. Note that while in SERDES mode
the polarity of this signal is programmable
to support interoperability with differing
optical transmitters.
GMII Transmit Coding Error (Port 1)
Active high signal asserted when an error
is detected during transmission. Please
refer to the Operations section for a full
listing of error conditions reported by the
PM3386 using the TX_ER1 output. This
signal is updated on the rising edge of
GTX_CLK1.
RX_CLK1Schmitt
Input
B20
GMII Receive Clock (Port 1)
125 MHz GMII reference clock received
from the PHY device.
RXD1[0]
RXD1[1]
RXD1[2]
RXD1[3]
RXD1[4]
RXD1[5]
RXD1[6]
RXD1[7]
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
InputC22
D21
A23
B22
C21
D20
A22
B21
GMII Receive Data (Port 1)
Byte-wide receive data is input on these
pins synchronously from the PHY device.
The least significant bit, RXD1[0] is
expected to contain the first bit received on
the line.
Active high signal asserted when valid data
is present on the RXD1[7:0] and RX_ER1
pins.
This signal is synchronized to RX_CLK1
GMII Receive Error (Port 1)
Active high signal asserted when there has
been an error during the received physical
packet.
This signal is synchronized to RX_CLK1.
MII Management Data Clock
MDC provides the MII reference clock for
communication between the PM3386 and
other transceivers.
MII Management Data
When configured as an input, the external
PHY supplies status during MII
Management read cycles. When
configured as an output, the PM3386
supplies control during MII Management
write/read cycles and data during MII
Management write cycles.
Data values on the MDIO pin are updated
and sampled on the rising edge of MDC.
Table 4-POS-PHY Level 3 Transmit Interface
Signal NameDirectionPin No.Function
TFCLKSchmitt
Input
AF7
POS-PHY Transmit FIFO Write Clock
TFCLK is used to synchronize data transfer
transactions between the higher layer
device and the PM3386. TFCLK cycles at
a 60 to 104 MHz rate.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
This bus carries the packet octets that are
written to the selected transmit FIFO and
the in-band port address to select the
desired transmit FIFO. The TDAT bus is
considered valid only when TENB is
simultaneously asserted.
When a 32-bit interface is used, data must
be transmitted in big endian order on
TDAT[31:0].
TDAT[31:0] is sampled on the rising edge
of TFCLK.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
Active high signal used to indicate that the
current packet must be aborted. TERR
should only be considered valid when
TENB and TEOP are simultaneously
asserted.
TERR is sampled on the rising edge of
TFCLK.
POS-PHY Transmit Write Enable
Active low signal used to control the flow of
data to the transmit FIFOs.
When TENB is high, the TDAT[31:0],
TMOD, TSOP, TEOP, TPRTY and TERR
signals are invalid and are ignored by the
PM3386. However, the TSX signal if
asserted is valid and is processed by the
PM3386 only when TENB is high.
When TENB is low, the TDAT[31:0], TMOD,
TSOP, TEOP, TPRTY and TERR signals
are valid and are processed by the
PM3386. The TSX signal is ignored by the
PM3386 when TENB is low.
TENB is sampled on the rising edge of
TFCLK.
TPRTYInputAE6
POS-PHY Transmit bus parity
The transmit parity (TPRTY) signal
indicates the parity calculated over the
TDAT bus. TPRTY is considered valid only
when TENB or TSX are asserted.
By default the PM3386 uses odd parity.
The PM3386 supports both even and odd
parity. The PM3386 reports any parity error
to the host processor via a maskable
interrupt, but does not interfere with the
transferred data.
TPRTY is sampled on the rising edge of
TFCLK.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
TMOD[1:0] indicates the number of valid
bytes of data in TDAT[31:0]. The TMOD
bus should always be all zero, except
during the last double-word transfer of a
packet on TDAT[31:0]. When TEOP and
TENB are asserted, the number of valid
packet data bytes on TDAT[31:0] is
specified by TMOD[1:0].
TMOD[1:0] = “00”TDAT[31:0] valid
TMOD[1:0] = “01”TDAT[31:8] valid
TMOD[1:0] = “10”TDAT[31:16] valid
TMOD[1:0] = “11”TDAT[31:24] valid
TMOD [1:0] is sampled on the rising edge
of TFCLK.
POS-PHY Transmit Start of Transfer
Active high signal indicating when the inband port address is present on the
TDAT[31:0] bus. When TSX is high and
TENB is high (not asserted), the value of
contained within TDAT[7:0] is the address
of the transmit FIFO to be selected.
TDAT[7:0] == 0 selects channel zero.
TDAT[7:0] == 1 selects channel one.
Subsequent data transfers on the TDAT
bus will fill the FIFO specified by this inband address.
If TDAT[7:0] is not 0 or 1 no channel within
the PM3386 device will be selected.
Subsequent data transfers on the TDAT
bus to address outside of 0 or 1 will be
dropped at the PL3 interface.
TSX is considered valid only when TENB is
not asserted.
TSX is sampled on the rising edge of
TFCLK.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The TADR signal is used with the PTPA
signal to poll the transmit FIFOs packet
available status.
When TADR is sampled on the rising edge
of TFCLK by the PM3386, the polled
packet available indication PTPA signal is
updated with the status of the port specified
by the TADR address on the following rising
edge of TFCLK.
TADR = 0 = channel 0
TADR = 1 = channel 1
TADR is sampled on the rising edge of
TFCLK.
POS-PHY Polled-PHY Transmit Packet
Available
PTPA transitions high when a predefined
(user programmable) minimum number of
bytes are available in the polled transmit
FIFO. Once high, PTPA indicates that the
transmit FIFO is not full. When PTPA
transitions low, it indicates that the transmit
FIFO is full or near full (user
programmable).
PTPA allows the polling of the PM3386
channel selected by TADR address pin.
The port which PTPA reports is updated on
the following rising edge of TFCLK after the
PM3386 channel address on TADR is
sampled by the PM3386 device.
PTPA is updated on the rising edge of
TFCLK.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
STPA transitions high when a predefined
(user programmable) minimum number of
bytes are available in the transmit FIFO
specified by the in-band address on TDAT
bus. Once high, STPA indicates the
transmit FIFO is not full. When STPA
transitions low, it indicates that the transmit
FIFO is full or near full (user
programmable).
STPA always provides status indication for
the selected port of the PM3386 device in
order to avoid FIFO overflows while polling
is performed. The port which STPA reports
is updated on the following rising edge of
TFCLK after the PM3386 channel address
on TDAT is sampled by the PM3386
device.
STPA is updated on the rising edge of
TFCLK.
DTPA0
DTPA1
OutputAF3
AE4
POS-PHY Direct Transmit Packet
Available
Active high signals that provide direct
status indication for the corresponding
ports in the PM3386. DTPA[1:0] transitions
high when a predefined (user
programmable) minimum number of byes
are available in the transmit FIFO. Once
high, the DTPA[1:0] signals indicate that its
corresponding transmit FIFO is not full.
When DTPA[1:0] transitions low, it indicates
that its transmit FIFO is full or near full.
(user programmable).
DTPA0 corresponds to channel zero.
DTPA1 corresponds to channel one.
DTPA0 and DTPA1 are updated on the
rising edge of TFCLK.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
RFCLK is used to synchronize data
transfer transactions between the higher
layer device and the PM3386. RFCLK
cycles at a rate of 60 to 104 MHz.
POS-PHY Receive Data Valid
Active high signal indicating the validity of
the receive data signals. RVAL will
transition low when a receive FIFO is
empty, at the end of a data burst from a
given channel.
When RVAL is high, the RDAT[31:0],
RPRTY, RMOD[1:0], RSOP, REOP and
RERR signals are valid. When RVAL is
low, the RDAT[31:0], RPRTY, RMOD[1:0],
RSOP, REOP and RERR signals are
invalid and must be disregarded.
The RSX signal is only valid when RVAL is
low.
RVAL is updated on the rising edge of
RFCLK.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
Active low signal used to control the flow of
data from the PM3386.
The higher layer device may de-assert
RENB at anytime if it is unable to accept
data from the PM3386.
When RENB is sampled low by the
PM3386, the upper level device is signaling
that it can receive data.
RSX may then be asserted to indicate a
new address on the RDAT[0] bus pin or
RVAL may be asserted indicating validity of
read data and control on the RDAT[31:0],
RPRTY, RMOD[1:0], RSOP, REOP, and
RERR signals. Note that these signals will
be updated on the following rising edge of
the RFCLK.
When RENB is sampled high by the
PM3386, the upper level device is signaling
that it can no longer accept data.
On the following rising edge of RFCLK, if
active, the RVAL signal will remain
asserted signifying valid data and control
on RDAT[31:0], RPRTY, RMOD[1:0],
RSOP, REOP, and RERR.
RENB is sampled on the rising edge of
RFCLK.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The receive parity (RPRTY) signal
indicates the parity calculated over the
RDAT bus. RPRTY is only valid when
RVAL or RSX is asserted. The PM3386
supports both odd and even parity over the
RDAT bus.
RPRTY is updated on the rising edge of
RFCLK.
POS-PHY Receive Word Modulo
RMOD[1:0] indicates the number of valid
bytes of data in RDAT[31:0]. The RMOD
bus must always be zero, except during the
last double-word transfer of a packet on
RDAT[31:0]. When REOP and RVAL are
asserted, the number of valid packet data
bytes on RDAT[31:0] is specified by
RMOD[1:0].
RMOD[1:0] = “00”RDAT[31:0] valid
RSOPOutputY2
RMOD[1:0] = “01”RDAT[31:8] valid
RMOD[1:0] = “10”RDAT[31:16] valid
RMOD[1:0] = “11”RDAT[31:24] valid
RMOD[1:0] is considered valid only when
RVAL and REOP are asserted.
RMOD[1:0] is updated on the rising edge of
RFCLK.
POS-PHY Receive Start of Packet
Active high signal used to delineate the
packet boundaries on the RDAT bus.
When RSOP is high, the start of the packet
is present on the RDAT bus.
RSOP is required to be present at the start
of every packet and is only considered
valid when RVAL is asserted.
RSOP is updated on the rising edge of
RFCLK.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
Active high signal used to delineate the
packet boundaries on the RDAT bus.
When REOP is high, the end of the packet
is present on the RDAT bus.
Note that RMOD[1:0] indicates the number
of valid bytes the last double word is
composed of when REOP and RVAL are
asserted.
REOP is required to be present at the end
of every packet and is considered valid
only when RVAL is asserted.
REOP is updated on the rising edge of
RFCLK.
POS-PHY Receive error indicator
Active high signal used to indicate that the
current packet is aborted and should be
discarded. RERR shall only be asserted
when REOP and RVAL are asserted.
Conditions that can cause RERR to be set
may be, but are not limited to, FIFO
overflow, abort sequence detection and
FCS error.
RERR is updated on the rising edge of
RFCLK.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
RSX indicates when the in-band port
address is present on the RDAT bus.
When RSX is high and RVAL is low, the
value of RDAT[0] is the address of the
receive FIFO to be selected by the
PM3386. Subsequent data transfers on
the RDAT bus will be from the FIFO
specified by this in-band address.
RSX is considered valid only when RVAL is
not asserted.
RSX is considered valid only when RENB
was asserted on the previous cycle.
RSX is updated on the rising edge of
RFCLK.
Table 6- Side-band Flow Control
NameTypePin No.Description
PAUSE0
PAUSE1
Input
Internal
pull-down
AB1
Y4
PAUSE Control
Assertion of the PAUSE0 or PAUSE1
signals may cause (programmed option)
the PM3386 on a per channel basis to
transmit 802.3-1998 PAUSE frames and
either drop at the MAC layer or pass to the
POS-PHY L3 client any further incoming
frames (programmed option). De-assertion
of the PAUSE0 or PAUSE1 signal can
cause the removal of the PAUSE condition
on a per channel basis.
Due to the programmability options for
these pins please see the PAUSE flow
control section in the Operations section.
PAUSE0 and PAUSE1 are active high
signals.
PAUSE0 and PAUSE1 are sampled on the
rising edge of the RFCLK.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The PAUSED0 and PAUSED1 signals
indicate the reception and execution of
802.3-1998 PAUSE control frames on the
given port of the PM3386.
An asserted (high) PAUSED0 or PAUSED1
pin indicates that the corresponding
channels ingress PAUSE timer is non-zero.
This also typically indicates (if enabled via
the FCRX bit in the EGMAC GMACC1-Config Register) that the given channel is
in a paused state.
De-assertion of the PAUSED0 or
PAUSED1 pin indicates that the
corresponding channels PAUSE counter is
now zero. This also typically indicates that
the given channel is no longer pausing on
that channel. Please refer to the FCRX bit
definition for more information.
PAUSED0 and PAUSED1 are updated on
the rising edge of RFCLK.
Table 7 Microprocessor Interface
Pin NameTypePin No.Function
CSBInputA15
Active-low chip select
The CSB signal is low during PM3386
register accesses.
If CSB is not required (i.e., registers
accesses are controlled using the RDB and
WRB signals only), CSB must be
connected tied low.
RDBInputB15
Active-low read enable
The RDB signal is low during PM3386
register read accesses. The PM3386
drives the D[15:0] bus with the contents of
the addressed register while RDB and CSB
are low.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The WRB signal is low during a PM3386
register write accesses. The D[15:0] bus
contents are clocked into the addressed
register on the rising WRB edge while CSB
is low.
The bi-directional data bus
D[15:0] is used during PM3386 register
read and write accesses.
Address bus
A[10:0] selects specific registers during
PM3386 register accesses.
ALEInput
Internal
pull-up
A16
Address latch enable
ALE is active-high and latches the address
bus A[10:0] when low. When ALE is high,
the internal address latches are
transparent. It allows the PM3386 to
interface to a multiplexed address/data
bus. ALE has an integral pull-up resistor.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
INTB is set low when a PM3386 interrupt
source is active and that source is
unmasked. The PM3386 may be enabled
to report many alarms or events via
interrupts.
INTB is tri-stated when the interrupt is
acknowledged via an appropriate register
access. INTB is an open drain output.
Table 8- Device Miscellaneous
NameTypePin No.Description
RSTBSchmitt
input
Internal
pull-up
G3
Master Reset
This active low reset signal input provides
an asynchronous reset to the device.
RSTB is a Schmitt triggered input with an
internal pull-up resistor. When RSTB is
forced low, all device registers are forced to
their default states.
PMD_SEL0
PMD_SEL1
Input
Internal
pull-down
V24
F25
Physical Medium Select
These active high signals select between
using the on-board SERDES or external
transceiver via the GMII pins.
A low (tied to VSS) will select internal
SERDES.
A high (tied to VDDO) will select external
transceiver via the GMII pins.
These pins are required to be tied to VDDO
or VSS prior to device power up.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The JTAG test clock (TCK) signal provides
clock timing for test operations that are
carried out using the IEEE P1149.1 test
access port. TCK must be tied to VSS or
VDDO when not in JTAG test.
JTAG Test Mode Select
TMS controls the test operations that are
carried out using the IEEE P1149.1 test
access port. TMS is sampled on the rising
edge of TCK. TMS has an internal pull up
resistor.
JTAG test Input
TDI carries test data into the PM3386 via
the IEEE P1149.1 test access port. TDI is
sampled on the rising edge of TCK. TDI
has an internal pull-up resistor
JTAG Test Output
TDO carries test data out of the PM3386
via the IEEE P1149.1 test access port.
TDO is updated on the falling edge of TCK.
TDO is a tri-state output which is inactive
except when in the progress of shifting
boundary scan data out.
TRSTBSchmitt
Input
Internal
pull-up
C5
JTAG Test Reset
TRSTB provides an asynchronous reset for
testing via the IEEE P1149.1 test access
port. TRSTB is a Schmitt triggered input
with and internal put-up resistor.
Note that when not being used for JTAG
testing the TRSTB pin must be connected
to the RSTB input for proper normal mode
operation.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
1. All PM3386 inputs and bi-directional signals present minimum capacitive
loading and operate at TTL logic levels except the inputs marked as Analog
or PECL.
4. The PECL inputs and outputs should be terminated in a passive network and
interface at PECL levels as described in the Operations section.
5. It is mandatory that every ground pin (VSS) be connected to the printed
circuit board ground plane to ensure reliable device operation.
6. It is mandatory that every digital power pin (VDDI, VDDO, and VDDQ) be
connected to the printed circuit board power planes to ensure reliable device
operation.
7. All analog power pins can be sensitive to noise. They must be isolated from
the digital power. Care must be taken to correctly decouple these pins.
8. It is mandatory that every analog power pin (AVDL, AVDH, and AVDQ) be
de-coupled from but connected to the printed circuit board power planes to
ensure reliable device operation.
8. Due to ESD protection structures in the pads it is necessary to exercise
caution when powering a device up or down. ESD protection devices behave
as diodes between power supply pins and from I/O pins to power supply pins.
Under extreme conditions it is possible to damage these ESD protection
devices or trigger latch up. Please adhere to the recommended power supply
sequencing as described in the Operation section of this document.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The PM3386 provides a high density and low power solution for implementing
Gigabit Ethernet connectivity. The PM3386 is a dual Gigabit Ethernet controller
with integrated SERDES and GMAC functions connecting to a standard POSPHY Level 3 system interface. The PM3386 accepts serial bit streams from
optical transceiver devices or Gigabit Ethernet PHY devices and performs Media
Access Control frame verification. Statistics are maintained and the frame is
forwarded to internal FIFOs for the POS-PHY Level 3 interface. The PM3386
may be connected to an upper layer device via the POS-PHY Level 3 interface
for classification and forwarding.
The PM3386 is partitioned into the following major functional blocks. The
operation of each block is described in more detail in subsequent sections.
• SERDES
• Enhanced Gigabit Media Access Control
• Ethernet Statistics
• Address Filtering
• POS-PHY Level 3 System Interface
• Microprocessor Interface
10.1 Serializer-Deserializer (SERDES)
The PM3386 has two internal serializer-deserializer transceivers. The SERDES
is IEEE 802.3-1998 Gigabit Ethernet compatible supporting gigabit data transfer
flows. The SERDES is based on the X3T11 10 Bit specification. The PECL cells
used to implement the SERDES are capable of both 5V and 3.3V low voltage
PECL operation as they can be AC coupled within the system design.
The transmitter section of the SERDES accepts 10-bit wide parallel data and
serializes this data into a high-speed serial data stream. The parallel data is
8B/10B encoded data. An internally generated reference clock is then multiplied
to generate the 1250 MHz serial clock used to clock the encoded data out the
high-speed output at a rate of 1250 Mbit/s. The high-speed outputs are capable
of interfacing directly to a separate fiber optic module for optical transmission.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The receiver section accepts a serial electrical data stream at 1250 Mbit/s and
recovers the original 10-bit wide parallel data. The receiver Clock Recovery Unit
(CRU) locks onto the incoming serial signal and facilitates the recovery of the
high-speed serial data. The serial data is converted back into 10-bit parallel
data, recognizing the 8B/10B comma character to establish byte alignment. The
recovered parallel data is presented to the EGMAC.
10.2 Enhanced Gigabit Media Access Control (EGMAC)
10.2.1 EGMAC General
The PM3386 integrates standard IEEE 802.3-1998 Gigabit Ethernet Media
Access Control interfaces for connection to internal serializer-deserializers
(SERDES) or external transceivers using Gigabit Media Independent Interface
(GMII) pins on each gigabit Ethernet port. The dual ports of the PM3386 are
capable of operation in either SERDES or GMII mode. The ports can be
configured to operate independently from each other using the PMD_SEL0 and
PMD_SEL1 pins.
The EGMAC is capable of supporting normal Ethernet frame sizes of 1518
bytes, VLAN tagged frame sizes of 1522 bytes, and Jumbo frames sizes up to
9.6k bytes. The Transmit Max Frame Length and the Receive Max Frame
Length registers contain the values associate with maximum accepted Ethernet
frame sizes. By default these registers contain a value of 1518 bytes. This
allows for normal frame sizes as well as 1522 VLAN tagged frames to be
accepted. The EGMAC will base all frame length calculations and statistics off of
these registers. The EGMAC takes into account the VLAN tagging of frames to
ensure their proper representation in the statistics gathering process. Note that it
is possible to program the ingress and egress maximum frame sizes separately.
10.2.2 EGMAC Egress Direction
In the egress direction packet data from the PL3EP is presented to the EGMAC
synchronizing transmit FIFO. The EGMAC/PL3EP interface is a push style
interface. If packet data is available for transmit the PL3EP will push (transfer)
data to the EGMAC. The PL3EP will notify the EGMAC of the start and end of
packets by using simple end of packet and start of packet indications. The
PL3EP will also present to the EGMAC an error signal that is asserted when an
error condition is observed on the POS-PHY bus or if an internal error is
encountered in the egress data path.
The EGMAC has an upper bound of 9.6k bytes on the size of egress frames.
The egress direction of the EGMAC can accept packets of a minimum size of 14
bytes. Egress packets sent to the EGMAC that are of the minimum 14 bytes but
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
are less than the minimum 64 byte frame length required by 802.3-1998 have
the programmed option to be padded appropriately to 64 bytes (68 bytes for
VLAN tagged frames) and optionally have the associated 32 bit CRC appended
to the frame prior to transmit. The user may also elect to program the EGMAC to
insert the Frame Check Sequence (FCS) field.
In the case that the link device disregards the flow control information provided
by DTPA0, DTPA1, STPA, or PTPA and continues to write to the PM3386 in an
attempt to overflow the egress FIFO the PM3386 will truncate the current packet
when the FIFO becomes full. At this time the PM3386 will wait until a minimum
packet can be accepted and then resume data transfer.
In the event that the link device can not deliver the data fast enough to the
PM3386, placing the PM3386 in a case of FIFO underrun, the current packet will
be truncated sending all bytes currently available and then the PM3386 will resync to TSOP. In all error cases the CRC-32 that is kept over the packet will be
invalidated and appended to the frame as it is transmitted thereby signaling an
error.
Following each frame transmission the EGMAC provides a statistical vector to
the MSTAT block that updates statistic collection counters maintained in system
visible registers. Please refer to the MSTAT functional description and Register
section of this document for a full list of port statistics.
10.2.3 EGMAC Ingress Direction
In the ingress direction the SERDES or GMII presents receive physical packet to
the EGMAC. The EGMAC scans the preamble looking for the Start Frame
Delimiter (SFD). By default the preamble and SFD are stripped converting the
physical packet to a frame. The EGMAC will then compare the destination
address in the frame to the address filtering logic for the given port. If enabled
the address filtering logic may be programmed to accept or reject incoming
frames. The EGMAC is also programmable to accept all frames regardless of
validity.
The EGMAC supports ingress frame sizes of up to 9.6k bytes. The EGMAC
interfaces to the PL3IP using a simple push style interface. The EGMAC signals
start of frame and end of frame while transferring data information to the PL3IP.
There are two decision points at which the frame forwarding and filtering
decisions are made. The first decision point is at the beginning of the ingress
frame. At this point and once the SA, DA, and the possible VID fields are
recognized the frame may be filtered based on the address filter logic described
later. If the frame is to be forwarded the incoming data will be written to the
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
EGMAC ingress FIFO in preparation for frame transfer. If the frame is to be
filtered the frame will not be written to the EGMAC FIFO and the EGMAC will resync to the next incoming ingress frame.
The second decision point is at the end of the frame. The EGMAC will perform
frame integrity checks such as length and CRC. If the frame violates these
integrity checks the frame will need to be discarded. Discarding a frame can be
done in two possible ways. The cases are described below.
1. If the number of bytes that have been written to the EGMAC ingress
FIFO are less than the programmed value within the EGMAC ReceiveFIFO Forwarding Threshold register, the frame in its entirety is stored
within the FIFO, and will therefore be dropped within the EGMAC. The
EGMAC will flush this frame from the FIFO and resume reception of
ingress traffic on the next start of frame indication.
2. If the number of bytes that have been written to the EGMAC ingress
FIFO are greater than the programmed value within the EGMAC ReceiveFIFO Forwarding Threshold register the frame will have started draining
from the FIFO and therefore can not be dropped within the PM3386. In
this case the frame will be marked as bad by assertion of the RX_ERR bit
on the EGMAC PL3IP interface. This indication is carried to the POSPHY Level 3 interface and will cause the assertion of the RERR bit on the
last byte transfer of the packet.
As mentioned above ingress frames are held in the receive FIFO within the
EGMAC until the byte count exceeds the forwarding threshold programmed in
the EGMAC Receive FIFO Forwarding Threshold register or until End Of
Frame (EOF). Frames that contain errors and are greater than the programmed
value within the EGMAC Receive FIFO Forwarding Threshold register will be
marked as erred by the PM3386 but will not be discarded within the PM3386.
The EGMAC will distinguish between unicast, broadcast, and multicast frames.
The EGMAC can be programmed to forwarded or filter frames based on unicast,
broadcast, or multicast type frames.
10.2.4 EGMAC Flow Control - MAC Control Sublayer
The PM3386 provides loss-less frame flow control for frame sizes up to 9.6k
bytes over 1000BASE TX, 1000BASE SX, and 1000BASE LX implementations.
The EGMAC interface contains the MAC Control Sublayer which adheres to
IEEE 802.3-1998 and provides support for Control frames. The EGMAC
performs the functions out lined in IEEE 802.3-1998 Clause 31 “MAC Control”
and Annexes 31A and 31B. Clause 31 introduces the optional MAC Control
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
sublayer to the popular layer stack. This sublayer provides for real-time control
and manipulation of the MAC operation. The clause defines MAC control frames
distinguishable by their unique Length/Type field identifier.
The EGMAC supports Annex 31A opcode PAUSE by implementing Annex31B’s
frame based flow control scheme which utilizes PAUSE Control frames. The
purpose of flow control is to slow down the aggregate rate of frames that the
other end of a link is sending. Finite FIFO depths have a tendency to overflow
when line-rate frames are being received and the upper layer device cannot
keep up. Thus to prevent the overflow of the FIFOs, flow control is used. A MAC
Control client wishing to inhibit transmission of data frames from the PM3386
generates a PAUSE Control frame which contains the reserved multicast
address (01-80-C2-00-00-01), the Control frame type field 88-08, the PAUSE
opcode, 00-01, and the pauseTimer, a 16-bit value expressed in pause quanta of
512 bit times. When the EGMAC receives a PAUSE Control frame, it loads the
Pause Timer with the value sent in the pauseTime filed. If pauseTime is nonzero and the FCRX bit within the EGMAC GMACC1-Config Register is
asserted, the EGMAC will pause from transmitting frames and will wait for
pauseTime number of slot times before resuming operation. If, however, the
pauseTime value is equal to zero, the EGMAC is allowed to resume transmitting
data frames. At any time if the EGMAC is receiving PAUSE control frames the
EGMAC will assert the PAUSED0 or PAUSED1 status pins. These pins will be
held asserted until the EGMAC pauseTime counts down to zero and the EGMAC
resumes transmitting data frames. It is possible depending on the system
requirements to allow ingress PAUSE Control frames to be processed or not
processed at the EGMAC layer (see FCRX bit) and PAUSE Control frames to be
dropped at the EGMAC layer or passed to the upper layer device(see
PASS_CTRL bit).
If for any reason the upstream device needs to stop incoming frames, it can
accomplish this by four different ways. First, the upper layer device can send
802.3-1998 PAUSE Control frames of its own. Second, the upper layer device
can assert the PAUSE0 or PAUSE1 pins on the device to have the EGMAC
automatically send PAUSE Control frames. Third, the system processor can
initiate PAUSE operation via configuration registers in the EGMAC. Fourth, the
link device can de-assert RENB and cause the FIFO fill levels in the PL3IP block
to fill and start automatic flow control. Note that even though the EGMAC can be
sending egress PAUSE Control frames the ingress channel will still be
operational with the exception of normal blocking of the POS-PHY L3 data-path
from the link level. Please refer to the Operations section under PAUSE Flow
Control for programming options.
At the end of a PAUSE operation the PM3386 will send a PAUSE frame with a
null Pause Timer value allowing quick PAUSE off signaling to downstream
devices.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The EGMAC implements Clause 37 of the IEEE 802.3-1998 Standard, AutoNegotiation function, type 1000BASE-X. The Auto-Negotiation for 1000BASE-X
function provides the means to exchange information between two devices that
share a link segment allowing management the ability to configure both devices
in such a way that takes maximum advantage of their capabilities. After a reset
occurs the EGMAC senses whether or not Auto-Negotiation is enabled. If so the
EGMAC will start Auto-Negotiation exactly following the state diagram as outlined
in 802.3-1998 Clause 37. Base page Auto-Negotiation is therefore completely
taken care of by the EGMAC.
Above base page Auto-Negotiation, the EGMAC communicates between the
host processor and an external MII physical device by means of a two wire
interface. The EGMAC block produces the clock (MDC) and the general MII I/O
pin MDIO. The host controls the EGMAC MII via the MII management registers.
10.2.6 EGMAC Address Filter Logic
The EGMAC provides a rich set of address filtering options. The host
microprocessor has complete programmable access to all filtering features.
The EGMAC can perform 8 separate exact-match MAC/VID unicast filter
operations. Each unicast filter will perform an exact match on either the DA or
the SA, and an optional exact match on the VID. If enabled, each unicast filter
channel can be programmed to indicate ACCEPT or DISCARD upon match.
Each unicast filter channel can be enabled separately.
The EGMAC also includes a 64-bin hash-based multicast filter. This hash-based
filter utilizes 6-bits of the CRC-32 output taken over the MAC DA to provide the
standard imperfect multicast filtering capability. The multicast filter output will be
asserted only if the IEEE Group/Functional bit is set in the DA of the frame (Most
significant bit of the least significant byte of the MAC DA). If enabled, the filter
output will indicate ACCEPT only. If not enabled, it will indicate nothing.
10.3 Management Statistics (MSTAT)
The MSTAT block is used to accumulate Ethernet specific counts used for
supporting management agents such RMON, SNMP, and Etherlike interfaces.
The MSTAT provides counter width support for compliance with 802.3-1998
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
rollover requirements of 58 minutes. The MSTAT supports full system probing
with counter snapshotting via shadow registers. Incorporated into the MSTAT
block is a fully programmable interrupt array enabling per counter rollover
monitoring with interrupt reporting.
10.4 POS-PHY Level 3 Physical Layer Interface
10.4.1 POS-PHY Level 3 General
The PM3386 can connect to a single upper level device through a POS-PHY
Level 3 Interface. The POS-PHY Level 3 interface is a 32-bits wide interface
with a clock rate of 104 MHz. POS-PHY Level 3 was developed with the
cooperation of the SATURN Development Group to cover all application bit rates
up to and including 3.2 Gbit/s. The POS-PHY Level 3 specification defines the
requirements for interoperation between devices such as the multi-PHY PM3386
and a single Link Layer device. Each channel within the PM3386 contains a 64k
byte ingress and 16k byte egress POS-PHY latency FIFO.
As a POS-PHY slave device, hence in the ingress or receive direction, the
PM3386 outputs received packets to the upper layer device whenever data is
available. The interface accepts a read clock (RFCLK) and read enable signal
(RENB) when data is read from the ingress FIFO (using the rising edge of the
RFCLK). The start of packet (RSOP) marks the first byte of received packet data
on the RDAT[31:0] bus. The RPRTY signal reports parity on the RDAT[31:0]
bus. Parity defaults to odd but may be programmed for even parity. The end of
a packet is indicated by the REOP signal. The RERR signal is provided to
indicate that an error in a received packet has occurred. The RVAL signal is
used to indicate when RSOP, REOP, RERR, and RDAT[31:0] are valid. RSX
indicates the start of transfer and marks the clock cycle where the in-band
channel address is given on the RDAT[31:0] bus.
In the event that the upper level device cannot accept data it can de-assert
RENB. At this point the specific port’s POS-PHY interface ingress 64k byte FIFO
will start to fill up. When the FIFO exceeds the programmed high water mark
flow control threshold the ingress FIFO will assert an indication to the EGMAC to
start PAUSE flow control. The ingress POS-PHY FIFO will continue to keep the
flow control signal high until the number of entries in the FIFO have decreased to
the programmed low water mark flow control threshold level.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
In the event that the link layer device does not re-assert RENB to continue the
data flow the PM3386 will buffer the incoming frames from the line side interface
until all the buffer facilities within the PM3386 are exhausted. At this time the
PM3386 will no longer accept data from the line side. All data bits will be
dropped at the line interface until resources within the PM3386 become
available. At this time the PM3386 will re-sync to physical packet and continue
reception. In the event that the PM3386 truncates a frame because of resource
exhaustion the frame will be marked as erred by asserting the RERR bit on the
last interface transaction for the packet transfer as specified by the PL3 bus
protocol.
The POS-PHY ingress FIFO will absorb in-flight frames when the PM3386 is
placed into a PAUSE flow control state from the upper level device. The FIFO
will accept a number of maximum size 9.6k byte frames without loss.
The scheduling of packets through the ingress POS-PHY interface is controlled
via a simple round robin approach that fairly switches between both Gigabit
Ethernet channels. The POS-PHY bursts packets across the interface using
programmable burst sizes.
The POS-PHY Level 3 compliant interface consists of a write clock (TFCLK), a
write enable signal (TENB), the start of packet (TSOP) indication, the end of
packet (TEOP) indication, erred packet (TERR) indication, and the parity bit
(TPRTY).
The PM3386 supports all three POS-PHY Level 3 egress status modes. The
STPA signal reports the selected egress FIFO’s fill status. The PTPA signal
shows the FIFO fill status for the polled channel. The DTPA[1:0] signal pins
show the direct FIFO fill status on a per-channel basis. The TSX signal indicates
when the in-band channel selection is given on the TDAT[7:0] pins. This is done
at the beginning of each transfer sequence. If the in-band address does not
equal 0 or 1 subsequent data transfers on the TENB bus will be dropped.
The TMOD[1:0] signal is provided to indicate whether 1, 2, 3, or 4 bytes are valid
on the final word transfer of the packet(TEOP is asserted). A packet may be
aborted by asserting the TERR signal at the end of the packet.
In the egress direction the PM3386 collects packets into the PM3386 egress
FIFO and delays data transfer to the PM3386 EGMAC for transmission until the
number of bytes gathered are equal to or greater than the PL3EP ChannelMinimum Frame Size register or until end of packet (via TEOP) is signaled.
Each packet must satisfy one of the two forwarding conditions prior to
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
transmission. This allows for programmable MAC underrun protection
depending upon the application.
10.5 Microprocessor Interface
The PM3386 uses a simple 16 bit multiplexed or non-multiplexed microprocessor
interface that is commonly found on PMC-Sierra devices.
The PM3386 supports complete accessibility to internal resources from the host
microprocessor. This allows the host to read and write all host accessible
registers and chip data structures.
10.6 JTAG Test Access Port Interface
The JTAG Test Access Port block provides JTAG support for boundary scan.
The standard JTAG EXTEST, SAMPLE, BYPASS, IDCODE and STCTEST
instructions are supported. The PM3386 identification code is 033860CD
hexadecimal.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The Reset Control Register generates the reset source output used by blocks in
the PM3386.
DRESETB:
Master digital device reset. Performing a hardware reset will clear this bit to a
1. Setting this bit to a 0 will cause the digital portion of the device to reset. It
is the responsibility of the programmer to de-assert or set this bit to a one in
order to perform a proper software reset sequence. Please refer to the
operations section of this document for instructions concerning resetting this
device using software.
ARESETB:
Master analog device reset. Performing a hardware reset will clear this bit to
a 1. Setting this bit to a 0 will cause the analog portion of the device to reset.
It is the responsibility of the programmer to de-assert or set this bit to a one in
order to perform a proper software reset sequence. Please refer to the
operations section of this document for instructions concerning resetting this
device using software.
DIS_STRETCH:
By default the internal digital reset is held asserted approximately 10ms after
the de-assertion of the RSTB pin. To disable this delay the DIS_STRETCH
bit can be set to logic 1. This will terminate the internal digital reset delay. By
default this bit is disabled. Please refer to the operations section for further
information.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
This bit allows for software reset of the PL3IP logic. By default this pin is not
asserted or logic 1. To reset the PL3IP the programmer must set this bit to
logic 0, wait for a minimum of 100 ns (there is no maximum), and then set
this bit back to logic 1.
RESET_PL3EP:
This bit allows for software reset of the PL3EP logic. By default this pin is not
asserted or logic 1. To reset the PL3EP the programmer must set this bit to
logic 0, wait for a minimum of 100 ns (there is no maximum), and then set
this bit back to logic 1.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
Interrupt indication bits. Theses bits indicate that the given interrupt is
currently active. In general this is a global interrupt status indication. Simply
reading this register does not clear the interrupt. Each interrupt source may
have its own requirements for clearing the interrupt condition. Further
specification on each interrupt bit can be found in the Operation section of
this document. A logical NOR of all the X_INT signals produces the active
low INTB signal used to notify the external processor of an interrupt condition.
The following table provides the block source interrupt and mask registers
that make up the top level interrupt bits as listed above.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The Software Resource register does not control any internal function within
the PM3386. This register is not reset. This register is read/writeable for use
by software.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The PL3IP Interrupt Status register is used to capture error status bits from both
channels. This register is used in conjunction with the PL3IP Interrupt Mask
register. This register is read only to the user. A read of this register will clear
the register and the interrupt.
IP_IS[5] – Channel 0 Software Programmed Fault
The software programmed fault occurs when the user programs the PL3IP
Channel Low Watermark Register 0x121 to a larger value than the PL3IP
Channel High Watermark Register 0x120.
IP_IS[7] – Channel 0 Equalization Indication
Indicates that at some time during the operation of the PL3IP that the
equalization for this channel was activated.
IP_IS[13] – Channel 1 Software Programmed Fault
A software programmed fault occurs when the user programs the PL3IP
Channel Low Watermark Register 0x141 to a larger value then the PL3IP
Channel High Watermark Register 0x140.
IP_IS[15] – Channel 1 Equalization Indication
Indicates that at some time during the operation of the PL3IP that the
equalization for this channel was activated.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The PL3IP Interrupt Mask register is used to mask out errors when determining
when to send an interrupt. A bit set in any location will enable the corresponding
interrupt notification by unmasking the possible pending interrupt. This is a user
programmable register.
The PL3IP Configuration Register controls the enabling and disabling of features
for the PL3IP. Writing a 1 to a non-reserved bit location will cause the feature to
be enabled.
IP_CR[0] - Channel 0 Protocol Check Enable
This bit turns on the protocol checking feature and does not allow corrupted
packets to be written into the FIFO. Disabling this feature may be useful for
system diagnostics. High is on. Low is off.
IP_CR[1] - Channel 1 Protocol Check Enable
This bit turns on the protocol checking feature and does not allow corrupted
packets to be written into the FIFO. Disabling this feature may be useful for
system diagnostics. High is on. Low is off.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
Enable equalized transfer mode. When enabled, the threshold register and
the limit register will be used to evaluate the state of both channels.
IP_CR[3] - Parity Odd or Even Generation
Parity Generation mode for the PL3IP. The default is odd mode parity
generation (0). If set high (1), even mode parity generation will be used. Once
set, the same mode is used on both channels.
IP_CR[5:4] - RFCLK Transfer Gap Selection
Bits [5:4] are used to set the transfer gap selection for the POS-PHY L3
interface. The rate is programmable from 0 to 3 RFCLK cycles. This will allow
the user to program the latency between selection of new channel and
transmitting of a new packet.
Table 11-14: Transfer Gap Rate
IP_CR[5:4]Gap Transfer Rate
00(Default)0 RFCLKs
011 RFCLKs
102 RFCLKs
113 RFCLKs
IP_CR[6] – Pause Mode Selection
Pause Mode Selection controls how the PAUSE0 and PAUSE1 pins are
used.
If Pause Mode Selection is low (default) the PAUSE0 and PAUSE1 inputs
control the PAUSE frame generation for their respective channels. Setting
PAUSE0 or PAUSE1 to high will cause the PM3386 to start sending pause
frames on their corresponding channels as described in the Operations
section. Setting PAUSE0 or PAUSE1 low, and the PM3386 was previously
sending PAUSE frames, the PM3386 will send an xoff PAUSE frame on that
channel.
If Pause Mode Selection is high the PAUSE0 and PAUSE1 pins are masked
from directly effecting the PAUSE frame generation. In this case when the
user asserts the PAUSE0 or PAUSE1 pins the respective channel will finish
sending on the PL3 bus the remaining number of bytes in the programmed
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
minimum burst size or until EOP is detected and then hold off sending data
on the channel until the PAUSE0 or PAUSE1 pins are de-asserted. Upon deassertion, if available, data will continue to be transferred across the PL3
interface for that channel. Please refer to the Operation section for more
detail on this feature.
IP_CR[7] – Channel Enable
Channel Enable is used to update configuration values into the PL3IP when
required due to configuration change. The differing PL3IP configuration
registers (0x104, 0x105, 0x120, 0x121, 0x122, 0x140, 0x141, 0x142) may be
written to at any time but will only update when this bit is cleared. The user
programs the PL3IP configuration registers and then writes a zero to this bit
to update the registers within the PL3IP. This bit will automatically return to
one when the update is complete..
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The PL3IP Equalization Threshold Limit is used when the equalized transfer
mode is enabled. This register can be written at any time but is only updated
internally by using the PL3IP Configuration register.
IP_ETL[2:0]
PL3IP Threshold Limit Register is used to set the upper limit in bytes for
equalization support. Please refer to the Operations section for more
information on equalization. Table 15 provides the programmable options.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
The PL3IP Equalization Difference Limit Register is used when the equalized
transfer mode is enabled. This register can be written at any time but is only
updated by using the PL3IP Configuration register.
IP_EDL[2:0]
PL3IP Equalization Difference Limit is used to set the maximum difference in
bytes between the two channels FIFOs. Default is 32768 bytes, or the 1/2
FIFO storage space. The lower limit supported by the hardware is 512 bytes.
Please refer to the Operations section for more information on equalization.
Table 16 provides the accepted programmable options.
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
93
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.