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

    IMPORTANT: New Firmware Update Tool Released (version 1.1.2.b1)

    Scheduled Pinned Locked Moved Announcements & News
    firmware
    24 Posts 10 Posters 9.7k Views 9 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.
    • R Offline
      rdixey
      last edited by

      I deleted all previous versions of the Update Tool from my Ubuntu system. Then downloaded the New Firmware Update tool v1.1.2.b1 from pycom.io Pycom upgrader Linux link.
      When I run it as I have dozens of times in the past I get the messages:

      • Connecting to the device to get it's information, please wait.
      • Something failed trying to connect to the device.

      Looks like the .update bash script throws this message when updater.py can't establish the serial connection

      I'm using /dev/ttyUSB0 through which I routinely connect to the Lopy with Screen at 115200 baud.

      I don't understand why the new update tool can't establish the connection as it had so easily with the prior update tool?

      robert-hhR 1 Reply Last reply Reply Quote 0
      • robert-hhR Offline
        robert-hh @rdixey
        last edited by robert-hh

        @rdixey Same here. It stops after changing the baud rate to 921600. Updating a self-built firmware with esptool.py initiated with "make flash" works.
        OS Debian 8

        B 1 Reply Last reply Reply Quote 0
        • D Offline
          daniel
          last edited by

          @rdixey I just tried the Unix it on Mac OS. Works as normal. I'll try this on Ubuntu tomorrow, and see if there's an specific issue there.

          R 1 Reply Last reply Reply Quote 0
          • FridaF Offline
            Frida
            last edited by

            Works ok here on Linux Mint 18.1 64 bit

            ´´´

            os.uname()
            (sysname='WiPy', nodename='WiPy', release='1.7.7.b1', version='v1.8.6-715-g5fa16c2c on 2017-07-20', machine='WiPy with ESP32')

            ´´´

            1 Reply Last reply Reply Quote 0
            • R Offline
              rdixey @daniel
              last edited by

              @daniel Did you find any specific issue with Update Tool 1.1.2.b1 on Ubuntu?

              1 Reply Last reply Reply Quote 0
              • B Offline
                b3da @robert-hh
                last edited by

                @robert-hh exactly the same for me on Ubuntu: Changing baud rate to 921600 - Failure!

                1 Reply Last reply Reply Quote 0
                • E Offline
                  Emmanuel Goudot
                  last edited by

                  Same issue on ubuntu: cannot update LoPy/SiPy anymore...

                  1 Reply Last reply Reply Quote 0
                  • D Offline
                    daniel
                    last edited by daniel

                    Hello everyone,

                    Thanks for reporting this issue with the linux updater. We haves just fixed it and released version 1.1.2.b2 for unix. It's available here:

                    https://software.pycom.io/findupgrade?product=pycom-firmware-updater&type=all&platform=unix&redirect=true

                    Apologies for the inconveniences...

                    Cheers,
                    Daniel

                    robert-hhR R 2 Replies Last reply Reply Quote 0
                    • robert-hhR Offline
                      robert-hh @daniel
                      last edited by

                      @daniel tried it, got a little bit further, up to the message:
                      " Something failed trying to contact the server."

                      1 Reply Last reply Reply Quote 0
                      • D Offline
                        daniel
                        last edited by

                        @robert-hh can you please try again? The issue reported before was caused because of the slow baudrate (38400) used before for the initial connection with the board. Increasing it to 57600 fixed it. We just trying again on our Ubuntu machines where it was failing before and now it's all fine.

                        @Emmanuel-Goudot @b3da @rdixey could you please try and let me know? Thanks!

                        robert-hhR E 2 Replies Last reply Reply Quote 0
                        • R Offline
                          rdixey @daniel
                          last edited by

                          @daniel 1.1.2.b2 worked on my Ubuntu 16.04 Thanks....

                          1 Reply Last reply Reply Quote 0
                          • robert-hhR Offline
                            robert-hh @daniel
                            last edited by

                            @daniel Now it works.

                            1 Reply Last reply Reply Quote 0
                            • E Offline
                              Emmanuel Goudot @daniel
                              last edited by

                              @daniel It works, report 1.7.7.b1

                              os.uname()
                              (sysname='LoPy', nodename='LoPy', release='1.7.7.b1', version='v1.8.6-715-g5fa16c2c on 2017-07-20', machine='LoPy with ESP32', lorawan='1.0.0')

                              1 Reply Last reply Reply Quote 1
                              • bmarkusB Offline
                                bmarkus
                                last edited by bmarkus

                                LoPy update fails on WIN10 (64-bit). Connecting to the device with a serial terminal using 115200 bit/s I see

                                rst:0x1 (POWERON_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
                                waiting for download

                                but the PyCom updater fails to connect.

                                Updater is just downloaded as 1.1.2.b1

                                Version number is not displayed in the updater and clicking on '?' in the upper right corner nothing happens. It looks like there is no way to get installer version.

                                1 Reply Last reply Reply Quote 0
                                • bmarkusB Offline
                                  bmarkus
                                  last edited by

                                  Update was succesful on another WIN10 machine.

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

                                    Why doesn't the update tool support OTA updates, or at least make the firmware binaries available directly?

                                    1 Reply Last reply Reply Quote 1

                                    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