10vrstvá pravidla směrování desek plošných spojů pro DDR5, PCIe a Crosstalk

Routing rules for a ten-layer PCB should be derived from the stackup, device design guides and channel analysis. They should not be copied from a generic table of mil values. Equal physical length does not always mean equal electrical delay, a “5W rule” is not a crosstalk guarantee, and a protocol generation does not automatically dictate a laminate or a fixed residual via stub.

The purpose of this guide is to turn electrical requirements into layout constraints that remain valid through fabrication. It focuses on return paths, coupled routing, memory timing, serial-link transitions, crosstalk and the handoff to DFM. Final widths and gaps come from the released impedance model.

Freeze the Electrical Rules Before Routing Begins

Routing should not begin with provisional dielectric thicknesses and finish with a request that the fabricator “adjust the stackup to fit.” Changing the stackup changes width, pair spacing, propagation delay, reference assignment and sometimes layer capacity. The baseline package should identify the stackup revision, material construction, copper, controlled structures, device-specific timing rules and the electrical models used for the critical channels.

Use a rule hierarchy. Device- or form-factor-specific requirements override a general company rule; a simulated exception should be documented; and fabrication minimums are limits, not preferred routing dimensions.

Layer Assignment and Return-Path Continuity

Every high-speed route needs a continuous reference conductor. On a common signal-integrity-focused ten-layer stackup, outer signals reference adjacent ground planes and selected inner signals are placed between two ground planes. That arrangement is useful because the return current can remain close to the signal. Other stackups can work, but the layout rules must reflect their actual references.

Do not route across a reference split

When a trace crosses a void or a split in its reference plane, return current detours around the opening, increasing loop area and coupling into other structures. Moving the trace to a layer with a continuous reference is usually better than adding a capacitor after layout. If a power plane is intentionally used as a high-frequency reference, its connection to the relevant ground domain must be part of the design.

Layer changes require a return transition

A signal via moves the forward current between layers; the return current also needs a path between the old and new references. Ground-to-ground transitions commonly use nearby stitching vias. Power-to-ground transitions may need a decoupling structure placed so that the return loop is acceptably small over the relevant spectrum. “One ground via within 50 mil” is a heuristic, not a universal rule.

Adjacent signal layers

Orthogonal routing can reduce broadside coupling between adjacent signal layers, but it does not make an inherently poor stackup harmless. Where two signal layers face each other with no plane between them, limit overlap, increase separation and reserve the pair for less sensitive nets. For critical serial links, plane-separated routing is preferable.

Differential Pairs: Geometry, Skew and Transitions

A differential pair should preserve a consistent electromagnetic environment. Width, pair spacing, reference distance and nearby copper should remain within the structure used for impedance calculation. Short neck-downs at pads may be unavoidable, but they should be modeled or kept within a validated footprint.

Intra-pair skew is an electrical quantity

Convert the allowed time skew into length using the actual propagation delay on the routed layer. A pair that changes layers can have equal physical length but unequal delay if the two traces sample different glass, use different via geometry or encounter different reference transitions. For very high-speed links, extract delay and mode conversion rather than relying only on the PCB tool’s centerline length.

Keep the two transitions symmetric

Signal via pads, antipads, reference vias and breakout should be mirror-symmetric where practical. Avoid placing one trace closer to a plane void, mounting hole or connector shield feature. If polarity inversion is permitted by the interface, use it deliberately rather than adding a long crossover to preserve visual orientation.

Pair-to-pair matching is not automatically required

Many serial receivers deskew lanes, so forcing all PCIe or SerDes pairs to the same physical length can add unnecessary loss and meanders. Follow the governing lane-to-lane skew requirement, but prioritize low loss, clean return paths and minimal transitions. Intra-pair skew is normally more critical than matching unrelated lanes to one another.

DDR5 and Other Parallel Memory Interfaces

DDR5 constraints depend on controller package, DRAM organization, module or down topology, speed bin, loading and termination. The correct source is the controller and memory vendor’s design guide, supported by simulation models. A generic statement such as “DQ must match within +/-5 mil” can be either unnecessarily tight or unsafe for a particular platform.

Group rules by function

Define separate groups for DQ/DMI relative to DQS, differential clock, command/address/control and any module-specific signals. Use delay constraints in picoseconds where possible, because physical length converts differently on different layers. The layout tool can then apply layer-specific delay rather than assuming one propagation constant.

