• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login

No communication after erase button pressed

Scheduled Pinned Locked Moved
Firmware installation
firmware connectivity erase
3
25
3.6k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • undefined
    Spodeopieter
    last edited by 22 Apr 2018, 08:47

    Hello ,

    I have accidentally pressed the erase button on my duet3dwifi , It was working fine beforehand.

    I am trying to reinstall the firmware with SAM-BA , but I am not getting the device to show up as anything else than unknown usb device , have tried multiple cables and pc's.

    I have tried installing drivers from duet and from microchip, but I am still getting unknow device , will attach screenshots.

    0_1524386678312_Screenshot2.png 3_1524386686839_screenshot4.png 2_1524386686839_Screenshot3.png 1_1524386686839_Screenshot2.png 0_1524386686839_Screenshot1.png

    1 Reply Last reply Reply Quote 0
    • undefined
      dc42 administrators
      last edited by 22 Apr 2018, 09:22

      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.

      Duet WiFi hardware designer and firmware engineer
      Please do not ask me for Duet support via PM or email, use the forum
      http://www.escher3d.com, https://miscsolutions.wordpress.com

      undefined 2 Replies Last reply 22 Apr 2018, 12:36 Reply Quote 0
      • undefined
        Spodeopieter @dc42
        last edited by 22 Apr 2018, 12:36

        @dc42

        I am running the board without anything connected to it.

        1 Reply Last reply Reply Quote 0
        • undefined
          Spodeopieter @dc42
          last edited by 22 Apr 2018, 12:44

          @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 ?

          undefined 1 Reply Last reply 22 Apr 2018, 19:11 Reply Quote 0
          • undefined
            dc42 administrators
            last edited by 22 Apr 2018, 13:20

            Have you tried with and without VIN power applied?

            Duet WiFi hardware designer and firmware engineer
            Please do not ask me for Duet support via PM or email, use the forum
            http://www.escher3d.com, https://miscsolutions.wordpress.com

            undefined 1 Reply Last reply 22 Apr 2018, 17:56 Reply Quote 0
            • undefined
              Spodeopieter @dc42
              last edited by 22 Apr 2018, 17:56

              @dc42
              yes , I have tried this , it makes no difference.

              1 Reply Last reply Reply Quote 0
              • undefined
                dc42 administrators
                last edited by 22 Apr 2018, 18:29

                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.

                Duet WiFi hardware designer and firmware engineer
                Please do not ask me for Duet support via PM or email, use the forum
                http://www.escher3d.com, https://miscsolutions.wordpress.com

                undefined 1 Reply Last reply 22 Apr 2018, 18:48 Reply Quote 0
                • undefined
                  Spodeopieter @dc42
                  last edited by 22 Apr 2018, 18:48

                  @dc42

                  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.

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    dc42 administrators
                    last edited by 22 Apr 2018, 19:05

                    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?

                    Duet WiFi hardware designer and firmware engineer
                    Please do not ask me for Duet support via PM or email, use the forum
                    http://www.escher3d.com, https://miscsolutions.wordpress.com

                    undefined 1 Reply Last reply 22 Apr 2018, 19:16 Reply Quote 0
                    • undefined
                      denke @Spodeopieter
                      last edited by 22 Apr 2018, 19:11

                      @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

                      undefined 1 Reply Last reply 22 Apr 2018, 19:30 Reply Quote 0
                      • undefined
                        Spodeopieter @dc42
                        last edited by 22 Apr 2018, 19:16

                        @dc42

                        Yes , I have tried a few different cables.

                        Should I have the sd card inserted or not ?

                        undefined 1 Reply Last reply 22 Apr 2018, 19:26 Reply Quote 0
                        • undefined
                          dc42 administrators @Spodeopieter
                          last edited by 22 Apr 2018, 19:26

                          @spodeopieter said in No communication after erase button pressed:

                          @dc42

                          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.

                          Duet WiFi hardware designer and firmware engineer
                          Please do not ask me for Duet support via PM or email, use the forum
                          http://www.escher3d.com, https://miscsolutions.wordpress.com

                          undefined 2 Replies Last reply 22 Apr 2018, 19:34 Reply Quote 0
                          • undefined
                            Spodeopieter @denke
                            last edited by 22 Apr 2018, 19:30

                            @denke

                            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 device

                            lsusb

                            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

                            undefined 1 Reply Last reply 22 Apr 2018, 19:40 Reply Quote 0
                            • undefined
                              Spodeopieter @dc42
                              last edited by 22 Apr 2018, 19:34

                              @dc42

                              Noted. I have been trying without the SD card anyway, so what is the next step ?

                              1 Reply Last reply Reply Quote 0
                              • undefined
                                denke @Spodeopieter
                                last edited by denke 22 Apr 2018, 19:40

                                @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 port it means some general communication error, but either way it is worth a try

                                I, 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

                                undefined 1 Reply Last reply 22 Apr 2018, 19:55 Reply Quote 0
                                • undefined
                                  Spodeopieter @denke
                                  last edited by 22 Apr 2018, 19:55

                                  @denke

                                  Ok , so I just tried this , still no luck. I also tried running through usb isolator.

                                  1 Reply Last reply Reply Quote 0
                                  • undefined
                                    Spodeopieter @dc42
                                    last edited by 23 Apr 2018, 06:42

                                    @dc42

                                    So what are the next steps ?

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      dc42 administrators
                                      last edited by 23 Apr 2018, 08:08

                                      Which country are you in?

                                      Duet WiFi hardware designer and firmware engineer
                                      Please do not ask me for Duet support via PM or email, use the forum
                                      http://www.escher3d.com, https://miscsolutions.wordpress.com

                                      undefined 1 Reply Last reply 23 Apr 2018, 08:20 Reply Quote 0
                                      • undefined
                                        Spodeopieter @dc42
                                        last edited by 23 Apr 2018, 08:20

                                        @dc42

                                        I am in South Africa , Pretoria

                                        1 Reply Last reply Reply Quote 0
                                        • undefined
                                          dc42 administrators
                                          last edited by 23 Apr 2018, 08:33

                                          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.

                                          Duet WiFi hardware designer and firmware engineer
                                          Please do not ask me for Duet support via PM or email, use the forum
                                          http://www.escher3d.com, https://miscsolutions.wordpress.com

                                          1 Reply Last reply Reply Quote 0
                                          4 out of 25
                                          • First post
                                            4/25
                                            Last post
                                          Unless otherwise noted, all forum content is licensed under CC-BY-SA