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

  • How to Use This Course
  • Reading Path
  • STA Glossary
  • STA Metrics Reference
  • STA Mastery Cheatsheet
  • Timing Paths and Checks16
  • Constraints & SDC Fundamentals20
    • Clock Definition & Uncertainty
    • Generated Clocks & Dividers
    • I/O Timing & Boundary Contracts
    • Exceptions & Audit Policy
      • False Paths
      • Multicycle Paths
      • Min and Max Delay Exceptions
      • Exception Audit
    • Environment and Design Rules
  • Delay Graph & Path Analysis16
  • Beyond Setup and Hold16
  • Multi-Corner Multi-Mode Signoff16
  • OCV, AOCV, POCV and Variation16
  • Crosstalk and Noise16
  • ECO and Closure16
  • STA Debug Playbook16
  • STA Interview Prep26
  • Capstone Timing Signoff Lab4
Loading lesson

‹Constraints & SDC Fundamentals
  1. Topics
  2. Static Timing Analysis
  3. Constraints & SDC Fundamentals
  4. Exceptions & Audit Policy

Part 2 · Constraints and SDC · All levels

Exceptions & Audit Policy

False paths, multicycle paths and min/max delay exceptions: what each removes or changes, and how to audit them.

  • 4topics
  • 4lessons

Exceptions tell STA that the default one-cycle relationship is wrong for some paths. They are powerful and dangerous: every exception removes or relaxes a check, and every wrong exception hides a real failure. This topic covers false paths, multicycle paths, point-to-point delay exceptions, and the audit and policy that keep them honest.

Lesson

After it you can...

False Paths

Say what a false path removes and when it is justified.

Multicycle Paths

Set setup and hold multipliers correctly.

Min and Max Delay Exceptions

Replace a path requirement with an explicit delay limit.

Exception Audit

Run an audit that catches overbroad or stale exceptions.

The RTL view is in Multi-Cycle and False Paths; the CDC view of exceptions is in CDC Constraints and STA.

Check yourself Which is more dangerous in review, a missing exception or an extra one?

An extra (overbroad) one: a missing exception produces a visible violation, while an extra one silently removes a check and the report looks cleaner than it should.

Interview

Frame every exception as a claim: this path never matters, or this path has N cycles. Then ask what evidence supports the claim.

PreviousNext: False Paths

Up next

Up nextFalse Paths

Sign in to save progress

Practice this lessonReport an error

See also

  • Clock Definition & Uncertainty
  • Generated Clocks & Dividers
  • I/O Timing & Boundary Contracts