I use instructions here to get openvfd working.

Yesterday I did some changes to the defconfig and to the csc, hoping that it would help and it certainly seems so, BUT I get no further console logs after Starting kernel and, when the box is hooked to a display, the loading icon freezes after a few seconds after the kernel message. I removed parts of the csc and also combined the latest Sige 5 defconfig ant the one from earlier in the thread. As you can see, I did remove the blacklist for the GPU drive (which is one of the errors at the end of the bootlog) and also the boot process is different this time. UFS support is removed from the defconfig since we don't need it and the OP-TEE client (the errors that I got previously) is also no longer needed as well as the BL32 blob that was present in csc. At least now I won't need to force MASKROM mode to install newer images. Will try to follow the errors and hope to update this post soon. armsom-sige5-rk3576_defconfig h96-m9.csc

I installed the image https://dl.armbian.com/orangepizero2w/Bookworm_current_minimal on my Orange Pi Zero 2W board. But when I tied to check sound from the headphone interface on the expansion board I have a problem: user@orangepizero2w:~$ aplay -l aplay: device_list:274: no soundcards found... There is no chance to turn it on even through DTB overlay in armbian-config because there is no sound card in there. How to make sound work in this board with Armbian?

@Igor, I totally get that . Then, perhaps, there is even a simpler and quicker solution: getting a new WiFi dongle. From what I see from https://www.armbian.com/compatible/?_search=wifi, the AC 8811au and AC 8812BU should be supported. Is that still the case? Which chip would you recommend getting, keeping future compatibility in mind?

I assume 'without success' refers to: all zeros in 'SPI flash chip'. There could be other effects as well. All Armbian Rockchip kernels have eMMC (just '/dev/mmcblk*' essentially) fixed/builtin in the kernel so in vmlinuz, no initrd or overlays needed. I don't know OP5+ HW, but note that you can have 3 bootable storage devices on a Rockchip based SBC where U-Boot can be loaded from. So besides SPI, also eMMC and/or SD-card can contain a U-Boot bootloader (see first 16MiB of those devices). If so, then the question is what version of U-Boot? Besides lacking a mmcblk dev, like is the case for example if I use an old version of EDK2 UEFI on my NanoPi-R6C (RK3588s) on the eMMC(!), It might be that a mainline U-Boot version does not work with vendor kernel. I had that for my Rock3A for example (kernel crash).