STA Mastery · All levels

Path Group Prioritization

Delay Graph & Path Analysis: Path groups classify timing intent so optimization and debug focus on the paths that matter for signoff and product modes.

What this topic teaches

Path Group Prioritization is about converting constraints and path rules into measurable slack. Path groups classify timing intent so optimization and debug focus on the paths that matter for signoff and product modes. 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 WNS by path group, reg2reg vs in2reg vs reg2out slack moves, can you identify the failing path group, the STA layer, the responsible owner, and the smallest experiment that proves the root cause?

diagram

STA CLOSURE FLOW — Path Group Prioritization

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.

Path group map

diagram

PATH GROUPS

reg2reg   : FF -> logic -> FF     (core closure)
in2reg    : input -> FF           (interface)
reg2out   : FF -> output          (interface)
reg2cg    : FF -> clock gate      (special hold risk)

Optimize and report WNS per group — not global average only.

Timing path sequence

diagram

TIMING PATH — Path Group Prioritization

launch FF --logic stages--> capture FF
     |                           |
  launch clock                capture clock
     |                           |
  required: arrival < capture_edge - setup
  metric: WNS by path group, reg2reg vs in2reg vs reg2out slack

Who owns which layer

diagram

STA OWNERSHIP LAYERS — Path Group Prioritization

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: WNS by path group, reg2reg vs in2reg vs reg2out slack.
Primary artifact: path group summary, group_policy SDC, endpoint classification report.
Owners to bring into review: STA lead, synthesis owner, PD owner.
Spec clause or requirement ID for every constraint claim.
One failing report_timing excerpt and one reduced path that isolates the rule.

Ownership map

diagram

OWNERSHIP MAP — Path Group Prioritization

artifact              owner
----------------      -----------------
timing report       STA lead
SDC/constraint      synthesis owner
implementation      PD owner

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

Slack is a path story — read the graph, not just the number.

Concept diagram

diagram

TIMING GRAPH

FF --cell-- logic --net-- logic --cell-- FF
launch                              capture

Metric graph

diagram

SLACK TAIL

paths |    ***
      |  *******
      |*********  <- fix WNS first

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

Practice this lesson