Login doesn't work

[Kaduk]

I tried to log in to the RevPi using the username and password on the side of the RevPi, but the PuTTY terminal print "Access denied".

[dirk]

Hello Kaduk, How do you log in? Via SSH terminal or with USB keyboard and HDMI screen? Your keyboard layout depends on this and via USB log-in it is English (QWERTY). Does your password contain the characters 1, I or L? Unfortunately, they are almost identical to the font used so far. In case just try to switch them if you have them in the password on the label. If this does not work, restore the factory settings using the steps in this checklist - afterward you can log in to the device.

Revolution Pi Checklist

EDIT: If you are using the Public Beta Image "RevPi Bookworm OS" the login username is always "pi".
But if you are using another version, i.e. "RevPi Bullseye OS" there are two different usernames a) admin for the WebStatus Login and b) pi for the Shell or Secure Shell (SSH) login.

[ptthomps]

Hello Kaduk, How do you log in? Via SSH terminal or with USB keyboard and HDMI screen? Your keyboard layout depends on this and via USB log-in it is English (QWERTY). Does your password contain the characters 1, I or L? Unfortunately, they are almost identical to the font used so far. In case just try to switch them if you have them in the password on the label. If this does not work, restore the factory settings using the steps in this checklist - afterward you can log in to the device.

Revolution Pi Checklist

EDIT: If you are using the Public Beta Image "RevPi Bookworm OS" the login username is always "pi".
But if you are using another version, i.e. "RevPi Bullseye OS" there are two different usernames a) admin for the WebStatus Login and b) pi for the Shell or Secure Shell (SSH) login.

Hi Dirk. Is there a process for reinstalling the factory default image without using a windows computer? Our IT has restrictions on certain software, and the Win32 Disk Imager and rpiboot_setup.exe are both on the forbidden list. I do have access to other Raspberry Pi's though. Can the imaging be done with that?

[tboehler]

Hi ptthomps,

there is also a way to flash the RevPi using a Linux machine, i.e. a Raspberry Pi. Make sure to install rpiboot (e.g. through the package manager with "sudo apt install rpiboot") and download the image you want to install onto the Linux machine.

Run rpiboot with sudo, connect the RevPi with the Linux machine using a USB cable, power on the RevPi, and after a few seconds you should see some output from rpiboot. Wait until it's done, and there should be a new device in /dev (i.e. /dev/sda) with multiple partitions (i.e. /dev/sda1). You can also use "lsblk" to list the devices before rpiboot and after rpiboot, the newly added device after rpiboot ran will be the RevPi.

