Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • RTL Foundations36
  • Combinational Design25
  • Sequential Design27
  • FSM & Control27
  • Timing & Clocking39
    • STA Foundations
      • Where RTL Meets STA
      • Canonical STA Flow
      • Corners
      • SDC Starter Set
      • Why RTL Architecture Dominates
    • Setup, Hold and Slack
    • Skew and Variation
    • Timing Exceptions
    • Clock Gating
    • RTL for Timing
    • Clock Architecture
  • Reset & CDC34
  • Memory & Buses57
  • Advanced RTL28
  • Senior & Interview76
  • Glossary and Notation
Loading lesson

‹Timing & Clocking
  1. Topics
  2. RTL Design
  3. Timing & Clocking
  4. STA Foundations

Part 5 · Timing & Clocking · Intermediate

STA Foundations

STA checks every path without vectors, and RTL structure decides the result.

  • 5topics
  • 5lessons

Topics in this section

  1. 1Where RTL Meets STA1 lesson
  2. 2Canonical STA Flow1 lesson
  3. 3Corners1 lesson
  4. 4SDC Starter Set1 lesson
  5. 5Why RTL Architecture Dominates1 lesson
On this page

    Static timing analysis checks every path against the clock without input vectors. It needs a netlist, constraints and libraries, and RTL structure decides its result.

    Flow from RTL through synthesis and STA to reports, with feedback to RTL.
    Static timing analysis combines the netlist, the constraints and the cell timing libraries into slack numbers for every path.

    Lessons in this topic

    5 lessons, about 24 min

    1. 1Where RTL Meets STAYou can name the startpoint and endpoint of each kind of timing path, say what RTL features set a path's contents, and estimate logic depth before running a tool.4 min
    2. 2Canonical STA FlowYou can run through the seven steps of a timing run, read WNS and TNS together, and fix negative slack in the right order.4 min
    3. 3CornersYou can explain why signoff checks several corners and modes, show with a scale factor how the path delay changes, and compute a minimum period from a path's terms.4 min
    4. 4SDC Starter SetYou can write the starter constraints (clocks, input and output delays, uncertainty), compute the input and output budgets, and audit coverage after applying them.6 min
    5. 5Why RTL Architecture DominatesYou can compare a plain adder with a prefix adder by depth and gate count, trace one carry through the prefix network, and list the levers that shorten a slow path.6 min
    Check yourself Simulation passes with 1,000,000 random vectors. Does that show the design meets timing?

    No. Functional simulation (without back-annotated delays) ignores delays entirely. Timing needs STA on the gate-level netlist with the constraints and the libraries.

    Interview

    “What is STA and how does it differ from simulation?” Static, exhaustive over paths (not over input values), needs constraints, checks setup and hold, cannot see functional bugs. Pair that answer with “what would you change in RTL if setup fails?”.

    Revision sheet

    The whole topic on one page, taken from each lesson's Remember box. Read it before an interview, or print it.

    Where RTL Meets STA

    • A path runs from a flip-flop clock pin or an input port to a flip-flop data pin or an output port.

    • Yosys ltp -noff finds the longest combinational path. Inspect its start and end nets, because it is not limited to register-to-register paths.

    • Levels ignore wire delay and fanout, so a path with fewer levels can still be slower.

    Rule of thumb: use depth as an early warning, and confirm it with real timing.

    Canonical STA Flow

    • A run reads libraries, netlist, constraints and parasitics, checks the constraints, updates timing and reports slack.

    • Check the constraints first, then the worst path, then group failing paths by cause. Hundreds of failures are often one slow module.

    • Fix depth and fanout structurally in RTL. Use tool optimisation for the small remainder.

    Rule of thumb: treat constraints as code, and read the unconstrained-endpoint report before trusting a clean summary.

    Corners

    • Gate delay depends on process, supply voltage and temperature, and wires add RC corners.

    • Slow data often limits setup and fast data often limits hold, but the relative clock and data delays decide the worst view.

    • Check every mode (functional, test, sleep) at every relevant corner.

    Rule of thumb: do not discard a hold failure in a slow view or a setup failure in a fast view.

    SDC Starter Set

    • With a 2.0 ns clock, 0.8 ns input delay and 0.15 ns uncertainty, the input budget is 1.05 ns for logic plus setup.

    • The output budget is the clock period minus the output delay and uncertainty (1.25 ns here), for clock-to-Q plus logic.

    • Every false path needs a written justification.

    Rule of thumb: a missing clock is silent, so check the unconstrained endpoints before you trust a clean summary.

    Why RTL Architecture Dominates

    • Plain + specifies the sum and not a ripple structure. Synthesis can restructure carry logic, and an explicit prefix network expresses one candidate.

    • Five prefix stages are not five gate levels, so the mapped depth is higher.

    • Compare candidates on the same library, constraints and physical flow before replacing portable arithmetic.

    Rule of thumb: start from the path: how many levels, which operator dominates, and which lever fits.

    Practise it

    • Mini project: close timing on an 8-tap FIR filter

    • Interview: run a mock interview on this topic

    PreviousNext: Where RTL Meets STA

    Up next

    Up nextWhere RTL Meets STA

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Setup, Hold and Slack
    • Skew and Variation
    • Timing Exceptions