A documented future? : Pi500/CM5 and Pi5 firmware requirement?

[markmi]

Just an FYI: One of the new RPi firmware release notes reports:

Update recovery.bin to the most recent version required for CM5 and Pi500.
(firmware version 2024-10-21)

This suggests that, if rpi5-uefi is to support the Pi500, once it is available, rpi5-uefi may end up needing a update to the RPi firmware it is based on and whatever else goes along with making that work. A bcm2712-rpi-500.dtb is published, along with 4 bcm2712-rpi-CM5*.dtb files. Likely preliminary content for now?

[einsteinagogo]

following up from this, does this release 0.3 work with CM5 as is - current ?

[mibosshard]

following up from this, does this release 0.3 work with CM5 as is - current ?

at least for me, no. I would also like to know if it should work though...

[markmi]

There have been no commits after: Mar 16, 2024 . No one with the appropriate background knowledge and interest looks to have worked on it since then. The EDK2 material ended up not going through the process to have it upstreamed into the official EDK2 materials.

For reference . . .

This release (from a microsd card with it):

# mount -noatime /dev/mmcblk0p1 /mnt
# ls -C /mnt/*.dtb
/mnt/bcm2712-rpi-5-b.dtb

Modern (from RaspiOS64 [my abbreviation] media):

# ls -C1 /boot/firmware/bcm2712*
/boot/firmware/bcm2712d0-rpi-5-b.dtb
/boot/firmware/bcm2712-rpi-500.dtb
/boot/firmware/bcm2712-rpi-5-b.dtb
/boot/firmware/bcm2712-rpi-cm5-cm4io.dtb
/boot/firmware/bcm2712-rpi-cm5-cm5io.dtb
/boot/firmware/bcm2712-rpi-cm5l-cm4io.dtb
/boot/firmware/bcm2712-rpi-cm5l-cm5io.dtb

The status relative to the additional *.dtb files and relative to any bcm2712-rpi-5-b.dtb update is unknown/untested so far as I know. No one is working on making sure that any of those would work so far as I can tell, not even if reports of problems were made.

I similar point might apply to updates to the EEPROM content, in part because the loaded *.dtb file content might get live updates before EDK2 is involved.

Nothing claims any of the more modern context is or will ever be supported by someone.

FYI: See #18 (comment)

In it, the author of the EDK2 code says, in part:

It all takes a lot of effort and public interest is also fairly low, so I have pretty much no incentive to continue working on this.

. . .
@Croydon, It started out of curiosity to see what would be possible with this hardware in terms of standardization, so yes, mostly a proof-of-concept. I'm not actively working on it, but this doesn't mean it's dead - contributions are welcome.

About upstreaming:

The TF-A port is upstreamed, minus one PCI patch that's waiting on review.

I've also submitted the patches in my EDK2 base fork back in January, but I haven't heard anything since. The EDK2 review process is slow in general, at times non-existent (understandably, not many maintainers), so I just gave up on that idea.

[NumberOneGit]

Start by copying the appropriate firmware boot file to replace the rpi5 dtb file. I use the cm5io file selected. Add a line in config.txt to explicitly use that file, for example:
device_tree=bcm2712-rpi-cm5-cm5io.dtb

If I change framebuffer depth in the config.txt file to 16 or 24, I no longer get a black screen. I don't have a proper USB dock for all the peripherals that I need to continue but if you do, let me know if you can get past the boot screen with these settings.

EDIT: After trying for awhile, it freezes when trying to load beyond the UEFI boot screen, similar to CM4 behavior which I’m not sure was ever remedied.

[omerfsen]

I am having same issue. Pi500 black screen but with Pi5 that is ok, though it fails afterwards