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

firmware update failed

Scheduled Pinned Locked Moved
Beta Firmware
5
13
655
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
    TomW
    last edited by 4 Dec 2021, 20:47

    😢
    I did something to break my new Duet mini5+ while trying to update the (I think) v3.3 firmware up to the 3.4.0beta6.

    Firstly, what I have is a new RatRig vcore-3 "default" using an SBC (? raspberry pi4) connected as instructed. No modifications to the Duet SBC image, other than to install the read-only overlay package.. Connection to the SBC is via cat5 cable. The printer has been running great so far, with the exception of the M600 not working properly (endless loops of pause / resume on color changes).

    Side note: I'm well familiar with marlin + BTT + firmware.bin. I presumed that the bootloader / config / setup was pretty much the same: copy file up, reboot and re-flash..?

    So, reading the forum, I see that a change was made to the RRF whereas an issue with M600 + color change was corrected.

    I followed the firmware instructions on the Duet.com site. Followed the link to the latest firmware as I would be updating via DWC.

    As instructed, I downloaded the recommended latest stable release of Duet3Firmware_Mini5plus.uf2. I uploaded it via the DWC under System in the firmware tab.

    50 minutes later, nothing, the mini5+ has apparently been bricked? So, I did the unthinkable of power cycling both the SBC + Duet by removing AC power, and apply it again. Nothing, the SBC comes up but the DWC webpage from the SBC continually says "Failed to connect to Duet, check your connection (DCS is not started").

    Ok, how do I proceed from here? Remove the SBC and try the direct USB from PC connection?

    TIA

    undefined 1 Reply Last reply 4 Dec 2021, 21:11 Reply Quote 0
    • undefined
      PCR @TomW
      last edited by 4 Dec 2021, 21:11

      @tomw

      The 3 mini is super easy to "unbrick"
      https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Duet_3_Mini_5_WiFi_Ethernet

      undefined 1 Reply Last reply 4 Dec 2021, 21:15 Reply Quote 0
      • undefined
        TomW @PCR
        last edited by 4 Dec 2021, 21:15

        @pcr WHEW, thanks! My board did not come with an SD card, or I dropped it when putting this kit together, do I need to put a fresh 8G card in before doing the above procedure?

        undefined 1 Reply Last reply 4 Dec 2021, 21:53 Reply Quote 0
        • undefined
          PCR @TomW
          last edited by 4 Dec 2021, 21:53

          @tomw don't think so.

          undefined 1 Reply Last reply 5 Dec 2021, 02:59 Reply Quote 0
          • undefined
            TomW @PCR
            last edited by 5 Dec 2021, 02:59

            @pcr No good. The mini5+ is "alive", I can connect to it via minicom over USB. It responds to reprap commands (e.g. M115, M114) but do a G28X and it complains of "Homing file homex.g not found".

            Okay, at least it is "there", I have control over the board. It still won't allow the SBC to connect to it, "DCS is not started". So, that tells me that the SPI link is not operational?

            Nothing was disturbed on the wiring, this was a software breakage. <sigh> /me writes a lot of code.

            undefined 1 Reply Last reply 5 Dec 2021, 03:01 Reply Quote 0
            • undefined
              TomW @TomW
              last edited by 5 Dec 2021, 03:01

              @tomw OH, and I did re-image the Pi4 with 2021-07-12-DuetPi.img

              undefined 1 Reply Last reply 5 Dec 2021, 04:43 Reply Quote 0
              • undefined
                PCR @TomW
                last edited by 5 Dec 2021, 04:43

                @tomw do you have now a SD card in the mini 5? If yes remove it

                undefined 1 Reply Last reply 5 Dec 2021, 15:25 Reply Quote 0
                • undefined
                  Rushmere3D
                  last edited by Rushmere3D 12 May 2021, 08:10 5 Dec 2021, 08:10

                  This post is deleted!
                  1 Reply Last reply Reply Quote 0
                  • undefined
                    TomW @PCR
                    last edited by 5 Dec 2021, 15:25

                    @pcr FINALLY, I've been able to restore the machine back to v3.3! That was a lot of work. There appears to be a problem with the 3.4.0beta6 release, it will not load into my Duet Mini5+ (with 2 driver expansion). The board rev is v1.01, no wifi connected / configured, Raspberry Pi3 Model A+ on the SBC link running the 2021-07-12-DuetPi.img.

                    I've had to run the SBC (Pi) in multi-user mode instead of graphical. The desktop package loads the raspberry too heavily! Response to DWC console commands is sluggish, at best.

                    Now, the goal was to get the M600 command working correctly. Previously, with v3.3 of DWC, the M600 would force an endless loop of pause.g and resume.g, it would never resume printing.

                    So, let's try this again:

                    1. I have a working RatRig v-core 3 printer to start.
                    2. As per INSTALLING AND UPDATING FIRMWARE, it instructs me to download "Download firmware zip bundle (named Duet2and3Firmware-3.xxx.zip)" ... There is no such file?

                    Apparently the instructions are in error or a file is missing or I'm following the wrong set of instructions?

                    This should be much easier to do. I've uploaded that 3.4.0beta6 several times into DWC firmware section and bricked the controller each time. Getting the controller back to v3.3 has required a fresh copy of the 2021-07-12-DuetPi.img into the SBC, crossed my fingers and uploaded the original Duet3Firmware_Mini5plus.uf2 via the USB cable.

                    undefined 1 Reply Last reply 5 Dec 2021, 15:30 Reply Quote 0
                    • undefined
                      Stephen6309 @TomW
                      last edited by Stephen6309 12 May 2021, 15:32 5 Dec 2021, 15:30

                      @tomw When using a Raspberry PI. all updates must be doen with sudo apt update and sudp apt upgrade. To use the current beta version switch to unstable. I use PuTTY to acces the PI.
                      https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Software_Installation

                      undefined 1 Reply Last reply 5 Dec 2021, 15:42 Reply Quote 2
                      • undefined
                        TomW @Stephen6309
                        last edited by 5 Dec 2021, 15:42

                        @stephen6309 Thank you Stephen, it worked a charm! Now running 3.4-b6. It is always something stupid, usually me 😕

                        undefined 1 Reply Last reply 5 Dec 2021, 15:48 Reply Quote 0
                        • undefined
                          droftarts administrators @TomW
                          last edited by 5 Dec 2021, 15:48

                          @tomw somewhere on the updating firmware page, it says that firmware update is different if you use an SBC, and links to those instructions (on phone, too hard to see!). It also says that only release versions of firmware have the full zip file; beta and RC versions do not. It seems both of these points need to be a bit clearer!

                          Ian

                          Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                          1 Reply Last reply Reply Quote 0
                          • undefined
                            TomW
                            last edited by 5 Dec 2021, 16:43

                            M600 is now properly processed within the gcode stream. 🙂

                            I write code and know how hard it is write for another audience. It is hard to write "down to" someone less familiar with the given task. Yes, it is confusing.

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