DMA Driver Sample Application

Description

The DMA Driver sample application demonstrates DMA-based memory transfers and data validation on the supported boards for this application. Instead of copying large buffers in software, it uses the DMA engine to move data and then verifies that the destination content matches the expected transfer result.

The sample includes multiple transfer demonstrations:

1D transfer: copy a large linear buffer from source to destination.
2D transfer: copy matrix-style data (ROWS x COLS) with row/stride settings.
Linked transfers: execute a descriptor-based transfer chain in sequence.
Software-triggered transfer: trigger each DMA step manually from software.

Feature support by board:

2D transfer is supported on SR110_RDK only.
1D transfer, linked transfers, and software-triggered transfer are supported on all supported boards for this application.

During each run, the app logs channel allocation, transfer start/pause/resume, completion status, and validation results. This makes it easy for end users to confirm that DMA setup and data integrity checks are working as expected.

The latest example structure uses a common application source tree with board-specific hardware setup kept under hw/<BOARD>/. For this app:

Common application sources such as main.c, dma_sample_app.c, and dma_sample_app.h stay in the app root.
Application defconfigs are stored under configs/.
Board and hardware-specific setup is selected from hw/<BOARD>/, for example hw/SR110_RDK/.

The application can also be exported and built as a standalone app repository. In that flow, keep this app in its own directory, point SRSDK_DIR to the SDK root, and build from the app directory itself. For the full application workflow model, see Astra MCU SDK User Guide.

Supported Boards

This application supports:

SR110_RDK
SL2610_RDK

Select the defconfig that matches your target board, and the build system will pick the corresponding board-specific hardware setup from hw/<BOARD>/.

Prerequisites

Choose one setup path:
- CLI: Setup and Install SDK using CLI
- VS Code: Setup and Install SDK using VS Code

Test Case Selection

Before building, choose the testcase defconfig that matches both your target board and the transfer mode you want to validate.

You can:

Select the required defconfig directly from the application’s configs/ directory.
Run make list_defconfigs from the application directory to list all supported defconfigs.

Available defconfigs:

sl2610_rdk_cm52_dma_sample_app_1d_defconfig
sl2610_rdk_cm52_dma_sample_app_all_transfers_defconfig
sl2610_rdk_cm52_dma_sample_app_linked_defconfig
sl2610_rdk_cm52_dma_sample_app_sw_trig_defconfig
sr110_rdk_cm55_dma_sample_app_1d_defconfig
sr110_rdk_cm55_dma_sample_app_2d_defconfig
sr110_rdk_cm55_dma_sample_app_all_transfers_defconfig
sr110_rdk_cm55_dma_sample_app_linked_defconfig
sr110_rdk_cm55_dma_sample_app_sw_trig_defconfig

For this app, the default defconfig is:

SR110_RDK: sr110_rdk_cm55_dma_sample_app_all_transfers_defconfig
SL2610_RDK: sl2610_rdk_cm52_dma_sample_app_all_transfers_defconfig

Building and Flashing the Example using VS Code

Use the VS Code flow described in the respective soc vscode guides and the VS Code Extension guide:

Build (VS Code):

Open Build and Deploy -> Build Configurations.
Select the dma_sample_app project configuration in the Project Configuration dropdown.
Select the required defconfig for the application.
Build with Build (SDK+Project) for the first build, or Build (Project) for rebuilds.

Flash (VS Code):

For SR110:
- Use Image Conversion to generate the flash image.
- Use Image Flashing with SWD/JTAG to flash the firmware image.
For SL2610:
- Use the SL2610 image-generation flow to generate the required sub-image.
- Open Image Flashing (SL2610).
- Select Flash Target as M52 Image.
- In Image Path, browse to and select the generated sub-image file, such as sysmgr.subimg.gz.
- Start the flashing operation to program the image to the target.

Building and Flashing the Example using CLI

Use the CLI flow described in the respective build guide:

Build (CLI):

Build from the application directory itself:

cd <sdk-root>/examples/driver_examples/dma_sample_app
export SRSDK_DIR=<sdk-root>
make <testcase_defconfig> BUILD=SRSDK

For faster rebuilds when only app code changes, reuse the app-local installed SDK package:

cd <sdk-root>/examples/driver_examples/dma_sample_app
export SRSDK_DIR=<sdk-root>
make build

If this app has been exported to its own repository, use the same commands from that exported app directory after setting SRSDK_DIR to the SDK root.

Build outputs (CLI):

Application binary: <app-dir>/out/<target>/release/<target>.elf
App-local SDK package: <app-dir>/install/<BOARD>/<BUILD_TYPE>/

Flash (CLI):

Flash SR110

Activate the SDK venv (required for image generation tools):

# Linux/macOS
source <sdk-root>/.venv/bin/activate
# Windows PowerShell
.\.venv\Scripts\Activate.ps1

Generate the flash image:

cd <sdk-root>/tools/srsdk_image_generator
python srsdk_image_generator.py \
  -B0 \
  -flash_image \
  -sdk_secured \
  -spk "<sdk-root>/tools/srsdk_image_generator/Inputs/spk_rc4_1_0_secure_otpk.bin" \
  -apbl "<sdk-root>/tools/srsdk_image_generator/Inputs/sr100_b0_bootloader_ver_0x012F_ASIC.axf" \
  -m55_image "<sdk-root>/examples/driver_examples/dma_sample_app/out/sr110_cm55_fw/release/sr110_cm55_fw.elf" \
  -flash_type "GD25LE128" \
  -flash_freq "67"

Flash the firmware image:

cd <sdk-root>
python tools/openocd/scripts/flash_xspi_tcl.py \
  --cfg_path tools/openocd/configs/sr110_m55.cfg \
  --image tools/srsdk_image_generator/Output/B0_Flash/B0_flash_full_image_GD25LE128_67Mhz_secured.bin \
  --erase-all

Flash SL2610

Build the SL2610 bootloader image.

cd <sdk-root>
export SRSDK_DIR=<sdk-root>
make <SL2610_Bootloader_defconfig> BOARD=<BOARD>
make astrasdk

Generate the system sub-image.

cd <sdk-root>/examples/driver_examples/dma_sample_app
export SRSDK_DIR=<sdk-root>
make imagegen

Flash/download image to target.

Refer: SL2610 Platform Guide

Running the Application using VS Code Extension

Press RESET on the board after flashing.
For logging output, click SERIAL MONITOR and connect to the DAP logger port on J14.
- To make it easier to identify, ensure only J14 is plugged in (not J13).
- The logger port is not guaranteed to be consistent across OSes. As a starting point:
  - Windows: try the lower-numbered J14 COM port first.
  - Linux/macOS: try the higher-numbered J14 port first.
- If you do not see logs after a reset, switch to the other J14 port.
DMA sample logs appear in the logger window, including transfer progress and validation results.

Expected Logs

SR110