Topology matters

Command/address and clock may use a fly-by topology in module-based designs, while data signals are source-synchronous point-to-point connections within a byte lane. Down designs, registered modules and buffered modules introduce different loading and routing. Do not copy a DIMM topology onto a soldered-down design without the platform documentation.

Reference and power integrity

Memory timing is affected by reference-plane noise and power distribution as well as trace length. Keep byte lanes in a stable reference environment, provide appropriate VREF and VDDQ treatment, and avoid placing tuning structures over plane openings. Simulate simultaneous switching and termination behavior when platform margin is limited.

PCIe and High-Speed Serial Links

For PCIe Gen5 and later, route quality is dominated by frequency-dependent loss, connector and via discontinuities, crosstalk and mode conversion. A layout rule set should therefore include more than target impedance.

PCIe 6.0 uses PAM4 at 64 GT/s with the same 16 GHz Nyquist frequency as PCIe 5.0 NRZ, but it is not “the same channel with twice the bits.” The compliance, noise and FEC context differs. PCIe 7.0 at 128 GT/s moves the Nyquist frequency to 32 GHz and makes transition extraction and manufacturing correlation more demanding.

Crosstalk, Spacing and Reference-Plane Noise

The frequently cited 3W or 5W rule is a geometric heuristic. Crosstalk also depends on dielectric height, parallel length, aggressor rise time, reference structure and whether the lines are edge- or broadside-coupled. On a thin dielectric, a smaller spacing may already meet the target; on adjacent unreferenced signal layers, a large spacing may still be inadequate.

Set a crosstalk target appropriate to the interface and use extraction or a validated geometry table to turn that target into spacing. Consider the complete victim length and simultaneous aggressors. Clock, strobe and high-swing single-ended nets may deserve more isolation than unrelated slow controls.

Plane noise can couple through the reference structure even when trace-to-trace spacing is generous. Keep high-current switching loops compact, use appropriate plane pairs and decoupling, and avoid forcing sensitive traces to reference fragmented power islands. Crosstalk and power integrity should be reviewed together on dense processors and accelerator boards.

Length Tuning Without Creating a New Discontinuity

Meanders add delay, but closely spaced segments couple to each other and deliver less delay than their centerline length suggests. They also increase loss and create local impedance variation. Use the widest practical spacing between adjacent tuning segments, minimize the number of turns and distribute tuning where it does not disturb breakouts or reference continuity.

There is no universal rule that tuning must be near the source or near the receiver. Placement depends on topology and the purpose of the match. For a source-synchronous bus, tune within the defined group and preserve the topology. For a differential pair, correct skew with a compact, symmetric feature that does not create a long uncoupled section.

Rounded corners are not automatically required, and a single 90-degree bend is not a 15% reflection in every geometry. Use 45-degree or curved routing for manufacturability, pair symmetry and consistent spacing, but focus engineering effort on larger discontinuities such as pads, vias, connectors and reference-plane breaks.

BGA Escape, Vias and Manufacturability

BGA pitch alone does not determine whether HDI is required. Pad diameter, solder-mask strategy, number of rows, pin map, available routing layers and escape direction all matter. Some 0.5 mm-pitch devices can use a carefully designed through-via or limited blind-via approach; others require via-in-pad and multiple buildup layers. Review the actual package fanout rather than applying a pitch-only table.

Via-in-pad should state whether the via is copper filled, resin filled and capped, or handled by another qualified process. For stacked microvias, the buildup sequence and reliability plan must be agreed. The HDI guide covers structure selection; layout must still provide capture lands, antipads and keep-outs compatible with the supplier’s registration capability.

Escape routing should also preserve reference continuity. Dense antipad fields can remove too much plane copper under a package, so the power and ground breakout should be reviewed as an electromagnetic structure. Adding more ground vias is not always beneficial if it forces oversized voids or obstructs routing.

Pre-Fabrication Routing Review

A DFM review should not silently rewrite electrical constraints. When CAM proposes a width, pad, antipad or stackup change, the change should be checked against the impedance or channel model and documented. Submit the final layout with the fabrication drawing and netlist through the Proces přezkumu DFM.

Connector Launches, Board Boundaries and Test Structures

