Describe the bug

We build a minimal image for the EOL tests. These images only contain the devicetree + overlays for the product and cm5. The bootloader wont boot until we configure os_check=0 in config.txt, because the os check requires bcm2712-rpi-5-b.dtb.

While the workaround is ok, it still feels not right. Therefore I'd like to consider extending the os_check, so the dtb for cm5 is enough for the os check on CM5. Something with low prio though...

Steps to reproduce the behaviour

1. Flash RPi OS to eMMC of a CM5
2. Remove /boot/firmware/bcm2712-rpi-5-b.dtb
3. Reboot

(or build a minimal image with only contains the cm5 dtb + bcm2712d0.dtbo etc)

Device (s)

Other

Bootloader configuration.

System

Bootloader version: 2025-03-19

Bootloader logs

No response

USB boot

No response

NVMe boot

No response

Network (TFTP boot)

No response