The Industrial Raspberry Pi Forum

I wanted to boot Revolution Pi Connect from USB because of the small amount of storage one it. I did like described in that forum article: https://revolutionpi.de/forum/viewtopic.php?t=1977
Now it boots on USB but my image on that wasn't working. I tried to put it on other USB sticks and drives but that changed nothing.
That meas the Revolution Pi is not booting at all now. It prints for interrupting boot: Anyway i wanted to reset the whole RevPi but i can't connect it to my Laptop aswell. I tried it like described here: https://revolutionpi.de/tutorials/image ... ufspielen/. RPIboot doesn't detect the device. I tried it with another RevPi aswell which is NOT booting from USB, there RPIboot is working.
How can I reset the RevPi so it is not booting from USB again, when i can't connect per RPIboot?? or how can ich fix that RPIboot recognize it?

Hi marvmilo,

please try the following:

• Download the latest version of rpiboot from https://github.com/raspberrypi/usbboot and check if it works
• Try another USB port / cable / system. In my experience a Linux system works often better when others fail

Nicolai

Hi Nicolai,

thank you for your fast answer.
I followed your steps. I don't have physical Linux machine at home except some normal Raspberry Pis so i used one of them. Same picture here RPIboot is not recognizing the RevPi and i can't see something in lsusb. I don't think this is a problem of RPIboot, the Cable or OS, since on all of them the other RevPi connection is working.
Is RPIboot the only way to connect to a RevPi?

Hi marvmilo,

there are several reports that the cable was the cause like this thread in German: viewtopic.php?f=8&t=186&sid=86233976ba9 ... 2&start=50 (TLDR: try a shorter cable of 0.5 m - 1 m). Please also describe your whole process from connecting the cable over powering the device etc.

Nicolai

Ok, that seems to have done the trick, thanks!

I did notice that the Revpi shipped with a jumper between the 0V terminal and the WD terminal. When I removed it the RevPi would boot loop every few minutes and when I put it back it stopped looping. What is the purpose of that jumper?

Thanks,
-Max

Hi Max,

this jumper must be connected if you don't want to use the integrated hardware watchdog. More details can be found in our tutorial: https://revolutionpi.com/tutorials/uebe ... rect=en_US

Nicolai

Hello,

even though is thread is from a long time ago, I'm running into a similar issue...

Apperently, my RevPi connect won't boot from the internal eMMC.
Trigger was updating to bullseye...
- tried first from Windows
- later also via linux with rpiboot dd
- later also via linux with rpiboot and rpi-imager
==> PWR, WD, REL are statically green; no blinking... eth links don't come up when adding a cable to a switch ... same for USB/ETH dongle...

When I mount the rootfs afterwards w/ rpiboot, I'm not seeing any evidence that the system ever started, i.e. no relevant entries in /var/boot

Did not yet check the HDMI output, as the ordered cable did not arrive yet.

==> is there anything else I can do to make the RevPi booting from the eMMC again?

Thanks
Thomas

Update: it turns out that flashing buster instead of bullseye did the trick.
Would be interested to know if I did something wrong...