STA Mastery · All levels

Report Timing Deep Read: Step-by-Step Walkthrough

Step-by-Step Walkthrough for Report Timing Deep Read.

Step-by-step analysis walkthrough

Use when you own Report Timing Deep Read in a timing war room.

Open signoff scenario list — note worst WNS corner.
report_timing -max/-min on failing group.
Trace launch and capture clocks on critical path.
Check exceptions and generated clocks on path.
Break down cell vs net delay.
Compare implementation vs signoff view if delta suspicious.
Assign owner: RTL, synth, PD, CTS, SI.
Propose ECO with hold/SI check plan.
Run regression matrix.
Update closure dashboard and memo.

Artifacts to collect

annotated timing report, path viewer screenshot, constraint trace
SDC file
SPEF tag
MMMC scenario list
ECO ticket

Decision memo template

diagram

STA DECISION MEMO — Report Timing Deep Read
corner/mode:
WNS/TNS:
hypothesis:
ECO:
regression:
owners: STA owner, timing closure lead

Reference visuals

Critical path annotation

diagram

REPORT TIMING LINE (what to read)

 (rise) 0.12  U234/Z (AND2)     <- incremental delay
        0.45  net foo/bar       <- net delay + fanout
 (fall) 0.08  U567/D (DFF)      <- sense and edge matter
 clock: clk_main rise@500ps      <- launch/capture clocks

Read incremental delay, not just total slack.

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.

Principal STA review addendum

Senior STA debug reads incremental delay, sense, edge, clock domain, and exception flags on the critical path — not just slack number.

Metric: incremental delay attribution accuracy, false debug rate

Practice this lesson