DP83849I
DP83849I PHYTER DUAL Industrial Temperature with Flexible Port Switching
Dual Port 10/100 Mb/s Ethernet Physical Layer Transceiver
Literature Number: SNOSAX1D
© 2008 National Semiconductor Corporation www.national.com
1
DP83849I PHYTER® DUAL Industrial Temperature with Flexible Port Switching
Dual Port 10/100 Mb/s Ethernet Physical Layer Transceiver
May 2008
DP83849I PHYTER® DUAL Industrial Temperature with Flexible Port Switching
Dual Port 10/100 Mb/s Ethernet Physical Layer Transceiver
General Description
The number of applications requiring Ethernet Con-
nectivity continues to expand. Along with this
increased market demand is a change in application
requirements. Where single channel Ethernet used to
be sufficient, many applications such as wireless
remote base stations and industrial networking now
require DUAL Port functionality for redundancy or sys-
tem management.
The DP83849I is a highly reliable, feature rich device
perfectly suited for industrial applications enabling
Ethernet on the factory floor. The DP83849I features
two fully independent 10/100 ports for multi-port appli-
cations. NATIONAL’s unique port switching capability
also allows the two ports to be configured to provide
fully integrated range extension, media conversion,
hardware based failover and port monitoring.
The DP83849I provides optimum flexibility in MPU
selection by supporting both MII and RMII interfaces.
In addition this device includes a powerful new diag-
nostics tool to ensure initial network operation and
maintenance.
In addition to the TDR scheme, commonly used for
detecting faults during installation, NATIONALs inno-
vative cable diagnostics provides for real time continu-
ous monitoring of the link quality. This allows the
system designer to implement a fault prediction mech-
anism to detect and warn of changing or deteriorating
link conditions.
With the DP83849I, National Semiconductor continues
to build on its Ethernet expertise and leadership posi-
tion by providing a powerful combination of features
and flexibility, easing Ethernet implementation for the
system designer.
System Diagram
PHYTER is a registered trademark of National Semiconductor Corporation
Status
10BASE-T
or
100BASE-TX
MII/RMII/SNI
25 MHz
Magnetics
RJ-45
Clock LEDs
DP83849I
MPU/CPU
Source
Typical Application
MAC MAC
MII/RMII/SNI
10BASE-T
or
100BASE-TX
Magnetics
RJ-45
Port A
Port B
Features
Low-power 3.3V, 0.18µm CMOS technology
Low power consumption <600mW Typical
3.3V MAC Interface
Auto-MDIX for 10/100 Mb/s
Energy Detection Mode
Flexible MII Port Assignment
Dynamic Integrity Utility
Dynamic Link Quality Monitoring
TDR based Cable Diagnostic and Cable Length Detection
Optimized Latency for Real Time Ethernet Operation
Reference Clock out
RMII Rev. 1.2 Interface (configurable)
SNI Interface (configurable)
MII Serial Management Interface (MDC and MDIO)
IEEE 802.3u MII
IEEE 802.3u Auto-Negotiation and Parallel Detection
IEEE 802.3u ENDEC, 10BASE-T transceivers and filters
IEEE 802.3u PCS, 100BASE-TX transceivers and filters
IEEE 1149.1 JTAG
Integrated ANSI X3.263 compliant TP-PMD physical sub-layer
with adaptive equalization and Baseline Wander compensation
Programmable LED support for Link, 10 /100 Mb/s Mode, Activ-
ity, Duplex and Collision Detect
Single register access for complete PHY status
10/100 Mb/s packet BIST (Built in Self Test)
80-pin TQFP package (12mm x 12mm)
Applications
Medical Instrumentation
Factory Automation
Motor & Motion Control
Wireless Remote Base Station
General Embedded Applications
www.national.com 2
DP83849I
MANAGEMENT
RXTXTX RX
LED
DRIVERS
LEDS
INTERFACE
10/100 PHY CORE 10/100 PHY CORE
BOUNDARY
JTAG
SCAN
MII/RMII/SNI
PORT A
MII/RMII/SNI
PORT B
MII MANAGEMENT
INTERFACE
MDC MDIO
LED
DRIVERS
LEDS
PORT B
PORT A
TPTD± TPRD± TPTD± TPRD±
Figure 1. DP83849I Functional Block Diagram
3 www.national.com
DP83849I
Table of Contents
1.0 Pin Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.1 Serial Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
1.2 MAC Data Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
1.3 Clock Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
1.4 LED Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
1.5 JTAG Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
1.6 Reset and Power Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
1.7 Strap Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
1.8 10 Mb/s and 100 Mb/s PMD Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
1.9 Special Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
1.10 Power Supply Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
1.11 Package Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
2.0 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.1 Auto-Negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
2.1.1 Auto-Negotiation Pin Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.1.2 Auto-Negotiation Register Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.1.3 Auto-Negotiation Parallel Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.1.4 Auto-Negotiation Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.1.5 Enabling Auto-Negotiation via Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.1.6 Auto-Negotiation Complete Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.2 Auto-MDIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
2.3 PHY Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
2.3.1 MII Isolate Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.4 LED Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
2.4.1 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.4.2 LED Direct Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.5 Half Duplex vs. Full Duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
2.6 Internal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
2.7 BIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
3.0 MAC Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1 MII Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
3.1.1 Nibble-wide MII Data Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1.2 Collision Detect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1.3 Carrier Sense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.2 Reduced MII Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
3.3 10 Mb Serial Network Interface (SNI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
3.4 Single Clock MII Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
3.5 Flexible MII Port Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
3.5.1 RX MII Port Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.5.2 TX MII Port Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.5.3 Common Flexible MII Port Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.5.4 Strapped Extender Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.5.5 Notes and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.6 802.3u MII Serial Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
3.6.1 Serial Management Register Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.6.2 Serial Management Access Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.6.3 Serial Management Preamble Suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.6.4 Simultaneous Register Write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.0 Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.1 100BASE-TX TRANSMITTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
4.1.1 Code-group Encoding and Injection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.1.2 Scrambler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.1.3 NRZ to NRZI Encoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.1.4 Binary to MLT-3 Convertor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.2 100BASE-TX RECEIVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
www.national.com 4
DP83849I
4.2.1 Analog Front End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.2.2 Digital Signal Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.2.2.1 Digital Adaptive Equalization and Gain Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.2.2.2 Base Line Wander Compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.2.3 Signal Detect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.2.4 MLT-3 to NRZI Decoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.2.5 NRZI to NRZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.2.6 Serial to Parallel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.2.7 Descrambler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.2.8 Code-group Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.2.9 4B/5B Decoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.2.10 100BASE-TX Link Integrity Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.2.11 Bad SSD Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.3 10BASE-T TRANSCEIVER MODULE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
4.3.1 Operational Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.3.2 Smart Squelch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.3.3 Collision Detection and SQE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.3.4 Carrier Sense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.3.5 Normal Link Pulse Detection/Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.3.6 Jabber Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.3.7 Automatic Link Polarity Detection and Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.3.8 Transmit and Receive Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.3.9 Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.3.10 Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.0 Design Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.1 TPI Network Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
5.2 ESD Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
5.3 Clock In (X1) Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
5.4 Power Feedback Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
5.5 Power Down/Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
5.5.1 Power Down Control Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.5.2 Interrupt Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.6 Energy Detect Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
5.7 Link Diagnostic Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
5.7.1 Linked Cable Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.7.1.1 Polarity Reversal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.7.1.2 Cable Swap Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.7.1.3 100MB Cable Length Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.7.1.4 Frequency Offset Relative to Link Partner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.7.1.5 Cable Signal Quality Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.7.2 Link Quality Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.7.2.1 Link Quality Monitor Control and Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.7.2.2 Checking Current Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.7.2.3 Threshold Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.7.3 TDR Cable Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.7.3.1 TDR Pulse Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.7.3.2 TDR Pulse Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.7.3.3 TDR Control Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.7.3.4 TDR Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.0 Reset Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.1 Hardware Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
6.2 Full Software Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
6.3 Soft Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
7.0 Register Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7.1 Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
7.1.1 Basic Mode Control Register (BMCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.1.2 Basic Mode Status Register (BMSR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
7.1.3 PHY Identifier Register #1 (PHYIDR1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
7.1.4 PHY Identifier Register #2 (PHYIDR2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
7.1.5 Auto-Negotiation Advertisement Register (ANAR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5 www.national.com
DP83849I
7.1.6 Auto-Negotiation Link Partner Ability Register (ANLPAR) (BASE Page) . . . . . . . . . . . . . . . . 59
7.1.7 Auto-Negotiation Link Partner Ability Register (ANLPAR) (Next Page) . . . . . . . . . . . . . . . . . 60
7.1.8 Auto-Negotiate Expansion Register (ANER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
7.1.9 Auto-Negotiation Next Page Transmit Register (ANNPTR) . . . . . . . . . . . . . . . . . . . . . . . . . . 62
7.1.10 PHY Status Register (PHYSTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
7.1.11 MII Interrupt Control Register (MICR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7.1.12 MII Interrupt Status and Misc. Control Register (MISR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7.1.13 Page Select Register (PAGESEL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
7.2 Extended Registers - Page 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
7.2.1 False Carrier Sense Counter Register (FCSCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
7.2.2 Receiver Error Counter Register (RECR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
7.2.3 100 Mb/s PCS Configuration and Status Register (PCSR) . . . . . . . . . . . . . . . . . . . . . . . . . . 67
7.2.4 RMII and Bypass Register (RBR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.2.5 LED Direct Control Register (LEDCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
7.2.6 PHY Control Register (PHYCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
7.2.7 10 Base-T Status/Control Register (10BTSCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
7.2.8 CD Test and BIST Extensions Register (CDCTRL1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
7.2.9 Phy Control Register 2 (PHYCR2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
7.2.10 Energy Detect Control (EDCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
7.3 Link Diagnostics Registers - Page 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
7.3.1 100Mb Length Detect Register (LEN100_DET), Page 2, address 14h . . . . . . . . . . . . . . . . . 77
7.3.2 100Mb Frequency Offset Indication Register (FREQ100), Page 2, address 15h . . . . . . . . . 77
7.3.3 TDR Control Register (TDR_CTRL), Page 2, address 16h . . . . . . . . . . . . . . . . . . . . . . . . . . 78
7.3.4 TDR Window Register (TDR_WIN), Page 2, address 17h . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
7.3.5 TDR Peak Register (TDR_PEAK), Page 2, address 18h . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
7.3.6 TDR Threshold Register (TDR_THR), Page 2, address 19h . . . . . . . . . . . . . . . . . . . . . . . . . 79
7.3.7 Variance Control Register (VAR_CTRL), Page 2, address 1Ah . . . . . . . . . . . . . . . . . . . . . . 80
7.3.8 Variance Data Register (VAR_DATA), Page 2, address 1Bh . . . . . . . . . . . . . . . . . . . . . . . . 80
7.3.9 Link Quality Monitor Register (LQMR), Page 2, address 1Dh . . . . . . . . . . . . . . . . . . . . . . . . 81
7.3.10 Link Quality Data Register (LQDR), Page 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
8.0 Electrical Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
8.1 DC Specs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
8.2 AC Specs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
8.2.1 Power Up Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
8.2.2 Reset Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
8.2.3 MII Serial Management Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
8.2.4 100 Mb/s MII Transmit Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
8.2.5 100 Mb/s MII Receive Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
8.2.6 100BASE-TX MII Transmit Packet Latency Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
8.2.7 100BASE-TX MII Transmit Packet Deassertion Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
8.2.8 100BASE-TX Transmit Timing (tR/F & Jitter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
8.2.9 100BASE-TX MII Receive Packet Latency Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
8.2.10 100BASE-TX MII Receive Packet Deassertion Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
8.2.11 10 Mb/s MII Transmit Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
8.2.12 10 Mb/s MII Receive Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
8.2.13 10 Mb/s Serial Mode Transmit Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
8.2.14 10 Mb/s Serial Mode Receive Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
8.2.15 10BASE-T Transmit Timing (Start of Packet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
8.2.16 10BASE-T Transmit Timing (End of Packet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
8.2.17 10BASE-T Receive Timing (Start of Packet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.2.18 10BASE-T Receive Timing (End of Packet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.2.19 10 Mb/s Heartbeat Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
8.2.20 10 Mb/s Jabber Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
8.2.21 10BASE-T Normal Link Pulse Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
8.2.22 Auto-Negotiation Fast Link Pulse (FLP) Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
8.2.23 100BASE-TX Signal Detect Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
8.2.24 100 Mb/s Internal Loopback Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
8.2.25 10 Mb/s Internal Loopback Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
8.2.26 RMII Transmit Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8.2.27 RMII Receive Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
8.2.28 Single Clock MII (SCMII) Transmit Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
www.national.com 6
DP83849I
8.2.29 Single Clock MII (SCMII) Receive Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.2.30 Isolation Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8.2.31 CLK2MAC Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8.2.32 100 Mb/s X1 to TX_CLK Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
9.0 Physical Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
7 www.national.com
DP83849I
List of Figures
Figure 1. DP83849I Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Figure 2. PHYAD Strapping Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 3. AN Strapping and LED Loading Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 4. MII Port Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 5. Typical MDC/MDIO Read Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 6. Typical MDC/MDIO Write Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 7. 100BASE-TX Transmit Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 8. 100BASE-TX Receive Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 9. EIA/TIA Attenuation vs. Frequency for 0, 50, 100, 130 & 150 meters of CAT 5 cable . . . . . . . . . . . 36
Figure 10. 100BASE-TX BLW Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 11. 10BASE-T Twisted Pair Smart Squelch Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 12. 10/100 Mb/s Twisted Pair Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 13. Crystal Oscillator Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 14. Power Feeback Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
www.national.com 8
DP83849I
List of Table
Table 1. Auto-Negotiation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Table 2. PHY Address Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Table 3. LED Mode Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Table 4. Supported packet sizes at +/-50ppm frequency accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Table 5. Supported SCMII packet sizes at +/-50ppm frequency accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Table 6. RX MII Port Mapping Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Table 7. RX MII Port Mapping Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Table 8. TX MII Port Mapping Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Table 9. TX MII Port Mapping Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Table 10. Common Flexible MII Port Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Table 11. Common Strapped Extender Mode Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Table 12. Typical MDIO Frame Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Table 13. 4B5B Code-Group Encoding/Decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Table 14. 25 MHz Oscillator Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Table 15. 50 MHz Oscillator Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Table 16. 25 MHz Crystal Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Table 17. Link Quality Monitor Parameter Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Table 18. Register Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Table 19. Register Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Table 20. Basic Mode Control Register (BMCR), address 00h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Table 21. Basic Mode Status Register (BMSR), address 01h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Table 22. PHY Identifier Register #1 (PHYIDR1), address 02h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Table 23. PHY Identifier Register #2 (PHYIDR2), address 03h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Table 24. Negotiation Advertisement Register (ANAR), address 04h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Table 25. Auto-Negotiation Link Partner Ability Register (ANLPAR) (BASE Page), address 05h . . . . . . . . .59
Table 26. Auto-Negotiation Link Partner Ability Register (ANLPAR) (Next Page), address 05h . . . . . . . . . .60
Table 27. Auto-Negotiate Expansion Register (ANER), address 06h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Table 28. Auto-Negotiation Next Page Transmit Register (ANNPTR), address 07h . . . . . . . . . . . . . . . . . . . .62
Table 29. PHY Status Register (PHYSTS), address 10h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Table 30. MII Interrupt Control Register (MICR), address 11h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Table 31. MII Interrupt Status and Misc. Control Register (MISR), address 12h . . . . . . . . . . . . . . . . . . . . . . .65
Table 32. Page Select Register (PAGESEL), address 13h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Table 33. False Carrier Sense Counter Register (FCSCR), address 14h . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Table 34. Receiver Error Counter Register (RECR), address 15h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Table 35. 100 Mb/s PCS Configuration and Status Register (PCSR), address 16h . . . . . . . . . . . . . . . . . . . . .67
Table 36. RMII and Bypass Register (RBR), addresses 17h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Table 37. LED Direct Control Register (LEDCR), address 18h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Table 38. PHY Control Register (PHYCR), address 19h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Table 39. 10Base-T Status/Control Register (10BTSCR), address 1Ah . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Table 40. CD Test and BIST Extensions Register (CDCTRL1), address 1Bh . . . . . . . . . . . . . . . . . . . . . . . . . .75
Table 41. Phy Control Register 2 (PHYCR2), address 1Ch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Table 42. Energy Detect Control (EDCR), address 1Dh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
Table 43. 100Mb Length Detect Register (LEN100_DET), address 14h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Table 44. 100Mb Frequency Offset Indication Register (FREQ100), address 15h . . . . . . . . . . . . . . . . . . . . . .77
Table 45. TDR Control Register (TDR_CTRL), address 16h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Table 46. TDR Window Register (TDR_WIN), address 17h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Table 47. TDR Peak Register (TDR_PEAK), address 18h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Table 48. TDR Threshold Register (TDR_THR), address 19h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Table 49. Variance Control Register (VAR_CTRL), address 1Ah . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Table 50. Variance Data Register (VAR_DATA), address 1Bh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Table 51. Link Quality Monitor Register (LQMR), address 1Dh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Table 52. Link Quality Data Register (LQDR), address 1Eh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
9 www.national.com
DP83849I
Pin Layout
Top View
NS Package Number VHB80A
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
40
39
38
37
36
35
34
33
32
31
30
29
28
27
26
25
24
23
22
21
60
59
58
57
56
55
54
53
52
51
50
49
48
47
46
45
44
43
42
41
DP83849IVS
o
ANAGND4
TPRDM_B
TPRDP_B
CDGND2
TPTDM_B
TPTDP_B
PFBIN3
ANAGND3
RBIAS
PFBOUT
ANA33VDD
ANAGND2
PFBIN2
TPTDP_A
TPTDM_A
CDGND1
TPRDP_A
TPRDM_A
ANAGND1
LED_ACT/LED_COL/AN_EN_A
CRS_B/CRS_DV_B/LED_CFG_B
RX_DV_B/MII_MODE_B
RX_CLK_B
IOGND3
IOVDD3
MDIO
MDC
CLK2MAC
X2
X1
RESET_N
TCK
TDO
TMS
TRSTN
TDI
IOGND4
IOVDD4
RX_CLK_A
RX_DV_A/MII_MODE_A
CRS_A/CRS_DV_A/LED_CFG_A
RX_ER_A/MDIX_EN_A
COL_A
RXD0_A/PHYAD1
RXD1_A/PHYAD2
COREGND1
PFBIN1
RXD2_A/CLK2MAC_DIS
RXD3_A/ED_EN_A
IOGND1
IOVDD1
TX_CLK_A
TX_EN_A
TXD0_A
TXD1_A
TXD2_A
TXD3_A/SNI_MODE_A
PWRDOWN_INT_A
LED_LINK_A/AN0_A
LED_SPEED_A/AN1_A
RX_ER_B/MDIX_EN_B
COL_B
RXD0_B/PHYAD3
RXD1_B/PHYAD4
RXD2_B/EXTENDER_EN
COREGND2
PFBIN4
RXD3_B/ED_EN_B
IOGND2
IOVDD2
TX_CLK_B
TX_EN_B
TXD0_B
TXD1_B
TXD2_B
TXD3_B/SNI_MODE_B
PWRDOWN_INT_B
LED_LINK_B/AN0_B
LED_SPEED_B/AN1_B
LED_ACT/LED_COL/AN_EN_B
www.national.com 10
DP83849I
1.0 Pin Descriptions
The DP83849I pins are classified into the following inter-
face categories (each interface is described in the sections
that follow):
Serial Management Interface
MAC Data Interface
Clock Interface
LED Interface
—JTAG Interface
Reset and Power Down
Strap Options
10/100 Mb/s PMD Interface
Special Connect Pins
Power and Ground pins
Note: Strapping pin option. Please see Section 1.7 for strap
definitions.
All DP83849I signal pins are I/O cells regardless of the par-
ticular use. The definitions below define the functionality of
the I/O cells for each pin.
1.1 Serial Management Interface
1.2 MAC Data Interface
Type: I Input
Type: O Output
Type: I/O Input/Output
Type OD Open Drain
Type: PD,PU Internal Pulldown/Pullup
Type: S Strapping Pin (All strap pins have weak in-
ternal pull-ups or pull-downs. If the default
strap value is to be changed then an exter-
nal 2.2 k resistor should be used. Please
see Section 1.7 for details.)
Signal Name Type Pin # Description
MDC I67 MANAGEMENT DATA CLOCK: Synchronous clock to the MDIO
management data input/output serial interface which may be asyn-
chronous to transmit and receive clocks. The maximum clock rate is
25 MHz with no minimum clock rate.
MDIO I/O 66 MANAGEMENT DATA I/O: Bi-directional management instruc-
tion/data signal that may be sourced by the station management entity
or the PHY. This pin requires a 1.5 k pullup resistor.
Signal Name Type Pin # Description
TX_CLK_A
TX_CLK_B
O12
50
MII TRANSMIT CLOCK: 25 MHz Transmit clock output in 100 Mb/s
mode or 2.5 MHz in 10 Mb/s mode derived from the 25 MHz reference
clock.
Unused in RMII mode. The device uses the X1 reference clock input
as the 50 MHz reference for both transmit and receive.
SNI TRANSMIT CLOCK: 10 MHz Transmit clock output in 10 Mb SNI
mode. The MAC should source TX_EN and TXD_0 using this clock.
TX_EN_A
TX_EN_B
I13
49
MII TRANSMIT ENABLE: Active high input indicates the presence of
valid data inputs on TXD[3:0].
RMII TRANSMIT ENABLE: Active high input indicates the presence
of valid data on TXD[1:0].
SNI TRANSMIT ENABLE: Active high input indicates the presence of
valid data on TXD_0.
TXD[3:0]_A
TXD[3:0]_B
I17,16,15,14
45,46,47,48
MII TRANSMIT DATA: Transmit data MII input pins, TXD[3:0], that
accept data synchronous to the TX_CLK (2.5 MHz in 10 Mb/s mode
or 25 MHz in 100 Mb/s mode).
RMII TRANSMIT DATA: Transmit data RMII input pins, TXD[1:0],
that accept data synchronous to the 50 MHz reference clock.
SNI TRANSMIT DATA: Transmit data SNI input pin, TXD_0, that ac-
cept data synchronous to the TX_CLK (10 MHz in 10 Mb/s SNI mode).
11 www.national.com
DP83849I
RX_CLK_A
RX_CLK_B
O79
63
MII RECEIVE CLOCK: Provides the 25 MHz recovered receive
clocks for 100 Mb/s mode and 2.5 MHz for 10 Mb/s mode.
Unused in RMII mode. The device uses the X1 reference clock input
as the 50 MHz reference for both transmit and receive.
SNI RECEIVE CLOCK: Provides the 10 MHz recovered receive
clocks for 10 Mb/s SNI mode.
RX_DV_A
RX_DV_B
O80
62
MII RECEIVE DATA VALID: Asserted high to indicate that valid data
is present on the corresponding RXD[3:0].
RMII RECEIVE DATA VALID: Asserted high to indicate that valid
data is present on the corresponding RXD[1:0]. This signal is not re-
quired in RMII mode, since CRS_DV includes the RX_DV signal, but
is provided to allow simpler recovery of the Receive data.
This pin is not used in SNI mode.
RX_ER_A
RX_ER_B
O 2
60
MII RECEIVE ERROR: Asserted high synchronously to RX_CLK to
indicate that an invalid symbol has been detected within a received
packet in 100 Mb/s mode.
RMII RECEIVE ERROR: Asserted high synchronously to X1 whenev-
er an invalid symbol is detected, and CRS_DV is asserted in 100 Mb/s
mode. This pin is also asserted on detection of a False Carrier event.
This pin is not required to be used by a MAC in RMII mode, since the
Phy is required to corrupt data on a receive error.
This pin is not used in SNI mode.
RXD[3:0]_A
RXD[3:0]_B
O9,8,5,4
53,56,57,58
MII RECEIVE DATA: Nibble wide receive data signals driven syn-
chronously to the RX_CLK, 25 MHz for 100 Mb/s mode, 2.5 MHz for
10 Mb/s mode). RXD[3:0] signals contain valid data when RX_DV is
asserted.
RMII RECEIVE DATA: 2-bits receive data signals, RXD[1:0], driven
synchronously to the X1 clock, 50 MHz.
SNI RECEIVE DATA: Receive data signal, RXD_0, driven synchro-
nously to the RX_CLK. RXD_0 contains valid data when CRS is as-
serted. RXD[3:1] are not used in this mode.
CRS_A/CRS_DV_A
CRS_B/CRS_DV_B
O 1
61
MII CARRIER SENSE: Asserted high to indicate the receive medium
is non-idle.
RMII CARRIER SENSE/RECEIVE DATA VALID: This signal com-
bines the RMII Carrier and Receive Data Valid indications. For a de-
tailed description of this signal, see the RMII Specification.
SNI CARRIER SENSE: Asserted high to indicate the receive medium
is non-idle. It is used to frame valid receive data on the RXD_0 signal.
COL_A
COL_B
O 3
59
MII COLLISION DETECT: Asserted high to indicate detection of a
collision condition (simultaneous transmit and receive activity) in 10
Mb/s and 100 Mb/s Half Duplex Modes.
While in 10BASE-T Half Duplex mode with heartbeat enabled this pin
is also asserted for a duration of approximately 1µs at the end of
transmission to indicate heartbeat (SQE test).
In Full Duplex Mode, for 10 Mb/s or 100 Mb/s operation, this signal is
always logic 0. There is no heartbeat function during 10 Mb/s full du-
plex operation.
RMII COLLISION DETECT: Per the RMII Specification, no COL sig-
nal is required. The MAC will recover CRS from the CRS_DV signal
and use that along with its TX_EN signal to determine collision.
SNI COLLISION DETECT: Asserted high to indicate detection of a
collision condition (simultaneous transmit and receive activity) in 10
Mb/s SNI mode.
Signal Name Type Pin # Description
www.national.com 12
DP83849I
1.3 Clock Interface
1.4 LED Interface
The DP83849I supports three configurable LED pins. The
LEDs support two operational modes which are selected
by the LED mode strap and a third operational mode which
is register configurable. The definitions for the LEDs for
each mode are detailed below. Since the LEDs are also
used as strap options, the polarity of the LED output is
dependent on whether the pin is pulled up or down.
Signal Name Type Pin # Description
X1 I70 CRYSTAL/OSCILLATOR INPUT: This pin is the primary clock
reference input for the DP83849I and must be connected to a 25
MHz 0.005% (+50 ppm) clock source. The DP83849I supports ei-
ther an external crystal resonator connected across pins X1 and
X2, or an external CMOS-level oscillator source connected to pin
X1 only.
RMII REFERENCE CLOCK: This pin is the primary clock refer-
ence input for the RMII mode and must be connected to a 50 MHz
0.005% (+50 ppm) CMOS-level oscillator source.
X2 O69 CRYSTAL OUTPUT: This pin is the primary clock reference out-
put to connect to an external 25 MHz crystal resonator device.
This pin must be left unconnected if an external CMOS oscillator
clock source is used.
CLK2MAC O68 CLOCK TO MAC:
In MII mode, this pin provides a 25 MHz clock output to the sys-
tem.
In RMII mode, this pin provides a 50 MHz clock output to the sys-
tem.
This allows other devices to use the reference clock from the
DP83849I without requiring additional clock sources.
If the system does not require the CLK2MAC signal, the
CLK2MAC output should be disabled via the CLK2MAC disable
strap.
Signal Name Type Pin # Description
LED_LINK_A
LED_LINK_B
I/O 19
43
LINK LED: In Mode 1, this pin indicates the status of the LINK.
The LED will be ON when Link is good.
LINK/ACT LED: In Mode 2 and Mode 3, this pin indicates transmit
and receive activity in addition to the status of the Link. The LED
will be ON when Link is good. It will blink when the transmitter or
receiver is active.
LED_SPEED_A
LED_SPEED_B
I/O 20
42
SPEED LED: The LED is ON when device is in 100 Mb/s and OFF
when in 10 Mb/s. Functionality of this LED is independent of mode
selected.
LED_ACT/LED_COL_A
LED_ACT/LED_COL_B
I/O 21
41
ACTIVITY LED: In Mode 1, this pin is the Activity LED which is
ON when activity is present on either Transmit or Receive.
COLLISION/DUPLEX LED: In Mode 2, this pin by default indi-
cates Collision detection. For Mode 3, this LED output may be
programmed to indicate Full-duplex status instead of Collision.
13 www.national.com
DP83849I
1.5 JTAG Interface
1.6 Reset and Power Down
1.7 Strap Options
The DP83849I uses many of the functional pins as strap
options. The values of these pins are sampled during reset
and used to strap the device into specific modes of opera-
tion. The strap option pin assignments are defined below.
The functional pin name is indicated in parentheses.
A 2.2 k resistor should be used for pull-down or pull-up to
change the default strap option. If the default option is
required, then there is no need for external pull-up or pull
down resistors. Since these pins may have alternate func-
tions after reset is deasserted, they should not be con-
nected directly to VCC or GND.
Signal Name Type Pin # Description
TCK I, PU 72 TEST CLOCK
This pin has a weak internal pullup.
TDO O73 TEST OUTPUT
TMS I, PU 74 TEST MODE SELECT
This pin has a weak internal pullup.
TRSTN I, PU 75 TEST RESET Active low test reset.
This pin has a weak internal pullup.
TDI I, PU 76 TEST DATA INPUT
This pin has a weak internal pullup.
Signal Name Type Pin # Description
RESET_N I, PU 71 RESET: Active Low input that initializes or re-initializes the
DP83849I. Asserting this pin low for at least 1 µs will force a reset
process to occur. All internal registers will re-initialize to their de-
fault states as specified for each bit in the Register Block section.
All strap options are re-initialized as well.
PWRDOWN_INT_A
PWRDOWN_INT_B
I, PU 18
44
The default function of this pin is POWER DOWN.
POWER DOWN: The pin is an active low input in this mode and
should be asserted low to put the device in a Power Down mode.
INTERRUPT: The pin is an open drain output in this mode and will
be asserted low when an interrupt condition occurs. Although the
pin has a weak internal pull-up, some applications may require an
external pull-up resister. Register access is required for the pin to
be used as an interrupt mechanism. See Section 5.5.2 Interrupt
Mechanism for more details on the interrupt mechanisms.
Signal Name Type Pin # Description
PHYAD1 (RXD0_A)
PHYAD2 (RXD1_A)
PHYAD3 (RXD0_B)
PHYAD4 (RXD1_B)
S, O, PD
S, O, PD
S, O, PD
S, O, PD
4
5
58
57
PHY ADDRESS [4:1]: The DP83849I provides four PHY address
pins, the state of which are latched into the PHYCTRL register at
system Hardware-Reset. Phy Address[0] selects between ports A
and B.
The DP83849I supports PHY Address strapping for Port A even
values 0 (<0000_0>) through 30 (<1111_0>). Port B will be
strapped to odd values 1 (<0000_1>) through 31 (<1111_1>).
PHYAD[4:1] pins have weak internal pull-down resistors.
www.national.com 14
DP83849I
AN_EN
(LED_ACT/LED_COL_A)
AN1_A (LED_SPEED_A)
AN0_A (LED_LINK_A)
AN_EN
(LED_ACT/LED_COL_B)
AN1_B (LED_SPEED_B)
AN0_B (LED_LINK_B)
S, O, PU 21
20
19
41
42
43
Auto-Negotiation Enable: When high, this enables Auto-Negoti-
ation with the capability set by AN0 and AN1 pins. When low, this
puts the part into Forced Mode with the capability set by AN0 and
AN1 pins.
AN0 / AN1: These input pins control the forced or advertised op-
erating mode of the DP83849I according to the following table.
The value on these pins is set by connecting the input pins to
GND (0) or VCC (1) through 2.2 kresistors. These pins should
NEVER be connected directly to GND or VCC.
The value set at this input is latched into the DP83849I at Hard-
ware-Reset.
The float/pull-down status of these pins are latched into the Basic
Mode Control Register and the Auto_Negotiation Advertisement
Register during Hardware-Reset.
The default is 111 since these pins have internal pull-ups.
MII_MODE_A (RX_DV_A)
SNI_MODE_A (TXD3_A)
MII_MODE_B (RX_DV_B)
SNI_MODE_B (TXD3_B)
S, O, PD 80
17
62
45
MII MODE SELECT: This strapping option pair determines the
operating mode of the MAC Data Interface. Default operation
(No pull-ups) will enable normal MII Mode of operation. Strapping
MII_MODE high will cause the device to be in RMII or SNI modes
of operation, determined by the status of the SNI_MODE strap.
Since the pins include internal pull-downs, the default values are
0. Both MAC Data Interfaces must have their RMII Mode settings
the same, i.e. both in RMII mode or both not in RMII mode.
The following table details the configurations:
LED_CFG_A
(CRS_A/CRS_DV_A)
LED_CFG_B
(CRS_B/CRS_DV_B)
S, O, PU 1
61
LED CONFIGURATION: This strapping option determines the
mode of operation of the LED pins. Default is Mode 1. Mode 1 and
Mode 2 can be controlled via the strap option. All modes are con-
figurable via register access.
See Ta bl e 3 on page 21 for LED Mode Selection.
Signal Name Type Pin # Description
AN_EN AN1 AN0 Forced Mode
0 0 0 10BASE-T, Half-Duplex
0 0 1 10BASE-T, Full-Duplex
0 1 0 100BASE-TX, Half-Duplex
0 1 1 100BASE-TX, Full-Duplex
AN_EN AN1 AN0 Advertised Mode
1 0 0 10BASE-T, Half/Full-Duplex
1 0 1 100BASE-TX, Half/Full-Duplex
1 1 0 10BASE-T Half-Duplex
100BASE-TX, Half-Duplex
1 1 1 10BASE-T, Half/Full-Duplex
100BASE-TX, Half/Full-Duplex
MII_MODE SNI_MODE MAC Interface Mode
0 X MII Mode
1 0 RMII Mode
1 1 10 Mb SNI Mode
15 www.national.com
DP83849I
MDIX_EN_A (RX_ER_A)
MDIX_EN_B (RX_ER_B)
S, O, PU 2
60
MDIX ENABLE: Default is to enable MDIX. This strapping option
disables Auto-MDIX. An external pull-down will disable Auto-
MDIX mode.
ED_EN_A (RXD3_A)
ED_EN_B (RXD3_B)
S, O, PD 9
53
Energy Detect ENABLE: Default is to disable Energy Detect
mode. This strapping option enables Energy Detect mode for the
port. In Energy Detect mode, the device will initially be in a low-
power state until detecting activity on the wire. An external pull-up
will enable Energy Detect mode.
CLK2MAC_DIS (RXD2_A) S, O, PD 8Clock to MAC Disable: This strapping option disables (floats) the
CLK2MAC pin. Default is to enable CLK2MAC output. An external
pullup will disable (float) the CLK2MAC pin. If the system does not
require the CLK2MAC signal, the CLK2MAC output should be dis-
abled via this strap option.
EXTENDER_EN (RXD2_B) S, O, PD 56 Extender Mode Enable: This strapping option enables Extender
Mode for both ports. When enabled, the strap will enable Single
Clock MII TX and RX modes unless RMII Mode is also strapped.
SNI Mode cannot be strapped if Extender Mode is strapped.
Signal Name Type Pin # Description
www.national.com 16
DP83849I
1.8 10 Mb/s and 100 Mb/s PMD Interface
1.9 Special Connections
1.10 Power Supply Pins
Signal Name Type Pin # Description
TPTDM_A
TPTDP_A
TPTDM_B
TPTDP_B
I/O 26
27
36
35
10BASE-T or 100BASE-TX Transmit Data
In 10BASE-T or 100BASE-TX: Differential common driver trans-
mit output (PMD Output Pair). These differential outputs are auto-
matically configured to either 10BASE-T or 100BASE-TX
signaling.
In Auto-MDIX mode of operation, this pair can be used as the Re-
ceive Input pair.
These pins require 3.3V bias for operation.
TPRDM_A
TPRDP_A
TPRDM_B
TPRDP_B
I/O 23
24
39
38
10BASE-T or 100BASE-TX Receive Data
In 10BASE-T or 100BASE-TX: Differential receive input (PMD In-
put Pair). These differential inputs are automatically configured to
accept either 100BASE-TX or 10BASE-T signaling.
In Auto-MDIX mode of operation, this pair can be used as the
Transmit Output pair.
These pins require 3.3V bias for operation.
Signal Name Type Pin # Description
RBIAS I32 Bias Resistor Connection: A 4.87 kΩ 1% resistor should be con-
nected from RBIAS to GND.
PFBOUT O31 Power Feedback Output: Parallel caps, 10µ F and 0.1µF, shou l d
be placed close to the PFBOUT. Connect this pin to PFBIN1 (pin
13), PFBIN2 (pin 27), PFBIN3 (pin35), PFBIN4 (pin 49). See
Section 5.4 for proper placement pin.
PFBIN1
PFBIN2
PFBIN3
PFBIN4
I 7
28
34
54
Power Feedback Input: These pins are fed with power from
PFBOUT pin. A small capacitor of 0.1µF should be connected
close to each pin.
Note: Do not supply power to these pins other than from
PFBOUT.
Signal Name Pin # Description
IOVDD1, IOVDD2, IOVDD3,
IOVDD4
11,51,65,78 I/O 3.3V Supply
IOGND1, IOGND2,
IOGND3, IOGND4
10,52,64,77 I/O Ground
COREGND1, COREGND2 6,55 Core Ground
CDGND1, CDGND2 25,37 CD Ground
ANA33VDD 30 Analog 3.3V Supply
ANAGND1, ANAGND2,
ANAGND3, ANAGND4
22,29,33,40 Analog Ground
17 www.national.com
DP83849I
1.11 Package Pin Assignments
VHB80A Pin
#
Pin Name
1CRS_A/CRS_DV_A/LED_CFG_A
2RX_ER_A/MDIX_EN_A
3COL_A
4RXD0_A/PHYAD1
5RXD1_A/PHYAD2
6COREGND1
7PFBIN1
8RXD2_A/CLK2MAC_DIS
9RXD3_A/ED_EN_A
10 IOGND1
11 IOVDD1
12 TX_CLK_A
13 TX_EN_A
14 TXD0_A
15 TXD1_A
16 TXD2_A
17 TXD3_A/SNI_MODE_A
18 PWRDOWN_INT_A
19 LED_LINK_A/AN0_A
20 LED_SPEED_A/AN1_A
21 LED_ACT/LED_COL/AN_EN_A
22 ANAGND1
23 TPRDM_A
24 TPRDP_A
25 CDGND1
26 TPTDM_A
27 TPTDP_A
28 PFBIN2
29 ANAGND2
30 ANA33VDD
31 PFBOUT
32 RBIAS
33 ANAGND3
34 PFBIN3
35 TPTDP_B
36 TPTDM_B
37 CDGND2
38 TPRDP_B
39 TPRDM_B
40 ANAGND4
41 LED_ACT/LED_COL/AN_EN_B
42 LED_SPEED_B/AN1_B
43 LED_LINK_B/AN0_B
44 PWRDOWN_INT_B
45 TXD3_B/SNI_MODE_B
46 TXD2_B
47 TXD1_B
48 TXD0_B
49 TX_EN_B
50 TX_CLK_B
51 IOVDD2
52 IOGND2
53 RXD3_B/ED_EN_B
54 PFBIN4
55 COREGND2
56 RXD2_B/EXTENDER_EN
57 RXD1_B/PHYAD4
58 RXD0_B/PHYAD3
59 COL_B
60 RX_ER_B/MDIX_EN_B
61 CRS_B/CRS_DV_B/LED_CFG_B
62 RX_DV_B/MII_MODE_B
63 RX_CLK_B
64 IOGND3
65 IOVDD3
66 MDIO
67 MDC
68 CLK2MAC
69 X2
70 X1
71 RESET_N
72 TCK
73 TDO
74 TMS
75 TRSTN
76 TDI
77 IOGND4
78 IOVDD4
79 RX_CLK_A
80 RX_DV_A/MII_MODE_A
VHB80A Pin
#
Pin Name
www.national.com 18
DP83849I
2.0 Configuration
This section includes information on the various configura-
tion options available with the DP83849I. The configuration
options described below include:
Media Configuration
Auto-Negotiation
PHY Address and LEDs
Half Duplex vs. Full Duplex
Isolate mode
Loopback mode
—BIST
2.1 Auto-Negotiation
The Auto-Negotiation function provides a mechanism for
exchanging configuration information between two ends of
a link segment and automatically selecting the highest per-
formance mode of operation supported by both devices.
Fast Link Pulse (FLP) Bursts provide the signalling used to
communicate Auto-Negotiation abilities between two
devices at each end of a link segment. For further detail
regarding Auto-Negotiation, refer to Clause 28 of the IEEE
802.3u specification. The DP83849I supports four different
Ethernet protocols (10 Mb/s Half Duplex, 10 Mb/s Full
Duplex, 100 Mb/s Half Duplex, and 100 Mb/s Full Duplex),
so the inclusion of Auto-Negotiation ensures that the high-
est performance protocol will be selected based on the
advertised ability of the Link Partner. The Auto-Negotiation
function within the DP83849I can be controlled either by
internal register access or by the use of the AN_EN, AN1
and AN0 pins.
2.1.1 Auto-Negotiation Pin Control
The state of AN_EN, AN0 and AN1 determines whether the
DP83849I is forced into a specific mode or Auto-Negotia-
tion will advertise a specific ability (or set of abilities) as
given in Table 1. These pins allow configuration options to
be selected without requiring internal register access.
The state of AN_EN, AN0 and AN1, upon power-up/reset,
determines the state of bits [8:5] of the ANAR register.
The Auto-Negotiation function selected at power-up or
reset can be changed at any time by writing to the Basic
Mode Control Register (BMCR) at address 00h.
2.1.2 Auto-Negotiation Register Control
When Auto-Negotiation is enabled, the DP83849I transmits
the abilities programmed into the Auto-Negotiation Adver-
tisement register (ANAR) at address 04h via FLP Bursts.
Any combination of 10 Mb/s, 100 Mb/s, Half-Duplex, and
Full Duplex modes may be selected.
Auto-Negotiation Priority Resolution:
(1) 100BASE-TX Full Duplex (Highest Priority)
(2) 100BASE-TX Half Duplex
(3) 10BASE-T Full Duplex
(4) 10BASE-T Half Duplex (Lowest Priority)
The Basic Mode Control Register (BMCR) at address 00h
provides control for enabling, disabling, and restarting the
Auto-Negotiation process. When Auto-Negotiation is dis-
abled, the Speed Selection bit in the BMCR controls
switching between 10 Mb/s or 100 Mb/s operation, and the
Duplex Mode bit controls switching between full duplex
operation and half duplex operation. The Speed Selection
and Duplex Mode bits have no effect on the mode of oper-
ation when the Auto-Negotiation Enable bit is set.
The Link Speed can be examined through the PHY Status
Register (PHYSTS) at address 10h after a Link is
achieved.
The Basic Mode Status Register (BMSR) 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
DP83849I (only the 100BASE-T4 bit is not set since the
DP83849I does not support that function).
The BMSR also provides status on:
Whether or not Auto-Negotiation is complete
Whether or not the Link Partner is advertising that a re-
mote fault has occurred
Whether or not valid link has been established
Support for Management Frame Preamble suppression
The Auto-Negotiation Advertisement Register (ANAR) indi-
cates the Auto-Negotiation abilities to be advertised by the
DP83849I. All available abilities are transmitted by default,
but any ability can be suppressed by writing to the ANAR.
Table 1. Auto-Negotiation Modes
AN_EN AN1 AN0 Forced Mode
0 0 0 10BASE-T, Half-Duplex
0 0 1 10BASE-T, Full-Duplex
0 1 0 100BASE-TX, Half-Duplex
0 1 1 100BASE-TX, Full-Duplex
AN_EN AN1 AN0 Advertised Mo0e
1 0 0 10BASE-T, Half/Full-Duplex
1 0 1 100BASE-TX, Half/Full-Duplex
1 1 0 10BASE-T Half-Duplex
100BASE-TX, Half-Duplex
1 1 1 10BASE-T, Half/Full-Duplex
100BASE-TX, Half/Full-Duplex
19 www.national.com
DP83849I
Updating the ANAR to suppress an ability is one way for a
management agent to change (restrict) the technology that
is used.
The Auto-Negotiation Link Partner Ability Register
(ANLPAR) at address 05h is used to receive the base link
code word as well as all next page code words during the
negotiation. Furthermore, the ANLPAR will be updated to
either 0081h or 0021h for parallel detection to either 100
Mb/s or 10 Mb/s respectively.
The Auto-Negotiation Expansion Register (ANER) indi-
cates additional Auto-Negotiation status. The ANER pro-
vides status on:
Whether or not a Parallel Detect Fault has occurred
Whether or not the Link Partner supports the Next Page
function
Whether or not the DP83849I supports the Next Page
function
Whether or not the current page being exchanged by
Auto-Negotiation has been received
Whether or not the Link Partner supports Auto-Negotia-
tion
2.1.3 Auto-Negotiation Parallel Detection
The DP83849I supports the Parallel Detection function as
defined in the IEEE 802.3u specification. Parallel Detection
requires both the 10 Mb/s and 100 Mb/s receivers to moni-
tor the receive signal and report link status to the Auto-
Negotiation function. Auto-Negotiation uses this informa-
tion to configure the correct technology in the event that the
Link Partner does not support Auto-Negotiation but is
transmitting link signals that the 100BASE-TX or 10BASE-
T PMAs recognize as valid link signals.
If the DP83849I completes Auto-Negotiation as a result of
Parallel Detection, bits 5 and 7 within the ANLPAR register
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 deter-
mine that negotiation completed via Parallel Detection by
reading a zero in the Link Partner Auto-Negotiation Able bit
once the Auto-Negotiation Complete bit is set. If configured
for parallel detect mode and any condition other than a sin-
gle good link occurs then the parallel detect fault bit will be
set.
2.1.4 Auto-Negotiation Restart
Once Auto-Negotiation has completed, it may be restarted
at any time by setting bit 9 (Restart Auto-Negotiation) of the
BMCR to one. If the mode configured by a successful Auto-
Negotiation loses a valid link, then the Auto-Negotiation
process will resume and attempt to determine the configu-
ration for the link. This function ensures that a valid config-
uration is maintained if the cable becomes disconnected.
A renegotiation request from any entity, such as a manage-
ment agent, will cause the DP83849I to halt any transmit
data and link pulse activity until the break_link_timer
expires (~1500 ms). Consequently, the Link Partner will go
into link fail and normal Auto-Negotiation resumes. The
DP83849I will resume Auto-Negotiation after the
break_link_timer has expired by issuing FLP (Fast Link
Pulse) bursts.
2.1.5 Enabling Auto-Negotiation via Software
It is important to note that if the DP83849I has been initial-
ized upon power-up as a non-auto-negotiating device
(forced technology), and it is then required that Auto-Nego-
tiation or re-Auto-Negotiation be initiated via software,
bit 12 (Auto-Negotiation Enable) of the Basic Mode Control
Register (BMCR) must first be cleared and then set for any
Auto-Negotiation function to take effect.
2.1.6 Auto-Negotiation Complete Time
Parallel detection and Auto-Negotiation take approximately
2-3 seconds to complete. In addition, Auto-Negotiation with
next page should take approximately 2-3 seconds to com-
plete, depending on the number of next pages sent.
Refer to Clause 28 of the IEEE 802.3u standard for a full
description of the individual timers related to Auto-Negotia-
tion.
2.2 Auto-MDIX
When enabled, this function utilizes Auto-Negotiation to
determine the proper configuration for transmission and
reception of data and subsequently selects the appropriate
MDI pair for MDI/MDIX operation. The function uses a ran-
dom seed to control switching of the crossover circuitry.
This implementation complies with the corresponding IEEE
802.3 Auto-Negotiation and Crossover Specifications.
Auto-MDIX is enabled by default and can be configured via
strap or via PHYCR (19h) register, bits [15:14].
Neither Auto-Negotiation nor Auto-MDIX is required to be
enabled in forcing crossover of the MDI pairs. Forced
crossover can be achieved through the FORCE_MDIX bit,
bit 14 of PHYCR (19h) register.
Note: Auto-MDIX will not work in a forced mode of opera-
tion.
2.3 PHY Address
The 4 PHY address inputs pins are shown below.
The DP83849I provides four address strap pins for deter-
mining the PHY addresses for ports A and B of the device.
The 4 address strap pins provide the upper four bits of the
PHY address. The lowest bit of the PHY address is depen-
dent on the port. Port A has a value of 0 for the PHY
address bit 0 while port B has a value of 1. The PHY
address strap input pins are shown in Tab l e 2.
The PHY address strap information is latched into the
PHYCR register (address 19h, bits [4:0]) at device power-
up and hardware reset. The PHY Address pins are shared
with the RXD pins. Each DP83849I or port sharing an
Table 2. PHY Address Mapping
Pin # PHYAD Function RXD Function
4PHYAD1 RXD0_A
5PHYAD2 RXD1_A
58 PHYAD3 RXD0_B
57 PHYAD4 RXD1_B
www.national.com 20
DP83849I
MDIO bus in a system must have a unique physical
address.
The DP83849I supports PHY Address strapping of Port A
to even values 0 (<0000_0>) through 30 (<1111_0>). Port
B is strapped to odd values 1 (<0000_1>) through 31
(<1111_1>). Note that Port B address is always 1 greater
than Port A address.
For further detail relating to the latch-in timing requirements
of the PHY Address pins, as well as the other hardware
configuration pins, refer to the Reset summary in
Section 6.0.
Refer to Figure 2 for an example of a PHYAD connection to
external components. In this example, the PHYAD strap-
ping results in address 00010 (02h) for Port A and address
00011 (03h) for Port B.
2.3.1 MII Isolate Mode
The DP83849I can be put into MII Isolate mode by writing
to bit 10 of the BMCR register.
When in the MII isolate mode, the DP83849I does not
respond to packet data present at TXD[3:0], TX_EN inputs
and presents a high impedance on the TX_CLK, RX_CLK,
RX_DV, RX_ER, RXD[3:0], COL, and CRS outputs. When
in Isolate mode, the DP83849I will continue to respond to
all management transactions.
While in Isolate mode, the PMD output pair will not transmit
packet data but will continue to source 100BASE-TX
scrambled idles or 10BASE-T normal link pulses.
The DP83849I can Auto-Negotiate or parallel detect to a
specific technology depending on the receive signal at the
PMD input pair. A valid link can be established for the
receiver even when the DP83849I is in Isolate mode.
Figure 2. PHYAD Strapping Example
RXD0_A
RXD1_A
RXD0_B
RXD1_B
VCC
2.2k
PHYAD1 = 1
PHYAD2 = 0PHYAD3 = 0
PHYAD4= 0
21 www.national.com
DP83849I
2.4 LED Interface
The DP83849I supports three configurable Light Emitting
Diode (LED) pins for each port.
Several functions can be multiplexed onto the three LEDs
using three different modes of operation. The LED opera-
tion mode can be selected by writing to the LED_CFG[1:0]
register bits in the PHY Control Register (PHYCR) at
address 19h, bits [6:5]. In addition, LED_CFG[0] for each
port can be set by a strap option on the CRS_A and
CRS_B pins. LED_CFG[1] is only controllable through reg-
ister access and cannot be set by as strap pin.
See Table 3 for LED Mode selection.
The LED_LINK pin in Mode 1 indicates the link status of
the port. In 100BASE-T mode, link is established as a
result of input receive amplitude compliant with the TP-
PMD specifications which will result in internal generation
of signal detect. A 10 Mb/s Link is established as a result of
the reception of at least seven consecutive normal Link
Pulses or the reception of a valid 10BASE-T packet. This
will cause the assertion of LED_LINK. LED_LINK will deas-
sert in accordance with the Link Loss Timer as specified in
the IEEE 802.3 specification.
The LED_LINK pin in Mode 1 will be OFF when no LINK is
present.
The LED_LINK pin in Mode 2 and Mode 3 will be ON to
indicate Link is good and BLINK to indicate activity is
present on activity. The BLINK frequency is defined in
BLINK_FREQ, bits [7:6] of register LEDCR (18h).
Activity is defined as configured in LEDACT_RX, bit 8 of
register LEDCR (18h). If LEDACT_RX is 0, Activity is sig-
naled for either transmit or receive. If LEDACT_RX is 1,
Activity is only signaled for receive.
The LED_SPEED pin indicates 10 or 100 Mb/s data rate of
the port. The LED is ON when operating in 100Mb/s mode
and OFF when operating in 10Mb/s mode. The functional-
ity of this LED is independent of mode selected.
The LED_ACT/LED_COL pin in Mode 1 indicates the pres-
ence of either transmit or receive activity. The LED will be
ON for Activity and OFF for No Activity. In Mode 2, this pin
indicates the Collision status of the port. The LED will be
ON for Collision and OFF for No Collision.
The LED_ACT/LED_COL pin in Mode 3 indicates Duplex
status for 10 Mb/s or 100 Mb/s operation. The LED will be
ON for Full Duplex and OFF for Half Duplex.
In 10 Mb/s half duplex mode, the collision LED is based on
the COL signal.
Since these LED pins are also used as strap options, the
polarity of the LED is dependent on whether the pin is
pulled up or down.
2.4.1 LEDs
Since the Auto-Negotiation (AN) strap options share the
LED output pins, the external components required for
strapping and LED usage must be considered in order to
avoid contention.
Specifically, when the LED outputs are used to drive LEDs
directly, the active state of each output driver is dependent
on the logic level sampled by the corresponding AN input
upon power-up/reset. For example, if a given AN input is
resistively pulled low then the corresponding output will be
configured as an active high driver. Conversely, if a given
AN input is resistively pulled high, then the corresponding
output will be configured as an active low driver.
Refer to Figure 3 for an example of AN connections to
external components at port A. In this example, the AN
strapping results in Auto-Negotiation disabled with 100
Full-Duplex forced.
The adaptive nature of the LED outputs helps to simplify
potential implementation issues of these dual purpose pins.
Table 3. LED Mode Select
Mode LED_CFG[1] LED_CFG[0] LED_LINK LED_SPEED LED_ACT/LED_COL
1don’t care 1ON for Good Link
OFF for No Link
ON in 100 Mb/s
OFF in 10 Mb/s
ON for Activity
OFF for No Activity
2 0 0 ON for Good Link
BLINK for Activity
ON in 100 Mb/s
OFF in 10 Mb/s
ON for Collision
OFF for No Collision
3 1 0 ON for Good Link
BLINK for Activity
ON in 100 Mb/s
OFF in 10 Mb/s
ON for Full Duplex
OFF for Half Duplex
www.national.com 22
DP83849I
2.4.2 LED Direct Control
The DP83849I provides another option to directly control
any or all LED outputs through the LED Direct Control Reg-
ister (LEDCR), address 18h. The register does not provide
read access to LEDs.
2.5 Half Duplex vs. Full Duplex
The DP83849I supports both half and full duplex operation
at both 10 Mb/s and 100 Mb/s speeds.
Half-duplex relies on the CSMA/CD protocol to handle colli-
sions and network access. In Half-Duplex mode, CRS
responds to both transmit and receive activity in order to
maintain compliance with the IEEE 802.3 specification.
Since the DP83849I is designed to support simultaneous
transmit and receive activity it is capable of supporting full-
duplex switched applications with a throughput of up to 200
Mb/s per port when operating in 100BASE-TX. Because
the CSMA/CD protocol does not apply to full-duplex opera-
tion, the DP83849I disables its own internal collision sens-
ing and reporting functions and modifies the behavior of
Carrier Sense (CRS) such that it indicates only receive
activity. This allows a full-duplex capable MAC to operate
properly.
All modes of operation (100BASE-TX, 10BASE-T) can run
either half-duplex or full-duplex. Additionally, other than
CRS and Collision reporting, all remaining MII signaling
remains the same regardless of the selected duplex mode.
It is important to understand that while Auto-Negotiation
with the use of Fast Link Pulse code words can interpret
and configure to full-duplex operation, parallel detection
can not recognize the difference between full and half-
duplex from a fixed 10 Mb/s or 100 Mb/s link partner over
twisted pair. As specified in the 802.3u specification, if a
far-end link partner is configured to a forced full duplex
100BASE-TX ability, the parallel detection state machine in
the partner would be unable to detect the full duplex capa-
bility of the far-end link partner. This link segment would
negotiate to a half duplex 100BASE-TX configuration
(same scenario for 10Mb/s).
2.6 Internal Loopback
The DP83849I includes a Loopback Test mode for facilitat-
ing system diagnostics. The Loopback mode is selected
through bit 14 (Loopback) of the Basic Mode Control Reg-
ister (BMCR). Writing 1 to this bit enables MII transmit data
to be routed to the MII receive outputs. Loopback status
may be checked in bit 3 of the PHY Status Register
(PHYSTS). While in Loopback mode the data will not be
transmitted onto the media. To ensure that the desired
operating mode is maintained, Auto-Negotiation should be
disabled before selecting the Loopback mode.
2.7 BIST
The DP83849I incorporates an internal Built-in Self Test
(BIST) circuit to accommodate in-circuit testing or diagnos-
tics. The BIST circuit can be utilized to test the integrity of
the transmit and receive data paths. BIST testing can be
performed with the part in the internal loopback mode or
externally looped back using a loopback cable fixture.
The BIST is implemented with independent transmit and
receive paths, with the transmit block generating a continu-
ous stream of a pseudo random sequence. The user can
select a 9 bit or 15 bit pseudo random sequence from the
PSR_15 bit in the PHY Control Register (PHYCR). The
received data is compared to the generated pseudo-ran-
dom data by the BIST Linear Feedback Shift Register
(LFSR) to determine the BIST pass/fail status.
The pass/fail status of the BIST is stored in the BIST status
bit in the PHYCR register. The status bit defaults to 0 (BIST
fail) and will transition on a successful comparison. If an
error (mis-compare) occurs, the status bit is latched and is
cleared upon a subsequent write to the Start/Stop bit.
For transmit VOD testing, the Packet BIST Continuous
Mode can be used to allow continuous data transmission,
setting BIST_CONT_MODE, bit 5, of CDCTRL1 (1Bh).
The number of BIST errors can be monitored through the
BIST Error Count in the CDCTRL1 (1Bh), bits [15:8].
LED_LINK_A
LED_SPEED_A
LED_ACT/LED_COL_A
VCC
165
165
2.2k
165
AN0_A = 1
AN1_A = 1
AN_EN_A
= 0
GND
Figure 3. AN Strapping and LED Loading Example
23 www.national.com
DP83849I
3.0 MAC Interface
The DP83849I supports several modes of operation using
the MII interface pins. The options are defined in the follow-
ing sections and include:
MII Mode
RMII Mode
10 Mb Serial Network Interface (SNI)
Single Clock MII Mode (SCMII)
In addition, the DP83849I supports the standard 802.3u MII
Serial Management Interface and a Flexible MII Port
Assignment scheme.
The modes of operation can be selected by strap options
or register control. For RMII mode, it is required to use the
strap option, since it requires a 50 MHz clock instead of the
normal 25 MHz.
In each of these modes, the IEEE 802.3 serial manage-
ment interface is operational for device configuration and
status. The serial management interface of the MII allows
for the configuration and control of multiple PHY devices,
gathering of status, error information, and the determina-
tion of the type and capabilities of the attached PHY(s).
3.1 MII Interface
The DP83849I incorporates the Media Independent Inter-
face (MII) as specified in Clause 22 of the IEEE 802.3u
standard. This interface may be used to connect PHY
devices to a MAC in 10/100 Mb/s systems. This section
describes the nibble wide MII data interface.
The nibble wide MII data interface consists of a receive bus
and a transmit bus each with control signals to facilitate
data transfer between the PHY and the upper layer (MAC).
3.1.1 Nibble-wide MII Data Interface
Clause 22 of the IEEE 802.3u specification defines the
Media Independent Interface. This interface includes a
dedicated receive bus and a dedicated transmit bus. These
two data buses, along with various control and status sig-
nals, allow for the simultaneous exchange of data between
the DP83849I and the upper layer agent (MAC).
The receive interface consists of a nibble wide data bus
RXD[3:0], a receive error signal RX_ER, a receive data
valid flag RX_DV, and a receive clock RX_CLK for syn-
chronous transfer of the data. The receive clock operates
at either 2.5 MHz to support 10 Mb/s operation modes or at
25 MHz to support 100 Mb/s operational modes.
The transmit interface consists of a nibble wide data bus
TXD[3:0], a transmit enable control signal TX_EN, and a
transmit clock TX_CLK which runs at either 2.5 MHz or 25
MHz.
Additionally, the MII includes the carrier sense signal CRS,
as well as a collision detect signal COL. The CRS signal
asserts to indicate the reception of data from the network
or as a function of transmit data in Half Duplex mode. The
COL signal asserts as an indication of a collision which can
occur during half-duplex operation when both a transmit
and receive operation occur simultaneously.
3.1.2 Collision Detect
For Half Duplex, a 10BASE-T or 100BASE-TX collision is
detected when the receive and transmit channels are
active simultaneously. Collisions are reported by the COL
signal on the MII.
If the DP83849I is transmitting in 10 Mb/s mode when a
collision is detected, the collision is not reported until seven
bits have been received while in the collision state. This
prevents a collision being reported incorrectly due to noise
on the network. The COL signal remains set for the dura-
tion of the collision.
If a collision occurs during a receive operation, it is immedi-
ately reported by the COL signal.
When heartbeat is enabled (only applicable to 10 Mb/s
operation), approximately 1µs after the transmission of
each packet, a Signal Quality Error (SQE) signal of approx-
imately 10 bit times is generated (internally) to indicate
successful transmission. SQE is reported as a pulse on the
COL signal of the MII.
3.1.3 Carrier Sense
Carrier Sense (CRS) is asserted due to receive activity,
once valid data is detected via the squelch function during
10 Mb/s operation. During 100 Mb/s operation CRS is
asserted when a valid link (SD) and two non-contiguous
zeros are detected on the line.
For 10 or 100 Mb/s Half Duplex operation, CRS is asserted
during either packet transmission or reception.
For 10 or 100 Mb/s Full Duplex operation, CRS is asserted
only due to receive activity.
CRS is deasserted following an end of packet.
www.national.com 24
DP83849I
3.2 Reduced MII Interface
The DP83849I incorporates the Reduced Media Indepen-
dent Interface (RMII) as specified in the RMII specification
(rev1.2) from the RMII Consortium. This interface may be
used to connect PHY devices to a MAC in 10/100 Mb/s
systems using a reduced number of pins. In this mode,
data is transferred 2-bits at a time using the 50 MHz
RMII_REF clock for both transmit and receive. The follow-
ing pins are used in RMII mode:
—TX_EN
—TXD[1:0]
RX_ER (optional for Mac)
CRS_DV
RXD[1:0]
X1 (RMII Reference clock is 50 MHz)
In addition, the RMII mode supplies an RX_DV signal
which allows for a simpler method of recovering receive
data without having to separate RX_DV from the CRS_DV
indication. This is especially useful for diagnostic testing
where it may be desirable to externally loop Receive MII
data directly to the transmitter.
The RX_ER output may be used by the MAC to detect
error conditions. It is asserted for symbol errors received
during a packet, False Carrier events, and also for FIFO
underrun or overrun conditions. Since the Phy is required
to corrupt receive data on an error, a MAC is not required
to use RX_ER.
It is important to note that since both digital channels in the
DP83849I share the X1/RMII_REF input, both channels
must have RMII mode enabled or both channels must have
RMII mode disabled. Either channel may be in 10Mb or
100Mb mode in RMII or non-RMII mode.
Since the reference clock operates at 10 times the data
rate for 10 Mb/s operation, transmit data is sampled every
10 clocks. Likewise, receive data will be generated every
10th clock so that an attached device can sample the data
every 10 clocks.
RMII mode requires a 50 MHz oscillator be connected to
the device X1 pin. A 50 MHz crystal is not supported.
To tolerate potential frequency differences between the 50
MHz reference clock and the recovered receive clock, the
receive RMII function includes a programmable elasticity
buffer. The elasticity buffer is programmable to minimize
propagation delay based on expected packet size and
clock accuracy. This allows for supporting a range of
packet sizes including jumbo frames.
The elasticity buffer will force Frame Check Sequence
errors for packets which overrun or underrun the FIFO.
Underrun and Overrun conditions can be reported in the
RMII and Bypass Register (RBR). The following table indi-
cates how to program the elasticity buffer fifo (in 4-bit incre-
ments) based on expected max packet size and clock
accuracy. It assumes both clocks (RMII Reference clock
and far-end Transmitter clock) have the same accuracy.
Packet lengths can be scaled linearly based on accuracy
(+/- 25ppm would allows packets twice as large). If the
threshold setting must support both 10Mb and 100Mb
operation, the setting should be made to support both
speeds.
Table 4. Supported packet sizes at +/-50ppm frequency accuracy
Start Threshold
RBR[1:0]
Latency Tolerance Recommended Packet Size
at +/- 50ppm
100Mb 10Mb 100Mb 10Mb
01 (default) 2 bits 8 bits 2,400 bytes 9,600 bytes
10 6 bits 4 bits 7,200 bytes 4,800 bytes
11 10 bits 8 bits 12,000 bytes 9,600 bytes
00 14 bits 12 bits 16,800 bytes 14,400 bytes
25 www.national.com
DP83849I
3.3 10 Mb Serial Network Interface (SNI)
The DP83849I incorporates a 10 Mb Serial Network Inter-
face (SNI) which allows a simple serial data interface for 10
Mb only devices. This is also referred to as a 7-wire inter-
face. While there is no defined standard for this interface, it
is based on early 10 Mb physical layer devices. Data is
clocked serially at 10 MHz using separate transmit and
receive paths. The following pins are used in SNI mode:
—TX_CLK
—TX_EN
—TXD[0]
—RX_CLK
—RXD[0]
CRS
—COL
3.4 Single Clock MII Mode
Single Clock MII (SCMII) Mode allows MII operation using
a single 25MHz reference clock. Normal MII Mode requires
three clocks, a reference clock for physical layer functions,
a Transmit MII clock, and a Receive MII clock. Similar to
RMII mode, Single Clock MII mode requires only the refer-
ence clock. In addition to reducing the number of pins
required, this mode allows the attached MAC device to use
only the reference clock domain. Since the DP83849I has
two ports, this actually reduces the number of clocks from 6
to 1. A/C Timing requirements for SCMII operation are
similar to the RMII timing requirements.
For 10Mb operation, as in RMII mode, data is sampled and
driven every 10 clocks since the reference clock is at 10x
the data rate.
Separate control bits allow enabling the Transmit and
Receive Single Clock modes separately, allowing just
transmit or receive to operate in this mode. Control of Sin-
gle Clock MII mode is through the RBR register.
Single Clock MII mode incorporates the use of the RMII
elasticity buffer, which is required to tolerate potential fre-
quency differences between the 25MHz reference clock
and the recovered receive clock. Settings for the Elasticity
Buffer for SCMII mode are detailed in the following table.
Table 5. Supported SCMII packet sizes at +/-50ppm frequency accuracy
Start Threshold
RBR[1:0]
Latency Tolerance Recommended Packet Size
at +/- 50ppm
100Mb 10Mb 100Mb 10Mb
01 (default) 4 bits 8 bits 4,000 bytes 9,600 bytes
10 4 bits 8 bits 4,000 bytes 9,600 bytes
11 12 bits 8 bits 9.600 bytes 9,600 bytes
00 12 bits 8 bits 9,600 bytes 9,600 bytes
www.national.com 26
DP83849I
3.5 Flexible MII Port Assignment
The DP83849I supports a flexible assignment scheme for
each of the channels to the MII/RMII interface. Either of
the MII ports may be assigned to the internal channels A/B.
These values are controlled by the RMII and Bypass Reg-
ister (RBR), address 17h. Transmit assignments and
Receive assignments can be made separately to allow
even more flexibility (i.e. both channels could transmit from
MII A while still allowing separate receive paths for the
channels).
In addition, the opposite receive channel may be used as
the transmit source for each channel. As shown in
Figure 4, Channel A receive data may be used as the
Channel B transmit data source while Channel B receive
data may be used as the Channel A transmit data source.
For proper clock synchronization, this function requires the
device be in RMII mode or Single Clock MII mode of opera-
tion. A configuration strap is provided on pin 56,
RXD2_B/EXTENDER_EN to enable this mode.
MII Channel A
Port
A
TX
RX
TX
RX
MII Channel B
Port
B
TX
RX
TX
RX
10BASE-T
or
100BASE-TX
10BASE-T
or
100BASE-TX
Figure 4. MII Port Mapping
27 www.national.com
DP83849I
3.5.1 RX MII Port Mapping
Note that Channel A is the master of MII Port A, and Chan-
nel B is the master of MII Port B. This means that in order
for Channel B to control MII Port A, Channel A must be
configured to either control MII Port B or be Disabled; the
reverse is also true.
RX MII Port Mapping controls and configurations are
shown in the following tables:
Table 6. RX MII Port Mapping Controls
Table 7. RX MII Port Mapping Configurations
RBR[12:11] Desired RX Channel Destination
00 Normal Port
01 Opposite Port
10 Both Ports
11 Disabled
Channel A RBR[12:11] Channel B RBR[12:11] RX MII Port A Source RX MII Port B Source
00 00 Channel A Channel B
00 01 Channel A Channel B
00 10 Channel A Channel B
00 11 Channel A Disabled
01 00 Channel A Channel B
01 01 Channel B Channel A
01 10 Channel B Channel A
01 11 Disabled Channel A
10 00 Channel A Channel B
10 01 Channel B Channel A
10 10 Channel A Channel B
10 11 Channel A Channel A
11 00 Disabled Channel B
11 01 Channel B Disabled
11 10 Channel B Channel B
11 11 Disabled Disabled
www.national.com 28
DP83849I
3.5.2 TX MII Port Mapping
TX MII Port Mapping controls and configurations are
shown in the following tables:
Table 8. TX MII Port Mapping Controls
Table 9. TX MII Port Mapping Configurations
3.5.3 Common Flexible MII Port Configurations
Table 10. Common Flexible MII Port Configurations
RBR[10:9] TX Channel Source
00 Normal Port
01 Opposite Port
10 Opposite RX Port
11 Disabled
Channel A RBR[10:9] Port A TX Source Channel B RBR[10:9] Port B TX Source
00 MII Port A 00 MII Port B
01 MII Port B 01 MII Port A
10 RX Channel B 10 RX Channel A
11 Disabled 11 Disabled
Mode Channel A
RBR[12:9]
Channel B
RBR[12:9]
Description
Normal 0000 0000 MII port A assigned to Channel A, MII
Port B assigned to Channel B
Full Port Swap 0101 0101 MII port A assigned to Channel B, MII
Port B assigned to Channel A
Extender 1110 1110 MII RX disabled, Channel A transmits
from Channel B RX data, Channel B
transmits from Channel A RX data
Broadcast TX MII Port A xx00 xx01 Both Channels transmit from TX MII
Port A
Broadcast TX MII Port B xx01 xx00 Both Channels transmit from TX MII
Port B
Mirror RX Channel A 10xx 11xx Channel A RX traffic appears on both
Ports.
Mirror RX Channel B 11xx 10xx Channel B RX traffic appears on both
Ports.
Disable Port A 1111 xxxx MII Port A is disabled
Disable Port B xxxx 1111 MII Port B is disabled
29 www.national.com
DP83849I
3.5.4 Strapped Extender Mode
The DP83849I provides a simple strap option to automati-
cally configure both channels for Extender Mode with no
device register configuration necessary. The
EXTENDER_EN Strap can be used in conjunction with the
Auto-Negotiation Straps (AN_EN, AN0, AN1), the RMII
Mode Strap to allow many possible configurations. If
Extender Mode is strapped but RMII Mode is not, both
channels will automatically be configured for Single Clock
MII Receive and Transmit Modes. The optional use of
RMII Mode in conjunction with Extender Mode allows flexi-
bility in the system design.
Several common configurations are shown in Table 11.
Table 11. Common Strapped Extender Mode Configurations
3.5.5 Notes and Restrictions
Extender: Both channels must be operating at the same
speed (10 or 100Mb). This can be accomplished using
straps or channel register controls. Both channels must
be in Full Duplex mode. Both channels must either be in
RMII Mode (RBR:RMII_EN = 1) or full Single Clock MII
Mode (RBR:SCMII_RX = 1 and RBR:SCMII_TX = 1) to
ensure synchronous operation. If only one RX to TX path
is enabled, SCMII_RX in the RX channel (RBR register
17h bit 7) and SCMII_TX in the TX channel (RBR regis-
ter 17h bit 6) must be set to 1.
Broadcast TX MII Port Mode: To ensure synchronous
operation, both channels must be in RMII Mode (RBR
register 17h bit 5 = 1) or in Single Clock TX MII Mode
(RBR register 17h bit 6 = 1). Both channels must be op-
erating at the same speed (10 or 100Mb). Both channels
must be in Full Duplex mode to ensure no collisions are
seen. This is because in Single Clock TX MII Mode, a
collision on one PHY channel would cause both chan-
nels to send the Jam pattern.
RMII Mode: Both Channels must have RMII Mode en-
abled or disabled concurrently due to the internal refer-
ence clocking scheme. In Full Port Swap Mode,
Channels are not required to have a common speed.
10Base-T Serial Mode: This MAC-side mode, also
known as Serial Network Interface (SNI), may not be
used when both channels share data connections (Ex-
tender or Broadcast TX MII Port). This is due to the re-
quirement of synchronous operation between channels,
which is not supported in SNI Mode.
CRS Assignment: When a channel is not in RMII Mode,
its associated CRS pin is sourced from the transmitter
and controlled by the TX MII Port Assignment, bits [10:9]
of RBR (17h). When a channel is in RMII Mode, the as-
sociated CRS pin is sourced from the receiver and con-
trolled by the RX MII Port Assignment, bits [12:11] of
RBR (17h).
Output Enables: Flexible MII Port Assignment does not
control signal output enables.
Test Modes: Test modes are not designed to be com-
patible with Flexible MII Port Selection, which assumes
default MII pin directions.
LED Assignment: LEDs are associated with their re-
spective digital channels, and therefore do not get
mapped to alternate channels. For example, assertion
of LED_LINK_A indicates valid link status for Channel A
independent of the MII Port Assignment.
Straps: Strap pins are always associated with their re-
spective channel, i.e. a strap on RX_ER_A is used by
Channel A.
Port Isolate Mode: Each MII port’s Isolate function, bit
10 of BMCR (00h) is always associated with its respec-
tive channel, i.e. the Isolate function for Port A is always
controlled by Channel A’s BMCR (00h). Due to the var-
ious possible combinations of TX and RX port selection,
it may not be advisable to place a port in Isolate mode.
Energy Detect and Powerdown Modes: The output
enables for each MII port are always controlled by the re-
spective channel Energy Detect and Powerdown func-
tions. These functions should be disabled whenever an
MII port is in use but not assigned to its default channel.
Note that Extender/Media Converter modes allow the
use of Energy Detect and Powerdown modes if the RX
MII ports are not in use.
Mode Auto-Negotiation Straps
100Mb Copper Extender Both channels are forced to 100Mb Full Duplex
10Mb Copper Extender Both channels are forced to 10Mb Full Duplex
www.national.com 30
DP83849I
3.6 802.3u MII Serial Management Interface
3.6.1 Serial Management Register Access
The serial management MII specification defines a set of
thirty-two 16-bit status and control registers that are acces-
sible through the management interface pins MDC and
MDIO. The DP83849I implements all the required MII reg-
isters as well as several optional registers. These registers
are fully described in Section 7.0. A description of the serial
management access protocol follows.
3.6.2 Serial Management Access Protocol
The serial control interface consists of two pins, Manage-
ment Data Clock (MDC) and Management Data Input/Out-
put (MDIO). MDC has a maximum clock rate of 25 MHz
and no minimum rate. The MDIO line is bi-directional and
may be shared by up to 32 devices. The MDIO frame for-
mat is shown below in Table 12.
In addition, the MDIO pin requires a pull-up resistor (1.5
k) which, during IDLE and turnaround, will pull MDIO
high. In order to initialize the MDIO interface, the station
management entity sends a sequence of 32 contiguous
logic ones on MDIO to provide the DP83849I with a
sequence that can be used to establish synchronization.
This preamble may be generated either by driving MDIO
high for 32 consecutive MDC clock cycles, or by simply
allowing the MDIO pull-up resistor to pull the MDIO pin high
during which time 32 MDC clock cycles are provided. In
addition 32 MDC clock cycles should be used to re-sync
the device if an invalid start, opcode, or turnaround bit is
detected.
The DP83849I waits until it has received this preamble
sequence before responding to any other transaction.
Once the DP83849I serial management port has been ini-
tialized no further preamble sequencing is required until
after a power-on/reset, invalid Start, invalid Opcode, or
invalid turnaround bit has occurred.
The Start code is indicated by a <01> pattern. This assures
the MDIO line transitions from the default idle line state.
Turnaround is defined as an idle bit time inserted between
the Register Address field and the Data field. To avoid con-
tention during a read transaction, no device shall actively
drive the MDIO signal during the first bit of Turnaround.
The addressed DP83849I drives the MDIO with a zero for
the second bit of turnaround and follows this with the
required data. Figure 5 shows the timing relationship
between MDC and the MDIO as driven/received by the Sta-
tion (STA) and the DP83849I (PHY) for a typical register
read access.
For write transactions, the station management entity
writes data to the addressed DP83849I thus eliminating the
requirement for MDIO Turnaround. The Turnaround time is
filled by the management entity by inserting <10>. Figure 6
shows the timing relationship for a typical MII register write
access.
Table 12. Typical MDIO Frame Format
Figure 5. Typical MDC/MDIO Read Operation
MII Management
Serial Protocol
<idle><start><op code><device addr><reg addr><turnaround><data><idle>
Read Operation <idle><01><10><AAAAA><RRRRR><Z0><xxxx xxxx xxxx xxxx><idle>
Write Operation <idle><01><01><AAAAA><RRRRR><10><xxxx xxxx xxxx xxxx><idle>
MDC
MDIO
00011 110000000
(STA)
Idle Start Opcode
(Read)
PHY Address
(PHYAD = 0Ch)
Register Address
(00h = BMCR) TA Register Data
Z
MDIO
(PHY)
Z
Z
Z0 0 011000100000000Z
Idle
Z
Z
31 www.national.com
DP83849I
Figure 6. Typical MDC/MDIO Write Operation
3.6.3 Serial Management Preamble Suppression
The DP83849I supports a Preamble Suppression mode as
indicated by a one in bit 6 of the Basic Mode Status Regis-
ter (BMSR, address 01h.) If the station management entity
(i.e. MAC or other management controller) determines that
all PHYs in the system support Preamble Suppression by
returning a one in this bit, then the station management
entity need not generate preamble for each management
transaction.
The DP83849I requires a single initialization sequence of
32 bits of preamble following hardware/software reset. This
requirement is generally met by the mandatory pull-up
resistor on MDIO in conjunction with a continuous MDC, or
the management access made to determine whether Pre-
amble Suppression is supported.
While the DP83849I requires an initial preamble sequence
of 32 bits for management initialization, it does not require
a full 32-bit sequence between each subsequent transac-
tion. A minimum of one idle bit between management
transactions is required as specified in the IEEE 802.3u
specification.
3.6.4 Simultaneous Register Write
The DP83849I incorporates a mode which allows simulta-
neous write access to both Port A and B register blocks at
the same time. This mode is selected by setting bit 15 of
RMII and Bypass Register (RBR, address 17h) in Port A.
As long as this bit remains set, subsequent writes to Port A
will write to registers in both ports.
Register reads are unaffected. Each port must still be read
individually.
MDC
MDIO
00011110000000
(STA)
Idle Start Opcode
(Write)
PHY Address
(PHYAD = 0Ch)
Register Address
(00h = BMCR) TA Register Data
Z0 0 0 000 00000000Z
Idle
1000
ZZ
www.national.com 32
DP83849I
4.0 Architecture
This section describes the operations within each trans-
ceiver module, 100BASE-TX and 10BASE-T. Each opera-
tion consists of several functional blocks and described in
the following:
100BASE-TX Transmitter
100BASE-TX Receiver
10BASE-T Transceiver Module
4.1 100BASE-TX TRANSMITTER
The 100BASE-TX transmitter consists of several functional
blocks which convert synchronous 4-bit nibble data, as pro-
vided by the MII, to a scrambled MLT-3 125 Mb/s serial
data stream. Because the 100BASE-TX TP-PMD is inte-
grated, the differential output pins, PMD Output Pair, can
be directly routed to the magnetics.
The block diagram in Figure 7. provides an overview of
each functional block within the 100BASE-TX transmit sec-
tion.
The Transmitter section consists of the following functional
blocks:
Code-group Encoder and Injection block
Scrambler block (bypass option)
NRZ to NRZI encoder block
Binary to MLT-3 converter / Common Driver
The bypass option for the functional blocks within the
100BASE-TX transmitter provides flexibility for applications
where data conversion is not always required. The
DP83849I implements the 100BASE-TX transmit state
machine diagram as specified in the IEEE 802.3u Stan-
dard, Clause 24.
Figure 7. 100BASE-TX Transmit Block Diagram
4B5B CODE-
GROUP
ENCODER &
SCRAMBLER
NRZ TO NRZI
ENCODER
5B PARALLEL
TO SERIAL
PMD OUTPUT PAIR
TX_CLK TXD[3:0] /
TX_EN
BINARY
TO MLT-3 /
COMMON
DRIVER
125MHZ CLOCK
BP_SCR MUX
100BASE-TX
LOOPBACK
MLT[1:0]
DIVIDE
BY 5
33 www.national.com
DP83849I
Table 13. 4B5B Code-Group Encoding/Decoding
DATA CODES
011110 0000
101001 0001
210100 0010
310101 0011
401010 0100
501011 0101
601110 0110
701111 0111
810010 1000
910011 1001
A10110 1010
B10111 1011
C11010 1100
D11011 1101
E11100 1110
F11101 1111
IDLE AND CONTROL CODES
H00100 HALT code-group - Error code
I11111 Inter-Packet IDLE - 0000 (Note 1)
J11000 First Start of Packet - 0101 (Note 1)
K10001 Second Start of Packet - 0101 (Note 1)
T01101 First End of Packet - 0000 (Note 1)
R00111 Second End of Packet - 0000 (Note 1)
INVALID CODES
V00000
V00001
V00010
V00011
V00101
V00110
V01000
V01100
Note: Control code-groups I, J, K, T and R in data fields will be mapped as invalid codes, together with RX_ER as-
serted.
www.national.com 34
DP83849I
4.1.1 Code-group Encoding and Injection
The code-group encoder converts 4-bit (4B) nibble data
generated by the MAC into 5-bit (5B) code-groups for
transmission. This conversion is required to allow control
data to be combined with packet data code-groups. Refer
to Table 13 for 4B to 5B code-group mapping details.
The code-group encoder substitutes the first 8-bits of the
MAC preamble with a J/K code-group pair (11000 10001)
upon transmission. The code-group encoder continues to
replace subsequent 4B preamble and data nibbles with
corresponding 5B code-groups. At the end of the transmit
packet, upon the deassertion of Transmit Enable signal
from the MAC, the code-group encoder injects the T/R
code-group pair (01101 00111) indicating the end of the
frame.
After the T/R code-group pair, the code-group encoder
continuously injects IDLEs into the transmit data stream
until the next transmit packet is detected (reassertion of
Transmit Enable).
4.1.2 Scrambler
The scrambler is required to control the radiated emissions
at the media connector and on the twisted pair cable (for
100BASE-TX applications). By scrambling the data, the
total energy launched onto the cable is randomly distrib-
uted over a wide frequency range. Without the scrambler,
energy levels at the PMD and on the cable could peak
beyond FCC limitations at frequencies related to repeating
5B sequences (i.e., continuous transmission of IDLEs).
The scrambler is configured as a closed loop linear feed-
back shift register (LFSR) with an 11-bit polynomial. The
output of the closed loop LFSR is X-ORd with the serial
NRZ data from the code-group encoder. The result is a
scrambled data stream with sufficient randomization to
decrease radiated emissions at certain frequencies by as
much as 20 dB. The DP83849I uses the PHY_ID (pins
PHYAD [4:1]) to set a unique seed value.
4.1.3 NRZ to NRZI Encoder
After the transmit data stream has been serialized and
scrambled, the data must be NRZI encoded in order to
comply with the TP-PMD standard for 100BASE-TX trans-
mission over Category-5 Unshielded twisted pair cable.
4.1.4 Binary to MLT-3 Convertor
The Binary to MLT-3 conversion is accomplished by con-
verting the serial binary data stream output from the NRZI
encoder into two binary data streams with alternately
phased logic one events. These two binary streams are
then fed to the twisted pair output driver which converts the
voltage to current and alternately drives either side of the
transmit transformer primary winding, resulting in a MLT-3
signal.
The 100BASE-TX MLT-3 signal sourced by the PMD Out-
put Pair common driver is slew rate controlled. This should
be considered when selecting AC coupling magnetics to
ensure TP-PMD Standard compliant transition times (3 ns
< Tr < 5 ns).
The 100BASE-TX transmit TP-PMD function within the
DP83849I is capable of sourcing only MLT-3 encoded data.
Binary output from the PMD Output Pair is not possible in
100 Mb/s mode.
4.2 100BASE-TX RECEIVER
The 100BASE-TX receiver consists of several functional
blocks which convert the scrambled MLT-3 125 Mb/s serial
data stream to synchronous 4-bit nibble data that is pro-
vided to the MII. Because the 100BASE-TX TP-PMD is
integrated, the differential input pins, RD±, can be directly
routed from the AC coupling magnetics.
See Figure 8 for a block diagram of the 100BASE-TX
receive function. This provides an overview of each func-
tional block within the 100BASE-TX receive section.
The Receive section consists of the following functional
blocks:
Analog Front End
Digital Signal Processor
Signal Detect
MLT-3 to Binary Decoder
NRZI to NRZ Decoder
Serial to Parallel
Descrambler
Code Group Alignment
—4B/5B Decoder
Link Integrity Monitor
Bad SSD Detection
4.2.1 Analog Front End
In addition to the Digital Equalization and Gain Control, the
DP83849I includes Analog Equalization and Gain Control
in the Analog Front End. The Analog Equalization reduces
the amount of Digital Equalization required in the DSP.
4.2.2 Digital Signal Processor
The Digital Signal Processor includes Adaptive Equaliza-
tion with Gain Control and Base Line Wander Compensa-
tion.
35 www.national.com
DP83849I
4B/5B DECODER
DESCRAMBLER
MLT-3 TO BINARY
DECODER
RX_CLK RXD[3:0] / RX_ER
NRZI TO NRZ
DECODER
CODE GROUP
ALIGNMENT
SERIAL TO
PARALLEL
RX_DV/CRS
RX_DATA VALID
SSD DETECT
RD +/−
SIGNAL
DETECT
LINK
INTEGRITY
MONITOR
DIGITAL
SIGNAL
PROCESSOR
ANALOG
FRONT
END
Figure 8. 100BASE-TX Receive Block Diagram
www.national.com 36
DP83849I
4.2.2.1 Digital Adaptive Equalization and Gain Control
When transmitting data at high speeds over copper twisted
pair cable, frequency dependent attenuation becomes a
concern. In high-speed twisted pair signalling, the fre-
quency content of the transmitted signal can vary greatly
during normal operation based primarily on the random-
ness of the scrambled data stream. This variation in signal
attenuation caused by frequency variations must be com-
pensated to ensure the integrity of the transmission.
In order to ensure quality transmission when employing
MLT-3 encoding, the compensation must be able to adapt
to various cable lengths and cable types depending on the
installed environment. The selection of long cable lengths
for a given implementation, requires significant compensa-
tion which will over-compensate for shorter, less attenuat-
ing lengths. Conversely, the selection of short or
intermediate cable lengths requiring less compensation will
cause serious under-compensation for longer length
cables. The compensation or equalization must be adap-
tive to ensure proper conditioning of the received signal
independent of the cable length.
The DP83849I utilizes an extremely robust equalization
scheme referred as ‘Digital Adaptive Equalization.
The Digital Equalizer removes ISI (inter symbol interfer-
ence) from the receive data stream by continuously adapt-
ing to provide a filter with the inverse frequency response
of the channel. Equalization is combined with an adaptive
gain control stage. This enables the receive 'eye pattern' to
be opened sufficiently to allow very reliable data recovery.
The curves given in Figure 9 illustrate attenuation at certain
frequencies for given cable lengths. This is derived from
the worst case frequency vs. attenuation figures as speci-
fied in the EIA/TIA Bulletin TSB-36. These curves indicate
the significant variations in signal attenuation that must be
compensated for by the receive adaptive equalization cir-
cuit.
Figure 9. EIA/TIA Attenuation vs. Frequency for 0, 50,
100, 130 & 150 meters of CAT 5 cable
37 www.national.com
DP83849I
4.2.2.2 Base Line Wander Compensation
The DP83849I is completely ANSI TP-PMD compliant and
includes Base Line Wander (BLW) compensation. The
BLW compensation block can successfully recover the TP-
PMD defined “killer” pattern.
BLW can generally be defined as the change in the aver-
age DC content, relatively short period over time, of an AC
coupled digital transmission over a given transmission
medium. (i.e., copper wire).
BLW results from the interaction between the low fre-
quency components of a transmitted bit stream and the fre-
quency response of the AC coupling component(s) within
the transmission system. If the low frequency content of
the digital bit stream goes below the low frequency pole of
the AC coupling transformers then the droop characteris-
tics of the transformers will dominate resulting in potentially
serious BLW.
The digital oscilloscope plot provided in Figure 10 illus-
trates the severity of the BLW event that can theoretically
be generated during 100BASE-TX packet transmission.
This event consists of approximately 800 mV of DC offset
for a period of 120 µs. Left uncompensated, events such as
this can cause packet loss.
4.2.3 Signal Detect
The signal detect function of the DP83849I is incorporated
to meet the specifications mandated by the ANSI FDDI TP-
PMD Standard as well as the IEEE 802.3 100BASE-TX
Standard for both voltage thresholds and timing parame-
ters.
Note that the reception of normal 10BASE-T link pulses
and fast link pulses per IEEE 802.3u Auto-Negotiation by
the 100BASE-TX receiver do not cause the DP83849I to
assert signal detect.
4.2.4 MLT-3 to NRZI Decoder
The DP83849I decodes the MLT-3 information from the
Digital Adaptive Equalizer block to binary NRZI data.
4.2.5 NRZI to NRZ
In a typical application, the NRZI to NRZ decoder is
required in order to present NRZ formatted data to the
descrambler.
4.2.6 Serial to Parallel
The 100BASE-TX receiver includes a Serial to Parallel
converter which supplies 5-bit wide data symbols to the
PCS Rx state machine.
Figure 10. 100BASE-TX BLW Event
www.national.com 38
DP83849I
4.2.7 Descrambler
A serial descrambler is used to de-scramble the received
NRZ data. The descrambler has to generate an identical
data scrambling sequence (N) in order to recover the origi-
nal unscrambled data (UD) from the scrambled data (SD)
as represented in the equations:
Synchronization of the descrambler to the original scram-
bling sequence (N) is achieved based on the knowledge
that the incoming scrambled data stream consists of
scrambled IDLE data. After the descrambler has recog-
nized 12 consecutive IDLE code-groups, where an
unscrambled IDLE code-group in 5B NRZ is equal to five
consecutive ones (11111), it will synchronize to the receive
data stream and generate unscrambled data in the form of
unaligned 5B code-groups.
In order to maintain synchronization, the descrambler must
continuously monitor the validity of the unscrambled data
that it generates. To ensure this, a line state monitor and a
hold timer are used to constantly monitor the synchroniza-
tion status. Upon synchronization of the descrambler the
hold timer starts a 722 µs countdown. Upon detection of
sufficient IDLE code-groups (58 bit times) within the 722 µs
period, the hold timer will reset and begin a new count-
down. This monitoring operation will continue indefinitely
given a properly operating network connection with good
signal integrity. If the line state monitor does not recognize
sufficient unscrambled IDLE code-groups within the 722 µs
period, the entire descrambler will be forced out of the cur-
rent state of synchronization and reset in order to re-
acquire synchronization.
4.2.8 Code-group Alignment
The code-group alignment module operates on unaligned
5-bit data from the descrambler (or, if the descrambler is
bypassed, directly from the NRZI/NRZ decoder) and con-
verts it into 5B code-group data (5 bits). Code-group align-
ment occurs after the J/K code-group pair is detected.
Once the J/K code-group pair (11000 10001) is detected,
subsequent data is aligned on a fixed boundary.
4.2.9 4B/5B Decoder
The code-group decoder functions as a look up table that
translates incoming 5B code-groups into 4B nibbles. The
code-group decoder first detects the J/K code-group pair
preceded by IDLE code-groups and replaces the J/K with
MAC preamble. Specifically, the J/K 10-bit code-group pair
is replaced by the nibble pair (0101 0101). All subsequent
5B code-groups are converted to the corresponding 4B
nibbles for the duration of the entire packet. This conver-
sion ceases upon the detection of the T/R code-group pair
denoting the End of Stream Delimiter (ESD) or with the
reception of a minimum of two IDLE code-groups.
4.2.10 100BASE-TX Link Integrity Monitor
The 100 Base TX Link monitor ensures that a valid and sta-
ble link is established before enabling both the Transmit
and Receive PCS layer.
Signal detect must be valid for 395us to allow the link mon-
itor to enter the 'Link Up' state, and enable the transmit and
receive functions.
4.2.11 Bad SSD Detection
A Bad Start of Stream Delimiter (Bad SSD) is any transition
from consecutive idle code-groups to non-idle code-groups
which is not prefixed by the code-group pair /J/K.
If this condition is detected, the DP83849I will assert
RX_ER and present RXD[3:0] = 1110 to the MII for the
cycles that correspond to received 5B code-groups until at
least two IDLE code groups are detected. In addition, the
False Carrier Sense Counter register (FCSCR) will be
incremented by one.
Once at least two IDLE code groups are detected, RX_ER
and CRS become de-asserted.
4.3 10BASE-T TRANSCEIVER MODULE
The 10BASE-T Transceiver Module is IEEE 802.3 compli-
ant. It includes the receiver, transmitter, collision, heart-
beat, loopback, jabber, and link integrity functions, as
defined in the standard. An external filter is not required on
the 10BASE-T interface since this is integrated inside the
DP83849I. This section focuses on the general 10BASE-T
system level operation.
4.3.1 Operational Modes
The DP83849I has two basic 10BASE-T operational
modes:
Half Duplex mode
Full Duplex mode
Half Duplex Mode
In Half Duplex mode the DP83849I functions as a standard
IEEE 802.3 10BASE-T transceiver supporting the
CSMA/CD protocol.
Full Duplex Mode
In Full Duplex mode the DP83849I is capable of simulta-
neously transmitting and receiving without asserting the
collision signal. The DP83849I's 10 Mb/s ENDEC is
designed to encode and decode simultaneously.
4.3.2 Smart Squelch
The smart squelch is responsible for determining when
valid data is present on the differential receive inputs. The
DP83849I implements an intelligent receive squelch to
ensure that impulse noise on the receive inputs will not be
mistaken for a valid signal. Smart squelch operation is
independent of the 10BASE-T operational mode.
The squelch circuitry employs a combination of amplitude
and timing measurements (as specified in the IEEE 802.3
10BSE-T standard) to determine the validity of data on the
twisted pair inputs (refer to Figure 11).
The signal at the start of a packet is checked by the smart
squelch and any pulses not exceeding the squelch level
(either positive or negative, depending upon polarity) will
UD SD N()=
SD UD N()=
39 www.national.com
DP83849I
be rejected. Once this first squelch level is overcome cor-
rectly, the opposite squelch level must then be exceeded
within 150 ns. Finally the signal must again exceed the
original squelch level within 150 ns to ensure that the input
waveform will not be rejected. This checking procedure
results in the loss of typically three preamble bits at the
beginning of each packet.
Only after all these conditions have been satisfied will a
control signal be generated to indicate to the remainder of
the circuitry that valid data is present. At this time, the
smart squelch circuitry is reset.
Valid data is considered to be present until the squelch
level has not been generated for a time longer than 150 ns,
indicating the End of Packet. Once good data has been
detected, the squelch levels are reduced to minimize the
effect of noise causing premature End of Packet detection.
end of packet
start of packet
V
SQ-(reduced)
V
SQ-
V
SQ+(reduced)
V
SQ+
<150 ns <150 ns >150 ns
Figure 11. 10BASE-T Twisted Pair Smart Squelch Operation
www.national.com 40
DP83849I
4.3.3 Collision Detection and SQE
When in Half Duplex, a 10BASE-T collision is detected
when the receive and transmit channels are active simulta-
neously. Collisions are reported by the COL signal on the
MII. Collisions are also reported when a jabber condition is
detected.
The COL signal remains set for the duration of the collision.
If the PHY is receiving when a collision is detected it is
reported immediately (through the COL pin).
When heartbeat is enabled, approximately 1 µs after the
transmission of each packet, a Signal Quality Error (SQE)
signal of approximately 10-bit times is generated to indi-
cate successful transmission. SQE is reported as a pulse
on the COL signal of the MII.
The SQE test is inhibited when the PHY is set in full duplex
mode. SQE can also be inhibited by setting the
HEARTBEAT_DIS bit in the 10BTSCR register.
4.3.4 Carrier Sense
Carrier Sense (CRS) may be asserted due to receive activ-
ity once valid data is detected via the squelch function.
For 10 Mb/s Half Duplex operation, CRS is asserted during
either packet transmission or reception.
For 10 Mb/s Full Duplex operation, CRS is asserted only
during receive activity.
CRS is deasserted following an end of packet.
4.3.5 Normal Link Pulse Detection/Generation
The link pulse generator produces pulses as defined in the
IEEE 802.3 10BASE-T standard. Each link pulse is nomi-
nally 100 ns in duration and transmitted every 16 ms in the
absence of transmit data.
Link pulses are used to check the integrity of the connec-
tion with the remote end. If valid link pulses are not
received, the link detector disables the 10BASE-T twisted
pair transmitter, receiver and collision detection functions.
When the link integrity function is disabled
(FORCE_LINK_10 of the 10BTSCR register), a good link is
forced and the 10BASE-T transceiver will operate regard-
less of the presence of link pulses.
4.3.6 Jabber Function
The jabber function monitors the DP83849I's output and
disables the transmitter if it attempts to transmit a packet of
longer than legal size. A jabber timer monitors the transmit-
ter and disables the transmission if the transmitter is active
for approximately 85 ms.
Once disabled by the Jabber function, the transmitter stays
disabled for the entire time that the ENDEC module's inter-
nal transmit enable is asserted. This signal has to be de-
asserted for approximately 500 ms (the “unjab” time)
before the Jabber function re-enables the transmit outputs.
The Jabber function is only relevant in 10BASE-T mode.
4.3.7 Automatic Link Polarity Detection and Correction
The DP83849I's 10BASE-T transceiver module incorpo-
rates an automatic link polarity detection circuit. When
three consecutive inverted link pulses are received, bad
polarity is reported.
A polarity reversal can be caused by a wiring error at either
end of the cable, usually at the Main Distribution Frame
(MDF) or patch panel in the wiring closet.
The bad polarity condition is latched in the 10BTSCR regis-
ter. The DP83849I's 10BASE-T transceiver module cor-
rects for this error internally and will continue to decode
received data correctly. This eliminates the need to correct
the wiring error immediately.
4.3.8 Transmit and Receive Filtering
External 10BASE-T filters are not required when using the
DP83849I, as the required signal conditioning is integrated
into the device.
Only isolation transformers and impedance matching resis-
tors are required for the 10BASE-T transmit and receive
interface. The internal transmit filtering ensures that all the
harmonics in the transmit signal are attenuated by at least
30 dB.
4.3.9 Transmitter
The encoder begins operation when the Transmit Enable
input (TX_EN) goes high and converts NRZ data to pre-
emphasized Manchester data for the transceiver. For the
duration of TX_EN, the serialized Transmit Data (TXD) is
encoded for the transmit-driver pair (PMD Output Pair).
TXD must be valid on the rising edge of Transmit Clock
(TX_CLK). Transmission ends when TX_EN deasserts.
The last transition is always positive; it occurs at the center
of the bit cell if the last bit is a one, or at the end of the bit
cell if the last bit is a zero.
4.3.10 Receiver
The decoder detects the end of a frame when no additional
mid-bit transitions are detected. Within one and a half bit
times after the last bit, carrier sense is de-asserted.
Receive clock stays active for five more bit times after CRS
goes low, to guarantee the receive timings of the controller.
41 www.national.com
DP83849I
5.0 Design Guidelines
5.1 TPI Network Circuit
Figure 12 shows the recommended circuit for a 10/100
Mb/s twisted pair interface.
Below is a partial list of recommended transformers. It is
important that the user realize that variations with PCB and
component characteristics requires that the application be
tested to ensure that the circuit meets the requirements of
the intended application.
Pulse H1102
Pulse H2019
Belfuse S558-5999-U7
Halo TG110-S050N2RL
Figure 12. 10/100 Mb/s Twisted Pair Interface
RJ45
TPRDM
TDRDP
TPTDM
TPTDP
RD-
RD+
TD-
TD+
1:1
0.1µF*
T1
1:1
COMMON MODE CHOKES
MAY BE REQUIRED.
49.9
49.9
0.1µF*
Vdd
NOTE: CENTER TAP IS PULLED TO VDD
*PLACE CAPACITORS CLOSE TO THE
TRANSFORMER CENTER TAPS
0.1µF
All values are typical and are +/- 1%
PLACE RESISTORS AND
CAPACITORS CLOSE TO
THE DEVICE.
Vdd
49.9
49.90.1µF
Vdd
www.national.com 42
DP83849I
5.2 ESD Protection
Typically, ESD precautions are predominantly in effect
when handling the devices or board before being installed
in a system. In those cases, strict handling procedures
need be implemented during the manufacturing process to
greatly reduce the occurrences of catastrophic ESD
events. After the system is assembled, internal compo-
nents are less sensitive from ESD events.
The network interface pins are more susceptible to ESD
events.
5.3 Clock In (X1) Requirements
The DP83849I supports an external CMOS level oscillator
source or a crystal resonator device.
Oscillator
If an external clock source is used, X1 should be tied to the
clock source and X2 should be left floating.
Specifications for CMOS oscillators: 25 MHz in MII Mode
and 50 MHz in RMII Mode are listed in Table 14 and Table
15.
Crystal
A 25 MHz, parallel, 20 pF load crystal resonator should be
used if a crystal source is desired. Figure 13 shows a typi-
cal connection for a crystal resonator circuit. The load
capacitor values will vary with the crystal vendors; check
with the vendor for the recommended loads.
The oscillator circuit is designed to drive a parallel reso-
nance AT cut crystal with a minimum drive level of 100µW
and a maximum of 500µW. If a crystal is specified for a
lower drive level, a current limiting resistor should be
placed in series between X2 and the crystal.
As a starting point for evaluating an oscillator circuit, if the
requirements for the crystal are not known, CL1 and CL2
should be set at 33 pF, and R1 should be set at 0Ω.
Specification for 25 MHz crystal are listed in Table 16.
Figure 13. Crystal Oscillator Circuit
X1 X2
CL2
CL1
R1
Table 14. 25 MHz Oscillator Specification
Parameter Min Typ Max Units Condition
Frequency 25 MHz
Frequency
Tolerance
+50 ppm Operational Tempera-
ture
Frequency
Stability
+50 ppm 1 year aging
Rise / Fall Time 6nsec 20% - 80%
Jitter 8001psec Short term
Jitter 8001psec Long term
Symmetry 40% 60% Duty Cycle
1 This limit is provided as a guideline for component selection and to guaranteed by production testing.
Refer to AN-1548, “PHYTER 100 Base-TX Reference Clock Jitter Tolerance,“ for details on jitter performance.
43 www.national.com
DP83849I
5.4 Power Feedback Circuit
To ensure correct operation for the DP83849I, parallel caps
with values of 10 µF and 0.1 µF should be placed close to
pin 31 (PFBOUT) of the device. Pin 7 (PFBIN1), pin 28
(PFBIN2), pin 34 (PFBIN3) and pin 54 (PFBIN4) must be
connected to pin 31 (PFBOUT), each pin requires a small
capacitor (.1 µF). See Figure 14 below for proper connec-
tions.
Table 15. 50 MHz Oscillator Specification
Parameter Min Typ Max Units Condition
Frequency 50 MHz
Frequency
Tolerance
+50 ppm Operational Temperature
Frequency
Stability
+50 ppm Operational Temperature
Rise / Fall Time 6nsec 20% - 80%
Jitter 8001psec Short term
Jitter 8001psec Long term
Symmetry 40% 60% Duty Cycle
1 This limit is provided as a guideline for component selection and to guaranteed by production testing.
Refer to AN-1548, “PHYTER 100 Base-TX Reference Clock Jitter Tolerance,“ for details on jitter performance.
Table 16. 25 MHz Crystal Specification
Parameter Min Typ Max Units Condition
Frequency 25 MHz
Frequency
Tolerance
+50 ppm Operational
Temperature
Frequency
Stability
+50 ppm 1 year aging
Load Capacitance 25 40 pF
.1 µF
10 µF
Pin 31 (
PFBOUT
)
.1 µF
.1 µF
Pin 7 (PFBIN1)
Pin 28 (PFBIN2)
+
-
.1 µF
.1 µF
Pin 34 (PFBIN3)
Pin 54 (PFBIN4)
Figure 14. Power Feeback Connection
www.national.com 44
DP83849I
5.5 Power Down/Interrupt
The Power Down and Interrupt functions are multiplexed
on pin 18 and pin 44 of the device. By default, this pin func-
tions as a power down input and the interrupt function is
disabled. Setting bit 0 (INT_OE) of MICR (11h) will config-
ure the pin as an active low interrupt output. Ports A and B
can be powered down individually, using the separate
PWRDOWN_INT_A and PWRDOWN_INT_B pins.
5.5.1 Power Down Control Mode
The PWRDOWN_INT pins can be asserted low to put the
device in a Power Down mode. This is equivalent to setting
bit 11 (Power Down) in the Basic Mode Control Register,
BMCR (00h). An external control signal can be used to
drive the pin low, overcoming the weak internal pull-up
resistor. Alternatively, the device can be configured to ini-
tialize into a Power Down state by use of an external pull-
down resistor on the PWRDOWN_INT pin. Since the
device will still respond to management register accesses,
setting the INT_OE bit in the MICR register will disable the
PWRDOWN_INT input, allowing the device to exit the
Power Down state.
5.5.2 Interrupt Mechanisms
Since each port has a separate interrupt pin, the interrupts
can be connected individually or may be combined in a
wired-OR fashion. If the interrupts share a single connec-
tion, each port status should be checked following an inter-
rupt.
The interrupt function is controlled via register access. All
interrupt sources are disabled by default. Setting bit 1
(INTEN) of MICR (11h) will enable interrupts to be output,
dependent on the interrupt mask set in the lower byte of
the MISR (12h). The PWRDOWN_INT pin is asynchro-
nously asserted low when an interrupt condition occurs.
The source of the interrupt can be determined by reading
the upper byte of the MISR. One or more bits in the MISR
will be set, denoting all currently pending interrupts. Read-
ing of the MISR clears ALL pending interrupts.
Example: To generate an interrupt on a change of link sta-
tus or on a change of energy detect power state, the steps
would be:
Write 0003h to MICR to set INTEN and INT_OE
Write 0060h to MISR to set ED_INT_EN and
LINK_INT_EN
Monitor PWRDOWN_INT pin
When PWRDOWN_INT pin asserts low, the user would
read the MISR register to see if the ED_INT or LINK_INT
bits are set, i.e. which source caused the interrupt. After
reading the MISR, the interrupt bits should clear and the
PWRDOWN_INT pin will deassert.
5.6 Energy Detect Mode
When Energy Detect is enabled and there is no activity on
the cable, the DP83849I will remain in a low power mode
while monitoring the transmission line. Activity on the line
will cause the DP83849I to go through a normal power up
sequence. Regardless of cable activity, the DP83849I will
occasionally wake up the transmitter to put ED pulses on
the line, but will otherwise draw as little power as possible.
Energy detect functionality is controlled via register Energy
Detect Control (EDCR), address 1Dh.
5.7 Link Diagnostic Capabilities
The DP83849I contains several system diagnostic capabil-
ities for evaluating link quality and detecting potential
cabling faults in Twisted Pair cabling. Software configura-
tion is available through the Link Diagnostics Registers -
Page 2 which can be selected via Page Select Register
(PAGESEL), address 13h. These capabilities include:
Linked Cable Status
Link Quality Monitor
TDR (Time Domain Reflectometry) Cable Diagnostics
5.7.1 Linked Cable Status
In an active connection with a valid link status, the following
diagnostic capabilities are available:
Polarity reversal
Cable swap (MDI vs MDIX) detection
100Mb Cable Length Estimation
Frequency offset relative to link partner
Cable Signal Quality Estimation
5.7.1.1 Polarity Reversal
The DP83849I detects polarity reversal by detecting nega-
tive link pulses. The Polarity indication is available in bit 12
of the PHYSTS (10h) or bit 4 of the 10BTSCR (1Ah).
Inverted polarity indicates the positive and negative con-
ductors in the receive pair are swapped. Since polarity is
corrected by the receiver, this does not necessarily indicate
a functional problem in the cable.
Since the polarity indication is dependent on link pulses
from the link partner, polarity indication is only valid in
10Mb modes of operation, or in 100Mb Auto-Negotiated
mode. Polarity indication is not available in 100Mb forced
mode of operation or in a parallel detected 100Mb mode.
5.7.1.2 Cable Swap Indication
As part of Auto-Negotiation, the DP83849I has the ability
(using Auto-MDIX) to automatically detect a cable with
swapped MDI pairs and select the appropriate pairs for
transmitting and receiving data. Normal operation is
termed MDI, while crossed operation is MDIX. The MDIX
status can be read from bit 14 of the PHYSTS (10h).
45 www.national.com
DP83849I
5.7.1.3 100MB Cable Length Estimation
The DP83849I provides a method of estimating cable
length based on electrical characteristics of the 100Mb
Link. This essentially provides an effective cable length
rather than a measurement of the physical cable length.
The cable length estimation is only available in 100Mb
mode of operation with a valid Link status. The cable
length estimation is available at the Link Diagnostics Reg-
isters - Page 2, register 100Mb Length Detect
(LEN100_DET), address 14h.
5.7.1.4 Frequency Offset Relative to Link Partner
As part of the 100Mb clock recovery process, the DSP
implementation provides a frequency control parameter.
This value may be used to indicate the frequency offset of
the device relative to the link partner. This operation is only
available in 100Mb operation with a valid link status. The
frequency offset can be determined using the register
100Mb Frequency Offset Indication (FREQ100), address
15h, of the Link Diagnostics Registers - Page 2.
Two different versions of the Frequency Offset may be
monitored through bits [7:0] of register FREQ100 (15h).
The first is the long-term Frequency Offset. The second is
the current Frequency Control value, which includes short-
term phase adjustments and can provide information on
the amount of jitter in the system.
5.7.1.5 Cable Signal Quality Estimation
The cable signal quality estimator keeps a simple tracking
of results of the DSP and can be used to generate an
approximate Signal-to-Noise Ratio for the 100Mb receiver.
This information is available to software through the Link
Diagnostics Registers - Page 2: Variance Control
(VAR_CTRL), address 1Ah and Data (VAR_DATA),
address 1Bh.
The variance computation times (VAR_TIMER) can be
chosen from the set of {2, 4, 6, 8} ms. The 32-bit variance
sum can be read by two consecutive reads of the
VAR_DATA register. This sum can be used to compute an
SNR estimate by software using the following equation:
SNR = 10log10((37748736 * VAR_TIMER) / Variance).
5.7.2 Link Quality Monitor
The Link Quality Monitor allows a method to generate an
alarm when the DSP adaption strays from a programmable
window. This could occur due to changes in the cable
which could indicate a potential problem. Software can
program thresholds for the following DSP parameters to be
used to interrupt the system:
Digital Equalizer C1 Coefficient (DEQ C1)
Digital Adaptive Gain Control (DAGC)
Digital Base-Line Wander Control (DBLW)
Recovered Clock Long-Term Frequency Offset (FREQ)
Recovered Clock Frequency Control (FC)
Software is expected to read initial adapted values and
then program the thresholds based on an expected valid
range. This mechanism takes advantage of the fact that
the DSP adaption should remain in a relatively small range
once a valid link has been established.
5.7.2.1 Link Quality Monitor Control and Status
Control of the Link Quality Monitor is done through the Link
Quality Monitor Register (LQMR), address 1Dh and the
Link Quality Data Register (LQDR), address 1Bh of the
Link Diagnostics Registers - Page 2. The LQMR register
includes a global enable to enable the Link Quality Monitor
function. In addition, it provides warning status from both
high and low thresholds for each of the monitored parame-
ters. Note that individual low or high parameter threshold
comparisons can be disabled by setting to the minimum or
maximum values.
To allow the Link Quality Monitor to interrupt the system,
the Interrupt must be enabled through the interrupt control
registers, MICR (11h) and MISR (12h).
5.7.2.2 Checking Current Parameter Values
Prior to setting Threshold values, it is recommended that
software check current adapted values. The thresholds
may then be set relative to the adapted values. The current
adapted values can be read using the LQDR register by
setting the Sample_Param bit [13] of LQDR, address
(1Eh).
For example, to read the DBLW current value:
1. Write 2400h to LQDR (1Eh) to set the Sample_Param
bit and set the LQ_PARAM_SEL[2:0] to 010.
2. Read LQDR (1Eh). Current DBLW value is returned
in the low 8 bits.
5.7.2.3 Threshold Control
The LQDR (1Eh) register also provides a method of pro-
gramming high and low thresholds for each of the four
parameters that can be monitored. The register imple-
ments an indirect read/write mechanism.
Writes are accomplished by writing data, address, and a
write strobe to the register. Reads are accomplished by
writing the address to the register, and reading back the
value of the selected threshold. Setting thresholds to the
maximum or minimum values will disable the threshold
comparison since values have to exceed the threshold to
generate a warning condition.
Warnings are not generated if the parameter is equal to the
threshold. By default, all thresholds are disabled by setting
to the min or max values. The following table shows the
four parameters and range of values:
www.national.com 46
DP83849I
Table 17. Link Quality Monitor Parameter Ranges
5.7.3 TDR Cable Diagnostics
The DP83849I implements a Time Domain Reflectometry
(TDR) method of cable length measurement and evalua-
tion which can be used to evaluate a connected twisted
pair cable. The TDR implementation involves sending a
pulse out on either the Transmit or Receive conductor pair
and observing the results on either pair. By observing the
types and strength of reflections on each pair, software can
determine the following:
—Cable short
Cable open
Distance to fault
Identify which pair has a fault
Pair skew
The TDR cable diagnostics works best in certain condi-
tions. For example, an unterminated cable provides a
good reflection for measuring cable length, while a cable
with an ideal termination to an unpowered partner may pro-
vide no reflection at all.
5.7.3.1 TDR Pulse Generator
The TDR implementation can send two types of TDR
pulses. The first option is to send 50ns or 100ns link
pulses from the 10Mb Common Driver. The second option
is to send pulses from the 100Mb Common Driver in 8ns
increments up to 56ns in width. The 100Mb pulses will
alternate between positive and negative pulses. The
shorter pulses provide better ability to measure short cable
lengths, especially since they will limit overlap between the
transmitted pulse and a reflected pulse. The longer pulses
may provide better measurements of long cable lengths.
In addition, if the pulse width is programmed to 0, no pulse
will be sent, but monitor circuit will still be activated. This
allows sampling of background data to provide a baseline
for analysis.
5.7.3.2 TDR Pulse Monitor
The TDR function monitors data from the Analog to Digital
Converter (ADC) to detect both peak values and values
above a programmable threshold. It can be programmed
to detect maximum or minimum values. In addition, it
records the time, in 8ns intervals, at which the peak or
threshold value first occurs.
The TDR monitor implements a timer that starts when the
pulse is transmitted. A window may be enabled to qualify
incoming data to look for response only in a desired range.
This is especially useful for eliminating the transmitted
pulse, but also may be used to look for multiple reflections.
5.7.3.3 TDR Control Interface
The TDR Control interface is implemented in the Link Diag-
nostics Registers - Page 2 through TDR Control
(TDR_CTRL), address 16h and TDR Window (TDR_WIN),
address 17h. The following basic controls are:
TDR Enable: Enable bit 15 of TDR_CTRL (16h) to allow
the TDR function. This bypasses normal operation and
gives control of the CD10 and CD100 block to the TDR
function.
TDR Send Pulse: Enable bit 11 of TDR_CTRL (16h) to
send the TDR pulse and starts the TDR Monitor.
The following Transmit mode controls are available:
Transmit Mode: Enables use of 10Mb Link pulses from
the 10Mb Common Driver or data pulses from the 100Mb
Common Driver by enabling TDR 100Mb, bit 14 of
TDR_CRTL (16h).
Transmit Pulse Width: Bits [10:8] of TDR_CTRL (16h)
allows sending of 0 to 7 clock width pulses. Actual puls-
es are dependent on the transmit mode. If Pulse Width
is set to 0, then no pulse will be sent.
Transmit Channel Select: The transmitter can send
pulses down either the transmit pair or the receive pair
by enabling bit 13 of TDR_CTRL (16h). Default value is
to select the transmit pair.
The following Receive mode controls are available:
Min/Max Mode Select: Bit 7 of TDR_CTRL (16h) con-
trols the TDR Monitor operation. In default mode, the
monitor will detect maximum (positive) values. In Min
mode, the monitor will detect minimum (negative) val-
ues.
Receive Channel Select: The receiver can monitor ei-
ther the transmit pair or the receive pair by enabling bit
12 of TDR_CTRL (16h). Default value is to select the
transmit pair.
Parameter Minimum Value Maximum Value Min (2-s comp) Max (2-s comp)
DEQ C1 -128 +127 0x80 0x7F
DAGC 0+255 0x00 0xFF
DBLW -128 +127 0x80 0x7F
Freq Offset -128 +127 0x80 0x7F
Freq Control -128 +127 0x80 0x7F
47 www.national.com
DP83849I
Receive Window: The receiver can monitor receive
data within a programmable window using the TDR Win-
dow Register (TDR_WIN), address 17h. The window is
controlled by two register values: TDR Start Window, bits
[15:8] of TDR_WIN (17h) and TDR Stop Window, bits
[7:0] of TDR_WIN (17h). The TDR Start Window indi-
cates the first clock to start sampling. The TDR Stop
Window indicates the last clock to sample. By default,
the full window is enabled, with Start set to 0 and Stop
set to 255. The window range is in 8ns clock increments,
so the maximum window size is 2048ns.
5.7.3.4 TDR Results
The TDR function monitors data from the Analog to Digital
Converter (ADC) to detect both peak values and values
above a programmable threshold. It can be programmed
to detect maximum or minimum values. In addition, it
records the time, in 8ns intervals, at which the peak or
threshold value first occurs. The results of a TDR peak and
threshold measurement are available in the TDR Peak
Measurement Register (TDR_PEAK), address 18h and
TDR Threshold Measurement Register (TDR_THR),
address 19h. The threshold measurement may be a more
accurate method of measuring the length for longer cables
to provide a better indication of the start of the received
pulse, rather than the peak value.
Software utilizing the TDR function should implement an
algorithm to send TDR pulses and evaluate results. Multi-
ple runs should be used to best qualify any received pulses
as multiple reflections could exist. In addition, when moni-
toring the transmitting pair, the window feature should be
used to disqualify the transmitted pulse. Multiple runs may
also be used to average the values providing more accu-
rate results.
Actual distance measurements are dependent on the
velocity of propagation of the cable. The delay value is typ-
ically on the order of 4.6 to 4.9 ns/m.
www.national.com 48
DP83849I
6.0 Reset Operation
The DP83849I includes an internal power-on reset (POR)
function and does not need to be explicitly reset for normal
operation after power up. If required during normal opera-
tion, the device can be reset by a hardware or software
reset.
6.1 Hardware Reset
A hardware reset is accomplished by applying a low pulse
(TTL level), with a duration of at least 1 µs, to the
RESET_N pin. This will reset the device such that all regis-
ters will be reinitialized to default values and the hardware
configuration values will be re-latched into the device (simi-
lar to the power-up/reset operation).
6.2 Full Software Reset
A full-chip software reset is accomplished by setting the
reset bit (bit 15) of the Basic Mode Control Register
(BMCR). The period from the point in time when the reset
bit is set to the point in time when software reset has con-
cluded is approximately 1 µs.
The software reset will reset the device such that all regis-
ters will be reset to default values and the hardware config-
uration values will be maintained. Software driver code
must wait 3 µs following a software reset before allowing
further serial MII operations with the DP83849I.
6.3 Soft Reset
A partial software reset can be initiated by setting the Soft
Reset bit (bit 9) in the PHYCR2 Register. Setting this bit will
reset all transmit and receive operations, but will not reset
the register space. All register configurations will be pre-
served. Register space will remain available following a
Soft Reset.
49 www.national.com
DP83849I
7.0 Register Block
Table 18. Register Map
Offset Access Tag Description
Hex Decimal
00h 0RW BMCR Basic Mode Control Register
01h 1RO BMSR Basic Mode Status Register
02h 2RO PHYIDR1 PHY Identifier Register #1
03h 3RO PHYIDR2 PHY Identifier Register #2
04h 4RW ANAR Auto-Negotiation Advertisement Register
05h 5RW ANLPAR Auto-Negotiation Link Partner Ability Register (Base Page)
05h 5RW ANLPARNP Auto-Negotiation Link Partner Ability Register (Next Page)
06h 6RW ANER Auto-Negotiation Expansion Register
07h 7RW ANNPTR Auto-Negotiation Next Page TX
08h-Fh 8-15 RESERVED RESERVED
10h 16 RO PHYSTS PHY Status Register
11h 17 RW MICR MII Interrupt Control Register
12h 18 RW MISR MII Interrupt Status Register
13h 19 RW PAGESEL Page Select Register
Extended Registers - Page 0
14h 20 RO FCSCR False Carrier Sense Counter Register
15h 21 RO RECR Receive Error Counter Register
16h 22 RW PCSR PCS Sub-Layer Configuration and Status Register
17h 23 RW RBR RMII and Bypass Register
18h 24 RW LEDCR LED Direct Control Register
19h 25 RW PHYCR PHY Control Register
1Ah 26 RW 10BTSCR 10Base-T Status/Control Register
1Bh 27 RW CDCTRL1 CD Test Control Register and BIST Extensions Register
1Ch 28 RW PHYCR2 Phy Control Register 2
1Dh 29 RW EDCR Energy Detect Control Register
1Eh-1Fh 30-31 RESERVED RESERVED
Reserved Registers
14h-1Fh 30-31 RESERVED RESERVED
Link Diagnostics Registers - Page 2
14h 20 RO LEN100_DET 100Mb Length Detect Register
15h 21 RW FREQ100 100Mb Frequency Offset Indication Register
16h 22 RW TDR_CTRL TDR Control Register
17h 23 RW TDR_WIN TDR Window Register
18h 24 RO TDR_PEAK TDR Peak Measurement Register
19h 25 RO TDR_THR TDR Threshold Measurement Register
1Ah 26 RW VAR_CTRL Variance Control Register
1Bh 27 RO VAR_DAT Variance Data Register
1Ch 28 RESERVED RESERVED
1Dh 29 RW LQMR Link Quality Monitor Register
1Eh 30 RW LQDR Link Quality Data Register
1Fh 31 RESERVED RESERVED
www.national.com 50
DP83849I
Table 19. Register Table
Register Name Addr Tag Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Basic Mode Control Register 00h BMCR Reset Loop-
back
Speed
Selection
Auto-
Neg
Enable
Power
Down
Isolate Restart
Auto-
Neg
Duplex
Mode
Collision
Test
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Basic Mode Status Register 01h BMSR 100Base
-T4
100Base
-TX FDX
100Base
-TX HDX
10Base-
T
FDX
10Base-
T
HDX
Re-
served
Re-
served
Re-
served
Re-
served
MF Pre-
amble
Sup-
press
Auto-
Neg
Com-
plete
Remote
Fault
Auto-
Neg
Ability
Link
Status
Jabber
Detect
Extend-
ed Capa-
bility
PHY Identifier Register 1 02h PHYIDR
1
OUI MSB OUI MSB OUI MSB OUI MSB OUI MSB OUI MSB OUI MSB OUI MSB OUI MSB OUI MSB OUI MSB OUI MSB OUI MSB OUI MSB OUI MSB OUI MSB
PHY Identifier Register 2 03h PHYIDR
2
OUI LSB OUI LSB OUI LSB OUI LSB OUI LSB OUI LSB VNDR_
MDL
VNDR_
MDL
VNDR_
MDL
VNDR_
MDL
VNDR_
MDL
VNDR_
MDL
MDL_
REV
MDL_
REV
MDL_
REV
MDL_
REV
Auto-Negotiation Advertisement Register 04h ANAR Next
Page Ind
Re-
served
Remote
Fault
Re-
served
ASM_DI
R
PAUSE T4 TX_FD TX 10_FD 10 Protocol
Selection
Protocol
Selection
Protocol
Selection
Protocol
Selection
Protocol
Selection
Auto-Negotiation Link Partner Ability Register
(Base Page)
05h ANLPAR Next
Page Ind
ACK Remote
Fault
Re-
served
ASM_DI
R
PAUSE T4 TX_FD TX 10_FD 10 Protocol
Selection
Protocol
Selection
Protocol
Selection
Protocol
Selection
Protocol
Selection
Auto-Negotiation Link Partner Ability Register
Next Page
05h AN-
LPARNP
Next
Page Ind
ACK Mes-
sage
Page
ACK2 Toggle Code Code Code Code Code Code Code Code Code Code Code
Auto-Negotiation Expansion Register 06h ANER Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
PDF LP_NP_
ABLE
NP_
ABLE
PAGE_
RX
LP_AN_
ABLE
Auto-Negotiation Next Page TX Register 07h ANNPTR Next
Page Ind
Re-
served
Mes-
sage
Page
ACK2 TOG_TX CODE CODE CODE CODE CODE CODE CODE CODE CODE CODE CODE
RESERVED 08-0fh Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
PHY Status Register 10h PHYSTS Re-
served
MDIX
mode
Rx Err
Latch
Polarity
Status
False
Carrier
Sense
Signal
Detect
De-
scram-
bler Lock
Page
Receive
MII Inter-
rupt
Remote
Fault
Jabber
Detect
Auto-
Neg
Com-
plete
Loop-
back Sta-
tus
Duplex
Status
Speed
Status
Link
Status
MII Interrupt Control Register 11h MICR Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
TINT INTEN INT_OE
MII Interrupt Status and Misc. Control Regis-
ter
12h MISR LQ_INT ED_INT LINK_IN
T
SPD_IN
T
DUP_IN
T
ANC_IN
T
FHF_INT RHF_IN
T
LQ_INT_
EN
ED_INT_
EN
LINK_IN
T_EN
SPED_I
NT_EN
DUP_IN
T_EN
ANC_IN
T_EN
FHF_INT
_EN
RHF_IN
T_EN
Page Select Register 13h Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Page_Se
l Bit
Page_Se
l Bit
EXTENDED REGISTERS
False Carrier Sense Counter Register 14h FCSCR Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
FCSCNT FCSCNT FCSCNT FCSCNT FCSCNT FCSCNT FCSCNT FCSCNT
Receive Error Counter Register 15h RECR Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
RXER-
CNT
RXER-
CNT
RXER-
CNT
RXER-
CNT
RXER-
CNT
RXER-
CNT
RXER-
CNT
RXER-
CNT
PCS Sub-Layer Configuration and Status
Register
16h PCSR Re-
served
Re-
served
Re-
served
Re-
served
FREE_C
LK
TQ_EN SD_FOR
CE_PMA
SD_
OPTION
DESC_T
IME
Re-
served
FORCE_
100_OK
Re-
served
Re-
served
NRZI_
BYPASS
Re-
served
Re-
served
51 www.national.com
DP83849I
RMII and Bypass Register 17h RBR SIM_WR
ITE
Re-
served
DIS_TX_
OPT
RX_POR
T
RX_POR
T
TX_SOU
RCE
TX_SOU
RCE
PMD_LO
OP
SCMII_R
X
SCMII_T
X
RMII_M
ODE
RMII_RE
V1_0
RX_OVF
_STS
RX_UNF
_STS
ELAST_
BUF
ELAST_
BUF
LED Direct Control Register 18h LEDCR Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
LEDACT
_RX
BLINK_F
REQ
BLINK_F
REQ
DRV_SP
DLED
DRV_LN
KLED
DRV_AC
TLED
SPDLED LNKLED ACTLED
PHY Control Register 19h PHYCR MDIX_E
N
FORCE_
MDIX
PAUSE_
RX
PAUSE_
TX
BIST_FE PSR_15 BIST_
STATUS
BIST_ST
ART
BP_STR
ETCH
LED_
CNFG[1]
LED_
CNFG[0]
PHY
ADDR
PHY
ADDR
PHY
ADDR
PHY
ADDR
PHY
ADDR
10Base-T Status/Control Register 1Ah 10BT_S
ERIAL
Re-
served
Re-
served
Re-
served
Re-
served
SQUELC
H
SQUELC
H
SQUELC
H
LOOPBA
CK_10_
DIS
LP_DIS FORCE_
LINK_10
Re-
served
POLARI-
TY
Re-
served
Re-
served
HEARTB
EAT_DIS
JABBER
_DIS
CD Test Control and BIST Extensions Regis-
ter
1Bh CDCTRL
1
BIST_ER
ROR_C
OUNT
BIST_ER
ROR_C
OUNT
BIST_ER
ROR_C
OUNT
BIST_ER
ROR_C
OUNT
BIST_ER
ROR_C
OUNT
BIST_ER
ROR_C
OUNT
BIST_ER
ROR_C
OUNT
BIST_ER
ROR_C
OUNT
Re-
served
Re-
served
BIST_C
ONT_M
ODE
CDPattE
N_10
Re-
served
10Meg_
Patt_Ga
p
CDPatt-
Sel
CDPatt-
Sel
Phy Control Register 2 1Ch PHYCR2 Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
SOFT_R
ESET
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Energy Detect Control Register 1Dh EDCR ED_EN ED_AUT
O_UP
ED_AUT
O_DOW
N
ED_MAN ED_BUR
ST_DIS
ED_PW
R_STAT
E
ED_ERR
_MET
ED_DAT
A_MET
ED_ERR
_COUNT
ED_ERR
_COUNT
ED_ERR
_COUNT
ED_ERR
_COUNT
ED_DAT
A_COUN
T
ED_DAT
A_COUN
T
ED_DAT
A_COUN
T
ED_DAT
A_COUN
T
RESERVED 1Eh-1Fh Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
RESERVED REGISTERS
RESERVED 14h-1Fh Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
LINK DIAGNOSTICS REGISTERS - PAGE 2
100Mb Length Detect Register 14h LEN100_
DET
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
CABLE_
LEN
CABLE_
LEN
CABLE_
LEN
CABLE_
LEN
CABLE_
LEN
CABLE_
LEN
CABLE_
LEN
CABLE_
LEN
100Mb Frequency Offset Indication Register 15h FREQ10
0
SAMPLE
_FREQ
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
SEL_FC FREQ_O
FFSET
FREQ_O
FFSET
FREQ_O
FFSET
FREQ_O
FFSET
FREQ_O
FFSET
FREQ_O
FFSET
FREQ_O
FFSET
FREQ_O
FFSET
TDR Control Register 16h TDR_CT
RL
TDR_EN
ABLE
TDR_10
0Mb
TX_CHA
NNEL
RX_CHA
NNEL
SEND_T
DR
TDR_WI
DTH
TDR_WI
DTH
TDR_WI
DTH
TDR_MI
N_MOD
E
Re-
served
RX_THR
ESHOLD
RX_THR
ESHOLD
RX_THR
ESHOLD
RX_THR
ESHOLD
RX_THR
ESHOLD
RX_THR
ESHOLD
TDR Window Register 17h TDR_WI
N
TDR_ST
ART
TDR_ST
ART
TDR_ST
ART
TDR_ST
ART
TDR_ST
ART
TDR_ST
ART
TDR_ST
ART
TDR_ST
ART
TDR_ST
OP
TDR_ST
OP
TDR_ST
OP
TDR_ST
OP
TDR_ST
OP
TDR_ST
OP
TDR_ST
OP
TDR_ST
OP
TDR Peak Register 18h TDR_PE
AK
Re-
served
Re-
served
TDR_PE
AK
TDR_PE
AK
TDR_PE
AK
TDR_PE
AK
TDR_PE
AK
TDR_PE
AK
TDR_PE
AK_TIM
E
TDR_PE
AK_TIM
E
TDR_PE
AK_TIM
E
TDR_PE
AK_TIM
E
TDR_PE
AK_TIM
E
TDR_PE
AK_TIM
E
TDR_PE
AK_TIM
E
TDR_PE
AK_TIM
E
TDR Threshold Register 19h TDR_TH
R
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
TDR_TH
R_MET
TDR-
THR_TI
ME
TDR-
THR_TI
ME
TDR-
THR_TI
ME
TDR-
THR_TI
ME
TDR-
THR_TI
ME
TDR-
THR_TI
ME
TDR-
THR_TI
ME
TDR-
THR_TI
ME
Variance Control Register 1Ah VAR_CT
RL
VAR_RD
Y
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
VAR_FR
EEZE
VAR_TI
MER
VAR_TI
MER
VAR_TI
MER
Variance Data Register 1Bh VAR_DA
TA
VAR_DA
TA
VAR_DA
TAT
VAR_DA
TA
VAR_DA
TA
VAR_DA
TA
VAR_DA
TAT
VAR_DA
TA
VAR_DA
TA
VAR_DA
TA
VAR_DA
TAT
VAR_DA
TA
VAR_DA
TA
VAR_DA
TA
VAR_DA
TAT
VAR_DA
TA
VAR_DA
TA
RESERVED 1Ch Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Table 19. Register Table
Register Name Addr Tag Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
www.national.com 52
DP83849I
Link Quality Monitor Register 1Dh LQMR LQM_EN
ABLE
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
FC_HI_
WARN
FC_LO_
WARN
FREQ_H
I_WARN
FREQ_L
O_WAR
N
DBLW_H
I_WARN
DBLW_L
O_WAR
N
DAGC_H
I_WARN
DAGC_L
O_WAR
N
C1_HI_
WARN
C1_LO_
WARN
Link Quality Data Register 1Eh LQDR Re-
served
Re-
served
SAMPLE
_PARAM
WRITE_
LQ_THR
LQ_PAR
AM_SEL
LQ_PAR
AM_SEL
LQ_PAR
AM_SEL
LQ_THR
_SEL
LQ_THR
_DATA
LQ_THR
_DATA
LQ_THR
_DATA
LQ_THR
_DATA
LQ_THR
_DATA
LQ_THR
_DATA
LQ_THR
_DATA
LQ_THR
_DATA
RESERVED 1Fh Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Re-
served
Table 19. Register Table
Register Name Addr Tag Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
53 www.national.com
DP83849I
7.1 Register Definition
In the register definitions under the ‘Default’ heading, the following definitions hold true:
RW=Read Write access
SC=Register sets on event occurrence and Self-Clears when event ends
RW/SC =Read Write access/Self Clearing bit
RO=Read Only access
COR = Clear on Read
RO/COR=Read Only, Clear on Read
RO/P=Read Only, Permanently set to a default value
LL=Latched Low and held until read, based upon the occurrence of the corresponding event
—LH=Latched High and held until read, based upon the occurrence of the corresponding event
www.national.com 54
DP83849I
7.1.1 Basic Mode Control Register (BMCR)
Table 20. Basic Mode Control Register (BMCR), address 00h
Bit Bit Name Default Description
15 RESET 0, RW/SC Reset:
1 = Initiate software Reset / Reset in Process.
0 = Normal operation.
This bit, which is self-clearing, returns a value of one until the reset process
is complete. The configuration is re-strapped.
14 LOOPBACK 0, RW Loopback:
1 = Loopback enabled.
0 = Normal operation.
The loopback function enables MII transmit data to be routed to the MII re-
ceive data path.
Setting this bit may cause the descrambler to lose synchronization and
produce a 500 µs “dead time” before any valid data will appear at the MII
receive outputs.
13 SPEED
SELECTION
Strap, RW Speed Select:
When auto-negotiation is disabled writing to this bit allows the port speed
to be selected.
1 = 100 Mb/s.
0 = 10 Mb/s.
12 AUTO-NEGOTI-
ATION
ENABLE
Strap, RW Auto-Negotiation Enable:
Strap controls initial value at reset.
1 = Auto-Negotiation Enabled - bits 8 and 13 of this register are ignored
when this bit is set.
0 = Auto-Negotiation Disabled - bits 8 and 13 determine the port speed and
duplex mode.
11 POWER DOWN 0, RW Power Down:
1 = Power down.
0 = Normal operation.
Setting this bit powers down the PHY. Only the register block is enabled
during a power down condition. This bit is OR’d with the input from the
PWRDOWN_INT pin. When the active low PWRDOWN_INT pin is assert-
ed, this bit will be set.
10 ISOLATE 0, RW Isolate:
1 = Isolates the Port from the MII with the exception of the serial manage-
ment.
0 = Normal operation.
9RESTART
AUTO-NEGOTI-
ATION
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.
8DUPLEX MODE Strap, RW Duplex Mode:
When auto-negotiation is disabled writing to this bit allows the port Duplex
capability to be selected.
1 = Full Duplex operation.
0 = Half Duplex operation.
55 www.national.com
DP83849I
7COLLISION
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 within 512-bit times. The COL signal will be de-as-
serted within 4-bit times in response to the de-assertion of TX_EN.
6:0 RESERVED 0, RO RESERVED: Write ignored, read as 0.
Table 20. Basic Mode Control Register (BMCR), address 00h (Continued)
Bit Bit Name Default Description
www.national.com 56
DP83849I
7.1.2 Basic Mode Status Register (BMSR)
Table 21. Basic Mode Status Register (BMSR), address 01h
Bit Bit Name Default Description
15 100BASE-T4 0, RO/P 100BASE-T4 Capable:
0 = Device not able to perform 100BASE-T4 mode.
14 100BASE-TX
FULL DUPLEX
1, RO/P 100BASE-TX Full Duplex Capable:
1 = Device able to perform 100BASE-TX in full duplex mode.
13 100BASE-TX
HALF DUPLEX
1, RO/P 100BASE-TX Half Duplex Capable:
1 = Device able to perform 100BASE-TX in half duplex mode.
12 10BASE-T
FULL DUPLEX
1, RO/P 10BASE-T Full Duplex Capable:
1 = Device able to perform 10BASE-T in full duplex mode.
11 10BASE-T
HALF DUPLEX
1, RO/P 10BASE-T Half Duplex Capable:
1 = Device able to perform 10BASE-T in half duplex mode.
10:7 RESERVED 0, RO RESERVED: Write as 0, read as 0.
6MF PREAMBLE
SUPPRESSION
1, RO/P 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.
0 = Normal management operation.
5AUTO-NEGOTIATION
COMPLETE
0, RO Auto-Negotiation Complete:
1 = Auto-Negotiation process complete.
0 = Auto-Negotiation process not complete.
4REMOTE 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.
3AUTO-NEGOTIATION
ABILITY
1, RO/P Auto Negotiation Ability:
1 = Device is able to perform Auto-Negotiation.
0 = Device is not able to perform Auto-Negotiation.
2LINK STATUS 0, RO/LL Link Status:
1 = Valid link established (for either 10 or 100 Mb/s operation).
0 = Link not established.
The criteria for link validity is implementation specific. 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.
1JABBER DETECT 0, RO/LH Jabber Detect: This bit only has meaning in 10 Mb/s mode.
1 = Jabber condition detected.
0 = No Jabber.
This bit is implemented with a latching function, such that the occur-
rence of a jabber condition causes it to set until it is cleared by a read
to this register by the management interface or by a reset.
0EXTENDED
CAPABILITY
1, RO/P Extended Capability:
1 = Extended register capabilities.
0 = Basic register set capabilities only.
57 www.national.com
DP83849I
The PHY Identifier Registers #1 and #2 together form a unique identifier for the DP83849I. The Identifier consists of a
concatenation of the Organizationally Unique Identifier (OUI), the vendor's model number and the model revision num-
ber. 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 080017h.
7.1.3 PHY Identifier Register #1 (PHYIDR1)
7.1.4 PHY Identifier Register #2 (PHYIDR2)
7.1.5 Auto-Negotiation Advertisement Register (ANAR)
This register contains the advertised abilities of this device as they will be transmitted to its link partner during Auto-Nego-
tiation. Any writes to this register prior to completion of Auto-Negotiation (as indicated in the Basic Mode Status Register
(address 01h) Auto-Negotiation Complete bit, BMSR[5]) should be followed by a renegotiation. This will ensure that the
new values are properly used in the Auto-Negotiation.
Table 22. PHY Identifier Register #1 (PHYIDR1), address 02h
Bit Bit Name Default Description
15:0 OUI_MSB <0010 0000 0000
0000>, RO/P
OUI Most Significant Bits: Bits 3 to 18 of the OUI (080017h) 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).
Table 23. PHY Identifier Register #2 (PHYIDR2), address 03h
Bit Bit Name Default Description
15:10 OUI_LSB <0101 11>, RO/P OUI Least Significant Bits:
Bits 19 to 24 of the OUI (080017h) are mapped from bits 15 to 10
of this register respectively.
9:4 VNDR_MDL <00 1010>, RO/P Vendor Model Number:
The six bits of vendor model number are mapped from bits 9 to 4
(most significant bit to bit 9).
3:0 MDL_REV <0010>, RO/P Model Revision Number:
Four bits of the vendor model revision number are mapped from
bits 3 to 0 (most significant bit to bit 3). This field will be incremented
for all major device changes.
Table 24. Negotiation Advertisement Register (ANAR), address 04h
Bit Bit Name Default Description
15 NP 0, RW Next Page Indication:
0 = Next Page Transfer not desired.
1 = Next Page Transfer desired.
14 RESERVED 0, RO/P 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, RW RESERVED for Future IEEE use: Write as 0, Read as 0
www.national.com 58
DP83849I
11 ASM_DIR 0, RW Asymmetric PAUSE Support for Full Duplex Links:
The ASM_DIR bit indicates that asymmetric PAUSE is supported.
Encoding and resolution of PAUSE bits is defined in IEEE 802.3
Annex 28B, Tables 28B-2 and 28B-3, respectively. Pause resolu-
tion status is reported in PHYCR[13:12].
1 = Advertise that the DTE (MAC) has implemented both the op-
tional MAC control sublayer and the pause function as specified in
clause 31 and annex 31B of 802.3u.
0= No MAC based full duplex flow control.
10 PAUSE 0, RW PAUSE Support for Full Duplex Links:
The PAUSE bit indicates that the device is capable of providing the
symmetric PAUSE functions as defined in Annex 31B.
Encoding and resolution of PAUSE bits is defined in IEEE 802.3
Annex 28B, Tables 28B-2 and 28B-3, respectively. Pause resolu-
tion status is reported in PHYCR[13:12].
1 = Advertise that the DTE (MAC) has implemented both the op-
tional MAC control sublayer and the pause function as specified in
clause 31 and annex 31B of 802.3u.
0= No MAC based full duplex flow control.
9T4 0, RO/P 100BASE-T4 Support:
1= 100BASE-T4 is supported by the local device.
0 = 100BASE-T4 not supported.
8TX_FD Strap, RW 100BASE-TX Full Duplex Support:
1 = 100BASE-TX Full Duplex is supported by the local device.
0 = 100BASE-TX Full Duplex not supported.
7TX Strap, RW 100BASE-TX Support:
1 = 100BASE-TX is supported by the local device.
0 = 100BASE-TX not supported.
610_FD Strap, RW 10BASE-T Full Duplex Support:
1 = 10BASE-T Full Duplex is supported by the local device.
0 = 10BASE-T Full Duplex not supported.
510 Strap, RW 10BASE-T Support:
1 = 10BASE-T is supported by the local device.
0 = 10BASE-T not supported.
4:0 SELECTOR <00001>, RW Protocol Selection Bits:
These bits contain the binary encoded protocol selector supported
by this port. <00001> indicates that this device supports IEEE
802.3u.
Table 24. Negotiation Advertisement Register (ANAR), address 04h (Continued)
Bit Bit Name Default Description
59 www.national.com
DP83849I
7.1.6 Auto-Negotiation Link Partner Ability Register (ANLPAR) (BASE Page)
This register contains the advertised abilities of the Link Partner as received during Auto-Negotiation. The content
changes after the successful auto-negotiation if Next-pages are supported.
Table 25. Auto-Negotiation Link Partner Ability Register (ANLPAR) (BASE Page), address 05h
Bit Bit Name Default Description
15 NP 0, RO 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 Auto-Negotiation state machine will automatically control the
this bit based on the incoming FLP bursts.
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 ASM_DIR 0, RO ASYMMETRIC PAUSE:
1 = Asymmetric pause is supported by the Link Partner.
0 = Asymmetric pause is not supported by the Link Partner.
10 PAUSE 0, RO PAUSE:
1 = Pause function is supported by the Link Partner.
0 = Pause function is not supported by the Link Partner.
9T4 0, RO 100BASE-T4 Support:
1 = 100BASE-T4 is supported by the Link Partner.
0 = 100BASE-T4 not supported by the Link Partner.
8TX_FD 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.
7TX 0, RO 100BASE-TX Support:
1 = 100BASE-TX is supported by the Link Partner.
0 = 100BASE-TX not supported by the Link Partner.
610_FD 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.
510 0, RO 10BASE-T Support:
1 = 10BASE-T is supported by the Link Partner.
0 = 10BASE-T not supported by the Link Partner.
4:0 SELECTOR <0 0000>, RO Protocol Selection Bits:
Link Partner’s binary encoded protocol selector.
www.national.com 60
DP83849I
7.1.7 Auto-Negotiation Link Partner Ability Register (ANLPAR) (Next Page)
Table 26. Auto-Negotiation Link Partner Ability Register (ANLPAR) (Next Page), address 05h
Bit Bit Name Default Description
15 NP 0, RO Next Page Indication:
1 = Link Partner desires Next Page Transfer.
0 = Link Partner does not desire Next Page Transfer.
14 ACK 0, RO Acknowledge:
1 = Link Partner acknowledges reception of the ability data word.
0 = Not acknowledged.
The Auto-Negotiation state machine will automatically control the
this bit based on the incoming FLP bursts. Software should not at-
tempt to write to this bit.
13 MP 0, RO Message Page:
1 = Message Page.
0 = Unformatted Page.
12 ACK2 0, RO Acknowledge 2:
1 = Link Partner does have the ability to comply to next page mes-
sage.
0 = Link Partner does not have the ability to comply to next page
message.
11 TOGGLE 0, RO Toggle:
1 = Previous value of the transmitted Link Code word equalled 0.
0 = Previous value of the transmitted Link Code word equalled 1.
10:0 CODE <000 0000 0000>,
RO
Code:
This field represents the code field of the next page transmission.
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
Clause 28. Otherwise, the code shall be interpreted as an “Unfor-
matted Page,” and the interpretation is application specific.
61 www.national.com
DP83849I
7.1.8 Auto-Negotiate Expansion Register (ANER)
This register contains additional Local Device and Link Partner status information.
Table 27. Auto-Negotiate Expansion Register (ANER), address 06h
Bit Bit Name Default Description
15:5 RESERVED 0, RO RESERVED: Writes ignored, Read as 0.
4PDF 0, RO Parallel Detection Fault:
1 = A fault has been detected via the Parallel Detection function.
0 = A fault has not been detected.
3LP_NP_ABLE 0, RO Link Partner Next Page Able:
1 = Link Partner does support Next Page.
0 = Link Partner does not support Next Page.
2NP_ABLE 1, RO/P Next Page Able:
1 = Indicates local device is able to send additional “Next Pages”.
1PAGE_RX 0, RO/COR Link Code Word Page Received:
1 = Link Code Word has been received, cleared on a read.
0 = Link Code Word has not been received.
0LP_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-Negotia-
tion.
www.national.com 62
DP83849I
7.1.9 Auto-Negotiation Next Page Transmit Register (ANNPTR)
This register contains the next page information sent by this device to its Link Partner during Auto-Negotiation.
Table 28. Auto-Negotiation Next Page Transmit Register (ANNPTR), address 07h
Bit Bit Name Default Description
15 NP 0, RW Next Page Indication:
0 = No other Next Page Transfer desired.
1 = Another Next Page desired.
14 RESERVED 0, RO RESERVED: Writes ignored, read as 0.
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.
11 TOG_TX 0, RO Toggle:
1 = Value of toggle bit in previously transmitted Link Code Word
was 0.
0 = Value of toggle bit in previously transmitted Link Code Word
was 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 <000 0000 0001>,
RW
Code:
This field represents the code field of the next page transmission.
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 "Un-
formatted 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.
63 www.national.com
DP83849I
7.1.10 PHY Status Register (PHYSTS)
This register provides a single location within the register set for quick access to commonly accessed information.
Table 29. PHY Status Register (PHYSTS), address 10h
Bit Bit Name Default Description
15 RESERVED 0, RO RESERVED: Write ignored, read as 0.
14 MDIX MODE 0, RO MDIX mode as reported by the Auto-Negotiation logic:
This bit will be affected by the settings of the MDIX_EN and
FORCE_MDIX bits in the PHYCR register. When MDIX is enabled,
but not forced, this bit will update dynamically as the Auto-MDIX al-
gorithm swaps between MDI and MDIX configurations.
1 = MDI pairs swapped
(Receive on TPTD pair, Transmit on TPRD pair)
0 = MDI pairs normal
(Receive on TRD pair, Transmit on TPTD pair)
13 RECEIVE ERROR
LATCH
0, RO/LH Receive Error Latch:
This bit will be cleared upon a read of the RECR register.
1 = Receive error event has occurred since last read of RXERCNT
(address 15h, Page 0).
0 = No receive error event has occurred.
12 POLARITY STATUS 0, RO Polarity Status:
This bit is a duplication of bit 4 in the 10BTSCR register. This bit will
be cleared upon a read of the 10BTSCR register, but not upon a
read of the PHYSTS register.
1 = Inverted Polarity detected.
0 = Correct Polarity detected.
11 FALSE CARRIER
SENSE LATCH
0, RO/LH False Carrier Sense Latch:
This bit will be cleared upon a read of the FCSR register.
1 = False Carrier event has occurred since last read of FCSCR (ad-
dress 14h).
0 = No False Carrier event has occurred.
10 SIGNAL DETECT 0, RO/LL 100Base-TX qualified Signal Detect from PMA:
This is the SD that goes into the link monitor. It is the AND of raw
SD and descrambler lock, when address 16h, bit 8 (page 0) is set.
When this bit is cleared, it will be equivalent to the raw SD from the
PMD.
9DESCRAMBLER
LOCK
0, RO/LL 100Base-TX Descrambler Lock from PMD.
8PAGE RECEIVED 0, RO Link Code Word Page Received:
This is a duplicate of the Page Received bit in the ANER register,
but this bit will not be cleared upon a read of the PHYSTS register.
1 = A new Link Code Word Page has been received. Cleared on
read of the ANER (address 06h, bit 1).
0 = Link Code Word Page has not been received.
7MII INTERRUPT 0, RO MII Interrupt Pending:
1 = Indicates that an internal interrupt is pending. Interrupt source
can be determined by reading the MISR Register (12h). Reading
the MISR will clear the Interrupt.
0 = No interrupt pending.
www.national.com 64
DP83849I
6REMOTE FAULT 0, RO Remote Fault:
1 = Remote Fault condition detected (cleared on read of BMSR (ad-
dress 01h) register or by reset). Fault criteria: notification from Link
Partner of Remote Fault via Auto-Negotiation.
0 = No remote fault condition detected.
5JABBER DETECT 0, RO Jabber Detect: This bit only has meaning in 10 Mb/s mode
This bit is a duplicate of the Jabber Detect bit in the BMSR register,
except that it is not cleared upon a read of the PHYSTS register.
1 = Jabber condition detected.
0 = No Jabber.
4AUTO-NEG COM-
PLETE
0, RO Auto-Negotiation Complete:
1 = Auto-Negotiation complete.
0 = Auto-Negotiation not complete.
3LOOPBACK STA-
TUS
0, RO Loopback:
1 = Loopback enabled.
0 = Normal operation.
2DUPLEX STATUS 0, RO Duplex:
This bit indicates duplex status and is determined from Auto-Nego-
tiation or Forced Modes.
1 = Full duplex mode.
0 = Half duplex mode.
Note: This bit is only valid if Auto-Negotiation is enabled and com-
plete and there is a valid link or if Auto-Negotiation is disabled and
there is a valid link.
1SPEED STATUS 0, RO Speed10:
This bit indicates the status of the speed and is determined from
Auto-Negotiation or Forced Modes.
1 = 10 Mb/s mode.
0 = 100 Mb/s mode.
Note: This bit is only valid if Auto-Negotiation is enabled and com-
plete and there is a valid link or if Auto-Negotiation is disabled and
there is a valid link.
0LINK STATUS 0, RO Link Status:
This bit is a duplicate of the Link Status bit in the BMSR register,
except that it will not be cleared upon a read of the PHYSTS regis-
ter.
1 = Valid link established (for either 10 or 100 Mb/s operation)
0 = Link not established.
Table 29. PHY Status Register (PHYSTS), address 10h
Bit Bit Name Default Description
65 www.national.com
DP83849I
7.1.11 MII Interrupt Control Register (MICR)
This register implements the MII Interrupt PHY Specific Control register. Sources for interrupt generation include: Energy
Detect State Change, Link State Change, Speed Status Change, Duplex Status Change, Auto-Negotiation Complete or
any of the counters becoming half-full. The individual interrupt events must be enabled by setting bits in the MII Interrupt
Status and Event Control Register (MISR).
7.1.12 MII Interrupt Status and Misc. Control Register (MISR)
This register contains event status and enables for the interrupt function. If an event has occurred since the last read of
this register, the corresponding status bit will be set. If the corresponding enable bit in the register is set, an interrupt will
be generated if the event occurs. The MICR register controls must also be set to allow interrupts. The status indications
in this register will be set even if the interrupt is not enabled.
Table 30. MII Interrupt Control Register (MICR), address 11h
Bit Bit Name Default Description
15:3 RESERVED 0, RO RESERVED: Writes ignored, read as 0.
2TINT 0, RW Test Interrupt:
Forces the PHY to generate an interrupt to facilitate interrupt test-
ing. Interrupts will continue to be generated as long as this bit re-
mains set.
1 = Generate an interrupt
0 = Do not generate interrupt
1INTEN 0, RW Interrupt Enable:
Enable interrupt dependent on the event enables in the MISR reg-
ister.
1 = Enable event based interrupts
0 = Disable event based interrupts
0INT_OE 0, RW Interrupt Output Enable:
Enable interrupt events to signal via the PWRDOWN_INT pin by
configuring the PWRDOWN_INT pin as an output.
1 = PWRDOWN_INT is an Interrupt Output
0 = PWRDOWN_INT is a Power Down Input
Table 31. MII Interrupt Status and Misc. Control Register (MISR), address 12h
15 LQ_INT 0, RO/COR Link Quality interrupt:
1 = Link Quality interrupt is pending and is cleared by the current
read.
0 = No Link Quality interrupt pending.
14 ED_INT 0, RO/COR Energy Detect interrupt:
1 = Energy detect interrupt is pending and is cleared by the current
read.
0 = No energy detect interrupt pending.
13 LINK_INT 0, RO/COR Change of Link Status interrupt:
1 = Change of link status interrupt is pending and is cleared by the
current read.
0 = No change of link status interrupt pending.
12 SPD_INT 0, RO/COR Change of speed status interrupt:
1 = Speed status change interrupt is pending and is cleared by the
current read.
0 = No speed status change interrupt pending.
www.national.com 66
DP83849I
7.1.13 Page Select Register (PAGESEL)
This register is used to enable access to the Link Diagnostics Registers.
11 DUP_INT 0, RO/COR Change of duplex status interrupt:
1 = Duplex status change interrupt is pending and is cleared by
the current read.
0 = No duplex status change interrupt pending.
10 ANC_INT 0, RO/COR Auto-Negotiation Complete interrupt:
1 = Auto-negotiation complete interrupt is pending and is cleared
by the current read.
0 = No Auto-negotiation complete interrupt pending.
9FHF_INT 0, RO/COR False Carrier Counter half-full interrupt:
1 = False carrier counter half-full interrupt is pending and is
cleared by the current read.
0 = No false carrier counter half-full interrupt pending.
8RHF_INT 0, RO/COR Receive Error Counter half-full interrupt:
1 = Receive error counter half-full interrupt is pending and is
cleared by the current read.
0 = No receive error carrier counter half-full interrupt pending.
7LQ_INT_EN 0, RW Enable Interrupt on Link Quality Monitor event
6ED_INT_EN 0, RW Enable Interrupt on energy detect event
5LINK_INT_EN 0, RW Enable Interrupt on change of link status
4SPD_INT_EN 0, RW Enable Interrupt on change of speed status
3DUP_INT_EN 0, RW Enable Interrupt on change of duplex status
2ANC_INT_EN 0, RW Enable Interrupt on Auto-negotiation complete event
1FHF_INT_EN 0, RW Enable Interrupt on False Carrier Counter Register half-full event
0RHF_INT_EN 0, RW Enable Interrupt on Receive Error Counter Register half-full event
Table 32. Page Select Register (PAGESEL), address 13h
Bit Bit Name Default Description
15:2 RESERVED 0, RO RESERVED: Writes ignored, Read as 0
1:0 PAGE_SEL 0, RW Page_Sel Bit:
Selects between paged registers for address 14h to 1Fh.
0 = Extended Registers Page 0
1 = Test Mode Register Page 1
2 = Link Diagnostics Registers Page 2
Table 31. MII Interrupt Status and Misc. Control Register (MISR), address 12h
67 www.national.com
DP83849I
7.2 Extended Registers - Page 0
7.2.1 False Carrier Sense Counter Register (FCSCR)
This counter provides information required to implement the “False Carriers” attribute within the MAU managed object
class of Clause 30 of the IEEE 802.3u specification.
7.2.2 Receiver Error Counter Register (RECR)
This counter provides information required to implement the “Symbol Error During Carrier” attribute within the PHY man-
aged object class of Clause 30 of the IEEE 802.3u specification.
7.2.3 100 Mb/s PCS Configuration and Status Register (PCSR)
This register contains control and status information for the 100BASE Physical Coding Sublayer.
Table 33. False Carrier Sense Counter Register (FCSCR), address 14h
Bit Bit Name Default Description
15:8 RESERVED 0, RO RESERVED: Writes ignored, Read as 0
7:0 FCSCNT[7:0] 0, RO/COR False Carrier Event Counter:
This 8-bit counter increments on every false carrier event. This
counter sticks when it reaches its max count (FFh).
Table 34. Receiver Error Counter Register (RECR), address 15h
Bit Bit Name Default Description
15:8 RESERVED 0, RO RESERVED: Writes ignored, Read as 0
7:0 RXERCNT[7:0] 0, RO/COR RX_ER Counter:
When a valid carrier is present and there is at least one occurrence
of an invalid data symbol, this 8-bit counter increments for each re-
ceive error detected. This event can increment only once per valid
carrier event. If a collision is present, the attribute will not incre-
ment. The counter sticks when it reaches its max count.
Table 35. 100 Mb/s PCS Configuration and Status Register (PCSR), address 16h
Bit Bit Name Default Description
15:12 RESERVED <00>, RO RESERVED: Writes ignored, Read as 0.
11 FREE_CLK 0, RW Receive Clock:
1 = RX_CLK is free-running
0 = RX_CLK phase adjusted based on alignment
10 TQ_EN 0, RW 100Mbs True Quiet Mode Enable:
1 = Transmit True Quiet Mode.
0 = Normal Transmit Mode.
9SD FORCE PMA 0,RW Signal Detect Force PMA:
1 = Forces Signal Detection in PMA.
0 = Normal SD operation.
www.national.com 68
DP83849I
8SD_OPTION 1, RW Signal Detect Option:
1 = Default operation. Link will be asserted following detection of
valid signal level and Descrambler Lock. Link will be maintained as
long as signal level is valid. A loss of Descrambler Lock will not
cause Link Status to drop.
0 = Modified signal detect algorithm. Link will be asserted following
detection of valid signal level and Descrambler Lock. Link will be
maintained as long as signal level is valid and Descrambler re-
mains locked.
7DESC_TIME 0, RW Descrambler Timeout:
Increase the descrambler timeout. When set this should allow the
device to receive larger packets (>9k bytes) without loss of syn-
chronization.
1 = 2ms
0 = 722us (per ANSI X3.263: 1995 (TP-PMD) 7.2.3.3e)
6RESERVED 0RESERVED:
Must be zero.
5FORCE_100_OK 0, RW Force 100Mb/s Good Link:
1 = Forces 100Mb/s Good Link.
0 = Normal 100Mb/s operation.
4:3 RESERVED 0RESERVED:
Must be zero.
2NRZI_BYPASS 0, RW NRZI Bypass Enable:
1 = NRZI Bypass Enabled.
0 = NRZI Bypass Disabled.
1:0 RESERVED 0RESERVED:
Must be zero.
Table 35. 100 Mb/s PCS Configuration and Status Register (PCSR), address 16h (Continued)
Bit Bit Name Default Description
69 www.national.com
DP83849I
7.2.4 RMII and Bypass Register (RBR)
This register configures the RMII/MII Interface Mode of operation. This register controls selecting MII, RMII, or Single
Clock MII mode for Receive or Transmit. In addition, several additional bits are included to allow datapath selection for
Transmit and Receive in multiport applications.
Table 36. RMII and Bypass Register (RBR), addresses 17h
Bit Bit Name Default Description
15 SIM_WRITE 0, RW Simultaneous Write:
Setting this bit in port A register space enables simultaneous write to Phy
registers in both ports. Subsequent writes to port A registers will write to
registers in both ports A and B.
1 = Simultaneous writes to both ports
0 = Per-port write
14 RESERVED 0, RO RESERVED: Writes ignored, Read as 0
13 DIS_TX_OPT 0, RW Disable RMII TX Latency Optimization:
Normally the RMII Transmitter will minimize the transmit latency by
realigning the transmit clock with the Reference clock phase at the
start of a packet transmission. Setting this bit will disable Phase re-
alignment and ensure that IDLE bits will always be sent in multiples
of the symbol size. This will result in a larger uncertainty in RMII
transmit latency.
12:11 RX_PORT 00, RW Receive Port:
See Section 3.5 for more information on Flexible Port Switching.
10:9 TX_SOURCE Strap, RW Transmit Source:
See Section 3.5 for more information on Flexible Port Switching.
00 = Not strapped for Extender Mode
10 = Strapped for Extender Mode
8PMD_LOOP 0, RW PMD Loopback:
0= Normal Operation
1= Remote (PMD) Loopback
Setting this bit will cause the device to Loopback data received
from the Physical Layer. The loopback is done prior to the MII or
RMII interface. Data received at the internal MII or RMII interface
will be applied to the transmitter. This mode should only be used if
RMII mode or Single Clock MII mode is enabled.
7SCMII_RX Strap, RW Single Clock RX MII Mode:
0= Standard MII mode
1= Single Clock RX MII Mode
Setting this bit will cause the device to generate receive data
(RX_DV, RX_ER, RXD[3:0]) synchronous to the X1 Reference
clock. RX_CLK is not used in this mode. This mode uses the RMII
elasticity buffer to tolerate variations in clock frequencies. This bit
cannot be set if RMII_MODE is set to a 1. This bit is strapped to 1
if EXTENDER_EN is 1 and RMII Mode is not strapped at hard re-
set.
6SCMII_TX Strap, RW Single Clock TX MII Mode:
0= Standard MII mode
1= Single Clock TX MII Mode
Setting this bit will cause the device to sample transmit data
(TX_EN, TXD[3:0]) synchronous to the X1 Reference clock.
TX_CLK is not used in this mode. This bit cannot be set if
RMII_MODE is set to a 1. This bit is strapped to 1 if
EXTENDER_EN is 1 and RMII Mode is not strapped at hard reset.
www.national.com 70
DP83849I
5RMII_MODE Strap, RW Reduced MII Mode:
0 = Standard MII Mode
1 = Reduced MII Mode
4RMII_REV1_0 0, RW Reduced MII Revision 1.0:
0 = (RMII revision 1.2) CRS_DV will toggle at the end of a packet
to indicate deassertion of CRS.
1 = (RMII revision 1.0) CRS_DV will remain asserted until final data
is transferred. CRS_DV will not toggle at the end of a packet.
3RX_OVF_STS 0, RO/COR RX FIFO Over Flow Status:
0 = Normal
1 = Overflow detected
2RX_UNF_STS 0, RO/COR RX FIFO Under Flow Status:
0 = Normal
1 = Underflow detected
1:0 ELAST_BUF[1:0] 01, RW Receive Elasticity Buffer:
This field controls the Receive Elasticity Buffer which allows for fre-
quency variation tolerance between the 50MHz RMII clock and the
recovered data. See Section 3.2 for more information on Elasticity
Buffer settings in RMII mode. See Section 3.4 for more information
on Elasticity Buffer settings in SCMII mode.
Table 36. RMII and Bypass Register (RBR), addresses 17h (Continued)
Bit Bit Name Default Description
71 www.national.com
DP83849I
7.2.5 LED Direct Control Register (LEDCR)
This register provides the ability to directly control any or all LED outputs. It does not provide read access to LEDs. In
addition, it provides control for the Activity source and blinking LED frequency.
Table 37. LED Direct Control Register (LEDCR), address 18h
Bit Bit Name Default Description
15:9 RESERVED 0, RO RESERVED: Writes ignored, read as 0.
8LEDACT_RX 0, RW 1 = Activity is only indicated for Receive traffic
0 = Activity is indicated for Transmit or Receive traffic
7:6 BLINK_FREQ 00, RW LED Blink Frequency
These bits control the blink frequency of the LED_LINK output
when blinking on activity is enabled.
0 = 6Hz
1 = 12Hz
2 = 24Hz
3 = 48Hz
5DRV_SPDLED 0, RW 1 = Drive value of SPDLED bit onto LED_SPEED output
0 = Normal operation
4DRV_LNKLED 0, RW 1 = Drive value of LNKLED bit onto LED_LINK output
0 = Normal operation
3DRV_ACTLED 0, RW 1 = Drive value of ACTLED bit onto LED_ACT/LED_COL output
0 = Normal operation
2SPDLED 0, RW Value to force on LED_SPEED output
1LNKLED 0, RW Value to force on LED_LINK output
0ACTLED 0, RW Value to force on LED_ACT/LED_COL output
www.national.com 72
DP83849I
7.2.6 PHY Control Register (PHYCR)
This register provides control for Phy functions such as MDIX, BIST, LED configuration, and Phy address. It also pro-
vides Pause Negotiation status.
Table 38. PHY Control Register (PHYCR), address 19h
Bit Bit Name Default Description
15 MDIX_EN Strap, RW Auto-MDIX Enable:
1 = Enable Auto-neg Auto-MDIX capability.
0 = Disable Auto-neg Auto-MDIX capability.
The Auto-MDIX algorithm requires that the Auto-Negotiation En-
able bit in the BMCR register to be set. If Auto-Negotiation is not
enabled, Auto-MDIX should be disabled as well.
14 FORCE_MDIX 0, RW Force MDIX:
1 = Force MDI pairs to cross.
(Receive on TPTD pair, Transmit on TPRD pair)
0 = Normal operation.
13 PAUSE_RX 0, RO Pause Receive Negotiated:
Indicates that pause receive should be enabled in the MAC. Based
on ANAR[11:10] and ANLPAR[11:10] settings.
This function shall be enabled according to IEEE 802.3 Annex 28B
Table 28B-3, “Pause Resolution”, only if the Auto-Negotiated High-
est Common Denominator is a full duplex technology.
12 PAUSE_TX 0, RO Pause Transmit Negotiated:
Indicates that pause transmit should be enabled in the MAC. Based
on ANAR[11:10] and ANLPAR[11:10] settings.
This function shall be enabled according to IEEE 802.3 Annex 28B
Table 28B-3, “Pause Resolution”, only if the Auto-Negotiated High-
est Common Denominator is a full duplex technology.
11 BIST_FE 0, RW/SC BIST Force Error:
1 = Force BIST Error.
0 = Normal operation.
This bit forces a single error, and is self clearing.
10 PSR_15 0, RW BIST Sequence select:
1 = PSR15 selected.
0 = PSR9 selected.
9BIST_STATUS 0, LL/RO BIST Test Status:
1 = BIST pass.
0 = BIST fail. Latched, cleared when BIST is stopped.
For a count number of BIST errors, see the BIST Error Count in the
CDCTRL1 register.
8BIST_START 0, RW BIST Start:
1 = BIST start.
0 = BIST stop.
7 BP_STRETCH 0, RW Bypass LED Stretching:
This will bypass the LED stretching and the LEDs will reflect the in-
ternal value.
1 = Bypass LED stretching.
0 = Normal operation.
73 www.national.com
DP83849I
7.2.7 10 Base-T Status/Control Register (10BTSCR)
This register is used for control and status for 10BASE-T device operation.
6
5
LED_CNFG[1]
LED_CNFG[0]
0, RW
Strap, RW
LED Configuration
In Mode 1, LEDs are configured as follows:
LED_LINK = ON for Good Link, OFF for No Link
LED_SPEED = ON in 100 Mb/s, OFF in 10 Mb/s
LED_ACT/LED_COL = ON for Activity, OFF for No Activity
In Mode 2, LEDs are configured as follows:
LED_LINK = ON for good Link, BLINK for Activity
LED_SPEED = ON in 100 Mb/s, OFF in 10 Mb/s
LED_ACT/LED_COL = ON for Collision, OFF for No Collision
Full Duplex, OFF for Half Duplex
In Mode 3, LEDs are configured as follows:
LED_LINK = ON for Good Link, BLINK for Activity
LED_SPEED = ON in 100 Mb/s, OFF in 10 Mb/s
LED_ACT/LED_COL = ON for Full Duplex, OFF for Half Duplex
4:0 PHYADDR[4:0] Strap, RW PHY Address: PHY address for port.
Table 39. 10Base-T Status/Control Register (10BTSCR), address 1Ah
Bit Bit Name Default Description
15 10BT_SERIAL Strap, RW 10Base-T Serial Mode (SNI)
1 = Enables 10Base-T Serial Mode
0 = Normal Operation
Places 10 Mb/s transmit and receive functions in Serial Network
Interface (SNI) Mode of operation. Has no effect on 100 Mb/s
operation.
14:12 RESERVED 0, RW RESERVED:
Must be zero.
11:9 SQUELCH 100, RW Squelch Configuration:
Used to set the Squelch ‘ON’ threshold for the receiver.
Default Squelch ON is 330mV peak.
Table 38. PHY Control Register (PHYCR), address 19h (Continued)
Bit Bit Name Default Description
LED_CNFG[1] LED_ CNFG[0] Mode Description
Don’t care 1 Mode 1
0 0 Mode 2
1 0 Mode 3
www.national.com 74
DP83849I
8LOOPBACK_10_DIS 0, RW 10Base-T Loopback Disable:
In half-duplex mode, default 10BASE-T operation loops Transmit
data to the Receive data in addition to transmitting the data on the
physical medium. This is for consistency with earlier 10BASE2 and
10BASE5 implementations which used a shared medium. Setting
this bit disables the loopback function.
This bit does not affect loopback due to setting BMCR[14].
7LP_DIS 0, RW Normal Link Pulse Disable:
1 = Transmission of NLPs is disabled.
0 = Transmission of NLPs is enabled.
6FORCE_LINK_10 0, RW Force 10Mb Good Link:
1 = Forced Good 10Mb Link.
0 = Normal Link Status.
5RESERVED 0, RW RESERVED:
Must be zero.
4POLARITY RO/LH 10Mb Polarity Status:
This bit is a duplication of bit 12 in the PHYSTS register. Both bits
will be cleared upon a read of 10BTSCR register, but not upon a
read of the PHYSTS register.
1 = Inverted Polarity detected.
0 = Correct Polarity detected.
3RESERVED 0, RW RESERVED:
Must be zero.
2RESERVED 1, RW RESERVED:
Must be set to one.
1HEARTBEAT_DIS 0, RW Heartbeat Disable: This bit only has influence in half-duplex 10Mb
mode.
1 = Heartbeat function disabled.
0 = Heartbeat function enabled.
When the device is operating at 100Mb or configured for full
duplex operation, this bit will be ignored - the heartbeat func-
tion is disabled.
0JABBER_DIS 0, RW Jabber Disable:
Applicable only in 10BASE-T.
1 = Jabber function disabled.
0 = Jabber function enabled.
Table 39. 10Base-T Status/Control Register (10BTSCR), address 1Ah (Continued)
Bit Bit Name Default Description
75 www.national.com
DP83849I
7.2.8 CD Test and BIST Extensions Register (CDCTRL1)
This register controls test modes for the 10BASE-T Common Driver. In addition it contains extended control
and status for the packet BIST function.
7.2.9 Phy Control Register 2 (PHYCR2)
This register provides additional general control.
Table 40. CD Test and BIST Extensions Register (CDCTRL1), address 1Bh
Bit Bit Name Default Description
15:8 BIST_ERROR_COUNT 0, RO BIST ERROR Counter:
Counts number of errored data nibbles during Packet BIST. This
value will reset when Packet BIST is restarted. The counter sticks
when it reaches its max count.
7:6 RESERVED 0, RW RESERVED:
Must be zero.
5 BIST_CONT_MODE 0, RW Packet BIST Continuous Mode:
Allows continuous pseudo random data transmission without any
break in transmission. This can be used for transmit VOD testing.
This is used in conjunction with the BIST controls in the PHYCR
Register (19h). For 10Mb operation, jabber function must be dis-
abled, bit 0 of the 10BTSCR (1Ah), JABBER_DIS = 1.
4CDPATTEN_10 0, RW CD Pattern Enable for 10Mb:
1 = Enabled.
0 = Disabled.
3RESERVED 0, RW RESERVED:
Must be zero.
210MEG_PATT_GAP 0, RW Defines gap between data or NLP test sequences:
1 = 15 µs.
0 = 10 µs.
1:0 CDPATTSEL[1:0] 00, RW CD Pattern Select[1:0]:
If CDPATTEN_10 = 1:
00 = Data, EOP0 sequence
01 = Data, EOP1 sequence
10 = NLPs
11 = Constant Manchester 1s (10MHz sine wave) for harmonic dis-
tortion testing.
Table 41. Phy Control Register 2 (PHYCR2), address 1Ch
Bit Bit Name Default Description
15:10 RESERVED 0, RO RESERVED: Writes ignored, read as 0.
9SOFT_RESET 0, RW/SC Soft Reset:
Resets the entire device minus the registers - all configuration is
preserved.
1= Reset, self-clearing.
8:0 RESERVED 0, RO RESERVED: Writes ignored, read as 0.
www.national.com 76
DP83849I
7.2.10 Energy Detect Control (EDCR)
This register provides control and status for the Energy Detect function.
Table 42. Energy Detect Control (EDCR), address 1Dh
Bit Bit Name Default Description
15 ED_EN Strap, RW Energy Detect Enable:
Allow Energy Detect Mode.
When Energy Detect is enabled and Auto-Negotiation is disabled
via the BMCR register, Auto-MDIX should be disabled via the PHY-
CR register.
14 ED_AUTO_UP 1, RW Energy Detect Automatic Power Up:
Automatically begin power up sequence when Energy Detect Data
Threshold value (EDCR[3:0]) is reached. Alternatively, device
could be powered up manually using the ED_MAN bit (ECDR[12]).
13 ED_AUTO_DOWN 1, RW Energy Detect Automatic Power Down:
Automatically begin power down sequence when no energy is de-
tected. Alternatively, device could be powered down using the
ED_MAN bit (EDCR[12]).
12 ED_MAN 0, RW/SC Energy Detect Manual Power Up/Down:
Begin power up/down sequence when this bit is asserted. When
set, the Energy Detect algorithm will initiate a change of Energy De-
tect state regardless of threshold (error or data) and timer values.
In managed applications, this bit can be set after clearing the Ener-
gy Detect interrupt to control the timing of changing the power
state.
11 ED_BURST_DIS 0, RW Energy Detect Burst Disable:
Disable bursting of energy detect data pulses. By default, Energy
Detect (ED) transmits a burst of 4 ED data pulses each time the CD
is powered up. When bursting is disabled, only a single ED data
pulse will be send each time the CD is powered up.
10 ED_PWR_STATE 0, RO Energy Detect Power State:
Indicates current Energy Detect Power state. When set, Energy
Detect is in the powered up state. When cleared, Energy Detect is
in the powered down state. This bit is invalid when Energy Detect
is not enabled.
9ED_ERR_MET 0, RO/COR Energy Detect Error Threshold Met:
No action is automatically taken upon receipt of error events. This
bit is informational only and would be cleared on a read.
8ED_DATA_MET 0, RO/COR Energy Detect Data Threshold Met:
The number of data events that occurred met or surpassed the En-
ergy Detect Data Threshold. This bit is cleared on a read.
7:4 ED_ERR_COUNT 0001, RW Energy Detect Error Threshold:
Threshold to determine the number of energy detect error events
that should cause the device to take action. Intended to allow aver-
aging of noise that may be on the line. Counter will reset after ap-
proximately 2 seconds without any energy detect data events.
3:0 ED_DATA_COUNT 0001, RW Energy Detect Data Threshold:
Threshold to determine the number of energy detect events that
should cause the device to take actions. Intended to allow averag-
ing of noise that may be on the line. Counter will reset after approx-
imately 2 seconds without any energy detect data events.
77 www.national.com
DP83849I
7.3 Link Diagnostics Registers - Page 2
Page 2 Link Diagnostics Registers are accessible by setting bits [1:0] = 10 of PAGESEL (13h).
7.3.1 100Mb Length Detect Register (LEN100_DET), Page 2, address 14h
This register contains linked cable length estimation in 100Mb operation. The cable length is an estimation of the effec-
tive cable length based on the characteristics of the recovered signal. The cable length is valid only during 100Mb oper-
ation with a valid Link status indication.
7.3.2 100Mb Frequency Offset Indication Register (FREQ100), Page 2, address 15h
This register returns an indication of clock frequency offset relative to the link partner. Two values can be read, the long
term Frequency Offset, or a short term Frequency Control value. The Frequency Control value includes short term
phase correction. The variance between the Frequency Control value and the Frequency Offset can be used as an indi-
cation of the amount of jitter in the system.
Table 43. 100Mb Length Detect Register (LEN100_DET), address 14h
Bit Bit Name Default Description
15:8 RESERVED 0, RO RESERVED: Writes ignored, read as 0.
7:0 CABLE_LEN 0, RO Cable Length Estimate:
Indicates an estimate of effective cable length in meters. A value
of FF indicates cable length cannot be determined.
Table 44. 100Mb Frequency Offset Indication Register (FREQ100), address 15h
Bit Bit Name Default Description
15 SAMPLE_FREQ 0, RW Sample Frequency Offset:
If Sel_FC is set to a 0, then setting this bit to a 1 will poll the DSP
for the long-term Frequency Offset value. The value will be avail-
able in the Freq_Offset bits of this register.
If Sel_FC is set to a 1, then setting this bit to a 1 will poll the DSP
for the current Frequency Control value. The value will be available
in the Freq_Offset bits of this register.
This register bit will always read back as 0.
14:9 RESERVED 0, RO RESERVED: Writes ignored, read as 0.
8SEL_FC 0, RW Select Frequency Control:
Setting this bit to a 1 will select the current Frequency Control value
instead of the Frequency Offset. This value contains Frequency
Offset plus the short term phase correction and can be used to in-
dicate amount of jitter in the system. The value will be available in
the Freq_Offset bits of this register.
7:0 FREQ_OFFSET 0, RO Frequency Offset:
Frequency offset value loaded from the DSP following assertion of
the Sample_Freq control bit. The Frequency Offset or Frequency
Control value is a twos-complement signed value in units of ap-
proximately 5.1562ppm. The range is as follows:
0x7F = +655ppm
0x00 = 0ppm
0x80 = -660ppm
www.national.com 78
DP83849I
7.3.3 TDR Control Register (TDR_CTRL), Page 2, address 16h
This register contains control for the Time Domain Reflectometry (TDR) cable diagnostics. The TDR cable diagnostics
sends pulses down the cable and captures reflection data to be used to estimate cable length and detect certain cabling
faults.
Table 45. TDR Control Register (TDR_CTRL), address 16h
Bit Bit Name Default Description
15 TDR_ENABLE 0, RW TDR Enable:
Enable TDR mode. This forces powerup state to correct operating
condition for sending and receiving TDR pulses.
14 TDR_100Mb 0, RW TDR 100Mb:
Sets TDR controller to use the 100Mb Transmitter. This allows for
sending pulse widths in multiples of 8ns. Pulses in 100Mb mode
will alternate between positive pulses and negative pulses.
Default operation uses the 10Mb Link Pulse generator. Pulses may
include just the 50ns preemphasis portion of the pulse or the 100ns
full link pulse (as controlled by setting TDR Width).
13 TX_CHANNEL 0, RW Transmit Channel Select:
Select transmit channel for sending pulses. Pulse can be sent on
the Transmit or Receive pair.
0 : Transmit channel
1 : Receive channel
12 RX_CHANNEL 0, RW Receive Channel Select:
Select receive channel for detecting pulses. Pulse can be moni-
tored on the Transmit or Receive pair.
0 : Transmit channel
1 : Receive channel
11 SEND_TDR 0, RW/SC Send TDR Pulse:
Setting this bit will send a TDR pulse and enable the monitor circuit
to capture the response. This bit will automatically clear when the
capture is complete.
10:8 TDR_WIDTH 0, RW TDR Pulse Width:
Pulse width in clocks for the transmitted pulse. In 100Mb mode,
pulses are in 8ns increments. In 10Mb mode, pulses are in 50ns
increments, but only 50ns or 100ns pulses can be sent. Sending a
pulse of 0 width will not transmit a pulse, but allows for baseline
testing.
7TDR_MIN_MODE 0, RW Min/Max Mode control:
This bit controls direction of the pulse to be detected. Default looks
for a positive peak. Threshold and peak values will be interpreted
appropriately based on this bit.
0 : Max Mode, detect positive peak
1 : Min Mode, detect negative peak
6RESERVED 0, RO RESERVED: Writes ignored, read as 0.
5:0 RX_THRESHOLD <10_0000>, RW RX Threshold:
This value provides a threshold for measurement to the start of a
peak. If Min Mode is set to 0, data must be greater than this value
to trigger a capture. If Min Mode is 1, data must be less than this
value to trigger a capture. Data ranges from 0x00 to 0x3F, with
0x20 as the midpoint. Positive data is greater than 0x20, negative
data is less than 0x20.
79 www.national.com
DP83849I
7.3.4 TDR Window Register (TDR_WIN), Page 2, address 17h
This register contains sample window control for the Time Domain Reflectometry (TDR) cable diagnostics. The two val-
ues contained in this register specify the beginning and end times for the window to monitor the response to the transmit-
ted pulse. Time values are in 8ns increments. This provides a method to search for multiple responses and also to
screen out the initial outgoing pulse.
7.3.5 TDR Peak Register (TDR_PEAK), Page 2, address 18h
This register contains the results of the TDR Peak Detection. Results are valid if the TDR_CTRL[11] is clear following
sending the TDR pulse.
7.3.6 TDR Threshold Register (TDR_THR), Page 2, address 19h
This register contains the results of the TDR Threshold Detection. Results are valid if the TDR_CTRL[11] is clear follow-
ing sending the TDR pulse.
Table 46. TDR Window Register (TDR_WIN), address 17h
Bit Bit Name Default Description
15:8 TDR_START 0, RW TDR Start Window:
Specifies start time for monitoring TDR response.
7:0 TDR_STOP 0xFF, RW TDR Stop Window:
Specifies stop time for monitoring TDR response. The Stop Win-
dow should be set to a value greater than or equal to the Start Win-
dow.
Table 47. TDR Peak Register (TDR_PEAK), address 18h
Bit Bit Name Default Description
15:14 RESERVED 0, RO RESERVED: Writes ignored, read as 0.
13:8 TDR_PEAK 0, RO TDR Peak Value:
This register contains the peak value measured during the TDR
sample window. If Min Mode control (TDR_CTRL[7]) is 0, this con-
tains the maximum detected value. If Min Mode control is 1, this
contains the minimum detected value.
7:0 TDR_PEAK_TIME 0, RO TDR Peak Time:
Specifies the time for the first occurrence of the peak value.
Table 48. TDR Threshold Register (TDR_THR), address 19h
Bit Bit Name Default Description
15:9 RESERVED 0, RO RESERVED: Writes ignored, read as 0.
8TDR_THR_MET 0, RO TDR Threshold Met:
This bit indicates the TDR threshold was met during the sample
window. A value of 0 indicates the threshold was not met.
7:0 TDR_THR_TIME 0, RO TDR Threshold Time:
Specifies the time for the first data that met the TDR threshold.
This field is only valid if the threshold was met.
www.national.com 80
DP83849I
7.3.7 Variance Control Register (VAR_CTRL), Page 2, address 1Ah
The Variance Control and Data Registers provide control and status for the Cable Signal Quality Estimation function.
The Cable Signal Quality Estimation allows a simple method of determining an approximate Signal-to-Noise Ratio for the
100Mb receiver. This register contains the programmable controls and status bits for the variance computation, which
can be used to make a simple Signal-to-Noise Ratio estimation.
7.3.8 Variance Data Register (VAR_DATA), Page 2, address 1Bh
This register contains the 32-bit Variance Sum. The contents of the data are valid only when VAR_RDY is asserted in the
VAR_CTRL register. Upon detection of VAR_RDY asserted, software should set the VAR_FREEZE bit in the VAR_CTRL
register to prevent loading of a new value into the VAR_DATA register. Since the Variance Data value is 32-bits, two
reads of this register are required to get the full value.
Table 49. Variance Control Register (VAR_CTRL), address 1Ah
Bit Bit Name Default Description
15 VAR_RDY 0, RO Variance Data Ready Status:
Indicates new data is available in the Variance data register. This
bit will be automatically cleared after two consecutive reads ot
VAR_DATA.
14:4 RESERVED 0, RO RESERVED: Writes ignored, read as 0.
3VAR_FREEZE 0, RW Freeze Variance Registers:
Freeze VAR_DATA register.
This bit is ensures that VAR_DATA register is frozen for software
reads. This bit is automatically cleared after two consecutive reads
of VAR_DATA.
2:1 VAR_TIMER 0, RW Variance Computation Timer (in ms):
Selects the Variance computation timer period. After a new value
is written, computation is automatically restarted. New variance
register values are loaded after the timer elapses.
Var_Timer = 0 => 2 ms timer (default)
Var_Timer = 1 => 4 ms timer
Var_Timer = 2 => 6 ms timer
Var_Timer = 3 => 8 ms timer
Time units are actually 217 cycles of an 8ns clock, or 1.048576ms.
0VAR_ENABLE 0, RW Variance Enable:
Enable Variance computation. Off by default.
Table 50. Variance Data Register (VAR_DATA), address 1Bh
Bit Bit Name Default Description
15:0 VAR_DATA 0, RO Variance Data:
Two reads are required to return the full 32-bit Variance Sum value.
Following setting the VAR_FREEZE control, the first read of this
register will return the low 16 bits of the Variance data. A second
read will return the high 16 bits of Variance data.
81 www.national.com
DP83849I
7.3.9 Link Quality Monitor Register (LQMR), Page 2, address 1Dh
This register contains the controls for the Link Quality Monitor function. The Link Quality Monitor provides a mechanism
for programming a set of thresholds for DSP parameters. If the thresholds are violated, an interrupt will be asserted if
enabled in the MISR. Monitor control and status are available in this register, while the LQDR register controls read/write
access to threshold values and current parameter values. Reading of LQMR register clears warning bits and re-arms the
interrupt generation. In addition, this register provides a mechanims for allowing automatic reset of the 100Mb link based
on the Link Quality Monitor status.
Table 51. Link Quality Monitor Register (LQMR), address 1Dh
Bit Bit Name Default Description
15 LQM_ENABLE 0, RW Link Quality Monitor Enable:
Enables the Link Quality Monitor. The enable is qualified by having
a valid 100Mb link. In addition, the individual thresholds can be dis-
abled by setting to the max or min values.
14:10 RESERVED 0, RO RESERVED: Writes ignored, read as 0.
9FC_HI_WARN 0, RO/COR Frequency Control High Warning:
This bit indicates the Frequency Control High Threshold was ex-
ceeded. This register bit will be cleared on read.
8FC_LO_WARN 0, RO/COR Frequency Control Low Warning:
This bit indicates the Frequency Control Low Threshold was ex-
ceeded. This register bit will be cleared on read.
7FREQ_HI_WARN 0, RO/COR Frequency Offset High Warning:
This bit indicates the Frequency Offset High Threshold was ex-
ceeded. This register bit will be cleared on read.
6FREQ_LO_WARN 0, RO/COR Frequency Offset Low Warning:
This bit indicates the Frequency Offset Low Threshold was exceed-
ed. This register bit will be cleared on read.
5DBLW_HI_WARN 0, RO/COR DBLW High Warning:
This bit indicates the DBLW High Threshold was exceeded. This
register bit will be cleared on read.
4DBLW_LO_WARN 0, RO/COR DBLW Low Warning:
This bit indicates the DBLW Low Threshold was exceeded. This
register bit will be cleared on read.
3DAGC_HI_WARN 0, RO/COR DAGC High Warning:
This bit indicates the DAGC High Threshold was exceeded. This
register bit will be cleared on read.
2DAGC_LO_WARN 0, RO/COR DAGC Low Warning:
This bit indicates the DAGC Low Threshold was exceeded. This
register bit will be cleared on read.
1C1_HI_WARN 0, RO/COR C1 High Warning:
This bit indicates the DEQ C1 High Threshold was exceeded. This
register bit will be cleared on read.
0C1_LO_WARN 0, RO/COR C1 Low Warning:
This bit indicates the DEQ C1 Low Threshold was exceeded. This
register bit will be cleared on read.
www.national.com 82
DP83849I
7.3.10 Link Quality Data Register (LQDR), Page 2
This register provides read/write control of thresholds for the 100Mb Link Quality Monitor function. The register also pro-
vides a mechanism for reading current adapted parameter values. Threshold values may not be written if the device is
powered-down.
Table 52. Link Quality Data Register (LQDR), address 1Eh
Bit Bit Name Default Description
15:14 RESERVED 0, RO RESERVED: Writes ignored, read as 0.
13 SAMPLE_PARAM 0, RW Sample DSP Parameter:
Setting this bit to a 1 enables reading of current parameter values
and initiates sampling of the parameter value. The parameter to be
read is selected by the LQ_PARAM_SEL bits.
12 WRITE_LQ_THR 0, RW Write Link Quality Threshold:
Setting this bit will cause a write to the Threshold register selected
by LQ_PARAM_SEL and LQ_THR_SEL. The data written is con-
tained in LQ_THR_DATA. This bit will always read back as 0.
11:9 LQ_PARAM_SEL 0, RW Link Quality Parameter Select:
This 3-bit field selects the Link Quality Parameter. This field is used
for sampling current parameter values as well as for reads/writes to
Threshold values. The following encodings are available:
000: DEQ_C1
001: DAGC
010: DBLW
011: Frequency Offset
100: Frequency Control
8LQ_THR_SEL 0, RW Link Quality Threshold Select:
This bit selects the Link Quality Threshold to be read or written. A
0 selects the Low threshold, while a 1 selects the high threshold.
When combined with the LQ_PARAM_SEL field, the following en-
codings are available {LQ_PARAM_SEL, LQ_THR_SEL}:
000,0: DEQ_C1 Low
000,1: DEQ_C1 High
001,0: DAGC Low
001,1: DAGC High
010,0: DBLW Low
010,1: DBLW High
011,0: Frequency Offset Low
011,1: Frequency Offset High
100,0: Frequency Control Low
100,1: Frequency Control High
7:0 LQ_THR_DATA 0, RW Link Quality Threshold Data:
The operation of this field is dependent on the value of the
Sample_Param bit.
If Sample_Param = 0:
On a write, this value contains the data to be written to the selected
Link Quality Threshold register.
On a read, this value contains the current data in the selected Link
Quality Threshold register.
If Sample_Param = 1:
On a read, this value contains the sampled parameter value. This
value will remain unchanged until a new read sequence is started.
83 www.national.com
DP83849I
8.0 Electrical Specifications
Note: All parameters are guaranteed by test, statistical analysis or design.
Absolute Maximum Ratings Recommended Operating Conditions
Absolute maximum ratings are those values beyond which
the safety of the device cannot be guaranteed. They are
not meant to imply that the device should be operated at
these limits.
8.1 DC Specs
Supply Voltage (VCC)-0.5 V to 4.2 V
DC Input Voltage (VIN)-0.5V to VCC + 0.5V
DC Output Voltage (VOUT)-0.5V to VCC + 0.5V
Storage Temperature (TSTG)-65oC to 150°C
Lead Temp. (TL)
(Soldering, 10 sec.)
260 °C
ESD Rating
(RZAP = 1.5k, CZAP = 100 pF)
4.0 kV
Supply voltage (VCC)3.3 Volts + .3V
Industrial - Ambient Temperature (TA)-40 to 85 °C
Power Dissipation (PD)594 mW
Thermal Characteristic Max Units
Maximum Case Temperature @ 1.0 W 108 °C
Theta Junction to Case (Tjc) @ 1.0 W 17.3 °C / W
Theta Junction to Ambient (Tja) degrees Celsius/Watt - No Airflow @ 1.0 W 53 °C / W
Symbol Pin Types Parameter Conditions Min Typ Max Units
VIH I
I/O
Input High Voltage Nominal VCC 2.0 V
VIL I
I/O
Input Low Voltage 0.8 V
IIH I
I/O
Input High Current VIN = VCC 10 µA
IIL I
I/O
Input Low Current VIN = GND 10 µA
VOL O,
I/O
Output Low
Voltage
IOL = 4 mA 0.4 V
VOH O,
I/O
Output High
Voltage
IOH = -4 mA Vcc - 0.5 V
IOZ I/O,
O
TRI-STATE
Leakage
VOUT = VCC + 10 µA
VTPTD_100 PMD Output
Pair
100M Transmit
Voltage
0.95 11.05 V
VTPTDsym PMD Output
Pair
100M Transmit
Voltage Symmetry
+ 2 %
VTPTD_10 PMD Output
Pair
10M Transmit
Voltage
2.2 2.5 2.8 V
CIN1 ICMOS Input
Capacitance
8pF
COUT1 OCMOS Output
Capacitance
8pF
www.national.com 84
DP83849I
SDTHon PMD Input
Pair
100BASE-TX
Signal detect turn-
on threshold
1000 mV diff pk-pk
SDTHoff PMD Input
Pair
100BASE-TX
Signal detect turn-
off threshold
200 mV diff pk-pk
VTH1 PMD Input
Pair
10BASE-T Re-
ceive Threshold
585 mV
Idd100 Supply 100BASE-TX
(Full Duplex)
180 mA
Idd10 Supply 10BASE-T
(Full Duplex)
180 mA
Idd Supply Power Down
Mode
CLK2MAC disabled 9.5 mA
Symbol Pin Types Parameter Conditions Min Typ Max Units
85 www.national.com
DP83849I
8.2 AC Specs
8.2.1 Power Up Timing
Note: In RMII Mode, the minimum Post Power up Stabilization and Hardware Configuration Latch-in times are 84ms.
Parameter Description Notes Min Typ Max Units
T2.1.1 Post Power Up Stabilization
time prior to MDC preamble for
register accesses
MDIO is pulled high for 32-bit serial man-
agement initialization
X1 Clock must be stable for a min. of
167ms at power up.
167 ms
T2.1.2 Hardware Configuration Latch-
in Time from power up
Hardware Configuration Pins are de-
scribed in the Pin Description section
X1 Clock must be stable for a min. of
167ms at power up.
167 ms
T2.1.3 Hardware Configuration pins
transition to output drivers
50 ns
Vcc
Hardware
RESET_N
MDC
32 clocks
Latch-In of Hardware
Configuration Pins
Dual Function Pins
Become Enabled As Outputs
input output
T2.1.3
T2.1.2
T2.1.1
X1 clock
www.national.com 86
DP83849I
8.2.2 Reset Timing
Note: It is important to choose pull-up and/or pull-down resistors for each of the hardware configuration pins that provide
fast RC time constants in order to latch-in the proper value prior to the pin transitioning to an output driver.
Parameter Description Notes Min Typ Max Units
T2.2.1 Post RESET Stabilization time
prior to MDC preamble for reg-
ister accesses
MDIO is pulled high for 32-bit serial man-
agement initialization
3µs
T2.2.2 Hardware Configuration Latch-
in Time from the Deassertion
of RESET (either soft or hard)
Hardware Configuration Pins are de-
scribed in the Pin Description section
3µs
T2.2.3 Hardware Configuration pins
transition to output drivers
50 ns
T2.2.4 RESET pulse width X1 Clock must be stable for at min. of 1us
during RESET pulse low time.
1µs
Vcc
Hardware
RESET_N
MDC
32 clocks
Latch-In of Hardware
Configuration Pins
Dual Function Pins
Become Enabled As Outputs
input output
T2.2.3
T2.2.2
T2.2.1
X1 clock
T2.2.4
87 www.national.com
DP83849I
8.2.3 MII Serial Management Timing
8.2.4 100 Mb/s MII Transmit Timing
Parameter Description Notes Min Typ Max Units
T2.3.1 MDC to MDIO (Output) Delay Time 030 ns
T2.3.2 MDIO (Input) to MDC Setup Time 10 ns
T2.3.3 MDIO (Input) to MDC Hold Time 10 ns
T2.3.4 MDC Frequency 2.5 25 MHz
Parameter Description Notes Min Typ Max Units
T2.4.1 TX_CLK High/Low Time 100 Mb/s Normal mode 16 20 24 ns
T2.4.2 TXD[3:0], TX_EN Data Setup to TX_CLK 100 Mb/s Normal mode 10 ns
T2.4.3 TXD[3:0], TX_EN Data Hold from TX_CLK 100 Mb/s Normal mode 0ns
MDC
MDC
MDIO (output)
MDIO (input) Valid Data
T2.3.1
T2.3.2 T2.3.3
T2.3.4
TX_CLK
TXD[3:0]
TX_EN Valid Data
T2.4.2 T2.4.3
T2.4.1 T2.4.1
www.national.com 88
DP83849I
8.2.5 100 Mb/s MII Receive Timing
Note: RX_CLK may be held low or high for a longer period of time during transition between reference and recovered
clocks. Minimum high and low times will not be violated.
8.2.6 100BASE-TX MII Transmit Packet Latency Timing
Note: For Normal mode, latency is determined by measuring the time from the first rising edge of TX_CLK occurring after
the assertion of TX_EN to the first bit of the “J” code group as output from the PMD Output Pair. 1 bit time = 10 ns in 100
Mb/s mode.
Parameter Description Notes Min Typ Max Units
T2.5.1 RX_CLK High/Low Time 100 Mb/s Normal mode 16 20 24 ns
T2.5.2 RX_CLK to RXD[3:0], RX_DV, RX_ER Delay 100 Mb/s Normal mode 10 30 ns
Parameter Description Notes Min Typ Max Units
T2.6.1 TX_CLK to PMD Output Pair
Latency
100BASE-TX mode 5bits
RX_CLK
RXD[3:0]
RX_DV
T2.5.2
T2.5.1 T2.5.1
Valid Data
RX_ER
TX_CLK
TX_EN
TXD
PMD Output Pair (J/K) IDLE DATA
T2.6.1
89 www.national.com
DP83849I
8.2.7 100BASE-TX MII Transmit Packet Deassertion Timing
Note: Deassertion is determined by measuring the time from the first rising edge of TX_CLK occurring after the deasser-
tion of TX_EN to the first bit of the “T” code group as output from the PMD Output Pair. 1 bit time = 10 ns in 100 Mb/s mode.
Parameter Description Notes Min Typ Max Units
T2.7.1 TX_CLK to PMD Output Pair
Deassertion
100BASE-TX mode 5bits
TX_CLK
TXD
TX_EN
PMD Output Pair (T/R) DATA IDLE
T2.7.1
(T/R) DATA IDLE
www.national.com 90
DP83849I
8.2.8 100BASE-TX Transmit Timing (tR/F & Jitter)
Note: Normal Mismatch is the difference between the maximum and minimum of all rise and fall times
Note: Rise and fall times taken at 10% and 90% of the +1 or -1 amplitude
Parameter Description Notes Min Typ Max Units
T2.8.1 100 Mb/s PMD Output Pair tR
and tF
3 4 5 ns
100 Mb/s tR and tF Mismatch 500 ps
T2.8.2 100 Mb/s PMD Output Pair
Transmit Jitter
1.4 ns
PMD Output Pair
T2.8.1
T2.8.1
T2.8.1
T2.8.1
+1 rise
+1 fall
-1 fall -1 rise
eye pattern
T2.8.2
T2.8.2
90%
10%
10%
90%
PMD Output Pair
91 www.national.com
DP83849I
8.2.9 100BASE-TX MII Receive Packet Latency Timing
Note: Carrier Sense On Delay is determined by measuring the time from the first bit of the “J” code group to the assertion
of Carrier Sense.
Note: 1 bit time = 10 ns in 100 Mb/s mode
Note: PMD Input Pair voltage amplitude is greater than the Signal Detect Turn-On Threshold Value.
8.2.10 100BASE-TX MII Receive Packet Deassertion Timing
Note: Carrier Sense Off Delay is determined by measuring the time from the first bit of the “T” code group to the deasser-
tion of Carrier Sense.
Note: 1 bit time = 10 ns in 100 Mb/s mode
Parameter Description Notes Min Typ Max Units
T2.9.1 Carrier Sense ON Delay 100BASE-TX mode 20 bits
T2.9.2 Receive Data Latency 100BASE-TX mode 24 bits
Parameter Description Notes Min Typ Max Units
T2.10.1 Carrier Sense OFF Delay 100BASE-TX mode 24 bits
CRS
RXD[3:0]
PMD Input Pair
RX_DV
RX_ER
IDLE Data
T2.9.1
T2.9.2
(J/K)
CRS
T2.10.1
PMD Input Pair DATA IDLE
(T/R)
www.national.com 92
DP83849I
8.2.11 10 Mb/s MII Transmit Timing
Note: An attached Mac should drive the transmit signals using the positive edge of TX_CLK. As shown above, the MII
signals are sampled on the falling edge of TX_CLK.
8.2.12 10 Mb/s MII Receive Timing
Note: RX_CLK may be held low for a longer period of time during transition between reference and recovered clocks.
Minimum high and low times will not be violated.
Parameter Description Notes Min Typ Max Units
T2.11.1 TX_CLK High/Low Time 10 Mb/s MII mode 190 200 210 ns
T2.11.2 TXD[3:0], TX_EN Data Setup to TX_CLK fall 10 Mb/s MII mode 25 ns
T2.11.3 TXD[3:0], TX_EN Data Hold from TX_CLK rise 10 Mb/s MII mode 0ns
Parameter Description Notes Min Typ Max Units
T2.12.1 RX_CLK High/Low Time 160 200 240 ns
T2.12.2 RX_CLK to RXD[3:0], RX_DV Delay 10 Mb/s MII mode 100 ns
T2.12.3 RX_CLK rising edge delay from RXD[3:0],
RX_DV Valid
10 Mb/s MII mode 100 ns
TX_CLK
TXD[3:0]
TX_EN Valid Data
T2.11.2 T2.11.3
T2.11.1 T2.11.1
RX_CLK
RXD[3:0]
RX_DV
T2.12.2
T2.12.1 T2.12.1
T2.12.3
Valid Data
93 www.national.com
DP83849I
8.2.13 10 Mb/s Serial Mode Transmit Timing
8.2.14 10 Mb/s Serial Mode Receive Timing
Note: RX_CLK may be held high for a longer period of time during transition between reference and recovered clocks.
Minimum high and low times will not be violated.
Parameter Description Notes Min Typ Max Units
T2.13.1 TX_CLK High Time 10 Mb/s Serial mode 20 25 30 ns
T2.13.2 TX_CLK Low Time 10 Mb/s Serial mode 70 75 80 ns
T2.13.3 TXD_0, TX_EN Data Setup to TX_CLK rise 10 Mb/s Serial mode 25 ns
T2.13.4 TXD_0, TX_EN Data Hold from TX_CLK rise 10 Mb/s Serial mode 0ns
Parameter Description Notes Min Typ Max Units
T2.14.1 RX_CLK High/Low Time 35 50 65 ns
T2.14.2 RX_CLK fall to RXD_0, RX_DV Delay 10 Mb/s Serial mode -10 10 ns
TX_CLK
TXD[0]
TX_EN Valid Data
T2.13.3 T2.13.4
T2.13.1 T2.13.2
RX_CLK
RXD[0]
RX_DV
T2.14.2
T2.14.1 T2.14.1
Valid Data
www.national.com 94
DP83849I
8.2.15 10BASE-T Transmit Timing (Start of Packet)
Note: 1 bit time = 100 ns in 10Mb/s.
8.2.16 10BASE-T Transmit Timing (End of Packet)
Parameter Description Notes Min Typ Max Units
T2.15.1 Transmit Output Delay from the
Falling Edge of TX_CLK
10 Mb/s MII mode 3.5 bits
T2.15.2 Transmit Output Delay from the
Rising Edge of TX_CLK
10 Mb/s Serial mode 3.5 bits
Parameter Description Notes Min Typ Max Units
T2.16.1 End of Packet High Time
(with ‘0’ ending bit)
250 300 ns
T2.16.2 End of Packet High Time
(with ‘1’ ending bit)
250 300 ns
TX_CLK
TX_EN
TXD
PMD Output Pair
T2.15.1
T2.15.2
TX_CLK
TX_EN
PMD Output Pair 00
11
PMD Output Pair
T2.16.1
T2.16.2
95 www.national.com
DP83849I
8.2.17 10BASE-T Receive Timing (Start of Packet)
Note: 10BASE-T RX_DV Latency is measured from first bit of preamble on the wire to the assertion of RX_DV
Note: 1 bit time = 100 ns in 10 Mb/s mode.
8.2.18 10BASE-T Receive Timing (End of Packet)
Parameter Description Notes Min Typ Max Units
T2.17.1 Carrier Sense Turn On Delay (PMD
Input Pair to CRS)
630 1000 ns
T2.17.2 RX_DV Latency 10 bits
T2.17.3 Receive Data Latency Measurement shown from SFD 8bits
Parameter Description Notes Min Typ Max Units
T2.18.1 Carrier Sense Turn Off Delay 1.0 µs
TPRD±
CRS
RX_CLK
RX_DV
1st SFD bit decoded
RXD[3:0]
T2.17.1
T2.17.2
T2.17.3
101010101011
Preamble SFD Data
0000
101
PMD Input Pair
RX_CLK
CRS
IDLE
T2.18.1
www.national.com 96
DP83849I
8.2.19 10 Mb/s Heartbeat Timing
8.2.20 10 Mb/s Jabber Timing
Parameter Description Notes Min Typ Max Units
T2.19.1 CD Heartbeat Delay 10 Mb/s half-duplex mode 1200 ns
T2.19.2 CD Heartbeat Duration 10 Mb/s half-duplex mode 1000 ns
Parameter Description Notes Min Typ Max Units
T2.20.1 Jabber Activation Time 85 ms
T2.20.2 Jabber Deactivation Time 500 ms
TX_CLK
TX_EN
COL
T2.19.1
T2.19.2
TXE
PMD Output Pair
COL
T2.20.2
T2.20.1
97 www.national.com
DP83849I
8.2.21 10BASE-T Normal Link Pulse Timing
Note: These specifications represent transmit timings.
8.2.22 Auto-Negotiation Fast Link Pulse (FLP) Timing
Note: These specifications represent transmit timings.
Parameter Description Notes Min Typ Max Units
T2.21.1 Pulse Width 100 ns
T2.21.2 Pulse Period 16 ms
Parameter Description Notes Min Typ Max Units
T2.22.1 Clock, Data Pulse Width 100 ns
T2.22.2 Clock Pulse to Clock Pulse
Period
125 µs
T2.22.3 Clock Pulse to Data Pulse
Period
Data = 1 62 µs
T2.22.4 Burst Width 2ms
T2.22.5 FLP Burst to FLP Burst Period 16 ms
T2.21.2
T2.21.1
Normal Link Pulse(s)
clock
pulse data
pulse clock
pulse
FLP Burst FLP Burst
Fast Link Pulse(s)
T2.22.1
T2.22.1
T2.22.2
T2.22.3
T2.22.4
T2.22.5
www.national.com 98
DP83849I
8.2.23 100BASE-TX Signal Detect Timing
Note: The signal amplitude on PMD Input Pair must be TP-PMD compliant.
8.2.24 100 Mb/s Internal Loopback Timing
Note1: Due to the nature of the descrambler function, all 100BASE-TX Loopback modes will cause an initial “dead-time”
of up to 550 µs during which time no data will be present at the receive MII outputs. The 100BASE-TX timing specified is
based on device delays after the initial 550µs “dead-time”.
Note2: Measurement is made from the first rising edge of TX_CLK after assertion of TX_EN.
Parameter Description Notes Min Typ Max Units
T2.23.1 SD Internal Turn-on Time 1ms
T2.23.2 SD Internal Turn-off Time 350 µs
Parameter Description Notes Min Typ Max Units
T2.24.1 TX_EN to RX_DV Loopback 100 Mb/s internal loopback mode 240 ns
T2.23.1
SD+ internal
T2.23.2
PMD Input Pair
TX_CLK
TX_EN
TXD[3:0]
CRS
RX_CLK
RXD[3:0]
RX_DV
T2.24.1
99 www.national.com
DP83849I
8.2.25 10 Mb/s Internal Loopback Timing
Note: Measurement is made from the first rising edge of TX_CLK after assertion of TX_EN.
Parameter Description Notes Min Typ Max Units
T2.25.1 TX_EN to RX_DV Loopback 10 Mb/s internal loopback mode 2µs
TX_CLK
TX_EN
TXD[3:0]
CRS
RX_CLK
RXD[3:0]
RX_DV
T2.25.1
www.national.com 100
DP83849I
8.2.26 RMII Transmit Timing
Parameter Description Notes Min Typ Max Units
T2.26.1 X1 Clock Period 50 MHz Reference Clock 20 ns
T2.26.2 TXD[1:0], TX_EN, Data Setup
to X1 rising
4ns
T2.26.3 TXD[1:0], TX_EN, Data Hold
from X1 rising
2ns
T2.26.4 X1 Clock to PMD Output Pair
Latency (100Mb)
100BASE-TX mode 11 bits
X1
TXD[1:0]
TX_EN Valid Data
T2.26.2 T2.26.3
T2.26.1
PMD Output Pair Symbol
T2.26.4
101 www.national.com
DP83849I
8.2.27 RMII Receive Timing
Note: Per the RMII Specification, output delays assume a 25pF load.
Note: CRS_DV is asserted asynchronously in order to minimize latency of control signals through the Phy. CRS_DV may
toggle synchronously at the end of the packet to indicate CRS deassertion.
Note: RX_DV is synchronous to X1. While not part of the RMII specification, this signal is provided to simplify recovery of
receive data.
Note: CRS ON delay is measured from the first bit of the JK symbol on the PMD Receive Pair to initial assertion of
CRS_DV.
Note: CRS_OFF delay is measured from the first bit of the TR symbol on the PMD Receive Pair to initial deassertion of
CRS_DV.
Note: Receive Latency is measured from the first bit of the symbol pair on the PMD Receive Pair. Typical values are with
the Elasticity Buffer set to the default value (01).
Parameter Description Notes Min Typ Max Units
T2.27.1 X1 Clock Period 50 MHz Reference Clock 20 ns
T2.27.2 RXD[1:0], CRS_DV, RX_DV
and RX_ER output delay from
X1 rising
214 ns
T2.27.3 CRS ON delay (100Mb) 100BASE-TX mode 18.5 bits
T2.27.4 CRS OFF delay (100Mb) 100BASE-TX mode 27 bits
T2.27.5 RXD[1:0] and RX_ER latency
(100Mb)
100BASE-TX mode 38 bits
CRS_DV
X1
RXD[1:0]
RX_ER
T2.27.2
T2.27.1
T2.27.2
PMD Input Pair
IDLE Data
(J/K)
T2.27.3
T2.27.5
Data
(TR)
T2.27.4
RX_DV
T2.27.2
T2.27.2
www.national.com 102
DP83849I
8.2.28 Single Clock MII (SCMII) Transmit Timing
Note: Latency measurement is made from the X1 Rising edge to the first bit of symbol.
Parameter Description Notes Min Typ Max Units
T2.28.1 X1 Clock Period 25MHz Reference Clock 40 ns
T2.28.2 TXD[3:0], TX_EN Data Setup To X1 rising 4ns
T2.28.3 TXD[3:0], TX_EN Data Hold From X1 rising 2ns
T2.28.4 X1 Clock to PMD Output Pair
Latency (100Mb)
100BASE-TX mode 13 bits
TXD[3:0]
TX_EN Valid Data
T2.28.2 T2.28.3
PMD Output Pair Symbol
T2.28.4
X1
T2.28.1
103 www.national.com
DP83849I
8.2.29 Single Clock MII (SCMII) Receive Timing
Note: Output delays assume a 25pF load.
Note: CRS is asserted and deasserted asynchronously relative to the reference clock.
Note: CRS ON delay is measured from the first bit of the JK symbol on the PMD Receive Pair to assertion of CRS_DV.
Note: CRS_OFF delay is measured from the first bit of the TR symbol on the PMD Receive Pair to deassertion of
CRS_DV.
Note: Receive Latency is measured from the first bit of the symbol pair on the PMD Receive Pair. Typical values are with
the Elasticity Buffer set to the default value (01).
Parameter Description Notes Min Typ Max Units
T2.29.1 X1 Clock Period 25MHz Reference Clock 40 ns
T2.29.2 RXD[3:0], RX_DV and RX_ER
output delay
From X1 rising 218 ns
T2.29.3 CRS ON delay (100Mb) 100BASE-TX mode 19 bits
T2.29.4 CRS OFF delay (100Mb) 100BASE-TX mode 26 bits
T2.29.5 RXD[1:0] and RX_ER latency
(100Mb)
100BASE-TX mode 56 bits
X1
CRS
RX_DV
T2.29.1
T2.29.2
PMD Input Pair
IDLE Data
(J/K)
T2.29.3
T2.29.5
Data
(TR)
T2.29.4
RXD[1:0]
RX_ER
T2.29.2
www.national.com 104
DP83849I
8.2.30 Isolation Timing
8.2.31 CLK2MAC Timing
Note: CLK2MAC characteristics are dependent upon the X1 input characteristics.
Parameter Description Notes Min Typ Max Units
T2.30.1 From software clear of bit 10 in
the BMCR register to the transi-
tion from Isolate to Normal Mode
100 µs
Parameter Description Notes Min Typ Max Units
T2.31.1 CLK2MAC High/Low Time MII mode 20 ns
RMII mode 10 ns
T2.31.2 CLK2MAC propagation delay Relative to X1 8ns
Clear bit 10 of BMCR
(return to normal operation
from Isolate mode)
MODE
ISOLATE NORMAL
T2.30.1
X1
T2.31.2
CLK2MAC
T2.31.1 T2.31.1
105 www.national.com
DP83849I
8.2.32 100 Mb/s X1 to TX_CLK Timing
Note: X1 to TX_CLK timing is provided to support devices that use X1 instead of TX_CLK as the reference for transmit
Mll data.
Parameter Description Notes Min Typ Max Units
T2.32.1 X1 to TX_CLK delay 100 Mb/s Normal mode 0 5 ns
X1
T2.32.1
TX_CLK
DP83849I PHYTER® DUAL Industrial Temperature with Flexible Port Switching
Dual Port 10/100 Mb/s Ethernet Physical Layer Transceiver
inches (millimeters) unless otherwise noted
THE CONTENTS OF THIS DOCUMENT ARE PROVIDED IN CONNECTION WITH NATIONAL SEMICONDUCTOR CORPORATION
(“NATIONAL”) PROCUCTS. NATIONAL MAKES NO REPRESENTATIONS OR WARRANTIES WITH RESPECT TO THE ACCURACY
OR COMPLETENESS OF THE CONTENTS OF THIS PUBLICATION AND RESERVES THE RIGHT TO MAKE CHANGES TO SPEC-
IFICATIONS AND PRODUCT DESCRIPTIONS AT ANY TIME WITHOUT NOTICE. NO LICENSE, WHETHER EXPRESS, IMPLIED,
ARISING BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT.
TESTING AND OTHER QUALITY CONTROLS ARE USED TO THE EXTENT NATIONAL DEEMS NECESSARY TO SUPPORT
NATIONAL’S PRODUCT WARRANT. EXCEPT WHERE MANDATED BY GOVERNMENT REQUIREMENTS, TESTING OF ALL
PARAMETER OF EACH PRODUCT IS NOT NECESSARILY PERFORMED. NATIONAL ASSUMES NO LIABILITY FOR APPLIC-
TIONS ASSISTANCE OR BUYER PRODUCT DESIGN. BUYERS ARE RESPONSIBLE FOR THEIR PROCUCTS AND APPLICA-
TIONS USING NATIONAL COMPONENTS. PRIOR TO USING OR DISTRIBUTING ANY PROCUCTS THAT INCLUDE NATIONAL
COMPONENTS, BUYERS SHOULD PROVIDE ADEQUATE DESIGN, TESTING AND OPERATING SAFEGUARDS.
EXCEPT AS PROVIDED IN NATIONAL’S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, NATIONAL ASSUMES NO
LIABILITY WHATSOEVER, AND NATIONAL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY RELATING TO THE SALE
AND/OR USE OF NATIONAL PRODUCTS INCLUDEDING LIBILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICU-
LAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROP-
ERTY RIGHT.
LIFE SUPPORT POLICY
NATIONAL’S PRODUCTS ARE NOT AUTHORIZED FOR USE AS CRITICAL COMPONENTS IN LIFE SUPPORT
DEVICES OR SYSTEMS WITHOUT THE EXPRESS WRITTEN APPROVAL OF THE CHIEF EXECUTIVE OFFICER
AND GENERAL COUNSEL OF NATIONAL SEMICONDUCTOR CORPORATION. As used herein:
Life support devices or systems are devices which (a) are intended for surgical implant into the body, or (b) support or sustain life and
whose failure to perform when properly used in accordance with instructions for use provided in the labeling can be reasonably expected
to result in a significant injury to the user. A critical component is any component of a life support device or system whose failure to per-
form can be reasonably expected to cause the failure of the life support device or system or to affect its safety or effectiveness.
National Semiconductor
Americas Technical
Support Center
Email:
new.feedback@nsc.com
Tel: 1-800-272-9959
National Semiconductor Europe
Technical Support Center
Email: europe.support@nsc.com
German Tel: +49 (0) 180 5010 771
English Tel: +44 (0) 870 850 4288
National Semiconductor Japan
Technical Support Center
Email: jpn.feedback@nsc.com
www.national.com
National Semiconductor Asia
Pacific Technical
Support Center
Email: ap.support@nsc.com
National Semiconductor and the National Semiconductor logo are registered trademarks of National Semiconductor Corporation. All other
brand or product names may be trademarks or registered trademarks of their respective holders.
Copyright © 2008 National Semiconductor Corporation
For the most current product information visit us at www.national.com
9.0 Physical Dimensions
Thin Quad Flat Package (TQFP)
NS Package Number VHB80A
IMPORTANT NOTICE
Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, modifications, enhancements, improvements,
and other changes to its products and services at any time and to discontinue any product or service without notice. Customers should
obtain the latest relevant information before placing orders and should verify that such information is current and complete. All products are
sold subject to TIs terms and conditions of sale supplied at the time of order acknowledgment.
TI warrants performance of its hardware products to the specifications applicable at the time of sale in accordance with TIs standard
warranty. Testing and other quality control techniques are used to the extent TI deems necessary to support this warranty. Except where
mandated by government requirements, testing of all parameters of each product is not necessarily performed.
TI assumes no liability for applications assistance or customer product design. Customers are responsible for their products and
applications using TI components. To minimize the risks associated with customer products and applications, customers should provide
adequate design and operating safeguards.
TI does not warrant or represent that any license, either express or implied, is granted under any TI patent right, copyright, mask work right,
or other TI intellectual property right relating to any combination, machine, or process in which TI products or services are used. Information
published by TI regarding third-party products or services does not constitute a license from TI to use such products or services or a
warranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual
property of the third party, or a license from TI under the patents or other intellectual property of TI.
Reproduction of TI information in TI data books or data sheets is permissible only if reproduction is without alteration and is accompanied
by all associated warranties, conditions, limitations, and notices. Reproduction of this information with alteration is an unfair and deceptive
business practice. TI is not responsible or liable for such altered documentation. Information of third parties may be subject to additional
restrictions.
Resale of TI products or services with statements different from or beyond the parameters stated by TI for that product or service voids all
express and any implied warranties for the associated TI product or service and is an unfair and deceptive business practice. TI is not
responsible or liable for any such statements.
TI products are not authorized for use in safety-critical applications (such as life support) where a failure of the TI product would reasonably
be expected to cause severe personal injury or death, unless officers of the parties have executed an agreement specifically governing
such use. Buyers represent that they have all necessary expertise in the safety and regulatory ramifications of their applications, and
acknowledge and agree that they are solely responsible for all legal, regulatory and safety-related requirements concerning their products
and any use of TI products in such safety-critical applications, notwithstanding any applications-related information or support that may be
provided by TI. Further, Buyers must fully indemnify TI and its representatives against any damages arising out of the use of TI products in
such safety-critical applications.
TI products are neither designed nor intended for use in military/aerospace applications or environments unless the TI products are
specifically designated by TI as military-grade or "enhanced plastic."Only products designated by TI as military-grade meet military
specifications. Buyers acknowledge and agree that any such use of TI products which TI has not designated as military-grade is solely at
the Buyer's risk, and that they are solely responsible for compliance with all legal and regulatory requirements in connection with such use.
TI products are neither designed nor intended for use in automotive applications or environments unless the specific TI products are
designated by TI as compliant with ISO/TS 16949 requirements. Buyers acknowledge and agree that, if they use any non-designated
products in automotive applications, TI will not be responsible for any failure to meet such requirements.
Following are URLs where you can obtain information on other Texas Instruments products and application solutions:
Products Applications
Audio www.ti.com/audio Communications and Telecom www.ti.com/communications
Amplifiers amplifier.ti.com Computers and Peripherals www.ti.com/computers
Data Converters dataconverter.ti.com Consumer Electronics www.ti.com/consumer-apps
DLP®Products www.dlp.com Energy and Lighting www.ti.com/energy
DSP dsp.ti.com Industrial www.ti.com/industrial
Clocks and Timers www.ti.com/clocks Medical www.ti.com/medical
Interface interface.ti.com Security www.ti.com/security
Logic logic.ti.com Space, Avionics and Defense www.ti.com/space-avionics-defense
Power Mgmt power.ti.com Transportation and Automotive www.ti.com/automotive
Microcontrollers microcontroller.ti.com Video and Imaging www.ti.com/video
RFID www.ti-rfid.com
OMAP Mobile Processors www.ti.com/omap
Wireless Connectivity www.ti.com/wirelessconnectivity
TI E2E Community Home Page e2e.ti.com
Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265
Copyright ©2011, Texas Instruments Incorporated