Module 1311 min

Crosstalk & Signal Integrity

Crosstalk and signal integrity in STA: coupling capacitance, crosstalk delta delay (same vs opposite direction), noise glitches, fixes (spacing, shielding, NDR), and SI-aware signoff.

Pro Tip

Wires that run alongside each other are coupled by capacitance. When one net (the aggressor) switches, it injects charge onto its neighbour (the victim) through that coupling, changing the victim's delay, and sometimes creating a glitch on a net that should have been quiet. This is crosstalk, the heart of signal-integrity (SI) analysis, and at advanced nodes it is a first-class timing effect, not a footnote.

Coupling capacitance

Every pair of adjacent wires forms a small capacitor. The longer they run in parallel and the closer they are, the larger the coupling capacitance. On old, wide nodes this was negligible; on modern nodes, where wires are tall, thin and packed tightly, the coupling capacitance between neighbours can rival a net's capacitance to ground, so a neighbour's behaviour genuinely changes your net's timing.

Crosstalk delay (delta delay)

When the aggressor switches at the same time as the victim, it shifts the victim's delay, the delta delay. If the aggressor switches in the same direction as the victim, it helps the victim along and the victim gets faster (a negative delta delay). If it switches in the opposite direction, it fights the victim and the victim gets slower (a positive delta delay), which can push a path into a setup violation. The victim's own delay now depends on what its neighbours do.

A switching aggressor couples into the victim: same-direction speeds it up, opposite-direction slows it down (click to enlarge)

Crosstalk noise (glitch)

The second effect appears on a victim that is supposed to be quiet. When the aggressor switches, coupling injects a bump, a glitch, onto the static victim. If that glitch is large enough and lands on a signal like a clock, reset or an asynchronous input, it can be interpreted as a real transition and cause a functional failure. Noise analysis checks that glitches stay below the level downstream gates would react to.

How to fix crosstalk

  • Increase spacing between the victim and its aggressors (less coupling).
  • Shield the sensitive net, run grounded wires beside it so it couples to ground, not to a switching neighbour.
  • Apply non-default rules (NDR): wider, more-spaced routing for clocks and critical nets.
  • Strengthen the victim (upsize its driver) or weaken the aggressor (downsize / slow it) so the victim wins.
  • Buffer long parallel runs to break them into shorter coupled segments.

How STA handles it

Signoff STA does this with an SI-aware engine, PrimeTime-SI or Tempus SI. It identifies aggressor/victim pairs from the extracted parasitics, works out the worst-case switching alignment, and folds the delta delay into the timing and the glitch into noise checks. It is iterative because fixing one coupling can change another. See PrimeTime for where SI sits in signoff.

Note

Recap: adjacent wires couple through capacitance, so a switching aggressor changes a victim's timing (delta delay: same-direction faster, opposite slower) and can glitch a quiet net. Fix it with spacing, shielding, NDR and driver strength; sign it off with SI-aware STA. At advanced nodes, crosstalk is a real part of timing closure.