My approach to "patch" the PYNQ image with image.ub (using a modified device_tree) does not work.
(almost all works, just using Interrupts in overlay bit file (AXI IntC), fails: it does not find OUI and the interrupt vector 121 needed for it)
Now I am building a complete PYNQ image for the ZUBoard, from scratch.
Why is it so 'painful'?
I have to check the build log, try to figure out what is missing, what is not set, even modifying the build scripts (e.g. xcst was not found) ...
It takes >10 hours just to setup the build environment (assume one entire day just to setup all properly for a clean build).
And when it was running once completely to the end - I want to change now just my device tree in 'system_user.dtsi', in order to add
a node for mmcblk1 (eMMC module, mmcblk0 is the SD card).
Why is the buildzu.sh loading, compiling, installing ... all the time "all" again?
It takes hours (a half day) just to make a small modification in just one device_tree file.
(few lines of text added to device tree and the build process takes hours again - WHY?)
What is the fastest way just to compile PYNQ for ZUBoard again?
(make should realize what is unchanged, but the script seems to run almost all again, "rrrrr"
and it seems to fetch a lot of stuff again from Internet, including to fetch/submit something from/to GitHub - what is this build process doing?)
(unless just wasting my time)
Please,
who does have or could generate a PYNQ SD card image:
- which would see, support the eMMC module (or even the SSD M.2 module, alternatively)
as the PetaLinux does (but this PetaLinux image does not enable FPGA Manger or has Python (PYNQ) support integrated) - Please, please, ...
just merge the eMMC (and SSD M.2) module into a ZUBoard PYNQ image. THANK YOU!
How get a ZUBoard PYNQ image which would "see" (support) eMMC (and/or SSD M.2) module?
