Intel III 866 MHz 80526PZ866256 User Manual
Product codes
80526PZ866256
50
Datasheet
Pentium
®
III Processor for the PGA370 Socket at 500 MHz to 1.13 GHz
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 (note that if AF = 1, then the
event occurs at all times and no other events can occur).
NO other overshoot/undershoot events, even of lesser magnitude (note that if AF = 1, then the
event occurs at all times and no other events can occur).
Note:
Activity factor for AGTL+ signals is referenced to BCLK frequency.
Note:
Activity factor for CMOS signals is referenced to PICCLK frequency.
3.3.5
Reading Overshoot/Undershoot Specification Tables
The overshoot/undershoot specification for the Pentium
III
processor for the PGA370 socket is not
a simple single value. Instead, many factors are needed to determine what the over/undershoot
specification is. In addition to the magnitude of the overshoot, the following parameters must also
be known: the junction temperature the processor will be operating at, the width of the overshoot
(as measured above 1.635 V) and the Activity Factor (AF). To determine the allowed overshoot for
a particular overshoot event, the following must be done:
specification is. In addition to the magnitude of the overshoot, the following parameters must also
be known: the junction temperature the processor will be operating at, the width of the overshoot
(as measured above 1.635 V) and the Activity Factor (AF). To determine the allowed overshoot for
a particular overshoot event, the following must be done:
1. Determine the signal group that particular signal falls into. If the signal is an AGTL+ signal
operating with a 100 MHz system bus, use
Table 25
(100MHz AGTL+ signal group). If the
signal is an AGTL+ signal operating with a 133MHz system bus, use
Table 26
(133 MHz
AGTL+ signal group). If the signal is a CMOS signal, use
Table 27
(33 MHz CMOS signal
group).
2. Determine the maximum junction temperature (Tj) for the range of processors that the system
will support (80
o
C or 85
o
C).
3. Determine the Magnitude of the overshoot (relative to V
SS
)
4. Determine the Activity Factor (how often does this overshoot occur?)
5. From the appropriate Specification table, read off the Maximum Pulse Duration (in ns)
allowed.
6. 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.
specifications.
The above procedure is similar for undershoots after the undershoot waveform has been converted
to look like an overshoot. Undershoot events must be analyzed separately from Overshoot events
as they are mutually exclusive.
to look like an overshoot. Undershoot events must be analyzed separately from Overshoot events
as they are mutually exclusive.
Below is an example showing how the maximum pulse duration is determined for a given
waveform.
waveform.
NOTES:
1. Corresponding Maximum Pulse Duration Specification - 2.4 ns
2. Pulse Duration (measured) - 2.0 ns
2. Pulse Duration (measured) - 2.0 ns
Given the above parameters, and using
Table 26
(85
o
C/AF = 0.1 column) the maximum allowed
pulse duration is 2.4 ns. Since the measure pulse duration is 2.0 ns, this particular overshoot event
passes the overshoot specifications, although this doesn't guarantee that the combined overshoot/
undershoot events meet the specifications.
passes the overshoot specifications, although this doesn't guarantee that the combined overshoot/
undershoot events meet the specifications.
Table 24. Example Platform Information
Required Information
Maximum Platform Support
Notes
FSB Signal Group
133 MHz AGTL+
Max Tj
85 °C
Overshoot Magnitude
2.13V
Measured Value
Activity Factor (AF)
0.1
Measured overshoot occurs on
average every 20 clocks
average every 20 clocks