Rev Pi Connect issue

[JoshuaP]

I have not been able to access my Rev Pi connect (PR100274) via its web interface or by USB boot. The lights on the front turn on (PWR, WD and REL all light up green and A1 is a faint red), but I don't see it when scanning the local network ranges 10.56.0.0/16 (company sub-net), 192.168.0.0/16 and 169.254.0.0/16. So I attempted to connect via USB. When running rpiboot from windows 10 I receive a warning that the device is not working and in the device manager it is listed with Unknown USB Device (Device Descriptor Request Failed), This happens on all USB ports and multiple cables.

From the rpiboot.exe console:
Waiting for BCM2835/6/7/2711...
Loading embedded: bootcode.bin
Sending bootcode.bin
Successful read 4 bytes
Waiting for BCM2835/6/7/2711...
Loading embedded: bootcode.bin

After this I attempted to use rpiboot from a second Pi (3b+) and received the same errors. When using verbose mode I receive the following:

$ sudo ./rpiboot -v
RPIBOOT: build-date Jan 14 2022 version 20220111~130126 97f618fc
Waiting for BCM2835/6/7/2711...
Loading embedded: bootcode.bin
Device located successfully
Initialised device correctly
Found serial number 0
Sending bootcode.bin
libusb_bulk_transfer sent 24 bytes; returned 0
Writing 52456 bytes
libusb_bulk_transfer sent 52456 bytes; returned 0
libusb: error [udev_hotplug_event] ignoring udev action bind
Successful read 4 bytes
Waiting for BCM2835/6/7/2711...
Loading embedded: bootcode.bin
Device located successfully
Failed to open the requested device

The dmesg from this event is as follows:

[10620.827306] usb 1-1.5: new high-speed USB device number 19 using dwc_otg
[10620.957741] usb 1-1.5: config index 0 descriptor too short (expected 55, got 32)
[10620.958128] usb 1-1.5: New USB device found, idVendor=0a5c, idProduct=2764, bcdDevice= 0.00
[10620.958141] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[10620.958150] usb 1-1.5: Product: BCM2710 Boot
[10620.958160] usb 1-1.5: Manufacturer: Broadcom
[10624.267737] usb 1-1.5: USB disconnect, device number 19
[10624.567330] usb 1-1.5: new full-speed USB device number 20 using dwc_otg
[10639.827412] usb 1-1.5: device descriptor read/64, error -110
[10655.187501] usb 1-1.5: device descriptor read/64, error -110
[10655.407498] usb 1-1.5: new full-speed USB device number 21 using dwc_otg
[10670.627584] usb 1-1.5: device descriptor read/64, error -110
[10685.987670] usb 1-1.5: device descriptor read/64, error -110
[10686.107863] usb 1-1-port5: attempt power cycle
[10686.767672] usb 1-1.5: new full-speed USB device number 22 using dwc_otg
[10697.087767] usb 1-1.5: device descriptor read/8, error -110
[10702.287789] usb 1-1.5: device descriptor read/8, error -110
[10702.507756] usb 1-1.5: new full-speed USB device number 23 using dwc_otg
[10712.847852] usb 1-1.5: device descriptor read/8, error -110
[10718.047873] usb 1-1.5: device descriptor read/8, error -110
[10718.168052] usb 1-1-port5: unable to enumerate USB device

I don't think this is a USB power issue (I assume the Rev Pi doesn't try to pull power via the micro usb on the front).

Any ideas about whats going on here orother things to try?

[dirk]

Dear JoshuaP, thank you very much for the inquiry and the detailed report. This is impressive and detailed. Problems can often be traced back to USB which are manifold. The following checklist can help you to fix the problems in a structured way:

RevolutionPi USB Checklist

You just have to register with your E-Mail address to access it.
The registration page is currently in German language only so here is a short animation how it works:

[JoshuaP]

Thanks for the reply Dirk. I was able to make an account and see that page without issue. I have still not been able to interact with the RevPi. I have switched to a short USB cable (that I have used for both power and program other devises so I know the wires are intact), I also tried using different USB ports on the Raspberry Pi (3b+) that I am using to flash the RevPi. The rpiboot software on the 3b+ is build new as of a few days ago so its not an old version.

The new information I have is that when I plug in a screen to the RevPi I don't get a signal (no prompt or anything). Also in contrast to this thread (viewtopic.php?f=4&t=3101&p=10999#p10999) my flashing process never gives me the "Second stage boot server" message, I don't know how relevant that is to my issue.

[crismancich]

Hi JoshuaP,

thanks for testing this. The easiest way to see if the flashing works would be to flash another RevPi - or is it the only RevPi yopu have at hand?
Can you use a display and see if its booting up properly?

[JoshuaP]

Unfortunately this is the only RevPi I have. I did try a screen but it did not show any display, and goes into sleep mode so I don't think there is any signal.