- Set the desired runtime settings in the xrt.ini file.
As described in xrt.ini File, the file specifies various parameters to control debugging, profiling, and message logging in XRT when running the host application and kernel execution. As described in Enabling Profiling in Your Application this enables the runtime to capture debugging and profile data as your application is running.
The xrt.ini file, as well as any additional files required for running the application, must be included in the output files as explained in Packaging for Embedded Platforms.Tip: Be sure to use the
v++ -goption when compiling your kernel code for emulation mode.
- Launch the QEMU emulation environment by running the launch_sw_emu.sh script or launch_hw_emu.sh script.
launch_sw_emu.sh -forward-port 1440 22
The script is created in the emulation directory during the packaging process, and uses the
launch_emulator.pycommand to setup and launch QEMU. When launching the emulation script you can also specify options for the
launch_emulator.pycommand. Such as the
-forward-portoption to forward the QEMU port to an open port on the local system. This is needed when trying to copy files from QEMU as discussed in Step 5 below. Refer to launch_emulator Utility for details of the command.
Another example would be to specify
launch_hw_emu.sh -enable-debugto configure additional XTERMs to be opened for QEMU and PL processes to observe live transcripts of command execution to aid in debugging the application. This is not enabled by default, but can be useful when needed for debug.
- Mount and configure the QEMU shell with the required settings.
The Xilinx embedded base platforms have
rootfson a separate EXT4 partition on the SD card. After booting Linux, this partition needs to be mounted. If you are running emulation manually, you need to run the following commands from the QEMU shell:
mount /dev/mmcblk0p1 /mnt cd /mnt export LD_LIBRARY_PATH=/mnt:/tmp:$LD_LIBRARY_PATH export XCL_EMULATION_MODE=hw_emu export XILINX_XRT=/usr export XILINX_VITIS=/mntTip: You can set the
XCL_EMULATION_MODEenvironment variable to
sw_emufor software emulation, or
hw_emufor hardware emulation. This configures the host application to run in emulation mode.
- Run the application from within the QEMU shell.
With the runtime initialization (xrt.ini), the
XCL_EMULATION_MODEenvironment set, run the host executable with the command line as required by the host application. For example:
./host.elf kernel.xclbinTip: This command line assumes that the host program is written to take the name of the xclbin file as an argument, as most Vitis examples and tutorials do. However, your application can have the name of the xclbin file hard-coded into the host program, or can require a different approach to running the application.
- After the application run has completed, you might have some files that
were produced by the runtime, such as opencl_summary.csv, opencl_trace.csv, and xrt.run_summary. These files can be found in the /mnt folder inside the QEMU environment. However,
to view these files you must copy them from the QEMU Linux system back to your local
system. The files can be copied using the
scpcommand as follows:
scp -P 1440 root@<host-ip-address>:/mnt/<file> <dest_path>
1440is the QEMU port to connect to.
root@<host-ip-address>is the root login for the PetaLinux running under QEMU on the specified IP address. The default root password is "root".
- /mnt/<file> is the path and file name of the file you want to copy from the QEMU environment.
- <dest_path> specifies the path and file name to copy the file to on the local system.
scp -P 1440 firstname.lastname@example.org:/mnt/xrt.run_summary
- When your application has completed emulation and you have copied any
needed files, click Ctrl + a + x keys to
terminate the QEMU shell and return to the Linux shell. Note: If you have trouble terminating the QEMU environment, you can kill the processes it launches to run the environment. The tool reports the process IDs (pids) at the start of the transcript, or you can specify the
-pid-fileoption to capture the pids when launching emulation.
Recommended: The file size limit on your machine should either be set to unlimited or a higher value (over 16 GB) because embedded HW Emulation can create files with larger file size for memory.
Tip: Set up the command shell or window as described in Setting Up the Vitis Environment prior to running the builds.