Compliant with the IEEE 802.3u 100BASE-TX
standard
■
Compliant with the ANSI X3T12 TP-PMD 1995
standard
■
Compliant with the IEEE 802.3u AutoNegotiation protocol for automatic link type
selection
■
Supports the MII with serial management
interface
■
Supports Full Duplex operation for 10 Mbps and
100 Mbps
■
High performance 100 Mbps clock generator
and data recovery circuitry
■
Adaptive equalization circuitry for 100 Mbps
receiver
Controlled output edge rates in 100 Mbps
Supports a 10BASE-T interface without the
need for an external filter
Provides Loopback mode for system
diagnostics
Includes flexible LED configuration capability
Digital clock recovery circuit using advanced
digital algorithm to reduce jitter
Low-power, high-performance CMOS process
Available in a 100-pin PQFP package
GENERAL DESCRIPTION
The NetPHY-1 device is a physical-layer, single-chip,
low-power transceiver for 100BASE-TX, 100BASE-FX,
and 10BASE-T operations. On the media side, it provides a direct interface to Fiber Media for 100BASE-FX
Fast Ethernet, Unshielded Twisted Pair Category 5
Cable (UTP5) for 100BASE-TX Fast Ethernet, or
UTP5/UTP3 Cable for 10BASE-T Ethernet. Through
the IEEE 802.3u Media Independent Interface (MII),
the NetPHY-1 device connects to the Medium Access
Control (MAC) layer, ensuring a high interoperability
among products from different vendors.
The NetPHY-1 device uses a low-power, high-performance CMOS process. It contains the entire physical
layer functions of 100BASE-FX and 100BASE-TX as
defined by the IEEE 802.3u standard, including the
Physical Coding Sublayer (PCS), Physical Medium
Attachment (PMA), 100BASE-TX Twisted Pair Physical
Medium Dependent (TP-PMD) sublayer, and a
10BASE-T Encoder/Decoder (ENDEC). The NetPHY-1
device provides strong support for the Auto-Negotiation
function utilizing automatic media speed and protocol
selection. The NetPHY-1 device incorporates an internal wave-shaping filter to control rise/fall time, eliminating the need for external filtering on the 10/100
Mbps signals.
This document contains information on a product under development at Advanced Micro Devices. The information
is intended to help you evaluate this product. AMD reserves the right to change or discontinue work on this proposed
product without notice.
Refer to AMD’s Website (www.amd.com) for the latest information.
Publication# 22164 Rev: AAmendment/+2
Issue Date: February 1999
AMD standard products are available in se ver al packages and operating ranges . The order number (V alid Combination) is f ormed
by a combination of the elements below.
Am79C873
Am79C873
KC\W
Valid Combinations
KC\W
ALTERNATE PACKAGING OPTION
\W = Trimmed and formed in a tray
TEMPERATURE RANGE
C = Commercial (0˚C to +70˚C)
P ACKA GE TYPE
K = Plastic Quad Flat Pack (PQR100)
SPEED OPTION
Not Applicable
DEVICE NUMBER/DESCRIPTION
Am79C873
NetPHY-1™ 10/100 Mbps Ethernet Physical Layer
Single-Chip Transceiver with 100BASE-FX Support
Valid Combinations
Valid Combinations list configurations planned to be supported in volume for this device. Consult the local AMD sales
office to confirm availability of specific valid combinations and
to check on newly released combinations.
4Am79C873
PRELIMINARY
RELATED AMD PRODUCTS
Part No.Description
Controllers
Am79C90CMOS Local Area Network Controller for Ethernet (C-LANCE™)
Integrated Controllers
Am79C930PCnet™-Mobile Single Chip Wireless LAN Media Access Controller
Am79C940Media Access Controller for Ethernet (MACE™)
Am79C961APCnet-ISA II Full Duplex Single-Chip Ethernet Controller for ISA Bus
Am79C965APCnet-32 Single-Chip 32-Bit Ethernet Controller for 486 and VL Buses
Am79C970APCnet-PCI II Full Duplex Single-Chip Ethernet Controller for PCI Local Bus
Am79C971PCnet-FAST Single-Chip Full Duplex 10/100 Mbps Ethernet Controller for PCI Local Bus
Am79C972PCnet-FAST+ Enhanced 10/100 Mbps PCI Ethernet Controller with OnNow Support
Am79C973/
Am79C975
Am79C978PCnet-Home Single-chip 1/10 Mbps PCI Home networking Controller
In 100 Mbps mode, if this signal is asserted high and
TX_EN is active, the HALT symbol is substituted for the
actual data nibble. In 10 Mbps mode, this input
is ignored.
In bypass modes (BP4B5B or BPALIGN), TX_ER becomes the TXD4 pin, the fifth TXD data bit.
TXD[3:0]
Transmit DataInput
These are the transmit data input pins for nibble
data from the MII in 100 Mbps or 10 Mbps nibble
mode (25 MHz
Mbps nibble mode).
In 10 Mbps serial mode, the TXD0 pin is used as the
serial data input pin. TXD[3:1] are ignored.
for 100 Mbps mode, 2.5 MHz for 10
TX_EN
Transmit EnableInput
Active high input indicates the presence of valid nibble data on TXD[3:0] for both 100 Mbps or 10 Mbps
nibble mode.
RXD[3:0]
Receive DataOutput/Z
Nibble wide receive data (synchronous to RX_CLK - 25
MHz for 100BASE-TX mode, 2.5 MHz for 10BASE-T
nibble mode). Data is dr iven on the falling edge of
RX_CLK.
In 10 Mbps serial mode, the RXD0 pin is used as the
data output pin. RXD[3:1] are ignored.
1
RX_CLK
Receive ClockOutput/Z
Provides the recovered receive clock for different
modes of operation:
- 25 MHz nibble clock in 100 Mbps mode
- 2.5 MHz nibble clock in 10 Mbps nibble mode
- 10 MHz receive clock in 10 Mbps serial mode
1
CRS
Carrier SenseOutput/Z
This pin is asserted high to indicate the presence of
carrier due to receive or transmit activities in 10BASET or 100BASE-TX Half Duplex modes.
In Repeater, when Full Duplex or Loopback mode is a
logic 1, it indicates the presence of carrier due only to
receive activity.
1
In 10 Mbps serial mode, active high indicates the presence of valid 10 Mbps data on TXD0.
TX_CLK
Transmit ClockOutput/Z
This pin provides the transmit clock output from the
NetPHY-1 deviceas follows:
- 25 MHz nibble transmit clock derived from transmit Phase Locked Loop (TX PLL) in 100BASE-TX
mode
- 2.5 MHz transmit clock in 10BASE-T nibble mode
- 10 MHz transmit clock in 10BASE-T serial mode
1
MDC
Management Data ClockInput
This pin is the synchronous clock to the MDIO management data input/output serial interface which is asynchronous to transmit and receive clocks . The maxim um
clock rate is 2.5 MHz.
MDIO
Management Data I/OInput/Output
This pin is the bidirectional management instruction/
data signal that may be driven by the station management entity or the PHY. This pin requires a 1.5 KΩ pullup resistor.
COL
Collision DetectOutput/Z
This pin is asserted high to indicate detection of collision conditions in 10 Mbps and 100 Mbps Half Duplexmodes. In 10BASE-T Half Duplex mode with Heartbeat
set active (bit 13, register 18h), it is also asserted for a
duration of approximately 1ms at the end of transmission to indicate heartbeat. In Full Duplex mode, this
signal is always logic 0. There is no heartbeat function
in Full Duplex mode.
1
RX_DV
Receive Data ValidOutput/Z
This pin is asserted high to indicate that valid data is
present on RXD[3:0].
1
RX_ER/RXD4
Receive ErrorOutput/Z
This pin is asserted high to indicate that an invalid symbol has been detected inside a received packet in 100
Mbps mode.
In a bypass mode (BP4B5B or BPALIGN modes),
RX_ER becomes RXD4, the fifth RXD data bit of the
5B symbols.
1
1. Goes to high impedance.
8Am79C873
PRELIMINARY
RX_EN
Receive EnableInput
This pin is active high enabled for receive signals
RXD[3:0], RX_CLK, RX_D V and RX_ER. A low on this
input tri-states these output pins. For normal operation
in a NODE application, this pin should be pulled high.
These pins are the differential receive input for
10BASE-T and 100BASE-TX. They are capable of receiving 100BASE-TX MLT-3 or 10BASE-T Manchester
encoded data.
FXRD±
100BASE-FX PECL Differential Input PairInput
These pins are the differential receive input for
100BASE-FX. They are capable of receiving
100BASE-FX.
FXSD±
100BASE-FX PECL Signal DetectInput
These input signals from the FX-PMD transceiver indicate detection of a receive signal from the Fiber Media.
function will change to indicate the Polarity status for 10
Mbps operation. If polarity is inv erted, the POLLED will
go ON.
COLLED
Collision LEDOutput
This pin indicates the presence of collision activity for
10 Mbps and 100 Mbps operation. This LED has no
meaning for 10 Mbps or 100 Mbps Full Duplex operation (Active low).
LINKLED
Link LEDOutput
This pin indicates Good Link status for 10 Mbps and
100 Mbps operation (Active low). It functions as the
TRAFFIC LED when bit 5 of register 16 is set to 1. In
TRAFFIC LED mode, it is always ON when the link is
OK. The TRAFFIC LED flashes when transmitting or
receiving.
RXLED
Receive LEDOutput Drain
This pin indicates the presence of receive activity for 10
Mbps and 100 Mbps operation (Active low). The NetPHY-1 device incorporates a “monostable” function on
the RXLED output. This ensures that even minimal receive activity will generate an adequate LED ON time.
(TRAFFIC LED)
10TXO±
10BASE-T Differential Output PairOutput
This output pair provides controlled rise and fall times
designed to filter the transmitters output.
100TXO±
100BASE-TX Twisted Pair Differential Output Pair
Output
This output pair drives MLT-3 encoded data to the
100 M twisted pair cable and provides controlled rise
and fall times designed to filter the transmitters output,
reducing any associated EMI.
FXTD±
100BASE-FX PECL Differential Output PairOutput
These pins are the differential transmit output for
100BASE-FX. They are capable of transmitting
100BASE-FX
LED Interface
These outputs can directly drive LEDs or provide status
information to a network management device.
FDXLED
Polarity/Full Duplex LEDOutput
This pin indicates Full Duplex mode status for 100
Mbps and 10 Mbps operation (Active low). If bit 4 of
Register 16 (FDXLED_MODE) is set, the FDXLED pin
(POLLED)
TXLED
Transmit LEDOutput Drain
This pin indicates the presence of transmit activity for 10
Mbps and 100 Mbps operation (Active low). The NetPHY-1 device incorporates a “monostable” function on
the TXLED output. This ensures that even minimal
transmit activity will generate an adequate LED ON time.
Device Configuration/Control/Status
Interface
UTP
UTP Cable IndicationOutput
This pin is the UTP Cable Indication. When UTP=1, it
indicates that the UTP cable is being used.
SPEED10
Speed 10 MbpsOutput
When set high, this bit indicates a 10 Mbps operation,
when set low 100 Mbps operation. This pin can drive
a low current LED to indicate that 100 Mbps operation
is selected.
RX_LOCK
Lock for Clock/Data Recovery PLLOutput
When this pin is high, it indicates that the receiver recovery PLL logic has locked to the input data stream.
Am79C8739
PRELIMINARY
LNKSTS
Link Status Register BitOutput
This pin reflects the status of bit 2 register 1.
OPMODE0-OPMODE3
OPMODE0-OPMODE3Input
These pins are used to control the forced or advertised
operating mode of the NetPHY-1 device (see table below). The v alue is latched into the NetPHY-1 device registers at power-up/rese..
OP-
MODE3
0000
0001
0010
0011
0100
OP-
MODE2
OP-
MODE1
OP-
MODE0Function
Auto-Negotiation
enable with all
capabilities with
Flow Control
Auto-Negotiation
enable without all
capabilities without
Flow Control
Auto-Negotiation
100TX FDX with
Flow Control only
Auto-Negotiation
100TX FDX/HDX
without Flow
Control
Auto-Negotiation
10TP FDX with
Flow Control only
TPR/NODE
R
Repeater/Node ModeInput
When set high, this bit selects REPEA TER mode; when
set low, it selects NODE. In REPEATER mode or
NODE mode with Full Duplex configured, the Carrier
Sense (CRS) output from the NetPHY-1 device will be
asserted only during receive activity . In NODE mode or
a mode not configured for Full Duplex operation, CRS
will be asserted during receive or transmit activity. At
power-up/reset, the value on this pin is latched into
Register 16, bit 11.
BPALIGN
Bypass AlignmentInput
This pin allows 100 Mbps transmit and receive data
streams to bypass all of the transmit and receive operations when set high. At power-up/reset, the value on
this pin is latched into bit Register 16, bit 13.
BP4B5B
Bypass 4B5B Encoder/DecoderInput
This pin allows 100 Mbps transmit and receive data
streams to bypass the 4B to 5B encoder and 5B to 4B
decoder circuits when set high. At power-up/reset, the
value on this pin is latched into Register 16, bit 15.
BPSCR
Bypass Scrambler/DescramblerInput
This pin allows 100 Mbps transmit and receive data
streams to bypass the scrambler and descrambler circuits when set high. At power-up/reset, the value on
this pin is latched into Register 16, bit 14.
Auto-Negotiation
0101
0110
0111
1000
1001
1010
1011
1111
10TX FDX/HDX
without Flow
Control
Manual select
100TX FDX
Manual select
100TX HDX
Manual select
10TX FDX
Manual select
10TX HDX
Manual select
100FX FDX
Manual select
100FX HDX
Auto-Negotiation
10/100TX. HDX
only
10BTSER
Serial/Nibble SelectInput
10 Mbps Serial Operation:
When set high, this input selects a serial data transfer
mode. Manchester encoded transmit and receive data
is exchanged serially with a 10 MHz clock rate on the
least significant bits of the nibble-wide MII data buses,
pin TXD[0] and RXD[0] respectively. This mode is intended for use with the NetPHY-1 device connected to
a device (MAC or Repeater) that has a 10 Mbps serial
interface. Serial operation is not supported in 100 Mbps
mode. For 100 Mbps, this input is ignored.
10 and 100 Mbps Nibble Operation:
When set low, this input selects the MII compliant nib-
ble data transfer mode . Transmit and receive data is e xchanged in nibbles on the TXD[3:0] and RXD[3:0] pins
respectively.
At power-up/reset, the value on this pin is latched into
Register 18, bit 10.
10Am79C873
PRELIMINARY
■
Clock Interface
OSCI/X1
Crystal or Oscillator InputInput
This pin should be connected to a 25 MHz (±50 ppm)
crystal if OSC/XTL=0 or a 25 MHz (±50 ppm) external
TTL oscillator input, if OSC/XTLB=1.
X2
Crystal Oscillator OutputOutput
An external 25 MHz (±50 ppm) crystal should be connected to this pin if OSC/XTL=0, or left unconnected if
OSC/XTL=1.
OSC/XTL
Crystal or Oscillator Selector PinOutput
OSC/XTL=0: An external 25 MHz (±50ppm) crystal
should be connected to X1 and X2 pins.
OSC/XTL=1: An external 25 MHz (±50ppm) oscillator should be connected to X1 and X2 should be left
unconnected.
CLK25M
25 MHz Clock OutputOutput/Z
This clock is derived directly from the crystal circuit.
PHY Address Interface
The PHYAD[4:0] pins provide up to 32 unique PHY
addresses. An address selection of all zeros (00000)
will result in a PHY isolation condition. See the isolate
bit description in the BMCR, address 00.
PHYAD0
PHY Address 0Input
This pin provides PHY address bit 0 for multiple PHY
address applications. The status of this pin is latched
into Register 17, bit 8 during power up/reset.
PHYAD4
PHY Address 4Input
This pin provides PHY address bit 4 for multiple PHY
address applications. The status of this pin is latched
into Register 17, bit 4 during power up/reset.
Miscellaneous
NC
No Connect
These pins are to be left unconnected (floating).
BGREF
Bandgap V oltage ReferenceInput
Connect a 6.01K Ω, 1% resistor between this pin and
the BGRET pin to provide an accurate current reference for the NetPHY-1 device.
BGRET
Bandgap Voltage Reference ReturnInput
This is the return pin for 6.01K Ω resistor connection.
TRIDRV
Tri-State Digital OutputInput
When set high, all digital output pins are set to a high
impedance state, and I/O pins, go to input mode.
RESET
ResetInput
This pin is the active low input that initializes the NetPHY1 device. It should remain low for 30 ms after VCC has
stabilized at 5 Vdc (nominal) before it transitions high.
TESTMODE
Test Mode Control PinInput
TESTMODE=0: Normal operating mode.
TESTMODE=1: Enable test mode.
PHYAD1
PHY Address 1Input
This pin provides PHY address bit 1 for multiple PHY
address applications. The status of this pin is latched
into Register 17, bit 7 during power up/reset.
PHYAD2
PHY Address 2Input
This pin provides PHY address bit 2 for multiple PHY
address applications. The status of this pin is latched
into Register 17, bit 6 during power up/reset.
PHYAD3
PHY Address 3Input
This pin provides PHY address bit 3 for multiple PHY
address applications. The status of this pin is latched
into Register 17, bit 5 during power up/reset.
Am79C87311
Power and Ground Pins
The power (VCC) and ground (GND) pins of the NetPHY-1 device are grouped in pairs of two categories Digital Circuitry Power/Ground Pairs and Analog Circuitry Power/Ground Pair.
DGND
Digital Logic GroundPower
These pins are the digital supply pairs.
DVCC
Digital Logic Power SupplyPower
These pins are the digital supply pairs.
AGND
Analog Circuit GroundPower
These pins are the analog circuit supply pairs.
AVCC
Analog Circuit Power SupplyPower
These pins are the analog circuit supply pairs.
PRELIMINARY
FUNCTIONAL DESCRIPTION
The NetPHY-1 Fast Ethernet single-chip transceiver,
provides the functionality as specified in the IEEE
802.3u standard, integrates complete 100BASE-FX,
100BASE-TX modules and a complete 10BASE-T
module. The NetPHY-1 device provides a Media Independent Interface (MII) as defined in the IEEE 802.3u
standard (Clause 22).
MII Interface
Carrier
Sense
The NetPHY-1 device performs all Physical Coding
Sublayer (PCS), Physical Media Access (PMA),
Twisted Pair Physical Medium Dependent (TP-PMD)
sublayer, 10BASE-T Encoder/Decoder, and Twisted
Pair Media Access Unit (TPMAU) functions. Figure 1
shows the major functional blocks implemented in the
NetPHY-1 device.
100Base
Transmitter
100Base
Receiver
10Base-T
Tranceiver
Collision
Detection
Auto
Negotiation
MII Serial
Management
Interface
Figure 1.Functional Block Diagram
MII Interface
The purpose of the MII interface is to provide a simple,
easy to implement connection between the MAC Reconciliation layer and the PHY. The MII is designed to
make the differences between various media transparent to the MAC sublayer.
The MII consists of a nibble wide receive data bus, a
nibble wide transmit data bus , and control signals to f acilitate data transfers between the PHY and the Reconciliation layer.
■ TXD (transmit data) is a nibble (4 bits) of data that
are driven by the reconciliation sublayer synchronously with respect to TX_CLK. For each TX_CLK
period which TX_EN is asserted, TXD (3:0) are accepted for transmission by the PHY.
■ TX_CLK (transmit clock) output to the MAC reconciliation sublay er is a continuous clock that pro vides
the timing reference for the transfer of the TX_EN,
TXD, and TX_ER signals.
22164A-3
■ TX_EN (transmit enable) input from the MAC reconciliation sublay er to indicate nibbles are being presented on the MII for transmission on the physical
medium. TX_ER (transmit coding error) transitions
synchronously with respect to TX_CLK. If TX_ER is
asserted for one or more clock periods, and TX_EN
is asserted, the PHY will emit one or more symbols
that are not part of the valid data delimiter set somewhere in the frame being transmitted.
■ RXD (receive data) is a nibble (4 bits) of data that
are sampled by the reconciliation sublayer synchronously with respect to RX_CLK. For each
RX_CLK period which RX_DV is asserted, RXD
(3:0) are transferred from the PHY to the MAC
reconciliation sublayer.
■ RX_CLK (receive clock) output to the MA C reconciliation sublayer is a continuous clock that provides
the timing reference for the transfer of the RX_DV,
RXD, and RX_ER signals.
12Am79C873
PRELIMINARY
■ RX_D V (receive data valid) input from the PHY to indicate the PHY is presenting recovered and decoded nibbles to the MAC reconciliation sub lay er . To
interpret a receive frame correctly by the reconciliation sublayer, RX_DV must encompass the frame
starting no later than the Star t-of-Frame delimiter
and excluding any End-Stream delimiter.
■ RX_ER (receive error) transitions synchronously
with respect to RX_CLK. RX_ER will be asserted
TXD
CRS
TXD
IDLE
SSD
J/K
PreambleSFDData
Preamble
SFD
for 1 or more clock periods to indicate to
the reconciliation sublayer that an error was
detected somewhere in the frame being transmitted from the PHY to the reconciliation sublayer.
■ CRS (carrier sense) is asserted by the PHY when
either the transmit or receive medium is non-idle and
deasserted by the PHY when the transmit and receive
medium are idle. Figure 2 depicts the behavior of CRS
during 10BASE-T and 100BASE-TX transmission.
100Base-TX
Data
ESD
T/R
EFD
IDLE
CRS
Figure 2.Carrier Sense during 10BASE-T and 100BASE-TX Transmission
100BASE Operation
The 100BASE transmitter receives 4-bit nibble data
clocked in at 25 MHz at the MII and outputs a scrambled 5-bit encoded MLT-3 signal to the media at 100
Mbps. The on-chip clock circuit converts the 25 MHz
clock into a 125 MHz clock for internal use.
The IEEE 802.3u specification defines the Media Independent Interface. The interface specification defines a
dedicated receive data bus and a dedicated transmit
data bus.
10Base-T
22164A-4
These two busses include various controls and signal
indications that facilitate data transfers between the
NetPHY-1 device and the Reconciliation layer.
100BASE T ransmit
The 100BASE transmitter consists of the functional
blocks shown in Figure 3. The 100BASE transmit section converts 4-bit synchronous data provided by the
MII to a scrambled MLT-3 125 million symbols per second serial data stream.
The block diagram in Figure 3 provides an overview of
the functional blocks contained in the transmit section.
The transmitter section contains the following functional blocks:
■ 4B5B Encoder
■ Scrambler
■ Parallel-to-Serial Converter
■ NRZ-to-NRZI Converter
■ PECL Driver (For FX Operation)
■ NRZI to MLT-3 (For TX Operation)
■ MLT-3 Driver (For TX Operation)
4B5B Encoder
The 4B5B encoder converts 4-bit (4B) nibble data generated by the MAC Reconciliation Layer into a 5-bit
(5B) code group for transmission (see Table 1). This
conversion is required f or control and pack et data to be
Carrier
Sense
Auto-
Negotiation
22164A-5
combined in code groups. The 4B5B encoder substitutes the first 8 bits of the MAC preamble with a J/K
code-group pair (11000 10001) upon transmit.
The 4B5B encoder continues to replace subsequent
4B preamble and data nibbles with corresponding 5B
code-groups. At the end of the transmit packet, upon
the deassertion of the Transmit Enable signal from the
MAC Reconciliation lay er , the 4B5B encoder injects the
T/R code-group pair (01101 00111) indicating end of
frame. After the T/R code-group pair , the 4B5B encoder
continuously injects IDLEs into the transmit data
stream until Transmit Enable is asserted and the next
transmit packet is detected.
The NetPHY-1 device includes a Bypass 4B5B conversion option within the 100BASE-TX transmitter for support of applications like 100 Mbps repeaters which do
not require 4B5B conversion.
the twisted pair cable in 100BASE-TX operation. By
scrambling the data, the total energy presented to the
cable is randomly distributed over a wide frequency
range. Without the scrambler, energy levels on the
cable could peak beyond FCC limitations at frequencies related to repeated 5B sequences like continuous
transmission of IDLE symbols. The scrambler output is
combined with the NRZ 5B data from the code-group
encoder via an XOR logic function. The result is a
scrambled data stream with sufficient randomization to
decrease radiated emissions at critical frequencies.
Since EMI is not a concern in a fiber application, the
scrambler is bypassed in 100BASE-FX.
Parallel-to-Serial Converter
The Parallel-to-Serial Converter receives parallel 5B
scrambled data from the scrambler and serializes it
(i.e., converts it from a parallel to a serial data stream).
The serialized data stream is then presented to the
NRZ-to-NRZI Encoder block
NRZ-to-NRZI Converter
After the transmit data stream has been scrambled and
serialized, the data must be NRZI encoded for compatibility with the TP-PMD standard for 100BASE-TX transmission over Category-5 unshielded twisted pair cable.
The scrambler is required to control the radiated emissions (EMI) by spreading the transmit energy across
the frequency spectrum at the media connector and on
PECL Driver For 100BASE-FX
The PECL driver accepts NRZI coded data and converts
it to PECL signal levels f or transmission over fiber media.
The output pair is a differential pseudo ECL (PECL) interface designed to connect directly to a standard fiber
optic PMD. The differential driver for the FXTD± is current mode and is designed to drive resistive termination
in a complementary mode. The FXTD± pins are incapable of sourcing current, this implies that VOH must
be set by the ratios of the Thevenin termination resistors for each of the lines. RIOH is a pull-up resistor connected from the FXTD± output to VCC. RIOL is a pulldown resistor connected from the FXTD± output to
ground. RIOH and RIOL are electrically in parallel from
an AC standpoint. A target impedance of 50 Ω is
needed for the transmission line impedance. A value of
62 Ω for RIOH and a value of 300 Ω for RIOL will yield
a Thevenin equivalent characteristic impedance of
49.7 Ω and a VOH value of VCC-.88 volts, compatible
with PECL circuits. VOL is required to be VDD-1.81 or
greater. A sink current of 19 milli-amps (mA) would
achieve this through the output termination resistors.
MLT-3 Converter
The ML T-3 conv ersion is accomplished by converting the
data stream output from the NRZI encoder into two binary data streams with alternately phased logic
one events .
Am79C87315
PRELIMINARY
MLT-3 Driver
The two binary data streams created at the MLT -3 converter are fed to the twisted pair output driver which
converts these streams to current sources and alternately drives either side of the transmit transformer primary winding resulting in a minimal current MLT-3
signal. Refer to Figure 4 for the block diagram of the
MLT-3 converter.
100BASE Receiver
The 100BASE receiver contains several function
blocks that conv ert the scrambled 125 Mbps serial data
to synchronous 4-bit nibble data that is then provided to
the MII.
The receive section contains the following functional
blocks:
D
Q
Q
CK
Binary plus
■ Signal Detect
■ Adaptive Equalization
■ MLT-3-to-Binary Decoder
■ Clock Recovery Module
■ NRZI -o-NRZ Decoder
■ Serial-to-Parallel Converter
■ Descrambler
■ Code Group Alignment
■ 4B5B Decoder
100BASE-TX Signal Detect
The signal detect function meets the specifications mandated by the ANSI XT12 TP-PMD 100BASE-TX standards for both voltage thresholds and timing parameters .
Binary In
Binary minus
Binary In
MLT-3
Figure 4.MLT-3 Converter Block Diagram
100BASE-FX Signal Detect
The NetPHY-1 device accepts signal detect information
on the FXSD pin at PECL signal levels from the FX
Optical Module.
Adaptive Equalization
When transmitting data at high speeds over copper
twisted pair cable, attenuation based on frequency becomes a concern. In high speed twisted pair signaling,
the frequency content of the transmitted signal can
vary greatly during normal operation based on the randomness of the scrambled data stream. This variation
Common
Driver
MLT-3
22164A-6
in signal attenuation caused by frequency variations
must be compensated for to ensure the integrity of the
received data.
In order to ensure quality transmission when employing
MLT-3 encoding, the compensation must be able to
adapt to various cable lengths and cable types depending on the installed environment. The selection of long
cable lengths for a given implementation, requires significant compensation which will be over-kill in a situation that includes shorter, less attenuating cable
lengths. Conv ersely, the selection of short or intermediate cable lengths requiring less compensation will
16Am79C873
PRELIMINARY
cause serious under-compensation for longer length
cables. Therefore, the compensation or equalization
must be adaptive to ensure proper conditioning of the
received signal independent of the cable length.
PECL Receiver
The PECL receiver accepts PECL signal-level data
from the FX Optical Module and presents it to the Clock
Recovery Module.
MLT-3-to-NRZI Decoder
The NetPHY-1 device decodes the MLT-3 information
from the Digital Adaptive Equalizer into NRZI data. The
relationship between NRZI and MLT-3 data is shown in
Figure 4.
Clock Recovery Module
The Clock Recovery Module accepts NRZI data from
the MLT-3-to-NRZI decoder or the PECL Receiver. The
Clock Recovery Module locks onto the data stream and
extracts the 125 MHz reference clock. The extracted
and synchronized clock and data are presented to the
NRZI-to-NRZ Decoder.
NRZI-to-NRZ Decoder
The transmit data stream is required to be NRZI encoded in for compatibility with 100BASE transmission
over. This con version process must be reversed on the
receive end. The NRZI-to-NRZ decoder, receives the
NRZI data stream from the Clock Recovery Module
and converts it to a NRZ data stream to be presented
to the Serial to Parallel conversion block.
Serial-to-Parallel Converter
The Serial-to-Parallel Converter receives a serial data
stream from the NRZI-to-NRZ converter, and converts
the data stream to parallel data to be presented to the
descrambler.
Descrambler
Because of the scrambling process required to control
the radiated emissions of transmit data streams, the receiver must descramble the receive data streams. The
descrambler receives scrambled parallel data streams
from the Serial to Parallel converter, descrambles the
data streams, and presents the data streams to the
Code Group alignment block.
Note: The scrambler is bypassed for 100BASE-FX
operation.
Code Group Alignment
The Code Group Alignment block receives unaligned
5B data from the descrambler and converts it into 5B
code group data. Code Group Alignment occurs after
the J/K is detected, and subsequent data is aligned on
a fixed boundary.
4B5B Decoder
The 4B5B Decoder functions as a look-up table that
translates incoming 5B code groups into 4B (Nibble)
data. When receiving a frame, the first two 5-bit code
groups received are the start-of-frame delimiter (J/K
symbols). The J/K symbol pair is stripped and two nibbles of preamble pattern are substituted. The last two
code groups are the end-of-frame delimiter (T/R symbols).The T/R symbol pair is also stripped from the nibble presented to the Reconciliation layer.
10BASE-T Operation
The 10BASE-T transceiver is IEEE 802.3u compliant.
When the NetPHY-1 device is operating in 10BASE-T
mode, the coding scheme is Manchester. Data processed for transmit is presented to the MII interface in
nibble format, converted to a serial bit stream, then
Manchester encoded. When receiving, the Manchester
encoded bit stream is decoded and converted into nibble format for presentation to the MII interface.
Collision Detection
For Half Duplex oper ation, a collision is detected when
the transmit and receive channels are active simultaneously. When a collision has been detected, it will be
reported by the COL signal on the MII interface. Collision detection is disabled in Full Duplex operation.
Carrier Sense
Carrier Sense (CRS) is asserted in Half Duplex operation during transmission or reception of data. During
Full Duplex mode, CRS is asserted only during
receive operations.
Auto-Negotiation
The objective of Auto-Negotiation is to pro vide a means
to exchange information between segment linked devices and to automatically configure both devices to
take maximum advantage of their abilities. It is important to note that Auto-Negotiation does not test the link
segment characteristics. The A uto-Negotiation function
provides a means for a device to advertise supported
modes of operation to a remote link partner, acknowledge the receipt and understanding of common modes
of operation, and to reject un-shared modes of operation. This allows devices on both ends of a segment to
establish a link at the best common mode of operation.
If more than one common mode exists between the two
devices, a mechanism is provided to allow the devices
to resolve to a single mode of operation using a predetermined priority resolution function.
Auto-Negotiation also provides a parallel detection
function for devices that do not support the Auto-Negotiation feature. During Parallel detection there is no exchange of configuration information, instead, the
receive signal is examined. If it is discovered that the
signal matches a technology that the receiving device
Am79C87317
PRELIMINARY
supports, a connection will be automatically established using that technology. This allows devices that
do not support Auto-Negotiation but support a common
mode of operation to establish a link.
MII Serial Management
The MII serial management interface consists of a data
interface, basic register set, and a serial management
interface to the register set. Through this interface it is
possible to control and configure multiple PHY devices ,
get status and error information, and determine the
type and capabilities of the attached PHY device(s).
The NetPHY-1 devices management functions correspond to MII specification for IEEE 802.3u-1995
(Clause 22) for registers 0 through 6 with vendor-specific registers 16,17, and 18.
In read/write operation, the management data frame is
64-bits long and starts with 32 contiguous logic one bits
(preamble) synchronization clock cycles on MDC. The
Start of Frame Delimiter (SFD) is indicated by a <01>
pattern followed by the operation code (OP):<10> indicates Read operation and <01> indicates Write operation. For read operation, a 2-bit tur naround (TA) filing
between Register Address field and Data field is provided for MDIO to avoid contention. Following the turnaround time, 16-bit data is read from or written onto
management registers.
Serial Management Interface
The serial control interface uses a simple two-wired serial interface to obtain and control the status of the physical layer through the MII interface. The serial control
interface consists of Management Data Clock (MDC),
and Management Data Input/Output (MDI/O) signals.
The MDIO pin is bidirectional and may be shared by up
to 32 devices.
OthersReservedReserved For Future Use-Do Not Read/Write To These Registers
Key to Default
In the register description that follows, the default column takes the form:
<Reset Value>, <Access Type> / <Attribute(s)>
Where
<Reset V alue>:
1Bit set to logic one
0Bit set to logic zero
XNo default value
(Pin No.)Value latched in from pin number at reset
<Access Type>:
RO = Read only
RW = Read/Write
<Attribute (s)>:
SC = Self clearing
P = Value permanently set
LL = Latching low
LH = Latching high
Am79C87319
PRELIMINARY
Basic Mode Control Register (BMCR) Register 0
BitBit NameDefaultDescription
Reset:
1=Software reset
0=Normal operation
0.15Reset0, RW/SC
0.14Loopback0, RW
0.13Speed Selection1, RW
When set this bit configures the PHY status and control registers to their
default states. This bit will return a value of one until the reset process is
complete.
Loopback:
Loopback control register
1=Loopback enabled
0=Normal operation
When in 100M operation is selected, setting this bit will cause the
descrambler to lose synchronization. A 720ms “dead time” will occur
before any valid data appears at the MII receive outputs.
Speed Select:
1=100 Mbps
0=10 Mbps
Link speed may be selected either by this bit or by Auto-Negotiation if bit
12 of this register is set. When Auto-Negotiation is enabled, this bit will
return Auto-Negotiation link speed.
0.12
0.11Power Down0, RW
0.10Isolate
Auto-Negotiation
Enable
1, RW
(PHYAD=
00000),
RW
Auto-Negotiation Enable:
1= Auto-Negotiation enabled:
0= Auto-Negotiation disabled:
When auto-Negotiation is enabled bits 8 and 13 will contain the Auto-
Negotiation results. When Auto-Negotiation is disabled bits 8 and 13 will
determine the duplex mode and link speed.
Power Down:
1=Power Down
0=Normal Operation
Setting this bit will power down the NetPHY-1 device with the exception of
the crystal oscillator circuit.
Isolate:
1= Isolate
0= Normal Operation
When this bit is set the data path will be isolated from the MII interface.
TX_CLK, RX_CLK, RX_DV, RX_ER, RXD[3:0], COL and CRS will be
placed in a high impedance state. The management interface is not
effected by this bit. When the PHY Address is set to 00000 the isolate bit
will be set upon power-up/reset.
20Am79C873
PRELIMINARY
Basic Mode Control Register (BMCR) Register 0 (Continued)
BitBit NameDefaultDescription
Restart Auto-Negotiation:
1= Restart Auto-Negotiation.
0= Normal Operation
0.9
0.8Duplex Mode1, RW
0.7Collision T est0, RW
Restart Auto-
Negotiation
0, RW/SC
When this bit is set the Auto-Negotiation process is re-initiated. When
Auto-Negotiation is disabled (bit 12 of this register cleared), this bit has no
function and it should be cleared. This bit is self-clearing and will return a
value of 1 until Auto-Negotiation is initiated. The operation of the AutoNegotiation process will not be affected by the management entity that
clears this bit.
Duplex Mode:
1= Full Duplex operation.
0= Normal operation
If Auto-Negotiation is disabled, setting this bit will cause the NetPHY-1
device to operate in Full Duplex mode . When A uto-Negotiation is enabled,
this bit reflects the duplex selected by Auto-Negotiation.
Collision Test:
1= Collision Test enabled.
0= Normal Operation
When set, this bit will cause the COL signal to be asserted in response to
the assertion of TX_EN.
0.6Reserved0, RO
Reserved:
Write as 0, ignore on read.
Am79C87321
PRELIMINARY
Basic Mode Status Register (BMSR) Register 1
BitBit NameDefaultDescription
100BASE-T4 Capable:
1.15100BASE-T40,RO/P
1.14
1.13
100BASE-TX
Full Duplex
100BASE-TX
Half Duplex
1,RO/P
1,RO/P
1=NetPHY-1 device is able to perform in 100BASE-T4 mode.
0=NetPHY-1 device is not able to perform in 100BASE-T4 mode.
100BASE-TX Full Duplex Capable:
1=NetPHY-1 device is able to perform 100BASE-TX in Full Duplex mode.
0=NetPHY-1 device is not able to perform 100BASE-TX in Full Duplex
mode.
100BASE-TX Half Duplex Capable:
1=NetPHY-1 device is able to perform 100BASE-TX in Half Duplex mode.
0=NetPHY-1 device is not able to perform 100BASE-TX in Half Duplex
mode.
1.12
1.11
1.10-1.7Reserved0,RO
1.6
1.5
1.4Remote Fault
10BASE-T
Full Duplex
10BASE-T
Half Duplex
MF Preamble
Suppression
Auto-Negotiation
Complete
1,RO/P
1,RO/P
0,RO
0,RO
0,
RO/LH
10BASE-T Full Duplex Capable:
1=NetPHY-1 device is able to perform 10BASE-T in Full Duplex mode.
0=NetPHY-1 device is not able to perform 10BASE-T in Full Duplex mode.
10BASE-T Half Duplex Capable:
1=NetPHY-1 device is able to perform 10BASE-T in Half Duplex mode.
0=NetPHY -1 de vice is not able to perf orm 10BASE-T in Half Duplex mode.
Reserved:
Write as 0, ignore on read.
MII Frame Preamble Suppression:
1=PHY will accept management frames with preamble suppressed.
0=PHY will not accept management frames with preamble suppressed.
Auto-Negotiation Complete:
1=Auto-Negotiation process completed.
0=Auto-Negotiation process not completed.
Remote Fault:
1= Remote fault condition detected (cleared on read or by a chip reset).
Fault criteria and detection method is NetPHY-1 device implementation
specific. This bit will set after the RF bit in the ANLPAR (bit 13, register
address 05) is set.
0= No remote fault condition detected.
1.3
1.2Link Status0,RO/LL
Auto-Negotiation
Ability
1,RO/P
Auto Configuration Ability:
1=NetPHY-1 device able to perform Auto-Negotiation.
0=NetPHY-1 device not able to perform Auto-Negotiation.
Link Status:
1=Valid link established (for either 10 Mbps or 100 Mbps operation).
0=Link not established.
The link status bit is implemented with a latching function, so that the
occurrence of a link failure condition causes the Link Status bit to be
cleared and remain cleared until it is read via the management interface.
22Am79C873
PRELIMINARY
Basic Mode Status Register (BMSR) Register 1
BitBit NameDefaultDescription
Jabber Detect:
1=Jabber condition detected.
1.1Jabber Detect
0,
RO/LH
0=No jabber condition detected.
This bit is implemented with a latching function. Once Jabber conditions
are detected this bit will remain set until a read operation is completed
through a management interface or a NetPHY-1 device reset. This bit
works only in 10 Mbps mode.
Unique Identifier (OUI), a vendor's model number,
and a model revision number. The IEEE assigned OUI
is 00606E.
The PHY Identifier Registers 1 and 2 work together in
a single identifier of the NetPHY-1 device. The Identifier
consists of a concatenation of the Organizationally
BitBit NameDefaultDescription
OUI Most Significant Bits:
2.15-2.0OUI_MSB<0181H>
This register stores bits 3 - 18 of the OUI (00606E) to bits 15 - 0 of this
register, respectiv ely. The most significant tw o bits of the OUI are ignored
(the IEEE standard refers to these as bit 1 and 2).
PHY Identifier Register 2 (PHYIDR2) Register 3
BitBit NameDefaultDescription
OUI Least Significant Bits:
3.15-3.10OUI_LSB<101110>,RO/P
Bits 19 - 24 of the OUI (00606E) are mapped to bits 15 - 10 of this register,
respectively .
3.9-3.4VNDR_MDL<000000>,R O/P
3.3-3.0MDL_REV<0001>,RO/P
Vendor Model Number:
Six bits of the vendor model number mapped to bits 9 - 4 (most significant
bit to bit 9).
Model Revision Number:
Four bits of the vendor model re vision number mapped to bits 3 - 0 (most
significant bit to bit 3).
This register contains the advertised abilities of the NetPHY-1 device as they will be transmitted to link partners during Auto-Negotiation.
BitBit NameDefaultDescription
Next Page Indication:
0=No next page available
4.15NP0,RO/P
4.14ACK0,RO
4.13RF0, RW
1=Next page available
The NetPHY-1 device does not support the next page function. This bit is
permanently set to 0
Acknowledge:
1=Link partner ability data reception acknowledged.
0=Not acknowledged.
The NetPHY-1 device's Auto-Negotiation state machine will automatically
control this bit in the outgoing FLP bursts and set it at the appropriate time
during the Auto-Negotiation process. Software should not attempt to write
to this bit.
Flow Control Support:
1=Controller chip supports flow control ability.
0=Controller chip does not support flow control ability.
100BASE-T4 Support:
1=100BASE-T4 supported by the local device.
0=100BASE-T4 not supported.
The NetPHY-1 device does not support 100BASE-T4 so this bit is
permanently set to 0.
100BASE-TX Full Duplex Support:
1=100BASE-TX Full Duplex supported by the local device.
0=100BASE-TX Full Duplex not supported.
100BASE-TX Support:
1=100BASE-TX supported by the local device.
0=100BASE-TX not supported.
10BASE-T Full Duplex Support:
1=10BASE-T Full Duplex supported by the local device.
0=10BASE-T Full Duplex not supported.
10BASE-T Support:
1=10BASE-T supported by the local device.
0=10BASE-T not supported.
Protocol Selection Bits:
4.4-4.0Selector<00001>, RW
These bits contain the binary encoded protocol selector supported by this
node.
<00001> indicates that this device supports IEEE 802.3 CSMA/CD.
24Am79C873
PRELIMINARY
Auto-Negotiation Link Partner Ability
Register (ANLPAR) - Register 5
This register contains the advertised abilities of the link partner as they are received during Auto-Negotiation.
BitBit NameDefaultDescription
Next Page Indication:
5.15NP0, RO
5.14ACK0, RO
5.13RF0, RO
0= Link partner, no next page available.
1= Link partner, next page available.
Acknowledge:
1=Link partner ability data reception acknowledged.
0=Not acknowledged.
The NetPHY-1 device's Auto-Negotiation state machine will automatically
control this bit from the incoming FLP bursts. Software should not attempt
to write to this bit.
Remote Fault:
1=Remote fault indicated by link partner.
0=No remote fault indicated by link partner.
5.12-5.10Reserved0, RO
5.9T40, RO
5.8TX_FDX0, RO
5.7TX_HDX0, RO
5.610_FDX0, RO
5.510_HDX0, RO
5.4-5.0Selector<00000>, RO
Reserved:
Write as 0, ignore on read.
100BASE-T4 Support:
1=100BASE-T4 supported by the link partner.
0=100BASE-T4 not supported by the link partner.
100BASE-TX Full Duplex Support:
1=100BASE-TX Full Duplex supported by the link partner.
0=b 100BASE-TX Full Duplex not supported by the link partner.
100BASE-TX Support:
1=100BASE-TX Half Duplex supported by the link partner.
0=100BASE-TX Half Duplex not supported by the link partne.r
10BASE-T Full Duplex Support:
1=10BASE-T Full Duplex supported by the link partner.
0=10BASE-T Full Duplex not supported by the link partner.
10BASE-T Support:
1=10BASE-T Half Duplex supported by the link partner.
0=10BASE-T Half Duplex not supported by the link partner.
Protocol Selection Bits:
Link partners binary encoded protocol selector.
Local Device Parallel Detection Fault:
PDF=1: A fault detected via parallel detection function.
PDF=0: No fault detected via parallel detection function.
Link Partner Next Page Able:
LP_NP_ABLE=1: Link partner, next page available.
LP_NP_ABLE=0: Link partner, no next page.
Local Device Next Page Able:
NP_ABLE=1: NetPHY-1 device, next page available.
NP_ABLE=0: NetPHY-1 device, no next page.
NetPHY-1 device does not support this function, so this bit is always 0.
New Page Received:
A new link code word page received. This bit will be automatically cleared
when the register (Register 6) is read by management.
Link Partner Auto-Negotiation Able:
LP_AN_ABLE=1 indicates that the link partner supports AutoNegotiation.
1=4B5B encoder and 5B4B decoder function bypassed.
0=Normal 4B5B and 5B4B operation The value of the pin is latched into
this bit at power-up/reset.
Bypass Scrambler/Descrambler Function:
1=Scrambler and descrambler function bypassed.
0=Normal scrambler and descrambler operation.
The value of the input pin is latched into this bit at power-up/reset.
Bypass Symbol Alignment Function:
1= Receive functions (descrambler, symbol alignment and symbol
decoding functions) bypassed. Transmit functions (symbol encoder and
scrambler) bypassed.
0= Normal operation.
The value of the BPALIGN input pin is latched into this bit at power-up/
reset.
16.12Reserved0, RW
16.11REPEATERPin 94, RW
16.10TX1, RW
16.9UTP1, RW
16.8CLK25MDIS0, RW
Reserved:
This bit must be set as 0.
Repeater/Node Mode:
1=Repeater mode.
0=Node mode.
In Repeater mode, the Carrier Sense (CRS) output from the NetPHY-1
device will be asserted only by receive activity. In NODE mode, or a mode
not configured for Full Duplex operation, CRS will be asserted by either
receive or transmit activity.
The value of the RPTR/NODE input pin is latched into this bit at power-up
reset.
100BASE-TX or FX Mode Control:
1=100BASE-TX operation.
0=100BASE-FX operation.
UTP Cable Control:
1=The media is a UTP cable, 0=STP.
CLK25M Disable:
1=CLK25M output clock signal tri-stated.
0=CLK25M enabled.
This bit should be set to 1 to disable the 25 MHz output and reduce ground
bounce and power consumption. For applications requiring the CLK25M
output, set this bit to 0.
16.7F_LINK_1001, RW
16.6Reserved0, RW
Force Good Link in 100 Mbps:
1=Normal 100 Mbps operation.
0=Force 100 Mbps good link status.
This bit is useful for diagnostic purposes.
0= Link LED output configured to indicate link status only.
16.5LINKLED_CTL0, RW
16.4FDXLED_MODE0, RW
16.3SMRST0, RW
16.2MFPSC0, RW
1= Link LED output configured to indicate traffic status: When the link
status is OK, the LED will be on. When the chip is in transmitting or
receiving, it flashes.
FDXLED Mode Select:
1= FDXLED output configured to indicate polarity in 10BASE-T mode.
0= FDXLED output configured to indicate Full DuplexFull Duplex mode
status for 10 Mbps and 100 Mbps operation.
Reset State Machine:
When this bit is set to 1, all state internal machines will be reset. This bit
will clear after reset is completed.
MF Preamble Suppression Control:
1= MF preamble suppression on.
0= MF preamble suppression off.
MII frame preamble suppression control bi.t
16.1SLEEP0, RW
16.0RLOUT0, RW
Sleep Mode:
Writing a 1 to this bit will cause NetPHY -1 de vice to enter Sleep mode and
power down all circuits except the oscillator and cloc k generator circuit. To
exit Sleep mode, write 0 to this bit position. The prior configuration will be
retained when the sleep state is terminated, but the state machine will be
reset.
Remote Loopout Control:
When this bit is set to 1, the received data will loop out to the transmit
channel. This is useful for bit error rate testing.
28Am79C873
PRELIMINARY
AMD Specified Configuration and Status
Register (DSCSR) - Register 17
BitBit NameDefaultDescription
100 M Full Duplex Operation:
17.15100FDX1, RO
17.14100HDX1, RO
17.1310FDX1, RO
17.1210HDX1, RO
After Auto-Negotiation is completed, the results will be written to this bit.
A 1 in this bit position indicates 10 0M Full Duplex operation. The software
can read bits [15:12] to determine which mode is selected after AutoNegotiation. This bit is invalid when Auto-Negotiation is disabled.
100 M Half Duplex Operation:
After Auto-Negotiation is completed, the results will be written to this bit.
A 1 in this bit position indicates 100 M Half Duplex operation. The software
can read bits [15:12] to determine which mode is selected after AutoNegotiation. This bit is invalid when Auto-Negotiation is disabled.
10 M Full Duplex Operation:
After Auto-Negotiation is completed, the results will be written to this bit.
A 1 in this bit position indicates 10 M Full Duplex operation. The software
can read bits [15:12] to determine which mode is selected after AutoNegotiation. This bit is invalid when Auto-Negotiation is disabled.
10 M Half Duplex Operation:
After Auto-Negotiation is completed, the results will be written to this bit.
A 1 in this bit position indicates 10M Half Duplex operation. The software
can read bits [15:12] to determine which mode is selected after AutoNegotiation. This bit is invalid when Auto-Negotiation is disabled.
17.11-
17.10
17.8-17.4PHYAD[4:0](PHYAD), RW
BitBit NameDefaultDescription
17.3-17.0ANMB[3:0]0, RO
Reserved0, RW
Reserved:
Write as 0, ignore on read.
PHY Address Bit 4:0:
The values of the PHYAD[4:0] pins are latched to this register at power-
up/reset. The first PHY address bit tr ansmitted or received is the MSB (bit
4). A station management entity connected to multiple PHY entities m ust
know the appropriate address of each PHY. A PHY address of <00000>
will cause the isolate bit of the BMCR (bit 10, Register Address 00) to be
set.
Auto-Negotiation Monitor Bits:
These bits are for debug only. The Auto-Negotiation status will be written
to these bits.
b3 b2b1b0
0000In IDLE state
0001Ability match
0010Acknowledge match
0011Acknowledge match fail
0100Consistency match
0101Consistency match fail
0110Parallel detect signal_link_ready
0111Parallel detect signal_link_ready fail
1000Auto-Negotiation completed successfully
Link Pulse Enable:
1=Transmission of link pulses enabled.
0=Link pulses disabled, good link condition forced.
This bit is valid only in 10 Mbps operation.
Heartbeat Enable:
1=Heartbeat function enabled.
0=Heartbeat function disabled.
When the NetPHY-1 device is configured for Full Duplex operation, this bit
will be ignored (the collision/heartbeat function is invalid in Full Duplex
mode). The initial state of this bit is the inv erse value of RPTR/NODE input
pin at power on reset.
Reserved:
Write as 0, ignore on read.
Jabber Enable:
1= Jabber function enabled.
0= Jabber function disabled.
Enables or disables the Jabber function when the NetPHY-1 device is in
10BASE-T Full Duplex or 10BASE-T Transceiver Loop-back mode.
10BASE-T Serial Mode:
1=10BASE-T serial mode selected.
0=10BASE-T nibble mode selected.
The value on the 10BTSER input pin is latched into this bit at power-up/
rese.t
Serial mode not supported for 100 Mbps operation.
18.9-18.1Reserved0, RO
18.0POLR0, RO
Reserved:
Write as 0, ignore on read.
Polarity Reversed:
When this bit is set to 1, it indicates that the 10M cable polarity is reversed.
This bit is set and cleared by 10BASE-T module automatically.
30Am79C873
PRELIMINARY
ABSOLUTE MAXIMUM RATINGS
Storage Temperature . . . . . . . . . . . . –65°C to +150°C
Ambient Temperature
with Power Applied. . . . . . . . . . . . . . . . –0°C to +70°C
Supply V oltage
with Respect to Ground . . . . . . . . . -4.75 V to +5.25 V
DC Input Voltage (VIN) . . . . . . . . –0.5 V to VCC +0.5 V
DC Output or I/O Pin Voltage (V
Stresses above those listed under Absolute Maximum
Ratings may cause permanent device failure. Functionality
at or above these limits is not implied. Exposure to Absolute Maximum Ratings for extended periods may affect
device reliability.
). . . . .–0.5 V to
OUT
VCC +0.5 V
OPERATING RANGES
Commercial (C) Devices
Ambient Temperature (TA)
Operating in Free Air. . . . . . . . . . . . . . . .0°C to +70°C
Supply V oltage (VCC)
with Respect to Ground . . . . . . . . +4.75 V to +5.25 V
Operating ranges define those limits between which the
functionality of the device is guaranteed.
Figure 14.MDIO Timing when OUTPUT by STA Timing Diagram
MDIO Timing when OUTPUT by NetPHY-1 Device
MDC
0 - 300 ns
t
3
MDIO
10 ns
(Min)
t
t
1
2
22164A-16
22164A-17
Figure 15.MDIO Timing when OUTPUT by NetPHY-1 Timing Diagram
MII Timing Parameters
SymbolParameterConditionsMinTypical MaxUnit
t1MDIO Setup Before MDCWhen OUTPUT By STA10--ns
t2MDIO Hold After MDCWhen OUTPUT By STA10--ns
t3MDC To MDIO Output Delay
When OUTPTU By
NetPHY-1 device
0-100ns
Am79C87339
PRELIMINARY
32
31
OSC/XTLB
OSCGND
AGND
AGND
AGND
C18
18 pF
Y1 25M
C19
18 pF
29
30
X1
X2
22164A-18
MAGNETICS SELECTION GUIDE
The NetPHY-1 device requires a 1:1 ratio for both the
receive and the transmit transformers. Refer to Table 2
for transformer requirements. Transformers meeting
these requirements are available from a v ariety of magnetic manufacturers. Designers should test and qualify
all magnetics before using them in an application. The
transformers listed in Table 2 are electrical equivalent,
but may not be pin-to-pin equivalent.
Table 2.Transformer Requirements
ManufacturerPart Number
Bel FuseS558-5999-01
DeltaLF8200, LF8221
Single Port
TG22-3506ND, TD22-
3506G1, TG22-S010ND,
HALO Electronics, Inc.
TG22-S012ND,
TG110-S050N2
Quad P
TG110-6506NX, TG110-
S450NX, TG110-S452NX
ort
CRYSTAL SELECTION GUIDE
A crystal can be used to generate the 25 MHz reference clock instead of a crystal oscillator. An M-TRON
crystal, par t number is 00301-00169, MP-1 Fund, @
25.000000 MHz, ±50 ppm or equivalent may be used.
The crystal must be a fundamental type, parallel resonant. Connect to X1 and X2, shunt each crystal lead
to ground with an 18pf capacitor (see Figure 16).
NPI 6181-37, NPI 6120-30,
Nano Pulse Inc.
Pulse Engineering
ValorST6114, ST6118
YCL20PMT04, 20PMT05
NPI 6120-37
NPI 6170-30
PE-68517, PE-68515,
H1019, H1012 ----Single
Port
H1027, H1028 ---- Dual Port
PE-69037, H1001,
H1036, H1044 ---- Quad