SR100.Logger	warning	1769080093.215686	LOGR	0	M55	00:06:31:469:271	Changing logger interface to LOGGER_IF_UART_1
SR100.Logger	info	1769080093.215686	SYS 	0	M55	00:00:00:000:023	System initialization complete without errors.
SR100.Logger	info	1769080093.215686	SYS 	0	M55	00:00:00:003:583	sr110 SDK version 1.3.0
SR100.Logger	info	1769080093.215686	DMA 	0	M55	00:00:00:006:056	Starting DMA Sample Application...
SR100.Logger	info	1769080093.215686	DMA 	0	M55	00:00:00:009:047	Running All DMA Transfer Tests...
SR100.Logger	info	1769080093.215686	DMA 	0	M55	00:00:00:012:436	Channel 0 allocated successfully.
SR100.Logger	info	1769080093.231331	DMA 	0	M55	00:00:00:015:369	[DMA] Preparing 1D transfer: 65536 elements from 0x33f61140 to 0x33f21140
SR100.Logger	info	1769080093.231331	DMA 	0	M55	00:00:00:020:510	Transfer Paused.
SR100.Logger	info	1769080093.247018	DMA 	0	M55	00:00:00:022:633	Transfer resumed.
SR100.Logger	info	1769080093.247018	DMA 	0	M55	00:00:00:026:665	[DMA] 1D transfer successful: 65536 elements verified
SR100.Logger	info	1769080093.247018	DMA 	0	M55	00:00:00:030:562	Channel 0 allocated successfully.
SR100.Logger	info	1769080093.247018	DMA 	0	M55	00:00:00:033:493	Transfer Paused.
SR100.Logger	info	1769080093.262636	DMA 	0	M55	00:00:00:035:617	Transfer resumed.
SR100.Logger	info	1769080093.262636	DMA 	0	M55	00:00:00:037:789	[DMA] 2D transfer successful: 8x8 elements verified
SR100.Logger	info	1769080093.262636	DMA 	0	M55	00:00:00:043:093	Transfer Paused.
SR100.Logger	info	1769080093.262636	DMA 	0	M55	00:00:00:045:216	Transfer resumed.
SR100.Logger	info	1769080093.262636	DMA 	0	M55	00:00:00:051:115	Linked transfers verified successfully.
SR100.Logger	info	1769080093.262636	DMA 	0	M55	00:00:00:055:082	Channel 0 allocated successfully.
SR100.Logger	info	1769080093.278704	DMA 	0	M55	00:00:00:070:316	Final status = 0x10000
SR100.Logger	info	1769080093.278704	DMA 	0	M55	00:00:00:072:726	Transfer completed. Verifying data...
SR100.Logger	info	1769080093.30992	DMA 	0	M55	00:00:00:077:705	SW-triggered DMA transfer successful!
SR100.Logger	info	1769080093.310964	DMA 	0	M55	00:00:00:080:833	All DMA transfers successful.
SR100.Logger	info	1769080093.31193	DMA 	0	M55	00:00:00:083:578	DMA Sample Application Completed.

SL2610

BL: MCU Init...
Init DDR4 @ 3200
DHL:v0p40 PT:v0p40 ID:0x21010000
USB MOUNTED
0000000000:[0][INF][SYS ]:System initialization complete without errors.
0000000000:[0][INF][SYS ]:sl2610 SDK version 1.3.0
0000000000:[0][INF][DMA ]:Starting DMA Sample Application...
0000000005:[0][INF][DMA ]:Running 1D DMA Transfer Test...
0000000010:[0][INF][DMA ]:Channel 0 allocated successfully.
0000000015:[0][INF][DMA ]:[DMA] Preparing 1D transfer: 64 elements from 0x300020a0 to 0x30001fa0
0000000024:[0][INF][DMA ]:Transfer Paused.
0000000028:[0][INF][DMA ]:Transfer resumed.
0000000032:[0][INF][DMA ]:[DMA] 1D transfer successful: 64 elements verified
0000000039:[0][INF][DMA ]:Running Linked DMA Transfer Test...
0000000044:[0][INF][DMA ]:Transfer Paused.
0000000048:[0][INF][DMA ]:Transfer resumed.
0000000052:[0][INF][DMA ]:Linked transfers verified successfully.
0000000058:[0][INF][DMA ]:Running SW-Triggered DMA Transfer Test...
0000000064:[0][INF][DMA ]:Channel 0 allocated successfully.
0000000069:[0][INF][DMA ]:Final status = 0x10000
0000000074:[0][INF][DMA ]:Transfer completed. Verifying data...
0000000079:[0][INF][DMA ]:SW-triggered DMA transfer successful!
0000000085:[0][INF][DMA ]:DMA Sample Application Completed.