How youssef-fd/axi-based-dma-design works
This repository implements a memory-to-memory AXI4 DMA engine. The documented workflow is: a host supplies transfer parameters and starts the engine; the controller triggers read and write masters; the read master fetches source bursts into an internal FIFO, and the write master drains it to the destination. The README also describes AXI slave behavior and error propagation, but the available material contains no source excerpts, so those components are shown without speculative connections. Relationships below are limited to those explicitly documented.
Main entry points: dma_engine.sv DMA engine · axi_read-master.sv AXI read master · axi_write_master.sv AXI write master · dma_controller.sv DMA controller
Components 11
Transfer control
- DMA controller
hdl/DMA_Controller/dma_controller.sv
DMA datapath
- DMA engine
hdl/dma_engine.sv - Transfer FIFO
hdl/dma_engine.sv
AXI interfaces
- AXI read master
hdl/AXI_Read_MASTER/axi_read-master.sv - AXI write master
hdl/AXI_Write_MASTER/axi_write_master.sv - Read FIFO
hdl/AXI_Read_MASTER/FIFO.sv - Write FIFO
hdl/AXI_Write_MASTER/FIFO.sv - AXI RAM slave
hdl/axi_RAM_slave.sv
Other components
- Host processor
- Source memory space
- Destination memory space
Connections 11
- Host processor → DMA engine: configures and starts
README.md - DMA engine → DMA controller: integrates
README.md - DMA engine → AXI read master: integrates
README.md - DMA engine → AXI write master: integrates
README.md - DMA engine → Transfer FIFO: integrates
README.md - DMA controller → AXI read master: triggers read
README.md - DMA controller → AXI write master: triggers write
README.md - AXI read master → Transfer FIFO: pushes data
README.md - Transfer FIFO → AXI write master: supplies data
README.md - AXI read master → Source memory space: reads bursts
README.md - AXI write master → Destination memory space: writes bursts
README.md