How to solve the firmware update failures

[Xykon]

I also looked through the 4MB image I made of the LoPy flash using esptool.py --chip esp32 --port COM24 --baud 115200 read_flash 0 4194304 lopy_firmware.bin

It seems the "recovery" firmware is at 0x10000, the previous version is at 0x110000 and the main firmware at 0x210000.

After flashing with esptool.py --chip esp32 --port COM24 --baud 115200 write_flash 0x210000 lopy_0.9.1.b1_868.bin -fs 4MB -z the latest version 0.9.1.b1 is starting as default.

I also flashed 0x10000 the same way and now my recovery image (when I leave the safeboot jumper on until the blue heartbeat LED starts) is now also at 0.9.1.b1.

My boot.py file and MAC address don't seem to be affected by this.

[LoneTech]

@daniel I think that bug causes full on readonly mode (I could be wrong). The data present in flash indicates that it did write, but didn't erase properly. On the second board, I did try esptool erase then OTA update; while it marked the image as updated, it caused a memory access error on boot. So I used esptool to write the firmware, and after that it booted the new revision. So it would seem, for the secondary flash position to update correctly on these particular boards, I need to get both the OTA done and write it with esptool. I haven't analyzed the bugfix you refer to to see if it would solve this, but I am certainly willing to try; I have backups of my boards now and could recover. Right now I'm happy I got them to boot the most recent release. :)

[oneeyed]

@Xykon said in How to solve the firmware update failures:

esptool.py --chip esp32 --port COM24 --baud 115200 write_flash 0x210000 lopy_0.9.1.b1_868.bin -fs 4MB -z

Indeed it allowed be to program the firmware as well, when no other methods could. Thanks.

[daniel]

@daniel I think that bug causes full on readonly mode (I could be wrong). The data present in flash indicates that it did write, but didn't erase properly.

The bug causes random bits in the flash status register to be written with wrong values, which can lead to different behaviors, the most common is the entire flash to be write protected, but it also can write protect only some sections of the flash memory.

[Bashir]

@oneeyed said in How to solve the firmware update failures:

@Xykon said in How to solve the firmware update failures:

esptool.py --chip esp32 --port COM24 --baud 115200 write_flash 0x210000 lopy_0.9.1.b1_868.bin -fs 4MB -z

Indeed it allowed be to program the firmware as well, when no other methods could. Thanks.

Hi, I can confirm this method worked for me also. I flashed the default address and recovery areas.

Thank you

[Xykon]

@Bashir said in How to solve the firmware update failures:

Thank you

Glad I could help.

Would you mind up-voting my post above? This helps getting rid of certain restrictions on this forum.

[livius]

Hi,

i have problem with update my Wipy2.0.
I have unlocked successfully - all looks like on screen @Batilan

But i still ca not update my board. When i copy appimg.bin to /flash/sys and restart my WiPy
it does not start. If i turn on self mode it start with oldest firmware.

Two questions here:

1. how to upgrade to most recent version?
2. how to permanently revert this update? I see no way to revert firmware to any previous version PERMANENTLY. I can revert it temporary but not permanently.

I try update WiPy2.0 only because it crash on simple blink heart led in the loop. And i think first upgrade and test again.

[livius]

Hi,

i have problem with update my Wipy2.0.
I have unlocked successfully - all looks like on screen @Batilan

But i still ca not update my board. When i copy appimg.bin to /flash/sys and restart my WiPy
it does not start. If i turn on self mode it start with oldest firmware.

Two questions here:

1. how to upgrade to most recent version?
2. how to permanently revert this update? I see no way to revert firmware to any previous version PERMANENTLY. I can revert it temporary but not permanently.

I try update WiPy2.0 only because it crash on simple blink heart led in the loop. And i think first upgrade and test again.

[Ralph]

Hi, @livius

First, try using the update tool (go to Firmware Updates) to update your WiPy2.0 and see if it solves your problem. This tool wil automatically update to the latest version.

If you still have the crash at startup after doing this, please provide the code you are using that is making it crash, and we can help you fix it.

[jgmdavies]

@livius Did you try the Pycom updater, or where did you get the file appimg.bin?

Jim

[livius]

@jgmdavies
I have downloaded updated app and go to folder and rename file for wipy to appimg.bin
then i put it by ftp

[jgmdavies]

@livius Thanks!

[jgmdavies]

@livius Thanks, I hadn't realised that is an option. For anyone else using Windows, you can probably find the .bin files at:

C:\Program Files (x86)\Pycom\Pycom Firmware Update\Upgrader

[livius]

@Ralph
I have tried it
It can conect and send data to wipy
but it can not connect after rebot and say that update failed
It store image to Wipy because wipy can not start normally only in "self" mode and it revert temporarly to old version.

After that problems i have tried to put the same appimg.bin self by ftp with same result. It store bin file and of course it dissapear
but wipy can not start - only in self mode

[Xykon]

I don't have a WiPy2 but if someone can upload the 4MB flash dump I can take a look to confirm the memory regions for the firmware images. I'd be surprised if they are any different from the LoPy though.

[Bashir]

@Xykon said in How to solve the firmware update failures:

I don't have a WiPy2 but if someone can upload the 4MB flash dump I can take a look to confirm the memory regions for the firmware images. I'd be surprised if they are any different from the LoPy though.

Don't use the ftp method, if you look at Xykon post below you will have a solution. I tried everything and the only thing the worked was (on a windows OS):-

1. Install python 2.7 and pyserial
2. Run the tool to unlock the flash area via command prompt (See official instructions)
3. Install the standalone update tool (next, next finish)
4. Copy the appropriate bin file for your device from C:\Program Files (x86)\Pycom\Pycom Firmware update\Upgrader to the location of the tools folder e.g. C:\flash_debug_tool
5. Open CMD in the directory you have the tools in e.g. "C:\flash_debug_tool" or cd to it and run the below
   esptool.py --chip esp32 --port COM3 --baud 115200 write_flash 0x210000 lopy_0.9.1.b1_868.bin -fs 4MB -z

Change the com3 to your comport number
Change the lopy_0.9.1.b1_868.bin to your bin file name (lopy_0.9.1.b1_868.bin, lopy_0.9.1.b1_915.bin or wipy_0.9.1.b1.bin)

this will install the latest firmware onto the default boot partition.

thank you

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