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

    New development firmware updater 1.15.2.b1

    Scheduled Pinned Locked Moved Beta Announcements & Development News
    firmware update
    11 Posts 3 Posters 2.0k Views 4 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.
    • S Offline
      Sympatron
      last edited by

      The serial port is still not saved.

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

        @sympatron Sorry I misunderstood this previously. I interpreted it as the serial port being reset to the default speed value (which was actually true for the PIC based boards).

        I'll add this in the next release.

        Christian Ehlers

        S 2 Replies Last reply Reply Quote 0
        • S Offline
          Sympatron @Xykon
          last edited by

          @xykon
          When will there be a new version? I assume the change would be rather trivial...

          1 Reply Last reply Reply Quote 0
          • S Offline
            Sympatron @Xykon
            last edited by

            @xykon
            Also the updater does not release the serial port on the result page. Only after you click on "Restart".
            And the handling of failed connection attempts is not very good. If the serial port cannot be opened the program hangs without an error message or an option to abort or retry. This is annoying when you often reflash the firmware and forgot to close the port in another application.

            P 1 Reply Last reply Reply Quote 0
            • P Offline
              Paul Thornton @Sympatron
              last edited by

              @sympatron said in New development firmware updater 1.15.2.b1:

              @xykon
              And the handling of failed connection attempts is not very good. If the serial port cannot be opened the program hangs without an error message or an option to abort or retry. This is annoying when you often reflash the firmware and forgot to close the port in another application.

              I tried this and after a while it timed out. I've not been able to replicate it just hanging there indefinitely on windows 10 at least could you share some more info about your setup?

              S 1 Reply Last reply Reply Quote 0
              • S Offline
                Sympatron @Paul Thornton
                last edited by

                @paul-thornton I don't think it does hang indefinietly (I never waited long enough), but very long considering that it could detect immediately that the port cannot be opened and abort with an error message.
                Or at least retry very often while waiting so that it can begin when the port is free again, which it does not as far as I can see.
                The timeout is simply far too long. Either the port can be opened in 1-2s or it has to be considered a failed attempt and either aborted or retried.

                P 1 Reply Last reply Reply Quote 0
                • P Offline
                  Paul Thornton @Sympatron
                  last edited by

                  @sympatron Thanks for the clarification.

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

                    @Sympatron Sorry it's been quite a while since I last worked on the firmware updater. I've been taking on new responsibilities at Pycom and we're still recruiting new developers.

                    I built a Windows version from the latest sources that you can download here but this has not yet been properly tested. Specifically, this version added support for a new format of the script file to support the changes we made to the partition layout in the development / release candidate firmware. However this is not yet 100% complete and may lead to unexpected results in certain circumstances.

                    This version does remember the last COM port being used so maybe you'll still find it more useful than the official development release.

                    I'm currently in China visiting our manufacturer but I'll try to look at the "indefinite" hanging issue when the COM port is blocked after I return to the Netherlands at the end of next week. This seems to be a "Windows only" issue and since most of the development and testing is done on MacOS I didn't notice that before. I've also noticed that there are some issues when you have a really slow internet connection.

                    Christian Ehlers

                    S 1 Reply Last reply Reply Quote 0
                    • S Offline
                      Sympatron @Xykon
                      last edited by

                      @xykon
                      I cannot access the files. OwnCloud wants me to sign in...

                      Is the new script format documented somewhere? I just found this documentation of the old format.

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

                        @sympatron Can you try this link please? https://xykon.pycom.nl/s/M8braq020b9gInb

                        Internet and China don't work well together...

                        There isn't really documentation for the new format yet because it's not yet been officially released. If you do manage to download the firmware updater you'd be the first person outside Pycom to actually use it. And as I said before it's still experimental and I'm aware of some issues with it such as the otadata partition definition missing, so please don't try to modify the script2 file in a firmware package.

                        I'm still in China this week and things tend to get more and more hectic towards the end of the trip so I likely won't be able to do any work on the firmware updater until I'm back in Eindhoven.

                        Christian Ehlers

                        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