Clock Definition & Uncertainty: Theory Deep Dive

Foundational theory

Clock Definition & Uncertainty is central to Constraints & SDC Fundamentals. SDC clocks define launch and capture time bases; uncertainty and skew model timing margin consumed before data-path delay is evaluated. Senior STA engineers always tie slack movement to corner, mode, constraint set, and parasitic view — not just a single report line.

Core concepts explained

• SDC clocks define launch and capture time bases; uncertainty and skew model timing margin consumed before data-path delay is evaluated.

• Primary metric: WNS/TNS on clocked paths, clock skew reports, uncertainty budget

• Primary artifact: report_clock, clock tree report, SDC clock block, skew histogram

• Owners: STA owner, synthesis owner, CTS owner

• Setup: max delay path; Hold: min delay path

• WNS/TNS summarize tail risk across endpoints

Why this matters at signoff

At signoff, Clock Definition & Uncertainty failures block tapeout or force risky ECO. SDC is the contract between RTL intent, synthesis, and signoff STA. Wrong analysis setup wastes weeks of PD effort.

Mental model

SETUP CHECK (simplified)

launch clock edge ----> data propagates through logic ----> arrives at capture FF
                                                              |
capture clock edge -----------------------------------------> required time
                                                              |
slack = required_time - arrival_time  (setup)

Hold is the reverse inequality: data must stay stable after capture edge.

Worked intuition

1. Name corner, mode, and view for the failing run.

2. Open WNS/TNS on clocked paths, clock skew reports, uncertainty budget and identify worst path group.

3. Read critical path: cell vs net, launch/capture clocks.

4. Check constraints on that path (exceptions, generated clocks).

5. Collect report_clock, clock tree report, SDC clock block, skew histogram and tag database versions.

6. Classify: constraint bug, view mismatch, or real path.

7. Propose minimal ECO and list MMMC+SI regression.

Common misconceptions

• One typical corner is enough for signoff.

• False paths can be applied broadly to green-wash violations.

• Implementation WNS equals signoff WNS without view mapping.

• Setup fix automatically preserves hold.

Visual reinforcement

Launch vs capture clock domains

SETUP CHECK (simplified)

launch clock edge ----> data propagates through logic ----> arrives at capture FF
                                                              |
capture clock edge -----------------------------------------> required time
                                                              |
slack = required_time - arrival_time  (setup)

Hold is the reverse inequality: data must stay stable after capture edge.

Uncertainty budget stack

CLOCK UNCERTAINTY BUDGET

period
  |-- clock skew (CTS)
  |-- jitter (source + PLL)
  |-- uncertainty (SDC margin)
  |-- useful skew (if any)
  = effective capture window for data

If uncertainty is too small -> false optimism.
If too large -> wasted timing margin.

Layer responsibilities

STA OWNERSHIP LAYERS — Clock Definition & Uncertainty

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

STA deep dive

SDC quality determines whether STA measures reality or fiction.

Concept diagram

SDC FLOW

RTL clocks -> create_clock / generated_clock
board      -> set_input/output_delay
exceptions -> false_path / multicycle (audited)
analysis   -> report_timing

Metric graph

CONSTRAINT QUALITY

audited exceptions  ████████████████  good
stale IO delays     ██████            risk
missing gen clock   ████              high escape

Reports and artifacts

• clock report

• uncertainty budget

• IO delay coverage

• exception audit log

Mini case study

1000 new failing paths overnight: SDC merge dropped a generated_clock on divider output. No PD change needed.

Debug branches

• Diff SDC before ECO

• Validate clocks on failing path

• Audit false paths quarterly

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.

Theory reinforcement

SDC is the contract between RTL intent, synthesis, and signoff STA.