Creating a Custom Kria App - Part 2

RE: Creating a Custom Kria App - Part 2

juanyi — Tue, 22 Feb 2022 05:16:05 GMT

Seeking help. Following the advice to source all the petalinux & xilinx vivao (or vitis) setting, i managed to start the build, but after long hours of running (>12hrs), it come to this error:

[Sun Feb 20 17:44:01 2022] Waiting for synth_1 to finish...

/home/user/Desktop/Xilinx/Vivado/2021.1/bin/loader: line 312: 4616 killed "$RDI_PROG" "$@"

Makefile:29: recipe for target 'project/kv260_ispMipiRx_vcu_DP.xsa' failed

make[2]: *** [project/kv260_ispMipiRx_vcu_DP.xsa] Error 137

make[2]: Leaving directory 'home/user/Desktop/CustomApp/kv260-vitis/platforms/vivado/kv260_ispMipiRx_vcu_DP'

Makefile:42: recipe for target 'vivado/kv260_ispMipiRx_vcu_DP/project/kv260_ispMipiRx_vcu_DP.xsa' failed

make[1]: *** [vivado/kv260_ispMipiRx_vcu_DP/project/kv260_ispMipiRx_vcu_DP.xsa] Error 2

make[1]: Leaving directory 'home/user/Desktop/CustomApp/kv260-vitis/platforms'

Makefile:78: recipe for target '/home/user/Desktop/CustomApp/kv260-vitis/platforms/xilinx_kv260_ispMipiRx_vcu_DP_202110_1/kv260_ispMipiRx_vcu_DP.xpfm' failed

make: *** [/home/user/Desktop/CustomApp/kv260-vitis/platforms/xilinx_kv260_ispMipiRx_vcu_DP_202110_1/kv260_ispMipiRx_vcu_DP.xpfm] Error 2

I can't check the runme.log to see what went wrong because my VM become freeze after running this step. Hoping someone can point me how to troubleshoot this. Thanks.

RE: Creating a Custom Kria App - Part 2

Jan Cumps — Mon, 24 Jan 2022 13:11:36 GMT

... you should also review (and install) this patch: y2k22.

Since January 1st, all known Vitis HLS versions fail to generate the final IP unless you either:

temporarily set the clock back to somewhere in 2021 before invoking Vitis HLS, or
apply the patch

RE: Creating a Custom Kria App - Part 2

schneisw — Thu, 20 Jan 2022 13:45:14 GMT

Tip:

If you are getting some errors after running make, you might not have sourced the settings scripts for both Vivado and Vitis. I noticed this after doing neither, and then only Vivado, which incidentally gave me a successful return on “which vitis” resulting in my not sourcing the Vitis script until later.