ESP8266 Community Forum

- Sun May 03, 2015 4:29 am #16331

OK, I tried flashing my second failing module with raz123's .bin file once again, and now that module also seems to be working. This is magic...of the good kind!

I have several times "rescued" a non-working ESP by flashing AT firmware, then NodeMCU again. For some reason, reflashing with NodeMCU does not seem to do the magic - at least not for me!

- Sun May 03, 2015 6:39 pm #16408 OK, ArnieO, interesting information. I am under the impression that raz123's .bin file *is* nodeMCU fw, but I haven't yet verified that. Next time I have a failing ESP I will try AT firmware first. The process of "broken-repair-verify-working" for the purpose of gaining better insight in this is a bit slow since the reason for modules failing is a bit unclear... and even if it *was* clear I probably don't want to deliberately induce failure anyway, risking bricking the module in the end! Hoping for someone else to figure it out, I guess

- Tue May 05, 2015 3:57 pm #16627 Moin,

I didn't checked but ...
if AT firmware is bigger than nodemcu firmware and probably even includes the memory area where
persistent config like wifi config is stored flashing it would reset the config.
Alternative to try:
Flash blank.bin to 0x7e000 for some esps. May be different offset for bigger flash sizes.

Cal

Get your modules here:

https://www.banggood.com/custlink/KvGGhGF4wG