No communication after erase button pressed
-
The "Device Descriptor request failed" message indicates that Windows failed to fetch the information from the Duet. Quite often this is because Windows has got the port into a funny state. Please try the following:
-
If you are running the Duet from USB power only, disconnect any devices from it that draw a lot of current, e.g. PanelDue. Alternatively, make sure you are providing 12V or 24V power before you connect the USB cable - but see the wiki page on USB ground loops.
-
Press the Erase button again for 1 second, then press the Reset button.
-
Try another USB port on your PC. If you don't have one, reboot Windows.
-
-
I am running the board without anything connected to it.
-
@dc42
Also I have tried the usb ports of ,multiple windows 10 PC's , all with the same issue.
Also tried a Linux pc , no luck.
Should I try a windows 7 pc perhaps?Perhaps reflash over jtag would be an option ?
-
Have you tried with and without VIN power applied?
-
@dc42
yes , I have tried this , it makes no difference. -
If the following are true:
- you have already tried pressing Erase again for one second followed by Reset as I suggested earlier;
- you always get the "Device Descriptor Request Failed" message (not "Unknown device")
then if your Duet is still under warranty, ask for it to be replaced.
-
Both of those are true. What does this mean happened ?
My duet is no longer under warranty.
I would be quite disappointed and angry if I should buy a new one.
-
If all you did to create the problem was to press the Erase button, then it should be possible to reprogram it. Have you tried a different USB cable?
-
@spodeopieter said in No communication after erase button pressed:
Also tried a Linux pc , no luck.
It might be helpful if you included the dmesg part around the time you plugged it in, and an lsusb after you plugged it in
-
-
@spodeopieter said in No communication after erase button pressed:
Yes , I have tried a few different cables.
Should I have the sd card inserted or not ?
It doesn't matter, unless the SD card is faulty and drawing a large current from the 3.3V rail.
-
Dmesg
[846482.444916] usb 3-6: new full-speed USB device number 33 using xhci_hcd
[846482.556934] usb 3-6: device descriptor read/64, error -71
[846482.772945] usb 3-6: device descriptor read/64, error -71
[846482.988898] usb 3-6: new full-speed USB device number 34 using xhci_hcd
[846483.100971] usb 3-6: device descriptor read/64, error -71
[846483.316940] usb 3-6: device descriptor read/64, error -71
[846483.532862] usb 3-6: new full-speed USB device number 35 using xhci_hcd
[846483.533051] usb 3-6: Device not responding to setup address.
[846483.736958] usb 3-6: Device not responding to setup address.
[846483.940851] usb 3-6: device not accepting address 35, error -71
[846484.052817] usb 3-6: new full-speed USB device number 36 using xhci_hcd
[846484.053010] usb 3-6: Device not responding to setup address.
[846484.257021] usb 3-6: Device not responding to setup address.
[846484.460791] usb 3-6: device not accepting address 36, error -71
[846484.460831] usb usb3-port6: unable to enumerate USB device
[846508.071353] usb 3-6: new full-speed USB device number 37 using xhci_hcd
[846508.183413] usb 3-6: device descriptor read/64, error -71
[846508.399383] usb 3-6: device descriptor read/64, error -71
[846508.615249] usb 3-6: new full-speed USB device number 38 using xhci_hcd
[846508.727321] usb 3-6: device descriptor read/64, error -71
[846508.943313] usb 3-6: device descriptor read/64, error -71
[846509.159258] usb 3-6: new full-speed USB device number 39 using xhci_hcd
[846509.159404] usb 3-6: Device not responding to setup address.
[846509.363394] usb 3-6: Device not responding to setup address.
[846509.567269] usb 3-6: device not accepting address 39, error -71
[846509.679246] usb 3-6: new full-speed USB device number 40 using xhci_hcd
[846509.679451] usb 3-6: Device not responding to setup address.
[846509.883424] usb 3-6: Device not responding to setup address.
[846510.087244] usb 3-6: device not accepting address 40, error -71
[846510.087315] usb usb3-port6: unable to enumerate USB devicelsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 04ca:7022 Lite-On Technology Corp.
Bus 003 Device 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader
Bus 003 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 012: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter
Bus 003 Device 006: ID 0e8d:763e MediaTek Inc. MT7630e Bluetooth Adapter
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -
Noted. I have been trying without the SD card anyway, so what is the next step ?
-
@spodeopieter said in No communication after erase button pressed:
device descriptor read/64, error -71
Did some digging,
and red that this message usually means that the device has exceeded the current limit of the portit means some general communication error, but either way it is worth a tryI, provided I have a notebook, would try to remove the sdcard, give the panel external 12/24v power, unplug the notebook from the charger and any other device connected to the mains voltage, and try the connection that way.
And / or an usb cable with multiple computer side connectors used by some mobile hdds.
I really do not know if it would help, but it is worth a try
-
Ok , so I just tried this , still no luck. I also tried running through usb isolator.
-
So what are the next steps ?
-
Which country are you in?
-
I am in South Africa , Pretoria
-
Unless you have someone local to you who may be able to diagnose the board, your best option may be to arrange with forum user W3DRK to send the board to him (he is in the US) and take a look at it. he is experienced at diagnosing and repairing Duets.
-
Can you assist me with a jtag reflash ?