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
  • SoC Interview Prep16
  • Capstone: Integrate NanoSoC19
    • Capstone Brief
    • Stage 1: Memory Map and Interconnect
    • Stage 2: Clocks, Resets, Power
    • Stage 3: Interrupts and Boot
    • Stage 4: Verification and Signoff
      • Integration Test Plan Catching All Ten
      • Signoff Manifest and Waiver Ageing
      • Final Manifest Check and Readiness
    • Solutions
Loading lesson

←Stage 4: Verification and Signoff
  1. Topics
  2. SoC Design
  3. Capstone: Integrate NanoSoC
  4. Stage 4: Verification and Signoff
  5. Signoff Manifest and Waiver Ageing
On this page

    Part 14 of 14, lesson 13 of 19Part 14 of 14/Capstone: Integrate NanoSoC/Lesson 13 of 19All levels

    Signoff Manifest and Waiver Ageing

    Produce a manifest with digests and a checked waiver table.

    The observation to investigate

    Gather results from all stages with the revisions of the data that produced them. A copied result without its inputs is incomplete evidence.

    Required behaviour

    All stage artefacts feed the manifest; a signed baseline is reviewed data; waiver evidence must match its inputs.
    Capstone manifest dependencies and waiver evidence

    What to notice. All stage artefacts feed the manifest; a signed baseline is reviewed data; waiver evidence must match its inputs.

    Check yourself When the map changes after signing, which dependency must be revisited?

    The Stage 1 map and all results derived from it; the old signature does not establish the changed baseline.

    Your investigation

    Generate every manifest field from the stage artefacts. Record a revision or digest for each input and choose a controlled change to prove that the comparison notices drift. Review waiver age, expiry, evidence revision and ownership; label project-specific limits illustrative.

    Inputs to start from

    • The manifest fields in What Goes in the Manifest and the baseline rules in The Manifest Checker.

    • The stage 1 to 3 artefacts and a revision or digest for each.

    • A waiver list with owner, expiry date, evidence reference and revision (project limits illustrative).

    Deliverable and pass criterion

    Deliverable. A generated manifest with one entry per stage artefact and its digest, and a waiver table checked against the review date.

    Pass criterion. The comparison against the signed baseline passes on unchanged inputs and fails when you alter one input; an expired, unowned or stale-evidence waiver is flagged.

    Evidence to hand in

    • The manifest with each digest.

    • The controlled change you made and the line of output that shows the comparison noticing it.

    • The waiver table with the outcome for each row.

    Keep your diagnosis in your own report. After the stage checks, compare it with Solutions and run the provided injection checks.

    Related topics

    • Next: Final Manifest Check and Readiness

    • NanoSoC reference tour

    Previous

    278 / 294

    Next: Final Manifest Check and Readiness

    Up next

    Up nextFinal Manifest Check and Readiness

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error