Multi Channel DMA Intel® FPGA IP for PCI Express* Design Example User Guide

Download PDF
ID 683517
Date 6/09/2025
Public
Document Table of Contents
Document Table of Contents x
1. Introduction 2. Design Example Detailed Description 3. Design Example Quick Start Guide 4. Multi Channel DMA Intel FPGA IP for PCI Express Design Example User Guide Archives 5. Revision History for the Multi Channel DMA Intel FPGA IP for PCI Express Design Example User Guide
1. Introduction x
1.1. Terms and Acronyms 1.2. MCDMA IP Modes
2. Design Example Detailed Description x
2.1. Design Example Overview 2.2. PIO using MCDMA Bypass Mode 2.3. Avalon-ST Packet Generate/Check 2.4. Avalon-ST Device-side Packet Loopback 2.5. Avalon-MM DMA 2.6. BAM_BAS Traffic Generator and Checker 2.7. External Descriptor Controller
2.1. Design Example Overview x
2.1.1. H-Tile MCDMA IP - Design Examples for Endpoint 2.1.2. P-Tile MCDMA IP - Design Examples for Endpoint 2.1.3. F-Tile MCDMA IP - Design Examples for Endpoint 2.1.4. R-Tile MCDMA IP - Design Examples for Endpoint 2.1.5. Design Example BAR Mappings 2.1.6. Design Example Driver Support
2.2. PIO using MCDMA Bypass Mode x
2.2.1. Avalon-ST PIO using MCDMA Bypass Mode 2.2.2. Avalon-MM PIO using MCDMA Bypass Mode
2.2.1. Avalon-ST PIO using MCDMA Bypass Mode x
2.2.1.1. Single-Port Avalon-ST PIO using MCDMA Bypass Mode
2.2.2. Avalon-MM PIO using MCDMA Bypass Mode x
2.2.2.1. Simulation Results 2.2.2.2. Hardware Test Results
2.3. Avalon-ST Packet Generate/Check x
2.3.1. Single-Port Avalon-ST Packet Generate/Check
2.3.1. Single-Port Avalon-ST Packet Generate/Check x
2.3.1.1. Simulation Waveforms 2.3.1.2. Simulation Log 2.3.1.3. Hardware Test Result
2.4. Avalon-ST Device-side Packet Loopback x
2.4.1. Simulation Results 2.4.2. Hardware Test Results
2.5. Avalon-MM DMA x
2.5.1. Simulation Results 2.5.2. Hardware Test Results
2.6. BAM_BAS Traffic Generator and Checker x
2.6.1. BAM_BAS Traffic Generator and Checker Example Design Register Map
2.7. External Descriptor Controller x
2.7.1. Registers 2.7.2. Hardware Test Results
2.7.1. Registers x
2.7.1.1. GCSR Registers (Base address 64’h00000) 2.7.1.2. QCSR Registers(Base address 64’h10000)
3. Design Example Quick Start Guide x
3.1. Design Example Directory Structure 3.2. Generating the Example Design using Quartus® Prime 3.3. Simulating the Design Example 3.4. Compiling the Example Design in Quartus® Prime 3.5. Running the Design Example Application on a Hardware Setup
3.2. Generating the Example Design using Quartus® Prime x
3.2.1. Procedure
3.3. Simulating the Design Example x
3.3.1. Testbench Overview 3.3.2. Supported Simulators 3.3.3. Example Testbench Flow for DMA Test with Avalon-ST Packet Generate/Check Design Example 3.3.4. Run the Simulation Script 3.3.5. Steps to Run the Simulation 3.3.6. View the Results
3.3.5. Steps to Run the Simulation x
3.3.5.1. Steps to Run the Simulation : QuestaSim* / Questa* Intel® FPGA Edition 3.3.5.2. Steps to Run the Simulation : VCS* / VCS* MX 3.3.5.3. Steps to Run the Simulation : Xcelium*
3.5. Running the Design Example Application on a Hardware Setup x
3.5.1. Hardware Requirements 3.5.2. Software Requirements 3.5.3. Set Up the Hardware and Program the FPGA 3.5.4. Configuration Changes from BIOS 3.5.5. Host Operating System Check for Ubuntu v22.04 3.5.6. Installing the Required Kernel Version for Ubuntu v24.04 3.5.7. Set the Boot Parameters 3.5.8. MCDMA Custom Driver 3.5.9. MCDMA DPDK Poll Mode Driver 3.5.10. MCDMA Kernel Mode Network Device Driver
3.5.8. MCDMA Custom Driver x
3.5.8.1. Prerequisites 3.5.8.2. PIO Test 3.5.8.3. DMA Test 3.5.8.4. BAM Test 3.5.8.5. BAS Test
3.5.8.1. Prerequisites x
3.5.8.1.1. Install the Linux Kernel Driver 3.5.8.1.2. Enable Virtual Function 3.5.8.1.3. Build and Install the User Space Library 3.5.8.1.4. Build the Reference Application
3.5.8.2. PIO Test x
3.5.8.2.1. Custom PIO Read Write Test
3.5.8.3. DMA Test x
3.5.8.3.1. Avalon-MM DMA (AVMM DMA) 3.5.8.3.2. Avalon-ST Device-side Packet Loopback (Device-side Packet Loopback) 3.5.8.3.3. Avalon-ST Packet Generate/Check (Packet Generate/Check) 3.5.8.3.4. External Descriptor Controller
3.5.8.3.2. Avalon-ST Device-side Packet Loopback (Device-side Packet Loopback) x
3.5.8.3.2.1. DMA Test Beyond 256 Channels
3.5.8.3.3. Avalon-ST Packet Generate/Check (Packet Generate/Check) x
3.5.8.3.3.1. DMA Test Beyond 256 Channels
3.5.9. MCDMA DPDK Poll Mode Driver x
3.5.9.1. Prerequisites 3.5.9.2. PIO Test 3.5.9.3. DMA Test 3.5.9.4. BAM Test 3.5.9.5. BAS Test
3.5.9.1. Prerequisites x
3.5.9.1.1. Install the PMD Driver 3.5.9.1.2. Bind the Device 3.5.9.1.3. Enable Virtual Function
3.5.9.3. DMA Test x
3.5.9.3.1. Avalon-MM DMA (AVMM DMA) 3.5.9.3.2. Avalon-ST Packet Generate/Check (Packet Generate/Check) 3.5.9.3.3. Avalon-ST Device-side Packet Loopback (Device-side Packet Loopback)
3.5.9.3.2. Avalon-ST Packet Generate/Check (Packet Generate/Check) x
3.5.9.3.2.1. DMA Test Beyond 256 Channels
3.5.9.3.3. Avalon-ST Device-side Packet Loopback (Device-side Packet Loopback) x
3.5.9.3.3.1. DMA Test Beyond 256 Channels
3.5.10. MCDMA Kernel Mode Network Device Driver x
3.5.10.1. Prerequisites 3.5.10.2. PIO Test 3.5.10.3. Ping Test
3.5.10.1. Prerequisites x
3.5.10.1.1. Build and Install Netdev Driver 3.5.10.1.2. Enable Virtual Function
1. Introduction
2. Design Example Detailed Description
3. Design Example Quick Start Guide
4. Multi Channel DMA Intel FPGA IP for PCI Express Design Example User Guide Archives
5. Revision History for the Multi Channel DMA Intel FPGA IP for PCI Express Design Example User Guide

