How to solve the firmware update failures

[livius]

i try
esptool.py --chip esp32 --port COM3 --baud 115200 write_flash 0x210000 wipy_0.9.1.b1.bin -fs 4MB -z
and got error:

C:\Python27\flash_debug_tool>esptool.py --chip esp32 --port COM3 --baud 115200 w
rite_flash 0x210000 wipy_0.9.1.b1.bin -fs 4MB -z
usage: esptool [-h] [--port PORT] [--baud BAUD]
{load_ram,dump_mem,read_mem,write_mem,write_flash,run,image_info,
make_image,elf2image,read_mac,chip_id,flash_id,read_flash,verify_flash,erase_fla
sh,version}
...
esptool: error: argument operation: invalid choice: 'esp32' (choose from 'load_r
am', 'dump_mem', 'read_mem', 'write_mem', 'write_flash', 'run', 'image_info', 'm
ake_image', 'elf2image', 'read_mac', 'chip_id', 'flash_id', 'read_flash', 'verif
y_flash', 'erase_flash', 'version')

[Xykon]

error: argument operation: invalid choice: 'esp32'

Are you sure you copied the command correctly? Maybe try typing it manually on the command line?

[livius]

i try type it but the same error
in previous post you have copy from cmd.exe window - without any modification - maybe i miss something?

[Xykon]

What happens when you run "esptool.py version" and "esptool.py --chip esp32". Can you please post exact output of both commands?

[livius]

I see that i have python 2.7.11
with python 2.7.12 now all looks good :)

Will be good to see in steeps that we need python 2.7.12

esptool.py v2.0-dev
Connecting...
Uploading stub...
Running stub...
Stub running...
Attaching SPI flash...
Configuring flash size...
Erasing flash...
Unc size 615696 comp size 362758 comp blocks 355
Wrote 362758 bytes at 0x00210000 in 32.6 seconds (89.1 kbit/s)...
Hash of data verified.

Leaving...

[Ralph]

Very nice to hear you got it working @livius

If anyone still has problems with firmware update failures: 0.9.2.b1 has just been released. This release fixes the bug where the flash memory gets write protected in some cases.

[Xykon]

If anyone still has problems with firmware update failures: 0.9.2.b1 has just been released. This release fixes the bug where the flash memory gets write protected in some cases.

I just tried the new firmware updater for Windows, it goes through the questions about LoPy/country/COM port but then fails immediately. Trying to figure out why.

I manually flashed the firmware, partition table and bootloader so it's not a big problem but I'm curious why the updater doesn't work.

[AgriKinetics]

@Xykon Hi, we are having the same problem, although after multiple attempts, it did get past that immediate fail, but, then had a fail with an unknown error in pythonW. Not sure what is going at the moment.

[livius]

Maybe because it is still wipy_0.9.1.b1.bin not wipy_0.9.2.b1.bin
i look into the folder and there is 1 not 2.

[AgriKinetics]

The correct 0.9.2.b1 is in the 'firmware' folder. I tried copying into the main 'upgrader' folder, but, the Upgrader still fails. Thought it might be the version of python (I was running 3.5) but, 2.7.12 fails also.

[Ralph]

Thanks for pointing this out. It must be an issue with the windows build of the updater, since the mac version works. We'll try to figure it out and get back to you guys as soon as we can.

[livius]

i do manual update by:
esptool.py --chip esp32 --port COM8 --baud 115200 write_flash 0x210000 wipy_0.9.2.b1.bin -fs 4MB -z
esptool.py --chip esp32 --port COM8 --baud 115200 write_flash 0x204000 partitions.bin -fs 4MB -z
esptool.py --chip esp32 --port COM8 --baud 115200 write_flash 0x201000 bootloader.bin -fs 4MB -z

i can connect by ftp and by telnet

by tenet i got:

import os
os.uname()
(sysname='WiPy', nodename='WiPy', release='0.9.2.b1', version='333b92c on 2016-10-26', machine='WiPy with ESP32')

but when i start wipy2.0 with board2.0
i can not connect by pymark - i do not know why it not "listen" on UART
but i can do above operations again - and as i understand corectly it is done by UART?

[Xykon]

@livius There are some extra steps in the updater to preserve your flash memory (MAC address, files on /flash). Since you skipped these steps it's likely your boot.py was overwritten.

Upload a new boot.py file with the following code:

import os
from machine import UART
uart = UART(0, 115200)
os.dupterm(uart)

P.S. Does anyone know where to find the formatting guide for this forum? I've seen people post source codes with a nice black background and syntax highlighting. How do you do that? Is there a help button somewhere for this?

[Xykon]

import os
from machine import UART
uart = UART(0, 115200)
os.dupterm(uart)

[livius]

Thank you for the help but it does not change anything
still pymakr can not connect :(
I see that update script does erase only some block(3.5MB)
i ommit that and i clear block

If someone have mre concept :)

[livius]

interested that UART work ok
with com port monitor i retrive data without any problem only PYMAKR can not connect

[Xykon]

So far I did manage to get the Linux updater to work.

In ./bin/updater I set BAUD_RATE = 115200 and commented #self.esp.change_baud(baudrate)

I tried the same thing in the Windows version but it still doesn't work.

[Xykon]

OK I got the Windows updater to work as well (though not the GUI).

First make the same modifications to "C:\Program Files (x86)\Pycom\Pycom Firmware Update\Upgrader\bin\updater.py"

Line12: BAUD_RATE = 115200
Line23:#self.esp.change_baud(baudrate)

Now open a command prompt and run:

cd "C:\Program Files (x86)\Pycom\Pycom Firmware Update\Upgrader"
..\Python27\python.exe bin\updater.py --port COM4 --file firmware\lopy_0.9.2.b1_868.bin

Make sure that you choose the correct COM port and firmware file for your module/region.

[livius]

@LarryTru
you are the best :)

This work for me - but Pymark still can not connect to WiPy2.0 :(
Before upgrade it work ok.
I can only conect by: wifi, ftp, telnet
boot.py looks ok
I also can see data sended by UART programmatically on com port monitor but Pymark can not :(

[livius]

Xykon not LarryTru