sadly it's the same... rst:0x7 (TG0WDT_SYS_RESET),boot:0x37 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:1 load:0x3fff8020,len:8 load:0x3fff8028,len:2140 ho 0 tail 12 room 4 load:0x4009fa00,len:19760 entry 0x400a05bc

@misterlisty I did not fully analyze Pycom's implementation of the Watchdog, As far as I understand, the event they trigger is an interrupt, not reset. Which means, that in a full this interrupt fails too. Using the RTC it is possible to set up an WDT which pulls reset on expiry, but that one seems not to be used.

Could you simply feed the WDT while you write until you flush?

@timh I've already implemented internal watchdog but it doesn't help in case of Guru Meditation Error. @Martinnn You and I have the same problem. Thank you for suggestion, as I can see this watchdog times is not in a form of a development board like this one: https://shop.switchdoc.com/products/switchdoc-labs-dual-watchdog-timer-board-for-arduino-raspberry-pi?variant=3340467699742. Am I right? Thank in advance.

Hi @Andrea-Filippini, This is almost ready to be deployed, Daniel has some final tweaks he wants to make before we push this up to the firmware. Slightly confusingly, we already have the documentation live for this but are just waiting to push it to the firmware. Thanks for your patience! Alex

@pchirouze no, it should be: https://docs.pycom.io/pycom_esp32/library/machine.WDT.html