throbber
Am79C971
`PCnet'M·FAST
`Hardware User's Manual
`
`AMD~
`
`Page 1
`
` Dell Inc.
` Exhibit 1014
`
`

`
`dliiiii;l
`INTRODUCTION
`
`1
`
`AMDl1
`
`1.1
`
`INTRODUCTION
`The PCnet™-FASTboard is an advanced PC network interface adapter card targeted for
`the Ethernet-PCI adapter card market. It is based on the Am79C971 PCnet-FASTdevice,
`a single-chip 32-bit full-duplex, 10/100-Mbps highly integrated Ethernet system solution.
`Designed to address high performance system applications, the flexible bus master archi(cid:173)
`tecture provides high data throughput in the system and low CPU and system bus utilization .
`The PCnet-FASTboard supports the PCI Specification (Rev. 2.1 ), jumperless bus and
`media configuration , and driver software compatible with the existing PCnet family of driv(cid:173)
`ers.
`
`This manual provides a complete description of the PCnet-FASTboard, with sections
`covering the functional description of each building block, the setup and installation of the
`board, and the hardware specification .
`
`It is assumed that the user of this manual has access to the information listed below, since
`references to these documents are made throughout this manual:
`
`• AMD Ethernet!IEEE 802.3 Family, 1994 World Network Data Book/Handbook
`(PID# 14287).
`
`• Am79C971 PCnet-FAST Single-Chip Full-Duplex 101100 Mbps Ethernet Controller for
`PC/ Local Bus Preliminary Data Sheet (PID# 20550B)
`
`• PCnet Family Network Family Driver Installation Guide (PID# 18233D)
`
`• PC/ Specification, Revision 2. 1
`
`Publication# 20963 Rev: A Amendment/0
`Issue Date: July 1996
`
`Page 2
`
`

`
`AMD~
`AMDII
`
`1-2
`1·2
`
`Page 3
`
`Introduction
`Introduction
`
`Page 3
`
`

`
`dlt4Qii;j
`FUNCTIONAL DESCRIPTION
`
`2
`
`AMD~
`
`2.1
`
`BOARD DESCRIPTION
`The PCnet-FAST board is a 10/ 1 00-Mbps PCI network interface card. The Ethernet con(cid:173)
`nection is implemented through the single RJ-45 jack which is connected to an external
`1 0/1 00 TX transceiver. The transceiver is connected to the PC net- FAST controller through
`the integrated Media Independent Interface (Mil). Due to the high integration of the PC net(cid:173)
`FAST device, very few external parts are needed. The PCnet- FAST evaluation board pro(cid:173)
`vides the remote boot capability via an EPROM on the FLASH device. In addition, SRAMs
`may be added to optimize performance. In most applications, two 15-ns 32x8 SRAMs are
`sufficient to satisfy the buffer requirement.
`
`The following diagram illustrates the implementation of the PCnet- FASTboard.
`
`B
`
`10/100
`PHY
`
`I SRAM
`I SRAM
`
`I
`
`I
`
`EPROM
`
`I
`
`r - -....
`Q)
`E
`~ <ll
`c:
`!!!
`1-
`
`'------
`
`I EEPROJ II
`
`Am79C971
`PCnet·FAST
`
`LEDs
`
`RJ-45
`
`I
`
`20963A-1
`
`Figure 2·1 Board Diagram
`
`2.2
`
`ETHERNET NODE CONTROLLER
`The single-chip Am79C971 PCnet-FAST Ethernet solution is a highly integrated solution
`that contains a Bus Interface Unit (BIU), a DMA buffer management unit, an ISO/IEC
`8802-3 and ANSI/IEEE 802.3-compliant Media Access Control (MAC) function, a flexible
`buffer architecture with an SRAM-based FIFO extension for support up to 128 Kbytes of
`external frame buffering, optional remote boot PROM/FLASH, integrated 10BASE-T and
`10BASE-2/5 (AUI ) physical layer interface, and an ANSI/IEEE 802.3-compliant Media In(cid:173)
`dependent Interface (Mil).
`
`Functional Description
`
`2·1
`
`Page 4
`
`

`
`AMD~
`
`2.3
`
`2.4
`
`2.5
`
`2.6
`
`2.7
`
`2.8
`
`LOCAL BUS INTERFACE
`The PCnet-FASTboard implements the local bus interface to the Peripheral Components
`Interconnect (PCI) revision 2.1 specification through the Am79C97 1 chip. The BIU in the
`chip is designed to operate as a PCI bus master during normal operations, and some slave
`1/0 accesses to the controller are required in normal operation as well. Initialization of the
`Ethernet controller is achieved through a combination of PCI Configuration Space ac(cid:173)
`cesses, bus slave accesses, bus master accesses, and an optional read of a serial EE(cid:173)
`PROM that is performed by the controller.
`
`ETHERNET INTERFACE
`The Ethernet interface for the PCnet-FAST board is achieved through the single RJ-45
`jack. The RJ-45 jack is connected to an external 1 0/ 1 00-Mbps transceiver connected to
`the PCnet-FAST controller through the integrated Mil.
`
`EXPANSION BOOT ROM/FLASH
`The PCnet-FASTboard can accommodate up to 256K bits of Boot ROM Code. An external
`latch is used to allow Boot ROM Address and Data Latching when AS_EBOE is asserted.
`The PCnet-FASTboard supports EPROM or Flash as an Expansion boot ROM device.
`Both are configured using the same methods and operate the same way.
`
`SRAM INTERFACE
`When using the controller in a 1 00-Mbps environment, additional frame buffering capability
`is provided by a 16-bit w ide SRAM interface which provides high performance and high
`latency tolerance on the system bus and network. The controller can use up to 128 Kbytes
`of SRAM as an extension of its dual transmit and receive FIFOs. When no SRAM is used,
`the Am79C97 1 controller's FIFOs are programmed to bypass the SRAM interface.
`SERIAL EEPROM INTERFACE
`The PCnet-FASTboard stores the unique IEEE physical address and bus configuration of
`each node in the serial EEPROM. Once pow ered up, the Am79C971 chip automatically
`detects the presence of the EEPROM and reads the 32 words stored in it through the Mi(cid:173)
`croWire interface protocol. For details of the MicroWire interface, refer to the Am79C971
`data sheet. The interface also supports the W RITE operation to the EEPROM.
`
`AUTO-NEGOTIATION CONTROL
`The PCnet-FASTboard implements the Auto-Negotiation standard per the IEEE 802.3
`specification for the 10BASE-T Media Attachment Unit (MAU) and the M il port.
`Auto-Negotiation automatically configures the link between two link partners through the
`Fast Link Pulse. The Fast Link Pulse is made up of a train of 17 clocks alternating with the
`16 data fields for a total of 33 pulses. The two link partners send information in the 16 data
`positions between themselves. Both sides look to see w hat is possible and then connect
`at the greatest speed and capability (without any software support) as show n in the table
`below. The Auto-Negotiation capabilities for the PCnet-FASTboard are as follows:
`
`Table 2·1
`
`Auto-Negotiation Capabilities
`
`Network Speed
`200 Mbps
`100 Mbps
`20 Mbps
`10 Mbps
`
`Physical Network Type
`100BASE-TX, Full Duplex
`100BASE-TX, Half Duplex
`10BASE-T, Full Duplex
`10BASE-T, Half Duplex
`
`2·2
`
`Functional Description
`
`Page 5
`
`

`
`diKiQii;j
`SETUP AND INSTALLATION
`
`3
`
`AMD~
`
`3.1
`
`3.2
`
`BOARD CONFIGURATION
`Configuration of the 1/0 base address and the interrupt channel is automatic upon power
`up, without any hardware jumpers. The system BIOS routine is responsible for assigning
`the 1/0 base address and binding the appropriate interrupt channels to the PCnet-FAST
`board. One may find out what the 1/0 base assignment and the interrupt channel binding
`through the AMD installation software and configuration utility. For more detailed informa(cid:173)
`tion on this utility, refer to the PCnet Family Network Driver Installation Guide.
`
`10/100BASE·T PHYSICAL CONNECTIONS
`A Data Terminal Equipment (DTE) system with the installed PCnet-FASTboard can
`connect to an Ethernet network using the on-board RJ-45 jack for either 1 OBASE-T or
`1 OOBASE-TX connection. Figure 3-1 illustrates a typical network configuration for the net(cid:173)
`work using the PCnet-FASTboard.
`
`TWISted-Pair Gable
`
`888
`~ ?
`
`I
`
`.......... .
`
`8-Pin RJ-45 Jack
`
`20963A-2
`
`Figure 3-1 PCnet-FAST 10/100BASE-T Physical Connections
`
`The Auto-Poll™ feature of the PCnet-FASTcontroller determines that the Mil port is used
`for the network connection. Since an external 1 0/1 00-Mbps transceiver is used in the
`PCnet-FASTboard , the Auto-Negotiation feature of the PCnet-FASTcontroller configures
`
`Setup and Installation
`
`3-1
`
`Page 6
`
`

`
`AMD~
`
`whether the capability of the network is 1 0 Mbps or 1 00 Mbps, and whether it is full or half(cid:173)
`duplex.
`
`3.3
`
`NETWORK STATUS
`Four LEOs on the bracket provide the network status as shown in the following table:
`
`LED 2
`
`Amber
`
`10/100*
`
`LED 3
`
`Green
`
`COL
`
`On = 100 Mbps
`Off = 10 Mbps
`
`On = Collision
`Off = No Collision
`
`LED
`Color
`
`Function
`
`Meaning
`
`LED 0
`
`Green
`
`LNKST
`
`On = Link Pass
`Off= Link Fail
`
`LED 1
`
`Green
`
`ACT
`
`For XMT:
`On = Transmit
`Off = No Trans.
`For ACT:
`On = Busy
`Off = No Activity
`
`"Valid only when LED 0 is On.
`
`The placement of the LEOs are shown in Figure 3-2.
`
`LED2
`
`LED O
`
`LED3
`
`LED 1
`
`Figure 3·2 LED Placement
`
`20963A-3
`
`3·2
`
`Setup and Installation
`
`Page 7
`
`

`
`Gliiiiii;J
`HARDWARE SPECIFICATIONS
`
`4
`
`AMD~
`
`4.1
`
`PCIINTERFACE
`The Am79C971 chip on the PCnet-FASTboard contains the interface logic to the PCI bus.
`Connections to the PCI bus are straightforward in that there is no external glue logic on the
`PCnet-FASTboard, thus making the PCnet-FASTboard fully compliant to the PC I loading
`and trace length specifications.
`
`The types of PCI cycles supported on the PCnet- FASTboard are as follows:
`
`• Master Memory Read
`• Master Memory Write
`• Master Memory Read Line
`• Slave Configuration Read
`• Slave Configuration Write
`• Slave 1/0 Read
`• Slave 1/0 Write
`
`The first three types are the Master cycles that the Am79C971 chip uses to transfer data
`across the PCI bus. The Am79C971 chip owns and controls the address/data bus after its
`request is acknowledged by the system arbiter. If there are two or less double words to
`read, the Am79C971 chip uses the Memory Read cycle; if there are more than two double
`words to read, the Am79C971 chip uses the Memory Read Line cycle. All Master cycles
`also support the four types of slave termination schemes specified in the PCI Revision 2.1
`specification.
`
`4.2
`
`The last four types are the Slave cycles that the host CPU uses to access configuration
`and register information in the Am79C971 chip.
`
`1/0 BASE ADDRESS AND INTERRUPT
`In a PCI system, the 1/0 base address and the interrupt channel that the PCnet- FAST
`board uses are assigned by the POST routine. Software drivers determine the 1/0 base
`address and the interrupt channel assigned to the PCnet-FAST board by reading the PCI
`configuration space of the device.
`
`Hardware Specifications
`
`4·1
`
`Page 8
`
`

`
`AMD!t1
`
`Table 4·1
`
`1/0 Port Address
`
`1/0 Resource
`
`Access Code
`
`APR OM
`
`1/0 Base address + Oh
`
`RDP
`
`RAP
`
`1/0 Base address + 1 Oh
`
`1/0 Base address + 12h for word 1/0 mode (in Am 1500 driver compatible
`mode)
`
`1/0 Base address + 14h for double word mode
`
`Reset Register
`
`1/0 Base address + 14h for word 1/0 mode (in Am 1500 driver compatible
`mode)
`
`1/0 Base address + 1 Ch for double word 1/0 mode
`
`BOP
`
`1/0 Base adddres + 16h for word 1/0 mode (in Am1500 driver compatible
`mode)
`
`1/0 Base address +1Ch for double word 1/0 mode
`
`4.3
`
`RJ-45 INTERFACE
`The PCnet-FASTboard is equipped w ith a RJ-45 type, eight-pin modular interface. The pin
`configuration and definition for the RJ-45 connection are as follows:
`
`Table 4·2
`
`RJ-45 Pinout
`
`Pin Number
`
`Pin 1
`
`Pin 2
`
`Pin 3
`
`Pin 6
`
`Pin 4
`
`Pin 5
`
`Pin 7
`
`Pin 8
`
`Color Code
`
`white/orange band
`
`orange/white band
`
`white/green band
`
`green/white band
`
`blue/white band
`
`white/blue band
`
`solid orange
`
`solid gray
`
`Function
`
`TX+
`
`TX-
`
`RX+
`
`RX-
`
`Not Used
`
`Not Used
`
`Not Used
`
`Not Used
`
`The color code may vary from one cable manufacturer to another. Make sure that the TX+
`and the TX- w ires are twisted as a pair and the RX+ and the RX- w ires are twisted as an(cid:173)
`other pair. For 1 00-Mbps operation, category 5 w ire must be used for proper 1 OOBASE-TX
`operation.
`
`Note: Do not use the telephone-type cable commonly known as "silver satin" (flat, with sil(cid:173)
`ver vinyl jacket) to connect the stations as none of the wires are twisted.
`
`SERIAL EEPROM
`The serial EEPROM contains the IEEE physical address unique to each node, the bus
`configuration, and the MAU configuration information . The format of the EEPROM
`contents is the follow ing, beginning with the byte that resides at the lowest EEPROM
`address:
`
`Hardware Specifications
`
`4.4
`
`4·2
`
`Page 9
`
`

`
`Table 4·3
`
`EEPROM Address Format
`
`AMD~
`
`Byte
`Word
`Address Addr Most Significant Byte (MSB)
`2nd byte of the ISO 8802-3
`OOh
`01h
`(IEEE! ANSI 802.3) station
`physical address for this node
`4th byte of node address
`6th byte of node address
`Reserved location; must be OOh
`
`01h
`02h
`03h
`
`03h
`05h
`07h
`
`02h
`04h
`06h
`
`Byte
`Addr Least Significant Byte (LSB)
`OOh
`1st byte of the ISO 8802-3
`(IEEE! ANSI 802.3) station
`physical address for this node
`3rd byte of node address
`5th byte of node address
`Reserved location; must be
`OOh
`Reserved location; must be
`OOh
`
`08h
`
`33h
`
`Reserved location; must be OOh
`
`32h
`
`Hardware Specifications
`
`4·3
`
`04h
`
`09h
`
`05h
`06h
`
`OBh
`ODh
`
`07h
`
`OFh
`
`11h
`
`13h
`15h
`17h
`19h
`1Bh
`
`1Dh
`
`1Fh
`21h
`
`23h
`
`25h
`27h
`29h
`
`2Bh
`
`2Dh
`2Fh
`31h
`
`08h
`
`09h
`OAh
`OBh
`OCh
`ODh
`
`OEh
`
`OFh
`10h
`
`11h
`
`12h
`13h
`14h
`
`15h
`
`16h
`17h
`18h
`
`19h
`
`Hardware ID: must be 11 h rt
`compatibility to AMD drivers is
`desired
`User programmable space
`MSB of two-byte checksum,
`which is the sum of bytes OOh-
`OBh and bytes OEh and OFh
`Must be ASCII "W" (57h) if
`compatibility to AMD driver
`software is desired
`BCR2[15:8] (Miscellaneous
`Configuration)
`BCR4[15:8] (Link Status LED)
`BCR5[15:8] (LED1 Status)
`BCR6[15:8] (LED2 Status)
`BCR7[15:8] (LED3 Status)
`BCR9[15:8] (Full-Duplex
`Control)
`BCR18[15:8] (Burst & Bus
`Control)
`BCR22[15:8] (PCI Latency)
`BCR23[15:8] (PCI Subsystem
`Vendor ID)
`BCR24[15:8] (PCI Subsystem
`I D)
`24h
`BCR25[15:8] (SRAM Size)
`BCR26[15:8] (SRAM Boundary) 26h
`28h
`BCR27[15:8] (SRAM Interface
`Control)
`BCR32[15:8] (Mil Control &
`Status)
`BCR33[15:8] (Mil Address)
`BCR35[15:8] (PCI Vendor ID)
`Reserved location; must be OOh
`
`OAh
`OCh
`
`OEh
`
`10h
`
`12h
`14h
`16h
`18h
`1Ah
`
`1Ch
`
`1Eh
`20h
`
`22h
`
`2Ah
`
`2Ch
`2Eh
`30h
`
`User programmable space
`LSB of two byte checksum,
`which is the sum of bytes OOh-
`OBh and bytes OEh and OFh
`Must be ASCII "W" (57h) if
`compatibility to AMD driver
`software is desired
`BCR2[7:0] (Miscellaneous
`Configuration)
`BCR4[7:0] (Link Status LED)
`BCR5[7:0] (LED1 Status)
`BCR6[7:0] (LED2 Status)
`BCR7[7:0] (LED3 Status)
`BCR9[7:0] (Full-Duplex
`Control)
`BCR18[7:0] (Burst & Bus
`Control)
`BCR22[7:0] (PCI Latency
`BCR23[7:0] (PCI Subsystem
`Vendor ID)
`BCR24[7:0] (PCI Subsystem
`I D)
`BCR25[7:0] (SRAM Size)
`BCR26[7:0] (SRAM Bounder)
`BCR27[7:0] (SRAM Interface
`Control)
`BCR32[7:0] (Mil Control &
`Status)
`BCR33[7:0] (Mil Address)
`BCR35[7:0] (PCI Vendor ID)
`Reserved location; must be
`OOh
`Reserved location; must be
`OOh
`
`Page 10
`
`

`
`AMD;t1
`
`1Ah
`
`1Bh
`
`1Ch
`
`1Dh
`
`1Eh
`
`1Fh
`
`35h
`
`Reserved location; must be OOh 34h
`
`37h
`
`Reserved location; must be OOh 36h
`
`39h
`
`Reserved location; must be OOh 38h
`
`3Bh
`
`Reserved location; must be OOh 3Ah
`
`3Dh
`
`Reserved location; must be OOh 3Ch
`
`3Fh
`
`Checksum adjust byte for the 64 3Eh
`bytes of the EEPROM contents,
`checksum of the 64 bytes of the
`EEPROM should total to Ffh
`
`Reserved location; must be
`OOh
`Reserved location; must be
`OOh
`Reserved location; must be
`OOh
`Reserved location; must be
`OOh
`Reserved location; must be
`OOh
`Reserved location; must be
`OOh
`
`The IEEE physical address is unique to each node and manufacturer. Each manufacturer
`of the PCnet-FASTboard must only use the address block assigned to the company. AMD
`uses 00 00 1A 18 XX XX address block. To apply for an IEEE block address, the board
`manufacturer must contact:
`
`IEEE Standard Department
`445 Hoer Lane
`Piscataway, NJ 08855-1331
`c/o OUI Registrar
`Tel: (908) 562-3809
`
`The EEPROM contents could either be pre-programmed on an off-line EEPROM program(cid:173)
`mer, or be programmed on the PCnet-FASTboard via the MicroWire protocol. The actual
`programming procedure on the off-line is left to the user.
`
`Note: The last four digits of the IEEE address can be found on a label attached to the
`EEPROM of the PCnet-FAST board.
`
`4.5
`
`PHYSICAL DIMENSIONS
`W ithout the bracket mounted to the board, the physical dimensions of the board are as
`follows:
`
`• W idth: 4.7 inches
`
`• Height: 3.6 inches
`
`4.6
`
`POWER REQUIREMENTS
`The power requirements are as follows:
`
`• 3.25 W maximum, 5 V DC, at 25°C (w ith NSC 10/100 PHY)
`
`• 1.90 W maximum, 5 V DC, at 25°C (w ith ICS 10/100 PHY)
`
`To properly reflect the power consumption of the board in the PCI environment, the
`PRSNT#1 and PRSNT#2 signals on the boards are shorted to Ground according to the
`PCI rev 2.1 Specification.
`
`4-4
`
`Hardware Specifications
`
`Page 11
`
`

`
`© 1996 Advanced Micro Devices, Inc.
`
`Advanced Micro Devices reserves the right to make changes in its products
`without notice in order to improve design or performance characteristics.
`
`This publication neither states nor implies any warranty of any kind, including but not limited to implied warrants of merchantability or fitness for

`a particular application. AMD
` assumes no respons bility for any circuitry other than the circuitry in an AMD product.
`
`The information in this publication is believed to be accurate in all respects at the time of publication, but is subject to change without notice. AMD
`assumes no responsibility for any errors or omissions, and disclaims responsibility for any consequences resulting from the use of the information
`included herein. Additionally, AMD assumes no responsibility for the functioning of undescribed features or parameters.
`
`Copyright © 1996 Advanced Micro Devices, Inc. All rights reserved.
`
`AMD, the AMD logo, and combinations thereof are trademarks of Advanced Micro Devices, Inc.
`
`Auto-Poll and PCnet are trademarks of Advanced Micro Devices, Inc.
`
`Product names used in this publication are for identification purposes only and may be trademarks of their respective companies.
`
`
`
`Page 12

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket