Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    [ARCHIVED] Downgrading firmware (advanced users)

    Scheduled Pinned Locked Moved Announcements & News
    firmware
    24 Posts 16 Posters 18.6k Views 19 Watching
    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.
    • K Offline
      Knoahlr @abilio
      last edited by

      @abilio Which firmware version was the last to properly support ssl? And will dowgrading firmware using updater.py erase any files?

      1 Reply Last reply Reply Quote 1
      • U Offline
        ubiq_01 Pybytes Beta
        last edited by

        for me 0.9.7.b1 works with SSL (including certificate based client auth). It did not erase files when I downgraded with the respective installer - I diid nevertheless save files via FTP before - just to be sure.

        best regards
        Ralf

        1 Reply Last reply Reply Quote 0
        • T Offline
          toribios_people
          last edited by

          Trying to downgrade on windows I get the following error, any idea why? Thanks.

          C:\pyupgrade>c:\python27\python bin\updater.py -t 1.2.2.b1-WiPy.tar.gz -p COM8
          Namespace(file=None, port='COM8', speed=115200, tar='1.2.2.b1-WiPy.tar.gz')
          Connecting...
          Uploading stub...
          Running stub...
          Stub running...
          Changing baud rate to 115200
          Changed.
          Exception: Error -3 while decompressing: invalid stored block lengths, on line 131

          S 1 Reply Last reply Reply Quote 1
          • S Offline
            sakis @toribios_people
            last edited by

            @toribios_people

            It could be a corrupted file, a Windows-specific issue, or something else...

            I just downgraded from the latest version (1.4.0.b1) to 1.1.0.b1 on macOS and it worked flawlessly.

            I'd advice you to retry and if it still fails try doing it on Linux to see if it's Windows-specific. That way we can try to resolve it.

            K T 2 Replies Last reply Reply Quote 0
            • K Offline
              Knoahlr @sakis
              last edited by

              @sakis seem to be getting the same error code as @toribios_people
              I`m also doing this from a windows machine.

              Namespace(file=None, port='COM7', speed=115200, tar='1.1.0.b1-WiPy.tar.gz')
              Connecting...
              Uploading stub...
              Running stub...
              Stub running...
              Changing baud rate to 115200
              Changed.
              Exception: Error -3 while decompressing: invalid literal/length code, on line 124

              1 Reply Last reply Reply Quote 0
              • L Offline
                livius
                last edited by livius

                i try downgrade my wipy to version 1.3.0.b1 but - on Windows 10 64 bit:

                C:\Program Files (x86)\Pycom\Pycom Firmware Update\Python27\pyupgrade>"C:\Program Files (x86)\Pycom\Pycom Firmware Update\Python27\python" "bin\updater.py" -t WiPy.tar.gz -p COM3
                Namespace(file=None, port='COM3', speed=115200, tar='WiPy.tar.gz')
                Connecting...
                Uploading stub...
                Running stub...
                Stub running...
                Changing baud rate to 115200
                Changed.
                Exception: Error -3 while decompressing: invalid stored block lengths, on line 131
                

                think about people first, then computers

                1 Reply Last reply Reply Quote 0
                • T Offline
                  toribios_people @sakis
                  last edited by

                  @sakis I have tried with linux through VirtualBox and I don't get that error any more, althought the flashing process is not very stable. Took me 6 attempts to get the WiPy flashed, on the other 5 I got this error at ramdom completion percentages:

                  Writing at 0x0009400... (80%) Exception: Failed to write compressed data to flash after seq 33 (result was 0xc1, 0x0), on line 132

                  Maybe the problem is beacuse of flashing it through a virtual machine.

                  S 1 Reply Last reply Reply Quote 0
                  • S Offline
                    sakis @toribios_people
                    last edited by

                    @toribios_people

                    That could be the case (usage of VM). Thanks all for the testing, it seems that this is a Windows-specific issue. I'll report it to our firmware updater expert.

                    1 Reply Last reply Reply Quote 0
                    • A Offline
                      abilio
                      last edited by

                      @toribios_people, @sakis, @Knoahlr, @livius, the problem for (up/downgrading) versions 1.0.0.b1 and higher under Windows should be fixed now.

                      Can you please download the latest version of the tool, retry the procedure and post your feedbacks?

                      S 1 Reply Last reply Reply Quote 0
                      • S Offline
                        Shaun @abilio
                        last edited by

                        @abilio
                        The latest updater on Windows 7 worked for me.
                        No more:
                        Exception: Error -3 while decompressing: invalid literal/length code, on line 124

                        1 Reply Last reply Reply Quote 0
                        • T Offline
                          toribios_people
                          last edited by

                          Works fine here as well, with Windows 10.

                          1 Reply Last reply Reply Quote 0
                          • P Offline
                            PCA @abilio
                            last edited by

                            @abilio Where can we find 1.4.0 and 1.5.1.b1 releases ?
                            Thanks
                            Pascal

                            A 1 Reply Last reply Reply Quote 0
                            • A Offline
                              abilio @PCA
                              last edited by abilio

                              @PCA, just upgraded the original list up to the last release :)

                              1 Reply Last reply Reply Quote 0
                              • C Offline
                                Colateral
                                last edited by

                                Updater Version 1.1.1 on LopY doesn't work anymore

                                d:\Pycom>"c:\Program Files (x86)\Pycom\Pymakr\Python27\python.exe" pyupgrade/bin/updater.py -t 1.5.0.b1-LoPy_868.tar.gz -p COM14 -s 115200 flash
                                Connecting...........................................
                                Exception: Failed to connect to ESP32: Timed out waiting for packet header, on line 157

                                1 Reply Last reply Reply Quote 0
                                • Y Offline
                                  yahia
                                  last edited by yahia

                                  To download higher firmware versions that are not present in the above list; use the below link with the firmware version of choice:

                                  https://software.pycom.io/downloads/LoPy_868-1.6.7.b1.tar.gz

                                  I am adding this here to keep downgrading related information in one place for future reference.

                                  1 Reply Last reply Reply Quote 0
                                  • P Offline
                                    pjoerke
                                    last edited by

                                    Hi,

                                    I want to downgrade my LoPy. Unfortunately I get an error when running

                                    python bin/updater.py -t LoPy_868-1.9.2.b2.tar.gz -p COM12 -s 921600

                                    I get the error: "updater.py: error: too few arguments"
                                    What's going wrong?

                                    Regards
                                    Pascal

                                    X 1 Reply Last reply Reply Quote 0
                                    • X Offline
                                      Xykon administrators @pjoerke
                                      last edited by

                                      @pjoerke Please use python bin/updater.py -t LoPy_868-1.9.2.b2.tar.gz -p COM12 -s 921600 flash

                                      Christian Ehlers

                                      1 Reply Last reply Reply Quote 0
                                      • rcolisteteR Offline
                                        rcolistete
                                        last edited by rcolistete

                                        It is worth noting that LoPy4 has different firmware file from v1.13.0.b1 onwards, the diference is simply a '4' after 'LoPy'.
                                        Links for direct download :
                                        https://software.pycom.io/downloads/LoPy4_868-1.13.0.b1.tar.gz
                                        https://software.pycom.io/downloads/LoPy4_915-1.13.0.b1.tar.gz
                                        https://software.pycom.io/downloads/LoPy4_868-1.14.0.b1.tar.gz
                                        https://software.pycom.io/downloads/LoPy4_915-1.14.0.b1.tar.gz
                                        https://software.pycom.io/downloads/LoPy4_868-1.15.0.b1.tar.gz
                                        https://software.pycom.io/downloads/LoPy4_915-1.15.0.b1.tar.gz

                                        My "MicroPython Samples". My "MicroPython Firmwares" with many options (double precision, ulab, etc).

                                        1 Reply Last reply Reply Quote 0
                                        • C Offline
                                          Colateral
                                          last edited by

                                          Hello Abilio,

                                          If we building from git, we are getting appimg.bin, lopy_868.bin, also in upper folders bootloader.bin. and partitions bin. There is also a script file in exp32\boards <board> folder

                                          I noticed in your LoPy868 tar file lopy_868.bin bootloader.bin partitions.bin, script and ._script files.

                                          I can not find "._script" file. How you are generating this file?

                                          Thank you

                                          1 Reply Last reply Reply Quote 0
                                          • A Offline
                                            aevraewrvaervea
                                            last edited by

                                            This post is deleted!
                                            1 Reply Last reply Reply Quote 0

                                            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                            With your input, this post could be even better 💗

                                            Register Login
                                            • 1
                                            • 2
                                            • 1 / 2
                                            • First post
                                              Last post

                                            Pycom on Twitter

                                            Pycom