Datasheet
53
System Bus Signal Quality Specifications
NOTES:
1. Activity factor for common clock AGTL+ signals is referenced to BCLK[1:0] frequency.
2. Activity factor for source synchronous (2x) signals is referenced to ADSTB[1:0]#.
3. Activity factor for source synchronous (4x) signals is referenced to DSTBP[3:0]#and DSTBN[3:0]#.
3.3.5
Reading Overshoot/Undershoot Specification Tables
The overshoot/undershoot specification for the Intel Xeon processor MP on the 0.13 micron
process processor is not a simple single value. Instead, many factors are needed to determine the
over/undershoot specification. In addition to the magnitude of the overshoot, the following
parameters must be considered: the width of the overshoot 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. For AGTL+ signals operating in
the 4X source synchronous domain, use
Table 25. For AGTL+ signals operating in the 2X
source synchronous domain, use
Table 26. If the signal is an AGTL+ signal operating in the
common clock domain, use
Table 27. Finally, all other signals reside in the 33 MHz domain
(asynchronous GTL+, TAP, etc.) and are referenced in
Table 28.
2. Determine the magnitude of the overshoot or the undershoot (relative to VSS).
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.
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.
Undershoot events must be analyzed separately from overshoot events as they are mutually
exclusive.
3.3.6
Determining if a System Meets the Overshoot/Undershoot
Specifications
The overshoot/undershoot specifications listed in the following tables specify the allowable
overshoot/undershoot for a single overshoot/undershoot event. However most systems will have
multiple overshoot and/or undershoot events for a given transition, with each having their own set
of parameters (duration, AF and magnitude). While each overshoot on its own may meet the
overshoot specification, when you add the total impact of all overshoot events, the system may fail
(see
Figure 25). A guideline to ensure a system passes the overshoot and undershoot specifications
is shown below.
1. Ensure no signal ever exceeds VCC or -0.25V or
2. If only one overshoot/undershoot event magnitude occurs, ensure it meets the over/undershoot
specifications in the following tables or
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.