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

    Windows Users - Firmware upgrade

    Scheduled Pinned Locked Moved Announcements & News
    9 Posts 5 Posters 2.6k Views 5 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.
    • A Offline
      abilio
      last edited by abilio

      After receiving reports from Windows users on an issue with the firmware upgrade tool, we suspect it could be related to the way we've been running the program, using pythonw.exe.

      There is out a new version of the file, v.0.9.2.b2b (download from here), that uses python.exe by default. Running the wizard, a new command dialog will now appear in the back.

      For those users willing to give new feedback, a copy of the text in that dialog will be highly regarded.

      The firmware itself continues to be the same: v.0.9.2.b2. The features were reported earlier in this other thread.

      Note: MacOS and Linux installers remain the same for this time. Only Windows users seem to be affected.

      K C 2 Replies Last reply Reply Quote 3
      • X Offline
        Xykon administrators
        last edited by

        This one worked for me at the first attempt :)

        Guess I won't be needed any more ;)

        Christian Ehlers

        1 Reply Last reply Reply Quote 2
        • N Offline
          n0ahg
          last edited by

          Worked perfectly first time on both of my LoPy

          1 Reply Last reply Reply Quote 0
          • K Offline
            Keptenkurk @abilio
            last edited by

            @abilio Yes!!! This one does the upgrade well! Appreciate the status window in this version. Nice job,.

            1 Reply Last reply Reply Quote 0
            • C Offline
              cappy2112 @abilio
              last edited by

              @abilio

              "it could be related to the way we've been running the program, using pythonw.exe"

              If you use pythonw.exe, you won't see a console window. This is the intended purpose of pythonw.exe, as opposed to python.exe

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

                Yes @cappy2112, that's why we were initially using pythonw, as we also do on Pymakr, to make it look like a clean Windows app. But the upgrade process failed. With no changes to the code, running the thing on python.exe made the trick. I'll still have to figure out why.

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

                  Could this be to do with stdout,stdin,stderr being invalid file descriptors when your script is running under pythonw.exe?

                  See http://bugs.python.org/issue706263

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

                    Yeah @n0ahg, that could be the reason. Thanks a lot for the suggestion :)

                    1 Reply Last reply Reply Quote 0
                    • C Offline
                      cappy2112 @abilio
                      last edited by

                      @abilio

                      When I was using Pythonw,.exe, if I want to get the scripts to execute with pythonw instead of python, I had to rename the extension of the .py files to .pyw.

                      I also needed to register pythonw.exe as the application to execute the .pyw files. This was slightly different in Windows 7 than Windows XP. The installer for the FW updater should be able to register pythonw as the application to run the .pyw files.

                      Good luck

                      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