Closed apowers313 closed 1 year ago
Thanks for reporting this, I have been making many changes to the build process of u-boot and the kernel in preparation for supporting other boards. I'm looking into this now.
I tested the latest build on my build server, and U-Boot works fine. However, think that I know the issue. U-Boot will not report an error if python2 is not installed and will continue the build process. Try downloading the below packages and compile U-Boot again, it should work without issue.
sudo apt-get install -y build-essential gcc-aarch64-linux-gnu bison \
qemu-user-static qemu-system-arm qemu-efi u-boot-tools binfmt-support \
debootstrap flex libssl-dev bc rsync kmod cpio xz-utils fakeroot parted \
udev dosfstools uuid-runtime git-lfs device-tree-compiler python2 python3 \
python-is-python3 fdisk
That did the trick, thanks!
And thanks again for the awsome project and speedy help.
After building the Orange Pi 5 U-Boot image and writing it to SPI, the board won't boot. The only difference on the serial console is that
atf-1
and similar don't seem to be loaded (see below). It appears that the Arm Trusted Firmware isn't included in the SPI image (despite being part of the build process).To reproduce (building on the Orange Pi 5 itself):
Output when booting:
[device hangs at this point]
Output when booting using Orange Pi provided U-Boot (/usr/lib/linux-u-boot-legacy-orangepi5_1.1.4_arm64/rkspi_loader.img):
[device continues to boot at this point]