MCAP VSEC - 3.3 English

Versal ACAP CPM DMA and Bridge Mode for PCI Express Product Guide (PG347)

Document ID
Release Date
3.3 English
Important: The MCAP VSEC can only natively address the lower 4 GB of the address map, as it can only issue 32-bit address transactions. To reach the SBI buffer address, the NOC NMU address remapping capability must be employed, see the following recommended command as an example to employ remapping from 32 bit address space to 48 bit address space for the SBI buffer.
set_property CONFIG.REMAPS {M00_AXI {{0xF122_0000 0x1_0122_0000 64K} {0xF210_0000 0x1_0210_0000 64K}}} [get_bd_intf_pins /axi_noc_0/S00_AXI]
  1. Navigate to driver root directory
    1. $> cd <parent-path>/dma_ip_drivers/XVSEC/linux-kernel
  2. Compile driver and user space applications
    1. $> make all
  3. Copy driver and application executables to standard destinations
    1. $> make install
  4. Install the driver into the kernel
    1. $> modprobe xvsec
  5. Perform the transfer to SBI; must set transfer mode to fixed address, issue 128-bit transactions, and target the remapped address range
    1. $> xvsecctl -b 0x01 -F 0x0 -c 1 -p mode 128b type fixed 0xF2100000 <.pdi file> tr_mode fast [sbi 0xF1220000]
    Note: Depending on the way the previous bitstreams are loaded to the device through the SBI, it might be required to set the SBI to accept data from the AXI slave interface. The SBI control and status registers are located at base address 0x101220000; examine the SBI_CTRL register in the block. The xvsecctl application can automatically set the register by appending the sbi <reg block target base address> argument as shown above. To use this functionality, it is assumed that the PMC slave target (the slave boot control and status register block) is assigned in the CPM address map and NOC NMU address remapping is employed to reach the SBI buffer, as demonstrated in the important note above.