Version 2.3.0 and 2.3.1 can't provision Raspberry pi 5, work with CM4/CM5

[T-droneops]

I am trying to provision a system on full size Raspi 5, I'm connecting it with PWR button down, but the bootstrap fails and the error is always the same:

2026-07-02T13:17:31.940Z raise Exception("update-bootcode: Can't update image - 128K must be reserved for bootcode").

I am provisioning Raspi 5 in naked mode, but what makes me worried is that the error is caused by this command:

rpi-eeprom-config --out /srv/rpi-sb-provisioner/tmp/rpi-sb-bootstrap.yop/non-secure-bootloader//pieeprom.bin.intermediate --bootcode /tmp/tmp.G3oUxADAZM/bootcode.bin.signed /usr/lib/firmware/raspberrypi/bootloader-2711/default/pieeprom-2026-05-17.bin

Why does it use the bootloader for 2711?

My rpibnoot and rpi-eeprom:

soros@raspberrypi:~ $ dpkg -l rpiboot rpi-eeprom
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version         Architecture Description
+++-==============-===============-============-===============================>
ii  rpi-eeprom     28.28-1         all          Raspberry Pi 4/5 boot EEPROM up>
ii  rpiboot        20260603~182203 arm64        Raspberry Pi USB booting code
lines 1-7/7 (END)

[tdewey-rpi]

Having inspected the code, the only path I can see to cause this failure is if you selected Raspberry Pi 4 in the Options, and then connected a Raspberry Pi 5. Can you confirm that if you:

1. Go to the Options page
2. On the OS selector, select your OS, and then in the right-hand-side metadata pane, select 'Clear cached files'
3. On the device selector, select Raspberry Pi 5
4. Expand 'browse available firmware', and explicitly select the 'default' or 'latest' option.
5. Re-connect your Raspberry Pi 5

That it still fails?