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
  • The NanoSoC Tour
  • Reading Path
  • SoC Glossary10
  • SoC Metrics Reference
  • SoC Cheatsheet
  • What SoC Integration Is12
  • Architecture and Budgets21
  • Memory Maps and Address Decode26
  • Interconnect and Bus Fabrics26
  • Clock and Reset Architecture24
  • Power Architecture21
  • Interrupts, DMA and Peripherals15
  • Memories, Boot and Security21
  • IP Integration and Handoff21
  • Top-Level Verification and Bring-up21
  • Package, Pads and I/O18
  • Chip Signoff and Tapeout18
    • The Signoff Manifest
      • What Goes in the Manifest
      • Freezing a Baseline
      • The Manifest Checker
    • Waiver Governance
    • Closure Dashboards
    • Tapeout Readiness Review
    • ECO and Respin Risk
    • Errata and Post-Silicon
  • SoC Interview Prep16
  • Capstone: Integrate NanoSoC14
Loading lesson

←Chip Signoff and Tapeout
  1. Topics
  2. SoC Design
  3. Chip Signoff and Tapeout
  4. The Signoff Manifest

Part 12 of 14Part 12 of 14/Chip Signoff and TapeoutAll levels

The Signoff Manifest

What goes in the manifest, freezing a baseline, reproducibility, and a checker that proves it complete.

  • 3topics
  • 3lessons

The manifest is the single document that says what is being taped out and what was checked. Every argument at a tapeout review is really an argument about the manifest: a version nobody recorded, a check nobody ran, a result attached to the wrong revision. This topic builds the NanoSoC manifest from scratch: what rows it holds, how the baseline is frozen so it cannot drift, how a second engineer reproduces it, and the script that checks it every night. Its one job is the list and its integrity; what the waivers inside it mean is the next topic.

Lesson

After it you can...

What Goes in the Manifest

Name every row of a chip manifest and who owns it.

Freezing a Baseline

Freeze a baseline, derived databases included, so no input can drift under a result.

The Manifest Checker

Run the checker that proves a manifest complete and current, and make it fail on purpose.

Suggested order: top to bottom. Contents first, because the freeze only makes sense once you know what is frozen; then the checker, which enforces both. The waiver topic next door explains the rows this topic treats as entries.

Check yourself A timing result is green but was run against last week's netlist. What is broken: the check or the manifest?

The manifest: a result without a recorded revision is not evidence. The freeze rule exists so this cannot happen silently.

If asked what you would demand before signing, answer with the manifest rows: revisions, the databases results ran on, checks, results, waivers, and the dashboard that summarises them.

PreviousNext: What Goes in the Manifest

Up next

Up nextWhat Goes in the Manifest

Sign in to save progress

Practice this lessonPrevious lessonReport an error

See also

  • Waiver Governance
  • Closure Dashboards
  • Tapeout Readiness Review