3.5.8.4. BAM Test

  1. If the BAM support is enabled on hardware, enable the following flag in p0_software/user/common/mk/common.mk for 256-bit or 128-bit read or write operations:

    __cflags += -DIFC_PIO_256 → 256b read/write operations on the PIO BAR.

    __cflags += -DIFC_PIO_128 → 128b read/write operations on the PIO BAR.

    Note: For PIO using MQDMA Bypass with BAM/BAS user mode, you are required to undefine the following software flag:

    #undef IFC_QDMA_INTF_ST(p0_software/user/common/ include/mcdma_ip_params.h)

  2. Complete the instructions outlined in Prerequisites to install the Linux Kernel driver, and build the driver application for testing.
  3. If the data width has changed from the default 64 bits due to the flag settings mentioned above, rebuild the application for the new setting to take effect by following the instructions in Build the Reference Application.

If only the 64-bit BAM PIO is enabled:

root@bapveac025t:perfq_app# sudo ./perfq_app -b 0000:98:00.0 -o --bam_perf
PIO 64 Write Performance Test ...
Total Bandwidth:                0.05GBPS
Pass
root@bapveac025t:perfq_app#

If 128-bit and 256-bit BAM PIO are also enabled:

root@bapveac025t:perfq_app# sudo ./perfq_app -b 0000:98:00.0 -o --bam_perf
PIO 128 Write Performance Test ...
Total Bandwidth:                0.07GBPS
Pass
root@bapveac025t:perfq_app#

root@bapveac025t:perfq_app# sudo ./perfq_app -b 0000:98:00.0 -o --bam_perf
PIO 256 Write Performance Test ...
Total Bandwidth:                0.17GBPS
Pass
  • By default, BAR 2 is used for BAM. Pass the BAR number parameter as shown below:

    --bar=2 for BAM

  • For example:

    ./perfq_app -b 0000:01:00.0 --bam_perf -o --bar=2

  • The Performance mode of BAM tries to send the data for 10 seconds and calculates the bandwidth.
  • The PIO 256b test may display a Fail because only a 2k memory is enabled in the device and the PIO test is trying to access a memory greater than 2k.
Note: Refer to BAR Mappings for BAR mapping information.
Level Two Title