STA Mastery · All levels
Report Timing Deep Read: Review Checklist
Review Checklist for Report Timing Deep Read.
Review checklist
Review Checklist for Report Timing Deep Read focuses on incremental delay attribution accuracy, false debug rate. The goal is to connect the observable symptom to timing mechanism, ownership, and regression risk.
SDC revision and implemented clock/exception policy are named.
Clock/reset and CDC assumptions are reviewed.
Path groups, IO delays, and exception rationale are documented.
MMMC scenario list maps back to signoff requirements.
WNS/TNS artifact stored with corner/mode/view tags.
Owners signed: STA owner, timing closure lead.
Sign-off ownership
OWNERSHIP MAP — Report Timing Deep Read
artifact owner
---------------- -----------------
timing report STA owner
SDC/constraint timing closure lead
Every WNS cluster needs a named owner before ECO.STA deep dive
Slack is a path story — read the graph, not just the number.
Concept diagram
TIMING GRAPH
FF --cell-- logic --net-- logic --cell-- FF
launch captureMetric graph
SLACK TAIL
paths | ***
| *******
|********* <- fix WNS firstReports and artifacts
WNS/TNS
path slack histogram
cell vs net %
path group summary
Mini case study
WNS -90ps but 80% net delay on one congested route — PD route fix beat upsizing three cells.
Debug branches
Cell-heavy -> sizing/VT
Net-heavy -> route/layer
Check launch/capture clocks
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
Senior STA debug reads incremental delay, sense, edge, clock domain, and exception flags on the critical path — not just slack number.
Metric: incremental delay attribution accuracy, false debug rate