Intel 955X Express Chipset: Datasheet
Intel 955X Express Chipset: Datasheet
April 2005
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® 82955X Memory Controller Hub (MCH) 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.
1
Hyper-Threading Technology requires a computer system with an Intel® Pentium® 4 processor supporting HT Technology and a Hyper-Threading
Technology enabled chipset, BIOS and operating system. Performance will vary depending on the specific hardware and software you use. See
http://www.intel.com/info/hyperthreading/ for more information including details on which processors support HT Technology.
Intel and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
*Other names and brands may be claimed as the property of others.
Copyright© 2005, Intel Corporation
Contents
1 Introduction ....................................................................................................................... 15
1.1 Terminology.......................................................................................................... 17
1.2 Reference Documents.......................................................................................... 18
1.3 MCH Overview ..................................................................................................... 19
1.3.1 Host Interface........................................................................................ 19
1.3.2 System Memory Interface..................................................................... 20
1.3.3 PCI Express* Graphics Interface .......................................................... 21
1.3.4 Direct Media Interface (DMI)................................................................. 22
1.3.5 System Interrupts.................................................................................. 22
1.3.6 MCH Clocking ....................................................................................... 23
1.3.7 Power Management.............................................................................. 23
2 Signal Description ............................................................................................................. 25
2.1 Host Interface Signals .......................................................................................... 27
2.2 DDR2 DRAM Channel A Interface ....................................................................... 30
2.3 DDR2 DRAM Channel B Interface ....................................................................... 31
2.4 DDR2 DRAM Reference and Compensation....................................................... 32
2.5 PCI Express* Interface Signals ............................................................................ 32
2.6 Clocks, Reset, and Miscellaneous ....................................................................... 33
2.7 Direct Media Interface (DMI) ................................................................................ 33
2.8 Power, Ground ..................................................................................................... 34
2.9 Reset States and Pull-up/Pull-downs................................................................... 34
3 MCH Register Description ................................................................................................ 39
3.1 Register Terminology ........................................................................................... 40
3.2 Platform Configuration.......................................................................................... 41
3.3 Configuration Mechanisms................................................................................... 44
3.3.1 Standard PCI Configuration Mechanism .............................................. 44
3.3.2 PCI Express* Enhanced Configuration Mechanism ............................. 44
3.4 Routing Configuration Accesses .......................................................................... 46
3.4.1 Internal Device Configuration Accesses............................................... 47
3.4.2 Bridge Related Configuration Accesses ............................................... 47
3.4.2.1 PCI Express* Configuration Accesses ................................ 47
3.4.2.2 DMI Configuration Accesses ............................................... 48
3.5 I/O Mapped Registers .......................................................................................... 48
3.5.1 CONFIG_ADDRESS—Configuration Address Register ...................... 48
3.5.2 CONFIG_DATA—Configuration Data Register .................................... 50
4 Host Bridge Registers (D0:F0).......................................................................................... 51
4.1 Configuration Register Details (D1:F0) ................................................................ 53
4.1.1 VID—Vendor Identification (D0:F0) ...................................................... 53
4.1.2 DID—Device Identification (D0:F0) ...................................................... 53
Figures
Figure 1-1. Intel® 955X Express Chipset System Block Diagram Example ..................... 16
Figure 2-1. Signal Information Diagram ............................................................................ 26
Figure 3-1. Conceptual Intel® 955X Express Chipset Platform PCI Configuration Diagram42
Figure 3-2. Register Organization..................................................................................... 43
Figure 3-3. Memory Map to PCI Express* Device Configuration Space .......................... 45
Figure 3-4. MCH Configuration Cycle Flow Chart ............................................................ 46
Figure 4-1. Link Declaration Topology.............................................................................. 98
Figure 7-1. System Address Ranges .............................................................................. 172
Figure 7-2. Microsoft MS-DOS* Legacy Address Range ............................................... 173
Figure 7-3. Main Memory Address Range...................................................................... 177
Figure 7-4. PCI Memory Address Range........................................................................ 179
Figure 8-1. System Memory Styles................................................................................. 190
Figure 8-2. Platform Clocking Example .......................................................................... 197
Figure 10-1. Intel® 82955X MCH Ballout Diagram (Top View – Columns 43–30).......... 208
Figure 10-2. Intel® 82955X MCH Ballout Diagram (Top View – Columns 29–16).......... 209
Figure 10-3. Intel® 82955X MCH Ballout Diagram (Top View – Columns 15–1)............ 210
Figure 10-4. MCH Package Dimensions (Top View)...................................................... 223
Figure 10-5. MCH Package Dimensions (Side View)..................................................... 223
Figure 10-6. MCH Package Dimensions (Bottom View)................................................. 224
Figure 11-1. XOR Test Mode Initialization Cycles .......................................................... 226
Tables
Table 4-1. Host Bridge Register Address Map (D0:F0).................................................... 51
Table 4-2. MCHBAR Register Address Map .................................................................... 83
Table 4-3. Egress Port Register Address Map ................................................................. 98
Table 5-1. Host-PCI Express* Graphics Bridge Register Address Map (D1:F0) ........... 103
Table 6-1. DMI Register Address Map ........................................................................... 159
Table 7-1. Expansion Area Memory Segments .............................................................. 175
Table 7-2. Extended System BIOS Area Memory Segments ......................................... 175
Table 7-3. System BIOS Area Memory Segments ......................................................... 175
Table 7-4. Pre-Allocated Memory Example for 64-MB DRAM, 1-MB VGA and 1-MB
TSEG ....................................................................................................................... 178
Table 7-5. SMM Space ................................................................................................... 184
Table 7-6. SMM Control .................................................................................................. 185
Table 8-1. Sample System Memory Organization with Interleaved Channels ............... 189
Table 8-2. Sample System Memory Organization with Asymmetric Channels .............. 189
Table 8-3. DDR2 DIMM Supported Configurations ........................................................ 192
Table 8-4. DRAM Address Translation (Single Channel/Dual Asymmetric Mode) ........ 193
Table 8-5. DRAM Address Translation (Dual Channel Symmetric Mode) ..................... 193
Table 9-1. Absolute Minimum and Maximum Ratings .................................................... 200
Table 9-2. Non Memory Power Characteristics .............................................................. 201
Table 9-3. DDR2 Power Characteristics......................................................................... 201
Table 9-4. Signal Groups ................................................................................................ 202
Table 9-5. DC Characteristics......................................................................................... 204
Table 10-1. Intel® 82955X MCH Ballout – Sorted by Signal Name ................................ 211
Table 11-1. Complimentary Pins to Drive ....................................................................... 225
Table 11-2. XOR Chain Outputs ..................................................................................... 227
Table 11-3. XOR Chain 0............................................................................................... 228
Table 11-4. XOR Chain 1............................................................................................... 229
Table 11-5. XOR Chain 2............................................................................................... 230
Table 11-6. XOR Chain 3............................................................................................... 230
Table 11-7. XOR Chain 4............................................................................................... 231
Table 11-8. XOR Chain 5............................................................................................... 232
Table 11-9. XOR Chain 6............................................................................................... 233
Table 11-10. XOR Chain 7............................................................................................. 233
Table 11-11. XOR Chain 8............................................................................................. 234
Table 11-12. XOR Chain 9............................................................................................. 235
Table 11-13. XOR Pad Exclusion List............................................................................. 236
Revision History
1 Introduction
The Intel® 955X Express chipset is designed for use with Intel® Pentium® 4 processor in the
90 nm process in the LGA775 Land Grid Array package, Intel® Pentium® D processor, and Intel®
Pentium® processor Extreme Edition based platforms. The chipset contains two components:
82955X Memory Controller Hub (MCH) for the host bridge and I/O Controller Hub 7 (ICH7) for
the I/O subsystem. The MCH provides the interface to the processor, main memory, PCI
Express*, and the ICH7. The ICH7 is the seventh generation I/O Controller Hub and provides a
multitude of I/O related functions. Figure 1-1 shows an example system block diagram for the
955X Express chipset.
This document is the datasheet for the Intel® 82955X MCH. Topics covered include; signal
description, system memory map, register descriptions, a description of the MCH interfaces and
major functional units, electrical characteristics, ballout definitions, and package characteristics.
Note: Unless otherwise specified, ICH7 refers to the Intel® 82801GB ICH7 and 82801GR ICH7R I/O
Controller Hub components.
Figure 1-1. Intel® 955X Express Chipset System Block Diagram Example
Processor
System Memory
DDR2
Channel A
PCI Express*
Intel® 82955X MCH DDR2
Graphics x16 Graphics
Display
Card
Channel B DDR2
DDR2
DMI Interface
USB* 2.0
8 ports, 480 Mb/s
Power Management
IDE
Clock Generation
LPC Interface
Other ASICs
(Optional)
Super I/O
TPM
(Optional)
Flash BIOS
Sys_Blk_955X
1.1 Terminology
Term Description
Accelerated Refers to the AGP/PCI interface that was previously in the MCH components. This port
Graphics Port is not on the 82955X MCH; It has been replaced by PCI Express*.
(AGP)
DMI Direct Media Interface. This is the interface between the MCH and ICH7.
FSB Front Side Bus. This term is synonymous with Host bus or processor bus
Full Reset Full reset is when PWROK is de-asserted. Warm reset is when both RSTIN# and
PWROK are asserted.
INTx An interrupt request signal where X stands for interrupts A,B,C, and D
®
Intel ICH7 Seventh generation I/O Controller Hub component that contains additional functionality
compared to previous ICH components. The I/O Controller Hub component that
contains the primary PCI interface, LPC interface, USB2, ATA-100, and other I/O
functions. It communicates with the MCH over a proprietary interconnect called DMI.
MCH 82955X Memory Controller Hub component that contains the processor interface,
DRAM controller, and x16 PCI Express port (typically the external graphics interface). It
®
communicates with the I/O controller hub (Intel ICH7*) and other I/O controller hubs
over the DMI interconnect.
MSI Message Signaled Interrupt. A transaction initiated outside the host, conveying interrupt
information to the receiving agent through the same path that normally carries read and
write commands.
PCI Express* Third generation input/output graphics attach called PCI Express Graphics. It is a high-
speed serial interface whose configuration is software compatible with the existing PCI
specifications. The specific PCI Express implementation intended for connecting the
MCH to an external Graphics Controller is a x16 link and replaces AGP.
Primary PCI The physical PCI bus that is driven directly by the ICH7 component. Communication
between Primary PCI and the MCH occurs over DMI. Note that the Primary PCI bus is
not PCI Bus 0 from a configuration standpoint.
® ®
Processor Refers to the Intel Pentium 4 processor in the 90 nm process in the LGA775 Land
® ® ®
Grid Array package, Intel Pentium D processor, and Intel Pentium processor
Extreme Edition.
Term Description
SERR System Error. An indication that an unrecoverable error has occurred on an I/O bus.
SMI System Management Interrupt. SMI is used to indicate any of several system conditions
such as thermal sensor events, throttling activated, access to System Management
RAM, chassis open, or other system state related activity.
Rank A unit of DRAM corresponding to eight x8 SDRAM devices in parallel or four x16
SDRAM devices in parallel, ignoring ECC. These devices are usually, but not always,
mounted on a single side of a DIMM.
TOLM Top Of Low Memory. The highest address below 4 GB for which a processor-initiated
memory read or write transaction will create a corresponding cycle to DRAM on the
memory interface.
The MCH supports one or two channels of DDR2 SDRAM. It also supports PCI Express based
external graphics attach. To increase system performance, the MCH incorporates several queues
and a write cache. The MCH also contains advanced power management logic.
The MCH supports 36-bit host addressing, decoding up to 8 GB of the processor’s usable
memory address space. Host-initiated I/O cycles are decoded to PCI Express, DMI, or the MCH
configuration space. Host-initiated memory cycles are decoded to PCI Express, DMI or main
memory. PCI Express device accesses to non-cacheable system memory are not snooped on the
host bus. Memory accesses initiated from PCI Express using PCI semantics and from DMI to
system SDRAM will be snooped on the host bus.
To provide for true isochronous transfers and configurable Quality of Service (QoS) transactions,
the ICH7 supports two virtual channels on DMI: VC0 and VC1. These two channels provide a
fixed arbitration scheme where VC1 is always the highest priority. VC0 is the default conduit of
traffic for DMI and is always enabled. VC1 must be specifically enabled and configured at both
ends of the DMI link (i.e., the Intel ICH7 and MCH). Configuration registers for DMI, virtual
channel support, and DMI active state power management (ASPM) are in the RCRB space in the
MCH Register Description. Features of the DMI include:
• A chip-to-chip connection interface to Intel ICH7.
• 2 GB/s point-to-point DMI to ICH7 (1 GB/s each direction).
• 100 MHz reference clock (shared with PCI Express graphics attach).
• 32-bit downstream addressing.
• APIC and MSI interrupt messaging support. MCH will send Intel-defined “End Of Interrupt”
broadcast message when initiated by the processor.
• Message Signaled Interrupt (MSI) messages.
• SMI, SCI, and SERR error indication.
• Legacy support for ISA regime protocol (PHOLD/PHOLDA) required for parallel port
DMA, floppy drive, and LPC bus masters.
The internal and external memory clocks of 266 MHz and 333 MHz are generated from one of
two MCH PLLs that use the Host clock as a reference. Also included are 2x and 4x clocks for
internal optimizations.
The PCI Express core clock of 250 MHz is generated from a separate PCI Express PLL. This
clock uses the fixed 100 MHz serial reference clock (GCLKP/GCLKN) for reference.
All of the above mentioned clocks are capable of tolerating Spread Spectrum clocking as defined
in the Clock Generator specification. Host, Memory, and PCI Express PLLs, and all associated
internal clocks are disabled until PWROK is asserted.
2 Signal Description
This section provides a detailed description of MCH signals. The signals are arranged in
functional groups according to their associated interface.
PCIE PCI Express interface signals. These signals are compatible with PCI Express
1.0 Signaling Environment AC Specifications and are AC coupled. The buffers
are not 3.3 V tolerant. Differential voltage spec = (|D+ – D-|) * 2 = 1.2 Vmax.
Single-ended maximum = 1.5 V. Single-ended minimum = 0 V.
DMI Direct Media Interface signals. These signals are compatible with PCI Express
1.0 Signaling Environment AC Specifications, but are DC coupled. The buffers
are not 3.3 V tolerant. Differential voltage spec = (|D+ – D-|) * 2 = 1.2 Vmax.
Single-ended maximum = 1.5 V. Single-ended minimum = 0 V.
HCSL Host Clock Signal Level buffers. Current mode differential pair. Differential
typical swing = (|D+ - D-|) * 2 = 1.4 V. Single ended input tolerant from
-0.35 V to 1.2 V. Typical crossing voltage 0.35 V.
SSTL-1.8 Stub Series Termination Logic. These are 1.8 V output capable buffers. 1.8 V
tolerant.
HA[31:3]#
HD[63:0]# PCI
EXP_RXN[15:0], EXP_RXP[15:0]
HADS# Express *
EXP_TXN[15:0], EXP_TXP[15:0]
HBNR# x16
EXP_COMPO
HBPRI# Graphics EXP_COMPI
HDBSY# Port
HDEFER#
HDRDY#
HEDRDY# HCLKP, HCLKN
HHIT# GCLKP, GCLKN
HHITM# DREFCLKN, DREFCLKP
Processor RSTIN#
HLOCK# Clocks,
System PWROK
HREQ[4:0]# Reset, and
Bus EXTTS#
HPCREQ# Misc.
Interface XORTEST
HTRDY#
HRS[2:0]# EXP_SLR
HCPURST# ICH_SYNC#
HBREQ0# ALLZTEST
HDINV[3:0]#
HADSTB[1:0]# Direct DMI_RXP[3:0], DMI_RXN[3:0]
HDSTBP[3:0]#, HDSTBN[3:0]# Media DMI_TXP[3:0], DMI_TXN[3:0]
BSEL[2:0] Interface
HRCOMP
HSCOMP
HSWING VCC
HDVREF VTT
HACCVREF VCC_EXP
Voltage VCCA_3GBG
Reference, VCCSM
SCS_A[3:0]# and Power VCC2
SMA_A[13:0] VCCA_EXPPLL
SBS_A[2:0] VCCA_HPLL
System
SRAS_A# VCCA_SMPLL
Memory VSS
SCAS_A#
SWE_A# DDR2
SDQ_A[63:0] Channel System
SDM_A[7:0] A SRCOMP[1:0]
SCB_A[7:0] Memory
SOCOMP[1:0]
SDQS_A[8:0], SDQS_A[8:0]# SMVREF[1:0]
SCKE_A[3:0] DDR2 Ref./
SCLK_A[5:0], SCLK_A[5:0]# Comp.
SODT_A[3:0]
SCS_B[3:0]#
SMA_B[13:0]
SBS_B[2:0] System
SRAS_B# Memory
SCAS_B#
SWE_B# DDR2
SDQ_B[63:0] Channel
SDM_B[7:0]
B
SCB_B[7:0]
SDQS_B[8:0], SDQS_B[8:0]#
SCKE_B[3:0]
SCLK_B[5:0], SCLK_B[5:0]#
SODT_B[3:0]
Signal_Info_955X
HADS# I/O Address Strobe: The processor bus owner asserts HADS# to
GTL+ indicate the first of two cycles of a request phase. The MCH can
assert this signal for snoop cycles and interrupt messages.
HBNR# I/O Block Next Request: This signal is used to block the current request
GTL+ bus owner from issuing new requests. This signal is used to
dynamically control the processor bus pipeline depth.
HBPRI# O Priority Agent Bus Request: The MCH is the only Priority Agent on
GTL+ the processor bus. It asserts this signal to obtain the ownership of the
address bus. This signal has priority over symmetric bus requests and
will cause the current symmetric owner to stop issuing new
transactions unless the HLOCK# signal was asserted.
HBREQ0# I/O Bus Request 0: The MCH pulls the processor’s bus HBREQ0# signal
GTL+ low during HCPURST#. The processor samples this signal on the
active-to-inactive transition of HCPURST#. The minimum setup time
for this signal is 4 HCLKs. The minimum hold time is 2 HCLKs and the
maximum hold time is 20 HCLKs. HBREQ0# should be tri-stated after
the hold time requirement has been satisfied.
HCPURST# O CPU Reset: The HCPURST# pin is an output from the MCH. The
GTL+ MCH asserts HCPURST# while RSTIN# is asserted and for
approximately 1 ms after RSTIN# is de-asserted. The HCPURST#
allows the processors to begin execution in a known state.
®
Note that the Intel ICH7 must provide processor frequency select
strap setup and hold times around HCPURST#. This requires strict
synchronization between MCH HCPURST# de-assertion and the
ICH7 driving the straps.
HDBSY# I/O Data Bus Busy: This signal is used by the data bus owner to hold the
GTL+ data bus for transfers requiring more than one cycle.
HDEFER# O Defer: HDEFER# signals that the MCH will terminate the transaction
GTL+ currently being snooped with either a deferred response or with a retry
response.
HDINV[3:0]# I/O Dynamic Bus Inversion: HDINV[3:0]# are driven along with the
GTL+ HD[63:0] signals. They indicate if the associated signals are inverted
or not. HDINV[3:0]# are asserted such that the number of data bits
driven electrically low (low voltage) within the corresponding 16 bit
group never exceeds 8.
HDINV3# HD[63:48]
HDINV2# HD[47:32]
HDINV1# HD[31:16]
HDINV0# HD[15:0]
HDRDY# I/O Data Ready: This signal is asserted for each cycle that data is
GTL+ transferred.
HEDRDY# O Early Data Ready: This signal indicates that the data phase of a read
GTL+ transaction will start on the bus exactly one common clock after
assertion.
HA[35:3]# I/O Host Address Bus: HA[35:3]# connect to the processor address bus.
GTL+ During processor cycles, the HA[35:3]# are inputs. The MCH drives
HA[35:3]# during snoop cycles on behalf of DMI and PCI Express*
initiators. HA[35:3]# are transferred at 2x rate.
HADSTB[1:0]# I/O Host Address Strobe: These signals are the source synchronous
GTL+ strobes used to transfer HA[31:3]# and HREQ[4:0] at the 2x transfer
rate.
HD[63:0]# I/O Host Data: These signals are connected to the processor data bus.
GTL+ Data on HD[63:0]# is transferred at 4x rate. Note that the data signals
may be inverted on the processor bus, depending on the HDINV[3:0]#
signals.
HDSTBP[3:0]# I/O Differential Host Data Strobes: The differential source synchronous
GTL+ strobes used to transfer HD[63:0]# and HDINV[3:0]# at 4x transfer
HDSTBN[3:0]#
rate.
These signals are named this way because they are not level
sensitive. Data is captured on the falling edge of both strobes. Hence,
they are pseudo-differential, and not true differential.
HHIT# I/O Hit: This signal indicates that a caching agent holds an unmodified
GTL+ version of the requested line. This signal is also driven in conjunction
with HHITM# by the target to extend the snoop window.
HHITM# I/O Hit Modified: This signal indicates that a caching agent holds a
GTL+ modified version of the requested line and that this agent assumes
responsibility for providing the line. This signal is also driven in
conjunction with HHIT# to extend the snoop window.
HLOCK# I Host Lock: All processor bus cycles sampled with the assertion of
GTL+ HLOCK# and HADS#, until the negation of HLOCK# must be atomic
(i.e., no DMI or PCI Express accesses to DRAM are allowed when
HLOCK# is asserted by the processor).
HPCREQ# I Precharge Request: The processor provides a “hint” to the MCH that
GTL+ it is OK to close the DRAM page of the memory read request with
2x which the hint is associated. The MCH uses this information to
schedule the read request to memory using the special
“AutoPrecharge” attribute. This causes the DRAM to immediately
close (Precharge) the page after the read data has been returned.
This allows subsequent processor requests to more quickly access
information on other DRAM pages, since it will no longer be
necessary to close an open page prior to opening the proper page.
HPCREQ# is asserted by the requesting agent during both halves of
Request Phase. The same information is provided in both halves of
the request phase.
HREQ[4:0]# I/O Host Request Command: These signals define the attributes of the
GTL+ request. HREQ[4:0]# are transferred at 2x rate. They are asserted by
2x the requesting agent during both halves of Request Phase. In the first
half the signals define the transaction type to a level of detail that is
sufficient to begin a snoop request. In the second half the signals
carry additional information to define the complete transaction type.
HTRDY# O Host Target Ready: This signal indicates that the target of the
GTL+ processor transaction is able to enter the data transfer phase.
BSEL[2:0] I Bus Speed Select: At the de-assertion of RSTIN#, the value sampled
CMOS on these pins determines the expected frequency of the bus.
HRCOMP I/O Host RCOMP: This signal is used to calibrate the Host GTL+ I/O
CMOS buffers. This signal is powered by the Host Interface termination rail
(VTT).
HSCOMP I/O Slew Rate Compensation: This signal provides compensation for the
CMOS Host Interface.
HSWING I Host Voltage Swing: This signal provides the reference voltage used
A by FSB RCOMP circuits. HSWING is used for the signals handled by
HRCOMP.
HDVREF I Host Reference Voltage: This signal is the voltage input for the data,
A address, and common clock signals of the Host GTL interface.
HACCVREF I Host Reference Voltage. This signal is the reference voltage input
A for the address and common clock signals of the Host GTL interface.
SCB_A[7:0] I/O ECC Check Byte: These signals are used for ECC.
SSTL-1.8
2x
SBS_A[2:0] O Bank Select: These signals define which banks are selected
SSTL-1.8 within each SDRAM rank. DDR2: 1-Gb technology is 8 banks.
SRAS_A# O Row Address Strobe: This signal is used with SCAS_A# and
SSTL-1.8 SWE_A# (along with SCS_A#) to define the SDRAM
commands.
SWE_A# O Write Enable: This signal is used with SCAS_A# and SRAS_A#
SSTL-1.8 (along with SCS_A#) to define the SDRAM commands.
SDQ_A[63:0] I/O Data Lines: SDQ_Ax signals interface to the SDRAM data bus.
SSTL-1.8
2x
SDQS_A[8:0] I/O Data Strobes: For DDR2, SDQS_Ax and its complement
SSTL-1.8 SDQS_Ax# signal make up a differential strobe pair. The data is
2x captured at the crossing point of SDQS_Ax and its complement
SDQS_Ax# during read and write transactions.
SCB_B[7:0] I/O ECC Check Byte: These signals are used for ECC.
SSTL-1.8
2x
SBS_B[2:0] O Bank Select: These signals define which banks are selected
SSTL-1.8 within each SDRAM rank. DDR2: 1-Gb technology is 8 banks.
SRAS_B# O Row Address Strobe: This signal is used with SCAS_B# and
SSTL-1.8 SWE_B# (along with SCS_B#) to define the SDRAM commands
SCAS_B# O Column Address Strobe: This signal is used with SRAS_B# and
SSTL-1.8 SWE_B# (along with SCS_B#) to define the SDRAM commands.
SWE_B# O Write Enable: This signal is used with SCAS_B# and SRAS_B#
SSTL-1.8 (along with SCS_B#) to define the SDRAM commands.
SDQ_B[63:0] I/O Data Lines: SDQ_Bx signals interface to the SDRAM data bus.
SSTL-1.8
2x
SDM_B[7:0] O Data Mask: When activated during writes, the corresponding data
SSTL-1.8 groups in the SDRAM are masked. There is one SBDM for every
2x data byte lane.
SDQS_B[8:0] I/O Data Strobes: For DDR2, SDQS_Bx and its complement
SSTL-1.8 SDQS_Bx# make up a differential strobe pair. The data is
2x captured at the crossing point of SDQS_Bx and its complement
SDQS_Bx# during read and write transactions.
SOCOMP[1:0] I/O DDR2 On-Die DRAM Over Current Detection (OCD) driver
A compensation
SMVREF[1:0] I SDRAM Reference Voltage: Reference voltage inputs for each DQ,
A DM, DQS, and DQS# input signals.
HCLKP I Differential Host Clock In: These pins receive a differential host
HCSL clock from the external clock synthesizer. This clock is used by all of
HCLKN
the MCH logic that is in the Host clock domain. Memory domain
clocks are also derived from this source.
RSTIN# I Reset In: When asserted, this signal will asynchronously reset the
HVIN MCH logic. This signal is connected to the PCIRST# output of the
®
Intel ICH7. All PCI Express graphics attach output signals will also
tri-state compliant to PCI Express* Base Specification , Revision
1.0a.
EXP_SLR I PCI Express* Static Lane Reversal: MCH’s PCI Express lane
CMOS numbers are reversed.
XORTEST I/O XOR Test: This signal is used for Bed of Nails testing by OEMs to
GTL+ execute XOR Chain test.
ALLZTEST I/O All Z Test: As an input this signal is used for Bed of Nails testing by
GTL+ OEMs to execute XOR Chain test. It is used as an output for XOR
chain testing.
VSS 0V Ground
Legend:
DRIVE: Strong drive (to normal value supplied by core logic if not otherwise stated) .
TRI: Tri-state.
PU: Weak internal pull-up: 7.2 KΩ – 11.1 KΩ, unless otherwise specified.
CMCT: Common Mode Center Tapped. Differential signals are weakly driven to the
common mode central voltage.
HDREF I IN IN
HSWING I IN IN
HACCVREF I IN IN
SCKE_A[3:0] O LV LV
SCKE_A[3:0] O LV LV
SODT_A[3:0] O LV LV
SCKE_B[3:0] O LV LV
SODT_B[3:0] O LV LV
Clocks HCLKN I IN IN
HCLKP I IN IN
GCLKN I IN IN
GCLKP I IN IN
DREFCLKN I IN IN
DREFCLKP I IN IN
Misc. RSTIN# I IN IN
PWROK I HV HV
ICH_SYNC# O PU PU INT 10 KΩ
PU
EXTTS# I IN IN
The MCH internal registers (I/O Mapped, Configuration and PCI Express extended configuration
registers) are accessible by the processor. The registers that reside within the lower 256 bytes of
each device can be accessed as Byte, Word (16-bit), or DWord (32-bit) quantities, with the
exception of CONFIG_ADDRESS that 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). Registers that reside in bytes 256 through 4095 of each device may only be accessed using
memory-mapped transactions in DWord (32-bit) quantities.
Some of the MCH registers described in this section contain reserved bits. These bits are labeled
"Reserved”. Software must deal correctly with fields that are reserved. 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 positions are preserved.
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,
and write operation for the configuration address register.
In addition to reserved bits within a register, the MCH contains address locations in the
configuration space of the Host Bridge entity that are marked either "Reserved" or “Intel
Reserved”. The MCH responds to accesses to “Reserved” address locations by completing the
host cycle. When a “Reserved” register location is read, a zero value is returned. (“Reserved”
registers can be 8-, 16-, or 32-bits in size). Writes to “Reserved” registers have no effect on the
MCH. Registers that are marked as “Intel Reserved” must not be modified by system software.
Writes to “Intel Reserved” registers may cause system failure. Reads from “Intel Reserved”
registers may return a non-zero value.
Upon a Full Reset, the MCH sets its entire set of internal configuration registers to predetermined
default states. Some register values at reset are determined by external strapping options. The
default state represents the minimum functionality feature set required to successfully bringing up
the system. Hence, it does not represent the optimal system configuration. It is the responsibility
of the system initialization software (usually BIOS) to properly determine the DRAM
configurations, operating parameters and optional system features that are applicable, and to
program the MCH registers accordingly.
Item Description
RO/S Read Only / Sticky. Writes to these bits have no effect. These are status bits only. Bits
are not returned to their default values by “warm” reset, but will be reset with a
cold/complete reset (for PCI Express related bits, a cold reset is “Power Good Reset”
as defined in the PCI Express specification).
RS/WC Read Set / Write Clear bit(s). These bits are set to 1 when read and then will continue
to remain set until written. A write of 1 clears (sets to 0) the corresponding bit(s) and a
write of 0 has no effect.
R/W Read / Write bit(s). These bits can be read and written.
R/WC Read / Write Clear bit(s). These bits can be read. Internal events may set this bit. A
write of 1 clears (sets to 0) the corresponding bit(s) and a write of 0 has no effect.
R/WC/S Read / Write Clear / Sticky bit(s). These bits can be read. Internal events may set this
bit. A write of 1 clears (sets to 0) the corresponding bit(s) and a write of 0 has no effect.
Bits are not cleared by "warm" reset, but will be reset with a cold/complete reset (for
PCI Express* related bits a cold reset is “Power Good Reset” as defined in the PCI
Express* Specification).
R/W/L Read / Write / Lockable bit(s). These bits can be read and written. Additionally, there is
a bit (which may or may not be a bit marked R/W/L) that, when set, prohibits this bit
field from being writeable (bit field becomes Read Only).
R/W/S Read / Write / Sticky bit(s). These bits can be read and written. Bits are not cleared by
"warm" reset, but will be reset with a cold/complete reset (for PCI Express related bits a
cold reset is “Power Good Reset” as defined in the PCI Express* Specification).
R/WSC Read / Write Self Clear bit(s). These bits can be read and written. When the bit is 1,
hardware may clear the bit to 0 based upon internal events, possibly sooner than any
subsequent read could retrieve a 1.
R/WSC/L Read / Write Self Clear / Lockable bit(s). These bits can be read and written. When the
bit is 1, hardware may clear the bit to 0 based upon internal events, possibly sooner
than any subsequent read could retrieve a 1. Additionally there is a bit (which may or
may not be a bit marked R/W/L) that, when set, prohibits this bit field from being
writeable (bit field becomes Read Only).
R/WO Write Once bit(s). Once written, bits with this attribute become Read Only. These bits
can only be cleared by a Reset.
W Write Only. Whose bits may be written, but will always-return zeros when read. They
are used for write side effects. Any data written to these registers cannot be retrieved.
Note: The ICH7 internal LAN controller does not appear on bus 0; it appears on the external PCI bus
and this number is configurable.
The system’s primary PCI expansion bus is physically attached to the ICH7 and, from a
configuration perspective, appears to be a hierarchical PCI bus behind a PCI-to-PCI bridge;
therefore, it has a programmable PCI Bus number. The PCI Express graphics attach appears to
system software to be a real PCI bus behind a PCI-to-PCI bridge that is a device resident on PCI
bus 0.
Note: A physical PCI bus 0 does not exist; DMI and the internal devices in the MCH and ICH7
logically constitute PCI Bus 0 to configuration software (see Figure 3-1).
Figure 3-1. Conceptual Intel® 955X Express Chipset Platform PCI Configuration Diagram
Processor
MCH
PCI_Config_Dia
The MCH contains two PCI devices within a single physical component. The configuration
registers for the two devices are mapped as devices residing on PCI bus 0.
• Device 0: Host Bridge/DRAM Controller. Logically this appears as a PCI device residing
on PCI bus 0. Device 0 contains the standard PCI header registers, PCI Express base address
register, DRAM control (including thermal/throttling control), and configuration for the DMI
and other MCH specific registers.
• Device 1: Host-PCI Express Bridge. Logically this appears as a “virtual” PCI-to-PCI bridge
residing on PCI bus 0 and is compliant with PCI Express* Specification, Revision 1.0a.
Device 1 contains the standard PCI-to-PCI bridge registers and the standard PCI Express/PCI
configuration registers (including the PCI Express memory address mapping). It also contains
Isochronous and Virtual Channel controls in the PCI Express extended configuration space.
000h
DMI Root Complex Register
Block (RCRB)
FFFh
MCH-ICH7 Serial Interface
(DMI) Controls:
Analog Controls
Error Reporting Controls
VC Control (Incl. VCp)
000h
Device 1 Configuration
Registers: PCI Express* X16 PCI Express Address Range
FFFh 0FFF FFFFh
PCI Express* x16 Controls: Accessed only by PCI
Analog Controls Express enhanced access
Error Reporting Controls mechanism. 4 KB block
VC Controls allocated for each potential
Hot Plug/Slot Controls device in root hierarchy.
0FFh
NOTES:
1. Very high level representation. Many details omitted.
2. Only Device 1 uses PCI Express extended configuration space.
3. Device 0 uses only standard PCI configuration space.
4. Hex numbers represent address range size and not actual locations.
The PCI Local Bus Specification defines a slot based "configuration space" that allows each
device to contain up to 8 functions with each function containing up to 256 8-bit configuration
registers. The PCI specification defines two bus cycles to access the PCI configuration space:
Configuration Read and Configuration Write. Memory and I/O spaces are supported directly by
the processor. Configuration space is supported by a mapping mechanism implemented within the
MCH.
The configuration access mechanism makes use of the CONFIG_ADDRESS Register (at I/O
address 0CF8h though 0CFBh) and the CONFIG_DATA Register (at I/O address 0CFCh though
0CFFh). To reference a configuration register a DWord I/O write cycle is used to place a value
into CONFIG_ADDRESS that specifies the PCI bus, the device on that bus, the function within
the device, and a specific configuration register of the device function being accessed.
CONFIG_ADDRESS[31] must be 1 to enable a configuration cycle. CONFIG_DATA then
becomes a window into the four bytes of configuration space specified by the contents of
CONFIG_ADDRESS. Any read or write to CONFIG_DATA will result in the MCH translating
the CONFIG_ADDRESS into the appropriate configuration cycle.
The MCH is responsible for translating and routing the processor’s I/O accesses to the
CONFIG_ADDRESS and CONFIG_DATA registers to internal MCH configuration registers,
DMI or PCI Express.
The PCI compatible region can be accessed using either the Standard PCI Configuration
Mechanism or using the PCI Express enhanced configuration mechanism described in this
section. The extended configuration registers may only be accessed using the PCI Express
enhanced configuration mechanism. To maintain compatibility with PCI configuration addressing
mechanisms, system software must access the extended configuration space using 32-bit
operations (32-bit aligned) only. These 32-bit operations include byte enables allowing only
appropriate bytes within the DWord to be accessed. Locked transactions to the PCI Express
memory mapped configuration address space are not supported. All changes made using either
access mechanism are equivalent.
The PCI Express enhanced configuration mechanism uses a flat memory-mapped address space to
access device configuration registers. This address space is reported by the system firmware to the
operating system. The PCIEXBAR Register defines the base address for the 256 MB block of
addresses below the top of addressable memory (currently 8 GB) for the configuration space
associated with all busses, devices, and functions that are potentially a part of the PCI Express
root complex hierarchy. The PCIEXBAR Register has controls to limit the size of this reserved
memory mapped space; 256 MB is the amount of address space required to reserve space for
every bus, device, and function that could possibly exist. Options for 128 MB and 64 MB exist to
free up those addresses for other uses. In these cases, the number of busses and all of their
associated devices and functions are limited to 128 or 64 busses respectively.
Located By PCI
Express Base
Address MemMap_PCIExpress
As with PCI devices, each device is selected based on decoded address information that is
provided as a part of the address portion of Configuration Request packets. A PCI Express device
will decode all address information fields (bus, device, function, and extended address numbers)
to provide access to the correct register.
To access this space (steps 1, 2, and 3 are completed only once by BIOS),
1. use the PCI compatible configuration mechanism to enable the PCI Express enhanced
configuration mechanism by writing 1 to bit 0 of the PCIEXBAR register.
2. use the PCI compatible configuration mechanism to write an appropriate PCI Express
base address into the PCIEXBAR register
3. calculate the host address of the register you wish to set using (PCI Express base + (bus
number * 1 MB) + (device number * 32KB) + (function number * 4 KB) +
(1 B * offset within the function) = host address)
4. use a memory write or memory read cycle to the calculated host address to write or read
that register.
I/O Read/Write to
CONFIG_DATA
Yes
Bus# = 0
No
No No
No
No
No
Config_Cyc_Flow_955X
See the PCI Express specification for more information on both the PCI 2.3 compatible and PCI
Express enhanced configuration mechanism and transaction rules.
The device on other side of link must be Device #0. The MCH will Master Abort any Type 0
configuration access to a non-zero Device number. If there is to be more than one device on that
side of the link, there must be a bridge implemented in the downstream device.
When the Bus Number of a type 1 Standard PCI Configuration cycle or PCI Express enhanced
configuration access is within the claimed range (between the upper bound of the bridge device’s
Subordinate Bus Number register and the lower bound of the bridge device’s Secondary Bus
Number register) but does not match the Device #1 Secondary Bus Number, a PCI Express Type
1 configuration TLP is generated on the secondary side of the PCI Express link.
If the Bus Number is zero, the MCH will generate a Type 0 Configuration Cycle TLP on DMI. If
the Bus Number is non-zero, and falls outside the range claimed by the Host-PCI Express bridge,
the MCH will generate a Type 1 configuration cycle TLP on DMI.
The ICH7 routes configuration accesses in a manner similar to the MCH. The ICH7 decodes the
configuration TLP and generates a corresponding configuration access. Accesses targeting a
device on PCI Bus #0 may be claimed by an internal device. The ICH7 compares the non-zero
Bus Number with the Secondary Bus Number and Subordinate Bus Number registers of its PCI-
to-PCI bridges to determine if the configuration access is meant for Primary PCI, one of the
ICH7’s devices, the DMI, or some other downstream PCI bus or PCI Express link.
Configuration accesses that are forwarded to the ICH7, but remain unclaimed by any device or
bridge will result in a master abort.
CONFIG_ADDRESS is a 32-bit register that can be accessed only as a DWord. A Byte or Word
reference will "pass through" the Configuration Address Register and DMI onto the Primary PCI
bus 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.
30:24 Reserved
23:16 R/W Bus Number: If the Bus Number is programmed to 00h, the target of the
00h configuration cycle is a PCI Bus #0 agent. If this is the case and the MCH is not
the target (i.e., the device number is ≥ 2), then a DMI Type 0 configuration cycle is
generated.
If the Bus Number is non-zero, and does not fall within the ranges enumerated by
device 1’s Secondary Bus Number or Subordinate Bus Number Register, then a
DMI Type 1 configuration cycle is generated.
If the Bus Number is non-zero and matches the value programmed into the
Secondary Bus Number Register of device 1, a Type 0 PCI configuration cycle will
be generated on PCI Express.
If the Bus Number is non-zero, greater than the value in the Secondary Bus
Number register of device 1 and less than or equal to the value programmed into
the Subordinate Bus Number Register of device 1, a Type 1 PCI configuration
cycle will be generated on PCI Express.
This field is mapped to byte 8 [7:0] of the request header format during PCI
Express configuration cycles and A[23:16] during the DMI Type 1 configuration
cycles.
15:11 R/W Device Number: This field selects one agent on the PCI bus selected by the Bus
00h Number. When the Bus Number field is “00”, the MCH decodes the Device
Number field. The MCH is always Device Number 0 for the Host bridge entity,
Device Number 1 for the Host-PCI Express entity. Therefore, when the Bus
Number =0 and the Device Number equals 0, or 1, the internal MCH devices are
selected.
This field is mapped to byte 6 [7:3] of the request header format during PCI
Express configuration cycles and A[15:11] during the DMI configuration cycles.
10:8 R/W Function Number: This field allows the configuration registers of a particular
000b function in a multi-function device to be accessed. The MCH ignores configuration
cycles to its internal devices if the function number is not equal to 0.
This field is mapped to byte 6 [2:0] of the request header format during PCI
Express configuration cycles and A[10:8] during the DMI configuration cycles.
7:2 R/W Register Number: This field selects one register within a particular Bus, Device,
00h and Function as specified by the other fields in the Configuration Address
Register.
This field is mapped to byte 7 [7:2] of the request header format during PCI
Express configuration cycles and A[7:2] during the DMI Configuration cycles.
1:0 Reserved
Warning: Address locations that are not listed are considered Intel Reserved register locations. Reads to
Reserved address locations may return non-zero values. Writes to reserved locations may cause
system failures.
0Ch — Reserved — —
0F–2Bh — Reserved — —
30–33h — Reserved — —
35–3Fh — Reserved — —
50–53h — Reserved — —
5E–8Fh — Reserved — —
9Fh — Reserved — —
A2–C7h — Reserved — —
DA–DBh — Reserved — —
This register combined, with the Device Identification register, uniquely identifies any PCI
device.
15:0 RO Vendor Identification Number (VID): PCI standard identification for Intel.
8086h
This register, combined with the Vendor Identification register, uniquely identifies any PCI
device.
15:0 RO Device Identification Number (DID): Identifier assigned to the MCH core/primary
2774h PCI device.
Since MCH Device 0 does not physically reside on Primary PCI bus, many of the bits are not
implemented.
15:10 Reserved
8 R/W SERR Enable (SERRE): This bit is a global enable bit for Device 0 SERR
0b messaging. The MCH does not have a SERR signal. The MCH communicates
®
the SERR condition by sending a SERR message over DMI to the Intel ICH7.
0 = Disable. SERR message is not generated by the MCH for Device 0
1 = The MCH is enabled to generate SERR messages over DMI for specific
Device 0 error conditions that are individually enabled in the ERRCMD
Register. The error status is reported in the ERRSTS, and PCISTS Registers.
NOTE: This bit only controls SERR messaging for the Device 0. Device 1 has its
own SERRE bits to control error reporting for error conditions occurring in
that device. The control bits are used in a logical OR manner to enable
the SERR DMI message mechanism.
7 RO Address/Data Stepping Enable (ADSTEP): Not implemented. Hardwired to 0.
0b Address/data stepping is not implemented in the MCH.
3 Reserved
1 RO Memory Access Enable (MAE): Hardwired to 1. The MCH always allows access
1b to main memory.
This status register reports the occurrence of error events on Device 0’s PCI interface. Since the
MCH Device 0 does not physically reside on Primary PCI, many of the bits are not implemented.
14 R/W/C Signaled System Error (SSE): Software clears this bit by writing a 1 to it.
0b
0 = MCH Device 0 did Not generate a SERR message over DMI
1 = MCH Device 0 generated a SERR message over DMI for any enabled Device
0 error condition. Device 0 error conditions are enabled in the PCICMD, and
ERRCMD registers. Device 0 error flags are read/reset from the PCISTS, or
ERRSTS registers.
13 R/WC Received Master Abort Status (RMAS): Software clears this bit by writing a 1 to
0b it.
0 = MCH did Not generate a DMI request that received an Unsupported Request
completion packet.
1 = MCH generated a DMI request that received an Unsupported Request
completion packet.
12 R/WC Received Target Abort Status (RTAS): Software clears this bit by writing a 1 to
0b it.
0 = MCH did Not generate a DMI request that received a Completer Abort
completion packet.
1 = MCH generated a DMI request that receives a Completer Abort completion
packet.
10:9 RO DEVSEL Timing (DEVT): These bits are hardwired to "00". Device 0 does not
00b physically connect to Primary PCI. These bits are set to "00" (fast decode) so
that optimum DEVSEL timing for Primary PCI is not limited by the MCH.
6 Reserved
5 RO 66 MHz Capable: Hardwired to 0. This bit does not apply to PCI Express*.
0b
3:0 Reserved
This register contains the revision number of the MCH Device 0. These bits are read only and
writes to this register have no effect.
7:0 RO Revision Identification Number (RID): This is an 8-bit value that indicates the
®
revision identification number for the MCH Device 0. Refer to the Intel 955X
Express Chipset Specification Update for the value of the Revision ID Register.
This register identifies the basic function of the device, a more specific sub-class, and a register-
specific programming interface.
23:16 RO Base Class Code (BCC): This is an 8-bit value that indicates the base class
06h code for the MCH.
06h = Bridge device.
15:8 RO Sub-Class Code (SUBCC): This is an 8-bit value that indicates the category of
00h Bridge into which the MCH falls.
00h = Host Bridge.
7:0 RO Programming Interface (PI): This is an 8-bit value that indicates the
00h programming interface of this device. This value does not specify a particular
register set layout and provides no practical use for this device.
Device 0 in the MCH is not a PCI master. Therefore, this register is not implemented.
7:0 Reserved
This register identifies the header layout of the configuration space. No physical register exists at
this location.
7:0 RO PCI Header (HDR): This field always returns 0 to indicate that the MCH is a
00h single function device with standard header layout. Reads and writes to this
location have no effect.
15:0 R/WO Subsystem Vendor ID (SUBVID): This field should be programmed during boot-
0000h up to indicate the vendor of the system board. After it has been written once, it
becomes read only.
15:0 R/WO Subsystem ID (SUBID): This field should be programmed during BIOS
0000h initialization. After it has been written once, it becomes read only.
The CAPPTR Register provides the offset that is the pointer to the location of the first device
capability in the capability list.
7:0 RO Pointer to the Offset of the First Capability ID Register Block: In this case the
E0h first capability is the product-specific Capability Identifier (CAPID0).
This is the base address for the Egress Port MMIO Configuration space. There is no physical
memory within this 4-KB window that can be addressed. The 4 KB space reserved by this register
does not alias to any PCI 2.3 compliant memory mapped space.
Note: On reset, this register is disabled and must be enabled by writing a 1 to EPBAREN.
31:12 R/W Egress Port MMIO Base Address: This field corresponds to bits 31:12 of the
00000h base address Egress Port MMIO configuration space.
BIOS will program this register resulting in a base address for a 4-KB block of
contiguous memory address space. This register ensures that a naturally aligned
4-KB space is allocated within total addressable memory space of 4 GB.
System software uses this base address to program the MCH MMIO register set.
11:1 Reserved
This is the base address for the MCH memory mapped configuration space. There is no physical
memory within this 16-KB window that can be addressed. The 16 KB space reserved by this
register does not alias to any PCI 2.3 compliant memory mapped space.
Note: On reset, this register is disabled and must be enabled by writing a 1 to MCHBAREN.
31:14 R/W MCH Memory Mapped Base Address: This field corresponds to bits 31:14 of
00000h the base address MCH Memory Mapped configuration space.
BIOS will program this register resulting in a base address for a 16-KB block of
contiguous memory address space. This register ensures that a naturally aligned
16-KB space is allocated within total addressable memory space of 4 GB.
System software uses this base address to program the MCH Memory Mapped
register set.
13:1 Reserved
This is the base address for the PCI Express configuration space. This window of addresses
contains the 4 KB of configuration space for each PCI Express device that can potentially be part
of the PCI Express hierarchy associated with the MCH. There is not actual physical memory
within this window of up to 256-MBs that can be addressed. The actual length is determined by a
field in this register. Each PCI Express hierarchy requires a PCI Express BASE register. The
MCH supports one PCI Express hierarchy.
The region reserved by this register does not alias to any PCI 2.3 compliant memory mapped
space. For example MCHBAR reserves a 16-KB space outside of PCIEXBAR space. It cannot be
overlaid on the space reserved by PCIEXBAR for device 0.
On reset, this register is disabled and must be enabled by writing a 1 to the enable field in this
register. This base address shall be assigned on a boundary consistent with the number of buses
(defined by the Length field in this register) above TOLUD and still within total 32 bit
addressable memory space.
All other bits not decoded are read only 0. The PCI Express Base Address cannot be less than the
maximum address written to the Top of physical memory register (TOLUD). Software must
ensure that these ranges do not overlap with known ranges located above TOLUD.
31:28 R/W PCI Express* Base Address: This field corresponds to bits 31:28 of the base
Eh address for PCI Express enhanced configuration space. BIOS will program this
register resulting in a base address for a contiguous memory address space;
size is defined by bits 2:1 of this register.
This base address shall be assigned on a boundary consistent with the number
of buses (defined by the Length field in this register) above TOLUD and still
within total 32-bit addressable memory space. The address bits decoded
depend on the length of the region defined by this register.
The address used to access the PCI Express configuration space for a specific
device can be determined as follows:
PCI Express Base Address + Bus Number * 1MB + Device Number * 32KB +
Function Number * 4KB
The address used to access the PCI Express configuration space for Device 1
in this component would be PCI Express Base Address + 0 * 1MB + 1 * 32KB +
0 * 4KB = PCI Express Base Address + 32KB. Remember that this address is
the beginning of the 4 KB space that contains both the PCI compatible
configuration space and the PCI Express extended configuration space.
27 R/W 128 MB Base Address Mask (128ADMSK): This bit is either part of the PCI
0b Express Base Address (R/W) or part of the address mask (RO, read 0b),
depending on the value of bits 2:1 in this register.
26 R/W 64MB Base Address Mask (64ADMSK): This bit is either part of the PCI
0b Express Base Address (R/W) or part of the address mask (RO, read 0b),
depending on the value of bits 2:1 in this register
25:3 Reserved
2:1 R/W Length (LENGTH): This Field describes the length of this region: Enhanced
00b Configuration Space Region/Buses Decoded.
00 = 256 MB (buses 0–255). Bits 31:28 are decoded in the PCI Express Base
Address Field
01 = 128 MB (Buses 0–127). Bits 31:27 are decoded in the PCI Express Base
Address Field.
10 = 64 MB (Buses 0–63). Bits 31:26 are decoded in the PCI Express Base
Address Field.
11 = Reserved
This is the base address for the Root Complex configuration space. This window of addresses
contains the Root Complex Register set for the PCI Express hierarchy associated with the MCH.
There is no physical memory within this 4-KB window that can be addressed. The 4 KB reserved
by this register does not alias to any PCI 2.3 compliant memory mapped space.
On reset, this register is disabled and must be enabled by writing a 1 to the DMIBAREN in this
register.
31:12 R/W DMI Base Address: This field corresponds to bits 31:12 of the base address
00000h DMI configuration space.
BIOS will program this register resulting in a base address for a 4-KB block of
contiguous memory address space. This register ensures that a naturally
aligned 4-KB space is allocated within total addressable memory space of
4 GB.
System Software uses this base address to program the DMI register set.
11:1 Reserved
This register allows for enabling/disabling of PCI devices and functions that are within the MCH.
31:2 Reserved
31:7 RO/S Error Address Pointer (EAP): This field is used to store the 128B (Two Cache Line)
000000 address of main memory for which an error (single bit or multi-bit error) has occurred.
0h The address is captured after any address remapping through REMAPBASE/
REMAPLIMIT is applied, such that all physical system memory appears as a
contiguous logical address block. It is valid to compare this address against C0DRB*
and C1DRB* registers to determine which rank of memory failed.
Note that the value of this bit field represents the address of the first single or the first
multiple bit error occurrence after the error flag bits in the ERRSTS Register have
been cleared by software. A multiple bit error will overwrite a single bit error. Once the
error flag bits are set as a result of an error, this bit field is locked and doesn't change
as a result of a new error. These bits are reset on PWROK.
6:1 Reserved
0 RO/S Channel Indicator (CHI): This bit indicates which memory channel had the error.
0b
0 = Channel 0
1 = Channel 1
This register is used to report the ECC syndromes for each quadword of a 32B-aligned data
quantity read from the DRAM array.
7:0 RO/S DRAM ECC Syndrome (DECCSYN): After a DRAM ECC error on any QWord of the
00h data chunk resulting from a read command, hardware loads this field with a syndrome
that describes the set of bits associated with the first QWord containing an error. Note
that this field is locked from the time that it is loaded up to the time when the error flag
is cleared by software. If the first error was a single bit, correctable error, then a
subsequent multiple bit error on any of the QWords in this read transaction or any
subsequent read transaction will cause the field to be re-recorded. When a multiple bit
error is recorded, then the field is locked until the error flag is cleared by software. In
all other cases, an error, which occurs after the first error, and before the error flag,
has been cleared by software, will escape recording.
These bits are reset on PWROK.
This register is used to report the destination of the data containing an ECC error whose address is
recorded in DEAP.
7:6 Reserved
5:0 RO/S ECC Error Source Code (EESC): This field is updated concurrently with
00 0000b DERRSYN.
00h = Processor to memory reads
01h–07h = Reserved
08h–09h = DMI VC0 initiated and targeting cycles/data
0Ah–0Bh = DMI VC1 initiated and targeting cycles/data
0Ch–0Fh = Reserved
10h = PCI Express initiated and targeting cycles/data
11h = Reserved
12h = PCI Express initiated and targeting cycles/data
13h = Reserved
14h–16h = PCI Express initiated and targeting cycles/data
17h = Reserved
18h–3Eh = Reserved
3Fh = Used for broadcast messages with data targeting multiple units. (e.g.
EOI).
These bits are reset on PWROK.
This register controls the read, write, and shadowing attributes of the BIOS area from 0F0000h–
0FFFFFh
The MCH allows programmable memory attributes on 13 Legacy memory segments of various
sizes in the 768-KB to 1-MB address range. Seven Programmable Attribute Map (PAM) registers
support these features. Cache ability of these areas is controlled via the MTRR registers in the P6
processor. Two bits are used to specify memory attributes for each memory segment. These bits
apply to both host accesses and PCI initiator accesses to the PAM areas. These attributes are:
• RE (Read Enable). When RE = 1, the processor read accesses to the corresponding memory
segment are claimed by the MCH and directed to main memory. Conversely, when RE = 0,
the host read accesses are directed to PRIMARY PCI.
• WE (Write Enable). When WE = 1, the host write accesses to the corresponding memory
segment are claimed by the MCH and directed to main memory. Conversely, when WE = 0,
the host write accesses are directed to PRIMARY PCI.
The RE and WE attributes permit a memory segment to be read only, write only, read/write, or
disabled. For example, if a memory segment has RE = 1 and WE = 0, the segment is read only.
7:6 Reserved
5:4 R/W 0F0000–0FFFFFh Attribute (HIENABLE): This field controls the steering of read
00b and write cycles that addresses the BIOS area from 0F0000h to 0FFFFFh.
00 = DRAM Disabled: All accesses are directed to the DMI.
01 = Read Only: All reads are sent to DRAM. All writes are forwarded to the DMI.
10 = Write Only: All writes are sent to DRAM. Reads are serviced by DMI.
11 = Normal DRAM Operation: All reads and writes are serviced by DRAM.
3:0 Reserved
Warning: The MCH may hang if a PCI Express graphics attach or DMI originated access to Read Disabled
or Write Disabled PAM segments occur (due to a possible IWB to non-DRAM). For these
reasons, the following critical restriction is placed on the programming of the PAM regions:
At the time that a DMI or PCI Express graphics attach accesses to the PAM region may occur, the
targeted PAM segment must be programmed to be both readable and writeable.
7:6 Reserved
5:4 R/W 0C4000–0C7FFFh Attribute (HIENABLE): This field controls the steering of read
00b and write cycles that address the BIOS area from 0C4000h to 0C7FFFh.
00 = DRAM Disabled: Accesses are directed to the DMI.
01 = Read Only: All reads are serviced by DRAM. All writes are forwarded to the
DMI.
10 = Write Only: All writes are sent to DRAM. Reads are serviced by DMI.
11 = Normal DRAM Operation: All reads and writes are serviced by DRAM.
3:2 Reserved
1:0 R/W 0C0000–0C3FFFh Attribute (LOENABLE): This field controls the steering of read
00b and write cycles that address the BIOS area from 0C0000h to 0C3FFFh.
00 = DRAM Disabled: Accesses are directed to the DMI.
01 = Read Only: All reads are serviced by DRAM. All writes are forwarded to the
DMI.
10 = Write Only: All writes are sent to DRAM. Reads are serviced by DMI.
11 = Normal DRAM Operation: All reads and writes are serviced by DRAM.
7:6 Reserved
5:4 R/W 0CC000–0CFFFFh Attribute (HIENABLE):
00b 00 = DRAM Disabled: Accesses are directed to the DMI.
01 = Read Only: All reads are serviced by DRAM. All writes are forwarded to the DMI.
10 = Write Only: All writes are sent to DRAM. Reads are serviced by DMI.
11 = Normal DRAM Operation: All reads and writes are serviced by DRAM.
3:2 Reserved
1:0 R/W 0C8000–0CBFFFh Attribute (LOENABLE): This field controls the steering of read
00b and write cycles that address the BIOS area from 0C8000h to 0CBFFFh.
00 = DRAM Disabled: Accesses are directed to the DMI.
01 = Read Only: All reads are serviced by DRAM. All writes are forwarded to the DMI.
10 = Write Only: All writes are sent to DRAM. Reads are serviced by DMI.
11 = Normal DRAM Operation: All reads and writes are serviced by DRAM.
7:6 Reserved
5:4 R/W 0D4000–0D7FFFh Attribute (HIENABLE): This field controls the steering of read
00 b and write cycles that address the BIOS area from 0D4000h to 0D7FFFh.
00 = DRAM Disabled: Accesses are directed to the DMI.
01 = Read Only: All reads are serviced by DRAM. All writes are forwarded to the
DMI.
10 = Write Only: All writes are sent to DRAM. Reads are serviced by DMI.
11 = Normal DRAM Operation: All reads and writes are serviced by DRAM.
3:2 Reserved
1:0 R/W 0D0000–0D3FFFh Attribute (LOENABLE): This field controls the steering of read
00 b and write cycles that address the BIOS area from 0D0000h to 0D3FFFh.
00 = DRAM Disabled: Accesses are directed to the DMI.
01 = Read Only: All reads are serviced by DRAM. All writes are forwarded to the
DMI.
10 = Write Only: All writes are sent to DRAM. Reads are serviced by DMI.
11 = Normal DRAM Operation: All reads and writes are serviced by DRAM.
7:6 Reserved
5:4 R/W 0DC000–0DFFFFh Attribute (HIENABLE): This field controls the steering of read
00b and write cycles that address the BIOS area from 0DC000h to 0DFFFFh.
00 = DRAM Disabled: Accesses are directed to the DMI.
01 = Read Only: All reads are serviced by DRAM. All writes are forwarded to the
DMI.
10 = Write Only: All writes are sent to DRAM. Reads are serviced by DMI.
11 = Normal DRAM Operation: All reads and writes are serviced by DRAM.
3:2 Reserved
1:0 R/W 0D8000–0DBFFFh Attribute (LOENABLE): This field controls the steering of read
00b and write cycles that address the BIOS area from 0D8000h to 0DBFFFh.
00 = DRAM Disabled: Accesses are directed to the DMI.
01 = Read Only: All reads are serviced by DRAM. All writes are forwarded to the
DMI.
10 = Write Only: All writes are sent to DRAM. Reads are serviced by DMI.
11 = Normal DRAM Operation: All reads and writes are serviced by DRAM.
7:6 Reserved
5:4 R/W 0E4000–0E7FFFh Attribute (HIENABLE): This field controls the steering of read
00b and write cycles that address the BIOS area from 0E4000h to 0E7FFFh.
00 = DRAM Disabled: Accesses are directed to the DMI.
01 = Read Only: All reads are serviced by DRAM. All writes are forwarded to the
DMI.
10 = Write Only: All writes are sent to DRAM. Reads are serviced by DMI.
11 = Normal DRAM Operation: All reads and writes are serviced by DRAM.
3:2 Reserved
1:0 R/W 0E0000–0E3FFFh Attribute (LOENABLE): This field controls the steering of read
00b and write cycles that address the BIOS area from 0E0000h to 0E3FFFh.
00 = DRAM Disabled: Accesses are directed to the DMI.
01 = Read Only: All reads are serviced by DRAM. All writes are forwarded to the
DMI.
10 = Write Only: All writes are sent to DRAM. Reads are serviced by DMI.
11 = Normal DRAM Operation: All reads and writes are serviced by DRAM.
Controls the read, write, and shadowing attributes of the BIOS areas from 0E8000h–0EFFFFh.
7:6 Reserved
5:4 R/W 0EC000h–0EFFFFh Attribute (HIENABLE): This field controls the steering of read
00b and write cycles that address the BIOS area from 0E4000h to 0E7FFFh.
00 = DRAM Disabled: Accesses are directed to the DMI.
01 = Read Only: All reads are serviced by DRAM. All writes are forwarded to the
DMI.
10 = Write Only: All writes are sent to DRAM. Reads are serviced by DMI.
11 = Normal DRAM Operation: All reads and writes are serviced by DRAM.
3:2 Reserved
1:0 R/W 0E8000–0EBFFFh Attribute (LOENABLE): This field controls the steering of read
00b and write cycles that address the BIOS area from 0E0000h to 0E3FFFh.
00 = DRAM Disabled: Accesses are directed to the DMI.
01 = Read Only: All reads are serviced by DRAM. All writes are forwarded to the
DMI.
10 = Write Only: All writes are sent to DRAM. Reads are serviced by DMI.
11 = Normal DRAM Operation: All reads and writes are serviced by DRAM.
This 8-bit register controls a fixed DRAM hole from 15–16 MB.
7 R/W Hole Enable (HEN): This field enables a memory hole in DRAM space. The DRAM
0b that lies "behind" this space is not remapped.
0 = No memory hole.
1 = Memory hole from 15 MB to 16 MB.
6:1 Reserved
0 R/W MDA Present (MDAP): This bit works with the VGA Enable bits in the BCTRL
0b Register of Device 1 to control the routing of processor-initiated transactions
targeting MDA compatible I/O and memory address ranges. This bit should not be
set if device 1's VGA Enable bit is not set.
If device 1's VGA enable bit is not set, then accesses to I/O address range x3BCh–
x3BFh are forwarded to the DMI.
If the VGA enable bit is set and MDA is not present, then accesses to I/O address
range x3BCh–x3BFh are forwarded to PCI Express* if the address is within the
corresponding IOBASE and IOLIMIT; otherwise, they are forwarded to the DMI.
MDA resources are defined as the following:
Memory: 0B0000h – 0B7FFFh
I/O: 3B4h, 3B5h, 3B8h, 3B9h, 3BAh, 3BFh,
(Including ISA address aliases, A [15:10] are not used in decode)
Any I/O reference that includes the I/O locations listed above, or their aliases, will be
forwarded to the DMI even if the reference includes I/O locations not listed above.
The following table shows the behavior for all combinations of MDA and VGA:
15:10 Reserved
9:0 R/W Remap Base Address [35:26] (REMAPBASE): The value in this register defines
3FFh the lower boundary of the Remap window. The Remap window is inclusive of this
address. In the decoder A[25:0] of the Remap Base Address are assumed to be
0s. Thus, the bottom of the defined memory range will be aligned to a 64 MB
boundary.
When the value in this register is greater than the value programmed into the
Remap Limit register, the Remap window is disabled.
15:10 Reserved
9:0 R/W Remap Limit Address [35:26] (REMAPLMT): The value in this register defines
00h the upper boundary of the Remap window. The Remap window is inclusive of
this address. In the decoder A[25:0] of the remap limit address are assumed to
be F's. Thus the top of the defined range will be one less than a 64MB boundary.
When the value in this register is less than the value programmed into the
Remap Base register, the Remap window is disabled.
This 8-bit register defines the Top of Low Usable DRAM. TSEG Memory are within the DRAM
space defined. From the top, MCH optionally claims 1, 2, or 8 MB of DRAM for TSEG if
enabled.
7:3 R/W Top of Low Usable DRAM (TOLUD): This register contains bits 31:27 of an
01 h address one byte above the maximum DRAM memory that is usable by the
operating system. Address bits 31:27 programmed to 01h implies a minimum
memory size of 128 MBs.
Configuration software must set this value to the smaller of the following 2 choices.
Maximum amount memory in the system plus one byte or the minimum address
allocated for PCI memory.
Address bits 26:0 are assumed to be 000_0000h for the purposes of address
comparison. The Host interface positively decodes an address towards DRAM if the
incoming address is less than the value programmed in this register.
If this register is set to 0000 0 b it implies 128 MBs of system memory.
Note: That the Top of Low Usable DRAM is the lowest address above TSEG.
2:0 Reserved
The SMRAMC Register controls how accesses to Compatible and Extended SMRAM spaces are
treated. The Open, Close, and Lock bits function only when the G_SMRAME bit is set to a 1.
Also, the OPEN bit must be reset before the LOCK bit is set.
7 Reserved
6 R/W/L SMM Space Open (D_OPEN): When D_OPEN=1 and D_LCK=0, the SMM
0b space DRAM is made visible even when SMM decode is not active. This is
intended to help BIOS initialize SMM space. Software should ensure that
D_OPEN=1 and D_CLS=1 are not set at the same time.
5 R/W/L SMM Space Closed (D_CLS): When D_CLS = 1 SMM space DRAM is not
0b accessible to data references, even if SMM decode is active. Code references
may still access SMM space DRAM. This will allow SMM software to reference
through SMM space to update the display even when SMM is mapped over the
VGA range. Software should ensure that D_OPEN=1 and D_CLS=1 are not set
at the same time. Note that the D_CLS bit only applies to Compatible SMM
space.
4 R/W/L SMM Space Locked (D_LCK): When D_LCK is set to 1, then D_OPEN is reset
0b to 0 and D_LCK, D_OPEN, C_BASE_SEG, H_SMRAM_EN, TSEG_SZ and
TSEG_EN become read only. D_LCK can be set to 1 via a normal configuration
space write but can only be cleared by a Full Reset. The combination of D_LCK
and D_OPEN provide convenience with security. The BIOS can use the
D_OPEN function to initialize SMM space and then use D_LCK to "lock down"
SMM space in the future so that no application software (or BIOS itself) can
violate the integrity of SMM space, even if the program has knowledge of the
D_OPEN function.
2:0 RO Compatible SMM Space Base Segment (C_BASE_SEG): This field indicates
010b the location of SMM space. SMM DRAM is not remapped. It is simply made
visible if the conditions are right to access SMM space; otherwise, the access is
forwarded to DMI. Since the MCH supports only the SMM space between
A0000h and BFFFFh, this field is hardwired to 010.
The Extended SMRAM register controls the configuration of Extended SMRAM space. The
Extended SMRAM (E_SMRAM) memory provides a write-back cacheable SMRAM memory
space that is above 1 MB.
7 R/W/L Enable High SMRAM (H_SMRAME): This bit controls the SMM memory space
0b location (i.e., above 1 MB or below 1 MB). When G_SMRAME = 1 and
H_SMRAME = 1, the high SMRAM memory space is enabled. SMRAM accesses
within the range 0FEDA0000h to 0FEDBFFFFh are remapped to DRAM
addresses within the range 000A0000h to 000BFFFFh. Once D_LCK has been
set, this bit becomes read only.
6 R/W/C Invalid SMRAM Access (E_SMERR): This bit is set when processor has
0b accessed the defined memory ranges in Extended SMRAM (High Memory and
T-segment) while not in SMM space and with D-OPEN = 0. It is software’s
function to clear this bit. Software must write a 1 to this bit to clear it.
4 RO L1 Cache Enable for SMRAM (SM_L1): This bit is forced to 1 by the MCH.
1b
3 RO L2 Cache Enable for SMRAM (SM_L2): This bit is forced to 1 by the MCH.
1b
2:1 R/W/L TSEG Size (TSEG_SZ): This field selects the size of the TSEG memory block if
00b enabled. Memory from the top of DRAM space is partitioned away so that it may
only be accessed by the processor interface and only then when the SMM bit is
set in the request packet. Non-SMM accesses to this memory region are sent to
the DMI when the TSEG memory block is enabled.
00 = 1-MB TSEG (TOLUD –1M) to (TOLUD).
01 = 2-MB TSEG (TOLUD – 2M) to (TOLUD).
10 = 8-MB TSEG (TOLUD – 8M) to (TOLUD).
11 = Reserved.
Once D_LCK has been set, these bits become read only.
0 R/W/L TSEG Enable (T_EN): This bit is for enabling of SMRAM memory for Extended
0b SMRAM space only. When G_SMRAME =1 and TSEG_EN = 1, TSEG is
enabled to appear in the appropriate physical address space. Note that once
D_LCK is set, this bit becomes read only.
This register contains the size of physical memory. BIOS determines the memory size reported to
the OS using this Register.
15:9 Reserved
8:0 R/W Top of Memory (TOM): This register reflects the total amount of populated physical
01h memory. This is also the amount of addressable physical memory when remapping
is used appropriate to ensure that no physical memory is wasted. This is NOT
necessarily the highest main memory address (holes may exist in main memory
address map due to addresses allocated for memory mapped IO).
These bits correspond to address bits 35:27 (128MB granularity). Bits 26:0 are
assumed to be 0.
This register is used to report various error conditions via the SERR DMI messaging mechanism.
A SERR DMI message is generated on a 0-to-1 transition of any of these flags (if enabled by the
ERRCMD and PCICMD Registers). These bits are set regardless of whether or not the SERR is
enabled and generated. After the error processing is complete, the error logging mechanism can
be unlocked by clearing the appropriate status bit by software writing a 1 to it.
15:12 Reserved
10 Reserved
7:2 Reserved
This register controls the MCH responses to various system errors. Since the MCH does not have
an SERRB signal, SERR messages are passed from the MCH to the ICH7 over DMI. When a bit
in this register is set, a SERR message will be generated on DMI whenever the corresponding flag
is set in the ERRSTS register. The actual generation of the SERR message is globally enabled for
Device 0 via the PCI Command Register.
15:12 Reserved
10 Reserved
7:2 Reserved
This register enables various errors to generate an SMI DMI special cycle. When an error flag is
set in the ERRSTS register, it can generate an SERR, SMI, or SCI DMI special cycle when
enabled in the ERRCMD, SMICMD, or SCICMD registers, respectively. Note that one and only
one message type can be enabled.
15:2 RO Reserved
000h
This register enables various errors to generate an SMI DMI special cycle. When an error flag is
set in the ERRSTS Register, it can generate an SERR, SMI, or SCI DMI special cycle when
enabled in the ERRCMD, SMICMD, or SCICMD registers, respectively. Note that one and only
one message type can be enabled.
15:2 RO Reserved
000h
This register holds 32 writable bits with no functionality. It is for the convenience of BIOS and
graphics drivers.
71:28 Reserved
27:24 RO CAPID Version: This field has the value 0001b to identify the first revision of the
1h CAPID register definition.
23:16 RO CAPID Length: This field has the value 09h to indicate the structure length
09h (9 bytes).
15:8 RO Next Capability Pointer: This field is hardwired to 00h indicating the end of the
00h capabilities linked list.
7:0 RO CAP_ID: This field has the value 1001b to identify the CAP_ID assigned by the
09h PCI SIG for vendor dependent capability pointers.
This register is used with the DEAP register. This EDEAP register contains bit 32 of the address
of detected DRAM ECC error(s).
7:1 Reserved
0 RO/S Extended Error Address Pointer (EEAP): This bit provides bit 32 of the error
0b address after any remapping when an ECC error occurs. This bit is concatenated
with bits 31:7 of the DEAP register to get bits 32:7 of the address in which an
error occurred. This bit is reset on PWROK.
188h C1DRA0 Channel 1 DRAM Rank 0,1 Attribute 00h RO, R/W
189h C1DRA2 Channel 1 DRAM Rank 2,3 Attribute 00h RO, R/W
The DRAM Rank Boundary Register defines the upper boundary address of each DRAM rank
with a granularity of 32 MB. Each rank has its own single-byte DRB register. These registers are
used to determine which chip select will be active for a given address.
Programming guide:
C0DRB1 = Total memory in chA rank0 + chA rank1 (in 32-MB increments)
––––
C1DRB0 = Total memory in chA rank0 + chA rank1 + chA rank2 + chA rank3 + chB rank0
(in 32-MB increments)
If Channel B is empty, all of the C1DRBs are programmed with the same value as C0DRB3.
Programming guide:
C0DRB1 = C1DRB1 = Total memory in chA rank0 + chA rank1 (in 32-MB increments)
––––
C0DRB3 = C1DRB3 = Total memory in chA rank0 + chA rank1+ chA rank2 + chA rank3
(in 32-MB increments)
In all modes, if a DIMM is single sided, it appears as a populated rank and an empty rank. A DRB
must be programmed appropriately for each.
Each Rank is represented by a byte. Each byte has the following format.
7:0 R/W Channel A DRAM Rank Boundary Address: This 8 bit value defines the upper
00h and lower addresses for each DRAM rank. Bits 6:2 are compared against
Address 31:27 to determine the upper address limit of a particular rank. Bits 1:0
must be 0s. Bit 7 may be programmed to a 1 in the highest DRB (DRB3) if 4 GBs
of memory is present.
The operation of this register is detailed in the description for the C0DRB0 Register.
The operation of this register is detailed in the description for the C0DRB0 Register.
The operation of this register is detailed in the description for the C0DRB0 Register.
7 Reserved
6:4 R/W Channel A DRAM odd Rank Attribute: This 3 bit field defines the page size of
000b the corresponding rank.
000 = Unpopulated
001 = Reserved
010 = 4 KB
011 = 8 KB
100 = 16 KB
Others = Reserved
3 Reserved
2:0 R/W Channel A DRAM even Rank Attribute: This 3 bit field defines the page size of
000b the corresponding rank.
000 = Unpopulated
001 = Reserved
010 = 4 KB
011 = 8 KB
100 = 16 KB
Others = Reserved
The operation of this register is detailed in the description for the C0DRA0 Register.
This register can be used to disable the system memory clock signals to each DIMM slot, which
can significantly reduce EMI and Power concerns for clocks that go to unpopulated DIMMs.
Clocks should be enabled based on whether a slot is populated, and what kind of DIMM is
present.
7:6 Reserved
Note: Since there are multiple clock signals assigned to each Rank of a DIMM, it is important to clarify
exactly which Rank width field affects which clock signal:
0 0 or 1 SCLK_A[2:0]/ SCLK_A[2:0]#
0 2 or 3 SCLK_A[5:3]/ SCLK_A[5:3]#
1 0 or 1 SCLK_B[2:0]/ SCLK_B[2:0]#
1 2 or 3 SCLK_B[5:3]/ SCLK_B[5:3]#
This register is used to program the bank architecture for each Rank.
15:8 Reserved
31:24 Reserved
23:20 R/W Activate to Precharge delay (tRAS). This bit controls the number of DRAM clocks
9h for tRAS. Minimum recommendations are beside their corresponding encodings.
0h – 3h = Reserved
4h – Fh = Four to Fifteen Clocks respectively.
19:10 Reserved
9:8 R/W CASB Latency (tCL). This field is programmable on DDR2 DIMMs. The value
01b programmed here must match the CAS Latency of every DDR2 DIMM in the
system.
00 = 5
01 = 4
10 = 3
11 = Reserved
7 Reserved
6:4 R/W DRAM RAS to CAS Delay (tRCD). This bit controls the number of clocks inserted
010b between a row activate command and a read or write command to that row.
000 = 2 DRAM Clocks
001 = 3 DRAM Clocks
010 = 4 DRAM Clocks
011 = 5 DRAM Clocks
100–111 = Reserved
3 Reserved
2:0 R/W DRAM RAS Precharge (tRP). This bit controls the number of clocks that are
010b inserted between a row precharge command and an activate command to the
same rank.
000 = 2 DRAM Clocks
001 = 3 DRAM Clocks
010 = 4 DRAM Clocks
011 = 5 DRAM Clocks
100–111 = Reserved
31:30 Reserved
29 R/W Initialization Complete (IC): This bit is used for communication of software state
0b between the memory controller and the BIOS. BIOS sets this bit to 1 after
initialization of the DRAM memory array is complete.
28:11 Reserved
10:8 R/W Refresh Mode Select (RMS): This field determines whether refresh is enabled
000b and, if so, at what rate refreshes will be executed.
000 = Refresh disabled
001 = Refresh enabled. Refresh interval 15.6 µsec
010 = Refresh enabled. Refresh interval 7.8 µsec
011 = Refresh enabled. Refresh interval 3.9 µsec
100 = Refresh enabled. Refresh interval 1.95 µsec
111 = Refresh enabled. Refresh interval 64 clocks (fast refresh mode)
Other = Reserved
7 RO Reserved
0b
6:4 R/W Mode Select (SMS): These bits select the special operational mode of the
000b DRAM interface. The special modes are intended for initialization at power up.
000 = Post Reset state – When the MCH exits reset (power-up or otherwise), the
mode select field is cleared to "000". During any reset sequence, while
power is applied and reset is active, the MCH de-asserts all CKE signals.
After internal reset is de-asserted, CKE signals remain de-asserted until
this field is written to a value different than "000". On this event, all CKE
signals are asserted. During suspend, MCH internal signal triggers DRAM
controller to flush pending commands and enter all ranks into Self-Refresh
mode. As part of resume sequence, MCH will be reset, which will clear
this bit field to "000" and maintain CKE signals de-asserted. After internal
reset is de-asserted, CKE signals remain de-asserted until this field is
written to a value different than "000". On this event, all CKE signals are
asserted. During entry to other low power states (C3, S1), MCH internal
signal triggers DRAM controller to flush pending commands and enter all
ranks into Self-Refresh mode. During exit to normal mode, MCH signal
triggers DRAM controller to exit Self-Refresh and resume normal
operation without S/W involvement.
001 = NOP Command Enable – All processor cycles to DRAM result in a NOP
command on the DRAM interface.
010 = All Banks Pre-charge Enable – All processor cycles to DRAM result in an
"all banks precharge" command on the DRAM interface.
011 = Mode Register Set Enable – All processor cycles to DRAM result in a
"mode register" set command on the DRAM interface. Host address lines
are mapped to DRAM address lines in order to specify the command sent,
as shown in Volume 1, System Memory Controller section, memory
Detection and Initialization. Refer to JEDEC Standard 79-2A Section 2.2.2
“Programming the Mode and Extended Mode Registers”.
100 = Extended Mode Register Set Enable – All processor cycles to DRAM
result in an "extended mode register set" command on the DRAM
interface. Host address lines are mapped to DRAM address lines in order
to specify the command sent, as shown in Volume 1, System Memory
Controller section, memory Detection and Initialization. Refer to JEDEC
Standard 79-2A Section 2.2.2 “Programming the Mode and Extended
Mode Registers”.
110 = CBR Refresh Enable – In this mode all processor cycles to DRAM result in
a CBR cycle on the DRAM interface.
111 = Normal operation
3:2 Reserved
1:0 RO DRAM Type (DT): This field is used to select between supported SDRAM types.
00 = Reserved
01 = Reserved
10 = Second Revision Dual Data Rate (DDR2) SDRAM
11 = Reserved
The operation of this register is detailed in the description for the C0DRB0 Register.
The operation of this register is detailed in the description for the C0DRB0 Register.
The operation of this register is detailed in the description for the C0DRB0 Register.
The operation of this register is detailed in the description for the C0DRB0 Register.
The operation of this register is detailed in the description for the C0DRA0 Register.
The operation of this register is detailed in the description for the C0DRA0 Register.
The operation of this register is detailed in the description for the C0DCLKDIS Register.
The operation of this register is detailed in the description for the C0BNKARC Register.
The operation of this register is detailed in the description for the C0DRT1 Register.
The operation of this register is detailed in the description for the C0DRC0 Register.
The operation of this register is detailed in the description for the C0DRC1 Register.
31:5 Reserved
3:0 Reserved
31:2 Reserved
MCH
X16 PEG
(Port #2) Link #2
(Type 1)
Link #1
(Type 0) Egress Port Main Memory
(Port #0) Subsystem
Link #2
(Type 0)
Link #1
(Type 0)
DMI
(Port #1)
Link #1
X4
(Type 0) Intel® ICH7
Egress Port
(Port #0)
Egress_LinkDeclar_Topo
This register provides information about the root complex element containing this Link
Declaration Capability.
31:24 RO Port Number: This field specifies the port number associated with this element
00h with respect to the component that contains this element.
Value of 00 h indicates to configuration software that this is the default egress
port.
23:16 R/WO Component ID: This field identifies the physical component that contains this
00h Root Complex Element. Component IDs start at 1.
This value is a mirror of the value in the Component ID field of all elements in this
component. The value only needs to be written in one of the mirrored fields and it
will be reflected everywhere that it is mirrored.
15:8 RO Number of Link Entries: This field indicates the number of link entries following
02h the Element Self Description. This field reports 2 (one each for PCI Express and
DMI).
7:4 Reserved
3:0 RO Element Type: This field indicates the type of the Root Complex Element. Value
01h of 1h represents a port to system memory
This register provides the first part of a Link Entry that declares an internal link to another Root
Complex Element.
31:24 RO Target Port Number: This field specifies the port number associated with the
01h element targeted by this link entry (DMI). The target port number is with respect to
the component that contains this element as specified by the target component
ID.
23:16 R/WO Target Component ID: This field identifies the physical or logical component that
00h is targeted by this link entry. A value of 0 is reserved; Component IDs start at 1.
This value is a mirror of the value in the Component ID field of all elements in this
component. The value only needs to be written in one of the mirrored fields and it
will be reflected everywhere that it is mirrored.
15:2 Reserved
1 RO Link Type: This field indicates that the link points to memory-mapped space (for
0b RCRB). The link address specifies the 64-bit base address of the target RCRB.
This register provides the second part of a Link Entry that declares an internal link to another
Root Complex Element.
63:32 Reserved
31:12 R/WO Link Address: This field provides the memory mapped base address of the
RCRB that is the target element (DMI) for this link entry.
0 0000 h
11:0 Reserved
This register provides the first part of a Link Entry that declares an internal link to another Root
Complex Element.
31:24 RO Target Port Number: This field specifies the port number associated with the
02h element targeted by this link entry (PCI Express). The target port number is with
respect to the component that contains this element as specified by the target
component ID.
23:16 R/WO Target Component ID: This field identifies the physical or logical component that
00h is targeted by this link entry. A value of 0 is reserved; Component IDs start at 1.
This value is a mirror of the value in the Component ID field of all elements in this
component. The value only needs to be written in one of the mirrored fields and it
will be reflected everywhere that it is mirrored.
15:2 Reserved
1 RO Link Type: This field indicates that the link points to configuration space of the
1b integrated device that controls the x16 root port. The link address specifies the
configuration address (segment, bus, device, function) of the target root port.
This register provides the second part of a Link Entry that declares an internal link to another
Root Complex Element.
63:28 Reserved
19:15 RO Device Number: Target for this link is PCI Express* x16 port (Device 1).
0 0001b
11:0 Reserved
Warning: When reading the PCI Express "conceptual" registers such as this, you may not get a valid value
unless the register value is stable.
The PCI Express* Specification defines two types of reserved bits: Reserved and Preserved.
• Reserved for future RW implementations; software must preserve value read for writes to
bits.
• Reserved and Zero: Reserved for future R/WC/S implementations; software must use 0 for
writes to bits.
Unless explicitly documented as Reserved and Zero, all bits marked as reserved are part of the
Reserved and Preserved type, which have historically been the typical definition for Reserved.
Note: Most (if not all) control bits in this device cannot be modified unless the link is down. Software is
required to first Disable the link, then program the registers, and then re-enable the link (which
will cause a full-retrain with the new settings).
Table 5-1. Host-PCI Express* Graphics Bridge Register Address Map (D1:F0)
0Dh — Reserved — —
0F–17h — Reserved — —
1Bh — Reserved — —
30–33h — Reserved — —
35–3Bh — Reserved — —
40–7Fh — Reserved — —
9A–9Fh — Reserved — —
BE–BFh — Reserved — —
C4–FFh — Reserved — —
10E–10Fh — Reserved — —
118–119h — Reserved — —
124–125h — Reserved — —
128–13Fh — Reserved — —
148–14Fh — Reserved — —
154–157h — Reserved — —
1CC–1CFh — Reserved — —
1D8–217h — Reserved — —
220–FFFh — Reserved — —
This register combined with the Device Identification register uniquely identifies any PCI device.
This register combined with the Vendor Identification register uniquely identifies any PCI device.
15:0 RO Device Identification Number (DID1): Identifier assigned to the MCH device 1
2775h (virtual PCI-to-PCI bridge, PCI Express* Graphics port).
15:11 Reserved
8 R/W SERR Message Enable (SERRE1): This bit is an enable bit for Device 1 SERR
0b messaging. The MCH communicates the SERR# condition by sending a SERR
®
message to the Intel ICH7. This bit, when set, enables reporting of non-fatal and
fatal errors to the Root Complex. Note that errors are reported if enabled either
through this bit or through the PCI Express* specific bits in the Device Control
Register.
0 = The SERR message is generated by the MCH for Device 1 only under
conditions enabled individually through the Device Control Register.
1 = The MCH is enabled to generate SERR messages that will be sent to the
ICH7 for specific Device 1 error conditions generated/detected on the primary
side of the virtual PCI to PCI Express bridge (not those received by the
secondary side). The error status is reported in the PCISTS1 register.
7 Reserved
6 R/WO Parity Error Enable (PERRE): This bit controls whether or not the Master Data
0b Parity Error bit in the PCI Status Register can bet set.
0 = Master Data Parity Error bit in PCI Status register can Not be set.
1 = Master Data Parity Error bit in PCI Status register can be set.
2 R/W Bus Master Enable (BME): This bit controls the ability of the PCI Express port
0b to forward memory and I/O read/write requests in the upstream direction.
0 = This device is prevented from making memory or I/O requests to its primary
bus. Note that according to PCI Local Bus Specification, as MSI interrupt
messages are in-band memory writes, disabling the bus master enable bit
prevents this device from generating MSI interrupt messages or passing
them from its secondary bus to its primary bus. Upstream memory
writes/reads, I/O writes/reads, peer writes/reads, and MSIs will all be treated
as invalid cycles. Writes are forwarded to memory address 0 with byte
enables de-asserted. Reads will be forwarded to memory address 0 and will
return Unsupported Request status (or Master abort) in its completion packet.
1 = This device is allowed to issue requests to its primary bus. Completions for
previously issued memory read requests on the primary bus will be issued
when the data is available.
This bit does not affect forwarding of Completions from the primary interface to
the secondary interface.
This register reports the occurrence of error conditions associated with primary side of the
“virtual” Host-PCI Express bridge embedded within the MCH.
This register contains the revision number of the MCH device 1. These bits are read only and
writes to this register have no effect.
7:0 RO Revision Identification Number (RID1): This field indicates the number of times
that this device in this component has been “stepped” through the manufacturing
process. It is always the same as the RID values in all other devices in this
®
component. Refer to the Intel 955X Express Chipset Specification Update for
the value of the Revision ID Register.
This register identifies the basic function of the device, a more specific sub-class, and a register-
specific programming interface.
23:16 RO Base Class Code (BCC): This field indicates the base class code for this device.
06h
06h = Bridge device.
15:8 RO Sub-Class Code (SUBCC): This field indicates the sub-class code for this
04h device.
04h = PCI-to-PCI Bridge.
7:0 RO Programming Interface (PI): This field indicates the programming interface of
00h this device. This value does not specify a particular register set layout and
provides no practical use for this device.
7:0 R/W Cache Line Size (Scratch pad): Implemented by PCI Express* devices as a
00h read-write field for legacy compatibility purposes but has no impact on any PCI
Express device functionality.
This register identifies the header layout of the configuration space. No physical register exists at
this location.
7:0 RO Header Type Register (HDR): This field returns 01 to indicate that this is a
01h single function device with bridge header layout.
This register identifies that this “virtual” Host-PCI Express bridge is connected to PCI bus 0.
7:0 RO Primary Bus Number (BUSN): Configuration software typically programs this
00h field with the number of the bus on the primary side of the bridge. Since device 1
is an internal device and its primary bus is always 0, these bits are read only and
are hardwired to 0.
This register identifies the bus number assigned to the second bus side of the “virtual” bridge (i.e.,
to PCI Express). This number is programmed by the PCI configuration software to allow mapping
of configuration cycles to PCI Express.
7:0 R/W Secondary Bus Number (BUSN): This field is programmed by configuration
00h software with the bus number assigned to PCI Express*.
This register identifies the subordinate bus (if any) that resides at the level below PCI Express.
This number is programmed by the PCI configuration software to allow mapping of configuration
cycles to PCI Express.
This register controls the processor-to-PCI Express I/O access routing based on the following
formula:
Only the upper 4 bits of this register are programmable. For the purpose of address decode,
address bits A [11:0] are treated as 0. Thus, the bottom of the defined I/O address range will be
aligned to a 4-KB boundary.
7:4 R/W I/O Address Base (IOBASE): This field corresponds to A [15:12] of the I/O
Fh addresses passed by bridge 1 to PCI Express*. BIOS must not set this register to
00h; otherwise, 0CF8h/0CFCh accesses will be forwarded to the PCI Express
hierarchy associated with this device.
3:0 Reserved
This register controls the processor-to-PCI Express I/O access routing based on the following
formula:
Only upper 4 bits of this register are programmable. For the purposes of address decode, address
bits A [11:0] are assumed to be FFFh. Thus, the top of the defined I/O address range will be at the
top of a 4-KB aligned address block.
7:4 R/W I/O Address Limit (IOLIMIT): This field corresponds to A[15:12] of the I/O
0h address limit of device 1. Devices between this upper limit and IOBASE1 will be
passed to the PCI Express* hierarchy associated with this device.
3:0 Reserved
SSTS1 is a 16-bit status register that reports the occurrence of error conditions associated with
secondary side (i.e., PCI Express side) of the “virtual” PCI-to-PCI Bridge in the MCH.
8 Reserved
6 Reserved
4:0 Reserved
This register controls the processor-to-PCI Express non-prefetchable memory access routing
based on the following formula:
The upper 12 bits of the register are read/write and correspond to the upper 12 address bits
A[31:20] of the 32-bit address. The bottom 4 bits of this register are read-only and return zeroes
when read. The configuration software must initialize this register. For the purpose of address
decode, address bits A[19:0] are assumed to be 0. Thus, the bottom of the defined memory
address range will be aligned to a 1-MB boundary.
15:4 R/W Memory Address Base (MBASE): This field corresponds to A[31:20] of the
FFFh lower limit of the memory range that will be passed to PCI Express*.
3:0 Reserved
This register controls the processor-to-PCI Express non-prefetchable memory access routing
based on the following formula:
The upper 12 bits of the register are read/write and correspond to the upper 12 address bits
A[31:20] of the 32-bit address. The bottom 4 bits of this register are read-only and return zeroes
when read. The configuration software must initialize this register. For the purpose of address
decode, address bits A[19:0] are assumed to be FFFFFh. Thus, the top of the defined memory
address range will be at the top of a 1-MB aligned memory block.
Note: Memory range covered by MBASE and MLIMIT Registers are used to map non-pre-fetchable
PCI Express address ranges (typically, where control/status memory-mapped I/O data structures
of the Graphics Controller will reside) and PMBASE and PMLIMIT are used to map pre-
fetchable address ranges (typically, graphics local memory).
This segregation allows application of USWC space attribute to be performed in a true plug-and-
play manner to the pre-fetchable address range for improved processor -to-PCI Express memory
access performance.
Note: Configuration software is responsible for programming all address range registers (pre-fetchable,
non-prefetchable) with the values that provide exclusive address ranges (i.e., prevent overlap with
each other and/or with the ranges covered with the main memory). There is no provision in the
MCH hardware to enforce prevention of overlap and operations of the system in the case of
overlap are not ensured.
15:4 R/W Memory Address Limit (MLIMIT): This field corresponds to A[31:20] of the
000h upper limit of the address range passed to PCI Express*.
3:0 Reserved
This register, in conjunction with the corresponding Upper Base Address register, controls the
processor-to-PCI Express prefetchable memory access routing based on the following formula:
The upper 12 bits of this register are read/write and correspond to address bits A[31:20] of the 40-
bit address. The lower 8 bits of the Upper Base Address register are read/write and correspond to
address bits A[39:32] of the 40-bit address. The configuration software must initialize this
register. For the purpose of address decode, address bits A[19:0] are assumed to be 0. Thus, the
bottom of the defined memory address range will be aligned to a 1-MB boundary.
15:4 R/W Prefetchable Memory Base Address (MBASE): This field corresponds to
FFFh A[31:20] of the lower limit of the memory range that will be passed to PCI
Express*.
3:0 RO 64-bit Address Support: This field indicates that the upper 32-bits of the
1h prefetchable memory region limit address are contained in the Prefetchable
Memory Base Limit Address Register (offset 2Ch).
This register, in conjunction with the corresponding Upper Limit Address register, controls the
processor-to-PCI Express prefetchable memory access routing based on the following formula:
The upper 12 bits of this register are read/write and correspond to address bits A[31:20] of the 40-
bit address. The lower 8 bits of the Upper Limit Address register are read/write and correspond to
address bits A[39:32] of the 40-bit address. The configuration software must initialize this
register. For the purpose of address decode, address bits A[19:0] are assumed to be FFFFFh.
Thus, the top of the defined memory address range will be at the top of a 1-MB aligned memory
block. Note that prefetchable memory range is supported to allow segregation by the
configuration software between the memory ranges that must be defined as UC and the ones that
can be designated as a USWC (i.e. prefetchable) from the processor perspective.
15:4 R/W Prefetchable Memory Address Limit (PMLIMIT): This field corresponds to
000h A[31:20] of the upper limit of the address range passed to PCI Express*.
3:0 RO 64-bit Address Support: This field indicates that the bridge has 32-bit address
0h support only.
This register, in conjunction with the corresponding Upper Base Address register, controls the
processor-to-PCI Express prefetchable memory access routing based on the following formula:
The upper 12 bits of this register are read/write and correspond to address bits A[31:20] of the 40-
bit address. The lower 8 bits of the Upper Base Address register are read/write and correspond to
address bits A[39:32] of the 40-bit address. This register must be initialized by the configuration
software. For the purpose of address decode, address bits A[19:0] are assumed to be 0. Thus, the
bottom of the defined memory address range will be aligned to a 1-MB boundary.
3:0 R/W Prefetchable Memory Base Address (MBASEU): This field corresponds to
Fh A[35:32] of the lower limit of the prefetchable memory range that will be passed
to PCI Express.
This register, in conjunction with the corresponding Upper Limit Address register, controls the
processor-to-PCI Express prefetchable memory access routing based on the following formula:
The upper 12 bits of this register are read/write and correspond to address bits A[31:20] of the 40-
bit address. The lower 8 bits of the Upper Limit Address register are read/write and correspond to
address bits A[39:32] of the 40-bit address. This register must be initialized by the configuration
software. For the purpose of address decode, address bits A[19:0] are assumed to be FFFFFh.
Thus, the top of the defined memory address range will be at the top of a 1 MB aligned memory
block.
Note: Prefetchable memory range is supported to allow segregation by the configuration software
between the memory ranges that must be defined as UC and the ones that can be designated as a
USWC (i.e. prefetchable) from the processor perspective.
3:0 R/W Prefetchable Memory Address Limit (MLIMITU): This field corresponds to
0h A[35:32] of the upper limit of the prefetchable Memory range that will be passed to
PCI Express.
7:0 RO First Capability (CAPPTR1): The first capability in the list is the Subsystem ID
88h and Subsystem Vendor ID Capability.
7:0 R/W Interrupt Connection. This field communicates interrupt line routing information.
00h POST software writes the routing information into this register as it initializes and
configures the system. The value in this register indicates which input of the
system interrupt controller is connected to this device’s interrupt pin.
7:0 RO Interrupt Pin. As a single function device, the PCI Express* device specifies
01h INTA as its interrupt pin.
01h=INTA.
This register provides extensions to the PCICMD1 Register that are specific to PCI-to-PCI
bridges. The BCTRL provides additional control for the secondary interface (i.e., PCI Express) as
well as some bits that affect the overall behavior of the “virtual” Host-PCI Express bridge in the
MCH (e.g., VGA compatible address ranges mapping).
15:12 Reserved
6 R/W Secondary Bus Reset (SRESET): Setting this bit triggers a hot reset on the
0b corresponding PCI Express* Port.
5 RO Master Abort Mode (MAMODE): When acting as a master, unclaimed reads that
0b experience a master abort returns all 1s and any writes that experience a master
abort completes normally and the data is discarded. Hardwired to 0.
4 R/W VGA 16-bit Decode: This bit enables the PCI-to-PCI bridge to provide 16-bit
0b decoding of VGA I/O address precluding the decoding of alias addresses every
1 KB. This bit only has meaning if bit 3 (VGA Enable) of this register is also 1,
enabling VGA I/O decoding and forwarding by the bridge.
0 = Execute 10-bit address decodes on VGA I/O accesses.
1 = Execute 16-bit address decodes on VGA I/O accesses.
3 R/W VGA Enable (VGAEN): This bit controls the routing of processor-initiated
0b transactions targeting VGA compatible I/O and memory address ranges. See the
VGAEN/MDAP table in Device 0, offset 97h[0]. See the VGAEN/MDAP table in
the LAC Register[0] (Device 0, offset 97h).
2 R/W ISA Enable (ISAEN): This bit is needed to exclude legacy resource decode to
0b route ISA resources to legacy decode path. This bit modifies the response by the
MCH to an I/O access issued by the processor that target ISA I/O addresses.
This applies only to I/O addresses that are enabled by the IOBASE and IOLIMIT
registers.
0 = All addresses defined by the IOBASE and IOLIMIT for processor I/O
transactions will be mapped to PCI Express.
1 = MCH will not forward to PCI Express any I/O transactions addressing the last
768 bytes in each 1-KB block even if the addresses are within the range
defined by the IOBASE and IOLIMIT registers. Instead of going to PCI
Express these cycles will be forwarded to DMI where they can be
subtractively or positively claimed by the ISA bridge.
0 RO Parity Error Response Enable (PEREN): This bit controls whether or not the
0b Master Data Parity Error bit in the Secondary Status register is set when the
MCH receives across the link (upstream) a Read Data Completion Poisoned TLP
0 = Disable. Master Data Parity Error bit in Secondary Status register cannot be
set.
1 = Enable. Master Data Parity Error bit in Secondary Status register can be set..
31:27 RO PME Support: This field indicates the power states in which this device may
19h indicate PME wake via PCI Express messaging. D0, D3hot, and D3cold. This
device is not required to do anything to support D3hot and D3cold; it simply must
report that those states are supported. Refer to the PCI Power Management
Interface Specification, Revision 1.1 for encoding explanation and other power
management details.
24:22 RO Auxiliary Current: Hardwired to 0 to indicate that there are no 3.3 Vaux auxiliary
000b current requirements.
19 RO PME Clock: Hardwired to 0 to indicate this device does NOT support PME#
0b generation.
18:16 RO PCI PM CAP Version: Hardwired to 02h to indicate there are 4 bytes of power
010b management registers implemented and that this device complies with revision
1.1 of the PCI Power Management Interface Specification.
15:8 RO Pointer to Next Capability: This contains a pointer to the next item in the
90h / A0h capabilities list. If MSICH (CAPL[0] @ 7Fh) is 0, then the next item in the
capabilities list is the Message Signaled Interrupts (MSI) capability at 90h. If
MSICH (CAPL[0] @ 7Fh) is 1, then the next item in the capabilities list is the PCI
Express* capability at A0h.
7:0 RO Capability ID: The value of 01h identifies this linked list item (capability
01h structure) as being for PCI Power Management registers.
31:16 Reserved
15 RO PME Status: This bit indicates that this device does not support PME#
0b generation from D3cold.
14:13 RO Data Scale: This field indicates that this device does not support the power
00b management data register.
12:9 RO Data Select: Indicates that this device does not support the power management
0h data register.
8 R/W/S PME Enable: Indicates that this device does not generate PME# assertion from
0b any D-state.
0 = PME# generation not possible from any D State
1 = PME# generation enabled from any D State
The setting of this bit has no effect on hardware. See PM_CAP[15:11]
7:2 Reserved
1:0 R/W Power State: This field indicates the current power state of this device and can
00b be used to set the device into a new power state. If software attempts to write an
unsupported state to this field, write operation must complete normally on the
bus, but the data is discarded and no state change occurs.
00 = D0
01 = D1 (Not supported in this device.)
10 = D2 (Not supported in this device.)
11 = D3
Support of D3cold does not require any special action.
While in the D3hot state, this device can only act as the target of PCI
configuration transactions (for power management control). This device also
cannot generate interrupts or respond to MMR cycles in the D3 state. The
device must return to the D0 state in order to be fully functional.
There is no hardware functionality required to support these Power States.
This capability is used to uniquely identify the subsystem where the PCI device resides. Because
this device is an integrated part of the system and not an add-in device, it is anticipated that this
capability will never be used. However, it is necessary because Microsoft will test for its
presence.
31:16 Reserved
15:8 RO Pointer to Next Capability: This contains a pointer to the next item in the
80h capabilities list which is the PCI Power Management capability.
7:0 RO Capability ID: The value of 0Dh identifies this linked list item (capability
0Dh structure) as being for SSID/SSVID registers in a PCI-to-PCI Bridge.
System BIOS can be used as the mechanism for loading the SSID/SVID values. These values
must be preserved through power management transitions and hardware reset.
31:16 R/WO Subsystem ID (SSID): This field identifies the particular subsystem and is
0000h assigned by the vendor.
15:0 R/WO Subsystem Vendor ID (SSVID): This field identifies the manufacturer of the
8086h subsystem and is the same as the vendor ID that is assigned by the PCI Special
Interest Group.
When a device supports MSI, it can generate an interrupt request to the processor by writing a
predefined data item (a message) to a predefined memory address.
The reporting of the existence of this capability can be disabled by setting MSICH (CAPL[0] @
7Fh). In that case walking this linked list will skip this capability and instead go directly from the
PCI PM capability to the PCI Express capability.
15:8 RO Pointer to Next Capability: This field contains a pointer to the next item in the
A0h capabilities list which is the PCI Express* capability.
7:0 RO Capability ID: The value of 05h identifies this linked list item (capability structure)
05h as being for MSI registers.
System software can modify bits in this register, but the device is prohibited from doing so.
If the device writes the same message multiple times, only one of those messages will be
serviced. If all of them must be serviced, the device must not generate the same message again
until the driver services the earlier one.
15:8 Reserved
7 RO 64-bit Address Capable: Hardwired to 0 to indicate that the function does not
0b implement the upper 32 bits of the Message Address register and is incapable of
generating a 64-bit memory address.
6:4 R/W Multiple Message Enable (MME): System software programs this field to
000b indicate the actual number of messages allocated to this device. This number will
be equal to or less than the number actually requested. The encoding is the
same as for the MMC field below.
3:1 RO Multiple Message Capable (MMC): System software reads this field to
000b determine the number of messages being requested by this device.
000 = 1
001–111 = Reserved
0 R/W MSI Enable (MSIEN) Controls the ability of this device to generate MSIs.
0b
0 = MSI will not be generated.
1 = MSI will be generated when MCH receive PME or HotPlug messages. INTA
will not be generated and INTA Status (PCISTS1[3]) will not be set.
31:2 R/W Message Address: This field is used by system software to assign a MSI
00000000h address to the device. The device handles an MSI by writing the padded
contents of the MD register to this address.
15:0 R/W Message Data: Base message data pattern assigned by system software and
0000h used to handle an MSI from the device.
When the device must generate an interrupt request, it writes a 32-bit value to the
memory address specified in the MA Register. The upper 16 bits are always set to
0. This register supplies the lower 16 bits.
15:8 RO Pointer to Next Capability: This value terminates the capabilities list. The Virtual
00h Channel capability and any other PCI Express* specific capabilities that are
reported via this mechanism are in a separate capabilities list located entirely
within PCI Express extended configuration space.
7:0 RO Capability ID: This field identifies this linked list item (capability structure) as
10h being for PCI Express registers.
15:14 Reserved
7:4 RO Device/Port Type: Hardwired to 0100b to indicate root port of PCI Express Root
4h Complex.
31:6 Reserved
5 RO Extended Tag Field Supported: Hardwired to indicate support for 5-bit Tags as
0b a Requestor.
2:0 RO Max Payload Size: Hardwired to indicate 128B maximum supported payload for
000b Transaction Layer Packets (TLP).
This register provides control for PCI Express device specific capabilities.
Note: The error reporting enable bits are in reference to errors detected by this device, not error
messages received across the link. The reporting of error messages (ERR_CORR,
ERR_NONFATAL, ERR_FATAL) received by Root Port is controlled exclusively by Root Port
Command Register.
15:8 Reserved
4 Reserved
This register reflects status corresponding to controls in the Device Control register.
Note: The error reporting bits are in reference to errors detected by this device, not error messages
received across the link.
15:6 Reserved
5 RO Transactions Pending:
0b
0 = All pending transactions (including completions for any outstanding non-
posted requests on any used virtual channel) have been completed.
1 = Indicates that the device has transaction(s) pending (including completions
for any outstanding non-posted requests for all used Traffic Classes).
4 Reserved
2 R/WC Fatal Error Detected: When Advanced Error Handling is enabled, errors are
0b logged in this register regardless of the settings of the Correctable Error Mask
Register.
0 = Fatal Error Not detected.
1 = Indicates that fatal error(s) were detected. Errors are logged in this register
regardless of whether error reporting is enabled or not in the Device Control
Register.
1 R/WC Non-Fatal Error Detected: When Advanced Error Handling is enabled, errors are
0b logged in this register regardless of the settings of the Correctable Error Mask
Register.
0 = Non-fatal error Not detected.
1 = Indicates that non-fatal error(s) were detected. Errors are logged in this
register regardless of whether error reporting is enabled or not in the Device
Control Register.
0 R/WC Correctable Error Detected: When Advanced Error Handling is enabled, errors
0b are logged in this register regardless of the settings of the Correctable Error Mask
Register.
0 = Correctable error Not detected.
1 = Indicates that correctable error(s) were detected. Errors are logged in this
register regardless of whether error reporting is enabled or not in the Device
Control Register.
31:24 RO Port Number: This field indicates the PCI Express* port number for the given PCI
02h Express link. The field matches the value in Element Self Description [31:24].
23:18 Reserved
17:15 R/WO L1 Exit Latency: This field indicates the length of time this Port requires to
010b complete the transition from L1 to L0. The value 010 b indicates the range of 2 µs
to less than 4 µs. If this field is required to be any value other than the default,
BIOS must initialize it accordingly.
Both bytes of this register that contain a portion of this field must be written
simultaneously to prevent an intermediate (and undesired) value from ever
existing.
14:12 R/WO L0s Exit Latency: This field indicates the length of time this Port requires to
010b complete the transition from L0s to L0. The value 010 b indicates the range of 128
ns to less than 256 ns. If this field is required to be any value other than the
default, BIOS must initialize it accordingly.
15:7 Reserved
5 R/W Retrain Link: This bit always returns 0 when read. This bit is cleared
0b automatically (no need to write a 0).
0 = Normal operation
1 = Full Link retraining is initiated by directing the Physical Layer LTSSM from L0,
L0s, or L1 states to the Recovery state.
4 R/W Link Disable: Link retraining happens automatically on 0 to 0 transition, just like
0b when coming out of reset. Writes to this bit are immediately reflected in the value
read from the bit, regardless of actual Link state.
0 = Normal operation
1 = Link is disabled. Forces the LTSSM to transition to the Disabled state (via
Recovery) from L0, L0s, or L1 states.
2 Reserved
1:0 R/W Active State PM: This field controls the level of active state power management
00b supported on the given link.
00 = Disabled
01 = L0s Entry Supported
10 = Reserved
11 = L0s and L1 Entry Supported
15:13 Reserved
11 RO Link Training: This bit indicates that Link training is in progress. Hardware clears
0b this bit once Link training is complete.
31:19 R/WO Physical Slot Number: This field indicates the physical slot number attached to
0000h this Port. This field must be initialized by BIOS to a value that assigns a slot
number that is globally unique within the chassis.
18:17 Reserved
16:15 R/WO Slot Power Limit Scale: This field specifies the scale used for the Slot Power
00b Limit Value. If this field is written, the link sends a Set_Slot_Power_Limit
message.
00 = 1.0x
01 = 0.1x
10 = 0.01x
11 = 0.001x
14:7 R/WO Slot Power Limit Value: This field, in combination with the Slot Power Limit
00h Scale value, specifies the upper limit on power supplied by slot. Power limit (in
Watts) is calculated by multiplying the value in this field by the value in the Slot
Power Limit Scale field. If this field is written, the link sends a
Set_Slot_Power_Limit message.
6 R/WO Hot-plug Capable: This bit indicates that this slot is capable of supporting Hot-
0b plug operations.
0 = Not capable
1 =Capable
5 R/WO Hot-plug Surprise: This bit indicates that a device present in this slot might be
0b removed from the system without any prior notification.
0 = No Hot-plug Surprise
1 = Hot plug Surprise capable.
4 R/WO Power Indicator Present: This bit indicates that a Power Indicator is
0b implemented on the chassis for this slot.
0 = Not Present
1 = Present
3 R/WO Attention Indicator Present: This bit indicates that an Attention Indicator is
0b implemented on the chassis for this slot.
0 = Not Present
1 = Present
2:1 Reserved
0 R/WO Attention Button Present: This bit indicates that an Attention Button is
0b implemented on the chassis for this slot. The Attention Button allows the user to
request hot-plug operations.
0 = Not Present
1 = Present
PCI Express slot related registers allow for the support of Hot-Plug.
15:10 Reserved
9:8 R/W Power Indicator Control: Reads to this register return the current state of the
01b Power Indicator. Writes to this register set the Power Indicator and cause the
Port to send the appropriate POWER_INDICATOR_* messages.
00 = Reserved
01 = On
10 = Blink
11 = Off
7:6 R/W Attention Indicator Control: Reads to this register return the current state of the
11b Attention Indicator. Writes to this register set the Attention Indicator and cause
the Port to send the appropriate ATTENTION_INDICATOR_* messages.
00 = Reserved
01 = On
10 = Blink
11 = Off
2:1 Reserved
15:7 Reserved
6 RO Presence Detect State: This bit indicates the presence of a card in the slot.
Xb
0 = Slot Empty
1 = Card Present in slot.
5 Reserved
2:1 Reserved
This register allows control of PCI Express Root Complex specific parameters. The system error
control bits in this register determine if corresponding SERRs are generated when the device
detects an error (reported in this device’s Device Status register) or when an error message is
received across the link. Reporting of SERR as controlled by these bits takes precedence over the
SERR Enable in the PCI Command Register.
15:4 Reserved
2 R/W System Error on Fatal Error Enable: This bit controls the Root Complex’s
0b response to fatal errors.
0 = Disable. No SERR generated on receipt of fatal error.
1 = Indicates that an SERR should be generated if a fatal error is reported by
any of the devices in the hierarchy associated with this Root Port, or by the
Root Port itself.
1 R/W System Error on Non-Fatal Uncorrectable Error Enable: This bit controls the
0b Root Complex’s response to non-fatal errors.
0 = Disable. No SERR generated on receipt of non-fatal error.
1 = Indicates that an SERR should be generated if a non-fatal error is reported
by any of the devices in the hierarchy associated with this Root Port, or by
the Root Port itself.
0 R/W System Error on Correctable Error Enable: This bit controls the Root
0b Complex’s response to correctable errors.
0 = Disable. No SERR generated on receipt of correctable error.
1 = Indicates that an SERR should be generated if a correctable error is
reported by any of the devices in the hierarchy associated with this Root
Port, or by the Root Port itself.
This register provides information about PCI Express Root Complex specific parameters.
31:18 Reserved
17 RO PME Pending:
0b
0 = PME Not pending.
1 = Another PME is pending when the PME Status bit is set. When the PME
Status bit is cleared by software; the PME is delivered by hardware by
setting the PME Status bit again and updating the Requestor ID
appropriately. The PME pending bit is cleared by hardware if no more
PMEs are pending.
15:0 RO PME Requestor ID: This field indicates the PCI requestor ID of the last PME
0000h requestor.
This field controls functionality that is needed by Legacy (non-PCI Express aware) operating
systems during run time.
31:3 RO Reserved
0000
0000h
Note: Extended capability structures for PCI Express devices are located in PCI Express extended
configuration space and have different field definitions than standard PCI capability structures.
31:20 RO Pointer to Next Capability: The Link Declaration Capability is the next in the PCI
140h Express* extended capabilities list.
15:0 RO Extended Capability ID: Value of 0002h identifies this linked list item (capability
0002h structure) as being for PCI Express Virtual Channel registers.
This register describes the configuration of PCI Express Virtual Channels associated with this
port.
31:7 Reserved
6:4 RO Low Priority Extended VC Count: This field indicates the number of (extended)
000b Virtual Channels in addition to the default VC belonging to the low-priority VC
(LPVC) group that has the lowest priority with respect to other VC resources in a
strict-priority VC Arbitration.
The value of 0 in this field implies strict VC arbitration.
3 Reserved
2:0 R/WO Extended VC Count: This field indicates the number of (extended) Virtual
001b Channels in addition to the default VC supported by the device.
BIOS Requirement: Set this field to 000b for all configurations.
This register describes the configuration of PCI Express Virtual Channels associated with this
port.
31:24 RO VC Arbitration Table Offset: This field indicates the location of the VC Arbitration
00h Table. This field contains the zero-based offset of the table in DQWORDS (16
bytes) from the base address of the Virtual Channel Capability Structure. A value
of 0 indicates that the table is not present (due to fixed VC priority).
23:8 Reserved
7:0 RO VC Arbitration Capability: This field indicates that the only possible VC
01h arbitration scheme is hardware fixed (in the root complex).
VC1 is the highest priority, VC0 is the lowest priority.
15:4 Reserved
3:1 R/W VC Arbitration Select: This field will be programmed by software to the only
000b possible value as indicated in the VC Arbitration Capability field. The value 001b
when written to this field will indicate the VC arbitration scheme is hardware fixed
(in the root complex).
This field can not be modified when more than one VC in the LPVC group is
enabled.
0 Reserved
31:16 Reserved
14:0 Reserved
31 RO VC0 Enable: For VC0, this is hardwired to 1 and read only as VC0 can never be
1b disabled.
30:27 Reserved
26:24 RO VC0 ID: This field assigns a VC ID to the VC resource. For VC0, this is hardwired
000b to 0 and read only.
23:8 Reserved
7:1 R/W TC/VC0 Map: This field indicates the TCs (Traffic Classes) that are mapped to
7Fh the VC resource. Bit locations within this field correspond to TC values. For
example, when bit 7 is set in this field, TC7 is mapped to this VC resource. When
more than one bit in this field is set, it indicates that multiple TCs are mapped to
the VC resource. In order to remove one or more TCs from the TC/VC Map of an
enabled VC, software must ensure that no new or outstanding transactions with
the TC labels are targeted at the given Link.
15:2 Reserved
1 RO VC0 Negotiation Pending: This bit indicates the status of the process of Flow
1b Control initialization. It is set by default on Reset, as well as when the
corresponding Virtual Channel is Disabled or the Link is in the DL_Down state. It is
cleared when the link successfully exits the FC_INIT2 state.
0 = The VC negotiation is complete.
1 = The VC resource is still in the process of negotiation (initialization or
disabling).
Before using a Virtual Channel, software must check whether the VC Negotiation
Pending fields for that Virtual Channel are cleared in both Components on a Link.
0 Reserved
31:16 Reserved
14:0 Reserved
NOTES:
1. To enable a Virtual Channel, the VC Enable bits for that Virtual Channel
must be set in both Components on a Link.
2. To disable a Virtual Channel, the VC Enable bits for that Virtual Channel
must be cleared in both Components on a Link.
3. Software must ensure that no traffic is using a Virtual Channel at the time it
is disabled.
4. Software must fully disable a Virtual Channel in both Components on a Link
before re-enabling the Virtual Channel.
BIOS Requirement: This field must not be set to 1b. VC1 is not a POR feature.
30:27 Reserved
26:24 R/W VC1 ID: This field assigns a VC ID to the VC resource. Assigned value must be
001b non-zero.
This field cannot be modified when the VC is already enabled.
23:8 Reserved
7:1 R/W TC/VC1 Map: This field indicates the TCs (Traffic Classes) that are mapped to the
00h VC resource. Bit locations within this field correspond to TC values. For example,
when bit 7 is set in this field, TC7 is mapped to this VC resource. When more than
one bit in this field is set, it indicates that multiple TCs are mapped to the VC
resource. To remove one or more TCs from the TC/VC Map of an enabled VC,
software must ensure that no new or outstanding transactions with the TC labels
are targeted at the given Link.
15:2 Reserved
1 RO VC1 Negotiation Pending: This bit indicates the status of the process of Flow
Control initialization. It is set by default on Reset, as well as when the
1b
corresponding Virtual Channel is Disabled or the Link is in the DL_Down state. It is
cleared when the link successfully exits the FC_INIT2 state.
0 = The VC negotiation is complete.
1 = The VC resource is still in the process of negotiation (initialization or disabling).
Before using a Virtual Channel, software must check whether the VC Negotiation
Pending fields for that Virtual Channel are cleared in both Components on a Link.
0 Reserved
This capability declares links from this element (PCI Express) to other elements of the root
complex component to which it belongs. See the PCI Express specification for link/topology
declaration requirements.
31:20 RO Pointer to Next Capability: This is the last capability in the PCI Express*
000h extended capabilities list
15:0 RO Extended Capability ID: Value of 0005 h identifies this linked list item (capability
0005h structure) as being for PCI Express Link Declaration Capability.
Note: See corresponding Egress Port Link Declaration Capability registers for diagram of Link
Declaration Topology.
This register provides information about the root complex element containing this Link
Declaration Capability.
31:24 RO Port Number: This field specifies the port number associated with this element
02h with respect to the component that contains this element. The egress port of the
component to provide arbitration to this Root Complex Element uses this port
number value.
23:16 R/WO Component ID: This field identifies the physical component that contains this
00h Root Complex Element. Component IDs start at 1.
This value is a mirror of the value in the Component ID field of all elements in this
component. The value only needs to be written in one of the mirrored fields and it
will be reflected everywhere that it is mirrored.
15:8 RO Number of Link Entries: This field identifies the number of link entries following
01h the Element Self Description. This field reports 1 (to Egress port only as no peer-
to-peer capabilities are reported in this topology).
7:4 Reserved
3:0 RO Element Type: This field identifies the type of the Root Complex Element.
0h
Value of 0h represents a root port.
This register provides the first part of a Link Entry that declares an internal link to another Root
Complex Element.
31:24 RO Target Port Number: This field specifies the port number associated with the
00h element targeted by this link entry (Egress Port). The target port number is with
respect to the component that contains this element as specified by the target
component ID.
23:16 R/WO Target Component ID: This field identifies the physical or logical component that
00h is targeted by this link entry. A value of 0 is reserved; Component IDs start at 1.
This value is a mirror of the value in the Component ID field of all elements in this
component. The value only needs to be written in one of the mirrored fields and it
will be reflected everywhere that it is mirrored.
15:2 Reserved
1 RO Link Type: This field identifies that the link points to memory-mapped space (for
0b RCRB). The link address specifies the 64-bit base address of the target RCRB.
This register contains the second part of a Link Entry that declares an internal link to another Root
Complex Element.
63:32 Reserved
31:12 R/WO Link Address: This field contains the memory mapped base address of the
0 0000h RCRB that is the target element (Egress Port) for this link entry.
11:0 Reserved
This register reports error status of individual error sources on a PCI Express device. An
individual error status bit that is set indicates that a particular error occurred. Software clears an
error status by writing a 1 to the respective bit.
31:21 RO Reserved
000h
19 RO Reserved
0b
15 RO Reserved
0b
13:5 RO Reserved
0b
4 R/WC/S Data Link Protocol Error Status (DLPES): The Data Link Layer Protocol Error
0b that causes this bit to be set will also cause the Fatal Error Detected bit in
Device Status[2] to be set if not already set.
3:0 RO Reserved
000b
This register controls reporting of individual errors by the device (or logic associated with this
port) to the PCI Express Root Complex. As these errors are not originating on the other side of a
PCI Express link, no PCI Express error message is sent, but the unmasked error is reported
directly to the root control logic. A masked error (respective bit set to 1 in the mask register) has
no action taken. There is a mask bit per error bit of the Uncorrectable Error Status register.
31:2 RO Reserved
1 000h
19 RO Reserved
0b
15 RO Reserved
0b
13:5 RO Reserved
0b
3:0 RO Reserved
000b
This register reports error status of individual error sources on a PCI Express device. An
individual error status bit that is set indicates that a particular error occurred. Software may clear
an error status by writing a 1 to the respective bit.
31:13 RO Reserved
00000h
11:9 RO Reserved
000b
5:1 RO Reserved
00h
0 R/WC/S Receiver Error Status (RES): Receiver Errors will be indicated due to all of the
0b following: 8b/10b Decode Errors, Framing Errors, Lane Deskew Errors, and
Elasticity Buffer Overflow/Underflow.
0 = Error did Not occur
1 = Error occurred
This register controls reporting of individual correctable errors by the device (or logic associated
with this port) to the PCI Express Root Complex. As these errors are not originating on the other
side of a PCI Express link, no PCI Express error message is sent, but the unmasked error is
reported directly to the root control logic. A masked error (respective bit set to 1 in the mask
register) has no action taken. There is a mask bit per error bit of the Correctable Error Status
register.
31:13 RO Reserved
00000h
11:9 RO Reserved
000b
5:1 RO Reserved
00h
PCI Express status reporting that is required by the PCI Express specification.
63:60 Reserved
59:48 RO Next Transmit Sequence Number: This field contains the value of the
000h NXT_TRANS_SEQ counter. This counter represents the transmit Sequence
number to be applied to the next TLP to be transmitted onto the Link for the first
time.
47:44 Reserved
43:32 RO Next Packet Sequence Number: This field contains the packet sequence
000h number to be applied to the next TLP to be transmitted or re-transmitted onto the
Link.
31:28 Reserved
27:16 RO Next Receive Sequence Number: This is the sequence number associated with
000h the TLP that is expected to be received next.
15:12 Reserved
Note: IMPORTANT: All RCRB register spaces needs to remain organized as shown here.
31:20 RO Pointer to Next Capability: This field indicates the next item in the list.
040h
15:0 RO Capability ID: This field indicates this is the Virtual Channel capability item.
0002h
This register describes the configuration of Virtual Channels associated with this port.
31:12 Reserved
11:10 RO Port Arbitration Table Entry Size (PATS): This field indicates the size of the
00b port arbitration table is 4 bits (to allow up to 8 ports).
7 Reserved
6:4 RO Low Priority Extended VC Count (LPEVC): This field indicates that there are
000b no additional VCs of low priority with extended capabilities.
3 Reserved
2:0 R/WO Extended VC Count: This field indicates that there is one additional VC (VC1)
001b that exists with extended capabilities.
This register describes the configuration of Virtual Channels associated with this port.
31:24 RO VC Arbitration Table Offset (ATO): This field indicates that no table is present
00h for VC arbitration since it is fixed.
23:8 Reserved
7:0 RO VC Arbitration Capability: This field indicates that the VC arbitration is fixed in
01h the root complex. VC1 is highest priority and VC0 is lowest priority.
15:4 Reserved
3:1 R/W VC Arbitration Select: This field indicates which VC should be programmed in
000b the VC arbitration table. The root complex takes no action on the setting of this
field since there is no arbitration table.
0 RO Reserved
0b
31:23 Reserved
22:16 RO Maximum Time Slots (MTS): This VC implements fixed arbitration; therefore,
00h this field is not used.
15 RO Reject Snoop Transactions (RTS): This VC must be able to take snoopable
0b transactions.
14:8 Reserved
7:0 RO Port Arbitration Capability (PAC): This field indicates that this VC uses fixed
01h port arbitration..
This register controls the resources associated with PCI Express Virtual Channel 0.
15:2 Reserved
0 Reserved
31:16 Reserved
14:8 Reserved
7:0 RO Port Arbitration Capability (PAC): This field indicates the port arbitration
01h capability is time-based WRR of 128 phases.
26:24 R/W Virtual Channel Identifier (ID): This field indicates the ID to use for this virtual
001b channel.
23:20 Reserved
19:17 R/W Port Arbitration Select (PAS): This field indicates which port table is being
0h programmed. The only permissible value of this field is 4h for the time-based
WRR entries.
16:8 Reserved
7:1 R/W Transaction Class / Virtual Channel Map (TVM): This field indicates which
00h transaction classes are mapped to this virtual channel. When a bit is set, this
transaction class is mapped to the virtual channel.
0 Reserved
15:2 Reserved
0 Reserved
31:18 Reserved
14:12 R/WO L0s Exit Latency (EL0): This field indicates that exit latency is 128 ns to less
010b than 256 ns.
11:10 RO Active State Link PM Support (APMS): This field indicates that L0s is supported
11b on DMI.
9:4 RO Maximum Link Width (MLW): This field indicates the maximum link width is 4
4h ports.
3:0 RO Maximum Link Speed (MLS): This field indicates the link speed is 2.5 Gb/s.
1h
15:8 Reserved
6:2 Reserved
1:0 R/W Active State Link PM Control (APMC): This field indicates whether DMI should
00b enter L0s.
00 = Disabled
01 = L0s entry enabled
10 = Reserved
11 = Reserved
15:10 Reserved
This register reports error status of individual uncorrectable error sources on DMI. An individual
error status bit that is set indicates that a particular error occurred. Software can clear an error
status by writing a 1 to the respective bit.
31:21 RO Reserved
000h
19 RO Reserved
0b
15 RO Reserved
0b
13:5 RO Reserved
0b
3:0 RO Reserved
000b
This register controls reporting of individual uncorrectable errors over DMI. A masked error
(respective bit set to 1 in the mask register) has no action taken. There is a mask bit per error bit
of the DMIUESTS Register.
31:21 RO Reserved
000h
19 RO Reserved
0b
15 RO Reserved
0b
13:5 RO Reserved
00h
3:0 RO Reserved
000b
This register reports error status of individual correctable error sources on DMI. An individual
error status bit that is set indicates that a particular error occurred. Software can clear an error
status by writing a 1 to the respective bit.
31:13 RO Reserved
00000h
11:9 RO Reserved
000b
5:1 RO Reserved
00h
0 R/WC/S Receiver Error Status (RES): Receiver errors will be indicated due to all of the
0b following: 8b/10b Decode Errors, Framing Errors, Lane Deskew Errors, and
Elasticity Buffer Overflow/Underflow.
0 = Error did Not occur
1 = Error occurred
• All of these ranges MUST be unique and NON-OVERLAPPING. It is the BIOS or system
designer’s responsibility to limit memory population so that adequate PCI, PCI Express, High
BIOS, PCI Express memory-mapped space, and APIC memory space can be allocated.
• In the case of overlapping ranges with memory, the memory decode will be given priority.
• There are NO Hardware Interlocks to prevent problems in the case of overlapping ranges.
• Accesses to overlapped ranges may produce indeterminate results.
• The only peer-to-peer cycles allowed below the top of memory (TOLUD Register) are DMI-
to-PCI Express VGA range writes.
PCI Memory
Address Range Device 1 PMUbase/PMUlimit
Remap Limit
Main Memory
Address Range Remap Base/Limit
TOM
Main Memory
Address Range
4 GB
Device 0 Device 0 Device 1
PCI Memory Bars GGC Bars
Address Range (EPBAR, (Graphics (MBASE1/
(Subtractively MCHBAR, Stolen MLIMIT1,
decoded to DMI) PCIEXBAR, Memory) PMBASE1/
DMIBAR) PMLIMIT1)
TOLUD
Main Memory Independently Programmable
Address Range Non-Overlapping Windows
1 MB
Legacy Address
Range
0
Sys_Address_Ranges_955X
000F_FFFFh 1 MB
System BIOS (Upper)
64 KB
000F_0000h 960 KB
000E_FFFFh Extended System BIOS
(Lower)
000E_0000h 64 KB (16 KB x 4) 896 KB
000D_FFFFh
Expansion Area
128 KB (16 KB x 8)
000C_0000h
768 KB
000B_FFFFh
Legacy Video Area
(SMM Memory)
128 KB
000A_0000h
0009_FFFFh 640 KB
DOS Area
0000_0000h
MemMap_Legacy
Non-snooped accesses from PCI Express or DMI to this region are always sent to main memory.
Non-snooped accesses from PCI Express or DMI to this region are always sent to main memory.
Non-snooped accesses from PCI Express or DMI to this region are always sent to DRAM.
The MCH does not handle IWB (Implicit Write-Back) cycles targeting DMI. Since all memory
residing on DMI should be set as non-cacheable, there will normally not be IWB cycles targeting
DMI.
However, DMI becomes the default target for processor and DMI originated accesses to disabled
segments of the PAM region. If the MTRRs covering the PAM regions are set to WB or RC it is
possible to get IWB cycles targeting DMI. This may occur for DMI-originated cycles to disabled
PAM regions.
For example, say that a particular PAM region is set for “Read Disabled” and the MTRR
associated with this region is set to WB. A DMI master generates a memory read targeting the
PAM region. A snoop is generated on the FSB and the result is an IWB. Since the PAM region is
“Read Disabled”, the default target for the memory read becomes DMI. The IWB associated with
this cycle will cause the MCH to hang.
The MCH provides a maximum main memory address decode space of 8 GB. The MCH does not
remap APIC or PCI Express memory space. This means that as the amount of physical memory
populated in the system reaches 4 GB, there will be physical memory that exists yet is non-
addressable and, therefore, unusable by the system. The MCH does not limit main memory
address space in hardware.
FFFF_FFFFh 4 GB
Flash
APIC
Contains
programmable PCI Memory Range
windows, ICH7/PCI
ranges.
TOLUD
TSEG (1 MB / 2 MB /
8 MB, optional)
Main Memory
0100_000h 16 MB
ISA Hole (optional)
00F0_000h 15 MB
Main Memory
0010_000h 1 MB
DOS Compatibility
Memory
0h 0 MB
MemMap_MainMemory_955X
Video accelerators originally used this hole. It is also used by validation and customer SV teams
for some of their test cards. That is why it is being supported. There is no inherent BIOS request
for the 15–16-MB window.
7.2.2 TSEG
TSEG is optionally 1 MB, 2 MB, or 8 MB in size. SMM-mode processor accesses to enabled
TSEG, access the physical DRAM at the same address. Non- processor originated accesses are
not allowed to SMM space. PCI Express, and DMI originated cycles to enabled SMM space are
handled as invalid cycle type with reads and writes to location 0 and byte enables turned off for
writes. When the extended SMRAM space is enabled, processor accesses to the TSEG range
without SMM attribute or without WB attribute are also forwarded to memory as invalid accesses.
Non-SMM-mode write-back cycles that target TSEG space are completed to main memory for
cache coherency. When SMM is enabled, the maximum amount of memory available to the
system is equal to the amount of physical DRAM minus the value in the TSEG register that is
fixed at 1 MB, 2 MB, or 8 MB.
Table 7-4. Pre-Allocated Memory Example for 64-MB DRAM, 1-MB VGA and 1-MB TSEG
03E0_0000h – 03EF_FFFFh SMM Mode Only - TSEG Address Range and Pre-allocated
processor Reads Memory
The exceptions listed above for PCI Express ports MUST NOT overlap with APCI configuration,
FSB interrupt space, and High BIOS address range.
FFFF_FFFFh 4 GB
High BIOS
FFE0_0000h 4 GB – 2 MB
DMI Interface
(subtractive decode)
FEF0_0000h 4 GB – 17 MB
FSB Interrupts
FEE0_0000h 4 GB – 18 MB Optional HSEG
DMI Interface
(subtractive decode) FEDA_0000h to
FED0_0000h FEDB_FFFFh
Local (processor) 4 GB – 19 MB
APIC
FEC8_0000h
I/O APIC
FEC0_0000h
4 GB – 20 MB
DMI Interface
(subtractive decode)
F000_0000h
4 GB – 256 MB
E000_0000h
4 GB – 512 MB
Programmable
DMI Interface windows, graphics
(subtractive decode) ranges, PCI Express*
Port could be here
TOLUD
MemMap_PCI
The IOAPIC spaces are used to communicate with IOAPIC interrupt controllers that may be
populated in the system. Since it is difficult to relocate an interrupt controller using plug-and-play
software, fixed address decode regions have been allocated for them. Processor accesses to the
default IOAPIC region (FEC0_0000h to FEC7_FFFFh) are always forwarded to DMI.
The new remap configuration registers exist to reclaim lost main memory space.
Upstream write accesses above 36-bit addressing will be treated as peer writes by PCI Express
and DMI. Upstream read accesses above 36-bit addressing will be treated as invalid cycles by PCI
Express and DMI.
Top of Memory
This “Top of Memory” register reflects the total amount of populated physical memory. This is
also the amount of addressable physical memory when remapping is used to ensure that no
physical memory is wasted. This is NOT necessarily the highest main memory address (holes may
exist in main memory address map due to addresses allocated for memory mapped I/O).
The TOLUD Register is restricted to 4 GB memory (A[31:27]), but the MCH can support up to
8 GB, limited by DRAM pins. For physical memory greater than 4 GB, the TOM Register helps
identify the address range in-between the 4 GB boundary and the top of physical memory. This
identifies memory that can be directly accessed (no remap address calculation) which is useful for
memory access indication, early path indication, and trusted read indication.
C1DRB3 cannot be used directly to determine the effective size of memory as the values
programmed in the DRBs depend on the memory mode (stacked, interleaved). The Remap
Base/Limit registers also can not be used because remapping can be disabled. The TOM Register
is used for early memory channel identification (channel 0 vs. channel 1) in the case of stacked
memory.
In previous generation MCHs, the physical main memory overlapped by the logical address space
allocated to these memory mapped I/O devices was unusable. The result is that a large amount of
physical memory populated in the system is unusable.
The MCH provides the capability to re-claim the physical memory overlapped by the memory
mapped I/O logical address space. The MCH re-maps physical memory from the Top of Low
Memory (TOLUD) boundary up to the 4 GB boundary to an equivalent sized logical address
range located just above the top of physical memory.
Register. The top of the re-map window is defined by the value in the REMAPLIMIT Register.
An address that falls within this window is remapped to the physical memory starting at the
address defined by the TOLUD Register.
The MCH positively decodes memory accesses to PCI Express memory address space as defined
by the following inequalities:
It is essential to support a separate Prefetchable range to apply the USWC attribute (from the
processor point of view) to that range. The USWC attribute is used by the processor for write
combining.
Note that the MCH Device 1 memory range registers described above are used to allocate
memory address space for any PCI Express devices on PCI Express that require such a window.
The PCICMD1 Register can override the routing of memory accesses to PCI Express. In other
words, the memory access enable bit must be set in the device 1 PCICMD1 Register to enable the
memory base/limit and prefetchable base/limit windows.
Note: DMI and PCI Express masters are not allowed to access the SMM space.
Global Enable High Enable TSEG Enable Compatible High (H) TSEG (T)
G_SMRAME H_SMRAM_EN TSEG_EN (C) Range Range Range
0 x X x x Disable Disable
1 0 X 0 0 Disable Disable
1 0 0 0 1 Enable Enable
1 0 0 1 x Enable Enable
1 0 1 0 1 Enable Disable
1 0 1 1 x Invalid Invalid
1 1 X x 0 Disable Disable
1 1 0 x 1 Enable Enable
1 1 1 x 1 Enable Disable
provides addressability for 64 K+3 byte locations. Note that the upper 3 locations can be accessed
only during I/O address wrap-around when the processor bus HA16# address signal is asserted.
HA16# is asserted on the processor bus whenever an I/O access is made to 4 bytes from address
0FFFDh, 0FFFEh, or 0FFFFh. HA16# is also asserted when an I/O access is made to 2 bytes from
address 0FFFFh.
The I/O accesses (other than ones used for configuration space access) are forwarded normally to
the DMI bus unless they fall within the PCI Express I/O address range as defined by the
mechanisms explained below. I/O writes are not posted. Memory writes to ICH7 or PCI Express
are posted. The PCICMD1 Register can disable the routing of I/O cycles to PCI Express.
The MCH responds to I/O cycles initiated on PCI Express or DMI with a UR status. Upstream
I/O cycles and configuration cycles should never occur. If one does occur, the request will route
as a read to memory address 0h so a completion is naturally generated (whether the original
request was a read or write). The transaction will complete with a UR completion status.
For Pentium processors, I/O reads that lie within 8-byte boundaries but cross 4-byte boundaries
are issued from the processor as 1 transaction. The MCH breaks this into 2 separate transactions.
I/O writes that lie within 8-byte boundaries but cross 4-byte boundaries are assumed to be split
into 2 transactions by the processor.
8 Functional Description
This chapter describes the MCH interfaces and major functional units.
HDINV0# HD[15:0]#
HDINV1# HD[31:16]#
HDINV2# HD[47:32]#
HDINV3# HD[63:48]#
When the processor or the MCH drives data, each 16-bit segment is analyzed. If more than 8 of
the 16 signals would normally be driven low on the bus, the corresponding HDINV# signal will
be asserted and the data will be inverted prior to being driven on the bus. When the processor or
the MCH receives data, it monitors HDINV[3:0]# to determine if the corresponding data segment
should be inverted.
Interleaved Mode
This mode provides maximum performance on real applications. Addresses are ping-ponged
between the channels, and the switch happens after each cache line (64 byte boundary). If two
consecutive cache lines are requested, both may be retrieved simultaneously, since they are on
opposite channels. The drawbacks of Interleaved Mode are that the system designer must populate
both channels of memory such that they have equal capacity; however, the technology and device
width may vary from one channel to the other.
Asymmetric Mode
This mode trades performance for system design flexibility. Unlike the previous mode, addresses
start in channel A and stay there until the end of the highest rank in channel A; then addresses
continue from the bottom of channel B to the top. Real world applications are unlikely to make
requests that alternate between addresses that sit on opposite channels with this memory
organization. Thus, in most cases, bandwidth will be limited to that of a single channel. The
system designer is free to populate or not to populate any rank on either channel, including either
degenerate single channel case.
CL CL CL CH B
TOM CH B TOM TOM
CH A CH B
CH B0
CH A
TOM
CH A or CH B
CH B CH A
CH A
CH B
CH A CH A0
0 0
Scheme
XOR Bit 6 ≥ CL
MemSys_Styles
DRAM Rank Boundary (CxDRBy): The x represents a channel, either A or B. They represent a
rank, 0 through 3. DRB Registers define the upper addresses for a rank of DRAM devices in a
channel. When the MCH is configured in asymmetric mode, each register represents a single
rank. When the MCH is configured in a dual interleaved mode, each register represents a pair of
corresponding ranks in opposing channels. There are 4 DRB Registers for each channel.
All standard 256-Mb, 512-Mb, and 1-Gb technologies and addressing are supported for x16 and
x8devices.
For DDR2
533 (PC 4300)
ECC
Version A = Single sided x8
Version B = Double sided x8
There is No support for DIMMs with different technologies or capacities on opposite sides of the
same DIMM. If one side of a DIMM is populated, the other side is either identical or empty.
The DRAM sub-system supports single or dual channels, 64b or72b wide per channel. There can
be a maximum of 4 ranks populated (2 Double Sided DIMMs) per channel. Mixed mode DDR
DS-DIMMs (x8 and x16 on the same DIMM) are not supported.
By using 1Gb technology, the largest memory capacity is: 8 GB (16K rows * 1K columns *
1 cell/(row * column) * 8 b/cell * 8 banks/device * 8 devices/rank * 4 ranks/channel *
2 channel *1M/(K*K) * 1G/1024M * 1B/8b = 8 GB). Using 8 GB of memory is only possible in
Interleaved mode with all ranks populated at maximum capacity. By using 256 Mb technology,
the smallest memory capacity is: 128 MB (8K rows * 512 columns * 1 cell/(row * column) *
16b/cell * 4 banks/device * 4 devices/rank * 1 rank * 1M/1024K * 1B/8b = 128 MB).
Rank Size
Page Size
Banks
Tech
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3
NOTES:
1. b – ‘bank’ select bit
2. c – ‘column’ address bit
3. r – ‘row’ address bit
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3
NOTES:
1. b – ‘bank’ select bit
2. c – ‘column’ address bit
3. h – channel select bit
4. r – ‘row’ address bit
This MCH is part of a PCI Express root complex. This means it connects a host processor /
memory subsystem to a PCI Express hierarchy. The control registers for this functionality are
located in device 1 configuration space and two Root Complex Register Blocks (RCRBs). The
DMI RCRB contains registers for control of the ICH7 attach ports.
8.5 Clocking
The MCH has PLLs that provide the internal clocks. The PLLs are:
• Host PLL – Generates the main core clocks in the host clock domain. This PLL can also be
used to generate memory core clocks. It uses the Host clock (HCLKIN) as a reference.
• Memory PLL – Can be used to generate memory core clocks, when not generated by the
Host PLL. This PLL is not needed in all configurations, but exists to provide more flexible
frequency combinations without an unreasonable VCO frequency. It uses the Host clock
(HCLKIN) as a reference.
• PCI Express PLL – Generates all PCI Express related clocks, including the Direct Media
Interface that connects to the ICH7. This PLL uses the 100 MHz (GCLKIN) as a reference.
Memory
C3/S7 Processor Diff Pair
Mux
ITP
Main
Slot0
Slot1
Slot2
Slot3
x16 PCI Express
PLL
SSC
PCI Express
S6 DIf f Pair
PCI Express GFX
4 x1 PCI Exp
D1
DOT 96 MHz Dif f Pair
U1 USB 48MHz
48 R1 REF 14MHz
MHz REF 14MHz
PLL PCI 33MHz SIO LPC
REF 14MHz AC97 Bit Clock
AC97 Intel® ICH7
P9 PCI 33MHz
PCI DownDev ice
P8 PCI 33MHz
TPM LPC OSC
P7 PCI 33MHz
33 MHz
Buffer PCI 33MHz
FWH LPC
24 MHz
HD Audio
32.768kHz
P6
P5 PCI 33MHz Signal Name Reference
PCI Slot BCLK, ITPCLK, HCLK C1-C3
P4 PCI 33MHz
PCI Slot
P3 PCI 33MHz
PCI Slot SATACLK, ICHCLK, MCHCLK, S1-S7
14 MHz P2 PCI 33MHz LANCLK, PCIECLK
PCI Slot
Oscillator P1 PCI 33MHz
PCI Slot DOTCLK (NoConnect) D1
USBCLK U1
PCICLK P1-9
14.31818MHz REFCLK R1
9 Electrical Characteristics
This chapter contains the MCH absolute maximum electrical ratings, power dissipation values,
and DC characteristics.
At conditions outside functional operation condition limits, but within absolute maximum and
minimum ratings, neither functionality nor long-term reliability can be expected. If a device is
returned to conditions within functional operation limits after having been subjected to conditions
outside these limits, but within the absolute maximum and minimum ratings, the device may be
functional, but its lifetime may be degraded depending on exposure to conditions exceeding the
functional operation condition limits.
At conditions exceeding absolute maximum and minimum ratings, neither functionality nor long-
term reliability can be expected. Moreover, if a device is subjected to these conditions for any
length of time then, when returned to conditions within the functional operating condition limits,
it will either not function, or its reliability will be severely degraded.
Although the MCH contains protective circuitry to help resist damage from static electric
discharge, additional precautions should always be taken to avoid damage from high static
voltages or electric fields.
MCH Core
VCC 1.5 V Core Supply Voltage with respect to VSS -0.3 1.65 V
VTT System Bus Input Voltage with respect to VSS -0.3 1.65 V
VCCA_HPLL 1.5 V Host PLL Analog Supply Voltage with -0.3 1.65 V
respect to VSS
VCC_EXP 1.5 V PCI Express* and DMI Supply Voltage -0.3 1.65 V
with respect to VSS
VCCA_EXPPLL 1.5 V PCI Express PLL Analog Supply Voltage -0.3 1.65 V
with respect to VSS
VCCA_3GBG 2.5 V PCI Express Band-gap Supply Voltage -0.3 2.65 V
with respect to VSS
CMOS Interface
NOTES:
1. Possible damage to the MCH may occur if the MCH temperature exceeds 150 °C. Intel does not warrant
parts that have exceeded temperatures above 150 °C since this exceeds Intel’s specification.
NOTES:
1. Estimate is only for maximum current coming through chipset’s supply balls.
2. Rail includes DLLs and FSB sense amps.
3. Includes worst case leakage.
4. Calculated for highest frequencies.
5. Icc_max values are determined on a per-interface basis. Maximum currents cannot occur simultaneously on
all interfaces.
NOTES:
1. Estimate is only for maximum current coming through chipset’s supply balls.
2. Calculated for highest frequencies.
3. Icc_max values are determined on a per-interface basis. Maximum currents cannot occur simultaneously on
all interfaces.
GTL+ Open Drain GTL+ interface signal. Refer to the GTL+ I/O Specification for
complete details. The 82955X MCH integrates most GTL+ termination
resistors.
PCI Express* PCI Express interface signals. These signals are compatible with PCI
Express 1.0a signaling environment AC Specifications. The buffers are not
3.3 V tolerant.
(d) Analog Host I/F Ref & HDVREF, HACCVREF, HSWING HRCOMP, HSCOMP
Comp. Signals
(m) Low Voltage Diff. Clock HCLKN, HCLKP, DREFCLKP, DREFCLKN, GCLKP,
Input GCLKN
9.4 DC Characteristics
Table 9-5. DC Characteristics
VCCA_SMPLL (r) DDR2 I/O PLL Analog Supply 1.425 1.5 1.575 V
Voltage
Reference Voltages
HVREF (d) Host Address, Data, and 0.63 x VTT –2% 0.63 x VTT 0.63 x VTT +2% V
Common Clock Signal
Reference Voltage
HSWING (d) Host Compensation 0.22 x VTT –2% 0.22 x VTT 0.22 x VTT+2% V
Reference Voltage
SMVREF (j) DDR2 Reference Voltage 0.49 x VCCSM 0.50 x VCCSM 0.51 x VCCSM V
Host Interface
VIL_H (a, c) Host GTL+ Input Low Voltage -0.10 0 (0.63 x VTT)– V
0.1
VIH_H (a, c) Host GTL+ Input High Voltage (0.63 x VTT VTT +0.1 V
VTT)+0.1
DDR2 Interface
VCROSS(rel) (m) Relative Crossing Voltage 0.250 + 0.5* — 0.550 + 0.5* V 8,9
(VHavg – 0.700) (VHavg – 0.700)
NOTES:
1. Determined with 2x MCH DDR2 Buffer Strength Settings into a 50 Ω to 0.5xVCCSM test load.
2. Specified at the measurement point into a timing and voltage compliance test load as shown in
Transmitter compliance eye diagram of PCI Express specification and measured over any 250
consecutive TX Uls.
3. Specified at the measurement point and measured over any 250 consecutive Uls. The test load shown in
Receiver compliance eye diagram of PCI Express specification should be used as the RX device when
taking measurements.
4. This is the DC voltage supplied at the MCH and is inclusive of all noise up to 20 MHz. Any noise above
20 MHz at the MCH generated from any source other than the MCH itself may not exceed the DC voltage
range of 1.8 V ±100 mV.
5. Applies to the pin to VCC or VSS leakage current for the SDQ_A[63:0], SDQ_B[63:0], SCB_A[7:0], and
SCB_B[7:0] signals.
6. Applies to the pin-to-pin leakage current between the SDQS_A[8:0], SDQS_A[8:0]#, SDQS_B[8:0]#, and
SDQS_B[8:0]# signals.
7. Crossing Voltage is defined as the instantaneous voltage value when the rising edge is equal to the falling
edge.
8. VHavg is the statistical average of the VH measured by the oscilloscope.
9. The crossing point must meet the absolute and relative crossing point specifications simultaneously.
10. ∆VCROSS is defined as the total variation of all crossing voltages as defined in note 7.
11. For all noise components ≤ 20MHz, the sum of the DC voltage and AC noise component must be within
the specified DC min/max operating range.
10.1 Ballout
The following two figures diagram the MCH ballout for platforms using DDR2 system memory,
as viewed from the top side of the package. The figures are broken into a left-side view and right-
side view of the package.
Note: Balls that are listed as RSV are reserved. Board traces should Not be routed to these balls.
Note: Some balls marked as reserved (RSV) are used in XOR testing. See Chapter 11 for details.
Note: Some balls marked as reserved (RSV) can be used as test points. These are marked as RSV_TPx.
Figure 10-1. Intel® 82955X MCH Ballout Diagram (Top View – Columns 43–30)
43 42 41 40 39 38 37 36 35 34 33 32 31 30
BB NC VCCSM VSS SRAS_B# VSS VCCSM SODT_A2 SCS_A0# VSS VCCSM SMA_A0 SCLK_A3 SMA_A2 BB
BA VSS SWE_B# SCS_B0# SCS_A3# SODT_A0 SWE_A# SCS_A2# SBS_A1 SCLK_A3# SMA_A1 BA
AY VCCSM SODT_B0 VCCSM SODT_A3 SODT_A1 SCAS_A# SRAS_A# SMA_A10 SCLK_A0 SMA_A3 AY
AU SODT_B3 SCS_B3# SCS_B1# SDQ_A35 SDQ_B45 SDQ_A34 SDQS_A4 VSS VSS SDQ_B39 AU
AR VSS SDQ_A45 SDQ_A44 VSS SDM_B5 VSS SDQ_B44 SDQ_A38 VSS SDQ_B34 AR
AP SDM_A5 SDQS_A5# SDQ_A41 SDQ_A40 VSS SDQ_B41 SDQ_B40 SDQS_B5 VSS SDQ_A32 SDQ_B38 AP
AM SDQ_A43 SDQ_A42 SDQ_A47 VSS SDQ_B46 VSS VSS SDQS_B5# VSS SDQ_B42 SDQ_B35 AM
AL VSS SDQ_A53 SDQ_A52 SDQ_A48 SCLK_B2 VSS SCLK_B2# VSS SDQ_B53 VSS SDQ_B52 VSS AL
AJ SDM_B6 SCLK_B5 VSS SCLK_B5# VSS SDQ_B49 VSS SDQ_B48 SDQ_B43 VSS AJ
AG SDQS_A6 SDQS_A6# SDM_A6 VSS VSS VSS VSS SDQ_B54 SDQS_B6 VSS SDQS_B6# VSS VCC AG
AF VSS SDQ_A55 SDQ_A54 SDQ_A50 VSS SDQ_B61 VSS SDQ_B60 SDQ_B51 VSS SDQ_B50 VSS VCC AF
AD SDQ_A57 VSS SDQ_A56 SDQS_B7# VSS SDM_B7 SDQS_B7 VSS SDQ_B57 VSS SDQ_B55 VSS VSS AD
AC SDQS_A7 SDQS_A7# SDM_A7 VSS VSS VSS VSS SDQ_B63 SDQ_B62 VSS SDQ_B56 VSS VCC AC
AA HA33# HBREQ0# SDQ_A59 SDQ_A58 HA35# HA29# VSS HA32# HA34# VSS SDQ_B59 VSS VSS AA
Y HRS1# VSS HEDRDY# VSS HA28# VSS HA27# VSS HA31# VSS SDQ_B58 VSS VCC Y
V VSS HA25# HDRDY# VSS VSS VSS VSS HADSTB1# VSS HA22# HA30# RSV VSS V
U HDBSY# HHIT# HLOCK# HBNR# VSS HA19# VSS HA26# HA23# VSS HA24# VSS VCC U
R VSS HA21# VSS HA18# HA20# VSS HA10# HA17# VSS VSS R
N VSS HA14# HD4# VSS HA16# HA15# VSS HA9# HA12# VSS HA11# VSS N
M HD3# HD7# HD5# HD1# HA13# VSS HADSTB0# VSS HA8# HD33# HCLKP M
K HD8# HDSTBP0# HDINV0# VSS HA4# VSS HREQ2# HA6# VSS VSS HD34# K
J VSS HA5# HD10# HA3# VSS HA7# HD18# HD27# HD25# HD31# J
G HD11# HD13# HD12# HD9# VSS HREQ3# VSS HDSTBN1# VSS VSS G
D VSS HBPRI# HREQ1# HD19# HD53# HD51# HD56# HD54# HD61# HD63# D
B NC NC NC HD22# HD21# VSS HDSTBN3# HD26# HD28# VSS HDINV3# HD58# HD62# B
43 42 41 40 39 38 37 36 35 34 33 32 31 30
Figure 10-2. Intel® 82955X MCH Ballout Diagram (Top View – Columns 29–16)
29 28 27 26 25 24 23 22 21 20 19 18 17 16
BB VCCSM SMA_A8 SMA_A11 SBS_A2 VCCSM SMA_B10 SMA_B2 SMA_B3 VCCSM VSS SMA_B11 SBS_B2 VCCSM BB
AY SMA_A6 SMA_A7 SCKE_A0 SCKE_A3 SBS_B1 SMA_B5 SMA_B8 SMA_B9 SCKE_B2 SCKE_B0 AY
AH AH
AG VSS RSV RSV RSV RSV RSV RSV RSV VCC VCC VSS VSS AG
AF VCC VCC VCC VSS VCC VSS VCC VSS VCC VSS VCC VCC AF
AE VCC VCC VCC VSS VCC VSS VCC VSS VCC VSS VCC AE
AD VCC VCC VCC VSS VCC VSS VCC VSS VCC VSS VCC VCC AD
AC VCC VCC VCC VCC VSS VCC VSS VCC VSS VCC VSS VCC AC
AB VCC VCC VSS VCC VSS VCC VSS VCC VSS VCC VCC AB
AA VCC VCC VCC VCC VSS VCC VSS VCC VSS VCC VSS VCC AA
Y VSS VCC VCC VSS VCC VSS VCC VSS VCC VCC VCC VCC Y
W VCC VSS VCC VSS VCC VSS VCC VSS VCC VCC VCC W
V VCC VCC VCC VSS VCC VCC VCC VCC VCC VCC VCC VCC V
U VSS VCC VCC VCC VCC VCC VCC VCC VCC VCC VCC VCC U
T T
HDSTBN2
M HCLKN HD35# HD41# VTT VSS EXTTS# VCC VCC M
#
HACC
D HDVREF VTT VTT VTT VSS VSS RSV VCC_EXP VCC_EXP D
VREF
VCCA_
C HSCOMP VTT VTT VTT VSS RSV_TP5 VCC_EXP VCC_EXP C
SMPLL
VCCA_
B VSS HSWING VTT VTT VTT VSS VSS VSS VCC2 VCC_EXP VCC_EXP GCLKN B
EXPPLL
HRCOM VCCA_3GB
A VTT VTT VCCA_HPLL VCC_EXP VCC_EXP A
P G
29 28 27 26 25 24 23 22 21 20 19 18 17 16
Figure 10-3. Intel® 82955X MCH Ballout Diagram (Top View – Columns 15–1)
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
BB VSS SDQ_A18 SDQ_A23 VSS SDQ_A16 SDQ_A11 SDQ_A15 VSS SDQS_A1 SDQS_A1# NC NC NC BB
AY VCCSM SDQ_A22 SDM_A2 SDQ_A21 SCLK_A4 SCLK_A1# SDM_A1 SDQ_A13 SDQ_A8 VSS AY
AV SDQ_A30 SDM_A3 SDQ_B30 VSS SDM_B3 SDQ_B29 SDQ_B23 SDQ_A6 VSS SDQ_A7 AV
AU VSS VSS VSS SDQ_B25 VSS SDQ_B19 VSS SDM_A0 SDQ_A1 SDQS_A0 SDQS_A0# AU
AR VSS SDQ_B27 SDQS_B3# SDQS_B3 SDQ_B28 SDQS_B2# SDQS_B2 VSS SDQ_A5 SDQ_A0 VSS AR
AP SDQS_A3# SDQ_A29 VSS VSS SDQ_B22 SDM_B2 VSS SDQ_B17 VSS SDQ_B7 SDQ_B3 SDQ_A4 AP
AM SDQ_A28 SDQ_A24 SDQ_B31 SDQ_B16 VSS SDQ_B21 VSS SDQ_B20 SDM_B0 SDQ_B6 SDQS_B0# SDQS_B0 AM
AL RSV_TP1 VSS SDQ_B11 VSS SDQ_B10 SDQ_B14 VSS SDQ_B15 VSS VSS SDQ_B1 SDQ_B5 VSS AL
AJ VSS VSS VSS SDQ_B13 SCLK_B1# VSS SCLK_B1 VSS SCLK_B4 SCLK_B4# VSS AJ
AG VSS VSS VSS VSS SDQ_B9 VSS SDM_B1 SDQS_B1# VSS SDQS_B1 VSS VSS SMVREF1 SRCOMP1 AG
AF VCC VSS VSS VSS SDQ_B12 VSS SDQ_B8 VSS VSS VSS VSS SOCOMP0 VSS SRCOMP0 AF
AD VCC VSS VSS VSS VSS VSS VSS VSS VSS VSS VSS VSS VSS PWROK AD
EXP_
AC VCC VSS VSS EXP_COMPI VSS DMI_RXP3 DMI_RXN3 VSS VSS VSS DMI_TXN3 VSS VSS AC
COMPO
AA VCC VCC_EXP VCC_EXP VCC_EXP VSS DMI_RXN1 DMI_RXP1 VSS DMI_TXP2 DMI_TXN2 VSS DMI_RXP2 VSS DMI_TXP1 AA
Y VCC VCC_EXP VCC_EXP VCC_EXP VSS VCC_EXP VCC_EXP VSS VCC_EXP VCC_EXP VSS DMI_RXN2 VSS DMI_TXN0 Y
U VCC VCC_EXP VCC_EXP VCC_EXP VSS VCC_EXP VCC_EXP VSS VCC_EXP VCC_EXP VSS EXP_TXN13 VSS EXP_TXP14 U
EXP_
N VCC_EXP VCC_EXP VCC_EXP VCC_EXP VCC_EXP VCC_EXP VCC_EXP VCC_EXP VCC_EXP VSS EXP_TXN11 VSS N
TXP12
EXP_ EXP_
M VCC_EXP VCC_EXP VSS VSS VSS VSS VSS EXP_TXN10 VSS EXP_TXP11 M
RXN10 RXP10
K VCC_EXP VSS VSS VSS EXP_RXP9 EXP_RXN9 VSS VSS VSS EXP_TXN9 VSS EXP_RXP11 K
J VCC_EXP EXP_RXP2 VSS VSS EXP_RXP4 VSS EXP_RXN7 VSS EXP_TXP9 VSS EXP_TXN8 J
G VCC_EXP VSS EXP_RXP0 VSS VSS VSS EXP_RXP7 VSS EXP_TXN7 VSS EXP_TXP8 G
F VCC_EXP VCC_EXP EXP_RXN0 EXP_RXN3 EXP_RXN5 EXP_RXP5 VSS EXP_TXP7 VSS EXP_RXN8 F
EXP_TXP
D EXP_TXP2 EXP_TXN2 VSS EXP_TXP5 EXP_TXN5 VSS EXP_RXN6 VSS VSS D
0
EXP_
B GCLKP EXP_TXP1 EXP_TXN1 VSS EXP_RXN1 VSS EXP_TXN4 VSS VSS NC NC B
TXN6
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Ball Ball
Signal Name # Signal Name #
VSS B23
VSS B22
VSS B21
VSS B11
VSS B9
VSS B6
VSS B4
VSS A35
VSS A31
VSS A13
VSS M17
VTT M23
VTT L23
VTT K23
VTT J23
VTT H23
VTT G23
VTT F27
VTT F23
VTT E27
10.2 Package
The MCH package measures 34 mm × 34 mm; it is a 34 mm squared, 6-layer flip chip ball grid
array (FC-BGA) package The 1202 balls are located in a non-grid pattern. Figure 10-4 through
Figure 10-6 show the physical dimensions of the package. For further information on the
package, see the Intel® 955X Express Chipset Thermal/Mechanical Design Guidelines.
CapacitorArea, Ø5.20mm
HandlingExclusion Die
Zone 19.38
Keepout
10.67 Area
2.30
3.1
2.0
MCH
15.34 9.14 34.00
Die
3.0
3.1
6.17
HandlingArea
2.54
34.00
0.20 –C–
Seating Plane
0.435 ± 0.025 mm
See note 3
See note 1.
Notes:
1. Primary datum -C- and seating plan are defined by the spherical crow ns of the solder balls (show n before motherboard attach)
2. All dimensions and tolerances conform to ANSI Y14.5M-1994
3. BGA has a pre-SMT height of 0.5mm and post-SMT height of 0.41-0.46mm
4. Show n before motherboard attach; FCBGA has a convex (dome shaped) orientation before reflow and is expected to have a slightly
concave (bow l shaped) orientation after reflow
NOTES:
1 . All dimensions are in millimeters.
2. All dimensions and tolerances conform to ANSI Y14.5M-1994.
11 Testability
In the MCH, testability for Automated Test Equipment (ATE) board level testing has been
implemented as an XOR chain. An XOR-tree is a chain of XOR gates each with one input pin
connected to it.
On power up, hold PWROK, RSTIN#, and XORTEST (H20) low and start external clocks. After
a few clock cycles, pull PWROK high. After ~3–4 clocks, de-assert RSTIN# (pull it high).
Release XORTEST (H20) and RSV_TP5. No external drive. Allow the clocks to run for an
additional 32 clocks. Begin testing the XOR chains. Refer to Figure 11-1.
32 clocks
PWROK
~3-4 Clocks
RSTIN#
XOR_Chain_Tim
30 T40 HRS0#
31 U41 HHIT#
Table 11-4. XOR Chain 1
32 V41 HDRDY#
Pin Count Ball Signal Name 33 W41 HHITM#
#
34 W42 HADS#
1 G42 HD11#
35 U40 HLOCK#
2 K42 HD8#
36 Y43 HRS1#
3 G40 HD12#
37 U39 HBNR#
4 L43 HDSTBNB0#
38 W40 HTRDY#
5 G39 HD9#
39 R32 HA17#
6 M42 HD3#
40 R36 HA18#
7 J41 HD10#
41 U35 HA26#
8 P41 HD0#
42 R35 HA20#
9 P42 HD2#
43 U34 HA23#
10 K40 HDINV0#
44 U37 HA19#
11 M41 HD7#
45 R38 HA21#
12 M40 HD5#
46 AA41 HBREQ0#
13 N41 HD4#
47 Y34 HA31#
14 G37 HREQ3#
48 V35 HADSTB1#
15 J39 HA3#
49 V33 HA22#
16 K36 HREQ2#
50 U32 HA24#
17 M36 HADSTB0#
51 V32 HA30#
18 E41 HREQ0#
52 AA37 HA29#
19 J37 HA7#
53 Y36 HA27#
20 E42 HREQ4#
54 V42 HA25#
Pin Count Ball Signal Name Pin Count Ball Signal Name
# #
31 AV32 SDQ_A36
Table 11-5. XOR Chain 2 32 AT32 SDQ_A37
11 AL41 SDQ_A52
Table 11-6. XOR Chain 3
12 AG40 SDM_A6
Pin Count Ball Signal Name Pin Count Ball Signal Name
# #
13 AF34 SDQ_B51
14 AF32 SDQ_B50
Table 11-7. XOR Chain 4
15 AJ36 SCLK_B5#
Pin Count Ball Signal Name
16 AL36 SCLK_B2# #
17 AL38 SCLK_B2
1 AC41 SDQS_A7#
18 AN32 SDQ_B47
2 AL42 SDQ_A53
19 AJ31 SDQ_B43
3 AE40 SDQ_A51
20 AM33 SDQ_B42
4 AG41 SDQS_A6#
21 AR35 SDQ_B44
5 AH40 SCLK_A5#
22 AR38 SDM_B5
6 AK42 SCLK_A2
23 AM38 SDQ_B46
7 AP40 SDQ_A41
24 AP36 SDQ_B40
8 AM42 SDQ_A43
25 AP37 SDQ_B41
9 AP41 SDQS_A5#
26 BA40 SCS_B0#
10 AT34 SDM_A4
27 AW40 SCS_B2#
11 AU39 SDQ_A35
28 AU41 SCS_B3#
12 AU37 SDQ_A34
29 AW41 SODT_B2
13 AW35 SDQS_A4#
30 AP27 SDQ_B36
14 BA37 SODT_A0
31 AM31 SDQ_B35
15 BC38 SCS_A1#
32 AN29 SDQ_B33
16 BA32 SBS_A1
33 AR27 SDQ_B32
17 BA30 SMA_A1
34 AV40 SMA_B13
18 BB32 SMA_A0
35 AP24 SCB_B6
19 BB31 SCLK_A3
36 AM27 SCLK_B0#
20 AY28 SMA_A6
37 BA23 SBS_B0
21 AY30 SMA_A3
38 BA41 SWE_B#
22 AV18 SDQS_A8#
39 AY19 SMA_B9
23 AP21 SCB_A3
40 BB17 SBS_B2
24 AM20 SCB_A5
41 BA18 SMA_B12
25 AM18 SCB_A4
Pin Count Ball Signal Name Pin Count Ball Signal Name
# #
30 AV7 SDQ_B29
31 AR12 SDQS_B3#
Table 11-8. XOR Chain 5
32 BA17 SCKE_B1
Pin Count Ball Signal Name
# 33 BA14 SCKE_B3
34 AV6 SDQ_B23
1 AD39 SDQS_B7#
35 AP9 SDQ_B22
2 AF35 SDQ_B60
36 AP6 SDQ_B17
3 AC32 SDQ_B56
37 AM10 SDQ_B16
4 AG32 SDQS_B6#
38 AR7 SDQS_B2#
5 AJ34 SDQ_B49
Pin Count Ball Signal Name Pin Count Ball Signal Name
# #
30 AY7 SCLK_A4
31 BA5 SCLK_A1
Table 11-9. XOR Chain 6
32 BA9 SDQ_A10
Pin Count Ball Signal Name
# 33 BB9 SDQ_A11
34 BA3 SDQ_A9
1 BB37 SODT_A2
35 AY2 SDQ_A8
2 AY38 SODT_A1
36 AW2 SDQ_A12
3 AY37 SCAS_A#
37 AU5 SDM_A0
4 BA35 SWE_A#
38 AR3 SDQ_A5
5 AY34 SRAS_A#
39 AV1 SDQ_A7
6 AY33 SMA_A10
40 AW3 SDQ_A3
7 BA31 SCLK_A3#
41 AU4 SDQ_A1
8 AW27 SMA_A9
42 AP2 SDQ_A4
9 BB27 SMA_A8
43 AW4 SDQ_A2
10 AR18 SCB_A1
11 AV20 SCB_A7
Pin Count Ball Signal Name Pin Count Ball Signal Name
# #
8 AM21 SCB_B4
9 AT24 SCB_B7
Table 11-11. XOR Chain 8
10 AM26 SCB_B3
Pin Count Ball Signal Name
11 AR26 SCLK_B3# #
12 AW42 SCAS_B#
1 F12 EXP_RXN0
13 BB23 SMA_B10
2 C13 EXP_TXN0
14 BA22 SMA_B1
3 B10 EXP_RXN1
15 AY20 SMA_B8
4 B12 EXP_TXN1
16 AY21 SMA_B5
5 H13 EXP_RXN2
17 AR13 SDQ_B27
6 D11 EXP_TXN2
18 AN12 SDQ_B26
7 F10 EXP_RXN3
19 AV12 SDQ_B30
8 C9 EXP_TXN3
20 AV9 SDM_B3
9 H10 EXP_RXN4
21 AR9 SDQ_B28
10 B7 EXP_TXN4
22 AY16 SCKE_B0
11 F9 EXP_RXN5
23 AY17 SCKE_B2
12 D6 EXP_TXN5
24 AW7 SDQ_B18
13 D3 EXP_RXN6
25 AU7 SDQ_B19
14 B5 EXP_TXN6
26 AP8 SDM_B2
15 J6 EXP_RXN7
27 AM6 SDQ_B20
16 G4 EXP_TXN7
28 AM8 SDQ_B21
17 F1 EXP_RXN8
29 AJ9 SCLK_B1
18 J1 EXP_TXN8
30 AJ6 SCLK_B4#
19 K8 EXP_RXN9
31 AF9 SDQ_B8
20 K4 EXP_TXN9
32 AL10 SDQ_B10
21 M7 EXP_RXN10
33 AG9 SDM_B1
22 M4 EXP_TXN10
34 AJ12 SDQ_B13
23 L1 EXP_RXN11
35 AF11 SDQ_B12
24 N2 EXP_TXN11
36 AM5 SDM_B0
25 R10 EXP_RXN12
Pin Count Ball Signal Name Pin Count Ball Signal Name
# #
27 R7 EXP_RXN13 58 N3 EXP_TXP12
28 U4 EXP_TXN13 59 R8 EXP_RXP13
29 T1 EXP_RXN14 60 T4 EXP_TXP13
30 V2 EXP_TXN14 61 P2 EXP_RXP14
32 W4 EXP_TXN15 63 V9 EXP_RXP15
34 D14 EXP_TXP0
35 A11 EXP_RXP1
Table 11-12. XOR Chain 9
36 B13 EXP_TXP1
Pin Count Ball Signal Name
37 J13 EXP_RXP2 #
38 D12 EXP_TXP2
1 V7 DMI_RXN0
39 E10 EXP_RXP3
2 V6 DMI_RXP0
40 C10 EXP_TXP3
3 Y1 DMI_TXN0
41 J9 EXP_RXP4
4 W2 DMI_TXP0
42 A9 EXP_TXP4
5 AA10 DMI_RXN1
43 F7 EXP_RXP5
6 AA9 DMI_RXP1
44 D7 EXP_TXP5
7 AB1 DMI_TXN1
45 C4 EXP_RXP6
8 AA2 DMI_TXP1
46 A6 EXP_TXP6
9 Y4 DMI_RXN2
47 G6 EXP_RXP7
10 AA4 DMI_RXP2
48 F4 EXP_TXP7
11 AA6 DMI_TXN2
49 E2 EXP_RXP8
12 AA7 DMI_TXP2
50 G2 EXP_TXP8
13 AC8 DMI_RXN3
51 K9 EXP_RXP9
14 AC9 DMI_RXP3
52 J3 EXP_TXP9
15 AC4 DMI_TXN3
53 M6 EXP_RXP10
16 AB3 DMI_TXP3
54 L4 EXP_TXP10
55 K2 EXP_RXP11
56 M2 EXP_TXP11
HVREF SOCOMP1
HSWING SOCOMP0
SM_SLEWOUT1
SM_SLEWOUT0
SM_SLEWIN1
SM_SLEWIN0