Update to 20240926 version

[ Impact ]

The current version of rpiboot is unable to operate on the forthcoming CM5. In order to enable support for new hardware on the current LTS, we would like to back-port the current rpiboot to oracular and noble.

Unfortunately a minimal patch is not possible in this particular case, as rpiboot's method of operation relies upon the (closed source) bootloader it sends to the recipient (usually a Compute Module), so most of such a patch would just be binary blobs. However, the first version that officially supports the CM5 also moves some of the binary blobs to a dependency on rpi-eeprom (sensibly, as they are otherwise duplicates). Hence, the only realistic option in this case is to backport the whole version.

[ Test Plan ]

To be repeated with eMMC variants of the CM4 and CM5 (rpiboot is not required for lite variants of the CMs), on affected $series:

* Plug CM into IO board
* Attach boot inhibitor jumper
* Attach power to IO board
* Connect IO board's microUSB port to host machine
* On host machine:
* sudo apt install rpiboot
* sudo rpiboot
  - On CM5: application hangs awaiting board; wait 30 secs and Ctrl-C
  - On CM4: application proceeds to switch CM into MSD mode; sudo eject /dev/sda (substitute MSD device as appropriate)
* Disconnect IO board from host machine
* Re-connect IO board to host machine
* sudo apt install -t $series-proposed rpiboot
* sudo rpiboot
* On either model: application proceeds to switch CM into MSD mode
* Verify /dev/sda and /dev/sda1 exist (substitute MSD device as appropriate; see dmesg output)
* wget https://cdimage.ubuntu.com/releases/oracular/release/ubuntu-24.10-preinstalled-server-arm64+raspi.img.xz
* xzcat ubuntu-24.10-preinstalled-server-arm64+raspi.img.xz | sudo dd of=/dev/sda bs=16M status=progress (WARNING: substitute MSD device as appropriate)
* sudo eject /dev/sda (substitute MSD device as appropriate)
* Disconnect IO board from host machine
* Remove power from IO board
* Remove boot inhibitor jumper
* Attach screen, keyboard, ethernet to IO board
* Attach power to IO board
* Watch for successful boot

[ Risk Analysis ]

The bump of rpiboot doesn't affect the majority of Pi boards, as it's primary purpose (in Ubuntu) is to enable Compute Modules for flashing. As such, this bump doesn't affect the active "ability to boot" of any boards.

The current version of rpiboot is unable to interface with the forthcoming CM5, and thus can't regress much further in that regard. The main risk for regression is if the new version stops working with existing CM4 modules, or somehow causes issues with the eMMC on targetted boards.

The version proposed comes directly from upstream with the only modification that we strip out the Windows-support binaries (which are unneeded in Ubuntu). The test plan verifies that the CM5 issue exists, that the proposed version fixes it, and that it continues to work successfully on the CM4. Moreover, to guard against the possibility of corrupting the eMMC on the target modules, the test plan also covers actually flashing an Ubuntu image to the module and booting it fully.

[ Original Description ]

Please update to the new upstream version (at least 20240926). This is now required for CM5 support, 2712 support, and requires backport to oracular and noble.