Erased Firmware now I cannot connect via USB

droftarts

@meatfest Have you removed the jumper, then reset? Which Duet board are you using? I assume a 6HC?

Also, maybe your experience from a few years ago might help? https://forum.duet3d.com/post/152946

If you can find the Bossa port, see here for flashing firmware: https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware

Ian

meatfest

@droftarts Yes it is a 6HC, and I removed the erase jumper. I do not see a Bossa port...

meatfest

@meatfest 21 Jun 2024, 15:24

@Phaedrux Yes, I forgot about revealing hidden devices, I did that the Duet3 motion control electronics appeared in COM11 however it was not connected (greyed out). I am not sure what next step to take. At least the previous problem was solved but I am still unable to progress...

Phaedrux

In these cases it's usually a usb cable that isn't up to the task, or the usb port/controller on the pc isn't negotiating speeds correctly or not providing enough power.

I'd suggest trying different cables/ports or even a different PC.

A powered usb 3 hub has also helped people out in the past.

What was the original issue that prompted you to want to wipe the firmware in the first place?

meatfest

@Phaedrux Yes, but I have also tried another cable (both worked before I erased the board) and I use a powered hub as well. I will try and find another PC... Thanks for your suggestions, I hope I haven't messed up the Board...

Phaedrux

Very unlikely that the board has been damaged by wiping the firmware.

Follow along with this guide

https://docs.duet3d.com/en/User_manual/Troubleshooting/Duet_wont_respond

meatfest

@Phaedrux So, I suspected my Microsoft Windows 10 Dell laptop and removed all my personal files and rebuilt it. I installed driver files again from https://github.com/Duet3D/RepRapFirmware/blob/dev/Driver/WindowsDriverFiles.zip. I got the usual message after updating the USB driver with yellow triangle (right click, installed from the unzipped download (folder name WindowsDriverFiles) and it responded with "Unknown USB Device (Device Descriptor Request Failed). I have used the same USB cable that was working with YAT before I erased the DUet3 board. I use a powered USB hub. I see the little diag LED faintly lit, solid on, the bright red LED between USB socket and SD card and the green and red LEDs in the corner of the board on solid. Please can someone help?

dc42

@meatfest your 6HC firmware has been erased and the MCU is in Bossa mode waiting for a firmware upload. When in Bossa mode the USB port switched to high speed (a design choice that Microchip made). When in high speed mode it is very sensitive to the quality of the cable and the port it is connected to. So my advice is to try connecting it to different ports on your PC or laptop using different cables (never with an extension cable) until you find a combination that doesn't give you the Device Descriptor error message but instead makes the Bossa Port available on the PC. Then you will be able to use Bossa to install the firmware.

meatfest

@dc42 OK, good plan. I ordered a short (0.5M) USB cable with gold plated contacts. High transfer speed in spec... Hope it works, thanks for your kind help. I will post the results here.

oliof

@meatfest if you have USB 2 ports (black plastic inside) and USB 3 ports (blue plastic inside), by all means use the USB 3 ports.

zero K

@meatfest said in Erased Firmware now I cannot connect via USB:

@dc42 OK, good plan. I ordered a short (0.5M) USB cable with gold plated contacts. High transfer speed in spec... Hope it works, thanks for your kind help. I will post the results here.

Hi Meatfest

Not only a short wire ...
Have a look on diameter of the signaling wires.
Have a Look for AWG 24 or less - not AWG 26 or AWG 28 (American Wire Gauge - bigger number - less diameter)

Time ago I got an 1 m USB cabel with less than 0.1 mm (AWG 28 ?) - cheap but most useless.

Have a nice evening

meatfest

@zero-K My 0.5 gold plated chunky micro USB cable arrived this afternoon and solved the problem. If it's OK, I would like to suggest this solution, requirement, even be added to the Duet documentation. Also, @oliof USB3 or USB2 has nothing to do with the solution so please bear this in mind.

PROBLEM SOLVED.