Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Instructions on rolling back to 3.2b1?

    Beta Firmware
    6
    17
    345
    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.
    • oozeBot
      oozeBot last edited by oozeBot

      Can someone please assist with instructions on fully rolling back to 3.2b1? I need to roll back to do some testing prior to reporting an issue I'm having with G30 on 3.2b2 with a connected toolboard.

      This is needed for a Duet3/RPi combo..

      Thanks

      1 Reply Last reply Reply Quote 0
      • Luke'sLaboratory
        Luke'sLaboratory last edited by

        https://github.com/DanalEstes/DuetVersions

        Should work!

        Luke
        http://lukeslab.online

        1 Reply Last reply Reply Quote 1
        • oozeBot
          oozeBot last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • oozeBot
            oozeBot last edited by

            Thanks! Here is what is returned for the previous betas:

            DSF V3.2.0-beta1+1 DWC 3.2.0-beta1+2 RRF 3.2-beta1
            DSF V3.2.0-beta1 DWC 3.2.0-beta1+1 RRF 3.2-beta1
            

            Here is my command to regress the build:

            sudo apt -y --allow-downgrades install duetsoftwareframework=3.2.0-beta1+1 duetcontrolserver=3.2.0-beta1+1 duetruntime=3.2.0-beta1+1 duetsd=1.0.6 duettools=3.2.0-beta1+1 duetwebcontrol=3.2.0-beta1+2 duetwebserver=3.2.0-beta1 reprapfirmware=3.2-beta1
            

            And here is what is returned - everything is found except for rrf 3.2b1..

            Version '3.2-beta1' for 'reprapfirmware' was not found
            

            Note I've tried both "3.2-beta1" and "3.2-beta1" for rrf, but neither are found.. I'm not sure why as it lists RRF as 3.2beta1. If anyone has any ideas, please let me know.

            1 Reply Last reply Reply Quote 0
            • A Former User
              A Former User last edited by

              you could always use M997 to update the firmware after manually downloading the 3.2b1 binary to /opt/dsf/sd/sys/ and let apt deal with all the other packages?

              sudo apt -y --allow-downgrades install duetsoftwareframework=3.2.0-beta1+1 duetcontrolserver=3.2.0-beta1+1 duetruntime=3.2.0-beta1+1 duetsd=1.0.6 duettools=3.2.0-beta1+1 duetwebcontrol=3.2.0-beta1+2 duetwebserver=3.2.0-beta1
              sudo wget -O /opt/dsf/sd/sys/Duet3Firmware_MB6HC.bin https://github.com/Duet3D/RepRapFirmware/releases/download/3.2beta1/Duet3Firmware_MB6HC.bin
              echo M997 | sudo /opt/dsf/bin/CodeConsole
              

              (not sure what the latest on file system permssions are, you might not need sudo for line 2 and 3(

              oozeBot 1 Reply Last reply Reply Quote 0
              • oozeBot
                oozeBot @Guest last edited by oozeBot

                @bearer thanks! but it's throwing dependency errors.. ugh. I'll keep plugging away at it, but if anyone knows of a clean solution, please let me know before I just roll back to 3.1.1..

                1 Reply Last reply Reply Quote 0
                • oozeBot
                  oozeBot last edited by

                  I wasn't thinking clearly as I just realized I could clone one of my other machine's sd cards to get me back to 3.2b1.. After getting back setup with the exact same configs, G30 began working again. There appears to be something wrong with G30 when connected to a toolboard on 3.2b2..

                  I'll do more testing and report back

                  A Former User 1 Reply Last reply Reply Quote 0
                  • A Former User
                    A Former User @oozeBot last edited by

                    @oozeBot said in Instructions on rolling back to 3.2b1?:

                    I wasn't thinking clearly as I just realized I could clone one of my other machine's sd cards to get me back to 3.2b1..

                    you'd have to run M997 to flash the duet if you haven't already.

                    oozeBot 1 Reply Last reply Reply Quote 0
                    • oozeBot
                      oozeBot @Guest last edited by

                      @bearer yes- got that part right..! Thanks!

                      1 Reply Last reply Reply Quote 0
                      • gloomyandy
                        gloomyandy last edited by

                        Do anyone come up with a way of installing/rolling back to 3.2b1 on the SBC? It would be very useful to be able to do this to check for changes between beta1/beta2.

                        1 Reply Last reply Reply Quote 0
                        • jay_s_uk
                          jay_s_uk last edited by

                          This is also an issue for LPC/STM users who have accidentally upgraded or want to move over to the from 3.1.1.
                          We currently haven't released beta 2 builds as the changes are still being merged in.
                          I've tried to roll back using a number of version numbers but have been unable to do so.
                          Is this one for @chrishamm to look at?

                          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
                          • chrishamm
                            chrishamm administrators last edited by

                            To downgrade to 3.2-b1 you must install RRF 3.2-b1 first, because the protocol version has been increased and older DSF versions cannot communicate with it. To do that, download the corresponding firmware binary from GitHub, upload it on the System page, and install it.

                            Then open a terminal on the SBC (e.g. via SSH) and run the following command with the right software version (3.2.0-beta1 is what you want instead of 3.1.1):

                            apt-get install duetsoftwareframework=3.1.1 duetcontrolserver=3.1.1 duetsd=1.0.6 duettools=3.1.1 duetwebserver=3.1.0 duetwebcontrol=3.1.1 reprapfirmware=3.1.1-1 duetruntime=3.1.1
                            

                            Please note that the RRF package has an extra suffix after the software version (-1, may vary).

                            Duet software engineer

                            1 Reply Last reply Reply Quote 2
                            • jay_s_uk
                              jay_s_uk last edited by

                              @chrishamm said in Instructions on rolling back to 3.2b1?:

                              3.2.0-beta1

                              that still doesn't work. I can roll back to 3.1.1 but I can't roll forwards to 3.2.0-beta1.
                              This is what I am trying to run

                              sudo apt-get install duetsoftwareframework=3.2.0-beta1+1 duetcontrolserver=3.2.0-beta1+1 duetsd=1.0.7 duettools=3.2.0-beta1+1 duetwebserver=3.2.0-beta1 duetwebcontrol=3.2.0-beta1+2 reprapfirmware=3.2.0-beta1+1-1 duetruntime=3.2.0-beta1+1
                              

                              And I still get and unmet dependency for duetwebserver. See the output below

                              Reading package lists... Done
                              Building dependency tree
                              Reading state information... Done
                              Some packages could not be installed. This may mean that you have
                              requested an impossible situation or if you are using the unstable
                              distribution that some required packages have not yet been created
                              or been moved out of Incoming.
                              The following information may help to resolve the situation:
                              
                              The following packages have unmet dependencies:
                               duetwebserver : Depends: duetcontrolserver (>= 3.2.0-beta2) but 3.2.0-beta1+1 is to be installed
                                               Depends: duetruntime (>= 3.2.0-beta2) but 3.2.0-beta1+1 is to be installed
                              E: Unable to correct problems, you have held broken packages.
                              

                              How can a beta1 release be dependent on beta2?

                              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

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

                                @jay_s_uk Hmm right, I must have overwritten the old DWS package accidentally which caused this error. I just rebuilt b1 and b2 and updated the packages on the server. Try to run sudo apt-get update once again and then downgrade the packages using your command line. If it still doesn't work, remove the downloaded deb files from /var/cache/apt/archives and try again.

                                Duet software engineer

                                jay_s_uk oozeBot 2 Replies Last reply Reply Quote 0
                                • jay_s_uk
                                  jay_s_uk @chrishamm last edited by

                                  @chrishamm that works now, thank you

                                  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
                                  • A Former User
                                    A Former User last edited by

                                    Phew, I thought I was going bonkers .. probably are, but at least not with apt:)

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

                                      @chrishamm Thank you for the assist! I'm glad to see it wasn't my ignorance with Linux causing the issue..!

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