Chat freely about anything...

User avatar
By John Miller
#36764 Hello world,

I think the flash memory of my esp is physically damaged. How can I verify the uploaded firmware against the original?

Background: Got this version to run:
AT+GMR
AT version:0.40.0.0(Aug 8 2015 14:45:58)
SDK version:1.3.0
Ai-Thinker Technology Co.,Ltd.
Build:1.3.0.2 Sep 11 2015 11:48:04
OK

Then installed NODEMCU and LUA-scripting successfully. Got Wifi and a HTTP service running.

However, now my ESP doesn't boot properly anymore. On power up it gets stuck in an infinite loop sending serial data (which I wasn't able to interpret) to TX at about 64kHz. Consequently, the blue led is always on in operation mode.
Programming appears to work fine(see screenshot). At least there is no error reported. But I have the feeling that the boot code is corrupted somehow. Already tried to restore the original firmware without success.
The last think I did before the brick was to upload a compiled sketch (Example BLINK) via Arduino IDE.

The crystal is soldered correctly (there was an issue with the version reported on another thread here). But there's some strange behavior on GPIO02: It clones the TX-signal if data is sent. If connected to HIGH, TX seems to get stay HIGH, too, and the blue LED doesn't flash obviously. Looks to me that those 2 pins are internally connected somehow? That shouldn't be right.

I'm hoping for any suggestions.

Thank you.
Attachments
Firmware Update success2.png
User avatar
By John Miller
#36932 Thanks for the help to both of you.

If GPIO 02 is set to HIGH the blue LED won't flash once although data is transmitted heavily over TX (occurs in operation mode with GPIO 0 HIGH and 15 LOW). If GPIO 2 is disconnected during operation, the LED starts to flash again. This isn't normal, right? Maybe a breakdown between GPIO02 and TX?

Thanks for the utility. It will come in handy in the future. I think this ESP is broken. :(