SI Signoff Reports: Expanded Case Study

Extended case study

Signoff review: SI-clean path %, remaining aggressor violations, signoff waiver count fails after an apparently minor change affecting SI Signoff Reports.

Background

Team had closure last week on full MMMC matrix. New run shows regression clustered in one path group.

Symptoms observed

• SI-clean path %, remaining aggressor violations, signoff waiver count regression

• Disagreement between synth and STA WNS

• Hold violations after setup ECO

Investigation timeline

1. Hour 0: freeze netlist, SDC, SPEF, lib tags

2. Hour 1: diff constraints and run manifest

3. Hour 2: isolate corner/mode that fails

4. Hour 3: read worst path — cell vs net, clocks

5. Hour 4: classify root cause

6. Hour 5: minimal ECO or SDC fix

7. Hour 6: full regression + signoff memo

Root cause

Root cause tied to SI Signoff Reports: SI signoff aggregates delta delay and noise against foundry rules and product margin; reports must map to fix ownership.

Fix and validation

• Bounded ECO or audited SDC change

• Re-run SI signoff summary, foundry SI checklist, waiver log

• Full MMMC + SI regression

Lessons learned

• Tag every run

• Diff constraints before blaming PD

• Setup and hold together

CASE STUDY — SI Signoff Reports
baseline WNS / regressed WNS / post-fix WNS

Sequence under stress

TIMING PATH — SI Signoff Reports

launch FF --logic stages--> capture FF
     |                           |
  launch clock                capture clock
     |                           |
  required: arrival < capture_edge - setup
  metric: SI-clean path %, remaining aggressor violations, signoff waiver count

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.

Principal STA review addendum

SI signoff aggregates delta delay and noise against foundry rules and product margin; reports must map to fix ownership.

Metric: SI-clean path %, remaining aggressor violations, signoff waiver count