STA Mastery · All levels
MMMC Debug Playbook: Review Checklist
Review Checklist for MMMC Debug Playbook.
Review checklist
Review Checklist for MMMC Debug Playbook focuses on scenario-specific violation clusters, corner isolation time. 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 — MMMC Debug Playbook
artifact owner
---------------- -----------------
timing report STA owner
SDC/constraint timing closure lead
Every WNS cluster needs a named owner before ECO.STA deep dive
Signoff WNS is the minimum across the full scenario matrix.
Concept diagram
MMMC
corners (ss/tt/ff) x modes (func/test) x views (signoff RC)
= scenario set -> min(WNS) is signoffMetric graph
WNS HEATMAP BY CORNER
ss tt ff
setup -80 +10 +5
hold -15 -2 -8Reports and artifacts
per-corner WNS
mode summary
lib map audit
view delta
Mini case study
Passed TT typical but failed SS hold — signoff matrix was incomplete; added low-voltage mode.
Debug branches
Isolate failing scenario first
Never compare unlike SPEF tags
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
MMMC failures cluster by corner, mode, or library; triage isolates the scenario before touching RTL or layout.
Metric: scenario-specific violation clusters, corner isolation time