rpiboot with BOOT_ORDER set to network does not appear to allow for network boot

[correcthorse2]

Describe the bug

From commit 87d6e03.

Applying:

diff --git a/recovery5/boot.conf b/recovery5/boot.conf
index b0063ee..54c6681 100644
--- a/recovery5/boot.conf
+++ b/recovery5/boot.conf
@@ -3,5 +3,5 @@ BOOT_UART=1
 POWER_OFF_ON_HALT=1
 
 # Boot Order Codes, from https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#BOOT_ORDER
-# Try SD first (1), followed by, USB PCIe, NVMe PCIe, then network
-BOOT_ORDER=0xf2461
+# Try network (2)
+BOOT_ORDER=0xf2

Then running against a cm5:

cd recovery5 
./update-pieeprom.sh
sudo rpiboot -d .

Produces expected output:

RPIBOOT: build-date 2025/08/28 pkg-version local 48ec6cb7

Please fit the EMMC_DISABLE / nRPIBOOT jumper before connecting the power and USB cables to the target device.
If the device fails to connect then please see https://rpltd.co/rpiboot for debugging tips.

Loading: ./bootcode5.bin
Waiting for BCM2835/6/7/2711/2712...

Loading: ./bootcode5.bin
Sending bootcode.bin
Successful read 4 bytes 
Waiting for BCM2835/6/7/2711/2712...

Loading: ./bootcode5.bin
Second stage boot server
Loading: ./config.txt
File read: config.txt
Loading: ./pieeprom.bin
Loading: ./pieeprom.bin
Loading: ./pieeprom.sig
File read: pieeprom.sig
Loading: ./pieeprom.bin
File read: pieeprom.bin
Second stage boot server done

But does not appear to the tftp server.

Flashing a normal image and enabling network boot does work, so I don't think this is anything to do with the tftp server setup.

Steps to reproduce the behaviour

As above

Device(s)

cm5

Compute Module IO board.

cm4-nano-b

[pelwell]

The recovery images are for updating (or modifying) the EEPROM. You will have to reboot with the new EEPROM image in order for it to take effect.

You can confirm that the EEPROM image to be flashed to the target device has been updated with your boot.conf by running:

$ rpi-eeprom-config ./pieeprom.bin

[correcthorse2]

That worked, thanks! I thought I'd tried that previously but apparently not.

I was under the assumption that the changes made by usbboot were transient, because it seems like the usb gadget is.

It would be nice to have docs for setting a pi to netboot without flashing it on the network boot docs page. If possible it would also be useful to have a pieeprom.bin that does this in usbboot.