Versal ACAP: Tutorial https://github.com/Xilinx/Vitis-Tutorials/blob/2024.1/AI_Engine_Development/AIE/Feature_Tutorials/01-aie_a_to_z giving ERROR:[VPL-60-773] at step 3 when building the link - binary container.

[Fer6Flores]

Hi, I am following the tutorial of AIEs 01-aie_a_to_z: https://github.com/Xilinx/Vitis-Tutorials/blob/2024.1/AI_Engine_Development/AIE/Feature_Tutorials/01-aie_a_to_z . I have done steps 1 and 2 for a TE0950 board instead of VCK190 (But it doesn't matter I think). Step 3 is giving me the error: "[ERROR] ERROR: [VPL 60-773] In '/home/ffloresg/Documents/test_te0950/vitis_te0950_workspace/simple_aie_application_system_project/build/hw_emu/hw_link/binary_container_1/binary_container_1/vivado/vpl/runme.log', caught Tcl error: ERROR: [Common 17-69] Command failed: File '/home/ffloresg/Documents/test_te0950/vitis_te0950_workspace/simple_aie_application_system_project/build/hw_emu/hw_link/binary_container_1/binary_container_1/vivado/vpl/prj/custom_pfm_te0950_2.srcs/utils_1/imports/synth_1/ext_platform_part_wrapper.dcp' does not exist" when building the binary container. All the steps have been done properly and no error has shown until this point.

As far as I have seen, the problem is the "custom_pfm_te0950_2" in the path. This folder name is the project name of the vivado project I used in step 1. Vitis is supossing that this name should be prj and creating paths with prj/ instead of that in the system project, but the created .xsa in step 1 uses this string "custom_pfm_te0950_2" for pathing.

So, I don't know how to change the path in one of the two sides of the problem, I think that should be matched automatically by the tools but it is not being done. Any help?

I am using Vivado and Vitis 2023.2 and following the same version of the tutorial, under Ubuntu 22.04. Attached you can find a the runme.log under the path /home/ffloresg/Documents/test_te0950/vitis_te0950_workspace/simple_aie_application_system_project/build/hw_emu/hw_link/binary_container_1/binary_container_1/viva

runme.log

[xflorentw]

This was answered through the forums: https://adaptivesupport.amd.com/s/feed/0D5KZ00000mTTym0AG