Update from 3.1.0 to 3.1.1 initially behaved as failed then after some minutes started normaly

[mikekgr]

Basic Infos

• This issue complies with the issue POLICY doc.
• [ X] I have read the documentation at readthedocs and the issue is not addressed there.
• I have tested that the issue is present in current master branch (aka latest git).
• I have searched the issue tracker for a similar issue.
• If there is a stack dump, I have decoded it.
• I have filled out all fields below.

Platform

• Hardware: ESP8266
• Core Version: latest RELEASE 3.1.1
• Development Env: Arduino IDE 1.8.19
• Operating System: Windows 10

Settings in IDE

• Module: Generic ESP8266 Module
• Flash Mode: QIO
• Flash Size: 4MB
• lwip Variant: v2 Lower Memory
• Reset Method: nodemcu
• Flash Frequency: [40Mhz]
• CPU Frequency: 80Mhz
• Upload Using: OTA
• Upload Speed: [115200|other] (serial upload only)

Just to mention that I have chosen NONOS SDK version 3.0.5 after the update from 3.0.2 => 3.1.0 so the update from 3.1.0 => 3.1.1 had this SDK activated, if this makes sense to you

Problem Description

Dear Sirs,
First of all I wish you all Happy Healthy and Prosperous for the 2023. Also many thanks for keeping ESP8266 updated !
I am observed a very strange problem. In one of my ESP8266 I tried to OTA the exactly same sketch that is running with 3.1.0 just compiled with 3.1.1 . After the OTA finished ESP8266 stopped to function (I can "see" it only via my local Blynk server) and even lost from Port inside Arduino IDE (Tools => Port:). No having other way to interact, I can reach it only wirelessly, I switched his power off, stay at off several minutes and power on again. Nothing seems to worked and I left in power on state. Suddenly after let's say 6 minutes, started to functional normally both in Blynk Server (and Blynk App) and appeared as it should be in Arduino IDE Port. Do you know why can you guess what was wrong? Please take into consideration that this ESP8266 with exactly same sketch, when updated from 3.0.2 => 3.1.0 I didn't observed any problem nor "delay" to get back in functional state.

Thanks and Best Regards,
Mike Kranidis

[mcspr]

Assuming things worked ok in the end? Closing.

SDK upgrade should (preferably) go along with either ESP.eraseConfig() + __builtin_trap() immediately after or a manual flash erase being done with esptool.py
Also see #8828