If the installation is essentially writing a blank disk image that may be true. However, configuring things like eMMC user data areas, NVMe namespaces can require device resets or custom bootloader configuration and it's much easier to do that if the provisioner has power control over the CM.Would argue that using an installation method that uses a USB stick or network boot (like cmprovision) is still the most hassle free installation method.
Except for the initial alpha test CM5s the boot-order is now equivalent to CM4As those are in the default boot sequence of a CM (as long as they are factory fresh and eMMC is empty), so you can provision while the module is already in the final device, and you do not need to mess with jumpers to get it to rpiboot.
https://github.com/raspberrypi/usbboot/ ... /boot.conf
BOOT_ORDER=0xf2461
USB host boot is on RP1 only - not the USB2 (USB-C) interface because this no longer has an XHCI controller.
Statistics: Posted by timg236 — Fri Mar 21, 2025 9:33 am