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

    Firmware update (downgrade) failing

    Scheduled Pinned Locked Moved LoPy
    3 Posts 2 Posters 1.2k Views 2 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.
    • C Offline
      Colateral
      last edited by Colateral

      Hello,

      According to your guidelines if you connect G28 to 3.3V and pressed the reset button for 3+2=5 sec... it will run the previous installed firmware.

      Currently on the LopYwe have installed the latest build 1.5.1b1 and we want to go back , but this is not working... . We tried also to go to the factory default ... but no change, the output is always:

      (sysname='LoPy', nodename='LoPy', release='1.5.1.b1', version='v1.8.6-423-g18444a2 on 2017-02-07', machine='LoPy with ESP32', lorawan='1.0.0')

      We uninstalled 1.5.1b1 Pycom Firmware Update and installed pycom_firmware_update_1.0.0.b3.exe ... upgrading the board. The tool is completed successfully, but instead of desired release.... 1.5.1.b1 is still runing.

      NO MATTER WHAT WE ARE DOING... the latest release is running.

      On LopY how we can re-write the build that we want ? And why is not working the downgrade procedure?

      Thx

      .

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

        Yes, this also confused me originally.

        I concluded that running of the previous firmware is only until you restart the device again, I don't think it is persistent through restarts.

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

          @crankshaft Thx. Yes... That's why we want 'a natural way' to re-write a previous firmware.... and run on that one always.

          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 / 1
          • First post
            Last post

          Pycom on Twitter

          Pycom