Solved Both FreeBSD 13.2-RELEASE and 14-CURRENT are unable to boot on the Raspberry Pi 4B 8GB v1.5.

[ykla]

Both FreeBSD 13.2-RELEASE and 14-CURRENT are unable to boot on the Raspberry Pi 4B 8GB v1.5.The firmware is up to date.I am using a USB flash drive.The official Raspberry Pi OS is running normally.

I have tested the following systems with an external HDMI monitor, but none of them can boot successfully. During startup, a rainbow screen appears.

FreeBSD-13.2-RELEASE-arm64-aarch64-RPI.img.xz
FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20230713-510fd8313800-264135.img.xz
FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20230727-474708c334a7-264358.img.xz

I have used Rufus to burn the mentioned image and attempted to boot, but the rainbow screen persists.

I have tried downloading sysutils/rpi-firmware and sysutils/u-boot-rpi-arm64 on FreeBSD, and then copied them to the FAT partition.

I found that the version of sysutils/rpi-firmware is still from 2021, and some files have 2021 dates. As a result, I downloaded firmware from the official Raspberry Pi firmware repository to replace them. However, the rainbow screen issue persists, and I'm still unable to boot the system.

In general, regardless of whether I replace the firmware from the FreeBSD sources or the official Raspberry Pi sources, it results in the rainbow screen issue, and the system remains unable to boot


I suspect that the current firmware version provided by FreeBSD is too old, and there might be an issue with U-Boot as well.

I have a friend with a Raspberry Pi 4B 4GB version, and they said they can boot it successfully without any modifications using FreeBSD 13.2.But my Raspberry Pi 4 with 8GB RAM has been unable to boot successfully. It shows a rainbow screen.

see also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272792

 

[wb7odyfred]

/efi/boot/bootaarch64.efi

You might need to replace u-boot.bin or bootcode.bin with older version. October 2021
[SOLVED] Thanks Mark! Re: USB Flash drive booting from June 22,2023 RPI Snapshot FreeBSD 14.0
or use a later version of u-boot.bin
rpi4 8GB: sysutils/u-boot-*: 2023.07.02 && sysutils/rpi-firmware: 1.20230405


root@Fred_RasPi4B:/mnt/rpifat32 # cp -p ../msdos/u* .
root@Fred_RasPi4B:/mnt/rpifat32 # ls -l u*
-rwxr-xr-x 1 root wheel 568960 Oct 21 2021 u-boot.bin
-rwxr-xr-x 1 root wheel 602552 Jun 22 07:08 u-bootJune22_broken.bin
root@Fred_RasPi4B:/mnt/rpifat32 #

root@Fred_RasPi4B:/mnt/msdos # md5 u-boot.bin # 568960 Oct 21 2021
u-boot.bin Working Older Copy
MD5 (u-boot.bin) = 4c2998a9bd108775ada821a56e6362a7 # Working Older
Copy of u-boot.bin

-rwxr-xr-x 1 root wheel 602552 Jun 22 07:08 u-boot.bin
root@Fred_RasPi4B:/mnt/rpifat32 # md5 u-boot.bin #
MD5 (u-boot.bin) = be6c1637a6c775fad754efa723eff516 # Not booting
June 22 2023 u-boot.bin replaced

What is the MD5 checksum of the NOT BOOTING, displays 4 color screen? u-boot.bin file?

See if you can replace u-boot.bin with another version. Share MD5 checksums on both file with us, please

Audit your /boot files with md5deep audit tool May 16, 2021 see the MD5 checksum values.

I have tried downloading sysutils/rpi-firmware and sysutils/u-boot-rpi-arm64 on FreeBSD, and then copied them to the FAT partition. THE msdos FAT32LBA directory.
u-boot.bin

config.txt

c