How does crosstalk change delay, not just add noise?
From PDVerse PnR Interview Handbook · pdVerse Mentor Guide
Short Answer
When the aggressor and victim switch at the same time, the coupling capacitance changes how much charge the victim's driver must move. If they switch in opposite directions, the victim sees roughly its own capacitance plus twice the coupling, so it slows down. If they switch the same way, it speeds up, so crosstalk can hurt setup on one path and hold on another.
Technical Explanation
- A coupling capacitor between two wires has one wire on each plate. What the victim driver has to charge depends on how much the voltage across that capacitor changes.
- If only the victim switches, the coupling capacitor sees one full swing and acts like capacitance to ground:
Cv + Cx. - If the aggressor switches the opposite way at the same time, the voltage across the capacitor changes by two swings, so the effective load is about
Cv + 2Cx. The victim transition slows and its delay grows. - If both switch the same way, the capacitor sees almost no change and the victim moves faster than normal.
- The slowdown matters for setup on max paths, and the speed-up matters for hold on min paths. Signal integrity analysis applies each where it hurts.
- Timing windows decide whether the aggressor can actually switch while the victim does. If their windows never overlap, the delta is filtered out, which avoids false pessimism.
- Fixes include more spacing, shielding, changing layers, upsizing the victim driver, or making aggressor and victim drive strengths more similar.
Formula Or Decision Rule
- Opposite-direction switching: the victim sees an effective load of about
Cv + 2Cx, so it slows down (positive delta delay). - Same-direction switching: the coupling capacitor sees little voltage change, so the victim speeds up (negative delta delay).
Cv= victim capacitance to ground,Cx= coupling capacitance to the aggressor.
What To Check
- The crosstalk delta column in timing reports for the worst setup and hold paths.
- Nets with the largest delta delay, and who their aggressors are.
- Whether the aggressor and victim timing windows really overlap.
- Whether signal integrity analysis was enabled when the timing was run.
Command Checks & Actions
set_app_options -name time.si_enable_analysis -value trueTurns on signal integrity analysis so crosstalk delta delay is included in timing.
report_timing -delay_type max -crosstalk_deltaShows the worst setup path with each net's crosstalk delta delay.
report_timing -delay_type min -crosstalk_deltaShows the worst hold path, where negative delta delay makes data faster.
report_noiseReports noise violations, the glitch side of crosstalk, on routed nets.
Healthy, Suspicious & Hard-stop Results
- Healthy (illustrative): Delta delay on critical paths of a few picoseconds, with slack covering it in every scenario.
- Suspicious (illustrative): One net carrying most of a path's delta delay, usually a long parallel run beside a busy bus.
- Hard stop: Timing signed off with signal integrity analysis turned off.
Common Mistake
The Trap: Checking crosstalk only on setup paths. A same-direction aggressor speeds up a short data path by 12 ps, and a hold check that passed by 8 ps without SI now fails by 4 ps. The hold failure appears only in the SI-enabled signoff run.
What The Interviewer Is Testing
- Whether you can explain the
Cv + 2Cxresult physically. - Do you apply crosstalk to both setup and hold?
- A strong answer shows you know timing windows filter out impossible cases.
Follow-up Question & Model Response
"Why does a stronger victim driver reduce delta delay?"
Candidate Model Response: Delta delay comes from extra charge the victim driver has to move during its transition. A stronger driver has lower output resistance, so it moves that extra charge faster, and the transition stretches less. It also holds the victim more firmly against the aggressor's push. That is why upsizing the victim driver is a standard fix, although it adds input load to the previous stage.
Practical Example
Tapeout Scenario: A victim net has Cv = 20 fF and Cx = 8 fF to one aggressor (illustrative). Alone, its driver sees 28 fF. With the aggressor switching the opposite way, the effective load is about 20 + 16 = 36 fF, roughly 29% more, and report_timing -crosstalk_delta shows +11 ps on that stage. Increasing the spacing halves Cx to 4 fF, bringing the opposite-direction load to 28 fF, and the delta drops to +5 ps. On a hold path through the same pair, same-direction switching showed -7 ps before the change and -3 ps after.
PnR Flow Mentor Guide
Master the Physical Design Implementation Flow
Read the complete 8-chapter PnR Flow Mentor Guide free on the web — library setup through placement, clock tree synthesis, routing, chip finishing, hierarchical implementation, and ECO, all the way to stream-out.

Continue practising