Hey there,
I am currently using a Connect + 32GB Pi. I already installed the balena connect image on it. Now I want to reflash the Pi with the core image but my rpiboot did find the Pi and is stuck on "Waiting for BCM2835/6/7/2711..." even tho it is found in the device manager as an unknown device... (I am working with Win10)
I had the same problem with another Pi. Therefore, I reinstalled rpiboot and everything worked just fine.
I do not understand why my new Pi does not act the same...
Can someone please help me?
rpiboot doesn't find Pi
Hi ndavel, Interesting error picture and thanks for your details that it worked so far with a new installation of RPiBoot.exe.
I also have the following idea - try this RPiBoot checklist, which was created with great attention to detail:
https://kunbus-gmbh.atlassian.net/servi ... 2413494333
So far I can't say anything about Balena OS itself. However, writing to the eMMC memory should generally be possible.
You can use our good old Revolution Pi checklist:
https://kunbus-gmbh.atlassian.net/servi ... /836468748
Using these steps, it should be child's play to restore your device to the factory settings.
I also have the following idea - try this RPiBoot checklist, which was created with great attention to detail:
https://kunbus-gmbh.atlassian.net/servi ... 2413494333
So far I can't say anything about Balena OS itself. However, writing to the eMMC memory should generally be possible.
You can use our good old Revolution Pi checklist:
https://kunbus-gmbh.atlassian.net/servi ... /836468748
Using these steps, it should be child's play to restore your device to the factory settings.
Thank you dirk for your response but unfortunately, I still can't connect to my Pi via my PC.
I tried all the steps:
- I used another USB cable
- I tried the rpiboot via my WSL
- I used a coworker's notebook
- I made sure to use the latest version of rpiboot
- watchdog is deactivated
- I tried to work with this https://revolutionpi.com/tutorials/imag ... nd-stretch step-by-step
Nothing worked...
I flashed the Pi a lot in the past. Could that be the problem or does anyone have another idea?
I tried all the steps:
- I used another USB cable
- I tried the rpiboot via my WSL
- I used a coworker's notebook
- I made sure to use the latest version of rpiboot
- watchdog is deactivated
- I tried to work with this https://revolutionpi.com/tutorials/imag ... nd-stretch step-by-step
Nothing worked...
I flashed the Pi a lot in the past. Could that be the problem or does anyone have another idea?
Hi ndavel, What happens when you start up? What has changed?
Could it be that the 5 volts are not reaching the USB port and the device is booting instead of going into mode and waiting for a USB connection?
Would it be possible for you to connect an HDMI cable and a monitor?
Mechanical stresses on the micro USB port are of course also possible, causing one thing to lead to another and either the 5 volts are not present at the time of booting, which means that the device does not wait for a USB connection or, even worse, that the connection has a loose contact caused by fatigue of the plug connection.
Could it be that the 5 volts are not reaching the USB port and the device is booting instead of going into mode and waiting for a USB connection?
Would it be possible for you to connect an HDMI cable and a monitor?
Mechanical stresses on the micro USB port are of course also possible, causing one thing to lead to another and either the 5 volts are not present at the time of booting, which means that the device does not wait for a USB connection or, even worse, that the connection has a loose contact caused by fatigue of the plug connection.
