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
      • Interrupt Map and Latency Budget
      • DMA Programming Sequence and Driver Trace
      • Boot Flow and Secure Partition
    • Stage 4: Verification and Signoff
    • Solutions
Loading lesson

←Stage 3: Interrupts and Boot
  1. Topics
  2. SoC Design
  3. Capstone: Integrate NanoSoC
  4. Stage 3: Interrupts and Boot
  5. Interrupt Map and Latency Budget
On this page

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

    Interrupt Map and Latency Budget

    Produce a per-source interrupt test log and a latency budget.

    The observation to investigate

    For symptom 3, compare source, controller and CPU observations. Derive the expected map independently of the implementation.

    Required behaviour

    Every source has a distinct input; priority follows input number; the CPU receives one level.
    Capstone interrupt requirements for six active sources

    What to notice. Every source has a distinct input; priority follows input number; the CPU receives one level.

    Check yourself DMA and UART are enabled and pending: which source should TOP select?

    DMA input 1, which outranks UART input 3.

    Your investigation

    Force one source at a time and record RAW, ENABLE, PENDING and TOP against an independent expected map. Compute the latency through both synchronisers and the output register. Find and inject a fault reproducing symptom 3 and show which observation rejects it.

    Inputs to start from

    • The interrupt table in The NanoSoC Tour: inputs 0 to 7, with 6 and 7 reserved.

    • The controller registers RAW, ENABLE, PENDING and TOP, and the rule that the lowest input number wins.

    • Symptom 3 in the symptom table, and the delays through the two synchronisers and the output register.

    Deliverable and pass criterion

    Deliverable. An expected map (source to input number) with a per-source test log of RAW, ENABLE, PENDING and TOP, and a best-case and worst-case latency budget.

    Pass criterion. Forcing each source sets exactly its expected RAW bit and no other, TOP follows priority when two sources are pending, and the latency equals the sum of the stage delays you derived.

    Evidence to hand in

    • The expected map and the six test-log rows.

    • For symptom 3, the RAW bits you read against the ones you expected.

    • The latency table with each stage's delay in nanoseconds.

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

    Related topics

    • Next: DMA Programming Sequence and Driver Trace

    • NanoSoC reference tour

    Previous

    274 / 294

    Next: DMA Programming Sequence and Driver Trace

    Up next

    Up nextDMA Programming Sequence and Driver Trace

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • Boot Flow and Secure Partition