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

AboutRoadmapCareersInternshipsFAQContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • Reading Paths
  • Glossary
  • Metrics Reference
  • Formal Cheat Sheet
  • Formal Foundations19
  • Properties and SVA16
  • Property Development and Constraints19
  • Proof Engines and Convergence23
  • Formal Applications20
  • Equivalence Checking14
  • Formal Coverage and Signoff15
  • Methodology and Debug13
  • Interview Prep15
  • Capstone: A Chip-Block Verification Lab24
    • The Brief
      • The Brief and Deliverables
      • The Lab Harness and Engine
    • Stage 1: FIFO and Handshake
    • Stage 2: Registers and Arbiter
    • Stage 3: Pipeline and Equivalence
    • Stage 4: Induction and Signoff
    • Solutions
    • Appendix: Run It Yourself on an Open-Source Flow
Loading lesson

←Capstone: A Chip-Block Verification Lab
  1. Topics
  2. Formal Verification
  3. Capstone: A Chip-Block Verification Lab
  4. The Brief

Part 10 of 10Part 10 of 10/Capstone: A Chip-Block Verification LabAll levels

The Brief

The lab contract: the block under verification, what you must deliver, how it is graded, and how the results ledger is checked.

  • 2topics
  • 2lessons

You are the formal owner for a small chip block: a 4-entry FIFO, a valid/ready bridge stage, four control registers, a 4-requester round-robin arbiter, a 3-stage arithmetic pipeline with a retimed twin, and a decade counter. The lab plants 16 faults across the six designs. You get the symptoms first and the causes last: every stage lesson gives inputs, a deliverable and a pass criterion, and the Solutions topic after stage 4 gives the causes, the killing properties and the fixes. Every stage ends in the same place, rows in a results ledger that a script can check.

Lesson

After it you can...

The Brief and Deliverables

State the requirement set, the deliverables, the rubric, and the planted faults from their symptoms.

The Lab Harness and Engine

Fill in a ledger row from a run, and read each complaint the ledger checker can raise.

Suggested order: the brief first, then the harness lesson with the runner open beside you. Until the appendix at the end of the section, no tool is named.

The brief gives symptoms. Stages 1 to 4 each produce ledger rows that cite runs. The engine checks the rows. Only then does the Solutions topic give causes.
How the lab is arranged: symptoms first, work in four stages, rows checked by the engine, causes only after the checks.
Check yourself What is the one artefact every stage must produce?

Ledger rows: one per obligation, each citing the run it rests on. Proofs without ledger rows do not count.

Related topics

  • Earlier: The Formal Signoff Package

  • Formal Glossary

PreviousNext: The Brief and Deliverables

Up next

Up nextThe Brief and Deliverables

Sign in to save progress

Practice this lessonPrevious lessonReport an error

See also

  • Stage 1: FIFO and Handshake
  • Stage 2: Registers and Arbiter
  • Stage 3: Pipeline and Equivalence