Hi,
I just got a brand new Core3 32GB and I am trying to upload an image.
Bu the Rpiboot des not connect to the device, please find the info I get
Waiting for BCM2835/6/7/2711...
Sending bootcode.bin
Successful read 4 bytes
Waiting for BCM2835/6/7/2711...
I tried rebooting windows on "Disable driver signature enforcement", but it makes no good.
On device manager, I can see the Core 3 as " Universal bus devices : BCM2710"
Could anyone give me a hint ?
Thanks a lot.
Rpiboot not connecting
Hi gildas, this is unfortunately a common problem. Have a look at the FAQ at "I want to save or restore a system image. Why does RPiBoot.exe not connect to my device?"
https://revolution.kunbus.com/tutorials/faqs/
https://revolution.kunbus.com/tutorials/faqs/
-
- Posts: 58
- Joined: 03 Dec 2019, 10:29
Hy Dirk and gildas,
I have a similar problem with a brand new RevPi Connect+.
RPIBoot only shows:
"Waiting for BCM2835/6/7/2711..."
The device is indicated in the device manager as "Broadcom BCM2710 Boot".
Apparently, RPIBoot is not waiting for that device. I reinstalled RPIBoot according to your tutorials and also reinstalled the driver. Nothing worked yet.
Do you have further suggestions?
Best, Robert
I have a similar problem with a brand new RevPi Connect+.
RPIBoot only shows:
"Waiting for BCM2835/6/7/2711..."
The device is indicated in the device manager as "Broadcom BCM2710 Boot".
Apparently, RPIBoot is not waiting for that device. I reinstalled RPIBoot according to your tutorials and also reinstalled the driver. Nothing worked yet.
Do you have further suggestions?
Best, Robert
-
- Posts: 58
- Joined: 03 Dec 2019, 10:29
Dear all,
the problem was resolved by installing the newest guest additions to the VM I was using for windows.
Best, Robert
the problem was resolved by installing the newest guest additions to the VM I was using for windows.
Best, Robert
Hi Robert, thank you for your positive response. We'll add this to our FAQs.