Hi,
After I installed v2.3.0, it seems like the rpi-naked-provisioning.sh doesn't detect the Ethernet setup used to transfer the image file. This used to work on v2.2.0.
I'm using CM5 IO Board as the provisioning server, and I'm trying to flash a CM4 via a CM4 IO Board.
My AI agent suggested the following, which fixex the issue:
In service/rpi-naked-provisioner.sh, change the flash target from FASTBOOT_DEVICE_SPECIFIER to prefer FASTBOOT_TCP_FLASH_SPECIFIER when available.
# Re-check the fastboot devices specifier, as it may take a while for a device to gain IP connectivity
setup_fastboot_and_id_vars "${FASTBOOT_DEVICE_SPECIFIER}"
-fastboot -s "${FASTBOOT_DEVICE_SPECIFIER}" flash "${RPI_DEVICE_STORAGE_TYPE}" "${FLASH_IMAGE}"
+FLASH_SPECIFIER="${FASTBOOT_TCP_FLASH_SPECIFIER:-${FASTBOOT_DEVICE_SPECIFIER}}"
+fastboot -s "${FLASH_SPECIFIER}" flash "${RPI_DEVICE_STORAGE_TYPE}" "${FLASH_IMAGE}"
Explanation for issue text:
setup_fastboot_and_id_vars already computes split-mode routing and sets FASTBOOT_TCP_FLASH_SPECIFIER=tcp:<ip> when tcp-data-plane-only=yes. The script logs “flash over tcp:...”, but rpi-naked-provisioner.sh still flashes using FASTBOOT_DEVICE_SPECIFIER (USB serial), so TCP is never used for the actual image transfer. service/rpi-idp-provisioner.sh already uses the correct pattern (FLASH_SPECIFIER="${FASTBOOT_TCP_FLASH_SPECIFIER:-${FASTBOOT_DEVICE_SPECIFIER}}") for its flash step, so this makes naked mode consistent.
Also, I would just like to thank you for making this tool. It is very convenient and looks great :))
Hi,
After I installed v2.3.0, it seems like the rpi-naked-provisioning.sh doesn't detect the Ethernet setup used to transfer the image file. This used to work on v2.2.0.
I'm using CM5 IO Board as the provisioning server, and I'm trying to flash a CM4 via a CM4 IO Board.
My AI agent suggested the following, which fixex the issue:
Also, I would just like to thank you for making this tool. It is very convenient and looks great :))