STA Mastery · All levels
Path Depth Sensitivity: Mechanism
Mechanism for Path Depth Sensitivity.
Mechanism to understand
Mechanism for Path Depth Sensitivity focuses on short-path hold margin, long-path setup margin, depth bucket WNS. The goal is to connect the observable symptom to timing mechanism, ownership, and regression risk.
Short paths see different variation pessimism than long paths; depth-aware models prevent both optimism and excess margin. Think of STA as a signed contract between constraints, parasitics, and implementation — slack is the measurable outcome.
Identify launch and capture clocks on the failing path.
Identify path group: reg2reg, in2reg, reg2out, or async.
Identify whether setup, hold, or both fail in the scenario.
Layered view
STA CLOSURE FLOW — Path Depth Sensitivity
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.Depth vs slack scatter
SLACK vs LOGIC DEPTH
slack
+ | * * *
| * * *
0 |--*--*-----*--- WNS
| *
- |*
+----------------> depth (stages)
Short paths cluster left — hold risk zone.Layer responsibilities
STA OWNERSHIP LAYERS — Path Depth Sensitivity
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 cornerSTA deep dive
Variation policy is negotiated margin, not a tool checkbox.
Concept diagram
VARIATION STACK
nominal delay + OCV/AOCV/POCV margin = signoff delayMetric graph
DERATE IMPACT ON WNS
OCV only WNS -120ps
AOCV WNS -45ps
POCV WNS -60ps (policy dependent)Reports and artifacts
derate table
AOCV depth report
POCV sigma
hold/setup split
Mini case study
Switched to AOCV without re-baselining hold — short paths failed min analysis.
Debug branches
Short paths for hold
Policy approval for derate changes
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.
Mechanism deep dive
Short paths see different variation pessimism than long paths; depth-aware models prevent both optimism and excess margin.