Hello:
I am having trouble trying to understand what is happening here. I will
appreciate your help.
I have downloaded the following NetBSD-Current RPi aarch64 image:
https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/202503110400Z/evbarm-
aarch64/binary/gzimg/arm64.img.gz
And last UEFI firmware distribution from:
https://github.com/pftf/RPi4/releases/download/v1.41/
RPi4_UEFI_Firmware_v1.41.zip
In my NetBSD amd64 system I unzipped arm64.img.gz image and flashed it
on the SD card with "dd if=arm64.img of=/dev/rsd0d bs=1m" command as
usual, then mounted the msdos partition and copied
RPi4_UEFI_Firmware_v1.41.zip. I extracted it overwriting the NetBSD-
current aarch64 files and fired up the RPi4.
It got stuck at the multi-color screen, not passing beyond it. Green LED
flashed 7 times repeatedly. I never could see the raspberry icon neither
the UEFI screen.
After that failure, I downloaded old v1.40 firmware and unpacked over
the same NetBSD-current SD image. It worked just fine, I was able to
enter UEFI screen, disable the 3 GB limit and change bot order. NetBSD-
Current worked just fine.
After the experiment I asumed that v1.41 was simply bad, but I was not
fully satisfied and continued with the experiment.
I started this time with a clean SD. I created and formated a unique new
msdos partition using fdisk under my NetBSD amd64 system, that partition
was 100 MB size. No more partitions were added to the SD card. I mounted
msdos partition and extracted v1.41 firmware inside the msdos partition
and fired up the RPi4. It seemed to boot fine and reach the UEFI screen.
No NetBSD files where in the SD card, so it was good until that point.
I still do not understand why v1.41 did not boot when extracted over the
NetBSD-current aarch64 image file on the SD. I am a bit puzzled and out
of ideas. I would like to understand what it happening.
Thanks so much.
Regards.