RTL Studio Open IDE

3.6 · RV SYS CLASS

IRQ DMA top

Integrate a complete SoC platform with DMA and interrupt support by configuring AXI interface parameters and verifying system-level behavior.

Video coming soon. This lesson page stays at the same URL when the lecture publishes.

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.

ComponentRole
rv32i_core_busRISC-V processor core generating memory and I/O requests.
multi_slave_interconnectRoutes CPU requests to the correct peripheral based on address.
periph_subsystemContains GPIO, timer, UART, and IRQ controller logic.
dma_engine_topHandles direct memory access without CPU intervention.
sysctrl_blockManages system control signals and boot configuration.

Practice

  1. Open RtlStudio and select this chapter from the Examples or Lecture list.
  2. Confirm that student/rtl/design.sv and student/tb/tb_top.sv appear in the Explore tree.
  3. Open student/rtl/design.sv in the editor.
  4. Locate the axi_if instance declarations for cpu_bus, s_gpio, s_timer, s_uart, and s_irq.
  5. Replace all __TODO__[0] placeholders in the ADDR_WIDTH parameter with 32.
  6. Save student/rtl/design.sv.
  7. Open the Simulation panel in the sidebar.
  8. Select student/tb/tb_top.sv as 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

  1. Open the system lesson in the IDE. The RV32I core and the mini-SoC fabric simulate together.
  2. Run Verilator and trace the program through MMIO: address, load/store data, and the peripheral response.
  3. Interrupts and DMA belong on the waveform next to the instruction stream, not only in a pass/fail line.
  4. 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.