both Ethernet and SCSI controllers allows reduced power consumption for critical battery
powered applications and ‘Green PCs’
■ Fully static design for low frequency and
power operation
■ 132-pin PQFP package
Advanced
Micro
Devices
GENERAL DESCRIPTION
The PCnet-SCSI combination Ethernet and 8-bit Fast
SCSI controller with a 32-bit PCI bus interface is a highly
integrated Ethernet-Fast SCSI system solution designed to address high-performance system application
requirements. This single-chip is a flexible bus-mastering device that can be used in many applications, including network- and SCSI-ready PCs, printers, fax
This document contains information on a product under development at Advanced Micro Devices, Inc. The information is intended
to help you to evaluate this product. AMD reserves the right to change or discontinue work on this proposed product without notice.
modems, and bridge/router designs. The bus-master
architecture provides high data throughput in the system and low CPU and system bus utilization. The
PCnet-SCSI controller is fabricated with AMD’s advanced low-power CMOS process to provide low operating and standby current for power sensitive
applications.
Publication# 18681 Rev. B Amendment/1
Issue Date: October 1994
AMD
P R E L I M I N A R Y
The PCnet-SCSI is part of AMD’s PCI product family of
plug-in and software compatible SCSI and Ethernet
controllers. This product compatibility ensures a low
cost system upgrade path and lower motherboard
manufacturing costs.
Ethernet Specific
The PCnet-SCSI controller includes a complete Ethernet node integrated into a single VLSI device. It contains
a bus interface unit, a DMA buffer management unit, an
IEEE 802.3-defined Media Access Control (MAC) function, individual 136-byte transmit and 128-byte receive
FIFOs, an IEEE 802.3-defined Attachment Unit Interface (AUI) and Twisted-Pair Transceiver Media Attachment Unit (10BASE-T MAU), and a Microwire EEPROM
interface. The PCnet-SCSI controller is also register
compatible with the LANCE (Am7990) Ethernet controller, the C-LANCE (Am79C90) Ethernet controller, the
ILACC (Am79C900) Ethernet controller, and all Ethernet controllers in the PCnet Family, including the PCnetISA controller (Am79C960), the PCnet-ISA+ controller
(Am79C961), and the PCnet-32 controller
(Am79C965). The buffer management unit supports the
LANCE, ILACC, and PCnet descriptor software models.
The PCnet-SCSI controller is software compatible with
the Novell NE2100 and NE1500 Ethernet adapter card
architectures. In addition, a Sleep function has been incorporated to provide low standby current, excellent for
notebooks and Green PCs.
The 32-bit multiplexed bus interface unit provides a direct interface to the PCI local bus applications, simplifying the design of an Ethernet node in a PC system. With
its built-in support for both little and big endian byte
alignment, this controller also addresses proprietary
non-PC applications.
The PCnet-SCSI controller supports auto configuration
in the PCI configuration space. Additional PCnet-SCSI
controller configuration parameters, including the
unique IEEE physical address, can be read from an external non-volatile memory (serial EEPROM) immediately following system RESET.
The controller also has the capability to automatically
select either the AUI port or the Twisted-Pair transceiver. Only one interface is active at any one time. The
individual transmit and receive FIFOs optimize system
overhead, providing sufficient latency during frame
transmission and reception, and minimizing intervention
during normal network error recovery. The integrated
Manchester encoder/decoder (MENDEC) eliminates
the need for an external Serial Interface Adapter (SIA) in
the system. In addition, the device provides programmable on-chip LED drivers for transmit, receive, collision, receive polarity, link integrity or jabber status.
SCSI Specific
The PCnet-SCSI controller also includes a highperformance Fast SCSI controller with a glueless interface to the PCI local bus. The PCnet-SCSI integrates its
own 32-bit bus mastering DMA engine with an industry
standard Fast SCSI-2 block. The DMA engine and accompanying 96 byte DMA FIFO allow 32-bit burst data
transfers across the high bandwidth PCI bus at speeds
of up to 132 Mbyte/s. Full support for scatter-gather
DMA transfers optimize performance in multi-tasking
system applications.
The PCnet-SCSI’s on-chip state machine controls SCSI
bus sequences in hardware and is coupled with the bus
mastering DMA engine to eliminate the need for an onchip RISC processor. This results in a smaller die size
giving the Am79C974 superior price/performance versus competitive offerings.
AMD supports the Am79C974 with a total system solution which includes:
A full suite of licensable SCSI drivers and utilities
fully tested under the following operating system
environments:
— DOS 5.0 – 6.0
— Windows 3.1
— Windows NT
— OS/2 2.x
— Netware 3.x, 4.x
— SCO UNIX 3.2.4, ODT 2.0
An INT13h Compatible SCSI ROM BIOS
ASPI Compatibility
Complete hardware reference design kit
For more detailed information on the PCnet-SCSI refer
to the technical manual, PID #18738A.
Am486
Am53C94/96High-Performance SCSI Controller
Am53C974PC
Am53CF94/96Enhanced Fast SCSI-2 Controller
Am79C90CMOS Local Area Network Controller for Ethernet (C-LANCE)
Am79C98Twisted-Pair Ethernet Transceiver (TPEX)
Am79C100Twisted-Pair Ethernet Transceiver Plus (TPEX+)
Am79C900Integrated Local Area Communications Controller
Am79C940Media Acces Controller for Ethernet (MACE
Am79C960PCnet-ISA Single-Chip Ethernet Controller (for ISA bus)
Am79C961PCnet-ISA
Am79C965PCnet-32 Single-Chip 32-Bit Ethernet Controller (for 386DX, 486 and VL buses)
Am79C970PCnet-PCI Single-Chip Ethernet Controller for PCI Local Bus
Am79C981Integrated Multiport Repeater Plus
Am79C987Hardware Implemented Management Information Base
Am7990Local Area Network Controller for Ethernet (LANCE)
Am7996IEEE 802.3/Ethernet/Cheapernet Tap Transceiver
Am85C30Enhanced Serial Communication Controller
Pin 1 is marked for orientation.
RESERVE = Don’t Connect.
12
VSSB
AD15
AD1439AD13
AD12
VSSB
AD1142AD10
AD9
AD8
AD7
AD6
VDDB
C/BE0
Am79C974
VSSB
AD5
AD453AD3
AD2
VSSB
AD1
AD0
VDD
PWDN
VSS
BUSY
SCSICLK
VSS
ATN
BSY
SCSI^RST
18681A-3
P R E L I M I N A R Y
AMD
ORDERING INFORMATION
Standard Products
AMD standard products are available in several packages and operating ranges. The order number (Valid Combination) is
formed by a combination of:
AM79C974KC\W
ALTERNATE PACKAGING OPTION
\W = Trimmed and Formed in a Tray
OPTIONAL PROCESSING
Blank = Standard Processing
TEMPERATURE RANGE
C = Commercial (0
PACKAGE TYPE (per Prod. Nomenclature)
K = Plastic Quad Flat Pack Trimmed and Formed
(PQB132)
°C to +70°C)
DEVICE NUMBER/DESCRIPTION
Am79C974
PCnet-SCSI Combination Ethernet and
SCSI Controller for PCI Systems
Valid Combinations
AM79C974
KC\W
SPEED OPTION
Not Applicable
Valid Combinations
Valid Combinations list configurations planned to be
supported in volume for this device. Consult the local
AMD sales office to confirm availability of specific
valid combinations and to check on newly released
combinations.
13Am79C974
AMD
P R E L I M I N A R Y
PIN DESIGNATIONS
Listed by Pin Number
Pin No.Pin NamePin No.Pin NamePin No.Pin NamePin No.Pin Name
EECSMicrowire Serial PROM Chip SelectOO81
EEDI/LNKSTMicrowire Serial EEPROM Data In/Link StatusOLED1
EEDO/LED3Microwire APROM Data Out/LED predriverIOLED1
EESK/LED1Microwire Serial PROM Clock/LED1IOLED1
SLEEPSleep Mode INA1
XTAL1–2Crystal Input/OutputIONA2
Attachment Unit Interface (AUI)
CI+/CI–AUI Collision Differential PairINA2
DI+/DI–AUI Data In Differential PairINA2
DO+/DO–AUI Data Out Differential PairODO2
10BASE-T Interface
RXD+/RXD–Receive Differential PairINA2
TXD+/TXD–Transmit Differential PairOTDO2
TXP+/TXP–Transmit Pre-distortion Differential PairOTPO2
LNKST/EEDILink Status/Microwire Serial EEPROM Data InOLED1
These signals are multiplexed on the same PCI pins.
During the first clock of a transaction AD[31:00] contain
the physical byte address (32 bits). During the subsequent clocks AD[31:00] contain data. Byte ordering is little endian by default. AD[07:00] are defined as least
significant byte and AD[31:24] are defined as the most
significant byte. For FIFO data transfers, the PCnetSCSI controller can be programmed for big endian byte
ordering. See CSR3, bit 2 (BSWP) for more details.
During the address phase of the transaction, when the
PCnet-SCSI controller is a bus master, AD[31:2] will address the active DWORD (double-word). The PCnetSCSI controller always drives AD[1:0] to ‘00’ during the
address phase indicating linear burst order. When the
PCnet-SCSI controller is not a bus master, the
AD[31:00] lines are continuously monitored to determine if an address match exists for I/O slave transfers.
During the data phase of the transaction, AD[31:00] are
driven by the PCnet-SCSI controller when performing
bus master writes and slave read operations. Data on
AD[31:00] is latched by the PCnet-SCSI controller when
performing bus master reads and slave write
operations.
When RST is active, AD[31:0] are inputs for NAND tree
testing.
C/BE [3:0]
Bus Command and Byte Enables
Input/Output, Active Low
These signals are multiplexed on the same PCI pins.
During the address phase of the transaction, C/BE[3:0]
define the bus command. During the data phase
C/BE[3:0] are used as Byte Enables. The Byte Enables
define which physical byte lanes carry meaningful data.
C/BE0 applies to byte 0 (AD[07:00]) and C/BE3 applies
to byte 3 (AD[31:24]). The function of the Byte Enables
is independent of the byte ordering mode (CSR3, bit 2).
When RST is active, C/BE[3:0] are inputs for NAND tree
testing.
CLK
Clock
Input
This signal provides timing for all the transactions on the
PCI bus and all PCI devices on the bus including the
PCnet-SCSI controller. All bus signals are sampled on
the rising edge of CLK and all parameters are defined
with respect to this edge. The PCnet-SCSI controller operates over a range of 0 to 33 MHz.
When RST is active, CLK is an input for NAND tree
testing.
DEVSEL
Device Select
Input/Output, Active Low
This signal when actively driven by the PCnet-SCSI
controller as a slave device signals to the master device
that the PCnet-SCSI controller has decoded its address
as the target of the current access. As an input it indicates whether any device on the bus has been selected.
When RST is active, DEVSEL is an input for NAND tree
testing.
FRAME
Cycle Frame
Input/Output, Active Low
This signal is driven by the PCnet-SCSI controller when
it is the bus master to indicate the beginning and duration of the access. FRAME is asserted to indicate a bus
transaction is beginning. FRAME is asserted while data
transfers continue. FRAME is deasserted when the
transaction is in the final data phase.
When RST is active, FRAME is an input for NAND tree
testing.
GNTA
Bus Grant
Input, Active Low
This signal indicates that the access to the bus has been
granted to the Am79C974’s SCSI controller.
The Am79C974 controller supports bus parking. When
the PCI bus is idle and the system arbiter asserts GNTA
without an active REQA from the Am79C974 controller,
the controller will actively drive the AD[31:00], C/
BE[3:0], and PAR lines.
When RST is active, GNTA is an input for NAND tree
testing.
GNTB
Bus Grant
Input, Active Low
This signal indicates that the access to the bus has been
granted to the Am79C974’s Ethernet controller. The
Am79C974 controller supports bus parking. When the
PCI bus is idle and the system arbiter asserts GNTB
without an active REQB from the Am79C974 controller,
the controller will actively drive the AD, C/BE and PAR
lines.
19Am79C974
AMD
P R E L I M I N A R Y
When RST is active, GNTB is an input for NAND tree
testing.
IDSELA
Initialization Device Select
Input, Active High
This signal is used as a SCSI controller selection for the
Am79C974 during configuration read and
write transaction.
When RST is active, IDSELA is an input for NAND tree
testing.
IDSELB
Initialization Device Select
Input, Active High
This signal is used as an Ethernet controller selection for
the PCnet-SCSI controller during configuration read
and write transaction.
When RST is active, IDSELB is an input for NAND tree
testing.
INTA
Interrupt Request
Input/Output, Active Low, Open Drain
This signal combines the interrupt requests from both
the SCSI DMA engine and the SCSI core. The interrupt
source can be determined by reading the SCSI DMA
Status Register. It is cleared when the Status Register is
read.
When RST is active, INTA is an input for NAND tree testing. This is the only time INTA is an input.
INTB
Interrupt Request
Input/Output, Active Low, Open Drain
An asynchronous attention signal which indicates that
one or more of the following status flags is set: BABL,
MISS, MERR, RINT, IDON, RCVCCO, RPCO, JAB,
MPCO, or TXSTRT. Each status flag has a mask bit
which allows for suppression of INTB assertion. The
flags have the following meaning:
When RST is active, INTB is an input for NAND tree
testing. This is the only time INTB is an input.
20
Am79C974
IRDY
Initiator Ready
Input/Output, Active Low
This signal indicates PCnet-SCSI controller’s ability, as
a master device, to complete the current data phase of
the transaction. IRDY is used in conjunction with the
TRDY. A data phase is completed on any clock when
both IRDY and TRDY are asserted. During a write IRDY
indicates that valid data is present on AD[31:00]. During
a read IRDY indicates that data is accepted by the
PCnet-SCSI controller as a bus master. Wait states are
inserted until both IRDY and TRDY are asserted simultaneously.
When RST is active, IRDY is an input for NAND tree
testing.
LOCK
Lock
Input, Active Low
LOCK is used by the current bus master to indicate an
atomic operation that may require multiple transfers.
As a slave device, the PCnet-SCSI controller can be
locked by any master device. When another master attempts to access the PCnet-SCSI while it is locked, the
PCnet-SCSI controller will respond by asserting
DEVSEL and STOP with TRDY deasserted (PCI retry).
The PCnet-SCSI controller will never assert LOCK as a
master.
When RST is active, LOCK is an input for NAND tree
testing.
PAR
Parity
Input/Output, Active High
Parity is even parity across AD[31:00] and C/BE[3:0].
When the PCnet-SCSI controller is a bus master, it
generates parity during the address and write data
phases. It checks parity during read data phases. When
the PCnet-SCSI controller operates in slave mode and
is the target of the current cycle, it generates parity during read data phases. It checks parity during address
and write data phases.
When RST is active, PAR is an input for NAND tree
testing.
PERR
Parity Error
Input/Output, Active Low, Open Drain
This signal is asserted for one CLK by the PCnet-SCSI
controller when it detects a parity error during any data
phase when its AD[31:00] lines are inputs. The PERR
pin is only active when PERREN (bit 6) in the PCI command register is set.
P R E L I M I N A R Y
AMD
The PCnet-SCSI controller monitors the PERR input
during a bus master write cycle. It will assert the Data
Parity Reported bit in the Status register of the Configuration Space when a parity error is reported by the target
device.
When RST is active, PERR is an input for NAND tree
testing.
REQA
Bus Request
Input/Output, Active Low
The Am79C974’s SCSI controller asserts REQA pin as
a signal that it wishes to become a bus master. Once asserted, REQA remains active until GNTA has become
active.
When RST is active, REQA is an input for NAND tree
testing. This is the only time REQA is an input.
REQB
Bus Request
Input/Output, Active Low
The Am79C974’s Ethernet controller asserts REQB pin
as a signal that it wishes to become a bus master. Once
asserted, REQB remains active until GNT has become
active, independent of subsequent assertion of SLEEP
or setting of the STOP bit or access to the S_RESET
port (offset14h).
When RST is active, REQB is an input for NAND tree
testing. This is the only time REQB is an input.
RST
Reset
Input, Active Low
When RST is asserted low, then the PCnet-SCSI controller performs an internal system reset of the type
H_RESET (HARDWARE_RESET). RST must be held
for a minimum of 30 CLK periods. While in the H_RESET state, the PCnet-SCSI controller will disable or
deassert all outputs. RST may be asynchronous to the
CLK when asserted or deasserted. It is recommended
that the deassertion be synchronous to guarantee a
clean and bounce free edge.
When RST is active, NAND tree testing is enabled. All
PCI interface pins are in input mode. The result of the
NAND tree testing can be observed on the BUSY output
(pin 62).
SERR
System Error
Input/Output, Active Low, Open Drain
This signal is asserted for one CLK by the PCnet-SCSI
controller when it detects a parity error during the address phase when its AD[31:00] lines are inputs.
The SERR pin is only active when SERREN (bit 8) and
PERREN (bit 6) in the PCI command register are set.
When RST is active, SERR is an input for NAND tree
testing.
STOP
Stop
Input/Output, Active Low
In the slave role, the PCnet-SCSI controller drives the
STOP signal to inform the bus master to stop the current
transaction. In the bus master role, the PCnet-SCSI
controller receives the STOP signal and stops the current transaction.
When RST is active, STOP is an input for NAND tree
testing.
TRDY
Target Ready
Input/Output, Active Low
This signal indicates the PCnet-SCSI controller’s ability
as a selected device to complete the current data phase
of the transaction. TRDY is used in conjunction with the
IRDY. A data phase is completed on any clock both
TRDY and IRDY are asserted. During a read TRDY indi-
cates that valid data is present on AD[31:00]. During a
write, TRDY indicates that data has been accepted.
Wait states are inserted until both IRDY and TRDY are
asserted simultaneously.
When RST is active, TRDY is an input for NAND tree
testing.
Ethernet Controller Pins
Board Interface
LED1
LED1
Output
This pin is shared with the EESK function. As LED1, the
function and polarity of this pin are programmable
through BCR5. By default, LED1 is active LOW and it indicates receive activity on the network. The LED1 output
from the PCnet-SCSI controller is capable of sinking the
12 mA of current necessary to drive an LED directly.
The LED1 pin is also used during EEPROM Auto-detec-
tion to determine whether or not an EEPROM is present
at the PCnet-SCSI controller Microwire interface. At the
trailing edge of the RST pin, LED1 is sampled to determine the value of the EEDET bit in BCR19. A sampled
HIGH value means that an EEPROM is present, and
EEDET will be set to ONE. A sampled LOW value
means that an EEPROM is not present, and EEDET will
be set to ZERO. See the EEPROM Auto-detection section for more details.
If no LED circuit is to be attached to this pin, then a pull
up or pull down resistor must be attached instead, in order to resolve the EEDET setting.
21Am79C974
AMD
P R E L I M I N A R Y
LED3
LED3
Output
This pin is shared with the EEDO function of the
Microwire serial EEPROM interface. When functioning
as LED3, the signal on this pin is programmable through
BCR7. By default, LED3 is active LOW and it indicates
transmit activity on the network. Special attention must
be given to the external circuitry attached to this pin. If
an LED circuit were directly attached to this pin, it would
create an I
serial EEPROM that would also be attached to this pin.
Therefore, if this pin is to be used as an additional LED
output while an EEPROM is used in the system, then
buffering is required between the LED3 pin and the LED
circuit. If no EEPROM is included in the system design,
then the LED3 signal may be directly connected to an
LED without buffering. The LED3 output from the
PCnet-SCSI controller is capable of sinking the 12 mA of
current necessary to drive an LED in this case. For more
details regarding LED connection, see the section on
LEDs.
OL requirement that could not be met by the
LNKST
LINK Status
Output
This pin provides 12 mA for driving an LED. By default, it
indicates an active link connection on the 10BASE-T interface. This pin can also be programmed to indicate
other network status (see BCR4). The LNKST pin
polarity is programmable, but by default, it is active
LOW. Note that this pin is multiplexed with the EEDI
function.
SLEEP
Sleep
Input
When SLEEP is asserted (active LOW), the PCnetSCSI controller performs an internal system reset of the
S_RESET type and then proceeds into a power savings
mode. (The reset operation caused by SLEEP assertion
will not affect BCR registers.) The PCI interface section
is not effected by SLEEP. In particular, access to the
PCI configuration space remains possible. None of the
configuration registers will be reset by SLEEP. All I/O
accesses to the PCnet-SCSI controller will result in a
PCI target abort response. The PCnet-SCSI controller
will not assert REQ while in sleep mode. When SLEEP
is asserted, all non-PCI interface outputs will be placed
in their normal S_RESET condition. All non-PCI interface inputs will be ignored except for the SLEEP pin itself. De-assertion of SLEEP results in wake-up. The
system must refrain from starting the network operations of the PCnet-SCSI device for 0.5 seconds following the deassertion of the SLEEP signal in order to allow
internal analog circuits to stabilize.
22
Am79C974
Both CLK and XTAL1 inputs must have valid clock signals present in order for the SLEEP command to take
effect. If SLEEP is asserted while REQ is asserted, then
the PCnet-SCSI controller will wait for the assertion of
GNT. When GNT is asserted, the REQ signal will be de-
asserted and then the PCnet-SCSI controller will proceed to the power savings mode.
The SLEEP pin should not be asserted during power
supply ramp-up. If it is desired that SLEEP be asserted
at power up time, then the system must delay the assertion of SLEEP until three CLK cycles after the completion of a valid pin RST operation.
The SLEEP pin does not affect the SCSI section.
XTAL1
Crystal Oscillator Input
Input
XTAL2
Crystal Oscillator Output
Output
The crystal frequency determines the network data rate.
The PCnet-SCSI controller supports the use of quartz
crystals to generate a 20 MHz frequency compatible
with the ISO 8802-3 (IEEE/ANSI 802.3) network frequency tolerance and jitter specifications. See the section External Crystal Characteristics (in section
Manchester Encoder/Decoder) for more detail.
The network data rate is one-half of the crystal frequency. XTAL1 may alternatively be driven using an external CMOS level source, in which case XTAL2 must
be left unconnected. Note that when the PCnet-SCSI
controller is in coma mode, there is an internal 22 KΩ resistor from XTAL1 to ground. If an external source drives
XTAL1, some power will be consumed driving this resistor. If XTAL1 is driven LOW at this time power consumption will be minimized. In this case, XTAL1 must remain
active for at least 30 cycles after the assertion of SLEEP
and deassertion of REQ.
Microwire EEPROM Interface
EESK
EEPROM Serial Clock
Input/Output
The EESK signal is used to access the external ISO
8802-3 (IEEE/ANSI 802.3) address PROM. This pin is
designed to directly interface to a serial EEPROM that
uses the Microwire interface protocol. EESK is connected to the Microwire EEPROM’s Clock pin. It is controlled by either the PCnet-SCSI controller directly
during a read of the entire EEPROM, or indirectly by the
host system by writing to BCR19, bit 1.
The EESK pin is also used during EEPROM Auto-detection to determine whether or not an EEPROM is present
P R E L I M I N A R Y
AMD
at the PCnet-SCSI controller Microwire interface. At the
trailing edge of the RST signal, EESK is sampled to determine the value of the EEDET bit in BCR19. A sampled HIGH value means that an EEPROM is present,
and EEDET will be set to ONE. A sampled LOW value
means that an EEPROM is not present, and EEDET will
be set to ZERO. See the EEPROM Auto-detection section for more details.
EESK is shared with the LED1 function. If no LED circuit
is to be attached to this pin, then a pull up or pull down
resistor must be attached instead, in order to resolve the
EEDET setting.
EEDO
EEPROM Data Out
Input
The EEDO signal is used to access the external ISO
8802-3 (IEEE/ANSI 802.3) address PROM. This pin is
designed to directly interface to a serial EEPROM that
uses the Microwire interface protocol. EEDO is connected to the Microwire EEPROM’s Data Output pin. It
is controlled by the EEPROM during reads. It may be
read by the host system by reading BCR19 bit 0.
EEDO is shared with the LED3 function.
EECS
EEPROM Chip Select
Output
The function of the EECS signal is to indicate to the
Microwire EEPROM device that it is being accessed.
The EECS signal is active high. It is controlled by either
the PCnet-SCSI controller during command portions of
a read of the entire EEPROM, or indirectly by the host
system by writing to BCR19 bit 2.
EEDI
EEPROM Data In
Output
The EEDI signal is used to access the external ISO
8802-3 (IEEE/ANSI 802.3) address PROM. EEDI functions as an output. This pin is designed to directly interface to a serial EEPROM that uses the Microwire
interface protocol. EEDI is connected to the Microwire
EEPROM’s Data Input pin. It is controlled by either the
PCnet-SCSI controller during command portions of a
read of the entire EEPROM, or indirectly by the host system by writing to BCR19 bit 0.
Attachment Unit Interface
CI±
Collision In
Input
A differential input pair signaling the PCnet-SCSI controller that a collision has been detected on the network
media, indicated by the CI± inputs being driven with a
10MHz pattern of sufficient amplitude and pulse width
to meet ISO 8802-3 (IEEE/ANSI 802.3) standards. Operates at pseudo ECL levels.
DI±
Data In
Input
A differential input pair to the PCnet-SCSI controller carrying Manchester encoded data from the network. Operates at pseudo ECL levels.
DO±
Data Out
Output
A differential output pair from the PCnet-SCSI controller
for transmitting Manchester encoded data to the network. Operates at pseudo ECL levels.
Twisted-Pair Interface
RXD±
10BASE-T Receive Data
Input
10BASE-T port differential receivers.
TXD±
10BASE-T Transmit Data
Output
10BASE-T port differential drivers.
TXP±
10BASE-T Pre-Distortion Control
Output
These outputs provide transmit pre-distortion control in
conjunction with the 10BASE-T port differential drivers.
EEDI is shared with the LNKST function.
23Am79C974
AMD
P R E L I M I N A R Y
SCSI Controller Pins
SCSI Bus Interface Signals
SCSI Bus Pins
SD [7:0]
SCSI Data
Input/Output, Active Low, Open Drain/Active
Negation, Schmitt Trigger
These pins are defined as bi-directional SCSI data bus.
SDP
SCSI Data Parity
Input/Output, Active Low, Open Drain/Active
Negation, Schmitt Trigger
This pin is defined as bi-directional SCSI data parity.
MSG
Message
Input, Active Low, Schmitt Trigger
It is a Schmitt trigger input in the initiator mode.
C/D
Command/Data
Input, Schmitt Trigger
It is a Schmitt trigger input in the initiator mode.
I/O
Input/Output
Input, Schmitt Trigger
It is a Schmitt trigger input in the initiator mode.
ATN
Attention
Output, Active Low, Open Drain
This signal is a 48 mA output in the initiator mode. This
signal will be asserted when the device detects a parity
error; also, it can be asserted via certain commands.
BSY
Busy
Input/Output, Active Low, Schmitt Trigger,
Open Drain
As a SCSI input signal it has a Schmitt trigger and as an
output signal it has a 48 mA drive.
SEL
Select
Input/Output, Active Low, Schmitt Trigger,
Open Drain
As a SCSI input signal it has a Schmitt trigger and as an
output signal it has a 48 mA drive.
SCSI^RST
Reset
Input/Output, Active Low, Schmitt Trigger,
Open Drain
As a SCSI input signal it has a Schmitt trigger and as an
output signal it has a 48 mA drive.
REQ
Request
Input, Active Low, Schmitt Trigger
This is a SCSI input signal with a Schmitt trigger in the
initiator mode.
ACK
Acknowledge
Output, Active Low, Open Drain/Active Negation
This is a SCSI output signal with a 48 mA drive in the
initiator mode.
SCSI CLK
SCSI Clock
Input
The SCSI clock signal is used to generate all internal device timings. The maximum frequency of this input is
40MHz and a minimum of 10 MHz is required to maintain the SCSI bus timings.
Note:
A 40 MHz clock must be supplied at this input to achieve
10 Mbyte/s Synchronous Fast SCSI transfers.
PWDN
Power Down Indicator
Input, Active High
This signal, when asserted, sets the PWDN status bit in
the DMA status register and sends an interrupt to
thehost.
Test Interface
BUSY
NAND Tree Out
Output, Active Low
This signal is logically equivalent to the SCSI bus signal
BSY. It is duplicated so that external logic can be
connected to monitor SCSI bus activity.
The results of the NAND tree testing can be observed on
the BUSY pin where RST is asserted; otherwise, BUSY
will reflect the state of the SCSI Bus Signal line BSY
(pin64).
24
Am79C974
P R E L I M I N A R Y
AMD
Miscellaneous
RESERVED
Reserved_DO NOT CONNECT
Input
This pin (#116) is reserved for internal test logic. It
MUST NOT BE CONNECTED to anything for proper
chip operation. It’s use is subject to change in future
products.
Power Supply Pins
Analog Power Supply Pins
AVDD
Analog Power (4 Pins)
Power
There are four analog +5 V supply pins. Special attention should be paid to the printed circuit board layout to
avoid excessive noise on these lines. Refer to
AppendixC and the
for details.
Technical Manual
(PID #18738A)
AVSS
Analog Ground (2 Pins)
Power
There are two analog ground pins. Special attention
should be paid to the printed circuit board layout to avoid
excessive noise on these lines. Refer to Appendix C and
the
Technical Manual
(PID #18738A) for details.
Digital Power Supply Pins
VDD/DVDD
Digital Power (5 Pins)
Power
There are 5 power supply pins that are used by the internal digital circuitry. All VDD pins must be connected to a
+5 V supply.
VDDB/VDDB
I/O Buffer Power (5 Pins)
Power
There are 5 power supply pins that are used by the PCI
bus Input/Output buffer drivers. All VDDB pins must be
connected to a +5 V supply.
VSS/DVSS
Digital Ground (9 Pins)
Ground
There are 9 ground pins that are used by the internal
digital circuitry.
VSSB/VSSBS
I/O Buffer Ground (11 Pins)
Ground
There are 11 ground pins that are used by the PCI bus
Input/Output buffer drivers.
25Am79C974
AMD
P R E L I M I N A R Y
BASIC FUNCTIONS
System Bus Interface Function
During normal operations the Am79C974 operates as a
bus master with a few slave l/O accesses for status and
control functions.
The Ethernet controller is initialized through a combination of PCI Configuration Space accesses, I/O space
Bus Slave accesses, Memory Space Bus Master accesses, and optional reads of an external serial
EEPROM. The EEPROM is read through the Microwire
interface either automatically by the Am79C974 or indirectly by a series of bus slave accesses to one of the
Ethernet Bus Configuration Registers (BCRs). The
EEPROM normally contains the ISO 8802-3 (IEEE/
ANSI 802.3) Ethernet node address and data to be
loaded into some of the Ethernet BCRs.
The SCSI controller is initialized by bus slave writes to
SCSI Core and SCSI DMA registers.
Software Interface
The Am79C794 uses four address spaces: Ethernet
PCI configuration space, SCSI PCI configuration space,
I/O space, and memory space.
SCSI PCI configuration space is selected when the
IDSELA pin is active. Ethernet PCI configuration space
is selected when the IDSELB pin is active. The way that
IDSELA and IDSELB are controlled depends on external hardware. Section 3.6.4.1 of the PCI Specification
recommends two methods of generating configuration
cycles called Configuration Mechanism #1 and Configuration Mechanism #2.
The PCI Configuration Spaces are used by system software to identify the SCSI and Ethernet controllers and to
set up device configuration without the use of jumpers.
Certain PCI configuration registers have read-only information about the devices resource requirements. Other
registers are used as mail boxes that system configuration software uses to inform other software what resources have been allocated to the device. The only PCI
Configuration Registers that affect the operation of the
Am79C794 are the SCSI and Ethernet Base Address
Registers, which are found at offset 10h in each of the
two configuration spaces, and the Command Registers
at offset 4. Writing to these registers establishes the
base address of the SCSI l/O space and the base address of the Ethernet I/O space.
The SCSI controller registers occupy 96 bytes of l/O
space that starts on whatever 128-byte boundary that is
programmed into the Base Address Register at offset
10h in the SCSI PCI Configuration Space. The Ethernet
controller registers occupy 32 bytes of l/O space that
starts on whatever 32-byte boundary that is programmed into the Base Address Register at offset 10h
in the Ethernet PCI Configuration Space. These
26
Am79C974
registers are used to set up controller operating modes,
to enable or disable various features, to start certain operations, and to monitor operating status.
In addition to the registers in the l/O space, the Ethernet
controller uses certain data structures that are set up
(typically by the host computer) in normal memory
space. These data structures are (1) the initialization
block that contains configuration data that the Ethernet
controller automatically loads into its Configuration and
Status Registers (CSRs), (2) the Receive and Transmit
Descriptor Rings, that contain pointers to receive and
transmit buffers and status and control information
about these buffers, and (3) the receive and transmit
buffers. The Ethernet controller uses bus master accesses to read the locations of the buffers, to store
frames received from the network into the receive buffers, and to transmit the contents of the transmit buffers.
Ethernet Interfaces
The Am79C974 controller can be connected to an 802.3
network via one of two network interfaces. The Attachment Unit Interface (AUI) provides an ISO 8802-3
(IEEE/ANSI 802.3) compliant differential interface to a
remote MAU or an on-board transceiver. The
10BASE-T interface provides a twisted-pair Ethernet
port. While in auto-selection mode, the interface in use
is determined by an auto-sensing mechanism which
checks the link status on the 10BASE-T port. If there is
no active link status, then the device assumes an AUI
connection.
SCSI Interfaces
The Am79C974 acts as a bridge between the PCI and
SCSI buses. As the maximum data transfer rate on the
PCI bus is a very high 132 Mbyte/s compared with the
SCSI bus 10 Mbyte/s, buffering is required between the
two buses. The buffering is provided by two FIFOs: a
16-byte (16X8 bits) SCSI Core FIFO and an additional
96-byte (24X32 bits) DMA FIFO. These FIFOs provide a
temporary storage for all command, data, status and
message bytes as they are transferred between the
32-bit PCI bus and the 8-bit SCSI bus.
The Am79C974’s SCSI Core and DMA registers are addressed using the value in the Base Address Register
(offset 10h in the PCI Configuration Space). The SCSI
registers occupy 16 double words and the DMA engine
registers occupy 8 double word locations. The I/O address map is as follows:
The PCI configuration space, Ethernet controller and
SCSI controller are described in detail in the following
sections.
P R E L I M I N A R Y
AMD
DETAILED FUNCTIONS
Bus Interface Unit (BIU)
The bus interface unit is built of several state machines
that run synchronously to CLK. One bus interface unit
state machine handles accesses where the Am79C974
controller is the bus slave, and another handles accesses where the Am79C974 controller is the bus master. All inputs are synchronously sampled. All outputs
are synchronously generated on the rising edge of CLK.
In the descriptions that follow, GNT, REQ, INT, and
IDSEL are used to refer to the set of GNTA, REQA,
INTA, and IDSELA for the SCSI controller and to the set
of GNTB, REQB, INTB, and IDSELB for the Ethernet
Controller, respectively.
Slave Configuration Transfers
The host can access the Am79C974 PCI configuration
CLK
123456
FRAME
space with a configuration read or write command. The
Am79C974 controller will assert DEVSEL if the IDSEL
input is asserted during the address phase and if the access is a configuration cycle. DEVSEL is asserted two
clock cycles after the host has asserted FRAME. All
configuration cycles are of fixed length. The Am79C974
controller will assert TRDY on the 3rd clock of the
dataphase.
Slave Configuration Read
The Slave Configuration Read command is used by the
host CPU to read the configuration space in the
Am79C974 controller. This provides the host CPU with
information concerning the device and its capabilities.
This is a single cycle, non-burst 8-bit, 16-bit, or 32-bit
transfer.
AD
C/BE
PAR
IRDY
TRDY
DEVSEL
STOP
IDSEL
ADDRDATA
1010BE's
PARPAR
18681A-5
Figure 1. Slave Configuration Read
27Am79C974
AMD
P R E L I M I N A R Y
Slave Configuration Write
The Slave Configuration Write command is used by the
host CPU to write the configuration space in the
Am79C974 controller. This allows the host CPU to
CLK
123456
FRAME
AD
C/BE
PAR
IRDY
ADDRDATA
1011BE's
PARPAR
control basic activity of the device, such as enable/disable, change I/O location, etc. This is a single cycle,
non-burst 8-bit, 16-bit, or 32-bit transfer.
TRDY
DEVSEL
STOP
IDSEL
18681A-6
Figure 2. Slave Configuration Write
28
Am79C974
P R E L I M I N A R Y
AMD
Slave I/O Transfers
After the Am79C974 controller is configured as I/O device (by setting IOEN in the PCI Command register), it
starts monitoring the PCI bus for access to its internal
registers. The Am79C974 controller will look for an address that falls within its I/O address space. The
Am79C974 controller will assert DEVSEL if it detects an
address match and the access is an I/O cycle. DEVSEL
is asserted two clock cycles after the host has asserted
FRAME. The Am79C974 controller will not assert DEV-
SEL if it detects an address match, but the PCI com-
mand is not of the type I/O read or I/O write. The
CLK
12345678
FRAME
AD
C/BE
ADDRDATA
0010BE's
Am79C974 controller will suspend looking for I/O cycles
while being a bus master.
Slave I/O Read
The Slave I/O Read command is used by the host CPU
to read the Am79C974’s CSRs, BCRs and EEPROM locations and SCSI and CCB registers. It is a single cycle,
non-burst 8-bit,16-bit or 32-bit transfer which is initiated
by the host CPU. The typical number of wait states
added to a slave I/O read access on the part of the
Am79C974 controller is 6 to 7 clock cycles. The
Am79C974 controller will not produce Slave I/O Read
commands while being a bus master.
91011
PAR
IRDY
TRDY
DEVSEL
STOP
PARPAR
18681A-7
Figure 3. Slave I/O Read
29Am79C974
AMD
P R E L I M I N A R Y
Slave I/O Write
The Slave I/O Write command is used by the host CPU
to write to the Am79C974’s CSRs, BCRs and EEPROM
locations and SCSI and CCB registers. It is a single cycle, non-burst 8-bit, 16–bit, or 32-bit transfer which is
CLK
12345678
FRAME
AD
C/BE
PAR
IRDY
ADDRDATA
0011BE's
PARPAR
initiated by the host CPU. The typical number of wait
states added to a slave I/O write access on the part of
the Am79C974 controller is 6 to 7 clock cycles. The
Am79C974 controller will not produce Slave I/O write
commands while being a bus master.
91011
TRDY
DEVSEL
STOP
18681A-8
Figure 4. Slave I/O Write
30
Am79C974
Loading...
+ 123 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.