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

[daniel]

@jcaron good point about the version numbering for Mac OS. We'll get this fixed next week, but it's just that the version number was not increased, the updater is the correct one.

are there any changes required if using updater.py on the command line (which allows changing the bps) as opposed to the GUI?

No, all the scripts have been properly changed, so using them on the command line is also fine.

Cheers,
Daniel

[rdixey]

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-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

[daniel]

@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.

[Frida]

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')

´´´

[rdixey]

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

[b3da]

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

[Emmanuel Goudot]

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

[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-hh]

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

[daniel]

@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!

[rdixey]

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

[robert-hh]

@daniel Now it works.

[Emmanuel Goudot]

@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')

[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.

[bmarkus]

Update was succesful on another WIN10 machine.

[colinza]

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