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
      • Map Table, Overlap and Alignment Check
      • Decode, Response Codes and the Alias
      • Link Table, Bandwidth and the Bottleneck
    • Stage 2: Clocks, Resets, Power
    • Stage 3: Interrupts and Boot
    • Stage 4: Verification and Signoff
Loading lesson

←Capstone: Integrate NanoSoC
  1. Topics
  2. SoC Design
  3. Capstone: Integrate NanoSoC
  4. Stage 1: Memory Map and Interconnect

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

Stage 1: Memory Map and Interconnect

Build the map table, run the overlap and alignment checker, derive the decode, check response codes and size the links.

  • 3topics
  • 3lessons

Stage 1 produces the map table and the link budget: proof that no two windows overlap, every base is aligned to its size, each hole answers with the right error code, and the link table names the bottleneck of the DMA stream and of CPU register traffic. Planted bugs 1 and 4 live here, plus the same-bank performance trap that halves the stream with no error flag.

Lesson

After it you can...

Map Table, Overlap and Alignment Check

Build the table and catch the overlapping decode.

Decode, Response Codes and the Alias

Derive the decode, name every hole's answer, and wire the DMA address correctly.

Link Table, Bandwidth and the Bottleneck

Recompute every link rate and find the bottleneck.

Suggested order: top to bottom. The table first, because the checker needs it; decode second, because the response codes fall out of it; bandwidth last, because the burst arithmetic assumes the map is settled. The APB slot rule addr[15:12] from this stage is quoted by every later stage.

Check yourself A DECERR and a SLVERR both abort the access. Why does the lab insist on distinguishing them?

DECERR means no slave was selected, a map or linker-script bug; SLVERR means a slave refused, a permission or state bug. The debug starts in opposite places.

Expect to draw the map from memory: three windows, seven APB slots, four holes with their codes, the alias rule, and the secure-only rows.

PreviousNext: Map Table, Overlap and Alignment Check

Up next

Up nextMap Table, Overlap and Alignment Check

Sign in to save progress

Practice this lessonPrevious lessonReport an error

See also

  • Capstone Brief
  • Stage 2: Clocks, Resets, Power
  • Stage 3: Interrupts and Boot