This tutorial covers the following two use cases. Both use cases are related to the changes done after the VMA import as there is no change in the flow until the AI Engine (AIE) and PL kernels compilation (same as Vitis Integrated flow).
Modification(s) in the hardware design after the VMA import (second iteration onwards) is in Vivado only. No changes affecting the AIE-PL boundary.
Modification(s) are related to the AIE-PL boundary and Vitis development after the VMA import (second iteration onwards). In this use case, modifications related to Vivado are also supported.
The complete flow (from hardware design creation to export .xclbin) is divided into seven steps as shown in the following figure:
