This tutorial covers two use cases as follows:
Use Case 1: Changes in the hardware design after VMA import not affecting the PLIO interface. In this use case, we are considering no hardware design change in Vivado affects the AIE-PL boundary or AIE/PL kernels. So, developer can do the hardware development in Vivado and generate the fixed xsa.
Use Case 2: Changes in the hardware design after VMA import affects the PLIO interface or changes in vitis sw files. This use case will be helpful to update the Vivado design for following Vitis development:
Changes are required in AIE-PL (PLIO) boundary.
Changes done in HLS kernel.
Changes done in connection and need modifications in Vitis configuration file.
To incorporate Vitis changes in Vivado, following steps are required:
Remove the imported VMA from vivado.
Re export the extensible xsa from vivado (if there are any changes done in vivado after the last extensible xsa export).
Re compile the modified software files with the latest exported extensible xsa.
Re export the VMA with updated software changes.
Import the latest VMA into the design.
Note: Use the make command in the tutorial from the parent folder 03_Vitis_Export_To_Vivado