![](http://datasheet.mmic.net.cn/300000/RK80530KZ006512_datasheet_16205385/RK80530KZ006512_46.png)
46
Datasheet
Intel
Pentium
III Processor with 512KB L2 Cache at 1.13GHz to 1.40GHz
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 (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 system bus clock 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 Intel
Pentium
III
processor with 512KB L2
cache 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 case temperature the processor will be operating at, the width of the
overshoot (as measured above 1.78 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 133 MHz system bus, use
Table 26
(133 MHz AGTL signal group). If the
signal is a CMOS signal, use
Table 28
(33 MHz CMOS signal group).
2. Determine the maximum case temperature (Tcase) for the range of processors that the system
will support.
3. Determine the Magnitude of the overshoot (relative to V
SS
)
4. Determine the Activity Factor (how often this overshoot occurs)
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.
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.
Below is an example showing how the maximum pulse duration is determined for a given
waveform.
Given the above parameters, and using
Table 26
(69
o
C/AF = 0.1 column) the maximum allowed
pulse duration is 7.5 ns. Since the measure pulse duration is 7.5 ns, this particular overshoot event
passes the overshoot specifications, although this doesn't guarantee that the combined overshoot/
undershoot events meet the specifications.
Table 25. Example Platform Information
Required Information
Maximum Platform Support
Notes
FSB Signal Group
133 MHz AGTL
Max Tcase
69 °C
Overshoot Magnitude
1.78 V
Measured Value
Activity Factor (AF)
0.1
Measured overshoot occurs on
average every 20 clocks