What you practice
IRQ DMA top (3.6). Integrate a complete SoC platform with DMA and interrupt support by configuring AXI interface parameters and verifying system-level behavior. It is in IRQ + DMA subsystem top — Part 3 · Interrupts & DMA of the RISC-V on SoC & System Masterclass.
The core and the mini-SoC simulate as one workspace in the IDE. Follow MMIO, interrupts, and the program on the Verilator waveform, not only a pass line.
What you will learn
You will integrate a complete SoC platform that combines a RISC-V core, DMA engine, and interrupt controller. This lesson demonstrates how to wire the AXI interconnect to support both memory-mapped peripherals and direct memory access operations. You will verify that the system correctly handles a timer interrupt while the DMA engine transfers data.
Learning objectives
- Complete the instance port connections for the AXI interface parameters in the top-level design.
- Understand how the multi-slave interconnect routes CPU requests to various peripherals.
- Verify the system behavior when a DMA transfer completes and triggers an interrupt.
- Analyze the simulation log to confirm correct GPIO state and program execution.
Theory
This lesson focuses on the top-level integration of a System-on-Chip (SoC). The design uses a RISC-V core connected to a multi-slave AXI interconnect. The interconnect routes requests to GPIO, timer, UART, IRQ, system control, and DMA peripherals. The DMA engine operates independently of the CPU to move data between memory and peripherals. When the DMA transfer completes, it asserts an interrupt line to the CPU. The CPU handles the interrupt, executes the interrupt service routine, and eventually halts. The AXI interface parameters must match across all instances to ensure correct address and data width handling.
| Component | Role |
|---|---|
rv32i_core_bus | RISC-V processor core generating memory and I/O requests. |
multi_slave_interconnect | Routes CPU requests to the correct peripheral based on address. |
periph_subsystem | Contains GPIO, timer, UART, and IRQ controller logic. |
dma_engine_top | Handles direct memory access without CPU intervention. |
sysctrl_block | Manages system control signals and boot configuration. |
Practice
- Open RtlStudio and select this chapter from the Examples or Lecture list.
- Confirm that
student/rtl/design.svandstudent/tb/tb_top.svappear in the Explore tree. - Open
student/rtl/design.svin the editor. - Locate the
axi_ifinstance declarations forcpu_bus,s_gpio,s_timer,s_uart, ands_irq. - Replace all
__TODO__[0]placeholders in theADDR_WIDTHparameter with32. - Save
student/rtl/design.sv. - Open the Simulation panel in the sidebar.
- Select
student/tb/tb_top.svas the testbench and click Run.
Summary
You integrated the DMA engine and interrupt controller into the SoC platform by configuring their AXI interface parameters. This exercise demonstrated how the RISC-V core offloads data movement to the DMA while handling asynchronous events via interrupts. Successfully running the simulation confirmed that the system correctly manages both mechanisms simultaneously.
© 2026 RtlStudio. Licensed under CC BY-NC-ND 4.0. Commercial use and modifications by third parties are not permitted.
Run it in the Verilog IDE
- Open the system lesson in the IDE. The RV32I core and the mini-SoC fabric simulate together.
- Run Verilator and trace the program through MMIO: address, load/store data, and the peripheral response.
- Interrupts and DMA belong on the waveform next to the instruction stream, not only in a pass/fail line.
- Edit the integration RTL, resimulate, and run Yosys on the structural block when you want a netlist.
The lesson is done when the simulation matches IRQ DMA top. Change the source, run the Verilog simulator again, and read the waveform without leaving the IDE. Simulation guide · Yosys guide.