Hi,
Please find the following build guide and issue report:
Unless people having hard time on setting up the environment:
Vagrant is not a good method to setup the SD build environment.
I have not investigate to the bottom but what previous engineer shows there might Virtual R/W issue during such setup.
STEPS:
I will suggest download 18.04.06 LTS Ubuntu from official website
Create a virtual disk size about 200GB or more, set the CPU >#4, RAM >#8192
Update Ubuntu packages before setting up the PYNQ
3b) Git clone the PYNQ to /home//PYNQ
3c) sudo ch…
Problem solve:
Indeed the boot arg is not default edited by the make script on the PYNQ.
I not even notice this is the case as once it stuck I had no idea how I can get the log why and what reason it is stucking.
Maybe Sarunas you can advise a bit how we can debug the root cause it is stuck.
Starting Samba NMB Daemon...
Starting OpenBSD Secure Shell server...
Starting Permit User Sessions...
[ OK ] Started Unattended Upgrades Shutdown.
[ OK ] Finished Permit U…
This setup confirmed by many developers that had good result with PYNQ 2.7.
Remember any share folder or right restricted folder will result in so many unexpected build issues.
This setup targeted PYNQ2.7 along with Vivado2020.2