For each card in the server, you will see an output similar to the example below.
Card [0000:65:00.0]
Card type: u200
Flash type: SPI
Flashable partition running on FPGA:
xilinx_u200_xdma_201830_2,[ID=0x000000005d1211e8],[SC=4.2.0]
Flashable partitions installed in system:
xilinx_u200_xdma_201830_2,[ID=0x000000005d1211e8],[SC=4.2.0]
In this example, the BDF is 0000:65:00.0.
The name of the plaorm and associated ID, along with the SC rmware version, running on
the FPGA are found under Flashable partition running on FPGA while the ones
installed in the system are found under Flashable partitions installed in
system.
In the above output example, the plaorm on the FPGA and system are idencal; the
deployment plaorm is named xilinx_u200_xdma_201830_2, the ID is
0x000000005d1211e8 and the SC version is 4.2.0. In the outputs above, ID is the
mestamp and SC refers to the Satellite Controller.
2. Verify that the deployment plaorm version installed on the FPGA is idencal to that
installed on the system. You can do this by making sure the lines under Flashable
partition running on FPGA and Flashable partitions installed in
system are idencal.
If these versions do not match, see Chapter 7: Troubleshoong.
xbutil validate
The xbutil validate command validates the correct installaon by performing the following
set of tests:
1. Validates the device found.
2. Checks PCIe link status.
3. Runs a verify kernel on the card.
4. Performs the following data bandwidth tests:
a. DMA test - Data transfer between host and card memory through PCIe.
b. Memory test - Data transfer between kernels and card memory.
The validate command has the format:
xbutil validate -d <card_bdf>
Chapter 5: Card Bring-Up and Validation
UG1301 (v1.5) June 3, 2020 www.xilinx.com
Getting Started with Alveo Accelerator Cards 29