I/O Timing & Boundary Contracts

What this topic teaches

I/O Timing & Boundary Contracts is about converting constraints and path rules into measurable slack. set_input_delay and set_output_delay translate board and pad timing into the block boundary so internal STA matches system timing. 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 interface setup/hold WNS, input/output delay coverage, port slack moves, can you identify the failing path group, the STA layer, the responsible owner, and the smallest experiment that proves the root cause?

STA CLOSURE FLOW — I/O Timing & Boundary Contracts

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.

Input / output delay model

BOARD                    CHIP BOUNDARY              INTERNAL
  |                            |                          |
pad delay -- set_input_delay -> FF capture path analyzed by STA
internal launch -- set_output_delay -> pad delay -> board

IO constraints are the contract between system and block STA.

Timing path sequence

TIMING PATH — I/O Timing & Boundary Contracts

launch FF --logic stages--> capture FF
     |                           |
  launch clock                capture clock
     |                           |
  required: arrival < capture_edge - setup
  metric: interface setup/hold WNS, input/output delay coverage, port slack

Who owns which layer

STA OWNERSHIP LAYERS — I/O Timing & Boundary Contracts

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: interface setup/hold WNS, input/output delay coverage, port slack.

• Primary artifact: boundary SDC, board delay spreadsheet, report_timing on IO paths.

• Owners to bring into review: STA owner, package owner, system integration 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

OWNERSHIP MAP — I/O Timing & Boundary Contracts

artifact              owner
----------------      -----------------
timing report       STA owner
SDC/constraint      package owner
implementation      system integration 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

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.