MMMC Debug Playbook

What this topic teaches

MMMC Debug Playbook is about converting constraints and path rules into measurable slack. MMMC failures cluster by corner, mode, or library; triage isolates the scenario before touching RTL or layout. The hard part is never the textbook inequality; it is proving, under the right corner/mode/view, which layer — constraint, view, or implementation — broke the contract.

The senior-engineer question

When scenario-specific violation clusters, corner isolation time moves, can you identify the failing path group, the STA layer, the responsible owner, and the smallest experiment that proves the root cause?

STA CLOSURE FLOW — MMMC Debug Playbook

constraints (SDC)
        |
        v
timing graph (cell + net delays)
        |
        v
MMMC scenarios (corner x mode x view)
        |
        v
variation + SI adjustments
        |
        v
slack (WNS/TNS) -> ECO -> regression

Debug rule: always state corner, mode, view, and database tag with slack.

Picture the timing closure flow

Start every study session by drawing the behavior before reading signals. The diagrams below are the mental models to reproduce on a whiteboard.

Corner isolation heatmap

WNS BY CORNER (mV)

        ss   tt   ff
reg2reg -80  +20  +5
hold    -12  -3   -15
io      +10  +30  +25

Cluster guides which scenario to debug first.

Timing path sequence

TIMING PATH — MMMC Debug Playbook

launch FF --logic stages--> capture FF
     |                           |
  launch clock                capture clock
     |                           |
  required: arrival < capture_edge - setup
  metric: scenario-specific violation clusters, corner isolation time

Who owns which layer

STA OWNERSHIP LAYERS — MMMC Debug Playbook

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

Evidence to collect

• Primary metric: scenario-specific violation clusters, corner isolation time.

• Primary artifact: per-corner WNS heatmap, mode failure matrix, scenario replay script.

• Owners to bring into review: STA owner, timing closure lead.

• Spec clause or requirement ID for every constraint claim.

• One failing report_timing excerpt and one reduced path that isolates the rule.

Ownership map

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.

Subpages in this topic

Each topic is taught across mechanism, inputs/outputs, reports, debug, worked example, pitfalls, interview, checklist, theory, design space, expanded case study, walkthrough, comparison matrix, software view, and silicon PPA impact.

Key takeaways

• State corner, mode, and view with every slack number.

• Separate constraint bugs, view mismatches, and real path delays before ECO.

• Run setup and hold plus full MMMC after every change.

Common pitfalls

• Comparing runs with different SPEF or SDC tags.

• Broad false_path to hide violations.

• Setup-only ECO without hold regression.

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 signoff

Metric graph

WNS HEATMAP BY CORNER

        ss    tt    ff
setup  -80   +10   +5
hold   -15   -2    -8

Reports 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.