转到网站首页
转为中文步骤：
1、请用电脑端360浏览器打开本页地址，如您电脑未安装360浏览器，请点这里下载;
2、点击360浏览器右上角的翻译插件，如右图红圈中所示:
3、点击所弹出窗口里的右下角的按钮 “翻译当前网页”;
4、弹窗提示翻译完毕后关闭弹窗即可；
Document Type: Data Sheet  
Document Stage: Release  
ICS1893  
3.3-V 10Base-T/100Base-TX Integrated PHYceiverä  
General  
Features  
The ICS1893 is a low-power, physical-layer device (PHY)  
that supports the ISO/IEC 10Base-T and 100Base-TX  
Carrier-Sense Multiple Access/Collision Detection  
(CSMA/CD) Ethernet standards. The ICS1893 architecture  
is based on the ICS1892. The ICS1893 supports managed  
or unmanaged node, repeater, and switch applications.  
• Supports category 5 cables with attenuation in excess of  
24 dB at 100 MHz across a temperature range from -5° to  
+85° C  
• DSP-based baseline wander correction to virtually  
eliminate killer packets across temperature range of from  
-5° to +85° C  
• Low-power, 0.35-micron CMOS (typically 400 mW)  
• Single 3.3-V power supply.  
The ICS1893 incorporates digital signal processing (DSP) in  
its Physical Medium Dependent (PMD) sublayer. As a result,  
it can transmit and receive data on unshielded twisted-pair  
(UTP) category 5 cables with attenuation in excess of 24 dB  
at 100 MHz. With this ICS-patented technology, the  
ICS1893 can virtually eliminate errors from killer packets.  
• Single-chip, fully integrated PHY provides PCS, PMA,  
PMD, and AUTONEG sublayers of IEEE standard  
• 10Base-T and 100Base-TX IEEE 802.3 compliant  
• Fully integrated, DSP-based PMD includes:  
– Adaptive equalization and baseline wander correction  
– Transmit wave shaping and stream cipher scrambler  
– MLT-3 encoder and NRZ/NRZI encoder  
The ICS1893 provides a Serial Management Interface for  
exchanging command and status information with a Station  
Management (STA) entity.  
• Highly configurable design supports:  
– Node, repeater, and switch applications  
– Managed and unmanaged applications  
– 10M or 100M half- and full-duplex modes  
– Parallel detection  
The ICS1893 Media Dependent Interface (MDI) can be  
configured to provide either half- or full-duplex operation at  
data rates of 10 MHz or 100 MHz. The MDI configuration  
can be established manually (with input pins or control  
register settings) or automatically (using the  
Auto-Negotiation features). W hen the ICS1893  
Auto-Negotiation sublayer is enabled, it exchanges  
technology capability data with its remote link partner and  
automatically selects the highest-performance operating  
mode they have in common.  
– Auto-negotiation, with Next Page capabilities  
• MAC/Repeater Interface can be configured as:  
– 10M or 100M Media Independent Interface  
– 100M Symbol Interface (bypasses the PCS)  
– 10M 7-wire Serial Interface  
• Small Footprint 64-pin Thin Quad Flat Pack (TQFP)  
Available in commercial and industrial temp ranges  
ICS1893 Block Diagram  
100Base-T  
PCS  
PMA  
TP_PMD  
•
•
Frame  
CRS/COL  
Detection  
Parallel to Serial  
4B/5B  
•
•
•
•
Clock Recovery  
Link Monitor  
Signal Detection  
Error Detection  
•
•
•
•
MLT-3  
10/100 MII or  
Alternate  
MAC/Repeater  
Interface  
Twisted-  
Pair  
Interface to  
Magnetics  
Modules and  
RJ45  
Interface  
MUX  
Integrated  
Switch  
Stream Cipher  
Adaptive Equalizer  
Baseline Wander  
Correction  
•
•
10Base-T  
Connector  
MII  
Low-Jitter  
Clock  
Synthesizer  
Auto-  
Negotiation  
Configuration  
and Status  
Extended  
Register  
Set  
MII Serial  
Management  
Interface  
Clock  
Power  
LEDs and PHY  
Address  
Table of Contents  
Section  
Title  
Page  
Revision History  
.............................................................................................................................9  
Chapter 1  
Chapter 2  
Chapter 3  
Abbreviations and Acronyms ......................................................................................... 11  
Conventions and Nomenclature..................................................................................... 13  
ICS1893 Enhanced Features........................................................................................... 15  
Chapter 4  
4.1  
Overview of the ICS1893.................................................................................................. 17  
100Base-TX Operation ..........................................................................................18  
4.2  
10Base-T Operation ...............................................................................................18  
Chapter 5  
5.1  
Operating Modes Overview.............................................................................................19  
Reset Operations ...................................................................................................20  
5.1.1  
5.1.2  
5.2  
5.3  
5.4  
5.5  
5.6  
5.7  
General Reset Operations .....................................................................................20  
Specific Reset Operations .....................................................................................21  
Power-Down Operations ........................................................................................22  
Automatic Power-Saving Operations .....................................................................23  
Auto-Negotiation Operations ..................................................................................23  
100Base-TX Operations ........................................................................................24  
10Base-T Operations .............................................................................................24  
Half-Duplex and Full-Duplex Operations ...............................................................24  
Chapter 6  
6.1  
Interface Overviews..........................................................................................................25  
MII Data Interface ..................................................................................................26  
6.2  
6.3  
6.4  
6.5  
6.5.1  
6.5.2  
6.6  
6.7  
6.8  
100M Symbol Interface ..........................................................................................27  
10M Serial Interface ...............................................................................................29  
Serial Management Interface .................................................................................31  
Twisted-Pair Interface ............................................................................................31  
Twisted-Pair Transmitter Interface .........................................................................32  
Twisted-Pair Receiver Interface .............................................................................33  
Clock Reference Interface .....................................................................................34  
Configuration Interface ...........................................................................................34  
Status Interface ......................................................................................................35  
Chapter 7  
7.1  
Functional Blocks............................................................................................................. 37  
Functional Block: Media Independent Interface .....................................................38  
7.2  
Functional Block: Auto-Negotiation ........................................................................39  
Auto-Negotiation General Process ........................................................................40  
Auto-Negotiation: Parallel Detection ......................................................................41  
Auto-Negotiation: Remote Fault Signaling .............................................................41  
Auto-Negotiation: Reset and Restart .....................................................................42  
Auto-Negotiation: Progress Monitor .......................................................................42  
7.2.1  
7.2.2  
7.2.3  
7.2.4  
7.2.5  
Table of Contents  
Section  
Title  
Page  
7.3  
Functional Block: 100Base-X PCS and PMA Sublayers ........................................44  
PCS Sublayer ........................................................................................................44  
PMA Sublayer ........................................................................................................44  
PCS/PMA Transmit Modules .................................................................................45  
PCS/PMA Receive Modules ..................................................................................46  
PCS Control Signal Generation .............................................................................47  
4B/5B Encoding/Decoding .....................................................................................47  
Functional Block: 100Base-TX TP-PMD Operations .............................................48  
100Base-TX Operation: Stream Cipher Scrambler/Descrambler ..........................48  
100Base-TX Operation: MLT-3 Encoder/Decoder .................................................48  
100Base-TX Operation: DC Restoration ................................................................48  
100Base-TX Operation: Adaptive Equalizer ..........................................................49  
100Base-TX Operation: Twisted-Pair Transmitter .................................................49  
100Base-TX Operation: Twisted-Pair Receiver .....................................................49  
100Base-TX Operation: Auto Polarity Correction ..................................................50  
100Base-TX Operation: Isolation Transformer ......................................................50  
Functional Block: 10Base-T Operations ................................................................51  
10Base-T Operation: Manchester Encoder/Decoder .............................................51  
10Base-T Operation: Clock Synthesis ...................................................................51  
10Base-T Operation: Clock Recovery ...................................................................51  
10Base-T Operation: Idle .......................................................................................52  
10Base-T Operation: Link Monitor .........................................................................52  
10Base-T Operation: Smart Squelch .....................................................................53  
10Base-T Operation: Carrier Detection .................................................................53  
10Base-T Operation: Collision Detection ...............................................................53  
10Base-T Operation: Jabber ..................................................................................54  
10Base-T Operation: SQE Test .............................................................................54  
10Base-T Operation: Twisted-Pair Transmitter .....................................................55  
10Base-T Operation: Twisted-Pair Receiver .........................................................55  
10Base-T Operation: Auto Polarity Correction .......................................................55  
10Base-T Operation: Isolation Transformer ...........................................................55  
Functional Block: Management Interface ...............................................................56  
Management Register Set Summary .....................................................................56  
Management Frame Structure ...............................................................................56  
7.3.1  
7.3.2  
7.3.3  
7.3.4  
7.3.5  
7.3.6  
7.4  
7.4.1  
7.4.2  
7.4.3  
7.4.4  
7.4.5  
7.4.6  
7.4.7  
7.4.8  
7.5  
7.5.1  
7.5.2  
7.5.3  
7.5.4  
7.5.5  
7.5.6  
7.5.7  
7.5.8  
7.5.9  
7.5.10  
7.5.11  
7.5.12  
7.5.13  
7.5.14  
7.6  
7.6.1  
7.6.2  
Table of Contents  
Section  
Title  
Page  
Chapter 8  
8.1  
Management Register Set ............................................................................................... 59  
Introduction to Management Register Set .............................................................60  
8.1.1  
8.1.2  
8.1.3  
8.1.4  
Management Register Set Outline .........................................................................60  
Management Register Bit Access ..........................................................................61  
Management Register Bit Default Values ..............................................................61  
Management Register Bit Special Functions .........................................................62  
8.2  
Register 0: Control Register ...................................................................................63  
Reset (bit 0.15) ......................................................................................................63  
Loopback Enable (bit 0.14) ....................................................................................64  
Data Rate Select (bit 0.13) .....................................................................................64  
Auto-Negotiation Enable (bit 0.12) .........................................................................64  
Low Power Mode (bit 0.11) ....................................................................................65  
Isolate (bit 0.10) .....................................................................................................65  
Restart Auto-Negotiation (bit 0.9) ..........................................................................65  
Duplex Mode (bit 0.8) .............................................................................................66  
Collision Test (bit 0.7) ............................................................................................66  
IEEE Reserved Bits (bits 0.6:0) .............................................................................66  
8.2.1  
8.2.2  
8.2.3  
8.2.4  
8.2.5  
8.2.6  
8.2.7  
8.2.8  
8.2.9  
8.2.10  
8.3  
Register 1: Status Register ....................................................................................67  
100Base-T4 (bit 1.15) ............................................................................................67  
100Base-TX Full Duplex (bit 1.14) .........................................................................68  
100Base-TX Half Duplex (bit 1.13) ........................................................................68  
10Base-T Full Duplex (bit 1.12) .............................................................................68  
10Base-T Half Duplex (bit 1.11) .............................................................................68  
IEEE Reserved Bits (bits 1.10:7) ...........................................................................69  
MF Preamble Suppression (bit 1.6) .......................................................................69  
Auto-Negotiation Complete (bit 1.5) .......................................................................69  
Remote Fault (bit 1.4) ............................................................................................70  
Auto-Negotiation Ability (bit 1.3) ............................................................................70  
Link Status (bit 1.2) ................................................................................................71  
Jabber Detect (bit 1.1) ...........................................................................................71  
Extended Capability (bit 1.0) ..................................................................................71  
8.3.1  
8.3.2  
8.3.3  
8.3.4  
8.3.5  
8.3.6  
8.3.7  
8.3.8  
8.3.9  
8.3.10  
8.3.11  
8.3.12  
8.3.13  
8.4  
Register 2: PHY Identifier Register ........................................................................72  
Table of Contents  
Section  
Title  
Page  
8.5  
Register 3: PHY Identifier Register ........................................................................74  
OUI bits 19-24 (bits 3.15:10) ..................................................................................74  
Manufacturer's Model Number (bits 3.9:4) .............................................................75  
Revision Number (bits 3.3:0) .................................................................................75  
8.5.1  
8.5.2  
8.5.3  
8.6  
Register 4: Auto-Negotiation Register ...................................................................76  
Next Page (bit 4.15) ...............................................................................................76  
IEEE Reserved Bit (bit 4.14) ..................................................................................77  
Remote Fault (bit 4.13) ..........................................................................................77  
IEEE Reserved Bits (bits 4.12:10) .........................................................................77  
Technology Ability Field (bits 4.9:5) .......................................................................78  
Selector Field (Bits 4.4:0) .......................................................................................79  
8.6.1  
8.6.2  
8.6.3  
8.6.4  
8.6.5  
8.6.6  
8.7  
Register 5: Auto-Negotiation Link Partner Ability Register ....................................80  
Next Page (bit 5.15) ...............................................................................................80  
Acknowledge (bit 5.14) ..........................................................................................81  
Remote Fault (bit 5.13) ..........................................................................................81  
Technology Ability Field (bits 5.12:5) .....................................................................81  
Selector Field (bits 5.4:0) .......................................................................................81  
8.7.1  
8.7.2  
8.7.3  
8.7.4  
8.7.5  
8.8  
Register 6: Auto-Negotiation Expansion Register ..................................................82  
IEEE Reserved Bits (bits 6.15:5) ...........................................................................82  
Parallel Detection Fault (bit 6.4) .............................................................................83  
Link Partner Next Page Able (bit 6.3) ....................................................................83  
Next Page Able (bit 6.2) .........................................................................................83  
Page Received (bit 6.1) .........................................................................................83  
Link Partner Auto-Negotiation Able (bit 6.0) ..........................................................83  
8.8.1  
8.8.2  
8.8.3  
8.8.4  
8.8.5  
8.8.6  
8.9  
Register 7: Auto-Negotiation Next Page Transmit Register ...................................84  
Next Page (bit 7.15) ...............................................................................................85  
IEEE Reserved Bit (bit 7.14) ..................................................................................85  
Message Page (bit 7.13) ........................................................................................85  
Acknowledge 2 (bit 7.12) .......................................................................................85  
Toggle (bit 7.11) .....................................................................................................85  
Message Code Field / Unformatted Code Field (bits 7.10:0) .................................85  
8.9.1  
8.9.2  
8.9.3  
8.9.4  
8.9.5  
8.9.6  
8.10  
Register 8: Auto-Negotiation Next Page Link Partner Ability Register ...................86  
Next Page (bit 8.15) ...............................................................................................87  
IEEE Reserved Bit (bit 8.14) ..................................................................................87  
Message Page (bit 8.13) ........................................................................................87  
Acknowledge 2 (bit 8.12) .......................................................................................87  
Message Code Field / Unformatted Code Field (bits 8.10:0) .................................87  
8.10.1  
8.10.2  
8.10.3  
8.10.4  
8.10.5  
Table of Contents  
Section  
Title  
Page  
8.11  
Register 16: Extended Control Register ................................................................88  
Command Override Write Enable (bit 16.15) .........................................................89  
ICS Reserved (bits 16.14:11) .................................................................................89  
PHY Address (bits 16.10:6) ...................................................................................89  
Stream Cipher Scrambler Test Mode (bit 16.5) .....................................................89  
ICS Reserved (bit 16.4) .........................................................................................89  
NRZ/NRZI Encoding (bit 16.3) ...............................................................................89  
Invalid Error Code Test (bit 16.2) ...........................................................................90  
ICS Reserved (bit 16.1) .........................................................................................90  
Stream Cipher Disable (bit 16.0) ............................................................................90  
8.11.1  
8.11.2  
8.11.3  
8.11.4  
8.11.5  
8.11.6  
8.11.7  
8.11.8  
8.11.9  
8.12  
Register 17: Quick Poll Detailed Status Register ...................................................91  
Data Rate (bit 17.15) ..............................................................................................92  
Duplex (bit 17.14) ...................................................................................................92  
Auto-Negotiation Progress Monitor (bits 17.13:11) ................................................93  
100Base-TX Receive Signal Lost (bit 17.10) .........................................................93  
100Base PLL Lock Error (bit 17.9) .........................................................................94  
False Carrier (bit 17.8) ...........................................................................................94  
Invalid Symbol (bit 17.7) ........................................................................................94  
Halt Symbol (bit 17.6) ............................................................................................95  
Premature End (bit 17.5) ........................................................................................95  
Auto-Negotiation Complete (bit 17.4) .....................................................................95  
100Base-TX Signal Detect (bit 17.3) .....................................................................95  
Jabber Detect (bit 17.2) .........................................................................................96  
Remote Fault (bit 17.1) ..........................................................................................96  
Link Status (bit 17.0) ..............................................................................................96  
8.12.1  
8.12.2  
8.12.3  
8.12.4  
8.12.5  
8.12.6  
8.12.7  
8.12.8  
8.12.9  
8.12.10  
8.12.11  
8.12.12  
8.12.13  
8.12.14  
8.13  
Register 18: 10Base-T Operations Register ..........................................................97  
Remote Jabber Detect (bit 18.15) ..........................................................................97  
Polarity Reversed (bit 18.14) .................................................................................98  
ICS Reserved (bits 18.13:6) ...................................................................................98  
Jabber Inhibit (bit 18.5) ..........................................................................................98  
ICS Reserved (bit 18.4) .........................................................................................98  
Auto Polarity Inhibit (bit 18.3) .................................................................................98  
SQE Test Inhibit (bit 18.2) ......................................................................................98  
Link Loss Inhibit (bit 18.1) ......................................................................................99  
Squelch Inhibit (bit 18.0) ........................................................................................99  
8.13.1  
8.13.2  
8.13.3  
8.13.4  
8.13.5  
8.13.6  
8.13.7  
8.13.8  
8.13.9  
Table of Contents  
Section  
Title  
Page  
8.14  
Register 19: Extended Control Register 2 ...........................................................100  
Node/Repeater Configuration (bit 19.15) .............................................................101  
Hardware/Software Priority Status (bit 19.14) ......................................................101  
Remote Fault (bit 19.13) ......................................................................................101  
ICS Reserved (bits 19.12:8) .................................................................................101  
Twisted Pair Tri-State Enable, TPTRI (bit 19.7) ...................................................102  
ICS Reserved (bits 19.12:6) .................................................................................102  
Force LEDs On (bit 19.5) .....................................................................................102  
ICS Reserved (bits 19.4:1) ...................................................................................102  
Automatic 100Base-TX Power-Down (bit 19.0) ...................................................102  
8.14.1  
8.14.2  
8.14.3  
8.14.4  
8.14.5  
8.14.6  
8.14.7  
8.14.8  
8.14.9  
Chapter 9  
9.1  
Pin Diagram, Listings, and Descriptions.....................................................................103  
ICS1893 Pin Diagram ..........................................................................................103  
9.2  
9.3  
ICS1893 Pin Listings ............................................................................................104  
ICS1893 Pin Descriptions ....................................................................................105  
Transformer Interface Pins ..................................................................................105  
Multi-Function (Multiplexed) Pins: PHY Address and LED Pins ..........................106  
Configuration Pins ................................................................................................110  
MAC/Repeater Interface Pins ..............................................................................112  
Reserved Pins ......................................................................................................121  
Ground and Power Pins .......................................................................................122  
9.3.1  
9.3.2  
9.3.3  
9.3.4  
9.3.5  
9.3.6  
Chapter 10  
10.1  
DC and AC Operating Conditions...............................................................................123  
Absolute Maximum Ratings .................................................................................123  
10.2  
10.3  
10.4  
Recommended Operating Conditions ..................................................................123  
Recommended Component Values .....................................................................124  
DC Operating Characteristics ..............................................................................125  
DC Operating Characteristics for Supply Current ................................................125  
DC Operating Characteristics for TTL Inputs and Outputs ..................................125  
DC Operating Characteristics for REF_IN ...........................................................126  
DC Operating Characteristics for Media Independent Interface ..........................126  
Timing Diagrams ..................................................................................................127  
Timing for Clock Reference In (REF_IN) Pin .......................................................127  
Timing for Transmit Clock (TXCLK) Pins .............................................................128  
Timing for Receive Clock (RXCLK) Pins ..............................................................129  
100M MII / 100M Stream Interface: Synchronous Transmit Timing .....................130  
10M MII: Synchronous Transmit Timing ..............................................................131  
MII / 100M Stream Interface: Synchronous Receive Timing ................................132  
MII Management Interface Timing .......................................................................133  
10M Serial Interface: Receive Latency ................................................................134  
10M Media Independent Interface: Receive Latency ...........................................135  
10.4.1  
10.4.2  
10.4.3  
10.4.4  
10.5  
10.5.1  
10.5.2  
10.5.3  
10.5.4  
10.5.5  
10.5.6  
10.5.7  
10.5.8  
10.5.9  
Table of Contents  
Section  
Title  
Page  
10.5.10  
10.5.11  
10.5.12  
10.5.13  
10.5.14  
10.5.15  
10.5.16  
10.5.17  
10.5.18  
10.5.19  
10.5.20  
10.5.21  
10.5.22  
10M Serial Interface: Transmit Latency ...............................................................136  
10M Media Independent Interface: Transmit Latency ..........................................137  
MII / 100M Stream Interface: Transmit Latency ...................................................138  
100M MII: Carrier Assertion/De-Assertion (Half-Duplex Transmission) ...............139  
10M MII: Carrier Assertion/De-Assertion (Half-Duplex Transmission) .................140  
100M MII / 100M Stream Interface: Receive Latency ..........................................141  
100M Media Dependent Interface: Input-to-Carrier Assertion/De-Assertion .......142  
Reset: Power-On Reset .......................................................................................143  
Reset: Hardware Reset and Power-Down ...........................................................144  
10Base-T: Heartbeat Timing (SQE) .....................................................................145  
10Base-T: Jabber Timing .....................................................................................146  
10Base-T: Normal Link Pulse Timing ..................................................................147  
Auto-Negotiation Fast Link Pulse Timing .............................................................148  
Chapter 11  
Chapter 12  
Physical Dimensions of ICS1893 Package................................................................149  
Ordering Information ...................................................................................................151  
Revision History  
• The initial release of this document, Rev A, was dated August 5, 1999.  
• Rev B was dated September 10, 1999. The following list also indicates what changes were made.  
– Page 1. Document status changes from ‘Preliminary’ to ‘Release’. Also, change to text in bullet that  
starts with “Low-power”.  
– Table of Contents reflect page renumbering.  
– Revision History  
– Chapter 3, “ICS1893 Enhanced Features”. Change to text in 1(a).  
– Section 7.4.1, “100Base-TX Operation: Stream Cipher Scrambler/Descrambler”. Added paragraph.  
– Section 8.6.4, “IEEE Reserved Bits (bits 4.12:10)”. New paragraph. (Subsequent paragraphs reflect  
renumbering.)  
– Chapter 9, “Pin Diagram, Listings, and Descriptions”. ICS1893 pin names have changes.  
– Table 10-1 reflects changes to ICS1893 pin names.  
– Table 10-2 reflects changes to ICS1893 pin names.  
– Section 10.4.1, “DC Operating Characteristics for Supply Current”. Changes to text and table reflect  
changes to ICS1893 pin names.  
– Section 10.4.2, “DC Operating Characteristics for TTL Inputs and Outputs”. Changes to text and  
table reflect changes to ICS1893 pin names.  
– Table 10-6. Changes to table values.  
– Table 10-7. Changes to table values.  
– Table 10-16. Changes to table values. Table title added.  
– Table 10-18. Changes to table values.  
– Section 10.5.13, “100M MII: Carrier Assertion/De-Assertion (Half-Duplex Transmission)”. Changes  
to table values and timing diagram.  
– Section 10.5.14, “10M MII: Carrier Assertion/De-Assertion (Half-Duplex Transmission)”. Changes to  
table values and timing diagram.  
– Table 10-24. Changes to table values. Also, the value that was previously ‘TBD’ is now determined.  
– Table 10-25. Changes to table values.  
– Table 10-26. Changes to table values.  
– Table 10-27. Changes to table values.  
– Table 10-28. Changes to table values.  
– Table 10-29. Changes to table values.  
– Chapter 11, “Physical Dimensions of ICS1893 Package”. Changes to text in bullets.  
• This release of this document, Rev C, is dated May 22, 2000. Change bars indicate where all changes  
are made. (For an explanation of change bars, see the Change Bar note on this page.) The following list  
also indicates where changes occur.  
– Table of Contents reflect page renumbering.  
– Table 3-1 value xxx changes from 000011b to 000100b  
– Section 6.5, “Twisted-Pair Interface” text changes.  
– Section 6.5.1, “Twisted-Pair Transmitter Interface” and Section 6.5.2, “Twisted-Pair Receiver  
Interface” are two new sections with two new figures.  
– Section 6.6, “Clock Reference Interface” reflects deletion of references to crystal oscillator, as the  
ICS1893 does not work with a crystal. (Section 6.6.1 and Section 6.6.2 are deleted.)  
– Section 6.8, “Status Interface” has two new notes, Notes 5 and 6.  
– A new figure, Figure 6-3, follows Section 6.8, “Status Interface”.  
– Table 8-9 value changes from F420 to F441.  
– Section 8.5.2, “Manufacturer's Model Number (bits 3.9:4)” text changes.  
– Table 8-10 value changes from 0000 to 0001.  
– In the following areas, ICS1894 changes to ICS1893:  
• Section 8.13.1, “Remote Jabber Detect (bit 18.15)”  
• Table 9-5 RXCLK pin description.  
• Table 9-6 RXCLK pin description.  
• Table 9-8 NC pin description.  
– In the following sections, pin 54 changes from VDD_IO to VDD:  
• Section 9.1, “ICS1893 Pin Diagram”  
• Section 9.2, “ICS1893 Pin Listings”  
• Section 9.3.6, “Ground and Power Pins”  
– Table 9-4 text changes for the REF_IN and REF_OUT pin descriptions.  
– Table 9-7 text changes for the RXTRI pin descriptions.  
– Section 9.3.6, “Ground and Power Pins” adds the VSS ground pin, pin 22.  
– Section 10.3, “Recommended Component Values” text changes.  
– A new figure, Figure 10-1, follows Section 10.3, “Recommended Component Values”.  
Change Bars  
Change bars on subsequent ICS1893 data sheets indicate new documents posted to the web. (Change  
bars within a new version of a document also indicates changes to the document.)  
Sample change bar  
–
Rev D, 8/11/09 - Added EOL note for ordering information per PDN U-09-01.  
Rev E, 5/13/10 - removed green parts ordering information per PDN U-09-01.  
Chapter 1 Abbreviations and Acronyms  
Table 1-1 lists and interprets the abbreviations and acronyms used throughout this data sheet.  
Table 1-1. Abbreviations and Acronyms  
Abbreviation /  
Acronym  
Interpretation  
4B/5B  
ANSI  
CMOS  
CSMA/CD  
CW  
4-Bit / 5-Bit Encoding/Decoding  
American National Standards Institute  
complimentary metal-oxide semiconductor  
Carrier Sense Multiple Access with Collision Detection  
Command Override Write  
digital signal processing  
DSP  
ESD  
FDDI  
FLL  
End-of-Stream Delimiter  
Fiber Distributed Data Interface  
frequency-locked loop  
FLP  
Fast Link Pulse  
IDL  
A ‘dead’ time on the link following a 10Base-T packet, not to be confused with idle  
International Electrotechnical Commission  
Institute of Electrical and Electronic Engineers  
International Standards Organization  
Latching High  
IEC  
IEEE  
ISO  
LH  
LL  
Latching Low  
LMX  
MAC  
Max.  
Mbps  
MDI  
Latching Maximum  
Media Access Control  
maximum  
Megabits per second  
Media Dependent Interface  
Management Frame  
MF  
MII  
Media Independent Interface  
minimum  
Min.  
MLT-3  
N/A  
Multi-Level Transition Encoding (3 Levels)  
Not Applicable  
NLP  
No.  
Normal Link Pulse  
Number  
NRZ  
NRZI  
OSI  
Not Return to Zero  
Not Return to Zero, Invert on one  
Open Systems Interconnection  
Table 1-1. Abbreviations and Acronyms (Continued)  
Abbreviation /  
Acronym  
Interpretation  
OUI  
PCS  
PHY  
Organizationally Unique Identifier  
Physical Coding sublayer  
physical-layer device  
The ICS1893 is a physical-layer device, also referred to as a ‘PHY’ or ‘PHYceiver’. (The  
ICS1890 is also a physical-layer device.)  
PLL  
PMA  
PMD  
ppm  
QFP  
RO  
phase-locked loop  
Physical Medium Attachment  
Physical Medium Dependent  
parts per million  
quad flat pack  
read only  
R/W  
R/W0  
SC  
read/write  
read/write zero  
self-clearing  
SF  
Special Functions  
Start-of-Frame Delimiter  
SFD  
SI  
Stream Interface, Serial Interface, or Symbol Interface.  
With reference to the MII/SI pin, the acronym ‘SI’ has multiple meanings.  
• Generically, SI means 'Stream Interface', and is documented as such in this data  
sheet.  
• However, when the MAC/Repeater Interface is configured for:  
– 10M operations, SI is an acronym for 'Serial Interface'.  
– 100M operations, SI is an acronym for 'Symbol Interface'.  
SQE  
SSD  
STA  
Signal Quality Error  
Start-of-Stream Delimiter  
Station Management Entity  
shielded twisted pair  
STP  
TAF  
Technology Ability Field  
Twisted-Pair Physical Layer Medium Dependent  
typical  
TP-PMD  
Typ.  
UTP  
unshielded twisted pair  
Chapter 2 Conventions and Nomenclature  
Table 2-1 lists and explains the conventions and nomenclature used throughout this data sheet.  
Table 2-1. Conventions and Nomenclature  
Item  
Convention / Nomenclature  
Bits  
• A bit in a register is identified using the format ‘register.bit’. For example, bit  
0.15 is bit 15 of register 0.  
• When a colon is used with bits, it indicates the range of bits. For example,  
bits 1.15:11 are bits 15, 14, 13, 12, and 11 of register 1.  
• For a range of bits, the order is always from the most-significant bit to the  
least-significant bit.  
Code groups  
Colon (:)  
Within this table, see the item ‘Symbols’  
Within this table, see these items:  
• ‘Bits’  
• ‘Pin (or signal) names’  
Numbers  
• As a default, all numbers use the decimal system (that is, base 10) unless  
followed by a lowercase letter. A string of numbers followed by a lowercase  
letter:  
– A ‘b’ represents a binary (base 2) number  
– An ‘h’ represents a hexadecimal (base 16) number  
– An ‘o’ represents an octal (base 8) number  
• All numerical references to registers use decimal notation (and not  
hexadecimal).  
Pin (or signal) names  
• All pin or signal names are provided in capital letters.  
• A pin name that includes a forward slash ‘/’ is a multi-function, configuration  
pin. These pins provide the ability to select between two ICS1893  
functions. The name provided:  
– Before the ‘/’ indicates the pin name and function when the signal level  
on the pin is logic zero.  
– After the ‘/’ indicates the pin name and function when the signal level on  
the pin is logic one.  
For example, the HW/SW pin selects between Hardware (HW) mode and  
Software (SW) mode. When the signal level on the HW/SW pin is logic:  
– Zero, the ICS1893 Hardware mode is selected.  
– One, the ICS1893 Software mode is selected.  
• An ‘n’ appended to the end of a pin name or signal name (such as  
RESETn) indicates an active-low operation.  
• When a colon is used with pin or signal names, it indicates a range. For  
example, TXD[3:0] represents pins/signals TXD3, TXD2, TXD1, and TXD0.  
• When pin name abbreviations are spelled out, words in parentheses  
indicate additional description that is not part of the pin name abbreviation.  
Registers  
• A bit in a register is identified using the format ‘register.bit’. For example, bit  
0.15 is bit 15 of register 0.  
• All numerical references to registers use decimal notation (and not  
hexadecimal).  
• When register name abbreviations are spelled out, words in parentheses  
indicate additional description that is not part of the register name  
abbreviation.  
Table 2-1. Conventions and Nomenclature (Continued)  
Item  
Convention / Nomenclature  
• When referring to signals, the terms:  
Signal references  
– ‘FALSE’, ‘low’, or ‘zero’ represent signals that are logic zero.  
– ‘TRUE’, ‘high’, or ‘one’ represent signals that are logic one.  
• Chapter 10, “DC and AC Operating Conditions” defines the electrical  
specifications for ‘logic zero’ and ‘logic one’ signals.  
Symbols  
• In this data sheet, code group names are referred to as ‘symbols’ and they  
are shown between '/' (slashes). For example, the symbol /J/ represents  
the first half of the Start-of-Stream Delimiter (SSD1).  
• Symbol sequences are shown in succession. For example, /I/J/K/  
represents an IDLE followed by the SSD.  
Terms:  
‘set’,  
The terms ‘set’, ‘active’, and ‘asserted’ are synonymous.  
They do not necessarily infer logic one.  
‘active’,  
‘asserted’,  
(For example, an active-low signal can be set to logic zero.)  
Terms:  
The terms ‘cleared’, ‘inactive’, and ‘de-asserted’ are synonymous.  
They do not necessarily infer logic zero.  
‘cleared’,  
‘de-asserted’,  
‘inactive’  
Terms:  
‘twisted-pair receiver’  
In reference to the ICS1893, the term ‘Twisted-Pair Receiver’ refers to the set  
of Twisted-Pair Receive output pins (TP_RXP and TP_RXN).  
Terms:  
In reference to the ICS1893, the term ‘Twisted-Pair Transmitter’ refers to the  
‘twisted-pair transmitter’ set of Twisted-Pair Transmit output pins (TP_TXP and TP_TXN).  
Chapter 3 ICS1893 Enhanced Features  
The ICS1893 is an enhanced version of the ICS1890. In contrast to the ICS1890, the ICS1893 offers  
significant improvements in both performance and features while maintaining backward compatibility. The  
specific differences between these devices are listed below.  
1. The ICS1893 employs an advanced digital signal processing (DSP) architecture that improves the  
100Base-TX Receiver performance beyond that of any other PHY in the market. Specifically:  
a. The ICS1893 DSP-based, adaptive equalization process allows the ICS1893 to accommodate a  
maximum cable attenuation/insertion loss in excess of 24 dB, which is nearly equivalent to the  
attenuation loss of a 100-meter Category 5 cable.  
b. The ICS1893 DSP-based, baseline-wander correction process eliminates killer packets.  
2. The analog 10Base-T Receive Phase-Locked Loop (PLL) of the ICS1890 is replaced with a digital PLL  
in the ICS1893, thereby resulting in lower jitter and improved stability.  
3. The ICS1890 Frequency-Locked Loop (FLL) that is part of the 100Base-TX Clock and Data Recovery  
circuitry is replaced with a digital FLL in the ICS1893, also resulting in lower jitter and improved  
stability.  
4. The ICS1893 transmit circuits are improved in contrast to the ICS1890, resulting in a decrease in the  
magnitude of the 10Base-T harmonic content generated during transmission. (See ISO/IEC 8802-3:  
1993 clause 8.3.1.3.)  
5. The ICS1893 supports the Auto-Negotiation Next Page functions described in IEEE Std 802.3u-1995  
clause 28.2.3.4.  
6. The ICS1893 supports Management Frame (MF) Preamble Suppression.  
7. The ICS1893 provides the Remote Jabber capability.  
8. The ICS1893 has an improved version of the ICS1890 10Base-T Squelch operation.  
9. The ICS1893 “seeds” (that is, initializes) the Transmit Stream Cipher Shift register by using the  
ICS1893 PHY address from Table 8-16, which minimizes crosstalk and noise in repeater applications.  
10. The ICS1893 offers an automatic 10Base-T power-down mode.  
11. The enhanced features of the ICS1893 required some modifications to the ICS1890 Management  
Registers. However, the ICS1893 Management Registers are backward-compatible with the ICS1890  
Management Registers. Table 3-1 summarizes the differences between the ICS1890 and the ICS1893  
Management Registers.  
Table 3-1. Summary of Differences between ICS1890 and ICS1893 Registers  
Register.  
Bit(s)  
ICS1890  
Function  
Reserved  
ICS1893  
Function  
Default  
Default  
1.6  
0b (always) Management Frame Preamble  
Suppression  
0b  
3.9:4  
3.3:0  
6.2  
Model Number  
000010b  
0011b  
Model Number  
000100b  
0000b  
1b  
Revision Number  
Next Page Able  
Not applicable (N/A)  
Revision Number  
0b (always) Next Page Able  
7.15:0  
N/A  
Auto-Negotiate Next Page  
2001h  
Transmit Register  
8.15:0  
N/A  
N/A  
Auto-Negotiate Next Page  
Link Partner Ability  
0000h  
FFFFh  
9.15:0  
through  
15.15:0  
IEEE reserved.  
0000h  
IEEE reserved.  
Note: Although the default value is  
changed, this response more  
accurately reflects an MDIO  
access to registers 9–15.  
18.15  
19.1  
Reserved  
Reserved  
0b  
Remote Jabber  
0b  
1b  
0b  
Automatic 10Base-T Power Down  
20.15:0 N/A  
through  
31.15:0  
N/A  
ICS test registers.  
(There is no claim of backward  
compatibility for these registers.)  
See specific  
registers and  
bits.  
Note:  
1. There are new registers and bits. For example:  
a. Registers 7 and 8 are new (that is, the ICS1890 does not have these registers).  
b. Registers 20 through 31 are new ICS test registers.  
2. For some bits (such as the model number and revision number bits), the default values are changed.  
Chapter 4 Overview of the ICS1893  
The ICS1893 is a stream processor. During data transmission, it accepts sequential nibbles from its MAC  
(Media Access Control)/Repeater Interface, converts them into a serial bit stream, encodes them, and  
transmits them over the medium through an external isolation transformer. When receiving data, the  
ICS1893 converts and decodes a serial bit stream (acquired from an isolation transformer that interfaces  
with the medium) into sequential nibbles. It subsequently presents these nibbles to its MAC/Repeater  
Interface.  
The ICS1893 implements the OSI model’s physical layer, consisting of the following, as defined by the  
ISO/IEC 8802-3 standard:  
• Physical Coding sublayer (PCS)  
• Physical Medium Attachment sublayer (PMA)  
• Physical Medium Dependent sublayer (PMD)  
• Auto-Negotiation sublayer  
The ICS1893 is transparent to the next layer of the OSI model, the link layer. The link layer has two  
sublayers: the Logical Link Control sublayer and the MAC sublayer. The ICS1893 can interface directly to  
the MAC and offers multiple, configurable modes of operation. Alternately, this configurable interface can  
be connected to a repeater, which extends the physical layer of the OSI model.  
The ICS1893 transmits framed packets acquired from its MAC/Repeater Interface and receives  
encapsulated packets from another PHY, which it translates and presents to its MAC/Repeater Interface.  
Note: As per the ISO/IEC standard, the ICS1893 does not affect, nor is it affected by, the underlying  
structure of the MAC/repeater frame it is conveying.  
4.1 100Base-TX Operation  
During 100Base-TX data transmission, the ICS1893 accepts packets from a MAC/repeater and inserts  
Start-of-Stream Delimiters (SSDs) and End-of-Stream Delimiters (ESDs) into the data stream. The  
ICS1893 encapsulates each MAC/repeater frame, including the preamble, with an SSD and an ESD. As  
per the ISO/IEC Standard, the ICS1893 replaces the first octet of each MAC preamble with an SSD and  
appends an ESD to the end of each MAC/repeater frame.  
When receiving data from the medium, the ICS1893 removes each SSD and replaces it with the  
pre-defined preamble pattern before presenting the nibbles to its MAC/Repeater Interface. When the  
ICS1893 encounters an ESD in the received data stream, signifying the end of the frame, it ends the  
presentation of nibbles to its MAC/Repeater Interface. Therefore, the local MAC/repeater receives an  
unaltered copy of the transmitted frame sent by the remote MAC/repeater.  
During periods when MAC frames are being neither transmitted nor received, the ICS1893 signals and  
detects the IDLE condition on the Link Segment. In the 100Base-TX mode, the ICS1893 transmit channel  
sends a continuous stream of scrambled ones to signify the IDLE condition. Similarly, the ICS1893 receive  
channel continually monitors its data stream and looks for a pattern of scrambled ones. The results of this  
signaling and monitoring provide the ICS1893 with the means to establish the integrity of the Link Segment  
between itself and its remote link partner and inform its Station Management Entity (STA) of the link status.  
For 100M data transmission, the ICS1893 MAC/Repeater Interface can be configured to provide either a  
100M Media Independent Interface (MII) or a 100M Symbol Interface. With the Symbol Interface  
configuration, the data stream bypasses the ICS1893 Physical Coding sublayer (PCS). In addition:  
1. The ICS1893 shifts the responsibility of performing the 4B/5B translation to the MAC/repeater. As a  
result, the requirement is for a 5-bit data path between the MAC/repeater and the ICS1893.  
2. The latency through the ICS1893 is reduced. (The ICS1893 provides this 100M Symbol Interface  
primarily for repeater applications for which latency is a critical performance parameter.)  
4.2 10Base-T Operation  
During 10Base-T data transmission, the ICS1893 inserts only the IDL delimiter into the data stream. The  
ICS1893 appends the IDL delimiter to the end of each MAC frame. However, since the 10Base-T preamble  
already has a Start-of-Frame delimiter (SFD), it is not required that the ICS1893 insert an SSD-like  
delimiter.  
When receiving data from the medium (such as a twisted-pair cable), the ICS1893 uses the preamble to  
synchronize its receive clock. When the ICS1893 receive clock establishes lock, it presents the preamble  
nibbles to its MAC/Repeater Interface. The 10M MAC/Repeater Interface can be configured as either a  
10M MII, a 10M Serial Interface, or a Link Pulse Interface.  
In 10M operations, during periods when MAC frames are being neither transmitted nor received, the  
ICS1893 signals and detects Normal Link Pulses. This action allows the integrity of the Link Segment with  
the remote link partner to be established and then reported to the ICS1893’s STA.  
Chapter 5 Operating Modes Overview  
The ICS1893 operating modes and interfaces are configurable with one of two methods. The HW/SW  
(hardware/software) pin determines which method the ICS1893 is to use, either its hardware pins or its  
register bits. When the HW/SW bit is logic zero the ICS1893 is in hardware mode. In hardware mode, the  
hardware pins have priority over the internal registers for establishing the configuration settings of the  
ICS1893. When the HW/SW bit is logic one the ICS1893 is in software mode. In software mode, the  
internal register bits have priority over the hardware pins for establishing the configuration settings of the  
ICS1893. The register bits are typically controlled from software.  
The ICS1893 register bits are accessible through a standard MII (Media Independent Interface) Serial  
Management Port. Even when the ICS1893 MAC/Repeater Interface is not supporting the standard MII  
Data Interface, access to the Serial Management Port is provided (that is, operation of the Serial  
Management Port is independent of the MAC/Repeater Interface configuration).  
The ICS1893 provides a number of configuration functions to support a variety of operations. For example,  
the MAC/Repeater Interface can be configured to operate as a 10M MII, a 100M MII, a 100M Symbol  
Interface, a 10M Serial Interface, or a Link Pulse Interface. The protocol on the Medium Dependent  
Interface (MDI) can be configured to support either 10M or 100M operations in either half-duplex or  
full-duplex modes.  
The ICS1893 is fully compliant with the ISO/IEC 8802-3 standard, as it pertains to both 10Base-T and  
100Base-TX operations. The feature-rich ICS1893 allows easy migration from 10-Mbps to 100-Mbps  
operations as well as from systems that require support of both 10M and 100M links.  
This chapter is an overview of the following ICS1893 modes of operation:  
• Section 5.1, “Reset Operations”  
• Section 5.2, “Power-Down Operations”  
• Section 5.3, “Automatic Power-Saving Operations”  
• Section 5.4, “Auto-Negotiation Operations”  
• Section 5.5, “100Base-TX Operations”  
• Section 5.6, “10Base-T Operations”  
• Section 5.7, “Half-Duplex and Full-Duplex Operations”  
5.1 Reset Operations  
This section first discusses reset operations in general and then specific ways in which the ICS1893 can be  
configured for various reset options.  
5.1.1 General Reset Operations  
The following reset operations apply to all the specific ways in which the ICS1893 can be reset, which are  
discussed in Section 5.1.2, “Specific Reset Operations”.  
5.1.1.1 Entering Reset  
When the ICS1893 enters a reset condition (either through hardware, power-on reset, or software), it does  
the following:  
1. Isolates the MAC/Repeater Interface input pins  
2. Drives all MAC/Repeater Interface output pins low  
3. Tri-states the signals on its Twisted-Pair Transmit pins (TP_TXP and TP_TXN)  
4. Initializes all its internal modules and state machines to their default states  
5. Enters the power-down state  
6. Initializes all internal latching low (LL), latching high (LH), and latching maximum (LMX) Management  
Register bits to their default values  
5.1.1.2 Exiting Reset  
When the ICS1893 exits a reset condition, it does the following:  
1. Exits the power-down state  
2. Latches the Serial Management Port Address of the ICS1893 into the Extended Control Register, bits  
16.10:6. [See Section 8.11.3, “PHY Address (bits 16.10:6)”.]  
3. Enables all its internal modules and state machines  
4. Sets all Management Register bits to either (1) their default values or (2) the values specified by their  
associated ICS1893 input pins, as determined by the HW/SW pin  
5. Enables the Twisted-Pair Transmit pins (TP_TXP and TP_TXN)  
6. Resynchronizes both its Transmit and Receive Phase-Locked Loops, which provide its transmit clock  
(TXCLK) and receive clock (RXCLK)  
7. Releases all MAC/Repeater Interface pins, which takes a maximum of 640 ns after the reset condition  
is removed  
5.1.1.3 Hot Insertion  
As with the ICS189X products, the ICS1893 reset design supports ‘hot insertion’ of its MII. (That is, the  
ICS1893 can connect its MAC/Repeater Interface to a MAC/repeater while power is already applied to the  
MAC/repeater.)  
5.1.2 Specific Reset Operations  
This section discusses the following specific ways that the ICS1893 can be reset:  
• Hardware reset (using the RESETn pin)  
• Power-on reset (applying power to the ICS1893)  
• Software reset (using Control Register bit 0.15)  
Note: At the completion of a reset (either hardware, power-on, or software), the ICS1893 sets all  
registers to their default values.  
5.1.2.1 Hardware Reset  
Entering Hardware Reset  
Holding the active-low RESETn pin low for a minimum of five REF_IN clock cycles initiates a hardware  
reset (that is, the ICS1893 enters the reset state). During reset, the ICS1893 executes the steps listed in  
Section 5.1.1.1, “Entering Reset”.  
Exiting Hardware Reset  
After the signal on the RESETn pin transitions from a low to a high state, the ICS1893 completes in 640 ns  
(that is, in 16 REF_IN clocks) steps 1 through 5, listed in Section 5.1.1.2, “Exiting Reset”. After the first five  
steps are completed, the Serial Management Port is ready for normal operations, but this action does not  
signify the end of the reset cycle. The reset cycle completes when the transmit clock (TXCLK) and receive  
clock (RXCLK) are available, which is typically 53 ms after the RESETn pin goes high. [For details on this  
transition, see Section 10.5.18, “Reset: Hardware Reset and Power-Down”.]  
Note:  
1. The MAC/Repeater Interface is not available for use until the TXCLK and RXCLK are valid.  
2. The Control Register bit 0.15 does not represent the status of a hardware reset. It is a self-clearing bit  
that is used to initiate a software reset.  
5.1.2.2 Power-On Reset  
Entering Power-On Reset  
When power is applied to the ICS1893, it waits until the potential between VDD and VSS achieves a  
minimum voltage before entering reset and executing the steps listed in Section 5.1.1.1, “Entering Reset”.  
After entering reset from a power-on condition, the ICS1893 remains in reset for approximately 20 ms. (For  
details on this transition, see Section 10.5.17, “Reset: Power-On Reset”.)  
Exiting Power-On Reset  
The ICS1893 automatically exits reset and performs the same steps as for a hardware reset. (See Section  
5.1.1.2, “Exiting Reset”.)  
Note: The only difference between a hardware reset and a power-on reset is that during a power-on  
reset, the ICS1893 isolates its RESETn input pin. All other functionality is the same. As with a  
hardware reset, Control Register bit 0.15 does not represent the status of a power-on reset.  
5.1.2.3 Software Reset  
Entering Software Reset  
Initiation of a software reset occurs when a management entity writes a logic one to Control Register bit  
0.15. When this write occurs, the ICS1893 enters the reset state for two REF_IN clock cycles.  
Note: Entering a software reset is nearly identical to entering a hardware reset or a power-on reset,  
except that during a software-initiated reset, the ICS1893 does not enter the power-down state.  
Exiting Software Reset  
At the completion of a reset (either hardware, power-on, or software), the ICS1893 sets all registers to their  
default values. This action automatically clears (that is, sets equal to logic zero) Control Register bit 0.15,  
the software reset bit. Therefore, for a software reset (only), bit 0.15 is a self-clearing bit that indicates the  
completion of the reset process.  
Note:  
1. The RESETn pin is active low but Control Register bit 0.15 is active high.  
2. Exiting a software reset is nearly identical to exiting a hardware reset or a power-on reset, except that  
upon exiting a software-initiated reset, the ICS1893 does not re-latch its Serial Management Port  
Address into the Extended Control Register. [For information on the Serial Management Port Address,  
see Section 8.11.3, “PHY Address (bits 16.10:6)”.]  
3. The Control Register bit 0.15 does not represent the status of a hardware reset. It is a self-clearing bit  
that is used to initiate a software reset. During a hardware or power-on reset, Control Register bit 0.15  
does not get set to logic one. As a result, this bit 0.15 cannot be used to indicate the completion of the  
reset process for hardware or power-on resets.  
5.2 Power-Down Operations  
The ICS1893 enters the power-down state whenever either (1) the RESETn pin is low or (2) Control  
Register bit 0.11 (the Power-Down bit) is logic one. In the power-down state, the ICS1893 disables all  
internal functions and drives all MAC/Repeater Interface output pins to logic zero except for those that  
support the MII Serial Management Port. In addition, the ICS1893 tri-states its Twisted-Pair Transmit pins  
(TP_TXP and TP_TXN) to achieve an additional reduction in power.  
There is one significant difference between entering the power-down state by setting Control Register bit  
0.11 as opposed to entering the power-down state during a reset. When the ICS1893 enters the  
power-down state:  
• By setting Control Register bit 0.11, the ICS1893 maintains the value of all Management Register bits  
except for the latching low (LL), latching high (LH), and latching maximum (LMX) status bits. Instead,  
these LL, LH, and LMX Management Register bits are re-initialized to their default values.  
• During a reset, the ICS1893 sets all of its Management Register bits to their default values. It does not  
maintain the state of any Management Register bit.  
For more information on power-down operations, see the following:  
• Section 8.14, “Register 19: Extended Control Register 2”  
• Section 10.4, “DC Operating Characteristics”, which has tables that specify the ICS1893 power  
consumption while in the power-down state  
5.3 Automatic Power-Saving Operations  
The ICS1893 has power-saving features that automatically minimize its total power consumption while it is  
operating. Table 5-1 lists the ICS1893 automatic power-saving features for the various modes.  
Table 5-1. Automatic Power-Saving Features, 10Base-T and 100Base-TX Modes  
Power-  
Saving  
Feature  
Mode for ICS1893  
10Base-T Mode  
100Base-TX Mode  
Disable Inter- In 10Base-T mode, the ICS1893 disables  
nal Modules all its internal 100Base-TX modules.  
In 100Base-TX mode, the ICS1893  
disables all its internal 10Base-T modules.  
STA Control When an STA sets the state of the ICS1893 When an STA sets the state of the ICS1893  
of Automatic Extended Control Register 2, bit 19.0 to  
Extended Control Register 2, bit 19.1 to  
logic:  
• Zero, the 10Base-T modules always  
remain enabled, even during  
100Base-TX operations.  
Power-  
Saving  
logic:  
• Zero, the 100Base-TX modules always  
remain enabled, even during 10Base-T  
operations.  
Features  
• One, the ICS1893 automatically  
disables 100Base-TX modules while the  
ICS1893 is operating in 10Base-T  
mode.  
• One, the ICS1893 automatically  
disables 10Base-T modules while the  
ICS1893 is operating in 100Base-TX  
mode.  
5.4 Auto-Negotiation Operations  
The ICS1893 has an Auto-Negotiation sublayer and provides both an input pin, ANSEL (Auto-Negotiation  
Select) and a Control Register bit (bit 0.12) to determine whether its Auto-Negotiation sublayer is enabled  
or disabled. The ICS1893 HW/SW input pin exclusively selects whether the ANSEL pin (which is used for  
the hardware mode) or Control Register bit 0.12 (which is used for the software mode) controls its  
Auto-Negotiation sublayer.  
When enabled, the ICS1893 Auto-Negotiation sublayer exchanges technology capability data with its  
remote link partner and automatically selects the highest-performance operating mode it has in common  
with its remote link partner. For example, if the ICS1893 supports 100Base-TX and 10Base-T modes – but  
its link partner supports 100Base-TX and 100Base-T4 modes – the two devices automatically select  
100Base-TX as the highest-performance common operating mode. For details regarding initialization and  
control of the auto-negotiation process, see Section 7.2, “Functional Block: Auto-Negotiation”.  
5.5 100Base-TX Operations  
The ICS1893 100Base-TX mode provides 100Base-TX physical layer (PHY) services as defined in the  
ISO/IEC 8802-3 standard. In the 100Base-TX mode, the ICS1893 is a 100M translator between a  
MAC/repeater and the physical transmission medium. As such, the ICS1893 has two interfaces, both of  
which are fully configurable: one to the MAC/repeater and one to the Link Segment. In 100Base-TX mode,  
the ICS1893 provides the following functions:  
• Data conversion from both parallel-to-serial and serial-to-parallel formats  
• Data encoding/decoding (4B/5B, NRZ/NRZI, and MLT-3)  
• Data scrambling/descrambling  
• Data transmission/reception over a twisted-pair medium  
To accurately transmit and receive data, the ICS1893 employs DSP-based wave shaping, adaptive  
equalization, and baseline wander correction. In addition, in 100Base-TX mode, the ICS1893 provides a  
variety of control and status means to assist with Link Segment management. For more information on  
100Base-TX, see Section 7.4, “Functional Block: 100Base-TX TP-PMD Operations”.  
5.6 10Base-T Operations  
The ICS1893 10Base-T mode provides 10Base-T physical layer (PHY) services as defined in the ISO/IEC  
8802-3 standard. In the 10Base-T mode, the ICS1893 is a 10M translator between a MAC/repeater and the  
physical transmission medium. As such, the ICS1893 has two interfaces, both of which are fully  
configurable: one to the MAC/repeater and one to the Link Segment. In 10Base-T mode, the ICS1893  
provides the following functions:  
• Data conversion from both parallel-to-serial and serial-to-parallel formats  
• Manchester data encoding/decoding  
• Data transmission/reception over a twisted-pair medium  
In addition, in 10Base-T mode, the ICS1893 provides a variety of control and status means to assist with  
Link Segment management. For more information on 10Base-T, see Section 7.5, “Functional Block:  
10Base-T Operations”.  
5.7 Half-Duplex and Full-Duplex Operations  
The ICS1893 supports half-duplex and full-duplex operations for both 10Base-T and 100Base-TX  
applications. Full-duplex operation allows simultaneous transmission and reception of data, which  
effectively doubles the Link Segment throughput to either 20 Mbps (for 10Base-T operations) or 200 Mbps  
(for 100Base-TX operations).  
As per the ISO/IEC standard, full-duplex operations differ slightly from half-duplex operations. These  
differences are necessary, as during full-duplex operations a PHY actively uses both its transmit and  
receive data paths simultaneously.  
• In 10Base-T full-duplex operations, the ICS1893 disables its loopback function (that is, it does not  
automatically loop back data from its transmitter to its receiver) and disables its SQE Test function.  
• In both 10Base-T and 100Base-TX full-duplex operations, the ICS1893 asserts its CRS signal only in  
response to receive activity while its COL signal always remains inactive.  
For more information on half-duplex and full-duplex operations, see the following sections:  
• Section 8.2, “Register 0: Control Register”  
• Section 8.2.8, “Duplex Mode (bit 0.8)”  
• Section 8.3, “Register 1: Status Register”  
• Section 8.6, “Register 4: Auto-Negotiation Register”  
Chapter 6 Interface Overviews  
The ICS1893 MAC/Repeater Interface is fully configurable, thereby allowing it to accommodate many  
different applications.  
This chapter includes overviews of the following MAC/repeater-to-PHY interfaces:  
• Section 6.1, “MII Data Interface”  
• Section 6.2, “100M Symbol Interface”  
• Section 6.3, “10M Serial Interface”  
• Section 6.4, “Serial Management Interface”  
• Section 6.4, “Serial Management Interface”  
• Section 6.5, “Twisted-Pair Interface”  
• Section 6.6, “Clock Reference Interface”  
• Section 6.7, “Configuration Interface”  
• Section 6.8, “Status Interface”  
6.1 MII Data Interface  
The most common configuration for an ICS1893’s MAC/Repeater Interface is the Medium Independent  
Interface (MII) operating at either 10 Mbps or 100 Mbps. When the ICS1893 MAC/Repeater Interface is  
configured for the MII Data Interface mode, data is transferred between the PHY and the MAC/repeater as  
framed, 4-bit parallel nibbles. In addition, the interface also provides status and control signals to  
synchronize the transfers.  
The ICS1893 provides a full complement of the ISO/IEC-specified MII signals. Its MII has both a transmit  
and a receive data path to synchronously exchange 4 bits of data (that is, nibbles).  
• The ICS1893’s MII transmit data path includes the following:  
– A data nibble, TXD[3:0]  
– A transmit data clock to synchronize transfers, TXCLK  
– A transmit enable signal, TXEN  
– A transmit error signal, TXER  
• The ICS1893’s MII receive data path includes the following:  
– A separate data nibble, RXD[3:0]  
– A receive data clock to synchronize transfers, RXCLK  
– A receive data valid signal, RXDV  
– A receive error signal, RXER  
Both the MII transmit clock and the MII receive clock are provided to the MAC/Reconciliation sublayer by  
the ICS1893 (that is, the ICS1893 sources the TXCLK and RXCLK signals to the MAC/repeater).  
Clause 22 also defines as part of the MII a Carrier Sense signal (CRS) and a Collision Detect signal (COL).  
The ICs1893 is fully compliant with these definitions and sources both of these signals to the  
MAC/repeater. When operating in:  
• Half-duplex mode, the ICS1893 asserts the Carrier Sense signal when data is being either transmitted or  
received. While operating in half-duplex mode, the ICS1893 also asserts its Collision Detect signal to  
indicate that data is being received while a transmission is in progress.  
• Full-duplex mode, the ICS1893 asserts the Carrier Sense signal only when receiving data and forces the  
Collision Detect signal to remain inactive.  
As mentioned in Section 5.1.1.3, “Hot Insertion”, the ICS1893 design allows hot insertion of its MII. That is,  
it is possible to connect its MII to a MAC when power is already applied to the MAC. To support this  
functionality, the ICS1893 isolates its MII signals and tri-states the signals on all Twisted-Pair Transmit pins  
(TP_TXP and TP_TXN) during a power-on reset. Upon completion of the reset process, the ICS1893  
enables its MII and enables its Twisted-Pair Transmit signals.  
6.2 100M Symbol Interface  
The 100M Symbol Interface has a primary objective of supporting 100Base-TX repeater applications for  
which the repeater requires only recovered parallel data and for which the repeater provides all the  
necessary framing and control functions.  
When the ICS1893 MAC/Repeater Interface is configured for 100M Symbol operations, the PHY and the  
MAC/repeater exchange unframed 5-bit, parallel symbols at a 25-MHz clock rate.  
The configuration functions of the ICS1893 determine the operation of its MAC/Repeater Interface. The  
configuration functions are controlled by either input pins (in which case, the HW/SW pin is logic zero to  
select the hardware mode) or Management Register bits (in which case, the HW/SW pin is logic one to  
select the software mode).  
• In hardware mode, the ICS1893 enables the 100M Symbol Interface when both of the following are true:  
– Its MII/SI input pin is sampled as a logic one (that is, the selection is for the Symbol Interface).  
– Its 10/100SEL input pin is sampled as a logic one (that is, the selection is for 100M operations).  
• In software mode, the ICS1893 enables the 100M Symbol Interface when both the following are true:  
– Its MII/SI input pin is sampled as a logic one (that is, the selection is for the Symbol Interface).  
– Its Control Register Data Rate bit (bit 0.13) is set to logic one (that is, the selection is for selecting  
100M operations)  
The 100M Symbol Interface bypasses the ICS1893’s PCS and provides a direct, unscrambled, unframed,  
5-bit interface between the MAC/repeater and the PMA sublayer. A benefit of bypassing the PCS is a  
reduction in the latency through the PHY. That is, when the ICS1893’s MAC/Repeater Interface is  
configured as a 100M Symbol Interface, the bit delays through the PHY are smaller than the standard MII  
Data Interface can allow. The ICS1893 provides this 100M Symbol Interface primarily for Repeater  
applications, for which latency is a critical performance parameter.  
In addition to the exchange of symbol data, an ICS1893 configured for 100M Symbol mode provides  
ISO/IEC-compliant control signals (such as CRS) to the MAC/repeater. The ICS1893’s CRS signal  
provides a fast look-ahead, which can benefit a repeater application.  
In the 100M Symbol Interface mode, the ICS1893 continues to assert the CRS signal using its PCS logic.  
This action does not affect the bit delay or latency because the PCS CRS logic examines the bits received  
from the PMA sublayer serially. In fact, because the PCS CRS does not wait for a nibble or symbol to be  
constructed, the PCS CRS is available in advance of the symbol generation. Therefore, by using the PCS  
CRS generation logic, the ICS1893 can provide an ‘early’ indication of a Carrier Detect to the  
MAC/repeater.  
The 100M Symbol Interface consists of the following fourteen signals:  
• SCRS  
• SD  
• SRCLK  
• SRD[4:0]  
• STCLK  
• STD[4:0]  
When the ICS1893 MAC/Repeater Interface is configured for 100M Symbol operations, its default MII pin  
names and their associated functions are redefined. For more information, see Section 9.3.4.2,  
“MAC/Repeater Interface Pins for 100M Symbol Interface”.  
Table 6-1 lists the pin mappings for the ICS1893 100M Symbol Interface mode.  
Table 6-1. Pin Mappings for 100M Symbol Interface Mode  
Default  
10M / 100M  
MII Pin Names  
MAC/Repeater Interface Pin Mappings, Configured for  
100M Symbol Interface Mode  
COL  
No connect. [Because the MAC/repeater sources both active and ‘idle’ data, a PHY  
cannot distinguish between an active and idle transmission channel (that is, to a PHY  
the transmit channel always appears active). Therefore, a PHY cannot accurately  
detect a collision.]  
CRS  
SCRS  
MDC  
MDC  
MDIO  
RXCLK  
RXD0  
RXD1  
RXD2  
RXD3  
RXDV  
MDIO  
SRCLK  
SRD0  
SRD1  
SRD2  
SRD3  
No connect. (Data exchanged between the MAC/repeater and a PHY is not framed in  
the 100M Symbol Interface mode. Therefore, RXDV has no meaning.)  
RXER  
TXCLK  
TXD0  
TXD1  
TXD2  
TXD3  
TXEN  
SRD4  
STCLK  
STD0  
STD1  
STD2  
STD3  
No connect. (100Base-TX operations require continuous transmission of data.  
Therefore, the MAC/repeater is responsible for sourcing IDLE symbols when it is not  
transmitting data.)  
TXER  
STD4  
6.3 10M Serial Interface  
When the Mac/Repeater Interface is configured as a 10M Serial Interface, the ICS1893 and the  
MAC/repeater exchange a framed, serial bit stream along with associated control signals. The 10M Serial  
Interface configuration is ideally suited to applications that already incorporate a serial 10Base-T MAC with  
a standard ‘7-wire’ interface. The ICS1893 MAC/Repeater Interface can be configured for 10M Serial  
Interface operations, as determined by ICS1893 configuration functions. When the HW/SW pin is set for:  
• Hardware mode, the 10M Serial Interface is selected when both of the following are true:  
– The MII/SI input pin is logic one (that is, the selection is for a Serial Interface).  
– The 10/100SEL input pin is logic zero (that is, the selection is for 10M operations).  
• Software mode, the 10M Serial Interface is selected when both of the following are true:  
– The MII/SI input pin is logic one (that is, the selection is for a Serial Interface).  
– The Control Register Data Rate bit (bit 0.13) is logic zero (that is, the selection is for 10M operations).  
Note: In software mode, the 10/100SEL pin becomes an output that indicates the state of bit 0.13.  
A10M Serial Interface has two data paths: one for data transmission and one for data reception. Each data  
path exchanges a serial bit stream with the MAC/repeater at a 10-MHz clock rate. A benefit of using the  
10M Serial Interface – in contrast to the 10M MII Interface – is a reduction in the bit latency through the  
ICS1893. This reduction is attributed to eliminating both parallel-to-serial and serial-to-parallel data  
conversions.  
The 10M Serial Interface consists of the following eight signals:  
• 10COL  
• 10CRS  
• 10RCLK  
• 10RD  
• 10RXDV  
• 10TCLK  
• 10TD  
• 10TXEN  
When the ICS1893’s MAC/Repeater Interface is configured for 10M Serial operations, both its default MII  
pin names and their associated functions are redefined. For more information, see Section 9.3.4.3,  
“MAC/Repeater Interface Pins for 10M Serial Interface”.  
Table 6-2 lists the pin mappings for the ICS1893 10M Serial Interface mode.  
Table 6-2. Pin Mappings for 10M Serial Interface Mode  
Default  
10M / 100M  
MII Pin Names  
MAC/Repeater Interface Pin Mappings, Configured for  
10M Serial Interface Mode  
COL  
10COL  
10CRS  
MDC  
CRS  
MDC  
MDIO  
MDIO  
RXCLK  
RXD0  
RXD[3:1]  
RXDV  
RXER  
TXCLK  
TXD0  
10RCLK  
10RD  
No connect. [Data reception is serial, so only the 10RD (RXD0) pin is needed.]  
10RXDV  
No connect. (10Base-T mode does not support error generation or detection.)  
10TCLK  
10TD  
TXD[3:1]  
TXEN  
TXER  
No connect. [Data transmission is serial, so only the 10TD (TXD0) pin is needed.]  
10TXEN  
No connect. (10Base-T mode does not support error generation or detection.)  
6.4 Serial Management Interface  
The ICS1893 provides an ISO/IEC compliant, two-wire Serial Management Interface as part of its  
MAC/Repeater Interface. This Serial Management Interface is used to exchange control, status, and  
configuration information between a Station Management entity (STA) and the physical layer device (PHY),  
that is, the ICS1893.  
The ISO/IEC standard also specifies a frame structure and protocol for this interface as well as a set of  
Management Registers that provide the STA with access to a PHY such as the ICS1893. A Serial  
Management Interface is comprised of two signals: a bi-directional data pin (MDIO) along with an  
associated input pin for a clock (MDC). The clock is used to synchronize all data transfers between the  
ICS1893 and the STA.  
In addition to the ISO/IEC defined registers, the ICS1893 provides several extended status and control  
registers to provide more refined control of the MII and MDI interfaces. For example, the QuickPoll Detailed  
Status Register provides the ability to acquire the most-important status functions with a single MDIO read.  
Note: In the ICS1893, the MDIO and MDC pins remain active for all the MAC/Repeater Interface modes  
(that is, 10M MII, 100M MII, 100M Symbol, and 10M Serial).  
6.5 Twisted-Pair Interface  
For the twisted-pair interface, the ICS1893 uses 1:1 ratio transformers for both transmit and receive.  
Better operation results from using a split ground plane through the transformer. In this case:  
• The RJ-45 transformer windings must be on the chassis ground plane along with the Bob Smith  
termination.  
• The ICS1893 system ground plane must include the ICS1893-side transformer windings along with the  
61.9W resistors and the 120-nH inductor.  
• The transformer provides the isolation with one set of windings on one ground plane and another set of  
windings on the second ground plane.  
6.5.1 Twisted-Pair Transmitter Interface  
The twisted-pair transmitter driver uses an H-bridge configuration, which requires that the transmit  
transformer not have a choke on the chip side. ICS suggests any of the following for the H-bridge:  
• Halo TG22S012ND transformer  
• Transpower HB617-LP transformer  
• Pulse 68517 transformer, which can be turned around to move the choke windings to the RJ-45 side  
Figure 6-1 shows the design for the ICS1893 twisted-pair transmitter interface.  
• Two 61.9W 1% resistors are in series, with a 120-nH 5% inductor between them. These components  
form a network that connects across both the transformer and the ICS1893 TP_TXP and TP_TXN pins.  
• The ICS1893 supplies the power to the transformer. (No VDD connection is required.)  
• The ICS1893 TP_CT pin is connected directly to the transformer transmit center tap connection and is  
bypassed to ground with a 100-pF capacitor. The transformer center tap must not connect to the  
resistor/inductor network.  
Note:  
1. If the transmit transformer has a choke, put a choke on the RJ-45 side. Do not put a choke on the  
ICS1893 side of the transformer for the transmit windings.  
2. Keep all TX traces as short as possible.  
3. When making board traces, 50W-characteristic impedance is desirable  
4. Include a 0W resistor in series with TP_CT. (Some systems work better without the TP_CT  
connection.)  
Figure 6-1. ICS1893 Transmit Twisted Pair  
System Ground Plane Chassis Ground Plane  
Separate Ground Plane  
1:1  
TP_TXP 5  
61.9W 1%  
Center  
Tap  
To RJ-45  
120 nH  
61.9W 1%  
0W  
ICS1893  
TP_TXN 6  
TP_CT 3  
75W  
100 pF  
0.1 mF  
Ideally, for these traces Z = 50W.  
o
6.5.2 Twisted-Pair Receiver Interface  
Figure 6-2 shows the design for the ICS1893 twisted-pair receiver interface.  
• Two 56.2W 1% resistors are in series, with the center bypassed to ground with a 0.1-mF bypass  
capacitor.  
• No bypass capacitor is used with the receive transformer center tap.  
• A 4.7-pF capacitor must be included across the ICS1893 side of the receive transformer.  
Note:  
1. Keep leads as short as possible.  
2. Install the resistor network as close to the ICS1893 as possible.  
Figure 6-2. ICS1893 Receiver Twisted Pair  
System Ground Plane Chassis Ground Plane  
SeparateGround  
Plane  
1:1  
TP_RXP 13  
56.2W 1%  
Center  
Tap  
4.7 pF  
To RJ-45  
ICS1893  
0.1 mF  
56.2W 1%  
TP_RXN 14  
75W  
0.1 mF 2 kV  
6.6 Clock Reference Interface  
The REF_IN pin provides the ICS1893 Clock Reference Interface. The ICS1893 requires a single clock  
reference with a frequency of 25 MHz ±50 parts per million. This accuracy is necessary to meet the  
interface requirements of the ISO/IEEE 8802-3 standard, specifically clauses 22.2.2.1 and 24.2.3.4. The  
ICS1893 supports two clock source configurations: a CMOS oscillator or a CMOS driver. The input to  
REF_IN is CMOS (10% to 90% VDD), not TTL.  
6.7 Configuration Interface  
The following Configuration and Status Interface pins allow the ICS1893 to be completely configured and  
controlled in hardware mode:  
• 10/100SEL  
• ANSEL  
• DPXSEL  
• HW/SW  
• MII/SI  
• NOD/REP  
• RESETn  
• RXTRI  
These pins allow the ICS1893 to accommodate the following:  
• 10M or 100M operations  
• Four MAC/Repeater Interface configurations:  
– 10M MII  
– 100M MII  
– 100M Symbol  
– 10M Serial  
• Node or repeater applications  
• Full-duplex or half-duplex data links  
In addition to the ISO/IEC-specified, MII control signals, the ICS1893 provides RXTRI, which is a tri-state  
enable pin for the MII receive data path. When this pin is active (that is, a logic one), the following pins are  
tri-stated:  
• RXCLK  
• RXD[3:0]  
• RXDV  
• RXER  
Functionally, the RXTRI pin affects the MII receive channel in the same way as the Control Register’s  
isolate bit, bit 0.10. (The isolate bit also affects the transmit data path.) The ICS1893 can tri-state these  
seven signals for all five types of MAC/Repeater Interface configurations, not just the MII interface.  
6.8 Status Interface  
The ICS1893 LSTA pin provides a Link Status, and its LOCK pin provides a Stream Cipher Locking Status.  
In addition, as listed in Table 6-3, the ICS1893 provides five multi-function configuration pins that report the  
results of continual link monitoring by providing signals that are intended for driving LEDs. (For the pin  
numbers, see Table 9.3.2.)  
Table 6-3. Pins for Monitoring the Data Link  
Pin  
P0AC  
LED Driven by the Pin’s Output Signal  
AC (Link Activity) LED  
P1CL  
P2LI  
CL (Collisions) LED  
LI (Link Integrity) LED  
P3TD  
P4RD  
TD (Transmit Data) LED  
RD (Receive Data) LED  
Note:  
1. During either a power-on reset or a hardware reset, each multi-function configuration pin is an input  
that is sampled when the ICS1893 exits the reset state. After sampling is complete, these pins are  
output pins that can drive status LEDs.  
2. A software reset does not affect the state of a multi-function configuration pin. During a software reset,  
all multi-function configuration pins are outputs.  
3. Each multi-function configuration pin must be pulled either up or down with a resistor to establish the  
address of the ICS1893. LEDs may be placed in series with these resistors to provide a designated  
status indicator as described in Table 6-3.  
Caution: All pins listed in Table 6-3 must not float.  
4. As outputs, the asserted state of a multi-function configuration pin is the inverse of the sense sampled  
during reset. This inversion provides a signal that can illuminate an LED during an asserted state. For  
example, if a multi-function configuration pin is pulled down to ground through an LED and a  
current-limiting resistor, then the sampled sense of the input is low. To illuminate this LED for the  
asserted state, the output is driven high.  
5. Adding 10KW resistors across the LEDs ensures the PHY address is fully defined during slow VDD  
power-ramp conditions.  
6. PHY address 00 tri-states the MII interface. (Do not select PHY address 00 unless you want the MII  
tri-stated.)  
Figure 6-3 shows typical biasing and LED connections for the ICS1893.  
Figure 6-3. ICS1893 LED - PHY Address  
ICS1893  
P4RD  
64  
P3TD  
62  
P2LI  
60  
P1CL  
59  
P0AC  
55  
REC  
LINK  
ACTIVITY  
COL  
TRANS  
VDD  
10KW  
10KW  
1KW  
LED  
10KW  
1KW  
LED  
10KW  
1KW  
LED  
10KW  
This circuit decodes to PHY address = 1.  
Note:  
1. All LED pins must be set during reset.  
2. PHY address 00 tri-states the MII interface.  
3. For more reliable address capture during power-on reset, add a 10KW resistor across  
the LED.  
Chapter 7 Functional Blocks  
This chapter discusses the following ICS1893 functional blocks.  
• Section 7.1, “Functional Block: Media Independent Interface”  
• Section 7.2, “Functional Block: Auto-Negotiation”  
• Section 7.3, “Functional Block: 100Base-X PCS and PMA Sublayers”  
• Section 7.4, “Functional Block: 100Base-TX TP-PMD Operations”  
• Section 7.5, “Functional Block: 10Base-T Operations”  
• Section 7.6, “Functional Block: Management Interface”  
7.1 Functional Block: Media Independent Interface  
All ICS1893 MII interface signals are fully compliant with the ISO/IEC 8802-3 standard. In addition, the  
ICS1893 MIIs can support two data transfer rates: 25 MHz (for 100Base-TX operations) and 2.5 MHz (for  
10Base-T operations).  
The Media Independent Interface (MII) consists of two primary components:  
1. An interface between a MAC (Media Access Control sublayer) and the PHY (that is, the ICS1893). This  
MAC-PHY part of the MII consists of three subcomponents:  
a. A synchronous Transmit interface that includes the following signals:  
(1) A data nibble, TXD[3:0]  
(2) An error indicator, TXER  
(3) A delimiter, TXEN  
(4) A clock, TXCLK  
b. A synchronous Receive interface that includes the followings signals:  
(1) A data nibble, RXD[3:0]  
(2) An error indicator, RXER  
(3) A delimiter, RXDV  
(4) A clock, RXCLK  
c. A Media Status or Control interface that consists of a Carrier Sense signal (CRS) and a Collision  
Detection signal (COL).  
2. An interface between the PHY (the ICS1893) and an STA (Station Management entity). The STA-PHY  
part of the MII is a two-wire, Serial Management Interface that consists of the following:  
a. A clock (MDC)  
b. A synchronous, bi-directional data signal (MDIO) that provides an STA with access to the ICS1893  
Management Register set  
The ICS1893 Management Register set (discussed in Chapter 8, “Management Register Set”) consists of  
the following:  
• Basic Management registers.  
As defined in the ISO/IEC 8802-3 standard, these registers include the following:  
– Control Register (register 0), which handles basic device configuration  
– Status Register (register 1), which reports basic device capabilities and status  
• Extended Management registers.  
As defined in the ISO/IEC 8802-3 standard, the ICS1893 supports Extended registers that provide  
access to the Organizationally Unique Identifier and all auto-negotiation functionality.  
• ICS (Vendor-Specific) Management registers.  
The ICS1893 provides vendor-specific registers for enhanced PHY operations. Among these is the  
QuickPoll Detailed Status Register that provides a comprehensive and consolidated set of real-time PHY  
information. Reading the QuickPoll register enables the MAC to obtain comprehensive status data with  
a single register access.  
7.2 Functional Block: Auto-Negotiation  
The auto-negotiation logic of the ICS1893 has the following main functions:  
• To determine the capabilities of the remote link partner, (that is, the device at the other end of the link  
segment’s medium or cable)  
• To advertise the capabilities of the ICS1893 to the remote link partner  
• To establish a protocol with the remote link partner using the highest-performance operating mode that  
they have in common  
The design of the ICS1893 Auto-Negotiation sublayer supports both legacy 10Base-T connections as well  
as new connections that have multiple technology options for the link. For example, when the ICS1893 has  
the auto-negotiation process enabled and it is operating with a 10Base-T remote link partner, the ICS1893  
monitors the link and automatically selects the 10Base-T operating mode – even though the remote link  
partner does not support auto-negotiation. This process, called parallel detection, is automatic and  
transparent to the remote link partner and allows the ICS1893 to function seamlessly with existing legacy  
network structures without any management intervention.  
(For an overview of the auto-negotiation process, see Section 5.4, “Auto-Negotiation Operations”.)  
7.2.1 Auto-Negotiation General Process  
The Auto-Negotiation sublayer uses a physical signaling technique that is transparent at the packet level  
and all higher protocol levels. This technique builds on the link pulse mechanism employed in 10Base-T  
operations and is fully compliant with clause 28 of the ISO/IEC 8802-3 standard.  
During the auto-negotiation process, both the ICS1893 and its remote link partner use Fast Link Pulses  
(FLPs) to simultaneously ‘advertise’ (that is, exchange) information on their respective technology  
capabilities as follows:  
1. For the auto-negotiation process to take place, both the ICS1893 and its remote link partner must first  
both support and be enabled for Auto-Negotiation.  
2. The ICS1893 obtains the data for its FLP bursts from the Auto-Negotiation Advertisement Register  
(Register 4).  
3. Both the ICS1893 and the remote link partner substitute Fast Link Pulse (FLP) bursts in place of the  
Normal Link Pulses (NLPs). In each FLP burst, the ICS1893 transmits information on its technology  
capability through its Link Control Word, which includes link configuration and status data.  
4. Similarly, the ICS1893 places the Auto-Negotiation data received from its remote link partner's FLP  
bursts into the Auto-Negotiation Link Partner Ability Register (Register 5).  
5. After the ICS1893 and its remote link partner exchange technology capability information, the ICS1893  
Auto-Negotiation sublayer contrasts the data in Registers 4 and 5 and automatically selects for the  
operating mode the highest-priority technology that both Register 4 and 5 have in common. (That is,  
both the ICS1893 and its remote link partner use a predetermined priority list for selecting the operating  
mode, thereby ensuring that both sides of the link make the same selection.) As follows from Annex  
28B of the ISO/IEC 8802-3 standard, the pre-determined technology priorities are listed from 1 (highest  
priority) to 5 (lowest priority):  
(1) 100Base-TX full duplex  
(2) 100Base-T4. (The ICS1893 does not support this technology.)  
(3) 100Base-TX (half duplex)  
(4) 10Base-T full duplex  
(5) 10Base-T (half duplex)  
Table 7-1 shows an example of how the selection process of the highest-priority technology takes  
place.  
Table 7-1. Example of Selection Process of Highest-Priority Technology  
If Register 4 Has These  
Technologies:  
If Register 5 Has These  
Technologies:  
Resulting Highest-Priority Common  
Technology from Auto-Negotiation  
Sublayer  
(3) 100Base-TX half duplex (1) 100Base-TX full duplex (3) 100Base-TX half duplex  
(4) 100Base-T full duplex (3) 100Base-TX half duplex  
6. To indicate that the auto-negotiation process is complete, the ICS1893 sets bits 1.5 and 17.4 high to  
logic one. After successful completion of the auto-negotiation process, the ICS1893 Auto-Negotiation  
sublayer performs the following steps:  
a. It sets to logic one the Status Register’s Auto-Negotiation Complete bit (bit 1.5, which is also  
available in the QuickPoll register as bit 17.4).  
b. It enables the negotiated link technology (such as the 100Base Transmit modules and 100Base  
Receive modules).  
c. It disables the unused technologies to reduce the overall power consumption.  
7.2.2 Auto-Negotiation: Parallel Detection  
The ICS1893 supports parallel detection. It is therefore compatible with networks that do not support the  
auto-negotiation process. When enabled, the Auto-Negotiation sublayer can detect legacy 10Base-T link  
partners as well as 100Base-TX link partners that do not have an auto-negotiation capability.  
The Auto-Negotiation sublayer performs this parallel detection function when it does not get a response to  
its FLP bursts. In these situations, the Auto-Negotiation sublayer performs the following steps:  
1. It sets the LP_AutoNeg_Able bit (bit 6.0) to logic zero, thereby identifying the remote link partner as not  
being capable of executing the auto-negotiation process.  
2. It sets the bit in the Auto-Negotiation Link Partner Abilities Register that corresponds to the 'parallel  
detected' technology [for example, half-duplex, 10Base-T (bit 5.5) or half-duplex, 100Base-TX (bit  
5.7)].  
3. It sets the Status Register’s Auto-Negotiation Complete bit (bit 1.5) to logic one, indicating completion  
of the auto-negotiation process.  
4. It enables the detected link technology and disables the unused technologies.  
A remote link partner that does not support the auto-negotiation process does not respond to the  
transmitted FLP bursts. The ICS1893 detects this situation and responds according to the data it receives.  
The ICS1893 can receive one of five potential responses to the FLP bursts it is transmitting: FLP bursts,  
10Base-T link pulses (that is, Normal Link Pulses), scrambled 100Base IDLEs, nothing, or a combination of  
signal types.  
A 10Base-T link partner transmits only Normal Link Pulses when idle. When the ICS1893 receives Normal  
Link Pulses, it concludes that the remote link partner is a device that can use only 10Base-T technology. A  
100Base-TX node without an Auto-Negotiation sublayer transmits 100M scrambled IDLE symbols in  
response to the FLP bursts. Upon receipt of the scrambled IDLEs, the ICS1893 concludes that its remote  
link partner is a 100Base-TX node that does not support the auto-negotiation process. For both 10Base-T  
and 100Base-TX nodes without an Auto-Negotiation sublayer, the ICS1893 clears bit 6.0 to logic zero,  
indicating that the link partner cannot perform the auto-negotiation process.  
If the remote link partner responds to the FLP bursts with FLP bursts, then the link partner is a 100Base-TX  
node that can support the auto-negotiation process. In this case, the ICS1893 sets to logic one the  
Auto-Negotiation Expansion Register’s Link Partner Auto-Negotiation Ability bit (bit 6.0).  
If the Auto-Negotiation sublayer does not receive any signal when monitoring the receive channel, then the  
QuickPoll Detailed Status Register’s Signal Detect bit (bit 17.3) is set to logic one, indicating that no signal  
is present.  
Another possibility is that the ICS1893 senses that it is receiving multiple technology indications. In this  
situation, the ICS1893 cannot determine which technology to enable. It informs the STA of this problem by  
setting to logic one the Auto-Negotiation Expansion Register’s Parallel Detection Fault bit (bit 6.4).  
7.2.3 Auto-Negotiation: Remote Fault Signaling  
If the remote link partner detects a fault, the ICS1893 reports the remotely detected fault to the STA by  
setting to logic one the Remote Fault Detected bit(s), 1.4, 5.13, 17.1, and 19.13. In general, the reception  
of a remote fault means that the remote link partner has a problem with the integrity of its receive channel.  
Similarly, if the ICS1893 detects a link fault, it transmits a remote fault-detected condition to its remote link  
partner. In this situation, the ICS1893 sets to logic one the Auto-Negotiation Link Partner Ability Register’s  
Remote Fault Indication bit (bit 4.13).  
For details, see Section 8.14.3, “Remote Fault (bit 19.13)” and Section 8.3.9, “Remote Fault (bit 1.4)”.  
7.2.4 Auto-Negotiation: Reset and Restart  
If enabled, execution of the ICS1893 auto-negotiation process occurs at power-up and upon management  
request. There are two primary ways to begin the Auto-Negotiation state machine:  
• ICS1893 reset  
• Auto-Negotiation Restart  
7.2.4.1 Auto-Negotiation Reset  
During a reset, the ICS1893 initializes its Auto-Negotiation sublayer modules to their default states. (That  
is, the Auto-Negotiation Arbitration State Machine and the Auto-Negotiation Progress Monitor reset to their  
idle states.) In addition, the Auto-Negotiation Progress Monitor status bits are all set to logic zero. This  
action occurs for any type of reset (hardware reset, software reset, or power-on reset).  
7.2.4.2 Auto-Negotiation Restart  
As with a reset, during an Auto-Negotiation restart, the ICS1893 initializes the Auto-Negotiation Arbitration  
State Machine and the Auto-Negotiation Progress Monitor modules to their default states. However, during  
an Auto-Negotiation Restart, the Auto-Negotiation Progress Monitor status bits maintain their current state.  
Only three events can alter the state of the Auto-Negotiation Progress Monitor status bits after a Restart:  
(1) an STA read operation, (2) a reset, or (3) the Auto-Negotiation Arbitration State Machine progressing to  
a higher state or value.  
The Auto-Negotiation Progress Monitor Status bits change only if they are progressing to a state with a  
value greater than their current state (that is, a state with a higher logical value than that of their current  
state). For a detailed explanation of these bits and their operation, see Section 7.2.5, “Auto-Negotiation:  
Progress Monitor”.  
After the Auto-Negotiation Arbitration State Machine reaches its final state (which is Auto-Negotiation  
Complete), only an STA read of the QuickPoll Detailed Status Register or an ICS1893 reset can alter these  
status bits.  
Any of the following situations initiates a restart of the ICS1893 Auto-Negotiation sublayer:  
• A link failure  
• In software mode:  
– Writing a logic one to the Control Register’s Restart Auto-Negotiation bit (bit 0.9), which is a self-  
clearing bit.  
– Toggling the Control Register’s Auto-Negotiation Enable bit (bit 0.12) from a logic one to a logic zero,  
and back to a logic one.  
• In hardware mode:  
– Toggling the ANSEL (Auto-Negotiation Select) pin from a logic one to a logic zero, and back to a  
logic one.  
7.2.5 Auto-Negotiation: Progress Monitor  
Under typical circumstances, the Auto-Negotiation sublayer can establish a connection with the ICS1893’s  
remote link partner. However, some situations can prevent the auto-negotiation process from properly  
achieving this goal. For these situations, the ICS1893 has an Auto-Negotiation Progress Monitor to provide  
detailed status information to its Station Management (STA) entity. With this status information, the STA  
can diagnose the failure mechanism and – in some situations – establish the link by correcting the problem.  
When enabled, the auto-negotiation process typically requires less than 500 ms to execute, independent of  
the link partner's ability to perform the auto-negotiation process. Typically, an STA polls both the  
Auto-Negotiation Complete bit (bit 1.5) and the Link Status bit (bit 1.2) to determine when a link is  
successfully established, either through auto-negotiation or parallel detection. The STA can then poll the  
Auto-Negotiation Link Partner Ability Register and determine the highest-performance operating mode in  
common with the capabilities it is advertising.  
The ISO/IEC-defined priority table determines the established link type. As a simpler alternative, the STA  
can read the QuickPoll Detailed Status Register and determine the link type from the Data Rate bit (bit  
17.15) and the Duplex bit (bit 17.14). For convenience, the QuickPoll Register also includes the Link Status  
bit (bit 17.0) and the Auto-Negotiation Complete bit (bit 17.4).  
If (1) the auto-negotiation process does not complete, or (2) the link is not established, or (3) both the  
auto-negotiation process does not complete and the link is not established, then the STA can determine the  
cause of the link failure by using the outputs of the ICS1893 Auto-Negotiation Progress Monitor.  
The Auto-Negotiation Progress Monitor provides the STA with four status bits of data to indicate both the  
history and the present state of the auto-negotiation process. This status data is provided in the QuickPoll  
Detailed Status register by using the Auto-Negotiation Complete bit (bit 17.4) as well as bits 17.13:11. The  
bit order, from most-significant bit to least-significant bit, is 17.4, 17.13, 17.12, and 17.11. Using these four  
bits, the Auto-Negotiation Progress Monitor provides nine state codes detailing the operation of the  
auto-negotiation process for the STA. [For more information, see Section 8.12.3, “Auto-Negotiation  
Progress Monitor (bits 17.13:11)”.]  
The nine Auto-Negotiation Progress Monitor state codes are 0h through 8h and Fh. The Auto-Negotiation  
Progress Monitor automatically latches the values of the Auto-Negotiation Arbitration State Machine into  
the status bits only if the value of the present state is greater than the value that is currently in the status  
bits.  
For example, if the status bits have a value of 3h and the auto-negotiation process moves into:  
• State 1, the Auto-Negotiation Progress Monitor does not update the status bits to indicate the new state.  
• State 5, the Auto-Negotiation Progress Monitor updates the status bits to indicate the new state, State 5.  
In this case, the status bits increase in value until either the auto-negotiation process successfully  
completes or the STA reads the Auto-Negotiation Progress Monitor status bits.  
When the STA reads the status bits, the present state of the auto-negotiation process is automatically  
latched into the status bits, regardless of how they compare to the value currently in the latch. However,  
the read presents the STA with the previously latched values of the status bits, not the values just  
latched into the status register by the read. Therefore, the STA must perform two reads of the status bits  
to determine the present state of the Auto-Negotiation Arbitration State Machine.  
The first read provides a 'history' of the auto-negotiation process, (that is, the highest state achieved by  
the auto-negotiation process). The second read provides the present state of the auto-negotiation  
process. This behavior allows management to determine the greatest forward progress made by the  
auto-negotiation logic, which is valuable for diagnosing link errors and failures.  
Note: Once the auto-negotiation process completes successfully, the value of all the Progress Monitor  
status bits and the Auto-Negotiation Complete bit have a value of logic one. A read operation of the  
QuickPoll Register provides a value of logic one for the Auto-Negotiation Complete bit and an octal  
value of 111 for the status bits.  
Subsequent reads of the QuickPoll Register also provide a value of logic one for the  
Auto-Negotiation Complete bit. However, the value of the status bits are 000b, providing the link  
remains established.  
7.3 Functional Block: 100Base-X PCS and PMA Sublayers  
The ICS1893 is fully compliant with clause 24 of the ISO/IEC specification, which defines the 100Base-X  
Physical Coding sublayer (PCS) and Physical Medium Attachment (PMA) sublayers.  
7.3.1 PCS Sublayer  
The ICS1893 100Base-X PCS sublayer provides two interfaces: one to a MAC/repeater and the other to  
the ICS1893 PMA sublayer. An ICS1893’s PCS sublayer performs the transmit, receive, and control  
functions and consists of the following:  
• PCS Transmit sublayer, which provides the following:  
– Parallel-to-serial conversion  
– 4B/5B encoding  
– Collision detection  
• PCS Receive sublayer, which provides the following:  
– Serial-to-parallel conversion  
– 4B/5B encoding  
– Carrier detection  
– Code group framing  
• PCS control functions, which provide:  
– Assertion of the CRS (carrier sense) signal  
– Assertion of the COL (collision detection) signal  
Note: When configured for 100M Symbol mode operations, the MAC/Repeater Interface bypasses most  
of the PCS. When the ICS1893 MAC/Repeater Interface is in this mode, most of its PCS Transmit  
and Receive modules are inactive. However, its PCS control functions (CRS and COL) remain  
operational.  
7.3.2 PMA Sublayer  
The ICS1893 100Base-X PMA Sublayer consists of two interfaces: one to the Physical Coding sublayer  
and the other to the Physical Medium Dependent sublayer. Functionally, the PMA sublayer is responsible  
for the following:  
• Link Monitoring  
• Carrier Detection  
• NRZI encoding/decoding  
• Transmit Clock Synthesis  
• Receive Clock Recovery  
7.3.3 PCS/PMA Transmit Modules  
Both the PCS and PMA sublayers have Transmit modules.  
7.3.3.1 PCS Transmit Module  
The ICS1893 PCS Transmit module accepts nibbles from the MAC/Repeater Interface and converts the  
nibbles into 5-bit ‘code groups’ (referred to here as ‘symbols’). In addition, the PCS Transmit module  
performs a parallel-to-serial conversion on the symbols, and subsequently passes the resulting serial bit  
stream to the PMA sublayer.  
The first 16 nibbles of each MAC/Repeater Frame represent the Frame Preamble. The PCS replaces the  
first two nibbles of the Frame Preamble with the Start-of-Stream Delimiter (SSD), that is, the symbols /J/K/.  
After receipt of the last Frame nibble, detected when TX_EN = FALSE, the PCS appends to the end of the  
Frame an End-of-Stream Delimiter (ESD), that is, the symbols /T/R/. (The ICS1893 PCS does not alter any  
other data included within the Frame.)  
The PCS Transmit module also performs collision detection. In compliance with the ISO/IEC specification,  
when the transmission and reception of data occur simultaneously and the ICS1893 is in:  
• Half-duplex mode, the ICS1893 asserts the collision detection signal (COL).  
• Full-duplex mode, COL is always FALSE.  
7.3.3.2 PMA Transmit Module  
The ICS1893 PMA Transmit module accepts a serial bit stream from its PCS and converts the data into  
NRZI format. Subsequently, the PMA passes the NRZI bit stream to the Twisted-Pair Physical Medium  
Dependent (TP-PMD) sublayer.  
The ICS1893 PMA Transmit module uses a digital PLL to synthesize a transmit clock from the Clock  
Reference Interface. When the ICS1893 is configured for an interface that is:  
• 10M MII (that is, 10Base-T), the TXCLK signal is 2.5 MHz  
• 10M Serial Interface, the TXCLK signal is 10 MHz  
• Either of the following, the TXCLK signal (a buffered version of the REF_IN signal) is 25 MHz:  
– 100M MII (that is, 100Base-TX)  
– 100M Symbol Interface  
Note:  
1. All of the TXCLK signals are derived from the REF_IN signal that goes to the digital PLL.  
2. For the MII, for both the 10Base-T and 100Base-TX modes, the clock that is generated synchronizes  
all data transfers across the MII.  
7.3.4 PCS/PMA Receive Modules  
Both the PCS and PMA sublayers have Receive modules.  
7.3.4.1 PCS Receive Module  
The ICS1893 PCS Receive module accepts both a serial bit stream and a clock signal from the PMA  
sublayer. The PCS Receive module converts the bit stream from a serial format to a parallel format and  
then processes the data to detect the presence of a carrier.  
When a link is in the idle state, the PCS Receive module receives IDLE symbols. (All bits are logic one.)  
Upon receiving two non-contiguous zeros in the bit stream, the PCS Receive module examines the  
ensuing bits and attempts to locate the Start-of-Stream Delimiter (SSD), that is, the /J/K/ symbols.  
Upon verification of a valid SSD, the PCS Receive module substitutes the first two standard nibbles of a  
Frame Preamble for the detected SSD. In addition, the PCS Receive module uses the SSD to begin  
framing the ensuing data into 5-bit code symbols. The final PCS Receive module performs 4B/5B decoding  
on the symbols and then synchronously passes the resulting nibbles to the MAC/Repeater Interface.  
The Receive state machine continues to accept PMA data, convert it from serial to parallel format, frame it,  
decode it, and pass it to the MAC/Repeater Interface. During this time, the Receive state machine  
alternates between Receive and Data States. It continues this process until detecting one of the following:  
• An End-of-Stream Delimiter (ESD, that is, the /T/R/ symbols)  
• An error  
• A premature end (IDLEs)  
Upon receipt of an ESD, the Receive state machine returns to the IDLE state without passing the ESD to  
the MAC/Repeater Interface. Detection of an error forces the Receive state machine to assert the receive  
error signal (RX_ER) and wait for the next symbol. If the ICS1893 Receive state machine detects a  
premature end, it forces the assertion of the RX_ER signal, sets the Premature End bit (bit 17.5) to logic  
one, and transitions to the IDLE State.  
7.3.4.2 PMA Receive Modules  
The ICS1893 has a PMA Receive module that provides the following functions:  
• NRZI Decoding  
The Receive module performs the NRZI decoding on the serial bit stream received from the Twisted-Pair  
Physical Medium Dependent (TP-PMD) sublayer. It converts the bit stream to a unipolar, positive, binary  
format that the PMA subsequently passes to the PCS.  
• Receive Clock Recovery  
The Receive Clock Recovery function consists of a phase-locked loop (PLL) that operates on the serial  
data stream received from the PMD sublayer. This PLL automatically synchronizes itself to the clock  
encoded in the serial data stream and then provides both a recovered clock and data stream to the PCS.  
• Link Monitoring  
– The ICS1893’s PMA Link Monitoring function observes the Receive Clock PLL. If the Receive Clock  
PLL cannot acquire ‘lock’ on the serial data stream, it asserts an error signal. The status of this error  
signal can be read in the QuickPoll Detailed Status Register’s PLL Lock Error bit (bit 17.9). This bit is  
a latching high (LH) bit. (For more information on latching high and latching low bits, see Section  
8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
– In addition, the ICS1893’s PMA Link Monitor function continually audits the state of the connection  
with the remote link partner. It asserts a receive channel error if a receive signal is not detected or if  
a PLL Lock Error occurs. These errors, in turn, generate a link fault and force the link monitor  
function to clear both the Status Register’s Link Status bit (bit 1.2) and the QuickPoll Detailed Status  
Register’s Link Status bit (bit 17.0).  
7.3.5 PCS Control Signal Generation  
For the PCS sublayer, there are two control signals: a Carrier Sense signal (CRS) and a Collision Detect  
signal (COL).  
The CRS control signals is generated as follows:  
1. When a logic zero is detected in an idle bit stream, the Receive Functions examines the ensuing bits.  
2. When the Receive Functions find the first two non-contiguous zero bits, the Receive state machine  
moves into the Carrier Detect state.  
3. As a result, the Boolean Receiving variable is set to TRUE.  
4. Consequently, the Carrier Sense state machine moves into the Carrier Sense ‘on’ state, which asserts  
the CRS signal.  
5. If the PCS Functions:  
a. Cannot confirm either the /I/J/ (IDLE, J) symbols or the /J/K/ symbols, the receive error signal  
(RX_ER) is asserted, and the Receive state machine returns to the IDLE state. In IDLE, the  
Boolean Receiving variable is set to FALSE, thereby causing the Carrier Sense state machine to  
set the CRS signal to FALSE.  
b. Can confirm the /I/J/K/ symbols, then the Receive state machine transitions to the ‘Receive’ state.  
The COL control signal is generated by the transmit modules. For details, see Section 7.3.3.1, “PCS  
Transmit Module”.  
7.3.6 4B/5B Encoding/Decoding  
The 4B/5B encoding methodology maps each 4-bit nibble to a 5-bit symbol (also called a “code group”).  
There are 32 five-bit symbols, which include the following:  
• Of the 32 five-bit symbols, 16 five-bit symbols are required to represent the 4-bit nibbles.  
• The remaining 16 five-bit symbols are available for control functions. The IEEE Standard defines 6  
symbols for control, and the remaining 10 symbols of this grouping are invalid. The 6 control symbols  
include the following:  
– /H/, which represents a Halt, also used to signify a Transmit Error  
– /I/, which represents an IDLE  
– /J/, which represents the first symbol of the Start-of-Stream Delimiter (SSD)  
– /K/, which represents the second symbol of the Start-of-Stream Delimiter (SSD)  
– /T/, which represents the first symbol of the End-of-Stream Delimiter (ESD)  
– /R/, which represents the second symbol of the End-of-Stream Delimiter (ESD)  
If the ICS1893 PCS receives:  
– One of the 10 undefined symbols, it sets its QuickPoll Detailed Status Register’s Invalid Symbol bit  
(bit 17.7) to logic one.  
– A Halt symbol, it sets the Halt Symbol Detected bit in its QuickPoll Detailed Status Register (bit 17.6)  
to logic one.  
Note: An STA can force the ICS1893 to transmit symbols that are typically classified as invalid, by both  
(1) setting the Extended Control Register’s Transmit Invalid Codes bit (bit 16.2) to logic one and (2)  
asserting the associated TXER signal. For more information, see Section 8.11.7, “Invalid Error  
Code Test (bit 16.2)”.  
7.4 Functional Block: 100Base-TX TP-PMD Operations  
The ICS1893 supports both 10Base-T and 100Base-TX operations. For 100Base-TX operations, the  
TP-PMD module performs stream-cipher scrambling/descrambling and MLT-3 encoding/decoding (3-level,  
multi-level transition) in compliance with the ANSI Standard X3.263: 199X FDDI TP-PMD as defined in the  
specification for 100Base-TX Twisted-Pair Physical Media Dependent (TP-PMD) Sublayer. The ICS1893’s  
TP-PMD also performs DC restoration (that is, baseline wander correction) and adaptive equalization on  
the received signals.  
Note:  
1. For an overview of 100Base-TX operations, see Section 5.5, “100Base-TX Operations”.  
2. For more information on the Twisted-Pair Interface, see Section 6.5, “Twisted-Pair Interface”.  
7.4.1 100Base-TX Operation: Stream Cipher Scrambler/Descrambler  
When the ICS1893 is operating in 100Base-TX mode, it employs a stream cipher scrambler/descrambler  
that complies with the ANSI Standard X3.263: 199X FDDI TP-PMD. The purpose of the stream cipher  
scrambler is to spread the transmission spectrum to minimize electromagnetic compatibility problems. The  
stream cipher descrambler restores the received serial bit stream to its unscrambled form.  
The ICS1893 “seeds” (that is, initializes) the Transmit Stream Cipher Shift register by using the ICS1893  
PHY address from Table 8-16, which minimizes crosstalk and noise in repeater applications.  
The MAC/Repeater Interface bypasses the stream cipher scrambler/descrambler when in the 100M  
Symbol Interface mode.  
7.4.2 100Base-TX Operation: MLT-3 Encoder/Decoder  
When operating in the 100Base-TX mode, the ICS1893 TP-PMD sublayer employs an MLT-3 encoder and  
decoder. During data transmission, the TP-PMD encoder converts the NRZI bit stream received from the  
PMA sublayer to a 3-level Multi-Level Transition code. The three levels are -1, 0, and +1. The results of  
MLT-3 encoding provide a reduction in the transmitted energy over the critical frequency range from 20  
MHz to 100 MHz. The TP-PMD MLT-3 decoder converts the received three-level signal back to an NRZI bit  
stream.  
7.4.3 100Base-TX Operation: DC Restoration  
The ICS1893’s 100Base-TX operations uses a stream-cipher scrambler to minimize peak amplitudes in the  
frequency spectrum. However, the nature of the stream cipher and MLT-3 encoding is such that long  
sequences of consecutive zeros or ones can exist. These unbalanced data patterns produce an  
undesirable DC component in the data stream known as ‘baseline wander’.  
Baseline wander adversely affects the noise immunity of the receiver, because the ‘baseline’ signal moves  
or ‘wanders’ from its nominal DC value. The ICS1893 uses a unique technique to restore the DC  
component ‘lost’ by the medium. As a result, the design is very robust, immune to noise and independent  
of the data stream.  
7.4.4 100Base-TX Operation: Adaptive Equalizer  
The ICS1893 has a TP-PMD sublayer that uses adaptive equalization circuitry to compensate for signal  
amplitude and phase distortion incurred from the transmission medium. At a data rate of 100 Mbps, the  
transmission medium (that is, the cable) introduces significant signal distortion because of high-frequency  
attenuation and phase shift. The high-frequency loss occurs primarily because of the cable skin effect that  
causes the conductor resistance to rise as the square of the frequency rises.  
The ICS1893 has an adaptive equalizer that accurately compensates for these losses in shielded  
twisted-pair (STP) and unshielded twisted-pair (UTP) cables. The DSP-based adaptive equalizer uses a  
technique that compensates for a wide range of cable lengths. The optimizing parameter for the  
equalization process is the overall bit error rate of the ICS1893. This technique closes the loop on the entire  
data reception process and provides a very high overall reliability.  
7.4.5 100Base-TX Operation: Twisted-Pair Transmitter  
The ICS1893 uses the same Twisted-Pair Transmit pins (TP_TXP and TP_TXN) for both 10Base-T and  
100Base-TX operations. Each twisted-pair transmitter module is a current-driven, differential driver that  
can supply either of the following:  
• A two-level 10Base-T (that is, Manchester-encoded) signal  
• A three-level 100Base-TX (that is, MLT-3 encoded) signal  
The ICS1893 interfaces with the medium through an isolation transformer (sometimes referred to as a  
magnetic module). The ICS1893’s transmitter uses wave-shaping techniques to control the output signal  
rise and fall times (thereby eliminating the need for external filters) and interfaces directly to the isolation  
transformer.  
Note:  
1. In reference to the ICS1893, the term ‘Twisted-Pair Transmitter’ refers to the set of Twisted-Pair  
Transmit output pins (TP_TXP and TP_TXN).  
2. For information on the 10Base-T Twisted-Pair Transmitter, see Section 7.5.11, “10Base-T Operation:  
Twisted-Pair Transmitter”.  
7.4.6 100Base-TX Operation: Twisted-Pair Receiver  
The ICS1893 uses the same Twisted-Pair Receive pins (TP_RXP and TP_RXN) for both 10Base-T and  
100Base-TX operations. The internal twisted-pair receiver modules interface with the medium through an  
isolation transformer. The 100Base-TX receiver module accepts and processes a differential three-level  
100Base-TX (that is, MLT-3 encoded) signal from the isolation transformer. (In contrast, the 10Base-T  
receiver module accepts and processes a differential two-level, Manchester- encoded, 10Base-T signal  
from the isolation transformer).  
Note:  
1. In reference to the ICS1893, the term ‘Twisted-Pair Receiver’ refers to the set of Twisted-Pair Receive  
output pins (TP_RXP and TP_RXN).  
2. For information on the 10Base-T Twisted-Pair Receiver, see Section 7.5.12, “10Base-T Operation:  
Twisted-Pair Receiver”.  
7.4.7 100Base-TX Operation: Auto Polarity Correction  
The ICS1893 can sense and then automatically correct a signal polarity that is reversed on its Twisted-Pair  
Receiver inputs. A signal polarity reversal occurs when the input signals on the TP_RXP and TP_RXN pins  
are crossed or swapped (a problem that can occur during network installation or wiring). This function is  
primarily a 10Base-T function, however, it is also active during Auto-Negotiation. For more information on  
the 10Base-T Auto Polarity Correction, see Section 7.5.13, “10Base-T Operation: Auto Polarity Correction”  
7.4.8 100Base-TX Operation: Isolation Transformer  
The ICS1893 interfaces with a medium through isolation transformers. The PHY requires two isolation  
transformers: one for its Twisted-Pair Transmitter and the other for its Twisted-Pair Receiver. These  
isolation transformers provide both physical isolation as well as the means for coupling a signal between  
the ICS1893 and the medium for both 10Base-T and 100Base-TX operations.  
Note: For information on isolation transformers (also referred to as magnetic modules), see Section 6.5,  
“Twisted-Pair Interface”.  
7.5 Functional Block: 10Base-T Operations  
When configured for 10Base-T mode, the ICS1893 MAC/Repeater Interface can be configured to provide  
either a 10M MII (Media Independent Interface) or a 10M Serial Interface. The Twisted-Pair Interface is  
automatically configured to provide a two-level, Manchester-encoded signal at the voltage levels specified  
in the ISO/IEC standard. (For more information on the Twisted-Pair Interface, see Section 6.5,  
“Twisted-Pair Interface”.)  
The 10Base-T and 100Base-TX operations differ as follows. 10Base-T operations are fundamentally  
simpler than 100Base-TX operations. The data rate is slower, requiring less encoding than 100Base-TX  
operations. In addition, the bandwidth requirements (and therefore the line attenuation issues) are not as  
severe as with 100-MHz operations. Consequently, when an ICS1893 is set for 10Base-T operations, it  
requires fewer internal circuits in contrast to 100Base-TX operations. (For an overview of 10Base-T  
operations, see Section 5.6, “10Base-T Operations”.).  
7.5.1 10Base-T Operation: Manchester Encoder/Decoder  
During data transmission the ICS1893 acquires data from its MAC/Repeater Interface in either 4-bit nibbles  
or as a serial bit stream. The ICS1893 converts this data into a Manchester-encoded signal for presentation  
to its MDI, as required by the ISO/IEC specification.  
In a Manchester-encoded signal, all logic:  
• Ones are:  
– Positive during the first half of the bit period  
– Negative during the second half of the bit period  
• Zeros are:  
– Negative during the first half of the bit period  
– Positive during the second half of the bit period  
During 10Base-T data reception, a Manchester Decoder translates the serial bit stream obtained from the  
Twisted-Pair Receiver (MDI) into an NRZ bit stream. The Manchester Decoder then passes the data to the  
MAC/Repeater Interface in either serial or parallel format, depending on the interface configuration.  
Manchester-encoded signals have the following advantages:  
• Every bit period has an encoded clock.  
• The split-phase nature of the signal always provides a zero DC level regardless of the data (that is, there  
is no baseline wander phenomenon).  
The primary disadvantage in using Manchester-encoded signals is that it doubles the data rate, making it  
operationally prohibitive for 100-MHz operations.  
7.5.2 10Base-T Operation: Clock Synthesis  
The ICS1893 synthesizes the clocks required for synchronizing data transmission. In 10Base-T mode, the  
MAC/Repeater Interface can provide either a 10M MII (Media Independent Interface) or a 10M Serial  
Interface. When the ICS1893 is configured to support a:  
• 10M MII interface, the ICS1893 synthesizes a 2.5-MHz clock for nibble-wide transactions  
• 10M Serial Interface to the MAC/repeater, the ICS1893 synthesizes a 10-MHz clock  
7.5.3 10Base-T Operation: Clock Recovery  
The ICS1893 recovers its receive clock from the Manchester-encoded data stream obtained from its  
Twisted-Pair Receiver using a phase-locked loop (PLL). The ICS1893 then uses this recovered clock for  
synchronizing data transmission between itself and the MAC/repeater. Receive-clock PLL acquisitions begin  
with reception of the MAC Frame Preamble and continue as long as the ICS1893 is receiving data.  
7.5.4 10Base-T Operation: Idle  
An ICS1893 transmits Normal Link Pulses (that is, 10Base-T Idles) on its MDI in the absence of data (that is,  
when the MAC/repeater is not requiring it to transmit any data). During this time the link is Idle, and the  
ICS1893 periodically transmits link pulses at a rate of one link pulse every 16 ms in compliance with the  
ISO/IEC 8802-3 standard. In 10Base-T mode, the ICS1893 continues transmitting link pulses even while  
receiving data. This situation does not generate a Collision Detect signal (COL) because link pulses indicate  
an idle state for a link.  
7.5.5 10Base-T Operation: Link Monitor  
When an ICS1893 is in 10Base-T mode, its Link Monitor Function observes the data received by the  
10Base-T Twisted-Pair Receiver to determine the link status. The results of this continual monitoring are  
stored in the Link Status bit. The Station Management entity (STA) can access the Link Status bit in either  
the Status Register (bit 1.2) or the QuickPoll Detailed Status Register (bit 17.0).  
When the Link Status bit is:  
• Zero, either a valid link is not established or the link is momentarily dropped since either the last read of  
the Link Status bit or the last reset of the ICS1893.  
• One, a valid link is established.  
The ICS1893 Link Status bit is a latching low (LL) bit. (For more information on latching high and latching  
low bits, see Section 8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
The criteria used by the Link Monitor Function to declare a link either valid (that is, ‘established’ or ‘up’) or  
invalid (that is, ‘failed’ or ‘down’) depends upon these factors: the present state of the link, whether its  
Smart Squelch function is enabled, and the incoming data.  
When the 10Base-T link is:  
• Invalid, and the Smart Squelch function is:  
– Disabled (bit 18.0 is logic zero), the Link Monitor Function must detect at least one of the following  
events before transitioning its link from the invalid state to the valid state:  
• More than seven, ISO/IEC-defined, Normal Link Pulses (NLPs)  
• Any valid data  
– Enabled (bit 18.0 is logic one), the Link Monitor Function must detect at least one of the following  
events before transitioning its link from the invalid state to the valid state:  
• More than seven, ISO/IEC-defined, Normal Link Pulses (NLPs)  
• Any valid data followed by a valid IDL  
• Valid, and the Smart Squelch function is:  
– Disabled (bit 18.0 is logic zero), the Link Monitor Function continues to report its link as valid as long  
as it continues to detect any of the following:  
• ISO/IEC-defined, Normal Link Pulses (NLPs)  
• Any valid data  
– Enabled (bit 18.0 is logic one), the Link Monitor Function continues to report its link as valid as long  
as it continues to detect any of the following:  
• ISO/IEC-defined, Normal Link Pulses (NLPs)  
• Any valid data followed by a valid IDL  
• Valid, the Link Monitor Function declares the link as invalid if it receives neither data nor NLPs (that is,  
the link shows either no activity or inconsistent activity) for more than 81 to 83 ms. In this case the Link  
Monitor Function sets the Link Status bit to logic zero.  
Note:  
1. An ICS1893 receives ‘valid data’ when its Twisted-Pair Receiver phase-locked loop can acquire lock  
and extract the receive clock from the incoming data stream for a minimum of three consecutive bit  
times.  
2. When a link is invalid and the Link Monitor Function detects the presence of data, the ICS1893 does  
not transition the link to the valid state until after the reception of the present packet is complete.  
3. Enabling or disabling the Smart Squelch Function affects the Link Monitor function.  
4. A transition from the invalid state to the valid state does not automatically update the latching-low Link  
Status bit.  
7.5.6 10Base-T Operation: Smart Squelch  
The Smart Squelch Function imposes more stringent requirements on the Link Monitor Function regarding  
the definition of a valid link, thereby providing a level of insurance that spurious noise is not mistaken for a  
valid link during cable installation.  
An STA can control the execution of the ICS1893 Smart Squelch Function using bit 18.0 (the Smart  
Squelch Inhibit bit in the 10Base-T Operations Register). When bit 18.0 is logic:  
• Zero (the default), an ICS1893 enables its Smart Squelch Function. In this case, the Link Monitor must  
confirm the presence of both data and a valid IDL at the end of the packet before declaring a link valid.  
• One, an ICS1893 disables or inhibits its Smart Squelch Function. In this case, the Link Monitor does not  
have to confirm the presence of an IDL to declare a link valid (that is, the reception of any data is  
sufficient).  
In 10Base-T mode, an ICS1893 appends an IDL to the end of each packet during data transmission. The  
receiving PHY (that is, the remote link partner) sees this IDL and removes it from the data stream.  
7.5.7 10Base-T Operation: Carrier Detection  
The ICS1893 has a 10Base-T Carrier Detection Function that establishes the state of its Carrier Sense  
signal (CRS), based upon the state of its Transmit and Receive state machines. These functions indicate  
whether the ICS1893 is (1) transmitting data, (2) receiving data, or (3) in a collision state (that is, the  
ICS1893 is both transmitting and receiving data on its twisted-pair medium, as defined in the ISO/IEC  
8802-3 standard). When the ICS1893 is configured for:  
• Half-duplex operations, the ICS1893 asserts its CRS signal when either transmitting or receiving data.  
• Full-duplex operations (or when it is in Repeater mode), the ICS1893 asserts its CRS signal only when it  
is receiving data.  
7.5.8 10Base-T Operation: Collision Detection  
The ICS1893 has a 10Base-T Collision Detection Function that establishes the state of its Collision  
Detection signal (COL) based upon both (1) the state of its Receiver state machine and (2) the state of its  
Transmit state machine. When the ICS1893 is operating in:  
• Half-duplex mode, the ICS1893 asserts its COL signal to indicate it is receiving data while transmission  
of data is also in progress.  
• Full-duplex mode, the ICS1893 always sets its COL signal to FALSE.  
7.5.9 10Base-T Operation: Jabber  
The ICS1893 has an ISO/IEC compliant Jabber Detection Function that, when enabled, monitors the data  
stream sent to its Twisted-Pair Transmitter to ensure that it does not exceed the 10Base-T Jabber  
activation time limit (that is, the maximum transmission time). For more information, see Section 10.5.20,  
“10Base-T: Jabber Timing”.  
When the Jabber Detection Function detects that its transmission time exceeds the maximum Jabber  
activation time limit and Jabber Detection is enabled, the ICS1893 asserts its Collision Detect (COL) signal.  
During this ISO/IEC specified ‘jabber de-activation time’, the ICS1893 transmit data stream is interrupted  
and prevented from reaching its Twisted-Pair Transmitter. During this time, when interrupting the data  
stream and asserting its COL signal, the ICS1893 transmits Normal Link Pulses and sets its QuickPoll  
Detailed Status Register’s Jabber Detected bit (bit 17.2) to logic one. This bit is a latching high (LH) bit. (For  
more information on latching high and latching low bits, see Section 8.1.4.1, “Latching High Bits” and  
Section 8.1.4.2, “Latching Low Bits”.)  
The ICS1893 provides an STA with the ability to disable the Jabber Detection Function using the Jabber  
Inhibit bit (bit 18.5 in the 10Base-T Operations Register). Setting bit 18.5 to logic:  
• Zero (the default) enables the Jabber Detection Function.  
• One disables the Jabber Detection Function.  
7.5.10 10Base-T Operation: SQE Test  
The ICS1893 has an ISO/IEC compliant Signal Quality Error (SQE) Test Function used exclusively for  
10Base-T operations. When enabled, the ICS1893 performs the SQE Test at the completion of each  
transmitted packet (that is, whenever its TX_EN signal transitions from asserted to de-asserted). When the  
ICS1893 executes its SQE Test, it asserts the COL signal to its MAC Interface for a pre-determined time  
duration (ISO/IEC specified). [For more information, see Section 10.5.19, “10Base-T: Heartbeat Timing  
(SQE)”.]  
An ICS1893 SQE Test Function is:  
• Enabled only when all the following conditions are true:  
– The ICS1893 is in node mode.  
– The ICS1893 is in half-duplex mode.  
– The ICS1893 has a valid link.  
– The 10Base-T Operations Register’s SQE Test Inhibit bit (bit 18.2) is logic zero (the default).  
– The ICS1893 TX_EN signal has transitioned from asserted (high) to de-asserted (low).  
• Disabled whenever any of the following are true:  
– The ICS1893 is in Repeater mode.  
– The ICS1893 is in full-duplex mode.  
– The ICS1893 detects a link failure.  
– The ICS1893 SQE Test Inhibit bit (bit 18.2) in the 10Base-T Operations Register is logic one. [This  
bit provides the Station Management entity (STA) with the ability to disable the SQE Test function.]  
Note:  
1. In 10Base-T mode, a bit time has a typical duration of 100 ns.  
2. The SQE Test also has the name 10Base-T Heartbeat. For details on the SQE waveforms, see Section  
10.5.19, “10Base-T: Heartbeat Timing (SQE)”.  
7.5.11 10Base-T Operation: Twisted-Pair Transmitter  
The 10Base-T Twisted-Pair Transmitter is functionally similar to the 100Base-TX Twisted-Pair Transmitter.  
The primary differences are in the data rate and signaling, as specified in the ISO/IEC specifications. For  
more information, see Section 7.4.5, “100Base-TX Operation: Twisted-Pair Transmitter”.  
7.5.12 10Base-T Operation: Twisted-Pair Receiver  
The 10Base-T Twisted-Pair Receiver is functionally similar the 100Base-TX Twisted-Pair Receiver. The  
primary differences are in the data rate and signaling, as specified in the ISO/IEC specifications. For more  
information, see Section 7.4.6, “100Base-TX Operation: Twisted-Pair Receiver”.  
7.5.13 10Base-T Operation: Auto Polarity Correction  
The ICS1893 can sense and then automatically correct a signal polarity that is reversed on its Twisted-Pair  
Receiver inputs. A signal polarity reversal occurs when the input signals on an ICS1893’s TP_RXP and  
TP_RXN pins are crossed or swapped (a problem that can occur during network installation or wiring).  
The ICS1893 accomplishes reversed signal polarity detection and correction by examining the signal  
polarity of the Normal Link Pulses (NLPs). In 10Base-T mode, an ICS1893 transmits and receives NLPs  
when its link is in the Idle state. In 100Base-TX mode, an ICS1893 transmits and receives NLPs during  
Auto-Negotiation. An STA can control this feature using the 10Base-T Operations Register bit 18.3, the  
Auto Polarity-Inhibit bit. When this bit is logic:  
• Zero, the ICS1893 automatically senses and corrects a reversed or inverted signal polarity on its  
Twisted-Pair Receive pins (TP_RXP and TP_RXN).  
• One, the ICS1893 disables this feature.  
When an ICS1893 detects a reversed signal polarity on its Twisted-Pair Receiver pins and the Auto  
Polarity-Inhibit bit is also logic zero (enabled), the ICS1893 (1) automatically corrects the data stream and  
(2) sets its Polarity Reversed bit (bit 18.14) to logic one, to indicate to the STA that this situation exists. Bit  
18.14 is a latching high (LH) bit. (For more information on latching high and latching low bits, see Section  
8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
Note: The Auto Polarity Correction Function is primarily a 10Base-T operation. However, it is part of the  
Twisted-Pair Receiver and is operational during the 100Base-TX auto-negotiation process.  
7.5.14 10Base-T Operation: Isolation Transformer  
The 10Base-T Isolation Transformer operates the same as the 100Base-TX Isolation Transformer. In fact,  
in a typical ICS1893 application they are the same unit. For more information, see Section 7.4.8,  
“100Base-TX Operation: Isolation Transformer”.  
7.6 Functional Block: Management Interface  
As part of the MAC/Repeater Interface, the ICS1893 provides a two-wire serial management interface  
which complies with the ISO/IEC 8802-3 standard MII Serial Management Interface. This interface is used  
to exchange control, status, and configuration information between a Station Management entity (STA) and  
the physical layer device (PHY). The PHY and STA exchange this data through a pre-defined set of  
management registers. The ISO/IEC standard specifies the following components of this serial  
management interface:  
• A set of registers (Section 7.6.1, “Management Register Set Summary”)  
• The frame structure (Section 7.6.2, “Management Frame Structure”)  
• The protocol  
In compliance with the ISO/IEC specification, the ICS1893 implementation of the serial management  
interface provides a bi-directional data pin (MDIO) along with a clock (MDC) for synchronizing the  
exchange of data. These pins remain active in all ICS1893 MAC/Repeater Interface modes (that is, the  
10/100 MII, 100M Symbol, and 10M Serial interface modes).  
7.6.1 Management Register Set Summary  
The ICS1893 implements a Management Register set that adheres to the ISO/IEC standard. This register  
set (discussed in detail in Chapter 8, “Management Register Set”) includes the mandatory ‘Basic’ Control  
and Status registers and the ISO/IEC ‘Extended’ registers as well as some ICS-specific registers.  
7.6.2 Management Frame Structure  
The Serial Management Interface is a synchronous, bi-directional, two-wire, serial interface for the  
exchange of configuration, control, and status data between a PHY, such as an ICS1893, and an STA. All  
data transferred on an MDIO signal is synchronized by its MDC signal. The PHY and STA exchange data  
through a pre-defined register set.  
The ICS1893 complies with the ISO/IEC defined Management Frame Structure and protocol. This structure  
supports both read and write operations. Table 7-2 summarizes the Management Frame Structure.  
Note: The Management Frame Structure starts from and returns to an IDLE condition. However, the  
IDLE periods are not part of the Management Frame Structure.  
Table 7-2. Management Frame Structure Summary  
Frame Field  
Frame Function  
Data  
Comment  
Acronym  
PRE  
Preamble (Bit 1.6)  
Start of Frame  
Operation Code  
PHY Address (Bits 16.10:6)  
Register Address  
Turnaround  
11..11  
01  
32 ones  
2 bits  
SFD  
OP  
10/01 (read/write) 2 bits  
PHYAD  
REGAD  
TA  
AAAAA  
RRRRR  
5 bits  
5 bits  
Z0/10 (read/write) 2 bits  
DDD..DD 16 bits  
DATA  
Data  
7.6.2.1 Management Frame Preamble  
The ICS1893 continually monitors its serial management interface for either valid data or a Management  
Frame (MF) Preamble, based upon the setting of the MF Preamble Suppression bit, 1.6. When the MF  
Preamble Suppression is disabled, an ICS1893 waits for a MF Preamble which indicates the start of an  
STA transaction. A Management Frame Preamble is a pattern of 32 contiguous logic one bits on the MDIO  
pin, along with 32 corresponding clock cycles on the MDC pin.  
The ICS1893 supports the Management Frame (MF) Preamble Suppression capability on its Management  
Interface, thereby providing a method to shorten the Management Frame and provide an STA with faster  
access to the Management Registers.  
The ability to process Management Frames that do not have a preamble is provided by the Management  
Frame Preamble Suppression bit, (bit 1.6 in the ICS1893’s Status Register). This is an ISO/IEC defined  
status bit that is intended to provide an indication of whether or not a PHY supports the MF Preamble  
Suppression feature. In order to maintain backward compatibility with the ICS1890, which did not support  
MF Preamble Suppression, the ICS1893 MF Preamble Suppression bit is a Command Override Write bit  
which defaults to a logic zero. An STA can enable MF Preamble Suppression by writing a logic one to bit  
1.6 subsequent to a write of logic one to the Command Override bit, 16.15. For an explanation of the  
Command Override Write bits, see Section 8.1.2, “Management Register Bit Access”.  
7.6.2.2 Management Frame Start  
A valid Management Frame includes a start-of-frame delimiter, SFD, immediately following the preamble.  
The SFD bit pattern is 01b and is synchronous with two clock cycles on the MDC pin.  
7.6.2.3 Management Frame Operation Code  
A valid Management Frame includes an operation code (OP) immediately following the start-of-frame  
delimiter. There are two valid operation codes: one for reading from a management register, 10b, and one  
for writing to a management register, 01b. The ICS1893 does not respond to the codes 00b and 11b, which  
the ISO/IEC specification defines as invalid.  
7.6.2.4 Management Frame PHY Address  
The two-wire, Serial Management Interface is specified to allow busing (that is, the sharing of the two wires  
among multiple PHYs). The Management Frame includes a 5-bit PHY Address field, PHYAD, allowing for  
32 unique addresses. An STA uniquely identifies each of the PHYs that share a single serial management  
interface by using this 5-bit PHY Address field, PHYAD.  
Upon receiving a valid STA transaction, during a power-on or hardware reset an ICS1893 compares the  
PHYAD field included within the management frame with the value of its PHYAD bits stored in register 16.  
(For information on the PHYAD bits, see Table 8-16.) An ICS1893 responds to all transactions that match  
its stored address bits.  
7.6.2.5 Management Frame Register Address  
A Management Frame includes a 5-bit register address field, REGAD. This field identifies which of the 32  
Management Registers are involved in a transaction between an STA and a PHY.  
7.6.2.6 Management Frame Operational Code  
A management frame includes a 2-bit operational code field, OP. If the operation code is a:  
• Read, the REGAD field identifies the register used as the source of data returned to the STA by the  
ICS1893.  
• Write, the REGAD identifies the destination register that is to receive the data sent by the STA to the  
ICS1893.  
7.6.2.7 Management Frame Turnaround  
A valid management frame includes a turn-around field (TA), which is a 2-bit time space between the  
REGAD field and the Data field. This time allows an ICS1893 and an STA to avoid contentions during read  
transactions. During an operation that is a:  
• Read, an ICS1893 remains in the high-impedance state during the first bit time and subsequently drives  
its MDIO pin to logic zero for the second bit time.  
• Write, an ICS1893 waits while the STA transmits a logic one, followed by a logic zero on its MDIO pin.  
7.6.2.8 Management Frame Data  
A valid management frame includes a 16-bit Data field for exchanging the register contents between the  
ICS1893 and the STA. All Management Registers are 16 bits wide, matching the width of the Data field.  
During a transaction that is a:  
• Read, (OP is 10b) the ICS1893 obtains the contents of the register identified in the REGAD field and  
returns this Data to the STA synchronously with its MDC signal.  
• Write, (OP is 01b) the ICS1893 stores the value of the Data field in the register identified in the REGAD  
field.  
If the STA attempts to:  
• Read from a non-existent ICS1893 register, the ICS1893 returns logic one for all bits in the Data field,  
FFFFh.  
• Write to a non-existent ICS1893 register, the ICS1893 isolates the Data field of the management frame  
from every reaching the registers.  
Note: The first Data bit transmitted and received is the most-significant bit of a Management Register, bit  
X.15.  
7.6.2.9 Serial Management Interface Idle State  
The MDIO signal is in an idle state during the time between STA transactions. When the Serial  
Management Interface is in the idle state, the ICS1893 disables (that is, tri-states) its MDIO pin, which  
enters a high-impedance state. The ISO/IEC 8802-3 standard requires that an MDIO signal be idle for at  
least one bit time between management transactions. However, the ICS1893 does not have this limitation  
and can support a continual bit stream on its MDIO signals.  
Chapter 8 Management Register Set  
The tables in this chapter detail the functionality of the bits in the management register set. The tables  
include the register locations, the bit positions, the bit definitions, the STA Read/Write Access Types, the  
default bit values, and any special bit functions or capabilities (such as self-clearing). Following each table  
is a description of each bit. This chapter includes the following sections:  
• Section 8.1, “Introduction to Management Register Set”  
• Section 8.2, “Register 0: Control Register”  
• Section 8.3, “Register 1: Status Register”  
• Section 8.4, “Register 2: PHY Identifier Register”  
• Section 8.5, “Register 3: PHY Identifier Register”  
• Section 8.6, “Register 4: Auto-Negotiation Register”  
• Section 8.7, “Register 5: Auto-Negotiation Link Partner Ability Register”  
• Section 8.8, “Register 6: Auto-Negotiation Expansion Register”  
• Section 8.9, “Register 7: Auto-Negotiation Next Page Transmit Register”  
• Section 8.10, “Register 8: Auto-Negotiation Next Page Link Partner Ability Register”  
• Section 8.11, “Register 16: Extended Control Register”  
• Section 8.12, “Register 17: Quick Poll Detailed Status Register”  
• Section 8.13, “Register 18: 10Base-T Operations Register”  
• Section 8.14, “Register 19: Extended Control Register 2”  
8.1 Introduction to Management Register Set  
This section explains in general terms the Management Register set discussed in this chapter. (For a  
summary of the Management Register set, see Section 7.6.1, “Management Register Set Summary”.)  
8.1.1 Management Register Set Outline  
This section outlines the ICS1893 Management Register set. Table 8-1 lists the ISO/IEC-specified  
Management Register Set that the ICS1893 implements.  
Table 8-1. ISO/IEC-Specified Management Register Set  
Register Address  
Register Name  
Basic / Extended  
Basic  
0
Control  
1
Status  
Basic  
2,3  
PHY Identifier  
Extended  
Extended  
Extended  
Extended  
Extended  
Extended  
Extended  
Extended  
4
Auto-Negotiation Advertisement  
Auto-Negotiation Link Partner Ability  
Auto-Negotiation Expansion  
5
6
7
Auto-Negotiation Next Page Transmit  
Auto-Negotiation Next Page Link Partner Ability  
Reserved by IEEE  
8
9 through 15  
16 through 31  
Vendor-Specific (ICS) Registers  
Table 8-2 lists the ICS-specific registers that the ICS1893 implements. These registers enhance the  
performance of the ICS1893 and provide the Station Management entity (STA) with additional control and  
status capabilities.  
Table 8-2. ICS-Specific Registers  
Register Address  
16  
Register Name  
Extended Control  
Basic / Extended  
Extended  
17  
QuickPoll Detailed Status  
10Base-T Operations  
Extended  
18  
Extended  
19  
Auto-Negotiation Advertisement  
Reserved by ICS  
Extended  
20 through 31  
Extended  
8.1.2 Management Register Bit Access  
The ICS1893 Management Registers include one or more of the following types of bits:  
Table 8-3. Description of Management Register Bit Types  
Management  
Bit  
Description  
Register Bit Types Symbol  
Read-Only  
RO  
An STA can obtain the value of a RO register bit. However, it cannot  
alter the value of (that is, it cannot write to) an RO register bit. The  
ICS1893 isolates any STA attempt to write a value to an RO bit.  
Command Override  
Write  
CW  
An STA can read a value from a CW register bit. However, write  
operations are conditional, based on the value of the Command  
Register Override bit (bit 16.15). When bit 16.15 is logic:  
• Zero (the default), the ICS1893 isolates STA attempts to write to  
the CW bits (that is, CW bits cannot be altered when bit 16.15 is  
logic zero).  
• One, the ICS1893 permits an STA to alter the value of the CW bits  
in the subsequent register write. (Bit 16.15 is self-clearing and  
automatically clears to zero on the subsequent write.)  
Read/Write  
R/W  
An STA can unconditionally read from or write to a R/W register bit.  
Read/Write Zero  
R/W0  
An STA can unconditionally read from a R/W0 register bit, but only a  
‘0’ value can be written to this bit.  
8.1.3 Management Register Bit Default Values  
The tables in this chapter specify for each register bit the default value, if one exists. The ICS1893 sets all  
Management Register bits to their default values after a reset. Table 8-4 lists the valid default values for  
ICS1893 Management Register bits.  
Table 8-4. Range of Possible Valid Default Values for ICS1893 Register Bits  
Default Condition  
Default Value  
Indicates there is no default value for the bit  
–
0
1
Indicates the bit’s default value is logic zero  
Indicates the bit’s default value is logic one  
State of pin at reset For some bits, the default value depends on the state (that is, the logic value) of a  
particular pin at reset (that is, the logic value of a pin is latched at reset). An  
example of pins that have a default condition that depends on the state of the pin  
at reset are the PHY / LED pins (P0AC, P1CL, P2LI, P3TD, and P4RD) discussed  
in the following sections:  
• Section 6.8, “Status Interface”  
• Section 8.11, “Register 16: Extended Control Register”  
• Section 9.3.2, “Multi-Function (Multiplexed) Pins: PHY Address and LED Pins”  
Note: The ICS1893 has a number of reserved bits throughout the Management Registers. Most of these  
bits provide enhanced test modes. The Management Register tables provide the default values for  
these bits. The STA must not change the value of these bits under any circumstance. If the STA  
inadvertently changes the default values of these reserved register bits, normal operation of the  
ICS1893 can be affected.  
8.1.4 Management Register Bit Special Functions  
This section discusses the types of special functions for the Management Register bits.  
8.1.4.1 Latching High Bits  
The purpose of a latching high (LH) bit is to record an event. An LH bit records an event by monitoring an  
active-high signal and then latching this active-high signal when it triggers (that is, when the event occurs).  
A latching high bit, once set to logic one, remains set until either a reset occurs or it is read by an STA.  
Immediately following an STA read of an LH bit, the ICS1893 latches the current state of the signal into the  
LH bit. When an STA reads an LH bit:  
• Once, the LL bit provides the STA with a history of whether or not the event has ever occurred. That is,  
this first read provides the STA with a history of the condition and latches the current state of the signal  
into the LL bit for the next read.  
• Twice in succession, the LH bit provides the STA with the current state of the monitored signal.  
8.1.4.2 Latching Low Bits  
As with latching high bits, the purpose of a latching low (LL) bit is also to record an event. An LL bit records  
an event by monitoring an active-low signal and then latching this active-low signal when it triggers (that is,  
when the event occurs).  
A latching low bit, once cleared to logic zero, remains cleared until either a reset occurs or it is read by an  
STA. Immediately following an STA read of an LL bit, the ICS1893 latches the current state of the  
active-low signal into the LL bit. When an STA reads an LL bit:  
• Once, the LL bit provides the STA with a history of whether or not the event has ever occurred. That is,  
this first read provides the STA with a history of the condition and latches the current state of the signal  
into the LL bit for the next read.  
• Twice in succession, the LL bit provides the STA with the current state of the monitored signal.  
8.1.4.3 Latching Maximum Bits  
For the ICS1893, the purpose of latching maximum (LMX) bits is to track the progress of internal state  
machines. The LMX bits act in combination with other LMX bits to save the maximum collective value of a  
defined group of LMX bits, from the most-significant bit to the least-significant bit.  
For example, assume a group of LMX bits is defined as register bits 13 through 11. If these bits first have a  
value of 3o (octal) and then the state machine they are monitoring advances to state:  
• 2o, then the 2o value does not get latched.  
• 4o (or any other value greater than 3o), then in this case, the value of 4o does get latched.  
LMX bits retain their value until either a reset occurs or they are read by an STA. Immediately following an  
STA read of a defined group of LMX bits, the ICS1893 latches the current state of the monitored state  
machine into the LMX bits. When an STA reads a group of LMX bits:  
• Once, the LMX bits provide the STA with a history of the maximum value that the state machine has  
achieved and latches the current state of the state machine into the LMX bits for the next read.  
• Twice in succession, the LMX bits provide the STA with the current state of the monitored state machine.  
8.1.4.4 Self-Clearing Bits  
Self-clearing (SC) bits automatically clear themselves to logic zero after a pre-determined amount of time  
without any further STA access. The SC bits have a default value of logic zero and are triggers to begin  
execution of a function. When the STA writes a logic one to an SC bit, the ICS1893 begins executing the  
function assigned to that bit. After the ICS1893 completes executing the function, it clears the bit to indicate  
that the action is complete.  
8.2 Register 0: Control Register  
Table 8-5 lists the bits for the Control Register, a 16-bit register used to establish the basic operating  
modes of the ICS1893.  
• The Control Register is accessible through the MII Management Interface.  
• Its operation is independent of the MAC/Repeater Interface configuration.  
• It is fully compliant with the ISO/IEC Control Register definition.  
Note: For an explanation of acronyms used in Table 8-5, see Chapter 1, “Abbreviations and Acronyms”.  
Table 8-5. Control Register (Register 0 [0x00]  
Bit  
Definition  
When Bit = 0  
When Bit = 1  
Ac-  
SF  
De-  
Hex  
cess  
fault  
0.15 Reset  
No effect  
ICS1893 enters Reset  
mode  
R/W  
SC  
0
3
0.14 Loopback enable  
0.13 Data rate select  
Disable Loopback mode Enable Loopback mode  
10 Mbps operation 100 Mbps operation  
R/W  
R/W  
R/W  
R/W  
R/W  
R/W  
R/W  
R/W  
RO  
–
–
0
1
0.12 Auto-Negotiation enable DisableAuto-Negotiation Enable Auto-Negotiation  
–
1
0.11 Low-power mode  
0.10 Isolate  
Normal power mode  
No effect  
Low-power mode  
–
0
0/4†  
Isolate ICS1893 from MII  
–
0/1†  
0
0.9  
0.8  
0.7  
0.6  
0.5  
0.4  
0.3  
0.2  
0.1  
0.0  
Auto-Negotiation restart No effect  
Restart Auto-Negotiation  
SC  
–
Duplex mode  
Collision test  
Half-duplex operation  
No effect  
Full-duplex operation  
0
Enable collision test  
–
0
0
IEEE reserved  
IEEE reserved  
IEEE reserved  
IEEE reserved  
IEEE reserved  
IEEE reserved  
IEEE reserved  
Always 0  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
–
0‡  
0‡  
0‡  
0‡  
0‡  
0‡  
0‡  
Always 0  
RO  
–
Always 0  
RO  
–
Always 0  
RO  
–
0
Always 0  
RO  
–
Always 0  
RO  
–
Always 0  
RO  
–
† Whenever the PHY address of Table 8-16:  
• Is equal to 00000 (binary), the Isolate bit 0.10 is logic one.  
• Is not equal to 00000, the Isolate bit 0.10 is logic zero.  
‡ As per the IEEE Std 802.3u, during any write operation to any bit in this register, the STA must write the default value  
to all Reserved bits.  
8.2.1 Reset (bit 0.15)  
This bit controls the software reset function. Setting this bit to logic one initiates an ICS1893 software reset  
during which all Management Registers are set to their default values and all internal state machines are  
set to their idle state. For a detailed description of the software reset process, see Section 5.1.2.3,  
“Software Reset”.  
During reset, the ICS1893 leaves bit 0.15 set to logic one and isolates all STA management register  
accesses. However, the reset process is not complete until bit 0.15 (a Self-Clearing bit), is set to logic zero,  
which indicates the reset process is terminated.  
8.2.2 Loopback Enable (bit 0.14)  
This bit controls the Loopback mode for the ICS1893. Setting this bit to logic:  
• Zero disables the Loopback mode.  
• One enables the Loopback mode by disabling the Twisted-Pair Transmitter, the Twisted-Pair Receiver,  
and the collision detection circuitry. (The STA can override the ICS1893 from disabling the collision  
detection circuitry in Loopback mode by writing logic one to bit 0.7.) When the ICS1893 is in Loopback  
mode, the data presented at the MAC/repeater transmit interface is internally looped back to the  
MAC/repeater receive interface. The delay from the assertion of Transmit Data Enable (TXEN) to the  
assertion of Receive Data valid (RXDV) is less than 512 bit times.  
8.2.3 Data Rate Select (bit 0.13)  
This bit provides a means of controlling the ICS1893 data rate. Its operation depends on the state of  
several other functions, including the HW/SW input pin and the Auto-Negotiation Enable bit (bit 0.12).  
When the ICS1893 is configured for:  
• Hardware mode (that is, the HW/SW pin is logic zero), the ICS1893 isolates this bit 0.13 and uses the  
10/100SEL input pin to establish the data rate for the ICS1893. In this Hardware mode:  
– Bit 0.13 is undefined.  
– The ICS1893 provides a Data Rate Status bit (in the QuickPoll Detailed Status Register, bit 17.15),  
which always shows the setting of an active link.  
• Software mode (that is, the HW/SW pin is logic one), the function of bit 0.13 depends on the  
Auto-Negotiation Enable bit 0.12. When the Auto-Negotiation sublayer is:  
– Enabled, the ICS1893 isolates bit 0.13 and relies on the results of the auto-negotiation process to  
establish the data rate.  
– Disabled, bit 0.13 determines the data rate. In this case, setting bit 0.13 to logic:  
• Zero selects 10-Mbps ICS1893 operations.  
• One selects 100-Mbps ICS1893 operations.  
8.2.4 Auto-Negotiation Enable (bit 0.12)  
This bit provides a means of controlling the ICS1893 Auto-Negotiation sublayer. Its operation depends on  
the HW/SW input pin.  
When the ICS1893 is configured for:  
• Hardware mode, (that is, the HW/SW pin is logic zero), the ICS1893 isolates bit 0.12 and uses the  
ANSEL (Auto-Negotiation Select) input pin to determine whether to enable the Auto-Negotiation  
sublayer.  
Note: In Hardware mode, bit 0.12 is undefined.  
• Software mode, (that is, the HW/SW pin is logic one), bit 0.12 determines whether to enable the  
Auto-Negotiation sublayer. When bit 0.12 is logic:  
– Zero:  
• The ICS1893 disables the Auto-Negotiation sublayer.  
• The ICS1893 bit 0.13 (the Data Rate bit) and bit 0.8 (the Duplex Mode bit) determine the data rate  
and the duplex mode.  
– One:  
• The ICS1893 enables the Auto-Negotiation sublayer.  
• The ICS1893 isolates bit 0.13 and bit 0.8.  
8.2.5 Low Power Mode (bit 0.11)  
This bit provides one way to control the ICS1893 low-power mode function. When bit 0.11 is logic:  
• Zero, there is no impact to ICS1893 operations.  
• One, the ICS1893 enters the low-power mode. In this case, the ICS1893 disables all internal functions  
and drives all MAC/repeater output pins low except for those that support the MII Serial Management  
Port. In addition, the ICS1893 internally activates the TPTRI function to tri-state the signals on the  
Twisted-Pair Transmit pins (TP_TXP and TP_TXN) and achieve additional power savings.  
Note: There are two ways the ICS1893 can enter low-power mode. When entering low-power mode:  
• By setting bit 0.11 to logic one, the ICS1893 maintains the value of all Management Register bits  
except the latching high (LH) and latching low (LL) status bits, which are re-initialized to their  
default values instead. (For more information on latching high and latching low bits, see Section  
8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
• During a reset, the ICS1893 sets all management register bits to their default values.  
8.2.6 Isolate (bit 0.10)  
This bit controls the ICS1893 Isolate function. When bit 0.10 is logic:  
• Zero, there is no impact to ICS1893 operations.  
• One, the ICS1893 electrically isolates its data paths from the MAC/Repeater Interface. The ICS1893  
places all MAC/repeater output signals (TXCLK, RXCLK, RXDV, RXER, RXD[3:0], COL, and CRS) in a  
high-impedance state and it isolates all MAC/repeater input signals (TXD[3:0], TXEN, and TXER). In this  
mode, the Serial Management Interface continues to operate normally (that is, bit 0.10 does not affect  
the Management Interface).  
The default value for bit 0.10 depends upon the PHY address of Table 8-16. If the PHY address:  
• Is equal to 00000b, then the default value of bit 0.10 is logic one, and the ICS1893 isolates itself from the  
MAC/Repeater Interface.  
• Is not equal to 00000b, then the default value of bit 0.10 is logic zero, and the ICS1893 does not isolate  
its MAC/Repeater Interface.  
8.2.7 Restart Auto-Negotiation (bit 0.9)  
This bit allows an STA to restart the auto-negotiation process in Software mode (that is, the HW/SW pin is  
logic one). When bit 0.12 is logic:  
• Zero, the Auto-Negotiation sublayer is disabled, and the ICS1893 isolates any attempt by the STA to set  
bit 0.9 to logic one.  
• One (as set by an STA), the ICS1893 restarts the auto-negotiation process. Once the auto-negotiation  
process begins, the ICS1893 automatically sets this bit to logic zero, thereby providing the self-clearing  
feature.  
8.2.8 Duplex Mode (bit 0.8)  
This bit provides a means of controlling the ICS1893 Duplex Mode. Its operation depends on several other  
functions, including the HW/SW input pin and the Auto-Negotiation Enable bit (bit 0.12). When the ICS1893  
is configured for:  
• Hardware mode (that is, the HW/SW pin is logic zero), the ICS1893 isolates bit 0.8 and uses the  
DPXSEL input pin to establish the Duplex mode for the ICS1893. In this Hardware mode:  
– Bit 0.8 is undefined.  
– The ICS1893 provides a Duplex Mode Status bit (in the QuickPoll Detailed Status Register, bit  
17.14), which always shows the setting of an active link.  
• Software mode (that is, the HW/SW pin is logic one), the function of bit 0.8 depends on the  
Auto-Negotiation Enable bit, 0.12. When the auto-negotiation process is:  
– Enabled, the ICS1893 isolates bit 0.8 and relies upon the results of the auto-negotiation process to  
establish the duplex mode.  
– Disabled, bit 0.8 determines the Duplex mode. Setting bit 0.8 to logic:  
• Zero selects half-duplex operations.  
• One selects full-duplex operations. (When the ICS1893 is operating in Loopback mode, it isolates  
bit 0.8, which has no effect on the operation of the ICS1893.)  
8.2.9 Collision Test (bit 0.7)  
This bit controls the ICS1893 Collision Test function. When an STA sets bit 0.7 to logic:  
• Zero, the ICS1893 disables the collision detection circuitry for the Collision Test function. In this case, the  
COL signal does not track the TXEN signal. (The default value for this bit is logic zero, that is, disabled.)  
• One, as per the ISO/IEE 8802-3 standard, clause 22.2.4.1.9, the ICS1893 enables the collision detection  
circuitry for the Collision Test function, even if the ICS1893 is in Loopback mode (that is, bit 0.14 is set to  
1). In this case, the Collision Test function tracks the Collision Detect signal (COL) in response to the  
TXEN signal. The ICS1893 asserts the Collision signal (COL) within 512 bit times of receiving an  
asserted TXEN signal, and it de-asserts COL within 4 bit times of the de-assertion of the TXEN signal.  
8.2.10 IEEE Reserved Bits (bits 0.6:0)  
The IEEE reserves these bits for future use. When an STA:  
• Reads a reserved bit, the ICS1893 returns a logic zero.  
• Writes to a reserved bit, it must use the default value specified in this data sheet.  
The ICS1893 uses some reserved bits to invoke auxiliary functions. To ensure proper operation of the  
ICS1893, an STA must maintain the default value of these bits. Therefore, ICS recommends that during  
any STA write operation, an STA write the default value to all reserved bits, even those bits that are Read  
Only.  
8.3 Register 1: Status Register  
Table 8-6 lists the Status Register bits. These 16 bits of data provide an interface between the ICS1893  
and an STA. There are two types of status bits: some report the capabilities of the port, and some indicate  
the state of signals used to monitor internal circuits.  
The STA accesses the Status Register using the Serial Management Interface. During a reset, the  
ICS1893 initializes the Status Register bits to pre-defined, default values.  
Note: For an explanation of acronyms used in Table 8-5, see Chapter 1, “Abbreviations and Acronyms”.  
Table 8-6. Status Register (Register 1 [0x01])  
Bit  
Definition  
When Bit = 0  
When Bit = 1  
Ac-  
SF  
De-  
Hex  
cess  
fault  
1.15 100Base-T4  
Always 0. (Not supported.) N/A  
RO  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
RO  
–
–
–
–
–
–
–
–
–
–
0
1
7
1.14 100Base-TX full duplex Mode not supported  
1.13 100Base-TX half duplex Mode not supported  
Mode supported  
Mode supported  
Mode supported  
Mode supported  
N/A  
1
1.12 10Base-T full duplex  
1.11 10Base-T half duplex  
1.10 IEEE reserved  
1.9 IEEE reserved  
Mode not supported  
Mode not supported  
Always 0  
1
1
8
0
0†  
0†  
0†  
0†  
0
Always 0  
N/A  
1.8 IEEE reserved  
Always 0  
N/A  
1.7 IEEE reserved  
Always 0  
N/A  
1.6 MF Preamble  
suppression  
PHY requires MF  
Preambles  
PHY does not require  
MF Preambles  
1.5 Auto-Negotiation  
complete  
Auto-Negotiation is in  
process, if enabled  
Auto-Negotiation is  
completed  
RO  
LH  
0
1.4 Remote fault  
No remote fault detected  
Remote fault detected  
RO  
RO  
LH  
–
0
1
1.3 Auto-Negotiation ability N/A  
Always 1: PHY has  
9
Auto-Negotiation ability  
1.2 Link status  
Link is invalid/down  
Link is valid/established  
RO  
RO  
LL  
0
0
1.1 Jabber detect  
No jabber condition  
Jabber condition  
detected  
LH  
1.0 Extended capability  
N/A  
Always 1: PHY has  
extended capabilities  
RO  
–
1
† As per the IEEE Std 802.3u, during any write operation to any bit in this register, the STA must write the default value  
to all Reserved bits.  
8.3.1 100Base-T4 (bit 1.15)  
The STA reads this bit to learn if the ICS1893 can support 100Base-T4 operations. Bit 1.15 of the ICS1893  
is permanently set to logic zero, which informs an STA that the ICS1893 cannot support 100Base-T4  
operations.  
8.3.2 100Base-TX Full Duplex (bit 1.14)  
The STA reads this bit to learn if the ICS1893 can support 100Base-TX, full-duplex operations. The  
ISO/IEC specification requires that the ICS1893 must set bit 1.14 to logic:  
• Zero if it cannot support 100Base-TX, full-duplex operations.  
• One if it can support 100Base-TX, full-duplex operations. (For the ICS1893, the default value of bit 1.14  
is logic one, in that the ICS1893 supports 100Base-TX, full-duplex operations.)  
Bit 1.14 is a Command Override Write bit, which allows an STA to alter the default value of this bit. [See the  
description of bit 16.15, the Command Override Write Enable bit, in Section 8.11, “Register 16: Extended  
Control Register”.]  
8.3.3 100Base-TX Half Duplex (bit 1.13)  
The STA reads this bit to learn if the ICS1893 can support 100Base-TX, half-duplex operations. The  
ISO/IEC specification requires that the ICS1893 must set bit 1.13 to logic:  
• Zero if it cannot support 100Base-TX, half-duplex operations.  
• One if it can support 100Base-TX, half-duplex operations. (For the ICS1893, the default value of bit 1.13  
is logic one. Therefore, when an STA reads the Status Register, the STA is informed that the ICS1893  
supports 100Base-TX, half-duplex operations.)  
This bit 1.13 is a Command Override Write bit, which allows an STA to alter the default value of this bit.  
[See the description of bit 16.15, the Command Override Write Enable bit, in Section 8.11, “Register 16:  
Extended Control Register”.]  
8.3.4 10Base-T Full Duplex (bit 1.12)  
The STA reads this bit to learn if the ICS1893 can support 10Base-T, full-duplex operations. The ISO/IEC  
specification requires that the ICS1893 must set bit 1.12 to logic:  
• Zero if it cannot support 10Base-T, full-duplex operations.  
• One if it can support 10Base-T, full-duplex operations. (For the ICS1893, the default value of bit 1.12 is  
logic one. Therefore, when an STA reads the Status Register, the STA is informed that the ICS1893  
supports 10Base-T, full-duplex operations.)  
This bit 1.12 is a Command Override Write bit, which allows an STA to alter the default value of this bit.  
[See the description of bit 16.15, the Command Override Write Enable bit, in Section 8.11, “Register 16:  
Extended Control Register”.]  
8.3.5 10Base-T Half Duplex (bit 1.11)  
The STA reads this bit to learn if the ICS1893 can support 10Base-T, half-duplex operations. The ISO/IEC  
specification requires that the ICS1893 must set bit 1.11 to logic:  
• Zero if it cannot support 10Base-T, half-duplex operations.  
• One if it can support 10Base-T, half-duplex operations. (For the ICS1893, the default value of bit 1.11 is  
logic one. Therefore, when an STA reads the Status Register, the STA is informed that the ICS1893  
supports 10Base-T, half-duplex operations.)  
Bit 1.11 of the ICS1893 Status Register is a Command Override Write bit., which allows an STA to alter the  
default value of this bit. [See the description of bit 16.15, the Command Override Write Enable bit, in  
Section 8.11, “Register 16: Extended Control Register”.]  
8.3.6 IEEE Reserved Bits (bits 1.10:7)  
The IEEE reserves these bits for future use. When an STA:  
• Reads a reserved bit, the ICS1893 returns a logic zero.  
• Writes a reserved bit, the STA must use the default value specified in this data sheet.  
Both the ISO/IEC standard and the ICS1893 reserve the use of some Management Register bits. ICS uses  
some reserved bits to invoke ICS1893 test functions. To ensure proper operation of the ICS1893, an STA  
must maintain the default value of these bits. Therefore, ICS recommends that an STA write the default  
value to all reserved bits during all Management Register write operations.  
Reserved bits 1.10:7 are Command Override Write (CW) bits. When bit 16.15, the Command Register  
Override bit, is logic:  
• Zero, the ICS1893 prevents all STA writes to CW bits.  
• One, an STA can modify the value of these bits.  
8.3.7 MF Preamble Suppression (bit 1.6)  
Status Register bit 1.6 is the Management Frame (MF) Preamble Suppression bit. The ICS1893 sets bit 1.6  
to inform the STA of its ability to receive frames that do not have a preamble. When this bit is logic:  
• Zero, the ICS1893 is indicating it cannot accept frames with a suppressed preamble.  
• One, the ICS1893 is indicating it can accept frames that do not have a preamble.  
Although the ICS1893 supports Management Frame Preamble Suppression, its default value for bit 1.6 is  
logic zero. This default value ensures that bit 1.6 is backward compatible with the ICS1890, which does not  
have this capability. As the means of enabling this feature, the ICS1893 implements bit 1.6 as a Command  
Override Write bit, instead of as a Read-Only bit as in the ICS1890. An STA uses the bit 1.6 to enable MF  
Preamble Suppression in the ICS1893. [See the description of bit 16.15, the Command Override Write  
Enable bit, in Section 8.11, “Register 16: Extended Control Register”.]  
8.3.8 Auto-Negotiation Complete (bit 1.5)  
An STA reads bit 1.5 to determine the state of the ICS1893 auto-negotiation process. The ICS1893 sets  
the value of this bit using two criteria. When its Auto-Negotiation sublayer is:  
• Disabled, the ICS1893 sets bit 1.5 to logic zero.  
• Enabled, the ICS1893 sets bit 1.5 to a value based on the state of the Auto-Negotiation State Machine.  
In this case, it sets bit 1.5 to logic one only upon completion of the auto-negotiation process. This setting  
indicates to the STA that a link is arbitrated and the contents of Management Registers 4, 5, and 6 are  
valid. For details on the auto-negotiation process, see Section 7.2, “Functional Block: Auto-Negotiation”.  
Bit 1.5 is a latching high (LH) bit. (For more information on latching high and latching low bits, see Section  
8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
Note: An Auto-Negotiation Restart does not clear an LH bit. However, performing two consecutive reads  
of this register provides the present state of the bit.  
8.3.9 Remote Fault (bit 1.4)  
An STA reads bit 1.4 to determine if a Remote Fault exists. The ICS1893 sets bit 1.4 based on the Remote  
Fault bit received from its remote link partner. The ICS1893 receives the Remote Fault bit as part of the  
Link Code Word exchanged during the auto-negotiation process. If the ICS1893 receives a Link Code  
Word from its remote link partner and the Remote Fault bit is set to:  
• Zero, then the ICS1893 sets bit 1.4 to logic zero.  
• One, then the ICS1893 sets bit 1.4 to logic one. In this case, the remote link partner is reporting the  
detection of a fault, which typically occurs when the remote link partner is having a problem with its  
receive channel.  
Bit 1.4 is a latching high status bit. (For more information on latching high and latching low bits, see Section  
8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
Note: The ICS1893 has two versions of the Remote Fault bit.  
• One version of the Remote Fault bit is a latching high version. An STA can access this version  
through either Management Register 1 (bit 1.4) or 17 (bit 17.1). This bit 1.4/17.1 is cleared when  
an STA reads either of these registers. (Bit 1.4 is identical to bit 17.1 in that they are the same  
internal bit.)  
• Another version of the Remote Fault bit is updated whenever the ICS1893 receives a new Link  
Control Word. An STA can access this version through Management Register 5 (bit 5.13), which  
like bits 1.4/17.1, also reports the status of the Remote Fault bit received from the remote link  
partner. However, bit 5.13 is not a latching high bit.  
The operation of both bit 1.4/17.1 and bit 5.13 are in compliance with the IEEE Std 802.3u.  
8.3.10 Auto-Negotiation Ability (bit 1.3)  
The STA reads bit 1.3 to determine if the ICS1893 can support the auto-negotiation process. If the  
ICS1893:  
• Cannot support the auto-negotiation process, it clears bit 1.3 to logic zero.  
• Can support the auto-negotiation process, it sets bit 1.3 to logic one. (For the ICS1893, the default value  
of bit 1.3 is logic one.)  
8.3.11 Link Status (bit 1.2)  
The purpose of this bit 1.2 (which is also accessible through the QuickPoll Detailed Status Register, bit  
17.0) is to determine if an established link is dropped, even momentarily. To indicate a link that is:  
• Valid, the ICS1893 sets bit 1.2 to logic one.  
• Invalid, the ICS1893 clears bit 1.2 to logic zero.  
This bit is a latching low (LL) bit that the Link Monitor function controls. (For more information on latching  
high and latching low bits, see Section 8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low  
Bits”.) The Link Monitor function continually observes the data received by either its 10Base-T or  
100Base-TX Twisted-Pair Receivers to determine the link status and stores the results in the Link Status  
bit.  
The criterion the Link Monitor uses to determine if a link is valid or invalid depends on the following:  
• Type of link  
• Present link state (valid or invalid)  
• Presence of any link errors  
• Auto-negotiation process  
For more information on the Link Monitor Function (relative to the Link Status bit), see Section 7.5.5,  
“10Base-T Operation: Link Monitor”.  
8.3.12 Jabber Detect (bit 1.1)  
The purpose of this bit is to allow an STA to determine if the ICS1893 detects a Jabber condition as defined  
in the ISO/IEC specification.The ICS1893 Jabber Detection function is controlled by the Jabber Inhibit bit in  
the 10Base-T Operations register (bit 18.5). To detect a Jabber condition, first the ICS1893 Jabber  
Detection function must be enabled. When bit 18.5 is logic:  
• Zero, the ICS1893 disables Jabber Detection and sets the Jabber Detect bit to logic zero.  
• One, the ICS1893 enables Jabber Detection and sets the Jabber Detect bit to logic one upon detection  
of a Jabber condition. When no Jabber condition is detected, the Jabber Detect bit is not altered.  
Note:  
1. The Jabber Detect bit is accessible through both the Status register (as bit 1.1) and the QuickPoll  
Detailed Status Register (as bit 17.2). A read of either register clears the Jabber Detect bit.  
2. The Jabber Detect bit is a latching high (LH) bit. (For more information on latching high and latching low  
bits, see Section 8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
8.3.13 Extended Capability (bit 1.0)  
The STA reads bit 1.0 to determine if the ICS1893 has an extended register set. In the ICS1893 this bit is  
always logic one, indicating that it has extended registers.  
8.4 Register 2: PHY Identifier Register  
Table 8-7 lists the bits for PHY Identifier Register (Register 2), which is one of two PHY Identifier Registers  
that are part of a set defined by the ISO/IEC specification. As a set, the PHY Identifier Registers (Registers  
2 and 3) include a unique, 32-bit PHY Identifier composed from the following:  
• Organizationally Unique Identifier (OUI), discussed in this section  
• Manufacturer’s PHY Model Number, discussed in Section 8.5, “Register 3: PHY Identifier Register”  
• Manufacturer’s PHY Revision Number, discussed in Section 8.5, “Register 3: PHY Identifier Register”  
All of the bits in the two PHY Identifier Registers are Command Override Write bits. An STA can read them  
at any time without condition. However, an STA can modify these register bits only when the Command  
Register Override bit (bit 16.15) is enabled with a logic one.  
Note: For an explanation of acronyms used in Table 8-5, see Chapter 1, “Abbreviations and Acronyms”.  
Table 8-7. PHY Identifier Register (Register 2 [0x02])  
Bit  
Definition  
When Bit = 0 When Bit = 1 Access  
Special  
Default  
Hex  
Function  
2.15  
2.14  
2.13  
2.12  
2.11  
2.10  
2.9  
OUI bit 3 | c  
OUI bit 4 | d  
OUI bit 5 | e  
OUI bit 6 | f  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
0
0
0
0
0
0
0
0
0
0
0
1
0
1
0
1
0
OUI bit 7 | g  
OUI bit 8 | h  
OUI bit 9 | I  
0
1
5
2.8  
OUI bit 10 | j  
OUI bit 11 | k  
OUI bit 12 | l  
OUI bit 13 | m  
OUI bit 14 | n  
OUI bit 15 | o  
OUI bit 16 | p  
OUI bit 17 | q  
OUI bit 18 | r  
2.7  
2.6  
2.5  
2.4  
2.3  
2.2  
2.1  
2.0  
IEEE-Assigned Organizationally Unique Identifier (OUI)  
For each manufacturing organization, the IEEE assigns an 3-octet OUI. For Integrated Circuit Systems,  
Inc. the IEEE-assigned 3-octet OUI is 00A0BEh.  
The binary representation of an OUI is formed by expressing each octet as a sequence of eight bits, from  
least significant to most significant, and from left to right. Table 8-8 provides the ISO/IEC-defined mapping  
of the OUI (in IEEE Std 802-1990 format) to Management Registers 2 and 3.  
Table 8-8. IEEE-Assigned Organizationally Unique Identifier  
First Octet  
Second Octet  
Third Octet  
0
0
0
A
E
B
a
1
b
2
c
d
4
e
5
f
g
7
h
8
i
j
k
l
m
n
o
p
q
r
s
t
u
v
w
x
3
6
9
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24  
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
1
0
1
1
1
1
1
0
1
0
0
1
5
F
1
2.15:12  
2.11:8  
2.7:4  
2.3:0  
3.15:12  
Register 3  
3.11:10  
Register 2  
8.5 Register 3: PHY Identifier Register  
Table 8-9 lists the bits for PHY Identifier Register (Register 3), which is one of two PHY Identifier Registers  
that are part of a set defined by the ISO/IEC specification. This register stores the following:  
• Part of the OUI [see the text in Section 8.4, “Register 2: PHY Identifier Register”]  
• Manufacturer’s PHY Model Number  
• Manufacturer’s PHY Revision Number  
All the bits in the two PHY Identifier Registers are Command Override Write bits. An STA can read them at  
any time without condition. However, An STA can modify these register bits only when the Command  
Register Override bit (bit 16.15) is enabled with a logic one.  
Note: For an explanation of acronyms used in Table 8-5, see Chapter 1, “Abbreviations and Acronyms”.  
Table 8-9. PHY Identifier Register (Register 3 [0x03])  
Bit  
Definition  
When Bit = 0 When Bit = 1 Access  
Special  
Default Hex  
Function  
3.15 OUI bit 19 | s  
3.14 OUI bit 20 | t  
3.13 OUI bit 21 | u  
3.12 OUI bit 22 | v  
3.11 OUI bit 23 | w  
3.10 OUI bit 24 | x  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
1
1
1
1
0
1
0
0
0
1
0
0
0
0
0
1
F
4
4
1
3.9  
3.8  
3.7  
3.6  
3.5  
3.4  
3.3  
3.2  
3.1  
3.0  
Manufacturer’s Model Number bit 5  
Manufacturer’s Model Number bit 4  
Manufacturer’s Model Number bit 3  
Manufacturer’s Model Number bit 2  
Manufacturer’s Model Number bit 1  
Manufacturer’s Model Number bit 0  
Revision Number bit 3  
Revision Number bit 2  
Revision Number bit 1  
Revision Number bit 0  
8.5.1 OUI bits 19-24 (bits 3.15:10)  
The most-significant 6 bits of register 3 (that is, bits 3.15:10) include OUI bits 19 through 24. OUI bit 19 is  
stored in bit 3.15, while OUI bit 24 is stored in bit 3.10.  
8.5.2 Manufacturer's Model Number (bits 3.9:4)  
The model number for the ICS1893 is 4 (decimal). It is stored in bit 3.9:4 as 00100b.  
8.5.3 Revision Number (bits 3.3:0)  
Table 8-10 lists the valid ICS1893 revision numbers, which are 4-bit binary numbers stored in bits 3.3:0.  
Table 8-10. ICS1893 Revision Number  
Decimal  
Bits 3.3:0  
Description  
0
0001  
ICS First Release  
8.6 Register 4: Auto-Negotiation Register  
Table 8-11 lists the bits for the Auto-Negotiation Register. An STA uses this register to select the ICS1893  
capabilities that it wants to advertise to its remote link partner. During the auto-negotiation process, the  
ICS1893 advertises (that is, exchanges) capability data with its remote link partner by using a pre-defined  
Link Code Word. The Link Code Word is embedded in the Fast Link Pulses exchanged between PHYs  
when the ICS1893 has its Auto-Negotiation sublayer enabled. The value of the Link Control Word is  
established based on the value of the bits in this register.  
Note: For an explanation of acronyms used in Table 8-5, see Chapter 1, “Abbreviations and Acronyms”.  
Table 8-11. Auto-Negotiation Advertisement Register (register 4 [0x04])  
Bit  
Definition  
When Bit = 0  
When Bit = 1  
Ac-  
cess  
SF De- Hex  
fault  
4.15 Next Page  
Next page not supported  
Always 0  
Next page supported  
N/A  
R/W  
CW  
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
0
0†  
0
0
1
E
1
4.14 IEEE reserved  
4.13 Remote fault  
4.12 IEEE reserved  
4.11 IEEE reserved  
4.10 IEEE reserved  
4.9 100Base-T4  
Locally, no faults detected  
Always 0  
Local fault detected  
N/A  
R/W  
CW  
0†  
0†  
0†  
0
Always 0  
N/A  
CW  
Always 0  
N/A  
CW  
Always 0. (Not supported.)  
N/A  
CW  
4.8 100Base-TX, full duplex Do not advertise ability  
4.7 100Base-TX, half duplex Do not advertise ability  
Advertise ability  
Advertise ability  
Advertise ability  
Advertise ability  
Note 1  
Note 1  
Note 1  
Note 1  
CW  
1
1
4.6 10Base-T, full duplex  
4.5 10Base-T half duplex  
4.4 Selector Field bit S4  
4.3 Selector Field bit S3  
4.2 Selector Field bit S2  
4.1 Selector Field bit S1  
4.0 Selector Field bit S0  
Do not advertise ability  
Do not advertise ability  
1
1
IEEE 802.3-specified default N/A  
IEEE 802.3-specified default N/A  
IEEE 802.3-specified default N/A  
IEEE 802.3-specified default N/A  
0
CW  
0
CW  
0
CW  
0
N/A  
IEEE 802.3-specified  
default  
CW  
1
† As per the IEEE Std 802.3u, during any write operation to any bit in this register, the STA must write the default value  
to all Reserved bits.  
Note 1:  
• In Hardware mode (that is, HW/SW pin is logic zero), this bit is a Read-Only bit.  
• In Software mode (that is, HW/SW pin is logic one), this bit is a Command Override Write bit.  
8.6.1 Next Page (bit 4.15)  
This bit indicates whether the ICS1893 uses the Next Page Mode functions during the auto-negotiation  
process. If bit 4.15 is logic:  
• Zero, then the ICS1893 indicates to its remote link partner that these features are disabled. (Although  
the default value of this bit is logic zero, the ICS1893 does support the Next Page function.)  
• One, then the ICS1893 advertises to its remote link partner that this feature is enabled.  
8.6.2 IEEE Reserved Bit (bit 4.14)  
The ISO/IEC specification reserves this bit for future use. However, the ISO/IEC Standard also defines bit  
4.14 as the Acknowledge bit.  
When this reserved bit is read by an STA, the ICS1893 returns a logic zero. However, whenever an STA  
writes to this reserved bit, it must use the default value specified in this data sheet. ICS uses some  
reserved bits to invoke auxiliary functions. To ensure proper operation of the ICS1893, an STA must  
maintain the default value of these bits. Therefore, ICS recommends that an STA always write the default  
value of any reserved bits during all management register write operations.  
Reserved bit 4.14 is a Command Override Write (CW) bit. Whenever bit 16.15 (the Command Register  
Override bit) is logic:  
• Zero, the ICS1893 isolates all STA writes to bit 4.14.  
• One, an STA can modify the value of bit 4.14.  
8.6.3 Remote Fault (bit 4.13)  
When the ICS1893 Auto-Negotiation sublayer is enabled, the ICS1893 transmits the Remote Fault bit 4.13  
to its remote link partner during the auto-negotiation process. The Remote Fault bit is part of the Link Code  
Word that the ICS1893 exchanges with its remote link partner. The ICS1893 sets this bit to logic one  
whenever it detects a problem with the link, locally. The data in this register is sent to the remote link partner  
to inform it of the potential problem. If the ICS1893 does not detect a link fault, it clears bit 4.13 to logic zero.  
Whenever the ICS1893:  
• Does not detect a link fault, the ICS1893 clears bit 4.13 to logic zero.  
• Detects a problem with the link, during the auto-negotiation process, this bit is set. As a result, the data  
on this bit is sent to the remote link partner to inform it of the potential problem.  
8.6.4 IEEE Reserved Bits (bits 4.12:10)  
The IEEE reserves these bits for future use. When an STA:  
• Reads a reserved bit, the ICS1893 returns a logic zero.  
• Writes to a reserved bit, it must use the default value specified in this data sheet.  
The ICS1893 uses some reserved bits to invoke auxiliary functions. To ensure proper operation of the  
ICS1893, an STA must maintain the default value of these bits. Therefore, ICS recommends that during  
any STA write operation, an STA write the default value to all reserved bits, even those bits that are Read  
Only.  
8.6.5 Technology Ability Field (bits 4.9:5)  
When its Auto-Negotiation sublayer is enabled, the ICS1893 transmits its link capabilities to its remote link  
partner during the auto-negotiation process. The Technology Ability Field (TAF) bits 4.12:5 determine the  
specific abilities that the ICS1893 advertises. The ISO/IEC specification defines the TAF technologies in  
Annex 28B.  
The ISO/IEC specification reserves bits 4.12:10 for future use. When each of these reserved bits is:  
• Read by an STA, the ICS1893 returns a logic zero  
• Written to by an STA, the STA must use the default value specified in this data sheet  
ICS uses some reserved bits to invoke auxiliary functions. To ensure proper operation of the ICS1893, an  
STA must maintain the default value of these bits. Therefore, ICS recommends that an STA always write  
the default value of any reserved bits during all management register write operations.  
Reserved bits 4.12:10 are Command Override Write (CW) bits. Whenever bit 16.15 (the Command  
Register Override bit) is logic:  
• Zero, the ICS1893 isolates all STA writes to CW bits, including bits 4.12:10.  
• One, an STA can modify the value of bits 4.12:10  
Each of the bits 4.9:5 in the TAF represent a specific technology capability. When one of these bits is logic:  
• Zero, it indicates to the remote link partner that the local device cannot support the technology  
represented by the bit.  
• One, it indicates to the remote link partner that the local device can support the technology.  
With the exception of bit 4.9, the default settings of the TAF bits depend on the ICS1893 operating mode.  
Bit 4.9 is always logic zero, indicating that the ICS1893 cannot support 100Base-T4 operations.  
8.6.5.1 Technology Ability Field: Hardware Mode  
When the ICS1893 is operating in hardware mode (that is, the HW/SW pin is logic zero), these TAF bits are  
Read-Only bits. The default value of these bits depends on the signal level on the HW/SW pin and whether  
the Auto-Negotiation sublayer is enabled.  
In hardware mode, with the ANSEL pin pulled:  
• Low to a disabled state, the ICS1893 does not execute the auto-negotiation process. Upon completion  
of the initialization sequence, the ICS1893 proceeds to the idle state and begins ‘sending idles’  
according to the technology mode selected by the 10/100SEL pin and the DPXSEL pin. In this mode, the  
values of the TAF bits (bits 4.8:5) are undefined.  
• High to an enabled state, the ICS1893 executes the auto-negotiation process and advertises its  
capabilities to the remote link partner immediately following reset. The 10/100SEL and DPXSEL input  
pins determine the single capability that the ICS1893 advertises. The ICS1893 updates the  
Auto-Negotiation Advertisement Register TAF field to indicate the selection made by these pins. The  
ICS1893 sets only one of these four bits to logic one. The other three bits are a logic zero.  
Note: The ICS1893 does not alter the value of the Status Register bits. Although the ICS1893 is  
advertising only one technology, the ISO/IEC definitions for the Status Register bits require  
these bits to indicate all the capabilities of the ICS1893.  
8.6.5.2 Technology Ability Field: Software Mode  
In Software mode (that is, the HW/SW pin is logic one), these TAF bits are Command Override Write bits.  
The default value of these bits depends on the signal level on the HW/SW pin and whether the  
Auto-Negotiation sublayer is enabled.  
In Software mode, with the Auto-Negotiation Enable bit (bit 0.12) set to logic:  
• Zero (that is, disabled), the ICS1893 does not execute the auto-negotiation process. Upon completion of  
the initialization sequence, the ICS1893 proceeds to the Idle state and begins transmitting IDLES. Two  
Control Register bits – the Data Rate Select bit (bit 0.13) and the Duplex Select bit (bit 0.8) – determine  
the technology mode that the ICS1893 uses for data transmission and reception. In this mode, the  
values of the TAF bits (bits 4.8:5) are undefined.  
• One (that is, enabled), the ICS1893 executes the auto-negotiation process and advertises its capabilities  
to the remote link partner. The TAF bits (bits 4.8:5) determine the capabilities that the ICS1893  
advertises to its remote link partner. For the ICS1893, all of these bits 4.8:5 are set to logic one,  
indicating the ability of the ICS1893 to provide these technologies.  
Note:  
1. The ICS1893 does not alter the value of the Status Register bits based on the TAF bits in register  
4, as the ISO/IEC definitions for the Status Register bits require these bits to indicate all the  
capabilities of the ICS1893.  
2. In this mode, an STA can alter the default TAF bit settings, 4.12:5, and subsequently issue an  
Auto-Negotiation Restart.  
8.6.6 Selector Field (Bits 4.4:0)  
When its Auto-Negotiation Sublayer is enabled, the ICS1893 transmits its link capabilities to its remote Link  
Partner during the auto-negotiation process. The Selector Field is transmitted based on the value of bits  
4.4:0. These bits indicate to the remote link partner the type of message being sent during the  
auto-negotiation process. The ICS1893 supports IEEE Std 802.3, represented by a value of 00001b in bits  
4.4:0. The ISO/IEC 8802-3 standard defines the Selector Field technologies in Annex 28A.  
8.7 Register 5: Auto-Negotiation Link Partner Ability Register  
Table 8-12 lists the bits for the Auto-Negotiation Link Partner Ability Register. An STA uses this register to  
determine the capabilities being advertised by the remote link partner. During the auto-negotiation process,  
the ICS1893 advertises (that is, exchanges) the capability data with its remote link partner using a  
pre-defined Link Code Word. The value of the Link Control Word received from its remote link partner  
establishes the value of the bits in this register.  
Note:  
1. For an explanation of acronyms used in Table 8-12, see Chapter 1, “Abbreviations and Acronyms”.  
2. The values in this register are valid only when the auto-negotiation process is complete, as indicated by  
bit 1.5 or bit 17.4.  
Table 8-12. Auto-Negotiation Link Partner Ability Register (register 5 [0x05])  
Bit  
Definition  
When Bit = 0  
When Bit = 1  
Ac- SF De- Hex  
cess  
RO  
RO  
RO  
RO  
RO  
RO  
RO  
RO  
RO  
RO  
RO  
RO  
CW  
CW  
CW  
CW  
fault  
5.15 Next Page  
Next Page disabled  
Always 0  
Next Page enabled  
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
0
0
0
0
0
5.14 Acknowledge  
5.13 Remote fault  
5.12 IEEE reserved  
5.11 IEEE reserved  
5.10 IEEE reserved  
N/A  
0
No faults detected  
Always 0  
Remote fault detected  
0
N/A  
0†  
0†  
0†  
0
Always 0  
N/A  
Always 0  
N/A  
5.9  
5.8  
5.7  
5.6  
5.5  
5.4  
5.3  
5.2  
5.1  
5.0  
100Base-T4  
Always 0. (Not supported.)  
N/A  
100Base-TX, full duplex Link partner is not capable  
100Base-TX, half duplex Link partner is not capable  
Link partner is capable  
Link partner is capable  
Link partner is capable  
Link partner is capable  
0
0
10Base-T, full duplex  
10Base-T, half duplex  
Selector Field bit S4  
Selector Field bit S3  
Selector Field bit S2  
Selector Field bit S1  
Selector Field bit S0  
Link partner is not capable  
Link partner is not capable  
0
0
IEEE 802.3 defined. Always 0. N/A  
IEEE 802.3 defined. Always 0. N/A  
IEEE 802.3 defined. Always 0. N/A  
IEEE 802.3 defined. Always 0. N/A  
0
0
0
0
N/A  
IEEE 802.3 defined.  
Always 1.  
0
† As per the IEEE Std 802.3u, during any write operation to any bit in this register, the STA must write the default value  
to all Reserved bits.  
8.7.1 Next Page (bit 5.15)  
If bit 5.15 is logic:  
• Zero, then the remote link partner is indicating that this is the last page being transmitted.  
• One, then the remote link partner is indicating that additional pages follow.  
8.7.2 Acknowledge (bit 5.14)  
The ISO/IEC specification defines bit 5.14 as the Acknowledge bit. When this bit is a:  
• Zero, it indicates that the remote link partner has not received the ICS1893 Link Control Word.  
• One, it indicates to the ICS1893 / STA that the remote link partner has acknowledged reception of the  
ICS1893 Link Control Word.  
8.7.3 Remote Fault (bit 5.13)  
The ISO/IEC specification defines bit 5.13 as the Remote Fault bit. This bit is set based on the Link Control  
Word received from the remote link partner. When this bit is a logic:  
• Zero, it indicates that the remote link partner detects a Link Fault.  
• One, it indicates to the ICS1893 / STA that the remote link partner detects a Link Fault.  
Note: For more information about this bit, see Section 8.3.9, “Remote Fault (bit 1.4)”.  
8.7.4 Technology Ability Field (bits 5.12:5)  
The Technology Ability Field (TAF) bits (bits 5.12:5) determine the specific abilities that the remote link  
partner is advertising. These bits are set based upon the Link Code Word received from the remote link  
partner during the auto-negotiation process. The ISO/IEC specification defines the TAF technologies in  
Annex 28B.  
The ISO/IEC specification reserves bits 5.12:10 for future use. When each of these reserved bits is:  
• Read by an STA, the ICS1893 returns a logic zero.  
• Written to by an STA, the STA must use the default value specified in this data sheet.  
ICS uses some reserved bits to invoke auxiliary functions. To ensure proper operation of the ICS1893, an  
STA must maintain the default value of these bits. Therefore, ICS recommends that an STA always write  
the default value of any reserved bits during all management register write operations.  
8.7.5 Selector Field (bits 5.4:0)  
The Selector Field bits indicate the technology or encoding that the remote link partner is using for the  
Auto-Negotiation message. The ICS1893 supports only IEEE Std 802.3, represented by a value of 00001b  
in bits 5.4:0. The ISO/IEC standard defines the Selector Field technologies in Annex 28A. Presently, the  
IEEE standard defines the following two valid codes:  
• 00001b (IEEE Std 802.3)  
• 00010b (IEEE Std 802.9)  
8.8 Register 6: Auto-Negotiation Expansion Register  
Table 8-13 lists the bits for the Auto-Negotiation Expansion Register, which indicates the status of the  
Auto-Negotiation process.  
Note: For an explanation of acronyms used in Table 8-13, see Chapter 1, “Abbreviations and Acronyms”.  
Table 8-13. Auto-Negotiation Expansion Register (register 6 [0x06])  
Bit  
Definition  
When Bit = 0  
When Bit = 1  
Ac- SF De- Hex  
cess  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
CW  
fault  
0†  
0†  
0†  
0†  
0†  
0†  
0†  
0†  
0†  
0†  
0†  
0
6.15 IEEE reserved  
6.14 IEEE reserved  
6.13 IEEE reserved  
6.12 IEEE reserved  
6.11 IEEE reserved  
6.10 IEEE reserved  
Always 0  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
–
–
–
–
–
–
–
–
–
–
–
0
0
0
Always 0  
Always 0  
Always 0  
Always 0  
Always 0  
Always 0  
Always 0  
Always 0  
Always 0  
Always 0  
No Fault  
6.9  
6.8  
6.7  
6.6  
6.5  
6.4  
IEEE reserved  
IEEE reserved  
IEEE reserved  
IEEE reserved  
IEEE reserved  
Parallel detection fault  
Multiple technologies  
detected  
RO LH  
6.3  
6.2  
Link partner Next Page  
able  
Link partner is not Next  
Page able  
Link partner is Next Page  
able  
RO  
RO  
–
–
0
1
4
Next Page able  
Local device is not Next  
Page able  
Local device is Next Page  
able  
6.1  
6.0  
Page received  
Next Page not received  
Next Page received  
RO LH  
RO  
0
0
Link partner  
Link partner is not  
Link partner is  
–
Auto-Negotiation able  
Auto-Negotiation able  
Auto-Negotiation able  
† As per the IEEE Std 802.3u, during any write operation to any bit in this register, the STA must write the default value  
to all Reserved bits.  
8.8.1 IEEE Reserved Bits (bits 6.15:5)  
The ISO/IEC specification reserves these bits for future use. When an STA:  
• Reads a reserved bit, the ICS1893 returns a logic zero.  
• Writes to a reserved bit, the STA must use the default value specified in this data sheet.  
ICS uses some reserved bits to invoke auxiliary functions. To ensure proper operation of the ICS1893, an  
STA must maintain the default value of these bits. Therefore, ICS recommends that an STA always write  
the default value of any reserved bits during all management register write operations.  
Reserved bits 5.15:5 are Command Override Write (CW) bits. When the Command Register Override bit  
(bit 16.15) is logic:  
• Zero, the ICS1893 isolates all STA writes to CW bits.  
• One, an STA can modify the value of these bits  
8.8.2 Parallel Detection Fault (bit 6.4)  
The ICS1893 sets this bit to a logic one if a parallel detection fault is encountered. A parallel detection fault  
occurs when the ICS1893 cannot disseminate the technology being used by its remote link partner.  
Bit 6.4 is a latching high (LH) status bit. (For more information on latching high and latching low bits, see  
Section 8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
8.8.3 Link Partner Next Page Able (bit 6.3)  
Bit 6.3 is a status bit that reports the capabilities of the remote link partner to support the Next Page  
features of the auto-negotiation process. The ICS1893 sets this bit to a logic one if the remote link partner  
sets the Next Page bit in its Link Control Word.  
8.8.4 Next Page Able (bit 6.2)  
Bit 6.2 is a status bit that reports the capabilities of the ICS1893 to support the Next Page features of the  
auto-negotiation process. The ICS1893 sets this bit to a logic one to indicate that it can support these  
features.  
8.8.5 Page Received (bit 6.1)  
The ICS1893 sets its Page Received bit to a logic one whenever a new Link Control Word is received and  
stored in its Auto-Negotiation link partner ability register. The Page Received bit is cleared to logic zero on  
a read of the Auto-Negotiation Expansion Register.  
Bit 6.1 is a latching high (LH) status bit. (For more information on latching high and latching low bits, see  
Section 8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
8.8.6 Link Partner Auto-Negotiation Able (bit 6.0)  
If the ICS1893:  
• Does not receive Fast Link Pulse bursts from its remote link partner, then this bit remains a logic zero.  
• Receives valid FLP bursts from its remote link partner (thereby indicating that it can participate in the  
auto-negotiation process), then the ICS1893 sets this bit to a logic one.  
8.9 Register 7: Auto-Negotiation Next Page Transmit Register  
Table 8-14 lists the bits for the Auto-Negotiation Next Page Transmit Register, which establishes the  
contents of the Next Page Link Control Word that is transmitted during Next Page Operations. This table is  
compliant with the ISO/IEC specification.  
Note: For an explanation of acronyms used in Table 8-14, see Chapter 1, “Abbreviations and Acronyms”.  
Table 8-14. Auto-Negotiation Next Page Transmit Register (register 7 [0x07])  
Bit  
Definition  
When Bit = 0  
When Bit = 1  
Ac- SF De- Hex  
cess  
RW  
RO  
fault  
7.15 Next Page  
Last Page  
Additional Pages follow  
N/A  
–
–
–
–
0
2
7.14 IEEE reserved  
7.13 Message Page  
7.12 Acknowledge 2  
Always 0  
0†  
1
Unformatted Page  
Message Page  
RW  
RW  
Cannot comply with  
Message  
Can comply with  
Message  
0
7.11 Toggle  
Previous Link Code  
Word was zero  
Previous Link Code  
Word was one  
RO  
RW  
RW  
RW  
RW  
RW  
RW  
RW  
RW  
RW  
RW  
RW  
–
–
–
–
–
–
–
–
–
–
–
–
0
0
0
0
0
0
0
0
0
0
0
1
0
7.10 Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
7.9  
7.8  
7.7  
7.6  
7.5  
7.4  
7.3  
7.2  
7.1  
7.0  
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
0
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
1
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
Message code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
/Unformatted code field  
† As per the IEEE Std 802.3u, during any write operation to any bit in this register, the STA must write the default value  
to all Reserved bits.  
8.9.1 Next Page (bit 7.15)  
This bit is used by a PHY/STA to enable the transmission of Next Pages following the base Link Control  
Word as long as the remote link partner supports the Next Page features of Auto-Negotiation.  
This bit is used to establish the state of the Next Page (NP) bit of the Next Page Link Control Word (that is,  
the NP bit of the Next Page Link Control Word tracks this bit). During a Next Page exchange, if the NP bit  
is logic:  
• Zero, it indicates to the remote link partner that this is the last Message or Page.  
• One, it indicates to the remote link partner that additional Pages follow this Message.  
8.9.2 IEEE Reserved Bit (bit 7.14)  
The ISO/IEC specification reserves this bit for future use. When this reserved bit is:  
• Read by an STA, the ICS1893 returns a logic zero.  
• Written to by an STA, the STA must use the default value specified in this data sheet.  
ICS uses some reserved bits to invoke auxiliary functions. To ensure proper operation of the ICS1893, an  
STA must maintain the default value of these bits. Therefore, ICS recommends that an STA always write  
the default value of any reserved bits during all management register write operations.  
8.9.3 Message Page (bit 7.13)  
The Message Page (MP) bit (bit 7.13) is used to determine the format or type of Page being transmitted.  
The value of this bit establishes the state of the MP bit in the Next Page Link Control Word.  
If this bit is set to logic:  
• Zero, it indicates that the Page is an Unformatted Page.  
• One, it indicates to the remote link partner that the Page being transmitted is a Message Page.  
8.9.4 Acknowledge 2 (bit 7.12)  
This bit is used to indicate the ability of the ICS1893 to comply with a message.  
The value of this bit establishes the state of the Ack2 bit in the Next Page Link Control Word. If this bit is set  
to logic:  
• Zero, it indicates that the ICS1893 cannot comply with the message.  
• One, it indicates to the remote link partner that the ICS1893 can comply with the message.  
8.9.5 Toggle (bit 7.11)  
The Toggle (T) bit (bit 7.11) is used to synchronize the transmission of Next Page messages with the  
remote link partner. The value of this bit establishes the state of the Toggle bit in the Next Page Link  
Control Word. This bit toggles with each transmitted Link Control Word.  
If the previous Next Page Link Control Word Toggle bit has a value of logic:  
• Zero, then the Toggle bit is set to logic one.  
• One, then the Toggle bit is set to logic zero.  
The initial Next Page Link Control Word Toggle bit is set to the inverse of the base Link Control Word bit 11.  
8.9.6 Message Code Field / Unformatted Code Field (bits 7.10:0)  
Bits 7.10:0 represent either the Message Code field M[10:0] or the Unformatted Code field U[10:0] bits. The  
value of these bits establish the state of the M[10:0] / U[10:0] bits in the Next Page Link Control Word.  
8.10 Register 8: Auto-Negotiation Next Page Link Partner Ability Register  
Table 8-15 lists the bits for the Auto-Negotiation Next Page Link Partner Ability Register, which establishes  
the contents of the Next Page Link Control Word that is transmitted during Next Page Operations. This  
table is compliant with the ISO/IEC specification.  
Note: For an explanation of acronyms used in Table 8-15, see Chapter 1, “Abbreviations and Acronyms”.  
Table 8-15. Auto-Negotiation Next Page Link Partner Ability Register (register 8 [0x08])  
Bit  
Definition  
When Bit = 0  
When Bit = 1  
Ac- SF De- Hex  
cess  
RO  
RO  
RO  
RO  
fault  
8.15 Next Page  
Last Page  
Additional Pages follow  
N/A  
–
–
–
–
0
0
8.14 IEEE reserved  
8.13 Message Page  
8.12 Acknowledge 2  
Always 0  
0†  
0
Unformatted Page  
Message Page  
Cannot comply with  
Message  
Can comply with  
Message  
0
8.11 Toggle  
Previous Link Code  
Word was zero  
Previous Link Code  
Word was one  
RO  
RO  
RO  
RO  
RO  
RO  
RO  
RO  
RO  
RO  
RO  
RO  
–
–
–
–
–
–
–
–
–
–
–
–
0
0
0
0
0
0
0
0
0
0
0
0
0
8.10 Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
8.9  
8.8  
8.7  
8.6  
8.5  
8.4  
8.3  
8.2  
8.1  
8.0  
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
0
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
0
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
Message code field  
/Unformatted code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
Message code field  
Bit value depends on  
the particular message  
Bit value depends on  
the particular message  
/Unformatted code field  
† As per the IEEE Std 802.3u, during any write operation to any bit in this register, the STA must write the default value  
to all Reserved bits.  
8.10.1 Next Page (bit 8.15)  
This bit is used by a PHY/STA to enable the transmission of Next Pages following the base Link Control  
Word as long as the remote link partner supports the Next Page features of Auto-Negotiation.  
This bit is used to establish the state of the Next Page (NP) bit of the Next Page Link Control Word (that is,  
the NP bit of the Next Page Link Control word tracks this bit). During a Next Page exchange, if the NP bit is  
logic:  
• Zero, it indicates to the remote link partner that this is the last Message or Page.  
• One, it indicates to the remote link partner that additional Pages follow this Message.  
8.10.2 IEEE Reserved Bit (bit 8.14)  
The ISO/IEC specification reserves this bit for future use. When this reserved bit is:  
• Read by an STA, the ICS1893 returns a logic zero.  
• Written to by an STA, the STA must use the default value specified in this data sheet.  
ICS uses some reserved bits to invoke auxiliary functions. To ensure proper operation of the ICS1893, an  
STA must maintain the default value of these bits. Therefore, ICS recommends that an STA always write  
the default value of any reserved bits during all management register write operations.  
8.10.3 Message Page (bit 8.13)  
The Message Page (MP) bit (bit 8.13) is used to determine the format or type of Page being transmitted.  
The value of this bit establishes the state of the MP bit in the Next Page Link Control Word.  
If this bit is set to logic:  
• Zero, it indicates that the Page is an Unformatted Page.  
• One, it indicates to the remote link partner that the Page being transmitted is a Message Page.  
8.10.4 Acknowledge 2 (bit 8.12)  
This bit is used to indicate the ability of the ICS1893 to comply with a message.  
The value of this bit establishes the state of the Ack2 bit in the Next Page Link Control Word. If this bit is set  
to logic:  
• Zero, it indicates that the ICS1893 cannot comply with the message.  
• One, it indicates to the remote link partner that the ICS1893 can comply with the message.  
If the previous Next Page Link Control Word Toggle bit has a value of logic:  
• Zero, then the Toggle bit is set to logic one.  
• One, then the Toggle bit is set to logic zero.  
The initial Next Page Link Control Word Toggle bit is set to the inverse of the base Link Control Word bit 11.  
8.10.5 Message Code Field / Unformatted Code Field (bits 8.10:0)  
Bits 8.10:0 represent either the Message Code field M[10:0] or the Unformatted Code field U[10:0] bits. The  
value of these bits establish the state of the M[10:0] / U[10:0] bits in the Next Page Link Control Word.  
8.11 Register 16: Extended Control Register  
Table 8-16 lists the bits for the Extended Control Register, which the ICS1893 provides to allow an STA to  
customize the operations of the device.  
Note:  
1. For an explanation of acronyms used in Table 8-16, see Chapter 1, “Abbreviations and Acronyms”.  
2. During any write operation to any bit in this register, the STA must write the default value to all  
Reserved bits.  
Table 8-16. Extended Control Register (register 16 [0x10])  
Bit  
Definition  
When Bit = 0  
When Bit = 1  
Ac-  
SF  
De-  
Hex  
cess  
fault  
16.15 Command Override Write Disabled  
enable  
Enabled  
RW  
SC  
0
–
16.14 ICS reserved  
16.13 ICS reserved  
16.12 ICS reserved  
16.11 ICS reserved  
16.10 PHY Address Bit 4  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
RW/0  
RW/0  
RW/0  
RW/0  
RO  
–
–
–
–
–
0
Read unspecified  
Read unspecified  
Read unspecified  
0
0
0
–
For a detailed explanation of this bit’s operation,  
see Section 6.8, “Status Interface”.  
P4RD†  
16.9  
16.8  
16.7  
16.6  
PHY Address Bit 3  
PHY Address Bit 2  
PHY Address Bit 1  
PHY Address Bit 0  
For a detailed explanation of this bit’s operation,  
see Section 6.8, “Status Interface”.  
RO  
RO  
RO  
RO  
–
–
–
–
P3TD†  
P2LI†  
For a detailed explanation of this bit’s operation,  
see Section 6.8, “Status Interface”.  
For a detailed explanation of this bit’s operation,  
see Section 6.8, “Status Interface”.  
P1CL†  
P0AC†  
–
8
For a detailed explanation of this bit’s operation,  
see Section 6.8, “Status Interface”.  
16.5  
16.4  
16.3  
16.2  
16.1  
16.0  
Stream Cipher Test Mode Normal operation  
Test mode  
RW  
RW/0  
RW  
–
–
–
–
–
–
0
–
1
0
0
0
ICS reserved  
Read unspecified  
NRZ encoding  
Disabled  
Read unspecified  
NRZI encoding  
Enabled  
NRZ/NRZI encoding  
Transmit invalid codes  
ICS reserved  
RW  
Read unspecified  
Read unspecified  
RW/0  
RW  
Stream Cipher disable  
Stream Cipher enabled Stream Cipher disabled  
† The default is the state of this pin at reset.  
8.11.1 Command Override Write Enable (bit 16.15)  
The Command Override Write Enable bit provides an STA the ability to alter the Command Override Write  
(CW) bits located throughout the MII Register set. A two-step process is required to alter the value of a CW  
bit:  
1. Step one is to issue a Command Override Write, (that is, set bit 16.15 to logic one). This step enables  
the next MDIO write to have the ability to alter any CW bit.  
2. Step two is to write to the register that includes the CW bit which requires modification.  
Note: The Command Override Write Enable bit is a Self-Clearing bit that is automatically reset to logic  
zero after the next MII write, thereby allowing only one subsequent write to alter the CW bits in a  
single register. To alter additional CW bits, the Command Override Write Enable bit must once  
again be set to logic one.  
8.11.2 ICS Reserved (bits 16.14:11)  
ICS is reserving these bits for future use. Functionally, these bits are equivalent to IEEE Reserved bits.  
When one of these reserved bits is:  
• Read by an STA, the ICS1893 returns a logic zero.  
• Written to by an STA, the STA must use the default value specified in this data sheet.  
ICS uses some reserved bits to invoke auxiliary functions. To ensure proper operation of the ICS1893, an  
STA must maintain the default value of these bits. Therefore, ICS recommends that an STA always write  
the default value of any reserved bits during all management register write operations.  
8.11.3 PHY Address (bits 16.10:6)  
These five bits hold the Serial Management Port Address of the ICS1893. During either a hardware reset  
or a power-on reset, the PHY address is read from the LED interface. (For information on the LED  
interface, see Section 6.8, “Status Interface” and Section 9.3.2, “Multi-Function (Multiplexed) Pins: PHY  
Address and LED Pins”). The PHY address is then latched into this register. (The value of each of the PHY  
Address bits is unaffected by a software reset.)  
8.11.4 Stream Cipher Scrambler Test Mode (bit 16.5)  
The Stream Cipher Scrambler Test Mode bit is used to force the ICS1893 to lose LOCK, thereby requiring  
the Stream Cipher Scrambler to resynchronize.  
8.11.5 ICS Reserved (bit 16.4)  
See Section 8.11.2, “ICS Reserved (bits 16.14:11)”, the text for which also applies here.  
8.11.6 NRZ/NRZI Encoding (bit 16.3)  
This bit allows an STA to control whether NRZ (Not Return to Zero) or NRZI (Not Return to Zero, Invert on  
One) encoding is applied to the serial transmit data stream in 100Base-TX mode. When this bit is logic:  
• Zero, the ICS1893 encodes the serial transmit data stream using NRZ encoding.  
• One, the ICS1893 encodes the serial transmit data stream using NRZI encoding.  
8.11.7 Invalid Error Code Test (bit 16.2)  
The Invalid Error Code Test bit allows an STA to force the ICS1893 to transmit symbols that are typically  
classified as invalid. The purpose of this test bit is to permit thorough testing of the 4B/5B encoding and the  
serial transmit data stream by allowing generation of bit patterns that are considered invalid by the ISO/IEC  
4B/5B definition.  
When this bit is logic:  
• Zero, the ISO/IEC defined 4B/5B translation takes place.  
• One – and the TXER signal is asserted by the MAC/repeater – the MII input nibbles are translated  
according to Table 8-17.  
Table 8-17. Invalid Error Code Translation Table  
Symbol  
Meaning  
MII Input Translation  
Nibble  
V
V
Invalid Code  
Invalid Code  
Invalid Code  
Invalid Code  
Error  
0000  
0001  
0010  
0011  
0100  
0101  
0110  
0111  
1000  
1001  
1010  
1011  
1100  
1101  
1110  
1111  
00000  
00001  
00010  
00011  
00100  
00101  
00110  
00111  
00000  
01101  
01100  
10001  
10000  
11001  
11000  
11111  
V
V
H
V
Invalid Code  
Invalid Code  
ESD  
V
R
V
Invalid Code  
ESD  
T
V
Invalid Code  
SSD  
K
V
Invalid Code  
Invalid Code  
SSD  
V (S)  
J
I
Idle  
8.11.8 ICS Reserved (bit 16.1)  
See Section 8.11.2, “ICS Reserved (bits 16.14:11)”, the text for which also applies here.  
8.11.9 Stream Cipher Disable (bit 16.0)  
The Stream Cipher Disable bit allows an STA to control whether the ICS1893 employs the Stream Cipher  
Scrambler in the transmit and receive data paths. When this bit is set to logic:  
• Zero, the Stream Cipher Encoder and Decoder are both enabled for normal operations.  
• One, the Stream Cipher Encoder and Decoder are disabled. This action results in an unscrambled data  
stream (for example, the ICS1893 transmits unscrambled IDLES, and so forth.  
Note: The Stream Cipher Scrambler can be used only for 100-MHz operations.  
8.12 Register 17: Quick Poll Detailed Status Register  
Table 8-18 lists the bits for the Quick-Poll Detailed Status Register. This register is a 16-bit read-only  
register used to provide an STA with detailed status of the ICS1893 operations. During reset, it is initialized  
to pre-defined default values.  
Note:  
1. For an explanation of acronyms used in Table 8-18, see Chapter 1, “Abbreviations and Acronyms”.  
2. Most of this register’s bits are latching high or latching low, which allows the ICS1893 to capture and  
save the occurrence of an event for an STA to read. (For more information on latching high and  
latching low bits, see Section 8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
3. Although some of these status bits are redundant with other management registers, the ICS1893  
provides this group of bits to minimize the number of Serial Management Cycles required to collect the  
status data.  
Table 8-18. Quick Poll Detailed Status Register (register 17 [0x11])  
Bit  
Definition  
When Bit = 0  
When Bit = 1  
Ac-  
cess  
SF  
De- Hex  
fault  
17.15 Data rate  
17.14 Duplex  
10 Mbps  
Half duplex  
100 Mbps  
Full duplex  
RO  
RO  
RO  
–
–
–
–
0
–
17.13 Auto-Negotiation  
Progress Monitor Bit 2  
Reference Decode Table Reference Decode Table  
Reference Decode Table Reference Decode Table  
Reference Decode Table Reference Decode Table  
LMX  
17.12 Auto-Negotiation  
Progress Monitor Bit 1  
RO  
RO  
RO  
RO  
LMX  
LMX  
LH  
0
0
0
0
17.11 Auto-Negotiation  
Progress Monitor Bit 0  
0
17.10 100Base-TX signal  
lost  
Valid signal  
PLL locked  
Signal lost  
17.9  
100BasePLL Lock  
Error  
PLL failed to lock  
LH  
17.8  
17.7  
False Carrier detect  
Normal Carrier or Idle  
False Carrier  
RO  
RO  
LH  
LH  
0
0
Invalid symbol  
detected  
Valid symbols observed  
Invalid symbol received  
0
17.6  
17.5  
Halt Symbol detected No Halt Symbol received Halt Symbol received  
RO  
RO  
LH  
LH  
0
0
Premature End  
detected  
Normal data stream  
Stream contained two  
IDLE symbols  
17.4  
17.3  
Auto-Negotiation  
complete  
Auto-Negotiation in  
process  
Auto-Negotiation  
complete  
RO  
RO  
–
–
0
0
100Base-TX signal  
detect  
No signal present  
Signal present  
0
17.2  
17.1  
17.0  
Jabber detect  
Remote fault  
Link Status  
No jabber detected  
Jabber detected  
RO  
RO  
RO  
LH  
LH  
LL  
0
0
0
No remote fault detected Remote fault detected  
Link is not valid Link is valid  
8.12.1 Data Rate (bit 17.15)  
The Data Rate bit indicates the ‘selected technology’. If the ICS1893 is in:  
• Hardware mode, the value of this bit is determined by the 10/100SEL input pin.  
• Software mode, the value of this bit is determined by the Data Rate bit 0.13.  
When bit 17.15 is logic:  
• Zero, it indicates that 10-MHz operations are selected.  
• One, the ICS1893 is indicating that 100-MHz operations are selected.  
Note: This bit does not imply any link status.  
8.12.2 Duplex (bit 17.14)  
The Duplex bit indicates the ‘selected technology’. If the ICS1893 is in:  
• Hardware mode, the value of this bit is determined by the DPXSEL input pin.  
• Software mode, the value of this bit is determined by the Duplex Mode bit 0.8.  
When bit 17.14 is logic:  
• Zero, it indicates that half-duplex operations are selected.  
• One, the ICS1893 is indicating that full-duplex operations are selected.  
Note: This bit does not imply any link status.  
8.12.3 Auto-Negotiation Progress Monitor (bits 17.13:11)  
The Auto-Negotiation Progress Monitor consists of the Auto-Negotiation Complete bit (bit 17.4) and the  
three Auto-Negotiation Monitor bits (bits 17.13:11). The Auto-Negotiation Progress Monitor continually  
examines the state of the Auto-Negotiation Process State Machine and reports the status of  
Auto-Negotiation using the three Auto-Negotiation Monitor bits. Therefore, the value of these three bits  
provides the status of the Auto-Negotiation Process.  
These three bits are initialized to logic zero in one of the following ways:  
• A reset (see Section 5.1, “Reset Operations”)  
• Disabling Auto-Negotiation [see Section 8.2.4, “Auto-Negotiation Enable (bit 0.12)”]  
• Restarting Auto-Negotiation [see Section 8.2.7, “Restart Auto-Negotiation (bit 0.9)”]  
If Auto-Negotiation is enabled, these bits continually latch the highest state that the Auto-Negotiation State  
Machine achieves. That is, they are updated only if the binary value of the next state is greater than the  
binary value of the present state as outlined in Table 8-19.  
Note: An MDIO read of these bits provides a history of the greatest progress achieved by the  
auto-negotiation process. In addition, the MDIO read latches the present state of the  
Auto-Negotiation State Machine for a subsequent read.  
Table 8-19. Auto-Negotiation State Machine (Progress Monitor)  
Auto-Negotiation State Machine  
Auto-Negotiation Progress Monitor  
Auto-  
Auto-  
Auto-  
Auto-  
Negotiation  
Negotiation  
Negotiation  
Negotiation  
Complete Bit Monitor Bit 2 Monitor Bit 1 Monitor Bit 0  
(Bit 17.4)  
(Bit 17.13)  
(Bit 17.12)  
(Bit 17.11)  
Idle  
0
0
0
0
0
0
0
0
1
0
0
0
0
1
1
1
1
0
0
0
1
1
0
0
1
1
0
0
1
0
1
0
1
0
1
0
Parallel Detected  
Parallel Detection Failure  
Ability Matched  
Acknowledge Match Failure  
Acknowledge Matched  
Consistency Match Failure  
Consistency Matched  
Auto-Negotiation Completed  
Successfully  
8.12.4 100Base-TX Receive Signal Lost (bit 17.10)  
The 100Base-TX Receive Signal Lost bit indicates to an STA whether theICS1893 has lost its 100Base-TX  
Receive Signal. If this bit is set to a logic:  
• Zero, it indicates the Receive Signal has remained valid since either the last read or reset of this register.  
• One, it indicates the Receive Signal was lost since either the last read or reset of this register.  
This bit is a latching high bit. (For more information on latching high and latching low bits, see Section  
8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
Note: This bit has no definition in 10Base-T mode.  
8.12.5 100Base PLL Lock Error (bit 17.9)  
The Phase-Locked Loop (PLL) Lock Error bit indicates to an STA whether the ICS1893 has ever  
experienced a PLL Lock Error. A PLL Lock Error occurs when the PLL fails to lock onto the incoming  
100Base data stream. If this bit is set to a logic:  
• Zero, it indicates that a PLL Lock Error has not occurred since either the last read or reset of this register.  
• One, it indicates that a PLL Lock Error has occurred since either the last read or reset of this register.  
This bit is a latching high bit. (For more information on latching high and latching low bits, see Section  
8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
Note: This bit has no definition in 10Base-T mode.  
8.12.6 False Carrier (bit 17.8)  
The False Carrier bit indicates to an STA the detection of a False Carrier by the ICS1893 in 100Base mode.  
A False Carrier occurs when the ICS1893 begins evaluating potential data on the incoming 100Base data  
stream, only to learn that it was not a valid /J/K/. If this bit is set to a logic:  
• Zero, it indicates a False Carrier has not been detected since either the last read or reset of this register.  
• One, it indicates a False Carrier was detected since either the last read or reset of this register.  
This bit is a latching high bit. (For more information on latching high and latching low bits, see Section  
8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
Note: This bit has no definition in 10Base-T mode.  
8.12.7 Invalid Symbol (bit 17.7)  
The Invalid Symbol bit indicates to an STA the detection of an Invalid Symbol in a 100Base data stream by  
the ICS1893.  
When the ICS1893 is receiving a packet, it examines each received Symbol to ensure the data is error free.  
If an error occurs, the port indicates this condition to the MAC/repeater by asserting the RXER signal. In  
addition, the ICS1893 sets its Invalid Symbol bit to logic one. Therefore, if this bit is set to a logic:  
• Zero, it indicates an Invalid Symbol has not been detected since either the last read or reset of this  
register.  
• One, it indicates an Invalid Symbol was detected since either the last read or reset of this register.  
This bit is a latching high bit. (For more information on latching high and latching low bits, see Section  
8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
Note: This bit has no definition in 10Base-T mode.  
8.12.8 Halt Symbol (bit 17.6)  
The Halt Symbol bit indicates to an STA the detection of a Halt Symbol in a 100Base data stream by the  
ICS1893.  
During reception of a valid packet, the ICS1893 examines each symbol to ensure that the data being  
passed to the MAC/Repeater Interface is error free. In addition, it looks for special symbols such as the Halt  
Symbol. If a Halt Symbol is encountered, the ICS1893 indicates this condition to the MAC/repeater.  
If this bit is set to a logic:  
• Zero, it indicates a Halt Symbol has not been detected since either the last read or reset of this register.  
• One, it indicates a Halt Symbol was detected in the packet since either the last read or reset of this  
register.  
This bit is a latching high bit. (For more information on latching high and latching low bits, see Section  
8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
Note: This bit has no definition in 10Base-T mode.  
8.12.9 Premature End (bit 17.5)  
The Premature End bit indicates to an STA the detection of two consecutive Idles in a 100Base data  
stream by the ICS1893.  
During reception of a valid packet, the ICS1893 examines each symbol to ensure that the data being  
passed to the MAC/Repeater Interface is error free. If two consecutive Idles are encountered, it indicates  
this condition to the MAC/repeater by setting this bit.  
If this bit is set to a logic:  
• Zero, it indicates a Premature End condition has not been detected since either the last read or reset of  
this register.  
• One, it indicates a Premature End condition was detected in the packet since either the last read or reset  
of this register.  
This bit is a latching high bit. (For more information on latching high and latching low bits, see Section  
8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
Note: This bit has no definition in 10Base-T mode.  
8.12.10 Auto-Negotiation Complete (bit 17.4)  
The Auto-Negotiation Complete bit is used to indicate to an STA the completion of the Auto-Negotiation  
process. When this bit is set to logic:  
• Zero, it indicates that the auto-negotiation process is either not complete or is disabled by the Control  
Register’s Auto-Negotiation Enable bit (bit 0.12)  
• One, it indicates that the ICS1893 has completed the auto-negotiation process and that the contents of  
Management Registers 4, 5, and 6 are valid.  
8.12.11 100Base-TX Signal Detect (bit 17.3)  
The 100Base-TX Signal Detect bit indicates either the presence or absence of a signal on the Twisted-Pair  
Receive pins (TP_RXP and TP_RXN) in 100Base-TX mode. This bit is logic:  
• Zero when no signal is detected on the Twisted-Pair Receive pins.  
• One when a signal is present on the Twisted-Pair Receive pins.  
8.12.12 Jabber Detect (bit 17.2)  
Bit 17.2 is functionally identical to bit 1.1. The Jabber Detect bit indicates whether a jabber condition has  
occurred. This bit is a 10Base-T function.  
8.12.13 Remote Fault (bit 17.1)  
Bit 17.1 is functionally identical to bit 1.4.  
8.12.14 Link Status (bit 17.0)  
Bit 17.0 is functionally identical to bit 1.2.  
8.13 Register 18: 10Base-T Operations Register  
The 10Base-T Operations Register provides an STA with the ability to monitor and control the ICS1893  
activity while the ICS1893 is operating in 10Base-T mode.  
Note:  
1. For an explanation of acronyms used in Table 8-20, see Chapter 1, “Abbreviations and Acronyms”.  
2. During any write operation to any bit in this register, the STA must write the default value to all  
Reserved bits.  
Table 8-20. 10Base-T Operations Register (register 18 [0x12])  
Bit  
Definition  
When Bit = 0  
When Bit = 1  
Ac-  
cess  
SF  
De- Hex  
fault  
18.15 Remote Jabber  
Detect  
No Remote Jabber  
Condition detected  
Remote Jabber Condition  
Detected  
RO  
LH  
0
–
18.14 Polarity reversed  
18.13 ICS reserved  
18.12 ICS reserved  
18.11 ICS reserved  
18.10 ICS reserved  
Normal polarity  
Polarity reversed  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Jabber Check disabled  
Read unspecified  
RO  
LH  
–
0
–
–
–
–
–
–
–
–
0
1
0
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Normal Jabber behavior  
Read unspecified  
RW/0  
RW/0  
RW/0  
RW/0  
RW/0  
RW/0  
RW/0  
RW/0  
RW  
–
–
–
–
0
–
18.9  
18.8  
18.7  
18.6  
18.5  
18.4  
18.3  
ICS reserved  
ICS reserved  
ICS reserved  
ICS reserved  
Jabber inhibit  
ICS reserved  
–
–
–
–
–
RW/1  
RW  
–
Auto polarity inhibit Polarity automatically  
corrected  
Polarity not automatically  
corrected  
–
18.2  
18.1  
18.0  
SQE test inhibit  
Link Loss inhibit  
Squelch inhibit  
Normal SQE test behavior SQE test disabled  
RW  
RW  
RW  
–
–
–
0
0
0
Normal Link Loss behavior Link Always = Link Pass  
Normal squelch behavior  
No squelch  
8.13.1 Remote Jabber Detect (bit 18.15)  
The Remote Jabber Detect bit is provided to indicate that an ICS1893 port has detected a Jabber Condition  
on its receive path. This bit is reset to logic zero on a read of the 10Base-T operations register. When this  
bit is logic:  
• Zero, it indicates a Jabber Condition has not occurred on the port’s receive path since either the last read  
of this register or the last reset of the associated port.  
• One, it indicates a Jabber Condition has occurred on the port’s receive path since either the last read of  
this register or the last reset of the associated port.  
This bit is a latching high bit. (For more information on latching high and latching low bits, see Section  
8.1.4.1, “Latching High Bits” and Section 8.1.4.2, “Latching Low Bits”.)  
Note: This bit is provided for information purposes only (that is, no actions are taken by the port). The  
ISO/IEC specification defines the Jabber Condition in terms of a port’s transmit path. To set this bit,  
an ICS1893 port monitors its receive path and applies the ISO/IEC Jabber criteria to its receive  
path.  
8.13.2 Polarity Reversed (bit 18.14)  
The Polarity Reversed bit is used to inform an STA whether the ICS1893 has detected that the signals on  
the Twisted-Pair Receive Pins (TP_RXP and TP_RXN) are reversed. When the signal polarity is:  
• Correct, the ICS1893 sets bit 18.14 to a logic zero.  
• Reversed, the ICS1893 sets bit 18.14 to logic one.  
Note: The ICS1893 can detect this situation and perform all its operations normally, independent of the  
reversal.  
8.13.3 ICS Reserved (bits 18.13:6)  
See Section 8.11.2, “ICS Reserved (bits 16.14:11)”, the text for which also applies here.  
8.13.4 Jabber Inhibit (bit 18.5)  
The Jabber Inhibit bit allows an STA to disable Jabber Detection. When an STA sets this bit to:  
• Zero, the ICS1893 enables 10Base-T Jabber checking.  
• One, the ICS1893 disables its check for a Jabber condition during data transmission.  
8.13.5 ICS Reserved (bit 18.4)  
See Section 8.11.2, “ICS Reserved (bits 16.14:11)”, the text for which also applies here.  
8.13.6 Auto Polarity Inhibit (bit 18.3)  
The Auto Polarity Inhibit bit allows an STA to prevent the automatic correction of a polarity reversal on the  
Twisted-Pair Receive pins (TP_RXP and TP_RXN). If an STA sets this bit to logic:  
• Zero (the default), the ICS1893 automatically corrects a polarity reversal on the Twisted-Pair Receive  
pins.  
• One, the ICS1893 either disables or inhibits the automatic correction of reversed Twisted-Pair Receive  
pins.  
Note: This bit is also used to correct a reversed signal polarity for 100Base-TX operations.  
8.13.7 SQE Test Inhibit (bit 18.2)  
The SQE Test Inhibit bit allows an STA to prevent the generation of the Signal Quality Error pulse. When  
an STA sets this bit to logic:  
• Zero, the ICS1893 enables its SQE Test generation.  
• One, the ICS1893 disables its SQE Test generation.  
The SQE Test provides the ability to verify that the Collision Logic is active and functional. A 10Base-T  
SQE test is performed by pulsing the Collision signal for a short time after each packet transmission  
completes, that is, after TXEN goes inactive.  
Note:  
1. The SQE Test is automatically inhibited in full-duplex and repeater modes, thereby disabling the  
functionality of this bit.  
2. This bit is a control bit and not a status bit. Therefore, it is not updated to indicate this automatic  
inhibiting of the SQE test in full-duplex mode or repeater mode.  
8.13.8 Link Loss Inhibit (bit 18.1)  
The Link Loss Inhibit bit allows an STA to prevent the ICS1893 from dropping the link in 10Base-T mode.  
When an STA sets this bit to logic:  
• Zero, the state machine behaves normally and the link status is based on the signaling detected Twisted-  
Pair Receiver inputs.  
• One, the ICS1893 10Base-T Link Integrity Test state machine is forced into the ‘Link Passed’ state  
regardless of the Twisted-Pair Receiver input conditions.  
8.13.9 Squelch Inhibit (bit 18.0)  
The Squelch Inhibit bit allows an STA to control the ICS1893 Squelch Detection in 10Base-T mode. When  
an STA sets this bit to logic:  
• Zero, before the ICS1893 can establish a valid link, the ICS1893 must receive valid 10Base-T data.  
• One, before the ICS1893 can establish a valid link, the ICS1893 must receive both valid 10Base-T data  
followed by an IDL.  
8.14 Register 19: Extended Control Register 2  
The Extended Control Register provides more refined control of the internal ICS1893 operations.  
Note:  
1. For an explanation of acronyms used in Table 8-20, see Chapter 1, “Abbreviations and Acronyms”.  
2. During any write operation to any bit in this register, the STA must write the default value to all  
Reserved bits.  
Table 8-21. Extended Control Register (register [0x13])  
Bit  
Definition  
When Bit = 0  
When Bit = 1  
Repeater mode  
Software mode  
Ac-  
cess  
SF  
–
De-  
fault  
Hex  
19.15 Node/Repeater Mode  
Node mode  
RO  
RO  
RO  
NOD/  
REP†  
–
19.14 Hardware/Software  
Mode  
Hardware mode  
–
HW/  
SW†  
19.13 Remote Fault  
No faults detected  
Remote fault  
detected  
–
0
19.12 ICS reserved  
19.11 ICS reserved  
19.10 ICS reserved  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
RW  
RW  
RO  
RW  
RW  
RW  
–
–
–
–
–
–
0
0
0
0
0
0
0
0
19.9  
19.8  
19.7  
ICS reserved  
ICS reserved  
Twisted Pair Tri-State  
Enable, TPTRI  
Twisted Pair Signals Twisted Pair Signals  
are not Tri-Stated or  
No effect  
are Tri-Stated  
19.6  
19.5  
19.4  
19.3  
19.2  
19.1  
19.0  
ICS reserved  
Force LEDs On  
ICS reserved  
ICS reserved  
ICS reserved  
ICS reserved  
Read unspecified  
No effect  
Read unspecified  
Force all LEDs on  
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
RW  
RW  
RW  
RW  
RW  
RW  
RW  
–
–
–
–
–
–
–
0
0
0
0
0
0
1
Read unspecified  
Read unspecified  
Read unspecified  
Read unspecified  
1
Automatic 100Base-TX  
Power Down  
Do not automatically Power down  
power down automatically  
† The default is the state of this pin at reset.  
8.14.1 Node/Repeater Configuration (bit 19.15)  
The Node/Repeater Configuration bit directly indicates the state of the NOD/REP input pin. When this bit is  
logic:  
• Zero, the NOD/REP input pin is pulled down, which instructs the operation code to operate in Node  
mode.  
• One, the NOD/REP input pin is pulled up, which instructs the ICS1893 to operate in Repeater mode.  
There are two primary differences between Node mode and Repeater mode.  
• In Node mode:  
– The SQE Test default setting is enabled.  
– The Carrier Sense signal (CRS) is asserted in response to either transmit or receive activity.  
• In Repeater mode:  
– The SQE Test default setting is disabled.  
– The Carrier Sense signal (CRS) is asserted in response only to receive activity.  
8.14.2 Hardware/Software Priority Status (bit 19.14)  
The Hardware/Software Priority Status bit directly indicates the state of the HW/SW pin. When this bit is  
logic:  
• Zero, the hardware pins have priority over the (software) register bits for establishing the ICS1893  
configuration.  
• One, the (software) register bits have priority over the hardware pins for establishing the ICS1893  
configuration.  
8.14.3 Remote Fault (bit 19.13)  
The ISO/IEC specification defines bit 5.13 as the Remote Fault bit, and bit 19.13 is functionally identical to  
bit 5.13. The Remote Fault bit is set based on the Link Control Word received from the remote link partner.  
When this bit is a logic:  
• Zero, it indicates the remote link partner does not detect a Link Fault.  
• One, it indicates to an STA that the remote link partner detects a Link Fault.  
8.14.4 ICS Reserved (bits 19.12:8)  
See Section 8.11.2, “ICS Reserved (bits 16.14:11)”, the text for which also applies here.  
8.14.5 Twisted Pair Tri-State Enable, TPTRI (bit 19.7)  
The ICS1893 provides a Twisted Pair Tri-State Enable bit. This bit forces the TP_TXP and TP_TXN signals  
to a high-impedance state. When this bit is set to logic:  
• Zero, the Twisted Pair Interface is operational.  
• One, the Twisted Pair Interface is tri-stated.  
8.14.6 ICS Reserved (bits 19.12:6)  
See Section 8.11.2, “ICS Reserved (bits 16.14:11)”, the text for which also applies here.  
8.14.7 Force LEDs On (bit 19.5)  
Each ICS1893 provides a Force LEDs On bit as a diagnostic function. This bit overrides the normal  
operation of the LEDs and forces them on. When this bit is set to logic:  
• Zero, the normal operation of all ICS1893 LEDs is unaffected.  
• One, all ICS1893 LEDs forced on.  
Note: The ‘on’ state of the LEDs driven from multi-function configuration pins is determined after the pin  
is sampled.  
8.14.8 ICS Reserved (bits 19.4:1)  
See Section 8.11.2, “ICS Reserved (bits 16.14:11)”, the text for which also applies here.  
8.14.9 Automatic 100Base-TX Power-Down (bit 19.0)  
The Automatic 100Base-TX Power Down bit provides an STA with the means of enabling the ICS1893 to  
automatically shut down 100Base-TX support functions when 10Base-T operations are being used. When  
this bit is set to logic:  
• Zero, the 100Base-TX Transceiver does not power down automatically in 100Base-TX mode.  
• One, and the ICS1893 is operating in 10Base-T mode, the 100Base-TX Transceiver automatically turns  
off to reduce the overall power consumption of the ICS1893.  
Note: There are other means of powering down the 100Base-TX Transceiver (for example, when the  
entire device is isolated using bit 0:10).  
Chapter 9 Pin Diagram, Listings, and Descriptions  
9.1 ICS1893 Pin Diagram  
NOD/REP  
10/100SEL  
TP_CT  
VSS  
1
2
48  
47  
46  
45  
44  
43  
42  
41  
40  
39  
38  
37  
36  
35  
34  
33  
TXD3  
TXD2  
TXD1  
TXD0  
TXEN  
TXCLK  
TXER  
RXTRI  
VSS  
3
4
TP_TXP  
TP_TXN  
VDD  
5
6
7
VDD  
8
ICS1893  
10TCSR  
100TCSR  
VSS  
9
10  
11  
12  
13  
14  
15  
16  
RXER  
RXCLK  
VDD_IO  
RXDV  
RXD0  
RXD1  
RXD2  
VSS  
TP_RXP  
TP_RXN  
VDD  
VDD  
9.2 ICS1893 Pin Listings  
Table 9-1 lists the ICS1893 pins by pin number.  
Table 9-1. ICS1893 Pins, by Pin Number  
Pin Pin Name  
No.  
Pin Pin Name  
No.  
Pin Pin Name  
No.  
Pin Pin Name  
No.  
1
NOD/REP  
10/100SEL  
TP_CT  
VSS  
17  
18  
19  
20  
21  
22  
23  
24  
25  
26  
27  
28  
29  
30  
31  
32  
VSS  
33  
34  
35  
36  
37  
38  
39  
40  
41  
42  
43  
44  
45  
46  
47  
48  
RXD2  
RXD1  
RXD0  
RXDV  
VDD_IO  
RXCLK  
RXER  
VSS  
49  
50  
51  
52  
53  
54  
55  
56  
57  
58  
59  
60  
61  
62  
63  
64  
COL  
2
RESETn  
MII/SI  
NC  
CRS  
3
VDD_IO  
REF_OUT  
REF_IN  
VDD  
4
5
TP_TXP  
TP_TXN  
VDD  
LSTA  
VSS  
6
7
HW/SW  
DPXSEL  
VDD  
P0AC  
VSS  
8
VDD  
9
10TCSR  
100TCSR  
VSS  
RXTRI  
TXER  
TXCLK  
TXEN  
TXD0  
TXD1  
TXD2  
TXD3  
VSS  
10  
11  
12  
13  
14  
15  
16  
ANSEL  
LOCK  
VSS  
VSS  
P1CL  
P2LI  
VSS  
TP_RXP  
TP_RXN  
VDD  
VSS  
VSS  
MDIO  
MDC  
P3TD  
VDD  
VDD  
RXD3  
P4RD  
9.3 ICS1893 Pin Descriptions  
The tables in this section list the ICS1893 pins by their functional grouping.  
9.3.1 Transformer Interface Pins  
Table 9-2 lists the pins for the transformer interface group of pins.  
Table 9-2. Transformer Interface Pins  
Pin  
Pin  
Pin  
Pin Description  
Name  
Number  
Type  
TP_RXN  
14  
Input  
Twisted-Pair Receive (Data) Negative.  
Within this table, see the description at the TP_RXP pin.  
TP_RXP  
13  
Input  
Twisted-Pair Receive (Data) Positive.  
Data reception of differential analog signals occurs over the TP_RXN  
and TP_RXP pair of differential-signal pins. Together these pins  
receive the serial bit stream from the UTP cable through an isolation  
transformer.  
Depending on the operating mode of the remote link partner, the  
received data is one of the following types of signals:  
• Two-level 10Base-T (that is, Manchester-encoded) signals  
• Three-level 100Base-TX, (that is, MLT-3 encoded) signals  
The TP_RXN and TP_RXP pins interface directly to an isolation  
transformer, which in turn, interfaces with the UTP cable.  
TP_TXN  
TP_TXP  
6
5
Output Twisted-Pair Transmit (Data) Negative.  
Within this table, see the description at the TP_TXP pin.  
Output Twisted-Pair Transmit (Data) Positive.  
Differential analog signal transmission occurs over the TP_TXN and  
TP_TXP pair of pins. Together these pins drive the serial bit stream  
over the UTP cable.  
Depending on the operating mode of the ICS1893 MDI, the  
current-driven differential driver produces one of the following types of  
signals:  
• Two-level 10Base-T (that is, Manchester-encoded) signals  
• Three-level 100Base-T (that is, MLT-3 encoded) signals  
The TP_RXN and TP_RXP pins interface directly to an isolation  
transformer, which in turn, drives the UTP cable.  
9.3.2 Multi-Function (Multiplexed) Pins: PHY Address and LED Pins  
Table 9-3 lists the pins for the multi-function group of pins (that is, the multiplexed PHY Address / LED  
pins).  
Note:  
1. During either a power-on reset or a hardware reset, each multi-function configuration pin is an input  
that is sampled when the ICS1893 exits the reset state. After sampling is complete, these pins are  
output pins that can drive status LEDs.  
2. A software reset does not affect the state of a multi-function configuration pin. During a software reset,  
all multi-function configuration pins are outputs.  
3. Each multi-function configuration pin must be pulled either up or down with a resistor to establish the  
address of the ICS1893. LEDs placed in series with these resistors provide a designated status  
indicator.  
Caution: All pins listed in Table 9-3 must not float.  
4. As outputs, the asserted state of a multi-function configuration pin is the inverse of the sense sampled  
during reset. This inversion provides a signal that can illuminate an LED during an asserted state. For  
example, if a multi-function configuration pin is pulled down to ground through an LED and a  
current-limiting resistor, then the sampled sense of the input is low. To illuminate an LED for the  
asserted state requires the output to be high.  
Note: Each of these pins monitor the data link by providing signals that directly drive LEDs.  
Table 9-3. PHY Address and LED Pins  
Pin  
Pin  
Pin  
Pin Description  
Name Number  
Type  
P0AC  
55  
Input or PHY (Address Bit) 0 / Activity LED.  
Output For more information on this pin, see Section 6.8, “Status Interface”.  
• This multi-function configuration pin is:  
– An input pin during either a power-on reset or a hardware reset. In  
this case, this pin configures the ICS1893 when it is in either  
hardware mode or software mode.  
– An output pin following reset. In this case, this pin provides link status  
of the ICS1893.  
As an input pin:  
• This pin establishes the address for the ICS1893. When the signal on  
this pin is logic:  
– Low, that address bit is set to logic zero.  
– High, that address bit is set to logic one.  
As an output pin:  
• When the signal on this pin is:  
– De-asserted, this state indicates the ICS1893 does not have a link.  
– Asserted, this state indicates the ICS1893 has a valid link.  
Caution: This pin must not float. (See the notes at Section 9.3.2,  
“Multi-Function (Multiplexed) Pins: PHY Address and LED  
Pins”.)  
Table 9-3. PHY Address and LED Pins  
Pin  
Pin  
Pin  
Pin Description  
Name Number  
Type  
P1CL  
59  
Input or PHY (Address Bit) 1 / Collision LED.  
Output For more information on this pin, see Section 6.8, “Status Interface”.  
• This multi-function configuration pin is:  
– An input pin during either a power-on reset or a hardware reset. In  
this case, this pin configures the ICS1893 when it is in either  
hardware mode or software mode.  
– An output pin following reset. In this case, this pin provides collision  
status for the ICS1893.  
As an input pin:  
• This pin, in combination with the 10/100SEL pin, selects the operating  
modes of the ICS1893 MAC/repeater Interfaces, either 10M MII, 100M  
MII, 10M Serial, or 100M Symbol. When the signal on this pin is logic:  
– Low, the ICS1893 configures its MAC/repeater Interface as a Media  
Independent Interface.  
– High, the ICS1893 configures its MAC/repeater Interface as a  
Stream Interface (that is, either a 10M Serial Interface or a 100M  
Symbol Interface).  
As an output pin:  
• When the signal on this pin is:  
– De-asserted, this state indicates the ICS1893 does not detect any  
collisions.  
– Asserted, this state indicates the ICS1893 detects collisions.  
• The ICS1893 asserts its Collision LED for a period of approximately 70  
msec when it detects a collision.  
Caution: This pin must not float. (See the notes at Section 9.3.2,  
“Multi-Function (Multiplexed) Pins: PHY Address and LED  
Pins”.)  
Table 9-3. PHY Address and LED Pins  
Pin  
Pin  
Pin  
Pin Description  
Name Number  
Type  
P2LI  
60  
Input or PHY (Address Bit) 2 / Link Integrity LED.  
Output For more information on this pin, see Section 6.8, “Status Interface”.  
• This multi-function configuration pin is:  
– An input pin during either a power-on reset or a hardware reset. In  
this case, this pin configures the address of the ICS1893 when it is in  
either hardware mode or software mode.  
– An output pin following reset. In this case, this pin provides link status  
for the ICS1893.  
As an input pin:  
• This pins establishes the address for the ICS1893. When the signal on  
this pin is logic:  
– Low, that address bit is set to logic zero.  
– High, that address bit is set to logic one.  
As an output pin:  
• When the signal on this pin is:  
– De-asserted, this state indicates the ICS1893 does not have a link.  
– Asserted, this state indicates the ICS1893 has a valid link.  
Caution: This pin must not float. (See the notes at Section 9.3.2,  
“Multi-Function (Multiplexed) Pins: PHY Address and LED  
Pins”.)  
P3TD  
62  
Input or PHY (Address Bit) 3 / Transmit Data LED.  
Output For more information on this pin, see Section 6.8, “Status Interface”.  
• These multi-function configuration pins are:  
– Input pins during either a power-on reset or a hardware reset. In this  
case, these pins configure the address of the ICS1893 when it is in  
either hardware mode or software mode.  
– Output pins following reset. In this case, this pin provides link status  
for the ICS1893.  
As an input pin:  
• This pin establishes the address for the ICS1893. When the signal on  
one of these pins is logic:  
– Low, that address bit is set to logic zero.  
– High, that address bit is set to logic one.  
As an output pin:  
• When the signal on this pin is:  
– De-asserted, this state indicates the ICS1893 does not have a link.  
– Asserted, this state indicates the ICS1893 has a valid link.  
Caution: This pin must not float. (See the notes at Section 9.3.2,  
“Multi-Function (Multiplexed) Pins: PHY Address and LED  
Pins”.)  
Table 9-3. PHY Address and LED Pins  
Pin  
Pin  
Pin  
Pin Description  
Name Number  
Type  
P4RD  
64  
Input or PHY (Address Bit) 4 / Receive Data LED.  
Output For more information on this pin, see Section 6.8, “Status Interface”.  
The ‘Pin Type’ for this multiplexed pin depends on the where the ICS1893  
is in its reset cycle.  
• During a reset of the ICS1893, this pins acts as an input.  
• After a reset of the ICS1893, this pins latches the state of the inputs  
into their respective PHY Address bits. (See Table 8-16.) The ICS1893  
then converts the pin signal to an output that can drive the respective  
LED directly.  
Caution: This pin must not float. (See the notes at Section 9.3.2,  
“Multi-Function (Multiplexed) Pins: PHY Address and LED  
Pins”.)  
9.3.3 Configuration Pins  
Table 9-4 lists the configuration pins.  
Table 9-4. Configuration Pins  
Pin  
Pin  
Pin  
Pin Description  
Name  
Number  
Type  
10/100SEL  
2
Input or 10Base-T / 100Base-TX Select.  
Output The ‘Pin Type’ for this pin depends on the setting for the HW/SW pin  
(pin 23). When the HW/SW pin is set for:  
• Hardware mode, this pin acts as an input. In this case, when the  
signal on this pin is logic:  
– Low, this pin selects 10Base-T operations.  
– High, this pin selects 100Base-TX operations.  
• Software mode, this pin acts as an output that indicates the current  
status of this pin. In this case, when the signal on this pin is logic:  
– Low, this pin indicates 10Base-T operations are selected.  
– High, this pin indicates 100Base-TX operations are selected.  
10TCSR  
9
Input  
Input  
10M Transmit Current Set Resistor.  
• A resistor, connected between this pin and ground, is required to  
establish the value of the transmit current used in 10Base-T mode.  
• The value and tolerance of this resistor is specified in Section 10.3,  
“Recommended Component Values”.  
100TCSR  
10  
100M Transmit Current Set Resistor.  
• A resistor, connected between this pin and ground, is required to  
establish the value of the transmit current used in 100Base-TX  
mode.  
• The value and tolerance of this resistor is specified in Section 10.3,  
“Recommended Component Values”.  
ANSEL  
26  
Input or Auto-Negotiation Select.  
Output The ‘Pin Type’ for this pin depends on the setting for the HW/SW pin  
(pin 23). When the HW/SW pin is set for:  
• Hardware mode, this pin acts as an input. In this case, when the  
signal on this pin is logic:  
– Low, this pin does not select Auto-Negotiation operations.  
– High, this pin selects Auto-Negotiation operations.  
• Software mode, this pin acts as an output that indicates the current  
status of this pin. In this case, when the signal on this pin is logic:  
– Low, this pin indicates that Auto-Negotiation is disabled.  
– High, this pin indicates that Auto-Negotiation is enabled.  
DPXSEL  
24  
Input or Half-Duplex / Full-Duplex Select.  
Output The ‘Pin Type’ for this pin depends on the setting for the HW/SW pin  
(pin 23). When the HW/SW pin is set for:  
• Hardware mode, this pin acts as an input. In this case, when the  
signal on this pin is logic:  
– Low, this pin selects half-duplex operations.  
– High, this pin selects full-duplex operations.  
• Software mode, this pin acts as an output that indicates the current  
status of this pin. In this case, when the signal on this pin is logic:  
– Low, this pin indicates that it is set for half-duplex operations.  
– High, this pin indicates that it is set for full-duplex operations.  
Table 9-4. Configuration Pins (Continued)  
Pin  
Pin  
Pin  
Pin Description  
Name  
Number  
Type  
HW/SW  
LOCK  
LSTA  
23  
27  
21  
Input  
Hardware/Software (Select).  
When the signal on this pin is logic:  
• Low, this pin selects Hardware mode operations.  
• High, this pin selects Software mode operations.  
Output (Stream Cipher) Lock (Acquired).  
When the signal on this pin is logic:  
• Low, the ICS1893 does not have a lock on the data stream.  
• High, the ICS1893 has a lock on the data stream.  
Output Link Status.  
This pin is used to report the status of the link segment. When the  
signal on this pin is logic:  
• Low, there is no link established.  
• High, there is a link established.  
This pin is mapped according to the interface for which the ICS1893 is  
mapped. For the:  
• Media Independent Interface (MII), the LSTA is mapped as LSTA.  
• 100M Symbol Interface, the LSTA is mapped as SD.  
• 10M Serial Interface, the LSTA is mapped as LSTA.  
• Link Pulse Interface, the LSTA is mapped as SD.  
MII/SI  
19  
Input  
Media Independent Interface / Stream Interface (Select).  
This pin is used in combination with the 10/LP and 10/100SEL pins to  
configure the ICS1893 MAC/Repeater Interface. When the signal on  
this pin is logic:  
• Low, this pin configures the MAC/Repeater Interface as a Media  
Independent Interface.  
• High, this pin configures the MAC/Repeater Interface as a Stream  
Interface.  
NOD/REP  
REF_IN  
1
Input  
Input  
Node/Repeater (Select).  
This selection on this pin affects both the SQE test and the Carrier  
Sense (CSR) signal. When the signal on this pin is logic:  
• Low, this pin enables the ICS1893 to default to node operations.  
• High, this pin enables the ICS1893 to default to repeater  
operations.  
53  
(Frequency) Reference Input.  
This pin is connected to a 25-MHz oscillator. For a tolerance, see  
Section 10.5.1, “Timing for Clock Reference In (REF_IN) Pin”.  
REF_OUT  
RESETn  
52  
18  
Input  
Input  
(Frequency) Reference Output.  
This pin is eserved and must be left unconnected.  
(System) Reset (Active Low).  
• When the signal on this active-low pin is logic:  
– Low, the ICS1893 is in hardware reset.  
– High, the ICS1893 is operational.  
• For more information on hardware resets, see the following:  
– Section 5.1.2.1, “Hardware Reset”  
– Section 10.5.18, “Reset: Hardware Reset and Power-Down”  
9.3.4 MAC/Repeater Interface Pins  
This section lists pin descriptions for each of the following interfaces  
• Section 9.3.4.1, “MAC/Repeater Interface Pins for Media Independent Interface”  
• Section 9.3.4.2, “MAC/Repeater Interface Pins for 100M Symbol Interface”  
• Section 9.3.4.3, “MAC/Repeater Interface Pins for 10M Serial Interface”  
9.3.4.1 MAC/Repeater Interface Pins for Media Independent Interface  
Table 9-5 lists the MAC/Repeater Interface pin descriptions for the MII.  
Table 9-5. MAC/Repeater Interface Pins: Media Independent Interface (MII)  
Pin  
Pin  
Pin  
Pin Description  
Name Number  
Type  
COL  
49  
Output Collision (Detect).  
The ICS1893 asserts a signal on the COL pin when the ICS1893 detects  
receive activity while transmitting (that is, while the TXEN signal is  
asserted by the MAC/repeater, that is, when transmitting). When the  
mode is:  
• 10Base-T, the ICS1893 detects receive activity by monitoring the  
un-squelched MDI receive signal.  
• 100Base-TX, the ICS1893 detects receive activity when there are two  
non-contiguous zeros in any 10-bit symbol derived from the MDI  
receive data stream.  
Note:  
1. The signal on the COL pin is not synchronous to either RXCLK or  
TXCLK.  
2. In full-duplex mode, the COL signal is disabled and always remains  
low.  
3. The COL signal is asserted as part of the signal quality error (SQE)  
test. This assertion can be suppressed with the SQE Test Inhibit bit  
(bit 18.2).  
CRS  
50  
31  
Output Carrier Sense.  
When the ICS1893 mode is:  
• Half-duplex, the ICS1893 asserts a signal on its CRS pin when it  
detects either receive or transmit activity.  
• Either full-duplex or Repeater mode, the ICS1893 asserts a signal on  
its CRS pin only in response to receive activity.  
Note: The signal on the CRS pin is not synchronous to the signal on  
either the RXCLK or TXCLK pin.  
MDC  
Input  
Management Data Clock.  
The ICS1893 uses the signal on the MDC pin to synchronize the transfer  
of management information between the ICS1893 and the Station  
Management Entity (STA), using the serial MDIO data line. The MDC  
signal is sourced by the STA.  
Table 9-5. MAC/Repeater Interface Pins: Media Independent Interface (MII) (Continued)  
Pin  
Pin  
Pin  
Type  
Pin Description  
Management Data Input/Output.  
Name Number  
MDIO  
30  
Input/  
Output The signal on this pin can be tri-stated and can be driven by one of the  
following:  
• A Station Management Entity (STA), to transfer command and data  
information to the registers of the ICS1893.  
• The ICS1893, to transfer status information.  
All transfers and sampling are synchronous with the signal on the MDC  
pin.  
Note: If the ICS1893 is to be used in an application that uses the  
mechanical MII specification, MDIO must have a 1.5 kW ±5%  
pull-up resistor at the ICS1893 end and a 2 kW ±5% pull-down  
resistor at the station management end. (These resistors enable  
the station management to determine if the connection is intact.)  
RXCLK  
38  
Output Receive Clock.  
The ICS1893 sources the RXCLK to the MAC/repeater interface. The  
ICS1893 uses RXCLK to synchronize the signals on the following pins:  
RXD[3:0], RXDV, and RXER. The following table contrasts the behavior  
on the RXCLK pin when the mode for the ICS1893 is either 10Base-T or  
100Base-TX.  
10Base-T  
100Base-TX  
The RXCLK frequency is 2.5  
MHz.  
The RXCLK frequency is 25 MHz.  
The ICS1893 generates its  
The ICS1893 generates its  
RXCLK from the MDI data stream RXCLK from the MDI data stream  
using a digital PLL. When the MDI while there is a valid link (that is,  
data stream terminates, the PLL  
continues to operate,  
synchronously referenced to the  
last packet received.  
either data or IDLEs). In the  
absence of a link, the ICS1893  
uses the REF_IN clock to  
generate the RXCLK.  
The ICS1893 switches between  
clock sources during the period  
between when its CRS is  
asserted and prior to its RXDV  
being asserted. While the  
ICS1893 is locking onto the  
incoming data stream, a clock  
phase change of up to 360  
degrees can occur.  
While the ICS1893 is bringing up  
a link, a clock phase change of up  
to 360 degrees can occur.  
The RXCLK aligns once per  
packet.  
The RXCLK aligns once, when  
the link is being established.  
Note: The signal on the RXCLK pin is conditioned by the RXTRI pin.  
Table 9-5. MAC/Repeater Interface Pins: Media Independent Interface (MII) (Continued)  
Pin  
Pin  
Pin  
Pin Description  
Name Number  
Type  
RXD0,  
RXD1,  
RXD2,  
RXD3  
35,  
34,  
33,  
32  
Output Receive Data 0–3.  
• RXD0 is the least-significant bit and RXD3 is the most-significant bit of  
the MII receive data nibble.  
• While the ICS1893 asserts RXDV, the ICS1893 transfers the receive  
data signals on the RXD0–RXD3 pins to the MAC/Repeater Interface  
synchronously on the rising edges of RXCLK.  
RXDV  
36  
Output Receive Data Valid.  
The ICS1893 asserts RXDV to indicate to the MAC/repeater that data is  
available on the MII Receive Bus (RXD[3:0]). The ICS1893:  
• Asserts RXDV after it detects and recovers the Start-of-Stream  
delimiter, /J/K/. (For the timing reference, see Chapter 10.5.6, “MII /  
100M Stream Interface: Synchronous Receive Timing”.)  
• De-asserts RXDV after it detects either the End-of-Stream delimiter  
(/T/R/) or a signal error.  
Note: RXDV is synchronous with the Receive Data Clock, RXCLK.  
RXER  
39  
Output Receive Error.  
When the MAC/Repeater Interface is in:  
• 10M MII mode, RXER is not used.  
• 100M MII mode, the ICS1893 asserts a signal on the RXER pin when  
either of the following two conditions are true:  
– Errors are detected during the reception of valid frames  
– A False Carrier is detected  
Note:  
1. An ICS1893 asserts a signal on the RXER pin upon detection of a  
False Carrier so that repeater applications can prevent the  
propagation of a False Carrier.  
2. The RXER signal always transitions synchronously with RXCLK.  
3. The signal on RXER pin is conditioned by the RXTRI pin.  
RXTRI  
TXCLK  
41  
43  
Input  
Receive (Interface), Tri-State.  
The input on this pin is from a MAC. When the signal on this pin is logic:  
• Low, the MAC indicates that it is not in a tri-state condition.  
• High, the MAC indicates that it is in a tri-state condition. In this case,  
the ICS1893 acts to ensure that only one PHY is active at a time.  
Output Transmit Clock.  
The ICS1893 generates this clock signal to synchronize the transfer of  
data from the MAC/Repeater Interface to the ICS1893. When the mode is:  
• 10Base-T, the TXCLK frequency is 2.5 MHz.  
• 100Base-TX, the TXCLK frequency is 25 MHz.  
TXD0,  
TXD1,  
TXD2,  
TXD3  
45,  
46,  
47,  
48  
Input  
Transmit Data 0–3.  
• TXD0 is the least-significant bit and TXD3 is the most-significant bit of  
the MII transmit data nibble received from the MAC/repeater.  
• The ICS1893 samples its TXEN signal to determine when data is  
available for transmission. When TXEN is asserted, the signals on a  
the TXD[3:0] pins are sampled synchronously on the rising edges of  
the TXCLK signal.  
Table 9-5. MAC/Repeater Interface Pins: Media Independent Interface (MII) (Continued)  
Pin  
Pin  
Pin  
Pin Description  
Name Number  
Type  
TXEN 44  
Input  
Transmit Enable.  
In MII mode:  
• The ICS1893 samples its TXEN signal to determine when data is  
available for transmission. When TXEN is asserted, the ICS1893  
begins sampling the data nibbles on the transmit data lines TXD[3:0]  
synchronously with TXCLK. The ICS1893 then transmits this data over  
the media.  
• Following the de-assertion of TXEN, the ICS1893 terminates  
transmission of nibbles over the media.  
TXER  
42  
Input  
Transmit Error.  
When the MAC/Repeater Interface is in:  
• 10M MII mode, TXER is not used.  
• 100M MII mode:  
– The ICS1893 synchronously samples its TXER signal on the rising  
edges of its TXCLK signal.  
– The assertion of TXER by the MAC/repeater causes the ICS1893 to  
transmit an Invalid Symbol.  
– the Invalid Error Code Test bit (bit 16.2) is set to logic one, the 5-bit  
symbol shown in the Invalid Error Code Translation Table (Table  
8-17) is used instead of the normal 4B/5B encoding described in the  
ISO/IEC specification.  
Note: The Invalid Symbol used for this function is the HALT symbol,  
which is substituted for the transmit nibble received from the  
MAC/repeater whenever the TXER is asserted.  
9.3.4.2 MAC/Repeater Interface Pins for 100M Symbol Interface  
Table 9-6 lists the MAC/Repeater Interface pin descriptions for the 100M Symbol Interface.  
Table 9-6. MAC/Repeater Interface Pins: 100M Symbol Interface  
MII Pin  
Name  
100M  
Symbol  
Pin  
Pin  
No.  
Pin  
Type  
Pin Description  
Name  
COL  
–
49  
No  
Collision (Detect).  
Connect For the 100M Symbol Interface, this pin is a no connect. For  
more information, see Table 6-1.  
CRS  
SCRS  
MDC  
50  
31  
30  
Output Symbol Carrier Sense.  
This pin’s description is the same as that given in Table 9-5.  
MDC  
MDIO  
Input  
Management Data Clock.  
This pin’s description is the same as that given in Table 9-5.  
MDIO  
Input/  
Management Data Input/Output.  
Output This pin’s description is the same as that given in Table 9-5.  
Table 9-6. MAC/Repeater Interface Pins: 100M Symbol Interface (Continued)  
MII Pin  
Name  
100M  
Symbol  
Pin  
Pin  
No.  
Pin  
Type  
Pin Description  
Name  
RXCLK  
SRCLK  
38  
Output (Symbol) Receive Clock.  
In Symbol Mode, the ICS1893 sources an SRCLK to a  
MAC/repeater. The SRCLK synchronizes the signals on the  
SRD[4:0] pins between the ICS1893 and the MAC/repeater.  
The following table contrasts the SRCLK behavior when the  
mode for the ICS1893 is either 10Base-T or 100Base-TX.  
10Base-T  
100Base-TX  
The SRCLK frequency is  
2.5 MHz.  
The SRCLK frequency is  
25 MHz.  
The ICS1893 generates its The ICS1893 generates its  
SRCLK from the MDI data SRCLK from the MDI data  
stream using a digital PLL. stream while there is a  
When the MDI data stream valid link (that is, either  
terminates the PLL  
continues to operate,  
data or IDLEs). In the  
absence of a link, the  
synchronously referenced ICS1893 uses the REF_IN  
to the last packet received. clock to generate the  
SRCLK.  
The ICS1893 switches  
between clock sources  
While the ICS1893 is  
bringing up a link, a clock  
during the period between phase change of up to 360  
when its SCRS is asserted degrees can occur.  
and prior to its RXDV being  
asserted. While the  
ICS1893 is locking onto  
the incoming data stream,  
a clock phase change of  
up to 360 degrees can  
occur.  
The RXCLK aligns once  
per packet.  
The RXCLK aligns once,  
when the link is being  
established.  
Note: The signal on the SRCLK pin is conditioned by the  
RXTRI pin.  
Table 9-6. MAC/Repeater Interface Pins: 100M Symbol Interface (Continued)  
MII Pin  
Name  
100M  
Symbol  
Pin  
Pin  
No.  
Pin  
Type  
Pin Description  
Name  
RXD0,  
RXD1,  
RXD2,  
RXD3  
SRD0,  
SRD1,  
SRD2,  
SRD3  
35,  
34,  
33,  
32  
Output Symbol Receive Data 0–3.  
In 100M Symbol mode:  
• The ICS1893’s SRD0 pin transmits the least-significant bit  
and the SRD4 pin transmits the most-significant bit of the  
symbol received from its MAC/Repeater interface.  
• The ICS1893 continually transfers the data it receives from  
its MDI to its SRD[4:0] pins (that is, to its MAC/Repeater  
Interface). In the 100M Symbol mode, data is not framed.  
Therefore, the ICS1893 does not assert its RXDV signal.  
• The ICS1893 transfers its receive data to the SRD[4:0] pins  
synchronously on the rising edges of its SRCLK signal.  
Note: The signal on the ICS1893’s SRD[3:0] pins are  
conditioned by the RXTRI pin.  
RXDV  
–
36  
No  
Receive Data Valid.  
Connect For the 100M Symbol Interface, this pin is a no connect. For  
more information, see Table 6-1.  
RXER  
RXTRI  
SRD4  
39  
41  
Output Symbol Receive Data 4.  
This pin’s description is the same as that given in Table 9-5.  
Input  
Receive (Interface), Tri-State.  
This pin’s input is from a MAC. When this pin’s signal is logic:  
• Low, the MAC indicates it is not in a tri-state condition.  
• High, the MAC indicates it is in a tri-state condition. In this  
case, the ICS1893 acts to ensure that only one PHY is active  
at a time. (A PHY address of 00 also tri-states the MII  
interface.)  
TXCLK  
STCLK  
43  
Output Symbol Transmit Clock.  
This pin’s description is the same as that given in Table 9-5.  
TXD0–3 STD0,  
STD1,  
45,  
46,  
47,  
48  
Input  
Symbol Transmit Data 0–3.  
In 100M Symbol mode:  
• The ICS1893 STD0 pin receives the least-significant bit and  
the STD4 pin receives the most-significant bit of the symbol  
received from the MAC/Repeater interface.  
STD2,  
STD3  
• The signals on the ICS1893 STD[4:0] pins are continually  
and synchronously sampled on the rising edges of its  
STCLK. These signals are independent of the TXEN signal.  
Note: In 100M Symbol mode, TXEN is not used because the  
MAC/Repeater is responsible for sending both IDLE  
symbols and data.  
TXEN  
TXER  
–
44  
42  
No  
Transmit Enable.  
Connect For the 100M Symbol Interface, this pin is a no connect. For  
more information, see Table 6-1.  
STD4  
Input  
Symbol Transmit Data 4.  
This pin’s description is the same as that given in Table 9-5.  
9.3.4.3 MAC/Repeater Interface Pins for 10M Serial Interface  
Table 9-7 lists the MAC/Repeater Interface pin descriptions for the 10M Serial Interface.  
Table 9-7. MAC/Repeater Interface Pins: 10M Serial Interface  
MII Pin  
Name  
100M  
Symbol  
Pin  
Pin  
No.  
Pin  
Type  
Pin Description  
Name  
COL  
10COL  
10CRS  
MDC  
49  
50  
31  
30  
38  
Output 10M (Serial Interface) Collision (Detect).  
This pin’s description is the same as that given in Table 9-5.  
CRS  
Output 10M (Serial Interface) Carrier Sense.  
This pin’s description is the same as that given in Table 9-5.  
MDC  
MDIO  
RXCLK  
Input  
Management Data Clock.  
This pin’s description is the same as that given in Table 9-5.  
MDIO  
Input/  
Management Data Input/Output.  
Output This pin’s description is the same as that given in Table 9-5.  
10RCLK  
Output 10M Receive Clock.  
In 10M Serial mode, the ICS1893 sources the 10RCLK to its  
MAC/repeater Interface. The 10RCLK synchronizes the data on  
the 10RD0 pin between the ICS1893 and the MAC/repeater.  
• The 10RCLK frequency is 10 MHz.  
• The ICS1893 generates 10RCLK from the MDI data stream  
using a digital PLL. When the MDI data stream terminates,  
the PLL continues to operate, synchronously referenced to  
the last packet received.  
• The ICS1893 switches between clock sources during the  
period between when 10CRS is being asserted and  
10RXDV is being asserted. While the ICS1893 locks onto  
the incoming data stream, a clock phase change of up to 360  
degrees can occur.  
• The 10RCLK aligns once per packet.  
Note: The signal on the 10RCLK pin is conditioned by the  
RXTRI pin.  
RXD0  
10RD  
–
35  
10M (Serial Interface) Receive Data 0.  
This pin’s description is the same as that given in Table 9-5.  
RXD1,  
RXD2,  
RXD3  
34,  
33,  
32  
No  
Receive Data 1–3.  
Connect For the 10M Serial Interface, these pins are a no connect. For  
more information, see Table 6-2.  
Table 9-7. MAC/Repeater Interface Pins: 10M Serial Interface (Continued)  
MII Pin  
Name  
100M  
Symbol  
Pin  
Pin  
No.  
Pin  
Type  
Pin Description  
Name  
RXDV  
10RXDV  
36  
Output 10M (Serial Interface) Receive Data Valid.  
The ICS1893 asserts 10RXDV to indicate to the MAC/repeater  
that data is available on the MII Receive Bus (RXD[3:0]). The  
ICS1893:  
• Asserts 10RXDV after it detects and recovers the  
Start-of-Stream delimiter, /J/K/. (For the timing reference,  
see Chapter 10.5.6, “MII / 100M Stream Interface:  
Synchronous Receive Timing”.)  
• De-asserts 10RXDV after it detects either the End-of-Stream  
delimiter (/T/R/) or a signal error.  
Note: 10RXDV is synchronous with the Receive Data Clock,  
10RCLK.  
RXER  
RXTRI  
–
39  
41  
No  
Receive Error.  
connect For the 10M Serial Interface, this pin is a no connect. For more  
information, see Table 6-2.  
Input  
Receive (Interface), Tri-State.  
• The input on this pin is from a MAC. When the signal on this  
pin is logic:  
– Low, the MAC indicates that it is not in a tri-state condition.  
– High, the MAC indicates that it is in a tri-state condition. In  
this case, the ICS1893 acts to ensure that only one PHY is  
active at a time.  
• If the PHY address is 00, the ICS1893 acts as if the RX-TRI  
pin is held high.  
TXCLK  
TXD0  
10TCLK  
10TD  
–
43  
45  
Output 10M (Serial Interface) Transmit Clock.  
This pin’s description is the same as that given in Table 9-5.  
Input  
No  
10M (Serial Interface) Transmit Data.  
This pin’s description is the same as that given in Table 9-5.  
TXD1,  
TXD2,  
TXD3  
46,  
47,  
48  
Transmit Data 1–3.  
connect For the 10M Serial Interface, these pins are a no connect. For  
more information, see Table 6-2.  
TXEN  
10TXEN  
–
44  
Input  
10M (Serial Interface) Transmit Enable.  
This pin’s description is the same as that given in Table 9-5.  
TXER  
42  
No  
Transmit Error.  
connect For the 10M Serial Interface, this pin is a no connect. For more  
information, see Table 6-2.  
9.3.5 Reserved Pins  
Table 9-8 lists the reserved pins.  
Table 9-8. Reserved Pins  
Pin  
Pin  
Pin  
Pin Description  
Name Number  
Type  
NC 20  
–
No Connect.  
• This pin is always reserved for use by ICS.  
• Depending on the interface that is used, some of the MAC/Repeater  
interface pins can also be no-connects. For pins that are no connects  
when the interface is the:  
– 100M Symbol Interface, see Section 9.3.4.2, “MAC/Repeater  
Interface Pins for 100M Symbol Interface”.  
– 10M Serial Interface, see Section 9.3.4.3, “MAC/Repeater Interface  
Pins for 10M Serial Interface”.  
Caution: Pins designated as ‘no-connect’ pins must not be connected,  
as connecting them can affect the performance of the  
ICS1893.  
9.3.6 Ground and Power Pins  
Table 9-9 lists the ground and power pins.  
Table 9-9. Ground and Power Pins  
Pin Name Pin Number  
Pin Type  
Ground  
Ground  
Ground  
Ground  
Ground  
Ground  
Ground  
Ground  
Ground  
Ground  
Ground  
Ground  
Power  
VSS  
4
VSS  
11  
12  
17  
22  
28  
29  
40  
56  
57  
58  
61  
7
VSS  
VSS  
VSS  
VSS  
VSS  
VSS  
VSS  
VSS  
VSS  
VSS  
VDD  
VDD  
VDD  
VDD  
VDD  
VDD_IO  
VDD_IO  
VDD  
VDD  
8
Power  
15  
16  
25  
37  
51  
54  
63  
Power  
Power  
Power  
Power  
Power  
Power  
Power  
Chapter 10 DC and AC Operating Conditions  
10.1 Absolute Maximum Ratings  
Table 10-1 lists absolute maximum ratings. Stresses above these ratings can permanently damage the  
ICS1893. These ratings, which are standard values for ICS commercially rated parts, are stress ratings  
only. Functional operation of the ICS1893 at these or any other conditions above those indicated in the  
operational sections of the specifications is not implied. Exposure to absolute maximum rating conditions  
for extended periods can affect product reliability. Electrical parameters are guaranteed only over the range  
of the recommended operating temperature.  
Table 10-1. Absolute Maximum Ratings for ICS1893  
Item  
Rating  
VDD (measured to VSS)  
Digital Inputs / Outputs  
Storage Temperature  
Junction Temperature  
Soldering Temperature  
Power Dissipation  
-0.3 V to 3.6V  
-0.3 V to VDD +0.3 V  
-55° C to +150° C  
125° C  
260° C  
See Section 10.4.1, “DC Operating Characteristics for Supply Current”  
10.2 Recommended Operating Conditions  
Table 10-2. Recommended Operating Conditions for ICS1893  
Parameter  
Symbols  
Min. Max. Units  
Ambient Operating Temperature  
T
0
+70  
° C  
A
Power Supply Voltage (measured to VSS)  
VDD  
+3.14 +3.47  
V
10.3 Recommended Component Values  
Table 10-3. Recommended Component Values for ICS1893  
Parameter  
Minimum  
Typical  
Maximum  
Tolerance  
Units  
MHz  
W
Oscillator Frequency  
10TCSR Resistor Value  
100TCSR Resistor Value  
LED Resistor Value  
–
–
25  
2.00k  
–
–
± 50 ppm †  
1%  
1%  
–
–
See Figure 10-1  
1k  
–
W
510  
10k  
W
† There are two IEEE Std 802.3 requirements that drive the tolerance for the frequency of the oscillator.  
• Clause 22.2.2.1 requires the MII TX_CLK to have an accuracy of ± 100 ppm.  
• Clause 24.2.3.4 is more stringent. It requires the code-bit timer to have an accuracy of 0.005% (that is, ±50 ppm).  
Note: Although the 10TCSR and 100TCSR pins do not need to be bypassed, include placeholders for  
bypass capacitors on a printed circuit board that uses the ICS1893.  
Figure 10-1. ICS1893 10TCSR and 100TCSR  
ICS1893  
VDD  
7
10TCSR  
9
100TCSR  
10  
12.1 KW 1%  
VDD  
10TCSR  
2.0KW 1%  
100TCSR  
1.54KW 1%  
Leave place holder but do not install bypass capacitors.  
10.4 DC Operating Characteristics  
This section lists the ICS1893 DC operating characteristics.  
10.4.1 DC Operating Characteristics for Supply Current  
Table 10-4 lists the DC operating characteristics for the supply current to the ICS1893 under various  
conditions.  
Note: All VDD_IO measurements are taken with respect to VSS (which equals 0 V).  
Table 10-4. DC Operating Characteristics for Supply Current  
Parameter  
Operating Mode  
100Base-TX‡  
Symbol  
IDD_IO  
Min. Typ.  
Max. Units  
Supply Current†  
–
–
–
–
–
–
–
–
–
8
110  
5
11  
125  
8
mA  
mA  
mA  
mA  
mA  
mA  
mA  
mA  
mA  
IDD  
Supply Current†  
Supply Current†  
Supply Current†  
Supply Current†  
10Base-T‡  
Auto-Negotiation  
Power-Down  
Reset  
IDD_IO  
IDD  
150  
5
160  
8
IDD_IO  
IDD  
80  
3
90  
5
IDD_IO  
IDD  
40  
50  
50  
60  
IDD  
† These supply current parameters are measured through VDD pins to the ICS1893. The supply current  
parameters include external transformer currents.  
‡ Measurements taken with 100% data transmission and the minimum inter-packet gap.  
10.4.2 DC Operating Characteristics for TTL Inputs and Outputs  
Table 10-5 lists the 3.3-V DC operating characteristics of the ICS1893 TTL inputs and outputs.  
Note: All VDD_IO measurements are taken with respect to VSS (which equals 0 V).  
Table 10-5. 3.3-V DC Operating Characteristics for TTL Inputs and Outputs  
Parameter  
Symbol  
Conditions  
VDD_IO = 3.47 V  
Min. Max. Units  
TTL Input High Voltage  
TTL Input Low Voltage  
TTL Output High Voltage  
TTL Output Low Voltage  
V
–
2.0  
–
–
0.8  
–
V
V
V
V
V
IH  
V
VDD_IO = 3.47 V  
VDD_IO = 3.14 V  
VDD_IO = 3.14 V  
VDD_IO = 3.14 V  
–
IL  
V
I
= –4 mA  
= +4 mA  
= –4 mA  
2.4  
–
OH  
OH  
V
I
0.4  
–
OL  
OL  
TTL Driving CMOS,  
Output High Voltage  
V
I
2.4  
OH  
OH  
TTL Driving CMOS,  
Output Low Voltage  
V
VDD_IO = 3.14 V  
I
= +4 mA  
OL  
–
0.4  
V
OL  
10.4.3 DC Operating Characteristics for REF_IN  
Table 10-6 lists the 3.3-V DC characteristics for the REF_IN pin.  
Note: The REF_IN input switch point is 50% of VDD.  
Table 10-6. 3.3-V DC Operating Characteristics for REF_IN  
Parameter  
Symbol  
Test Conditions  
VDD_IO = 3.47 V  
VDD_IO = 3.14 V  
Min.  
2.4  
–
Max.  
–
Units  
Input High Voltage  
Input Low Voltage  
V
V
V
IH  
V
0.8  
IL  
10.4.4 DC Operating Characteristics for Media Independent Interface  
Table 10-7 lists DC operating characteristics for the Media Independent Interface (MII) for the ICS1893.  
Table 10-7. DC Operating Characteristics for Media Independent Interface  
Parameter  
Conditions  
Minimum  
Typical  
Maximum  
Units  
pF  
MII Input Pin Capacitance  
MII Output Pin Capacitance  
MII Output Drive Impedance  
–
–
–
–
–
–
8
14  
–
–
pF  
VDD_IO = 3.3V  
60  
W
10.5 Timing Diagrams  
10.5.1 Timing for Clock Reference In (REF_IN) Pin  
Table 10-8 lists the significant time periods for signals on the clock reference in (REF_IN) pin. Figure 10-2  
shows the timing diagram for the time periods.  
Note: The REF_IN switching point is 50% of VDD.  
Table 10-8. REF_IN Timing  
Time  
Parameter  
Conditions  
Min.  
Typ.  
Max. Units  
Period  
t1  
t2  
REF_IN Duty Cycle  
REF_IN Period  
–
–
45  
–
50  
40  
55  
–
%
ns  
Figure 10-2. REF_IN Timing Diagram  
t1  
REF_IN  
t2  
10.5.2 Timing for Transmit Clock (TXCLK) Pins  
Table 10-9 lists the significant time periods for signals on the Transmit Clock (TXCLK) pins for the various  
interfaces. Figure 10-3 shows the timing diagram for the time periods.  
Table 10-9. Transmit Clock Timing  
Time  
Parameter  
Conditions  
Min. Typ. Max. Units  
Period  
t1  
TXCLK Duty Cycle  
TXCLK Period  
TXCLK Period  
TXCLK Period  
TXCLK Period  
–
35  
–
50  
40  
65  
–
%
ns  
ns  
ns  
ns  
t2a  
t2b  
t2c  
t2d  
100M MII (100Base-TX)  
10M MII (10Base-T)  
–
400  
40  
–
100M Symbol Interface (100Base-TX)  
10M Serial Interface (10Base-T)  
–
–
–
100  
–
Figure 10-3. Transmit Clock Timing Diagram  
t1  
TXCLK  
t2x  
10.5.3 Timing for Receive Clock (RXCLK) Pins  
Table 10-10 lists the significant time periods for signals on the Receive Clock (RXCLK) pins for the various  
interfaces. Figure 10-4 shows the timing diagram for the time periods.  
Table 10-10. MII Receive Clock Timing  
Time  
Parameter  
Conditions  
Min. Typ. Max. Units  
Period  
t1  
RXCLK Duty Cycle  
RXCLK Period  
RXCLK Period  
RXCLK Period  
RXCLK Period  
–
35  
–
50  
40  
65  
–
%
ns  
ns  
ns  
ns  
t2a  
t2b  
t2c  
t2d  
100M MII (100Base-TX)  
10M MII (10Base-T)  
–
400  
40  
–
100M Symbol Interface (100Base-TX)  
10M Serial Interface (10Base-T)  
–
–
–
100  
–
Figure 10-4. Receive Clock Timing Diagram  
t1  
RXCLK  
t2  
10.5.4 100M MII / 100M Stream Interface: Synchronous Transmit Timing  
Table 10-11 lists the significant time periods for the 100M MII / 100M Stream Interface synchronous  
transmit timing. The time periods consist of timings of signals on the following pins:  
• TXCLK  
• TXD[3:0]  
• TXEN  
• TXER  
Figure 10-5 shows the timing diagram for the time periods.  
Table 10-11. 100M MII / 100M Stream Interface: Synchronous Transmit Timing  
Time  
Parameter  
Conditions  
Min.  
Typ.  
Max. Units  
Period  
t1  
t2  
TXD[3:0], TXEN, TXER Setup to TXCLK Rise  
TXD[3:0], TXEN, TXER Hold after TXCLK Rise  
–
–
15  
0
–
–
–
–
ns  
ns  
Figure 10-5. 100M MII / 100M Stream Interface Synchronous Transmit Timing Diagram  
TXCLK  
TXD[3:0]  
TXEN  
TXER  
t1  
t2  
10.5.5 10M MII: Synchronous Transmit Timing  
Table 10-12 lists the significant time periods for the 10M MII synchronous transmit timing. The time periods  
consist of timings of signals on the following pins:  
• TXCLK  
• TXD[3:0]  
• TXEN  
• TXER  
Figure 10-6 shows the timing diagram for the time periods.  
Table 10-12. 10M MII: Synchronous Transmit Timing  
Time  
Parameter  
Conditions  
Min.  
Typ.  
Max. Units  
Period  
t1  
t2  
TXD[3:0], TXEN, TXER Setup to TXCLK Rise  
TXD[3:0], TXEN, TXER Hold after TXCLK Rise  
–
–
375  
0
–
–
–
–
ns  
ns  
Figure 10-6. 10M MII Synchronous Transmit Timing Diagram  
TXCLK  
TXD[3:0]  
TXEN  
TXER  
t1  
t2  
10.5.6 MII / 100M Stream Interface: Synchronous Receive Timing  
Table 10-13 lists the significant time periods for the MII / 100M Stream Interface synchronous receive  
timing. The time periods consist of timings of signals on the following pins:  
• RXCLK  
• RXD[3:0]  
• RXDV  
• RXER  
Figure 10-7 shows the timing diagram for the time periods.  
Table 10-13. MII / 100M Stream Interface: Synchronous Receive Timing  
Time  
Parameter  
Min.  
Typ.  
Max. Units  
Period  
t1  
t2  
RXD[3:0], RXDV, and RXER Setup to RXCLK Rise  
RXD[3:0], RXDV, and RXER Hold after RXCLK Rise  
10.0  
10.0  
–
–
–
–
ns  
ns  
Figure 10-7. MII / 100M Stream Interface Synchronous Receive Timing Diagram  
RXCLK  
RXD[3:0]  
RXDV  
RXER  
t1  
t2  
10.5.7 MII Management Interface Timing  
Table 10-14 lists the significant time periods for the MII Management Interface timing (which consists of  
timings of signals on the MDC and MDIO pins). Figure 10-8 shows the timing diagram for the time periods.  
Table 10-14. MII Management Interface Timing  
Time  
Parameter  
Conditions Min.  
Typ.  
Max. Units  
Period  
t1  
t2  
t3  
t4  
t5  
t6  
MDC Minimum High Time  
–
–
–
–
–
–
160  
160  
400†  
0
–
–
†
–
–
–
–
–
ns  
ns  
ns  
ns  
ns  
ns  
MDC Minimum Low Time  
MDC Period  
–
MDC Rise Time to MDIO Valid  
MDIO Setup Time to MDC  
MDIO Hold Time after MDC  
300  
–
10  
10  
–
† The ICS1893 is tested at 25 MHz (a 40-ns period) with a 50-pF load. Designs must account for all board loading of  
MDC.  
Figure 10-8. MII Management Interface Timing Diagram  
MDC  
t1  
t2  
t3  
t4  
MDIO  
(Output)  
MDC  
MDIO  
(Input)  
t5  
t6  
10.5.8 10M Serial Interface: Receive Latency  
Table 10-15 lists the significant time periods for the 10M Serial Interface timing. The time periods consist of  
timings of signals on the following pins:  
• TP_RX (the MDI mapping of the 10M/100M MII TP_RXP and TP_RXN pins)  
• 10RCLK (the 10M Serial Interface mapping of the 10M/100M MII RXCLK pins)  
• 10RD (the 10M Serial Interface mapping of the 10M/100M MII RXD0 pins)  
Figure 10-9 shows the timing diagram for the time periods.  
Table 10-15. 10M Serial Interface Receive Latency Timing  
Time  
Parameter  
Conditions  
Min. Typ. Max.  
Units  
Period  
t1  
TP_RX Input to 10RD Delay  
10M Serial Interface  
–
3.6  
4
Bit times  
Figure 10-9. 10M Serial Interface Receive Latency Timing  
TP_RX  
Bit A  
Bit B  
10RCLK  
10RD  
Bit A  
Bit B  
t1  
10.5.9 10M Media Independent Interface: Receive Latency  
Table 10-16 lists the significant time periods for the 10M MII timing. The time periods consist of timings of  
signals on the following pins:  
• TP_RX (that is, the MII TP_RXP and TP_RXN pins)  
• RXCLK  
• RXD  
Figure 10-10 shows the timing diagram for the time periods.  
Table 10-16. 10M MII Receive Latency  
Time  
Period  
Parameter  
Conditions Min. Typ. Max.  
10M MII 6.5  
Units  
t1  
First Bit of /5/ on TP_RX to /5/D/ on RXD  
–
7
Bit times  
Figure 10-10. 10M MII Receive Latency Timing Diagram  
†
TP_RX  
RXCLK  
RXD  
5
5
5
D
t1  
†
Manchester  
encoding is  
not shown.  
10.5.10 10M Serial Interface: Transmit Latency  
Table 10-17 lists the significant time periods for the 10M Serial Interface transmit latency. The time periods  
consist of timings of signals on the following pins:  
• 10TXEN (the 10M Serial Interface mapping of the 10M/100M MII TXEN pins)  
• 10TCLK (the 10M Serial Interface mapping of the 10M/100M MII TXCLK pins)  
• 10TD (the 10M Serial Interface mapping of the 10M/100M MII TXD0 pins)  
• TP_TX (the MDI mapping of the 10M/100M MII TP_TXP and TP_TXN pins)  
Figure 10-11 shows the timing diagram for the time periods.  
Table 10-17. 10M Serial Interface Transmit Latency Timing  
Time  
Parameter  
Conditions  
Min. Typ. Max.  
Units  
Period  
t1  
10TD Into TP_TX Out Delay  
10M Serial Interface  
–
0.8  
1
Bit times  
Figure 10-11. 10M Serial Interface Transmit Latency Timing Diagram  
10TXEN  
10TCLK  
10TD  
Bit A  
Bit B  
(MDI)  
P[3:0]TP_TX  
Bit A  
Bit B  
t1  
10.5.11 10M Media Independent Interface: Transmit Latency  
Table 10-18 lists the significant time periods for the 10M MII transmit latency. The time periods consist of  
timings of signals on the following pins:  
• TXEN  
• TXCLK  
• TXD (that is, TXD[3:0])  
• TP_TX (that is, TP_TXP and TP_TXN)  
Figure 10-12 shows the timing diagram for the time periods.  
Table 10-18. 10M MII Transmit Latency Timing  
Time  
Period  
Parameter  
Conditions Min. Typ. Max.  
10M MII 1.2  
Units  
t1  
TXD Sampled to MDI Output of First Bit  
–
2
Bit times  
Figure 10-12. 10M MII Transmit Latency Timing Diagram  
TXEN  
TXCLK  
TXD  
5
5
5
†
TP_TX  
t1  
†
Manchester  
encoding is  
not shown.  
10.5.12 MII / 100M Stream Interface: Transmit Latency  
Table 10-19 lists the significant time periods for the MII / 100 Stream Interface transmit latency. The time  
periods consist of timings of signals on the following pins:  
• TXEN  
• TXCLK  
• TXD (that is, TXD[3:0])  
• TP_TX (that is, TP_TXP and TP_TXN)  
Figure 10-13 shows the timing diagram for the time periods.  
Table 10-19. MII / 100M Stream Interface Transmit Latency  
Time  
Parameter  
Conditions  
Min. Typ. Max.  
Units  
Period  
t1  
t2  
TXEN Sampled to MDI Output of First MII mode  
Bit of /J/ †  
–
–
2.8  
6.1  
3
7
Bit times  
Bit times  
TXD Sampled to MDI Output of First  
Bit of /J/ †  
100M Stream Interface  
† The IEEE maximum is 18 bit times.  
Figure 10-13. MII / 100M Stream Interface Transmit Latency Timing Diagram  
TXEN  
TXCLK  
TXD  
Preamble /J/  
Preamble /K/  
†
TP_TX  
t1  
t2  
†
Shown  
unscrambled.  
10.5.13 100M MII: Carrier Assertion/De-Assertion (Half-Duplex Transmission)  
Table 10-20 lists the significant time periods for the 100M MII carrier assertion/de-assertion during  
half-duplex transmission. The time periods consist of timings of signals on the following pins:  
• TXEN  
• TXCLK  
• CRS  
Figure 10-14 shows the timing diagram for the time periods.  
Table 10-20. 100M MII Carrier Assertion/De-Assertion (Half-Duplex Transmission Only)  
Time  
Period  
Parameter  
Condi- Min. Typ. Max.  
tions  
Units  
t1  
t2  
TXEN Sampled Asserted to CRS Assert  
TXEN De-Asserted to CRS De-Asserted  
0
0
3
3
4
4
Bit times  
Bit times  
Figure 10-14. 100M MII Carrier Assertion/De-Assertion Timing Diagram  
(Half-Duplex Transmission Only)  
t2  
TXEN  
TXCLK  
CRS  
t1  
10.5.14 10M MII: Carrier Assertion/De-Assertion (Half-Duplex Transmission)  
Table 10-21 lists the significant time periods for the 10M MII carrier assertion/de-assertion during  
half-duplex transmission. The time periods consist of timings of signals on the following pins:  
• TXEN  
• TXCLK  
• CRS  
Figure 10-15 shows the timing diagram for the time periods.  
Table 10-21. 10M MII Carrier Assertion/De-Assertion (Half-Duplex Transmission Only)  
Time  
Period  
Parameter  
Condi- Min. Typ. Max. Units  
tions  
t1  
t2  
TXEN Asserted to CRS Assert  
0
0
–
2
2
4
Bit times  
Bit times  
TXEN De-Asserted to CRS De-Asserted  
Figure 10-15. 10M MII Carrier Assertion/De-Assertion Timing Diagram  
(Half-Duplex Transmission Only)  
t2  
TXEN  
TXCLK  
CRS  
t1  
10.5.15 100M MII / 100M Stream Interface: Receive Latency  
Table 10-22 lists the significant time periods for the 100M MII / 100M Stream Interface receive latency. The  
time periods consist of timings of signals on the following pins:  
• TP_RX (that is, TP_RXP and TP_RXN)  
• RXCLK  
• RXD (that is, RXD[3:0])  
Figure 10-16 shows the timing diagram for the time periods.  
Table 10-22. 100M MII / 100M Stream Interface Receive Latency Timing  
Time  
Parameter  
Conditions  
Min. Typ. Max.  
Units  
Period  
t1  
t2  
First Bit of /J/ into TP_RX to /J/ on RXD 100M MII  
–
–
16  
8
17  
9
Bit times  
Bit times  
First Bit of /J/ into TP_RX to /J/ on RXD 100M Stream Interface  
Figure 10-16. 100M MII / 100M Stream Interface: Receive Latency Timing Diagram  
†
TP_RX  
RXCLK  
RXD  
t1  
t2  
†
Shown  
unscrambled.  
10.5.16 100M Media Dependent Interface: Input-to-Carrier Assertion/De-Assertion  
Table 10-23 lists the significant time periods for the 100M MDI input-to-carrier assertion/de-assertion. The  
time periods consist of timings of signals on the following pins:  
• TP_RX (that is, TP_RXP and TP_RXN)  
• CRS  
• COL  
Figure 10-17 shows the timing diagram for the time periods.  
Table 10-23. 100M MDI Input-to-Carrier Assertion/De-Assertion Timing  
Time  
Parameter  
Conditions  
Min. Typ. Max.  
Units  
Period  
t1  
t2  
First Bit of /J/ into TP_RX to CRS Assert †  
–
10  
9
–
–
14 Bit times  
13 Bit times  
First Bit of /J/ into TP_RX while  
Half-Duplex Mode  
Transmitting Data to COL Assert †  
t3  
t4  
First Bit of /T/ into TP_RX to CRS  
De-Assert ‡  
–
13  
–
–
18 Bit times  
18 Bit times  
First Bit of /T/ Received into TP_RX to  
COL De-Assert ‡  
Half-Duplex Mode 13  
† The IEEE maximum is 20 bit times.  
‡ The IEEE minimum is 13 bit times, and the maximum is 24 bit times.  
Figure 10-17. 100M MDI Input to Carrier Assertion / De-Assertion Timing Diagram  
First bit  
First bit of /T/  
†
TP_RX  
t3  
t1  
CRS  
COL  
t4  
t2  
†
Shown  
unscrambled.  
10.5.17 Reset: Power-On Reset  
Table 10-24 lists the significant time periods for the power-on reset. The time periods consist of timings of  
signals on the following pins:  
• VDD  
• TXCLK  
Figure 10-18 shows the timing diagram for the time periods.  
Table 10-24. Power-On Reset Timing  
Time  
Parameter  
Conditions  
Min.  
Typ. Max. Units  
Period  
t1  
VDD ³ 2.7 V to Reset Complete  
–
40  
45  
500  
ms  
Figure 10-18. Power-On Reset Timing Diagram  
2.7 V  
VDD  
t1  
TXCLK  
Valid  
10.5.18 Reset: Hardware Reset and Power-Down  
Table 10-25 lists the significant time periods for the hardware reset and power-down reset. The time  
periods consist of timings of signals on the following pins:  
• REF_IN  
• RESETn  
• TXCLK  
Figure 10-19 shows the timing diagram for the time periods.  
Table 10-25. Hardware Reset and Power-Down Timing  
Time  
Period  
Parameter  
Condi-  
tions  
Min. Typ. Max. Units  
t1  
t2  
t3  
RESETn Active to Device Isolation and Initialization  
Minimum RESETn Pulse Width  
–
–
–
–
500  
–
60  
40  
35  
–
–
ns  
ns  
RESETn Released to TXCLK Valid  
500  
ms  
Figure 10-19. Hardware Reset and Power-Down Timing Diagram  
REF_IN  
RESETn  
t1  
t2  
t3  
TXCLK Valid  
Power  
Consumption  
(AC only)  
10.5.19 10Base-T: Heartbeat Timing (SQE)  
Table 10-26 lists the significant time periods for the 10Base-T heartbeat (that is, the Signal Quality Error).  
The time periods consist of timings of signals on the following pins:  
• TXEN  
• TXCLK  
• COL  
Figure 10-20 shows the timing diagram for the time periods.  
Note:  
1. For more information on 10Base-T SQE operations, see Section 7.5.10, “10Base-T Operation: SQE  
Test”.  
2. In 10Base-T mode, one bit time = 100 ns.  
Table 10-26. 10Base-T Heartbeat (SQE) Timing  
Time  
Parameter  
Conditions  
Min. Typ.  
Max. Units  
Period  
t1  
COL Heartbeat Assertion Delay from 10Base-T Half Duplex  
TXEN De-Assertion  
–
–
850  
1500  
ns  
ns  
t2  
COL Heartbeat Assertion Duration  
10Base-T Half Duplex  
1000 1500  
Figure 10-20. 10Base-T Heartbeat (SQE) Timing Diagram  
TXEN  
TXCLK  
COL  
t1  
t2  
10.5.20 10Base-T: Jabber Timing  
Table 10-27 lists the significant time periods for the 10Base-T jabber. The time periods consist of timings of  
signals on the following pins:  
• TXEN  
• TP_TX (that is, TP_TXP and TP_TXN)  
• COL  
Figure 10-21 shows the timing diagram for the time periods.  
Note: For more information on 10Base-T jabber operations, see Section 7.5.9, “10Base-T Operation:  
Jabber”.  
Table 10-27. 10Base-T Jabber Timing  
Time  
Parameter  
Conditions  
Min.  
Typ.  
Max. Units  
Period  
t1  
t2  
Jabber Activation Time  
10Base-T Half Duplex  
10Base-T Half Duplex  
20  
–
–
35  
ms  
ms  
Jabber De-Activation Time  
300  
325  
Figure 10-21. 10Base-T Jabber Timing Diagram  
TXEN  
t1  
TP_TX  
COL  
t2  
10.5.21 10Base-T: Normal Link Pulse Timing  
Table 10-28 lists the significant time periods for the 10Base-T Normal Link Pulse (which consists of timings  
of signals on the TP_TXP pins). Figure 10-22 shows the timing diagram for the time periods.  
Table 10-28. 10Base-T Normal Link Pulse Timing  
Time  
Parameter  
Conditions  
Min. Typ. Max. Units  
Period  
t1  
t2  
Normal Link Pulse Width  
10Base-T  
–
8
100  
20  
–
ns  
Normal Link Pulse to Normal Link Pulse Period 10Base-T  
25  
ms  
Figure 10-22. 10Base-T Normal Link Pulse Timing Diagram  
TP_TXP  
t1  
t2  
10.5.22 Auto-Negotiation Fast Link Pulse Timing  
Table 10-29 lists the significant time periods for the ICS1893 Auto-Negotiation Fast Link Pulse. The time  
periods consist of timings of signals on the following pins:  
• TP_TXP  
• TP_TXN  
Figure 10-23 shows the timing diagram for one pair of these differential signals, for example TP_TXP  
minus TP_TXN.  
Table 10-29. Auto-Negotiation Fast Link Pulse Timing  
Time  
Parameter  
Conditions Min.  
Typ.  
Max.  
Units  
Period  
t1  
t2  
t3  
t4  
t5  
t6  
Clock/Data Pulse Width  
–
–
–
–
–
–
–
55  
110  
–
90  
60  
125  
5
–
70  
140  
–
ns  
ms  
Clock Pulse-to-Data Pulse Timing  
Clock Pulse-to-Clock Pulse Timing  
Fast Link Pulse Burst Width  
ms  
ms  
Fast Link Pulse Burst to Fast Link Pulse Burst  
Number of Clock/Data Pulses in a Burst  
10  
15  
15  
20  
25  
30  
ms  
pulses  
Figure 10-23. Auto-Negotiation Fast Link Pulse Timing Diagram  
Clock  
Pulse  
Data  
Pulse  
Clock  
Pulse  
Differential  
Twisted Pair  
Transmit Signal  
t1  
t1  
t3  
t2  
FLP Burst  
FLP Burst  
Differential  
Twisted Pair  
Transmit Signal  
t4  
t5  
Chapter 11 Physical Dimensions of ICS1893 Package  
This section gives the physical dimensions for the ICS1893 package.  
• The lead count (N) is 64 leads.  
• The nominal footprint (that is the body) is 10.0 mm.  
Table 11-1 lists the ICS1893 physical dimensions, which are shown in Figure 11-1.  
Table 11-1. ICS1893 Physical Dimensions  
Sym-  
bol  
Description  
Nominal  
(mm)  
Minimum  
Maximum  
Tolerance  
(mm)  
A
A1  
A2  
b
Full Package Height  
Package Standoff  
Package Thickness  
Lead Width with Plate  
Lead Height with Plate  
Tip-to-Tip Width  
Body Width  
–
–
0.05  
0.95  
0.17  
0.09  
–
1.20  
0.15  
1.05  
0.27  
0.20  
–
–
0.10  
1.00  
0.22  
0.15  
12.00  
10.00  
12.00  
10.00  
0.50  
0.60  
±0.05  
±0.05  
±0.05  
c
+0.05 / -0.06  
D
–
D1  
E
–
–
–
Tip-to-Tip Width  
Body Width  
–
–
–
E1  
e
–
–
–
Lead Pitch  
–
–
–
L
Foot Length  
0.45  
0.75  
+0.15 / -0.15  
Figure 11-1. ICS1893 Physical Dimensions  
D
D1  
N
1
E1  
E
A2  
e
Standoff  
A1  
A
Seating  
Plane  
B
c
L
Chapter 12 Ordering Information  
Figure 12-1 shows ordering information for the ICS1893 package:  
• ICS1893Y-10LF and ICS1893YI-10LF (industrial temp.)  
Figure 12-1. ICS1893 Ordering Information  
Y -10 LF T  
ICS 1893  
Tape and Reel  
Lead (Pb) Free, RoHS compliant  
Package Type  
Y-10 = 10 ´ 10 TQFP (Thin Quad Flat Pack)  
Device Identifier  
Company Identifier  
Integrated Circuit Systems, Inc.  
Integrated Circuit Systems, Inc.  
Corporate Headquarters:  
2435 Boulevard of the Generals  
P.O. Box 968  
Valley Forge, PA 19482-0968  
Telephone: 610-630-5300  
Fax:  
610-630-5399  
Silicon Valley:  
Web Site:  
525 Race Street  
San Jose, CA 95126-3448  
Telephone: 408-297-1201  
Fax:  
408-925-9460  
Email: webmaster@icst.com  
http://www.icst.com  
ICS reserves the right to make changes in the device data identified in  
this publication without further notice. ICS advises its customers to  
obtain the latest version of all device data to verify that any information  
being relied upon by the customer is current and accurate.  
IMPORTANT NOTICE AND DISCLAIMER  
RENESAS ELECTRONICS CORPORATION AND ITS SUBSIDIARIES (“RENESAS”) PROVIDES TECHNICAL  
SPECIFICATIONS AND RELIABILITY DATA (INCLUDING DATASHEETS), DESIGN RESOURCES (INCLUDING  
REFERENCE DESIGNS), APPLICATION OR OTHER DESIGN ADVICE, WEB TOOLS, SAFETY INFORMATION, AND  
OTHER RESOURCES “AS IS” AND WITH ALL FAULTS, AND DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,  
INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A  
PARTICULAR PURPOSE, OR NON-INFRINGEMENT OF THIRD PARTY INTELLECTUAL PROPERTY RIGHTS.  
These resources are intended for developers skilled in the art designing with Renesas products. You are solely responsible  
for (1) selecting the appropriate products for your application, (2) designing, validating, and testing your application, and (3)  
ensuring your application meets applicable standards, and any other safety, security, or other requirements. These  
resources are subject to change without notice. Renesas grants you permission to use these resources only for  
development of an application that uses Renesas products. Other reproduction or use of these resources is strictly  
prohibited. No license is granted to any other Renesas intellectual property or to any third party intellectual property.  
Renesas disclaims responsibility for, and you will fully indemnify Renesas and its representatives against, any claims,  
damages, costs, losses, or liabilities arising out of your use of these resources. Renesas' products are provided only subject  
to Renesas' Terms and Conditions of Sale or other applicable terms agreed to in writing. No use of any Renesas resources  
expands or otherwise alters any applicable warranties or warranty disclaimers for these products.  
(Rev.1.0 Mar 2020)  
Corporate Headquarters  
Contact Information  
TOYOSU FORESIA, 3-2-24 Toyosu,  
Koto-ku, Tokyo 135-0061, Japan  
www.renesas.com  
For further information on a product, technology, the most  
up-to-date version of a document, or your nearest sales  
office, please visit:  
www.renesas.com/contact/  
Trademarks  
Renesas and the Renesas logo are trademarks of Renesas  
Electronics Corporation. All trademarks and registered  
trademarks are the property of their respective owners.  
© 2020 Renesas Electronics Corporation. All rights reserved.