Re: ESP-12 bricked after sometime

2016-10-05T00:47:05+08:00

0x7c000 esp_init_data_default.bin 0x7e000 blank.bin

This is for the 512kB module, not the ESP-12 (at least not mine).
Check the manual to see if you are using the correct addresses.
Also try flashing a single block of blanks to fill the whole flash and reset it.

Statistics: Posted by Lurch — Wed Oct 05, 2016 12:47 am

Re: ESP-12 bricked after sometime

2016-10-03T04:03:28+08:00

Thank you for your comments,

It's hard to change Flash IC.

I understand about thirty party tools but bootloader should not corrupt that way and if it gets corrupted, there should be a way to reflash the unit.

Best.

Statistics: Posted by mhanuel — Mon Oct 03, 2016 4:03 am

Re: ESP-12 bricked after sometime

2016-09-24T19:30:34+08:00

Hello,

Does not seem like the ESP8266 is physically affected, if you can still read the flash ID. Can you change the flash chip and retry?
Also, please use the Espressif Flash Download tool and see if it works.

Other tools are third-party software and we cannot provide support for them. Sometimes these tools may have bugs and cause issues.

Statistics: Posted by Guest — Sat Sep 24, 2016 7:30 pm

ESP-12 bricked after sometime

2016-09-23T22:37:54+08:00

Hello SIr,

I am presenting an issue with ESP-12 module, after some tests (I was working with arduino firmware), the module was working but after few flash downloads, suddenly I notice the esp was not connecting more to WiFi and no serial port console.

I am trying to see if the module is bricked, so I have downloaded the AT firmware but still have no response, this is my command

Code:

(esp8266) mhanuel@debPLC:~/Devel/esp8266/firmware_at$ esptool.py --port /dev/ttyUSB2 --baud 460800 write_flash -fs 4m -ff 40m 0x00000 boot_v1.5.bin 0x01000 user1.1024.new.2.bin 0x7c000 esp_init_data_default.bin 0x7e000 blank.bin
esptool.py v1.1
Connecting...
Running Cesanta flasher stub...
Flash params set to 0x0000
Writing 4096 @ 0x0... 4096 (100 %)
Wrote 4096 bytes at 0x0 in 0.1 seconds (306.6 kbit/s)...
Writing 401408 @ 0x1000... 401408 (100 %)
Wrote 401408 bytes at 0x1000 in 8.8 seconds (365.4 kbit/s)...
Writing 4096 @ 0x7c000... 4096 (100 %)
Wrote 4096 bytes at 0x7c000 in 0.1 seconds (354.9 kbit/s)...
Writing 4096 @ 0x7e000... 4096 (100 %)
Wrote 4096 bytes at 0x7e000 in 0.1 seconds (356.3 kbit/s)...
Leaving...
(esp8266) mhanuel@debPLC:~/Devel/esp8266/firmware_at$ esptool.py --port /dev/ttyUSB2 --baud 460800 verify_flash 0x00000 boot_v1.5.bin 0x01000 user1.1024.new.2.bin 0x7c000 esp_init_data_default.bin 0x7e000 blank.bin
esptool.py v1.1
Connecting...
Running Cesanta flasher stub...
Verifying 0xca0 (3232) bytes @ 0x00000000 in flash against boot_v1.5.bin...
-- verify OK (digest matched)
Verifying 0x61764 (399204) bytes @ 0x00001000 in flash against user1.1024.new.2.bin...
-- verify FAILED (digest mismatch)
Verifying 0x80 (128) bytes @ 0x0007c000 in flash against esp_init_data_default.bin...
-- verify FAILED (digest mismatch)
Verifying 0x1000 (4096) bytes @ 0x0007e000 in flash against blank.bin...
-- verify OK (digest matched)

A fatal error occurred: Verify failed.

I can communicate, for example

Code:

(esp8266) mhanuel@debPLC:~/Devel/esp8266/firmware_at$ esptool.py --port /dev/ttyUSB2 chip_id
esptool.py v1.1
Connecting...
Chip ID: 0x00f480a0

Code:

(esp8266) mhanuel@debPLC:~/Devel/esp8266/firmware_at$ esptool.py --port /dev/ttyUSB2 read_mac
esptool.py v1.1
Connecting...
MAC: 18:fe:34:f4:80:a0

Not sure what might be wrong,

Would you mind to give me your comments,

Thank you in advance,

Statistics: Posted by mhanuel — Fri Sep 23, 2016 10:37 pm

ESP8266 Developer Zone

Re: ESP-12 bricked after sometime

Re: ESP-12 bricked after sometime

Re: ESP-12 bricked after sometime

ESP-12 bricked after sometime