# Library Incompatibility: PYNQ Composable Pipeline on KV260 **URL:** \ **Category:** Support\ **Created:** [February 17, 2023, 1:40pm UTC](https://discuss.pynq.io/t/library-incompatibility-pynq-composable-pipeline-on-kv260/5240 "2023-02-17T13:40:51Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Eoin\_Moore](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/eoin_moore/32/4273_2.png) [@Eoin\_Moore](https://discuss.pynq.io/u/Eoin_Moore)\ **Post date:** [February 17, 2023, 1:40pm UTC](https://discuss.pynq.io/t/library-incompatibility-pynq-composable-pipeline-on-kv260/5240/1 "2023-02-17T13:40:51Z")
Hi, I’ve been trying to follow the PYNQ Composable Pipeline instructions to build a bitfile for the Kria KV260 Vision AI Starter Kit, however I’m running into library incompatibility issues with Vitis\_Libraries. PYNQ Version - V3.0 Board Name - Kria KV260 Vision AI Starter Kit Tools: 1. PYNQ Composable Pipeline V1.0.0 2. Vitis Libraries v2020.2\_update1 3. Vivado 2022.2 4. Vitis HLS 2022.2 _To recreate the issue_ I cloned the PYNQ Composable Overlay from [https://github.com/Xilinx/PYNQ\_Composable\_Pipeline](https://github.com/Xilinx/PYNQ_Composable_Pipeline) and then cloned the Vitis\_Libraries repo from [https://github.com/mariodruiz/Vitis\_Libraries/tree/7bf6c52c3840e617f9c522e166f5c18b75afa0e9](https://github.com/mariodruiz/Vitis_Libraries/tree/7bf6c52c3840e617f9c522e166f5c18b75afa0e9) inside the PYNQ\_Composable\_Pipeline directory to fill out the empty Vitis\_Libraries directory given by the PYNQ\_Composable\_Pipeline repo. I navigated to boards/KV260 and ran `make`. The Makefile runs for a few seconds and then terminates with the errors shown below… ```auto ERROR: [HLS 207-2976] no template named 'ap_axiu' in namespace 'xf::cv'; did you mean simply 'ap_axiu'? (../../../../src/dilate/dilate.cpp:20:9) INFO: [HLS 207-4436] 'ap_axiu' declared here (/home/eoin/xilinx/Vitis_HLS/2022.2/common/technology/autopilot/ap_axi_sdata.h:95:1) INFO: [HLS 200-111] Finished Command csynth_design CPU user time: 1.16 seconds. CPU system time: 0.25 seconds. Elapsed time: 1.53 seconds; current allocated memory: 0.723 MB. while executing "source script_hls.tcl" ("uplevel" body line 1) invoked from within "uplevel \#0 [list source $arg] " INFO: [HLS 200-112] Total CPU user time: 3.47 seconds. Total CPU system time: 0.6 seconds. Total elapsed time: 14 seconds; peak allocated memory: 313.852 MB. INFO: [Common 17-206] Exiting vitis_hls at Fri Feb 17 12:58:33 2023... make[1]: *** [Makefile:26: dilate.vhlsprj] Error 1 make[1]: *** Waiting for unfinished jobs.... ERROR: [HLS 207-2976] no template named 'ap_axiu' in namespace 'xf::cv'; did you mean simply 'ap_axiu'? (../../../../src/duplicate/duplicate.cpp:18:9) INFO: [HLS 207-4436] 'ap_axiu' declared here (/home/eoin/xilinx/Vitis_HLS/2022.2/common/technology/autopilot/ap_axi_sdata.h:95:1) INFO: [HLS 200-111] Finished Command csynth_design CPU user time: 1.44 seconds. CPU system time: 0.3 seconds. Elapsed time: 1.88 seconds; current allocated memory: 0.680 MB. while executing "source script_hls.tcl" ("uplevel" body line 1) invoked from within "uplevel \#0 [list source $arg] " INFO: [HLS 200-112] Total CPU user time: 3.62 seconds. Total CPU system time: 0.68 seconds. Total elapsed time: 14.25 seconds; peak allocated memory: 313.785 MB. INFO: [Common 17-206] Exiting vitis_hls at Fri Feb 17 12:58:33 2023... WARNING: [HLS 207-5527] 'Resource pragma' is deprecated, use 'bind_op/bind_storage pragma' instead (/home/eoin/Downloads/PYNQ_Composable_Pipeline/Vitis_Libraries/vision/L1/include/imgproc/xf_erosion.hpp:257:9) ERROR: [HLS 207-2976] no template named 'ap_axiu' in namespace 'xf::cv'; did you mean simply 'ap_axiu'? (../../../../src/erode/erode.cpp:20:9) INFO: [HLS 207-4436] 'ap_axiu' declared here (/home/eoin/xilinx/Vitis_HLS/2022.2/common/technology/autopilot/ap_axi_sdata.h:95:1) INFO: [HLS 200-111] Finished Command csynth_design CPU user time: 1.43 seconds. CPU system time: 0.22 seconds. Elapsed time: 2.33 seconds; current allocated memory: 0.695 MB. while executing "source script_hls.tcl" ("uplevel" body line 1) invoked from within "uplevel \#0 [list source $arg] " ``` There is a recurring warning following these errors listed as follows… ```auto WARNING: [HLS 207-5527] 'Resource pragma' is deprecated, use 'bind_op/bind_storage pragma' instead (/home/eoin/Downloads/PYNQ_Composable_Pipeline/Vitis_Libraries/vision/L1/include/imgproc/xf_box_filter.hpp:230:9) ``` The only source code I’m using is what’s available on the PYNQ\_Composable\_Pipeline github. It appears to me like the cpp functions in src are relying on libraries in Vitis\_Libraries which have been changed and are no longer compatible. Is there a workaround or fix available for these issues? ---
**Author:** ![marioruiz](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/marioruiz/32/2177_2.png) [@marioruiz](https://discuss.pynq.io/u/marioruiz)\ **Post date:** [February 17, 2023, 5:01pm UTC](https://discuss.pynq.io/t/library-incompatibility-pynq-composable-pipeline-on-kv260/5240/2 "2023-02-17T17:01:48Z")
Hi @Eoin_Moore, Welcome to the PYNQ community. The composable overlay that is in the `main` branch can only be built with Vivado 2020.2.2 and would only work on PYNQ 2.7.0. The composable overlay that is delivered to the KV260 with the PYNQ 3.0.1 image is on this branch [GitHub - Xilinx/PYNQ\_Composable\_Pipeline at v1.1.0-dev](https://github.com/Xilinx/PYNQ_Composable_Pipeline/tree/v1.1.0-dev), and can be built with Vivado 2022.1 Recently there was a question about using Vivado 2022.2 to build the composable, you can try this branch. However, this is something that is not thoroughly tested. > [@PYNQ Composable Overlay Default Path](https://discuss.pynq.io/t/pynq-composable-overlay-default-path/5172/8): > > Hi @cking, You may be able to use this tcl file for 2022.2. [PYNQ\_Composable\_Pipeline/cv\_dfx\_3\_pr.tcl at v1.1.0-dev.2022.2 · mariodruiz/PYNQ\_Composable\_Pipeline · GitHub](https://github.com/mariodruiz/PYNQ_Composable_Pipeline/blob/v1.1.0-dev.2022.2/boards/KV260/cv_dfx_3_pr.tcl) However, this is not tested in depth, hence I cannot provide much support. Mario Mario