Connector launches are often larger discontinuities than ordinary bends. Review the signal pad, antipad, ground pin pattern, plane cutouts and transition into the routed pair as one structure. Vendor reference footprints are a starting point, not a guarantee, because board thickness, layer assignment and fabrication dimensions may differ. For the highest-speed connectors, use the vendor model and extract the local PCB launch.

At board edges, avoid abrupt reference-plane termination beneath a sensitive route. Card-edge contacts, coax launches and mezzanine connectors may require ground shaping, via fences or local layer transitions that are specific to the interface. Keep mechanical keep-outs, plating bars and breakaway tabs out of the electrical reference region unless they are included in the model.

Design test access without creating stubs

Ordinary probe pads and branched test points can add capacitance or an unterminated stub. Use a validated test coupon, connector access, removable component option or a pad integrated into the main transmission path. Coordinate in-circuit test requirements with signal integrity before layout is complete; deleting a test branch after qualification can also change the channel.

Document intentional exceptions

Dense layouts sometimes require a local width change, a reference transition or a spacing violation. Record the location, reason and simulation or vendor approval. A documented exception is safer than globally relaxing the rule or relying on a future DFM engineer to infer design intent.

Clock, Analog and Power Routing Boundaries

Not every important net is a differential serial link. Reference clocks, reset signals, analog sensor paths and switching-power nodes can create or receive interference. Classify nets by edge rate, noise sensitivity and current loop rather than by nominal frequency alone. A low-frequency clock with a fast edge can require more care than a higher-frequency sine wave.

Reference clocks

Route reference clocks over a continuous plane, avoid unnecessary test stubs and isolate them from switching nodes. The required topology-point-to-point, fanout buffer or another distribution method-comes from the clock source and receiver specifications. A star or daisy chain is not universally correct. Where multiple receivers are driven, simulate loading and termination.

Analog and converter interfaces

Keep small analog loops compact and separate them from aggressive digital return currents. Splitting the ground plane is not automatically beneficial; a continuous plane with thoughtful placement often provides a lower-impedance return. If analog and digital domains must join at a controlled point, ensure that signals do not cross the resulting gap and that the connection strategy matches the converter vendor’s guidance.

Switching power regions

The switch node, gate-drive loop and high-di/dt current paths deserve physical exclusion zones. Do not route high-speed pairs under inductors, transformers or switch-node copper. Plane voids and keep-outs should be reflected in the return-path review. Current-carrying width and thermal performance should be evaluated with IPC-2152 methods or validated simulation rather than a universal current-density number.

Document these regions in the layout constraints so DFM copper additions, thieving or panel features do not unintentionally enter a sensitive area.

Routing Rule Sign-Off

The final routing review should compare the layout with the released stackup and device-specific constraints rather than with a generic checklist of mil values. Critical groups should be checked using extracted delay, loss and transition models where those effects are material.

• Verify that every critical route remains over a continuous reference and that layer changes provide a return-current path.
• Check differential geometry through neck-downs, pads, vias, connectors and test structures-not only on straight traces.
• Apply memory timing by byte lane, command/address group and topology using the controller and memory documentation.
• Limit meanders and parallelism based on delay and crosstalk analysis rather than a universal spacing multiplier.
• Confirm BGA fanout, annular rings, antipads and via spans against the supplier’s approved capability.
• Deliver final artwork, netlist, drill/route data, stackup revision, impedance table and controlled-depth drawing as one revision-controlled package.

Layout rules should express the electrical objective and its source. This makes exceptions reviewable and prevents a fabrication change from silently invalidating the routing constraint set.

Managing Routing Exceptions

Dense layouts inevitably need exceptions to preferred rules. The objective is not to prohibit every neck-down, layer transition or local spacing reduction; it is to identify which exceptions are electrically significant and review them with the correct model.

Exceptions should be attached to nets, regions or classes and stored with the design review record. A broad verbal approval such as “spacing is acceptable” cannot be reproduced during an ECO or supplier transfer. The same principle applies to device-vendor reference layouts: preserve the electrical intent, but revalidate dimensions against the released board stackup.

The review record should also identify the extraction or simulation version used for critical exceptions. When an ECO moves a component, changes a layer or alters a connector footprint, the affected exception can then be re-evaluated instead of inheriting an approval that no longer matches the geometry.