PRELIMINARY draft 2
Sundance Technology
ST201
Fast Ethernet MAC
FEATURES
GENERAL DESCRIPTION
The ST201 is a single-chip, full duplex, 10/
100Mbps Ethernet MAC incorporating a 32-bit PCI
including bus master support. The ST201 is
designed for use in a variety of applications rang-
ing from workstation NICs, networking equipment
such as switches or routers, and other systems uti-
lizing a PCI bus which require network connectivity
to an Ethernet or Fast Ethernet LAN.
•
Single chip 10/100BASE, half or full duplex
Ethernet Media Access Controller
•
•
•
IEEE 802.3u compliant MII
IEEE 802.3x full duplex flow control
PCI Bus master scatter/gather DMA on any
byte boundary
•
•
•
On-chip transmit and receive FIFO buffers
On-chip LED drivers
The ST201 includes a PCI bus interface unit, IEEE
802.3 compliant MAC, transmit and receive FIFO
buffers, IEEE 802.3u compliant MII, serial Electri-
cally EEPROM interface, expansion ROM inter-
face, and LED drivers.
Power management capabilities for ACPI
1.0 compliant systems
The ST201 implements a rich set of control and
status registers. Accessible via the PCI interface,
these registers provide a host system visibility into
the features and operating state of the ST201. Net-
work management statistics are also recorded, and
host access to registers of the PHY device are
facilitated through the ST201’s PCI interface.
•
•
•
WakeOnLAN support
Management statistics gathering
IP multicast receive and filter support using
64 bit hash table
•
•
•
•
•
Receive early interrupt
Transmit polling
The ST201 supports several features for use in
“Green PCs” or systems where control over system
power consumption is desired. The ST201 sup-
ports several power down states, and the ability to
issue a system “wake event” via reception of
unique, user defined Ethernet frames. In addition,
the ST201 can assert a wake event in response to
changes in the Ethernet link status.
Auto pad insertion for short packets
Programmable minimum Inter Packet Gap
Programmable transmit and receive FIFO
watermarks
•
•
•
•
On-chip crystal oscillator
3.3V CMOS with 5V tolerant I/O
0.35mm technology
128-pin PQFP
Publication:
Date:
2
Rev: A
November 1998
See Sundance Technology’s website at www.sundanceti.com for the latest information.
Sundance Technology
ST201
PRELIMINARY draft 2
ORDERING INFORMATION
Sundance products are available in several combinations of packages and operating temperature ranges.
The order number is formed by a combination of the elements below
ST201
K
C
TEMPERATURE RANGE
C=Commercial (0 to +70C)
PACKAGE TYPE
K=Plastic Quad Flat Pack
DEVICE NUMBER/DESCRIPTION
ST201
Fast Ethernet MAC
3
Sundance Technology
PIN DIAGRAM
ST201
PRELIMINARY draft 2
4
Sundance Technology
PIN DESIGNATIONS
ST201
PRELIMINARY draft 2
PIN
NO.
PIN
NO.
PIN
NO.
PIN
PIN NAME
PIN NAME
AD9
PIN NAME
EA2
PIN NAME
NO.
1
VCC (5V)
CBEN3
IDSEL
AD23
33
65
97
RXCLK
RXDV
RXD0
RXD1
RXD2
RXD3
GND (5V)
MDC
2
3
4
5
6
7
8
34
35
36
37
38
39
40
GND (5V)
AD8
66
67
68
69
70
71
72
EA3
EA4
EA5
EA6
EA7
EA8
98
99
CBEN0
AD7
100
101
102
103
104
AD22
AD21
AD6
AD20
AD5
GND (5V)
GND (3.3V)
EA9/
LEDPWRN
9
AD19
AD18
41
42
VDET
AD4
73
74
EA10/
LEDLNKN
105
106
GND (3.3V)
MDIO
10
EA11/
LEDDPLXN
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
AD17
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
VCC (3.3V)
AD3
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
EA12
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
PHYLNKN
VCC (3.3V)
PHYSPDN
VCC (5V)
INTAN
AD16
GND (5V)
EA13/EEDO
EA14/EEDI
EA15/EESK
EECS
CBEN2
VCC (5V)
FRAMEN
IRDYN
GND (5V)
TRDYN
DEVSELN
STOPN
PERRN
SERRN
PAR
GND (5V)
VCC (5V)
AD2
AD1
RSTN
AD0
X25I
PCICLK
GNTN
EWEN
EOEN
GND (3.3V)
ED7/GPIO1
ED6/GPIO0
GND (5V)
ED5
X25O
VCC (5V)
RSTOUT
PHYDPLXN
CLK25
REQN
GND (3.3V)
WAKE
GND (5V)
AD31
CRS
CBEN1
GND (5V)
AD15
COL
AD30
VCC (3.3V)
ED4
TXD3
AD29
TXD2
VCC (3.3V)
AD28
AD14
ED3
TXD1
VCC (5V)
AD13
ED2
TXD0
AD27
ED1
TXEN
AD26
AD12
ED0
GND (5V)
TXCLK
RXER
AD25
AD11
EA0
GND (5V)
AD24
AD10
EA1
TABLE 1: ST201 Pin Designations
5
Sundance Technology
PIN DESCRIPTIONS
ST201
PRELIMINARY draft 2
PIN NAME
PIN TYPE
PIN DESCRIPTION
PCI INTERFACE
RSTN
INPUT
INPUT
Reset, asserted LOW. RSTN will cause the ST201 to reset all of its
functional blocks. RSTN must be asserted for a minimum duration of
10 PCICLK cycles.
PCICLK
PCI Bus Clock. This clock is used to drive the PCI bus interfaces and
the internal DMA logic. All bus signals are sampled on the rising edges
of PCICLK. PCICLK can operate from 0MHz to 33MHz.
GNTN
IDSEL
INTAN
INPUT
PCI Bus Grant, asserted LOW. GNTN signals access to the PCI bus
has been granted to ST201.
INPUT
Initialization Device Select. The IDSEL is used to select the ST201 dur-
ing configuration read and write transactions.
OUTPUT
Interrupt Request, asserted LOW. The ST201 asserts INTAN to
request an interrupt, when any one of the programmed interrupt event
occurs.
WAKE
OUTPUT
Wake Event, assertion level is programmable (see I/O Registers sec-
tion, WakeEvent bit 3). The ST201 asserts WAKE to signal the detec-
tion of a wake event.
REQN
OUTPUT
IN/OUT
Request, asserted LOW. The ST201 asserts REQN to request PCI bus
master operation.
AD[31..0]
PCI Bus Address/Data. Address and data are multiplexed on the AD
pins. The AD pins carry the physical address during the first clock cycle
of a transaction, and carry data during the subsequent clock cycles.
CBEN[3..0]
PAR
IN/OUT
IN/OUT
PCI Bus Command/Byte Enable, asserted LOW. Bus command and
byte enables are multiplexed on the CBEN pins. CBEN specify the bus
command during the address phase transaction, and carry byte
enables during the data phase.
Parity. PCI Bus parity is even across AD[31..0] and CBEN[3..0]. The
ST201 generates PAR during address and write data phases as a bus
master, and during read data phase as a target. It checks for correct
PAR during read data phase as bus master, during every address
phase as a bus slave, and during write data phases as a target.
FRAMEN
IRDYN
IN/OUT
IN/OUT
PCI Bus Cycle Frame, asserted LOW. FRAMEN is an indication of a
transaction. It is asserted at the beginning of the address phase of the
bus transaction and de-asserted before the final transfer of the data
phase of the transaction.
Initiator Ready, asserted LOW. A bus master asserts IRDYN to indi-
cate valid data phases on AD[31..0] during write data phases, indicates
it is ready to accept data during read data phases. A target will monitor
IRDYN.
TABLE 2: ST201 Pin Descriptions
6
Sundance Technology
ST201
PRELIMINARY draft 2
PIN NAME
TRDYN
PIN TYPE
IN/OUT
PIN DESCRIPTION
Target Ready, asserted LOW. A bus target asserts TRDYN to indicate
valid read data phases, and to indicate it is ready to accept data during
write data phases. A bus master will monitor TRDYN.
DEVSELN
IN/OUT
Device Select, asserted LOW. The ST201 asserts DEVSELN when it is
selected as a target during a bus transaction. It monitors DEVSELN for
any target to acknowledge a bus transaction initiated by the ST201.
STOPN
PERRN
IN/OUT
IN/OUT
Stop, asserted LOW. STOPN is driven by the slave target to inform the
bus master to terminate the current transaction.
Parity Error, asserted LOW. The ST201 asserts PERRN when it
checks and detects a bus parity errors. When it is generating PAR out-
put, the ST201 monitors for any reported parity error on PERRN.
SERRN
VDET
OUTPUT
INPUT
System Error, asserted LOW.
Power Detect. The ST201 detects PCI bus power supply loss when
VDET is LOW.
MII INTERFACE
TXD[3..0]
TXEN
OUTPUT
OUTPUT
Transmit Data. This is the 4-bit transmit data, from the transmit MAC to
the physical layer device. TXD[3..0] are synchronized to the TXCLK.
Transmit Enable. When asserted, TXEN indicates to the PHY that
TXD[3..0] carry valid transmit data. TXEN is asserted with the first nib-
ble of the preamble until the last nibble of the frame data. TXEN is syn-
chronous with TXCLK.
TXCLK
INPUT
Transmit Clock. TXCLK is a continuous clock supplied by the PHY to
synchronize the TXD transfer. Nominal rate of TXCLK is 25MHz for
100Mbps PHY and 2.5MHz when the PHY operates at 10Mbps.
RXD[3..0]
RXCLK
INPUT
INPUT
Receive Data. RXD[3..0] is the receive data from the PHY. RXD[3..0]
are synchronized to RXCLK.
Receive Clock. RXCLK provides the timing reference for RXD, RXER,
and RXDV signals. It is supplied by the PHY based on the receive
clock recovery circuit. Nominal rate for RXCLK is 25MHz (for
100Mbps) and 2.5MHz (for 10Mbps).
RXER
RXDV
INPUT
INPUT
Receive Error. RXER is an indication from the PHY when it detects
coding errors, or other types of PHY layer errors during frame data
reception. RXER is synchronous with RXCLK.
Receive Data Valid. RXDV signals valid frame data is present on the
RXD[3..0] pins. The PHY asserts RXDV before the SFD, and de-
asserts it after the last data nibble of the frame. RXDV is synchronous
with RXCLK.
CRS
INPUT
Carrier Sense. CRS is asserted by the PHY to signal a non-idle
medium, with either transmit or receive activity detected. CRS is asyn-
chronous to RXCLK and TXCLK.
TABLE 2: ST201 Pin Descriptions
7
Sundance Technology
ST201
PRELIMINARY draft 2
PIN NAME
COL
PIN TYPE
INPUT
PIN DESCRIPTION
Collision. COL is asserted by the PHY to a signal collision condition is
detected on the physical medium. COL is asynchronous to RXCLK and
TXCLK.
MDC
OUTPUT
IN/OUT
Management Data Clock. MDC is used to synchronize the read and
write operations of MDIO.
MDIO
Management Data Input/Output. MDIO carries management data for
the management port read and write operations.
PHY INTERFACE
PHYLNKN
INPUT
INPUT
PHY Link Status, asserted LOW. PHYLNKN is driven by the physical
layer device. It is asserted to signal a functional link (link up).
PHYDPLXN
PHY Duplex Status, assertion level is programmable (see I/O Regis-
ters, PhyCtrl bit 4). PHYDPLXN is driven by the physical layer device.
It is asserted to indicate a full duplex link, and de-asserted to indicate a
half duplex link. PHYDPLXN is undefined when PHYLNKN is not
asserted.
PHYSPDN
INPUT
PHY Speed Status. PHYSPDN is driven by the physical layer device. It
is asserted to indicate a 100Mbps link, and de-asserted to indicate a
10Mbps link. PHYSPDN is undefined when PHYLNKN is not asserted.
EEPROM INTERFACE
EEDO
EEDI
INPUT
EEPROM Data Output. This pin is connected directly to the data output
of the EEPROM device. (This pin is shared with EA13)
OUTPUT
OUTPUT
EEPROM Data In. This pin is connected directly to the data input of the
EEPROM device. (This pin is shared with EA14)
EESK
EEPROM Serial Clock. EESK is the clock used to synchronize the
EEPROM data access with EEDI and EEDO. It is connected directly to
the clock input of the EEPROM device. (This pin is shared with EA15)
EECS
OUTPUT
EEPROM Chip Select. EECS is asserted by the ST201 to access the
EEPROM. It is connected directly to the chip select input of the
EEPROM device.
EXPANSION ROM INTERFACE
ED[7..0]
IN/OUT
Expansion ROM Data. The ED[7..0] provide data access to the expan-
sion ROM.
EA[15..0]
OUTPUT
Expansion ROM Address. The EA[15..0] carry the address to the
expansion ROM.
EWEN
EOEN
OUTPUT
OUTPUT
Expansion ROM Write Enable.
Expansion ROM Output Enable.
LED DRIVERS
TABLE 2: ST201 Pin Descriptions
8
Sundance Technology
ST201
PRELIMINARY draft 2
PIN NAME
LEDPWRN
PIN TYPE
OUTPUT
PIN DESCRIPTION
Power Status LED. (This pin is shared with EA9). The operation of this
pin varies based on the setting in the I/O Registers, AsicCtrl bit 14 (the
LEDMode bit). In Mode 0, LOW when power is applied, and toggling
when frame transmission is in progress. In Mode 1, this pin is always
LOW when power is applied.
LEDLNKN
OUTPUT
Link Status LED. (This pin is shared with EA10). The operation of this
pin varies based on the setting in the I/O Registers, AsicCtrl bit 14 (the
LEDMode bit). In Mode 0, LOW when a valid link exists, toggling when
frame reception is in progress. In Mode 1, LOW when a valid link
exists, and toggling when either frame transmission or reception is in
progress.
LEDDPLXN
LEDSPDN
OUTPUT
OUTPUT
Duplex Status LED. (This pin is shared with EA11). This pin operates
independently of the I/O Registers, AsicCtrl bit 14 (the LEDMode bit).
This pin is LOW when the PHY is in full duplex mode, and toggles
when collisions are detected.
Speed Status LED. (This pin is shared with EA12). This pin operates
independently of the I/O Registers, AsicCtrl bit 14 (the LEDMode bit).
This pin is LOW when the link speed is 100Mbps, and HIGH when the
link speed is 10Mbps.
MISCELLANEOUS
GPIO0
IN/OUT
IN/OUT
OUTPUT
General Purpose Input/Output. (This pin is shared with ED6)
General Purpose Input/Output. (This pin is shared with ED7)
GPIO1
RSTOUT
Reset Output, assertion level is programmable (see I/O Registers,
AsicCtrl bit 15). The ST201 will assert RSTOUT when it is being reset.
RSTOUT is intended to be used to reset other circuitry on the adapter.
X25I
OSCIN
25MHz Crystal Oscillator Input. The external 25MHz crystal and capac-
itor is connected to the on-chip crystal oscillator circuit through X25I
input. Alternately, X25I can be driven by an external clock source.
X25O
OSCOUT
25MHz Crystal Oscillator Output. The external crystal and capacitor is
also connected to the output of the on-chip crystal oscillator circuit
through X25O. When X25I is driven by an external clock source, X25O
should be left unconnected.
CLK25
OUTPUT
25MHz Clock Output. CLK25 carries the reference clock generated by
the on-chip crystal oscillator. This is a free-running and continuous
clock signal.
POWER AND GROUND
VCC (5V)
POWER
GROUND
POWER
GROUND
+5 volts power supply.
GND (5V)
VCC (3.3V)
GND (3.3V)
+5 volts power return.
+3.3 volts power supply.
+3.3 volts power return.
TABLE 2: ST201 Pin Descriptions
9
Sundance Technology
ST201
PRELIMINARY draft 2
CSMA/CD, allowing data to be transmitted on
demand. An optional flow control mechanism in full
duplex mode is provided via the 802.3x MAC Con-
trol PAUSE function. Additionally, the MAC also
performs the following functions in either half or full
duplex mode:
ACRONYMS AND GLOSSARY
LAN
Local Area Network
MAC
Media Access Control Layer, or a
device implementing the functions
of this layer (a Media Access Con-
troller)
• Optional transmit FCS generation
PCI
Peripheral Component Interface
Network Interface Cards
First In First Out
• Padding to the minimum legal frame size
• Preamble and SFD generation
• Preamble and SFD removal
• Receive frame FCS checking and optional FCS
stripping
NIC
FIFO
MII
Media Independent Interface
EPROM
Erasable Programmable Read
Only Memory
• Receive frame destination address matching
• Support for multicast and broadcast frame recep-
tion or rejection (via filtering)
• Selective InterFrame Gap to avoid capture effect
• MAC Loopback
EEPROM
Electrically Erasable Programma-
ble Read Only Memory
LED
PHY
Light Emitting Diode
The MAC is responsible for generation of hardware
signals to update the internal statistics counters.
Physical Layer, or device imple-
menting functions of the Physical
Layer
MEDIA INDEPENDENT INTERFACE
CSMA/CD
Carrier Sense Multiple Access
with Collision Detect
The ST201 can support a variety of physical signal-
ing schemes via the IEEE 802.3u defined MII.
Through the MII, the ST201 supports Fast Ethernet
(such as 100BASE-TX) as well as the legacy
10BASE-T standard. The MII provides a general-
purpose interface between an 802.3u MAC and
various physical layer devices, and is comprised of
two independent components. The data interface
provides separate, 4-bit wide paths for receive and
transmit data, as well as independent clock and
control signals. The management interface is a
bidirectional, serial link that provides the ST201
access to registers residing within the physical
layer device. The host system controls the MII
management interface through the PhyCtrl regis-
ter.
FCS
SFD
CRC
IP
Frame Check Sequence
Start of Frame Delimiter
Cyclic-Redundancy-Check
Internet Protocol
TFD
RFD
DMA
ACPI
Transmit Frame Descriptor
Receive Frame Descriptor
Direct Memory Access
Advanced
Configuration
and
Power Management
STANDARDS COMPLIANCE
The ST201 implements functionality compliant with
the following standards:
• IEEE 802.3u Fast Ethernet
• IEEE 802.3x Full Duplex Flow Control
• PCI Local Bus Revision 2.1
• ACPI Revision 1.0
Since the MII is independent of the signaling
method (100BASE-TX, 10BASE-T, etc.), it is possi-
ble to use it to support numerous Ethernet or Fast
Ethernet LAN types depending upon the availability
of MII-compliant PHY devices. The most widely
available PHY devices support both 10BASE-T
and 100BASE-TX through a single MII.
FUNCTIONAL DESCRIPTION
It is most likely that a physical layer device con-
nected to ST201’s MII will include implementation
of the 802.3u Auto-Negotiation function. For
instance, a PHY device may be able to auto-nego-
tiate between 10BASE-T and 100BASE-TX. A host
system attempting to determine link status should
check the Auto-Negotiation function contained in
the MII-based PHY device through the MII man-
agement interface of the ST201.
The ST201 is composed of various functional
blocks as shown in Figure 1. An overview of the
functions performed by each block follows:
MEDIA ACCESS CONTROL
The MAC block implements the IEEE Ethernet
802.3u Media Access Control functions with 802.3x
Full Duplex and Flow Control enhancements. In
half duplex mode, the MAC implements the CSMA/
CD. Full duplex mode by definition does not utilize
10
Sundance Technology
ST201
PRELIMINARY draft 2
PCI BUS INTERFACE
complete frame must be transferred from the host
system memory to the TxFIFO again by TxDMA
Logic.
The PCI Bus Interface (PBI) implements the proce-
dures and algorithms needed to link the ST201 to a
PCI bus. The ST201 can be either a PCI bus mas-
ter or slave. The PBI is also responsible for manag-
ing the DMA interfaces and the host processors
access to the ST201 registers. Arbitration logic
within the PBI block accepts bus requests from the
TxDMA Logic and RxDMA Logic. The arbiter ser-
vices the four requests in the fixed priority order of:
1. RxDMA Urgent Request
RXDMA LOGIC
The ST201 supports a multi-frame, multi-fragment
DMA scatter process. Descriptors representing
frames are built and linked in system memory by a
host processor. The RxDMA Logic is responsible
for transferring the multi-fragment frame data from
the RxFIFO to the host memory.
2. TxDMA Urgent Request
3. RxDMA Request
4. TxDMA Request
The RxDMA Logic monitors the number of bytes in
the RxFIFO. After a number of bytes have been
received, the frame is “visible”. A frame is visible if:
• The frame being received is determined not to be
a runt, AND
The PBI also manages interrupt generation for a
host processor.
• The number of frame bytes received has
exceeded the value in the RxEarlyThresh reg-
ister (if enabled), OR
TXDMA LOGIC
The ST201 supports a multi-frame, multi-fragment
DMA gather process. Descriptors representing
frames are built and linked in system memory by a
host processor. The TxDMA Logic is responsible
for transferring the multi-fragment frame data from
the host memory into the TxFIFO.
• The entire frame has been received
After a frame becomes visible, the RxDMA Logic
will issue a request to the DMA arbiter when the
number of bytes in the RxFIFO is greater than the
value in the RxDMABurstThresh. To prevent
receive overruns, a RxDMA Urgent Request is
made when the amount of free space in the
RxFIFO falls below the value in RxDMAUrgent-
Thresh.
The TxDMA Logic monitors the amount of free
space in the TxFIFO, and uses this value to decide
when to request a TxDMA. A TxDMABurstThresh
register is used to delay the bus request until there
is enough free space in the TxFIFO for a long
burst.
RXFIFO
The ST201 uses 2K bytes of receive data buffer
between the Receive MAC and RxDMA Logic.
When the RxDMA Logic determines the number of
bytes in the RxFIFO is greater than the value in
RxEarlyThresh register, the ST201 will generate a
RxEarly interrupt (if enabled) to the host. The val-
ues in RxEarlyThresh and RxDMABurstThresh
also determine how many bytes of a frame must be
received into RxFIFO before RxDMA Logic is
allowed to begin data transfer.
To prevent a TxFIFO under run condition the
TxDMA logic forwards an urgent request to the
DMA arbiter, regardless of the TxDMABurstThresh
constraint, when the number of occupied bytes in
the TxFIFO drops below the value in TxDMAUr-
gentThresh register.
TXFIFO
The ST201 uses 2K bytes of transmit data buffer
between the TxDMA Logic and Transmit MAC.
When the TxDMA logic determines there is enough
space available in the TxFIFO, the TxDMA Logic
will move any pending frame data into the TxFIFO.
The TxReleaseThresh register value determines
the amount of data which must be transmitted out
of the TxFIFO before the FIFO memory space
occupied by that data can be released for use by
another frame.
When RxEarlyThresh is set to a value that is
greater than the length of the received frame, a
RxComplete interrupt will occur at the completion
of frame reception rather than a RxEarly interrupt.
EEPROM INTERFACE
The external serial EEPROM is used for non-vola-
tile storage of such information as the node
address, system ID, and default configuration set-
tings. As part of initialization after system reset, the
ST201 reads certain locations from the EEPROM
and places the data into host-accessible registers.
A TxReleaseError occurs when a frame experi-
ences a collision after the TxFIFO release thresh-
old has been crossed. The ST201 will not be able
to retransmit this frame from the TxFIFO and the
11
Sundance Technology
ST201
PRELIMINARY draft 2
EXPANSION ROM INTERFACE
• loBaseAddress sets the I/O base address for the
ST201 registers.
• MemBaseAddress sets the memory base address
for the ST201 registers.
The ST201 provides support for an optional Expan-
sion ROM. The ST201 supports the Atmel
AT29C512 (64K x 8) Flash EPROM device.
• ExpRomBaseAddress sets the base address and
size for an installed expansion ROM, if any.
• CacheLineSize indicates the system’s cache line
size. This value is used by the ST201 to opti-
mize bus master data transfers.
• LatencyTimer sets the length of time the ST201
can hold the PCI bus as a bus master.
• InterruptLine maps ST201’s interrupt request to a
specific interrupt line (level) on the system
board.
The Expansion ROM is configured through the PCI
configuration register, which maps the ROM into
the memory space of the host system. The ROM
contents can be scanned, copied to system RAM,
and executed at system initialization time.
The ROM is also byte-read and byte-write accessi-
ble to the host CPU using the ExpRomData and
ExpRomAddr registers. This allows a diagnostic
program to read or modify the ROM contents with-
out having to write to configuration registers.
• AsicCtrl is used to setup internal operations and
parameters.
OPERATION
The ST201 can be accessed across the PCI bus
without setting the PCI registers or reading data
from an external EEPROM. In this Forced Configu-
ration mode (useful for embedded applications
without an EEPROM), the ST201 is forced to the
following configuration:
Proper operation of the ST201 in a system requires
an understanding of initialization tasks, register
programming, transmit and receive behavior, inter-
rupt handling, statistic gathering, PCI bus transac-
tions, and power management capabilities.
• I/O base address 200h
• I/O target cycles enabled
INITIALIZATION
The ST201 provides several resets. The assertion
of the hardware reset signal on the PCI bus causes
a complete reset of the ST201. The ST201 configu-
rations previously set are lost after reset. A similar
reset is available via software using the GlobalRe-
set bit of the AsicCtrl register. The AsicCtrl register
also allows for selective reset of particular func-
tional blocks of the ST201. See the Registers and
Data Structures section for details on using the
AsicCtrl register for resetting the ST201.
• Memory target cycles disabled
• Bus master cycles enabled
• Expansion ROM cycles disabled
REGISTER PROGRAMMING
After initializing the ST201 to facilitate communica-
tion with the host system, an additional set of regis-
ters specific to operation of the Ethernet network
must be set.
The first setting relates to the Auto-Negotiation fea-
tures present in most Ethernet PHY devices. Since
the ST201 does not participate in the Auto-Negoti-
ation process, the host system must communicate
with the PHY device (across the MII Management
Interface) to determine the link status. Once the
result of Auto-Negotiation is determined, if a full
duplex mode has been chosen, the host system
must set the FullDuplexEnable bit in the MACCtrl
register. Other modes chosen during Auto-Negoti-
ation do not require any ST201 register settings.
The external serial EEPROM is used for non-vola-
tile storage of configuration information across
ST201 resets. Shortly after reset, the ST201 will
read the contents of an external EEPROM, placing
the data read into the following registers:
• ConfigParm
• AsicCtrl (least significant 16 bits)
• SubsystemVendorId
• SubsystemId
• StationAddress
There are several other registers which must be
configured during initialization. These registers
include the ST201 PCI configuration registers
which are set during a Power On Self Test (POST)
routine performed by the host system. Specifically,
the registers set during this stage of initialization
are:
• ConfigCommand enables adapter operation by
allowing it to respond to and generate PCI bus
cycles. ConfigCommand is also used to enable
parity error generation.
The ReceiveMode register determines which types
of frames, based on address matching mechanism,
the ST201 will receive. The host system must pro-
gram the adapter’s node address into the Station-
Address registers. This node address can be
obtained either from the EEPROM, or the host sys-
tem can set the value directly. Then, by setting the
ReceiveUnicast bit in the ReceiveMode register,
the ST201 will receive unicast frames whose desti-
nation address matches the value in the StationAd-
12
Sundance Technology
ST201
PRELIMINARY draft 2
dress register. Setting the ReceiveBroadcast and
ReceiveMulticast bits in the ReceiveMode register
will allow the ST201 to receive all broadcast and
multicast frames, respectively. The ReceiveMultic-
astHash bit in ReceiveMode enables a filtering
mechanism for Ethernet multicast frames. This fil-
tering mechanism uses a 64-bit hash table (Hash-
Table register) for selective reception of Ethernet
multicast frames. A CRC algorithm is applied to the
destination address of incoming Ethernet multicast
frames. The least significant 6 bits of the CRC
result are used as an index into the hash table. The
Ethernet multicast frame will be accepted by the
ST201 when the corresponding hash table bit is
set, otherwise the frame will be discarded. The
host system must configure the hash table before
any multicast frames are received using the filter-
ing mechanism.
ity to inhibit transmission of MAC data frames for a
specified period of time. The PAUSE frame format
is defined as shown in Figure 1.
LENGTH
(BYTES)
FIELD
DA
SA
0x0180C2000001
6
6
TYPE
0x8808
0x0001
2
OPCODE
2
Additionally, Ethernet frames containing IP multi-
cast destination addresses can also be received by
setting the ReceiveIPMulticast bit in the Receive-
Mode register. IP multicast, or Host Extension for
IP Multicasting, datagrams map to frames with
Ethernet destination addresses of 0x01005e******
(where * represents any hexadecimal value).
PAUSE TIME
PAD
2
42
FIGURE 1: PAUSE Frame
The MACCtrl register is used to configure parame-
ters including full duplex, flow control, and statistics
gathering.
In Figure 1, bytes within fields are transmitted left
to right, bits within bytes transmitted least-signifi-
cant bit first.
The ST201 can operate in either half duplex or full
duplex mode. In half duplex mode, the ST201
implements the CSMA/CD algorithm. CSMA/CD
requires that only one node transmit at a time. If
multiple nodes attempt to transmit simultaneously
(indicated when both the receive and transmit sig-
nals are active) a collision will occur resulting in
frame loss, and typically requiring re-transmission.
In full duplex mode, the ST201 can transmit and
receive frames simultaneously without incurring
collisions. To configure the ST201 for full duplex
mode operation, the host system must detect a full
duplex physical link via the appropriate PHY device
register, and must set the FullDuplexEnable bit in
the MACCtrl register.
Whenever the FlowControlEnable bit in the MAC-
Ctrl register is set, the ST201 compares the desti-
nation address with 0x0180C2000001 and the type
field with 0x8808 in all incoming frames. If both
fields match, the ST201 further checks for the
PAUSE opcode (0x0001) in the MAC Control
Opcode field. If found, the ST201 inhibits transmis-
sion of all data frames for the time specified in the
two-byte pause_time field. The pause_time field is
specified in slot times relative to the current data
rate; one slot time is 51.2 us at 10 Mbps, and 5.12
us at 100 Mbps. The transmission of PAUSE
frames is the responsibility of the host. The MAC
Control frame must be constructed by the host and
placed into the TxFIFO. The driver should program
the ReceiveMode register to receive PAUSE (MAC
Control frame) when flow control is enabled. For
end station applications, host system should only
accept PAUSE frames, and not generate them.
Flow control is designed to originate from network
devices such as switches.
The IEEE 802.3x Full Duplex standard defines a
special frame known as the PAUSE MAC Control
frame. The PAUSE frame is used to implement
flow control in full duplex networks allowing sta-
tions on opposite ends of a full duplex link the abil-
13
Sundance Technology
ST201
PRELIMINARY draft 2
TXDMA AND FRAME TRANSMISSION
The resulting linked list of TFDs is referred to as
the TxDMAList, as shown in Figure 3.
The TxDMA block transfers frame data from a host
system to the ST201 based on a linked list of frame
descriptors called TFDs. The frame to be transmit-
ted is divided into data fragments (or buffers) within
the host system’s memory. The host system cre-
ates a list of TFDs, also in system memory, where
each TFD contains the memory locations of one or
more fragments of a frame as shown in Figure 2.
HOST SYSTEM MEMORY
TFD 1
TFD 2
HOST SYSTEM MEMORY
Next TFD Ptr.
FIGURE 3: TxDMA List
TxFrameControl
1st TxDMAFragAddr
1st TxDMAFragLen
After reset, the ST201 MAC transmission is dis-
abled, until the TxEnable bit is set. Any data trans-
ferred by TxDMA Logic into the TxFIFO will stay in
the TxFIFO waiting for the TxEnable bit to be set
enabling transmission. After enabling data trans-
mission, the TxDMA Logic is in the idle state. In the
simple case of a single frame, the host system
must create a TFD within the host system memory.
This TFD must contain the addresses and lengths
of the fragments containing the data to be transmit-
ted. The host system must write zero into TxD-
MANextPtr since this is the only frame. The host
starts the TxDMA Logic by writing the memory
location (a non-zero address) of the TFD into TxD-
MAListPtr register. The TxDMA Logic, if is not in
the TxDMAHalt state, begins transferring data into
the ST201 when:
2nd TxDMAFragAddr
2nd TxDMAFragLen
TFD
Last TxDMAFragAddr
Last TxDMAFragLen
1st Data Frag (Buffer)
• The TxFIFO has 16 or more bytes of free space,
AND
• The fragment length is less than or equal to the
amount of free space in the TxFIFO,
2nd Data Frag (Buffer)
Last Data Frag (Buffer)
OR
• The amount of free space in the TxFIFO is
greater than or equal to the value (in bytes) of
32 * TxDMABurstThresh register
FIGURE 2: TxDMA Data Structure
If these conditions hold, the TxDMA Logic fetches
the fragment addresses and fragment lengths from
the TFD and writes them one at a time into the
ST201 registers, which are used to control the data
transfer operations. If the TxDMA Logic transfers
more data than can fit into the TxFIFO, an overrun
will occur.
The TFD format is covered in the Registers and
Data Structures section.
If the host system disables data transmission (by
resetting the TxDisable bit) while a frame transmis-
sion is in progress, the current frame transmission
will complete before data transmission is disabled.
14
Sundance Technology
ST201
PRELIMINARY draft 2
The TxDMAListPtr I/O register within the ST201
contains the physical address that points to the
head of the TxDMAList. TxDMAListPtr must point
to addresses which are on 8-byte boundaries. A
value of zero in the TxDMAListPtr register implies
there are no pending TFD’s for the ST201 to pro-
cess.
probably set TxDMAIndicate to generate an inter-
rupt. However, if during the TxDMA process of this
frame, the host system added a new TFD to the
end of the list, it might clear TxDMAIndicate in the
currently active TFD so that the interrupt is delayed
until the next TFD.
The ST201 has the ability to automatically round
up the length of a transmit frame. This is useful in
some NOS environments in which frame lengths
need to be an even number of words. Frame length
word-alignment is performed based upon the sum
of the fragment lengths specified in a TFD, and the
2-bit WordAlign field in the TFD’s TFC field. Word-
alignment occurs when the frame length implied by
the sum of the fragment lengths is not an even mul-
tiple of the value indicated by WordAlign. The
frame length is rounded up to either a word or
dword boundary, depending upon the value of
WordAlign. Host systems may disable frame length
word-alignment by setting the WordAlign bits in the
TransmitFrameControl to x1.
Generally, it is desirable for the host system to
queue multiple frames. Multiple TFD’s are linked
together in a list by pointing the TxDMANextPtr of
each TFD at the next TFD. The last TFD in the
linked list should have a value of zero for it’s TxD-
MANextPtr.
It is required that the host halt the TxDMA Logic by
setting the TxDMAHalt bit before modifying TxD-
MAList or writing a new value to TxDMAListPtr
(unless it is already zero). When the host has fin-
ished manipulating the list, it sets the TxDMARe-
sume bit.
The TxDMA process returns to the idle state upon
detection of a zero value for TxDMANextPtr. When
a new frame is available to transfer, the host sys-
tem must write the address of the new TFD into the
TxDMANextPtr memory location of the last TFD,
and either set the TxEnable bit, or utilize the
ST201’s automatic polling capability. Using auto-
matic polling, the ST201 will monitor the TxDMAN-
extPtr memory location until a non-zero value is
found at that location in system memory. The TxD-
MAPollPeriod register controls this polling function,
which is enabled when TxDMAPollPeriod contains
a non-zero value. The value written to TxDMAPoll-
Period determines the TxDMANextPtr polling inter-
val.
The MAC will initiate frame transmission (if trans-
mission is enabled) as soon as either the entire
frame is resident in the TxFIFO, or the number of
bytes present in the TxFIFO is greater than the
value in the TxStartThresh register.
As a frame transmits out of the TxFIFO, it is desir-
able to be able to release the FIFO space so that it
may be used for another frame. The value pro-
grammed into TxReleaseThresh determines how
much of a frame must be transmitted before its
FIFO space can be released.
A TxReleaseError occurs when a frame experi-
ences a collision after the frame’s release thresh-
old has been crossed. The ST201 will be unable to
retransmit the frame and the host needs to re-start
the TxDMA transfer. When a transmit error occurs,
a TxComplete interrupt is generated, and the spe-
cific error is indicated by status bits in TxStatus. To
recover from a transmit error, the host system must
re-enable the transmitter and, in the case of an
under run error, reset the transmit logic with TxRe-
set, before subsequent transmissions can occur.
When MaxCollisions or TxStatusOverflow errors
occur, any pending frames in the TxFIFO are pre-
served (except the frame that experienced Max-
Collisions). The frames are held in the TxFIFO due
to the fact that MaxCollisions and TxStatusOver-
flow errors do not require assertion of TxReset.
The preserved frames will be transmitted following
a transmitter re-enable.
The ST201 can be configured to generate TxDMA-
Complete interrupts on a per frame basis by setting
the TxDMAIndicate bit within the TFC field of each
TFD. In response to a TxDMAComplete interrupt,
when data transfer by TxDMA is finished, the host
system acknowledges the interrupt and returns the
frame data buffers to the system. In the case of a
multi-frame TxDMAList, multiple frames may have
been transferred by TxDMA when the host system
enters its interrupt service routine. The host system
can traverse the list of TFD’s, examining the TxD-
MAComplete bit in each TFD to determine which
frames have been transferred by TxDMA.
The ST201 fetches the TFC before frame data
transfer, and again at the end of TxDMA operation
to examine the TxDMAIndicate bit. This allows the
host system to change TxDMAIndicate while data
transfer of the frame is in progress. For instance, a
frame’s TFD might be at the end of the TxDMAList
when it starts TxDMA, so the host system would
Since TxDMA writes into one end of the TxFIFO
and the transmit MAC reads from the other end,
TxDMA and transmit completes (including errors)
15
Sundance Technology
ST201
PRELIMINARY draft 2
are independent of each other in general. A special
case is when a transmit under run occurs. In this
case the current frame being transmitted is the only
frame in the TxFIFO. When a transmit under run
occurs, the ST201 stops TxDMA operation and
generates an interrupt with a TxUnderrun error
flagged in TxStatus. The host system can deter-
mine which is the under run error frame by examin-
ing the current value of TxDMAListPtr. The host
system can assume that all frames in the TxDMAL-
ist ahead of the under run error frame have been
transmitted successfully. To recover from an under
run, the host system should halt the TxDMA Logic
by setting the TxDMAHalt bit, wait until TxDMAIn-
Prog and TxInProg are cleared, then issue a TxRe-
set to reset the under run (TxFIFO and Transmit
MAC). Transmission needs to be enabled (by
TxEnable) again and all transmit-related thresholds
(TxStartThresh in particular) should be restored.
To re-transmit the frame, the host system writes
the value of the under run frame’s TFD into the
TxDMAListPtr register.
contain pointers to the fragment buffers into which
the ST201 is to place receive data, as shown in
Figure 4.
HOST SYSTEM MEMORY
Next RFD Ptr.
RxFrameStatus
1st RxDMAFragAddr
1st RxDMAFragLen
2nd RxDMAFragAddr
2nd RxDMAFragLen
RFD
Last RxDMAFragAddr
Last RxDMAFragLen
FRAME RECEPTION AND RXDMA
1st Data Frag (Buffer)
The frame RxDMA mechanism is similar to the
TxDMA mechanism. RxDMA is structured around a
linked list of frame descriptors, called RFDs. RFDs
2nd Data Frag (Buffer)
Last Data Frag (Buffer)
FIGURE 4: RxDMA Data Structure
The RFD format is covered in the Registers and
Data Structures section.
Similar to TFDs, the resulting linked list of RFDs is
referred to as the RxDMAList. One option available
to RxDMA that differs from TxDMA is that the RxD-
MAList can be formed into a ring as shown in Fig-
ure 5. A host system can allocate a number of full
size frame buffers, create a RFD for each one, and
link the RFDs into a circular list. As frames are
16
Sundance Technology
ST201
PRELIMINARY draft 2
received and transferred by RxDMA, a RxDMA-
Complete interrupt will be generated for each
frame.
tions. Similar to TxDMA, the RxDMA Logic can be
controlled by the RxDMAHalt and RxDMAResume
bits. The host system should set the RxDMAHalt
bit before modifying the list pointers in the RxD-
MAList. The RxDMA Logic will return to the idle
state when the RxDMAListPtr register is zero.
HOST SYSTEM MEMORY
RFD 1
For RxDMA lists configured as a ring, the host sys-
tem should clear the RxDMAComplete bit within
the ReceiveFrameStatus field of the RFD from
which the host system has finished reading data. If
RxDMAPollPeriod is zero the host system should
also issue a RxDMAResume in case the ST201
has halted due to detection of a set RxDMACom-
plete bit within the ReceiveFrameStatus field of the
next RFD in the ring. If the ST201 fetches a RxD-
MAListPtr for a RFD that has already been used (a
RFD in which the RxDMAComplete bit is set in
ReceiveFrameStatus), the RxDMA Logic will either
assert an implicit RxDMAHalt or, if the RxDMAPoll-
Period register is set to a non-zero value, the
RxDMA Logic will automatically recheck RxDMA-
Complete periodically until it is cleared.
RFD 2
RFD n
The operation for adding RFDs into the RxDMAList
starts with halting the RxDMA Logic by setting the
RxDMAHalt bit within the DMACtrl register. The
host system then updates RxDMANextPtr in the
last RFD in the RxDMAList to point at the new
RFD. The host system will also need to read the
RxDMAListPtr, and if it was zero, write the address
of the just added RFD into RxDMAListPtr and set
the RxDMAResume bit within the DMACtrl register
to re-start the RxDMA Logic.
FIGURE 5: RxDMA List Shown in Ring
Configuration
The host system must create a RxDMAList and the
associated buffers prior to reception of a frame.
One approach calls for the host system to allocate
a block of full size (i.e. large enough to hold a max-
imum size Ethernet frame of 1518 bytes) frame
buffers in system data space and create RFDs that
point to them. Another approach is for the host sys-
tem to request the buffers from the protocol ahead
of time.
The ST201 can be configured to generate a RxD-
MAComplete interrupt when RxDMA completes a
frame reception. In response to a RxDMAComplete
interrupt, the host system must examine the
ReceiveFrameStatus field in the RFD of the
received frame to determine the size of the frame
and whether there were any errors. The host sys-
tem must then copy the frame out of the receive
buffers, if needed.
After reset, the ST201 receive function is disabled.
Once the RxEnable bit is set, frames will be
received according to the matching mode pro-
grammed in ReceiveMode register. Reception can
be disabled by setting the RxDisable bit. If set
while a frame is being received, RxDisable only
takes effect after the active frame reception is fin-
ished. The receive function begins with the RxDMA
Logic in the idle state. The RxDMA Logic will begin
processing a RxDMAList as soon as a non-zero
address is written into the RxDMAListPtr register.
The host system creates a RFD with the addresses
and lengths of the buffers to be used and programs
the RxDMAListPtr register to point to the head of
the list. The host system must program a zero into
the RxDMANextPtr of the last RFD to indicate the
end of the RxDMAList. When a frame is received in
the RxFIFO, the ST201 fetches the fragment
address and fragment length values one by one
from the current RFD, and writes these values into
internal registers which control data transfer opera-
In general, when the host system enters its inter-
rupt service routine, multiple frames may have
been transferred by RxDMA. The host system can
read RxDMAListPtr to determine which RFDs in
the list have been used. The host system begins at
the head of the RFD list, and traverses the list until
it reaches the RFD whose address matches RxD-
MAListPtr. However, since I/O operations are
costly, it is more efficient to use the RxDMACom-
plete bit in each RFD to determine which frames
have been transferred by RxDMA.
17
Sundance Technology
ST201
PRELIMINARY draft 2
Systems using the ST201 can be programmed to
generate an interrupt based upon the number of
bytes that have been received in a frame. The
RxEarlyThresh register sets the value for early
receive threshold. As soon as the number of bytes
that have been received is greater than the value in
RxEarlyThresh register, the ST201 will generate a
RxEarly interrupt, if it is enabled, to the host. The
RxEarly interrupt will only occur when the frame
being received is the top frame, i.e., can be trans-
ferred by the host during reception. The RxEar-
lyThresh mechanism will cause one RxEarly
interrupt per frame. The host system can program
any value greater than or equal to 0x08 into RxEar-
lyThresh. The ST201 needs a minimum of 8 frame
bytes to perform destination address filtering
before generating an RxEarly interrupt. The value
in RxEarlyThresh may also determine how many
bytes of a frame must be received before RxDMA
transfers for the frame are allowed to begin. If
RxEarlyEnable in DMACtrl is set, a frame becomes
eligible to start RxDMA when RxEarlyThresh bytes
have been received. Setting RxEarlyThresh too
low will cause the host to respond to the interrupt
before the entire receive frame header has been
received. Setting RxEarlyThresh too high will intro-
duce unnecessary delays in the system’s receive
response sequence. When RxEarlyThresh is set to
a value that is greater than the length of the
received frame, a RxComplete interrupt will occur
at the completion of frame reception rather than a
RxEarly interrupt. If the host system is particularly
slow in responding to a RxEarly interrupt, then it is
likely that the frame will have been completely
received by the time the driver examines the
ST201. In this case, RxEarly will be overridden by
RxComplete. RxEarly is cleared when RxComplete
becomes set, hence they are mutually exclusive. In
order to prevent spurious interrupts, RxComplete
should only be disabled if RxEarly is also disabled.
The host system can then perform memory copies
out of the RFD buffer in parallel with the RxDMA
operation.
INTERRUPTS
The term “interrupt” is used loosely to refer to inter-
rupts and indications. An interrupt is the actual
assertion of the hardware interrupt signal on the
PCI bus. An indication, or a set bit in the IntStatus
register, is the reporting of any event enabled by
the host. The host system will configure the ST201
to generate an interrupt for any indication that is of
interest to it. There are 10 different types of inter-
rupt indications that can be generated by the
ST201. The IntEnable register controls which of
the 10 indication bits can assert a hardware inter-
rupt. In order for an indication bit to be allowed to
generate an interrupt, its corresponding bit-position
in IntEnable must be set. When responding to an
interrupt, the host reads the IntStatus register to
determine the cause of the interrupt. The least sig-
nificant bit of IntStatus, InterruptStatus, is always
set whenever any of the interrupts are asserted.
InterruptStatus must be explicitly acknowledged
(cleared) by writing a 1 into the bit in order to pre-
vent spurious interrupts on the host bus.
Interrupts are acknowledged by the host carrying
out various actions specific to each interrupt.
These actions are as follows:
• HostError, acknowledged by issuing the appropri-
ate resets
• TxComplete, acknowledged by writing to TxSta-
tus
• RxComplete, acknowledged automatically by the
hardware
• UpdateStats, acknowledged by reading statistics
registers
• InterruptStatus, acknowledged by writing a 1 into
this bit
• RxEarly, acknowledged by writing a 1 into this bit
In some host systems, it may be desirable to copy
received frame data out of the scatter buffer to the
protocol buffer while the frame is still being trans-
ferred by RxDMA. The RxDMAStatus register is
provided for this purpose. If the host system sets
the RxDMAHalt bit in the DMACtrl register, reads
the RxDMAListPtr register and the RxDMAStatus
register, then sets the RxDMAResume bit in the
DMACtrl register, the host system can determine
how much of the frame has been transferred by
RxDMA. The RxDMAStatus register indicates the
number of bytes transferred by RxDMA for the cur-
rent RFD pointed to by the RxDMAListPtr register.
• IntRequested, acknowledged by writing a 1 into
this bit
• LinkEvent, acknowledged by writing a 1 into this
bit
• TxDMAComplete, acknowledged by writing a 1
into this bit
• RxDMAComplete, acknowledged by writing a 1
into this bit
• MACControlFrame, acknowledged by writing a 1
into this bit
18
Sundance Technology
STATISTICS
ST201
PRELIMINARY draft 2
this statistic.
• CarrierSenseErrors: Frames that were transmit-
ted without error but experienced a loss of car-
rier are counted by this statistic.
The ST201 implements 16 statistics counters of
various widths. Each statistic implemented com-
plies to the corresponding definition given in the
IEEE 802.3 standard. Setting the StatisticsEnable
bit in the MACCtrl register enables the gathering of
statistics. Reading a statistics register will clear the
read register. Statistic registers may be read with-
out disabling statistics gathering. For diagnostics
and testing purposes, the host system may write a
value to a statistic register, in which case the value
written is added to the current value of the register.
Whenever one or more of the statistics registers
reaches 75% of its maximum value, an Updat-
eStats interrupt is generated. Reading that statis-
tics register will acknowledge the UpdateStats
interrupt. A summary of the transmit and receive
statistics follows. Detailed descriptions of the sta-
tistic registers related to data transmission and
reception can be found in the Registers and Data
Structures section.
RECEIVE STATISTICS
• FramesReceivedOk: Frames of all types that are
received without error are counted here.
• BroadcastFramesReceivedOk: Frames of broad-
cast destination address that are received
without error are counted here.
• MulticastFramesReceivedOk: Frames of multi-
cast destination address that are received
without error are counted here.
• OctetsReceivedOk: A total octet count for all
frames received without error.
• FramesLostRxErrors: This is a count of frames
that would otherwise be received by the
ST201, but could not be accepted due to an
overrun condition in the RxFifo.
PCI BUS MASTER OPERATION
TRANSMIT STATISTICS
The ST201 supports all of the PCI memory com-
mands and decides on a burst-by-burst basis
which command to use in order to maximize bus
efficiency. The list of PCI memory commands is
shown below. For all commands, “read” and “write”
are with respect to the ST201 (i.e. read implies the
ST201 obtains information from an off-chip loca-
tion, write implies the ST201 sends information to
an off-chip location).
• FramesTransmittedOk: The number frames of all
types transmitted without errors. Loss of carrier
is not considered to be an error by this statistic.
• BroadcastFramesTransmittedOk: The number of
frames with broadcast destination address that
are transmitted without errors.
• MulticastFramesTransmittedOk: The number of
frames with multicast destination address that
are transmitted without errors.
• Memory Read (MR)
• OctetsTransmittedOk: The number of total octets
for all frames transmitted without error.
• FramesWithDeferredXmission: A count of frames
whose transmission was delayed on it’s first
attempt because network traffic.
• FramesWithExcessiveDeferral: If the transmis-
sion of a frame has been deferred for an
excessive period of time due to network traffic,
the event is recorded in this statistic.
• SingleCollisionFrames: Frames that are transmit-
ted without errors after one and only one colli-
sion (including late collisions) are counted by
this register.
• MultipleCollisionFrames: All frames transmitted
without error after experiencing from 2 through
15 collisions (including late collisions) are
counted here.
• Memory Read Line (MRL)
• Memory Read Multiple (MRM).
• Memory Write (MW)
• Memory Write Invalidate (MWI)
MR is used for all fetches of descriptor information.
For reads of transmit frame data, MR, MRL, or
MRM is used, depending upon the remaining num-
ber of bytes in the fragment, the amount of free
space in the TxFIFO, and whether the RxDMA
Logic is requesting a bus master operation.
MW is used for all descriptor writes. Writes of
receive frame data use either MW or MWI, depend-
ing upon the remaining number of bytes in the frag-
ment, the amount of frame data in the RxFIFO, and
whether the TxDMA Logic is requesting a bus mas-
ter operation.
The ST201 provides three configuration bits to
control the use of advanced memory commands.
The MWlEnable bit in the ConfigCommand config-
uration register allows the host to enable or disable
the use of MWI. The MWIDisable and MRLDisable
bits in DMACtrl allow the host system the ability to
• LateCollisions: Every occurrence of a late colli-
sion (there could be more than one per frame
transmitted) is counted by this statistic.
• FramesAbortedDueToXSColls: If the transmis-
sion of a frame had to be aborted due to
excessive collisions, the event is recorded in
19
Sundance Technology
ST201
PRELIMINARY draft 2
disable the use of MWI and MRL. MWIDisable and
MRLDisable are cleared by default, enabling MWI
and MRL.
ST201 optionally supports this state deter-
mined by the D1Support bit in the ConfigParm
word in EEPROM. The D1 state allows transi-
tion back to D0 with no delay. In this state, the
ST201 responds to PCI configuration
The ST201 provides a set of registers that control
the PCI burst behavior. These registers allow a
trade-off to be made between PCI bus efficiency
and under run/overrun frequency. Arbitration logic
within the PCI Bus Interface block accepts bus
requests from the TxDMA Logic and RxDMA Logic.
The TxDMA Logic uses the TxDMABurstThresh
register, as described in the TxDMA Logic section,
to delay the bus request until there is enough free
space in the TxFIFO for a long, efficient burst. The
TxDMA Logic can also make an urgent bus request
as described in the TxDMA Logic section, where
burst efficiency is sacrificed in favor of avoiding a
TxFIFO under run condition.
accesses, to allow the system to change the
power state. In D1 the ST201 does not
respond to any PCI I/O or memory accesses.
The ST201’s function in the D1 state is to rec-
ognize wake events and link state events and
pass them on to the system by asserting the
PMEN signal on the PCI bus.
• D2 (power state 2) is a partial power-down state.
The ST201 optionally supports this state deter-
mined by the D2Support bit in the ConfigParm
word in EEPROM. D2 allows a faster transition
back to D0 than is possible from the D3 state.
In this state, the ST201 responds to PCI con-
figuration accesses, to allow the system to
change the power state. In D2 the ST201 does
not respond to any PCI I/O or memory
accesses. The ST201’s function in the D2 state
is to recognize wake events and link state
events and pass them on to the system by
asserting the PMEN signal on the PCI bus.
• D3 Hot (power state 3) is the full power-down
state for the ST201. In D3 Hot, the ST201
loses all PCI configuration information except
for the value in PowerState. In this state, the
ST201 responds to PCI configuration
The RxDMA process is described in the RxDMA
Logic section. Typically, RxDMA requests will be
forwarded to the Arbiter, however RxDMA Urgent
Requests are also possible in order to prevent
receive overruns. The Arbiter services the four
requests in the fixed priority order as described in
the PCI Bus Interface section.
POWER MANAGEMENT
The ST201 supports operating system directed
power management according to the ACPI specifi-
cation. Power management registers in the PCI
configuration space, as defined by the PCI Bus
Power Management Interface specification, Revi-
sion 1.0 are described in the Registers and Data
Structures section.
accesses, to allow the system to change the
power state back to D0 Uninitialized. In D3 hot,
the ST201 does not respond to any PCI I/O or
memory accesses. The ST201’s main respon-
sibility in the D3 Hot state is to recognize wake
events and link state events and signal those
to the system by asserting the PMEN signal on
the PCI bus.
The ST201 supports several power management
states. The PowerState field in the PowerMgmtCtrl
register determines ST201’s current power state.
The power states are defined as follows:
• D0 Uninitialized (power state 0) is entered as a
result of hardware reset, or after a transition
from D3 Hot to D0. This state is the same as
D0 Active except that the PCI configuration
registers are uninitialized. In this state, the
ST201 responds to PCI configuration cycles
only.
• D0 Active (power state 0) is the normal opera-
tional power state for the ST201. In this state,
the PCI configuration registers have been ini-
tialized by the system, including the IoSpace,
MemorySpace, and BusMaster bits in Config-
Command, so the ST201 is able to respond to
PCI I/O, memory and configuration cycles and
can operate as a PCI master. The ST201 can-
not signal wake (PMEN) from the D0 state.
• D1 (power state 1) is a “light-sleep” state. The
• D3 Cold (power state undefined) is the power-off
state for the ST201. The ST201 does not func-
tion in this state. When power is restored, the
system guarantees the assertion of hardware
reset, which puts the ST201 into the D0 Unini-
tialized state.
The ST201 can generate wake events to the sys-
tem as a result of Wake Packet reception, Magic
Packet reception, or due to a change in the link sta-
tus. The WakeEvent register gives the host system
control over which of these events are passed to
the system. Wake events are signaled over the PCI
bus using the PMEN pin.
A Wake Packet event is controlled by the WakePk-
tEnable bit in WakeEvent register. WakePktEnable
has no effect when ST201 is in the D0 power state,
as the wake process can only take place in states
20
Sundance Technology
ST201
PRELIMINARY draft 2
D1, D2, or D3. When the ST201 detects a Wake
Packet, it signals a wake event on PMEN (if PMEN
assertion is enabled), and sets the WakePktEvent
bit in the WakeEvent register. The ST201 can sig-
nal that a wake event has occurred when it
receives a pre-defined frame from another station.
The host system transfers a set of frame data pat-
terns into the TxFIFO using the TxDMA function
before placing the ST201 in a power-down state.
Once powered down, the ST201 compares receive
frames with the frame patterns in the TxFIFO.
When a matching frame is received (and also
passes the filtering mode set in the ReceiveMode
register), a wake event is signaled.
An example pseudo-packet (based on the ARP
packet example from Appendix A of the “OnNow
Network Device Class Power Management Specifi-
cation”) loaded into the TxFIFO of the ST201 is
shown in Figure 6.
TXFIFO
0xc2
0x71
0xf4
0x10
psuedo
0x00
packet
Frame patterns are written to the TxFIFO in a sin-
gle “pseudo-packet”. Prior to transferring this
pseudo-packet, the host system should first issue
TxReset (to reset the TxFIFO pointers and prevent
transmission) then prepare a TFD that points to a
single data buffer. The buffer should contain one or
more frame patterns placed contiguously. The
number of frame patterns is limited by the TxFIFO
size. The TxDMAFragLen field in the TFD must
exactly equal the sum of the frame pattern bytes.
Also, the host system must set WordAlign to ‘x1’ in
the TransmitFrameControl field of the TFD to pre-
vent frame word-alignment. Finally, the host sys-
tem must write the TFD’s address to the
TxDMAListPtr register to transfer the frame into the
TxFIFO.
0xf3
0x19
0x08
0xd7
FIGURE 6: Example Psuedo Packet
Using the pseudo packet in Figure 6, the ST201
will assert a wake event if a packet of the form
shown in Figure 7 is received whereby a 32-bit
CRC over the indicated bytes of the received
packet yields the value 0xf31908d7.
The frame patterns in the TxFIFO specify which
bytes in the incoming frames are to be examined.
A CRC is calculated over these bytes and com-
pared with a CRC value supplied in the frame pat-
tern. This matching technique may result in false
wake events being reported to the host system.
Each wake packet pattern contains one or more
byte-offset/byte-count pairs, an end-of-pattern
symbol, and a 4-byte CRC value. The byte-offset
indicates the number of frame bytes to be skipped
in order to reach the next group of bytes to be
included in the CRC calculation. The byte-count
indicates the number of bytes in the next group to
be included in the CRC calculation. End-of pattern,
which is a byte value of 00, indicates the end of the
pattern for that wake frame. Immediately following
the end-of-pattern is a 4-byte CRC. The CRC cal-
culation uses the same polynomial as the Ethernet
MAC FCS. The pseudo packet frame patterns are
described in the Registers and Data Structures
section.
Byte Offset
Within Packet
Received Packet
byte 12
0x0c
0x0d
byte 13
byte 21
0x15
byte 38
byte 39
byte 40
byte 41
0x26
0x27
0x28
0x29
FIGURE 7: Example Wake Packet
The ST201 also supports Magic Packet™ technol-
ogy developed by Advanced Micro Devices to
allow remote wake-up of a sleeping station on a
21
Sundance Technology
ST201
PRELIMINARY draft 2
network via transmission of a special frame. Once
the ST201 has been placed in Magic Packet mode
and put to sleep, it scans all incoming frames
addressed to it for a data sequence consisting of
16 consecutive repetitions of its own 48-bit Ether-
net MAC StationAddress. This sequence can be
located anywhere within the frame, but must be
preceded by a synchronization stream. The syn-
chronization stream is defined as 6 bytes of 0xFF.
For example, if the MAC address programmed into
Magic Packet, it signals a wake event on PMEN (if
PMEN assertion is enabled), and sets the MagicP-
ktEvent bit in WakeEvent.
The ST201 can also signal a wake event when it
senses a change in the network link state, either
from LINK_OK to LINK_FAIL, or vice versa. Link
state wake is controlled by the LinkEventEnable bit
in the WakeEvent register. At the time LinkEven-
tEnable is set by the host system, the ST201 sam-
ples the current link state. It then waits for the link
state to change. If the link state changes before the
ST201 returns to state D0 or LinkEventEnable is
cleared, LinkEvent is set in WakeEvent, and (if it is
enabled) the PMEN signal is asserted.
the
StationAddress
register
is
0x11:22:33:44:55:66, then the ST201 would be
scanning for the frame data shown in Figure 8.
Received Packet
HOST SYSTEM RELATED
INFORMATION
0xFFFFFFFFFFFF
0x112233445566
0x112233445566
0x112233445566
0x112233445566
0x112233445566
0x112233445566
0x112233445566
0x112233445566
0x112233445566
0x112233445566
0x112233445566
0x112233445566
0x112233445566
0x112233445566
0x112233445566
0x112233445566
PROGRAMMING THE MII MANAGEMENT
INTERFACE
Register accesses across the MII Management
Interface occur serially, and are controlled by
manipulating the MgmtClk, MgmtData, and Mgmt-
Dir bits in the PhyCtrl register. The direction of the
serial transmission is controlled by MgmtDir. Mgm-
mtDir is set when writing bits to the PHY device,
and cleared when reading bits from the PHY. Data
bits are read from and written to MgmtData. Mgmt-
Clk supplies the synchronization clock for the inter-
face.
Management frames are transmitted from the
ST201 to the PHY device using one or more Read,
Write, or Z cycles. The actions which must be
taken by the host system to perform a Read, Write,
or Z cycle are described below. Note, in the cycle
descriptions below, time delays of 200ns can gen-
erally be assumed from back-to back I/O cycles on
the PCI bus. The host system may also use an
arbitrarily long timer to guarantee meeting mini-
mum transition delays.
To perform a Read cycle, consisting of a single
data bit read from the PHY device, the host system
must follow the procedure below.
1. Clear MgmtClk
2. Wait a minimum of 200 ns
FIGURE 8: Example Magic Packet
3. Set MgmtClk
4. Wait a minimum of 200 ns
5. Read the next data bit from MgmtData
6. Wait a minimum of 200 ns
Magic Packet wake up is controlled by the MagicP-
ktEnable bit in the WakeEvent register. A wake
event can only take place in the D1, D2, or D3
states, and MagicPktEnable has no effect when
the ST201 is in the D0 power state. The Magic
Packet must also pass the address matching crite-
ria set in ReceiveMode. A Magic Packet may also
be a broadcast frame. When the ST201 detects a
To perform a Write cycle, consisting of a single
data bit written to the PHY device, the host system
should follow the procedure below.
1. Clear MgmtClk
2. Wait a minimum of 200 ns
22
Sundance Technology
ST201
PRELIMINARY draft 2
3. Set MgmtClk
written within the PHY device.
4. Write the desired data bit to MgmtData
5. Wait a minimum of 200 ns
7. Execute 2 write cycles to transmit the 2 bit
Write Turnaround value of 0x02.
8. Execute 16 write cycles to write the data to the
PHY register. Data bits are written starting with
register bit 15 and ending with register bit 0.
9. Execute a Z cycle to terminate the frame.
To perform a Z cycle used during the Turnaround
portion of a register read frame, the host system
should follow the procedure below.
1. Clear MgmtClk
2. Wait a minimum of 200 ns
3. Set MgmtClk
4. Clear MgmtDir
EEPROM COMMANDS
The EepromCtrl register provides the host with a
method for issuing commands to the ST201’s
serial EEPROM controller. Individual 16-bit word
locations within the EEPROM may be written, read
or erased. Also, the EEPROM’s WriteEnable, Writ-
eDisable, EraseAll and WriteAll commands can be
issued.
5. Wait a minimum of 200 ns
Using the read, write, and Z cycle procedures, a
Read management frame is executed as follows.
1. Set MgmtDir.
2. Execute 32 write cycles to transmit the 32 bit
Preamble of 0xffffffff.
Two-bit opcodes and 8-bit addresses are written to
the EepromCtrl register to cause the ST201 to
carry out the desired EEPROM command. If data is
to be written to the EEPROM, the 16-bit data word
must be written to EepromData by the host system
prior to issuing the associated write command.
Similarly, if data is to be read from the EEPROM,
the read data will be available via EepromData reg-
ister after issuing the associated read command.
3. Execute 2 write cycles to transmit the 2 bit
Start of Frame of 0x01.
4. Execute 2 write cycles to transmit the 2 bit
Operation Code of 0x02.
5. Execute 5 write cycles to transmit the 5 bit
PHY Address to identify the target PHY device
for the Read frame.
6. Execute 5 write cycles to transmit the 5 bit
Register Address to identify the register to be
read within the PHY device.
7. Execute a Z cycle to prepare the interface to
receive read data bits (first half of Read Turn-
around).
8. Execute a single read cycle (second half of
Read Turnaround). The bit read from the PHY
will be a zero if the PHY intends to respond to
the Read frame. A value of one indicates that
no PHY device is responding, and the data to
follow is invalid.
9. Execute 16 read cycles to read the data from
the PHY register. Data bits are read starting
with register bit 15 and ending with register bit
0.
A mechanism within the EEPROM interface auto-
matically disables writes and erasures to prevent
accidental data changes should power be inter-
rupted. The ST201 disables writes and erasures
after every write or erase type command has been
executed. To write or erase a series of locations,
the host must issue the WriteEnable command
prior to every write or erase type command.
The serial EEPROM can only clear bits to zero dur-
ing a write command and cannot set individual bits
to ones. Therefore, an Erase or EraseAll command
must be issued prior to attempting to write data to
the EEPROM.
The EEPROM is a particularly slow device. It is
important that the host wait until the EepromBusy
bit is false before issuing a command to EepromC-
trl.
10. Execute a Z cycle to terminate the frame.
Using the read, write, and Z cycle procedures, a
Write management frame is executed as follows.
1. Set MgmtDir.
2. Execute 32 write cycles to transmit the 32 bit
Preamble of 0xffffffff.
3. Execute 2 write cycles to transmit the 2 bit
Start of Frame of 0x01.
4. Execute 2 write cycles to transmit the 2 bit
Operation Code of 0x01.
5. Execute 5 write cycles to transmit the 5 bit
PHY Address to identify the target PHY device
for the Write frame.
6. Execute 5 write cycles to transmit the 5 bit
Register Address to identify the register to be
The procedure for a typical write operation to the
EEPROM is as follows:
1. Verify EepromBusy is false.
2. Issue the WriteEnable command
(opcode = 00 11xx xxxx)
3. Verify EepromBusy is false.
4. Issue EraseRegister command
(opcode = 11 aaaa aaaa)
5. Verify EepromBusy is false.
6. Write data pattern to EepromData.
7. Issue WriteEnable command
(opcode = 00 11xx xxxx)
23
Sundance Technology
ST201
PRELIMINARY draft 2
8. Verify EepromBusy is false.
9. Issue WriteRegister command
(opcode = 01 aaaa aaaa)
TxDMAList with the address of the TFD being
added.
4. Read TxDMAListPtr.
5. If TxDMAListPtr is zero, write the address of
the new TFD to TxDMAListPtr.
Step 4 through 8 may be skipped for certain types
of EEPROM devices.
6. Resume the TxDMA Logic by setting TxD-
MAResume bit. The TxDMA Logic will become
idle when it fetches a zero TxDMANextPtr
value from a TFD. One way to restart the
TxDMA process is by writing a non-zero value
to TxDMAListPtr.
ADAPTER TXDMA SEQUENCE
Beginning with the host system writing to the TxD-
MAListPtr register (when starting from an empty
TxDMAList, for instance), the ST201 performs the
following procedure during transfers of TxDMA
frames.
1. Verifies the TxDMAListPtr is non-zero.
2. Verifies not in the TxDMAHalt state.
3. Fetches the second dword from the TFD
pointed to by TxDMAListPtr and writes this
value into the TxFIFO.
4. One by one, fetches the TxDMAFragAddr/TxD-
MAFragLen entries from the TFD, and moves
the associated data fragments to the TxFIFO.
5. Sets the TxDMAComplete bit in the TFD.
6. If TxDMAHalt is in effect, waits until a TxD-
MAResume is issued.
When polling is enabled (TxDMAPollPeriod is non-
zero), TFD’s can be added to the end of the TxD-
MAList with no register accesses by writing the
address of the new TFD in the last TFD’s TxD-
MANextPtr field.
INSERTING A TFD AT THE HEAD OF THE
TXDMALIST
TFD’s cannot be added before the active TFD in
the TxDMAList, they can only be added after the
active (unfinished) TFD. The following sequence
describes the process for adding TFD’s to the head
of the TxDMAList when TxDMA polling is disabled
(TxDMAPollPeriod is zero).
7. If a transmit under run has occurred, waits until
the host system sets the TxReset bit.
8. Re-fetches the TFC and, if the TxDMAIndicate
bit is set, sets TxDMAComplete (which may in
turn cause an interrupt if the IntEnable masks
are set appropriately)
1. Set TxDMAHalt bit.
2. Wait for the TxDMAHalt to complete by polling
the TxDMAHalted bit. When halted, the TxD-
MAListPtr register will hold the address of the
TFD which just completed transfer into the
ST201 (the “last TFD in the TxDMAList”).
3. Find the last TFD in the TxDMAList, corre-
sponding to the TFD at the address held in the
TxDMAListPtr register. This will also be the last
TFD in the TxDMAList with the TxDMACom-
plete bit set.
4. Copy the value in the “last TFD’s” TxDMANex-
tPtr into the TxDMANextPtr field of the TFD to
be inserted.
5. Update TxDMANextPtr field in the “last TFD”
with the address of the inserted TFD.
6. Read TxDMAListPtr.
9. Fetches the TxDMANextPtr from the current
TFD. If TxDMANextPtr is zero, the TxDMA
Logic becomes idle. If polling is disabled (TxD-
MAPollPeriod is zero), the TxDMA Logic waits
for a non-zero value to be written to TxDMAL-
istPtr. If polling is enabled (TxDMAPollPeriod
is non-zero), the old value in TxDMAListPtr is
preserved, and the ST201 polls on TxDMAN-
extPtr in the TFD until it fetches a non-zero
value from it. If the value fetched from TxD-
MANextPtr is non-zero, then the value is
loaded into TxDMAListPtr, advancing the
ST201 to the new TFD.
10. With a new TFD to process, the ST201 returns
to step 2.
7. If TxDMAListPtr is zero, write the address of
the inserted TFD to TxDMAListPtr.
8. Resume the TxDMA Logic by setting TxD-
MAResume.
ADDING TFD’S TO THE END OF THE
TXDMALIST
When polling is enabled (TxDMAPollPeriod is non-
zero), TFD’s can be inserted to the head of the
TxDMAList with no register accesses as follows.
1. Find the first TFD in the list with TxDMACom-
plete bit cleared (the “first TFD”).
2. Set the “first TFD’s” TxDMANextPtr to zero.
3. Check the TxDMAComplete bit of “the first
TFD”. If clear, proceed to the next step. If set,
it’s too late to insert the new TFD at the loca-
The following sequence describes the process for
adding TFD’s to the end of the TxDMAList when
TxDMA polling is disabled (TxDMAPollPeriod is
zero).
1. Set the TxDMAHalt bit.
2. Wait for the TxDMAHalt to complete by polling
on TxDMAHalted bit.
3. Update TxDMANextPtr in the last TFD in the
24
Sundance Technology
ST201
PRELIMINARY draft 2
tion of the “first TFD” in the TxDMAList.
Restore the TxDMANextPtr of the “first TFD”,
and restart this process.
ST201 updates the RxDMAStatus register with
any error codes from the frame transfer and
sets the RxDMAComplete bit.
4. Copy the value of the “first TFD’s” TxDMANex-
tPtr into the TxDMANextPtr field of the inserted
TFD.
5. Update the TxDMANextPtr field of the “first
TFD” with the address of the inserted TFD.
9. Issues an internal RxDiscard and waits for
completion.
10. If a RxDMAHalt has been asserted, waits until
a RxDMAResume has been issued.
11. Fetches RxDMANextPtr from the RFD. If RxD-
MANextPtr is zero and polling is enabled, the
ST201 begins a polling loop. If polling is dis-
abled, the ST201 loads the fetched value into
RxDMAListPtr.
12. Writes ReceiveFrameStatus to the RFD in host
memory.
13. If a polling loop has begun, polls on RxDMAN-
extPtr until a non-zero value is fetched. Loads
the value into RxDMAListPtr.
TRANSMIT INTERRUPT OPTIMIZATIONS
The transmit mechanism can be optimized by the
host system, allowing a reduction in the number of
interrupts generated. The host system can limit the
number of frames in the TxDMAList for which a
TxDMAComplete interrupt is generated. For exam-
ple, the host system could only set TxDMAIndicate
for the frame on the tail of the list (clearing TxD-
MAIndicate for the current tail before adding a new
frame to the list). Or it might require an interrupt
every N frames. In any case, on each interrupt it
would then dequeue all of the frames which were
transferred via TxDMA before that interrupt
occurred (TFDs in which TxDMAComplete is set).
Obviously, the host system is responsible for the
trade-off between latency and the number of inter-
rupts generated by the ST201.
14. If the RxDMAListPtr value is zero (polling is
disabled), then the RxDMA Logic becomes
idle, waiting for a non-zero value to be written
into the RxDMAListPtr register.
15. Repeat process at step 1.
WAKE EVENT PROGRAMMING
This section describes the sequences involved in
programming ST201 for wake events.
Powering down the ST201 will typically occur while
in the operating state (D0). The host system is noti-
fied by the operating system that a power state
change is imminent. The host system prepares for
power down with these steps.
1. Halt the ST201 TxDMA process, halt the
TxDMA Logic, wait for any TxDMA in progress
to complete, wait for any transmissions to com-
plete, and issue TxReset to reset the TxFIFO
pointers.
2. Perform the RxDMA process for any receive
frames remaining in RxFIFO, halt RxDMA
Logic (frames will potentially keep filling the
RxFIFO between now and when operating sys-
tem powers down the system, and once the
power down state is entered and Wakeup
Packet scanning enabled, these frames in the
RxFIFO will be scanned and could potentially
wake the system immediately).
3. Clear IntEnable register so no interrupts occur
before PowerState is changed.
4. Save any volatile state, such as a pending
power state and the HashTable settings, to
system memory (system memory is restored
after a power down).
5. The host system transfers Wakeup Packet pat-
terns to the TxFIFO (if Wakeup Packets are to
be enabled) and programs the WakeEvent reg-
ister to enable the desired wake events. The
RXDMA SEQUENCE
The ST201 performs the following procedure dur-
ing transfers of RxDMA frames.
1. Verifies the RxDMAListPtr register is non-zero.
2. Verifies not in the RxDMAHalt state.
3. Resets the RxDMAStatus register.
4. Fetches ReceiveFrameStatus from the current
RFD. If the current RFD has the RxDMACom-
plete bit set, the ST201 performs an implicit
RxDMAHalt, halting the RxDMA process. (If
RxDMAPollPeriod contains a nonzero value,
the ST201 will then poll on the RxDMACom-
plete bit, waiting for it to be cleared before con-
tinuing.) Otherwise, the RxDMA process
continues.
5. Waits for the top receive frame to become eli-
gible for RxDMA.
6. Transfers the frame via RxDMA into the frag-
ments specified in the RFD, or into the implied
buffer if ImpliedBufferEnable is set. If there is
more data in the frame than space in the frag-
ment buffers, the ST201 generates a RxD-
MAOverflow error.
7. As the frame is being transferred by the
RxDMA process, the ST201 maintains the
RxDMAStatus register, specifically the RxD-
MAFrameLen field.
8. At the end of the frame RxDMA process, the
25
Sundance Technology
ST201
PRELIMINARY draft 2
host system then returns to the operating sys-
tem an indication of readiness to be powered
down (making sure to leave the ReceiveMode
register set to receive the appropriate Wake/
Magic packets). The operating system eventu-
ally writes to the PowerMgmtCtrl register, plac-
ing the ST201 in one of the power down states,
and enabling PMEN assertion, while the
ST201 monitors for the occurrence of enabled
wake events.
WAKE EVENT
When a desired wake event occurs, the ST201
sets the appropriate event bit in the WakeEvent
register, sets the PmeStatus bit in the PowerMg-
mtCtrl register, and asserts the PMEN pin.
The host system responds to PMEN by scanning
the power management configuration registers of
all devices, looking for the device which asserted
PMEN. If the device with the ST201 signaled wake,
the system will find PmeStatus set in ST201’s Pow-
erMgmtCtrl register. The operating system then
clears the PmeEn bit in the PowerMgmtCtrl regis-
ter causing PMEN to be de-asserted.
The operating system raises the power state (prob-
ably to D0) by writing to the PowerState bits in the
PowerMgmtCtrl register. If the ST201 was previ-
ously in the D3 state, PCI configuration is lost and
must be restored by the operating system.
The host system must set TxReset to clear any
wake patterns out of the TxFIFO (if this is not done,
the patterns will be treated as frames and transmit-
ted once the transmitter is enabled).
The host system reads the WakeEvent register to
determine the wake event, and if requested,
passes it back to the operating system. The host
system restores any volatile state that was saved
in the power down sequence. The host system re-
enables interrupts by programming IntEnable. The
host system restores the RxDMAList (and any
other data structures required for operation). Any
wake packets in the RxFIFO are transferred by
RxDMA and passed to the operating system.
26
Sundance Technology
ST201
PRELIMINARY draft 2
REGISTERS AND DATA STRUCTURES
DMA DATA STRUCTURES
A TFD is used to move data, which is to be transmitted onto a LAN, from host system memory to the
TxFIFO within the ST201. A TFD is 16 to 512 bytes in length, and it’s location in host system memory is
indicated by the value in the TxDMAListPtr register.
A RFD is used to move data, which has been received from a LAN, from the RxFIFO within the ST201 to
host system memory. A RFD is 16 to 512 bytes in length, and it’s location in host system memory is indi-
cated by the value in the RxDMAListPtr register.
Figure 9 shows the two DMA data structures.
HOST SYSTEM MEMORY
HOST SYSTEM MEMORY
Offset from
Offset from
TFD Start
0x00
RFD Start
Next TFD Ptr.
Next RFD Ptr.
0x00
TxFrameControl
0x04
RxFrameStatus
0x04
1st TxDMAFragAddr 0x08
1st TxDMAFragLen 0x0c
2nd TxDMAFragAddr 0x10
2nd TxDMAFragLen 0x14
1st RxDMAFragAddr 0x08
1st RxDMAFragLen 0x0c
2nd RxDMAFragAddr 0x10
2nd RxDMAFragLen 0x14
TFD
RFD
nth TxDMAFragAddr 0x00+n·8
nth TxDMAFragLen 0x04+n·8
nth RxDMAFragAddr 0x00+n·8
nth RxDMAFragLen
0x04+n·8
FIGURE 9: TFD and RFD DMA Data Structures
27
Sundance Technology
ST201
PRELIMINARY draft 2
TXDMAFRAGADDR
Class....................DMA Data Structures, TFD
Base Address ......Start of TFD
Address Offset.....0x00+n·8 for nth fragment
Access Mode.......Read/Write
Width ...................32 bits
BIT
BIT NAME
BIT DESCRIPTION
31..0
TxDMAFragAddr
Transmit Fragment Address contains the physical address of a contig-
uous block of data to be transferred by TxDMA into the ST201 and
transmitted. A fragment can start on any byte boundary.
28
Sundance Technology
ST201
PRELIMINARY draft 2
TXDMAFRAGLEN
Class....................DMA Data Structures, TFD
Base Address ......Start of TFD
Address Offset.....0x04+n·8 for nth fragment
Access Mode.......Read/Write
Width ...................32 bits
Transmit Fragment Length (TxDMAFragLen) contains fragment length and control information for the
block of data pointed to by the corresponding TxDMAFragAddr.
BIT
BIT NAME
FragLen
BIT DESCRIPTION
12..0
The length of the contiguous block of data pointed to by the TxDMA-
FragAddr. The maximum fragment length is 8192 bytes.
30..13
31
Reserved
Reserved for future use. Should be set to 0.
TxDMAFragLast
Set by the host system to indicate the last fragment of the transmit
frame and that the ST201 should proceed to the next TFD.
29
Sundance Technology
ST201
PRELIMINARY draft 2
TXDMANEXTPTR
Class....................DMA Data Structures, TFD
Base Address ......Start of TFD
Address Offset.....0x00
Access Mode.......Read/Write
Width ...................32 bits
BIT
BIT NAME
BIT DESCRIPTION
31..0
TxDMANextPtr
Transmit Next Pointer, the first double word in the TFD contains the
physical address of the next TFD in the TxDMAList. The value of zero
accompanies the last frame of the list and it indicates there are no
more TFD’s in the TxDMAList. All TFD’s must be aligned on 8-byte
physical address boundaries, requiring Bits [2..0] of TxDMANextPtr to
be zero.
30
Sundance Technology
ST201
PRELIMINARY draft 2
TXFRAMECONTROL
Class....................DMA Data Structures, TFD
Base Address ......Start of TFD
Address Offset.....0x04
Access Mode.......Read/Write
Width ...................32 bits
TxFrameControl contains frame control information for the TxDMA function and the transmit function.
BIT
1..0
BIT NAME
WordAlign
BIT DESCRIPTION
These bits determine the boundary to which transmit frame lengths are
rounded up in the TxFIFO, and transmitted onto the network medium.
00: Align to dword
10: Align to word
X1: Align disabled
9..2
FrameId
This field can be used as a frame ID or sequence number. This value is
saved with the frame in the TxFIFO, and made visible in the TxFrameId
register while the frame is being transmitted. When a transmit error
occurs, the driver checks TxFrameId to determine which frame experi-
enced the error.
12..10
13
Reserved
Reserved for future use. Should be set to 0.
FcsAppendDisable
The host system sets this bit to prevent the ST201 from appending the
4-byte FCS to the end of the current frame. In this case, the host sys-
tem must supply the frame’s FCS as part of the data transferred by
TxDMA to the TxFIFO. An exception exists when a transmit under run
occurs; in this case a guaranteed-bad FCS will be appended to the
frame by the ST201. When FcsAppendDisable is cleared, the ST201
will compute and append FCS to this transmit frame.
14
15
Reserved
TxIndicate
Reserved for future use. Should be set to 0.
The host system sets this bit to request a TxComplete interrupt upon
completion of MAC transmission of this frame. If TxComplete is
cleared, no interrupt of transmit completion will be given by the ST201,
unless a transmit error occurs.
16
TxDMAComplete
Indicates that the frame transfer by TxDMA is complete. The ST201
sets this bit after it has finished transferring via the TxDMA process all
of the fragments specified in the TFD.
30..17
31
Reserved
Reserved for future use. Should be set to 0.
TxDMAIndicate
Set if the host system desires a TxDMAComplete interrupt upon com-
pletion of TxDMA of this frame. The TFC is read twice by the ST201;
the first time to write the TFC to the TxFIFO before frame data transfer,
and again after the TxDMA operation is complete to test TxDMAIndi-
cate in order to determine whether to generate an interrupt. This allows
the host system time to change TxDMAIndicate while the transfer by
TxDMA is in progress.
31
Sundance Technology
ST201
PRELIMINARY draft 2
RXDMANEXTPTR
Class....................DMA Data Structures, RFD
Base Address ......Start of RFD
Address Offset.....0x00
Access Mode.......Read/Write
Width ...................32 bits
BIT
BIT NAME
BIT DESCRIPTION
31..0
RxDMANextPtr
The first dword in the RFD contains the physical address of the next
RFD in the RxDMAList. If this is the last RFD in the RxDMAList, then
this value must be zero. RFDs must be aligned on 8-byte physical
address boundaries.
32
Sundance Technology
ST201
PRELIMINARY draft 2
RXFRAMESTATUS
Class....................DMA Data Structures, RFD
Base Address ......Start of RFD
Address Offset.....0x04
Access Mode.......Read/Write
Width ...................32 bits
The second dword in the RFD is ReceiveFrameStatus. At the end of a RxDMA frame transfer, the ST201
writes the value of the RxDMAStatus register into this location in the RFD. The bit definitions for
TxFrameStatus for bits[31..29] and [27..0] are identical to the corresponding bits of the I/O Register RxDM-
AStatus. Only bit[28] differs between the RFD field RxFrameStatus and the register RxDMAStatus.
BIT
BIT NAME
BIT DESCRIPTION
12..0
RxDMAFrameLen
During frame RxDMA, RxDMAFrameLen gives a real-time indication of
the number of bytes transferred by RxDMA for the frame. RxDMAFra-
meLen is cleared when the ST201 fetches a new RxDMAListPtr, and
counts up in steps no larger than a bus master burst. When the frame
has been completely transferred by RxDMA, RxDMAFrameLen indi-
cates the true frame length, except in the case where the frame is
larger than the number of bytes specified in the RxDMA fragments. In
this case, the RxDMAOverflow bit will be set.
13
14
Reserved
Reserved for future use. Should be set to 0.
RxFrameError
Indicates that an error occurred in the receipt of the frame. The driver
should examine bits 16 through 20 to determine the type of error(s).
This bit is undefined until RxDMAComplete bit is set.
15
16
RxDMAComplete
RxFIFOOverrun
Indicates that the frame transfer by RxDMA is complete. Unless a
RxDMA halt is in effect this bit would normally only remain set momen-
tarily (too short for the software to read it) since the hardware will then
fetch the next RFD.
Indicates that the hardware was unable to remove data from the
RxFIFO quickly enough (most likely because the software failed to free
a RFD quickly enough, or kept the ST201 in the RxDMAHalt state for
too long). Bytes will be missing from the frame at one or more locations
in the frame (unpredictable). This bit is undefined until RxDMACom-
plete bit is set.
17
RxRuntFrame
Indicates that the frame was a runt (less than 60 bytes). Normally such
frames are not transferred by RxDMA unless RxEarlyThresh is set to a
value less than the actual size of the runt frame, and the RxEarlyEn-
able of MacCtrl register must be set. This bit is undefined until RxDMA-
Complete bit is set.
18
19
20
RxAlignmentError
RxFCSError
Indicates that the frame had an alignment error (bad FCS and dribble
bits). This bit is undefined until RxDMAComplete bit is set.
Indicates a FCS checksum error on the frame data. This bit is unde-
fined until RxDMAComplete bit is set.
RxOversizedFrame Indicates the frame size was equal to or greater than the value set in
the MaxFrameSize register. This bit is undefined until RxDMACom-
plete bit is set.
33
Sundance Technology
ST201
PRELIMINARY draft 2
BIT
BIT NAME
Reserved
BIT DESCRIPTION
Reserved for future use. Should be set to 0.
22..21
23
DribbleBits
Indicates that the frame had accompanying dribble bits. This bit is
informational only, and does not indicate a frame error.
24
RxDMAOverflow
Indicates that the RFD had insufficient buffer space for the frame data
and there were still data left to be transferred by RxDMA when the
ST201 ran out of fragment space. The ST201 will transfer what it can
into the buffers provided, discard the remainder of the frame and set
this bit.
27..25
28
Reserved
Reserved for future use. Should be set to 0.
ImpliedBufferEn-
able
This bit enables a special RxDMA mode. Setting this bit instructs the
ST201 not to fetch any RxDMAFragAddr/RxDMAFragLen entries from
this RFD. Instead, the ST201 assumes there is one receive buffer of
length 1528 bytes, starting immediately after ReceiveFrameStatus at
(RFD address + 8).
The host system sets this bit when it prepares the RFD. The ST201
tests this bit before RxDMA a frame, at the same time it tests the RxD-
MAComplete bit. When the ST201 updates ReceiveFrameStatus at the
end of the RxDMA operation (in order to set RxDMAComplete), the
value written to ImpliedBufferEnable is undefined. A driver cannot
assume a certain value is left in this bit after the RFD is used. There-
fore, the driver must write the desired value to this bit every time it
releases a RFD to the ST201. This mode of operation reduces the
number of information fetches by the ST201, and is intended for server
applications in which frames are received into a ring of maximum frame
sized buffers.
31..29
Reserved
Reserved for future use. Should be set to 0.
34
Sundance Technology
ST201
PRELIMINARY draft 2
RXDMAFRAGADDR
Class....................DMA Data Structures, RFD
Base Address ......Start of RFD
Address Offset.....0x00+n·8 for nth fragment
Access Mode.......Read/Write
Width ...................32 bits
BIT
BIT NAME
BIT DESCRIPTION
31..0
RxDMAFragAddr
The third and all subsequent odd dwords in the RFD contains the phys-
ical address of a contiguous block of system memory to which receive
data is to be transferred by RxDMA. A fragment can start on any byte
boundary.
35
Sundance Technology
ST201
PRELIMINARY draft 2
RXDMAFRAGLEN
Class....................DMA Data Structures, RFD
Base Address ......Start of RFD
Address Offset.....0x04+n·8 for nth fragment
Access Mode.......Read/Write
Width ...................32 bits
The fourth and all subsequent even dwords in the RFD contains fragment length and control information
for the block of data pointed to by the previous RxDMAFragAddr.
BIT
BIT NAME
FragLen
BIT DESCRIPTION
12..0
The length of the contiguous block of data pointed to by the previous
RxDMAFragAddr.
30..13
31
Reserved
Reserved for future use. Should be set to 0.
RxDMALastFrag
Set by the host system to indicate the last fragment of the receive
frame.
36
Sundance Technology
ST201
PRELIMINARY draft 2
WAKE EVENT DATA STRUCTURES
The first Wake Event Data Structure is the Pseudo Packet. A Pseudo Packet is a set of patterns loaded
into the ST201 TxFIFO which specify bytes to be examined within received frames. A CRC is calculated
over these bytes and compared with a CRC value supplied in the Pseudo Packet. If a match is found, the
ST201 issues a Wake Event. The matching technique may result in false wake events being reported to
the host system. Each Pseudo Packet consists of one or more byte-offset/byte-count pairs (or Pseudo Pat-
terns), a terminator symbol, and a 4-byte CRC value. The byte offsets within the Pseudo Patterns indicate
the number of received frame bytes to be skipped in order to reach the next group of bytes to be included
in the CRC calculation. The byte-counts within the Pseudo Patterns indicate the number of bytes in the
next group to be included in the CRC calculation. The terminator indicates the end of the Pseudo Patterns
for the Pseudo Packet. Immediately following the terminator is a 4-byte CRC. If there is another Pseudo
Packet, it will immediately follow the CRC value.
The second Wake Event Data Structure is the Magic Packet. Magic Packets are uniquely formatted
frames, which upon reception invoke a Wake Event by the ST201. Once the ST201 has been placed in
Magic Packet mode and put to sleep, it scans all incoming frames addressed to it for a data sequence con-
sisting of a synchronization stream followed immediately by 16 consecutive repetitions of the station’s own
48-bit Ethernet MAC station address. The sequence can be located anywhere within the received frame.
The pseudo packet and Magic Packet data structures are shown in Figure 10.
ST201 TXFIFO
Received Packet
Ethernet Header
PsuedoPattern 1
PsuedoPattern 2
0x00
0x01
PsuedoPattern n
Terminator
0x00+n-1
0x00+n
psuedo
packet
0x00
0x06
MagicSyncStream
0x00+n+1
PsuedoCRC
Magic
Packet™
MagicSequence
Ethernet CRC
FIGURE 10: Wake Event Data Structures, Pseudo Packet and Magic Packet
37
Sundance Technology
ST201
PRELIMINARY draft 2
PSEUDOPATTERN
Class....................Wake Event Data Structures, Pseudo Packet
Base Address ......Start of Pseudo Packet
Address Offset.....0x00 thru 0x00+n-1 for nth PseudoPattern
Access Mode.......Write only
Width ...................8 bits
BIT
3..0
BIT NAME
ByteCount
BIT DESCRIPTION
ByteCount can take on a value of 0x0 to 0xe. A value of 0xf indicates
an extended value. The extended value will occupy 8 bits and is con-
tained in the next PseudoPattern. If both the ByteOffset and the Byte-
Count values are 0xf, the next PseudoPattern will be the extended
ByteOffset, and the PseudoPattern after that will be the extended Byte-
Count.
7..4
ByteOffset
ByteOffset can take on a value of 0x0 to 0xe. A value of 0xf indicates
an extended value. The extended value will occupy 8 bits and is con-
tained in the next PseudoPattern. If both the ByteOffset and the Byte-
Count values are 0xf, the next PseudoPattern will be the extended
ByteOffset, and the PseudoPattern after that will be the extended Byte-
Count.
38
Sundance Technology
ST201
PRELIMINARY draft 2
TERMINATOR
Class....................Wake Event Data Structures, Pseudo Packet
Base Address ......Start of Pseudo Packet
Address Offset.....0x00+n for n PseudoPattern
Access Mode.......Write only
Width ...................8 bits
BIT
7..0
BIT NAME
Terminator
BIT DESCRIPTION
A value of 0x00 indicates the end of the PseudoPattern.
39
Sundance Technology
ST201
PRELIMINARY draft 2
PSEUDOCRC
Class....................Wake Event Data Structures, Pseudo Packet
Base Address ......Start of Pseudo Packet
Address Offset.....0x00+n+1 for n PseudoPatterns
Access Mode.......Write only
Width ...................32 bits
The 32-bit CRC as defined in the IEEE 802.3 Ethernet standard for the FCS, taken over the bytes (indi-
cated by the PseudoPattern values) of a received frame.
BIT
7..0
BIT NAME
BIT DESCRIPTION
PsuedoCRCbyte0
PsuedoCRCbyte1
PsuedoCRCbyte2
PsuedoCRCbyte3
The least significant byte of the PseudoCRC.
The second lest significant byte of the PseudoCRC.
The second most significant byte of the PseudoCRC.
The most significant byte of the PseudoCRC.
15..8
23..16
31..24
40
Sundance Technology
ST201
PRELIMINARY draft 2
MAGICSYNCSTREAM
Class....................Wake Event Data Structures, Magic Packet
Base Address ......Start of Magic Packet
Address Offset.....0x00
Access Mode.......Read only
Width ...................48 bits
BIT
BIT NAME
BIT DESCRIPTION
47..0
MagicSyncStream
A stream of 6 bytes with the value 0xff indicates the start of the Magic-
Sequence.
41
Sundance Technology
ST201
PRELIMINARY draft 2
MAGICSEQUENCE
Class....................Wake Event Data Structures, Magic Packet
Base Address ......Start of Magic Packet
Address Offset.....0x06
Access Mode.......Read only
Width ...................768 bits
BIT
BIT NAME
BIT DESCRIPTION
767..0
MagicSequence
A sequence of 96 bytes, consisting of 16 consecutive, identical 6 bytes
sequences, where each 6 byte sequence equals the station address of
the station receiving the Magic Packet.
42
Sundance Technology
ST201
PRELIMINARY draft 2
I/O REGISTERS
The host interacts with the ST201 mainly through slave registers, which occupy 128 bytes in the host sys-
tem’s I/O space, memory space, or both. Generally, registers are referred to as “I/O registers”, implying
that the registers may in fact be mapped and accessed by the host system in memory space. I/O registers
must be accessed with instructions that are no larger than the bit-width of that register. For instance, even
though the FramesWithExcessiveDeferral, FramesLostRxErrors, and FramesWithDeferredXmission regis-
ters all appear in the same double word at offset 78, it is not legal to read all three registers with a single
32-bit I/O read instruction.
The ST201 I/0 register layout is show in Figure 11.
43
Sundance Technology
ST201
PRELIMINARY draft 2
byte 3
byte 2
byte 1
BcstFramesRcvdOk
byte 0
Offset
0x7c
McstFramesRcvdOk
FramesAbortXSColls
SingleColFrames
McstFramesXmtdOk
FramesWEXDeferral
MultipleColFrames
BcstFramesXmtdOk
FramesLostRxErrors FramesWDeferedXmt 0x78
LateCollisions
CarrierSenseErrors
0x74
0x70
FramesReceivedOk
FramesTransmittedOk
OctetsTransmittedOk(1)
OctetsReceivedOk(1)
HashTable(3)
OctetsTransmittedOk(0)
OctetsReceivedOk(0)
HashTable(2)
0x6c
0x68
0x64
0x60
HashTable(1)
HashTable(0)
PhyCtrl
TxReleaseThresh
ReceiveMode
0x5c
0x58
0x54
0x50
MaxFrameSize
StationAddress(1)
MACCtrl(1)
StationAddress(2)
StationAddress(0)
MACCtrl(0)
IntStatus
IntEnable
0x4c
0x48
0x44
0x40
IntStatusAck
Countdown
TxFrameId
TxStatus
WakeEvent
ExpRomAddr
ExpRomData
RxEarlyThresh
FIFOCtrl
TxSrartThresh
0x3c
0x38
0x34
0x30
EepromCtrl
EepromData
AsicCtrl
0x2c
0x28
0x24
0x20
0x1c
0x18
0x14
0x10
DebugCtrl
RxDMAPollPeriod
RxDMAUrgentThresh
RxDMABurstThresh
RxDMAListPtr
RxDMAStatus
0x0c
0x08
0x04
0x00
TxDMAPollPeriod
TxDMAUrgentThresh
TxDMABurstThresh
TxDMAListPtr
DMACtrl
FIGURE 11: ST201 I/O Register Layout
44
Sundance Technology
ST201
PRELIMINARY draft 2
ASICCTRL
Class....................I/O Registers, Control and Status
Base Address ......IoBaseAddress register value
Address Offset.....0x30
Access Mode.......Read/Write
Width ...................32 bits
AsicCtrl provides chip-specific, non-host-related settings. The contents of the least significant byte of Asic-
Ctrl are read from EEPROM at reset.
BIT
BIT NAME
Reserved
BIT DESCRIPTION
0
1
Reserved for future use. Should be set to 0.
ExpRomSize
Specifies the size of the Expansion ROM installed on the adapter, as
follows:
0 = 32 kB (default after reset)
1 = 64 kB
2
3
4
TxLargeEnable
RxLargeEnable
ExpRomDisable
This read/write bit, when set, enables transmission of frames that are
larger than the TxFIFO. Since ST201’s TxFIFO size is 2KB, this bit can
be left clear (the reset default).
This read/write bit, when set, enables reception of frames that are
larger than the RxFIFO. Since ST201’s RxFIFO size is 2KB, this bit
can be left clear (the reset default).
This bit, when set, disables accesses to the on-adapter Expansion
ROM. This bit is included to allow bypassing the Expansion ROM with-
out having to physically remove it from the board. When this bit is set,
the ST201 responds to any read in its configured Expansion ROM
space by returning 00000000h, and it ignores writes to the Expansion
ROM. This bit resets to 0.
5
6
7
PhySpeed10
PhySpeed100
PhyMedia
This read-only bit, when set, indicates the 10Mb/s operation is avail-
able from the PHY on the adapter. “0” indicates the PHY is not 10Mb/s
capable.
This read-only bit, when set, indicates the 100Mb/s operation is avail-
able from the PHY on the adapter. “0” indicates the PHY is not 100Mb/
s capable.
This read-only bit indicates the media type that is available on the
adapter. “0” indicates twisted-pair media, and “1” indicates fiber media.
The combination of PhyMedia, PhySpeed100, and PhySpeed10 will
determine the capability of the adapter. For example, [7,6,5] =
000: undefined
001: 10BASE-T PHY
010: 100BASE-T PHY
011: 10BASE-T and 100BASE-T dual-speed PHY
100: undefined
101: 10BASE-F PHY
110: 100BASE-F PHY
111: 10BASE-F and 100BASE-F dual-speed PHY
45
Sundance Technology
ST201
PRELIMINARY draft 2
BIT
BIT NAME
BIT DESCRIPTION
10..8
ForcedConfig
These bits are used to place the ST201 into Forced Configuration
mode. The bit values are latched in from ED[2..0] pins with a logic
inversion at the end of RSTN or power on reset.
000: no forced configuration
001: forced configuration mode 1
010-111: reserved
Note: When ForcedConfig[10] is set, the ST201 will use an alternate
DeviceID and VendorID.
11
D3ResetDisable
This read/write bit, when set, indicates that the ST201 is configured for
operation in an AMD-style (pre-ACPI) Wake-On-LAN environment.
Specifically, when the ST201 is in the D3 power state, assertion of PCI
RSTN will not reset the ST201. It is cleared upon reset.
12
13
Reserved
Reserved for future use. Should be set to 0.
SpeedupMode
This read/write bit is used for simulation only. When set, it indicates a
speed-up mode to decrease simulation time. The bit value is latched in
from ED5 pin with a logic inversion at the end of RSTN or power on
reset.
14
LEDMode
This bit is used to control the LED outputs. When cleared (default after
reset), the LED outputs are in mode 0; when set, the LED outputs are
in mode 1.
LEDPWRN: Mode 0: steady ON when power is applied, flashing when
frames are being transmitted. Mode 1: ON all the time.
LEDLNKN: Mode 0: steady ON when link is up, and flashing when
frames are being received. Mode 1: steady ON when link is up, and
flashing when frames are being transmitted or received.
LEDDPLXN: Mode 0/1: steady ON when PHY is in full duplex mode,
and flashing when collisions are being detected.
LEDSPDN: Mode 0/1: steady ON when link speed is 100mb/s, and
OFF when link speed is 10Mb/s.
15
16
RstOutPolarity
GlobalReset
When set, RSTOUT is asserted high. When cleared, RSTOUT is
asserted low.
This is a self-clearing global reset bit for the entire ST201. This bit con-
trols reset to various logic blocks depending on the values of the selec-
tion bits [24..19]. The ST201 should be re-initialized after a
GlobalReset. The registers in the PCI configuration space are not reset
by the GlobalReset; they are handled by the Power On Reset Test rou-
tine executed by the host.
17
18
RxReset
TxReset
When set, will reset receive logic throughout the ST201, including net-
work interface receive logic, RxFIFO control logic, and RxDMA Logic if
the corresponding selection bits [21..19] are set. This bit is self-clear-
ing. The RxReset should not be used after initialization except to
recover from receive errors such as a RxFIFO under run.
When set, will reset transmit logic throughout the ST201, including net-
work interface transmit logic, TxFIFO control logic, and TxDMA Logic,
if the corresponding selection bits [21..19] are set. This bit is self-clear-
ing. The TxReset is required after a transmit under run error.
46
Sundance Technology
ST201
PRELIMINARY draft 2
BIT
19
BIT NAME
DMA
BIT DESCRIPTION
When set, together with GlobalReset, RxReset, or TxReset bits, will
reset RxDMA and TxDMA Logic, including: TxDMAListPtr, RxDMAL-
istPtr, TxDMAComplete TxDMAInProg RxDMAComplete and RxEarly-
Enable in DMACtrl and RxDMAStatus. When cleared, reset will not
have action on the DMA Logic. This bit is self-clearing. Setting this bit
has no meaning if the corresponding reset bits are not set.
20
21
22
FIFO
When set, together with GlobalReset, RxReset, or TxReset bits, will
reset FIFO control logic, including TxStartThresh, TxReleaseThresh,
and RxEarlyThresh. When cleared, reset will not have action on the
DMA Logic. This bit is self-clearing. Setting this bit has no meaning if
the corresponding reset bits are not set.
Network
Host
When set, together with GlobalReset, RxReset, or TxReset bits, will
reset network interface logic, including CSMA/CD MAC core, Receive-
Mode, TxStatus, and the statistics registers. When cleared, reset will
not have action on the network logic. This bit is self-clearing. Setting
this bit has no meaning if the corresponding reset bits are not set.
When set, together with GlobalReset bit, will reset host bus interface
logic, including IntStatus, IntEnable, and Countdown. When cleared,
reset will not have action on the host bus interface logic. This bit is self-
clearing. Setting this bit has no meaning if the corresponding Global-
Reset bit is not set.
23
24
AutoInit
RstOut
When set, together with GlobalReset bit, will reset auto-initialize state
machine logic and EEPROM data is reloaded. This bit is self-clearing.
Setting this bit has no meaning if the corresponding GlobalReset bit is
not set.
When set, together with GlobalReset bit, will assert RSTOUT accord-
ing to RstOutPolarity. When cleared, reset will not cause any action on
RSTOUT. This bit is self-clearing. Setting this bit has no meaning if the
corresponding GlobalReset bit is not set.
25
26
InterruptRequest
ResetBusy
When set, the ST201 will assert IntRequested bit in the IntStatus regis-
ter. This bit is self-clearing.
When set, this bit indicates the reset is in progress. As the adapter’s
serial EEPROM may need to be read as part of the reset process, this
operation can take as long as 1 ms to complete. The ResetBusy bit
must be polled to be assured that the reset operation has completed.
31..27
Reserved
Reserved for future use. Should be set to 0.
47
Sundance Technology
ST201
PRELIMINARY draft 2
DEBUGCTRL
Class....................I/O Registers, Control and Status
Base Address ......IoBaseAddress register value
Address Offset.....0x1a
Access Mode.......Read/Write
Width ...................16 bits
DebugCtrl selects the functions of the GPIO pins. DebugCtrl is cleared by reset.
BIT
BIT NAME
GPIO0Ctrl
BIT DESCRIPTION
0
1
2
This bit controls the GPIO0 pin. When cleared, GPIO0 pin is an input.
When set, GPIO0 pin is an output. This bit is cleared on reset.
GPIO1Ctrl
GPIO0
This bit controls the GPIO1 pins. When cleared, GPIO1 pin is an input.
When set, GPIO1 pin is an output. This bit is cleared on reset.
When read, this bit shows the status values of the GPIO0 pin. When
written into, this bit will drive the GPIO0 pin if GPIO0Ctrl is set, and
GPIO0 pin functions as an output.
3
GPIO1
When read, this bit shows the status values of the GPIO1 pin. When
written into, this bit will drive the GPIO1 pin if GPIO1Ctrl is set, and
GPIO1 pin functions as an output.
15..4
Reserved
Reserved for future use. Should be set to 0.
48
Sundance Technology
ST201
PRELIMINARY draft 2
HASHTABLE
Class....................I/O Registers, Control and Status
Base Address ......IoBaseAddress register value
Address Offset.....0x66, 0x64, 0x62, 0x60
Access Mode.......Read/Write
Width ...................64 bits (accessible as 4, 16 bit words)
The host stores the 64-bit hash table in this register for selectively receiving multicast frames. Setting the
ReceiveMulticastHash bit in ReceiveMode enables the filtering mechanism. The hash table is cleared
upon reset, and must be properly programmed by the host.
BIT
BIT NAME
BIT DESCRIPTION
15..0
HashTableWord0
The least significant word of the hash table, corresponding to address
0x60.
31..16
47..32
63..48
HashTableWord1
HashTableWord2
HashTableWord3
The second least significant word of the hash table, corresponding to
address 0x62.
The second most significant word of the hash table, corresponding to
address 0x64.
The most significant word of the hash table, corresponding to address
0x66.
The ST201 applies a cyclic-redundancy-check (the same CRC used to calculate the frame data FCS) to
the destination address all incoming multicast frames (with multicast bit set). The low-order 6 bits of the
CRC result are used as an addressing index into the hash table. The MSB of HashTable(3) is the most sig-
nificant, and the LSB of HashTable(0) is the least significant bit, addressed by the 6-bit index. If the Hash-
Table bit addressed by the index is set, the frame is accepted by the ST201 and transferred to higher
layers. If the addressed hash table bit is cleared, the frame is discarded.
49
Sundance Technology
ST201
PRELIMINARY draft 2
MACCTRL
Class....................I/O Registers, Control and Status
Base Address ......IoBaseAddress register value
Address Offset.....0x50
Access Mode.......Read/Write
Width ...................32 bits
This register provides for setting of MAC-specific parameters. It is cleared upon reset.
BIT
1..0
BIT NAME
IFSSelect
BIT DESCRIPTION
This field is used to select the size of Inter-Frame Spacing (IFS). By
programming a larger number of bit times for the IFS, the ST201 will
become less “aggressive” on the network and may defer more than
normal. The performance of the ST201 may decrease as the IFS value
is increased from the standard value. This, however, will prevent the
ST201 from “capturing” the network.
00: no IFS extension, IFS = 96 BT (802.3 standard value).
01: IFS extended by 32 BT, IFS = 128 BT.
10: IFS extended by 128 BT, IFS = 224 BT.
11: IFS extended by 448 BT, IFS = 544 BT.
4..2
5
Reserved
Reserved for future use. Should be set to 0.
FullDuplexEnable
Setting this bit configures the ST201 to function in a full duplex man-
ner. Specifically, it disables transmitter deference to receive traffic,
allowing simultaneous receive and transmit traffic. It has the side-effect
of disabling CarrierSenseErrors statistics collection, since full duplex
operation requires carrier sense to be masked to the transmitter. TxRe-
set and RxReset bits in AsicCtrl must be set after changing the value of
this bit.
6
RcvLargeFrames
This bit determines the frame size at which the OversizedFrame error
is generated for receive frames. When RcvLargeFrames is cleared,
minimum OversizedFrame size is 1514 bytes. When RcvLargeFrames
is set, minimum OversizedFrame size is 4491 bytes. (This value was
the maximum FDDI frame size of 4500 bytes, subtracting bytes for
fields that have no Ethernet equivalent.)
The frame size at which an OversizedFrame error will be flagged
includes the destination and source addresses, the type/length field,
and the FCS field.
7
8
Reserved
Reserved for future use. Should be set to 0.
FlowControlEnable Flow control enable. When it is cleared (default), the ST201 treats all
incoming frames as data frames. When it is set, Flow control is
enabled and the ST201 will act upon incoming flow control PAUSE
frame. Note that FlowControlEnable should not be set unless FullDu-
plexEnable is also set.
50
Sundance Technology
ST201
PRELIMINARY draft 2
BIT
BIT NAME
RcvFCS
BIT DESCRIPTION
9
This bit is set by the host if it is desired for the receive frame’s FCS to
be passed to the host as part of the data in the RxFIFO. The state of
RcvFCS does not affect the ST201’s checking of the frame’s FCS and
its posting of FCS error status. RcvFCS is cleared by a system reset.
To avoid confusing the RxFIFO logic, the value of RcvFCS should only
be changed when the receiver is disabled and the RxFIFO is empty.
10
FIFOLoopback
MACLoopback
Setting this bit forces data loopback from the TxFIFO directly into the
RxFIFO. When using FIFO Loopback mode, it is the software’s respon-
sibility to ensure that the proper interframe gap is inserted between
frames, to avoid losing data in the receive path. To do this, the soft-
ware must not load more than one transmit frame into the TxFIFO at a
time. TxReset and RxReset bits in AsicCtrl must be set after changing
the value of this bit.
11
Setting this bit will cause the ST201 to loop back transmissions at the
output of the media access controller. TxReset and RxReset bits in
AsicCtrl must be set after changing the value of this bit.
15..12
16
Reserved
Reserved for future use. Should be set to 0.
CollisionDetect
This read-only bit provides a real-time indication of the state of the
COL signal within ST201.
17
18
19
CarrierSense
TxInProg
TxError
This read-only bit provides a real-time indication of the state of the
CRS signal within ST201.
A real-time indication that a frame is being transmitted. This bit is used
by drivers during under run recovery to delay issuing a TxReset.
If a TxUnderrun occurs, this bit is set, indicating that the transmitter
needs to be reset with the TxReset.
20
21
Reserved
Reserved for future use. Should be set to 0.
StatisticsEnable
When set, ST201 will collect statistics with the various statistics
counters and registers. This bit is self-clearing.
22
23
StatisticsDisable
StatisticsEnabled
When set, ST201 will stop collection of statistics with the statistics reg-
isters. The values in the statistics registers will remain unchanged. This
bit is self-clearing.
This read-only status bit is set by ST201 to indicate that statistics col-
lection is enabled.
24
25
26
TxEnable
TxDisable
TxEnabled
When set, the transmitter logic is enabled. This bit is self-clearing.
When set, the transmitter logic is disabled. This bit is self-clearing.
This read-only status bit is set by ST201 to indicate that transmitter is
enabled.
27
28
29
RxEnable
RxDisable
RxEnabled
When set, the receiver logic is enabled. This bit is self-clearing.
When set, the receiver logic is disabled. This bit is self-clearing.
This read-only status bit is set by ST201 to indicate that receiver is
enabled.
51
Sundance Technology
ST201
PRELIMINARY draft 2
BIT
30
BIT NAME
Paused
BIT DESCRIPTION
This read-only status bit is set by ST201 to indicate that a PAUSE MAC
Control frame had been received and halted the transmit MAC for the
duration of the pause_time. It is cleared when the MAC can resume
transmission.
31
Reserved
Reserved for future use. Should be set to 0.
The loopback modes available to a host system when using the ST201 are shown in Table 3.
Loopback Mode
FIFO Loopback
MAC Loopback
FIFOLoopback MACLoopback FullDuplexEnable
1
0
0
0
1
0
x
x
1
External Loopback (MII) or
True “On-wire” External
TABLE 3: ST201 Loopback Modes
External loopback type is controlled by the Mll PHY device. The host system must enable a loopback mode
within MII PHY device using the MII Management Interface. For the true “on-the-wire” loopback mode, use
a loopback plug (connector), clear all of the loopback bits, set the FullDuplexEnable bit in the MACCtrl reg-
ister, and enable the full duplex mode within the MII PHY device.
52
Sundance Technology
ST201
PRELIMINARY draft 2
MAXFRAMESIZE
Class....................I/O Registers, Control and Status
Base Address ......IoBaseAddress register value
Address Offset.....0x5a
Access Mode.......Read/Write
Width ...................16 bits
Sets the maximum frame size for received frames.
BIT
BIT NAME
BIT DESCRIPTION
15..0
MaxFrameSize
Received frames with sizes equal to or larger than the value in Max-
FrameSize will be flagged as oversize by RxOversizedFrame bit in
RxDMAStatus. MaxFrameSize defaults to 1514 upon reset. Upon
RxReset, MaxFrameSize is automatically loaded with 1514 or 4491
depending upon the value of RcvLargeFrames in MACCtrl.
53
Sundance Technology
ST201
PRELIMINARY draft 2
RECEIVEMODE
Class....................I/O Registers, Control and Status
Base Address ......IoBaseAddress register value
Address Offset.....0x5c
Access Mode.......Read/Write
Width ...................8 bits
Each bit in ReceiveMode, when set, enables reception of a different type of frame. ReceiveMode is cleared
upon reset.
BIT
BIT NAME
BIT DESCRIPTION
0
1
ReceiveUnicast
Setting this bit enables the ST201 to receive unicast frames that match
the 48-bit StationAddress of the ST201.
ReceiveMulticast
Setting this bit causes the ST201 to receive all multicast frames,
including broadcast.
2
3
4
ReceiveBroadcast
ReceiveAllFrames
Setting this bit causes the ST201 to receive all broadcast frames.
Setting this bit causes the ST201 to receive all frames promiscuously.
ReceiveMulticast-
Hash
Setting this bit enables the ST201 to receive frames that pass the hash
filtering mechanism.
5
ReceiveIPMulticast Setting this bit enables the ST201 to receive all multicast IP data-
grams, which are mapped into Ethernet multicast frames with destina-
tion address of 01:00:5e:xx:xx:xx as defined in RFC 1112 and RFC
1700. The first 3 bytes require exact match, and the last 3 bytes are
ignored.
7..6
Reserved
Reserved for future use. Should be set to 0.
54
Sundance Technology
ST201
PRELIMINARY draft 2
STATIONADDRESS
Class....................I/O Registers, Control and Status
Base Address ......IoBaseAddress register value
Address Offset.....0x47
Access Mode.......Read/Write
Width ...................8 bits
StationAddress is used to define the individual destination address that the ST201 will respond to when
receiving frames. Network addresses are generally specified in the form of 01:23:45:67:89:ab, where the
bytes are received left to right, and the bits within each byte are received right to left (Isb to msb). The
actual transmitted and received bits are in the order of 10000000 11000100 10100010 11100110
10010001 11010101.
BIT
BIT NAME
BIT DESCRIPTION
15..0
StationAddress
Word0
The least significant word of the station, corresponding to address
0x54.
31..16
47..32
StationAddress
Word1
The second least significant word of the station, corresponding to
address 0x56.
StationAddress
Word2
The most significant word of the station, corresponding to address
0x58.
The address comparison logic will compare the first 16 received destination address bits against Station-
Address(0), the second 16 received destination address bits against StationAddress(1), and the third 16
received destination address bits against StationAddress(2). The value set in the StationAddress register
is not inserted into the source address field of frames transmitted by the ST201. The source address field
for every frame must be specified by the host system as part of the frame data contents.
55
Sundance Technology
ST201
PRELIMINARY draft 2
TXFRAMEID
Class....................I/O Registers, Control and Status
Base Address ......IoBaseAddress register value
Address Offset.....0x5c
Access Mode.......Read
Width ...................8 bits
TxFrameId contains the frame ID for the currently transmitting or most recently transmitted frame.
BIT
7..0
BIT NAME
TxFrameId
BIT DESCRIPTION
This register contains the value from FrameId sub-field within the
frame’s TFD, TransmitFrameControl field.
Host systems can use TxFrameId register during transmit error recovery by scanning through the TFD’s in
the TxDMAList, searching for a match between the TxFrameId register value and a FrameId value in the
TFD.
56
Sundance Technology
ST201
PRELIMINARY draft 2
TXSTATUS
Class....................I/O Registers, Control and Status
Base Address ......IoBaseAddress register value
Address Offset.....0x46
Access Mode.......Read (write to advance queue)
Width ...................8 bits
The TxStatus register returns the status of frame transmission or transmission attempts. TxStatus actually
implements a queue of up to 31 transmit status bytes. An I/O write of an arbitrary value to TxStatus will
advance the queue to the next transmit status byte.
BIT
BIT NAME
Reserved
BIT DESCRIPTION
0
1
Reserved for future use. Should be set to 0.
TxReleaseError
TxStatusOverflow
MaxCollisions
TxUnderrun
Indicates that a transmit release error occurred, meaning that the
frame transmission experienced a collision after the front of the frame
had already been released to the TxFIFO free space. Refer to TxRe-
leaseThresh register for complete description.
2
3
4
When set, indicates that the TxStatus stack is full and as a result the
transmitter has been disabled. Writing TxStatus clears this bit, but the
transmitter must be re-enabled with the TxEnable before transmissions
may resume.
When set, the frame was not successfully transmitted due to encoun-
tering 16 collisions. TxEnable must be set to recover from this condi-
tion. The frame is discarded from the TxFIFO, so driver should
resubmit the frame for transmission.
This bit indicates that the frame experienced an under run during the
transmit process because the host was unable to supply the frame
data fast enough to keep up with the network data rate. An under run
will halt the transmitter and the TxFIFO. The TxReset and TxEnable
bits must be set prior to re-starting any frame.
5
6
Reserved
Reserved for future use. Should be set to 0.
TxIndicateReqd
This bit is asserted if the TxIndicate bit was set when the 32-bit Trans-
mitFrameControl was written to the ST201 for the frame.
7
TxComplete
If this bit is cleared, then the remainder of the status bits are undefined.
If the host chooses to poll this register while waiting for a frame trans-
mission to complete, then this bit is used to determine that a frame
transmission attempt has either experienced an error, or has com-
pleted successfully with the TxIndicate bit set in the TransmitFrame-
Control.
57
Sundance Technology
ST201
PRELIMINARY draft 2
WAKEEVENT
Class....................I/O Registers, Control and Status
Base Address ......IoBaseAddress register value
Address Offset.....0x45
Access Mode.......Read/Write
Width ...................8 bits
WakeEvent contains enable bits to control which types of events can generate a wake event to the host
system. It also contains status bits indicating the specific events that have occurred.
BIT
BIT NAME
BIT DESCRIPTION
0
1
WakePktEnable
Setting this read/write bit enables the ST201 to generate wake events
via a PCI interrupt due to Wake Packet reception. PmeEn must be set
in the PowerMgmtCtrl register in order for WakePktEnable to be recog-
nized. WakePktEnable has no effect in power mode D0.
MagicPktEnable
LinkEventEnable
Setting this read/write bit enables the ST201 to generate wake events
via a PCI interrupt due to Magic Packet reception. MagicPktEnable is
set after a ST201 reset. PmeEn must be set in the PowerMgmtCtrl reg-
ister in order for MagicPktEnable to be recognized. MagicPktEnable
has no effect in power mode D0.
2
Setting this read/write bit enables the ST201 to generate wake events
via a PCI interrupt due to a change in link status (cable connect or dis-
connect). PmeEn must be set in the PowerMgmtCtrl register in order
for LinkEventEnable to be recognized. LinkEventEnable has no effect
in power mode D0.
3
4
WakePolarity
Setting this read/write bit will cause the Wake pin to be asserted in the
HIGH state (default after RESET). MagicPktEnable is set after a
ST201 reset.
WakePktEvent
Indicates that a wake packet (which meets the reception criteria set by
driver) has been received. WakePktEvent is masked by WakePktEna-
ble, and must be set for WakePktEvent to operate. WakePktEvent is
cleared when the WakeEvent register is read.
5
MagicPktEvent
LinkEvent
Indicates that a magic packet has been received. MagicPktEvent is
masked by MagicPktEnable, and must be set for MagicPktEvent to
operate. MagicPktEvent is cleared when the WakeEvent register is
read.
6
7
Indicates that a link status event has occurred. LinkEvent is masked by
LinkEventEnable, and must be set for LinkEvent to operate. LinkEvent
is cleared when the WakeEvent register is read.
WakeOnLanEnable Setting this read/write bit puts the ST201 in the WakeOnLan mode
regardless of the power management register settings in the configura-
tion space.
58
Sundance Technology
ST201
PRELIMINARY draft 2
FIFOCTRL
Class....................I/O Registers, FIFO Control
Base Address ......IoBaseAddress register value
Address Offset.....0x3a
Access Mode.......Read/Write
Width ...................16 bits
The bits in this register provide various control and indications of TxFIFO and RxFIFO diagnostic.
BIT
BIT NAME
BIT DESCRIPTION
0
RAMTestMode
When set, the FIFO RAM is in the test mode. This bit is cleared after
reset.
8..1
9
Reserved
Reserved for future use. Should be set to 0.
RxOverrunFrame
This read/write bit determines how the ST201 handles receive overrun
frames. The default is zero, which causes the ST201 to discard all
overrun frames. Setting this bit causes the ST201 to keep and make
visible all overrun frames that have been made visible to the host, so
that they may be inspected for diagnostic purposes.
10
11
Reserved
Reserved for future use. Should be set to 0.
RxFIFOFull
This read-only bit is set when the RxFIFO is full. This bit does not in
itself indicate an overrun condition. However, if more data is received
while this bit is set, an overrun will occur. This bit is informational in
nature only. This bit is cleared as soon as the RxFIFO is no longer full.
13..12
14
Reserved
Reserved for future use. Should be set to 0.
Transmitting
Transmitting is read-only and set by ST201 whenever the MAC is
transmitting or waiting to transmit (deferring).
15
Receiving
This read-only bit is set whenever the ST201 is receiving a frame into
the RxFIFO. No particular action is expected on the part of the host
based on the state of this bit.
59
Sundance Technology
ST201
PRELIMINARY draft 2
RXEARLYTHRESH
Class....................I/O Registers, FIFO Control
Base Address ......IoBaseAddress register value
Address Offset.....0x3e
Access Mode.......Read/Write
Width ...................16 bits
The value stored in this register defines the number of bytes of the top of the frame that must be received
before a RxEarly interrupt will occur. The first byte of the destination address is considered to be byte 1.
The value in RxEarlyThresh may also determine how many bytes of a frame must be received before
RxDMA transfers for the frame are allowed to begin. If RxEarlyEnable in DMACtrl is set, a frame is not eli-
gible to start RxDMA until RxEarlyThresh bytes have been received. RxEarlyThresh resets to the value
1ffch, which disables the threshold mechanism.
BIT
BIT NAME
BIT DESCRIPTION
12..0
RxEarlyThresh
The number of bytes which must be present in the RxFIFO before a
RxEarly interrupt is asserted. The minimum value is 0x08, any value
smaller than this will be interpreted as 0x08. Values greater than 0x08
will be interpreted using a resolution of 4 bytes (i.e. 0x08, 0x0c, 0x0f,
etc.)
15..13
Unused
These bits are ignored.
60
Sundance Technology
ST201
PRELIMINARY draft 2
TXRELEASETHRESH
Class....................I/O Registers, FIFO Control
Base Address ......IoBaseAddress register value
Address Offset.....0x5d
Access Mode.......Read/Write
Width ...................8 bits
The value in TxReleaseThresh determines how much data of a frame must be transmitted before the
TxFIFO space can be released for use by another frame. Once the number of bytes equal to the value in
TxReleaseThresh have been transmitted, that number of bytes are discarded from the TxFIFO. Thereafter,
bytes are discarded as they are transmitted to the network. TxReleaseThresh resets to 8, i.e., a release
threshold of 128 bytes. A value of 255 in TxReleaseThresh disables the release mechanism and TxFIFO
frame space is not released until the entire frame is transmitted. A TxReleaseError is signaled in TxStatus
when a frame experiences a collision after its release threshold has been crossed, preventing MAC from
retry. When a release error occurs, the transmitter is disabled, and the frame’s ID or sequence number is
visible in TxFrameId.
BIT
7..0
BIT NAME
BIT DESCRIPTION
TxReleaseThresh
The number of 16 byte words which must be transmitted before the
space in the TxFIFO occupied by the transmitted data can be released.
To avoid excessive release errors due to in-window collisions, value
less than 4 should not be written into TxReleaseThresh.
61
Sundance Technology
ST201
PRELIMINARY draft 2
TXSTARTTHRESH
Class....................I/O Registers, FIFO Control
Base Address ......IoBaseAddress register value
Address Offset.....0x3c
Access Mode.......Read/Write
Width ...................16 bits
The value in TxStartThresh is used to control when frames are transmitted. Transmission of a frame
begins when the number of bytes for the frame transferred into the TxFIFO is greater than the value in
TxStartThresh. If TxStartThresh is set too low, the TxFIFO may experience under run due to the DMA data
transfers not able to keep up with the wire data rate. Host systems should use under run indications as a
hint to increase the TxStartThresh value. This register resets to 1ffch, which disables the threshold mecha-
nism.
BIT
BIT NAME
BIT DESCRIPTION
12..0
TxStartThresh
The number of bytes which must be present in the TxFIFO before
frame transmission begins. Values will be interpreted using a resolu-
tion of 4 bytes (i.e. 0x00, 0x04, 0x08, 0x0c, 0x0f, etc.)
15..13
Unused
These bits are ignored.
62
Sundance Technology
ST201
PRELIMINARY draft 2
COUNTDOWN
Class....................I/O Registers, Interrupt
Base Address ......IoBaseAddress register value
Address Offset.....0x48
Access Mode.......Read/Write
Width ...................16 bits
Countdown is a programmable down-counter that will generate an interrupt upon its expiration. If the
CountdownIntEnable bit in DMACtrl is set, the IntRequested interrupt will be generated when Countdown
counts through zero. Countdown has two modes of operation that is selected by the CountdownMode bit in
DMACtrl.When CountdownMode is cleared, Countdown is loaded by the host software with an initial
countdown value, then decrements at a rate determined by the CountdownSpeed bit in DMACtrl. When
CountdownSpeed is cleared, the count rate is once every 3.2 us. When CountdownSpeed is set, the count
rate is once every 320 ns. When Countdown reaches zero, it continues to count down, wrapping to 0xffff.
When CountdownMode is set, Countdown begins counting only when TxDMAComplete in IntStatus
becomes set. Countdown is cleared by reset.
BIT
BIT NAME
Countdown
BIT DESCRIPTION
15..0
Value of current state of Countdown timer.
63
Sundance Technology
ST201
PRELIMINARY draft 2
INTENABLE
Class....................I/O Registers, Interrupt
Base Address ......IoBaseAddress register value
Address Offset.....0x4c
Access Mode.......Read/Write
Width ...................16 bits
Enables individual interrupts as specified in the IntStatus register. Setting a bit in IntEnable will allow the
specific source to generate an interrupt on the PCI bus. IntEnable is cleared upon reset. IntEnable is also
cleared by a read of IntStatusAck.
BIT
BIT NAME
Unused
BIT DESCRIPTION
0
1
2
3
This bit will be ignored.
EnHostError
Enables the HostError interrupt.
EnTxComplete
Enables the TxComplete interrupt.
Enables the MACControlFrame interrupt.
EnMACControl-
Frame
4
5
6
7
8
9
EnRxComplete
EnRxEarly
Enables the RxComplete interrupt.
Enables the RxEarly interrupt.
EnInRequested
EnUpdateStats
EnLinkEvent
Enables the InRequested interrupt.
Enables the UpdateStats interrupt.
Enables the LinkEvent interrupt.
Enables the TxDMAComplete interrupt.
EnTxDMACom-
plete
10
EnRxDMACom-
plete
Enables the RxDMAComplete interrupt.
These bits bill be ignored.
15..11
Unused
64
Sundance Technology
ST201
PRELIMINARY draft 2
INTSTATUS
Class....................I/O Registers, Interrupt
Base Address ......IoBaseAddress register value
Address Offset.....0x4e
Access Mode.......Read/Write
Width ...................16 bits
IntStatus register indicates the source of interrupts and indications on the ST201. Bits 1 through 10 are the
interrupt-causing sources for the ST201. These bits can be individually disabled as interrupt sources using
the IntEnable register. The host can acknowledge the interrupt by writing a “1” into the indication bit(s),
which will cause ST201 to clear the interrupt indication. IntStatus is cleared by reset.
BIT
BIT NAME
BIT DESCRIPTION
0
1
2
InterruptStatus
Asserted when the ST201 is driving the bus interrupt signal. It is a logi-
cal OR of all the interrupt-causing bits after they have been filtered
through the IntEnable register.
HostError
This bit is set when a catastrophic error related to the bus interface
occurs. The errors which set HostError are: PCI target abort and PCI
master abort. HostError is cleared by GlobalReset/DMA bits set.
TxComplete
This bit is asserted when a frame whose TxIndicate bit is set has been
successfully transmitted or for any frame that experiences a transmis-
sion error. This interrupt is acknowledged by writing to TxStatus to
advance the status queue.
3
4
MACControlFrame
RxComplete
This bit is set when a MAC Control frame has been received by the
ST201. MACControlFrame is acknowledged by writing a 1 to this bit.
This bit is set when one or more entire frames have been received into
the RxFIFO. This bit is automatically acknowledged by the RxDMA
Logic as it transfers frames. Drivers should disable this interrupt and
mask this bit when reading IntStatus.
5
RxEarly
This bit is set when the number of bytes of the top frame that have
been received is greater than the value of RxEarlyThresh. When the
top frame has been completely received by the ST201, RxEarly will be
negated and RxComplete will assert. RxEarly is acknowledged by writ-
ing a 1 to this bit.
6
7
IntRequested
UpdateStats
This bit is set when the host requested interrupt by setting InterruptRe-
quest bit or by the expiration of the Countdown. It is acknowledged by
writing a 1 to this bit.
This bit indicates that one or more of the statistics counters is nearing
overflow condition (typically half of its maximum value). A driver should
respond to an UpdateStats interrupt by reading all of the statistics,
thereby acknowledging and clearing UpdateStats bit.
8
LinkEvent
This bit indicates transition of link status of the PHY. This bit can be
acknowledged by writing a 1 into this bit.
65
Sundance Technology
ST201
PRELIMINARY draft 2
BIT
BIT NAME
BIT DESCRIPTION
9
TxDMAComplete
This bit indicates that a frame TxDMA has completed, and the TFD in
question had the TxDMAIndicate bit in its TFC set. This bit can be
acknowledged by writing a 1 to this bit. The host should examine the
TxDMAListPtr to determine which frame(s) have been transferred by
TxDMA. Those frames in the TxDMAList before the current TxDMAL-
istPtr have already been transferred by TxDMA. If the TxDMAListPtr is
zero, then all the frames are transmitted.
10
RxDMAComplete
Reserved
This bit indicates that a frame RxDMA has completed. This bit can be
acknowledged by writing a 1 to this bit.
15..11
Reserved for future use. Should be set to 0.
66
Sundance Technology
ST201
PRELIMINARY draft 2
INTSTATUSACK
Class....................I/O Registers, Interrupt
Base Address ......IoBaseAddress register value
Address Offset.....0x4a
Access Mode.......Read only
Width ...................16 bits
IntStatusAck is another version of the IntStatus register, having the same bit definition as IntStatus, but
providing additional functionality to reduce the number of I/O operations required to perform common tasks
related to interrupt handling. In addition to returning the IntStatus value for the specified interrupt, when
read IntStatusAck also acknowledges the TxDMAComplete, RxDMAComplete, RxEarly, IntRequested,
MACControlFrame, and LinkEvent bits within the IntStatus register (if they are set), and clears the IntEna-
ble register (preventing subsequent events from generating an interrupt).
BIT
BIT NAME
BIT DESCRIPTION
0
1
2
InterruptStatus
Asserted when the ST201 is driving the bus interrupt signal. It is a logi-
cal OR of all the interrupt-causing bits after they have been filtered
through the IntEnable register.
HostError
This bit is set when a catastrophic error related to the bus interface
occurs. The errors which set HostError are: PCI target abort and PCI
master abort. HostError is cleared by GlobalReset/DMA bits set.
TxComplete
This bit is asserted when a frame whose TxIndicate bit is set has been
successfully transmitted or for any frame that experiences a transmis-
sion error. This interrupt is acknowledged by writing to TxStatus to
advance the status queue.
3
4
MACControlFrame
RxComplete
This bit is set when a MAC Control frame has been received by the
ST201. MACControlFrame is acknowledged by writing a 1 to this bit.
This bit is set when one or more entire frames have been received into
the RxFIFO. This bit is automatically acknowledged by the RxDMA
Logic as it transfers frames. Drivers should disable this interrupt and
mask this bit when reading IntStatus.
5
RxEarly
This bit is set when the number of bytes of the top frame that have
been received is greater than the value of RxEarlyThresh. When the
top frame has been completely received by the ST201, RxEarly will be
negated and RxComplete will assert. RxEarly is acknowledged by writ-
ing a 1 to this bit.
6
7
IntRequested
UpdateStats
This bit is set when the host requested interrupt by setting InterruptRe-
quest bit or by the expiration of the Countdown. It is acknowledged by
writing a 1 to this bit.
This bit indicates that one or more of the statistics counters is nearing
overflow condition (typically half of its maximum value). A driver should
respond to an UpdateStats interrupt by reading all of the statistics,
thereby acknowledging and clearing UpdateStats bit.
8
LinkEvent
This bit indicates transition of link status of the PHY. This bit can be
acknowledged by writing a 1 into this bit.
67
Sundance Technology
ST201
PRELIMINARY draft 2
BIT
BIT NAME
BIT DESCRIPTION
9
TxDMAComplete
This bit indicates that a frame TxDMA has completed, and the TFD in
question had the TxDMAIndicate bit in its TFC set. This bit can be
acknowledged by writing a 1 to this bit. The host should examine the
TxDMAListPtr to determine which frame(s) have been transferred by
TxDMA. Those frames in the TxDMAList before the current TxDMAL-
istPtr have already been transferred by TxDMA. If the TxDMAListPtr is
zero, then all the frames are transmitted.
10
RxDMAComplete
Reserved
This bit indicates that a frame RxDMA has completed. This bit can be
acknowledged by writing a 1 to this bit.
15..11
Reserved for future use. Should be set to 0.
68
Sundance Technology
ST201
PRELIMINARY draft 2
DMACTRL
Class....................I/O Registers, DMA
Base Address ......IoBaseAddress register value
Address Offset.....0x00
Access Mode.......Read/Write
Width ...................32 bits
DMACtrl controls some of the bus master functions in the RxDMA and TxDMA engines, and contains sta-
tus bits. DMACtrl is cleared by a reset.
BIT
BIT NAME
BIT DESCRIPTION
0
RxDMAHalted
This read-only bit is set whenever RxDMA is halted by setting the RxD-
MAHalt bit or an implicit halt due to fetching a RFD with RxDMACom-
plete in ReceiveFrameStatus already set. Cleared by setting the
RxDMAResume bit.
1
2
3
TxDMACmplReq
TxDMAHalted
This read-only bit is set to the value from the TxDMAIndicate field in
the TFC of the current TFD.
This read-only bit is set whenever TxDMA is halted by setting the TxD-
MAHalt bit. Cleared by setting the TxDMAResume bit.
RxDMAComplete
This read-only bit is the same as RxDMAComplete in IntStatus. This bit
is different from the RxDMAComplete bit in RxDMAStatus, which is a
real time indication of frame RxDMA completion and is cleared when a
new frame RxDMA begins. This bit is latched once a frame RxDMA
completion has occurred. This bit is cleared by acknowledgment to the
RxDMAComplete bit in the IntStatus register.
4
TxDMAComplete
This read-only bit is the same as TxDMAComplete in IntStatus. This bit
is cleared by acknowledgment to the TxDMAComplete bit in the IntSta-
tus register.
7..5
8
Reserved
Reserved for future use. Should be set to 0.
RxDMAHalt
Whenever this bit is set, the RxDMA is halted. This bit is self-clearing
and writing a 0 into this bit is ignored.
9
RxDMAResume
TxDMAHalt
Whenever this bit is set, the RxDMA is resumed. This bit is self-clear-
ing and writing a 0 into this bit is ignored.
10
11
Whenever this bit is set, the TxDMA is halted. This bit is self-clearing
and writing a 0 into this bit is ignored.
TxDMAResume
Whenever this bit is set, the TxDMA is resumed. This bit is self-clearing
and writing a 0 into this bit is ignored.
13..12
14
Reserved
Reserved for future use. Should be set to 0.
TxDMAInProg
This read-only bit indicates that a TxDMA operation is in progress. This
bit is primarily used by drivers in an under run recovery routine since
the driver needs waits for this bit to be cleared before issuing the TxRe-
set to clear the under run condition. Before checking TxDMAInProg,
issue TxDMAHalt to ensure that TxDMAInProg is not set as a result of
the ST201 being in a polling mode.
69
Sundance Technology
ST201
PRELIMINARY draft 2
BIT
15
BIT NAME
BIT DESCRIPTION
DMAHaltBusy
This read-only bit indicates that a DMA Halt operation (TxDMAHalt or
RxDMAHalt) is in progress and the drivers should wait for this bit to be
cleared before performing other actions.
16
17
Reserved
Reserved for future use. Should be set to 0.
RxEarlyEnable
This read/write bit determines when the ST201 may start RxDMA a
receive frame. By default (cleared), RxDMA qualify for bus-master arbi-
tration when the frame becomes visible, normally at 60 bytes unless a
RxEarlyThresh threshold smaller than that has been set. When set to
one, RxDMA won’t start until the RxEarlyThresh threshold has been
crossed (or the frame completes, whichever is first).
18
19
20
CountdownSpeed
CountdownMode
This read/write bit sets the speed at which Countdown counts. When
CountdownSpeed is cleared, the count rate is once every 3.2 us (i.e. 4
byte times at 10 Mbps). When CountdownSpeed is set, the count rate
is once every 320 ns (i.e. 4 byte times at 100 Mbps). By setting appro-
priate CountdownSpeed for the wire speed, conversions can be made
between byte times and counter values using simple shift operations.
This read/write bit controls the operating mode of the Countdown regis-
ter. With this bit cleared, Countdown begins its down counting opera-
tion as soon as a non-zero value is written to it. With this bit set,
Countdown will not begin counting down until TxDMAComplete (in
IntStatus) is set. See the Countdown register definition for more infor-
mation on the Countdown modes.
MWIDisable
Reserved
Setting this read/write bit prevents the bus master logic from using the
Memory Write Invalidate (MWI) PCI command.
21
22
Reserved for future use. Should be set to 0.
RxDMAOverrun-
Frame
This read/write bit, when clear (the default), causes the RxDMA engine
to discard receive overrun frames without transferring them to system
memory. When this bit is set, the RxDMA engine keeps and transfers
overrun frames.
23
CountdownIntEna-
ble
This read-only bit specifies whether expiration of Countdown can gen-
erate interrupts. If CountdownIntEnable is clear, Countdown expiration
will not set IntRequested; if it is set, expiration of Countdown will set
IntRequested. CountdownIntEnable is managed completely by the
hardware. This bit is cleared automatically by the act of setting IntRe-
quested or when a zero value is written into Countdown. This bit is set
implicitly when a non-zero value is written into Countdown by the host.
This allows the host to write a non-zero value to Countdown and an
interrupt will be generated in a corresponding amount of time. By writ-
ing a zero value to Countdown the host can suppress interrupts.
29..24
30
Reserved
Reserved for future use. Should be set to 0.
TargetAbort
This read-only bit is set when the ST201 experiences a target abort
sequence when operating as a bus master. This bit indicates a fatal
error, and must be cleared before further TxDMA or RxDMA operation
can proceed. This bit is cleared by the GlobalReset/DMA bit.
70
Sundance Technology
ST201
PRELIMINARY draft 2
BIT
31
BIT NAME
MasterAbort
BIT DESCRIPTION
This read-only bit is set when the ST201 experiences a master abort
sequence when operating as a bus master. This bit indicates a fatal
error, and must be cleared before further TxDMA or RxDMA operation
can proceed. This bit is cleared by the GlobalReset/DMA bit.
71
Sundance Technology
ST201
PRELIMINARY draft 2
RXDMABURSTTHRESH
Class....................I/O Registers, DMA
Base Address ......IoBaseAddress register value
Address Offset.....0x14
Access Mode.......Read/Write
Width ...................8 bits
RxDMABurstThresh sets the threshold when the ST201 makes RxDMA bus master requests, based upon
the number of used bytes in the RxFIFO, in units of 32 bytes. When the used space exceeds the threshold,
the ST201 may make a RxDMA request on the PCI bus. However, if the used space exceeds the current
RxDMAFragLen, ST201 will make RxDMA bus request regardless of whether the used space exceeds the
RxDMABurstThresh or not. RxDMABurstThresh may be overridden by the urgent request mechanism.
See the PCI Bus Master Operation section for information about the relationship between RxDMABurst-
Thresh and RxDMAUrgentThresh. A value of zero is invalid. RxDMABurstThresh defaults to 8, a threshold
of 256 bytes.
BIT
7..0
BIT NAME
BIT DESCRIPTION
RxDMABurst-
Thresh
The number of 32 byte words which must be present in the RxFIFO
prior to the assertion of a RxDMA bus master request.
72
Sundance Technology
ST201
PRELIMINARY draft 2
RXDMALISTPTR
Class....................I/O Registers, DMA
Base Address ......IoBaseAddress register value
Address Offset.....0x10
Access Mode.......Read/Write
Width ...................32 bits
RxDMAListPtr holds the physical address of the current RxDMA Frame Descriptor in the RxDMAList. A
value of zero in RxDMAListPtr indicates that no more RFDs are available to accept receive frames. RxD-
MAListPtr only points to addresses on 8-byte boundaries, so RFDs must be aligned on 8-byte physical
address boundaries. RxDMAListPtr is cleared by reset. RxDMAListPtr may be written directly by the host
system to point the ST201 to the head of a newly created RxDMAList. RxDMAListPtr is also updated by
the ST201 as it processes RFDs in the RxDMAList. As the ST201 finishes processing a RFD, it loads RxD-
MAListPtr with the value from RxDMANextPtr to allow it to move on to the next RFD. If the ST201 loads a
value of zero from the current RFD, the RxDMA engine enters the idle state, waiting for a non-zero value to
be written to RxDMAListPtr. To avoid access conflicts between the ST201 and the host system, the host
system must issue a RxDMAHalt before writing to RxDMAListPtr.
BIT
BIT NAME
BIT DESCRIPTION
31..0
RxDMAListPtr
Physical address, on a 8-byte boundary, of the current RFD in the
RxDMAList.
73
Sundance Technology
ST201
PRELIMINARY draft 2
RXDMASTATUS
Class....................I/O Registers, DMA
Base Address ......IoBaseAddress register value
Address Offset.....0x0c
Access Mode.......Read only
Width ...................32 bits
RxDMAStatus shows the status of various operations in the RxDMA Logic. Host systems should read this
register only while the RxDMA engine is in the RxDMAHalt state. Otherwise the ST201 may change RFDs
between accesses to this register. The format of this register is identical to that of the ReceiveFrameStatus
field written into each RFD, since the content of this register is written into the RFD upon RxDMA frame
completion with the exception of the ImpliedBufferEnable bit, which is not implemented in this register.
RxDMAStatus is cleared by a reset.
BIT
BIT NAME
BIT DESCRIPTION
12..0
RxDMAFrameLen
During frame RxDMA, RxDMAFrameLen gives a real-time indication of
the number of bytes transferred by RxDMA for the frame. RxDMAFra-
meLen is cleared when the ST201 fetches a new RxDMAListPtr, and
counts up in steps no larger than a bus master burst. When the frame
has been completely transferred by RxDMA, RxDMAFrameLen indi-
cates the true frame length, except in the case where the frame is
larger than the number of bytes specified in the RxDMA fragments. In
this case, the RxDMAOverflow bit will be set.
13
14
Reserved
Reserved for future use. Should be set to 0.
RxFrameError
Indicates that an error occurred in the receipt of the frame. The driver
should examine bits 16 through 20 to determine the type of error(s).
This bit is undefined until RxDMAComplete bit is set.
15
16
RxDMAComplete
RxFIFOOverrun
Indicates that the frame transfer by RxDMA is complete. Unless a
RxDMA halt is in effect this bit would normally only remain set momen-
tarily (too short for the software to read it) since the hardware will then
fetch the next RFD.
Indicates that the hardware was unable to remove data from the
RxFIFO quickly enough (most likely because the software failed to free
a RFD quickly enough, or kept the ST201 in the RxDMAHalt state for
too long). Bytes will be missing from the frame at one or more locations
in the frame (unpredictable). This bit is undefined until RxDMACom-
plete bit is set.
17
RxRuntFrame
Indicates that the frame was a runt (less than 60 bytes). Normally such
frames are not transferred by RxDMA unless RxEarlyThresh is set to a
value less than the actual size of the runt frame, and the RxEarlyEn-
able of MacCtrl register must be set. This bit is undefined until RxDMA-
Complete bit is set.
18
19
RxAlignmentError
RxFCSError
Indicates that the frame had an alignment error (bad FCS and dribble
bits). This bit is undefined until RxDMAComplete bit is set.
Indicates a FCS checksum error on the frame data. This bit is unde-
fined until RxDMAComplete bit is set.
74
Sundance Technology
ST201
PRELIMINARY draft 2
BIT
20
BIT NAME
BIT DESCRIPTION
RxOversizedFrame Indicates the frame size was equal to or greater than the value set in
the MaxFrameSize register. This bit is undefined until RxDMACom-
plete bit is set.
22..21
23
Reserved
Reserved for future use. Should be set to 0.
DribbleBits
Indicates that the frame had accompanying dribble bits. This bit is
informational only, and does not indicate a frame error.
24
RxDMAOverflow
Reserved
Indicates that the RFD had insufficient buffer space for the frame data
and there were still data left to be transferred by RxDMA when the
ST201 ran out of fragment space. The ST201 will transfer what it can
into the buffers provided, discard the remainder of the frame and set
this bit.
31..25
Reserved for future use. Should be set to 0.
75
Sundance Technology
ST201
PRELIMINARY draft 2
RXDMAPOLLPERIOD
Class....................I/O Registers, DMA
Base Address ......IoBaseAddress register value
Address Offset.....0x16
Access Mode.......Read/Write
Width ...................8 bits
The value in RxDMAPollPeriod determines the rate at which the current RFD is polled, looking for RxDMA-
Complete in ReceiveFrameStatus in RFD to be cleared. Polling is disabled when RxDMAPollPeriod is
cleared. RxDMAPollPeriod is cleared by reset. The value in RxDMAPollPeriod represents multiple of 320
ns time intervals. The maximum value is 127 (or 40.64 us).
BIT
6..0
BIT NAME
BIT DESCRIPTION
RxDMAPollPeriod
The number of 320ns intervals between polls of the RxDMAComplete
bit in the ReceiveFrameStatus field of the current RFD.
7
Unused
This bit is ignored.
76
Sundance Technology
ST201
PRELIMINARY draft 2
RXDMAURGENTTHRESH
Class....................I/O Registers, DMA
Base Address ......IoBaseAddress register value
Address Offset.....0x15
Access Mode.......Read/Write
Width ...................8 bits
The value in RxDMAUrgentThresh sets a threshold at which the RxDMA engine will make a urgent bus
master request. A urgent RxDMA request will have priority over all other requests on the ST201. The
urgent bus request is made when the free space in the RxFIFO falls below the value in RxDMAUrgent-
Thresh. A RxDMA urgent request is not subject to the RxDMABurstThresh constraint. When the RxFIFO is
close to overrun, burst efficiency is sacrificed in favor of requesting the bus as quickly as possible. The
value in RxDMAUrgentThresh represents free space in the RxFIFO in terms of 32-byte portions. RxDMAU-
rgentThresh resets to 4, or a threshold of 128 bytes.
BIT
4..0
BIT NAME
BIT DESCRIPTION
RxDMAUrgent-
Thresh
The minimum number of 32-byte words which must be available in the
RxFIFO to avoid assertion of a RxDMA Urgent Request.
7..5
Unused
These bits are ignored.
77
Sundance Technology
ST201
PRELIMINARY draft 2
TXDMABURSTTHRESH
Class....................I/O Registers, DMA
Base Address ......IoBaseAddress register value
Address Offset.....0x08
Access Mode.......Read/Write
Width ...................8 bits
TxDMABurstThresh determines the threshold for when the ST201 makes TxDMA bus master requests,
based upon the available space in the TxFIFO. The value in TxDMABurstThresh represents free space in
the TxFIFO in multiples of 32 bytes. When the free space exceeds the threshold, the ST201 may make a
TxDMA request. However, if the free space exceeds the current TxDMAFragLen, ST201 will make TxDMA
bus request regardless of whether the free space exceeds the TxDMABurstThresh or not. TxDMABurst-
Thresh may be overridden by the TxDMAUrgentThresh mechanism. See the PCI Bus Master Operation
section for information about the relationship between TxDMABurstThresh and TxDMAUrgentThresh. A
value of zero is invalid. TxDMABurstThresh defaults to 8, a threshold of 256 bytes.
BIT
4..0
BIT NAME
BIT DESCRIPTION
TxDMABurst-
Thresh
The number of 32-byte words which must be available in the TxFIFO
prior to assertion of a TxDMA Burst Request.
7..5
Unused
These bits are ignored.
78
Sundance Technology
ST201
PRELIMINARY draft 2
TXDMALISTPTR
Class....................I/O Registers, DMA
Base Address ......IoBaseAddress register value
Address Offset.....0x04
Access Mode.......Read/Write
Width ...................32 bits
TxDMAListPtr holds the physical address of the current TxDMA Frame Descriptor in the TxDMAList. A
value of zero in TxDMAListPtr is interpreted by the ST201 to mean that no more frames remain to be trans-
ferred by TxDMA. TxDMAListPtr can only point to addresses on 8-byte boundaries, so TFD’s must be
aligned on 8-byte boundaries. TxDMAListPtr is cleared by reset. TxDMAListPtr may be written directly by
the host system to point the ST201 at the head of a newly created TxDMAList. Writes to TxDMAListPtr are
ignored while the current value in TxDMAListPtr is non-zero. To avoid access conflicts between the ST201
and the host system, the host system must issue a TxDMAHalt before writing to TxDMAListPtr (unless the
host system has specific knowledge that TxDMAListPtr contains zero). TxDMAListPtr is also updated by
the ST201 as it processes TFD’s in the TxDMAList. As the ST201 finishes processing a TFD, it fetches the
value from TxDMANextPtr. If it is zero, the TxDMA engine becomes idle. Also, if TxDMA polling is enabled
(TxDMAPollPeriod is non-zero), the old value in TxDMAListPtr is preserved. If the value fetched from TxD-
MANextPtr is non-zero, then the value is stored temporarily in the ST201, and the ST201 inspects the TFD
at that location. The temporary value is loaded into TxDMAListPtr, advancing the ST201 to the new TFD.
There are two ways the TxDMA engine can leave the idle state. First, the driver can write a nonzero value
directly to TxDMAListPtr. Second, if polling is enabled, then the TxDMA engine will leave the idle state
when a non-zero value is finally fetched from TxDMANextPtr. Reading TxDMAListPtr while the TxDMA
engine is polling has the following side effects:
1. Any pending decision to advance to the next TFD is cancelled.
2. The TxDMA engine fetches the TxDMANextPtr in the current (completed) TFD immediately, rather
than waiting for the full TxDMAPollPeriod interval. (It is assumed that the host system will only read
TxDMAListPtr when it is in the process of inserting a TFD at the list head, so it will have written a new
value into TxDMANextPtr to hook up the inserted TFD).
BIT
BIT NAME
BIT DESCRIPTION
31..0
TxDMAListPtr
Physical address, on a 8-byte boundary, of the current TFD in the TxD-
MAList.
79
Sundance Technology
ST201
PRELIMINARY draft 2
TXDMAPOLLPERIOD
Class....................I/O Registers, DMA
Base Address ......IoBaseAddress register value
Address Offset.....0x0a
Access Mode.......Read/Write
Width ...................8 bits
The value in TxDMAPollPeriod determines the interval at which the current TFD is polled. When a zero
TxDMANextPtr is fetched from the current TFD, TxDMANextPtr is polled to determine when a new TFD is
ready to be processed. Polling is disabled when TxDMAPollPeriod is cleared. TxDMAPollPeriod is cleared
by reset. The value in TxDMAPollPeriod represents a multiple of 320 ns time intervals. The maximum
value is 127 (or 40.64 us).
BIT
6..0
BIT NAME
BIT DESCRIPTION
TxDMAPollPeriod
The number of 320ns intervals between polls of the TxDMANextPtr
field of the current TFD.
7
Unused
This bit is ignored.
80
Sundance Technology
ST201
PRELIMINARY draft 2
TXDMAURGENTTHRESH
Class....................I/O Registers, DMA
Base Address ......IoBaseAddress register value
Address Offset.....0x09
Access Mode.......Read/Write
Width ...................8 bits
When the number of used bytes in the TxFIFO falls below the value in the TxDMAUrgentThresh, the
TxDMA Logic will make an urgent bus master request. An urgent TxDMA request will have priority over the
RxDMA, unless it is also making an urgent request. A TxDMA urgent request is not subject to the
TxDMABurstThresh constraint. The relaxation of the TxDMABurstThresh constraint for this condition is
because the TxFIFO is close to under run, and burst efficiency is sacrificed to avoid FIFO under run. The
value in TxDMAUrgentThresh represents data in the TxFIFO in multiples of 32 bytes. TxDMAUrgent-
Thresh resets to 4, or a threshold of 128 bytes.
BIT
5..0
BIT NAME
BIT DESCRIPTION
TxDMAUrgent-
Thresh
The minimum number of 32-byte words which must be occupied in the
TxFIFO to avoid assertion of a TxDMA Urgent Request.
7..6
Unused
These bits are ignored.
81
Sundance Technology
ST201
PRELIMINARY draft 2
EEPROMCTRL
Class....................I/O Registers, External Interface Control
Base Address ......IoBaseAddress register value
Address Offset.....0x36
Access Mode.......Read/Write
Width ...................16 bits
EepromCtrl provides the host with a method for issuing commands to the ST201’s serial EEPROM control-
ler. Individual 16-bit word locations within the EEPROM may be written, read or erased. Also, the
EEPROM’s WriteEnable, WriteDisable, EraseAll and WriteAll commands can be issued. Two-bit opcodes
and 8-bit addresses are written to this register to cause the ST201 to carry out the desired EEPROM com-
mand. If data is to written to the EEPROM, the 16-bit data word must be written to EepromData by the host
prior to issuing the associated write command. Similarly, if data is to be read from the EEPROM, the read
data will be available via EepromData register. The EEPROM is a particularly slow device. It is important
that the host wait until the EepromBusy bit is false before issuing a command to EepromCtrl. EepromCtrl
defaults to 0000h upon reset.
BIT
7..0
BIT NAME
BIT DESCRIPTION
EepromAddress
These eight read/write bits identify one of the 256 sixteen-bit words to
be the target for the ReadRegister, WriteRegister and EraseRegister
commands. Bits 7 and 6 are further defined to identify an individual
command among the following group of four sub-commands:
sub-opcodesub-command
00WriteDisable
01WriteAII
10EraseAII
11WriteEnable
The definition of bits 7 and 6 are valid when the EepromOpcode in bits
9 and 8 equals 00.
9..8
EepromOpcode
These two read/write bits specify one of three individual commands
and a single group of four sub-commands. The following table defines
the opcodes:
EepromOpcode command
00 Write Enable/Disable & Write/Erase All sub-commands
01 WriteRegister
10 ReadRegister
11 EraseRegister
14..10
15
Reserved
Reserved for future use. Should be set to 0.
EepromBusy
This read-only bit is asserted during the execution of EEPROM com-
mands. Further commands should not be issued to EepromCtrl nor
should data be read from EepromData while this bit is true.
82
Sundance Technology
ST201
PRELIMINARY draft 2
EEPROMDATA
Class....................I/O Registers, External Interface Control
Base Address ......IoBaseAddress register value
Address Offset.....0x34
Access Mode.......Read/Write
Width ...................16 bits
EepromData is a 16-bit data register for use with the adapter’s serial EEPROM. Data from the EEPROM
can be read by the host from EepromData register after EepromBusy is cleared. Data to be written to the
EEPROM is written to EepromData prior to issuing the write command to EepromCtrl. EepromData is
cleared after a system reset.
BIT
BIT NAME
BIT DESCRIPTION
15..0
EepromData
Data read from, or to be written to, the external EEPROM.
83
Sundance Technology
ST201
PRELIMINARY draft 2
EXPROMADDR
Class....................I/O Registers, External Interface Control
Base Address ......IoBaseAddress register value
Address Offset.....0x40
Access Mode.......Read/Write
Width ...................32 bits
ExpRomAddr holds the address to be used for direct I/O accesses of the Expansion ROM through the
ExpRomData port. To access a byte in the Expansion ROM, write the address of the byte to be accessed
into ExpRomAddr. Then issue either a read or a write to ExpRomData. For reads, the ROM value will be
returned by the read instruction. For writes, the new value will be programmed into the ROM upon comple-
tion of the write instruction.
BIT
BIT NAME
BIT DESCRIPTION
15..0
ExpRomAddr
Reserved
Address used for accessing expansion ROM.
Reserved for future use. Should be set to 0.
31..16
84
Sundance Technology
ST201
PRELIMINARY draft 2
EXPROMDATA
Class....................I/O Registers, External Interface Control
Base Address ......IoBaseAddress register value
Address Offset.....0x44
Access Mode.......Read/Write
Width ...................8 bits
ExpRomData is the data port for performing direct I/O byte-wide accesses of the Expansion ROM. A read
of ExpRomData returns the ROM byte value from the location specified by ExpRomAddr. A write to
ExpRomData causes the write data to be programmed into the ROM location specified by ExpRomAddr.
Note: The Atmel EPROM devices supported by ST201 must be programmed in 64-byte pages. Refer to
the Atmel Flash Memory Device data book for information on programming EPROMs.
BIT
BIT NAME
BIT DESCRIPTION
15..0
ExpRomData
Data read from, or to be written to, expansion ROM.
85
Sundance Technology
ST201
PRELIMINARY draft 2
PHYCTRL
Class....................I/O Registers, External Interface Control
Base Address ......IoBaseAddress register value
Address Offset.....0x5e
Access Mode.......Read/Write
Width ...................8 bits
This register contains control bits for the MII Management Interface. The MII Management Interface is
used to access registers in an MII PHY device. The Management Interface is a two-wire serial interface
connecting ST201 to any MII-compliant PHY devices residing on the adapter. The host system operates
the Management Interface by writing and reading bit patterns to the PhyCtrl register which correspond to
the physical waveforms required on the interface signals. For more information on the Management Inter-
face signal protocols, refer to the Media Independent Interface standard of IEEE 802.3u Specification.
BIT
BIT NAME
MgmtClk
BIT DESCRIPTION
0
1
The MII Management Clock. This bit drives directly the management
clock to the PHY device(s).
MgmtData
The MII Management Data bit. When the MgmtDir bit (below) is set,
the value written to this bit is driven onto the MDIO signal. When Mgmt-
Dir is cleared, data being driven by the PMD can be read from this bit.
2
3
4
5
6
7
MgmtDir
The MII data direction control bit. Setting this bit causes ST201 to drive
MDIO with the data bit written into MgmtData.
DisableClk25
This bit is set to tri-state the CLK25 pin. DisableClk25 is cleared upon
reset.
PhyDuplexPolarity
PhyDuplexStatus
PhySpeedStatus
PhyLinkStatus
Clearing this read/write bit will cause the PHYDPLXN input pin to be
active low. The default value for this bit upon reset is cleared.
This read-only bit provides a real-time indication of the duplex status of
the PHY. This bit is set for full duplex operation.
This read-only bit provides a real-time indication of the speed status of
the PHY. This bit is set for 100Mb/s operation.
This read-only bit provides a real-time indication of the twisted-pair
transceiver link. This bit is set for operational link (link status up).
86
Sundance Technology
ST201
PRELIMINARY draft 2
STATISTICS
Reading a statistic register will clear it. The statistics gathering must be enabled by setting the StatisticsEn-
able bit in MACCtrl for the statistics registers to count events.
BROADCASTFRAMESRECEIVEDOK
Class....................I/O Registers, Statistics
Base Address ......IoBaseAddress register value
Address Offset.....0x7d
Access Mode.......Read (also clears register)/Write
Width ...................8 bits
BIT
7..0
BIT NAME
BIT DESCRIPTION
BroadcastFrames-
ReceivedOk
This statistic counts the number of frames that are successfully
received and are directed to the broadcast group address. This does
not include frames received with frame-too-long, FCS, length or align-
ment errors, or frames lost due to internal MAC error. This is a 8-bit
counter and will wrap around to zero after reaching ffh. An UpdateStats
interrupt will occur, if enabled, after the counter counts through c0h.
87
Sundance Technology
ST201
PRELIMINARY draft 2
BROADCASTFRAMESTRANSMITTEDOK
Class....................I/O Registers, Statistics
Base Address ......IoBaseAddress register value
Address Offset.....0x7c
Access Mode.......Read (also clears register)/Write
Width ...................8 bits
BIT
7..0
BIT NAME
Broadcast-
FramesTransmitte-
dOk
BIT DESCRIPTION
This statistic counts the number of frames that are successfully trans-
mitted to the broadcast address. Frames transmitted to multicast
addresses are excluded from this statistic. This is a 8-bit counter and
will wrap around to zero after reaching ffh. An UpdateStats interrupt will
occur, if enabled, after the counter counts through c0h.
88
Sundance Technology
ST201
PRELIMINARY draft 2
CARRIERSENSEERRORS
Class....................I/O Registers, Statistics
Base Address ......IoBaseAddress register value
Address Offset.....0x74
Access Mode.......Read (also clears register)/Write
Width ...................8 bits
BIT
3..0
BIT NAME
BIT DESCRIPTION
CarrierSenseErrors This statistic register counts the number of times that carrier_sense
was not asserted or was de-asserted during the transmission of a
frame without collision. Carrier sense is not monitored for the purpose
of this statistic until after the preamble and start-of-frame delimiter.
This is a 4-bit counter that will stick at 0fh. An UpdateStats interrupt will
occur, if enabled, after the counter has counted through 0ch.
7..4
Reserved
Reserved for future use. Should be set to 0.
89
Sundance Technology
ST201
PRELIMINARY draft 2
FRAMESABORTEDDUETOXSCOLLS
Class....................I/O Registers, Statistics
Base Address ......IoBaseAddress register value
Address Offset.....0x7b
Access Mode.......Read (also clears register)/Write
Width ...................8 bits
BIT
7..0
BIT NAME
BIT DESCRIPTION
FramesAbortedDu- This statistic counts the number of frames that, due to excessive colli-
eToXSColls
sions, are not transmitted successfully. This is an 8-bit counter and will
wrap around to zero after reaching ffh. An UpdateStats indication will
occur after the counter has counted through c0h.
90
Sundance Technology
ST201
PRELIMINARY draft 2
FRAMESLOSTRXERRORS
Class....................I/O Registers, Statistics
Base Address ......IoBaseAddress register value
Address Offset.....0x79
Access Mode.......Read (also clears register)/Write
Width ...................8 bits
BIT
7..0
BIT NAME
BIT DESCRIPTION
FramesLostRxEr-
rors
This statistic counts the number of frames that should have been
received (the destination address matched the filter criteria) but experi-
enced a RxFIFO overrun error due to there not being enough space to
hold the frame. This statistic only includes overruns that become
apparent to the driver, and does not count frames that are completely
ignored due to the RxFIFO being full at the start of frame reception.
This is an 8-bit counter and will wrap around to zero after reaching ffh.
An UpdateStats indication will occur after the counter has counted
through c0h.
91
Sundance Technology
ST201
PRELIMINARY draft 2
FRAMESRECEIVEDOK
Class....................I/O Registers, Statistics
Base Address ......IoBaseAddress register value
Address Offset.....0x72
Access Mode.......Read (also clears register)/Write
Width ...................16 bits
BIT
7..0
BIT NAME
BIT DESCRIPTION
FramesReceive-
dOk
This statistic counts the number of frames that are successfully
received. This does not include frames with frame-too-long, FCS,
length or alignment errors, or frames lost due to internal MAC error.
Error frames will have Overrun, RuntFrame, AlignmentError, FCSError,
or OversizedFrame is set in RxDMAStatus. This is a 16-bit counter and
will wrap around to zero after reaching ffffh. An UpdateStats interrupt
will occur, if enabled, after the counter counts through c000h.
92
Sundance Technology
ST201
PRELIMINARY draft 2
FRAMESTRANSMITTEDOK
Class....................I/O Registers, Statistics
Base Address ......IoBaseAddress register value
Address Offset.....0x70
Access Mode.......Read (also clears register)/Write
Width ...................16 bits
BIT
7..0
BIT NAME
BIT DESCRIPTION
FramesTransmitte-
dOk
This statistic counts the number of frames that are successfully trans-
mitted. This is a 16-bit counter and will wrap around to zero after reach-
ing ffffh. An UpdateStats interrupt will occur, if enabled, after the
counter counts through c000h.
93
Sundance Technology
ST201
PRELIMINARY draft 2
FRAMESWITHDEFERREDXMISSION
Class....................I/O Registers, Statistics
Base Address ......IoBaseAddress register value
Address Offset.....0x78
Access Mode.......Read (also clears register)/Write
Width ...................8 bits
BIT
7..0
BIT NAME
BIT DESCRIPTION
FramesWithDe-
ferredXmission
This statistic counts the number of frames that must delay its first
attempt of transmission because the medium was busy. Frames
involved in any collisions are not counted by this statistic. This is an 8-
bit counter and will wrap around to zero after reaching ffh. An Updat-
eStats interrupt will occur after the counter has counted through c0h.
94
Sundance Technology
ST201
PRELIMINARY draft 2
FRAMESWITHEXCESSIVEDEFERAL
Class....................I/O Registers, Statistics
Base Address ......IoBaseAddress register value
Address Offset.....0x7a
Access Mode.......Read (also clears register)/Write
Width ...................8 bits
BIT
7..0
BIT NAME
BIT DESCRIPTION
FramesWithExces-
siveDeferal
This statistic counts the number of frames that deferred for an exces-
sive period of time (exceeding the defer limit). This statistic is only
incremented once per LLC frame. This is an 8-bit counter and will wrap
around to zero after reaching ffh. An UpdateStats interrupt will occur
after the counter has counted through c0h.
95
Sundance Technology
ST201
PRELIMINARY draft 2
LATECOLLISIONS
Class....................I/O Registers, Statistics
Base Address ......IoBaseAddress register value
Address Offset.....0x75
Access Mode.......Read (also clears register)/Write
Width ...................8 bits
BIT
7..0
BIT NAME
BIT DESCRIPTION
LateCollisions
This statistic counts the number of times that a collision has been
detected later than 512 BT into the transmitted frame. A late collision is
counted both as a Collision and a LateCollision. This is an 8-bit counter
and will wrap around to zero after reaching ffh. An UpdateStats inter-
rupt will occur, if enabled, after the counter counts through c0h.
96
Sundance Technology
ST201
PRELIMINARY draft 2
MULTICASTFRAMESRECEIVEDOK
Class....................I/O Registers, Statistics
Base Address ......IoBaseAddress register value
Address Offset.....0x7f
Access Mode.......Read (also clears register)/Write
Width ...................8 bits
BIT
7..0
BIT NAME
BIT DESCRIPTION
MulticastFrames-
ReceivedOk
This statistic counts the number of frames that are successfully
received and are directed to an active non-broadcast group address.
This does not include frames received with frame-too-long, FCS,
length or alignment errors, or frames lost due to internal MAC error.
This is a 8-bit counter and will wrap around to zero after reaching ffh.
An UpdateStats interrupt will occur, if enabled, after the counter counts
through c0h.
97
Sundance Technology
ST201
PRELIMINARY draft 2
MULTICASTFRAMESTRANSMITTEDOK
Class....................I/O Registers, Statistics
Base Address ......IoBaseAddress register value
Address Offset.....0x7e
Access Mode.......Read (also clears register)/Write
Width ...................8 bits
BIT
7..0
BIT NAME
Multicast-
FramesTransmitte-
dOk
BIT DESCRIPTION
This statistic counts the number of frames that are successfully trans-
mitted to a group destination address other than broadcast. This is a 8-
bit counter and will wrap around to zero after reaching ffh. An Updat-
eStats interrupt will occur, if enabled, after the counter counts through
c0h.
98
Sundance Technology
ST201
PRELIMINARY draft 2
MULTIPLECOLLISIONFRAMES
Class....................I/O Registers, Statistics
Base Address ......IoBaseAddress register value
Address Offset.....0x76
Access Mode.......Read (also clears register)/Write
Width ...................8 bits
BIT
7..0
BIT NAME
BIT DESCRIPTION
MultipleCollision-
Frames
This statistic counts the number of frames that are involved in more
than one collision and are subsequently transmitted successfully. This
is a 8-bit counter and will wrap around to zero after reaching ffh. An
UpdateStats interrupt will occur, if enabled, when the counter has
counted through c0h.
99
Sundance Technology
ST201
PRELIMINARY draft 2
OCTETSRECEIVEDOK
Class....................I/O Registers, Statistics
Base Address ......IoBaseAddress register value
Address Offset.....0x68
Access Mode.......Read (also clears register)/Write
Width ...................32 bits
BIT
BIT NAME
BIT DESCRIPTION
19..0
OctetsReceivedOk
This statistic counts the total number of frame header, data and pad-
ding octets in frames that are successfully received. For the purposes
of this statistic, a successfully received frame is one that is completely
moved into the RxFIFO. This is a 20-bit counter and will wrap around to
zero after reaching fffffh. An UpdateStats interrupt will occur after the
counter has counted through c0000h. This statistic must be read as
two 16-bit quantity with the lower word first. Upon reading the lower
word, the upper word value is latched in and the lower value is cleared.
The upper word is also cleared when read.
31..20
Reserved
Reserved for future use. Should be set to 0.
100
Sundance Technology
ST201
PRELIMINARY draft 2
OCTETSTRANSMITTEDOK
Class....................I/O Registers, Statistics
Base Address ......IoBaseAddress register value
Address Offset.....0x6c
Access Mode.......Read (also clears register)/Write
Width ...................32 bits
BIT
BIT NAME
BIT DESCRIPTION
19..0
OctetsTransmitte-
dOk
This statistic counts the total number of frame header, data and pad-
ding octets in frames that are successfully transmitted. This is a 20-bit
counter and will wrap around to zero after reaching fffffh. An Updat-
eStats interrupt will occur after the counter has counted through
c0000h. This statistic must be read as two 16-bit quantity with the
lower word first. Upon reading the lower word, the upper word value is
latched in and the lower value is cleared. The upper word is also
cleared when read.
31..20
Reserved
Reserved for future use. Should be set to 0.
101
Sundance Technology
ST201
PRELIMINARY draft 2
SINGLECOLLISIONFRAMES
Class....................I/O Registers, Statistics
Base Address ......IoBaseAddress register value
Address Offset.....0x77
Access Mode.......Read (also clears register)/Write
Width ...................8 bits
BIT
7..0
BIT NAME
BIT DESCRIPTION
SingleCollision-
Frames
This statistic counts the number of frames that are involved in a single
collision, and are subsequently transmitted successfully. This is a 8-bit
counter and will wrap around to zero after reaching ffh. An UpdateStats
interrupt will occur after the counter has counted through c0h.
102
Sundance Technology
ST201
PRELIMINARY draft 2
PCI CONFIGURATION REGISTERS
PCI based systems use a slot-specific block of configuration registers to perform configuration of devices
on the PCI bus. The configuration registers are accessed with PCI Configuration Cycles. The PCI bus sup-
ports two types of Configuration Cycles. Type 0 cycles are used to configure devices on the local PCI bus.
Type 1 cycles are used to pass a configuration request to a PCI bus at a different hierarchical level. PCI
Configuration Cycles are directed at one out of eight possible PCI logical functions within a single physical
PCI device. A ST201 based PCI bus master device responds only to Type 0 Configuration Cycles, directed
at function 0. Type 1 cycles, and Type 0 cycles directed at functions other than 0, are ignored by the
ST201.
Each PCI bus device is required to decode 256 bytes of configuration registers. Of these, the first 64 bytes
are pre-defined by the PCI Specification. The remaining registers may be used as needed for PCI device-
specific configuration registers. In PCI Configuration Cycles, the host system provides a slot-specific
decode signal (IDSEL) which informs the PCI device that a configuration cycle is in progress. The PCI
device responds by asserting DEVSELN, and decoding the specific configuration register from the address
bus and the byte enable signals. See the PCI Expansion ROM specification for information on generating
configuration cycles from driver software.
Figure 12 shows the PCI configuration registers implemented by ST201. All locations marked “Reserved”,
and all of the locations within the 256-byte configuration space that are not shown in the table, are not
implemented and return zero when read.
103
Sundance Technology
ST201
PRELIMINARY draft 2
byte 3
byte 2
byte 1
byte 0
Offset
0xe0..
0x60
Reserved
Reserved
Reserved
0x5c
0x58
0x54
0x50
Reserved
PowerMgmtCtrl
NextItemPtr
PowerMgmtCap
CapId
Reserved
Reserved
Reserved
Reserved
0x4c
0x48
0x44
0x40
MaxLat
MinGnt
InterruptPin
InterruptLine
CapPtr
0x3c
0x38
0x34
0x30
Reserved
Reserved
ExpRomBaseAddress
SubsystemId
SubsystemVendorId
0x2c
0x28
0x24
0x20
Reserved
Reserved
Reserved
Reserved
Reserved
0x1c
0x18
0x14
0x10
MemBaseAddress
IoBaseAddress
Reserved
HeaderType
ClassCode
LatencyTimer
CacheLineSize
RevisionId
0x0c
0x08
0x04
0x00
ConfigStatus
DeviceId
ConfigCommand
VendorId
FIGURE 12: ST201 PCI Register Layout
104
Sundance Technology
ST201
PRELIMINARY draft 2
CACHELINESIZE
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x0c
Access Mode.......Read/Write
Width ...................8 bits
BIT
7..0
BIT NAME
BIT DESCRIPTION
CacheLineSize
The system BIOS writes the system’s cache line size into this register.
The adapter uses this to optimize PCI bus master operation (choosing
the best memory command, etc.). The value in CacheLineSize repre-
sents the number of dwords in a cache. CacheLineSize only supports
powers of two from 4 to 64 (giving a range of 16 to 256 bytes). An
unsupported value is treated the same as zero.
105
Sundance Technology
ST201
PRELIMINARY draft 2
CAPPTR
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x34
Access Mode.......Read Only
Width ...................8 bits
BIT
7..0
BIT NAME
CapPtr
BIT DESCRIPTION
This is a hard-coded value pointing to the beginning of a chain of regis-
ters that describe enhanced functions. The CapPtr register returns
50h, which points to the power management registers.
106
Sundance Technology
ST201
PRELIMINARY draft 2
CLASSCODE
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x09
Access Mode.......Read Only
Width ...................24 bits
BIT
BIT NAME
ClassCode
BIT DESCRIPTION
23..0
This register identifies the general function of the PCI device. The
ST201 returns 020000h, indicating Ethernet network controller.
107
Sundance Technology
ST201
PRELIMINARY draft 2
CONFIGCOMMAND
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x04
Access Mode.......Read/Write
Width ...................16 bits
This register provides control over the adapter’s ability to generate and respond to PCI cycles. When a
zero is written to this register, the adapter is logically disconnected from the PCI bus, except for configura-
tion cycles.
BIT
BIT NAME
IoSpace
BIT DESCRIPTION
0
1
Setting this bit allows the adapter to respond to I/O space accesses (if
the adapter is in the D0 power state).
MemorySpace
BusMaster
Setting this bit along with AddressDecodeEnable in ExpRomBaseAd-
dress allows the adapter to decode accesses to its Expansion ROM, if
one is installed, and if the adapter is in the D0 power state.
2
Setting this bit allows adapters with bus master capability to initiate bus
master cycles (if the adapter is in the D0 power state).
3
4
Reserved
Reserved for future use. Should be set to 0.
MWlEnable
Memory Write and Invalidate Enable. Setting this bit allows the adapter
to generate the MWI command.
5
6
Reserved
Reserved for future use. Should be set to 0.
ParityErrorRe-
sponse
This bit controls how the adapter responds to parity errors. Setting this
bit causes the adapter to take its normal action upon detecting a parity
error. Clearing this bit causes the adapter to ignore parity errors. This
bit is cleared upon system reset.
7
8
Reserved
Reserved for future use. Should be set to 0.
SERREnable
This bit is the enable bit for the SERRN pin driver. A value of zero dis-
ables the SERRN driver.
15..9
Reserved
Reserved for future use. Should be set to 0.
108
Sundance Technology
ST201
PRELIMINARY draft 2
CONFIGSTATUS
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x06
Access Mode.......Read/Write
Width ...................16 bits
This register is used to record status information for PCI bus events. Read/write bits in the register can
only be reset, not set, by writing to this register. Bits are reset by writing a one to that bit position.
BIT
3..0
BIT NAME
Reserved
BIT DESCRIPTION
Reserved for future use. Should be set to 0.
4
Capabilities
This read-only bit is always set, indicating the existence of a list of
extended capabilities registers. The CapPtr register points to the start
of the list.
6..5
7
Reserved
Reserved for future use. Should be set to 0.
FastBackToBack
This read-only bit, when set, indicates that the adapter, as a Target,
supports fast back-to-back transactions as defined by the criteria in the
section 3.4.2 of the PCI specification.
8
DataParityRe-
ported
The adapter sets this bit when, as a master, it detects the PERRN sig-
nal asserted, and the ParityErrorResponse bit is set in the ConfigCom-
mand register.
10..9
DevselTiming
This read-only field is used to encode the slowest time with which the
adapter asserts the DEVSELN signal. ST201-based adapters return
01b, indicating that they support “medium” speed DEVSELN assertion.
11
12
13
14
15
SignaledTargetA-
bort
The adapter sets this bit when it terminates a bus transaction with tar-
get-abort.
ReceivedTargetA-
bort
The adapter sets this bit when, operating as a bus master, its bus
transaction is terminated with target-abort.
ReceivedMaster-
Abort
The adapter sets this bit when, operating as a bus master, its bus
transaction is terminated with master-abort.
SignaledSystemEr- This bit is set whenever the adapter asserts SERRN.
ror
DetectedParityEr-
ror
The adapter sets this bit when it detects a parity error, regardless of
whether parity error handling is enabled.
109
Sundance Technology
ST201
PRELIMINARY draft 2
DEVICEID
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x02
Access Mode.......Read Only
Width ...................16 bits
BIT
BIT NAME
DeviceId
BIT DESCRIPTION
15..0
This register contains the 16-bit device ID for the ST201. It is hard-
wired to 0201h.
110
Sundance Technology
ST201
PRELIMINARY draft 2
EXPROMBASEADDRESS
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x30
Access Mode.......Read/Write
Width ...................32 bits
This read/write register allows the system to define the base address for the adapter’s Expansion ROM.
BIT BIT NAME BIT DESCRIPTION
AddressDecodeEn- When this bit is cleared, the adapter’s Expansion ROM is disabled.
0
able
Setting this bit causes the adapter to respond to accesses in its config-
ured expansion ROM space, if MemorySpace in the ConfigCommand
register is also set.
14..1
Reserved
Reserved for future use. Should be set to 0.
31..15
RomBaseAddress
The system programs the expansion ROM base address into this field.
The access to bit [15] depends on Expansion ROM size setting in Asic-
Ctrl register. When ExpRomSize is 0 (32KB ExpRom), bit [15] is written
as part of the RomBaseAddress. When ExpRomSize is 1 (64KB
ExpRom), bit [15] ignores any write operation.
111
Sundance Technology
ST201
PRELIMINARY draft 2
HEADERTYPE
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x0e
Access Mode.......Read Only
Width ...................8 bits
BIT
7..0
BIT NAME
HeaderType
BIT DESCRIPTION
This register is hard-wired to 00h, identifying the ST201 as a single-
function PCI and specifies the configuration register layout.
112
Sundance Technology
ST201
PRELIMINARY draft 2
INTERRUPTLINE
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x3c
Access Mode.......Read/Write
Width ...................8 bits
BIT
7..0
BIT NAME
BIT DESCRIPTION
InterruptLine
This register is written by the system to communicate to the device
driver which interrupt level is being used for the device. This allows the
driver to use the appropriate interrupt vector for its ISR. For 80x86 sys-
tems, the value in InterruptLine correspond to the IRQ numbers (0
through 15) of the standard dual 8259 configuration, and the value 255
correspond to “disabled”.
113
Sundance Technology
ST201
PRELIMINARY draft 2
INTERRUPTPIN
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x3d
Access Mode.......Read Only
Width ...................8 bits
BIT
7..0
BIT NAME
InterruptPin
BIT DESCRIPTION
This register indicates which PCI interrupt pin the adapter will use.
ST201-based adapters always use INTAN, so 01h is returned in Inter-
ruptPin.
114
Sundance Technology
ST201
PRELIMINARY draft 2
IOBASEADDRESS
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x10
Access Mode.......Read/Write
Width ...................32 bits
The host uses this register to define the I/O base address for the adapter. PCI system requires that I/O
base addresses be set as if the system used 32-bit I/O addressing. The upper 25 bits of the register are
read/write accessible, indicating that the ST201 requires 128 bytes of I/O space in the system I/O map.
BIT
BIT NAME
BIT DESCRIPTION
0
IoBaseAddrInd
A value of 1 indicates this register holds the I/O base address for the
ST201.
6..1
Reserved
Reserved for future use. Should be set to 0.
31..7
IoBaseAddress
The system programs the I/O base address into this field. Since the
ST201 uses 128 bytes of I/O space, 25 bits are required to completely
specify the I/O base address.
115
Sundance Technology
ST201
PRELIMINARY draft 2
LATENCYTIMER
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x0d
Access Mode.......Read/Write
Width ...................8 bits
This register specifies, in units of PCI bus clocks, the value of the latency timer for bus master operations.
The host system writes a value into LatencyTimer, which determines how long the ST201 may hold the
bus in the presence of other bus requestors. Whenever the ST201 asserts FRAMEN, the latency timer is
started. When the timer count expires, the ST201 must relinquish the bus as soon as its GNTN signal has
been negated. The granularity of the timer is 8 bus clocks.
BIT
BIT NAME
BIT DESCRIPTION
2..0
7..3
Reserved
LatencyTimer
Reserved for future use. Should be set to 0.
Indicates, in increments of 8 bus clocks, the length of time which the
ST201 may hold the PCI bus in the presence of other bus requestors.
116
Sundance Technology
ST201
PRELIMINARY draft 2
MAXLAT
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x3f
Access Mode.......Read Only
Width ...................8 bits
BIT
7..0
BIT NAME
MaxLat
BIT DESCRIPTION
MaxLat specifies, in 250 ns increments, how often the ST201 requires
bus access while operating as a bus master. The value for MaxLat is
stored in the ConfigParm word in EEPROM. Assumes the PCI system
allows 64-byte maximum bursts with full duplex operation, the ST201-
based 100 Mbps systems return the value 10 in this field, implying a
latency tolerance of 2.5us, according to the calculation:
64 bytes/(12.5 MB/s x 2) = 2.56us
The result is rounded to 2.5 us, which is 250 ns * 10
117
Sundance Technology
ST201
PRELIMINARY draft 2
MEMBASEADDRESS
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x14
Access Mode.......Read/Write
Width ...................32 bits
The host uses this register to define the memory base address for the adapter registers.
BIT
BIT NAME
BIT DESCRIPTION
0
MemBaseAddrInd
MemMapType
A value of 1 indicates this register is the memory base address.
2..1
These are read-only bits, and [2] is hard wired to 0. Bit[1] is loaded
from EEPROM Lower1Meg bit of the ConfigParm. When set to 01,
instructs the host system to map the adapter registers into the lowest 1
megabyte of memory address space. When set to 00, the registers can
be map to anywhere within the 32-bit address space.
6..3
Reserved
Reserved for future use. Should be set to 0.
31..7
MemBaseAddress
The system programs the memory base address into this field. Since
the adapter registers occupy 128 bytes of I/O space, 25 bits are
required to completely specify the memory base address.
118
Sundance Technology
ST201
PRELIMINARY draft 2
MINGNT
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x3e
Access Mode.......Read Only
Width ...................8 bits
BIT
7..0
BIT NAME
MinGnt
BIT DESCRIPTION
MinGnt specifies, in 250 ns increments, how long a burst period the
adapter requires when operating as a bus master. The value for
MinGnt is stored in the ConfigParm word in EEPROM. ST201-based
PCI systems return the value 10 in this field. This assumes a 33 MHz
bus (30 ns clock period), 1 clock for address phase, 10 clock latency to
first data phase, then no wait states for the 64 remaining data phases.
(1 + 10 + 64)30ns = 2.25us, rounded up to 2.5us; 2.5us/250 ns = 10
119
Sundance Technology
ST201
PRELIMINARY draft 2
REVISIONID
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x08
Access Mode.......Read Only
Width ...................8 bits
BIT
7..0
BIT NAME
RevisionId
BIT DESCRIPTION
This register provides a revision code for the ST201. The first ST201
will return 00h. Future revisions of the chip will cause this value to be
incremented.
120
Sundance Technology
ST201
PRELIMINARY draft 2
SUBSYSTEMID
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x2e
Access Mode.......Read Only
Width ...................16 bits
BIT
BIT NAME
BIT DESCRIPTION
This is the value read from EEPROM word 03h after system reset.
15..0
SubsystemId
121
Sundance Technology
ST201
PRELIMINARY draft 2
SUBSYSTEMVENDORID
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x2c
Access Mode.......Read Only
Width ...................16 bits
BIT
BIT NAME
BIT DESCRIPTION
This value is read from EEPROM location 02h after system reset.
15..0
SubsystemVen-
dorId
122
Sundance Technology
ST201
PRELIMINARY draft 2
VENDORID
Class....................PCI Configuration Registers, Configuration
Base Address ......PCI device configuration header start
Address Offset.....0x00
Access Mode.......Read Only
Width ...................16 bits
BIT
BIT NAME
VendorId
BIT DESCRIPTION
15..0
This register contains the unique 16-bit manufacturer’s ID as allocated
by the PCI SIG. Sundance’s manufacturer ID is hard-wired to 0x13f0.
123
Sundance Technology
ST201
PRELIMINARY draft 2
CAPID
Class....................PCI Configuration Registers, Power Management
Base Address ......PCI device configuration header start
Address Offset.....0x50
Access Mode.......Read Only
Width ...................8 bits
BIT
7..0
BIT NAME
CapId
BIT DESCRIPTION
This register indicates the type of capability data structure. It returns
01h to indicate a PCI Power Management structure.
124
Sundance Technology
ST201
PRELIMINARY draft 2
NEXTITEMPTR
Class....................PCI Configuration Registers, Power Management
Base Address ......PCI device configuration header start
Address Offset.....0x51
Access Mode.......Read Only
Width ...................8 bits
BIT
7..0
BIT NAME
NextItemPtr
BIT DESCRIPTION
This register points to the next capability data structure in the capabili-
ties list. It returns 00h to indicate that there are no further data struc-
tures.
125
Sundance Technology
ST201
PRELIMINARY draft 2
POWERMGMTCAP
Class....................PCI Configuration Registers, Power Management
Base Address ......PCI device configuration header start
Address Offset.....0x52
Access Mode.......Read Only
Width ...................16 bits
This register provides information about the adapter’s power management capabilities. The reset default is
7601h, but several bits are loaded from EEPROM shortly after reset.
BIT
2..0
BIT NAME
Version
BIT DESCRIPTION
This read-only field returns 1h, as specified in the PCI Bus Power Man-
agement Specification Revision 1.0.
8..3
9
Reserved
Reserved for future use. Should be set to 0.
D1Support
This read-only bit, when set, indicates that this device supports the D1
power state. This value of this bit is determined by bit 4 in the
EEPROM ConfigParm.
10
D2Support
This read-only bit, when set, indicates that this device supports the D2
power state. This value of this bit is determined by bit 5 in the
EEPROM ConfigParm.
15..11
PmeSupport
This read-only field indicates the power states from which this device is
able to generate a power management event by asserting PMEN.
Each bit corresponds to a power state. A zero in a particular bit indi-
cates that events cannot be generated from that state. The bits are
defined as follows:
xxxx1: Power management events can be generated from D0.
xxx1x: Power management events can be generated from D1.
xx1xx: Power management events can be generated from D2.
x1xxx: Power management events can be generated from D3hot.
1xxxx: Power management events can be generated from D3Cold.
The ST201 hard-wires bit 11 to zero and bit 14 to one. The values of
bits 12,13, and 15 are determined by bits 4, 5 and 3 respectively from
the EEPROM ConfigParm.
126
Sundance Technology
ST201
PRELIMINARY draft 2
POWERMGMTCTRL
Class....................PCI Configuration Registers, Power Management
Base Address ......PCI device configuration header start
Address Offset.....0x54
Access Mode.......Read/Write
Width ...................16 bits
This register allows control over the power state and the power management interrupts.
BIT
1..0
BIT NAME
PowerState
BIT DESCRIPTION
This read/write field is used to determine or set the ST201’s power
state. The following values are defined:
00: State D0
01: State D1
10: State D2
11: State D3
If PowerState is set to a non-zero value, the ST201 will not respond to
PCI I/O or memory cycles, nor will it be able to generate PCI bus mas-
ter cycles.
7..2
8
Reserved
PmeEn
Reserved for future use. Should be set to 0.
When this read/write bit is set, the ST201 is allowed to report wake
events on the PMEN signal. The specific events which can generate
wake are defined by the WakeEvent I/O register. This bit is loaded
from bit[6] of ConfigParm.
14..9
15
Reserved
Reserved for future use. Should be set to 0.
PmeStatus
This read/clear bit is set to indicate a wake event has occurred. This bit
is set regardless of the value in PmeEn. Writing a one to this bit clears
it. Writing zero has no effect.
127
Sundance Technology
ST201
PRELIMINARY draft 2
EEPROM DATA FORMAT
Figure 13 summarizes the layout of the EEPROM.
byte 1
byte 0
Offset
StationAddress2
0x14
0x12
0x10
StationAddress1
StationAddress0
SubSystemId
0x06
0x04
0x02
0x00
SubSystemVendorId
AsicCtrl
ConfigParam
FIGURE 13: EEPROM Data Layout
128
Sundance Technology
ST201
PRELIMINARY draft 2
CONFIGPARM
Class....................EEPROM Data Format
Base Address ......0x00, address written to EepromCtrl register
Address Offset.....0x00
Access Mode.......Read Only
Width ...................16 bits
This is loaded into the ST201 and controls various hardware functions related to PCI bus operation.
BIT
BIT NAME
BIT DESCRIPTION
0
1
2
FastBackToBack
Determines the value for the FastBackToBack bit in the ConfigStatus
register.
Lower1Meg
Provides the value for MemMapType[0] in the MemBaseAddress regis-
ter.
DisableMemBase
When set, disables the MemBaseAddr register. This bit causes Mem-
BaseAddr to read back as zeroes, appearing as if it is not implemented
by the adapter.
3
D3ColdPme
Provides the value returned in bit 15 of the PowerMgmtCap register.
This bit, when set, indicates that the adapter is capable of signaling
wake from the D3cold state.
4
5
6
D1Support
D2Support
PmeEn
Provides the value returned in D1Support and also bit 12 in the Power-
MgmtCap register.
Provides the value returned in D2Support and also bit 13 in the Power-
MgmtCap register.
When this bit is set, the ST201 is allowed to report wake events on the
PMEN signal.
10..7
MinGnt
MaxLat
Determines the value returned in bits [4..1] of the MinGnt register.
Determines the value returned in bits [5..1] of the MaxLat register.
15..11
ConfigParm has a default value of 2ab0h, but is normally overwritten by the value in EEPROM. The default
values specify:
FastBackToBack = 0
Lower1Meg = 0
DisableMemBase = 0
D3ColdPme = 0
D1Support = 1
D2Support = 1
PmeEn = 0
MinGnt = 0101b (2.5 us)
MaxLat = 00101b (2.5 us).
129
Sundance Technology
ST201
PRELIMINARY draft 2
STATIONADDRESS
Class....................EEPROM Data Format
Base Address ......0x00, address written to EepromCtrl register
Address Offset.....0x10, 0x12, 0x14
Access Mode.......Read Only
Width ...................48 bits
This is the field to be programmed into the StationAddress register. OEM customers may choose to pro-
gram this field with a different value.
BIT
BIT NAME
BIT DESCRIPTION
15..0
StationAddress0
The least significant word of the station address, corresponding to
address 0x10.
31..16
47..32
StationAddress1
StationAddress2
The second least significant word of the station address, correspond-
ing to address 0x12.
The most significant word of the station address, corresponding to
address 0x14.
130
Sundance Technology
ST201
PRELIMINARY draft 2
ASICCTRL
Class....................EEPROM Data Format
Base Address ......0x00, address written to EepromCtrl register
Address Offset.....0x02
Access Mode.......Read Only
Width ...................16 bits
This word supplies the value for the least significant byte of the AsicCtrl I/O Register. Bit[15] is loaded into
WakePolarity of the WakeEvent I/O Register. They are read automatically by the hardware upon reset to
provide default settings for non-system related configuration settings. The AsicCtrl register may be over-
written by the host system.
BIT
BIT NAME
Reserved
BIT DESCRIPTION
0
1
Reserved for future use. Should be set to 0.
ExpRomSize
Specifies the size of the Expansion ROM installed on the adapter, as
follows:
0 = 32 kB (default after reset)
1 = 64 kB
2
3
4
TxLargeEnable
RxLargeEnable
ExpRomDisable
This read/write bit, when set, enables transmission of frames that are
larger than the TxFIFO. Since ST201’s TxFIFO size is 2KB, this bit can
be left clear (the reset default).
This read/write bit, when set, enables reception of frames that are
larger than the RxFIFO. Since ST201’s RxFIFO size is 2KB, this bit
can be left clear (the reset default).
This bit, when set, disables accesses to the on-adapter Expansion
ROM. This bit is included to allow bypassing the Expansion ROM with-
out having to physically remove it from the board. When this bit is set,
the ST201 responds to any read in its configured Expansion ROM
space by returning 00000000h, and it ignores writes to the Expansion
ROM. This bit resets to 0.
5
6
7
PhySpeed10
PhySpeed100
PhyMedia
This read-only bit, when set, indicates the 10Mb/s operation is avail-
able from the PHY on the adapter. “0” indicates the PHY is not 10Mb/s
capable.
This read-only bit, when set, indicates the 100Mb/s operation is avail-
able from the PHY on the adapter. “0” indicates the PHY is not 100Mb/
s capable.
This read-only bit indicates the media type that is available on the
adapter. “0” indicates twisted-pair media, and “1” indicates fiber media.
The combination of PhyMedia, PhySpeed100, and PhySpeed10 will
determine the capability of the adapter. For example, [7,6,5] =
000: undefined
001: 10BASE-T PHY
010: 100BASE-T PHY
011: 10BASE-T and 100BASE-T dual-speed PHY
100: undefined
101: 10BASE-F PHY
110: 100BASE-F PHY
111: 10BASE-F and 100BASE-F dual-speed PHY
131
Sundance Technology
ST201
PRELIMINARY draft 2
BIT
BIT NAME
BIT DESCRIPTION
Reserved for future use. Should be set to 0.
14..8
15
Reserved
ResetPolarity
Setting this read/write bit will cause the RSTOUT pin to be asserted in
the HIGH state (default after RESET).
132
Sundance Technology
ST201
PRELIMINARY draft 2
SUBSYSTEMVENDORID
Address Offset ....0x04
Class....................EEPROM Data Format
Access Mode....... Read Only
Width................... 16 bits
Base Address ......0x00, address written to
EepromCtrl register
BIT
BIT NAME
BIT DESCRIPTION
15..0
SubsystemVen-
dorId
This is the two-byte subsystem vendor ID. Since in this case the sub-
system is an adapter, customers needs to use their PCI vendor ID.
133
Sundance Technology
ST201
PRELIMINARY draft 2
SUBSYSTEMID
Address Offset ....0x06
Class....................EEPROM Data Format
Access Mode....... Read Only
Width................... 16 bits
Base Address ......0x00, address written to
EepromCtrl register
BIT
BIT NAME
BIT DESCRIPTION
15..0
SubsystemId
This is the two-byte subsystem ID for the adapters, the same code as
the DeviceId is used.
134
Sundance Technology
ST201
PRELIMINARY draft 2
ABSOLUTE MAXIMUM RATINGS
OPERATING RANGES
Storage Temperature ..................-65ºC to +150ºC
Ambient Temperature....................-65ºC to +70ºC
Supply Voltage ...............................-0.3V to +6.0V
Commercial Devices
Temperature (T )............................. 0ºC to +70ºC
A
Supply Voltages (V ) ............................+5V ±5%
CC
Environmental stresses above those listed in Abso-
lute Maximum Ratings may cause permanent dam-
age resulting in device failure. Functionality at or
above the limits listed below is not guaranteed.
Exposure to the environmental stress at the levels
listed below for extended periods may adversely
affect device reliability.
Input voltages..........................................+5V ±5%
Operating ranges define the limits of guaranteed
device functionality.
135
Sundance Technology
DC CHARACTERISTICS
ST201
PRELIMINARY draft 2
DC characteristics are defined over commercial operating ranges unless specified otherwise.
PARAMETER
SYMBOL
PARAMETER
DESCRIPTION
TEST CONDITIONS
MIN
MAX UNIT
PIN TYPE IT (TTL, PCI INPUT BUFFER)
Input high voltage
V
V
2
V
IH
IL
Input low voltage
0.8
10
V
I
Input leakage current
V
= V /V
DD SS
-10
-10
µA
IN
IN
PIN TYPE ITU (TTL, PCI INPUT BUFFER WITH PULL UP)
Input high voltage
V
V
2
V
IH
IL
Input low voltage
0.8
10
V
I
Input leakage current
V
= V /V
DD SS
µA
IN
IN
PIN TYPE ITD (TTL, PCI INPUT BUFFER WITH PULL DOWN)
V
V
Input high voltage
Input low voltage
2
V
IH
IL
0.8
10
V
I
Input leakage current
V
= V /V
-10
µA
IN
IN
DD SS
PIN TYPE OT4/OC4 (TTL, CMOS OUTPUT BUFFER)
V
V
Output high voltage
Output low voltage
Output leakage current
I
I
= -4mA
= 4mA
2.4
-10
V
OH
OL
OH
OL
0.4
10
V
I
V
= V /V
DD SS
µA
OZ
IN
PIN TYPE OP3 (PCI OUTPUT BUFFER)
V
V
Output high voltage
Output low voltage
Output leakage current
I
I
= -2mA
= 3mA
2.4
-10
V
OH
OL
OH
OL
0.55
10
V
I
V
= V /V
DD SS
µA
OZ
IN
PIN TYPE OP6 (PCI OUTPUT BUFFER FOR PCI I/O WITH PULL UP)
V
V
Output high voltage
Output low voltage
Output leakage current
I
I
= -2mA
= 6mA
2.4
V
OH
OL
OH
OL
0.55
10
V
I
V
= V /V
DD SS
-10
µA
OZ
IN
TABLE 4: DC Characteristics
136
Sundance Technology
ST201
PRELIMINARY draft 2
PARAMETER
SYMBOL
PARAMETER
DESCRIPTION
TEST CONDITIONS
MIN
MAX UNIT
PIN TYPE OD6 (OPEN DRAIN OUTPUT BUFFER)
V
Output low voltage
I
= 6mA
OL
0.4
10
V
OL
I
Output leakage current
V
= V /V
DD SS
-10
-10
µA
OZ
IN
PIN TYPE OD8 (OPEN DRAIN OUTPUT BUFFER)
V
Output low voltage
I
= 8mA
0.4
10
V
OL
OL
I
Output leakage current
V
= V /V
DD SS
µA
OZ
IN
TABLE 4: DC Characteristics
PIN TYPE
PINS
PCI INTERFACE
IT
RSTN, PCICLK, GNTN, IDSEL
IT/OP3
ITU/OP6
OD6
AD[31:0], CBEN[3:0], PAR
FRAMEN, IRDYN, TRDYN, DEVSELN, STOPN, PERRN
INTAN, PMEN, SERRN
OP3
REQN
EXPANSIONROM INTERFACE
ITU/OT4
ITD/OT4
OT4
ED[7:5], ED[3:0]
ED[4]
EWEN, EOEN, EA[15:0]
EEPROM INTERFACE
IT
EEDO
OT4
EEDI, EESK, EECS
MII INTERFACE
IT
TXCLK, CRS, COL, RXER, RXDV, RXD[3:0], RXCLK
PHYLNKN, PHYSPDN, PHYDPLXN
TXD[3:0], TXEN, MDC
IT
OT4
IT/OT4
MDIO
TABLE 5: Pin Type Assignment
137
Sundance Technology
ST201
PRELIMINARY draft 2
PIN TYPE
PINS
MISC INTERFACE
ITU/OT4
OT4
GPIO0, GPIO1
RSTOUT
OD8
LEDPWRN, LEDLNKN, LEDDPLXN, LEDSPDN
OC4
CLK25
OSCI
X25I
OSCOH1
X25O
TABLE 5: Pin Type Assignment
138
Sundance Technology
ST201
PRELIMINARY draft 2
SWITCHING CHARACTERISTICS
PARAMETER
SYMBOL
PARAMETER
DESCRIPTION
TEST CONDITIONS
PCI INTERFACE
MIN
MAX UNIT
T
T
T
T
T
RSTN cycle
300
30
11
11
2
-
-
-
-
-
-
rc
cc
ch
cl
PCICLK cycle
PCICLK high
PCICLK low
-
-
-
PCICLK rise to bused signal
valid
11
rv
T
PCICLK rise to REQN,
GNTN valid
2
12
-
rvp
T
T
T
PCICLK rise to signal on
PCICLK rise to signal off
2
-
-
-
-
-
rzo
roz
su
28
-
bused signal setup wrt PCI-
CLK rise
7
T
T
T
T
GNTN setup wrt PCICLK rise
REQN setup wrt PCICLK rise
signal hold wrt PCICLK rise
10
12
0
-
-
-
-
-
sup1
sup2
hd
-
-
RSTN low to output signal
float
-
40
rstoff
EXPANSION ROM INTERFACE - READ
T
T
T
ED valid from EA stable
ED valid from EOEN low
0
0
0
150
70
-
-
-
adv
odv
dvz
ED tri-stated from EOEN
high
40
EXPANSION ROM INTERFACE - LOAD
T /T
EA, EOEN setup wrt EWEN
fall
0
-
as os
T
T
EA hold wrt EWEN fall
ED setup wrt EWEN rise
50
35
0
-
-
-
-
-
ah
ds
T /T
ED, EOEN hold wrt EWEN
fall
dh oh
TABLE 6: Switching Characteristics
139
Sundance Technology
ST201
PRELIMINARY draft 2
PARAMETER
SYMBOL
PARAMETER
TEST CONDITIONS
MIN
MAX UNIT
DESCRIPTION
EWEN write cycle high
EWEN write cycle low
T
100
90
-
-
-
wh
wl
T
-
EEPROM INTERFACE
T
T
T
T
T
T
T
T
T
EESK cycle
EESK high
EESK low
EECS low
1us
250
250
250
100
50
-
-
-
-
-
-
-
-
-
-
skc
skh
skl
-
-
-
cs
EEDI valid wrt EESK rise
EECS setup wrt EESK rise
EECS hold wrt EESK fall
EEDO setup wrt EESK rise
EEDO hold wrt EESK rise
-
pd
-
csk
csh
dos
doh
0
-
70
500
500
-
MII INTERFACE - TRANSMIT
T
T
T
TXCLK cycle
TXCLK high
TXCLK low
-
-
40T
cc
ch
cl
14T
14T
26T
26T
-
-
T = 1 when 100Mb/s; 10
when 10Mb/s
T
T
TXCLK rise to TXD, TXEN
valid
20
-
rv
TXD, TXEN hold after
TXCLK rise
5
-
rh
MII INTERFACE - RECEIVE
T
T
T
RXCLK cycle
RXCLK high
RXCLK low
-
-
40T
cc
ch
cl
14T
14T
26T
26T
-
-
T = 1 when 100Mb/s; 10
when 10Mb/s
T
RXD,RXER,RXDV setup wrt
RXCLK rise
10
5
-
-
-
-
su
hd
T
RXD,RXER,RXDV hold wrt
RXCLK rise
TABLE 6: Switching Characteristics
140
Sundance Technology
ST201
PRELIMINARY draft 2
PARAMETER
SYMBOL
PARAMETER
DESCRIPTION
TEST CONDITIONS
MIN
MAX UNIT
MII INTERFACE - MANAGEMENT
T
T
T
T
T
T
MDC cycle
MDC high
MDC low
400
160
160
10
-
-
-
-
-
-
-
cc
ch
cl
-
-
MDIO setup wrt MDC rise
MDIO hold wrt MDC rise
MDC rise to MDIO valid
-
su
hd
rv
10
-
-
20
MISC INTERFACE
T
T
T
CLK25 cycle
CLK25 high
CLK25 low
-
-
40
-
cc
ch
cl
16
16
24
24
-
TABLE 6: Switching Characteristics
141
Sundance Technology
ST201
PRELIMINARY draft 2
t
rc
RSTN
t
t
cc
t
ch
cl
PCICLK
t
t
rv su
BUSSED
SIGNALS
t
t
t
rvp
sup2
sup1
REQN
t
rvp
GNTN
t
t
t
rzo
roz
hd
ANY SIGNAL
ANY SIGNAL
t
rstoff
t
abc
FIGURE 14: PCI Switching Characteristics
Read
Load
EOEN
t
t
t
oh
os
wl
EWEN
t
t
t
wh
as ah
EA[15..0]
t
t
t
t
t
dh
odv
adv
dvz
ds
ED[7..0]
FIGURE 15: Expansion ROM Switching Characteristics
142
Sundance Technology
ST201
PRELIMINARY draft 2
t
t
cs
csh
EECS
EESK
t
t
skh
t
t
skc
csk
skl
t
pd
EEDI
A7
A0
t
t
dos
doh
EEDO
D15
D0
FIGURE 16: EEPROM Switching Characteristics
143
Sundance Technology
ST201
PRELIMINARY draft 2
Transmit
TXD[3..0]
TXEN
t
t
t
rv
rv
rh
t
t
t
t
rh
cl
cc
ch
TXCLK
Receive
RXD[3..0]
RXER
t
t
t
t
t
t
su
su
su
hd
hd
hd
RXDV
t
t
t
ch
cc
cl
RXCLK
Management
MDIO
MDC
t
t
t
t
t
t
ch
su hd
cc
rv
cl
FIGURE 17: MII Switching Characteristics
144
Sundance Technology
PHYSICAL DIMENSIONS
ST201
PRELIMINARY draft 2
Copyright Sundance Technology, Inc., 1998. The information contained in this data sheet is subject to change without notice. Sun-
dance Technology assumes no responsibility for the use of any circuitry other than circuitry embodied in a Sundance Technology
product. Nor does it convey or imply any license under patent or other rights. Sundance Technology does not authorize its products
for use as critical components in life-support systems where a malfunction or failure may reasonably be expected to result in signifi-
cant injury to the user. The inclusion of Sundance Technology products in life-support systems implies that the manufacturer
assumes all risk of such use and in doing so indemnifies Sundance Technology against all charges.
145
|