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.8k
    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.
    • Spodeopieterundefined
      Spodeopieter @dc42
      last edited by

      @dc42

      Yes , I have tried a few different cables.

      Should I have the sd card inserted or not ?

      dc42undefined 1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators @Spodeopieter
        last edited by

        @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

        Spodeopieterundefined 2 Replies Last reply Reply Quote 0
        • Spodeopieterundefined
          Spodeopieter @denke
          last edited by

          @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

          denkeundefined 1 Reply Last reply Reply Quote 0
          • Spodeopieterundefined
            Spodeopieter @dc42
            last edited by

            @dc42

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

            1 Reply Last reply Reply Quote 0
            • denkeundefined
              denke @Spodeopieter
              last edited by denke

              @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

              Spodeopieterundefined 1 Reply Last reply Reply Quote 0
              • Spodeopieterundefined
                Spodeopieter @denke
                last edited by

                @denke

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

                1 Reply Last reply Reply Quote 0
                • Spodeopieterundefined
                  Spodeopieter @dc42
                  last edited by

                  @dc42

                  So what are the next steps ?

                  1 Reply Last reply Reply Quote 0
                  • dc42undefined
                    dc42 administrators
                    last edited by

                    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

                    Spodeopieterundefined 1 Reply Last reply Reply Quote 0
                    • Spodeopieterundefined
                      Spodeopieter @dc42
                      last edited by

                      @dc42

                      I am in South Africa , Pretoria

                      1 Reply Last reply Reply Quote 0
                      • dc42undefined
                        dc42 administrators
                        last edited by

                        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
                        • Spodeopieterundefined
                          Spodeopieter
                          last edited by

                          Can you assist me with a jtag reflash ?

                          Spodeopieterundefined 1 Reply Last reply Reply Quote 0
                          • Spodeopieterundefined
                            Spodeopieter @Spodeopieter
                            last edited by

                            @dc42

                            Reliable shipping to USA and back would cost me quite a bit of money. Buying a new one would be a better bet for me.

                            I would really like to give the JTAG reflash a go.

                            What programmer do you use for flashing over JTAG ? and can you provide me with a wiring diagram ? Also , what binary should I flash ?

                            1 Reply Last reply Reply Quote 0
                            • dc42undefined
                              dc42 administrators
                              last edited by

                              We have never flashed a board using JTAG, we flash using USB.

                              The symptoms you report are odd and it sounds to me more like a wiring or driver issue, except that you have tried multiple PCs. Have you measured the voltage on the +3.3V rail? Is any of the chips or the WiFi module on the Duet getting hot?

                              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

                              Spodeopieterundefined 1 Reply Last reply Reply Quote 0
                              • Spodeopieterundefined
                                Spodeopieter @dc42
                                last edited by

                                @dc42 said in No communication after erase button pressed:

                                cept that you have tried multiple PCs. Have you measured the voltage on the +3.3V rail? Is any of the chips or the WiFi module on the Duet getting hot?

                                3.3 v rail seems good , the SAM chip is getting a little hot , around 40 degrees , the esp is ice cold.

                                Just another thing I noticed , if I press the erase or reset button , nothing happens , no flashing of any LED's

                                dc42undefined 1 Reply Last reply Reply Quote 0
                                • dc42undefined
                                  dc42 administrators @Spodeopieter
                                  last edited by

                                  @spodeopieter said in No communication after erase button pressed:

                                  3.3 v rail seems good , the SAM chip is getting a little hot , around 40 degrees , the esp is ice cold.

                                  Just another thing I noticed , if I press the erase or reset button , nothing happens , no flashing of any LED's

                                  The SAM shouldn't get hot if it's just waiting to be flashed. Perhaps it is faulty.

                                  Once the chip is erased and waiting to be bootloaded, I wouldn't expect the Erase or Reset buttons to flash any LEDs.

                                  It's possible in theory to program the processor via the PanelDue port (and for the same reason, having a PanelDue connected might interfere with programming over USB, although in practice it doesn't seem to). You would need Bossa or SAM-BA and a serial-to-UART converter with 3.3V signal levels.

                                  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
                                  • First post
                                    Last post
                                  Unless otherwise noted, all forum content is licensed under CC-BY-SA