STA Mastery · All levels

Useful Skew Tradeoffs

ECO Timing Closure: Intentional clock skew can borrow setup time but increases hold risk and clock tree complexity; useful skew is a negotiated margin.

What this topic teaches

Useful Skew Tradeoffs is about converting constraints and path rules into measurable slack. Intentional clock skew can borrow setup time but increases hold risk and clock tree complexity; useful skew is a negotiated margin. 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 skew budget used, hold impact, clock tree power 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 — Useful Skew Tradeoffs

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.

Useful skew borrow

diagram

CLOCK AT CAPTURE FF delayed intentionally

launch edge  |
data path    |-------->
capture edge |    +skew borrow
             more setup margin, hold risk increases

Timing path sequence

diagram

TIMING PATH — Useful Skew Tradeoffs

launch FF --logic stages--> capture FF
     |                           |
  launch clock                capture clock
     |                           |
  required: arrival < capture_edge - setup
  metric: skew budget used, hold impact, clock tree power

Who owns which layer

diagram

STA OWNERSHIP LAYERS — Useful Skew Tradeoffs

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: skew budget used, hold impact, clock tree power.
Primary artifact: CTS skew report, useful skew map, hold regression.
Owners to bring into review: CTS owner, STA lead, 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 — Useful Skew Tradeoffs

artifact              owner
----------------      -----------------
timing report       CTS owner
SDC/constraint      STA lead
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

ECO without regression is a coin flip.

Concept diagram

diagram

ECO LOOP

failing path -> fix -> setup check -> hold check -> SI -> MMMC matrix

Metric graph

diagram

ECO PROGRESS

WNS
 0 |              o target
-50|        o
-100|   o baseline
    +-----------------> ECO #

Reports and artifacts

pre/post WNS
hold delta
leakage delta
ECO ticket log

Mini case study

48-hour tapeout crunch: VT swap fixed setup; hold fixed with route on short path — order mattered.

Debug branches

Never ship setup-only proof
Logical ECO needs equivalence

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