Intel® 460GX Chipset System
Software Developer’s Manual
June 2001
Document Number: 248704 -001
THIS DOCUMENT IS PROVIDED “AS IS” WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY WARRANTY OF MERCHANTABILITY,
FITNESS FOR ANY PARTICULAR PURPOSE, OR ANY WARRANTY OTHERWISE ARISING OUT OF ANY PROPOSAL, SPECIFICATION OR
SAMPLE.
Information in this document is provided in connection with Intel® products. No license, express or implied, by estoppel or otherwise, to any
intellectual property rights is granted by this document. Except as provided in Intel's Terms and Conditions of Sale for such products, Intel assumes no
liability whatsoever, and Intel disclaims any express or implied warranty, relating to sale and/or use of Intel products including liability or warranties
relating to fitness for a particular purpose, merchantability , or infringement of any patent, copyright or other intellectual property right. Intel products are
not intended for use in medical, life saving, or life sustaining applications. Intel may make changes to specifications and product descriptions at any
time, without notice.
Designers must not rely on the absence or characteristics of any features or instructions marked “reserved” or “undefined.” Intel reserves these for
future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them.
The Intel 460GX chipset may contain design defects or errors known as errata which may cause the product to deviate from published specifications.
Current characterized errata are available on request.
Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.
Copies of documents which have an ordering number and are referenced in this document, or other Intel literature may be obtained by calling
16-1IFB Power States and Consumption................................................................16-1
16-2Causes of SMI#................................................................................................16-2
16-3Causes of SCI#................................................................................................16-3
16-4ACPI Bits Not Implemented in IFB...................................................................16-4
xiiIntel® 460GX Chipset System Software Developer’s Manual
Introduction1
This document provides information about the Intel® 460GX chipset compon e nts. The 460GX
chipset is a high performance memory and I/O chipset for the Intel Itanium™ processor, targeted
for multiprocessor server and high-end workstation designs.
This document describes the software programmer's interface to the 460GX chipset. It provides a
brief summary of the system architecture supported by the 460GX chipset, a list of features within
the chipset and a detailed description of software or other externally visible segments.
1.1System Overview
The Intel 460GX chipset is a high performance chipset for Intel Itanium processor-based systems,
targeted for multiprocessor servers and high-performance workstations. It provides the memory
controller interface and appropriate bridges to PCI, AGP 4X, and other standard I/O buses.
Figure 1-1 illustrates the basic system configuration of a four-processor platform.
Figure 1-1. Diagram of a Typical Intel® 460GX Chipset-based Sy stem with AGP
Interfaces the address and control portion of the Itanium™ processor
system bus and the memory bus. Acts as a host bridge interface to
peripheral I/O devices through four Expander busses.
Interfaces the data portion of the Itanium processor system bus and
the memory bus.
Provides the SDRAM RAS/CAS/WE/CS generation as well as
redriving the address to the SDRAMs. It is capable of buffering several
commands from the SAC.
Multiplexes the data from the SDRAM to the SDC. On reads, it latches
data from the SDRAM, then transfers the data to the SDC. On writes, it
latches the data from the SDC, then writes the data to the SDRAM.
Provides the control and data interface for an AGP 4X graphics port.
This device attaches to the SAC via two Expander busses which utilize
a special configuration.
Provides the primary control and data interface for two independent
64-bit, 66 MHz PCI interfaces. This device attaches to the SAC via an
Expander bus.
Provides the primary control and data interface for two independent
32-bit, 33-MHz PCI interfaces. These two 32-bit interfaces may
operate together to produce a single 64-bit, 33-MHz interface via a
configuration option. This device attaches to the SAC via an Expander
bus.
The IFB is a multi-function PCI device implementing a PCI-to-LPC
bridge function, a PCI IDE function, a Universal Serial Bus Host/Hub
function, an SMBus Interface function, Power Management function
and the Firmware Hub interface.
The FWH component interfaces to the IFB component and provides
firmware storage and security features. Further FWH information can
be found at http://developer.intel.com/design/chip sets/datasheets or by
ordering document 290658.
The PID is an interrupt controller that provides interrupt steering
functions. The PID contains the logic required to support 8259A mode,
APIC mode, and SAPIC mode interrupt controller operations. The PID
interfaces include a PCI bus interface, an APIC bus interface, a serial
IRQ interface, and an interrupt input interface.
1-2Intel® 460GX Chipset Software Develop er ’s Manual
1.2Product Features
Introduction
• High performance hardware base d on IA-64
architecture
—4.2 GB/s memory bandwidth can
simultaneously support both the full system
bus and the full I/O bus bandwidths
—Architectural support for 64 MB to 64 GB of
SDRAM
—Support for up to four bridge chips that
interface to the 82461GX (SAC) through
four Expander channels, each 30 bits wide
and providing 533 MB /s peak bandwidth
—AGP 4X compatible, via the 82465GX
(GXB) and two Expander channels running
at 266 MHz totaling 1 GB/s peak bandwidth
—Support for two 64-bit, 66-MHz PCI buses
using one 82466GX (WXB) component per
Expander channel
—Support for two independent 32-bit, 33-MHz
PCI buses or one 64-bit, 33-MHz PCI bus via
the 82467GX (PXB) pe r Expander channel
—Data streaming support between Expanders
and DRAM, up to 533 MB/s per Expander
channel
• Extensi ve RAS features for mission-critical
needs
—ECC protection on the system bus data
signals
—Memory ECC with single-bit error
correction, double and nibble error detect ion
—Address and data flows protected by parity
throughout ch ipset
—ECC bits in DRAM accessible by diagnostics
—Fault recording of multiple errors; sticky
through reset
—JT AG TAP port for debug and boundary scan
capability
—I2C slave interface for viewing and
modifying specific error and configurati on
registers
—Bus, memory and I/O performance counters
—Support of ACPI/DMI functions (support is
provided in the IFB)
• High bandwidth system bus for multiprocessor
scalability
—Support of the Intel® Itanium™ processor
64-bit dat a bus
—Full support for 4-way multiprocessing
—266 MHz data bus frequency
—Cache lin e size of 64 bytes
—Enhanced defer feature for out-of-order data
delivery using IDS#
—AGTL+ bus driver technology
• Features to support flexible platform
environments
—Hardware compatible with IA-32 binaries
—AGP address space up to 32 GB supported
—Support for Auto Detection of SDRAM
memory type and mixed memory sizes
allowed between r ows
—Supports 16-, 64- , 128- and 256-Mbit
DRAM devices
—Full support for the PCI Configuration Space
Enable (CSE) protocol to devices on all
Expander channels
—WXB supports 3.3 volt PCI bus operation
(supports universal and 3.3 volt PCI cards)
and has an Integrated Hot-Plug Controller**
—PCI Rev. 2.2 compliant on the WXB and
PXB
—GXB supports fast write s a nd 1x, 2x and 4x
data rates
—1 MB or greater of firmware storage
provided by the 8280 2 AC ( FWH)
—Interrupt controller, bus-mastering IDE and
Universal Serial Bus supported by the
82468GX (IFB)
—Support of 8259 A mod e , APIC mo d e an d
SAPIC mode interru pts via the
UPD55566S1-016 (PI D ) provided by NEC*
**Based on technology licensed from Compaq Computer Corp.
1.3Itanium™ Processor System Bus Support
• Full support for the Itanium processor system bus.
— 64-bit data bus.
— 266 MHz data bus frequency.
— Cache line size of 64 bytes.
— Supports SAPIC interrupt protocol.
• Full support for 4-way multiprocessing.
• Parity protection on address and control signals, ECC protection on the data signals.
• ECC with single-bit error correction, double and nibble error detection.
• Extensive processor-to-Memory and PCI-to-Memory write data buffering, thus minimizing
the interference of writes on read latency.
1.5I/O Support
• 4 Expander ports, each 30 bits wide and providing 533 MB/s peak bandwidth.
• Each Expander bus supports a single PXB or WXB. Two Expander busses can be configured
to support a GXB.
• Full support for the PCI Configuration Space Enable (CSE) protocol to devices on all
Expander ports.
• Data streaming support between Expanders and DRAM, up to 533 MB/s per Expander port.
• All outbound memory and I/O reads (except locked reads) are deferred.
• All outbound memory space writes are posted. Outbound I/O space writes are optionally
posted (unless targeting an address with side effects, in which case they are deferred).
• All inbound memory reads are delayed.
• All inbound memory space writes are posted.
• Supports concurrent processor and I/O initiated transactions to main memory.
• Maintains coherency with processors by snooping all inbound transactions to the system bus.
• Supports non-coherent traffic (for AGP), with a direct path to memory bypassing the system
bus.
1.5.1PXB Features
• Can be configured to provide two independent 32 bit, 33 MHz PCI buses or one 64 bit, 33
MHz PCI bus.
• PCI Rev. 2.2, 5V tolerant (PXB drives 3.3 volts, but is 5.0 volt tolerant).
1-4Intel® 460GX Chipset Software Develop er ’s Manual
• Parity protection on all PCI signals.
• Data collection & write assembly.
— Combines back-to-back sequential processor-to-PCI memory writes to PCI burst writes.
— Processor to PCI write assembly of full/partial line writes.
• T wo outbo und read requ ests containing a total of two cach e lines of read data fo r each PCI bus.
• Supports six outbound write requests containing a total of three cache lines of write data for
each 32 bit PCI bus. Supports 12 outbound write requests containing a total of six cache lines
of write data for a 64 bit PCI bus.
• Supports two delayed inbound read requests.
• Supports the I/O and Firmware Bridge (IFB).
• Supports either internal or external arbitration, allowing additional bus masters, on the PCI
bus.
1.5.2WXB Features
• Support for two 64 bit, 66 MHz PCI busses.
Introduction
• 3.3 Volt PCI bus operation (supports Universal and 3.3 Volt PCI cards).
• PCI Specification, Revision 2.2.
• Integrated Hot-Plug controller.
1.5.3GXB Features
• The GXB is AGP and AGP 4X mode compatible, nominal 66 MHz, 266 MHz, 1 GB/s peak
bandwidth.
• The GXB supports pipelined operation or sideband signals on AGP 4X mode bus.
• AGP address space of 1 GB or 256 MB supported. Also supports 32 GB of GART window, if
4 MB pages are used.
• Supports Fast Writes and 1x, 2x and 4x data rates.
1.6RAS Features
• ECC coverage of system data bus using the Itanium™ processor SEC/DED ECC code.
Memory is protected using a SEC/DED code which also provides nibble detection capabilities
of 4 bits. All control and address signals are parity protected. Local control buses are parity
protected. The Expander is covered by parity.
• Data flows protected by parity throughout chipset.
• ECC bits in DRAM accessible by diagnostics.
• Fault recording of multiple errors; sticky through reset, but NOT through power-down.
• I2C Slave Interface will allow viewing and modifying of specific error and configuration
registers.
1.7Other Platform Components
These 460GX devices provide access to flash space, interrupt collection and legacy features.
1.7.1I/O & Firmware Bridge (IFB)
The 460GX chipset is designed to work with the IFB south bridge. As part of this support, the PXB
includes an internal PCI arbiter as well as support for an external PCI arbiter. The IFB consists of
an 8259C Interrupt controller, a bus-mastering IDE interface, and a Universal Serial Bus interface.
Devices using IFB are limited to a 32 bit addressing space available for DMA, not the full 44 bits
supported by the Itanium™ processor.
1.7.2Programmable Interrupt Device (PID)
The PID is a PCI device that gathers interrupts and delivers them from the PCI bus to the system
bus using the SAPIC inte rr upt p rotocol. The interrupt will be presen te d t o o ne o f the p roces s ors on
the bus for servicing. A 460GX chipset based platform requires at least one PID located on the
compatibility PCI bus. The compatibility PID will hands hake with the IFB befo re delivering a
south bridge/compatibility device interrupt. The same PID may als o be used to deliver some
portion of the PCI based interrupts.
The system implementor can choose how many PIDs are used in the platform. If enough interrupt
lines are shared, there need be only one PID in the system; all interrupts in the system would then
be routed to that PID. Each P ID has en ough i nte rrupt i nputs to handl e dedicated interr upts fr om the
cards on two PCI buses. Therefore, using one PID per PXB provides a high performance solution
with minimum routing between PCI buses.
1.8Reference Documents
In addition to this document, the reader should be familiar with the following reference do cuments:
1-8Intel® 460GX Chipset Software Develop er ’s Manual
Register Descriptions2
The 460GX chipset has both memory mapped and PCI configuration space mapped registers. The
460GX chipset supports access mechanism #1 as defined in the PCI specification. Two 32-bit
register locations (CONFIG_ADDRESS and CONFIG_DATA) are defined in the Itanium
processor’s I/O space; I/O accesses to these registers are translated by the 460GX chipset into
appropriate PCI configuration cycles.
To access a configuration register in the 460GX chipset (or any other I/O device), software first
writes a value to the CONFIG_ADDRESS location consisting of the bus number, Device Number,
function number and register number. These writes are claimed and saved by the 460GX chipset.
Subsequent reads or writes to the CONFIG_DATA location result in the 460GX chipset using the
information stored in CONFIG_ADDRESS to deliver a PCI configuration read or write cycle to
the appropriate address on the appropriate PCI bus.
Upon reset, the 460GX chipset sets its internal configuration regist ers to predetermined default
states, representing the minimum feature set required to successfully bring up the system. It is
expected that the firmware will properly determine and program the optimal configuration settings.
The 460GX chipset implements a PCI-compatible configuration space for each PCI bus under the
PXBs, for each AGP bus under the GXB, and for each 460GX chipset component. Each
configuration space provides hardwired device identification, address range registers, operation
control registers, status and error regis ters. This chap ter describe s how the con figuration sp aces are
accessed, then provides detailed descriptions of each register.
2.1Access Mechanism
The PCI specification defines two bus cycles to access PCI configuration space: Configuration
Read and Configuration W rite. While memory and I/O spaces are supp orted by the micro processor ,
configuration space is not directly supported. The PCI specification defines two mechanisms to
access configuration space, Mechanism #1 and Mechanism #2. The 460GX chipset supports only
Mechanism #1.
Mechanism #1 defines two I/O-space locations: an address register (CONFIG_ADDRESS) at
location 0CF8h, and a data register (CONFIG_DATA) at location 0CFCh. Dword I/O W rites to the
configuration address are latched and held; they specify the PCI Bus Number, Device Number
within the bus, and Register Number within the device. Subsequent I/O reads and writes to the
configuration data location cause a configuration space access th e register specified by the add ress
stored in the configuration address location.
Note:The AGP bus under the GXB looks like a standard PCI bus for configuration purposes. The term
xXB refers to the PXB, WXB, or GXB. In general, any reference to an access to PCI bus includes
accesses to an AGP bus.
Configuration space accesses are processed as follows:
• If the SAC detects that the I/O request is a configuration acces s to its own con figuration space,
it will service that request entirely within the SAC or the other chipset comp onents. Reads
result in data being returned to the system bus.
• If the SAC detects that the I/O request is a configuration access to a xXB configuration space,
it will forward the request to the appropriate xXB for servicing. The request is not f orwar ded
to a PCI bus. Reads result in data being returned by the xXB through the SAC to the system
bus.
• Otherwise, the access is forwarded to the xXB to be placed on the PCI bus (or AGP bus) as a
Configuration Read or Configuration Write cycle. Reads will result in data being returned
through the xXB and SAC back to the system bus, just as in normal Outbound Read
operations.
2.2Access Restrictions
The 460GX chipset supports PCI configuration space access using the mechanism denoted as
Configuration Mechanism #1 in the PCI specification.
The 460GX chipset internal registers (both I/O Mapped and Configu ration registers) ar e accessible
by the Host CPU. The registers can be accessed as Byte, Word (16-bit), or Dword (32-bit)
quantities, with the exception of CONFIG_ADDRESS which can only be accessed as a Dword. All
multi-byte numeric fields use “little-endian” ordering (i.e. lower addresses contain the least
significant parts of the field).
2.2.1Partitioning
Each SAC, SDC, MAC, PXB, WXB, GXB, each AGP bus below an GXB, and each PCI bus below
an PXB or WXB, has an independent configuration space. None of the regis ters are shared between
the spaces; that is, the SAC, and each PCI bus in the PXB, have separate control and status
registers.
Configuration registers are accessed using an “address” comprised of the PCI Bus Number, the
Device Number within the bus, and the Register Number within the Device.
Accesses to devices on Bus #0 and Bus #(CBN) are serviced by the 460GX chipset depending on
their device number. Device 10h on Bus #0 is mapped to the SAC; it contains the programmable
Chipset Bus Number. All other chipset devices reside on bus CBN.
The DEVNPRES register is used to determine which chipset devices are present; see Table 2-1 for
mapping information.
Table 2-1. Device Mapping on Bus CBN
No.DeviceNo.Device
00hSAC10hExpander 0, Bus a
01hSAC11hExpander 0, Bus b
02hreserved12hExpander 1, Bus a
03hreserved13hExpander 1, Bus b
04hSDC14hExpander 2, Bus a
05hMemory Card A15hExpander 2, Bus b
06hMemory Card B16hExpander 3, Bus a
07hreserved17hExpander 3, Bus b
08h-0Fhreserved18h-1Fhreserved
a. This is the compatibility bus (where the boot vector is always directed).
a
Configuration registers located in the SDC are accessed over the private data bus. The SAC
translates CF8/CFC accesses to SDC registers into configuration commands over the PDB.
Configuration registers located on the memory boards are accessed over the I2C port. The SAC
2-2Intel® 460GX Chipset Software Develop er ’s Manual
translates CF8/CFC accesses to the MAC registers into read/write commands over the I2C port.
The SAC also contains an IIADR pointer register that can be used in conjunction with a CF8/CFC
access to generate I2C commands to generic I2C devices on the memory boards.
2.2.2Register Attributes
Registers have designated “access attributes”, with the following definitions:
Read OnlyWrites to this register have no effect.
Read/WriteData may be read from and written to this register. Selected bits in the register may
be designated as “hardwired” or “read-only”; such bits are not affected by data writes
to the register.
Read/ClearData may be read from the register. A data write operates strictly as a clear: a “1”-bit
in the data field clears the corresponding bit in the register , while a “0”-bit in the data
field has no effect on the corresponding bit in the register . Selected bits in the register
may be designated as “hardwired” or “read-only”; such bits are not af fected by data
writes to the register.
StickyData in this register remains valid and unchanged, du ring and following a hard reset.
Typically, these registers contain special configuration information or error logs.
Register Descriptions
2.2.3Reserved Bits Defined in Registers
Most 460GX chipset registers described in this s ection contain r eserved bits. Th e PCI specifica tion
requires that software correctly handle reserved fields, as follows. On reads, software must use
appropriate masks to extract the defined bits and not rely on reserved bits being any particular
value. On writes, software must ensure that the values of reserved bit pos itions are p rese rved. That
is, the values of reserved bit positions must first be read, merged with the new values for other bit
positions and then written back. Note the software does not need to perform read, merge, write
operation for the CONFIG_ADDRESS register.
2.2.4Reserved or Undefined Register Locations
In addition to reserved bits within a register, the 460GX chipset contains address locations in the
PCI configuration space that are marked “Reserved” or are simply undefined. Several of the
460GX chipset devices are multi-function devices; all registers in the unused functions are
considered “Reserved”. Reserved registers can be 8-, 16-, or 32-bit in size. The PCI specification
requires that the 460GX chipset respond to accesses to these address locations by completing the
host cycle. Reserved register locations must be treated by software the same as reserved fields are
treated: software can not rely on reads returning any particular value, and must not attempt to
change the value returned when read.
2.2.5Default Upon Reset
Upon reset, the 460GX chipset sets its internal configuration registers to pr edeterm in e d default
states. The default state represents the minimum functionality feature set required to successfully
bring up the system. Hence, it does not represent the optimal system configuration. It is the
responsibility of the system initialization software (firmware) to properly deter m ine the DRAM
configurations, operating parameters and optional system features that are applicable, and to
program the 460GX chipset registers accordingly.
There are a number of registers that are repeated in both the SAC and xXB/PCI spaces. It is
software’s responsibility to insure that these regis ters are progr a mmed in a consistent fashion.
Failure to insure consistency can produce indeterminate resu lts. See the Initialization Chapter for
an overview on initializing all chipset components.
When the address decode ranges of 460GX chipset devices are being updated, no other bus traffic
is allowed over the address ranges being affected by the update. This means that the code that
updates initial configuration must be executing from a location that will not be affected by the
update. Furthermore in a multiprocessor system, precautions should be taken to assure that only
one CPU is accessing configuration space at a time.
2.2.7GART Programming Region
The region starting at FE20_0000h is used for programming the GARTs. This region is accessible
either by the processor or PCI. See Section 7.2.1 for GART programming details
2.3I/O Mapped Registers
The 460GX chipset contains two registers that reside in the CPU I/O address space: the
Configuration Address (CONFIG_ADDRESS) Register and the Configuration Data
(CONFIG_DATA) Register. The Configuration Address Register enables/disables the
configuration space and determines what portion of configuration space is visible through the
Configuration Data window. The following sections define the fields within the
CONFIG_ADDRESS and CONFIG_DATA registers. The 460GX chipset’s device ID mapping
into the CONFIG_ADDRESS definition is shown in Table 2-1.
CONFIG_ADDRESS is a 32 bit register accessed only when referenced as a Dword. A Byte or
Word reference will “pass through” the Configuration Add ress R egi st er ont o t h e PC I b us as an I/ O
cycle. The CONFIG_ADDRESS register contains the Bus Number, Device Number, Function
Number, and Register Number for which a subsequent configuration access is intended.
Bits
31Configuration Enable(CFGE).
30:24reserved (0)
23:16Bus Number.
Description
When this bit is set to 1 accesses to PCI configuration space are enabled. If this bit is reset
to 0 accesses to PCI configuration space are disabled.
When the Bus Number is programmed to match the Chipset Bus Numb er (CBN), the
target of the Configuration Cycle is the 460GX chipset. If the Bus Number is not CBN,
the destination and type of acce ss is determined by the Bus Numb er and Subordinate Bus
Number of each PCI port in each PXB. A type 0 access is generated on the appropriate
PCI bus if one of the PXB port’s bus number is matched. Otherwise, a type 1
configuration cycle is generated on the appropriate PCI bus below the PXB port whose
2-4Intel® 460GX Chipset Software Develop er ’s Manual
subordinate bus number is in that range. For a type 1 cycle, the Bus Number is mapped
to AD[23:16] during the address phase.
15:11Device Number.
This field selects one agent on the PCI bus selected by the Bus Number. Device 16 (10h)
on Bus #0 is always reserved for programming the CBN. On the bus that the chipset is
mapped into (determined by the CBN register), Device Numbers 0-31 are reserved for
the 460GX chipset components as shown in Table 2-1. All other devices numbers are
forwarded to the selected bus.
1 0:8Function Number.
This field is mapped to AD[10:8] during PCI configuration cycles. This allows the
configuration registers of a particular function in a multi-function device to be accessed.
7:2Register Number.
This field selects one register within a particular Bus, Device, and Function as sp ecified
by the other fields in the Confi guration Address Register . This fi eld is mapped to AD[7:2]
during PCI configuration cycles.
1:0reserved (0)
2.3.2CONFIG_DATA: Configuration Data Register
I/O Address:CFChSize:32 bit s
Default Value:00000000h Attribute:Read/Write
Sticky:NoLocked:No
Register Descriptions
CONFIG_DATA is a 32 bit read/write window into configuration space. The portion of
configuration space that is referenced by CONFIG_DATA is determined by the contents of
CONFIG_ADDRESS.
Bits
31:0Configuration Data Window (CDW).
Description
If bit 31 of CONFIG_ADDRESS is 1 any I/O reference that falls in the CONFIG_DATA
I/O space will be mapped to configuration space using the contents of
CONFIG_ADDRESS.
Sticky:YesLocked:No
This register is used to capture the ITID for a single bit memory ECC error. The ITID can then be
used to determine the address of the failure. To force the ITID to be cleared and re-used, write a 1
to bit 6. This register is set anytime that the SEC bit is sent from the SDC to the SAC on a ’Retire
ITID’ command.
This bit can be written by software. When set, the ITID is retired immediately and not
captured. Therefore there can be no checking of the address. See Section 6 for the usage
of this bit.
6Valid
If set then the ITID in bits 5:0 is valid and shows the address of a single-bit memory error.
Writing a 1 to this bit will clear the ITID and reset the valid bit.
5:0ITID
The ITID of the SEC error. These bits are read-only.
This register is used to capture the ITID for a double bit memory ECC error. The ITID can then be
used to determine the address of the failure. To force the ITID to be cleared and re-used, write a 1
to bit 6. This register is set anytime that the DED bit is sent from the SDC to the SAC on a ‘Retire
ITID’ command.
Bits
7Disable
6Valid
5:0ITID
Description
This bit can be written by software. When set, the ITID is retired immediately and not
captured. Therefore there can be no checking of the address. See Section 6 for the usage
of this bit.
If set then the ITID in bits 5:0 is valid and shows the address of a double-bit memory
error. Writing a 1 to this bit will clear the ITID and reset the valid bit.
The ITID of the double-bit error. These bits are read-only.
This register is used to capture the ITID for a system bus data error. The ITID can then be used to
determine the address of the failure. To force the ITID to be cleared and re-used, write a 1 to bit 6.
This register is set anytime that the ADE bit is asserted and both SEC and DED are deasserted on a
’Retire ITID’ command from the SDC to the SAC. NOTE: this reg ister is set for both processorbus errors and errors on the SAC-to-SDC data bus.
2-6Intel® 460GX Chipset Software Develop er ’s Manual
BitsDescription
7Disable
This bit can be written by software. When set, the ITID is retired immediately and not
captured. Therefore there can be no checking of the address. See Section 6 for the usage
of this bit.
6Valid
If set then the ITID in bits 5:0 is valid and shows the address of a system bus data error.
Writing a 1 to this bit will clear the ITID and reset the valid bit.
5:0ITID
The ITID of the system bus error. These bits are read-only.
This register records the first error condition detected in the SAC/SDC.
Register Descriptions
Bits
31Memory Card B Error (MBE)
30Memory Card A Error (MAE)
29XSERR# Asserted (XSA)
28‘Store-Write’ Command Underflow, card A, Stack L (SCAL)
27‘Store-Write’ Command Underflow, card A, Stack R (SCAR)
26‘Store-Write’ Command Underflow, card B, Stack L (SCBL)
25‘Store-Write’ Command Underflow, card B, Stack R (SCBR)
24SDC Correctable Memory Error (SCME)
23SDC Non-Fatal Error (SNE)
22SDC Fatal Error (SFE)
21‘Completion’ Command Underflow; MAC A, Stack L (CCAL)
20‘Completion’ Command Underflow; MAC A, Stack R (CCAR)
19‘Completion’ Command Underflow; MAC B, Stack L (CCBL)
Description
Set when the memory card B signals a fatal error.
Set when the memory card A signals a fatal error.
Set when the SAC sees the signal XSERR# active.
One of these 4 is asserted when a signal is sent from the SDC to the SAC indicating write
data was sent to the MDC, and there is no outstanding write in the SAC.
Reports correctable DRAM errors (single-bit ECC errors). This bit does not mask other
bits in the FERR register from being set. It is the one exception to the rule that only one
bit in FERR may be set at a time.
Reports non-fatal errors that are uncorrectable such as double-bit ECC error, or parity
errors. This also reports a single-bit correctable error on the system bus. This bit will also
be set if there is a second cor rectable error from memo ry in the SDC, and the first one has
not been cleared by the time the second one occurs. The first correctable memory error
would have set the SCME bit, and all later correctable memory errors (until the SDC’s
error registers are cleared) are reported as SNE in the FERR or NERR.
One of these 4 bits is set when the SAC receives a completion from the MAC and the
SAC has no outstanding transaction.
BERR# seen on the system bus. Set whenever BERR# is observed active.
Set when the IOQ is empty and the SDC sends out a signal saying it popped something
from the top of the queu e. Or set when the I OQ is 8 (or 1 when the IOQ d epth is s et to 1)
and an ADS# is seen on the bus.
Set when XBINIT# is seen active. This signal is from an Expander port or other external
agent.
Retirement from SDC that doesn’t match an outstanding ITID in the SAC.
Asserted when an address on the system bus is above TOM and not inside the I/O gap
below 4 GB.
HITM# on non-memory access.
Processor access to an address above 64 GB, so that ASZ# = 10b or 11b.
Parity error on A[36:3]#.
Parity error on REQ[4:0]#.
Parity error on the ITID bus from SDC to SAC.
Parity error on the retirement bus from the SDC to the SAC.
Set when a LOCK# transaction occurs and there are no outbound resources available in
which to place the lock.
Set if the resource counter has an underflow or overflow.
A write to this register causes the SAC to update the BIUDATA register with the contents of the
CAM and RAM associated with the ITID that is written into this register.
This is the ITID that is used to address the CAM/RAM structure.
Register Descriptions
2.4.1.8BIUDATA: BI U D ata Register
Bus CBN, Device Number: 00hFunction:1
Address Offset:90hSize:128 bits
Default Value:undefinedAttribute:Read Only
Sticky:NoLocked:No
This is the contents of the CAM concatenated with the contents of the RAM associated with the
ITID in BIUITID.
Bits
127:116 reserved(0)
115:82Address bits [35:2].
81:76reserved(0)
75:71Reqa. Request phase a[4:0].
70:63DID. The DID for the transaction.
62:55BE. The byte enables for the transaction.
54rese rve d (0)
53OWN. OWN# active.
52DPS. DPS# active.
51:49Reqb. Request phase b bits [4:2].
48Lock. The transaction.had LOCK# asserted.
47LockLoad. The transaction is the first occurrence of an OB lock sequence.
46:43Dst. The destination of the transaction.
42ORetry. A retry due to HITO.
41:36CMD. The command for the transaction.
35P2P. Set for peer-to-peer transactions.
34FEorR. The end-of-request bit from the Expander port.
33:30FRoute. The Expander bus route.
29:22FLEN. The length on the Expander bus.
21:12FTID. The Expander id.
11:9Len. The length of the transaction.
8System Bus Retry. The transaction was retried on the bus.
7Dfr. The transaction is deferred.
6MEM. The target for the transaction if memory.
5System Bus. The target for the transaction is the system bus.
4CLINE. The transaction is for a full line.
3Zero. If set then this is a 0-length transaction.
2:0RS. The Response generated for the transaction by the BIU. This may not match the
Description
This is the contents of the CAM with address bits [5:2] from the RAM (bit 2 is only of
interest if the transaction came from an Expander bus).
system bus response sent, since the BIU’s response may be changed by the MIU. This
may be for a HITM# or other reasons.
Note: Note: if the P2P bit is not set, then bits [34:12] and [76] are not defined, since the transaction
originated on the system bus and not the Expander bus.
2-10Intel® 460GX Chipset Software Develop er ’s Manual
Loading...
+ 264 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.