This tutorial targets the Zynq® UltraScale+™ ZCU102 evaluation board. The examples in this tutorial were tested using the ZCU102 Rev 1 board. To use this guide, you need the following hardware items, which are included with the evaluation board:
ZCU102 Rev1 evaluation board
AC power adapter (12 VDC)
USB Type-A to USB Micro cable (for UART communications)
USB micro cable for programming and debugging via USB-Micro JTAG connection
SD-MMC flash card for Linux booting
Ethernet cable to connect target board with host machine
Monitor with DisplayPort (DP) capability and at least 1080P resolution
DP cable to connect the display output from the ZCU102 board to a DP monitor
Vitis Integrated Design Environment and Vivado Design Suite¶
Ensure that you have the Vitis™ 2022.1 unified software development platform installed. The Vitis software platform comes with all the hardware and software as a package. If you install the Vitis IDE, you will automatically get both the Vivado Design Suite and the Vitis IDE. You do not have to make any extra selections in the installer.
Visit this web page to download the required Vitis tool installer.
Make sure your operating system is supported by the Vitis embedded software development flow. For more information on installing the Vitis unified software platform, refer to the Installation section of the Vitis embedded software development flow documentation (UG1400).
Install the PetaLinux tools to run through the Linux portion of this tutorial. PetaLinux tools run under the Linux host system. The supported operation systems can be checked from the PetaLinux Tools Documentation: Reference Guide (UG1144).
This can use either a dedicated Linux host system or a virtual machine running one of these Linux operating systems on your Windows development platform.
When you install PetaLinux tools on your system of choice, you must do the following:
Tutorial Design Files¶
The reference design files for this tutorial are provided in the ref_files directory, organized with design number or chapter name. Chapters that need to use reference files will point to the specific
If the examples are GUI based, the
ref_filesdirectory provides the source files for the examples.
If the examples can be run in script mode, the
ref_filesdirectory contains the Makefile to help you run through the flow easily. Run
makein this directory to run through the implementation flow.