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 NanoSoC14
    • Capstone Brief
    • Stage 1: Memory Map and Interconnect
    • Stage 2: Clocks, Resets, Power
    • Stage 3: Interrupts and Boot
      • Interrupt Map and Latency Budget
      • DMA Programming Sequence and Contract Traps
      • Boot Flow and Secure Partition
    • Stage 4: Verification and Signoff
Loading lesson

←Capstone: Integrate NanoSoC
  1. Topics
  2. SoC Design
  3. Capstone: Integrate NanoSoC
  4. Stage 3: Interrupts and Boot

Part 14 of 14Part 14 of 14/Capstone: Integrate NanoSoCAll levels

Stage 3: Interrupts and Boot

Interrupt map and latency budget, DMA programming sequence and its contract traps, the boot flow with times and the secure partition.

  • 3topics
  • 3lessons

Stage 3 produces the event and start-up record: the 8-line interrupt map with its 135.4 to 182.3 ns budget, the DMA driver sequence that survives every contract trap, the sixteen-step boot flow totalling 12.581 ms, and the security attribute of both masters, with the one known hole in it. Planted bugs 3, 7, 8 and 9 live here: a mis-wired interrupt, a secure attribute, a length mismatch and three contract traps.

Lesson

After it you can...

Interrupt Map and Latency Budget

Wire each source to its line and bound its latency.

DMA Programming Sequence and Contract Traps

Programme a job that agrees on lengths, keys and status.

Boot Flow and Secure Partition

Walk the boot timeline and partition secure from non-secure.

Suggested order: top to bottom. Interrupts first, because the DMA sequence ends in one; DMA second, because boot runs a self-test job; boot last, because it consumes both. Every input here is an active-high level held until cleared; anything shorter than 2 clk_per (83.3 ns) can be missed.

Check yourself PENDING equals RAW and ENABLE with no storage. What does that imply for a pulse source?

The controller remembers nothing, so a pulse shorter than the synchroniser window vanishes; sources must hold their level until software clears it.

Expect to bound an interrupt live: two syncs plus the controller register, best and worst with the alignment term, in nanoseconds and in CPU cycles.

PreviousNext: Interrupt Map and Latency Budget

Up next

Up nextInterrupt Map and Latency Budget

Sign in to save progress

Practice this lessonPrevious lessonReport an error

See also

  • Capstone Brief
  • Stage 1: Memory Map and Interconnect
  • Stage 2: Clocks, Resets, Power