Delta Delay Mechanism: Theory Deep Dive

Foundational theory

Delta Delay Mechanism is central to SI Timing & Noise. Coupling capacitance between adjacent nets changes effective delay; aggressors slow or speed victims depending on switching alignment. Senior STA engineers always tie slack movement to corner, mode, constraint set, and parasitic view — not just a single report line.

Core concepts explained

• Coupling capacitance between adjacent nets changes effective delay; aggressors slow or speed victims depending on switching alignment.

• Primary metric: delta delay on critical paths, aggressor count, SI WNS impact

• Primary artifact: SI report, coupled net list, delta delay histogram

• Owners: SI owner, STA owner, extraction owner

• Setup: max delay path; Hold: min delay path

• WNS/TNS summarize tail risk across endpoints

Why this matters at signoff

At signoff, Delta Delay Mechanism failures block tapeout or force risky ECO. Coupling makes delay context-dependent — aggressors matter. Wrong analysis setup wastes weeks of PD effort.

Mental model

VICTIM NET  ~~~~~~~~~~~~ (quiet)
AGGRESSOR   ^   ^   ^   ^  (switching)

Aligned switching -> delta delay on victim
SI analysis adds coupling to effective RC

Worked intuition

1. Name corner, mode, and view for the failing run.

2. Open delta delay on critical paths, aggressor count, SI WNS impact and identify worst path group.

3. Read critical path: cell vs net, launch/capture clocks.

4. Check constraints on that path (exceptions, generated clocks).

5. Collect SI report, coupled net list, delta delay histogram and tag database versions.

6. Classify: constraint bug, view mismatch, or real path.

7. Propose minimal ECO and list MMMC+SI regression.

Common misconceptions

• One typical corner is enough for signoff.

• False paths can be applied broadly to green-wash violations.

• Implementation WNS equals signoff WNS without view mapping.

• Setup fix automatically preserves hold.

Visual reinforcement

Aggressor / victim coupling

VICTIM NET  ~~~~~~~~~~~~ (quiet)
AGGRESSOR   ^   ^   ^   ^  (switching)

Aligned switching -> delta delay on victim
SI analysis adds coupling to effective RC

Layer responsibilities

STA OWNERSHIP LAYERS — Delta Delay Mechanism

layer              owns                         failure mode
----------------   --------------------------   ---------------------
constraints        clocks, IO, exceptions       false violations
implementation     cells, nets, placement       real path delay
extraction         SPEF/RC corners              view mismatch
signoff policy     derate, MMMC matrix          margin disputes
closure           ECO order, regression        fix breaks other corner

STA deep dive

Coupling makes delay a function of neighbors, not just wire RC.

Concept diagram

SI ON VICTIM

victim net delay = base_RC + coupling_from_aggressors

Metric graph

DELTA DELAY ON CRITICAL PATHS

no SI   ████████  1.2ns
with SI ██████████  1.35ns  (+150ps)

Reports and artifacts

• delta delay report

• aggressor list

• noise peaks

• SI WNS delta

Mini case study

Setup fixed by upsize but SI worsened — spacing ECO on bus bits recovered margin.

Debug branches

• Re-run SI after every timing ECO

• Shield wide switching buses

Senior review question

Ask: what corner/mode/view proves this topic is closed or failing?

Key takeaways

• State corner, mode, view, and database tag with every slack claim.

• Run setup and hold plus MMMC regression after every ECO.

Common pitfalls

• Comparing STA runs with different SPEF or SDC tags.

• Broad false_path to green-wash violations.

• Setup-only ECO without hold check.

Theory reinforcement

Coupling makes delay context-dependent — aggressors matter.