Love your show, Peter! These types of posts are very helpful.
I’ve been trying to build the ZC706 PYNQ 2.7 port by following the instructions in this post to the letter, and can’t find the “board-agnostic rootfs image” for PYNQ 2.7! There is no *.img file, as in this post, only a *.tar.gz file. I would like to use that, but in the full process, the one that uses make, instead of image_from_prebuilt.sh, I run into exactly the same problem described here Package not found when making image - Support - PYNQ – even though I am already using Ubuntu 18.04.6 LTS!
Some clarification would be terrific. Even though I was able to use your post to generate PYNQ 2.5 for the ZC706, I had to look far and wide across the Interwebs to find the file bionic.arm.2.5.img. It should not be this hard! It would be terrific if the Xilinx gang supporting PYNQ would create sticky links that allow recreation of the post, especially since it’s only just over two years later!
Bottom line: I need to be able to perform this procedure for PYNQ 2.7, which seems to indicate I need to find the elusive “focal.arm.2.7.img” file.
As of v2.7 all board agnostic images are in tarball (tar.gz) form rather than .img. Functionally it makes no difference to the build scripts so the file you use just has a different extension.
In the post you linked, I believe the problem was a tool version incompatibility – since you were able to build a v2.5 image, I presume you were using Vivado 2019.1 and a BSP of the same version? When building for the v2.7 image, are you using a 2020.2 version of the tools and BSP?
Thank you for your speedy reply! Vitis and petalinux are both 2020.2. The problem I am wrestling with is that setup_host.sh called out a number of packages that were not installed and/or the incorrect version. (Especially a bunch of packages that are Ubuntu 18.04.06 and not bionic versions–wait, I thought they were the same thing?)
I was hoping that image_from_prebuilt.sh would avoid these requirements, but if it just ends up running a modified “Make” process, I would have the same problems anyway. In any event, forcing installation with aptitude ended up corrupting the kernel, so now this is an Ubuntu problem rather than PYNQ. After I reset my VirtualBox, I will update with another error, or report success.