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

    Duet 3 Standalone update from 3.3.0 to 3.4.0 failed

    Scheduled Pinned Locked Moved
    Firmware installation
    3
    7
    268
    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.
    • Ralmsundefined
      Ralms
      last edited by

      Hi there,

      For the first time I had an update fail on my Duet 3 board.

      I started on version 3.2.2 stable.
      I proceeded to update to 3.3 stable:

      1. I uploaded the Duet3_SDiap32_MB6HC.bin as instructed in the update notes.
      2. Next I uploaded the Duet2and3Firmware-3.2.zip, the upload went fine, the files were extracted and I was prompted if I wanted to apply the update, which I said yes.
      3. The update went successfully.

      Next, I proceeded to update to 3.4.0 stable the exact same way:

      1. I uploaded the Duet2and3Firmware-3.4.0.zip file, the upload went fine, the files were extracted and I was prompted if I wanted to apply the update, which I said yes.
      2. After this, I got the progress bar saying something around "waiting for the update" to complete.
      3. After 30 mins, I refreshed the page and is unresponsive.
      4. Check if the IP for Duet changed, which didn't.
      5. Next I proceeded to power cycle the the Duet and still, no new IP and unresponsive.
      6. When I look at the ethernet port, is like its not coming up, no lights.

      What can I do now to recover it?

      Thank you.

      dc42undefined jay_s_ukundefined 2 Replies Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators @Ralms
        last edited by

        @ralms is the DIAG led off, on, on but dim, or flashing?

        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

        Ralmsundefined 1 Reply Last reply Reply Quote 0
        • jay_s_ukundefined
          jay_s_uk @Ralms
          last edited by

          @ralms my guess is a bad flash and its gone into bossa mode. Plug a USB cable into it and see what comes up on the computer

          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

          Ralmsundefined 1 Reply Last reply Reply Quote 0
          • Ralmsundefined
            Ralms @dc42
            last edited by

            @dc42 Hey,

            If the DIAG Led is the one right next to the SD Card, its permanently on but dim, never flashes.

            1 Reply Last reply Reply Quote 0
            • Ralmsundefined
              Ralms @jay_s_uk
              last edited by

              @jay_s_uk And then what?

              What would be the expected behavior and what actions should be performed?

              jay_s_ukundefined 1 Reply Last reply Reply Quote 0
              • jay_s_ukundefined
                jay_s_uk @Ralms
                last edited by

                @ralms https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware#all-other-duet-boards
                fallback procedure 2 using bossa

                Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                Ralmsundefined 1 Reply Last reply Reply Quote 0
                • Ralmsundefined
                  Ralms @jay_s_uk
                  last edited by Ralms

                  @jay_s_uk said in Duet 3 Standalone update from 3.3.0 to 3.4.0 failed:

                  @ralms https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware#all-other-duet-boards
                  fallback procedure 2 using bossa

                  Well, after delaying this process for a few days, expecting a nightmare and headache knowing what to do, it was actually fairly painless.

                  After flashing the board with Bossa its back to working normally.

                  Just one suggestion regarding the documentation, the Bossa section is missing a last step just confirming that we are free to reset or disconnect the board from USB and use it normally.

                  Thank you.

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