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

    Firmware update bricked printer - SPI connection has been reset

    Scheduled Pinned Locked Moved
    Firmware installation
    6
    20
    842
    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.
    • p8blrundefined
      p8blr @p8blr
      last edited by

      @chrishamm how do I update to 3.5.3-rc.1 in sbc mode? Can you please send me the exact commands? I’ve tried all possible combinations and it doesn’t work. I updated in standalone mode, but when I connected my pi and tried to audio apt update/upgrade it downgraded my 6xd without asking me. I also have no way of manually updating DWC.

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

        @p8blr it looks like 3.5.3-rc1 isn't currently on the DSF package feed so you can't update to it in SBC mode

        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

        p8blrundefined 1 Reply Last reply Reply Quote 0
        • p8blrundefined
          p8blr @jay_s_uk
          last edited by

          @jay_s_uk Interesting. How did you check that so I know for future reference? Is there no manual way to update firmware in SBC mode?

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

            @p8blr was reported in the other thread. And you shouldn't manually update as there may be breaking changes between the firmware and DSF

            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

            1 Reply Last reply Reply Quote 0
            • timschneiderundefined
              timschneider @p8blr
              last edited by

              @p8blr was the extended delay able to get rid of the unknown driver messages?

              the M122 looks normal to me.

              p8blrundefined 1 Reply Last reply Reply Quote 0
              • p8blrundefined
                p8blr @timschneider
                last edited by

                @timschneider The delay didn't make a difference, however, changing the brake code to S10 from S1000 seems to have fixed that particular issue.

                M569.7 P0.2 C"out3" S10 ; driver 2 on board 6XD uses port out3 to control the brake
                M569.7 P0.3 C"out4" S10 ; driver 3 on board 6XD uses port out4 to control the brake
                M569.7 P0.4 C"out5" S10 ; driver 4 on board 6XD uses port out5 to control the brake
                M569.7 P0.5 C"out6" S10 ; driver 5 on board 6XD uses port out6 to control the brake

                Note that I was playing with increasing that value because my servos were getting position recovery errors.

                chrishammundefined 1 Reply Last reply Reply Quote 0
                • chrishammundefined
                  chrishamm administrators @p8blr
                  last edited by

                  @p8blr It's now available, looks like the GitHub Actions workflow for prereleases wasn't triggered correctly. Sorry for the inconvenience.

                  Duet software engineer

                  p8blrundefined 1 Reply Last reply Reply Quote 2
                  • p8blrundefined
                    p8blr @chrishamm
                    last edited by

                    @chrishamm Didn't work.
                    broken.jpg

                    Process:
                    Removed SD card from duet, connected RPI ribbon cable, powered on, M997 S2 F"unstable", sudo apt update, sudo apt full-upgrade

                    chrishammundefined 1 Reply Last reply Reply Quote 0
                    • chrishammundefined
                      chrishamm administrators @p8blr
                      last edited by

                      @p8blr /dev/gpiochip4 is correct for the Pi 5. Is it still the same board or did you replace it?

                      Duet software engineer

                      p8blrundefined 1 Reply Last reply Reply Quote 0
                      • p8blrundefined
                        p8blr @chrishamm
                        last edited by

                        @chrishamm Exact same board. I'll reimage the pi and try again.

                        chrishammundefined 1 Reply Last reply Reply Quote 0
                        • p8blrundefined p8blr referenced this topic
                        • chrishammundefined
                          chrishamm administrators @p8blr
                          last edited by

                          @p8blr If it's actually caused by a system update, don't use apt to install the latest system package versions, instead use M997 S2 only to update DSF. I'll investigate.

                          Duet software engineer

                          p8blrundefined oozeBotundefined 2 Replies Last reply Reply Quote 1
                          • p8blrundefined
                            p8blr @chrishamm
                            last edited by

                            @chrishamm new image with no updates works. M997 S2 F"unstable", M997 S2

                            1 Reply Last reply Reply Quote 1
                            • oozeBotundefined
                              oozeBot @chrishamm
                              last edited by

                              @chrishamm said in Firmware update bricked printer - SPI connection has been reset:

                              @p8blr If it's actually caused by a system update, don't use apt to install the latest system package versions, instead use M997 S2 only to update DSF. I'll investigate.

                              @chrishamm - any updates one what has caused this behavior to start happening? We hadn't noticed it until a recent apt upgrade (not Duet related). Are there workarounds to get this back on the command line? Thanks

                              chrishammundefined 1 Reply Last reply Reply Quote 0
                              • chrishammundefined
                                chrishamm administrators @oozeBot
                                last edited by

                                @oozeBot We have some more background information about the cause of this problem; it appears to affect the 6HC/6XD only. @dc42 is going to improve the upgrade mechanism in 3.6.0 stable.

                                Duet software engineer

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