# Make builds pynq-z1 and z2 but not ZCU104 **URL:** \ **Category:** Support\ **Created:** [October 22, 2019, 7:57pm UTC](https://discuss.pynq.io/t/make-builds-pynq-z1-and-z2-but-not-zcu104/596 "2019-10-22T19:57:34Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![johnk](https://avatars.discourse-cdn.com/v4/letter/j/59ef9b/32.png) [@johnk](https://discuss.pynq.io/u/johnk)\ **Post date:** [October 22, 2019, 7:57pm UTC](https://discuss.pynq.io/t/make-builds-pynq-z1-and-z2-but-not-zcu104/596/1 "2019-10-22T19:57:34Z")
I’m using pynq v2.4 on Ubuntu 16.04 (for supporting Xilinx tools 2018.3) With a fresh git clone, make builds both pynq-z1 and pynq-z2 but produces this error when trying ZCU104: ``` mkdir -p /home/joan/pynq/sdbuild/build/ZCU104 cp /home/joan/pynq/sdbuild/boot/image_aarch64.its /home/joan/pynq/sdbuild/build/ZCU104/image.its rm -rf /home/joan/pynq/sdbuild/build/ZCU104/petalinux_bsp mkdir -p /home/joan/pynq/sdbuild/build/ZCU104/petalinux_bsp BSP=xilinx-zcu104-v2018.3-final-v2.bsp BSP_BUILD=/home/joan/pynq/sdbuild/build/ZCU104/petalinux_bsp BSP_ABS=/home/joan/pynq/sdbuild/../boards/ZCU104/xilinx-zcu104-v2018.3-final-v2.bsp BSP_PROJECT=xilinx-zcu104-2018.3 /home/joan/pynq/sdbuild/scripts/create_bsp.sh /home/joan/pynq/sdbuild/../boards/ZCU104 zynqMP + set -e + board=/home/joan/pynq/sdbuild/../boards/ZCU104 + template=zynqMP + '[' '!' -z xilinx-zcu104-v2018.3-final-v2.bsp ']' + cp -f /home/joan/pynq/sdbuild/../boards/ZCU104/xilinx-zcu104-v2018.3-final-v2.bsp /home/joan/pynq/sdbuild/build/ZCU104/petalinux_bsp cp: cannot stat '/home/joan/pynq/sdbuild/../boards/ZCU104/xilinx-zcu104-v2018.3-final-v2.bsp': No such file or directory Makefile:298: recipe for target '/home/joan/pynq/sdbuild/build/ZCU104/petalinux_bsp/xilinx-zcu104-2018.3.bsp' failed make: *** [/home/joan/pynq/sdbuild/build/ZCU104/petalinux_bsp/xilinx-zcu104-2018.3.bsp] Error 1 ``` any clues? ---
**Author:** ![patocarr](https://avatars.discourse-cdn.com/v4/letter/p/d2c977/32.png) [@patocarr](https://discuss.pynq.io/u/patocarr)\ **Post date:** [October 23, 2019, 2:31am UTC](https://discuss.pynq.io/t/make-builds-pynq-z1-and-z2-but-not-zcu104/596/2 "2019-10-23T02:31:32Z")
I believe ZCU104 needs a Vivado video license to build correctly. It fails on my end as well. -Pat ---
**Author:** ![johnk](https://avatars.discourse-cdn.com/v4/letter/j/59ef9b/32.png) [@johnk](https://discuss.pynq.io/u/johnk)\ **Post date:** [October 23, 2019, 6:06am UTC](https://discuss.pynq.io/t/make-builds-pynq-z1-and-z2-but-not-zcu104/596/3 "2019-10-23T06:06:21Z")
In that case the error message is about the most confusing. If they are not going to help, why having that stream of random text? ---
**Author:** ![patocarr](https://avatars.discourse-cdn.com/v4/letter/p/d2c977/32.png) [@patocarr](https://discuss.pynq.io/u/patocarr)\ **Post date:** [October 23, 2019, 2:56pm UTC](https://discuss.pynq.io/t/make-builds-pynq-z1-and-z2-but-not-zcu104/596/4 "2019-10-23T14:56:36Z")
You can try downloading the .bsp from Xilinx and place it in …/boards/ZCU104. That way, you’d avoid having to build the logic from scratch and needing the license. -Pat ---
**Author:** ![johnk](https://avatars.discourse-cdn.com/v4/letter/j/59ef9b/32.png) [@johnk](https://discuss.pynq.io/u/johnk)\ **Post date:** [October 23, 2019, 3:02pm UTC](https://discuss.pynq.io/t/make-builds-pynq-z1-and-z2-but-not-zcu104/596/5 "2019-10-23T15:02:32Z")
Yes, it’s probably a good idea. I just built one from scratch and took many hours. ---
**Author:** ![gnatale](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/gnatale/32/11_2.png) [@gnatale](https://discuss.pynq.io/u/gnatale)\ **Post date:** [October 29, 2019, 11:11am UTC](https://discuss.pynq.io/t/make-builds-pynq-z1-and-z2-but-not-zcu104/596/6 "2019-10-29T11:11:07Z")
The error you are seeing is due to the absence of the bsp inside the ZCU104 board folder when trying to build. Since Xilinx provides an official BSP for that board (available [here](https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/embedded-design-tools.html)) that’s the one we use and support. Also, to my knowledge, Vivado WebPACK should be enough to build also the ZCU104, so it should not really be a licensing issue. EDIT: my bad, the ZCU104 requires the HDMI license, so even if it is supported by the webpack, you’ll need that license for it to build. ---
**Author:** ![pynqzen](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/pynqzen/32/97_2.png) [@pynqzen](https://discuss.pynq.io/u/pynqzen)\ **Post date:** [October 1, 2020, 3:59pm UTC](https://discuss.pynq.io/t/make-builds-pynq-z1-and-z2-but-not-zcu104/596/7 "2020-10-01T15:59:03Z")
Hi, Just came across this, what I have found is that an SDSoC license will also work, something probably in the Vision libraries uses that HDMI IP and SDSoC covers it. I have a full everything Vivado license and that is not good enough either. You have to use SDSoC or get the HDMI IP license or even better if you aren’t building for the ZCU104 don’t build it.