Library Set & Opcond Mapping: Interview Drills

Interview drills

Interview Drills for Library Set & Opcond Mapping focuses on library mismatch count, opcond alignment errors, derate mapping gaps. The goal is to connect the observable symptom to timing mechanism, ownership, and regression risk.

PROMPT
You see library mismatch count, opcond alignment errors, derate mapping gaps on Library Set & Opcond Mapping. Walk through root cause and fix.

STRONG ANSWER
1. Names corner/mode/view and path group.
2. Explains Each corner binds liberty libraries and operating conditions; wrong mapping makes every slack number meaningless.
3. Requests library configuration report, .lib corner map, opcond audit.
4. Proposes one reduced sequence and one system regression.

WEAK ANSWER
Jumps to upsizing cells, widening routes, or blaming tools without reading constraints and path delay.

Diagram to draw on the whiteboard

Corner to library mapping

CORNER ss_0p72v_125c
  -> opcond: ss_125c_0p72v
  -> lib: stdcell_ss_125c.lib
  -> rc: cworst_RC

Wrong lib at corner -> all slack invalid.

Root-cause tree to narrate

ROOT-CAUSE TREE — Library Set & Opcond Mapping

library mismatch count, opcond alignment errors, derate mapping gaps looks wrong
        |
   same netlist tag?
     /        \
   no          yes
   |            |
 view/SDC     real path or
 mismatch     constraint bug
 /    \           |
lib   SPEF    delay breakdown
diff  diff    cell vs net

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.

Principal STA review addendum

Each corner binds liberty libraries and operating conditions; wrong mapping makes every slack number meaningless.

Metric: library mismatch count, opcond alignment errors, derate mapping gaps