Step 3: Programming the Base Platform

All applications compiled by the SDAccel™ compiler for the KCU1500 card are compiled against a specific device. A device is a combination of interfaces and infrastructure components on the card, which are required for proper execution of the user program. The base device program or firmware is different for all devices. This program must be loaded onto the FPGA before the user applicationis loaded. To program the firmware program:

  1. Connect the KCU1500 card to the programming computer with an installation of Vivado® Design Suite using a USB cable as shown in the following figure.
  2. On the programming computer, start the Vivado® Design Suite, then on the Welcome page, select Open Hardware Manager.
  3. Select Open a New Hardware Target.
  4. Click Next.
  5. Select Local server in the Connect to field and click Next.

  6. In the Open New Hardware Target window, select xilinx_tcf and click Next.

  7. In the Open Hardware Target Summary window, click Finish.

  8. Right-click your FPGA (xcku115_0) and select Add Configuration Memory Device.
  9. Select mt25qu512-spi-x1_x2_x4_x8 as the configuration memory.
  10. Click OK to program the configuration memory.

  11. In the Programming Configuration Memory Device window, go to the Configuration File entry box, browse to and select the MCS file (xilinx_kcu1500_dynamic_5_0_primary.mcs) that you copied to the programming computer in Step 1.
  12. Go to the Configuration File 2 entry box, browse to, and select the second MCS file (xilinx_kcu1500_dynamic_5_0_secondary.mcs).
  13. Verify all other settings as shown in the Program Configuration Memory Device window. Click OK to start programming the configuration memory.

  14. After the memory has been configured, right-click the FPGA (xcku115_0) and select Boot from Configuration Memory Device

  15. The Tcl console displays Done pin status: HIGH after the FPGA device is booted successfully.

  16. Reboot the host computer.
Note: Programming of the device firmware is required only once per device support archive (dsa). All applications targeting the same dsa can share a single programming instance of the card firmware.