I thought the next step would be creating a myboard.bsp with petalinux and then run the image_from_prebuilt.sh letting it crunch the myBoard.bsp just created and the bionic.arm.2.4.img…
petalinux-create was OK
petalinux-config --get-hw-description=< path-to-my-hdf-folder > was OK
petalinux-build failed:
I will post on the xilinx-petallinux forum, too, as this looks PYNQ unrelated, but just in case anyone has seen this before…
image_from_prebuilt.sh assumes you have the bsp ready but you need bsp built first.
For example, for our Pynq-Z1 board, we can put a single file base.hdf in boards/Pynq-Z1/petalinux_bsp/hardware_project and our makefile is able to pick the hdf up and build the image.
Hello Rock,
I have the hdf, I just need to create this folder: mkdir <PYNQ_repository>/myboards/myboardname/petalinux_bsp/hardware_project
stuff the hdf in it and run: make BOADDIR=<PYNQ_repository>/myboards/myboardname
is that all?
Vivado 2018.3, Petalinux 2018.3
The complete config.log highlighting more info on the error is now attached.
I’ll check your link and see if I can come out of the hole
Thank you config.log.txt (16.5 KB)
This thread suggests to not build on shared folder… but vagrant sets up the VM with the github pynq repository seen specifically as a shared folder… how am I supposed to build in another folder?!? And how come it works for everybody else?!?
Hi, It seems that the Petalinux is not installed correctly, please check if you can find bitbake file in the Petalinux installation folder. If you can not find the file, please re-install the Petalinux software.
Please take note that Petalinux need to be installed as a non-root user. Please use sudo chown command to give access to current user if you want to install petalinux to a folder that current user has no access, for example /opt/petalinux folder.
petalinux was installed as vagrant user, because the VM was built running “vagrant up” as instructed in the documentation. Btw I do not have root credentials on the VM
Best regards
If I knew the path was significant, I would have done so… unfortunately now the VM has sucked all the 100GB I painfully freed in my host disk and I have no breathing space left.
Probably I will delete and recreate the VM and reinstall SDx and petalinux. To be honest, as mentioned in another thread, I already created another, huger, VM in the cloud, and tried to build the SD there, but failed miserably nevertheless
It failed much further down the line, though
Is it a mistake to do “petalinux-build” that prohibits correct image creation (as in “one MUST NOT do it”)
or
does it just waste time, because pynq’s “make BOARD=…” only needs the output of “petalinux-package --bsp …”?
I’m still searching for a more in-depth description of the custom board build process and possible caveats.
