DP83865
DP83865 Gig PHYTER V 10/100/1000 Ethernet Physical Layer
Literature Number: SNLS165B
DP83865 Gig PHYTER® V
10/100/1000 Ethernet Physical Layer
General Description
The DP83865 is a fully featured Physical Layer transceiver
with integrated PMD sublayers to support 10BASE-T,
100BASE-TX and 1000BASE-T Ethernet protocols.
The DP83865 is an ultra low power version of the DP83861
and DP83891. It uses advanced 0.18 um, 1.8 V CMOS
technology, fabricated at National Semiconductor’s South
Portland, Maine facility.
The DP83865 is designed for easy implementation of
10/100/1000 Mb/s Ethernet LANs. It interfaces directly to
Twisted Pair media via an external transformer. This device
interfaces directly to the MAC layer through the IEEE
802.3u Standard Media Independent Interface (MII), the
IEEE 802.3z Gigabit Media Independent Interface (GMII),
or Reduced GMII (RGMII).
The DP83865 is a fourth generation Gigabit PHY with field
proven architecture and performance. Its robust performance ensures drop-in replacement of existing
10/100 Mbps equipment with ten to one hundred times the
performance using the existing networking infrastructure.
■ Integrated PMD sublayer featuring adaptive equalization
and baseline wander compensation according to ANSI
X3.T12
■ 3.3 V or 2.5 V MAC interfaces:
■ IEEE 802.3u MII
■ IEEE 802.3z GMII
■ RGMII version 1.3
■ User programmable GMII pin ordering
■ IEEE 802.3u Auto-Negotiation and Parallel Detection
■ Fully Auto-Negotiates between 1000 Mb/s, 100 Mb/s,
and 10 Mb/s full duplex and half duplex devices
■ Speed Fallback mode to achieve quality link
■ Cable length estimator
■ LED support for activity, full / half duplex, link1000,
Applications
link100 and link10, user programmable (manual on/off),
or reduced LED mode
The DP83865 fits applications in:
■ 10/100/1000 Mb/s capable node cards
■ Supports 25 MHz operation with crystal or oscillator.
■ Switches with 10/100/1000 Mb/s capable ports
■ Requires only two power supplies, 1.8 V (core and
analog) and 2.5 V (analog and I/O). 3.3V is supported
as an alternative supply for I/O voltage
■ High speed uplink ports (backbone)
Features
■ User programable interrupt
■ Ultra low power consumption typically 1.1 watt
■ Supports Auto-MDIX at 10, 100 and 1000 Mb/s
■ Fully compliant with IEEE 802.3 10BASE-T, 100BASE-
TX and 1000BASE-T specifications
■ Supports JTAG (IEEE1149.1)
■ 128-pin PQFP package (14mm x 20mm)
SYSTEM DIAGRAM
DP83865
10/100/1000 Mb/s
ETHERNET MAC
10/100/1000 Mb/s
ETHERNET PHYSICAL LAYER
25 MHz
crystal or oscillator
10BASE-T
100BASE-TX
1000BASE-T
RJ-45
DP83820
MAGNETICS
MII
GMII
RGMII
STATUS
LEDs
PHYTER® is a registered trademark of National Semiconductor Corporation
© 2004 National Semiconductor Corporation
www.national.com
DP83865 Gig PHYTER® V 10/100/1000 Ethernet Physical Layer
October 2004
COMBINED MII / GMII / RGMII INTERFACE
GTX_CLK
TX_ER
TX_EN
TXD[7:0]
TX_CLK
RX_CLK
COL
CRS
RX_ER
RX_DV
RXD[7:0]
MGMT INTERFACE
MDIO
MDC
Interrupt
DP83865
Block Diagram
µC MGMT
& PHY CNTRL
MUX/DMUX
MII
10BASE-T
Block
100BASE-TX
Block
MII
MII
100BASE-TX
PCS
10BASE-T
PLS
100BASE-TX
PMA
10BASE-T
PMA
100BASE-TX
PMD
GMII
1000BASE-T
Block
GMII
1000BASE-T
PCS
Echo cancellation
Crosstalk cancellation
ADC
Decode/Descramble
Equalization
Timing
Skew compensation
BLW
1000BASE-T
PMA
Manchester
10 Mb/s
PAM-5
17 Level PR Shaped
125 Msymbols/s
MLT-3
100 Mb/s
DAC/ADC
SUBSYSTEM
TIMING
DRIVERS/
RECEIVERS
DAC/ADC
TIMING BLOCK
MAGNETICS
4-pair CAT-5 Cable
www.national.com
2
Table of Contents
1.0
2.0
3.0
4.0
5.0
Pin Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1
MAC Interfaces (MII, GMII, and RGMII) . . . . . . . 5
1.2
Management Interface
. . . . . . . . . . . . . . . . . . . .7
1.3
Media Dependent Interface
. . . . . . . . . . . . . . . .7
1.4
JTAG Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.5
Clock Interface
. . . . . . . . . . . . . . . . . . . . . . . . . .8
1.6
Device Configuration and LED Interface . . . . . . . . 8
1.7
Reset
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.8
Power and Ground Pins . . . . . . . . . . . . . . . . . . . . 11
1.9
Special Connect Pins . . . . . . . . . . . . . . . . . . . . 11
1.10 Pin Assignments in the Pin Number Order . . . . 12
Register Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.1
Register Definitions . . . . . . . . . . . . . . . . . . . . . . . 18
2.2
Register Map
. . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.3
Register Description . . . . . . . . . . . . . . . . . . . . . . 21
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.1
Accessing Expanded Memory Space . . . . . . . . . 40
3.2
Manual Configuration . . . . . . . . . . . . . . . . . . . . . . 40
3.3
Auto-Negotiation . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.4
Auto-Negotiation Register Set . . . . . . . . . . . . . . . 44
3.5
Auto-MDIX resolution . . . . . . . . . . . . . . . . . . . . . . 44
3.6
Polarity Correction . . . . . . . . . . . . . . . . . . . . . . . . 45
3.7
PHY Address, Strapping Options and LEDs . . . . 45
3.8
Reduced LED Mode . . . . . . . . . . . . . . . . . . . . . . 45
3.9
Modulate LED on Error . . . . . . . . . . . . . . . . . . . . 45
3.10 MAC Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.11 Clock to MAC Enable . . . . . . . . . . . . . . . . . . . . . . 46
3.12 MII/GMII/RGMII Isolate Mode . . . . . . . . . . . . . . . 46
3.13 Loopback Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.14 IEEE 802.3ab Test Modes . . . . . . . . . . . . . . . . . . 46
3.15 Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.16 Low Power Mode / WOL . . . . . . . . . . . . . . . . . . . 47
3.17 Power Down Mode . . . . . . . . . . . . . . . . . . . . . . . 47
3.18 BIST Configuration . . . . . . . . . . . . . . . . . . . . . . . 47
3.19 Cable Length Indicator . . . . . . . . . . . . . . . . . . . . . 48
3.20 10BASE-T Half Duplex Loopback . . . . . . . . . . . . 48
3.21 I/O Voltage Selection . . . . . . . . . . . . . . . . . . . . . . 48
3.22 Non-compliant inter-operability mode . . . . . . . . . 48
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.1
1000BASE-T PCS Transmitter . . . . . . . . . . . . . . 49
4.2
1000BASE-T PMA Transmitter . . . . . . . . . . . . . . 50
4.3
1000BASE-T PMA Receiver . . . . . . . . . . . . . . . . 50
4.4
1000BASE-T PCS Receiver . . . . . . . . . . . . . . . . 51
4.5
Gigabit MII (GMII) . . . . . . . . . . . . . . . . . . . . . . . . 52
4.6
Reduced GMII (RGMII) . . . . . . . . . . . . . . . . . . . . 53
4.7
10BASE-T and 100BASE-TX Transmitter . . . . . . 54
4.8
10BASE-T and 100BASE-TX Receiver . . . . . . . . 57
4.9
Media Independent Interface (MII) . . . . . . . . . . . . 60
Design Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.1
Hardware Reset . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.2
Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.3
Power Supply Decoupling . . . . . . . . . . . . . . . . . . 64
5.4
Sensitive Supply Pins . . . . . . . . . . . . . . . . . . . . . 64
5.5
PCB Layer Stacking . . . . . . . . . . . . . . . . . . . . . . . 64
5.6
Layout Notes on MAC Interface . . . . . . . . . . . . . . 66
5.7
Twisted Pair Interface . . . . . . . . . . . . . . . . . . . . . 66
5.8
RJ-45 Connections . . . . . . . . . . . . . . . . . . . . . . . 67
5.9
LED/Strapping Option . . . . . . . . . . . . . . . . . . . . . 67
5.10 Unused Pins and Reserved Pins . . . . . . . . . . . . . 67
5.11 I/O Voltage Considerations . . . . . . . . . . . . . . . . . 68
5.12 Power-up Recommendations . . . . . . . . . . . . . . . 68
5.13 Component Selection . . . . . . . . . . . . . . . . . . . . . 68
6.0
7.0
8.0
3
Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . . 71
6.1
DC Electrical Specification . . . . . . . . . . . . . . . . . 71
6.2
Reset Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.3
Clock Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6.4
1000 Mb/s Timing . . . . . . . . . . . . . . . . . . . . . . . . 74
6.5
RGMII Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.6
100 Mb/s Timing . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.7
10 Mb/s Timing . . . . . . . . . . . . . . . . . . . . . . . . . . 78
6.8
Loopback Timing . . . . . . . . . . . . . . . . . . . . . . . . 79
6.9
Serial Management Interface Timing . . . . . . . . . 80
6.10 Power Consumption . . . . . . . . . . . . . . . . . . . . . . 81
Frequently Asked Questions . . . . . . . . . . . . . . . . . . . 82
7.1
Do I need to access any MDIO register to start up
the PHY? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
7.2
I am trying to access the registers through MDIO
and I got invalid data. What should I do? . . . . . 82
7.3
Why can the PHY establish a valid link but can
not transmit or receive data? . . . . . . . . . . . . . . . 82
7.4
What is the difference between TX_CLK,
TX_TCLK, and GTX_CLK? . . . . . . . . . . . . . . . . 82
7.5
What happens to the TX_CLK during 1000 Mbps
operation? Similarly what happens to RXD[4:7]
during 10/100 Mbps operation? . . . . . . . . . . . . . 82
7.6
What happens to the TX_CLK and RX_CLK
during Auto-Negotiation and during idles? . . . . . 82
7.7
Why doesn’t the Gig PHYTER V complete AutoNegotiation if the link partner is a forced
1000 Mbps PHY? . . . . . . . . . . . . . . . . . . . . . . . . 82
7.8
What determines Master/Slave mode when AutoNegotiation is disabled in 1000Base-T mode? . . 82
7.9
How long does Auto-Negotiation take? . . . . . . . 83
7.10 How do I measure FLP’s? . . . . . . . . . . . . . . . . . 83
7.11 I have forced 10 Mbps or 100 Mbps operation but
the associated speed LED doesn’t come on. . . . 83
7.12 I know I have good link, but register 0x01, bit 2
“Link Status” doesn’t contain value ‘1’ indicating
good link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
7.13 Your reference design shows pull-up or pull-down
resistors attached to certain pins, which conflict
with the pull-up or pull-down information specified
in the datasheet? . . . . . . . . . . . . . . . . . . . . . . . . 83
7.14 How is the maximum package case temperature
calculated? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
7.15 The DP83865 will establish Link in 100 Mbps
mode with a Broadcom part, but it will not
establish link in 1000 Mbps mode. When this
happens the DP83865’s Link LED will blink on
and off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
7.16 How do I quickly determine the quality of the
link over the cable ? . . . . . . . . . . . . . . . . . . . . . . 83
7.17 What is the power up sequence for DP83865? . 83
7.18 What are some other applicable documents? . . 84
Physical Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . 86
www.national.com
DP83865
PQFP Pin Layout
VSS
MDID_N
MDID_P
VSS
VSS
1V8_AVDD1
VSS
MDIC_N
MDIC_P
VSS
VSS
1V8_AVDD1
VSS
MDIB_N
MDIB_P
VSS
VSS
1V8_AVDD1
VSS
MDIA_N
MDIA_P
VSS
VSS
1V8_AVDD1
VSS
1V8_AVDD1
128
127
126
125
124
123
122
121
120
119
118
117
116
115
114
113
112
111
110
109
108
107
106
105
104
103
NON_IEEE_STRAP
1
102
BG_REF
RESERVED
2
101
2V5_AVDD1
INTERRUPT
3
100
1V8_AVDD3
IO_VDD
4
99
VSS
VSS
5
98
1V8_AVDD2
TX_TCLK / MAN_MDIX_STRAP
6
97
VSS
ACTIVITY_LED / SPEED0_STRAP
7
96
2V5_AVDD2
LINK10_LED / RLED/SPEED1_STRAP
8
95
PHYADDR4_STRAP
LINK100_LED / DUPLEX_STRAP
9
94
MULTI_EN_STRAP / TX_TRIGGER
LINK1000_LED / AN_EN_STRAP
10
93
VSS
CORE_VDD
11
92
CORE_VDD
VSS
12
91
VSS
DUPLEX_LED / PHYADDR0_STRAP
13
90
IO_VDD
PHYADDR1_STRAP
14
89
MDIX_EN_STRAP
IO_VDD
15
88
MAC_CLK_EN_STRAP
VSS
16
87
CLK_OUT
PHYADDR2_STRAP
17
86
CLK_IN
PHYADDR3_STRAP
18
85
CLK_TO_MAC
CORE_VDD
19
84
RESERVED
VSS
20
83
IO_VDD
IO_VDD
21
82
VSS
VSS
22
81
MDC
RESERVED
23
80
MDIO
TCK
24
79
GTX_CLK/TCK
CORE_VDD
25
78
VSS
VSS
26
77
IO_VDD
TMS
27
76
TXD0/TX0
TDO
28
75
TXD1/TX1
IO_VDD
29
74
VSS
VSS
30
73
CORE_VDD
TDI
31
72
TXD2/TX2
TRST
32
71
TXD3/TX3
RESET
33
70
VSS
VDD_SEL_STRAP
34
69
IO_VDD
CORE_VDD
35
68
TXD4
VSS
36
67
TXD5
IO_VDD
37
66
TXD6
VSS
38
65
TXD7
DP83865DVH
Gig PHYTER V
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
COL/CLK_MAC_FREQ
CRS/RGMII_SEL0
RX_ER/RXDV_ER
IO_VDD
VSS
RX_DV/RCK
RXD7
RXD6
RXD5
CORE_VDD
VSS
RXD4
RXD3/RX3
RXD2/RX2
IO_VDD
VSS
RXD1/RX1
RXD0/RX0
RX_CLK
IO_VDD
VSS
TX_CLK/RGMII_SEL1
TX_ER
TX_EN/TXEN_ER
CORE_VDD
VSS
Figure 1. DP83865 Pinout
Order Part Number: DP83865DVH
www.national.com
4
DP83865
1.0 Pin Description
The DP83865 pins are classified into the following interface
categories (each is described in the sections that follow):
—
—
—
—
—
—
—
—
—
MAC Interfaces
Management Interface
Media Dependent Interface
JTAG Interface
Clock Interface
Device Configuration and LED Interface
Reset
Power and Ground Pins
Special Connect Pins
Type: I
Inputs
Type: O
Output
Type: O_Z
Tristate Output
Type: I/O_Z
Tristate Input_Output
Type: S
Strapping Pin
Type: PU
Internal Pull-up
Type: PD
Internal Pull-down
1.1 MAC Interfaces (MII, GMII, and RGMII)
Signal Name
Type
CRS/RGMII_SEL0
O_Z,
S, PD
PQFP
Pin #
40
Description
CARRIER SENSE or RGMII SELECT: CRS is asserted high to indicate the
presence of a carrier due to receive or transmit activity in Half Duplex mode.
For 10BASE-T and 100BASE-TX Full Duplex operation CRS is asserted when
a received packet is detected. This signal is not defined for 1000BASE-T Full
Duplex mode.
In RGMII mode, the CRS is not used. This pin can be used as a RGMII strapping selection pin.
RGMII_SEL1 RGMII_SEL0
COL/CLK_MAC_FREQ O_Z,
S, PD
39
MAC Interface
0
0
= GMII
0
1
= GMII
1
0
= RGMII - HP
1
1
= RGMII - 3COM
COLLISION DETECT: Asserted high to indicate detection of a collision condition (assertion of CRS due to simultaneous transmit and receive activity) in
Half Duplex modes. This signal is not synchronous to either MII clock
(GTX_CLK, TX_CLK or RX_CLK). This signal is not defined and stays low for
Full Duplex modes.
CLOCK TO MAC FREQUENCY Select:
1 = CLOCK TO MAC output is 125 MHz
0 = CLOCK TO MAC output is 25 MHz
TX_CLK/RGMII_SEL1
O_Z,
S, PD
60
TRANSMIT CLOCK or RGMII SELECT: TX_CLK is a continuous clock signal
generated from reference CLK_IN and driven by the PHY during 10 Mbps or
100 Mbps MII mode. TX_CLK clocks the data or error out of the MAC layer and
into the PHY.
The TX_CLK clock frequency is 2.5 MHz in 10BASE-T and 25 MHz in
100BASE-TX mode.
Note: “TX_CLK” should not be confused with the “TX_TCLK” signal.
In RGMII mode, the TX_CLK is not used. This pin can be used as a RGMII
strapping selection pin. This pin should be pulled high for RGMII interface.
5
www.national.com
DP83865
1.0 Pin Description (Continued)
Signal Name
TXD0/TX0
Type
PQFP
Pin #
I
76
TXD1/TX1
75
TXD2/TX2
72
TXD3/TX3
71
TXD4
68
TXD5
67
TXD6
66
TXD7
65
TX_EN/TXEN_ER
I
62
Description
TRANSMIT DATA: These signals carry 4B data nibbles (TXD[3:0]) during 10
Mbps and 100 Mbps MII mode, 4-bit data (TX[3:0]) in RGMII mode, and 8-bit
data (TXD[7:0]) in 1000 Mbps GMII mode. They are synchronous to the transmit clocks (TX_CLK, TCK, GTX_CLK).
Transmit data is input to PHY. In MII or GMII mode, the transmit data is enabled by TX_EN. In RGMII mode, the transmit data is enabled by TXEN_ER.
TRANSMIT ENABLE or TRANSMIT ENABLE/ERROR: In MII or GMII mode,
it is an active high input sourced from MAC layer to indicate transmission data
is available on the TXD.
In RGMII mode, it combines the transmit enable and the transmit error signals
of GMII mode using both clock edges.
GTX_CLK/TCK
I
79
GMII and RGMII TRANSMIT CLOCK: This continuous clock signal is sourced
from the MAC layer to the PHY. Nominal frequency is 125 MHz.
TX_ER
I
61
TRANSMIT ERROR: It is an active high input used in MII mode and GMII
mode forcing the PHY to transmit invalid symbols. The TX_ER signal is synchronous to the transmit clocks (TX_CLK or GTX_CLK).
In MII 4B nibble mode, assertion of Transmit Error by the controller causes the
PHY to issue invalid symbols followed by Halt (H) symbols until deassertion occurs.
In GMII mode, assertion causes the PHY to emit one or more code-groups that
are invalid data or delimiter in the transmitted frame.
This signal is not used in the RGMII mode.
RX_CLK
O_Z
57
RECEIVE CLOCK: Provides the recovered receive clocks for different modes
of operation:
2.5 MHz in 10 Mbps mode.
25 MHz in 100 Mbps mode.
125 MHz in 1000 Mps GMII mode.
This pin is not used in the RGMII mode.
RXD0/RX0
O_Z
56
RXD1/RX1
55
RXD2/RX2
52
RXD3/RX3
51
RXD4
50
RXD5
47
RXD6
46
RXD7
45
RX_ER/RXDV_ER
O_Z
41
RECEIVE DATA: These signals carry 4-bit data nibbles (RXD[3:0]) during 10
Mbps and 100 Mbps MII mode and 8-bit data bytes (RXD[7:0]) in 1000 Mbps
GMII mode. RXD is synchronous to the receive clock (RX_CLK). Receive data
is souirced from the PHY to the MAC layer.
Receive data RX[3:0] is used in RGMII mode. The data is synchronous to the
RGMII receive clock (RCK). The receive data available (RXDV_EN) indicates
valid received data to the MAC layer.
RECEIVE ERROR or RECEIVE DATA AVAILABLE/ERROR: In 10 Mbps,
100 Mbps and 1000 Mbps mode this active high output indicates that the PHY
has detected a Receive Error. The RX_ER signal is synchronous with the receive clock (RX_CLK).
In RGMII mode, the receive data available and receive error is combined
(RXDV_ER) using both rising and falling edges of the receive clock (RCK).
RX_DV/RCK
O_Z
44
RECEIVE DATA VALID or RECEIVE CLOCK: In MII and GMII modes, it is asserted high to indicate that valid data is present on the corresponding RXD[3:0]
in MII mode and RXD[7:0] in GMII mode.
In RGMII mode, this pin is the recovered receive clock (125MHz).
www.national.com
6
DP83865
1.0 Pin Description (Continued)
1.2 Management Interface
Type
PQFP
Pin #
MDC
I
81
MANAGEMENT DATA CLOCK: Synchronous clock to the MDIO serial management input/output data. This clock may be asynchronous to the MAC transmit and receive clocks. The maximum clock rate is 2.5 MHz and no minimum.
MDIO
I/O
80
MANAGEMENT DATA I/O: Bi-directional management instruction/data signal
that may be sourced by the management station or the PHY. This pin requires
a 2kΩ pullup resistor.
O_Z,
PU
3
MANAGEMENT INTERRUPT: It is an active-low open drain output indicating
to the MAC layer or to a managment interface that an interrupt has requested.
The interrupt status can be read through the Interrupt Status Register. (See
section “3.15 Interrupt” on page 47.)
Signal Name
INTERRUPT
Description
If used this pin requires a 2kΩ pullup resistor. This pin is to be left floating if it
is not used.
1.3 Media Dependent Interface
Signal Name
MDIA_P
Type
I/O
PQFP
PIn #
Description
108
Media Dependent Interface: Differential receive and transmit signals.
MDIA_N
109
MDIB_P
114
MDIB_N
115
The TP Interface connects the DP83865 to the CAT-5 cable through a single
common magnetics transformer. These differential inputs and outputs are configurable to 10BASE-T, 100BASE-TX or 1000BASE-T signalling:
MDIC_P
120
MDIC_N
121
MDID_P
126
MDID_N
127
The DP83865 will automatically configure the driver outputs for the proper signal type as a result of either forced configuration or Auto-Negotiation. The automatic MDI / MDIX configuration allows for transmit and receive channel
configuration and polarity configuration between channels A and B, and C and
D.
NOTE: During 10/100 Mbps operation only MDIA_P, MDIA_N, MDIB_P and
MDIB_N are active. MDIA_P and MDIA_N are transmitting only and MDIB_P
and MDIB_N are receiving only. (See section “3.5 Auto-MDIX resolution” on
page 44)
1.4 JTAG Interface
Type
PQFP
PIn #
TRST
I, PD
32
TEST RESET: IEEE 1149.1 Test Reset pin, active low reset provides for asynchronous reset of the Tap Controller. This reset has no effect on the device
registers.
TDI
I, PU
31
TEST DATA INPUT: IEEE 1149.1 Test Data Input pin, test data is scanned
into the device via TDI.
Signal Name
Description
This pin should be pulled down through a 2kΩ resistor if not used.
This pin should be left floating if not used.
TDO
O
28
TEST DATA OUTPUT: IEEE 1149.1 Test Data Output pin, the most recent
test results are scanned out of the device via TDO.
This pin should be left floating if not used.
TMS
I, PU
27
TEST MODE SELECT: IEEE 1149.1 Test Mode Select pin, the TMS pin sequences the Tap Controller (16-state FSM) to select the desired test instruction.
This pin should be left floating if not used.
7
www.national.com
DP83865
1.0 Pin Description (Continued)
Signal Name
TCK
Type
PQFP
PIn #
I
24
Description
TEST CLOCK: IEEE 1149.1 Test Clock input, primary clock source for all test
logic input and output controlled by the testing entity.
This pin should be left floating if not used.
1.5 Clock Interface
Type
PQFP
Pin #
CLK_IN
I
86
CLOCK INPUT: 25 MHz oscillator or crystal input (50 ppm).
CLK_OUT
O
87
CLOCK OUTPUT: Second terminal for 25 MHz crystal. Must be left floating if
a clock oscillator is used.
CLK_TO_MAC
O
85
CLOCK TO MAC OUTPUT: This clock output can be used to drive the clock
input of a MAC or switch device. This output is available after power-up and is
active during all modes except during hardware or software reset. Note that the
clock frequency is selectable through CLK_MAC_FREQ between 25 MHz and
125 MHz.
Signal Name
Description
To disable this clock output the MAC_CLK_EN_STRAP pin has to be tied low.
1.6 Device Configuration and LED Interface
(See section “3.7 PHY Address, Strapping Options and LEDs” on page 45 and section “5.9 LED/Strapping Option” on
page 67.)
Signal Name
NON_IEEE_STRAP
Type
I/O,
S, PD
PQFP
Pin #
1
Description
NON IEEE COMPLIANT MODE ENABLE: This mode allows interoperability
with certain non IEEE compliant 1000BASE-T transceivers.
‘1’ enables IEEE compliant operation and non-compliant operation
‘0’ enables IEEE compliant operation but inhibits non-compliant operation
Note: The status of this bit is reflected in bit 10 of register 0x10. This pin also
sets the default for and can be overwritten by bit 9 of register 0x12.
MAN_MDIX_STRAP /
TX_TCLK
I/O,
S, PD
6
MANUAL MDIX SETTING: This pin sets the default for manual MDI/MDIX
configuration.
‘1’ PHY is manually set to cross-over mode (MDIX)
‘0’ PHY is manually set to straight mode (MDI)
Note: The status of this bit is reflected in bit 8 of register 0x10. This pin also
sets the default for and can be overwritten by bit 14 of register 0x12.
TX_TCLK: TX_TCLK is enabled by setting bit 7 of register 0x12. It is used to
measure jitter in Test Modes 2 and 3 as described in IEEE 802.3ab specification. TX_TCLK should not be confused with the TX_CLK signal. See Table 12
on page 29 regarding Test Mode setting. This pin should be left floating if not
used.
www.national.com
8
DP83865
1.0 Pin Description (Continued)
Signal Name
ACTIVITY_LED /
SPEED0_STRAP
Type
I/O,
S, PD
PQFP
Pin #
7
Description
SPEED SELECT STRAP: These strap option pins have 2 different functions
depending on whether Auto-Negotiation is enabled or not.
Auto-Neg disabled:
Speed[1]
Speed[0]
1
1
Speed Enabled
= Reserved
1
0
= 1000BASE-T
0
1
= 100BASE-TX
0
0
= 10BASE-T
Auto-Neg enabled (Advertised capability):
Speed[1]
Speed[0]
1
1
Speed Enabled
= 1000BASE-T, 10BASE-T
1
0
= 1000BASE-T
0
1
= 1000BASE-T, 100BASE-TX
0
0
= 1000BASE-T, 100BASE-TX, 10BASE-T
Note: The status of this bit is reflected in register 0x10.12.
ACTIVITY LED: The LED output indicates the occurrence of either idle error
or packet transfer.
LINK10_LED /RLED/
SPEED1_STRAP
I/O,
S, PD
8
SPEED SELECT STRAP: The strap option pins have 2 different functions depending on whether Auto-Neg is enabled or not. See SPEED0_STRAP for details.
Note: The status of this bit is reflected in register 0x10.13.
10M GOOD LINK LED: In the standard 5-LED display mode, this LED output
indicates that the PHY has established a good link at 10 Mbps.
RLED MODE: There are two reduced LED modes, the 3-in-1 and 4-in-1
modes. Each RLED mode is enabled in register 0x13.5 and 0x1A.0.
– 3-in-1: 10, 100, and 1000 Mbps good links are combined into one LED.
– 4-in-1: 3-in-1 and activity are combined.
Note: LED steady on indicates good link and flashing indicates Tx/Rx activities.
LINK100_LED /
DUPLEX_STRAP
I/O,
S, PU
9
DUPLEX MODE: This pin sets the default value for the duplex mode. ‘1’ enables Full Duplex by default, ‘0’ enables Half Duplex only.
Note: The status of this bit is reflected in bit 14 of register 0x10.
100M SPEED AND GOOD LINK LED: The LED output indicates that the PHY
has established a good link at 100 Mbps.
In 100BASE-T mode, the link is established as a result of an input receive amplitude compliant with TP-PMD specifications which will result in internal generation of Signal Detect. LINK100_LED will assert after the internal Signal
Detect has remained asserted for a minimum of 500 µs. LINK100_LED will deassert immediately following the de-assertion of the internal Signal Detect.
LINK1000_LED /
AN_EN_STRAP
I/O,
S, PU
10
AUTO-NEGOTIATION ENABLE: Input to initialize Auto-Negotiation Enable
bit (register 0 bit-12).
‘1’ enables Auto-Neg and ‘0’ disables Auto-Neg.
Note: The status of this bit is reflected in bit 15 of register 0x10. This pin also
sets the default for and can be overwritten by bit 12 of register 0x00.
1000M SPEED AND GOOD LINK LED: The LED output indicates that the
PHY has established a good link at 1000 Mbps.
In 1000BASE-T mode, the link is established as a result of training, Auto-Negotiation completed, valid 1000BASE-T link established and reliable reception
of signals transmitted from a remote PHY is received.
9
www.national.com
DP83865
1.0 Pin Description (Continued)
Signal Name
Type
PQFP
Pin #
Description
DUPLEX_LED /
PHYADDR0_STRAP
I/O,
S, PU
13
PHYADDR1_STRAP
PD
14
PHYADDR2_STRAP
PD
17
PHYADDR3_STRAP
PD
18
PD
95
DUPLEX STATUS: The LED is lit when the PHY is in Full Duplex operation
after the link is established.
I/O,
S, PD
94
MULTIPLE NODE ENABLE: This pin determines if the PHY advertises Master
(multiple nodes) or Slave (single node) priority during 1000BASE-T Auto-Negotiation.
PHYADDR4_STRAP
MULTI_EN_STRAP /
TX_TRIGGER
PHY ADDRESS [4:0]: The DP83865 provides five PHY address-sensing pins
for multiple PHY applications. The setting on these five pins provides the base
address of the PHY.
The five PHYAD[4:0] bits are registered as inputs at reset with PHYADDR4 being the MSB of the 5-bit PHY address.
Note: The status of these bit is reflected in bits 4:0 of register 0x12.
‘1’ Selects multiple node priority (switch or hub)
‘0’ Selects single node priority (NIC)
Note: The status of this bit is reflected in bit 5 of register 0x10.
TX_TRIGGER: This output can be enabled during the IEEE 1000BASE-T testmodes. This signal is not required by IEEE to perform the tests, but will help to
take measurements. TX_TRIGGER is only available in test modes 1 and 4 and
provides a trigger to allow for viewing test waveforms on an oscilloscope.
MDIX_EN_STRAP
I/O,
S, PU
89
AUTO MDIX ENABLE: This pin controls the automatic pair swap (Auto-MDIX)
of the MDI/MDIX interface.
‘1’ enables pair swap mode
‘0’ disables the Auto-MDIX and defaults the part into the mode preset by the
MAN_MDIX_STRAP pin.
Note: The status of this bit is reflected in bit 6 of register 0x10. This pin also
sets the default for and can be overwritten by bit 15 of register 0x12.
MAC_CLK_EN_STRAP
/ TX_SYN_CLK
I, S,
PU
88
CLOCK TO MAC ENABLE:
‘1’ CLK_TO_MAC clock output enabled
‘0’ CLK_TO_MAC disabled
Note: This status of this pin is reflected in bit 7 of register 0x10.
TX_SYN_CLK: This output can be enabled during the IEEE 1000BASE-T testmodes. This signal is not required by IEEE to perform the tests, but will help to
take measurements. TX_SYN_CLK is only available in test modes 1 and 4.
TX_SYN_CLK = TX_TCLK / 4 in test mode 1
TX_SYN_CLK = TX_TCLK / 6 in test mode 4
VDD_SEL_STRAP
I/O, S
34
IO_VDD SELECT: This pin selects between 2.5V or 3.3V for I/O VDD .
‘1’ selects 3.3V mode
‘0’ selects 2.5V mode
This pin must either be connected directly to ground or directly to a supply voltage (2.5V to 3.3V).
1.7 Reset
Signal Name
RESET
www.national.com
Type
PQFP
Pin #
I
33
Description
RESET: The active low RESET input allows for hard-reset, soft-reset, and TRISTATE output reset combinations. The RESET input must be low for a minimum of 150 µs.
10
DP83865
1.0 Pin Description (Continued)
1.8 Power and Ground Pins
(See section “5.3 Power Supply Decoupling” on page 64.)
Signal Name
PQFP Pin #
Description
IO_VDD
4, 15, 21, 29, 37, 42, 53, 58, 69,
77, 83, 90
2.5V or 3.3V I/O Supply for “MAC Interfaces”, “Management
Interface”, “JTAG Interface”, “Clock Interface”, “Device Configuration and LED Interface” and “Reset”.
CORE_VDD
11, 19, 25, 35, 48, 63, 73, 92
1.8V Digital Core Supply
2V5_AVDD1
101
2.5V Analog Supply
2V5_AVDD2
96
2.5V Analog Supply
1V8_AVDD1
103, 105, 111, 117, 123
1.8V Analog Supply
1V8_AVDD2
98
1.8V Analog Supply - See section “5.4 Sensitive Supply
Pins” on page 64 for low pass filter recommendation.
1V8_AVDD3
100
1.8V Analog Supply - See section “5.4 Sensitive Supply
Pins” on page 64 for low pass filter recommendation.
VSS
5, 12, 16, 20, 22, 26, 30, 36, 38, Ground
43, 49, 54, 59, 64, 70, 74, 78, 82,
91, 93, 97, 99, 104, 106, 107,
110, 112, 113, 116, 118, 119,
122, 124, 125, 128
1.9 Special Connect Pins
Signal Name
BG_REF
RESERVED
TYPE
PQFP
Pin #
I
102
Description
Internal Reference Bias: See section “5.4 Sensitive Supply Pins” on page 64
for information on how to terminate this pin.
2, 23, These pins are reserved and must be left floating.
84
11
www.national.com
DP83865
1.0 Pin Description (Continued)
1.10 Pin Assignments in the Pin Number Order
Table 1.
Pin #
Data Sheet Pin Name
Type
Connection / Comment
Strap
Non IEEE Compliant Mode Enable: Use a 2kΩ
pull-up resistor to enable. Leave open to disable.
1
NON_IEEE_STRAP
2
RESERVED
3
INTERRUPT
Output
INTERRUPT: Connect to MAC or management
IC. This is a tri-state pin and requires an external
2kΩ pull-up resistor if the pin is used.
4
IO_VDD
Power
I/O VDD: (Digital) Connect to 2.5V or 3.3V. The
VDD_SEL pin must be tied accordingly.
5
VSS
Ground Ground: Connect to common ground plane.
6
TX_TCLK
Output
Transmit Test Clock: See section “1.9 Special
Connect Pins” on page 11.
7
ACTIVITY_LED / SPEED0_STRAP
Strap /
Output
Activity LED / SPEED0 Select: See section
“5.9 LED/Strapping Option” on page 67 on how
to connect this pin for speed selection and
ACTIVITY_LED function.
8
LINK10_LED / RLED/SPEED1_STRAP
Strap /
Output
10M Link LED / RLED / SPEED1: See section
“5.9 LED/Strapping Option” on page 67 on how
to connect this pin for speed selection and
LINK10_LED function.
9
LINK100_LED / DUPLEX_STRAP
Strap /
Output
100M Link LED / Duplex Select: See section
“5.9 LED/Strapping Option” on page 67 on how
to connect this pin for Duplex selection and
100_LED function.
10
LINK1000_LED / AN_EN_STRAP
Strap /
Output
1000M Link LED / Auto-Neg. Select: See section “5.9 LED/Strapping Option” on page 67 on
how to connect this pin for Auto-negotiation configuration and 1000_LED function.
Core VDD: (Digital) Connect to 1.8V.
Reserved Reserved: Leave floating.
11
CORE_VDD
Power
12
VSS
Ground Ground: Connect to common ground plane.
13
DUPLEX_LED / PHYADDR0_STRAP
Strap /
Output
Duplex LED / PHY Address 0: See section
“5.9 LED/Strapping Option” on page 67 on how
to connect this pin for PHY address configuration and DUPLEX_LED function.
14
PHYADDR1_STRAP
Strap
PHY Address 1: See section
“5.9 LED/Strapping Option” on page 67 on how
to connect this pin.
15
IO_VDD
Power
I/O VDD: (Digital) Connect to 2.5V or 3.3V. The
VDD_SEL pin must be tied accordingly.
16
VSS
Ground Ground: Connect to common ground plane.
17
PHYADDR2_STRAP
Strap
PHY Address 2: See section
“5.9 LED/Strapping Option” on page 67 on how
to connect this pin
18
PHYADDR3_STRAP
Strap
PHY Address 3: See section
“5.9 LED/Strapping Option” on page 67 on how
to connect this pin
19
CORE_VDD
Power
Core VDD: (Digital) Connect to 1.8V.
20
VSS
Gound
Ground: Connect to common ground plane.
21
IO_VDD
Power
I/O VDD: (Digital) Connect to 2.5V or 3.3V. The
VDD_SEL pin must be tied accordingly.
22
VSS
Ground Ground: Connect to common ground plane.
www.national.com
12
DP83865
1.0 Pin Description (Continued)
Table 1.
Pin #
Data Sheet Pin Name
Type
Connection / Comment
23
RESERVED
Reserved Reserved: Leave floating.
24
TCK
25
CORE_VDD
Power
Ground Ground: Connect to common ground plane.
Input
JTAG Test Clock: This pin should be left floating if not used.
Core VDD: (Digital) Connect to 1.8V.
26
VSS
27
TMS
Input
JTAG Test Mode Select: This pin should be left
floating if not used.
28
TDO
Output
JTAG Test Data Output: This pin should be left
floating if not used.
29
IO_VDD
Power
I/O VDD: (Digital) Connect to 2.5V or 3.3V. The
VDD_SEL pin must be tied accordingly.
30
VSS
Ground Ground: Connect to common ground plane.
31
TDI
Input
JTAG Test Data Input: This pin should be left
floating if not used.
32
TRST
Input
JTAG Test Reset: This pin should be pulled
down through a 2kΩ resistor if not used.
33
RESET
Input
Reset: Connect to board reset signal.
34
VDD_SEL_STRAP
Strap
I/O VDD Select: Pull high to select 3.3V or low
to select 2.5V. The pin must be connected directly to power or ground (no pull-up/down resistor!).
35
CORE_VDD
Power
Core VDD: (Digital) Connect to 1.8V.
36
VSS
Ground Ground: Connect to common ground plane.
37
IO_VDD
Power
I/O VDD: (Digital) Connect to 2.5V or 3.3V. The
VDD_SEL pin must be tied accordingly.
38
VSS
Ground Ground: Connect to common ground plane.
39
COL
Output
Collision: Connect to MAC chip through a single
50 Ω impedance trace. This output is capable of
driving 35 pF load and is not intended to drive
connectors, cables, backplanes or multiple traces. This applies if the part is in 100 Mbps mode
or 1000 Mbps mode.
40
CRS/RGMII_SEL0
Output
Carrier Sense: Connect to MAC chip through a
single 50Ω impedance trace. This output is capable of driving 35 pf load and is not intended to
drive connectors, cables, backplanes or multiple
traces. This applies if the part is in 100 Mbps
mode or 1000 Mbps mode.
41
RX_ER/RXDV_ER
Output
Receive Error: Connect to MAC chip through a
single 50 Ω impedance trace. This output is capable of driving 35 pf load and is not intended to
drive connectors, cables, backplanes or multiple
traces. This applies if the part is in 100 Mbps
mode or 1000 Mbps mode.
42
IO_VDD
Power
I/O VDD: (Digital) Connect to 2.5V or 3.3V. The
VDD_SEL pin must be tied accordingly.
43
VSS
Ground Ground: Connect to common ground plane.
44
RX_DV/RCK
Output
13
Receive Data Valid: Connect to MAC chip
through a single 50 Ω impedance trace. This output is capable of driving 35 pf load and is not intended to drive connectors, cables, backplanes
or multiple traces. This applies if the part is in
100 Mbps mode or 1000 Mbps mode.
www.national.com
DP83865
1.0 Pin Description (Continued)
Table 1.
Pin #
Data Sheet Pin Name
Type
Connection / Comment
45
RXD7
Output
Receive Data 7: Connect to MAC chip through
a single 50 Ω impedance trace. This output is capable of driving 35 pf load and is not intended to
drive connectors, cables, backplanes or multiple
traces. This applies if the part is in 100 Mbps
mode or 1000 Mbps mode.
46
RXD6
Output
Receive Data 6: Connect to MAC chip through
a single 50 Ω impedance trace. This output is capable of driving 35 pf load and is not intended to
drive connectors, cables, backplanes or multiple
traces. This applies if the part is in 100 Mbps
mode or 1000 Mbps mode.
47
RXD5
Output
Receive Data 5: Connect to MAC chip through
a single 50 Ω impedance trace. This output is capable of driving 35 pf load and is not intended to
drive connectors, cables, backplanes or multiple
traces. This applies if the part is in 100 Mbps
mode or 1000 Mbps mode.
Core VDD: (Digital) Connect to 1.8V.
48
CORE_VDD
Power
49
VSS
Ground Ground: Connect to common ground plane.
50
RXD4
Output
Receive Data 4: Connect to MAC chip through
a single 50 Ω impedance trace. This output is capable of driving 35 pf load and is not intended to
drive connectors, cables, backplanes or multiple
traces. This applies if the part is in 100 Mbps
mode or 1000 Mbps mode.
51
RXD3/RX3
Output
Receive Data 3: Connect to MAC chip through
a single 50 Ω impedance trace. This output is capable of driving 35 pf load and is not intended to
drive connectors, cables, backplanes or multiple
traces. This applies if the part is in 100 Mbps
mode or 1000 Mbps mode.
52
RXD2/RX2
Output
Receive Data 2: Connect to MAC chip through
a single 50 Ω impedance trace. This output is capable of driving 35 pf load and is not intended to
drive connectors, cables, backplanes or multiple
traces. This applies if the part is in 100 Mbps
mode or 1000 Mbps mode.
53
IO_VDD
Power
I/O VDD: (Digital) Connect to 2.5V or 3.3V. The
VDD_SEL pin must be tied accordingly.
54
VSS
Ground Ground: Connect to common ground plane.
55
RXD1/RX1
Output
Receive Data 1: Connect to MAC chip through
a single 50 Ω impedance trace. This output is capable of driving 35 pf load and is not intended to
drive connectors, cables, backplanes or multiple
traces. This applies if the part is in 100 Mbps
mode or 1000 Mbps mode.
56
RXD0/RX0
Output
Receive Data 0: Connect to MAC chip through
a single 50 Ω impedance trace. This output is capable of driving 35 pf load and is not intended to
drive connectors, cables, backplanes or multiple
traces. This applies if the part is in 100 Mbps
mode or 1000 Mbps mode.
www.national.com
14
DP83865
1.0 Pin Description (Continued)
Table 1.
Pin #
Data Sheet Pin Name
Type
Connection / Comment
57
RX_CLK
Output
Receive Clock/ Receive Byte Clock 1: Connect to MAC chip through a single 50 Ω impedance trace. This output is capable of driving 35
pf load and is not intended to drive connectors,
cables, backplanes or multiple traces. This applies if the part is in 100 Mbps mode or 1000
Mbps mode.
58
IO_VDD
Power
I/O VDD: (Digital) Connect to 2.5V or 3.3V. The
VDD_SEL pin must be tied accordingly.
59
VSS
Ground Ground: Connect to common ground plane.
60
TX_CLK/RGMII_SEL1
Output
Transmit Clock: Connect to MAC chip through
a single 50 Ω impedance trace. This input has a
typical input capacitance of 6 pF.
61
TX_ER
Input
Transmit Error: Connect to MAC chip through a
single 50 Ω impedance trace. This input has a
typical input capacitance of 6 pF.
62
TX_EN/TXEN_ER
Input
Transmit Enable: Connect to MAC chip through
a single 50 Ω impedance trace. This input has a
typical input capacitance of 6 pF.
63
CORE_VDD
Power
Ground Ground: Connect to common ground plane.
Core VDD: (Digital) Connect to 1.8V.
64
VSS
65
TXD7
Input
Transmit Data 7: Connect to MAC chip through
a single 50 Ω impedance trace. This input has a
typical input capacitance of 6 pF.
66
TXD6
Input
Transmit Data 6: Connect to MAC chip through
a single 50 Ω impedance trace. This input has a
typical input capacitance of 6 pF
67
TXD5
Input
Transmit Data 5: Connect to MAC chip through
a single 50 Ω impedance trace. This input has a
typical input capacitance of 6 pF
68
TXD4
Input
Transmit Data 4: Connect to MAC chip through
a single 50 Ω impedance trace. This input has a
typical input capacitance of 6 pF
69
IO_VDD
Power
I/O VDD: (Digital) Connect to 2.5V or 3.3V. The
VDD_SEL pin must be tied accordingly.
Ground Ground: Connect to common ground plane.
70
VSS
71
TXD3/TX3
Input
Transmit Data 3: Connect to MAC chip through
a single 50 Ω impedance trace. This input has a
typical input capacitance of 6 pF
72
TXD2/TX2
Input
Transmit Data 2: Connect to MAC chip through
a single 50 Ω impedance trace. This input has a
typical input capacitance of 6 pF
73
CORE_VDD
Power
Ground Ground: Connect to common ground plane.
Core VDD: (Digital) Connect to 1.8V.
74
VSS
75
TXD1/TX1
Input
Transmit Data 1: Connect to MAC chip through
a single 50 Ω impedance trace. This input has a
typical input capacitance of 6 pF
76
TXD0/TX0
Input
Transmit Data 0: Connect to MAC chip through
a single 50 Ω impedance trace. This input has a
typical input capacitance of 6 pF
77
IO_VDD
Power
I/O VDD: (Digital) Connect to 2.5V or 3.3V. The
VDD_SEL pin must be tied accordingly.
78
VSS
Ground Ground: Connect to common ground plane.
15
www.national.com
DP83865
1.0 Pin Description (Continued)
Table 1.
Pin #
Data Sheet Pin Name
Type
Connection / Comment
Input
GMII Transmit Clock: Connect to MAC chip
through a single 50 Ω impedance trace. This input has a typical input capacitance of 6 pF
79
GTX_CLK/TCK
80
MDIO
Input /
Output
Management Data I/O: This pin requires a 2kΩ
parallel termination resistor (pull-up to VDD).
81
MDC
Input
Management Data Clock: Connect to MAC or
controller using a 50 Ω impedance trace.
82
VSS
Ground Ground: Connect to common ground plane.
83
IO_VDD
Power
84
RESERVED
85
CLK_TO_MAC
86
I/O VDD: (Digital) Connect to 2.5V or 3.3V. The
VDD_SEL pin must be tied accordingly.
Reserved Reserved: Leave floating.
Output
Clock to MAC: Connect to the reference clock
input of a GMAC. Use pin
MAC_CLK_EN_STRAP to disable this function.
CLK_IN
Input
Clock Input: Connect to external 25MHz reference clock source. If a crystal is used connect to
first terminal of crystal.
87
CLK_OUT
Input
Clock Output: Connect to the second terminal
of a crystal. Leave floating if an external clock
source is used.
88
MAC_CLK_EN_STRAP
Strap
Clock to MAC Enable: Use a 2kΩ pull-down resistor to disable. Leave open to enable.
89
MDIX_EN_STRAP
Strap
Automatic MDIX Enable: Use a 2kΩ pull-down
resistor to disable. Leave open to enable.
90
IO_VDD
Power
I/O VDD: (Digital) Connect to 2.5V or 3.3V. The
VDD_SEL pin must be tied accordingly.
91
VSS
Ground Ground: Connect to common ground plane.
92
CORE_VDD
Power
93
VSS
Ground Ground: Connect to common ground plane.
94
MULTI_EN_STRAP
Strap
Multiple Node Enable: Use a 2kΩ pull-up resistor to enable. Leave open to disable.
95
PHYADDR4_STRAP
Strap
PHY Address 4: See section
“5.9 LED/Strapping Option” on page 67 on how
to connect this pin.
96
AFE_VDD
Power
AFE VDD: (Analog) Connect to 2.5V.
97
VSS
Ground Ground: Connect to common ground plane.
98
PGM_VDD
Power
99
VSS
Ground Ground: Connect to common ground plane.
100
1V8_AVDD3
Power
Analog Supply: Connect to 1.8V through a low
pass filter. See section “5.4 Sensitive Supply
Pins” on page 64 for details.
101
BG_VDD
Power
BG VDD: (Analog) Connect to 2.5V.
102
BG_REF
Input
103
RX_VDD
Power
104
VSS
Ground Ground: Connect to common ground plane.
105
RX_VDD
Power
106
VSS
Ground Ground: Connect to common ground plane.
www.national.com
16
Core VDD: (Digital) Connect to 1.8V.
PGM VDD: Connect to 1.8V through a low pass
filter. See section “5.4 Sensitive Supply Pins” on
page 64 for details.
BG Reference: See section “5.4 Sensitive Supply Pins” on page 64 on how to connect this pin.
Receive VDD: (Analog) Connect to 1.8V.
Receive VDD: (Analog) Connect to 1.8V.
DP83865
1.0 Pin Description (Continued)
Table 1.
Pin #
Data Sheet Pin Name
Type
Connection / Comment
107
VSS
Ground Ground: Connect to common ground plane.
108
MDIA_P
Input /
Output
MDI Channel A Positive: Connect to TD+ of
channel A of the magnetics.
109
MDIA_N
Input /
Output
MDI Channel A Negative: Connect to TD- of
channel A of the magnetics.
110
VSS
Ground Ground: Connect to common ground plane.
111
RX_VDD
Power
112
VSS
Ground Ground: Connect to common ground plane.
113
VSS
Ground Ground: Connect to common ground plane.
114
MDIB_P
Input /
Output
MDI Channel B Positive: Connect to TD+ of
channel B of the magnetics.
115
MDIB_N
Input /
Output
MDI Channel B Negative: Connect to TD- of
channel B of the magnetics.
116
VSS
Ground Ground: Connect to common ground plane.
117
RX_VDD
Power
118
VSS
Ground Ground: Connect to common ground plane.
119
VSS
Ground Ground: Connect to common ground plane.
120
MDIC_P
Input /
Output
MDI Channel C Positive: Connect to TD+ of
channel C of the magnetics.
121
MDIC_N
Input /
Output
MDI Channel C Negative: Connect to TD- of
channel C of the magnetics.
122
VSS
Ground Ground: Connect to common ground plane.
123
RX_VDD
Power
124
VSS
Ground Ground: Connect to common ground plane.
125
VSS
Ground Ground: Connect to common ground plane.
126
MDID_P
Input /
Output
MDI Channel D Positive: Connect to TD+ of
channel D of the magnetics.
127
MDID_N
Input /
Output
MDI Channel D Negative: Connect to TD- of
channel D of the magnetics.
128
VSS
Ground Ground: Connect to common ground plane.
17
Receive VDD: (Analog) Connect to 1.8 Volt.
Receive VDD: (Analog) Connect to 1.8V.
Receive VDD: (Analog) Connect to 1.8V.
www.national.com
DP83865
2.0 Register Block
2.1 Register Definitions
Register maps and address definitions are given in the following table:
Table 2. Register Block - DP83865 Register Map
Offset
Access
Tag
0
RW
BMCR
Basic Mode Control Register
1
RO
BMSR
Basic Mode Status Register
0x02
2
RO
PHYIDR1
PHY Identifier Register #1
0x03
3
RO
PHYIDR2
PHY Identifier Register #2
Hex
Decimal
0x00
0x01
Description
0x04
4
RW
ANAR
0x05
5
RW
ANLPAR
Auto-Negotiation Advertisement Register
0x06
6
RW
ANER
0x07
7
RW
ANNPTR
Auto-Negotiation Next Page TX
Auto-Negotiation Next Page RX
Auto-Negotiation Link Partner Ability Register
Auto-Negotiation Expansion Register
0x08
8
RW
ANNPRR
0x09
9
RW
1KTCR
1000BASE-T Control Register
0x0A
10
RO
1KSTSR
1000BASE-T Status Register
0x0B-0x0E
11-14
RO
Reserved
Reserved
0x0F
15
RO
1KSCR
0x10
16
RO
STRAP_REG
0x11
17
RO
LINK_AN
0x12
18
RW
AUX_CTRL
Auxiliary Control Register
0x13
19
RW
LED_CTRL
LED Control Register
0x14
20
RO
INT_STATUS
Interrupt Status Register
0x15
21
RW
INT_MASK
Interrupt Mask Register
0x16
22
RO
EXP_MEM_CTL
1000BASE-T Extended Status Register
Strap Options Register
Link and Auto-Negotiation Status Register
Expanded Memory Access Control
0x17
23
RW
INT_CLEAR
Interrupt Clear Register
0x18
24
RW
BIST_CNT
BIST Counter Register
0x19
25
RW
BIST_CFG1
BIST Configuration Register #1
0x1A
26
RW
BIST_CFG2
BIST Configuration Register #2
0x1B-0x1C
27-28
RO
Reserved
0x1D
29
RW
EXP_MEM_DATA
Expanded Memory Data
0x1E
30
RW
EXP_MEM_ADDR
Expanded Memory Address
0x1F
31
RW
PHY_SUP
www.national.com
Reserved
18
PHY Support Register
19
0
ACK2
0
ACK2
0
Reserved
0
Reserved
0
Reserved
1
OUI[22]
0
OUI[6]
10BASE-T
Full-Duplex
1
Register 0x0F (15’d)
1000BASE-T Extended
Status Register (1KSCR)
Register 0x0E (14’d)
Reserved
Register 0x0D (13’d)
Reserved
Register 0x0C (12’d)
Reserved
Register 0x0B (11’d)
Reserved
1000BASE-X
Half-Duplex
0
0
1000BASE-X
Full-Duplex
0
0
0
Reserved
Reserved
0
0
Reserved
0
Reserved
Reserved
0
0
Reserved
Reserved
Reserved
1000BASE-T
Full-Duplex
1
0
Reserved
0
Reserved
0
Reserved
0
Reserved
0
1000BASE-T
Half-Duplex
1
0
Reserved
0
Reserved
0
Reserved
0
Reserved
Remote Receiver Status
0
0
0
Message Page
1
Message Page
0
Reserved
0
Remote Fault
0
Remote Fault
0
OUI[21]
1
OUI[5]
100BASE-X
Half-Duplex
1
12
Auto-Neg
Enable
Strap[1]
Master/Slave
Master/Slave- Local Receiver
Register 0x0A (10’d)
Manual Config. Config. Resol.
Status
1000BASE-T Status Register
Fault
0
0
(1KSTSR)
0, LH, SC
0
13
Speed [0]
Selection
Strap[0]
Master/Slave
Config. Enable
0
Test Mode[1]
0
0
Test Mode[2]
ACK
0
ACK
Next Page
1
Next Page
0
0
0
Reserved
0
Reserved
ACK
Next Page
0
0
1
Reserved
0
Next Page
OUI[20]
0
0
OUI[19]
OUI[4]
100BASE-X
Full-Duplex
1
OUI[3]
0
100BASE-T4
0
0, SC
14
Loopback
15
PHY Reset
Test Mode[0]
Register 0x09
1000BASE-T Control
Register (1KTCR)
Register 0x08
Auto-Neg NP RX Register
(ANNPRR)
Register 0x07
Auto-Neg NP TX Register
(ANNPTR)
Register 0x06
Auto-Neg Expansion Register
(ANER)
Register 0x05
Auto-Neg Link Partner
Ability Register (ANLPAR)
Register 0x04
Auto-Neg Advertisement
Register (ANAR)
Register 0x03
PHY Identifier Register #2
(PHYIDR2)
Register 0x02
PHY Identifier Register #1
(PHYIDR1)
Register 0x01
Basic Mode Status Register
(BMSR)
Register 0x00
Basic Mode Control Register
(BMCR)
Register Name
2.2 Register Map
11
10
Reserved
0
Bit Name
Read/Writable
Default Value
0
Key:
0
Reserved
0
Reserved
0
Reserved
0
Reserved
LP
1000BASE-T
Half-Duplex
0
STRAP[0]
Repeater DTE
0
NP_M[10]
0
NP_M[10]
0
Reserved
0
PAUSE
0
PAUSE
1
OUI[24]
0
OUI[8]
100BASE-T2
Full-Duplex
0
0
Isolate
Reserved
0
Reserved
0
Reserved
0
Reserved
0
Reserved
LP
1000BASE-T
Full-Duplex
0
Master/Slave
Config. Value
0
0
TOG_RX
0
TOG_TX
0
Reserved
0
ASY_PAUSE
0
ASY_PAUSE
1
OUI[23]
0
OUI[7]
10BASE-T
Half-Duplex
1
0
Power Down
9
8
0
OUI[10]
1000BASE-T
Ext’d Status
1
Strap[1]
Duplex Mode
7
0
OUI[11]
0
Reserved
0
Collision Test
6
0
OUI[12]
Preamble
Suppression
1
Speed[1]
Selection
Strap[1]
5
0
OUI[13]
Auto-Neg
Complete
0
0
Reserved
4
0
OUI[14]
0, LH
Remote Fault
0
Reserved
0
0
Reserved
0
Reserved
0
Reserved
0
Reserved
0
Bit Name
Read Only
Value
0
Reserved
0
Reserved
0
Reserved
0
Reserved
0
Reserved
0
0
Reserved
Reserved
1000BASE-T
Half-Duplex
STRAP[1]
0
NP_M[8]
0
NP_M[8]
0
Reserved
100BASE-TX
Full-Duplex
0
100BASE-TX
Full-Duplex
STRAP[1]
Reserved
1000BASE-T
Full-Duplex
STRAP[1]
0
NP_M[9]
0
NP_M[9]
0
Reserved
0
100BASE-T4
0
100BASE-T4
0
0
Reserved
0
Reserved
0
Reserved
0
Reserved
0
Reserved
Idle Error
Count[7]
0
0
Reserved
0
NP_M[7]
0
NP_M[7]
0
Reserved
100BASE-TX
Half-Duplex
0
100BASE-TX
Half-Duplex
STRAP[1]
0
Reserved
0
Reserved
0
Reserved
0
Reserved
0
Reserved
0
Reserved
Idle Error
Count[6]
0
0
Reserved
0
NP_M[6]
0
NP_M[6]
0
Reserved
10BASE-T
Full-Duplex
0
10BASE-T
Full-Duplex
STRAP[1]
1
0
Reserved
0
Reserved
0
Reserved
0
Reserved
0
Reserved
Idle Error
Count[5]
0
0
Reservd
0
NP_M[5]
0
NP_M[5]
0
Reserved
10BASE-T
Half-Duplex
0
10BASE-T
Half-Duplex
STRAP[1]
1
0
Reserved
0
Reserved
0
Reserved
0
Reserved
0
Reserved
Idle Error
Count[4]
0
0
Reserved
0
NP_M[4]
0
NP_M[4]
0, LH
PDF
0
PSB[4]
0
PSB[4]
1
VMDR_MDL[5] VMDR_MDL[4] VMDR_MDL[3] VMDR_MDL[2] VMDR_MDL[1] VMDR_MDL[0]
0
OUI[9]
100BASE-T2
Half-Duplex
0
Restart
Auto-Neg
0, SC
3
0
Reserved
0
Reserved
0
Reserved
0
Reserved
0
Reserved
Idle Error
Count[3]
0
0
Reserved
0
NP_M[3]
0
NP_M[3]
0
LP_NP Able
0
PSB[3]
0
PSB[3]
1
MDL_REV[3]
0
OUI[15]
Auto-Neg
Ability
1
0
Reserved
2
0
Reserved
0
Reserved
0
Reserved
0
Reserved
0
Reserved
Idle Error
Count[2]
0
0
Reserved
0
NP_M[2]
0
NP_M[2]
1
NP_Able
0
PSB[2]
0
PSB[2]
0
MDL_REV[2]
0
OUI[16]
0, LL
Link Status
0
Reserved
1
0
Reserved
0
Reserved
0
Reserved
0
Reserved
0
Reserved
Idle Error
Count[1]
0
0
Reserved
0
NP_M[1]
0
NP_M[1]
0, LH
Page _RX
0
PSB[1]
0
PSB[1]
1
MDL_REV[1]
0
OUI[17]
Jabber
Detect
0, LH
0
Reserved
0
0
Reserved
0
Reserved
0
Reserved
0
Reserved
0
Reserved
Idle Error
Count[0]
0
0
Reserved
0
NP_M[0]
0
NP_M[0]
0
LP_AN Able
0
PSB[0]
1
PSB[0]
0
MDL_REV[0]
0
OUI[18]
1
Extended
Capability
0
Reserved
DP83865
2.0 Register Block (Continued)
www.national.com
www.national.com
TP_POL[2]
0
0
20
0, SC
0, SC
0
0, SC
Clear Int.
0, SC
Clear Int.
0
Reserved
0
Mask Int.
Polarity
Change Int.
0
100BASE-TX
Link LED[1]
0
Reserved
(RGMII Inband
Sig. Enable)
0
Reserved
(Power Down
Status)
0
10
0, SC
Clear Int.
0
Reserved
0
Mask Int.
PDF Detection
Fault Int.
0
100BASE-TX
Link LED[0]
0
Reserved
(RGMII Inband
Sig. Enable)
0
0
MDIX Status
STRAP[0]
NC Mode
0
Exp Mem Data
14
0
0
Exp Mem Data
15
0
Reserved
Reserved
0
0
Exp Mem Data
13
0
0
Reserved
0
Reserved
Transmit BIST
Packet
Count[2]
0
Transmit BIST
Packet Length
0
0
Exp Mem Data
12
0
0
Reserved
0
Reserved
Transmit BIST
Packet
Count[1]
0
Transmit BIST
IFG
0
0
Exp Mem Data
11
0
0
Reserved
0
Reserved
Transmit BIST
Packet
Count[0]
0
Transmit BIST
Enable
0
0
Exp Mem Data
10
0
0
Reserved
0
Exp Mem Data
9
0
0
Reserved
0
Reserved
0
Exp Mem Data
8
0
0
Reserved
0
Reserved
0
Reserved
0
0
Counter Bit[8]
0, SC
Clear Int.
Reserved
(Broadcast Enable)
0
0
Exp Mem Data
7
0
0
Reserved
0
Reserved
0
Reserved
Transmit BIST
Packet[7]
0
0
Counter Bit[7]
0, SC
Clear Int.
0
Broadcast En.
0
Mask Int.
0
Mask Int.
No Link Int.
0
Duplex LED[1]
TX_TCLK
Enable
0
Reserved
(Shallow Loopback Status
0
0
0
0
7
MAC Clock
Enable
STRAP[1]
No HCD Int.
1000BASE-T
Link LED[0]
0
RGMII_inband
Status Enable
0
Reserved
(Power-On Init
In Progress)
0
Reserved
Reserved
Reserved
8
Reserved
(REF_SEL)
STRAP[0]
Reserved
0
Counter Bit[9]
0, SC
Clear Int.
0
Reserved
0
Mask Int.
Master/Slave
Fail Int.
0
1000BASE-T
Link LED[1]
0
NC Mode
Enable
STRAP[0]
0
FIFO Error
Reserved
Transmit BIST
Packet Type
0
9
Reserved
(REF_SEL)
STRAP[0]
6
Exp Mem Data
6
0
0
Reserved
0
Reserved
0
Reserved
Transmit BIST
Packet[6]
0
0
Counter Bit[6]
0, SC
Clear Int.
0
Reserved
0
Mask Int.
Jabber Change
Int.
0
0
Duplex LED[0]
TX_TRIG
/SYNC Enable
0
(Deep) Loopback
Status
0
Auto MDIX
Enable
STRAP[1]
5
Exp Mem Data
5
0
0
Reserved
0
Reserved
0
Reserved
Transmit BIST
Packet[5]
0
0
Counter Bit[5]
0, SC
Clear Int.
0
Reserved
0
Mask Int.
Next Page
Received Int.
0
10M LED
RLED enable
0
Shallow Loopback Enable
0
NC Mode
Status
0
STRAP[0]
Multi Enable
4
Exp Mem Data
4
0
0
Reserved
0
Reserved
0
Reserved
Transmit BIST
Packet[4]
0
0
Counter Bit[4]
0, SC
Clear Int.
0
Reserved
0
Mask Int.
Auto-Neg.
Complete Int.
0
Modulate LED
on CRC Error
0
0
X_Mac Enable
Speed
Status[1]
0
STRAP[0]
PHYADDR[4]
3
Exp Mem Data
3
0
0
Reserved
0
Reserved
0
Reserved
Transmit BIST
Packet[3]
0
0
Counter Bit[3]
0, SC
Clear Int.
0
Reserved
0
Mask Int.
Remote Fault
Change Int.
0
Modulate LED
on Idle Error
0
0
Reserved
Speed
Status[0]
0
STRAP[0]
PHYADDR[3]
2
Exp Mem Data
2
0
0
Reserved
0
Reserved
0
Reserved
Transmit BIST
Packet[2]
0
0
Counter Bit[2]
0
Reserved
0
Reserved
0
Reserved
0
Reserved
AN Fallback
on Gigabit Link
0
0
Reserved
0
Link Status
STRAP[0]
PHYADDR[2]
1
Exp Mem Data
1
0
0
Reserved
0
Reserved
0
Reserved
Transmit BIST
Packet[1]
0
0
Counter Bit[1]
0
Reserved
0
XMode[1]
0
Reserved
0
Reserved
AN Fallback
on CRC Error
0
0
Reserved
0
Duplex Status
STRAP[0]
PHYADDR[1]
0
Exp Mem Data
0
0
0
Reserved
0
Reserved
10M LED
ACT/LNK-LNK
0
Transmit BIST
Packet[0]
0
0
Counter Bit[0]
0
Reserved
0
XMode[0]
0
Reserved
0
Reserved
AN Fallback
on Idle Error
0
0
Jabber Disable
0
Master/Slave
Config. Status
STRAP[1]
PHYADDR[0]
Register 0x1F (31’d)
PHY Support Register
(PHY_SUP)
Reserved
0
Reserved
0
0
Reserved
Reserved
BrdCst_AD[4]
0
Reserved
BrdCst_AD[2]
0
Bit Name
Read/Writable
Default Value
Reserved
BrdCst_AD[3]
0
Key:
Reserved
BrdCst_AD[1]
0
Bit Name
Read Only
Value
Reserved
BrdCst_AD[0]
0
0
Reserved
Reserved
0
Reserved
0
Reserved
PHY
ADDRESS[4]
0
PHY
ADDRESS[3]
0
PHY
ADDRESS[2]
0
PHY
ADDRESS[1]
0
PHY
ADDRESS[0]
1
Exp Mem Addr Exp Mem Addr Exp Mem Addr Exp Mem Addr Exp Mem Addr Exp Mem Addr Exp Mem Addr Exp Mem Addr Exp Mem Addr Exp Mem Addr Exp Mem Addr Exp Mem Addr Exp Mem Addr Exp Mem Addr Exp Mem Addr Exp Mem Addr
Register 0x1E (30’d)
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Exp Memory Address Pointer
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
(EXP_MEM_ADD)
Register 0x1D (29’d)
Exp Memory Data
(EXP_MEM_DATA)
Register 0x1C (28’d)
Reserved
Reserved
Register 0x1A (26’d)
BIST Configuration Register
#2 (BIST_CFG2)
0
BIST Counter
Select
0
Receive BIST
Enable
0
Register 0x19 (25’d)
BIST Configuration Register
#1 (BIST_CFG1)
Reserved
0
BIST Counter
Clear
0
0
Register 0x1B (27’d)
Reserved
0, SC
Clear Int.
Reserved
0
Mask Int.
MDIX Change
Int.
0
11
Reserved
(REF_SEL)
STRAP[0]
Counter Bit[15] Counter Bit[14] Counter Bit[13] Counter Bit[12] Counter Bit[11] Counter Bit[10]
0
Clear Int.
0, SC
Clear Int.
0
0
Mask Int.
Duplex
Change Int.
0
Reserved
BIST Counter
Type
0
Register 0x18 (24’d)
BIST Counter Register
(BIST_CNT)
Register 0x17 (23’d)
Interrupt Clear Register
(INT_CLEAR)
STRAP[0]
10BASE-T
Link LED[0]
0
STRAP[0]
10BASE-T
Link LED[1]
0
RGMII_EN[0]
0
RGMII_EN[1]
0
TP_POL[0]
STRAP[0]
TP_POL[1]
STRAP[0]
12
Speed[0]
13
Speed[1]
Reserved
0
0
Register 0x15 (21’d)
Interrupt Mask Register
(INT_MASK)
Global Reset
Mask Int.
Mask Int.
Register 0x16 (22’d)
Exp Memory Access Control
(EXP_MEM_CTL)
Link Change
Int.
0
0
0
Register 0x13 (19’d)
LED Control Register
(LED_CTRL)
Speed Change
Int.
0
Act. LED[0]
Act. LED[1]
Register 0x14 (20’d)
Interrupt Status Register
(INT_STATUS)
Manual MDIX
Mode
STRAP[0]
Auto MDIX
Enable
STRAP[1]
STRAP[1]
TP_POL[3]
14
Full Duplex
Enable
STRAP[1]
15
AN Enable
Register 0x12 (18’d)
Auxiliary Control Register
(AUX_CTRL)
Register 0x11 (17’d)
Link and Auto-Negotiation
Status Register (LINK_AN)
Register 0x10 (16’d)
Strap Option Register
(STRAP_REG)
Register Name
DP83865
2.0 Register Block (Continued)
DP83865
2.0 Register Block (Continued)
2.3 Register Description
In the register description under the ‘Default’ heading, the following definitions hold true:
—
—
—
—
—
—
—
RW
RO
LH
LL
SC
P
STRAP[x]
=
=
=
=
=
=
=
Read Write access
Read Only access
Latched High until read, based upon the occurrence of the corresponding event
Latched Low until read, based upon the occurrence of the corresponding event
Register sets on event occurrence (or is manually set) and Self-Clears when event ends
Register bit is Permanently set to a default value
Default value read from Strapped value at device pin at Reset, where x may take the values:
[0] internal pull-down
[1] internal pull-up
Table 3. Basic Mode Control Register (BMCR) address 0x00
Bit
Bit Name
Default
15
Reset
0, RW, SC
Description
Reset:
1 = Initiate software Reset / Reset in Process.
0 = Normal operation.
This bit sets the status and control registers of the PHY to their
default states. This bit, which is self-clearing, returns a value of
one until the reset process is complete (approximately 1.2 ms for
reset duration). Reset is finished once the Auto-Negotiation process has begun or the device has entered it’s forced mode.
14
Loopback
0, RW
Loopback:
1 = Loopback enabled.
0 = Normal operation.
The loopback function enables MII/GMII transmit data to be routed to the MII/GMII receive data path. The data loops around at
the DAC/ADC Subsystem (see block diagram page 2), bypassing
the Drivers/Receivers block. This exercises most of the PHY’s internal logic.
13
Speed[0]
STRAP[0], RW Speed Select:
When Auto-Negotiation is disabled, bits 6 and 13 select device
speed selection per table below:
Speed[1]
Speed[0]
Speed Enabled
1
1
= Reserved
1
0
= 1000 Mbps
0
1
= 100 Mbps
0
0
= 10 Mbps
(The default value of this bit is = to the strap value of pin 7 during
reset/power-on IF Auto-Negotiation is disabled.)
12
AN_EN
STRAP[1], RW Auto-Negotiation Enable:
1 = Auto-Negotiation Enabled - bits 6, 8 and 13 of this register are
ignored when this bit is set.
0 = Auto-Negotiation Disabled - bits 6, 8 and 13 determine the link
speed and mode.
(The default value of this bit is = to the strap value of pin 10 during
reset/power-on.)
21
www.national.com
DP83865
2.0 Register Block (Continued)
Table 3. Basic Mode Control Register (BMCR) address 0x00
Bit
Bit Name
Default
11
Power_Down
0, RW
Description
Power Down:
1 = Power down (only Management Interface and logic active.)
0 = Normal operation.
Note: This mode is internally the same as isolate mode (bit 10).
10
Isolate
0, RW
Isolate:
1 = Isolates the Port from the MII/GMII with the exception of the
serial management. When this bit is asserted, the DP83865 does
not respond to TXD[7:0], TX_EN, and TX_ER inputs, and it presents a high impedance on TX_CLK, RX_CLK, RX_DV, RX_ER,
RXD[7:0], COL and CRS outputs.
0 = Normal operation.
9
Restart_AN
0, RW, SC
Restart Auto-Negotiation:
1 = Restart Auto-Negotiation. Re-initiates the Auto-Negotiation
process. If Auto-Negotiation is disabled (bit 12 = 0), this bit is ignored. This bit is self-clearing and will return a value of 1 until
Auto-Negotiation is initiated, whereupon it will self-clear. Operation of the Auto-Negotiation process is not affected by the management entity clearing this bit.
0 = Normal operation.
8
Duplex
STRAP[1], RW Duplex Mode:
1 = Full Duplex operation. Duplex selection is allowed only when
Auto-Negotiation is disabled (AN_EN = 0).
0 = Half Duplex operation.
(The default value of this bit is = to the strap value of pin 9 during
reset/power-on IF Auto-Negotiation is disabled.)
7
Collision Test
0, RW
Collision Test:
1 = Collision test enabled.
0 = Normal operation.
When set, this bit will cause the COL signal to be asserted in response to the assertion of TX_EN withinTBD-bit times. The COL
signal will be de-asserted within 4-bit times in response to the deassertion of TX_EN.
6
Speed[1]
STRAP[0], RW Speed Select: See description for bit 13.
(The default value of this bit is = to the strap value of pin 8 during
reset/power-on IF Auto-Negotiation is disabled.)
5:0
Reserved
0, RO
Reserved by IEEE: Write ignored, read as 0.
Table 4. Basic Mode Status Register (BMSR) address 0x01
15
100BASE-T4
0, P
100BASE-T4 Capable:
0 = Device not able to perform 100BASE-T4 mode.
DP83865 does not support 100BASE-T4 mode and bit should always be read back as “0”.
14
13
www.national.com
100BASE-X
Full Duplex
1, P
100BASE-X
Half Duplex
1, P
100BASE-X Full Duplex Capable:
1 = Device able to perform 100BASE-X in Full Duplex mode.
100BASE-X Half Duplex Capable:
1 = Device able to perform 100BASE-X in Half Duplex mode.
22
DP83865
2.0 Register Block (Continued)
Table 4. Basic Mode Status Register (BMSR) address 0x01
12
10BASE-T
Full Duplex
1, P
11
10BASE-T
Half Duplex
1, P
100BASE-T2
Full Duplex
0, P
10
10BASE-T Full Duplex Capable:
1 = Device able to perform 10BASE-T in Full Duplex mode.
10BASE-T Half Duplex Capable:
1 = Device able to perform 10BASE-T in Half Duplex mode.
100BASE-T2 Full Duplex Capable:
0 = Device unable to perform 100BASE-T2 Full Duplex mode.
DP83865 does not support 100BASE-T2 mode and bit should always be read back as “0”.
9
100BASE-T2
Half Duplex
0, P
100BASE-T2 Half Duplex Capable:
0 = Device unable to perform 100BASE-T2 Half Duplex mode.
DP83865 does not support 100BASE-T2 mode and bit should always be read back as “0”.
8
1000BASE-T
Extended Status
1, P
7
Reserved
0, RO
6
Preamble
Suppression
1, P
Auto-Negotiation
Complete
0, RO
5
1000BASE-T Extended Status Register:
1 = Device supports Extended Status Register 0x0F.
Reserved by IEEE: Write ignored, read as 0.
Preamble suppression Capable:
1 = Device able to perform management transaction with preamble suppressed, 32-bits of preamble needed only once after reset, invalid opcode or invalid turnaround.
Auto-Negotiation Complete:
1 = Auto-Negotiation process complete, and contents of registers
5, 6, 7, & 8 are valid.
0 = Auto-Negotiation process not complete.
4
Remote Fault
0, RO, LH
Remote Fault:
1 = Remote Fault condition detected (cleared on read or by reset). Fault criteria: Far End Fault Indication or notification from
Link Partner of Remote Fault.
0 = No remote fault condition detected.
3
2
Auto-Negotiation
Ability
1, P
Link Status
0, RO, LL
Auto Configuration Ability:
1 = Device is able to perform Auto-Negotiation.
Link Lost Since Last Read Status:
1 = Link was good since last read of this register. (10/100/1000
Mbps operation).
0 = Link was lost since last read of this register.
The occurrence of a link failure condition will causes the Link Status bit to clear. Once cleared, this bit may only be set by establishing a good link condition and a read via the management
interface.
This bit doesn’t indicate the link status, but rather if the link was
lost since last read. For actual link status, either this register
should be read twice, or register 0x11 bit 2 should be read.
1
Jabber Detect
0, RO, LH
Jabber Detect: Set to 1 if 10BASE-T Jabber detected locally.
1 = Jabber condition detected.
0 = No Jabber.
0
Extended Capability
1, P
Extended Capability:
1 = Extended register capable.
23
www.national.com
DP83865
2.0 Register Block (Continued)
Table 5. PHY Identifier Register #1 (PHYIDR1) address 0x02
Bit
Bit Name
15:0
OUI[3:18]
Default
Description
16’b, P Bits 3 to 18 of the OUI (0x080017h) are stored in bits 15 to 0 of
this register. The most significant two bits of the OUI are ignored
(the IEEE standard refers to these as bits 1 and 2).
The PHY Identifier Registers #1 and #2 together form a unique identifier for the DP83865. The Identifier consists of a concatenation of the Organizationally Unique Identifier (OUI), the vendor’s model number and the model revision number. A
PHY may return a value of zero in each of the 32 bits of the PHY Identifier if desired. The PHY Identifier is intended to support network management. National’s IEEE assigned OUI is 0x080017h.
Table 6. PHY Identifier Register #2 (PHYIDR2) address 0x03
Bit
Bit Name
15:10
OUI[19:24]
Default
Description
6’b, P OUI Bits 19:24:
Bits 19 to 24 of the OUI (0x080017h) are mapped to bits 15 to 10
of this register respectively.
9:4
VNDR_MDL[5:0]
3:0
MDL_REV[3:0]
6’b , Vendor Model Number:
P
The six bits of vendor model number are mapped to bits 9 to 4
(most significant bit to bit 9).
4’b , P
Model Revision Number:
Four bits of the vendor model revision number are mapped to bits
3 to 0 (most significant bit to bit 3). This field will be incremented
for all major device changes.
Table 7. Auto-Negotiation Advertisement Register (ANAR) address 0x04
Bit
Bit Name
Default
15
NP
0, RW
Description
Next Page Indication:
1 = Next Page Transfer desired.
0 = Next Page Transfer not desired.
14
Reserved
0, RO
Reserved by IEEE: Writes ignored, Read as 0.
13
RF
0, RW
Remote Fault:
1 = Advertises that this device has detected a Remote Fault.
0 = No Remote Fault detected.
12
Reserved
0, RO
Reserved for Future IEEE use: Write as 0, Read as 0.
11
ASY_PAUSE
0, RW
Asymmetrical PAUSE:
1 = MAC/Controller supports Asymmetrical Pause direction.
0 = MAC/Controller does not support Asymmetrical Pause direction.
10
PAUSE
0, RW
PAUSE:
1 = MAC/Controller supports Pause frames.
0 = MAC/Controller does not support Pause frames.
9
100BASE-T4
0, RO
100BASE-T4 Support:
1 = 100BASE-T4 supported.
0 = No support for 100BASE-T4.
DP83865 does not support 100BASE-T4 mode and this bit
should always be read back as “0”.
www.national.com
24
DP83865
2.0 Register Block (Continued)
Table 7. Auto-Negotiation Advertisement Register (ANAR) address 0x04
Bit
Bit Name
8
100BASE-TX
Full Duplex
Default
Description
STRAP[1], RW 100BASE-TX Full Duplex Support:
1 = 100BASE-TX Full Duplex is supported by the local device.
0 = 100BASE-TX Full Duplex not supported.
The default value of this bit is determined by the combination of
the Duplex Enable and Speed[1:0] strap pins during reset/poweron IF Auto-Negotiation is enabled.
The advertised speed is determined by the Speed[1:0]:
Speed[1]
Speed[0]
Speeds Enabled
0
0
= 1000B-T, 100B-TX, 10B-T
0
1
= 1000B-T, 100B-TX
1
0
= 1000B-T
1
1
= 1000B-T, 10B-T
The advertised duplex mode is determined by Duplex Mode:
0 = Half Duplex
1 = Full Duplex
7
100BASE-TX
(Half Duplex)
STRAP[1], RW 100BASE-TX (Half Duplex) Support:
1 = 100BASE-TX (Half Duplex) is supported by the local device.
0 = 100BASE-TX (Half Duplex) not supported.
(The default value of this bit is determined by the combination of
the Duplex Enable and Speed[1:0] strap pins during reset/poweron IF Auto-Negotiation is enabled. See bit 8 for details.)
6
10BASE-T
Full Duplex
STRAP[1], RW 10BASE-T Full Duplex Support:
1 = 10BASE-T Full Duplex is supported.
0 = 10BASE-T Full Duplex is not supported.
(The default value of this bit is determined by the combination of
the Duplex Enable and Speed[1:0] strap pins during reset/poweron IF Auto-Negotiation is enabled. See bit 8 for details.)
5
10BASE-T
(Half Duplex)
STRAP[1], RW 10BASE-T (Half Duplex) Support:
1 = 10BASE-T (Half Duplex) is supported by the local device.
0 = 10BASE-T (Half Duplex) is not supported.
(The default value of this bit is determined by the combination of
the Duplex Enable and Speed[1:0] strap pins during reset/poweron IF Auto-Negotiation is enabled. See bit 8 for details.)
4:0
PSB[4:0]
5’b, P Protocol Selection Bits:
These bits contain the binary encoded protocol selector supported by this port. indicates that this device supports IEEE
802.3.
This register contains the advertised abilities of this device as they will be transmitted to its link partner during Auto-Negotiation.
25
www.national.com
DP83865
2.0 Register Block (Continued)
Table 8. Auto-Negotiation Link Partner Ability Register (ANLPAR) address 0x05
Bit
Bit Name
Default
15
NP
0, RO
Description
Next Page Indication:
0 = Link Partner does not desire Next Page Transfer.
1 = Link Partner desires Next Page Transfer.
14
ACK
0, RO
Acknowledge:
1 = Link Partner acknowledges reception of the ability data word.
0 = Not acknowledged.
The Device’s Auto-Negotiation state machine will automatically
control this bit based on the incoming FLP bursts. Software
should not attempt to write to this bit.
13
RF
0, RO
Remote Fault:
1 = Remote Fault indicated by Link Partner.
0 = No Remote Fault indicated by Link Partner.
12
Reserved
0, RO
Reserved for Future IEEE use: Write as 0, read as 0.
11
ASY_PAUSE
0, RO
Asymmetrical PAUSE:
1 = Link Partner supports Asymmetrical Pause direction.
0 = Link Partner does not support Asymmetrical Pause direction.
10
PAUSE
0, RO
PAUSE:
1 = Link Partner supports Pause frames.
0 = Link Partner does not support Pause frames.
9
100BASE-T4
0, RO
100BASE-T4 Support:
1 = 100BASE-T4 is supported by the Link Partner.
0 = 100BASE-T4 not supported by the Link Partner.
8
100BASE-TX
Full Duplex
0, RO
100BASE-TX
(Half Duplex)
0, RO
100BASE-TX Full Duplex Support:
1 = 100BASE-TX Full Duplex is supported by the Link Partner.
0 = 100BASE-TX Full Duplex not supported by the Link Partner.
7
100BASE-TX (Half Duplex) Support:
1 = 100BASE-TX (Half Duplex) is supported by the Link Partner.
0 = 100BASE-TX (Half Duplex) not supported by the Link Partner.
6
10BASE-T
Full Duplex
0, RO
10BASE-T Full Duplex Support:
1 = 10BASE-T Full Duplex is supported by the Link Partner.
0 = 10BASE-T Full Duplex not supported by the Link Partner.
5
10BASE-T
(Half Duplex)
0, RO
10BASE-T (Half Duplex) Support:
1 = 10BASE-T (Half Duplex) is supported by the Link Partner.
0 = 10BASE-T (Half Duplex) not supported by the Link Partner.
4:0
PSB[4:0]
5’b,
RO
Protocol Selection Bits:
Link Partners’s binary encoded protocol selector.
This register contains the advertised abilities of the Link Partner as received during Auto-Negotiation
www.national.com
26
DP83865
2.0 Register Block (Continued)
Table 9. Auto-Negotiate Expansion Register (ANER) address 0x06
Bit
Bit Name
Default
15:5
Reserved
0, RO
4
PDF
0, RO, LH
Description
Reserved by IEEE: Writes ignored, Read as 0.
Parallel Detection Fault:
1 = A fault has been detected via the Parallel Detection function.
0 = A fault has not been detected via the Parallel Detection function.
3
LP_NP Able
0, RO
Link Partner Next Page Able:
1 = Link Partner does support Next Page.
0 = Link Partner supports Next Page negotiation.
2
NP Able
1, RO
Next Page Able:
1 = Indicates local device is able to send additional “Next Pages”.
1
PAGE_RX
0, RO, LH
Link Code Word Page Received:
1 =Link Code Word has been received, cleared on read of this
register.
0 = Link Code Word has not been received.
0
LP_AN Able
0, RO
Link Partner Auto-Negotiation Able:
1 = Indicates that the Link Partner supports Auto-Negotiation.
0 = Indicates that the Link Partner does not support Auto-Negotiation.
This register contains additional Local Device and Link Partner status information.
Table 10. Auto-Negotiation Next Page Transmit Register (ANNPTR) address 0x07
Bit
Bit Name
Default
15
NP
1, RW
Description
Next Page Indication:
1 = Another Next Page desired.
0 = No other Next Page Transfer desired.
14
ACK
0, RO
Acknowledge:
1 = Acknowledge of 3 consecutive FLPs.
0 = No Link Code Word received.
13
MP
1, RW
Message Page:
1 = Message Page.
0 = Unformatted Page.
12
ACK2
0, RW
Acknowledge2:
1 = Will comply with message.
0 = Cannot comply with message.
Acknowledge2 is used by the next page function to indicate that
Local Device has the ability to comply with the message received.
27
www.national.com
DP83865
2.0 Register Block (Continued)
Table 10. Auto-Negotiation Next Page Transmit Register (ANNPTR) address 0x07
Bit
Bit Name
Default
11
TOG_TX
0, RO
Description
Toggle:
1 = Value of toggle bit in previously transmitted Link Code Word
was logic 0.
0 = Value of toggle bit in previously transmitted Link Code Word
was logic 1.
Toggle is used by the Arbitration function within Auto-Negotiation
to ensure synchronization with the Link Partner during Next Page
exchange. This bit shall always take the opposite value of the
Toggle bit in the previously exchanged Link Code Word.
10:0
CODE[10:0]
11’b, RW
If the MP bit is set (bit 13 of this register), then the code shall be
interpreted as a "Message Page”, as defined in annex 28C of
IEEE 802.3u. Otherwise, the code shall be interpreted as an "Unformatted Page”, and the interpretation is application specific.
The default value of the CODE represents a Null Page as defined
in Annex 28C of IEEE 802.3u.
This register contains the next page information sent by this device to its Link Partner during Auto-Negotiation.
Table 11. Auto-Negotiation Next Page Receive Register (ANNPRR) address 0x08
Bit
Bit Name
Default
15
NP
0, RO
Description
Next Page Indication:
1 = Another Next Page desired.
0 = No other Next Page Transfer desired.
14
ACK
0, RO
Acknowledge:
1 = Link Partner acknowledges reception of the next page.
0 = Not acknowledged.
13
MP
0, RO
Message Page:
1 = Message Page.
0 = Unformatted Page.
12
ACK2
0, RO
Acknowledge2:
1 = Link Partner will comply with message.
0 = Cannot comply with message.
Acknowledge2 is used by the next page function to indicate that
the Link Partner has the ability to comply with the message received.
www.national.com
28
DP83865
2.0 Register Block (Continued)
Table 11. Auto-Negotiation Next Page Receive Register (ANNPRR) address 0x08
Bit
Bit Name
Default
11
TOG_RX
0, RO
Description
Toggle:
1 = Value of toggle bit in previously transmitted Link Code Word
was logic 0.
0 = Value of toggle bit in previously transmitted Link Code Word
was logic 1.
Toggle is used by the Arbitration function within Auto-Negotiation
to ensure synchronization with the Link Partner during Next Page
exchange. This bit shall always take the opposite value of the
Toggle bit in the previously exchanged Link Code Word.
10:0
CODE[10:0]
11’b, RO If the MP bit is set (bit 13 of this register), then the code shall be
interpreted as a "Message Page”, as defined in annex 28C of
IEEE 802.3u. Otherwise, the code shall be interpreted as an "Unformatted Page”, and the interpretation is application specific.
The default value of the CODE represents a Reserved for future
use as defined in Annex 28C of IEEE 802.3u.
This register contains the next page information sent by its Link Partner during Auto-Negotiation.
Table 12. 1000BASE-T Control Register (1KTCR) address 0x09
Bit
Bit Name
Default
15:13
Test Mode
0, RW
Description
Test Mode Select:
bit 15
bit 14
bit 13
1
0
0
= Test Mode 4
Test Mode Selected
0
1
1
= Test mode 3
0
1
0
= Test Mode 2
0
0
1
= Test Mode 1
0
0
0
= Normal Operation
See IEEE 802.3ab section 40.6.1.1.2 “Test modes” for more information. Output for TX_TCLK when in Test Mode is on pin 6.
12
Master / Slave
Manual Config.
Enable
0, RW
Enable Manual Master / Slave Configuration:
1 = Enable Manual Master/Slave Configuration control.
0 = Disable Manual Master/Slave Configuration control.
Using the manual configuration feature may prevent the PHY
from establishing link in 1000Base-T mode if a conflict with the
link partner’s setting exists.
11
Master / Slave
Config. Value
0, RW
Manual Master / Slave Configuration Value:
1 = Set PHY as MASTER when register 09h bit 12 = 1.
0 = Set PHY as SLAVE when register 09h bit 12 = 1.
Using the manual configuration feature may prevent the PHY
from establishing link in 1000Base-T mode if a conflict with the
link partner’s setting exists.
10
Repeater / DTE
STRAP[0], RW Advertise Device Type: Multi or single port
1 = Repeater or Switch.
0 = DTE.
(The default value of this bit is = to the strap value of pin 94 during
reset/power-on IF Auto-Negotiation is enabled.)
29
www.national.com
DP83865
2.0 Register Block (Continued)
Table 12. 1000BASE-T Control Register (1KTCR) address 0x09
Bit
Bit Name
9
1000BASE-T
Full Duplex
Default
Description
STRAP[1], RW Advertise 1000BASE-T Full Duplex Capable:
1 = Advertise DTE as 1000BASE-T Full Duplex Capable.
0 = Advertise DTE as not 1000BASE-T Full Duplex Capable.
(The default value of this bit is determined by the combination of
the Duplex Enable and Speed[1:0] strap pins during reset/poweron IF Auto-Negotiation is enabled. See register 0x04 bit 8 for details.)
8
1000BASE-T
Half Duplex
STRAP[1], RW Advertise 1000BASE-T Half Duplex Capable:
1 = Advertise DTE as 1000BASE-T Half Duplex Capable.
0 = Advertise DTE as not 1000BASE-T Half Duplex Capable.
(The default value of this bit is determined by the combination of
the Duplex Enable and Speed[1:0] strap pins during reset/poweron IF Auto-Negotiation is enabled. See register 0x04 bit 8 for details.)
7:0
Reserved
0, RW
Reserved by IEEE: Writes ignored, Read as 0.
Table 13. 1000BASE-T Status Register (1KSTSR) address 0x0A (10’d)
Bit
Bit Name
Default
15
Master / Slave
Manual Config. Fault
0, RO, LH, SC
Description
MASTER / SLAVE manual configuration fault detected:
1 = MASTER/SLAVE manual configuration fault detected.
0 = No MASTER/SLAVE manual configuration fault detected.
14
Master / Slave
Config. Resolution
0, RO
MASTER / SLAVE Configuration Results:
1 = Configuration resolved to MASTER.
0 = Configuration resolved to SLAVE.
13
Local Receiver
Status
0, RO
Local Receiver Status:
1 = OK.
0 = Not OK.
12
Remote Receiver
Status
0, RO
LP 1000BASE-T
Full Duplex
0, RO
Remote Receiver Status:
1 = OK.
0 = Not OK.
11
Link Partner 1000BASE-T Full Duplex:
1 = Link Partner capable of 1000BASE-T Full Duplex.
0 = Link Partner not capable of 1000BASE-T Full Duplex.
10
LP 1000BASE-T
Half Duplex
0, RO
Link Partner 1000BASE-T Half Duplex:
1 = Link Partner capable of 1000BASE-T Half Duplex.
0 = Link Partner not capable of 1000BASE-T Half Duplex.
9:8
Reserved
0, RO
7:0
IDLE ErrorCount[7:0]
0, RO, SC
Reserved by IEEE: Write ignored, read as 0.
IDLE Error Count
This register provides status for 1000BASE-T link.
Note: Registers 0x0B - 0x0E are Reserved by IEEE.
www.national.com
30
DP83865
2.0 Register Block (Continued)
Table 14. 1000BASE-T Extended Status Register (1KSCR) address 0x0F (15’d)
Bit
Bit Name
Default
15
1000BASE-X
Full Duplex
0, P
Description
1000BASE-X Full Duplex Support:
1 = 1000BASE-X is supported by the local device.
0 = 1000BASE-X is not supported.
DP83865 does not support 1000BASE-X and bit should always
be read back as “0”.
14
1000BASE-X
Half Duplex
0, P
1000BASE-X Half Duplex Support:
1 = 1000BASE-X is supported by the local device.
0 =1000BASE-X is not supported.
DP83865 does not support 1000BASE-X and bit should always
be read back as “0”.
13
1000BASE-T
Full Duplex
1, P
1000BASE-T Full Duplex Support:
1 = 1000BASE-T is supported by the local device.
0 =1000BASE-T is not supported.
12
1000BASE-T
Half Duplex
1, P
Reserved
0, RO
1000BASE-T Half Duplex Support:
1 = 1000BASE-T is supported by the local device.
0 =1000BASE-T is not supported.
11:0
Reserved by IEEE: Write ignored, read as 0.
Table 15. Strap Option Register (STRAP_REG) address 0x10 (16’d)
Bit
Bit Name
15
AN Enable
14
Duplex Mode
13:12
Speed[1:0]
11
Reserved
10
NC Mode Enable
9
Reserved
Default
Description
STRAP[1], RO Auto-Negotiation Enable: Pin 10. Default value for bit 12 of register 0x00.
STRAP[1], RO Duplex Mode: Pin 9. Default value for bit 8 of register 0x00.
STRAP[00], RO Speed Select: Pins 8 and 7. Default value for bits 6 and 13 of register 0x00.
0, RO
Write as 0, ignore on read.
STRAP[0], RO Non-Compliant Mode: Pin 1. Default value for bit 9 of register
0x12.
0, RO
Write as 0, ignore on read.
0, RO
Write as 0, ignore on read.
8
Reserved
7
MAC Clock Enable
6
MDIX Enable
STRAP[1], RO Auto MDIX Enable: Pin 89. Default value for bit 15 of register
0x12.
5
Multi Enable
STRAP[0], RO Multi Port Enable: Pin 94. Default value for bit 10 of register
0x09.
4:0
PHYADDR[4:0]
STRAP[1], RO MAC Clock Output Enable: Pin 88.
STRAP[0_0001], PHY Address: Pins 95, 18, 17,14, 13. Default for bits 4:0 of regRO
ister 0x1F.
This register summarizes all the strap options. These can only be changed through restrapping and resetting the PHY.
31
www.national.com
DP83865
2.0 Register Block (Continued)
Table 16. Link and Auto-Negotiation Status Register (LINK_AN) address 0x11 (17’d)
Bit
Bit Name
Default
Description
15:12
TP Polarity[3:0]
0, RO
Twisted Pair Polarity Status: Indicates a polaritiy reversal on
pairs A to D ([15:12]). The PHY automatically detects this condition and adjusts for it.
1 = polarity reversed
0 = normal operation
11
Reserved
0, RO
(Power Down Status)
10
MDIX Status
Write as 0, ignore on read.
This bit is set to indicate that the PHY is in power down mode.
0, RO
MDIX Status: Indicates whether the PHY’s MDI is in straight or
cross-over mode.
1 = Cross-over mode
0 = Straight mode
9
FIFO Error
0, RO
Transmit FIFO Error: Indicates whether a FIFO overflow or underrun has occured. This bit is cleared every time link is lost.
1 = FIFO error occured
0 = normal operation
8
Reserved
0, RO
Write as 0, ignore on read.
7
Shallow Loopback
Status
0, RO
Shallow Loopback Status: (As set by bit 5, register 0x12)
Deep Loopback
Status
0, RO
Non-Compliant
Mode Status
0, RO
6
5
4:3
2
Speed[1:0] Status
Link Status
1 = The PHY operates in shallow loopback mode
0 = Normal operation
Deep Loopack Status: (As set by bit 14, register 0x00)
1 = The PHY operates in deep loopback mode
0 = Normal operation
Non-compliant Mode Status:
‘1’ detects only in non-compliant mode
‘0’ detects in both IEEE compliant and non-compliant mode
STRAP[00], RO Speed Resolved: These two bits indicate the speed of operation
as determined by Auto-negotiation or as set by manual configuration.
0, RO
Speed[1]
Speed[0]
Speed of operation
1
0
= 1000 Mbps
0
1
= 100 Mbps
0
0
= 10 Mbps
1
1
= reserved
Link status:
1 = indicates that a good link is established
0 = indicates no link.
1
Duplex Status
0, RO
Duplex status:
1 = indicates that the current mode of operation is full duplex
0 = indicates that the current mode of operation is half duplex
0
Master / Slave
Config. Status
0, RO
Master / Slave Configuration Status:
1 = PHY is currently in Master mode
0 = PHY is currently in Slave mode
www.national.com
32
DP83865
2.0 Register Block (Continued)
Table 17. Auxiliary Control Register (AUX_CTRL) address 0x12 (18’d)
Bit
Bit Name
15
Auto-MDIX Enable
Default
Description
STRAP[1], RW Automatic MDIX: Indicates (sets) whether the PHY’s capability
to automatically detect swapped cable pairs is used.
1 = Automatic MDIX mode, bit 14 is ignored
0 = Manual MDIX mode
Note: This bit is ignored and the setting of bit 14 applies if AutoNegotiation is disabled (AN_EN = 0). Bit 10 of register 0x11
should always be checked for the actual status of MDI/MDIX operation.
14
Manual MDIX Value
STRAP[0], RW Manual MDIX Value: If Manual MDIX mode is selected (AutoMDIX selection is disabled, bit 15 = 0) this bit sets the MDIX
mode of operation. If the PHY is in Auto-MDIX mode this bit has
no effect.
1 = cross-over mode (channels A and B are swapped)
0 = straight mode
Note: Bit 10 of register 0x11 should always be checked for the actual status of MDI/MDIX operation.
13:12
RGMII_EN[1:0]
STRAP[0]
RGMII ENABLE: These two bits enables RGMII mode or
MII/GMII mode.
RGMII_EN[1:0]
11 = RGMII - 3COM mode
10 = RGMII - HP mode
01 = GMII mode
00 = GMII mode
11:10
9
Reserved
0, RO
Write as 0, ignore on read.
Non-Compliant Mode STRAP[0], RW Non-Compliant Mode Enable: This bit enables the PHY to work
in non-IEEE compliant mode. This allows interoperabilty with certain non-IEEE compliant 1000BASE-T tranceivers.
1 = enables IEEE compliant operation and non-compliant operation
0 = enables IEEE compliant operation but inhibits non-compliant
operation
8
RGMII InBand
Status Enable
0, RW
RGMII InBand Status Enable:
1 = RGMII InBand Status enabled.
0 = RGMII InBand Status disabled.
When InBand Status is enabled, PHY places link status, speed,
and duplex mode information on RXD[3:0] between the data
frames. The InBand Status may ease the MAC layer design.
Note that this bit has no impact if bit 13 = 0.
7
TX_TCLK Enable
0, RW
TX_TCLK Enable: This bit enables the TX_TCLK (pin 6) output
during the IEEE 1000BASE-T test modes.
1 = TX_TCLK ouput enabled during IEEE test modes
0 = No TX_TCLK output (default)
6
TX_Trigger_Syn
Enable
0, RW
TX_TRIGGER and TX_SYNC Enable: This bit enables the
TX_SYNC_CLK (pin 88) and TX_TRIGGER (pin 94) output during the IEEE 1000BASE-T modes. These signals are not required
by IEEE to perform the tests, but will help to take measurements.
0 = No signal output
1 = Signal are output during IEEE test modes
Note: TX_SYN_CLK and TX_TRIGGER are only available in test
mode 1 and 4
TX_SYN_CLK = TX_TCLK / 4 in test mode 1
TX_SYN_CLK = TX_TCLK / 6 in test mode 4
33
www.national.com
DP83865
2.0 Register Block (Continued)
Table 17. Auxiliary Control Register (AUX_CTRL) address 0x12 (18’d)
Bit
Bit Name
Default
Description
5
Shallow Deep Loopback
Enable
0, RW
Shallow Deep Loopack Enable: (Loopback status bit 7, register
0x11)
This bit places PHY in the MAC side loopback mode. Any packet
entering into TX side appears on the RX pins immediately. This
operation bypasses all internal logic and packet does not appear
on the MDI interface.
1 = The PHY operates in shallow deep loopback mode
0 = Normal operation
4
X_Mac
0, RW
Reverse GMII Data Bit Order:
Setting this bit will reverse the pins of the TXD and RXD on the
GMII interface, respectively.
1 = TXD[7:0]=>TXD[0:7], RXD[7:0]=>RXD[0:7]
0 = Normal operation
3:1
Reserved
0, RO
Write as 0, ignore on read.
0
Jabber Disable
0, RW
Jabber Disable: (Only in 10BASE-T mode) If this bit is set the
PHY ignores all jabber conditions.
1 = disable jabber function
0 = normal operation
Table 18. LED Control Register (LED_CTRL) address 0x13 (19’d)
Bit
Bit Name
Default
15:14
Activity LED
0, RW
Description
Activity LED: This LED is active when the PHY is transmitting
data, receiving data, or detecting idle error.
The following modes are available for the ACT LED:
00 = Register controlled 0x13.3:0
01 = Forced off
10 = Blink mode (blink rate approx. 750 ms)
11 = Forced on
Note: Only in normal mode (00) LEDs reflect the actual status of
the PHY. All other modes force the driver to a permanent on, off
or blinking state.
13:12
Link10 LED
0, RW
10BASE-T Link LED: This LED is active when the PHY is linked
in 10BASE-T mode.
The following modes are available for LEDs:
00 = Normal (default)
01 = Forced off
10 = Blink mode (blink rate approx. 750 ms)
11 = Forced on
Note: Only in normal mode (00) LEDs reflect the actual status of
the PHY. All other modes force the driver to a permanent on, off
or blinking state.
11:10
Link100 LED
0, RW
100BASE-TX Link LED: This LED is active when the PHY is
linked in 100BASE-TX mode. See Activity LED for other settings.
9:8
Link1000 LED
0, RW
1000BASE-T Link LED: This LED is active when the PHY is
linked in 1000BASE-T mode. See Activity LED for other settings.
7:6
Duplex LED
0, RW
Duplex LED: This LED is active when the PHY has established
a link in Full Duplex mode. See Activity LED for other settings.
www.national.com
34
DP83865
2.0 Register Block (Continued)
Table 18. LED Control Register (LED_CTRL) address 0x13 (19’d)
Bit
Bit Name
Default
Description
5
reduced LED enable
0, RW
Reduced LED Mode Enable: This bit enables the reduced LED
(RLED) mode that is different from the normal five-LED mode. In
the RLED Mode, 10M Link LED is changed to link LED or Link
and activity combined LED.
When reg 0x13.5 is enabled:
Reg 0x1A.0 = 1 - 10M Link LED displays 10/100/1000 Link
Reg 0x1A.0 = 0 - 10M LED displays 10/100/1000 Link and ACT
Note: In Link mode, the LED is steady on. In Link/ACT mode,
LED is steady on when link is achieved, and LED blinks when
there is link and activity.
4
led_on_crc
0, RW
3
led_on_ie
0, RW
2
an_fallback_an
0, RW
1
an_fallback_crc
0, RW
0
an_fallback_ie
0, RW
Table 19. Interrupt Status Register (INT_STATUS) address 0x14 (20’d)
Bit
Bit Name
Default
Description
15
spd_cng_int
0, RO
Speed Change: Asserted when the speed of a link changes.
14
lnk_cng_int
0, RO
Link Change: Asserted when a link is established or broken.
13
dplx_cng_int
0, RO
Duplex Change: Asserted when the duplex mode of a link
changes.
12
mdix_cng_int
0, RO
MDIX Change: Asserted when the MDIX status changes, i.e. a
pair swap occured.
11
pol_cng_int
0, RO
Polarity Change: Asserted when the polarity of any channel
changes.
10
prl_det_flt_int
0, RO
Parallel Detection Fault: Asserted when a parallel detectin fault
has been detected.
9
mas_sla_err_int
0, RO
Master / Slave Error: Asserted when the Master / Slave configuration in 1000BASE-T mode could not be resolved.
8
no_hcd_int
0, RO
No HCD: Asserted when Auto-Negotiation could not determine a
Highest Common Denominator.
7
no_lnk_int
0, RO
No Link after Auto-Negotiation: Asserted when Auto-Negotiation has been completed successfully and no link could be established.
6
jabber_cng_int
0, RO
Jabber Change: Asserted in 10BASE-T mode when a Jabber
condition has occured or has been cleared.
5
nxt_pg_rcvd_int
0, RO
Next Page Received: Asserted when a Next Page has been received.
4
an_cmpl_int
0, RO
Auto-negotiation complete: Asserted when Auto-Negotiation
has been completed.
3
rem_flt_cng_int
0, RO
Remote Fault Change: Asserted when the remote fault status
changes.
2:0
Reserved
0, RO
Write as 0, ignore on read.
35
www.national.com
DP83865
2.0 Register Block (Continued)
Table 20. Interrupt Mask Register (INT_MASK) address 0x15 (21’d)
Bit
Bit Name
Default
Description
15
spd_cng_int_msk
0, RW
Setting this bit activates the spd_cng_int interrupt. The interrupt
is masked if the bit is cleared.
14
lnk_cng_int_msk
0, RW
Setting this bit activates the lnk_cng_int interrupt. The interrupt is
masked if the bit is cleared.
13
dplx_cng_int_msk
0, RW
Setting this bit activates the dplx_cng_int interrupt. The interrupt
is masked if the bit is cleared.
12
mdix_cng_int_msk
0, RW
Setting this bit activates the mdix_cng_int interrupt. The interrupt
is masked if the bit is cleared.
11
pol_cng_int_msk
0, RW
Setting this bit activates the pol_cng_int interrupt. The interrupt is
masked if the bit is cleared.
10
prl_det_flt_int_msk
0, RW
Setting this bit activates the prl_det_flt_int interrupt. The interrupt
is masked if the bit is cleared.
9
mas_sla_err_int_msk
0, RW
Setting this bit activates the mas_sla_err_int interrupt. The interrupt is masked if the bit is cleared.
8
no_hcd_int_msk
0, RW
Setting this bit activates the no_hcd_int interrupt. The interrupt is
masked if the bit is cleared.
7
no_lnk_int_msk
0, RW
Setting this bit activates the no_lnk_int interrupt. The interrupt is
masked if the bit is cleared.
6
jabber_cng_int_msk
0, RW
Setting this bit activates the jabber_cng_int interrupt. The interrupt is masked if the bit is cleared.
5
nxt_pg_rcvd_int_msk
0, RW
Setting this bit activates the nxt_pg_rcvd_int interrupt. The interrupt is masked if the bit is cleared.
4
an_cmpl_int_msk
0, RW
Setting this bit activates the an_cmpl_int interrupt. The interrupt
is masked if the bit is cleared.
3
rem_flt_cng_int_msk
0, RW
Setting this bit activates the rem_flt_cng_int interrupt. The interrupt is masked if the bit is cleared.
2:0
Reserved
0, RO
Write as 0, ignore on read.
Table 21. Expanded Memory Access Control (Exp_mem_ctl) address 0x16 (22’d)
Bit
Bit Name
Default
15
Global Reset
0, RW, SC
Description
Global Reset:
This bit resets the entire chip.
14:8
Reserved
0, RO
Write as 0, ignore on read.
7
Broadcast Enable
0, RW
Broadcast Enable:
1 = Respond to broadcast write at MDIO address 0
0 = Respond to MDIO address set in register 0x1F.4:0
6:2
Reserved
0, RO
1:0
Address Control
[11], RW
Write as 0, ignore on read.
Address Control:
00 = 8-bit expanded memory read/write (auto-incr disabled)
01 = 8-bit expanded memory read/write (auto-incr enabled)
10 = 16-bit expanded memory read/write (auto-incr enabled)
11 = 8-bit expanded memory write-only (auto-incr disabled)
www.national.com
36
DP83865
2.0 Register Block (Continued)
Table 22. Interrupt Clear Register (INT_CLEAR) address 0x17 (23’d)
Bit
Bit Name
Default
Description
15
spd_cng_int_clr
0, RW, SC
Setting this bit clears the spd_cng_int interrupt.
14
lnk_cng_int_clr
0, RW, SC
Setting this bit clears the lnk_cng_int interrupt.
13
dplx_cng_int_clr
0, RW, SC
Setting this bit clears the dplx_cng_int interrupt.
12
mdix_cng_int_clr
0, RW, SC
Setting this bit clears the mdix_cng_int interrupt.
11
pol_cng_int_clr
0, RW, SC
Setting this bit clears the pol_cng_int interrupt.
10
prl_det_flt_int_clr
0, RW, SC
Setting this bit clears the prl_det_flt_int interrupt.
9
mas_sla_err_int_clr
0, RW, SC
Setting this bit clears the mas_sla_err_int interrupt.
8
no_hcd_int_clr
0, RW, SC
Setting this bit clears the no_hcd_int interrupt.
7
no_lnk_int_clr
0, RW, SC
Setting this bit clears the no_lnk_int interrupt.
6
jabber_cng_int_clr
0, RW, SC
Setting this bit clears the jabber_cng_int interrupt.
5
nxt_pg_rcvd_int_clr
0, RW, SC
Setting this bit clears the nxt_pg_rcvd_int interrupt.
4
an_cmpl_int_clr
0, RW, SC
Setting this bit clears the an_cmpl_int interrupt.
3
rem_flt_cng_int_clr
0, RW, SC
Setting this bit clears the rem_flt_cng_int interrupt.
2:0
Reserved
0, RO
Write as 0, ignore on read.
Table 23. BIST Counter Register (BIST_CNT) address 0x18 (24’d)
Bit
Bit Name
Default
Description
15:0
BIST Counter
0, RO
BIST Counter: This register counts receive packets or receive
errors according to bit 15 in register BIST_CFG1. It shows either
the upper or lower 16 bit of a 32 bit value which can be selected
through bit 14 in register BIST_CFG2.
Table 24. BIST Configuration Register 1 (BIST_CFG1) address 0x19 (25’d)
Bit
Bit Name
Default
15
bist_cnt_type
0, RW
Description
Set BIST Counter Type:
1 = BIST_CNT counts receive CRC errors
0 = BIST_CNT counts receive packets
14
bist_cnt_clr
0, RW, SC
13
tx_bist_pak_len
0, RW
BIST Counter Clear: Setting this bit clears the BIST_CNT register to 0.
Transmit BIST Packet Length:
1 = 1514 bytes
0 = 60 bytes
12
tx_bist_ifg
0, RW
Transmit BIST Interframe Gap: This bit sets the IFG for transmit
BIST packets.
1 = 9.6 us
0 = 0.096us
11
tx_bist_en
0, RW, SC
Transmit BIST Enable: This bit starts the transmit BIST. The
number of selected packets or a continous data stream is sent out
when set. This bit self-clears after the packets have been sent.
1 = Transmit BIST enabled
0 = Transmit BIST disabled
37
www.national.com
DP83865
2.0 Register Block (Continued)
Table 24. BIST Configuration Register 1 (BIST_CFG1) address 0x19 (25’d)
Bit
Bit Name
Default
10
tx_bist_pak_type
0, RW
Description
Transmit BIST Packet Type:
1 = PSR9
0 = User defined packet
9:8
Reserved
0, RO
Write as 0, ignore on read.
7:0
tx_bist_pak
0, RW
User Defined Packet Content: This field sets the packet content
for the transmit BIST packets if the user defined packet type in bit
10 is selected.
Table 25. BIST Configuration Register 2 (BIST_CFG2) address 0x1A (26’d)
Bit
Bit Name
Default
Description
15
rx_bist_en
0, RW
Receive BIST Enable: This bit enables the receive BIST
counter. The BIST counter operation does not interfere with normal PHY operation.
0 = BIST counter disabled
1 = BIST counter enabled
14
bist_cnt_sel
0, RW
BIST Counter Select: This bit selects whether the upper or lower
16 bit of the 32 bit counter value are shown in the BIST_CNT register.
0 = displays lower 16 bit
1 = displays upper 16 bit
13:11
tx_bist_pak_cnt
0, RW
Transmit BIST Packet Count: Sets the number of transmit packets
000 = continuous transmit
001 = 1 packet
010 = 10 packets
011 = 100 packets
100 = 1,000 packets
101 = 10,000 packets
110 = 100,000 packets
111 = 10,000,000 packets
10:1
Reserved
0, RO
Write as 0, ignore on read.
0
Link/Link-ACT sel
0, RW
Link/Link-ACT Select: This bit has no impact when Reg 0x13.5
= 0.
1 = LINK only
0 = Combined Link/ACT
Note:
Registers 0x1B and 0x1C are reserved.
Table 26. Expanded Memory Data Register (Exp_mem_data) address 0x1D (29’d)
Bit
Bit Name
Default
Description
15:0
Expanded Memory
Data
0, RW
Expanded Memory Data: Data to be written to or read from expanded memory. Note that in 8-bit mode, the data resides at the
LSB octet of this register.
Table 27. Expanded Memory Address Register (Exp_mem_addr) address 0x1E (30’d)
Bit
Bit Name
Default
Description
15:0
Expanded Memory
Address
0, RW
Expanded Memory Address: Pointer to the address in expanded memory. The pointer is 16-bit wide.
www.national.com
38
DP83865
2.0 Register Block (Continued)
Table 28. PHY Support Register #2 (PHY_SUP) address 0x1F (31’d)
Bit
Bit Name
Default
15:5
Reserved
0, RO
4:0
PHY Address
Description
Write as 0, ignore on read.
STRAP[0_0001], PHY Address: Defines the port on which the PHY will accept SeRW
rial Management accesses.
39
www.national.com
DP83865
3.0 Configuration
This section includes information on the various configuration options available with the DP83865. The configuration
options include:
There are three registers used for accessing the expanded
memory. The Expanded Memory Access Control resiger
(0x16) sets up the memory access mode, for example, 8bit or 16-bit data addess, enable or disable automatic
address increment after each access, and read/write or
write-only opeation. The Expanded Memory Address
pointer register (0x1E) pionts the location of the expanded
memory to be accessed. The Expanded Memory Data
(0x1D) register contains the data read from or write to the
expanded memory.
— Accessing expanded memory space
— Manual configuration
– Speed / Duplex selection
– Forced Master / Slave
— Auto-Negotiation
– Speed / Duplex selection
– Gigabit speed fallback
– Gigabit retry forced link
– Master / Slave resolution
– Next Page support
– Parallel Detection
– Pause and Asymmetrical Pause resolution
– Restart Auto-Negotiation
– Auto-Negotiation complete time
— Auto-Negotiation register set
— Auto-MDIX configuration
— Automatic polarity correction
— PHY address and LEDs
— Reduced LED mode
— Modulate LED on error
— MII / GMII / RGMII MAC interfaces
— Clock to MAC output
— MII / GMII /RGMII isolate mode
— Loopback mode
— IEEE 802.3ab test modes
— Interrupt
— Power down modes
— Low power mode
— BIST usage
— Cable length indicator
— 10BASE-T HDX loopback disable
— I/O Voltage Selection
— Non-compliant interoperability mode
The DP83865 supports six different Ethernet protocols:
10BASE-T Full Duplex and Half Duplex, 100BASE-TX
Full Duplex and Half Duplex, 1000BASE-T Full Duplex and
Half Duplex. There are three ways to select the speed and
duplex modes, i.e. manual configuration with external
strapping options or through management register write
and Auto-Negotiation.
Note that the order of the writes to these registers is important. While register 0x1E points to the internal expanded
address and register 0x1D contains the data to be written
to or read from the expanded memory, the contents of register 0x1E automatically increments after each read or
write to data register 0x1D when auto-increment is
selected. Therefore, if data write need to be confirmed,
address register 0X1E should be reloaded with the original
address before reading from data register 0X1D (when
auto-increment is selected).
The expanded memory space data is 8-bit wide. In the 8-bit
read/write mode, the LSB 8 bits of the data register
0x1D.7:0 is mapped to the expanded memory.
The following is an example of step-by-step precedure
enabling the Speed Fallback mode:
— 1) Power down the DP83865 by setting register 0x00.11
= 1. This is to ensure that the memory access does not
interfere with the normal operation.
— 2) Write to register 0x16 the value 0x0000. This allows
access to expanded memory for 8-bit read/write.
— 3) Write to register 0x1E the value 0x1C0.
— 4) Write to register 0x1D the value 0x0008.
— 5) Take the out of power down mode by resetting register
0x00.11.
3.2 Manual Configuration
For manual configuration of the speed and the duplex
modes (also referred to as forced mode) , the Auto-Negotiation function has to be disabled. This can be done in two
ways. Strapping Auto-Negotiation Enable (AN_EN) pin low
disables the Auto-Negotiation. Auto-Negotiation can also
be disabled by writing a “0” to bit 12 of the BMCR 0x00 to
override the strapping option.
It should be noted that manual 1000BASE-T mode is not
supported by IEEE. The DP83865, when in manual
1000BASE-T mode, only communicates with another
National PHY. The manual 1000BASE-T mode is designed
for test purposes only.
3.2.1 Speed/Duplex Selection
3.1 Accessing Expanded Memory Space
In Manual mode, the strapping value of the SPEED[1:0]
pins is used to determine the speed, and the strap value of
the DUPLEX pin is used to determine duplex mode.
The 32 IEEE base page registers limits the number of functions and features to be accessed. The advanced proprietary features are implemented in the register located in
the expanded memory space. The following are features
and functions require access to expanded memory space:
—
—
—
—
For all of the modes above, the DUPLEX strap value “1”
selects Full Duplex (FD), while “0” selects Half Duplex
(HD). The strap values are latched on during power-on
reset and can be overwritten by access to the BMCR register 0x00 bits 13,12, 8 and 6.
Gigabit Speed Fallback
Gigabit Retry Forced Link
Cable length indicator
10BASE-T HDX loopback
www.national.com
40
DP83865
3.0 Configuration (Continued)
.
Table 29. Speed/Duplex Selection, AN_EN = 0
DUPLEX SPEED[1] SPEED[0]
Manual Mode
0
0
0
10BASE-T HD
0
0
1
100BASE-TX HD
0
1
0
1000BASE-T HD
(Between National
PHYs only)
0
1
1
Reserved
1
0
0
10BASE-T FD
1
0
1
100BASE-TX FD
1
1
0
1000BASE-T FD
(Between National
PHYs only)
1
1
1
Table 31. Master/Slave Resolution, AN_EN = 0
Reserved
3.2.2 Master/Slave
Slave mode
Master mode
Link Partner
Outcome
Manual
Master
Manual
Master
Unresolved
No Link
Unresolved
No Link
Manual
Master
Manual
Slave
Master
Slave
Manual
Master
Multi-node
(Auto-neg)
Master
Slave
Manual
Master
Single-node
(Auto-neg)
Master
Slave
Manual
Slave
Manual
Master
Slave
Master
Manual
Slave
Manual
Slave
Unresolved
No Link
Unresolved
No Link
Manual
Slave
Multi-node
(Auto-neg)
Slave
Master
Manual
Slave
Single-node
(Auto-neg)
Slave
Master
3.3.1 Speed/Duplex Selection - Priority Resolution
The Auto-Negotiation function provides a mechanism for
exchanging configuration information between the two
ends of a link segment. This mechanism is implemented by
exchanging Fast Link Pulses (FLP). FLP are burst pulses
that provide the signalling used to communicate the abilities between two devices at each end of a link segment.
For further details regarding Auto-Negotiation, refer to
Clause 28 of the IEEE 802.3u specification. The DP83865
supports six different Ethernet protocols: 10BASE-T Full
Duplex, 10BASE-T Half Duplex, 100BASE-TX Full Duplex,
100BASE-TX Half Duplex, 1000BASE-T Full Duplex, and
1000BASE-T Half Duplex. The process of Auto-Negotiation
ensures that the highest performance protocol is selected
(i.e., priority resolution) based on the advertised abilities of
the Link Partner and the local device. (Table 33)
Manual Mode
1
DP83865
Outcome
— Next Page
— Parallel Detection for 10/100 Mbps
— Restart Auto-Negotiation through software
Table 30. 1000BASE-T Master/Slave Sel., AN_EN = 0
0
Link Partner
Advertise
The DP83865 also supports features such as:
In 1000BASE-T the two link partner devices have to be
configured, one as Master and the other as Slave. The
Master device by definition uses a local clock to transmit
data on the wire; the Slave device uses the clock recovered of the incoming data from the link partner for transmitting its data. The Master and Slave assignments can be
manually set by using strapping options or register writes.
When the AN_EN pin is strapped low, strapping MULTI_EN
pin low selects Slave and high selects Master mode. Register 9 bits 12:11 allows software to overwrite the strapping
Master/Slave setting (Table 30). Note that if both the link
partner and the local device are manually given the same
Master/Slave assignment, an error will occur as indicated
in 1KSTSR 0x0A bit 15.
MULTI_EN
DP83865
Advertise
.
Depending on what the link partner is configured to, the
manual Master/Slave mode can be resolved to eight possible outcomes. Only two National PHYs will be able to link
to each other in manual configuration mode. (Table 32)
Table 32. Master/Slave Resolution, AN_EN = 0
3.3 Auto-Negotiation
All 1000BASE-T PHYs are required to support Auto-Negotiation. (The 10/100 Mbps Ethernet PHYs had an option to
support Auto-Negotiation, as well as parallel detecting
when a link partner did not support Auto-Neg.) The AutoNegotiation function in 1000BASE-T has three primary purposes:
— Auto-Negotiation of Speed & Duplex Selection
— Auto-Negotiation of Master/Slave Resolution
— Auto-Negotiation of Pause/Asymetrical Pause Resolution
41
DP83865
Advertise
Link Partner
Advertise
DP83865
Outcome
Link Partner
Outcome
Manual
Master
Manual
Master
Unresolved
No Link
Unresolved
No Link
Manual
Master
Manual
Slave
Master
Slave
Manual
Master
Multi-node
(Auto-neg)
Master
Slave
Manual
Master
Single-node
(Auto-neg)
Master
Slave
Manual
Slave
Manual
Master
Slave
Master
Manual
Slave
Manual
Slave
Unresolved
No Link
Unresolved
No Link
Manual
Slave
Multi-node
(Auto-neg)
Slave
Master
Manual
Slave
Single-node
(Auto-neg)
Slave
Master
www.national.com
DP83865
3.0 Configuration (Continued)
The default for AN Speed Fallback is that after five tries to
achieve a stable link, the link speed will drop down to the
next lower advertised speed. The default CRC and IE
Speed Fallback is that after five link drops due to increase
error rate, the link speed drops down to the next lower
advertised speed. If during the link retry stage that the link
partner drops the link or the CAT5 cable is unplugged, the
retry counter will reload the retry count with the default
value of five.
Table 33. Speed/Duplex Selection, AN_EN = 1
DUP
Speed[1] Speed[0]
Comments
0
0
0
1000/100/10 HDX
0
0
1
1000/100 HDX
0
1
0
1000 HDX
0
1
1
1000/10 HDX
1
0
0
1000/100/10 FDX + HDX
1
0
1
1000/100 FDX + HDX
1
1
0
1000 FDX + HDX
1
1
1
1000/10 FDX + HDX
Note that the Speed Fallback works only from gigabit mode
to 100 Mbps or 10 Mbps.
3.3.3 Gigabit Retry Forced Link
Under the situations that the cable media may not be
appropriate for the gigabit transmission, it may take excessive number of retries to achieve a stable link. If achieving
a stable link is the highest priority, the Retry Forced Link
Mode can be enabled. Retry Forced Link Mode allows
auto-negotiation to force link at the highest common link
speed after five retries.
The Auto-Negotiation priority resolution are as follows:
1.
2.
3.
4.
5.
6.
1000BASE-T Full Duplex (Highest Priority)
1000BASE-T Half Duplex
100BASE-TX Full Duplex
100BASE-TX Half Duplex
10BASE-T Full Duplex
10BASE-T Half Duplex (Lowest Priority)
There are two criteria established to initiate the gigabit
Retry Forced Link.
1. CRC error rate
2. Idle error rate
There are three basic control register bits used to configure
the Speed Fallback and Retry Forced Link. Expanded register 0x1C0.3 = 0 enables the Retry Forced Link mode (i.e.,
teh default mode upon power up). LED Control Register
0x13.1:0 selects the criteria for the Speed Fallback. Since
Retry Forced Link does not work when AN fails to achieve
stable link, LED Control Register 0x13.2 should be 0.
3.3.2 Gigabit Speed Fallback
When gigabit mode is advertised, the default auto-negotiation mode attempts to establish link at the highest common
denominator advertised. However, there are situations that
the cable media may not be appropriate for the gigabit
speed communication. If achieving a quality link is the
highest priority, the Speed Fallback Mode can be enabled.
The Speed Fallback Mode allows auto-negotiation to link at
the next lower speed advertised (100Mbps or 10Mbps) if
the gigabit mode fails.
Table 35. LED Control Reg 0x13, Reg 0x1C0.3 = 0
Bit 2, AN Bit 1, CRC
There are three criteria established to initiate the gigabit
Speed Fallback.
1. Auto-negotiation failing to achieve a stable gigabit link
2. CRC error rate
3. Idle error rate
There are four basic control register bits used to configure
the Speed Fallback. Expanded register 0x1C0.3 = 1
enables the Speed Fallback mode. LED Control Register
0x13.2:0 selects the criteria for the Speed Fallback.
Comments
0
0
0
No Speed Fallback (SF)
0
0
1
SF on idle error
0
1
0
SF on CRC error
0
1
1
SF on idle and CRC
1
0
0
SF on failing AN
1
0
1
SF on AN and IE
1
1
0
SF on AN and CRC
1
1
1
SF on AN, CRC, and IE
www.national.com
Comments
0
0
0
No Retry Forced Link
(RFL)
0
0
1
RFL on idle error
0
1
0
RFL on CRC error
0
1
1
RFL on idle and CRC
The default CRC and IE Retry Forced Link is that after five
link drops due to increase error rate, the link will be forced
at the highest advertised speed. If during the link retry
stage that the link partner drops the link or the CAT5 cable
is unplugged, the retry counter will reload the retry count
with the default value of five. Note that the retry may take
forever to achieve a forced link when link partner drops the
link or CAT5 cable is unplugged.
Table 34. LED Control Reg 0x13, Reg 0x1C0.3 = 1
Bit 2, AN Bit 1, CRC Bit 0, IE
Bit 0, IE
3.3.4 Master/Slave Resolution
If 1000BASE-T mode is selected during the priority resolution, the second goal of Auto-Negotiation is to resolve Master/Slave configuration. The Master mode priority is given
to the device that supports multiport nodes, such as
switches and repeaters. Single node devices such as DTE
or NIC card takes lower Master mode priority.
MULTI_EN is a strapping option for advertising the Multinode functionality. (Table 36) In the case when both PHYs
advertise the same option, the Master/Slave resolution is
42
resolved by a random number generation. See IEEE
802.3ab Clause 40.5.1.2 for more details.
ANNPTR 0x07 allows for the configuration and transmission of the Next Page. Refer to clause 28 of the IEEE
802.3u standard for detailed information regarding the
Auto-Negotiation Next Page function.
Table 36. 1000BASE-T Single/Multi-Node, AN_EN = 1
MULTI_EN
3.3.7 Parallel Detection
Forced Mode
0
Single node, Slave priority mode
1
Multi-node, Master priority mode
The DP83865 supports the Parallel Detection function as
defined in the IEEE 802.3u specification. Parallel Detection
requires the 10/100 Mbps receivers to monitor the receive
signal and report link status to the Auto-Negotiation function. Auto-Negotiation uses this information to configure
the correct technology in the event that the Link Partner
does not support Auto-Negotiation, yet is transmitting link
signals that the 10BASE-T or 100BASE-X PMA recognize
as valid link signals.
Depending on what link the partner is configured to, the
Auto-Negotiation of Master/Slave mode can be resolved to
eight possible outcomes. (Table 37)
Mult-node
Single-node
Master
Slave
Single-node
Manual
Master
Slave
Master
If the DP83865 completes Auto-Negotiation as a result of
Parallel Detection, without Next Page operation, bits 5 and
7 of ANLPAR 0x05 will be set to reflect the mode of operation present in the Link Partner. Note that bits 4:0 of the
ANLPAR will also be set to 00001 based on a successful
parallel detection to indicate a valid 802.3 selector field.
Software may determine that the negotiation is completed
via Parallel Detection by reading ‘0’ in bit 0 of ANER 0x06
after the Auto-Negotiation Complete bit (bit 5, BMSR 0x01)
is set. If the PHY is configured for parallel detect mode and
any condition other than a good link occurs, the parallel
detect fault bit will set (bit 4, ANER 0x06).
Single-node
Manual
Slave
Master
Slave
3.3.8 Restart Auto-Negotiation
Single-node
Multi-node
Slave
Master
Single-node
Single-node
M/S resolved
by random seed
M/S resolved
by random seed
Table 37. Master/Slave Resolution, AN_EN = 1
DP83865
Advertise
Link Partner
Advertise
DP83865
Outcome
Link Partner
Outcome
Mult-node
Manual
Master
Slave
Master
Mult-node
Manual
Slave
Master
Slave
Mult-node
Multi-node
M/S resolved
by random seed
M/S resolved
by random seed
If a link is established by successful Auto-Negotiation and
then lost, the Auto-Negotiation process will resume to
determine the configuration for the link. This function
ensures that a link can be re-established if the cable
becomes disconnected and re-connected. After AutoNegotiation is completed, it may be restarted at any time by
writing ‘1’ to bit 9 of the BMCR 0x00.
3.3.5 Pause and Asymmetrical Pause Resolution
When Full Duplex operation is selected during priority resolution, the Auto-Negotiation also determines the Flow Control capabilities of the two link partners. Flow control was
originally introduced to force a busy station’s Link Partner
to stop transmitting data in Full Duplex operation. Unlike
Half Duplex mode of operation where a link partner could
be forced to back off by simply generating collisions, the
Full Duplex operation needed a mechanism to slow down
transmission from a link partner in the event that the receiving station’s buffers are becoming full. A new MAC control
layer was added to handle the generation and reception of
Pause Frames. Each MAC Controller has to advertise
whether it is capable of processing Pause Frames. In addition, the MAC Controller advertises if Pause frames can be
handled in both directions, i.e. receive and transmit. If the
MAC Controller only generates Pause frames but does not
respond to Pause frames generated by a link partner, it is
called Asymmetrical Pause.
A restart Auto-Negotiation request from any entity, such as
a management agent, will cause DP83865 to halt data
transmission or link pulse activity until the break_link_timer
expires (~1500 ms). Consequently, the Link Partner will go
into link fail mode and the resume Auto-Negotiation. The
DP83865 will resume Auto-Negotiation after the
break_link_timer has expired by transmitting FLP (Fast
Link Pulse) bursts.
3.3.9 Enabling Auto-Negotiation via Software
If the DP83865 is initialized upon power-up with AutoNegotiation disabled (forced technology) and the user may
desire to restart Auto-Negotiation, this could be accomplished by software access. Bit 12 of BMCR 0x00 should
be cleared and then set for Auto-Negotiation operation to
take place.
The advertisement of Pause and Asymmetrical Pause
capabilities is enabled by writing ‘1’ to bits 10 and 11 of
ANAR 0x04. The link partner’s Pause capabilities is stored
ANLPAR 0x05 bits 10 and 11. The MAC Controller has to
read from ANLPAR to determine which Pause mode to
operate. The PHY layer is not involved in Pause resolution
other than simply advertising and reporting of Pause capabilities.
3.3.10 Auto-Negotiation Complete Time
Parallel detection and Auto-Negotiation take approximately
2-3 seconds to complete. In addition, Auto-Negotiation with
next page exchange takes approximately 2-3 seconds to
complete, depending on the number of next pages
exchanged.
Refer to Clause 28 of the IEEE 802.3u standard for a full
description of the individual timers related to Auto-Negotiation.
3.3.6 Next Page Support
The DP83865 supports the Auto-Negotiation Next Page
protocol as required by IEEE 802.3u clause 28.2.4.1.7. The
43
www.national.com
DP83865
3.0 Configuration (Continued)
DP83865
3.0 Configuration (Continued)
3.4 Auto-Negotiation Register Set
During the next page exchange operation, the station manager can not wait till the end of Auto-Negotiation to read
the ANLPAR because the register is used to store both the
base and next pages. The next page content overwrites the
base page content. The station manager needs to closely
monitor the negotiation status and to perform the following
tasks.
The strapping option settings of Auto-Negotiation, speed,
and duplex capabilities that initialized during power-up or at
reset can be altered any time by writing to the BMCR 0x00,
ANAR 0x04 or, to 1KTCR 0x09.
When Auto-Negotiation is enabled, the DP83865 transmits
the abilities programmed in the ANAR 0x04, and 1KTCR
0x09 via FLP Bursts. The following combinations of
10 Mbps,100 Mbps, 1000 Mbps, Half Duplex, and Full
Duplex modes may be selected.
— ANER 0x06 bit 1 is ‘1’ indicates a page is received. Station manage reads the base page information from
ANLPAR0x05 and stores the content in the memory.
— After reading the base page information, software needs
to write to ANNPTR 0x07 to load the next page information to be sent.
— The operation can be implemented as polled or interrupt
driven. If another page is received by polling bit 1 in the
ANER 0x06 or by interrupt, the station manager reads bit
15 of the ANLPAR indicating the partner has more next
pages to send. If the partner has more pages to send,
ANNPTR needs to be written to load another next page.
The ANER 0x06 indicates additional Auto-Negotiation status. The ANER provides status on:
Table 38. Advertised Modes during Auto-Negotiation,
AN_EN = 1
SPEED1
SPEED0
DUPLEX
Adertised Modes
1000BASE-T HD, 10BASE-T HD
1
1
0
1
0
0
1000BASE-T HD
0
1
0
1000BASE-T HD, 100BASE-TX HD
0
0
0
1000BASE-T HD, 100BASE-TX HD,
10BASE-T HD
1
1
1
1000BASE-T FD, 10BASE-T FD
1
0
1
1000BASE-T FD
0
1
1
1000BASE-T FD, 100BASE-TX FD
0
0
1
1000BASE-T FD, 100BASE-TX FD,
10BASE-T FD
— A Parallel Detect Fault has occurred (bit 4, ANER 0x06).
— The Link Partner supports the Next Page function (bit 3,
ANER 0x06).
— The DP83865 supports the Next Page function (bit 2,
ANER 0x06).
— The current page being exchanged by Auto-Negotiation
has been received (bit1, ANER 0x06).
— The Link Partner supports Auto-Negotiation (bit 0, ANER
0x06).
The ANNPTR 0x07 contains the next page code word to be
transmitted. See also Section “2.3 Register Description”
for details.
The Auto-Negotiation protocol compares the contents of
the ANLPAR (received from link partner) and ANAR registers (for 10/100 Mbps operation) and the contents of
1000BASE-T status and control registers, and uses the
results to automatically configure to the highest performance protocol (i.e., the highest common denominator)
between the local and the link partner. The results of AutoNegotiation may be accessed in registers BMCR 0x00
(Duplex Status and Speed Status), and BMSR 0x01 (AutoNeg Complete, Remote Fault, Link).
3.5 Auto-MDIX resolution
The GigPHYTER V can determine if a “straight” or “crossover” cable is used to connect to the link partner. It can
automatically re-assign channel A and B to establish link
with the link partner, (and channel C and D in 1000BASE-T
mode). Auto-MDIX resolution precedes the actual AutoNegotiation process that involves exchange of FLPs to
advertise capabilities. Automatic MDI/MDIX is described in
IEEE 802.3ab Clause 40, section 40.8.2. It is not a required
implementation for 10BASE-T and 100BASE-TX.
The BMCR 0x00 provides control for enabling, disabling,
and restarting the Auto-Negotiation process.
The BMSR 0x01 indicates the set of available abilities for
technology types, Auto-Negotiation ability, and extended
register capability. These bits are permanently set to indicate the full functionality of the DP83865. The BMSR also
provides status on:
— Auto-Negotiation is completed on bit 5
— The Link Partner is advertising that a remote fault has
occurred on bit 4
— A valid link has been established on bit 2
The ANAR 0x04 stores the capabilities advertised during
Auto-Negotiation. All available capabilities are transmitted
by default. However, the advertised capability can be suppressed by writing to the ANAR. This is a commonly used
by a management agent to change (i.e., to force) the communication technology.
Table 39. PMA signal to MDI and MDIX pin-out
The ANLPAR 0x05 is used to store the received base link
code word as well as all next page code words during the
negotiation that is transmitted from the link partner.
If Next Page is NOT being used, then the ANLPAR will
store the base link code word (link partner's abilities) and
retain this information from the time the page is received,
indicated by a ‘1’ in bit 1 of the ANER 0x06, through the
end of the negotiation and beyond.
www.national.com
44
Contact
MDI
MDIX
1
MDI_A+
MDI_B+
2
MDI_A-
MDI_B-
3
MDI_B+
MDI_A+
4
MDI_C+
MDI_D+
5
MDI_C-
MDI_D-
6
MDI_B-
MDI_A-
7
MDI_D+
MDI_C+
8
MDI_D-
MDI_C-
To enable Auto-MDIX, strapping option pin MDIX_EN
should be pulled up or left floating. Auto-MDIX can be disabled by strapping MDIX_EN pin low. When Auto-MDIX is
disabled, the PMA is forced to either MDI (“straight”) or
MDIX (“crossed”) - according to the setting of the
MAN_MDIX strapping option pin (high for MDIX and low for
MDI).
and it is implemented on DP83865DVH. Note that the
reduced LED mode is in addition to the existing five-LED
mode.
There are two reduced LED modes, the 3-in-1 mode and
the 4-in-1 mode. The 3-in-1 mode combines 10/100/100
Mbps links status in one LED, the standard LINK10_LED.
In the 3-in-1 mode, the rest of the four LED’s would still
function in the standard mode. This would allow user to use
one LED to indicate three-speed links, and other LED’s to
indicate 1000M link, TX/RX activity, or duplex.
The two strapping options for the MDI/MDIX configuration
can be overwritten by writing to bits 14 and 15 of register
AUX_CTRL (0x12). Bit 15 disables the Auto-MDIX feature
and bit 14 can change the straight/crossed and MDI/MDIX
setting.
Similar to 3-in-1 mode, the 4-in-1 mode combines an additional activity into the three-speed link modes. This mode
would further reduce the number of LED’s and still keep the
same number of display types.
Auto-MDIX is independent of Auto-Negotiation. Auto-MDIX
works in both AN mode and manual forced speed mode.
The Auto-MDIX in forced speed mode is added to
DP83865DVH revision and up.
To enable the RLED mode, LED Control Register 0x13.5 =
1, and register 0x1A.0 selects 3-in-1 or 4-in-1 mode.
3.6 Polarity Correction
Table 40. Reduced LED Mode
The GigPHYTER V will automatically detect and correct for
polarity reversal in wiring between the +/- wires for each
pair of the 4 ports.
RLED Ena
3/4-in-1 Sel
LINK10_LED
0
0
10M link
The current status of the polarity reversals is displayed in
bit 15:12 of register LINK_AN (0x11).
0
1
10M link
1
0
10/100/1000 link and ACT
3.7 PHY Address, Strapping Options and LEDs
1
1
10/100/1000 link
The PHY address can be set through external strapping
resistors. If all PHY address pins are left floating, the PHY
address is defaulted to 01h by internal pull up/down resistors.
3.9 Modulate LED on Error
The DP83865DVH uses ACT LED to display activity under
normal operation. The ACT LED is steady on when there is
Tx or Rx activity. The ACT can also display gigabit idle
error and CRC event. To differentiate ACT LED from normal Tx/Rx activity, the rate of the blink is faster when error
occurs. To enable the idle error modulation, LED Control
Register 0x13.3 = 1 and to enable CRC error modulation,
0x13.4 = 1.
The PHY address of DP83865 port can be configured to
any of the 31 possible PHY addresses (except 00h which
puts the PHY in isolation mode at power-up). However, if
more than one DP83865 is used on a board and if MDIO is
bused in a system, each of the DP83865’s address must
be different.
Table 41. LED Control Reg 0x13
PHY address strapping pin “0” is shared with the Duplex
LED pin.
Strap option pins can be left floating which will result in the
default for the particular pin to be set. External pull-up or
pull-down resistors (2kΩ recommended) can be used to
change the pre-set value.
The state of the strapping option pin inputs is latched (into
Strap_reg 0x10) at system power-on or reset. For further
details relating to the latch-in timing requirements of the
strapping option pins, as well as the other hardware configuration pins, refer to section “6.2 Reset Timing” on
page 73.
Bit 4
Bit 3
Activity LED
0
0
Normal ACT
0
1
ACT/Idle error
1
0
ACT/CRC error
1
1
ACT/Idle error/CRC error
3.10 MAC Interface
The DP83865 MAC interface can be configured to one of
the following different modes:
Some strap option pins are shared with LED output pins.
Since the strapping resistor could be a pull-up or a pulldown, an adaptive mechansim has been implemented to
simplify the required external circuit. In case the LED/strapping pin is strapped high, the LED drive level is active low.
In case the LED/strapping pin is strapped low, the LED
drive level is active high. See section “5.9 LED/Strapping
Option” on page 67 for details of the recommende external
components.
— MII Mode: Supports 10/100 Mbps MACs.
— GMII Mode: Supports 802.3z compliant 1000 Mbps
MACs.
— RGMII Mode: Supports RGMII version 1.3.
Only one mode is used at a time.
The interface is capable of driving 35 pF under worst conditions. Note that these outputs are not designed to drive
multiple loads, connectors, backplanes, or cables. See
section “5.6 Layout Notes on MAC Interface” on page 66
for design and layout details.
3.8 Reduced LED Mode
The DP83865DVH has a standard five-LED set. In some
applications, it is desirable to use fewer LED’s. The
“reduced LED mode” (RLED) is created to accommodate
the need for combining the LED functions into fewer LED’s
45
www.national.com
DP83865
3.0 Configuration (Continued)
DP83865
3.0 Configuration (Continued)
3.10.1 MII/GMII Interface
Note that upon power up, the clock output is available after
GPHY goes through its internal reset and initialization process. The clock output can be interrupted when GPHY is
going through software reset.
The link speed is determined by Auto-Negotiation, by
strapping options, or by register writes. Based on the
speed linked, an appropriate MAC interface is enabled.
3.12 MII/GMII/RGMII Isolate Mode
The DP83865 can be placed into MII/GMII/RGMII Isolate
mode by writing to bit 10 of the BMCR 0x00.
Table 42. Auto-Negotiation Disabled
SPEED[1:0]
Link Strapped
Controller I/F
00
10BASE-T
MII
01
100BASE-TX
MII
10
1000BASE-T
GMII/RGMII
11
reserved
---
3.12.1 10/100 Mbps Isolate Mode
In Isolation Mode, the DP83865 does not respond to
packet data present at TXD[3:0], TX_EN, and TX_ER
inputs and presents a high impedance on the TX_CLK,
RX_CLK, RX_DV, RX_ER, RXD[3:0], COL, and CRS outputs. The DP83865 will continue to respond to all management transactions through MDIO.
Table 43. Auto-Negotiation Enabled
While in Isolate mode, all medium access operations are
disabled.
Link Negotiated
Controller I/F
10BASE-T
MII
3.12.2 1000 Mbps Isolate Mode
100BASE-TX
MII
1000BASE-T
GMII/RGMII
During 1000 Mbps operation, the isolate mode will TRISTATE the GMII outputs of the GigPHYTER V. The PHY
also enters into the power down mode. All medium access
operations are halted. The only way to communicate to the
PHY is through MDIO management port.
3.10.2 RGMII Interface
The Reduced Gigabit Media Independent Interface
(RGMII) is a proposed standard by HP and 3Com. RGMII
is an alternative data interface to GMII and MII. RGMII
reduces the MAC interface pin count to 12.
3.13 Loopback Mode
The DP83865 includes a Loopback Test mode for easy
board diagnostics. The Loopback mode is selected through
bit 14 (Loopback) of BMCR 0x00. Writing 1 to this bit
enables MII/GMII transmit data to be routed to the MII/GMII
receive outputs. While in Loopback mode the data will not
be transmitted onto the media. This is true for 10Mbps, 100
Mbps, as well 1000 Mbps data.
The RGMII can be enabled either through strapping option
or MDIO register write. The strapping pins are shared with
CRS/RGMII_SEL0 and TX_CLK/RGMII_SEL1 since CRS
and TX_CLK signals are not used in the RGMII mode.
Table 44. RGMII Strapping for HP mode
Signal
Pin
Strap
CRS/RGMII_SEL0
40
0
TX_CLK/RGMII_SEL1
60
1
In 10BASE-T, 100BASE-TX, 1000BASE-T Loopback mode
the data is routed through the PCS and PMA layers into the
PMD sublayer before it is looped back. Therefore, in addition to serving as a board diagnostic, this mode serves as
quick functional verification of the device.
3.14 IEEE 802.3ab Test Modes
Table 45. RGMII Strapping for 3COM mode
Signal
Pin
IEEE 802.3ab specification for 1000BASE-T requires that
the PHY layer be able to generate certain well defined test
patterns on TX outputs. Clause 40 section 40.6.1.1.2 “Test
Modes” describes these tests in detail. There are four test
modes as well as the normal operation mode. These
modes can be selected by writing to the 1KTCR 0x09 as
shown.
Strap
CRS/RGMII_SEL0
40
1
TX_CLK/RGMII_SEL1
60
1
To enable RGMII through software, Register AUX_CTL
0x12.13:12 should be “10” or “11” binary. Note that
enabling the RGMII interface disables GMII and MII interfaces.
Table 46. IEEE Test Mode Select
3.11 Clock to MAC Enable
The DP83865 has a clock output (pin 85) that can be used
as a reference clock for other devices such as MAC or
switch silicon. The Clock to MAC output can be enabled
through strapping pins.
The Clock to MAC Enable Strap (pin 88) enables the clock
output. The output frequency can be selected between 25
MHz or 125 MHz. The frequency selection strapping pin is
combined with COL (pin 39), CLK_MAC_FRQ.
www.national.com
46
bit 15
bit 14
bit 13
Test Mode Selected
1
0
0
= Test Mode 4
0
1
1
= Test Mode 3
0
1
0
= Test Mode 2
0
0
1
= Test Mode 1
0
0
0
= Normal Operation
See IEEE 802.3ab section 40.6.1.1.2 “Test modes” for
more information on the nature of the test modes.
BIST. The receive BIST contains a receive error counter
and receive packet counter and the transmit BIST is used
to generate Ethernet packets.
The DP83865 provides a test clock synchronous to the
IEEE test patterns. The test patterns are output on the MDI
pins of the device and the test clock is output on the
TX_TCLK pin. There are also two support signals available
which are intended to improve the viewability of the test
patterns on an oscilloscope. TX_TRIGGER marks the start
of the test pattern and TX_SYNC_CLK provides and additional clock. Refer to section “1.6 Device Configuration and
LED Interface” on page 8 for pin numbers.
The BIST can be used to verify operations of all three
speed modes. The speed mode can be established
through auto-negotiation or manual forced mode. The BIST
may also be used in combination with the loopback mode
to verify both the transmit and receive operations of the
physical layer device.
Receive BIST
BIST_CNT displays the upper or lower 16-bit of an internal
32-bit counter. Bit 14 of BIST_CFG2 (bist_cnt_sel) selects
which 16-bit portion is shown while bit 15 of BIST_CFG1
(bist_cnt_type) selects whether the receive packet counter
or the receive error counter is active. The active counter
can be cleared by writing a ‘1’ to bit 14 of BIST_CFG1. The
receive BIST counter is disabled by default and can be
enabled through bit 15 of BIST_CFG2.
TX_TCLK, TX_TRIGGER and TX_SYN_CLK must be
enabled through bits 6 and 7 of register AUX_CTRL (0x12)
before they can be used.
3.15 Interrupt
The DP83865 can be configured to generate an interrupt
on pin 3 when changes of internal status occur. The interrupt allows a MAC to act upon the status in the PHY without polling the PHY registers. The interrupt source can be
selected through the interrrupt register set. This register set
consists of:
The receive BIST can be enabled during normal operation
in order to monitor the incoming data stream. The BIST
operation will not affect the PHY’s performance or behavior.
— Interrupt Status Register (INT_STATUS 0x14)
— Interrupt Mask Register (INT_MASK 0x15)
— Interrupt Clear Register (INT_CLEAR 0x17)
Upon reset, the interrupt is disabled and the interrupt registers are cleared. Any interrupt source can be enabled in the
INT_MASK register.
Transmit BIST
The transmit BIST allows the generation of packets with
pseudo-random (PSR9) or user defined content (bit 10 of
BIST_CFG1), different packet lengths (bit 13 of
BIST_CFG1) and variable interframe gap (bit 12 of
BIST_CFG1). Bits 7:0 of BIST_CFG1 contain the content
of the packet as defined by the user if that option has been
chosen.
The interrupt pin is active low. When the interrupt signal is
asserted it will remain asserted until the corresponding status bit is cleared.
The number of packets to be sent are specified through bits
13:11 of BIST_CFG2. Setting the enable bit in bit 11 of
BIST_CFG1 starts the transmittal. After the last packet was
sent this bit is automatically cleared. In case the ‘continuous transmit’ has been selected the enable bit must be
cleared in order to stop the stream of packets.
The interrupt pin is tri-stated when the interrupt is not
enabled or no interrupt has occured.
The status bits are the sources of the interrupt. These bits
are mapped in INT_STATUS. When the interrupt status bit
is “1”, the interrupt signal is asserted if the corresponding
INT_MASK bit is enabled. An interrupt status bit can be
cleared by writing a “1” to the corresponding bit in
INT_CLEAR. The clear bit returns to “0” automatically after
the interrupt status bit is cleared.
Table 47. BIST Configuration 1 Reg (0x19)
Bit
Function
15
Set active counter:
‘1’ = Receive error counter
‘0’ = Receive packet counter
3.16 Low Power Mode / WOL
The GigPHYTER V supports the Wake on LAN (WOL) feature of a higher layer device. In order to achive the least
possible power consumption the DP83865 must be put in
10BASE-T mode (Half or Full Duplex). In this mode the
device uses a maximum of 146mW of power.
14
‘1’ = Clear counter
13
Packet length:
‘1’ = 1514 bytes
‘0’ = 60 bytes
3.17 Power Down Mode
12
Interframe gap:
‘1’ = 9.6 µs
‘0’ = 0.096 µs
Register BMCR (0x00) bit 11 puts the GigPHYTER V in
Power Down mode. Writing a ‘1’ to this location causes the
DP83865 to deactivate everything but the management
(MDC / MDIO) interface. During this mode the device consumes the least possible power.
11
‘1’ = Enable transmit BIST
10
Packet type:
‘1’ = PSR9
‘0’ = User defined
3.18 BIST Configuration
The BIST (Built-In Self Test) provides a test interface that
allows to evaluate receive performance and to generate
valid transmit packets. Registers 0x18 (BIST_CNT), 0x19
(BIST_CFG1) and 0x1A (BIST_CFG2) contain the controls
to two distinct BIST functions: Receive BIST and transmit
7:0
47
User defined packet content.
www.national.com
DP83865
3.0 Configuration (Continued)
DP83865
3.0 Configuration (Continued)
3.20 10BASE-T Half Duplex Loopback
During transmit BIST operation the transmit path
(TXD[7:0]) of the GMII / MII is disabled. All generated packets will be sent out to the MDI path unless the loopback
mode is enabled. In that case the generated packets will be
presented at the receive path (RXD[7:0]) of the GMII / MII.
By default, the 10BASE-T half duplex transmitted packets
are looped back to the receive side. This is a legacy implementation. However, in the latest MAC or switch design,
the 10 Mbps loopback is desired to be turned off. The 10
Mbps HDX loopback can be disabled in the expanded
memory register 0x1C0.1.
Table 48. BIST Configuration 2 Reg (0x1A)
Bit
Function
15
‘1’ = Enable counter
14
Counter selection:
Bit 1
‘1’ = upper 16-bit
‘0’ = lower 16-bit
0
10BASE-T HDX loopback enabled
1
10BASE-T HDX loopback disabled
13:11
Table 50. 10M FDX Loopback Disable, Reg 0x1C0
Number of packets to transmit:
3.21 I/O Voltage Selection
‘000’ = continuous transmit
‘001’ = 1 packet
‘010’ = 10 packets
‘011’ = 100 packets
‘100’ = 1,000 packets
‘101’ = 10,000 packets
‘110’ = 100,000 packets
‘111’ = 10,000,000 packets
There are two options for the I/O voltage available. All
IO_VDD pins must be connected to the same power supply. It can either be 2.5V or 3.3V. The VDD_SEL pin must
be connected to ground in order to select 2.5V or to the
3.3V power supply to select 3.3 V. This pin must be connected directly to the respective power supply and must
not use a pull-up/-down resistor.
Pin which are effected by IO_VDD, i.e. will be driven at a
different voltage level, are all pin on the GMII/MII interface,
management interface, JTAG interface, clock interface,
device configuration and reset pins.
If BIST is operating the 1000BASE-T mode, active
GTX_CLK is required for the operation.
3.19 Cable Length Indicator
3.22 Non-compliant inter-operability mode
The maximum CAT5 cable length specified in IEEE 802.3
is 100 meters. When cable length extended beyond the
IEEE specified range, bit error rate (BER) will increase due
to the degredation of signal-to-noise ratio. The DP83865
has enough margin built-in to work at extended cable
reach.
In this mode the DP83865 allows with other vendor’s first
generation 1000 Mbps PHYs. National’s DP83865 is compliant to IEEE 802.3ab and optionally inter-operable with
non-compliant PHYs.
To enter non-compliant inter-operability mode the user can
use a 2kΩ resistor on NON_IEEE_STRAP (pin 1) or write
‘1’ to bit 9 of register 0x12.
When a 100BASE-TX or 1000BASE-T link is established,
the cable length is determined from adaptation parameters.
In 100BASE-TX mode, one cable length measurement is
available since there is one receive channel. In 1000BASET mode, four cable length measurements are available
since there are four receive channels. Each measurement
is stored in an 8-bit register in the expanded memory
space. User may choose to take the average of four measurement to achieve more accurate result. The number
stored in the cable length registers are in meters, and the
typical accuracy is ±5 meters.
The non-compliant mode is functional in auto-negotiation
configuration. It is not applicable in manual speed configuration.
Table 49. Cable Length Indicator Registers
Regiters
Addr
Description
Length_A
0x019F
Length, 100/1000 Mbps
Length_B
0x01A2
Length, 1000 Mbps
Length_C
0x01A5
Length, 1000 Mbps
Length_D
0x01A8
Length, 1000 Mbps
The error rate may be used in conjuction with the cable
length measurement to determine if the link is within IEEE
specifications. If the measurement shows that the cable
length exceeds 130 meters, either the cable is too long or
the cable quality is not meeting the CAT5 standard.
www.national.com
10BASE-T HDX Loopback Mode
48
The DP83865 is a full featured 10/100/1000 Ethernet Physical layer (PHY) chip. It consists of a digital 10/100/1000
Mb/s core with a common TP interface. It also has a combined versitle MAC interface that is capable of interfacing
with MII and GMII controller interfaces. In this section, the
following topics are covered:
—
—
—
—
—
—
—
—
—
4.1.2 Data and Symbol Sign Scrambler Word Generator
The word generator uses the Scrn[32:0] to generate further
scrambled values. The following signals are generated:
Sxn[3:0], Syn[3:0], and Sgn[3:0].
The 4-bit Sxn[3:0] and Syn[3:0] values are then sent to the
scrambler bit generator. The 4-bit Sgn[3:0] sign values are
provided to the sign scrambler nibble generator.
1000BASE-T PCS Transmitter
1000BASE-T PMA Transmitter
1000BASE-T PMA Receiver
1000BASE-T PCS Receiver
Gigabit MII (GMII)
Reduced GMII (RGMII)
10BASE-T and 100BASE-TX Transmitter
10BASE-T and 100BASE-TX Receiver
Media Dependent Interface (MII)
4.1.3 Scrambler Bit Generator
This sub block uses the Sxn and Syn signals along with the
tx_mode and tx_enable signals to generate the Scn[7:0],
that is further scrambled based on the condition of the
tx_mode and tx_enable signal. The tx_mode signal indicates sending idles (SEND_I), sending zeros (SEND_Z) or
sending idles/data (SEND_N). The tx_mode signal is generated by the micro controller function. The tx_enable signal is either asserted to indicate data transmission is
occurring or deasserted when there is no data transmission. The PCS Data Transmission Enable state machine
generates the tx_enable signal.
The 1000BASE-T transceiver includes PCS (Physical Coding Sublayer) Transmitter, PMA (Physical Medium Attachment) Transmitter, PMA Receiver and PCS Receiver. The
1000BASE-T functional block diagram is shown in section
“ Block Diagram” on page 2.
The 8-bit Scn[7:0] signals are then passed onto the data
scrambler functional block.
4.1.4 Data Scrambler
4.1 1000BASE-T PCS Transmitter
The Data Scrambler generates scrambled data by accepting the TxDn[7:0] data from the GMII and scrambling it
based on various inputs.
The PCS transmitter comprises several functional blocks
that convert the 8-bit TXDn data from the GMII to PAM-5
symbols passed onto the PMA function. The block diagram
of the PCS transmitter data path in Figure 2 provides an
overview of each of the architecture within the PCS transmitter.
The data scrambler generates the 8-bit Sdn[7:0] value,
which scrambles the TxDn data based primarily on the Scn
values and the accompanying control signals.
All 8-bits of Sdn[7:0] are passed onto the bit-to-quinary
symbol mapping block, while 2-bits, Sdn[7:6], are fed into
the convolutional encoder.
The PCS transmitter consists of eight sub blocks:
— LFSR (Linear Feedback Shift Register)
— Data scrambler and symbol sign scrambler word generator
— Scrambler bit generator
— Data scrambler
— Convolutional encoder
— Bit-to-symbol quinary symbol mapping
— Sign scrambler nibble generator
— Symbol sign scrambler
The requirements for the PCS transmit functionality are
also defined in the IEEE 802.3ab specification section
40.3.1.3 “PCS Transmit function”.
4.1.5 Convolutional Encoder
The encoder uses Sdn[7:6] bits and tx_enable to generate
an additional data bit, which is called Sdn[8].
The one clock delayed versions csn-1[1:0] are passed to
the data scrambler block. This Sdn[8] bit is then passed to
the bit-to-symbol quinary symbol mapping function.
4.1.6 Bit-to-Symbol Quinary Symbol Mapping
This block implements the IEEE 802.3ab specification
Tables 40-1 and 40-2 Bit-to-Symbol Mapping for even and
odd subsets. It takes the 9-bit Sdn[8:0] data and converts it
to the appropriate quinary symbols as defined by the
tables.
4.1.1 Linear Feedback Shift Register (LFSR)
The side-stream scrambler function uses a LFSR implementing one of two equations based on the mode of operation, i.e., a master or a slave. For master operation, the
equation is
The output of this block generates the TAn, TBn, TCn, and
TDn symbols that passed onto the symbol sign scrambler.
gM(x) = 1 + x13 + x33
4.1.7 Sign Scrambler Nibble Generator
For slave operation, the equation is
Sign Scrambler Nibble Generator performs some further
scrambling of the sign values Sgn[3:0] that are generated
by the data and symbol sign scrambler word generator.
The sign scrambling is dependent on the tx_enable signal.
gS(x) = 1 + x20 + x33
The 33-bit data output, Scrn[32:0], of this block is then fed
to the data scrambler and symbol sign scrambler word generator.
The SnAn, SnBn, SnCn, and SnDn outputs are then passed
onto the symbol sign scrambler function.
49
www.national.com
DP83865
4.0 Functional Description
DP83865
4.0 Functional Description (Continued)
Sign
Scrambled
PAM-5
Symbols
to PMA
TAn
Data Scrambler
and Symbol
LSFR
gM = 1 + x13 + x33
gS = 1 + x
20
+x
Scrn[32:0]
33
Sign Scrambler
Syn[3:0]
Scrambler
Bit
Generator
Data
Scrambler and
Convolutional
Encoder
Sdn[8:0]
Bit-to
Quinary Symbol
Mapping
Word Generator
g(x) = x ⊕ x
3
Input Data
Byte from GMII
Scn[7:0]
Sx n[3:0]
8
Sgn[3:0]
Sign
Scrambler
Nibble
Generator
TBn
TCn
An
TDn
Sn An
S nB n
Symbol
Bn
Sign
Scrambler
Cn
Dn
S nC n
S nD n
TxDn[7:0]
Figure 2. PCS TX Functional Block Diagram
4.1.8 Symbol Sign Scrambler
4.3 1000BASE-T PMA Receiver
Symbol Sign Scrambler scrambles the sign of the TAn,
TBn, TCn, and TDn input values from the bit-to-symbol quinary symbol mapping function by either inverting or not
inverting the signs. This is done as follows:
Cn = TCn x SnCn
The PMA Receiver (the “Receiver”) consists of several sub
functional blocks that process the four digitized voltage
waveforms representing the received quartet of quinary
PAM-5 symbols. The DSP processing implemented in the
receiver extracts a best estimate of the quartet of quinary
symbols originated by the link partner and delivers them to
the PCS Receiver block for further processing. There are
four separate Receivers, one for each twisted pair.
Dn = TDn x SnDn
The main processing sub blocks include:
The output of this block, namely An, Bn, Cn, and Dn, are the
sign scrambled PAM-5 symbols. They are then passed
onto the PMA for further processing.
—
—
—
—
—
An = TAn x SnAn
Bn = TBn x SnBn
4.2 1000BASE-T PMA Transmitter
The PMA transmit block shown in Figure 3 contains the following blocks:
4.3.1 Adaptive Equalizer
— Partial Response Encoder
— DAC and Line Driver
The Adaptive Equalizer compensates for the frequency
attenuation characteristics which results from the signal
distortion of the CAT-5 cable. The cable has higher attenuates at the higher frequencies and this attenuation must be
equalized. The Adaptive Equalizer is a digital filter with tap
coefficients continually adapted to minimize the Mean
Square Error (MSE) value of the slicer's error signal output.
Continuous adaptation of the equalizer coefficients means
that the optimum set of coefficients will always be achieved
for maximum specified length or lower quality of cable.
4.2.1 Partial Response Encoder
Partial Response (PR) coding (or shaping) is used on the
PAM-5 coded signals to spectrally shape the transmitted
PAM-5 signal in order to reduce emissions in the critical
frequency band ranging from 30 MHz to 60 MHz. The PR
Z-transform implemented is
0.75 + 0.25 Z
–1
4.3.2 Echo and Crosstalk Cancellers
The PR coding on the PAM-5 signal results in 17-level PAM5 or PAM-17 signal that is used to drive a common
10/100/1000 DAC and line driver. (Without the PR coding
each signal can have 5 levels given by ± 1, ± 0.5 and 0 V. If
all combinations of the 5 levels are used for the present and
previous outputs, then there are 17 unique output levels
when PR coding is used.)
The Echo and Crosstalk Cancellers cancel the echo and
crosstalk produced while transmitting and receiving simultaneously. Echo is produced when the transmitted signal
interferes with the received signal on the same wire pair.
Crosstalk is caused by the transmitted signal appearing on
each of the other three wire pairs interfering with the
receive signal on the fourth wire pair. An Echo and
Crosstalk Canceller is needed for each of the wire pairs.
Figure 3 shows the PMA Transmitter and the embedded
PR encoder block with its inputs and outputs. Figure 4
shows the effect on the spectrum of PAM-5 after PR shaping.
4.3.3 Automatic Gain Control (AGC)
The Automatic Gain Control acts upon the output of the
Echo and Crosstalk Cancellers to adjust the receiver gain.
Different AGC methods are available within the chip and
the optimum gain is selected based on the operational
state the chip (master, slave, start-up, etc.).
4.2.2 DAC and Line Driver
The PAM-17 information from the PR encoder is supplied
to a common 10/100/1000 DAC and line driver that converts digitally encoded data to differential analog voltages.
www.national.com
Adaptive Equalizer
Echo and Crosstalk Cancellers
Automatic Gain Control (AGC)
Baseline Wander (BLW) Correction
Slicer
50
DP83865
4.0 Functional Description (Continued)
PARTIAL RESPONSE PULSE SHAPE CODING
5-LEVEL PAM-5 TO 17-LEVEL PAM
SIGN
SCRAMBLER
PAM-5
3-bits/sample
Z -1
0.75
0.25
17-LEVEL
PAM-5
5-bits/sample
TABLE
LOOKUP
DAC
CONTROL
20-bits/sample
MUX
0.75∗X(k) + 0.25∗X(k-1)
10
100
1000
DAC
Manchester/
MLT-3/PAM-17
ANALOG
2-bit MLT-3
Manchester coding
PMA Transmitter Block
Figure 3. PMA Transmitter Block
PAM-5 w ith PR (.7 5+.2 5T)
Transmit Spectra
PAM-5
1.200
Re lativ e Amp litud e
1.000
0.800
0.600
0.400
0.200
0.000
-0.200
-0.400
10.00
critica l reg io n -- (30 MH z -- 6 0MH z)
100.00
F re q ue n cy (M Hz)
Figure 4. Effect on Spectrum of PR-shaped PAM-5 coding
4.3.4 Baseline Wander (BLW) Correction
actual voltage input and the ideal voltage level representing the symbol value. The error output is fed back to the
BLW, AGC, Crosstalk Canceller and Echo Canceller sub
blocks to be used in their respective algorithms.
Baseline wander is the slow variation of the DC level of the
incoming signal due to the non-ideal electrical characteristics of the magnetics and the inherent DC component of
the transmitted waveform. The BLW correction circuit utilizes the slicer error signal to estimate and correct for BLW.
4.4 1000BASE-T PCS Receiver
The PCS Receiver consists of several sub functional
blocks that convert the incoming quartet of quinary symbols (PAM-5) data from the PMA Receiver A, B, C, and D to
8-bit receive data (RXD[7:0]), data valid (RX_DV), and
receive error (RX_ER) signals on the GMII. The block diagram of the 1000BASE-T Functional Block in section
“ Block Diagram” on page 2 provides an overview of the
4.3.5 Slicer
The Slicer selects the PAM-5 symbol value (+2,+1,0,-1,-2)
closest to the voltage input value after the signal has been
corrected for line Inter Symbol Interference (ISI), attenuation, echo, crosstalk and BLW.
The slicer produces an error output and symbol value decision output. The error output is the difference between the
51
www.national.com
DP83865
4.0 Functional Description (Continued)
4.4.5 Receive State Machine
1000BASE-T transceiver and shows the functionality of the
PCS receiver.
The state machine operation is defined in IEEE 802.3ab
section 40.3.1.4. In summary, it provides the necessary
receive control signals of RX_DV and RX_ER to the GMII.
In specific conditions defined in the IEEE 802.3ab specification, it generates RXD[7:0] data.
The major sub functional blocks of the PCS Receiver
include:
— Delay Skew Compensation
— Delay Skew Control
— Forward Error Correction (FEC)
— Descrambler Subsystem
— Receive State Machine
— ADC/DAC/Timing Subsystem
The requirements for the PCS receive functionality are
defined in the IEEE 802.3ab specification in section
40.3.1.4 “PCS Receive function”.
4.4.6 ADC/DAC/Timing Subsystem
The 1000BASE-T receive section consists of 4 channels,
each receiving IEEE 802.3ab compliant PAM-5 coded data
including Partial Response (PR) shaping at 125 MBaud
over a maximum of a 100 m of CAT-5 cable. The 4 pairs of
receive input pins are AC coupled through the magnetics to
the CAT-5 cable. Each receive pin pair is differentially terminated into an external 100W resistor to match the cable
impedance. Each receive channel consists of a high precision Analog to Digital data converter (ADC) which quantizes the incoming data into a digital word at the rate of 125
Mb/s. The ADC is sampled with a clock of 125 MHz which
has been recovered from the incoming data stream.
4.4.1 Delay Skew Compensation
This is a mechanism used to align the received data from
the four PMA receivers and to determine the correct spacial ordering of the four incoming twisted pairs, i.e., which
twisted pair carries An, which one carries Bn, etc. The deskewed and ordered symbols are then presented to the
Forward Error Correction (FEC) Decoder. The differential
time or time delay skew is due to the differences in length
of each of the four pairs of twisted wire in the CAT-5 cable,
manufacturing variation of the insulation of the wire pairs,
and in some cases, differences in insulation materials used
in the wire pairs. Correct symbol order to the FEC is
required, since the receiver does not have prior knowledge
of the order of the incoming twisted pairs within the CAT-5
cable.
The 1000BASE-T transmit section consists of 4 channels,
each transmitting IEEE 802.3ab compliant 17-level PAM-5
data at 125 M symbols/second. The 4 pairs of transmit output pins are AC coupled through the magnetics to the CAT5 cable. Each transmit pin pair is differentially terminated
into an external 100W resistor to match the cable impedance. Each transmit channel consists of a Digital to Analog
data converter (DAC) and line driver capable of producing
17 discrete levels corresponding to the PR shaping of a
PAM-5 coded data stream. Each DAC is clocked with the
internal 125 MHz clock in the MASTER mode, and the
recovered receive clock in the SLAVE mode operation.
4.4.2 Delay Skew Control
The DP83865 incorporates a sophisticated Clock Generation Module (CGM) which supports 10/100/1000 modes of
operation with an external 25 MHz clock reference (±50
ppm). The Clock Generation module internally generates
multiple phases of clocks at various frequencies to support
high precision and low jitter Clock Recovery Modules
(CRM) for robust data recovery, and to support accurate
low jitter transmission of data symbols in the MASTER and
SLAVE mode operations.
This sub block controls the delay skew compensation function by providing the necessary controls to allow for compensation in two dimensions. The two dimensions are
referring to time and position. The time factor is the delay
skew between the four incoming data streams from the
PMA RX A, B, C, and D. This delay skew originates back at
the input to the ADC/DAC/TIMING subsystem. Since the
receiver initially does not know the ordering of the twisted
pairs, correct ordering must be determined automatically
by the receiver during start-up. Delay skew compensation
and twisted pair ordering is part of the training function performed during start-up mode of operation.
4.5 Gigabit MII (GMII)
The Gigabit Media Independent Interface (GMII) is
intended for use between Ethernet PHYs and Station Management (STA) entities and is selected by either hardware
or software configuration. The purpose of GMII is to make
various physical media transparent to the MAC layer.
4.4.3 Forward Error Correction (FEC) Decoder
The FEC Decoder decodes the quartet of quinary (PAM-5)
symbols and generates the corresponding Sdn binary
words. The FEC decoder uses a standard 8 state Trellis
code operation. Initially, Sdn[3:0] may not have the proper
bit ordering, however, correct ordering is established by the
reordering algorithm at start-up.
The GMII Interface accepts either GMII or MII data, control
and status signals and routes them either to the
1000BASE-T, 100BASE-TX, or 10BASE-T modules,
respectively.
4.4.4 Descrambler Subsystem
The descrambler block performs the reverse scrambling
function that was implemented in the transmit section. This
sub block works in conjunction with the delay skew control.
It provides the receiver generated Sdn[3:0] bits for comparison in the delay skew control function.
www.national.com
52
DP83865
4.0 Functional Description (Continued)
The mapping of the MAC interface is illustrated below in
Table 51.
RGMII
Table 51. GMII/RGMII/MII Mapping
GMII
RGMII
MII
RXD[3:0]
RX[3:0]
RXD[3:0]
TX_CLK
TD0
TD1
TD2
RXD[4:7]
RX_DV
RCK
RX_ER
RXDV_ER
RX_CLK
TXD[3:0]
TD3
TXEN_ER
RX_DV
RX_ER
TX_CLK
TX[3:0]
TXD[3:0]
RD0
TXEN_ER
TX_EN
RD1
RD2
RD3
RXDV_ER
TXD[4:7]
TX_EN
TX_ER
GTX_CLK
TX_ER
Figure 5. RGMII Signals
TCK
COL
CRS
BLOCK
RX_CLK
RX_CLK
RGMII_SEL1
GPHY
FUNCTIONAL
RGMII_SEL0
COL
4.6.1 1000 Mbps Mode Operation
CRS
All RGMII signals are positive logic. The 8-bit data is multiplexed by taking advantage of both clock edges. The lower
4 bits are latched on the positive clock edge and the upper
4 bits are latched on trailing clock edge. The control signals
are multiplexed into a single clock cycle using the same
technique.
The GMII interface has the following characteristics:
— Supports 10/100/1000 Mb/s operation
— Data and delimiters are synchronous to clock references
— Provides independent 8-bit wide transmit and receive
data paths
— Provides a simple management interface
— Uses signal levels that are compatible with common
CMOS digital ASIC processes and some bipolar processes
— Provides for Full Duplex operation
The GMII interface is defined in the IEEE 802.3z document
Clause 35. In each direction of data transfer, there are Data
(an eight-bit bundle), Delimiter, Error, and Clock signals.
GMII signals are defined such that an implementation may
multiplex most GMII signals with the similar PCS service
interface defined in IEEE 802.3u Clause 22.
To reduce power consumption of RGMII interface,
TXEN_ER and RXDV_ER are encoded in a manner that
minimize transitions during normal network operation. This
is done by following encoding method. Note that the value
of GMII_TX_ER and GMII_TX_EN are valid at the rising
edge of the clock. In RGMII mode, GMII_TX_ER is
resented on TXEN_ER at the falling edge of the TCK clock.
RXDV_ER coding is implemented the same fashion.
TXEN_ER
工商网监
湘ICP备2023018690号
