Can't connect rpiboot

[deividasn]

Hi,

i buyed Revolution Pi connect 4 . (used). I want write new OS, but i have error when try connect rpiboot. Can sameone explaining where is a problem. See atached file.

thanks!

[RamiGspo]

Hi deividasn,

I think you're using Windows, and it seems to me that you're using the wrong application.
Your Revolution Pi Connect 4 uses a CM4 (Compute Module 4), not the older CM1/CM2/CM3 modules. In Windows, you need to use different applications depending on the compute module:

• For CM1, CM2, CM3: Use the regular rpiboot application (which you're currently using)

• For CM4 and CM5: Use the "rpiboot-CM4-CM5 - Mass Storage Gadget" application

Unbenannt.png (116.02 KiB) Viewed 9219 times

Please use the application "rpiboot-CM4-CM5 - Mass Storage Gadget" instead.
This should resolve your issues and allow you to flash your RevPi Connect 4 correctly.

Good luck!

RamiGspo

[sequence-rob]

Hello !

I post a reply to this old post, with a similar problem on a more modern RevPi :

I have a revPi connect 5, on which I am trying to apply the image saving procedure :
https://revolutionpi.com/en/knowledge/r ... ling-image

But I can't get it to connect using rpiboot on my windows 11.
The device is recognized while booting with USB connection, but it does not load the boot image (and does not appear as a mass storage device):

Obviously rpiboot has evolved since the reply below. Today there is no "rpiboot-CM4-CM5", rpiboot simply default boots using "mass-strorag-gadget64" which should work on CM5 (?).

I am stuck and ChatGPT tells me only crap. ;-(

Thank you for your help !

Sequence-rob

[Amar]

Hi,
The error indicates your rpiboot version is outdated and missing bootcode files for BCM2711 (CM4), which the RevPi Connect 4 uses.

Solution for Windows:
Step 1: Uninstall current rpiboot version and preferably reboot
Step 2: Install latest version

Download from: https://github.com/raspberrypi/usbboot/releases
Get the latest windows-v1.0 release
Extract and navigate to win32 folder
Run rpiboot_setup.exe

Verification:
Updated rpiboot shows:

Code: Select all

RPIBOOT: build-date 2025/05/19 pkg-version local 402baf02

Regards,
Amar

[sequence-rob]

Thank you for your help !

The original post was with a RevPi Connect 4, in my case it is a RevPi Connect 5.
Your advice helped a little bit (rpiboot's output looks a bit nicer), but I am obviously stuck at the same place in the program.

I also tested on a different computer (windows 11 too): I get exactly the same issue.
Specifying the directory ".\rpiboot -d .\mass-storage-gadget64\" does not help either. It loads bootfiles.ini but then stays stuck at the same place.

To me, this looks like a driver issue. On my computer it says the driver for "BCM2712D0 Boot" is correctly installed but misses further configuration -> the device is recognized correctly, that is a good thing! On the second computer (fresh install from latest release) it says that no driver is installed for "BCM2712D0 Boot". Rpiboot's installation procedure displayed no error, but obviously something is still missing.

Thank you!

Sequence-rob

[Amar]

Good to see the progress.

1) Verify the files are present in C:\Program Files (x86)\Raspberry Pi\mass-storage-gadget64\ - check that all files (bootfiles.bin, boot.img, config.txt, etc.)
2) USB driver binding issue for BCM2712D0.
Fix the WinUSB driver binding:

Use Zadig (most reliable):
Download: https://zadig.akeo.ie/
Connect CM5 in boot mode
Run rpiboot (it will get stuck at "Waiting...")
In Zadig: Options → List All Devices
Select "BCM2712D0 Boot"
Choose WinUSB driver
Click "Install Driver"

Or manual driver install:
Device Manager → find "BCM2712D0 Boot" (yellow warning)
Right-click → Update Driver
Browse to: C:\Program Files (x86)\Raspberry Pi\drivers\
Install WinUSB driver

Easiest method: Just double-click rpi-mass-storage-gadget64.bat in C:\Program Files (x86)\Raspberry Pi\ to start mass storage mode automatically

Regards,
Amar

[Amar]

Hi,
rpiboot must be run from its installation directory, otherwise it fails to find the bootfiles even with the latest version.
First, verify rpiboot is installed correctly:

Check that rpiboot is installed at: C:\Program Files (x86)\Raspberry Pi\
Verify that bootfiles exist at: C:\Program Files (x86)\Raspberry Pi\mass-storage-gadget64\
The mass-storage-gadget64 folder should contain bootfiles.bin and subdirectories with boot code

If these files are missing or rpiboot is installed in a different location, this will cause path issues.

Code: Select all

cd "C:\Program Files (x86)\Raspberry Pi"
.\rpiboot.exe

Verify correct working directory:
The command prompt title should show: C:\WINDOWS\system32\cmd (or similar system path) when running from the correct location.

Do NOT:
Run rpiboot from a desktop shortcut
Run it from a different directory
Use custom working directories

This causes the error: "Directory not specified - trying default C:/Program Files (x86)/Raspberry Pi/mass-storage-gadget64/" and rpiboot will hang or fail to enumerate the device.
The command prompt title shows the current directory - make sure it shows the correct installation path, not something like "rpiboot-CM-CM2-CM3" or another custom folder name.

Regards,
Amar