You can then either use software like the Raspberry Pi Imager or flash the RevPi on the command line. You can do this on the commandline with "sudo dd if=<path to image> of=<path to revpi device> status=progress && sync", where the argument to "of=" would be something like /dev/sda (make sure to check if you're using the correct path, otherwise data could be lost!). For example, if the image can be found in "/home/pi/250528-revpi-bookworm-arm64-lite.img" and the RevPi is "/dev/sda":

Code: Select all

sudo dd if=/home/pi/250528-revpi-bookworm-arm64-lite.img of=/dev/sda status=progress && sync

Hope this helps.

Cheers
Thomas

[ptthomps]

Hi ptthomps,

there is also a way to flash the RevPi using a Linux machine, i.e. a Raspberry Pi. Make sure to install rpiboot (e.g. through the package manager with "sudo apt install rpiboot") and download the image you want to install onto the Linux machine.

Run rpiboot with sudo, connect the RevPi with the Linux machine using a USB cable, power on the RevPi, and after a few seconds you should see some output from rpiboot. Wait until it's done, and there should be a new device in /dev (i.e. /dev/sda) with multiple partitions (i.e. /dev/sda1). You can also use "lsblk" to list the devices before rpiboot and after rpiboot, the newly added device after rpiboot ran will be the RevPi.

You can then either use software like the Raspberry Pi Imager or flash the RevPi on the command line. You can do this on the commandline with "sudo dd if=<path to image> of=<path to revpi device> status=progress && sync", where the argument to "of=" would be something like /dev/sda (make sure to check if you're using the correct path, otherwise data could be lost!). For example, if the image can be found in "/home/pi/250528-revpi-bookworm-arm64-lite.img" and the RevPi is "/dev/sda":

Code: Select all

sudo dd if=/home/pi/250528-revpi-bookworm-arm64-lite.img of=/dev/sda status=progress && sync

Hope this helps.

Cheers
Thomas

Hi Thomas, thank you for the reply. I've got my RevPi Connect 5 USB-C port connected to the USB-A 3.0 port of my raspberry pi 4b following the instructions you provided above. However, after I started rpiboot, and power on the RevPi, it never updates. Running lsblk before starting rpiboot, and a few minutes after starting rpiboot, then connecting and powering on the RevPi, the same devices are still listed. Please find the output from rpiboot below:

Code: Select all

rpiboot
RPIBOOT: build-date Dec 15 2022 version 20221215~105525 7aa7e758
Waiting for BCM2835/6/7/2711...

It's like the raspberry pi does not detect the RevPi as a usb disk. Output of cat /etc/os-release on the raspberry pi is as follows:

Code: Select all

cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Do you have any suggestions?

[ptthomps]

Hi ptthomps,

there is also a way to flash the RevPi using a Linux machine, i.e. a Raspberry Pi. Make sure to install rpiboot (e.g. through the package manager with "sudo apt install rpiboot") and download the image you want to install onto the Linux machine.

Run rpiboot with sudo, connect the RevPi with the Linux machine using a USB cable, power on the RevPi, and after a few seconds you should see some output from rpiboot. Wait until it's done, and there should be a new device in /dev (i.e. /dev/sda) with multiple partitions (i.e. /dev/sda1). You can also use "lsblk" to list the devices before rpiboot and after rpiboot, the newly added device after rpiboot ran will be the RevPi.

You can then either use software like the Raspberry Pi Imager or flash the RevPi on the command line. You can do this on the commandline with "sudo dd if=<path to image> of=<path to revpi device> status=progress && sync", where the argument to "of=" would be something like /dev/sda (make sure to check if you're using the correct path, otherwise data could be lost!). For example, if the image can be found in "/home/pi/250528-revpi-bookworm-arm64-lite.img" and the RevPi is "/dev/sda":

Code: Select all

sudo dd if=/home/pi/250528-revpi-bookworm-arm64-lite.img of=/dev/sda status=progress && sync

Hope this helps.

Cheers
Thomas

Hi Thomas, thank you for the reply. I've got my RevPi Connect 5 USB-C port connected to the USB-A 3.0 port of my raspberry pi 4b following the instructions you provided above. However, after I started rpiboot, and power on the RevPi, it never updates. Running lsblk before starting rpiboot, and a few minutes after starting rpiboot, then connecting and powering on the RevPi, the same devices are still listed. Please find the output from rpiboot below:

Code: Select all

rpiboot
RPIBOOT: build-date Dec 15 2022 version 20221215~105525 7aa7e758
Waiting for BCM2835/6/7/2711...

It's like the raspberry pi does not detect the RevPi as a usb disk. Output of cat /etc/os-release on the raspberry pi is as follows:

Code: Select all

cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Do you have any suggestions?

As an addendum, I've verified that two separate RevPi Connect 5's fail to be recognized as a drive when I try to follow the procedure. I've also tried with two separate cables, so I don't think it's a cable issue.

[ptthomps]

As another addendum, I was able to get rpiboot installed on my windows machine and it provided the output below. I think this indicates that it is an issue with the raspberry pi device I'm trying to use, rather than the RevPi or the cables. Unfortunately, I'm not able to run the imaging software on my windows laptop because it requires admin permissions, so I still need to figure out how to get the raspberry pi to work for this. Please let me know if anyone has any ideas. I think my next step is to find an RPi 5 and see if I can get that to work.

Code: Select all

USB mass storage gadget for Raspberry Pi 5
RPIBOOT: build-date 2025/05/19 pkg-version local 402baf02

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: mass-storage-gadget64/bootfiles.bin
Using mass-storage-gadget64/bootfiles.bin
Waiting for BCM2835/6/7/2711/2712...

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

Second stage boot server
File read: mcb.bin
File read: memsys00.bin
File read: memsys01.bin
File read: memsys02.bin
File read: memsys03.bin
File read: bootmain
Loading: mass-storage-gadget64/config.txt
File read: config.txt
Loading: mass-storage-gadget64/boot.img
File read: boot.img
Second stage boot server done

Raspberry Pi Mass Storage Gadget started
EMMC/NVMe devices should be visible in the Raspberry Pi Imager in a few seconds.
For debug, you can login to the device using the USB serial gadget - see COM ports in Device Manager.

Press a key to close this window.

[RamiGspo]

Hi ptthomps,

Thank you again for the detailed information.
Yes, to flash a RevPi Connect 5 successfully, it's important to use the latest version of rpiboot, as older versions do not support Raspberry Pi 5-based hardware and will fail to recognize the device.

From the output you provided, it looks like rpiboot is now working correctly — there are no errors, and the mass storage gadget has started successfully. This indicates that the device is ready to be flashed, and the issue is most likely not related to the hardware, USB cable, or the RevPi itself.

However, as you mentioned, flashing tools require administrator rights, since they need elevated permissions to access USB devices and perform low-level operations.

To proceed, you can follow Thomas’s recommendation from his earlier reply: you can either use software like the Raspberry Pi Imager, or flash the RevPi via the command line. In both cases, administrator permissions are required.

Let us know if you need help with this process or verifying the correct device path.

Best regards,

RamiGspo

[ptthomps]

Hi ptthomps,

Thank you again for the detailed information.
Yes, to flash a RevPi Connect 5 successfully, it's important to use the latest version of rpiboot, as older versions do not support Raspberry Pi 5-based hardware and will fail to recognize the device.

From the output you provided, it looks like rpiboot is now working correctly — there are no errors, and the mass storage gadget has started successfully. This indicates that the device is ready to be flashed, and the issue is most likely not related to the hardware, USB cable, or the RevPi itself.

However, as you mentioned, flashing tools require administrator rights, since they need elevated permissions to access USB devices and perform low-level operations.

To proceed, you can follow Thomas’s recommendation from his earlier reply: you can either use software like the Raspberry Pi Imager, or flash the RevPi via the command line. In both cases, administrator permissions are required.

Let us know if you need help with this process or verifying the correct device path.

Best regards,

RamiGspo

I was able to get rpiboot to work on the raspberry pi as well by doing

Code: Select all

sudo apt upgrade rpiboot

However, after running

Code: Select all

sudo dd if=/home/pi/250528-revpi-bookworm-arm64-lite.img of=/dev/sda status=progress && sync

, I tried booting up the RevPi with keyboard, mouse, and HDMI connected, but it is failing to find the disk image. I ran lsblk and I see that there appears to only be one partition on the RevPi.

Code: Select all

~/usbboot $ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda           8:0    1  29.1G  0 disk 
mmcblk0     179:0    0 119.1G  0 disk 
├─mmcblk0p1 179:1    0   256M  0 part /boot
└─mmcblk0p2 179:2    0 118.9G  0 part /

[ptthomps]

Ok, I figured it out mostly. Turns out I forgot to unzip the disk image, so when I did the dd command it just copied over the zip. The revpi boots now, and I was able to connect via the web interface.

So it looks like when using a raspberry pi 4b, the steps are as follows:

1. Download disk image
2. Unzip disk image
3. Install rpiboot on the Raspberry Pi 4b using

   Code: Select all

   sudo apt install rpiboot

4. Upgrade rpiboot on the Raspberry Pi 4b using

   Code: Select all

   sudo apt upgrade rpiboot

5. Run rpiboot on the Raspberry Pi 4b using

   Code: Select all

   sudo ./rpiboot -d mass-storage-gadget64

6. Connect RevPi to Raspberry Pi 4b using the USB-C port on the RevPi
7. Power on the RevPi
8. Wait for rpiboot on the Raspberry Pi 4b to finish mounting the RevPi
9. Use the Imager app on the Raspberry Pi 4b to write the image to the RevPi, OR run

   Code: Select all

   sudo dd if=/home/pi/Documents/250528-revpi-bookworm-arm64-default.zip of=/dev/sda status=progress && sync

   , modifying as necessary
10. Reboot the RevPi
11. Connect keyboard, mouse and monitor to RevPi
12. Login to RevPi using login: pi, password: raspberry
13. Reboot RevPi after it finishes configuring itself

It was a bit of a journey, but now I've got it back up and running. Thanks for the help, all.