Intel® Xeon™ Processor and
Intel® E7500/E7501 Chipset
Compatible Platform
Design Guide Addendum for Embedded Applications
July 2003
Order Number: 273707-004
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 ASSUM ES NO LIABILIT Y WHA T SOEVER, AND INTE L DISCLAIMS
ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES
RELATING T O 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 the m.
®
The Intel
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 ordering number and are referenced in this document, or other Intel literature may be obtained by calling
1-800-548-4725 or by visiting Intel's website at http://www.intel.com.
AlertVIEW, AnyPoint, AppChoice, BoardWatch, BunnyPeople, CablePort, Celeron, Chips, CT Connect, CT Media, Dialogic, DM3, EtherExpress,
ETOX, FlashFile, i386, i486, i960, iCOMP, InstantIP, Intel, Intel logo, Intel386, Intel486, Intel740, IntelDX2, IntelDX4, IntelSX2, Intel Create & Share,
Intel GigaBlade, Intel InBusiness, Intel Inside, Intel Inside logo, Intel NetBurst, Intel NetMerge, Intel NetStructure, Intel Play, Intel Play logo, Intel
SingleDriver, Intel SpeedStep, Intel StrataFlash, Intel TeamStation, Intel Xeon, Intel XScale, IPLink, Itanium, LANDesk, LanRover, MCS, MM X, MMX
logo, Optimizer logo, OverDrive, Paragon, PC Dads, PC Parents, PDCharm, Pentium, Pentium II Xeon, Pentium III Xeon, Performance at Your
Command, RemoteExpress, Shiva, SmartDie, Solutions960, Sound Mark, StorageExpress, The Computer Inside., The Journey Inside,
TokenExpress, Trillium, VoiceBrick, Vtune, and Xircom are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United
States and other countri es.
Intel® Xeon™ Processor and Intel® E7500/E7501 Chipset Compatible Platform
1.0Introduction
This document is an addendum to the Intel® Xeon™ Processor and Intel® E7500/E7501 Chipset
Compatible Platform Design Guide. It contains applied computing-specific guidelines, such as uni-
processor design guidelines, angl ed Double Data Rate (DDR) guidelines and single channel DDR
guidelines.
Carefully follow the design information and recommendations provided in this document. These
design guidelines have been developed to ensure maximum flexibility for system designers while
reducing the risk of board-related issues.
Note that the guidelines recommended in this document are based on experience and preliminary
simulation work done at Intel.
1.1Reference Documentati on
T a ble 1. Reference Documents (Sheet 1 of 2)
DocumentLocation
®
Intel
E7501 Chipset Memory Controller Hub (MCH)
Datasheet
Intel® Xeon™ Processor and Intel® E7500/E7501
Chipset Compatible Platform Design Guide
Intel® Xeon™ Processor with 512 KB L2 Cache and
Intel E7500 Chipset Platform Design Guide
Intel® Xeon™ Processor with 512 KB L2 Cache at
Intel® Xeon™ Processor and Intel® E7500/E7501 Chipset Compatible Platform
2.0Uni-processor System Bus Routing Guidelines
This section covers the system bus source synchronous (data, address, and associated strobes) and
common clock signal routing for Intel
FSB)/Low Voltage Intel
®
Xeon™ processor (400 MHz FSB) and Intel® E7500/E7501 chipsetbased systems, in a uni-processor (UP) configuration. Table 2 lists the signals and their
corresponding signal types .
Figure 1 describes the uni-processor system bus topology.
T a ble 2. System Bus Signal Groups
Signal GroupTypeSignals
AGTL+ Common Clock InputSynchronous to BCLK
AGTL+ Common Clock I/OSynchronous to BCLK
AGTL+ Source Synchronous I/O:
4X Group
AGTL+ Source Synchronous I/O:
2X Group
AGTL+ Strobes
Async GTL+ Input
Async GTL+ Output
System Bus ClockClockBCLK0, BCLK1
TAP Input
TAP Output
SMBus Interface
Power/OtherPower/Other
NOTES:
1. These signals do not have on-die termination on the processor. They must be terminated properly on the
system board. If the signal is not connected, it must be pulled to the appropriate voltage level t hrough a 1
kΩ ± 5% resistor.
2. Xeon processors use only BR0# and BR1#.
3. These signals are ‘wired-OR’ signals and may be driven simultaneously by multiple agents. For further
details on how to implement wired-OR signals, refer to the routing guidelines in Section 2.2.1.
4. The value of these pins driving the active edge of RESET# determine processor configuration options.
5. SM_V
6. Terminations and routing for TAP signals and all debug port signals are found in the ITP700 Debug Port Design Guide.
7. PROCHOT # is input/output on Low Voltage Intel® Xeon™ processor D-stepping and beyond.
Intel® Xeon™ Processor and Intel® E7500/E7501 Chipset Compatible Platform
Figure 1. Uni-processor System Bus Topology
Note:
Package trace
Motherboard PCB trace
ProcessorMCH
Pad
Length L1 = 3.5 - 10"
Refer to Table 3 for a summary of the uni-processor system bus routing recommendations. Use this
as a quick reference only. The following sections provide more information for each parameter.
Intel strongly recommends simulation of all signals to ensure that setup and hold times are met.
T a ble 3. Uni-processor System Bus Routing Summary
ParameterPlatform Routing Guidelines
Trace width/spacing5/15 mils
3.5“– 10“pin-to-pin
4X signal group line lengths
DSTBn/p[3:0]# line lengths
2X signal group line lengthsAddress signals should follow the same routing rules as the data signals.
ADSTB[1:0]# line lengthsADSTB# signals should follow the same routing rules as the DSTB# signals.
Common clock signal line
lengths
Topology The processor must have on-die termination enabled.
Routing priorities
Reference plane requirements
System board Impedance50 Ω ± 10%
Length must be added to the system board trace between agents to
compensate for the stub created by the processor package
DSTB# signals should follow the same routing rules as the data signals
A 25 mil spacing should be maintained around each strobe signal (between
DSTBp# and DSTBn#, and any other signal.)
Common clock signals should follow the same routing rules as the data
signals, however no length compensation is necessary.
All signals within the same strobe group must be routed on same layer for the
entire length of the bus.
Ground reference only.
Avoid changing layers when routing system bus signals.
If a layer change must occur, use vias connecting the two reference planes to
provide a low impedance path for the return current. Vias should be as close
as possible to the signal via.
Pad
A9044-01
10Platform Design Guide Addendum
Intel® Xeon™ Processor and Intel® E7500/E7501 Chipset Compatible Platform
2.1Routing Guidelines fo r the 2X and 4X Signal Groups
The 4X group of signals uses four times the frequency of the base clock, or 400 MHz. The 2X
group uses twice the frequency of t h e bas e cloc k, o r 20 0 MHz. The 2 X and 4 X si gn als are l i st ed i n
Table 4. Table 5 lists the 2X and 4X signals with their associated strobes.
Table 4. 2X and 4X Signal Groups
2X Group4X Group
HA[35:3]#
REQ[4:0]#
Table 5. Source Synchronous Signals and Associated Strobes
Routing guidelines for the 2X and 4X signal groups are given below:
• Trace impedance = 50 Ω ± 10%
• Route traces using 5/15 mil spacing
• Route all traces at least 25 mils away from the strobes
• Route all traces with at least 50% of the trace width directly over the reference plane for short
distances only when needed in the interposer socket region.
• Route signals and their associated strobes on the same layer for the entire length of the bus.
• A strobe and its complement must be routed within 25 mils of the same length over the entire
length of the buses.
• All 2X and 4X signals of the same group (refer to Table 5) m ust be routed within ±25 mils of
the same length between the agents and within ±50 mils of the entire length of the bus.
• Total bus length must not exceed 10”.
• Trace length matching is required. Please contact your Intel field representative for a length
matching spreadsheet.
Trace length matching is required within each source synchronous group to compensate for the
package trace length differences between data signals and the associated strobe. This will balance
the strobe- t o-signal skew in the middle of the setup and hold window. Figure 1 shows how t o
implement trace length matching. An example of trace length matching is given in Equation 1.
Platform Design Guide Addendum11
Intel® Xeon™ Processor and Intel® E7500/E7501 Chipset Compatible Platform
2.1.1Design Recommendations
Below are the design recommendations for the data, address, strobes, and common clock signals.
For the following discussion, the pad is defined as the attach point of the silicon pad to the package
substrate.
DATA:
• The pin to pin distance from the processor to the chipset should be between 3.5" to 10" (i.e.,
3.5" < L1 < 10"). Data signals of the same source synchronous group should be routed to the
same pad to pad length within ± 100 mils of the associated strobes. As a result, additional
traces will be added to some data nets on the system board in order for all trace lengths within
the same data group to be the same length (± 100 mils) from the pad of the processor to the pad
of the chipset. This length compensation will result in minimizing the source sync hro nou s
skew that exists on the system bus. Without the length compensation the flight times between
a data signal and its strobe is different, which results in an inequity between the s etup and ho ld
times.
Equation 1. Calculating Package Delta Addition to System Board Length for UP Systems
delta
net,strobe
ADDRESS:
= (cpu_pkglen
† Strobe package length is the average of the strobe pair.
- cpu_pkglen
net
) + (chipset_pkglen
strobe†
- chipset_pkglen
net
strobe
• Address signals follow the same rules as data signals except they should be routed to the same
pad to pad length within ±200 mils of the associated strobes. Address signals may change
layers if the reference plane remains Vss and as long as the layers for a given group are all of
the same configuration (all stripline or all microstrip).
STROBE:
• A strobe and its complement should be routed to a length equal to their corresponding data
group's median pad-to-pad length ±25 mils. This causes the strobe to be received closer to the
center of the data pulse, which results in reasonably comparable setup and hold times. A strobe
and its complement (xSTBp/n#) should be routed to ±25 mils of the same length. It is
recommended to simulate skew in order to determine the length that best centers the strobe for
a given system.
COMMON CL OCK:
• Common clock signals should be routed to a minimum pin-to-pin system board length of 6"
and a maximum motherboard length of 10".
)
12Platform Design Guide Addendum
Intel® Xeon™ Processor and Intel® E7500/E7501 Chipset Compatible Platform
Routing guidelines for the source synchronous signal group are given below:
• Trace impedance = 50 Ω ±10%
• Route traces using 5/15 mil spacing
• Keep signals on the same layer for the entire length of the bus
• Route traces with at least 50% of the trace width directly over a reference plane
• Total bus length must not exceed 10"
2.2.1Wired-OR Signals
There are five wired-OR signals on the system bus. These signals are HIT#, HITM#, MCERR#,
BINIT#, and BNR#. These signals differ from the other fr ont-side bus signals in that more than one
agent can be driving the signal at the same time. Timing and signal integrity must be met for the
case where one agent is driving, all agents are driving, or any combination of agents are driving.
The wired-OR signals should follow the same routing rules as the common clock signals. Intel
recommends that simulations for these signals be performed for a given system.
Platform Design Guide Addendum13
Intel® Xeon™ Processor and Intel® E7500/E7501 Chipset Compatible Platform
2.3Routing Guidelines for Asynchronous GTL+ and
Miscellaneous Signals
This section provides routing guidelines for the sign als listed in Table 7.
Table 7. Asynchronous GTL+ and Miscellaneous Signals