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,
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 Dual-Core Intel® Itanium® 9000 and 9100 series processor may contain design defects or errors known as errata which may
cause the product to deviate from published specifications. Current characterized errata are available on request.
Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.
Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained
by calling1-800-548-4725, or by visiting Intel's website at http://www.intel.com.
Intel, Itanium, and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United
Implementation of the I2C bus/protocol or the SMBus bus/protocol may require licenses from various entities, including Phillips
Electronics, N.V. and North American Phillips Corporation.
2Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet9
The Dual-Core Intel® Itanium® processor 9000 and 9100 series delivers new levels of flexibility,
reliability, performance, and cost-effective scalability for your most data-intensive business and
technical applications. With double the performance of previous Intel Itanium processors, the DualCore Intel Itanium processor 9000 and 9100 series provides more reasons than ever to migrate your
business-critical applications off RISC and mainframe systems and onto cost-effective Intel
architecture servers. The Dual-Core Intel Itanium processor 9000 and 9100 series provides close to
triple the amount of L3 cache (24 megabytes), Hyper-Threading Technology for increased
performance, Intel® Virtualization Technology for improved virtualization, Intel® Cache Safe
Technology for increased availability, and 20 percent lower power consumption.
Dual-Core Itanium®-based systems are available from leading OEMs worldwide and run popular 64bit operating systems such as Microsoft* Windows Server* 2003; Linux* from SuSE, Red Hat, Red
Flag, and other distributions; HP NonStop*; OpenVMS*; and HP-UX*. More than 7,000 applications
are available for Itanium-based systems, from vendors such as Microsoft, BEA, IBM, Ansys, Gaussian,
Symantec/VERITAS, Oracle, SAP, and SAS. And with industry support growing and future Intel
Itanium processor family advances already in development, your Itanium-based server investment
will continue to deliver performance advances and savings for your most demanding applications.
§
10Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Introduction
1Introduction
1.1Overview
The Dual-Core Intel Itanium processor 9000 and 9100 series employs Explicitly Parallel
Instruction Computing (EPIC) design concepts for a tighter coupling between hardware
and software. In this design style, the interface between hardware and software is
engineered to enable the software to exploit all available compile-time information and
efficiently deliver this information to the hardware. It addresses several fundamental
performance bottlenecks in modern computers, such as memory latency, memory
address disambiguation, and control flow dependencies. The EPIC constructs provide
powerful architectural semantics and enable the software to make global optimizations
across a large scheduling scope, thereby exposing available Instruction Level
Parallelism (ILP) to the hardware. The hardware takes advantage of this enhanced ILP,
and provides abundant execution resources. Additionally, it focuses on dynamic runtime optimizations to enable the compiled code schedule to flow at high throughput.
This strategy increases the synergy between hardware and software, and leads to
greater overall performance.
The Dual-Core Intel Itanium processor 9000 and 9100 series provides a 6-wide and 8stage deep pipeline, running at up to 1.6 GHz. This provides a combination of abundant
resources to exploit ILP as well as increased frequency for minimizing the latency of
each instruction. The resources consist of six integer units, six multimedia units, two
load and two store units, three branch units, two extended-precision floating-point
units, and one additional single-precision floating-point unit per core. The hardware
employs dynamic prefetch, branch prediction, a register scoreboard, and non-blocking
caches to optimize for compile-time non-determinism. Three levels of on-die cache
minimize overall memory latency. This includes up to a 24 MB L3 cache, accessed at
core speed, providing up to 8.53 GB/sec. of data bandwidth. The system bus is
designed to support up to four physical processors (on a single system bus), and can
be used as an effective building block for very large systems. The balanced core and
memory subsystem provide high performance for a wide range of applications ranging
from commercial workloads to high-performance technical computing.
The Dual-Core Intel Itanium processor 9000 and 9100 series supports a range of
computing needs and configurations from a two-way to large SMP servers. This
document provides the electrical, mechanical and thermal specifications for the DualCore Intel Itanium processor 9000 and 9100 series for use while employing systems
with the processors.
1.2Processor Abstraction Layer
The Dual-Core Intel Itanium processor 9000 and 9100 series requires implementationspecific Processor Abstraction Layer (PAL) firmware. PAL firmware supports processor
initialization, error recovery, and other functionality. It provides a consistent interface
to system firmware and operating systems across processor hardware
implementations. The Intel® Itanium® Architecture Software Developer’s Manual,
Volume 2: System Architecture, describes PAL. Platforms must provide access to the
firmware address space and PAL at reset to allow the processors to initialize.
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet11
Introduction
The System Abstraction Layer (SAL) firmware contains platform-specific firmware to
initialize the platform, boot to an operating system, and provide runtime functionality.
Further information about SAL is available in the Intel®Itanium®Processor Family
System Abstraction Layer Specification.
1.3Mixing Processors of Different Frequencies and
Cache Sizes
All Dual-Core Intel Itanium processor 9000 and 9100 series on the same system bus
are required to have the same cache size (24 MB, 18 MB, 12 MB, 8 MB or 6 MB) and
identical core frequency. Mixing components of different core frequencies and cache
sizes is not supported and has not been validated by Intel. Operating system support
for multiprocessing with mixed components should also be considered.
While Intel has done nothing to specifically prevent processors within a multiprocessor
environment from operating at differing frequencies and differing cache sizes, there
may be uncharacterized errata that exist in such configurations. Customers would be
fully responsible for validation of system configurations with mixed components other
than the supported configurations described above.
1.4Terminology
In this document, “the processor” refers to the “Dual-Core Intel Itanium processor
9000 and 9100 series” processor, unless otherwise indicated.
A ‘#’ symbol after a signal name refers to an active low signal. This means that a signal
is in the active state (based on the name of the signal) when driven to a low level. For
example, when RESET# is low, a processor reset has been requested. When NMI is
high, a non-maskable interrupt has occurred. In the case of lines where the name does
not imply an active state but describes part of a binary sequence (such as address or
data), the ‘#’ symbol implies that the signal is inverted. For example, D[3:0] = ‘HLHL’
refers to a hex ‘A’, and D [3:0] # = ‘LHLH’ also refers to a hex ‘A’ (H = High logic level,
L = Low logic level).
The term “system bus” refers to the interface between the processor, system core logic,
and other bus agents. The system bus is a multiprocessing interface to processors,
memory, and I/O.
A signal name has all capitalized letters, for example, VCTERM.
A symbol referring to a voltage level, current level, or a time value carries a plain
subscript, for example, V
1.5State of Data
The data contained in this document is subject to change. It is the best information
that Intel is able to provide at the publication date of this document.
, or a capitalized, abbreviated subscript, for example, TCO.
core
12Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Introduction
1.6Reference Documents
The reader of this specification should also be familiar with material and concepts
presented in the following documents:
Itanium®2 Processor Reference Manual for Software Development and
Intel
Optimization
Intel®Itanium®Processor Family System Abstraction Layer Specification
ITP700 Debug Port Design Guide
System Management Bus Specification
Note:Contact your Intel representative or check http://developer.intel.com for the latest
revision of the reference documents.
§
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet13
Introduction
14Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Electrical Specifications
2Electrical Specifications
This chapter describes the electrical specifications of the Dual-Core Intel Itanium
Processor 9000 and 9100 series.
2.1Dual-Core Intel® Itanium® Processor 9000 and
9100 Series System Bus
Most Dual-Core Intel Itanium processor 9000 and 9100 series signals use the Itanium
processor’s assisted gunning transceiver logic (AGTL+) signaling technology. The
termination voltage, V
reference voltage. The buffers that drive most of the system bus signals on the
processor are actively driven to V
times and reduce noise. These signals should still be considered open-drain and require
termination to V
terminated to V
termination, in which case, the termination is provided by external resistors connected
to V
CTERM
.
CTERM
CTERM
, is generated on the baseboard and is the system bus high
CTERM
during a low-to-high transition to improve rise
CTERM
which provides the high level. The processor system bus is
at each end of the bus. There is also support of off-die
AGTL+ inputs use differential receivers which require a reference signal (V
used by the receivers to determine if a signal is a logical 0 or a logical 1. The processor
generates V
source.
on-die, thereby eliminating the need for an off-chip reference voltage
REF
2.1.1System Bus Power Pins
VCTERM (1.2 V) input pins on the processor provide power to the driver buffers and ondie termination. The GND pins, in addition to the GND input at the power tab connector,
provide ground to the processor. Power for the processor core is supplied through the
power tab connector by V
to provide power to the system management bus (SMBus). The V
pins must remain electrically separated from each other.
Core
, V
Cache, Vfixed.
2.1.2System Bus No Connect
All pins designated as “N/C” or “No Connect” must remain unconnected.
2.2System Bus Signals
2.2.1Signal Groups
Table 2-1 shows processor system bus signals that have been combined into groups by
buffer type and whether they are inputs, outputs, or bidirectional, with respect to the
processor.
). V
REF
The 3.3 V pin is included on the processor
, 3.3 V, and GND
CTERM
REF
is
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet15
..
Table 2-1.Itanium® Processor System Bus Signal Groups
AGTL+ Output SignalsFERR#, THRMTRIP#, DBSY[1:0]#, DRDY[1:0]#, SBSY[1:0]#
Special AGTL+ Asynchronous
Interrupt Input Signals
Power Good Signal
HSTL Clock SignalsBCLKn, BCLKp
TAP Input Signals
TAP Output Signals
System Management Signals13.3 V, SMA[2:0], SMSC, SMSD, SMWP, THRMALERT#
Power SignalsGND, VCTERM
LVTTL Power Pod Signals
OtherTERMA, TERMB, TUNER1, TUNER2, TUNER3, VCCMON, VSSMON
Notes:
1. Signals will not be terminated on-die even when on-die termination (ODT) is enabled. See the Intel®Itanium
2 Processor Hardware Developer’s Manual for further details.
All system bus outputs should be treated as open drain signals and require a high-level
source provided by the V
AGTL+ inputs have differential input buffers which use V
output signals require termination to V
CTERM
supply.
as a reference level. AGTL+
. In this document, “AGTL+ Input Signals”
CTERM
REF
refers to the AGTL+ input group as well as the AGTL+ I/O group when receiving.
Similarly, “AGTL+ Output Signals” refers to the AGTL+ output group as well as the
AGTL+ I/O group when driving.
The Test Access Port (TAP) connection input signals use a non-differential receiver with
levels that are similar to AGTL+. No reference voltage is required for these signals. The
TAP Connection Output signals are AGTL+ output signals.
The processor system bus requires termination on both ends of the bus. The processor
system bus supports both on-die and off-die termination controlled by two pins, TERMA
and TERMB. Please see the TERMA and TERMB pin description in Section 2.2.2.
The HSTL clock signals are the differential clock inputs for the processor. The SMBus
signals and LVTTL power pod signals are driven using the 3.3 V CMOS logic levels listed
in Table 2-8 and Table 2-9, respectively.
16Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Electrical Specifications
2.2.2Signal Descriptions
Appendix A, “Signals Reference”, contains functional descriptions of all system bus
signals and LVTTL power pod signals. Further descriptions of the system management
signals are contained in Chapter 6. The signals listed under the “Power” and “Other”
group are described here:
V
CTERM
GNDSystem ground.
N/CNo connection can be made to these pins.
TERMA, TERMBThe processor uses two pins to control the on-die termination
TUNER1, TUNER2,
TUNER3The TUNER1 Pin can either be left as a no-connect or left
VCCMON, VSSMONThese pins allows remote measurement of on-die Vcore voltage.
System bus termination voltage.
function: TERMA and TERMB. Both of these termination pins
must be pulled to VCTERM in order to terminate the system bus
using the on-die termination resistors. Both of these termination
pins must be pulled to GND in order to use off-die termination.
connected to VCTERM via resistor for the majority of platforms
supporting the Dual-Core Intel Itanium processor 9000 and
9100 series. The TUNER2 resistor is used to control the
termination resistance for the system bus I/O buffers. A lower
resistance will cause a lower on-die termination resistance. Ondie termination mode will only be selected if the TERMA and
TERMB pins are terminated as indicated above. The TUNER3 pin
will not be required for the majority of platforms supporting the
Dual-Core Intel Itanium processor 9000 and 9100 series. The
TUNER3 pin is used only in the case where A[21:17]# are driven
to all zeros or all ones during the configuration cycles at reset.
When all zeros or all ones are observed by the processor the
presence of the TUNER3 and TUNER1 pins is used to determine
system bus frequency. See Table 2-22 for the various TUNER pin
combinations and resulting system bus frequency and slew rate
combination.
No connections that constitute a current load can be made to
these pins.
Table 2-2.Nominal Resistance Values for Tuner1, Tuner2, and Tuner3
5-Load Platform (Ohms)
Tuner1: NC
Tuner2: 150
Tuner3: NC
Notes:
1. Depending on system configuration, the processor may or may not require a resistor on the
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet17
400 MHz
1
1
TUNER pin. OEMs may leave the pin unconnected or connect it to VCTERM through a 150
or 100 ohm resistor. If A[21:17]:# are driven to all 0’s or all 1’s at reset, see Table 2-22
for proper use of the TUNER Pins.
3-Load Platform (Ohms)
Tuner1: NC
Tuner2: 150
Tuner3: NC
400 MHz
1
1
3-Load Platform (Ohms)
Tuner1: NC
Tuner2: 150
Tuner3: NC
533 MHz
1
1
2.3Package Specifications
Table 2-3 through Table 2-9 list the DC voltage, current, and power specifications for
the processor. The voltage and current specifications are defined at the processor pins.
Operational specifications listed in Table 2-3 through Table 2-9 are only valid while
meeting specifications for case temperature, clock frequency, and input voltages.
Table 2-3.Processor Package Specifications
Electrical Specifications
SymbolParameter
V
core, PSVCC
V
cache, PSVcache
V
fixed, PSVfixed
V
CTERM
R
TERM
V
TAP
I
core,PS
I
cache,PS
I
fixed,PS
I
CTERM
PS
TT
PWR
max
PWR
TPE
PWR
TDP
Notes:
1. The range for Vcore is 1.0875 V to 1.25 V.
2. Vcache typical is 1.025 V.
3. The processor system bus is terminated at each end of the system bus. The processor supports both on-die
and off-die termination which is selected by the TERMA and TERMB pins. Termination tolerance is ±15% for
on-die termination measured at VOL and ±1% for off-die termination.
4. This is measured for On-Die Termination with a 45-ohm pull up resistor.
5. Max power is peak electrical power that must be provided for brief periods by the VR.
6. Represents the TDP level that should be used for system thermal design. Sustained power for all real-world
applications will remain at or below this power level.
Termination Voltage CurrentAll7.2A
Power Supply Slew Rate for
the Termination Voltage at the
Processor Pins
Max Power All177W
Thermal Power EnvelopeAll130W
Thermal Design Power – dual
core
Thermal Design Power –
single core
Core
Frequency
AllVID-17 mVVIDVID+17 mVV
AllVID-17 mVVIDVID+17 mVV
All1.25-20 mV1.25 1.25+20 mVV
All45-15%4545+15%Ohm
All1.2-1.5%1.21.5V
All2.889121A
All2.01718A
All0.79.211A
All0.05A/ns
All104W
1.6 GHz75W
MinimumTypMaximumUnit Notes
1
2
3
4
5
6
2.4Signal Specifications
This section describes the DC specifications of the system bus signals. The processor
signal’s DC specifications are defined at the processor pins. Table 2-4 through Table 2-9
describe the DC specifications for the AGTL+, PWRGOOD, HSTL clock, TAP port, system
management, and LVTTL signals. Please refer to the ITP700 Debug Port Design Guide
for the TAP connection signals’ DC specifications at the debug port.
18Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Electrical Specifications
Table 2-4.AGTL+ Signals DC Specifications
SymbolParameter
V
IL
V
IH
V
OL
V
OH
I
OL
I
OL
I
L
C
AGTL+
Notes:
1. The typical transition point between VIL and VIH assuming 125 mV V
V
REF_low
and V
2. Parameter measured into a 22.5 ohm resistor to 1.2 V. Minimum VOL and IOL are guaranteed by design/
characterization.
3. Calculated using off-die termination through two 45 ohm ±1% resistors in parallel.
4. Calculated using on-die termination to a 45 ±15% resistor measured at VOL.
5. At 1.2 V ±1.5%. V
6. Total of I/O buffer with ESD structure and processor parasitics if applicable. Capacitance values guaranteed
by design for all AGTL+ buffers.
Input Low VoltageAll0.625V
Input High VoltageAll0.875V
Output Low VoltageAll0.30.4V
Output High VoltageAllV
Output Low Current @ 0.3 VAll34mA
Output Low Current @ 0.3 VAll17mA
Leakage CurrentAll±100µA
AGTL+ Pad Capacitance All2pF
levels are V
levels are V
REF_low
±100 mV, respectively, for a system bus agent using on-board termination. V
REF
±125 mV, respectively, for a system bus agent using on-die termination.
REF
, minimum Vpin V
CTERM
Core
Frequency
, maximum.
CTERM
MinimumTypMaximumUnitNotes
1
1
2
,
CTERM
minimum
V
CTERM
REF
V
,
CTERM
maximum
uncertainty for ODT. V
V
REF_high
3
4
5
6
and
REF_high
Table 2-5.Power Good Signal DC Specifications
SymbolParameterMinimumMaximumUnitNotes
V
IL
V
IH
Input Low Voltage0.440V
Input High Voltage0.875V
Table 2-6.System Bus Clock Differential HSTL DC Specifications
1. The value specified for IOLapplies to all signals except for THRMALERT#.
2. The value specified for I
applies only to THRMALERT#, which is an open drain signal.
OL2
Table 2-9.LVTTL Signal DC Specifications
SymbolParameterMinimumMaximumUnitNotes
V
IL
V
IH
V
OL
V
OH
Input Low Voltage0.8V
Input High Voltage2.03.63V
Output Low Voltage0.4V
Output High Voltage2.4V
Electrical Specifications
3.143.33.47V3.3 V ±5
3.3 +5%
Min +
0.7*3.3V
1
2
Table 2-10 through Table 2-11 list the AC specifications for the processor’s clock and
SMBus (timing diagrams begin with Figure 2-1). The processor uses a differential HSTL
clocking scheme with a frequency of 200, 266, or 333 MHz. The SMBus is a subset of
the I2C* interface which supports operation of up to 100 kHz.
Table 2-10.System Bus Clock Differential HSTL AC Specifications (Sheet 1 of 2)
System
SymbolParameter
T
BCLKp Period2005.0nsFigure 2-1
period
T
skew
f
BCLK
T
jitter
T
high
T
low
T
period
T
skew
f
BCLK
T
jitter
T
high
T
low
System Clock Skew200100ps
BCLKp Frequency200200200 MHzFigure 2-1
BCLKp Input Jitter200100psFigure 2-1
BCLKp High Time2002.252.52.75nsFigure 2-1
BCLKp Low Time2002.252.52.75nsFigure 2-1
BCLKp Period2663.75nsFigure 2-1
System Clock Skew26660ps
BCLKp Frequency266266266 MHzFigure 2-1
BCLKp Input Jitter26650psFigure 2-1
BCLKp High Time2661.691.882.06nsFigure 2-1
BCLKp Low Time2661.691.882.06nsFigure 2-1
Bus
Clock
(MHz)
MinimumTypMaximumUnitFigureNotes
1
2
3
4
4
5
2
3
4
4
20Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Electrical Specifications
Table 2-10.System Bus Clock Differential HSTL AC Specifications (Sheet 2 of 2)
System
SymbolParameter
T
rise
T
fall
V
PP
Notes:
1. The system clock skew is ±100 ps.
2. Measured on cross-point of rising edge of BCLKp and falling edge of BCLKn. Long-term jitter is defined as peak-to-peak variation
measured by accumulating a large number of clock cycles and recording peak-to-peak jitter.
3. Cycle-to-cycle jitter is defined as peak-to-peak variation measured over 10,000 cycles peak-to-peak jitter.
4. Measured on cross point of rising edge of BCLKp and falling edge of BCLKn.
5. The system clock skew is ±60 ps.
6. V
PPmin
7. The measurement is taken at 40-60% of the signal and extrapolated to 20-80%.
BCLKp Rise Time
BCLKp Fall Time
Minimum Input Swing All600 mVFigure 2-1
is defined as the minimum input differential voltage which will cause no increase in the clock receiver timing.
1. Please refer to Figure 2-2 for the Standard Microsystems Corporation (SMSC)* clock waveform.
2. Bus Free Time is the minimum time allowed between request cycles.
SMSC Clock Frequency100kHz
SMSC Clock Period10µs
SMSC Clock High Time4.0µs
SMSC Clock Low Time4.7µs
SMSC Clock Rise Time1.0µs
SMSC Clock Fall Time0.3µs
SMBus Output Valid Delay1.0µs
SMBus Input Setup Time250ns
SMBus Input Hold Time0ns
Bus Free Time4.7µs
1
1
1
1
2
Figure 2-1.Generic Clock Waveform
T
high
T
rise
V
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet21
80%
pp
20%
T
Rise Time
=
rise
T
Fall Time
=
fall
T
High Time
=
high
T
Low Time
=
low
T
period
period
T
jitter
V
pp
T
low
T
fall
BCLKN
BCLKP
=T
Period
=
Long Term Peak-to-Peak Jitter
=
Peak-to-Peak Swing
=
T
jitter
000615
Figure 2-2.SMSC Clock Waveform
T
rise
75% V
T
T
rise
fall
cc
cc
Rise Time
=
Fall Time
=
SMSC
25% V
2.4.1Maximum Ratings
Table 2-12 contains the processor stress ratings. Functional operation at the absolute
maximum and minimum is neither implied nor guaranteed. The processor should not
receive a clock while subjected to these conditions. Functional operating conditions are
given in the DC tables. Extended exposure to the maximum ratings may affect device
reliability. Furthermore, although the processor contains protective circuitry to resist
damage from static electric discharge, one should always take precautions to avoid
static voltages or electric fields.
T
T
T
high
T
fall
high
low
High Time
=
Low Time
=
90% V
Electrical Specifications
V (3.3V)
cc
T
low
cc
000618
Table 2-12. Dual-Core Intel® Itanium® Processor Absolute Maximum Ratings
SymbolParameterMinimumMaximumUnitNotes
T
storage
T
shipping
V
core
V
cache
V
fixed
3.3VAny 3.3 V Supply Voltage with Respect to
V
in, SMBus
V
in, AGTL+
V
CTERM
V
in,TAP
Notes:
1. Storage temperature is temperature in which the processor can be stored for up to one year.
2. Shipping temperature is temperature in which the processor can be shipped for up to 24 hours.
3. Parameters are from third-party vendor specifications.
4. Maximum instantaneous voltage at receiver buffer input.
5. Specification includes V
respect to GND.
Processor Storage Temperature–1045°C
Processor Shipping Temperature–4575°C
Any V
Any V
Any V
GND
SMBus Buffer DC Input Voltage with
Respect to GND
AGTL+ Buffer DC Input Voltage with
Respect to GND
Any V
TAP Buffer DC Input Voltage with Respect
to GND.
Voltage with Respect to GND-0.31.55V
core
Voltage with Respect to GND-0.31.55V
cache
Voltage with Respect to GND-0.31.55V
fixed
–0.35.5V
–0.16.0V
–0.451.65V
Voltage with Respect to GND-0.451.65V
CTERM
-0.451.65V
in,AGTL+
and V
in,AGTL+ ASYNCHRONOUS
(AGTL+ asynchronous buffer DC input voltage with
1
2
3
3
4, 5
4
22Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Electrical Specifications
2.5System Bus Signal Quality Specifications and
Measurement Guidelines
Overshoot (or undershoot) is the absolute value of the maximum voltage above the
nominal V
undershoot specifications limit transitions beyond V
edge rates. The processor can be permanently damaged by repeated overshoot or
undershoot events on any input, output, or I/O buffer if the charge is large enough
(that is, if the overshoot/undershoot is great enough). Determining the impact of an
overshoot/undershoot condition requires knowledge of the magnitude, the pulse
duration, and the activity factor (AF).
2.5.1Overshoot/Undershoot Magnitude
Magnitude describes the maximum potential difference between a signal and its voltage
reference level. For the processor, both are referenced to GND, as shown in Figure 2-3.
It is important to note that overshoot and undershoot conditions are separate and their
impact must be determined independently. Overshoot/undershoot magnitude levels
must observe the absolute maximum specifications listed in Table 2-13 through
Table 2-17. These specifications must not be violated at any time, regardless of bus
activity or system state. Within these specifications are threshold levels that define
different allowed pulse duration. Provided that the magnitude of the overshoot/
undershoot is within the absolute maximum specifications, the pulse magnitude,
duration, and activity factors must all be used to determine if the overshoot/
undershoot pulse is within specifications.
voltage (or below GND), as shown in Table 2-3. The overshoot/
CTERM
or GND due to the fast signal
CTERM
Figure 2-3.System Bus Signal Waveform Exhibiting Overshoot/Undershoot
000588
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet23
Electrical Specifications
2.5.2Overshoot/Undershoot Pulse Duration
Pulse duration describes the total time that an overshoot/undershoot event exceeds the
overshoot/undershoot reference voltage (V
encompass several oscillations above the reference voltage. Multiple overshoot/
undershoot pulses within a single overshoot/undershoot event may need to be
measured to determine the total pulse duration.
Note:Oscillations below the reference voltage cannot be subtracted from the total overshoot/
undershoot pulse duration.
/GND). The total time could
CTERM
2.5.3Activity Factor
Activity factor (AF) describes the frequency of overshoot (or undershoot) occurrence
relative to a clock. Since the highest frequency of assertion of any common clock signal
is every other clock, an AF = 1 indicates that the specific overshoot (or undershoot)
waveform occurs every other clock cycle. Thus, an AF = 0.01 indicates that the specific
overshoot (or undershoot) waveform occurs one time in every 200 clock cycles. For
source synchronous signals (data, and associated strobes), the activity factor is in
reference to the strobe edge. The highest frequency of assertion of any source
synchronous signal is every active edge of its associated strobe. So, an AF = 1
indicates that the specific overshoot (or undershoot) waveform occurs every other
strobe cycle. The specifications provided in Table 2-14 through Table 2-17 show the
maximum pulse duration allowed for a given overshoot/undershoot magnitude at a
specific activity factor. Each table entry is independent of all others, meaning that the
pulse duration reflects the existence of overshoot/undershoot events of that magnitude
ONLY. A platform with an overshoot/undershoot that just meets the pulse duration for a
specific magnitude where the AF <1, means that there can be no other overshoot/
undershoot events, even of lesser magnitude (if AF = 1, then the event occurs at all
times and no other events can occur).
Note:AF for the common clock AGTL+ signals is referenced to BCLKn, and BCLKp frequency.
The wired-OR Signals (BINIT#, HIT#, HITM#, BNR#, TND#, BERR#) are common
clock AGTL+ signals.
Note:AF for source synchronous (2x) signals is referenced to STBP#[7:0], and STBN#[7:0].
The overshoot/undershoot specification for the processor is not a simple single value.
Instead, many factors are needed in order to correctly interpret the overshoot/
undershoot specification. In addition to the magnitude of the overshoot, the following
parameters must also be known: the width of the overshoot and the AF. To determine
the allowed overshoot for a particular overshoot event, the following must be done:
1. Determine the signal group that the particular signal falls into. For AGTL+ signals
operating in the 2x source synchronous domain, use Table 2-14 through
Table 2-16. If the signal is a wired-OR AGTL+ signal operating in the common clock
domain, use Table 2-15 through Table 2-17.
2. Determine the magnitude of the overshoot, or the undershoot (relative to GND).
3. Determine the activity factor (how often does this overshoot occur?).
4. Next, from the appropriate specification table, determine the maximum pulse duration (in nanoseconds) allowed. The pulse duration shown in the table refers to
the period where either the maximum overshoot (for high phase) and undershoot
(for low phase) occurred.
24Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Electrical Specifications
5. Compare the specified maximum pulse duration to the signal being measured. If
the pulse duration measured is less than the pulse duration shown in the table,
then the signal meets the specifications.
6. Undershoot events must be analyzed separately from overshoot events, as they are
mutually exclusive.
2.5.5Determining if a System Meets the Overshoot/Undershoot
Specifications
The overshoot/undershoot specifications listed in Table 2-13 through Table 2-17 specify
the allowable overshoot/undershoot for a single overshoot/undershoot event. However,
most systems will have multiple overshoot and/or undershoot events that each has
their own set of parameters (duration, AF and magnitude). While each overshoot on its
own may meet the overshoot specification, the total impact of all overshoot events may
cause the system to fail. A guideline to ensure a system passes the overshoot and
undershoot specifications is shown below:
1. Ensure that no signal ever exceeds V
2. If only one overshoot/undershoot event magnitude occurs, ensure that it meets the
specifications listed in Table 2-13 through Table 2-17.
3. If multiple overshoots and/or multiple undershoots occur, measure the worst-case
pulse duration for each magnitude and compare the results against the AF = 1
specifications. If all of these worst-case overshoot or undershoot events meet the
specifications (measured time < specifications) in the table (where AF = 1), then
the system passes.
CTERM
or GND.
2.5.6Wired-OR Signals
To ensure platform compatibility between the processors, system bus signals must
meet certain overshoot and undershoot requirements. The system bus wired-OR
signals (BINIT#, HIT#, HITM#, BNR#, TND#, BERR#) have the same absolute
overshoot and undershoot specification as the Source Synchronous AGTL+ Signals, but
they have different time-dependent overshoot/undershoot requirements.
Table 2-13. Source Synchronous AGTL+ Signal Group and Wired-OR Signal Group Absolute
The VR shall provide a selectable output voltage controlled via multiple binary weighted
Voltage Identification (VID) inputs. The VID value (high = 1; low = 0) is defined in
Table 2-20. VID pins will be controlled by the processor.
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet29
Electrical Specifications
Table 2-20. Processors Core Voltage Identification Code (V
30Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Electrical Specifications
2.7System Bus Clock and Processor Clocking
The BCLKn and BCLKp inputs control the operating frequency of the processor system
bus interface. All processor system bus timing parameters are specified with respect to
the falling edge of BCLKn and rising edge of BCLKp. The address pins A[21:17]# will be
used to specify the system bus frequency during reset. The processor will ensure that
the correct bus/core ratio is elected based on the bus frequency that is specified during
reset.
Cold Reset Sequence:
• The configuration pins (A[21:17]#) must be asserted the entire time RESET# is
asserted.
• RESET# must be asserted before PWRGOOD is asserted.
• The duration from the assertion of PWRGOOD to the deassertion of RESET# must
be 1 millisecond minimum.
• After RESET# is deasserted, all the configuration, including pins A[21:17]#, must
remain valid for 2 BCLKs (minimum) to 3 BCLKs (maximum).
• BCLK is shown as a time reference to the BCLK period. It is not a requirement that
this is BCLKn or BCLKp signal.
• Configuration signals other than A[21:17]# must be asserted 4 BCLKs prior to the
deasserted edge of RESET# and must remain valid for 2 BCLKs (minimum) to 3
BCLKs (maximum) after the deasserted edge of RESET#.
Figure 2-5 outlines the timing relationship between the configuration pins, RESET# and
PWRGOOD for cold reset.
Figure 2-5.System Bus Reset and Configuration Timings for Cold Reset
t
T
A
BCLK
PWRGOOD
RESET#
Bus Ratio
(A[21:17]#)
Additional
Configuration
Signals
t
-4t-3
T
C
TA= 1.15 ns minimum; (set up time to BCLK for deassertion edge of RESET#)
TB= 1 ms minimum for cold reset
TC= Bus ratio signals must be asserted no later than RESET#
TD= 2 BCLKs minimum, 3 BCLKs maximum
TE= 4 BCLKs minimum
TF= 2 BCLKs minimum, 3 BCLKs maximum
T
B
t
-2t-1t0
T
E
t2t
1
T
D
T
F
3
000859b
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet31
Warm Reset Sequence:
• PWRGOOD remains high throughout the entire sequence, as power is already
available and stable to the processor.
• The configuration pins (A[21:17]#) must be asserted the entire time RESET# is
asserted.
• The duration from the assertion of RESET# to the deassertion of RESET# must be 1
millisecond minimum.
• After RESET# is deasserted, the configuration pins must remain valid for two
BCLKs (minimum) to three BCLKs (maximum).
• BCLK is shown as a time reference to the BCLK period. It is not a requirement that
this is BCLKn or BCLKp signal.
• Configuration signals other than A[21:17]# must be asserted four BCLKs prior to
the deasserted edge of RESET# and must remain valid for two BCLKs (minimum) to
three BCLKs (maximum) after the deasserted edge of RESET#.
Figure 2-6 outlines the timing relationship between the configuration pins, RESET# and
PWRGOOD for warm reset.
Figure 2-6. System Bus Reset and Configuration Timings for Warm Reset
Electrical Specifications
BCLK
PWRGOOD
RESET#
Bus Ratio
(A[21:17]#)
Additional
Configuration
Signals
t
-4t-3
T
C
T
B
t
-2t-1t0
T
E
t1t2t
T
A
T
D
T
F
TA= 1.15 ns minimum; (set up time to BCLK for deassertion edge of RESET#)
TB= 1 ms minimum for warm reset
TC= Bus ratio signals must be asserted no later than RESET#
TD= 2 BCLKs minimum, 3 BCLKs maximum
TE= 4 BCLKs minimum
TF= 2 BCLKs minimum, 3 BCLKs maximum
3
000777b
32Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Electrical Specifications
2.8Recommended Connections for Unused Pins
Pins that are unused in an application environment (as opposed to testing
environment) should be connected to the states listed in Table 2-21. Pins that must be
used in an application are stated as such and do not have a recommended state for
unused connection.
Table 2-21. Connection for Unused Pins
Pins/Pin Groups
AGTL+ pinsH
Recommended
Connections
Notes
1, 2
HSTL Clock SignalsMust be used
All Power SignalsMust be used
PWRGOODMust be used
34Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Pinout Specifications
0
21314151617181920
2232425
3Pinout Specifications
This chapter describes the Dual-Core Intel Itanium processor 9000 and 9100 series
signals and pinout.
Note:The pins labeled “N/C” must remain unconnected. The processor uses a JEDEC
standard pin naming convention.
In this chapter, pin names are the actual names given to each physical pin of the
processor. System bus signal names are the names associated with the functions of
those pins. For those pins associated with multiple functions, their pin names and
system bus signal names are not necessarily identical.
Figure 3-1 shows the processor pin location diagram from the top view.
Figure 3-1. Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Pinout
AH AG AF AE AD AC AB AA Y W V U T R P N M L K J H G F E D C B A
62Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Pinout Specifications
Table 3-2.Pin/Signal Information Sorted by Pin Location (Sheet 14 of 15)
Pin Name
BR0#BREQ0#AF16IN/OUT
GNDGNDAF17IN
BR3#BREQ3#AF18IN
GNDGNDAF19IN
PPODGD#PPODGD#AF20OUTPower pod signal
GNDGNDAF21IN
LINT0INTAF22IN
LINT1NMIAF24IN
GNDGNDAG02IN
TUNER[2]AG03IN
GNDGNDAG04IN
N/CAG05
GNDGNDAG06IN
TDITDIAG07INJTAG
GNDGNDAG08IN
TCKTCKAG09INJTAG
GNDGNDAG10IN
N/CAG11
GNDGNDAG12IN
BCLKpCLKAG13IN
GNDGNDAG14IN
CPUPRES#CPUPRES#AG15OUTPower pod signal
GNDGNDAG16IN
N/CAG17
GNDGNDAG18IN
N/CAG19
GNDGNDAG20IN
N/CAG21
GNDGNDAG22IN
IGNNE#IGNNE#AG23N/C
GNDGNDAG24IN
THRMTRIP#THRMTRIP#AG25OUTThermal trip
GNDGNDAH01IN
TUNER[1]AH03IN
N/CAH05
TDOTDOAH07OUTJTAG
TMSTMSAH09INJTAG
N/CAH11
BCLKnBCLKNAH13IN
PWRGOODPWRGOODAH15IN
N/CAH17
N/CAH19
N/CAH21
System Bus
Signal Name
Pin
Location
Input/OutputNotes
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet63
Table 3-2.Pin/Signal Information Sorted by Pin Location (Sheet 15 of 15)
Pin Name
A20M#A20M#AH23N/C
FERR#FERR#AH25OUT
System Bus
Signal Name
Pin
Location
Input/OutputNotes
§
Pinout Specifications
64Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Mechanical Specifications
4Mechanical Specifications
This chapter provides the mechanical specifications of the Dual-Core Intel Itanium
processor 9000 and 9100 series.
4.1Processor Package Dimensions
Figure 4-1 through Figure 4-5 provide package mechanical drawings and dimensions of
the processor. Table 4-1 and Table 4-2 provide additional details on the package
dimensions. The main components of processor package are identified in Figure 4-2. All
specified package dimensions are in millimeters.
Figure 4-1 illustrates key package mechanical features. These features enable package
integration with socket, power pod, and cooling solution.
• Vcore, Vcache, Vfixed, GND, and VID Pads: Contact pads for delivering power
and I/O signals from the voltage regulator to the processor through its substrate.
• Socket Alignment Keyways: They define package position in X and Y direction
with respect to socket for proper alignment of package pins to socket contact holes.
• Pin Shroud Alignment Keyways: They define pin shroud position in X and Y
direction with respect to processor.
• Pin 1 Indicators: Identifies package orientation with respect to socket and
motherboard.
• Integrated Heat Spreader (IHS): Enhances dissipation of heat generated by the
processor. Provides interface surface between processor and cooling solution.
• Substrate: Processor mechanical and electrical integration vehicle with the
motherboard and processor enabling components.
• Pin Field (Grid): 28 x 25 partially-filled pin field for transmitting signals to and
from processor to motherboard.
• Voltage Regulator Connector Back Plate Keyway: It defines the VR connector
back plate position in X and Y direction with respect to the processor.
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet65
Figure 4-1. Processor Package
Mechanical Specifications
G
1
H
1
A1
J
2
A25AH25
J
1
B
1
AH1
Bottom View
C
1
H
2
G
2
Side View
B
C
2
B
2
A1
Package
C
L
D
IHS
C
L
1
A
Top View
A
Front View
001349
66Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Mechanical Specifications
Table 4-1.Processor Package Dimensions
Figure 4-2.Package Height and Pin Dimensions
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet67
Note: Keepout zones indicate no components will be on the processor package.
70Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Mechanical Specifications
4.1.1Voltage Regulator (MVR) to Processor Package Interface
Critical package mechanical requirements at its interface with the MVR are identified in
Figure 4-6 and Table 4-3. The processor interface boundary conditions with which MVR
must comply during and after installation are outlined in Table 4-3. These requirements
are intended to minimize potential damage to the processor that may result from
installation of the MVR.
Figure 4-6.Processor to MVR Interface Loads
Y
T
X
X
Z
Z
90
P
-z
T
A
90
y
P
+z
Processor Heatsink
Processor Heatsink
IHS
Socket
Table 4-3.Processor Package Load Limits at Power Tab (Sheet 1 of 2)
ParameterDescriptionValue
AFinal position of the package at the
power tab (unloaded) with respect to
system board
PAllowable load on the package in +z
and -z direction
dAllowable displacement at the
processor power tab in z direction
under load P
TzAllowable torque on the package tip in
z axis
3.8+/-
0.1mm
22.25N max
+/- 0.3 mm
max
0Package loading in Y direction is not
1
Position of the processor power tab is
based on the height of the mPGA700
ZIF socket height from the mother
post SMT
allowed. Hence, zero torque in Z-axis
Substrate
Mother Board
Comments
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet71
Table 4-3.Processor Package Load Limits at Power Tab (Sheet 2 of 2)
ParameterDescriptionValue
TxAllowable torque at the package power
T+yAllowable torque at the package power
tab in X axis
tab in +y direction
Allowable torque at the package power
tab in -y direction
0.57Nm max
1.24 Nm max Torque on the package edge in +Y
T-y
Notes:
1. Load determination done with 100-lb. load on the processor heatsink.
1
0.93Nm
max
direction is determined by the load
applied in -Z and the distance from the
edge the package to the socket.
Torque on the package edge in -Y
direction is determined by the load
applied in +Z and the distance from
the edge the package to the heatsink
base.
To determine T+y, distance from the
edge the package to the socket of
55.7mm is applied
To determine T-y, distance from the
edge the package to the heatsink
pedestal of 42mm is applied
4.2Package Marking
Mechanical Specifications
Comments
The following section details the processor top-side and bottom-side markings for
engineering samples and production units. This is provided to aid in identification.
Specific details regarding individual fields in the product markings will be furnished in a
future release of this document.
4.2.1Processor Top-Side Marking
The top-side mark is a laser marking on the IHS. Figure 4-7 shows the general location
of the processor top-side mark that provides the following information:
• Intel
• Itanium® Processor Family Legal Mark
• Assembly Process Order (APO) Number
• Unit Serial Number
• 2D Matrix Mark
®
72Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Mechanical Specifications
Figure 4-7.Processor Top-Side Marking on IHS
4.2.2Processor Bottom-Side Marking
The processor bottom-side mark for the product is a laser marking on the pin side of
the interposer. Figure 4-8 shows the placement of the laser marking on the pin side of
interposer. The processor bottom-side mark provides the following information:
• Product ID
• S-Spec
• Finish Process Order (FPO)
• 2D Matrix Mark
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet73
Figure 4-8. Processor Bottom-Side Marking Placement on Interposer
Laser Marking
2D Matrix Mark (see notes)
2D Matrix Mark (see notes)
Laser Marking
Mechanical Specifications
§
74Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Thermal Specifications
5Thermal Specifications
This chapter provides a description of the thermal features relating to the Dual-Core
Intel Itanium processor 9000 and 9100 series.
5.1Thermal Features
The processor has an internal thermal circuit which senses when a certain temperature
is reached on the processor core. This circuit is used for controlling various thermal
states. In addition, an on-chip thermal diode is available for use by the thermal sensing
device on the processor. Figure 5-1 shows the relationship between temperature, time,
and the thermal alert, enhanced thermal management (ETM), and thermal trip points.
Note:Figure 5-1 is not intended to show a linear relationship in time or temperature as a
processor's thermal state advances from one state to the next state when the cooling
solution fails to control the processor temperature, as this is affected by many factors
such as cooling solution performance degradation and processor workload variations.
Figure 5-1.Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Thermal Features
5.1.1Thermal Alert
THRMALERT# is a programmable thermal alert signal which is part of the processor
system management feature. THRMALERT# is asserted when the measured
temperature from the processor thermal diode equals or exceeds the temperature
threshold data programmed in the high temp (THIGH) or low temp (TLOW) registers on
the sensor. Intel recommends using the upper temperature reference byte listed in the
Processor Information ROM when programming the THIGH register (see Chapter 6 for
more details). This signal can be used by the platform to implement thermal regulation
features such as generating an external interrupt to tell the operating system that the
processor core die temperature is increasing.
Thermal Alert
Time
ETM
Thermal Trip
000653b
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet75
5.1.2Enhanced Thermal Management
ETM is a power and thermal protection feature. On the Dual-Core Intel Itanium
processor 9000 and 9100 series, ETM uses power and thermal sensing devices on the
die to monitor entry points, indicating dangerous operation exceeding the thermal or
power specification. Once the sensing devices observe the temperature rising above
the power or thermal entry point, the processor will enter a low power mode of
execution and notify the system by sending a Correctable Machine Check Interrupt
(CMCI). The processor will remain in this low power mode until the power and
temperature decrease below the entry points and remain there for approximately one
second, at which point it will send another CMCI and resume normal operation. If the
power and temperature cannot be reduced, and continue to rise to critical levels, the
processor will assert Power Trip or Thermal Trip. The ETM feature may be disabled
through the PAL.
5.1.3Power Trip
The Dual-Core Intel Itanium processor 9000 and 9100 series protects itself and the
MVR from catastrophic over power by use of an internal power sensor. The sensor trip
point is set above the normal operating power to ensure that there are no false trips.
The processor will signal a continuable MCA when the power draw exceeds a safe
operating level.
Thermal Specifications
Warning:Data will be lost if the MVR overheats and shuts down as a result of an extended over
power condition.
Once power trip is activated, the processor can continue operation, but may continue to
signal continuable MCAs as long as the over power condition exists.
5.1.4Thermal Trip
The Dual-Core Intel Itanium processor 9000 and 9100 series protects itself from
catastrophic overheating by use of an internal thermal sensor. The sensor trip point is
set well above the normal operating temperature to ensure that there are no false trips.
The processor will stop all execution when the junction temperature exceeds a safe
operating level.
Warning:Data will be lost if the processor goes into thermal trip (signaled to the system by the
THRMTRIP# pin).
Once thermal trip is activated, the processor remains stopped until RESET# is asserted.
The processor case temperature must drop below the specified maximum before
issuing a reset to the processor. Please see Section 5.2 for details on case temperature.
5.2Case Temperature
See Table 5-1 for the case temperature specifications for the Dual-Core Intel Itanium
processor 9000 and 9100 series. The case temperature is defined as the temperature
measured at the center of the top surface of the IHS.
Warning:Data may be lost if the case temperature exceeds the specified maximum.
76Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Thermal Specifications
2
Table 5-1.Case Temperature Specification
SymbolParameter
TcaseCase Temperature1.6GHz/24MB576°C
Core
Frequency
1.6GHz/18MB576°C
1.6GHz/9MB576°C
1.42GHz/12MB576°C
1.4GHz/12MB576°C
1.6GHz/6MB574°C
MinimumMaximumUnitNotes
Figure 5-2 contains dimensions for the thermocouple location on the processor
package. This is the recommended location for placement of a thermocouple for case
temperature measurement.
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet77
Thermal Specifications
78Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
System Management Feature Specifications
6System Management Feature
Specifications
The Dual-Core Intel Itanium processor 9000 and 9100 series includes a system
management bus (SMBus) interface. This chapter describes the features of the SMBus
and SMBus components.
6.1System Management Bus
6.1.1System Management Bus Interface
The processor includes an Itanium processor family SMBus interface which allows
access to several processor features. The system management components on the
processor include two memory components (EEPROMs) and a thermal sensing device
(digital thermometer). The processor information EEPROM (PIROM) is programmed by
Intel with manufacturing and feature information specific to the Dual-Core Intel
Itanium processor 9000 and 9100 series. This information is permanently writeprotected. Section 6.2 provides details on the PIROM. The other EEPROM is a scratch
EEPROM that is available for other data at the system vendor’s discretion. The thermal
sensor can be used in conjunction with the information in the PIROM and/or the Scratch
EEPROM for system thermal monitoring and management. The thermal sensing device
on the processor provides an accurate means of acquiring an indicator of the junction
temperature of the processor core die. The thermal sensing device is connected to the
anode and cathode of the processor on-die thermal diode. SMBus implementation on
the processor uses the clock and data signals as defined by SMBus specifications.
6.1.2System Management Interface Signals
Table 6-1 lists the system management interface signals and their descriptions. These
signals are used by the system to access the system management components via the
SMBus.
Table 6-1.System Management Interface Signal Descriptions
Signal NamePin CountDescription
3.3V1Voltage supply for EEPROMs and thermal sensor.
SMA[2:0]3Address select passed through from socket.
SMSC1System management bus clock.
SMSD1System management serial address/data bus.
SMWP1Scratch EEPROM write protect.
THRMALERT#1Temperature alert from the thermal sensor.
Figure 6-1 shows the logical schematics of SMBus circuitry on the processor and shows
how the various system management components are connected to the SMBus. The
reference to the System Board at the lower left corner of Figure 6-1 shows how SMBus
address configuration for multiple processors can be realized with resistor stuffing
options.
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet79
Figure 6-1.Logical Schematic of SMBus Circuitry
System Management Feature Specifications
10K
10K
SMA0
SMA1
3.3V
10K
V
A0
A1
A2
A0
A1
A2
SMA23.3V
CC
Processor
Information
ROM
V
CC
Scratch
EEPROM
SC
SD
SC
SD
WP
10K10K
10K
SMWP
SMSD
SMSCTHRMALERT#
Intel® Itanium® 2 Processor
VCC
A0
Thermal
Sensing
A1
Device
ALERT
Core
THERMDA
THERMDC
STBY
SC
SD
System Board
3.3V
Stuffing
Options
System Board
3.3V
10K
NOTE:
1. Actual implementation may vary.
2. For use in general understanding of the architecture.
000668b
80Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
System Management Feature Specifications
6.1.3SMBus Device Addressing
Of the addresses broadcast across the SMBus, the memory components claim those of
the form “1010XXYZb”. The “XX” and “Y” bits are used to enable the devices on the
processor at adjacent addresses. The Y bit is hard-wired on the processor to GND (‘0’)
for the Scratch EEPROM and pulled to 3.3 V (‘1’) for the processor information ROM.
The “XX” bits are defined by the processor socket via the SMA0 and SMA1 pins on the
processor connector. These address pins have a weak pull-down (10 k ) to ensure that
the memory components are in a known state in systems which do not support the
SMBus, or only support a partial implementation. The “Z” bit is the read/write bit for
the serial bus transaction.
The thermal sensing device internally decodes one of three upper address patterns
from the bus of the form “0011XXXZb”, “1001XXXZb” or “0101XXXZb”. The device’s
addressing, as implemented, uses SMA2 and SMA1 and includes a Hi-Z state for the
SMA2 address pin. Therefore, the thermal sensing device supports six unique resulting
addresses. To set the Hi-Z state for SMA2, the pin must be left floating. The system
should drive SMA1 and SMA0, and will be pulled low (if not driven) by the 10 k pulldown resistor on the processor substrate. Attempting to drive either of these signals to
a Hi-Z state would cause ambiguity in the memory device address decode, possibly
resulting in the devices not responding, thus timing out or hanging the SMBus. As
before, the “Z” bit is the read/write bit for the serial bus transaction.
Figure 6-1 shows a logical diagram of the pin connections. Table 6-2 and Table 6-3
describe the address pin connections and how they affect the addressing of the
devices.
Note:Addresses of the form “0000XXXXb” are Reserved and should not be generated by an
SMBus master. Also, system management software must be aware of the processor
select in the address for the thermal sensing device.
Table 6-2.Thermal Sensing Device SMBus Addressing on the Dual-Core Intel® Itanium
Processor 9000 and 9100 series
Address (Hex)Upper Address
3Xh0011000011000Xb
0011010011010Xb
5Xh0101Z
0101Z
9Xh1001101001100Xb
1001111001110Xb
Notes:
1. Upper address bits are decoded in conjunction with the select pins.
2. A tri-state or “Z” state on this pin is achieved by leaving this pin unconnected.
1
Processor Select8-Bit Address Word on Serial Bus
SMA2SMA1b[7:0]
2
b
00101001Xb
10101011Xb
®
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet81
System Management Feature Specifications
Table 6-3.EEPROM SMBus Addressing on the Dual-Core Intel® Itanium® Processor 9000
and 9100 Series
Upper
Address
(Hex)
A0h/A1h1010000XScratch EEPROM 1
A2h/A3h1010001XProcessor Information ROM 1
A4h/A5h1010010XScratch EEPROM 2
A6h/A7h1010011XProcessor Information ROM 2
A8h/A9h1010100XScratch EEPROM 3
AAh/ABh1010101XProcessor Information ROM 3
ACh/ADh1010110XScratch EEPROM 4
AEh/AFh1010111XProcessor Information ROM 4
Notes:
1. Although this addressing scheme is targeted for up to four-way MP systems, more processors can be supported
by using a multiplexed (or separate) SMBus implementation.
Address
Bits 7–4
Processor Select
1
(SMA1)
Bit 3
(SMA0)
Bit 2
Memory
Device
Select
Bit 1Bit 0
6.2Processor Information ROM
An electrically programmed read-only memory (ROM) provides information about the
processor. The checksum bits for each category provide error correction and serve as a
mechanism to check whether data is corrupted or not. This information is permanently
write-protected. Table 6-4 shows the data fields and formats provided in the memory.
Read/
Write
Device Addressed
Note:The data, in byte format, is written and read serially, with the most significant bit first.
Table 6-4.Processor Information ROM Format (Sheet 1 of 3)
Offset/
Section
Header
00h8Data Format RevisionTwo 4-bit hex digitsStart with 00h
01h16EEPROM SizeSize in bytes (MSB first)Use a decimal to hex
03h8Processor Data AddressByte pointer, 00h if not present0Eh
04h8Processor Core AddressByte pointer, 00h if not present17h
05h8Processor Cache AddressByte pointer, 00h if not present28h
06h8Processor Data AddressByte pointer, 00h if not present37h
07h8Part Number Data AddressByte pointer, 00h if not present3Eh
08h8Thermal Reference Data
09h8Feature Data AddressByte pointer, 00h if not present67h
0Ah8Other Data AddressByte pointer, 00h if not present7Ah
# of
Bits
Address
FunctionNotesExamples
transfer; 128 bytes =
0080h:
• 02h[7:4] = 0000
• 02h[3:0] = 0000
• 01h[7:4] = 1000
• 01h[3:0] = 0000
Byte pointer, 00h if not present63h
82Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
System Management Feature Specifications
Table 6-4.Processor Information ROM Format (Sheet 2 of 3)
Offset/
Section
0Bh16ReservedReserved for future use0000h
0Dh8Checksum1 byte checksumAdd up by byte and take
Processor
0Eh48S-spec NumberSix 8-bit ASCII charactersS-spec number of S123
14h2Sample/Production00b = Sample only (MSB First)00000001b = Production
15h8ReservedReserved for future use00h
16h8Checksum1 byte checksumAdd up by byte and take
Core
17h8Architecture RevisionFrom CPUID
18h8Processor Core FamilyFrom CPUIDTaken from
19h8Processor Core ModelFrom CPUIDTaken from
1Ah8Processor Core SteppingFrom CPUIDTaken from
1Bh24ReservedReserved for future use000000h
1Eh16Maximum Core FrequencyFour 4-bit hex digits (in MHz)1 GHz = 1000h
20h12Maximum System Bus
22h16Core Voltage IDVoltage in four 4-bit hex digits
24h8Core Voltage Tolerance, High Edge finger tolerance in mV, +
25h8Core Voltage Tolerance, LowEdge finger tolerance in mV, –
26h8ReservedReserved for future use00h
27h8Checksum1 byte checksumAdd up by byte and take
Cache
28h32ReservedReserved for future use00000000h
2Ch16Cache SizeFour 4-bit hex digits (in Kbytes)3072 Kbytes = 3072h
2Eh64ReservedReserved for future usex0h
36h8Checksum1 byte checksum
1 indicates EEPROM data
for specified field is valid.
processor
2’s complement.
84Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
System Management Feature Specifications
Notes:
1. Refer to the Intel® Itanium™ Architecture Software Developer’s Manual for details on CPUID registers.
2. The translation is using BCD.
3. Itanium 9000 and 9100 series use a hex-to-decimal conversion
6.3Scratch EEPROM
Also available on the SMBus interface on the processor is an EEPROM which may be
used for other data at the system vendor’s discretion (Intel will not be using the scratch
EEPROM). The data in this EEPROM, once programmed, can be write-protected by
asserting the active-high SMWP signal. This signal has a weak pull-down (10 k ) to
allow the EEPROM to be programmed in systems with no implementation of this signal.
6.4Processor Information ROM and Scratch EEPROM
Supported SMBus Transactions
The processor information ROM and scratch EEPROM responds to three of the SMBus
packet types: current address read, random address read, and sequential read.
Table 6-5 shows the format of the current address read SMBus packet. The internal
address counter keeps track of the address accessed during the last read or write
operation, incremented by one. Address “roll over” during reads is from the last byte of
the last eight byte page to the first byte of the first page. “Roll over” during writes is
from the last byte of the current eight byte page to the first byte of the same page.
Table 6-6 shows the format of the random read SMBus packet. The write with no data
loads the address desired to be read. Sequential reads may begin with a current
address read or a random address read. After the SMBus host controller receives the
data word, it responds with an acknowledge. This will continue until the SMBus host
controller responds with a negative acknowledge and a stop.
Table 6-7 shows the format of the byte write SMBus packet. The page write operates
the same way as the byte write, except that the SMBus host controller does not send a
stop after the first data byte and acknowledge. The Scratch EEPROM internally
increments its address. The SMBus host controller continues to transmit data bytes
until it terminates the sequence with a stop. All data bytes will result in an acknowledge
from the Scratch EEPROM. If more than eight bytes are written, the internal address
will “roll over” and the previous data will be overwritten.
In Table 6-5 through Table 6-7, ‘S’ represents the SMBus start bit, ‘P’ represents a stop
bit, ‘R’ represents a read, ‘W’ represents a write bit, ‘A’ represents an acknowledge, and
‘///’ represents a negative acknowledge. The shaded bits are transmitted by the
processor information ROM or Scratch EEPROM and the bits that are not shaded are
transmitted by the SMBus host controller. In the tables, the data addresses indicate
eight bits. The SMBus host controller should transmit eight bits, but as there are only
128 addresses, the most significant bit is a don’t care.
Table 6-5.Current Address Read SMBus Packet
Device
S
Address
17 bits118 bits11
RAData///P
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet85
Table 6-6.Random Address Read SMBus Packet
System Management Feature Specifications
Device
S
Address
17 bits118 bits117 bits118 bits11
WA
Data
Address
AS
Table 6-7.Byte Write SMBus Packet
Device
S
Address
17 bits018 bits18 bits11
WA
Data
Address
ADataAP
6.5Thermal Sensing Device
The Dual-Core Intel Itanium processor 9000 and 9100 series thermal sensing device
provides a means of acquiring thermal data from the processor. The accuracy of the
thermal reading is expected to be better than ±5 °C. The thermal sensing device is
composed of control logic, SMBus interface logic, a precision analog to digital converter,
and a precision current source. The thermal sensing device drives a small current
through a thermal diode located on the processor core and measures the voltage
generated across the thermal diode by the current. With this information, the thermal
sensing device computes a byte of temperature data. Software running on the
processor or on a micro-controller can use the temperature data from the thermal
sensing device to thermally manage the system.
The thermal sensing device provides a register with a data byte (seven bits plus sign)
which contains a value corresponding to the sampled output of the thermal diode in the
processor core. The value of the byte read from the thermal sensor is always higher
than the actual processor core temperature; therefore, the offset from the reading
needs to be subtracted to obtain an accurate reading of the processor core
temperature. This data can be used in conjunction with the upper temperature
reference byte (provided in the Processor Information ROM) for thermal management
purposes. The temperature data from the thermal sensor can be read out digitally
using an SMBus read command (see Section 6.6). The thermal sensor detects when
SMBus power is applied to the processor, and resets itself at power-up.
Device
Address
RAData///P
The thermal sensing device also contains alarm registers to store thermal reference
threshold data. These values can be individually programmed on the thermal sensor. If
the measured temperature equals or exceeds the alarm threshold value, the
appropriate bit is set in the thermal sensing device status register, which is also
brought out to the processor system bus via the THRMALERT# signal (see
Section 6.1.1 for more details). At power-up, the appropriate alarm register values
need to be programmed into the thermal sensing device via the SMBus. It is
recommended that the upper thermal reference threshold byte (provided in the
processor information ROM) be used for setting the upper threshold value in the alarm
register. To account for the offset inherent in the thermal sensing device reading, the
actual programmed value of the upper threshold value in the alarm register should be
the sum of the upper thermal reference threshold byte and the thermal calibration
offset byte (both provided in the PIROM).
When polling the thermal sensing device on the processor to read the processor
temperatures, it is recommended that the polling frequency be every 0.5 to 1 second.
86Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
The thermal sensing device responds to five of the SMBus packet types: write byte,
read byte, send byte, receive byte, and alert response address (ARA). The send byte
packet is used for sending one-shot commands only. The receive byte packet accesses
the register commanded by the last read byte packet. If a receive byte packet was
preceded by a write byte or send byte packet more recently than a read byte packet,
then the behavior is undefined. Table 6-8 through Table 6-12 diagram the five packet
types. In these tables, ‘S’ represents the SMBus start bit, ‘P’ represents a stop bit, ‘Ack’
represents an acknowledge, and ‘///’ represents a negative acknowledge. The shaded
bits are transmitted by the thermal sensor and the unshaded bits are transmitted by
the SMBus host controller. Table 6-13 shows the encoding of the command byte.
Table 6-8.Write Byte SMBus Packet
SAddressWriteAckCommandAckDataAckP
17 bits118 bits18 bits11
Table 6-9.Read Byte SMBus Packet
SAddressWriteAckCommandAckSAddressReadAckData
17 bits018 bits117 bits118 bits11
Table 6-10. Send Byte SMBus Packet
SAddressWriteAckCommandAckP
17 bits118 bits1
Table 6-11. Receive Byte SMBus Packet
SAddressReadAckData///P
17 bits118 bits11
Table 6-12. ARA SMBus Packet
SARAReadAckAddress///P
10001 100111001 101111
//
P
/
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet87
Table 6-13. Command Byte Bit Assignment
RegisterCommandReset StateFunction
RESERVED00hN/AReserved for future use.
RRT01hN/ARead processor core thermal data.
RS02hN/ARead status byte (flags, busy signal).
RC03h0000 0000Read configuration byte.
RCR04h0000 0010Read conversion rate byte.
RESERVED05h0111 1111Reserved for future use.
RESERVED06h1100 1001Reserved for future use.
RRHL07h0111 1111Read processor core thermal diode T
RRLL08h1100 1001Read processor core thermal diode T
WC09hN/AWrite configuration byte.
WCR0AhN/AWrite conversion rate byte.
RESERVED0BhN/AReserved for future use.
RESERVED0ChN/AReserved for future use.
WRHL0DhN/AWrite processor core thermal diode T
WRLL0EhN/AWrite processor core thermal diode T
OSHT0FhN/AOne shot command (use send byte packet).
RESERVED10h – FFhN/AReserved for future use.
All of the commands are for reading or writing registers in the thermal sensor except
the one-shot command (OSHT). The one-shot command forces the immediate start of
a new voltage-to-temperature conversion cycle. If a conversion is in progress when the
one-shot command is received, then the command is ignored. If the thermal sensing
device is in standby mode when the one-shot command is received, a conversion is
performed and the sensor returns to standby mode. If the thermal sensor is in autoconvert mode and is between conversions, then the conversion rate timer resets, and
the next automatic conversion takes place after a full delay elapses. Please refer to
Section 6.7.4 for further detail on standby and auto-convert modes.
System Management Feature Specifications
limit.
HIGH
limit.
LOW
limit.
HIGH
limit.
LOW
The default command after reset is the reserved value (00h). After reset, receive byte
packets will return invalid data until another command is sent to the thermal sensing
device.
6.7Thermal Sensing Device Registers
The system management software can configure and control the thermal sensor by
writing to and interacting with different registers in the thermal sensor. These registers
include a thermal reference register, two thermal limit registers, a status register, a
configuration register, a conversion rate register, and other reserved registers. The
following subsections describe the registers in detail.
6.7.1Thermal Reference Registers
The processor core and thermal sensing device internal thermal reference registers
contain the thermal reference value of the thermal sensing device and the processor
core thermal diodes. This value ranges from +127 to –128 decimal and is expressed as
a two’s complement, eight-bit number. These registers are saturating, that is, values
above 127 are represented at 127 decimal, and values below –128 are represented as
–128 decimal.
88Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
System Management Feature Specifications
6.7.2Thermal Limit Registers
The thermal sensing device has two thermal limit registers; they define high and low
limits for the processor core thermal diode. The encoding for these registers is the
same as for the thermal reference registers. If the diode thermal value equals or
exceeds one of its limits, then its alarm bit in the status register is triggered. This
indication is also brought out to the processor system bus via the THRMALERT# signal.
6.7.3Status Register
The status register shown in Table 6-14 indicates which (if any) of the thermal value
thresholds have been exceeded. It also indicates if a conversion is in progress or if an
open circuit has been detected in the processor core thermal diode connection. Once
set, alarm bits stay set until they are cleared by a status register read. A successful
read to the status register will clear any alarm bits that may have been set, unless the
alarm condition persists. Note that the THRMALERT# interrupt signal is latched and is
not automatically cleared when the status flag bit is cleared. The latch is cleared by
sending the Alert Response Address (0001100) on the SMBus.
Table 6-14. Thermal Sensing Device Status Register
BitNameFunction
7 (MSB)BUSYA one indicates that the device’s analog to digital converter is busy converting.
6RESERVEDReserved for future use.
5RESERVEDReserved for future use.
4RHIGHA one indicates that the processor core thermal diode high temperature alarm has
3RLOWA one indicates that the processor core thermal diode low temperature alarm has
2OPENA one indicates an open fault in the connection to the processor core diode.
1RESERVEDReserved for future use.
0 (LSB)RESERVEDReserved for future use.
been activated.
been activated.
6.7.4Configuration Register
The configuration register controls the operating mode (standby vs. auto-convert) of
the thermal sensing device. Table 6-15 shows the format of the configuration register.
If the RUN/STOP bit is set (high) then the thermal sensing device immediately stops
converting and enters standby mode. The thermal sensing device will still perform
analog-to-digital conversions in standby mode when it receives a one-shot command.
If the RUN/STOP bit is clear (low) then the thermal sensor enters auto-conversion
mode. The thermal sensing device starts operating in free running mode, autoconverting at 0.25 Hz after power-up.
7 (MSB)RESERVED0Reserved for future use.
6RUN/STOP0Standby mode control bit. If high, the device immediately stops
5–0RESERVED0Reserved for future use.
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet89
Reset
State
Function
converting, and enters standby mode. If low, the device converts in
either one-shot or timer mode.
System Management Feature Specifications
6.7.5Conversion Rate Register
The contents of the conversion rate register determine the nominal rate at which
analog-to-digital conversions happen when the thermal sensing device is in autoconvert mode. Table 6-16 shows the mapping between conversion rate register values
and the conversion rate. As indicated in Table 6-16, the conversion rate register is set
to its default state of 02h (0.25 Hz nominally) when the thermal sensing device is
powered-up. There is a ±25% error tolerance between the conversion rate indicated in
the conversion rate register and the actual conversion rate.
90Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Signals Reference
ASignals Reference
This appendix provides an alphabetical listing of all Dual-Core Intel Itanium 9000 and
9100 series processor system bus signals. The tables at the end of this appendix
summarize the signals by direction: output, input, and I/O.
For a complete pinout listing including processor specific pins, please refer to
Chapter 3, “Pinout Specifications.”
A.1Alphabetical Signals Reference
A.1.1A[49:3]# (I/O)
The Address (A[49:3]#) signals, with byte enables, define a 250Byte physical memory
address space. When ADS# is active, these pins transmit the address of a transaction.
These pins are also used to transmit other transaction related information such as
transaction identifiers and external functions in the cycle following ADS# assertion.
These signals must connect the appropriate pins of all agents on the processor system
bus. The A[49:27]# signals are parity-protected by the AP1# parity signal, and the
A[26:3]# signals are parity-protected by the AP0# parity signal.
On the active-to-inactive transition of RESET#, the processors sample the A[49:3]#
pins to determine their power-on configuration.
A.1.2A20M# (I)
A20M# is no connect and is ignored in the processor system environment.
A.1.3ADS# (I/O)
The Address Strobe (ADS#) signal is asserted to indicate the validity of the transaction
address on the A[49:3]#, REQ[5:0]#, AP[1:0]# and RP#pins. All bus agents observe
the ADS# activation to begin parity checking, protocol checking, address decode,
internal snoop, or deferred reply ID match operations associated with the new
transaction.
A.1.4AP[1:0]# (I/O)
The Address Parity (AP[1:0]#) signals can be driven by the request initiator along with
ADS# and A[49:3]#. AP[1]# covers A[49:27]#, and AP[0]# covers A[26:3]#. A
correct parity signal is high if an even number of covered signals are low and low if an
odd number of covered signals are low. This allows parity to be high when all the
covered signals are high.
A.1.5ASZ[1:0]# (I/O)
The ASZ[1:0]# signals are the memory address-space size signals. They are driven by
the request initiator during the first Request Phase clock on the REQa[4:3]# pins. The
ASZ[1:0]# signals are valid only when REQa[2:1]# signals equal 01B, 10B, or 11B,
indicating a memory access transaction. The ASZ[1:0]# decode is defined in Table A-1.
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet91
Table A-1. Address Space Size
Signals Reference
ASZ[1:0]#
00ReservedReserved
0136-bit0 to (64 GByte - 1)
1050-bit64 GByte to
11ReservedReserved
Memory Address
Space
Any memory access transaction addressing a memory region that is less than 64 GB
(that is, Aa[49:36]# are all zeroes) must set ASZ[1:0]# to 01. Any memory access
transaction addressing a memory region that is equal to or greater than 64 GB (that is,
Aa[49:36]# are not all zeroes) must set ASZ[1:0]# to 10. All observing bus agents
that support the 64 GByte (36-bit) address space must respond to the transaction
when ASZ[1:0]# equals 01. All observing bus agents that support larger than the 64
GByte (36-bit) address space must respond to the transaction when ASZ[1:0]# equals
01 or 10.
A.1.6ATTR[3:0]# (I/O)
The ATTR[3:0]# signals are the attribute signals. They are driven by the request
initiator during the second clock of the Request Phase on the Ab[35:32]# pins. The
ATTR[3:0]# signals are valid for all transactions. The ATTR[3]# signal is reserved. The
ATTR[2:0]# are driven based on the memory type. Please refer to Table A-2.
The BCLKp and BCLKn differential clock signals determine the bus frequency. All agents
drive their outputs and latch their inputs on the differential crossing of BCLKp and
BCLKn on the signals that are using the common clock latched protocol.
BCLKp and BCLKn indirectly determine the internal clock frequency of the processor.
Each processor derives its internal clock by multiplying the BCLKp and BCLKn
frequency by a ratio that is defined and allowed by the power-on configuration.
A.1.8BE[7:0]# (I/O)
The BE[7:0]# signals are the byte-enable signals for partial transactions. They are
driven by the request initiator during the second Request Phase clock on the Ab[15:8]#
pins.
92Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Signals Reference
For memory or I/O transactions, the byte-enable signals indicate that valid data is
requested or being transferred on the corresponding byte on the 128-bit data bus.
BE[0]# indicates that the least significant byte is valid, and BE[7]# indicates that the
most significant byte is valid. Since BE[7:0]# specifies the validity of only 8 bytes on
the 16 byte wide bus, A[3]# is used to determine which half of the data bus is validated
by BE[7:0]#.
For special transactions ((REQa[5:0]# = 001000B) and (REQb[1:0]# = 01B)), the
BE[7:0]# signals carry special cycle encodings as defined in Table A-3. All other
encodings are reserved.
Table A-3. Special Transaction Encoding on Byte Enables
For Deferred Reply transactions, BE[7:0]# signals are reserved. The Defer Phase
transfer length is always the same length as that specified in the Request Phase except
the Bus Invalidate Line (BIL) transaction.
A BIL transaction may return one cache line (128 bytes).
A.1.9BERR# (I/O)
The Bus Error (BERR#) signal can be asserted to indicate a recoverable error with
global MCA. BERR# assertion conditions are configurable at the system level.
Configuration options enable BERR# to be driven as follows:
• Asserted by the requesting agent of a bus transaction after it observes an internal
error.
• Asserted by any bus agent when it observes an error in a bus transaction.
When the bus agent samples an asserted BERR# signal and BERR# sampling is
enabled, the processor enters a Machine Check Handler.
BERR# is a wired-OR signal to allow multiple bus agents to drive it at the same time.
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet93
A.1.10BINIT# (I/O)
If enabled by configuration, the Bus Initialization (BINIT#) signal is asserted to signal
any bus condition that prevents reliable future operation.
If BINIT# observation is enabled during power-on configuration, and BINIT# is
sampled asserted, all bus state machines are reset. All agents reset their rotating IDs
for bus arbitration to the same state as that after reset, and internal count information
is lost. The L2 and L3 caches are not affected.
If BINIT# observation is disabled during power-on configuration, BINIT# is ignored by
all bus agents with the exception of the priority agent. The priority agent must handle
the error in a manner that is appropriate to the system architecture.
BINIT# is a wired-OR signal.
A.1.11BNR# (I/O)
The Block Next Request (BNR#) signal is used to assert a bus stall by any bus agent
that is unable to accept new bus transactions to avoid an internal transaction queue
overflow. During a bus stall, the current bus owner cannot issue any new transactions.
Since multiple agents might need to request a bus stall at the same time, BNR# is a
wired-OR signal. In order to avoid wired-OR glitches associated with simultaneous edge
transitions driven by multiple drivers, BNR# is asserted and sampled on specific clock
edges.
Signals Reference
A.1.12BPM[5:0]# (I/O)
The BPM[5:0]# signals are system support signals used for inserting breakpoints and
for performance monitoring. They can be configured as outputs from the processor that
indicate programmable counters used for monitoring performance, or inputs from the
processor to indicate the status of breakpoints.
A.1.13BPRI# (I)
The Bus Priority-agent Request (BPRI#) signal is used by the priority agent to arbitrate
for ownership of the system bus. Observing BPRI# asserted causes all other agents to
stop issuing new requests, unless such requests are part of an ongoing locked
operation.The priority agent keeps BPRI# asserted until all of its requests are
completed, then releases the bus by deasserting BPRI#.
A.1.14BR[0]# (I/O) and BR[3:1]# (I)
BR[3:0]# are the physical bus request pins that drive the BREQ[3:0]# signals in the
system. The BREQ[3:0]# signals are interconnected in a rotating manner to individual
processor pins. Table A-4 and Table A-4 give the rotating interconnection between the
processor and bus signals for both the 4P and 2P system bus topologies.
94Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
BREQ[0]#BR[0]#BR[1]#
BREQ[1]#BR[1]#BR[0]#
BREQ[2]#Not UsedNot Used
BREQ[3]#Not UsedNot Used
During power-on configuration, the priority agent must assert the BR[0]# bus signal.
All symmetric agents sample their BR[3:0]# pins on asserted-to-deasserted transition
of RESET#. The pin on which the agent samples an asserted level determines its agent
ID. All agents then configure their pins to match the appropriate bus signal protocol as
shown in Table A-6.
Table A-6. BR[3:0]# Signals and Agent IDs
Pin Sampled
Asserted on
RESET#
BR[0]#00
BR[3]#12
BR[2]#24
BR[1]#36
Arbitration ID
A.1.15BREQ[3:0]# (I/O)
The BREQ[3:0]# signals are the symmetric agent arbitration bus signals (called bus
request). A symmetric agent n arbitrates for the bus by asserting its BREQn# signal.
Agent n drives BREQn# as an output and receives the remaining BREQ[3:0]# signals
as inputs.
The symmetric agents support distributed arbitration based on a round-robin
mechanism. The rotating ID is an internal state used by all symmetric agents to track
the agent with the lowest priority at the next arbitration event. At power-on, the
rotating ID is initialized to three, allowing agent 0 to be the highest priority symmetric
agent. After a new arbitration event, the rotating ID of all symmetric agents is updated
to the agent ID of the symmetric owner. This update gives the new symmetric owner
lowest priority in the next arbitration event.
A new arbitration event occurs either when a symmetric agent asserts its BREQn# on
an Idle bus (all BREQ[3:0]# previously deasserted), or the current symmetric owner
deasserts BREQn# to release the bus ownership to a new bus owner n. On a new
arbitration event, all symmetric agents simultaneously determine the new symmetric
owner using BREQ[3:0]# and the rotating ID. The symmetric owner can park on the
bus (hold the bus) provided that no other symmetric agent is requesting its use. The
symmetric owner parks by keeping its BREQn# signal asserted. On sampling BREQn#
asserted by another symmetric agent, the symmetric owner deasserts BREQn# as soon
as possible to release the bus. A symmetric owner stops issuing new requests that are
not part of an existing locked operation on observing BPRI# asserted.
Agent ID
Reported
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet95
A symmetric agent can deassert BREQn# before it becomes a symmetric owner. A
symmetric agent can reassert BREQn# after keeping it deasserted for one clock.
A.1.16CCL# (I/O)
CCL# is the Cache Cleanse signal. It is driven on the second clock of the Request Phase
on the EXF[2]#/Ab[5]# pin. CCL# is asserted for Memory Write transaction to indicate
that a modified line in a processor may be written to memory without being invalidated
in its caches.
A.1.17CPUPRES# (O)
CPUPRES# can be used to detect the presence of a processor in a socket. A ground
indicates that a processor is installed, while an open indicates that a processor is not
installed.
A.1.18D[127:0]# (I/O)
The Data (D[127:0]#) signals provide a 128-bit data path between various system bus
agents. Partial transfers require one data transfer clock with valid data on the byte(s)
indicated by asserted byte enables BE[7:0]# and A[3]#. Data signals that are not valid
for a particular transfer must still have correct ECC (if data bus error checking is
enabled). The data driver asserts DRDY# to indicate a valid data transfer.
Signals Reference
A.1.19D/C# (I/O)
The Data/Code (D/C#) signal is used to indicate data (1) or code (0) on REQa[1]#,
only during Memory Read transactions.
A.1.20DBSY# (I/O)
The Data Bus Busy (DBSY#) signal is asserted by the agent that is responsible for
driving data on the system bus to indicate that the data bus is in use. The data bus is
released after DBSY# is deasserted.
DBSY# is replicated three times to enable partitioning of the data paths in the system
agents. This copy of the Data Bus Busy signal (DBSY#) is an input as well as an output.
A.1.21DBSY_C1# (O)
DBSY# is a copy of the Data Bus Busy signal. This copy of the Data Bus Busy signal
(DBSY_C1#) is an output only.
A.1.22DBSY_C2# (O)
DBSY# is a copy of the Data Bus Busy signal. This copy of the Data Bus Busy signal
(DBSY_C2#) is an output only.
A.1.23DEFER# (I)
The DEFER# signal is asserted by an agent to indicate that the transaction cannot be
guaranteed in-order completion. Assertion of DEFER# is normally the responsibility of
the priority agent.
96Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Signals Reference
A.1.24DEN# (I/O)
The Defer Enable (DEN#) signal is driven on the bus on the second clock of the Request
Phase on the Ab[4]# pin. DEN# is asserted to indicate that the transaction can be
deferred by the responding agent.
A.1.25DEP[15:0]# (I/O)
The Data Bus ECC Protection (DEP[15:0]#) signals provide optional ECC protection for
Data Bus (D[127:0]#). They are driven by the agent responsible for driving
D[127:0]#. During power-on configuration, bus agents can be enabled for either ECC
checking or no checking.
The ECC error correcting code can detect and correct single-bit errors and detect
double-bit or nibble errors.
A.1.26DHIT# (I)
The Deferred Hit (DHIT#) signal is driven during the Deferred Phase by the deferring
agent. For read transactions on the bus DHIT# returns the final cache status that would
have been indicated on HIT# for a transaction which was not deferred. DID[9:0]# (I/
O)
DID[9:0]# are Deferred Identifier signals. The requesting agent transfers these signals
by using A[25:16]#. They are transferred on Ab[25:16]# during the second clock of
the Request Phase on all transactions, but Ab[20:16]# is only defined for deferrable
transactions (DEN# asserted). DID[9:0]# is also transferred on Aa[25:16]# during the
first clock of the Request Phase for Deferred Reply transactions.
The Deferred Identifier defines the token supplied by the requesting agent. DID[9]#
and DID[8:5]# carry the agent identifiers of the requesting agents (always valid) and
DID[4:0]# carry a transaction identifier associated with the request (valid only with
DEN# asserted). This configuration limits the bus specification to 32 logical bus agents
with each one of the bus agents capable of making up to 32 requests. Table A-7 shows
the DID encodings.
Table A-7. DID[9:0]# Encoding
DID[9]#DID[8:5]#DID[4:0]#
Agent TypeAgent ID[3:0]Transaction ID[4:0]
DID[9]# indicates the agent type. Symmetric agents use 0. Priority agents use 1.
DID[8:5]# indicates the agent ID. Symmetric agents use their arbitration ID.
DID[4:0]# indicates the transaction ID for an agent. The transaction ID must be
unique for all deferrable transactions issued by an agent which have not reported their
snoop results.
The Deferred Reply agent transmits the DID[9:0]# (Ab[25:16]#) signals received
during the original transaction on the Aa[25:16]# signals during the Deferred Reply
transaction. This process enables the original requesting agent to make an identifier
match with the original request that is awaiting completion.
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet97
A.1.27DPS# (I/O)
The Deferred Phase Enable (DPS#) signal is driven to the bus on the second clock of
the Request Phase on the Ab[3]# pin. DPS# is asserted if a requesting agent supports
transaction completion using the Deferred Phase. A requesting agent that supports the
Deferred Phase will always assert DPS#. A requesting agent that does not support the
Deferred Phase will always deassert DPS#.
A.1.28DRDY# (I/O)
The Data Ready (DRDY#) signal is asserted by the data driver on each data transfer,
indicating valid data on the data bus. In a multi-cycle data transfer, DRDY# can be
deasserted to insert idle clocks.
DRDY# is replicated three times to enable partitioning of data paths in the system
agents. This copy of the Data Ready signal (DRDY#) is an input as well as an output.
A.1.29DRDY_C1# (O)
DRDY# is a copy of the Data Ready signal. This copy of the Data Phase data-ready
signal (DRDY_C1#) is an output only.
Signals Reference
A.1.30DRDY_C2# (O)
DRDY# is a copy of the Data Ready signal. This copy of the Data Phase data-ready
signal (DRDY_C2#) is an output only.
A.1.31DSZ[1:0]# (I/O)
The Data Size (DSZ[1:0]#) signals are transferred on REQb[4:3]# signals in the
second clock of the Request Phase by the requesting agent. The DSZ[1:0]# signals
define the data transfer capability of the requesting agent. For the processor, DSZ# =
01, always.
A.1.32EXF[4:0]# (I/O)
The Extended Function (EXF[4:0]#) signals are transferred on the A[7:3]# pins by the
requesting agent during the second clock of the Request Phase. The signals specify any
special functional requirement associated with the transaction based on the requestor
mode or capability. The signals are defined in Table A-8.
Table A-8. Extended Function Signals
Extended Function
Signal
EXF[4]#ReservedReserved
EXF[3]#SPLCK#/FCL#Split Lock / Flush Cache Line
EXF[2]#OWN#/CCL#Memory Update Not Needed / Cache Cleanse
EXF[1]#DEN#Defer Enable
EXF[0]#DPS#Deferred Phase Supported
Signal Name AliasFunction
98Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Signals Reference
A.1.33FCL# (I/O)
The Flush Cache Line (FCL#) signal is driven to the bus on the second clock of the
Request Phase on the A[6]# pin. FCL# is asserted to indicate that the memory
transaction is initiated by the global Flush Cache () instruction.
A.1.34FERR# (O)
The FERR# signal may be asserted to indicate a processor detected error when IERR
mode is enabled. If IERR mode is disabled, the FERR# signal will not be asserted in the
processor system environment.
A.1.35GSEQ# (I)
Assertion of the Guaranteed Sequentiality (GSEQ#) signal indicates that the platform
guarantees completion of the transaction without a retry while maintaining
sequentiality.
A.1.36HIT# (I/O) and HITM# (I/O)
The Snoop Hit (HIT#) and Hit Modified (HITM#) signals convey transaction snoop
operation results. Any bus agent can assert both HIT# and HITM# together to indicate
that it requires a snoop stall. The stall can be continued by reasserting HIT# and
HITM# together.
A.1.37ID[9:0]# (I)
The Transaction ID (ID[9:0]#) signals are driven by the deferring agent. The signals in
the two clocks are referenced IDa[9:0]# and IDb[9:0]#. During both clocks, ID[9:0]#
signals are protected by the IP0# parity signal for the first clock, and by the IP[1]#
parity signal on the second clock.
IDa[9:0]# returns the ID of the deferred transaction which was sent on Ab[25:16]#
(DID[9:0]#).
A.1.38IDS# (I)
The ID Strobe (IDS#) signal is asserted to indicate the validity of ID[9:0]# in that clock
and the validity of DHIT# and IP[1:0]# in the next clock.
A.1.39IGNNE# (I)
IGNNE# is no connect and is ignored in the processor system environment.
A.1.40INIT# (I)
The Initialization (INIT#) signal triggers an unmasked interrupt to the processor. INIT#
is usually used to break into hanging or idle processor states. Semantics required for
platform compatibility are supplied in the PAL firmware interrupt service routine.
Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet99
A.1.41INT (I)
INT is the 8259-compatible Interrupt Request signal which indicates that an external
interrupt has been generated. The interrupt is maskable. The processor vectors to the
interrupt handler after the current instruction execution has been completed. An
interrupt acknowledge transaction is generated by the processor to obtain the interrupt
vector from the interrupt controller.
The LINT[0] pin can be software configured to be used either as the INT signal or
another local interrupt.
A.1.42IP[1:0]# (I)
The ID Parity (IP[1:0]#) signals are driven on the second clock of the Deferred Phase
by the deferring agent. IP0# protects the IDa[9:0]# and IDS# signals for the first
clock, and IP[1]# protects the IDb[9:2, 0]# and IDS# signals on the second clock.
A.1.43LEN[2:0]# (I/O)
The Data Length (LEN[2:0]#) signals are transmitted using REQb[2:0]# signals by the
requesting agent in the second clock of Request Phase. LEN[2:0]# defines the length of
the data transfer requested by the requesting agent as shown in Table A-9. The
LEN[2:0]#, HITM#, and RS[2:0]# signals together define the length of the actual data
transfer.
LINT[1:0] are local interrupt signals. These pins are disabled after RESET#. LINT[0] is
typically software configured as INT, an 8259-compatible maskable interrupt request
signal. LINT[1] is typically software configured as NMI, a non-maskable interrupt.Both
signals are asynchronous inputs.
A.1.45LOCK# (I/O)
LOCK# is no connect and is ignored in the processor system environment.
100Dual-Core Intel® Itanium® Processor 9000 and 9100 Series Datasheet
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.