SMSC LAN8187

LAN8187/LAN8187I
High-Performance MII
and RMII 10/100 Ethernet
PHY with HP Auto-MDIX
PRODUCT FEATURES
„
„
„
„
Datasheet
Single-Chip Ethernet Physical Layer Transceiver
(PHY)
Performs HP Auto-MDIX in accordance with IEEE
802.3ab specification
Automatic Polarity Correction
Comprehensive SMSC flexPWRTM Technology
— Flexible Power Management Architecture
„
„
„
„
„
„
„
„
„
„
„
„
„
LVCMOS Variable I/O voltage range: +1.6V to +3.6V
Integrated 3.3V to 1.8V regulator for optional single
supply operation.
„
— Regulator can be disabled if 1.8V system supply is
available.
„
Energy Detect power-down mode
Low Current consumption power down mode
Low operating current consumption:
„
„
„
„
„
„
— 39mA typical in 10BASE-T and
— 79mA typical in 100BASE-TX mode
„
Applications
„
8kV HBM ESD Performance
Supports Auto-negotiation and Parallel Detection
Supports the Media Independent Interface (MII) and
Reduced Media Independent Interface (RMII)
Compliant with IEEE 802.3-2005 standards
„
„
„
Set Top Boxes
Network Printers and Servers
LAN on Motherboard
10/100 PCMCIA/CardBus Applications
Embedded Telecom Applications
Video Record/Playback Systems
Cable Modems/Routers
Digital Video Recorders
Personal video Recorders
IP and Video Phones
Wireless Access Points
Digital Televisions
Digital Media Adapters/Servers
POS Terminals
Automotive Networking
Gaming Consoles
Security Systems
— MII Pins tolerant to 3.6V
„
„
„
„
„
„
„
„
IEEE 802.3-2005 compliant register functions
Integrated DSP with Adaptive Equalizer
Baseline Wander (BLW) Correction
Vendor Specific register functions
Low profile 64-pin TQFP package; green, lead-free
4 LED status indicators
Commercial Operating Temperature 0° C to 70° C
Industrial Operating Temperature -40° C to 85° C
version available (LAN8187I)
ORDER NUMBER(S):
LAN8187-JT FOR 64-PIN, TQFP PACKAGE (GREEN, LEAD-FREE)
LAN8187I-JT FOR INDUSTRIAL TEMPERATURE 64-PIN, TQFP PACKAGE (GREEN, LEAD-FREE)
SMSC LAN8187/LAN8187I
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
80 Arkay Drive
Hauppauge, NY 11788
(631) 435-6000
FAX (631) 273-3123
Copyright © 2006 SMSC or its subsidiaries. All rights reserved.
Circuit diagrams and other information relating to SMSC products are included as a means of illustrating typical applications. Consequently,
complete information sufficient for construction purposes is not necessarily given. Although the information has been checked and is believed to be
accurate, no responsibility is assumed for inaccuracies. SMSC reserves the right to make changes to specifications and product descriptions at any
time without notice. Contact your local SMSC sales office to obtain the latest specifications before placing your product order. The provision of this
information does not convey to the purchaser of the described semiconductor devices any licenses under any patent rights or other intellectual
property rights of SMSC or others. All sales are expressly conditional on your agreement to the terms and conditions of the most recently dated
version of SMSC's standard Terms of Sale Agreement dated before the date of your order (the "Terms of Sale Agreement"). The product may
contain design defects or errors known as anomalies which may cause the product's functions to deviate from published specifications. Anomaly
sheets are available upon request. SMSC products are not designed, intended, authorized or warranted for use in any life support or other
application where product failure could cause or contribute to personal injury or severe property damage. Any and all such uses without prior written
approval of an Officer of SMSC and further testing and/or modification will be fully at the risk of the customer. Copies of this document or other
SMSC literature, as well as the Terms of Sale Agreement, may be obtained by visiting SMSC’s website at http://www.smsc.com. SMSC is a
registered trademark of Standard Microsystems Corporation (“SMSC”). Product names and company names are the trademarks of their respective
holders.
SMSC DISCLAIMS AND EXCLUDES ANY AND ALL WARRANTIES, INCLUDING WITHOUT LIMITATION ANY AND ALL IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND AGAINST INFRINGEMENT AND THE LIKE,
AND ANY AND ALL WARRANTIES ARISING FROM ANY COURSE OF DEALING OR USAGE OF TRADE. IN NO EVENT SHALL SMSC BE
LIABLE FOR ANY DIRECT, INCIDENTAL, INDIRECT, SPECIAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES; OR FOR LOST DATA,
PROFITS, SAVINGS OR REVENUES OF ANY KIND; REGARDLESS OF THE FORM OF ACTION, WHETHER BASED ON CONTRACT; TORT;
NEGLIGENCE OF SMSC OR OTHERS; STRICT LIABILITY; BREACH OF WARRANTY; OR OTHERWISE; WHETHER OR NOT ANY REMEDY
OF BUYER IS HELD TO HAVE FAILED OF ITS ESSENTIAL PURPOSE, AND WHETHER OR NOT SMSC HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
Revision 0.6 (02-24-06)
2
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table of Contents
Chapter 1 General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.1
Architectural Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter 2 Pin Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1
Package Pin-out Diagram and Signal Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 3 Pin Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1
I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 4 Architecture Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9
4.10
Top Level Functional Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
100Base-TX Transmit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1
100M Transmit Data Across the MII/RMII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2
4B/5B Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3
Scrambling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4
NRZI and MLT3 Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.5
100M Transmit Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.6
100M Phase Lock Loop (PLL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
100Base-TX Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1
100M Receive Input. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2
Equalizer, Baseline Wander Correction and Clock and Data Recovery . . . . . . . . . . . . .
4.3.3
NRZI and MLT-3 Decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4
Descrambling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.5
Alignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.6
5B/4B Decoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.7
Receive Data Valid Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.8
Receiver Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.9
100M Receive Data Across the MII/RMII Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10Base-T Transmit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1
10M Transmit Data Across the MII/RMII Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2
Manchester Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.3
10M Transmit Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10Base-T Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.1
10M Receive Input and Squelch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.2
Manchester Decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.3
10M Receive Data Across the MII/RMII Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.4
Jabber Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MAC Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1
MII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2
RMII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.3
MII vs. RMII Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.1
Parallel Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.2
Re-starting Auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.3
Disabling Auto-negotiation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.4
Half vs. Full Duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP Auto-MDIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Internal +1.8V Regulator Disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.9.1
Disable the Internal +1.8V Regulator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.9.2
Enable the Internal +1.8V Regulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(TX_ER/TXD4)/nINT Strapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SMSC LAN8187/LAN8187I
3
DATASHEET
18
18
18
18
20
20
20
20
21
21
21
21
22
22
22
22
23
23
23
23
24
24
24
24
24
24
25
25
25
25
26
27
29
29
29
29
29
30
30
30
30
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
4.11
4.12
4.13
PHY Address Strapping and LED Output Polarity Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Variable Voltage I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.12.1 Boot Strapping Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.12.2 I/O Voltage Stability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PHY Management Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.13.1 Serial Management Interface (SMI). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
31
32
32
32
32
Chapter 5 Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.1
5.2
5.3
5.4
SMI Register Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SMI Register Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interrupt Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Miscellaneous Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.1
Carrier Sense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.2
Collision Detect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.3
Isolate Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.4
Link Integrity Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.5
Power-Down modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.6
Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.7
LED Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.8
Loopback Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.9
Configuration Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
40
40
48
49
49
49
49
49
50
50
51
51
51
Chapter 6 Electrical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.1
6.2
6.3
6.4
6.5
6.6
Serial Management Interface (SMI) Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MII 10/100Base-TX/RX Timings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1
MII 100Base-T TX/RX Timings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.2
MII 10Base-T TX/RX Timings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RMII 10/100Base-TX/RX Timings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1
RMII 100Base-T TX/RX Timings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.2
RMII 10Base-T TX/RX Timings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
REF_CLK Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reset Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.6.1
Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.6.2
Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.6.3
DC Characteristics - Input and Output Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
53
54
54
55
57
57
58
59
60
61
61
61
62
Chapter 7 Package Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Revision 0.6 (02-24-06)
4
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
List of Figures
Figure 1.1
Figure 1.2
Figure 2.1
Figure 4.1
Figure 4.2
Figure 4.3
Figure 4.4
Figure 4.5
Figure 4.6
Figure 4.7
Figure 6.1
Figure 6.2
Figure 6.3
Figure 6.4
Figure 6.5
Figure 6.6
Figure 6.7
Figure 6.8
Figure 6.9
Figure 6.10
Figure 7.1
LAN8187/LAN8187I System Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
LAN8187/LAN8187I Architectural Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Package Pinout (Top View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
100Base-TX Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Receive Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Relationship Between Received Data and specific MII Signals . . . . . . . . . . . . . . . . . . . . . . . 22
Direct cable connection vs. Cross-over cable connection.. . . . . . . . . . . . . . . . . . . . . . . . . . . 30
PHY Address Strapping on LED’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
MDIO Timing and Frame Structure - READ Cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
MDIO Timing and Frame Structure - WRITE Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
SMI Timing Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
100M MII Receive Timing Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
100M MII Transmit Timing Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
10M MII Receive Timing Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
10M MII Transmit Timing Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
100M RMII Receive Timing Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
100M RMII Transmit Timing Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
10M RMII Receive Timing Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
10M RMII Transmit Timing Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Reset Timing Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
64 Pin TQFP Package Outline, 10X10X1.4 Body, 12x12 mm Footprint . . . . . . . . . . . . . . . . 66
SMSC LAN8187/LAN8187I
5
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
List of Tables
Table 2.1 LAN8187/LAN8187I 64-PIN TQFP Pinout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3.1 MII Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3.2 LED Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3.3 Management Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3.4 Boot Strap Configuration Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3.5 General Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3.6 10/100 Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3.7 Analog References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3.8 No Connect Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3.9 Power Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4.1 4B/5B Code Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4.2 MII/RMII Signal Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4.3 Boot Strapping Configuration Resistors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.1 Control Register: Register 0 (Basic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.2 Status Register: Register 1 (Basic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.3 PHY ID 1 Register: Register 2 (Extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.4 PHY ID 2 Register: Register 3 (Extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.5 Auto-Negotiation Advertisement: Register 4 (Extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.6 Auto-Negotiation Link Partner Base Page Ability Register: Register 5 (Extended) . . . . . . . . .
Table 5.7 Auto-Negotiation Expansion Register: Register 6 (Extended). . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.8 Auto-Negotiation Link Partner Next Page Transmit Register: Register 7 (Extended) . . . . . . .
Table 5.9 Register 8 (Extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.10 Register 9 (Extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.11 Register 10 (Extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.12 Register 11 (Extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.13 Register 12 (Extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.14 Register 13 (Extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.15 Register 14 (Extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.16 Register 15 (Extended) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.17 Silicon Revision Register 16: Vendor-Specific. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.18 Mode Control/ Status Register 17: Vendor-Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.19 Special Modes Register 18: Vendor-Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.20 Reserved Register 19: Vendor-Specific. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.21 Register 24: Vendor-Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.22 Register 25: Vendor-Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.23 Register 26: Vendor-Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.24 Special Control/Status Indications Register 27: Vendor-Specific . . . . . . . . . . . . . . . . . . . . . .
Table 5.25 Special Internal Testability Control Register 28: Vendor-Specific . . . . . . . . . . . . . . . . . . . . . .
Table 5.26 Interrupt Source Flags Register 29: Vendor-Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.27 Interrupt Mask Register 30: Vendor-Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.28 PHY Special Control/Status Register 31: Vendor-Specific . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.29 SMI Register Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.30 Register 0 - Basic Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.31 Register 1 - Basic Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.32 Register 2 - PHY Identifier 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.33 Register 3 - PHY Identifier 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.34 Register 4 - Auto Negotiation Advertisement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.35 Register 5 - Auto Negotiation Link Partner Ability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.36 Register 6 - Auto Negotiation Expansion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.37 Register 16 - Silicon Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.38 Register 17 - Mode Control/Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.39 Register 18 - Special Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.40 Register 27 - Special Control/Status Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Revision 0.6 (02-24-06)
6
DATASHEET
11
12
14
14
14
15
16
16
17
17
19
27
32
34
34
34
34
35
35
35
35
36
36
36
36
36
36
37
37
37
37
37
38
38
38
38
38
39
39
39
39
40
41
41
42
42
42
43
44
44
44
45
46
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 5.41 Register 28 - Special Internal Testability Controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.42 Register 29 - Interrupt Source Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.43 Register 30 - Interrupt Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.44 Register 31 - PHY Special Control/Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5.45 MODE[2:0] Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.1 SMI Timing Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.2 100M MII Receive Timing Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.3 100M MII Transmit Timing Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.4 10M MII Receive Timing Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.5 10M MII Transmit Timing Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.6 100M RMII Receive Timing Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.7 100M RMII Transmit Timing Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.9 10M RMII Transmit Timing Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.10 REF_CLK Timing Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.8 10M RMII Receive Timing Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.11 Reset Timing Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.12 Power Consumption Device Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.13 MII Bus Interface Signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.14 LAN Interface Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.15 LED Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.16 Configuration Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.17 General Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.18 Analog References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.19 Internal Pull-Up / Pull-Down Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.20 100Base-TX Transceiver Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6.21 10BASE-T Transceiver Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 7.1 64 Pin TQFP Package Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SMSC LAN8187/LAN8187I
7
DATASHEET
46
47
47
47
52
53
54
55
56
56
57
58
59
59
59
60
61
62
63
63
63
64
64
64
65
65
66
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Chapter 1 General Description
The SMSC LAN8187/LAN8187I is a low-power, industrial temperature (LAN8187I), variable I/O
voltage, analog interface IC with HP Auto-MDIX for high-performance embedded Ethernet applications.
The LAN8187/LAN8187I can be configured to operate on a single 3.3V supply utilizing an integrated
3.3V to 1.8V linear regulator. An option is available to disable the linear regulator to optimize system
designs that have a 1.8V power plane available.
1.1
Architectural Overview
The LAN8187/LAN8187I consists of an encoder/decoder, scrambler/descrambler, wave-shaping
transmitter, output driver, twisted-pair receiver with adaptive equalizer and baseline wander (BLW)
correction, and clock and data recovery functions. The LAN8187/LAN8187I can be configured to
support either the Media Independent Interface (MII) or the Reduced Media Independent Interface
(RMII).
The LAN8187/LAN8187I is compliant with IEEE 802.3-2005 standards (MII Pins tolerant to 3.6V) and
supports both IEEE 802.3-2005 -compliant and vendor-specific register functions. It contains a fullduplex 10-BASE-T/100BASE-TX transceiver and supports 10-Mbps (10BASE-T) operation on
Category 3 and Category 5 unshielded twisted-pair cable, and 100-Mbps (100BASE-TX) operation on
Category 5 unshielded twisted-pair cable.
10/100
Media
Access
Controller
(MAC)
or SOC
System Bus
MII /RMII
SMSC
LAN8187/
LAN8187I
Magnetics
Ethernet
LEDS/GPIO
25 MHz (MII) or 50MHz (RMIII)
Crystal or External Clock
Figure 1.1 LAN8187/LAN8187I System Block Diagram
Hubs and switches with multiple integrated MACs and external PHYs can have a large pin count due
to the high number of pins needed for each MII interface. An increasing pin count causes increasing
cost.
The RMII interface is intended for use on Switch based ASICs or other embedded solutions requiring
minimal pincount for ethernet connectivity. RMII requires only 6 pins for each MAC to PHY interface
plus one common reference clock. The MII requires 16 pins for each MAC to PHY interface.
The SMSC LAN8187/LAN8187I is capable of running in RMII mode. Please refer to the RMII
consortium for more information on the RMII standard http://www.rmii-consort.com.
The LAN8187/LAN8187I referenced throughout this document applies to both the commercial
temperature and industrial temperature components. The LAN8187I refers to only the industrial
temperature component.
Revision 0.6 (02-24-06)
8
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
MODE0
MODE1
MODE2
MODE Control
nRESET
SMI
AutoNegotiation
10M Tx
Logic
Management
Control
100M Tx
Logic
RXP / RXN
100M
Transmitter
MDIX
Control
RMII / MII Logic
RXD[0..3]
RX_DV
RX_ER
RX_CLK
TXP / TXN
Transmit Section
MII
CLK_FREQ
TXD[0..3]
TX_EN
TX_ER
TX_CLK
HP Auto-MDIX
10M
Transmitter
CRS
COL/CRS_DV
MDC
MDIO
100M Rx
Logic
DSP System:
Clock
Data Recovery
Equalizer
PLL
Analog-toDigital
100M PLL
Receive Section
10M Rx
Logic
PHY
Address
Latches
Squelch &
Filters
10M PLL
CH_SELECT
AMDIX_EN
Central
Bias
Interrupt
Generator
XTAL1
XTAL2
nINT
PHYAD[0..4]
LED Circuitry
SPEED100
LINK
ACTIVITY
FDUPLEX
GPO Circuitry
GPO0
GPO1
GPO2
Figure 1.2 LAN8187/LAN8187I Architectural Overview
SMSC LAN8187/LAN8187I
9
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Chapter 2 Pin Configuration
GPO0/MII
AVSS1
49
TXN
TXP
AVSS2
AVDD1
RXN
NC
RXP
AVDD2
AVSS3
EXRES1
AVSS4
AVDD3
VSS6
64
NC
Package Pin-out Diagram and Signal Table
REG_EN
2.1
1
48
GPO1/PHYAD4
CRS
COL/CRS_DV
nINT/TX_ER/TXD4
GPO2
MODE0
TXD3
MODE1
TXD2
MODE2
VDDIO
TXD1
VSS1
LAN8187/LAN8187I
NC
TXD0
TEST0
VSS5
TEST1
TX_EN
NC
TX_CLK
NC
AMDIX_EN
VDD33
CH_SELECT
VDD_CORE
RX_ER/RXD4
VSS2
33
RXD0
RXD1
RXD2
VSS4
RXD3
MDC
nRST
MDIO
VSS3
CLKIN/XTAL1
NC
XTAL2
ACTIVITY/PHYAD2
FDUPLEX/PHYAD3
NC
LINK/PHYAD1
RX_DV
32
16
17
SPEED100/PHYAD0
RX_CLK
Figure 2.1 Package Pinout (Top View)
Revision 0.6 (02-24-06)
10
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 2.1 LAN8187/LAN8187I 64-PIN TQFP Pinout
PIN NO.
PIN NAME
PIN NO.
PIN NAME
1
GPO0/MII
33
RX_DV
2
GPO1/PHYAD4
34
RX_CLK
3
GPO2
35
RX_ER/RXD4
4
MODE0
36
NC
5
MODE1
37
AMDIX_EN
6
MODE2
38
TX_CLK
7
VSS1
39
TX_EN
8
NC
40
VSS5
9
TEST0
41
TXD0
10
TEST1
42
TXD1
11
NC
43
VDDIO
12
NC
44
TXD2
13
VDD33
45
TXD3
14
VDD_CORE
46
nINT/TX_ER/TXD4
15
VSS2
47
COL/CRS_DV
16
SPEED100/PHYAD0
48
CRS
17
LINK/PHYAD1
49
AVSS1
18
NC
50
TXN
19
ACTIVITY/PHYAD2
51
TXP
20
FDUPLEX/PHYAD3
52
AVSS2
21
NC
53
AVDD1
22
XTAL2
54
RXN
23
CLKIN/XTAL1
55
RXP
24
VSS3
56
NC
25
nRST
57
AVDD2
26
MDIO
58
AVSS3
27
MDC
59
EXRES1
28
VSS4
60
AVSS4
29
RXD3
61
AVDD3
30
RXD2
62
VSS6
31
RXD1
63
REG_EN
32
RXD0
64
NC
SMSC LAN8187/LAN8187I
11
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Chapter 3 Pin Description
This chapter describes the signals on each pin. When a lower case “n” is used at the beginning of the
signal name, it indicates that the signal is active low. For example, nRST indicates that the reset signal
is active low.
3.1
I/O Signals
I
Input. Digital LVCMOS levels.
O
Output. Digital LVCMOS levels.
I/O
Input or Output. Digital LVCMOS levels.
Note: The digital signals are not 5V tolerant. The are variable voltage from +1.6V to +3.6V.
AI
Input. Analog levels.
AO
Output. Analog levels.
Table 3.1 MII Signals
SIGNAL NAME
TYPE
DESCRIPTION
TXD0
I
Transmit Data 0: Bit 0 of the 4 data bits that are accepted by
the PHY for transmission.
TXD1
I
Transmit Data 1: Bit 1 of the 4 data bits that are accepted by
the PHY for transmission.
TXD2
I
Transmit Data 2: Bit 2 of the 4 data bits that are accepted by
the PHY for transmission
Note:
TXD3
I
This signal should be grounded in RMII Mode.
Transmit Data 3: Bit 3 of the 4 data bits that are accepted by
the PHY for transmission.
Note:
nINT/
TX_ER/
TXD4
I/O
This signal should be grounded in RMII Mode
MII Transmit Error: When driven high, the 4B/5B encode
process substitutes the Transmit Error code-group (/H/) for the
encoded data word. This input is ignored in 10Base-T operation.
MII Transmit Data 4: In Symbol Interface (5B Decoding) mode,
this signal becomes the MII Transmit Data 4 line, the MSB of the
5-bit symbol code-group.
Notes:
„ This signal is not used in RMII Mode.
„ This signal is mux’d with nINT
„ See Section 4.10, "(TX_ER/TXD4)/nINT Strapping," on
page 30 for additional information on configuration/strapping
options.
TX_EN
I
Transmit Enable: Indicates that valid data is presented on the
TXD[3:0] signals, for transmission. In RMII Mode, only TXD[1:0]
have valid data.
TX_CLK
O
Transmit Clock: 25MHz in 100Base-TX mode. 2.5MHz in
10Base-T mode.
Note:
Revision 0.6 (02-24-06)
This signal is not used in RMII Mode
12
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 3.1 MII Signals (continued)
SIGNAL NAME
TYPE
DESCRIPTION
RXD0
O
Receive Data 0: Bit 0 of the 4 data bits that are sent by the PHY
in the receive path.
RXD1
O
Receive Data 1: Bit 1 of the 4 data bits that are sent by the PHY
in the receive path.
RXD2
O
Receive Data 2: Bit 2 of the 4 data bits that sent by the PHY in
the receive path.
Note:
RXD3/
nINTSEL
O
This signal is not used in RMII Mode.
Receive Data 3: Bit 3 of the 4 data bits that sent by the PHY in
the receive path.
nINTSEL: On power-up or external reset, the mode of the
nINT/TXER/TXD4 pin is selected.
„ When floated or pulled to VDDIO, nINT is selected (default).
„ When pulled low to VSS through a Pull-down resistor (see
Table 4.3, “Boot Strapping Configuration Resistors,” on
page 32), TXER/TXD4 is selected.
Notes:
„ RXD3 is not used in RMII Mode
„
„
RX_ER/
RXD4
I/O
If the nINT/TXER/TXD4 pin is configured for nINT mode, it
needs a pull-up resistor to VDDIO.
See Section 4.10, "(TX_ER/TXD4)/nINT Strapping," on
page 30 for additional information on configuration/strapping
options.
Receive Error: Asserted to indicate that an error was detected
somewhere in the frame presently being transferred from the
PHY.
MII Receive Data 4: In Symbol Interface (5B Decoding) mode,
this signal is the MII Receive Data 4 signal, the MSB of the
received 5-bit symbol code-group.
Notes:
„ The RX_ER signal is optional in RMII Mode.
RX_CLK
O
Receive Clock: 25MHz in 100Base-TX mode. 2.5MHz in
10Base-T mode.
Notes:
„ This signal is not used in RMII Mode
COL/CRS_DV
O
MII Collision Detect: Asserted to indicate detection of collision
condition.
RMII CRS_DV (Carrier Sense/Receive Data Valid) Asserted to
indicate when the receive medium is non-idle. When a 10BT
packet is received, CRS_DV is asserted, but RXD[1:0] is held
low until the SFD byte (10101011) is received. In 10BT, halfduplex mode, transmitted data is not looped back onto the
receive data pins, per the RMII standard.
Note:
SMSC LAN8187/LAN8187I
See Section 4.6.3, "MII vs. RMII Configuration," on
page 26 for more details.
13
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 3.2 LED Signals
SIGNAL NAME
TYPE
DESCRIPTION
CRS
O
Carrier Sense: Indicates detection of carrier.
RX_DV
O
Receive Data Valid: Indicates that recovered and decoded data
nibbles are being presented on RXD[3:0].
Note:
SPEED100/
PHYAD0
I/O
This signal is not used in RMII Mode.
LED1 – SPEED100 indication. Active indicates that the selected
speed is 100Mbps. Inactive indicates that the selected speed is
10Mbps.
Note:
LINK/
PHYAD1
I/O
This signal is mux’d with PHYAD0
LED2 – LINK ON indication. Active indicates that the Link
(100Base-TX or 10Base-T) is on.
Note:
ACTIVITY/
PHYAD2
I/O
This signal is mux’d with PHYAD1
LED3 – ACTIVITY indication. Active indicates that there is
Carrier sense (CRS) from the active PMD.
Note:
FDUPLEX/
PHYAD3
I/O
This signal is mux’d with PHYAD2
LED4 – DUPLEX indication. Active indicates that the PHY is in
full-duplex mode.
Note:
This signal is mux’d with PHYAD3
Table 3.3 Management Signals
SIGNAL NAME
TYPE
MDIO
I/O
MDC
I
DESCRIPTION
Management Data Input/OUTPUT: Serial management data
input/output.
Management Clock: Serial management clock.
Table 3.4 Boot Strap Configuration Inputsa
SIGNAL NAME
TYPE
GPO1/
PHYAD4
I/O
FDUPLEX/
PHYAD3
I/O
ACTIVITY/
PHYAD2
I/O
LINK/
PHYAD1
I/O
SPEED100/
PHYAD0
I/O
Revision 0.6 (02-24-06)
DESCRIPTION
PHY Address Bit 4: set the default address of the PHY. This
signal is mux’d with GPO1
PHY Address Bit 3: set the default address of the PHY.
Note:
This signal is mux’d with FDUPLEX
PHY Address Bit 2: set the default address of the PHY.
Note:
This signal is mux’d with ACTIVITY
PHY Address Bit 1: set the default address of the PHY.
Note:
This signal is mux’d with LINK
PHY Address Bit 0: set the default address of the PHY.
Note:
This signal is mux’d with SPEED100
14
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 3.4 Boot Strap Configuration Inputsa
SIGNAL NAME
TYPE
DESCRIPTION
MODE2
I
PHY Operating Mode Bit 2: set the default MODE of the PHY.
See Section 5.4.9.2, "Mode Bus – MODE[2:0]," on page 51, for
the MODE options.
MODE1
I
PHY Operating Mode Bit 1: set the default MODE of the PHY.
See Section 5.4.9.2, "Mode Bus – MODE[2:0]," on page 51, for
the MODE options.
MODE0
I
PHY Operating Mode Bit 0: set the default MODE of the PHY.
See Section 5.4.9.2, "Mode Bus – MODE[2:0]," on page 51, for
the MODE options.
TEST1
I
Test Mode Select 1: Must be left floating.
TEST0
I
Test Mode Select 0: Must be left floating.
REG_EN
I
Regulator Enable: Internal +1.8V regulator enable:
VDDIO – Enables internal regulator.
VSS– Disables internal regulator.
AMDIX_EN
I
HP Auto-MDIX Enable: Auto-MDIX mode enable.
+3.3V – Enables HP Auto-MDIX.
0V – Disables HP Auto-MDIX
CH_SELECT
I
Channel Select: With Auto-MDIX disabled above,
VDDIO – Enables HP Auto-MDIX.
0V – Disables HP Auto-MDIX
GPO0/MII
I/O
General Purpose Output 0 – General Purpose Output signal.
Driven by bits in registers 27 and 31.
MII – MII/RMII mode selection is latched on the rising edge of
the internal reset (nreset) based on the following strapping:
Float the GPO0 pin for MII mode or pull-high with an external
Pull-up resistor (see Table 4.3, “Boot Strapping Configuration
Resistors,” on page 32) to VDDIO to set the device in RMII
mode.
Note:
See Section 4.6.3, "MII vs. RMII Configuration," on
page 26 for more details.
a.On nRST transition high, the PHY latches the state of the configuration pins in this table.
Table 3.5 General Signals
SIGNAL NAME
TYPE
DESCRIPTION
nINT
I/O
LAN Interrupt – Active Low output. Place a pull-up external
resistor (see Table 4.3, “Boot Strapping Configuration Resistors,”
on page 32) to VCC 3.3V.
Notes:
„ This signal is mux’d with TX_ER/TXD4
„ See Section 4.10, "(TX_ER/TXD4)/nINT Strapping," on
page 30 for additional details on Strapping options.
nRST
SMSC LAN8187/LAN8187I
I
External Reset – input of the system reset. This signal is active
LOW.
15
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 3.5 General Signals (continued)
SIGNAL NAME
TYPE
DESCRIPTION
CLKIN/XTAL1
I
Clock Input – 25 Mhz or 50 MHz external clock or crystal input.
In MII mode, this signal is the 25 MHz reference input clock
In RMII mode, this signal is the 50 MHz reference input clock
which is typically also driven to the RMII compliant Ethernet MAC
clock input.
Note:
XTAL2
O
See Section 4.10, "(TX_ER/TXD4)/nINT Strapping," on
page 30 for additional details on Strapping options.
Clock Output – 25 MHz crystal output.
Note:
See Section 4.10, "(TX_ER/TXD4)/nINT Strapping," on
page 30 for additional details on Strapping options.
Also, float this pin if using an external clock being
driven through CLKIN/XTAL1
GPO2
O
General Purpose Output 2 – General Purpose Output signal
Driven by bits in registers 27 and 31.
GPO1
O
General Purpose Output 1 – General Purpose Output signal
Driven by bits in registers 27 and 31. This signal is mux’d with
PHYAD4.
GPO0/MII
I/O
General Purpose Output 0 – General Purpose Output signal.
Driven by bits in registers 27 and 31.
MII – MII/RMII mode selection is latched on the rising edge of
the internal reset (nreset) based on the following strapping:
Float the GPO0 pin for MII mode or pull-high with an external
(see Table 4.3, “Boot Strapping Configuration Resistors,” on
page 32) resistor to VDDIO to set the device in RMII mode.
Note:
See Section 4.6.3, "MII vs. RMII Configuration," on
page 26 for more details.
Table 3.6 10/100 Line Interface
SIGNAL NAME
TYPE
DESCRIPTION
TXP
AO
Transmit Data: 100Base-TX or 10Base-T differential transmit
outputs to magnetics.
TXN
AO
Transmit Data: 100Base-TX or 10Base-T differential transmit
outputs to magnetics.
RXP
AI
Receive Data: 100Base-TX or 10Base-T differential receive
inputs from magnetics.
RXN
AI
Receive Data: 100Base-TX or 10Base-T differential receive
inputs from magnetics.
Table 3.7 Analog References
SIGNAL NAME
TYPE
EXRES1
AI
Revision 0.6 (02-24-06)
DESCRIPTION
Connects to reference resistor of value 12.4K-Ohm, 1%
connected as described in the Analog Layout Guidelines.
16
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 3.8 No Connect Signals
SIGNAL NAME
TYPE
NC
DESCRIPTION
No Connect
Table 3.9 Power Signals
SIGNAL NAME
TYPE
AVDD1
POWER
+3.3V Analog Power
AVDD2
POWER
+3.3V Analog Power
AVDD3
POWER
+3.3V Analog Power
AVSS1
POWER
Analog Ground
AVSS2
POWER
Analog Ground
AVSS3
POWER
Analog Ground
AVSS4
POWER
Analog Ground
VDD_CORE
POWER
+1.8V (Core voltage) - 1.8V regulator output for digital circuitry
on chip. Place a 0.1uF capacitor near this pin and connect the
capacitor from this pin to ground. In parallel, place a 4.7uF +/20% low ESR capacitor near this pin and connect the capacitor
from this pin to ground. X5R or X7R ceramic capacitors are
recommended since they exhibit an ESR lower than 0.1ohm at
frequencies greater than 10kHz.
VDD33
POWER
+3.3V Digital Power
VDDIO
POWER
+1.6V to +3.6V Variable I/O Pad Power
VSS1
POWER
Digital Ground (GND)
VSS2
POWER
Digital Ground (GND)
VSS3
POWER
Digital Ground (GND)
VSS4
POWER
Digital Ground (GND)
VSS5
POWER
Digital Ground (GND)
VSS6
POWER
Digital Ground (GND)
SMSC LAN8187/LAN8187I
DESCRIPTION
17
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Chapter 4 Architecture Details
4.1
Top Level Functional Architecture
Functionally, the PHY can be divided into the following sections:
„
100Base-TX transmit and receive
„
10Base-T transmit and receive
„
MII or RMII interface to the controller
„
Auto-negotiation to automatically determine the best speed and duplex possible
„
Management Control to read status registers and write control registers
T X _C LK
(fo r M II o n ly)
MAC
100M
PLL
E x t R e f_ C L K (fo r R M II o n ly)
M II 2 5 M h z b y 4 b its
or
R M II 5 0 M h z b y 2 b its
25M H z
b y 4 b its
M II
4 B /5 B
E n co d e r
25M H z by
5 b its
M L T -3
M a g n e tic s
S cra m b le r
a n d P IS O
1 2 5 M b p s S e ria l
NRZI
C o n ve rte r
NRZI
M L T -3
C o n ve rte r
Tx
D rive r
M L T -3
M L T -3
R J4 5
M L T -3
C A T -5
Figure 4.1 100Base-TX Data Path
4.2
100Base-TX Transmit
The data path of the 100Base-TX is shown in Figure 4.1. Each major block is explained below.
4.2.1
100M Transmit Data Across the MII/RMII
For MII, the MAC controller drives the transmit data onto the TXD bus and asserts TX_EN to indicate
valid data. The data is latched by the PHY’s MII block on the rising edge of TX_CLK. The data is in
the form of 4-bit wide 25MHz data.
The MAC controller drives the transmit data onto the TXD bus and asserts TX_EN to indicate valid
data. The data is latched by the PHY’s MII block on the rising edge of REF_CLK. The data is in the
form of 2-bit wide 50MHz data.
4.2.2
4B/5B Encoding
The transmit data passes from the MII block to the 4B/5B encoder. This block encodes the data from
4-bit nibbles to 5-bit symbols (known as “code-groups”) according to Table 4.1. Each 4-bit data-nibble
is mapped to 16 of the 32 possible code-groups. The remaining 16 code-groups are either used for
control information or are not valid.
The first 16 code-groups are referred to by the hexadecimal values of their corresponding data nibbles,
0 through F. The remaining code-groups are given letter designations with slashes on either side. For
example, an IDLE code-group is /I/, a transmit error code-group is /H/, etc.
Revision 0.6 (02-24-06)
18
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
The encoding process may be bypassed by clearing bit 6 of register 31. When the encoding is
bypassed the 5th transmit data bit is equivalent to TX_ER.
Note that encoding can be bypassed only when the MAC interface is configured to operate in MII
mode.
Table 4.1 4B/5B Code Table
CODE
GROUP
SYM
RECEIVER
INTERPRETATION
11110
0
0
0000
01001
1
1
10100
2
10101
TRANSMITTER
INTERPRETATION
0
0000
0001
1
0001
2
0010
2
0010
3
3
0011
3
0011
01010
4
4
0100
4
0100
01011
5
5
0101
5
0101
01110
6
6
0110
6
0110
01111
7
7
0111
7
0111
10010
8
8
1000
8
1000
10011
9
9
1001
9
1001
10110
A
A
1010
A
1010
10111
B
B
1011
B
1011
11010
C
C
1100
C
1100
11011
D
D
1101
D
1101
11100
E
E
1110
E
1110
11101
F
F
1111
F
1111
11111
I
IDLE
Sent after /T/R until TX_EN
11000
J
First nibble of SSD, translated to “0101”
following IDLE, else RX_ER
Sent for rising TX_EN
10001
K
Second nibble of SSD, translated to
“0101” following J, else RX_ER
Sent for rising TX_EN
01101
T
First nibble of ESD, causes de-assertion
of CRS if followed by /R/, else assertion
of RX_ER
Sent for falling TX_EN
00111
R
Second nibble of ESD, causes
deassertion of CRS if following /T/, else
assertion of RX_ER
Sent for falling TX_EN
00100
H
Transmit Error Symbol
Sent for rising TX_ER
00110
V
INVALID, RX_ER if during RX_DV
INVALID
11001
V
INVALID, RX_ER if during RX_DV
INVALID
00000
V
INVALID, RX_ER if during RX_DV
INVALID
00001
V
INVALID, RX_ER if during RX_DV
INVALID
SMSC LAN8187/LAN8187I
DATA
19
DATASHEET
DATA
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 4.1 4B/5B Code Table (continued)
CODE
GROUP
SYM
00010
V
INVALID, RX_ER if during RX_DV
INVALID
00011
V
INVALID, RX_ER if during RX_DV
INVALID
00101
V
INVALID, RX_ER if during RX_DV
INVALID
01000
V
INVALID, RX_ER if during RX_DV
INVALID
01100
V
INVALID, RX_ER if during RX_DV
INVALID
10000
V
INVALID, RX_ER if during RX_DV
INVALID
4.2.3
RECEIVER
INTERPRETATION
TRANSMITTER
INTERPRETATION
Scrambling
Repeated data patterns (especially the IDLE code-group) can have power spectral densities with large
narrow-band peaks. Scrambling the data helps eliminate these peaks and spread the signal power
more uniformly over the entire channel bandwidth. This uniform spectral density is required by FCC
regulations to prevent excessive EMI from being radiated by the physical wiring.
The seed for the scrambler is generated from the PHY address, PHYAD[4:0], ensuring that in multiplePHY applications, such as repeaters or switches, each PHY will have its own scrambler sequence.
The scrambler also performs the Parallel In Serial Out conversion (PISO) of the data.
4.2.4
NRZI and MLT3 Encoding
The scrambler block passes the 5-bit wide parallel data to the NRZI converter where it becomes a
serial 125MHz NRZI data stream. The NRZI is encoded to MLT-3. MLT3 is a tri-level code where a
change in the logic level represents a code bit “1” and the logic output remaining at the same level
represents a code bit “0”.
4.2.5
100M Transmit Driver
The MLT3 data is then passed to the analog transmitter, which drives the differential MLT-3 signal, on
outputs TXP and TXN, to the twisted pair media across a 1:1 ratio isolation transformer. The 10BaseT and 100Base-TX signals pass through the same transformer so that common “magnetics” can be
used for both. The transmitter drives into the 100Ω impedance of the CAT-5 cable. Cable termination
and impedance matching require external components.
4.2.6
100M Phase Lock Loop (PLL)
The 100M PLL locks onto reference clock and generates the 125MHz clock used to drive the 125 MHz
logic and the 100Base-Tx Transmitter.
Revision 0.6 (02-24-06)
20
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
RX_CLK
(for MII only)
MAC
100M
PLL
Ext Ref_CLK (for RMII only)
MII 25Mhz by 4 bits
or
RMII 50Mhz by 2 bits
25MHz
by 4 bits
MII/RMII
4B/5B
Decoder
25MHz by
5 bits
Descrambler
and SIPO
125 Mbps Serial
NRZI
Converter
A/D
Converter
NRZI
MLT-3
MLT-3
Converter
Magnetics
DSP: Timing
recovery, Equalizer
and BLW Correction
MLT-3
RJ45
MLT-3
MLT-3
CAT-5
6 bit Data
Figure 4.2 Receive Data Path
4.3
100Base-TX Receive
The receive data path is shown in Figure 4.2. Detailed descriptions are given below.
4.3.1
100M Receive Input
The MLT-3 from the cable is fed into the PHY (on inputs RXP and RXN) via a 1:1 ratio transformer.
The ADC samples the incoming differential signal at a rate of 125M samples per second. Using a 64level quanitizer it generates 6 digital bits to represent each sample. The DSP adjusts the gain of the
ADC according to the observed signal levels such that the full dynamic range of the ADC can be used.
4.3.2
Equalizer, Baseline Wander Correction and Clock and Data Recovery
The 6 bits from the ADC are fed into the DSP block. The equalizer in the DSP section compensates
for phase and amplitude distortion caused by the physical channel consisting of magnetics, connectors,
and CAT- 5 cable. The equalizer can restore the signal for any good-quality CAT-5 cable between 1m
and 150m.
If the DC content of the signal is such that the low-frequency components fall below the low frequency
pole of the isolation transformer, then the droop characteristics of the transformer will become
significant and Baseline Wander (BLW) on the received signal will result. To prevent corruption of the
received data, the PHY corrects for BLW and can receive the ANSI X3.263-1995 FDDI TP-PMD
defined “killer packet” with no bit errors.
The 100M PLL generates multiple phases of the 125MHz clock. A multiplexer, controlled by the timing
unit of the DSP, selects the optimum phase for sampling the data. This is used as the received
recovered clock. This clock is used to extract the serial data from the received signal.
4.3.3
NRZI and MLT-3 Decoding
The DSP generates the MLT-3 recovered levels that are fed to the MLT-3 converter. The MLT-3 is then
converted to an NRZI data stream.
SMSC LAN8187/LAN8187I
21
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
4.3.4
Descrambling
The descrambler performs an inverse function to the scrambler in the transmitter and also performs
the Serial In Parallel Out (SIPO) conversion of the data.
During reception of IDLE (/I/) symbols. the descrambler synchronizes its descrambler key to the
incoming stream. Once synchronization is achieved, the descrambler locks on this key and is able to
descramble incoming data.
Special logic in the descrambler ensures synchronization with the remote PHY by searching for IDLE
symbols within a window of 4000 bytes (40us). This window ensures that a maximum packet size of
1514 bytes, allowed by the IEEE 802.3 standard, can be received with no interference. If no IDLEsymbols are detected within this time-period, receive operation is aborted and the descrambler re-starts
the synchronization process.
The descrambler can be bypassed by setting bit 0 of register 31.
4.3.5
Alignment
The de-scrambled signal is then aligned into 5-bit code-groups by recognizing the /J/K/ Start-of-Stream
Delimiter (SSD) pair at the start of a packet. Once the code-word alignment is determined, it is stored
and utilized until the next start of frame.
4.3.6
5B/4B Decoding
The 5-bit code-groups are translated into 4-bit data nibbles according to the 4B/5B table. The
translated data is presented on the RXD[3:0] signal lines. The SSD, /J/K/, is translated to “0101 0101”
as the first 2 nibbles of the MAC preamble. Reception of the SSD causes the PHY to assert the RX_DV
signal, indicating that valid data is available on the RXD bus. Successive valid code-groups are
translated to data nibbles. Reception of either the End of Stream Delimiter (ESD) consisting of the /T/R/
symbols, or at least two /I/ symbols causes the PHY to de-assert carrier sense and RX_DV.
These symbols are not translated into data.
The decoding process may be bypassed by clearing bit 6 of register 31. When the decoding is
bypassed the 5th receive data bit is driven out on RX_ER/RXD4. Decoding may be bypassed only
when the MAC interface is in MII mode.
4.3.7
Receive Data Valid Signal
The Receive Data Valid signal (RX_DV) indicates that recovered and decoded nibbles are being
presented on the RXD[3:0] outputs synchronous to RX_CLK. RX_DV becomes active after the /J/K/
delimiter has been recognized and RXD is aligned to nibble boundaries. It remains active until either
the /T/R/ delimiter is recognized or link test indicates failure or SIGDET becomes false.
RX_DV is asserted when the first nibble of translated /J/K/ is ready for transfer over the Media
Independent Interface (MII).
CLEAR-TEXT
J
K
5
5
5
D
data
data
data
data
T
R
5
5
5
5
5
D
data
data
data
data
Idle
RX_CLK
RX_DV
RXD
Figure 4.3 Relationship Between Received Data and specific MII Signals
Revision 0.6 (02-24-06)
22
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
4.3.8
Receiver Errors
During a frame, unexpected code-groups are considered receive errors. Expected code groups are the
DATA set (0 through F), and the /T/R/ (ESD) symbol pair. When a receive error occurs, the RX_ER
signal is asserted and arbitrary data is driven onto the RXD[3:0] lines. Should an error be detected
during the time that the /J/K/ delimiter is being decoded (bad SSD error), RX_ER is asserted true and
the value ‘1110’ is driven onto the RXD[3:0] lines. Note that the Valid Data signal is not yet asserted
when the bad SSD error occurs.
4.3.9
100M Receive Data Across the MII/RMII Interface
In MII mode, the 4-bit data nibbles are sent to the MII block. These data nibbles are clocked to the
controller at a rate of 25MHz. The controller samples the data on the rising edge of RX_CLK. To ensure
that the setup and hold requirements are met, the nibbles are clocked out of the PHY on the falling
edge of RX_CLK. RX_CLK is the 25MHz output clock for the MII bus. It is recovered from the received
data to clock the RXD bus. If there is no received signal, it is derived from the system reference clock
(CLKIN).
When tracking the received data, RX_CLK has a maximum jitter of 0.8ns (provided that the jitter of the
input clock, CLKIN, is below 100ps).
In RMII mode, the 2-bit data nibbles are sent to the RMII block. These data nibbles are clocked to the
controller at a rate of 50MHz. The controller samples the data on the rising edge of CLKIN/XTAL1
(REF_CLK). To ensure that the setup and hold requirements are met, the nibbles are clocked out of
the PHY on the falling edge of CLKIN/XTAL1 (REF_CLK).
4.4
10Base-T Transmit
Data to be transmitted comes from the MAC layer controller. The 10Base-T transmitter receives 4-bit
nibbles from the MII at a rate of 2.5MHz and converts them to a 10Mbps serial data stream. The data
stream is then Manchester-encoded and sent to the analog transmitter, which drives a signal onto the
twisted pair via the external magnetics.
The 10M transmitter uses the following blocks:
4.4.1
„
MII (digital)
„
TX 10M (digital)
„
10M Transmitter (analog)
„
10M PLL (analog)
10M Transmit Data Across the MII/RMII Interface
The MAC controller drives the transmit data onto the TXD BUS. For MII, when the controller has driven
TX_EN high to indicate valid data, the data is latched by the MII block on the rising edge of TX_CLK.
The data is in the form of 4-bit wide 2.5MHz data.
In order to comply with legacy 10Base-T MAC/Controllers, in Half-duplex mode the PHY loops back
the transmitted data, on the receive path. This does not confuse the MAC/Controller since the COL
signal is not asserted during this time. The PHY also supports the SQE (Heartbeat) signal. See Section
5.4.2, "Collision Detect," on page 49, for more details.
For RMII, TXD[1:0] shall transition synchronously with respect to REF_CLK. When TX_EN is asserted,
TXD[1:0] are accepted for transmission by the LAN8187/LAN8187I. TXD[1:0] shall be “00” to indicate
idle when TX_EN is deasserted. Values of TXD[1:0] other than “00” when TX_EN is deasserted are
reserved for out-of-band signalling (to be defined). Values other than “00” on TXD[1:0] while TX_EN is
deasserted shall be ignored by the LAN8187/LAN8187I.TXD[1:0] shall provide valid data for each
REF_CLK period while TX_EN is asserted.
SMSC LAN8187/LAN8187I
23
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
4.4.2
Manchester Encoding
The 4-bit wide data is sent to the TX10M block. The nibbles are converted to a 10Mbps serial NRZI
data stream. The 10M PLL locks onto the external clock or internal oscillator and produces a 20MHz
clock. This is used to Manchester encode the NRZ data stream. When no data is being transmitted
(TX_EN is low), the TX10M block outputs Normal Link Pulses (NLPs) to maintain communications with
the remote link partner.
4.4.3
10M Transmit Drivers
The Manchester encoded data is sent to the analog transmitter where it is shaped and filtered before
being driven out as a differential signal across the TXP and TXN outputs.
4.5
10Base-T Receive
The 10Base-T receiver gets the Manchester- encoded analog signal from the cable via the magnetics.
It recovers the receive clock from the signal and uses this clock to recover the NRZI data stream. This
10M serial data is converted to 4-bit data nibbles which are passed to the controller across the MII at
a rate of 2.5MHz.
This 10M receiver uses the following blocks:
4.5.1
„
Filter and SQUELCH (analog)
„
10M PLL (analog)
„
RX 10M (digital)
„
MII (digital)
10M Receive Input and Squelch
The Manchester signal from the cable is fed into the PHY (on inputs RXP and RXN) via 1:1 ratio
magnetics. It is first filtered to reduce any out-of-band noise. It then passes through a SQUELCH
circuit. The SQUELCH is a set of amplitude and timing comparators that normally reject differential
voltage levels below 300mV and detect and recognize differential voltages above 585mV.
4.5.2
Manchester Decoding
The output of the SQUELCH goes to the RX10M block where it is validated as Manchester encoded
data. The polarity of the signal is also checked. If the polarity is reversed (local RXP is connected to
RXN of the remote partner and vice versa), then this is identified and corrected. The reversed condition
is indicated by the flag “XPOL“, bit 4 in register 27. The 10M PLL is locked onto the received
Manchester signal and from this, generates the received 20MHz clock. Using this clock, the
Manchester encoded data is extracted and converted to a 10MHz NRZI data stream. It is then
converted from serial to 4-bit wide parallel data.
The RX10M block also detects valid 10Base-T IDLE signals - Normal Link Pulses (NLPs) - to maintain
the link.
4.5.3
10M Receive Data Across the MII/RMII Interface
For MII, the 4 bit data nibbles are sent to the MII block. In MII mode, these data nibbles are valid on
the rising edge of the 2.5 MHz RX_CLK.
For RMII, the 2bit data nibbles are sent to the RMII block. In RMII mode, these data nibbles are valid
on the rising edge of the RMII REF_CLK.
Revision 0.6 (02-24-06)
24
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
4.5.4
Jabber Detection
Jabber is a condition in which a station transmits for a period of time longer than the maximum
permissible packet length, usually due to a fault condition, that results in holding the TX_EN input for
a long period. Special logic is used to detect the jabber state and abort the transmission to the line,
within 45ms. Once TX_EN is deasserted, the logic resets the jabber condition.
As shown in Table 5.31, bit 1.1 indicates that a jabber condition was detected.
4.6
MAC Interface
The MII/RMII block is responsible for the communication with the controller. Special sets of hand-shake
signals are used to indicate that valid received/transmitted data is present on the 4 bit receive/transmit
bus.
The device must be configured in MII or RMII mode. This is done by specific pin strapping
configurations.
See section Section 4.6.3, "MII vs. RMII Configuration," on page 26 for information on pin strapping
and how the pins are mapped differently.
4.6.1
MII
The MII includes 16 interface signals:
„
transmit data - TXD[3:0]
„
transmit strobe - TX_EN
„
transmit clock - TX_CLK
„
transmit error - TX_ER/TXD4
„
receive data - RXD[3:0]
„
receive strobe - RX_DV
„
receive clock - RX_CLK
„
receive error - RX_ER/RXD4
„
collision indication - COL
„
carrier sense - CRS
In MII mode, on the transmit path, the PHY drives the transmit clock, TX_CLK, to the controller. The
controller synchronizes the transmit data to the rising edge of TX_CLK. The controller drives TX_EN
high to indicate valid transmit data. The controller drives TX_ER high when a transmit error is detected.
On the receive path, the PHY drives both the receive data, RXD[3:0], and the RX_CLK signal. The
controller clocks in the receive data on the rising edge of RX_CLK when the PHY drives RX_DV high.
The PHY drives RX_ER high when a receive error is detected.
4.6.2
RMII
The SMSC LAN8187/LAN8187I supports the low pin count Reduced Media Independent Interface
(RMII) intended for use between Ethernet PHYs and Switch ASICs. Under IEEE 802.3, an MII
comprised of 16 pins for data and control is defined. In devices incorporating many MACs or PHY
interfaces such as switches, the number of pins can add significant cost as the port counts increase.
The management interface (MDIO/MDC) is identical to MII. The RMII interface has the following
characteristics:
„
It is capable of supporting 10Mb/s and 100Mb/s data rates
„
A single clock reference is sourced from the MAC to PHY (or from an external source)
„
It provides independent 2 bit wide (di-bit) transmit and receive data paths
SMSC LAN8187/LAN8187I
25
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
„
It uses LVCMOS signal levels, compatible with common digital CMOS ASIC processes
The RMII includes 6 interface signals with one of the signals being optional:
4.6.2.1
„
transmit data - TXD[1:0]
„
transmit strobe - TX_EN
„
receive data - RXD[1:0]
„
receive error - RX_ER (Optional)
„
carrier sense - CRS_DV
„
Reference Clock - CLKIN/XTAL1 (RMII references usually define this signal as REF_CLK)
Reference Clock
The Reference Clock - CLKIN, is a continuous clock that provides the timing reference for CRS_DV,
RXD[1:0], TX_EN, TXD[1:0], and RX_ER. The Reference Clock is sourced by the MAC or an external
source. Switch implementations may choose to provide REF_CLK as an input or an output depending
on whether they provide a REF_CLK output or rely on an external clock distribution device.
The “Reference Clock” frequency must be 50 MHz +/- 50 ppm with a duty cycle between 35% and
65% inclusive. The SMSC LAN8187/LAN8187I uses the “Reference Clock” as the network clock such
that no buffering is required on the transmit data path. The SMSC LAN8187/LAN8187I will recover the
clock from the incoming data stream, the receiver will account for differences between the local
REF_CLK and the recovered clock through use of sufficient elasticity buffering. The elasticity buffer
does not affect the Inter-Packet Gap (IPG) for received IPGs of 36 bits or greater. To tolerate the clock
variations specified here for Ethernet MTUs, the elasticity buffer shall tolerate a minimum of +/-10 bits.
4.6.2.2
CRS_DV - Carrier Sense/Receive Data Valid
The CRS_DV is asserted by the LAN8187/LAN8187I when the receive medium is non-idle. CRS_DV
is asserted asynchronously on detection of carrier due to the criteria relevant to the operating mode.
That is, in 10BASE-T mode, when squelch is passed or in 100BASE-X mode when 2 non-contiguous
zeroes in 10 bits are detected, carrier is said to be detected.
Loss of carrier shall result in the deassertion of CRS_DV synchronous to the cycle of REF_CLK which
presents the first di-bit of a nibble onto RXD[1:0] (i.e. CRS_DV is deasserted only on nibble
boundaries). If the LAN8187/LAN8187I has additional bits to be presented on RXD[1:0] following the
initial deassertion of CRS_DV, then the LAN8187/LAN8187I shall assert CRS_DV on cycles of
REF_CLK which present the second di-bit of each nibble and de-assert CRS_DV on cycles of
REF_CLK which present the first di-bit of a nibble. The result is: Starting on nibble boundaries
CRS_DV toggles at 25 MHz in 100Mb/s mode and 2.5 MHz in 10Mb/s mode when CRS ends before
RX_DV (i.e. the FIFO still has bits to transfer when the carrier event ends.) Therefore, the MAC can
accurately recover RX_DV and CRS.
During a false carrier event, CRS_DV shall remain asserted for the duration of carrier activity. The data
on RXD[1:0] is considered valid once CRS_DV is asserted. However, since the assertion of CRS_DV
is asynchronous relative to REF_CLK, the data on RXD[1:0] shall be “00” until proper receive signal
decoding takes place.
4.6.3
MII vs. RMII Configuration
The LAN8187/LAN8187I must be configured to support the MII or RMII bus for connectivity to the
MAC. This configuration is done through the GPO0/MII pin.
MII or RMII mode selection is latched on the rising edge of the internal reset (nreset) based on the
strapping of the GPO0/MII pin. To select MII mode, float the GPO0/MII pin. To select RMII mode, pullhigh with an external resistor (see Table 4.3, “Boot Strapping Configuration Resistors,” on page 32) to
VDD33.
Revision 0.6 (02-24-06)
26
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Most of the MII and RMII pins are multiplexed. Table 4.2, "MII/RMII Signal Mapping", shown below,
describes the relationship of the related device pins to what pins are used in MII and RMII mode.
Table 4.2 MII/RMII Signal Mapping
4.7
SIGNAL NAME
MII MODE
RMII MODE
TXD0
TXD0
TXD0
TXD1
TXD1
TXD1
TX_EN
TX_EN
TX_EN
RX_ER/
RXD4
RX_ER/
RXD4/
RX_ER
Note 4.2
COL/CRS_DV
COL
CRS_DV
RXD0
RXD0
RXD0
RXD1
RXD1
RXD1
TXD2
TXD2
Note 4.1
TXD3
TXD3
Note 4.1
TX_ER/
TXD4
TX_ER/
TXD4
CRS
CRS
RX_DV
RX_DV
RXD2
RXD2
RXD3
RXD3
TX_CLK
TX_CLK
RX_CLK
RX_CLK
CLKIN/XTAL1
CLKIN/XTAL1
REF_CLK
Note 4.1
In RMII mode, this pin needs to tied to VSS.
Note 4.2
The RX_ER signal is optional on the RMII bus. This signal is required by the PHY, but it
is optional for the MAC. The MAC can choose to ignore or not use this signal.
Auto-negotiation
The purpose of the Auto-negotiation function is to automatically configure the PHY to the optimum link
parameters based on the capabilities of its link partner. Auto-negotiation is a mechanism for
exchanging configuration information between two link-partners and automatically selecting the highest
performance mode of operation supported by both sides. Auto-negotiation is fully defined in clause 28
of the IEEE 802.3 specification.
Once auto-negotiation has completed, information about the resolved link can be passed back to the
controller via the Serial Management Interface (SMI). The results of the negotiation process are
reflected in the Speed Indication bits in register 31, as well as the Link Partner Ability Register
(Register 5).
The auto-negotiation protocol is a purely physical layer activity and proceeds independently of the MAC
controller.
SMSC LAN8187/LAN8187I
27
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
The advertised capabilities of the PHY are stored in register 4 of the SMI registers. The default
advertised by the PHY is determined by user-defined on-chip signal options.
The following blocks are activated during an Auto-negotiation session:
„
Auto-negotiation (digital)
„
100M ADC (analog)
„
100M PLL (analog)
„
100M equalizer/BLW/clock recovery (DSP)
„
10M SQUELCH (analog)
„
10M PLL (analog)
„
10M Transmitter (analog)
When enabled, auto-negotiation is started by the occurrence of one of the following events:
„
Hardware reset
„
Software reset
„
Power-down reset
„
Link status down
„
Setting register 0, bit 9 high (auto-negotiation restart)
On detection of one of these events, the PHY begins auto-negotiation by transmitting bursts of Fast
Link Pulses (FLP). These are bursts of link pulses from the 10M transmitter. They are shaped as
Normal Link Pulses and can pass uncorrupted down CAT-3 or CAT-5 cable. A Fast Link Pulse Burst
consists of up to 33 pulses. The 17 odd-numbered pulses, which are always present, frame the FLP
burst. The 16 even-numbered pulses, which may be present or absent, contain the data word being
transmitted. Presence of a data pulse represents a “1”, while absence represents a “0”.
The data transmitted by an FLP burst is known as a “Link Code Word.” These are defined fully in IEEE
802.3 clause 28. In summary, the PHY advertises 802.3 compliance in its selector field (the first 5 bits
of the Link Code Word). It advertises its technology ability according to the bits set in register 4 of the
SMI registers.
There are 4 possible matches of the technology abilities. In the order of priority these are:
„
100M Full Duplex (Highest priority)
„
100M Half Duplex
„
10M Full Duplex
„
10M Half Duplex
If the full capabilities of the PHY are advertised (100M, Full Duplex), and if the link partner is capable
of 10M and 100M, then auto-negotiation selects 100M as the highest performance mode. If the link
partner is capable of Half and Full duplex modes, then auto-negotiation selects Full Duplex as the
highest performance operation.
Once a capability match has been determined, the link code words are repeated with the acknowledge
bit set. Any difference in the main content of the link code words at this time will cause auto-negotiation
to re-start. Auto-negotiation will also re-start if not all of the required FLP bursts are received.
The capabilities advertised during auto-negotiation by the PHY are initially determined by the logic
levels latched on the MODE[2:0] bus after reset completes. This bus can also be used to disable autonegotiation on power-up.
Writing register 4 bits [8:5] allows software control of the capabilities advertised by the PHY. Writing
register 4 does not automatically re-start auto-negotiation. Register 0, bit 9 must be set before the new
abilities will be advertised. Auto-negotiation can also be disabled via software by clearing register 0,
bit 12.
The LAN8187/LAN8187I does not support “Next Page” capability.
Revision 0.6 (02-24-06)
28
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
4.7.1
Parallel Detection
If the LAN8187/LAN8187I is connected to a device lacking the ability to auto-negotiate (i.e. no FLPs
are detected), it is able to determine the speed of the link based on either 100M MLT-3 symbols or
10M Normal Link Pulses. In this case the link is presumed to be Half Duplex per the IEEE standard.
This ability is known as “Parallel Detection.” This feature ensures interoperability with legacy link
partners. If a link is formed via parallel detection, then bit 0 in register 6 is cleared to indicate that the
Link Partner is not capable of auto-negotiation. The controller has access to this information via the
management interface. If a fault occurs during parallel detection, bit 4 of register 6 is set.
Register 5 is used to store the Link Partner Ability information, which is coded in the received FLPs.
If the Link Partner is not auto-negotiation capable, then register 5 is updated after completion of parallel
detection to reflect the speed capability of the Link Partner.
4.7.2
Re-starting Auto-negotiation
Auto-negotiation can be re-started at any time by setting register 0, bit 9. Auto-negotiation will also restart if the link is broken at any time. A broken link is caused by signal loss. This may occur because
of a cable break, or because of an interruption in the signal transmitted by the Link Partner. Autonegotiation resumes in an attempt to determine the new link configuration.
If the management entity re-starts Auto-negotiation by writing to bit 9 of the control register, the
LAN8187/LAN8187I will respond by stopping all transmission/receiving operations. Once the
break_link_timer is done, in the Auto-negotiation state-machine (approximately 1200ms) the autonegotiation will re-start. The Link Partner will have also dropped the link due to lack of a received
signal, so it too will resume auto-negotiation.
4.7.3
Disabling Auto-negotiation
Auto-negotiation can be disabled by setting register 0, bit 12 to zero. The device will then force its
speed of operation to reflect the information in register 0, bit 13 (speed) and register 0, bit 8 (duplex).
The speed and duplex bits in register 0 should be ignored when auto-negotiation is enabled.
4.7.4
Half vs. Full Duplex
Half Duplex operation relies on the CSMA/CD (Carrier Sense Multiple Access / Collision Detect)
protocol to handle network traffic and collisions. In this mode, the carrier sense signal, CRS, responds
to both transmit and receive activity. In this mode, If data is received while the PHY is transmitting,
a collision results.
In Full Duplex mode, the PHY is able to transmit and receive data simultaneously. In this mode, CRS
responds only to receive activity. The CSMA/CD protocol does not apply and collision detection is
disabled.
4.8
HP Auto-MDIX
HP Auto-MDIX facilitates the use of CAT-3 (10 Base-T) or CAT-5 (100 Base-T) media UTP interconnect
cable without consideration of interface wiring scheme. If a user plugs in either a direct connect LAN
cable, or a cross-over patch cable, as shown in Figure 4.4 on page 30, the SMSC LAN8187/LAN8187I
Auto-MDIX PHY is capable of configuring the TXP/TXN and RXP/RXN pins for correct transceiver
operation.
The internal logic of the device detects the TX and RX pins of the connecting device. Since the RX
and TX line pairs are interchangeable, special PCB design considerations are needed to accommodate
the symmetrical magnetics and termination of an Auto-MDIX design.
The Auto-MDIX function can be disabled through an internal register 27.15, or the external control pins
AMDIX_EN. When disabled the TX and RX pins can be configured with the Channel Select
(CH_SELECT) pin as desired.
SMSC LAN8187/LAN8187I
29
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Figure 4.4 Direct cable connection vs. Cross-over cable connection.
4.9
Internal +1.8V Regulator Disable
Part of the LAN8187/LAN8187I SMSC flexPWRTM technology is the ability to disable the internal +1.8v
regulator. This further increases the power savings as a more efficient external switching regulator can
provide the necessary +1.8v to the internal PHY circuitry.
4.9.1
Disable the Internal +1.8V Regulator
To disable the +1.8v internal regulator, a pulldown strapping resistor (see Table 4.3, “Boot Strapping
Configuration Resistors,” on page 32) is attached from REG_EN to VDDIO. When a reset event occurs,
the PHY will sample the REG_EN pin to determine if the internal regulator should turn on. If the pin
is grounded to VSS, then the internal regulator is off, and the system needs to supply +1.8v +/- 10%
to the VDD_CORE pin.
A 4.7uF low ESR and 0.1uF capacitor must be added to VDD_CORE and placed close to the PHY.
This capacitance provides decoupling of the external power supply noise and ensures stability of the
internal regulator.
4.9.2
Enable the Internal +1.8V Regulator
To enable the internal regulator, a pull-up resistor (see Table 4.3, “Boot Strapping Configuration
Resistors,” on page 32) to VDDIO needs to be added to the REG_EN pin.
A 4.7uF low ESR and 0.1uF capacitor must be added to VDD_CORE and placed close to the PHY.
This capacitance provides decoupling of the external power supply noise and ensures stability of the
internal regulator.
Note: For VDDIO operation below +2.5V, SMSC recommends designs add external strapping
resistors in addition the internal strapping resistors to ensure proper strapped operation.
4.10
(TX_ER/TXD4)/nINT Strapping
The TX_ER, TXD4 and nINT functions share a common pin. There are two functional modes for this
pin, the TX_ER/TXD4 mode and nINT (interrupt) mode. The RXD3 pin is used to select one of these
two functional modes.
Revision 0.6 (02-24-06)
30
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
The RXD3 pin is latched on the rising edge of the internal reset (nreset) to select the mode. The
system designer must float the RXD3 pin for nINT mode or pull-low with an external resistor (see
Table 4.3, “Boot Strapping Configuration Resistors,” on page 32) to VSS to set the device in
TX_ER/TXD4 mode. The default setting is high (nINT mode).
Note: For VDDIO operation below +2.5V, SMSC recommends designs add external strapping
resistors in addition the internal strapping resistors to ensure proper strapped operation.
4.11
PHY Address Strapping and LED Output Polarity Selection
The PHY ADDRESS bits are latched on the rising edge of the internal reset (nreset). The 5-bit address
word[0:4] is input on the LED1, LED2, LED3, LED4, GPO1 output pins. The default setting is all high
5'b1_1111.
The address lines are strapped as defined in the diagram below. The LED outputs will automatically
change polarity based on the presence of an external pull-down resistor. If the LED pin is pulled high
(by an internal 100K pull-up resistor) to select a logical high PHY address, then the LED output will
be active low. If the LED pin is pulled low (by an external pull-down resistor (see Table 4.3, “Boot
Strapping Configuration Resistors,” on page 32) to select a logical low PHY address, the LED output
will then be an active high output.
To set the PHY address on the LED pins without LEDs or on the GPO1 or CRS pin, float the pin to
set the address high or pull-down the pin with an external resistor (see Table 4.3, “Boot Strapping
Configuration Resistors,” on page 32) to GND to set the address low. See the figure below:
Phy Address = 0
LED output = active high
Phy Address = 1
LED output = active low
VDD
LED1-LED4
~10K ohms
~270 ohms
~270 ohms
LED1-LED4
Figure 4.5 PHY Address Strapping on LED’s
4.12
Variable Voltage I/O
The Digital I/O pins on the LAN8187/LAN8187I are variable voltage to take advantage of low power
savings from shrinking technologies. These pins can operate from a low I/O voltage of +1.6V up to
+3.6V. Due to this low voltage feature addition, the system designer needs to take consideration as
for two aspects of their design. Boot strapping configuration and I/O voltage stability.
SMSC LAN8187/LAN8187I
31
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
4.12.1
Boot Strapping Configuration.
Due to a lower I/O voltage, a lower strapping resistor needs to be used to ensure the strapped
configuration is latched into the PHY device at power-on reset.
Table 4.3 Boot Strapping Configuration Resistors
I/O voltage
Pull-up/Pull-down Resistor
3.0 to 3.6
10k ohm resistor
2.0 to 3.0
7.5k ohm resistor
1.6 to 2.0
5k ohm resistor
Note: For VDDIO operation below +2.5V, SMSC recommends designs add external strapping
resistors in addition the internal strapping resistors to ensure proper strapped operation.
4.12.2
I/O Voltage Stability
The I/O voltage the System Designer applies on VDDIO needs to maintain its value with a tolerance
of +/- 10%. Varying the voltage up or down, after the PHY has completed power-on reset can cause
errors in the PHY operation.
4.13
PHY Management Control
The Management Control module includes 3 blocks:
4.13.1
„
Serial Management Interface (SMI)
„
Management Registers Set
„
Interrupt
Serial Management Interface (SMI)
The Serial Management Interface is used to control the LAN8187/LAN8187I and obtain its status. This
interface supports registers 0 through 6 as required by Clause 22 of the 802.3 standard, as well as
“vendor-specific” registers 16 to 31 allowed by the specification. Non-supported registers (7 to 15) will
be read as hexadecimal “FFFF”.
At the system level there are 2 signals, MDIO and MDC where MDIO is bi-directional open-drain and
MDC is the clock.
A special feature (enabled by register 17 bit 3) forces the PHY to disregard the PHY-Address in the
SMI packet causing the PHY to respond to any address. This feature is useful in multi-PHY
applications and in production testing, where the same register can be written in all the PHYs using a
single write transaction.
The MDC signal is an aperiodic clock provided by the station management controller (SMC). The MDIO
signal receives serial data (commands) from the controller SMC, and sends serial data (status) to the
SMC. The minimum time between edges of the MDC is 160 ns. There is no maximum time between
edges.
The minimum cycle time (time between two consecutive rising or two consecutive falling edges) is 400
ns. These modest timing requirements allow this interface to be easily driven by the I/O port of a
microcontroller.
The data on the MDIO line is latched on the rising edge of the MDC. The frame structure and timing
of the data is shown in Figure 4.6 and Figure 4.7.
Revision 0.6 (02-24-06)
32
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
The timing relationships of the MDIO signals are further described in Section 6.1, "Serial Management
Interface (SMI) Timing," on page 53.
Read Cycle
...
...
MDC
MDI0
32 1's
Preamble
0
1
Start of
Frame
1
0
A4
OP
Code
A3
A2
A1
A0 R4 R3 R2 R1 R0
PHY Address
Register Address
D15
D14
Turn
Around
D1
D0
Data
Data From Phy
Data To Phy
Figure 4.6 MDIO Timing and Frame Structure - READ Cycle
Write Cycle
MDC
MDIO
32 1's
Preamble
0
1
Start of
Frame
0
1
OP
Code
A4
A3
A2
A1
A0
R4 R3 R2 R1 R0
PHY Address
Register Address
D15
D14
Turn
Around
...
...
D1
D0
Data
Data To Phy
Figure 4.7 MDIO Timing and Frame Structure - WRITE Cycle
SMSC LAN8187/LAN8187I
33
DATASHEET
Revision 0.6 (02-24-06)
Table 5.1 Control Register: Register 0 (Basic)
15
14
13
12
11
10
9
8
7
6
Rese
t
Loopbac
k
Speed
Select
A/N
Enable
Power
Down
Isolat
e
Restart A/N
Duplex
Mode
Collision
Test
5
4
3
2
1
0
Revision 0.6 (02-24-06)
Chapter 5 Registers
Reserved
15
14
13
12
11
100Bas
e-T4
100BaseTX
Full
Duplex
100BaseTX
Half
Duplex
10BaseT
Full
Duplex
10BaseT
Half
Duplex
10
9
8
7
6
Reserved
5
4
3
2
1
0
A/N
Complet
e
Remot
e
Fault
A/N
Abilit
y
Link
Statu
s
Jabbe
r
Detect
Extende
d
Capabilit
y
4
3
2
1
0
3
2
1
0
Table 5.3 PHY ID 1 Register: Register 2 (Extended)
15
14
13
12
11
10
9
8
7
6
5
34
DATASHEET
Table 5.2 Status Register: Register 1 (Basic)
PHY ID Number (Bits 3-18 of the Organizationally Unique Identifier - OUI)
15
14
13
12
11
10
PHY ID Number (Bits 19-24 of the Organizationally Unique
Identifier - OUI)
9
8
7
6
Manufacturer Model Number
5
4
Manufacturer Revision Number
SMSC LAN8187/LAN8187I
Table 5.4 PHY ID 2 Register: Register 3 (Extended)
14
13
12
11
10
9
8
7
6
5
4
Next
Page
Reserve
d
Remot
e
Fault
Reserve
d
Symmetric
Pause
Operation
Asymmetri
c
Pause
Operation
100BaseT4
100BaseTX
Full
Duplex
100BaseTX
10BaseT
Full
Duplex
10BaseT
3
2
1
0
IEEE 802.3 Selector
Field
Table 5.6 Auto-Negotiation Link Partner Base Page Ability Register: Register 5 (Extended)
15
14
13
Next
Page
Acknowled
ge
Remot
e
Fault
12
11
Reserved
10
9
8
7
6
5
4
Paus
e
100BaseT4
100Base-TX
Full Duplex
100BaseTX
10Base-T
Full
Duplex
10BaseT
3
2
1
0
IEEE 802.3 Selector Field
35
DATASHEET
Table 5.7 Auto-Negotiation Expansion Register: Register 6 (Extended)
15
14
13
12
11
10
9
8
7
6
5
Reserved
4
3
2
1
0
Parallel
Detect
Fault
Link
Partner
Next Page
Able
Next Page
Able
Page
Received
Link
Partner
A/N Able
Table 5.8 Auto-Negotiation Link Partner Next Page Transmit Register: Register 7 (Extended)
15
14
13
12
11
10
9
8
7
SMSC LAN8187/LAN8187I
Reserved
Note: Next Page capability is not supported.
6
5
4
3
2
1
0
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
15
Datasheet
Revision 0.6 (02-24-06)
Table 5.5 Auto-Negotiation Advertisement: Register 4 (Extended)
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
5
4
3
2
1
0
5
4
3
2
1
0
5
4
3
2
1
0
5
4
3
2
1
0
5
4
3
2
1
0
IEEE Reserved
Revision 0.6 (02-24-06)
Table 5.9 Register 8 (Extended)
Table 5.10 Register 9 (Extended)
15
14
13
12
11
10
9
8
7
6
IEEE Reserved
Table 5.11 Register 10 (Extended)
15
14
13
12
11
10
9
8
7
6
36
DATASHEET
IEEE Reserved
Table 5.12 Register 11 (Extended)
15
14
13
12
11
10
9
8
7
6
IEEE Reserved
15
14
13
12
11
10
9
8
7
6
IEEE Reserved
Table 5.14 Register 13 (Extended)
15
14
13
12
11
10
9
8
7
IEEE Reserved
6
SMSC LAN8187/LAN8187I
Table 5.13 Register 12 (Extended)
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
5
4
3
2
1
0
4
3
2
1
0
IEEE Reserved
Table 5.16 Register 15 (Extended)
15
14
13
12
11
10
9
8
7
6
IEEE Reserved
Table 5.17 Silicon Revision Register 16: Vendor-Specific
15
14
13
12
11
10
9
8
37
DATASHEET
Reserved
7
6
5
Silicon Revision
Reserved
Table 5.18 Mode Control/ Status Register 17: Vendor-Specific
15
14
13
12
11
10
9
8
7
Reserved
FASTRIP
EDPWRDOWN
Reserved
LOWSQEN
MDPREBP
FARLOOPBACK
FASTEST
6
5
Reserved
4
3
2
1
0
REFCLKEN
PHYADBP
Force
Good
Link
Status
ENERGYON
Reserved
Table 5.19 Special Modes Register 18: Vendor-Specific
SMSC LAN8187/LAN8187I
15
14
MIIMODE
13
12
11
10
9
8
CLKSELFREQ
DSPBP
SQBP
Reserved
PLLBP
ADCBP
7
6
MODE
5
4
3
2
PHYAD
1
0
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Revision 0.6 (02-24-06)
Table 5.15 Register 14 (Extended)
Revision 0.6 (02-24-06)
Table 5.20 Reserved Register 19: Vendor-Specific
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
5
4
3
2
1
0
5
4
3
2
1
0
5
4
3
2
1
0
Reserved
Table 5.21 Register 24: Vendor-Specific
15
14
13
12
11
10
9
8
7
6
Reserved
Table 5.22 Register 25: Vendor-Specific
15
14
13
12
11
10
9
8
7
6
38
DATASHEET
Reserved
Table 5.23 Register 26: Vendor-Specific
15
14
13
12
11
10
9
8
7
6
Reserved
Table 5.24 Special Control/Status Indications Register 27: Vendor-Specific
14
Reserved
13
12
11
10
9
8
7
6
5
4
SWRST_FA
ST
SQEOF
F
VCOOFF_L
P
Reserve
d
Reserve
d
Reserve
d
Reserve
d
Reserve
d
XPO
L
3
2
1
AUTONEGS
0
SMSC LAN8187/LAN8187I
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Reserved
Table 5.26 Interrupt Source Flags Register 29: Vendor-Specific
15
14
13
12
11
10
9
8
Reserved
7
6
5
4
3
2
1
0
INT7
INT6
INT5
INT4
INT3
INT2
INT1
Reserved
Table 5.27 Interrupt Mask Register 30: Vendor-Specific
39
DATASHEET
15
14
13
12
AMDIXCTR
L
Reserve
d
CH_SELEC
T
11
10
9
8
7
6
5
4
Reserved
3
2
1
0
Mask Bits
Table 5.28 PHY Special Control/Status Register 31: Vendor-Specific
15
14
13
12
Reserved
Reserved
Special
Autodone
11
10
Reserved
9
8
7
6
5
GPO2
GPO1
GPO0
Enable
4B5B
Reserved
4
3
Speed Indication
2
1
0
Reserved
Scramble
Disable
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
15
Datasheet
Revision 0.6 (02-24-06)
Table 5.25 Special Internal Testability Control Register 28: Vendor-Specific
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
5.1
SMI Register Mapping
The following registers are supported (register numbers are in decimal):
Table 5.29 SMI Register Mapping
REGISTER #
5.2
DESCRIPTION
Group
0
Basic Control Register
Basic
1
Basic Status Register
Basic
2
PHY Identifier 1
Extended
3
PHY Identifier 2
Extended
4
Auto-Negotiation Advertisement Register
Extended
5
Auto-Negotiation Link Partner Ability Register
Extended
6
Auto-Negotiation Expansion Register
Extended
16
Silicon Revision Register
Vendor-specific
17
Mode Control/Status Register
Vendor-specific
18
Special Modes
Vendor-specific
20
Reserved
Vendor-specific
21
Reserved
Vendor-specific
22
Reserved
Vendor-specific
23
Reserved
Vendor-specific
27
Control / Status Indication Register
Vendor-specific
28
Special internal testability controls
Vendor-specific
29
Interrupt Source Register
Vendor-specific
30
Interrupt Mask Register
Vendor-specific
31
PHY Special Control/Status Register
Vendor-specific
SMI Register Format
The mode key is as follows:
„
RW = read/write,
„
SC = self clearing,
„
WO = write only,
„
RO = read only,
„
LH = latch high, clear on read of register,
„
LL = latch low, clear on read of register,
„
NASR = Not Affected by Software Reset
Revision 0.6 (02-24-06)
40
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 5.30 Register 0 - Basic Control
ADDRESS
NAME
DESCRIPTION
MODE
DEFAULT
0.15
Reset
1 = software reset. Bit is self-clearing. For best results,
when setting this bit do not set other bits in this
register.
RW/
SC
0
0.14
Loopback
1 = loopback mode,
0 = normal operation
RW
0
0.13
Speed Select
1 = 100Mbps,
0 = 10Mbps.
Ignored if Auto Negotiation is enabled (0.12 = 1).
RW
Set by
MODE[2:0]
bus
0.12
AutoNegotiation
Enable
1 = enable auto-negotiate process
(overrides 0.13 and 0.8)
0 = disable auto-negotiate process
RW
Set by
MODE[2:0]
bus
0.11
Power Down
1 = General power down mode,
0 = normal operation
RW
0
0.10
Isolate
1 = electrical isolation of PHY from MII
0 = normal operation
RW
Set by
MODE[2:0]
bus
0.9
Restart AutoNegotiate
1 = restart auto-negotiate process
0 = normal operation. Bit is self-clearing.
RW/
SC
0
0.8
Duplex Mode
1 = Full duplex,
0 = Half duplex.
Ignored if Auto Negotiation is enabled (0.12 = 1).
RW
Set by
MODE[2:0]
bus
0.7
Collision Test
1 = enable COL test,
0 = disable COL test
RW
0
0.6:0
Reserved
RO
0
MODE
DEFAULT
1 = T4 able,
0 = no T4 ability
RO
0
Table 5.31 Register 1 - Basic Status
ADDRESS
NAME
1.15
100Base-T4
1.14
100Base-TX Full
Duplex
1 = TX with full duplex,
0 = no TX full duplex ability
RO
1
1.13
100Base-TX Half
Duplex
1 = TX with half duplex,
0 = no TX half duplex ability
RO
1
1.12
10Base-T Full
Duplex
1 = 10Mbps with full duplex
0 = no 10Mbps with full duplex ability
RO
1
1.11
10Base-T Half
Duplex
1 = 10Mbps with half duplex
0 = no 10Mbps with half duplex ability
RO
1
1.10:6
Reserved
1.5
Auto-Negotiate
Complete
1 = auto-negotiate process completed
0 = auto-negotiate process not completed
RO
0
1.4
Remote Fault
1 = remote fault condition detected
0 = no remote fault
RO/
LH
0
SMSC LAN8187/LAN8187I
DESCRIPTION
41
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 5.31 Register 1 - Basic Status (continued)
ADDRESS
NAME
1.3
Auto-Negotiate
Ability
1.2
Link Status
1.1
Jabber Detect
1.0
Extended
Capabilities
DESCRIPTION
MODE
DEFAULT
1 = able to perform auto-negotiation function
0 = unable to perform auto-negotiation function
RO
1
1 = link is up,
0 = link is down
RO/
LL
0
1 = jabber condition detected
0 = no jabber condition detected
RO/
LH
0
1 = supports extended capabilities registers
0 = does not support extended capabilities registers
RO
1
Table 5.32 Register 2 - PHY Identifier 1
ADDRESS
NAME
DESCRIPTION
MODE
DEFAULT
2.15:0
PHY ID Number
Assigned to the 3rd through 18th bits of the
Organizationally Unique Identifier (OUI), respectively.
OUI=00800Fh
RW
0007h
MODE
DEFAULT
Assigned to the 19th through 24th bits of the OUI.
RW
30h
Six-bit manufacturer’s model number.
RW
0Bh
Four-bit manufacturer’s revision number.
RW
1h
Table 5.33 Register 3 - PHY Identifier 2
ADDRESS
NAME
3.15:10
PHY ID Number
3.9:4
Model Number
3.3:0
Revision Number
DESCRIPTION
Table 5.34 Register 4 - Auto Negotiation Advertisement
ADDRESS
NAME
4.15
Next Page
4.14
Reserved
4.13
Remote Fault
4.12
Reserved
4.11:10
Pause Operation
4.9
100Base-T4
Revision 0.6 (02-24-06)
DESCRIPTION
MODE
DEFAULT
RO
0
RO
0
1 = remote fault detected,
0 = no remote fault
RW
0
00 = No PAUSE
01 = Asymmetric PAUSE toward link partner
10 = Symmetric PAUSE
11 = Both Symmetric PAUSE and Asymmetric
PAUSE toward local device
R/W
00
1 = T4 able,
0 = no T4 ability
This Phy does not support 100Base-T4.
RO
0
1 = next page capable,
0 = no next page ability
This Phy does not support next page ability.
42
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 5.34 Register 4 - Auto Negotiation Advertisement (continued)
ADDRESS
NAME
4.8
100Base-TX Full
Duplex
4.7
100Base-TX
4.6
10Base-T Full
Duplex
4.5
4.4:0
DESCRIPTION
MODE
DEFAULT
1 = TX with full duplex,
0 = no TX full duplex ability
RW
Set by
MODE[2:0]
bus
1 = TX able,
0 = no TX ability
RW
1
1 = 10Mbps with full duplex
0 = no 10Mbps with full duplex ability
RW
Set by
MODE[2:0]
bus
10Base-T
1 = 10Mbps able,
0 = no 10Mbps ability
RW
Set by
MODE[2:0]
bus
Selector Field
[00001] = IEEE 802.3
RW
00001
Table 5.35 Register 5 - Auto Negotiation Link Partner Ability
ADDRESS
NAME
5.15
Next Page
5.14
MODE
DEFAULT
1 = “Next Page” capable,
0 = no “Next Page” ability
This Phy does not support next page ability.
RO
0
Acknowledge
1 = link code word received from partner
0 = link code word not yet received
RO
0
5.13
Remote Fault
1 = remote fault detected,
0 = no remote fault
RO
0
5.12:11
Reserved
RO
0
5.10
Pause Operation
1 = Pause Operation is supported by remote MAC,
0 = Pause Operation is not supported by remote MAC
RO
0
5.9
100Base-T4
1 = T4 able,
0 = no T4 ability.
This Phy does not support T4 ability.
RO
0
5.8
100Base-TX Full
Duplex
1 = TX with full duplex,
0 = no TX full duplex ability
RO
0
5.7
100Base-TX
1 = TX able,
0 = no TX ability
RO
0
5.6
10Base-T Full
Duplex
1 = 10Mbps with full duplex
0 = no 10Mbps with full duplex ability
RO
0
5.5
10Base-T
1 = 10Mbps able,
0 = no 10Mbps ability
RO
0
5.4:0
Selector Field
[00001] = IEEE 802.3
RO
00001
SMSC LAN8187/LAN8187I
DESCRIPTION
43
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 5.36 Register 6 - Auto Negotiation Expansion
ADDRESS
NAME
DESCRIPTION
MODE
DEFAULT
6.15:5
Reserved
RO
0
6.4
Parallel Detection
Fault
1 = fault detected by parallel detection logic
0 = no fault detected by parallel detection logic
RO/
LH
0
6.3
Link Partner Next
Page Able
1 = link partner has next page ability
0 = link partner does not have next page ability
RO
0
6.2
Next Page Able
1 = local device has next page ability
0 = local device does not have next page ability
RO
0
6.1
Page Received
1 = new page received
0 = new page not yet received
RO/
LH
0
6.0
Link Partner AutoNegotiation Able
1 = link partner has auto-negotiation ability
0 = link partner does not have auto-negotiation ability
RO
0
MODE
DEFAULT
RO
0
RO
0001
RO
0
MODE
DEFAULT
RW
0
RW,
NASR
0
Enable the Energy Detect Power-Down mode:
0 = Energy Detect Power-Down is disabled
1 = Energy Detect Power-Down is enabled
RW
0
Write as 0, ignore on read
RW
0
Table 5.37 Register 16 - Silicon Revision
ADDRESS
NAME
DESCRIPTION
16.15:10
Reserved
16.9:6
Silicon Revision
16.5:0
Reserved
Four-bit silicon revision identifier.
Table 5.38 Register 17 - Mode Control/Status
ADDRESS
NAME
17.15
Reserved
Write as 0; ignore on read.
17.14
FASTRIP
10Base-T fast mode:
0 = normal operation
1 = Reserved
Must be left at 0
17.13
EDPWRDOWN
17.12
Reserved
17.11
LOWSQEN
The Low_Squelch signal is equal to LOWSQEN AND
EDPWRDOWN.
Low_Squelch = 1 implies a lower threshold
(more sensitive).
Low_Squelch = 0 implies a higher threshold
(less sensitive).
RW
0
17.10
MDPREBP
Management Data Preamble Bypass:
0 – detect SMI packets with Preamble
1 – detect SMI packets without preamble
RW
0
Revision 0.6 (02-24-06)
DESCRIPTION
44
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 5.38 Register 17 - Mode Control/Status (continued)
ADDRESS
NAME
DESCRIPTION
MODE
DEFAULT
17.9
FARLOOPBACK
Force the module to the FAR Loop Back mode, i.e. all
the received packets are sent back simultaneously (in
100Base-TX only). This bit is only active in RMII
mode. In this mode the user needs to supply a 50MHz
clock to the PHY. This mode works even if MII Isolate
(0.10) is set.
RW
0
17.8
FASTEST
Auto-Negotiation Test Mode
0 = normal operation
1 = activates test mode
RW
0
17.7:5
Reserved
Write as 0, ignore on read.
17.4
REFCLKEN
1= Enables special filtering using a 50 MHz Clock in
10Base-T mode.
RW
0
17.3
PHYADBP
1 = PHY disregards PHY address in SMI access
write.
RW
0
17.2
Force
Good Link Status
0 = normal operation;
1 = force 100TX- link active;
RW
0
ENERGYON – indicates whether energy is detected
on the line (see Section 5.4.5.2, "Energy Detect
Power-Down," on page 50); it goes to “0” if no valid
energy is detected within 256ms. Reset to “1” by
hardware reset, unaffected by SW reset.
RO
1
Write as “0”. Ignore on read.
RW
0
MODE
DEFAULT
Note:
17.1
ENERGYON
17.0
Reserved
This bit should be set only during lab testing
Table 5.39 Register 18 - Special Modes
ADDRESS
NAME
18.15:14
MIIMODE
18.13
CLKSELFREQ
18.12
DESCRIPTION
MII Mode: set the mode of the MII:
0 – MII interface.
1 – RMII interface
RW,
NASR
Clock In Selected Frequency. Set the requested input
clock frequency. This bit drives signal that goes to
external logic of the Phy and select the desired
frequency of the input clock:
0 – the clock frequency is 25MHz
1 – Reserved
RO,
NASR
DSPBP
DSP Bypass mode. Used only in special lab tests.
RW,
NASR
0
18.11
SQBP
SQUELCH Bypass mode.
RW,
NASR
0
18.10
Reserved
18.9
PLLBP
PLL Bypass mode.
RW,
NASR
18.8
ADCBP
ADC Bypass mode.
RW,
NASR
SMSC LAN8187/LAN8187I
RW,
NASR
45
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 5.39 Register 18 - Special Modes (continued)
ADDRESS
NAME
DESCRIPTION
MODE
DEFAULT
18.7:5
MODE
PHY Mode of operation. Refer to Section 5.4.9.2,
"Mode Bus – MODE[2:0]," on page 51 for more
details.
RW,
NASR
18.4:0
PHYAD
PHY Address.
The PHY Address is used for the SMI address and for
the initialization of the Cipher (Scrambler) key. Refer
to Section 5.4.9.1, "Physical Address Bus PHYAD[4:0]," on page 51 for more details.
RW,
NASR
PHYAD
Table 5.40 Register 27 - Special Control/Status Indications
ADDRESS
NAME
DESCRIPTION
MODE
DEFAULT
27.15
AMDIXCTRL
HP Auto-MDIX control
0 - Auto-MDIX enable
1 - Auto-MDIX disabled (use 27.13 to control channel)
RW
0
27.14
Reserved
Reserved
RW
0
27.13
CH_SELECT
Manual Channel Select
0 - MDI -TX transmits RX receives
1 - MDIX -TX receives RX transmits
RW
0
27.12
SWRST_FAST
1 = Accelerates SW reset counter from 256 ms to 10
us for production testing.
RW
0
27:11
SQEOFF
Disable the SQE test (Heartbeat):
0 - SQE test is enabled.
1 - SQE test is disabled.
RW,
NASR
0
27:10
VCOOFF_LP
Forces the Receive PLL 10M to lock on the reference
clock at all times:
0 - Receive PLL 10M can lock on reference or line as
needed (normal operation)
1 - Receive PLL 10M is locked on the reference clock.
In this mode 10M data packets cannot be received.
RW,
NASR
0
27.9
Reserved
Write as 0. Ignore on read.
RW
0
27.8
Reserved
Write as 0. Ignore on read.
RW
0
27.7
Reserved
Write as 0. Ignore on read
RW
0
27.6
Reserved
Write as 0. Ignore on read.
RW
0
27.5
Reserved
Write as 0. Ignore on read.
RW
27.4
XPOL
Polarity state of the 10Base-T:
0 - Normal polarity
1 - Reversed polarity
RO
0
27.3:0
AUTONEGS
Auto-negotiation “ARB” State-machine state
RO
1011b
MODE
DEFAULT
RW
N/A
Table 5.41 Register 28 - Special Internal Testability Controls
ADDRESS
NAME
28.15:0
Reserved
Revision 0.6 (02-24-06)
DESCRIPTION
Do not write to this register. Ignore on read.
46
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 5.42 Register 29 - Interrupt Source Flags
ADDRESS
NAME
29.15:8
Reserved
29.7
DESCRIPTION
MODE
DEFAULT
Ignore on read.
RO/
LH
0
INT7
1 = ENERGYON generated
0 = not source of interrupt
RO/
LH
0
29.6
INT6
1 = Auto-Negotiation complete
0 = not source of interrupt
RO/
LH
0
29.5
INT5
1 = Remote Fault Detected
0 = not source of interrupt
RO/
LH
0
29.4
INT4
1 = Link Down (link status negated)
0 = not source of interrupt
RO/
LH
0
29.3
INT3
1 = Auto-Negotiation LP Acknowledge
0 = not source of interrupt
RO/
LH
0
29.2
INT2
1 = Parallel Detection Fault
0 = not source of interrupt
RO/
LH
0
29.1
INT1
1 = Auto-Negotiation Page Received
0 = not source of interrupt
RO/
LH
0
29.0
Reserved
Ignore on read.
RO/
LH
0
MODE
DEFAULT
Table 5.43 Register 30 - Interrupt Mask
ADDRESS
NAME
DESCRIPTION
30.15:8
Reserved
Write as 0; ignore on read.
RO
0
30.7:0
Mask Bits
1 = interrupt source is enabled
0 = interrupt source is masked
RW
0
MODE
DEFAULT
Do not write to this register. Ignore on read.
RW
0
Must be set to 0
RW
0
Auto-negotiation done indication:
0 = Auto-negotiation is not done or disabled (or not
active)
1 = Auto-negotiation is done
RO
0
Table 5.44 Register 31 - PHY Special Control/Status
ADDRESS
NAME
31.15
Reserved
31.14
Reserved
31.13
Special
31.12
Autodone
SMSC LAN8187/LAN8187I
DESCRIPTION
47
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 5.44 Register 31 - PHY Special Control/Status (continued)
ADDRESS
NAME
31.11
MII_CLK_SEL
DESCRIPTION
MII Mode:
0 = MII Clock of 25MHz. (Default)
1 = Can be written in MII mode to set the interface
speed to 50MHz.
RMII Mode:
0 = Invalid (Do not clear this bit if in RMII mode)
1 = RMII Clock of 50 MHz (Default)
Note:
MODE
DEFAULT
RW
RMII/MII
mode
depnd’t
Defaults low (0) always in MII mode and high
always in RMII mode.
31.10
Reserved
Reserved
RW
0
31.9:7
GPO[2:0]
General Purpose Output connected to signals
GPO[2:0]
RW
0
31.6
Enable 4B5B
0 = Bypass encoder/decoder.
1 = enable 4B5B encoding/decoding.
MAC Interface must be configured in MII mode.
RW
1
31.5
Reserved
Write as 0, ignore on Read.
RW
0
31.4:2
Speed Indication
HCDSPEED value:
[001]=10Mbps Half-duplex
[101]=10Mbps Full-duplex
[010]=100Base-TX Half-duplex
[110]=100Base-TX Full-duplex
RO
000
31.1
Reserved
Write as 0; ignore on Read
RW
0
31.0
Scramble Disable
0 = enable data scrambling
1 = disable data scrambling,
RW
0
5.3
Interrupt Management
The Management interface supports an interrupt capability that is not a part of the IEEE 802.3
specification. It generates an active low interrupt signal on the nINT output whenever certain events
are detected. Reading the Interrupt Source register (Register 29) shows the source of the interrupt,
and clears the interrupt output signal. The Interrupt Mask register (Register 30) enables for each
source to set (LOW) the nINT, by asserting the corresponding mask bit. The Mask bit does not mask
the source bit in register 29. At reset, all bits are masked (negated). The nINT is an asynchronous
output.
INTERRUPT SOURCE
SOURCE/MASK REG BIT #
ENERGYON activated
7
Auto-Negotiate Complete
6
Remote Fault Detected
5
Link Status negated (not asserted)
4
Auto-Negotiation LP Acknowledge
3
Parallel Detection Fault
2
Auto-Negotiation Page Received
1
Revision 0.6 (02-24-06)
48
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
5.4
Miscellaneous Functions
5.4.1
Carrier Sense
The carrier sense is output on CRS. CRS is a signal defined by the MII specification in the IEEE 802.3u
standard. The PHY asserts CRS based only on receive activity whenever the PHY is either in repeater
mode or full-duplex mode. Otherwise the PHY asserts CRS based on either transmit or receive activity.
The carrier sense logic uses the encoded, unscrambled data to determine carrier activity status. It
activates carrier sense with the detection of 2 non-contiguous zeros within any 10 bit span. Carrier
sense terminates if a span of 10 consecutive ones is detected before a /J/K/ Start-of Stream Delimiter
pair. If an SSD pair is detected, carrier sense is asserted until either /T/R/ End–of-Stream Delimiter
pair or a pair of IDLE symbols is detected. Carrier is negated after the /T/ symbol or the first IDLE. If
/T/ is not followed by /R/, then carrier is maintained. Carrier is treated similarly for IDLE followed by
some non-IDLE symbol.
5.4.2
Collision Detect
A collision is the occurrence of simultaneous transmit and receive operations. The COL output is
asserted to indicate that a collision has been detected. COL remains active for the duration of the
collision. COL is changed asynchronously to both RX_CLK and TX_CLK. The COL output becomes
inactive during full duplex mode.
COL may be tested by setting register 0, bit 7 high. This enables the collision test. COL will be asserted
within 512 bit times of TX_EN rising and will be de-asserted within 4 bit times of TX_EN falling.
In 10M mode, COL pulses for approximately 10 bit times (1us), 2us after each transmitted packet (deassertion of TX_EN). This is the Signal Quality Error (SQE) signal and indicates that the transmission
was successful. The user can disable this pulse by setting bit 11 in register 27.
5.4.3
Isolate Mode
The PHY data paths may be electrically isolated from the MII by setting register 0, bit 10 to a logic
one. In isolation mode, the PHY does not respond to the TXD, TX_EN and TX_ER inputs. The PHY
still responds to management transactions.
Isolation provides a means for multiple PHYs to be connected to the same MII without contention
occurring. The PHY is not isolated on power-up (bit 0:10 = 0).
5.4.4
Link Integrity Test
The LAN8187/LAN8187I performs the link integrity test as outlined in the IEEE 802.3u (Clause 24-15)
Link Monitor state diagram. The link status is multiplexed with the 10Mbps link status to form the
reportable link status bit in Serial Management Register 1, and is driven to the LINK LED.
The DSP indicates a valid MLT-3 waveform present on the RXP and RXN signals as defined by the
ANSI X3.263 TP-PMD standard, to the Link Monitor state-machine, using internal signal called
DATA_VALID. When DATA_VALID is asserted the control logic moves into a Link-Ready state, and
waits for an enable from the Auto Negotiation block. When received, the Link-Up state is entered, and
the Transmit and Receive logic blocks become active. Should Auto Negotiation be disabled, the link
integrity logic moves immediately to the Link-Up state, when the DATA_VALID is asserted.
Note that to allow the line to stabilize, the link integrity logic will wait a minimum of 330 μsec from the
time DATA_VALID is asserted until the Link-Ready state is entered. Should the DATA_VALID input be
negated at any time, this logic will immediately negate the Link signal and enter the Link-Down state.
When the 10/100 digital block is in 10Base-T mode, the link status is from the 10Base-T receiver logic.
SMSC LAN8187/LAN8187I
49
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
5.4.5
Power-Down modes
There are 2 power-down modes for the Phy:
5.4.5.1
General Power-Down
This power-down is controlled by register 0, bit 11. In this mode the entire PHY, except the
management interface, is powered-down and stays in that condition as long as bit 0.11 is HIGH. When
bit 0.11 is cleared, the PHY powers up and is automatically reset.
5.4.5.2
Energy Detect Power-Down
This power-down mode is activated by setting bit 17.13 to 1. In this mode when no energy is present
on the line the PHY is powered down, except for the management interface, the SQUELCH circuit and
the ENERGYON logic. The ENERGYON logic is used to detect the presence of valid energy from
100Base-TX, 10Base-T, or Auto-negotiation signals
In this mode, when the ENERGYON signal is low, the PHY is powered-down, and nothing is
transmitted. When energy is received - link pulses or packets - the ENERGYON signal goes high, and
the PHY powers-up. It automatically resets itself into the state it had prior to power-down, and asserts
the nINT interrupt if the ENERGYON interrupt is enabled. The first and possibly the second packet
to activate ENERGYON may be lost.
When 17.13 is low, energy detect power-down is disabled.
5.4.6
Reset
The PHY has 3 reset sources:
Hardware reset (HWRST): connected to the nRST input, and to the internal POR signal.
If the nRST input is driven by an external source, it should be held LOW for at least 100 us to ensure
that the Phy is properly reset.
The Phy has an internal Power-On-Reset (POR) signal which is asserted for 21ms following a VDD33
(+3.3V) and VDDCORE (+1.8V) power-up. This internal POR is internally “OR”-ed with the nRST input.
During a Hardware reset, either external or POR, an external clock must be supplied to the CLKIN
signal.
Software (SW) reset: Activated by writing register 0, bit 15 high. This signal is self- clearing. After the
register-write, internal logic extends the reset by 256µs to allow PLL-stabilization before releasing the
logic from reset.
The IEEE 802.3u standard, clause 22 (22.2.4.1.1) states that the reset process should be completed
within 0.5s from the setting of this bit.
Power-Down reset: Automatically activated when the PHY comes out of power-down mode. The
internal power-down reset is extended by 256µs after exiting the power-down mode to allow the PLLs
to stabilize before the logic is released from reset.
These 3 reset sources are combined together in the digital block to create the internal “general reset”,
SYSRST, which is an asynchronous reset and is active HIGH. This SYSRST directly drives the PCS,
DSP and MII blocks. It is also input to the Central Bias block in order to generate a short reset for the
PLLs.
The SMI mechanism and registers are reset only by the Hardware and Software resets. During PowerDown, the SMI registers are not reset. Note that some SMI register bits are not cleared by Software
reset – these are marked “NASR” in the register tables.
For the first 16us after coming out of reset, the MII will run at 2.5 MHz. After that it will switch to 25
MHz if auto-negotiation is enabled.
Revision 0.6 (02-24-06)
50
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
5.4.7
LED Description
The PHY provides four LED signals. These provide a convenient means to determine the mode of
operation of the Phy. All LED signals are either active high or active low.
The four LED signals can be either active-high or active-low. Polarity depends upon the Phy address
latched in on reset. The LAN8187/LAN8187I senses each Phy address bit and changes the polarity of
the LED signal accordingly. If the address bit is set as level “1”, the LED polarity will be set to an activelow. If the address bit is set as level “0”, the LED polarity will be set to an active-high.
The ACTIVITY LED output is driven active when CRS is active (high). When CRS becomes inactive,
the Activity LED output is extended by 128ms.
The LINK LED output is driven active whenever the PHY detects a valid link. The use of the 10Mbps
or 100Mbps link test status is determined by the condition of the internally determined speed selection.
The SPEED100 LED output is driven active when the operating speed is 100Mbit/s or during Autonegotiation. This LED will go inactive when the operating speed is 10Mbit/s or during line isolation
(register 31 bit 5).
The Full-Duplex LED output is driven active low when the link is operating in Full-Duplex mode.
5.4.8
Loopback Operation
The 10/100 digital has two independent loop-back modes: Internal loopback and far loopback.
5.4.8.1
Internal Loopback
The internal loopback mode is enabled by setting bit register 0 bit 14 to logic one. In this mode, the
scrambled transmit data (output of the scrambler) is looped into the receive logic (input of the
descrambler). The COL signal will be inactive in this mode, unless collision test (bit 0.7) is active.
In this mode, during transmission (TX_EN is HIGH), nothing is transmitted to the line and the
transmitters are powered down.
5.4.9
Configuration Signals
The PHY has 11 configuration signals whose inputs should be driven continuously, either by external
logic or external pull-up/pull-down resistors.
5.4.9.1
Physical Address Bus - PHYAD[4:0]
The PHYAD[4:0] signals are driven high or low to give each PHY a unique address. This address is
latched into an internal register at end of hardware reset. In a multi-PHY application (such as a
repeater), the controller is able to manage each PHY via the unique address. Each PHY checks each
management data frame for a matching address in the relevant bits. When a match is recognized, the
PHY responds to that particular frame. The PHY address is also used to seed the scrambler. In a multiPHY application, this ensures that the scramblers are out of synchronization and disperses the
electromagnetic radiation across the frequency spectrum.
5.4.9.2
Mode Bus – MODE[2:0]
The MODE[2:0] bus controls the configuration of the 10/100 digital block.
SMSC LAN8187/LAN8187I
51
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 5.45 MODE[2:0] Bus
DEFAULT REGISTER BIT VALUES
MODE[2:0]
MODE DEFINITIONS
REGISTER 0
REGISTER 4
[13,12,10,8]
[8,7,6,5]
000
10Base-T Half Duplex. Auto-negotiation disabled.
0000
N/A
001
10Base-T Full Duplex. Auto-negotiation disabled.
0001
N/A
010
100Base-TX Half Duplex. Auto-negotiation
disabled.
CRS is active during Transmit & Receive.
1000
N/A
011
100Base-TX Full Duplex. Auto-negotiation disabled.
CRS is active during Receive.
1001
N/A
100
100Base-TX Half Duplex is advertised. Autonegotiation enabled.
CRS is active during Transmit & Receive.
1100
0100
101
Repeater mode. Auto-negotiation enabled.
100Base-TX Half Duplex is advertised.
CRS is active during Receive.
1100
0100
110
Power Down mode. In this mode the PHY wake-up
in Power-Down mode.
N/A
N/A
111
All capable. Auto-negotiation enabled.
X10X
1111
Revision 0.6 (02-24-06)
52
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Chapter 6 Electrical Characteristics
The timing diagrams and limits in this section define the requirements placed on the external signals
of the Phy.
6.1
Serial Management Interface (SMI) Timing
The Serial Management Interface is used for status and control as described in Section 4.13.
MDC
T1.1
T1.2
Valid Data
MDIO
(Read from PHY)
T1.3
T1.4
Valid Data
MDIO
(Write to PHY)
Figure 6.1 SMI Timing Diagram
Table 6.1 SMI Timing Values
PARAMETER
DESCRIPTION
MIN
T1.1
MDC minimum cycle time
400
T1.2
MDC to MDIO (Write) delay
0
T1.3
MDIO (Read) to MDC setup
10
ns
T1.4
MDIO (Read) to MDC hold
10
ns
SMSC LAN8187/LAN8187I
53
DATASHEET
TYP
MAX
UNITS
NOTES
ns
300
ns
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
6.2
MII 10/100Base-TX/RX Timings
6.2.1
MII 100Base-T TX/RX Timings
6.2.1.1
100M MII Receive Timing
RX_CLK
RXD[3:0]
RX_DV
RX_ER
Valid Data
T2.1
T2.2
Figure 6.2 100M MII Receive Timing Diagram
Table 6.2 100M MII Receive Timing Values
PARAMETER
DESCRIPTION
MIN
T2.1
Receive signals setup to RX_CLK
rising
10
ns
T2.2
Receive signals hold from
RX_CLK rising
10
ns
Revision 0.6 (02-24-06)
TYP
MAX
UNITS
RX_CLK frequency
25
MHz
RX_CLK Duty-Cycle
40
%
54
DATASHEET
NOTES
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
6.2.1.2
100M MII Transmit Timing
TX_CLK
TXD[3:0]
TX_EN
TX_ER
Valid Data
T3.1
T3.2
Figure 6.3 100M MII Transmit Timing Diagram
Table 6.3 100M MII Transmit Timing Values
PARAMETER
DESCRIPTION
MIN
TYP
MAX
UNITS
T3.1
Transmit signals setup to TX_CLK
rising
12
ns
T3.2
Transmit signals hold after
TX_CLK rising
0
ns
TX_CLK frequency
25
MHz
TX_CLK Duty-Cycle
40
%
6.2.2
MII 10Base-T TX/RX Timings
6.2.2.1
10M MII Receive Timing
NOTES
RX_CLK
RXD[3:0]
RX_DV
RX_ER
Valid Data
T4.1
T4.2
Figure 6.4 10M MII Receive Timing Diagram
SMSC LAN8187/LAN8187I
55
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 6.4 10M MII Receive Timing Values
PARAMETER
DESCRIPTION
MIN
TYP
MAX
UNITS
T4.1
Receive signals setup to RX_CLK
rising
10
ns
T4.2
Receive signals hold from RX_CLK
rising
10
ns
RX_CLK frequency
25
MHz
RX_CLK Duty-Cycle
40
%
Receive signals setup to RX_CLK
rising
6.2.2.2
10
NOTES
ns
10M MII Transmit Timing
TX_CLK
TXD[3:0]
TX_EN
Valid Data
T5.1
T5.2
Figure 6.5 10M MII Transmit Timing Diagrams
Table 6.5 10M MII Transmit Timing Values
PARAMETER
DESCRIPTION
MIN
T5.1
Transmit signals setup to
TX_CLK rising
T5.2
Transmit signals hold after
TX_CLK rising
Revision 0.6 (02-24-06)
TYP
MAX
12
UNITS
ns
0
ns
TX_CLK frequency
2.5
MHz
TX_CLK Duty-Cycle
50
%
56
DATASHEET
NOTES
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
6.3
RMII 10/100Base-TX/RX Timings
6.3.1
RMII 100Base-T TX/RX Timings
6.3.1.1
100M RMII Receive Timing
REF_CLK
RXD[1:0]
CRS_DV
Valid Data
T6.1
T6.2
Figure 6.6 100M RMII Receive Timing Diagram
Table 6.6 100M RMII Receive Timing Values
PARAMETER
DESCRIPTION
MIN
T6.1
Rising edge of REF_CLK to
receive signals output valid
T6.2
Rising edge of REF_CLK to
receive signals output not valid
TYP
2
REF_CLK frequency
SMSC LAN8187/LAN8187I
57
UNITS
4
ns
NOTES
ns
50
DATASHEET
MAX
MHz
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
6.3.1.2
100M RMII Transmit Timing
REF_CLK
TXD[1:0]
TX_EN
Valid Data
T8.1
T8.2
Figure 6.7 100M RMII Transmit Timing Diagram
Table 6.7 100M RMII Transmit Timing Values
PARAMETER
DESCRIPTION
MIN
T8.1
Transmit signals setup to rising
edge of REF_CLK
T8.2
Transmit signals hold after rising
edge of REF_CLK
TYP
MAX
UNITS
4
ns
2
REF_CLK frequency
50
6.3.2
RMII 10Base-T TX/RX Timings
6.3.2.1
10M RMII Receive Timing
NOTES
ns
MHz
REF_CLK
RXD[1:0]
CRS_DV
Valid Data
T9.1
T9.2
Figure 6.8 10M RMII Receive Timing Diagram
Revision 0.6 (02-24-06)
58
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 6.8 10M RMII Receive Timing Values
PARAMETER
DESCRIPTION
MIN
T9.1
Raising edge of REF_CLK to
receive signals output valid
T9.2
Raising edge of REF_CLK to
receive signals output not valid
TYP
UNITS
4
ns
2
NOTES
ns
REF_CLK frequency
6.3.2.2
MAX
50
MHz
10M RMII Transmit Timing
REF_CLK
TXD[1:0]
TX_EN
Valid Data
T10.1
T10.2
Figure 6.9 10M RMII Transmit Timing Diagram
Table 6.9 10M RMII Transmit Timing Values
PARAMETER
6.4
DESCRIPTION
T10.1
Transmit signals setup to
REF_CLK rising
T10.2
Transmit signals hold after
REF_CLK rising
MIN
TYP
MAX
4
UNITS
NOTES
ns
2
ns
REF_CLK Timing
Table 6.10 REF_CLK Timing Values
PARAMETER
DESCRIPTION
MIN
TYP
REF_CLK frequency
50
REF_CLK Frequency Drift
REF_CLK Duty Cycle
40
REF_CLK Jitter
SMSC LAN8187/LAN8187I
MAX
59
DATASHEET
UNITS
NOTES
MHz
+/- 50
ppm
60
%
150
psec
p-p – not RMS
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
6.5
Reset Timing
T6.1
nRST
T6.2
T6.3
Configuration signals
T6.4
Output drive
Figure 6.10 Reset Timing Diagram
Table 6.11 Reset Timing Values
PARAMETER
DESCRIPTION
MIN
TYP
MAX
UNITS
T6.1
Reset Pulse Width
100
us
T6.2
Configuration input setup to
nRST rising
200
ns
T6.3
Configuration input hold after
nRST rising
400
ns
T6.4
Output Drive after nRST rising
20
Revision 0.6 (02-24-06)
60
DATASHEET
800
ns
NOTES
20 clock cycles for
25 MHz clock
or
40 clock cycles for
50MHz clock
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
6.6
DC Characteristics
6.6.1
Operating Conditions
VDD33 Supply Voltage
+3.3V +/- 10%
VDDIO Supply Voltage
+1.6V to +3.6V
Operating Temperature
0°C to +70°C
Industrial Operating Temperature -40°C to +85°C version available (LAN8187I)
6.6.2
Power Consumption
6.6.2.1
Power Consumption Device Only
Power measurements taken over the operating conditions specified. See Section 5.4.5 for a description
of the power down modes.
Table 6.12 Power Consumption Device Only
3.3v CURRENT (mA)
MODE
1.8v CURRENT (mA)
I/O CURRENT (mA)
TOTAL (mA)
TYPICAL
MAX
TYPICAL
MAX
TYPICAL
MAX
TYPICAL
MAX
10BASE-T /w traffic
16
TBD
21
TBD
2
TBD
39
TBD
100BASE-TX /w traffic
34
TBD
38
TBD
7
TBD
79
TBD
0.04
TBD
2.6
TBD
0.06
TBD
2.7
TBD
Energy Detect Power Down
1. Current measurements do not include power applied to the magnetics.
2. Current measurements do not include power applied to the optional external LEDs.
3. Current measurements taken with VDDIO = +3.3V.
SMSC LAN8187/LAN8187I
61
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
6.6.3
DC Characteristics - Input and Output Buffers
Table 6.13 MII Bus Interface Signals
NAME
VIH
VIL
IOH
IOL
VOL
VOH
TXD0
VDDIO – +0.4 V
+0.5 V
TXD1
VDDIO – +0.4 V
+0.5 V
TXD2
VDDIO – +0.4 V
+0.5 V
TXD3
VDDIO – +0.4 V
+0.5 V
TX_EN
VDDIO – +0.4 V
+0.5 V
TX_CLK
-8 mA
+8 mA
+0.4 V
VDDIO – +0.4 V
RXD0
-8 mA
+8 mA
+0.4 V
VDDIO – +0.4 V
RXD1
-8 mA
+8 mA
+0.4 V
VDDIO – +0.4 V
RXD2
-8 mA
+8 mA
+0.4 V
VDDIO – +0.4 V
RXD3
-8 mA
+8 mA
+0.4 V
VDDIO – +0.4 V
RX_ER/RXD4
-8 mA
+8 mA
+0.4 V
VDDIO – +0.4 V
RX_DV
-8 mA
+8 mA
+0.4 V
VDDIO – +0.4 V
RX_CLK
-8 mA
+8 mA
+0.4 V
VDDIO – +0.4 V
CRS
-8 mA
+8 mA
+0.4 V
VDDIO – +0.4 V
COL
-8 mA
+8 mA
+0.4 V
VDDIO – +0.4 V
MDC
VDDIO – +0.4 V
+0.5 V
MDIO
VDDIO – +0.4 V
+0.5 V
-8 mA
+8 mA
+0.4 V
VDDIO – +0.4 V
nINT/TX_ER/TXD4
VDDIO – +0.4 V
+0.5 V
-8 mA
+8 mA
+0.4 V
3.6V
Revision 0.6 (02-24-06)
62
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 6.14 LAN Interface Signals
NAME
VIH
VIL
IOH
IOL
VOL
VOH
TXP
TXN
RXP
See Table 6.20, “100Base-TX Transceiver Characteristics,” on page 65 and Table 6.21,
“10BASE-T Transceiver Characteristics,” on page 65.
RXN
Table 6.15 LED Signals
NAME
VIH
VIL
IOH
IOL
VOL
VOH
SPEED100
VDDIO – +0.4 V
+0.5 V
-12 mA
+12 mA
+0.4 V
VDDIO – +0.4 V
LINK
VDDIO – +0.4 V
+0.5 V
-12 mA
+12 mA
+0.4 V
VDDIO – +0.4 V
ACTIVITY
VDDIO – +0.4 V
+0.5 V
-12 mA
+12 mA
+0.4 V
VDDIO – +0.4 V
FDUPLEX
VDDIO – +0.4 V
+0.5 V
-12 mA
+12 mA
+0.4 V
VDDIO – +0.4 V
Table 6.16 Configuration Inputs
NAME
VIH
VIL
IOH
IOL
VOL
VOH
PHYAD0
VDDIO – +0.4 V
+0.5 V
-12 mA
+12 mA
+0.4 V
VDDIO – +0.4 V
PHYAD1
VDDIO – +0.4 V
+0.5 V
-12 mA
+12 mA
+0.4 V
VDDIO – +0.4 V
PHYAD2
VDDIO – +0.4 V
+0.5 V
-12 mA
+12 mA
+0.4 V
VDDIO – +0.4 V
PHYAD3
VDDIO – +0.4 V
+0.5 V
-12 mA
+12 mA
+0.4 V
VDDIO – +0.4 V
-8 mA
+8 mA
+0.4 V
3.7 V
-8 mA
+8 mA
+0.4 V
VDDIO – +0.4 V
PHYAD4
MODE0
VDDIO – +0.4 V
+0.5 V
MODE1
VDDIO – +0.4 V
+0.5 V
MODE2
VDDIO – +0.4 V
+0.5 V
REG_EN
VDDIO – +0.4 V
+0.5 V
MII
SMSC LAN8187/LAN8187I
63
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 6.17 General Signals
NAME
VIH
VIL
IOH
IOL
VOL
VOH
GPO0
-8 mA
+8 mA
+0.4 V
VDDIO – +0.4 V
GPO1
-8 mA
+8 mA
+0.4 V
3.7 V
GPO2
-8 mA
+8 mA
+0.4 V
VDDIO – +0.4 V
nRST
VDDIO – +0.4 V
+0.5 V
CLKIN/XTAL1
Note 6.1
+1.40 V
+0.5 V
XTAL2
-
-
NC
These levels apply when a 0-3.3V Clock is driven into CLKIN/XTAL1 and XTAL2 is floating.
The maximum input voltage on XTAL1 is VDDIO + 0.4V.
Note 6.1
Table 6.18 Analog References
NAME
BUFFER TYPE
EXRES1
AI
NC
AI/O
VIH
VIL
IOH
IOL
VOL
VOH
Table 6.19 Internal Pull-Up / Pull-Down Configurations
NAME
PULL-UP OR PULL-DOWN
GPO0/MII
Pull-down
GPO1/PHYAD4
Pull-up
MODE0
Pull-up
MODE1
Pull-up
MODE2
Pull-up
TEST0
Pull-down
TEST1
Pull-down
SPEED100/PHYAD0
Pull-up
LINK/PHYAD1
Pull-up
ACTIVITY/PHYAD2
Pull-up
FDUPLEX//PHYAD3
Pull-up
nINT/TX_ER/TXD4
Pull-up
nRST
Pull-up
MDIO
Pull-down
MDC
Pull-down
Revision 0.6 (02-24-06)
64
DATASHEET
SMSC LAN8187/LAN8187I
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Table 6.19 Internal Pull-Up / Pull-Down Configurations
NAME
PULL-UP OR PULL-DOWN
RXD[3:0]
Pull-down
RX_DV
Pull-down
RX_CLK
Pull-down
RX_ER/RXD4
Pull-down
TXEN
Pull-down
COL
Pull-down
CRS
Pull-down
Note: For VDDIO operation below +2.5V, SMSC recommends designs add external strapping
resistors in addition the internal strapping resistors to ensure proper strapped operation.
Table 6.20 100Base-TX Transceiver Characteristics
PARAMETER
SYMBOL
MIN
TYP
MAX
UNITS
NOTES
Peak Differential Output Voltage High
VPPH
950
-
1050
mVpk
Note 6.2
Peak Differential Output Voltage Low
VPPL
-950
-
-1050
mVpk
Note 6.2
Signal Amplitude Symmetry
VSS
98
-
102
%
Note 6.2
Signal Rise & Fall Time
TRF
3.0
-
5.0
nS
Note 6.2
Rise & Fall Time Symmetry
TRFS
-
-
0.5
nS
Note 6.2
Duty Cycle Distortion
DCD
35
50
65
%
Note 6.3
Overshoot & Undershoot
VOS
-
-
5
%
1.4
nS
Jitter
Note 6.4
Note 6.2
Measured at the line side of the transformer, line replaced by 100Ω (+/- 1%) resistor.
Note 6.3
Offset from 16 nS pulse width at 50% of pulse peak
Note 6.4
Measured differentially.
Table 6.21 10BASE-T Transceiver Characteristics
PARAMETER
SYMBOL
MIN
TYP
MAX
UNITS
NOTES
Transmitter Peak Differential Output Voltage
VOUT
2.2
2.5
2.8
V
Note 6.5
Receiver Differential Squelch Threshold
VDS
300
420
585
mV
Note 6.5
SMSC LAN8187/LAN8187I
Min/max voltages guaranteed as measured with 100Ω resistive load.
65
DATASHEET
Revision 0.6 (02-24-06)
High-Performance MII and RMII 10/100 Ethernet PHY with HP Auto-MDIX
Datasheet
Chapter 7 Package Outline
Figure 7.1 64 Pin TQFP Package Outline, 10X10X1.4 Body, 12x12 mm Footprint
Table 7.1 64 Pin TQFP Package Parameters
MIN
NOMINAL
MAX
REMARKS
A
A1
A2
D
D1
E
E1
H
L
L1
e
~
0.05
1.35
11.80
9.80
11.80
9.80
0.09
0.45
~
1.60
0.15
1.45
12.20
10.20
12.20
10.20
0.20
0.75
~
θ
0o
~
~
~
~
~
~
~
~
0.60
1.00
0.50 Basic
~
7o
Overall Package Height
Standoff
Body Thickness
X Span
X body Size
Y Span
Y body Size
Lead Frame Thickness
Lead Foot Length
Lead Length
Lead Pitch
Lead Foot Angle
W
R
R2
ccc
0.17
0.08
0.08
~
0.22
~
~
~
0.27
~
0.20
0.08
Lead Width
Lead Shoulder Radius
Lead Foot Radius
Coplanarity
Notes:
1. Controlling Unit: millimeter.
2. Tolerance on the true position of the leads is ± 0.04 mm maximum.
3. Package body dimensions D1 and E1 do not include the mold protrusion.
Maximum mold protrusion is 0.25 mm per side.
4. Dimension for foot length L measured at the gauge plane 0.25 mm above the seating plane.
5. Details of pin 1 identifier are optional but must be located within the zone indicated.
Revision 0.6 (02-24-06)
66
DATASHEET
SMSC LAN8187/LAN8187I