I think (not tested) you can overwrite a file while running (since you are running a compiled version of the file). For hashing, see: https://docs.pycom.io/firmwareapi/micropython/uhashlib.html

Checking pycom micropython source I see, that you are not useing the esp-idf functions for performing the update .... so no danger of corrupting the ota_0 slot. Still I wonder why you are doing "your one thing" instead of using the esp-idf functions ... (https://github.com/pycom/pycom-micropython-sigfox/blob/83e2f7f59e28d726a5a1d79377a5ec37f9e0065b/esp32/ftp/updater.c)

@JuanMa I am currently trying the same, also referencing this video from Pycom: https://www.youtube.com/watch?v=NnUVYIedl_w When i run the HTTP server from the OTA folder in pycom-libraries-master/examples/OTA the folders are already in place, but i get same error as you! What did you do to solve it precisely? Thanks /RM

If you just want to serve static updates, you can use IIS. The only reason python is used for that example is because it generates the updates on the fly from any version to the latest. You could generate the JSON files yourself and just statically serve them along with the required files.

Hi, It's likely that your web browser is automatically correcting this but the wipy is not, the manifest downloads ok because it has no backslashes in the URL. Could you add the following line to OTA_server.py and let me know if it fixes the issue: def generate_manifest_entry(host, path, version): path = "/".join(path.split(os.path.sep)) # Add this line entry = {}

Hi @naveen, Sorry I'm late to the party here, but I believe that the PyMakr is the "expansion board". Take a look at the back of your PyMakr and it should say Expansionboard v2.X or v3.X. You should be able to update firmware using your PyMakr and this tutorial. https://docs.pycom.io/gettingstarted/installation/firmwaretool.html Hope this helps!

If you want to customise how the current process works have a look at the https://github.com/pycom/pycom-micropython-sigfox/tree/master/esp32/ftp folder, especially updater.c.

@dangerdan02 It's clear, someone invested a lot of money to develop Symphony Link. But if they license it to "large customers" without a fee, why not license it to e.g. Pycom for one dollar or two per LoPy? Think about the possibilities. And they could still sell their gateways.

@jmarcelino Unfortunately, the procedure posted here https://github.com/pycom/pycom-micropython-sigfox/issues/5 doesn't work. I' ve followed these steps: Change bootloader (1536 -> 1024) make BOARD=WIPY TARGET=boot make BOARD=WIPY TARGET=app make BOARD=WIPY flash everything work and now with Filezilla I can upload file with size > 1MB After I create a new image edited the frozen file _boot.py with a print("Hello World") make BOARD=WIPY TARGET=boot make BOARD=WIPY TARGET=app with Filezilla I copy appimg.bin in /flash/sys/ reset the board (with the physical button ) firmware doesn't change Instead if I execute: make BOARD=WIPY flash, the firmware changes. So I think that "the updater task" doesn't start on reset. EDIT: I notice that the file appimg.bin uploaded with Filezilla disappears immediately, before reset.