Important: You should import your command-line project
into the Vitis unified IDE as described in Working with User-Managed Flows, and debug it as described in Debugging the System Project and AI Engine Components.
The following describes the steps required to run the debug flow for software emulation from the command line:
- Set up the command shell or window as described in Setting Up the Vitis Environment prior to running the tools.
- Compile and Link the host code and System project for debugging by
adding the
-goption to theg++command line as described in Building and Running the System. - Launch GDB to debug the application. There are currently two flows
supporting debug during software emulation:
- Debugging PL or AI Engine kernels using the
kernel-dbgoption as explained in Software Emulation Debug for Embedded Processors, or Software Emulation Debug for Alveo Accelerators. This is a simple flow, but only enables debugging of the kernels in the .xclbin, and not the host application. - Debugging the host application and PL kernels using three
command terminals and
xrt_serveras described in Launching Host and Kernel Debug. This is a more complex flow, but supports concurrent debug of both the host and kernels.
- Debugging PL or AI Engine kernels using the