@paul-thornton The timing is rather critical. Couldn't you extend the time window for updating to let's say 30s?

See also my post here https://forum.pycom.io/topic/4130/pinout-pysense-etc

@stevo52 Yes, from the distance, it sounds like a hardware problem with the board. Maybe a broken wire or a bad solder point at the P2 pin.

@robi90 I misunderstood your first post, assuming a hard crash. I just tried your example and agree, that this is not good and must be fixed, because the device locks up in an unresponsive state. I tried that with version 1.20.0.rc4. The situation is a little bit better with Ctrl-F, because then the device falls at least back to safe boot, from which it can be restarted with machine.reset(). But only from the USB port. Using telnet is only possible then, if you use the default settings for WiFi.

Ill raise this internally. seems like a good idea.

For reference: Search for the post Firmware Files for Sequans LTE modem now are secured which contains the login and password

@robert-hh Es läuft jetzt. Ds Update ging nicht weil ich das Board für den Fipy überbrückt habe das es im batterie Modus läuft. nach entfernen des kabels ging auch das Update. Jetzt kann es weiter gehen. Danke für deine Mithilfe.

Thank you. I want to use CAT-M1 (not NB-IOT) so it looks like I can leave the modem firmware as it is?

@john-baird Can you try this? https://forum.pycom.io/topic/4022/unable-to-update-gpy-modem-firmware/4

@wghirakawa The issue is that socket.connect() and SSL handshake will not timeout also in case the socket timeout is set and hang the application forever. https://forum.pycom.io/topic/3985/new-lte-firmware-releases-v1-18-1-r4-stable-1-19-0-b5-development-nb-iot-firmware-40343/45

@rossdem699 You can use the pycom updater. Start the Pycom updater and tell it to update from a file. When it asks for a file, give it the name of the zip file. The updater will unpack the file itself. Generally you may also use ftp OTA update. Take the appimg.bin file from the package and transfer it to flash/sys. Once that is finished, reboot the device. But for a large change like 1.18.1r1 to 1.19.0.b4 and its possible change in the flash layout this may not work.

Hi @lasse You can find the firmware releases on GitHub: https://github.com/pycom/pycom-micropython-sigfox/releases I'll look into creating a page for changelogs somewhere.

@cmisztur Editing pycom-micropython-sigfox/esp32/pycom_version.h you can change the version, but I don't know how to change the name and the other parameters returned by uos.uname(). I'm sorry. Regards,

Resolved... diff --git a/py/mkrules.mk b/py/mkrules.mk index 633b0df..b9b235c 100644 --- a/py/mkrules.mk +++ b/py/mkrules.mk @@ -115,6 +115,13 @@ FROZEN_MPY_PY_FILES += $(shell find -L $(FROZEN_MPY_DIR)/Common/ -type f -name ' ifeq ($(BOARD), $(filter $(BOARD), GPY FIPY)) FROZEN_MPY_PY_FILES += $(shell find -L $(FROZEN_MPY_DIR)/LTE/ -type f -name '*.py' | $(SED) -e 's/$(FROZEN_MPY_DIR)\/LTE\///') endif +else ifeq ($(findstring MINGW32,$(OS_NAME)),MINGW32) +# make a list of all the .py files that need compiling and freezing +FROZEN_MPY_PY_FILES := $(shell find -L $(FROZEN_MPY_DIR)/Base/ -type f -name '*.py' | $(SED) -e 's/$(FROZEN_MPY_DIR)\/Base\///') +FROZEN_MPY_PY_FILES += $(shell find -L $(FROZEN_MPY_DIR)/Common/ -type f -name '*.py' | $(SED) -e 's/$(FROZEN_MPY_DIR)\/Common\///') +ifeq ($(BOARD), $(filter $(BOARD), GPY FIPY)) +FROZEN_MPY_PY_FILES += $(shell find -L $(FROZEN_MPY_DIR)/LTE/ -type f -name '*.py' | $(SED) -e 's/$(FROZEN_MPY_DIR)\/LTE\///') +endif else # make a list of all the .py files that need compiling and freezing FROZEN_MPY_PY_FILES := $(shell find -L $(FROZEN_MPY_DIR)/Base/ -type f -name '*.py' | $(SED) -e 's=^$(FROZEN_MPY_DIR)\/Base\//==')

@robert-hh I thought so. Thanks.

Solved. My mistake. I just connected to the expansion board, without the WiPy module on top of it. Then it had the error. With the WiPy module connected to the Expansion board, and following the instructions, the firmware update went fine.

@robert-hh said in LoPy link error: pycom-esp-idf That was the problem. Thanks - everything works and firmware flahses fine.