Hi all, I want to try the new Armbian, but before I do, I need to get this Orange Pi 5 Max updated with whatever UEFI project is still maintained and supports it.
The UEFI I have installed right now is a hacked relic from a now abandoned ARM distro that was given to me -- I assume surely this has been superceded by a more legitimate source?

Thanks kindly for any updates, looking forward to rejoining the Armbian family soon as my UEFI is updated

We have standard dt based (community supported) images and standard uefi arm64 images.

but not a specific combination of both. for uefi firmware you have to check with edk2 rk3588 project.

As Werner noted, the maintained project is edk2-porting/edk2-rockchip on GitHub: https://github.com/edk2-porting/edk2-rockchip Check the Releases page — the Orange Pi 5 family (RK3588S) builds are there. If there's no specific "5 Max" entry, the Orange Pi 5 build usually matches (same SoC variant), but verify the DDR init config covers your LPDDR5x bin. One thing worth noting: edk2-rockchip ships its own DTB, which can drift from the kernel DTB that Armbian provides. If you hit device-level quirks after switching (NPU, GPU, USB) that's usually the cause — the openSUSE MicroOS thread on this forum has a clean fix using sdbootutil DEVICETREE_SOURCE. Alternatively, Armbian 26.8 (just released) can build UEFI images as bootable Live ISOs, and the rewritten armbian-config installer can flash a bootloader directly to SPI. Worth considering if you're reinstalling anyway — you might not need a separate edk2 flash at all.

3 hours ago, Boardcon_yang said:

As Werner noted, the maintained project is edk2-porting/edk2-rockchip on GitHub: https://github.com/edk2-porting/edk2-rockchip Check the Releases page — the Orange Pi 5 family (RK3588S) builds are there. If there's no specific "5 Max" entry, the Orange Pi 5 build usually matches (same SoC variant), but verify the DDR init config covers your LPDDR5x bin. One thing worth noting: edk2-rockchip ships its own DTB, which can drift from the kernel DTB that Armbian provides. If you hit device-level quirks after switching (NPU, GPU, USB) that's usually the cause — the openSUSE MicroOS thread on this forum has a clean fix using sdbootutil DEVICETREE_SOURCE. Alternatively, Armbian 26.8 (just released) can build UEFI images as bootable Live ISOs, and the rewritten armbian-config installer can flash a bootloader directly to SPI. Worth considering if you're reinstalling anyway — you might not need a separate edk2 flash at all.

Which bot produced this?

I have been trying to further research this as that project linked above doesn't support the 5 Max natively, and was told of this project, but it has seen no updates since 2025:  https://github.com/amazingfate/edk2-rk35xx/releases

 

But it DOES have a 5 Max image available, at least.

 

I'm saddened that someone out there hasn't continued or forked this work with further updates, as it sounds like it's not working perfectly, especially with USB ports.

WIll try this afternoon, and hopefully post back from Armbian instead of NixOS arm64 next time I reply

Edited August 29Aug 29 by snow

2 hours ago, snow said:

as it sounds like it's not working perfectly, especially with USB ports.

FUSB302 is not implemented. If that matters for you depends on how you power the board. AFAIK OPi5's are '5V 4A' quoted for PSU requirements, which I interpret as no formal USB-C 5V max 3A, but just bumping the current a bit without PD negotiation (like the RPI5 with 5A). So the whole FUSB302 does not matter then, but check yourself, especially schematics of the board.

 

Also note that U-Boot can act as UEFI firmware/bootloader, might be only serial console, but grub works then. You need to change bootmethod, so make sure it only can do EFI boot, not boot.scr or extlinux, you need to hide/remove/move those.

Edited August 29Aug 29 by eselarm