[ARCHIVED] Downgrading firmware (advanced users)

[toribios_people]

Trying to downgrade on windows I get the following error, any idea why? Thanks.

C:\pyupgrade>c:\python27\python bin\updater.py -t 1.2.2.b1-WiPy.tar.gz -p COM8
Namespace(file=None, port='COM8', speed=115200, tar='1.2.2.b1-WiPy.tar.gz')
Connecting...
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 115200
Changed.
Exception: Error -3 while decompressing: invalid stored block lengths, on line 131

[sakis]

@toribios_people

It could be a corrupted file, a Windows-specific issue, or something else...

I just downgraded from the latest version (1.4.0.b1) to 1.1.0.b1 on macOS and it worked flawlessly.

I'd advice you to retry and if it still fails try doing it on Linux to see if it's Windows-specific. That way we can try to resolve it.

[Knoahlr]

@sakis seem to be getting the same error code as @toribios_people
I`m also doing this from a windows machine.

Namespace(file=None, port='COM7', speed=115200, tar='1.1.0.b1-WiPy.tar.gz')
Connecting...
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 115200
Changed.
Exception: Error -3 while decompressing: invalid literal/length code, on line 124

[livius]

i try downgrade my wipy to version 1.3.0.b1 but - on Windows 10 64 bit:

C:\Program Files (x86)\Pycom\Pycom Firmware Update\Python27\pyupgrade>"C:\Program Files (x86)\Pycom\Pycom Firmware Update\Python27\python" "bin\updater.py" -t WiPy.tar.gz -p COM3
Namespace(file=None, port='COM3', speed=115200, tar='WiPy.tar.gz')
Connecting...
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 115200
Changed.
Exception: Error -3 while decompressing: invalid stored block lengths, on line 131

[toribios_people]

@sakis I have tried with linux through VirtualBox and I don't get that error any more, althought the flashing process is not very stable. Took me 6 attempts to get the WiPy flashed, on the other 5 I got this error at ramdom completion percentages:

Writing at 0x0009400... (80%) Exception: Failed to write compressed data to flash after seq 33 (result was 0xc1, 0x0), on line 132

Maybe the problem is beacuse of flashing it through a virtual machine.

[sakis]

@toribios_people

That could be the case (usage of VM). Thanks all for the testing, it seems that this is a Windows-specific issue. I'll report it to our firmware updater expert.

[abilio]

@toribios_people, @sakis, @Knoahlr, @livius, the problem for (up/downgrading) versions 1.0.0.b1 and higher under Windows should be fixed now.

Can you please download the latest version of the tool, retry the procedure and post your feedbacks?

[Shaun]

@abilio
The latest updater on Windows 7 worked for me.
No more:
Exception: Error -3 while decompressing: invalid literal/length code, on line 124

[toribios_people]

Works fine here as well, with Windows 10.

[PCA]

@abilio Where can we find 1.4.0 and 1.5.1.b1 releases ?
Thanks
Pascal

[abilio]

@PCA, just upgraded the original list up to the last release :)

[Colateral]

Updater Version 1.1.1 on LopY doesn't work anymore

d:\Pycom>"c:\Program Files (x86)\Pycom\Pymakr\Python27\python.exe" pyupgrade/bin/updater.py -t 1.5.0.b1-LoPy_868.tar.gz -p COM14 -s 115200 flash
Connecting...........................................
Exception: Failed to connect to ESP32: Timed out waiting for packet header, on line 157

[yahia]

To download higher firmware versions that are not present in the above list; use the below link with the firmware version of choice:

https://software.pycom.io/downloads/LoPy_868-1.6.7.b1.tar.gz

I am adding this here to keep downgrading related information in one place for future reference.

[pjoerke]

Hi,

I want to downgrade my LoPy. Unfortunately I get an error when running

python bin/updater.py -t LoPy_868-1.9.2.b2.tar.gz -p COM12 -s 921600

I get the error: "updater.py: error: too few arguments"
What's going wrong?

Regards
Pascal

[Xykon]

@pjoerke Please use python bin/updater.py -t LoPy_868-1.9.2.b2.tar.gz -p COM12 -s 921600 flash

[rcolistete]

It is worth noting that LoPy4 has different firmware file from v1.13.0.b1 onwards, the diference is simply a '4' after 'LoPy'.
Links for direct download :
https://software.pycom.io/downloads/LoPy4_868-1.13.0.b1.tar.gz
https://software.pycom.io/downloads/LoPy4_915-1.13.0.b1.tar.gz
https://software.pycom.io/downloads/LoPy4_868-1.14.0.b1.tar.gz
https://software.pycom.io/downloads/LoPy4_915-1.14.0.b1.tar.gz
https://software.pycom.io/downloads/LoPy4_868-1.15.0.b1.tar.gz
https://software.pycom.io/downloads/LoPy4_915-1.15.0.b1.tar.gz

[Colateral]

Hello Abilio,

If we building from git, we are getting appimg.bin, lopy_868.bin, also in upper folders bootloader.bin. and partitions bin. There is also a script file in exp32\boards <board> folder

I noticed in your LoPy868 tar file lopy_868.bin bootloader.bin partitions.bin, script and ._script files.

I can not find "._script" file. How you are generating this file?

Thank you

[aevraewrvaervea]

This post is deleted!

[semireg]

It'd be nice if https://software.pycom.io/downloads/ had directory listings... or better yet, create a page with all the firmwares along with release notes so we can see what has changed.

[seb]

We will soon be uploading the firmware packages to: https://github.com/pycom/pycom-micropython-sigfox/releases

They are not there yet but will be soon