I’m porting PYNQ to a custom board from board agnostic rootfs. I’m using PYNQ 2.5.4 (but similar results with 2.5.1). Vivado/Petalinux 2019.1 (last SDK edition). The board has Ethernet on EIO interface, one GPIO LED that should light on startup, and an LED on done_0.
I have successfully built Petalinux, and generated a boot image that boots fine (ethernet functional, LED and done_0 fine). I used the Petalinux config to create a BSP archive successfully.
I used this to generate a PYNQ image.
I created under ~/PYNQ/boards my custom board tree:
ARCH_ebaz_new = arm
BSP_ebaz_new = ebaz_new.bsp
STAGE4_PACKAGES_ebaz_new = pynq ethernet
petalinux-util --webtalk off
make PREBUILT=~/Downloads/bionic.arm.2.5.img PYNQ_SDIST=~/Downloads/pynq-2.5.tar.gz BOARDS=myboard BOARDDOR=~/PYNQ/boards/
The build completes successfully. I copy the image to an SDcard with win32discimager successfully, and the image boots to PYNQ linux. However, I have no eth hardware identified, no gpio LED, and worst, done_0 LED remains off.
What went wrong? surely, if petalinux knows to configure the Zynq, some definition is over-ridden in PYNQ, but i have no idea where to find it.
Any help will be much appreciated!