ESP8266 Developer Zone

Re: Cannot recover from Fatal exception (0): problem during boot

2017-05-19T17:38:59+08:00

If somehow your program or flashing software is messing with the eFuse in the ESP8266, you will brick your module and it is not recoverable. The purpose of eFuse is to be programmed only once. And when you set your module to OTP or enable protection using eFuse by mistake, you brick your module.
There is no documentation on the eFuse part right now for certain internal reasons.

Statistics: Posted by Guest — Fri May 19, 2017 5:38 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2017-05-15T08:35:41+08:00

Has anyone found a way to recover from this bootloop issue?
I have 2 12E modules with this affliction.
I was hoping for settings for flashing that would over come this.
Or at least the reason why the EFUSE error means "buy another" module.

I have proper power supply, I realise that the 3,3V on an Arduino board is not enough to feed the ESP8266 with 300mA it needs.

Statistics: Posted by WheresWally — Mon May 15, 2017 8:35 am

Re: Cannot recover from Fatal exception (0): problem during boot

2017-01-15T00:30:02+08:00

thanks for the answers

today I tried esp download tool and get the efuse error

so I changed module and new one works, great !

once flashed with esp upload tool, I see boot message

but typing I receive back garbage chars

so I get leaded to and try

http://www.esp8266.com/viewtopic.php?p=34267#p34267

after that I can do serial at 115200 and perform AT commands

please note that for the first module, which when I try to upload flash with esp flash download tool is throwing efuse error, I just used Arduino IDE 1.8 to upload my sketch, and the fatalexception(0) began. I didn't test it before.

now I ask, is it safe to upload sketches with Arduino 1.8 ? or efuse ain't related to this ?

thanks again

EDIT: yes is safe to upload sketches with Arduino 1.8 !! I did and its working ... thanks

Statistics: Posted by pezGordo — Sun Jan 15, 2017 12:30 am

Re: Cannot recover from Fatal exception (0): problem during boot

2017-01-13T14:43:35+08:00

pratik wrote:
epc1=0x402147a4

This is the address of the instructions that cause exceptions. Does anyone here have the .S file of the output binary that has been causing exceptions? That file is absolutely necessary to get an idea of which function is actually triggering exception.
Random resets are power supply issue most of the time. But seems like something else here, I am not able to reproduce this issue.
Feel free to send me the binary files + your ESP8266 system config info on pratik@espressif.com so that I can check the binaries out. A .S file is much appreciated!

By the way, if you are breadboarding with ESP8266, do watch out for ground loops. A ground loop on a breadboard will mess your system if there are RF components involved.

Sent you the mail with the binaries that i've tried. Ensured no ground loops are there.
nodemcu_integer_0.9.x: 0X00000
esp_init_data_default.bin: 0XFC000

Statistics: Posted by aditgupta100 — Fri Jan 13, 2017 2:43 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2017-01-13T14:09:06+08:00

epc1=0x402147a4

This is the address of the instructions that cause exceptions. Does anyone here have the .S file of the output binary that has been causing exceptions? That file is absolutely necessary to get an idea of which function is actually triggering exception.
Random resets are power supply issue most of the time. But seems like something else here, I am not able to reproduce this issue.
Feel free to send me the binary files + your ESP8266 system config info on pratik@espressif.com so that I can check the binaries out. A .S file is much appreciated!

By the way, if you are breadboarding with ESP8266, do watch out for ground loops. A ground loop on a breadboard will mess your system if there are RF components involved.

Statistics: Posted by Guest — Fri Jan 13, 2017 2:09 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2017-01-13T02:12:30+08:00

ESP_Greg wrote:
Hi pezGordo,
You need select 8Mbit flash map at least. AT binary can't support less than 8Mbit flash map.

What is happening :
During time of flashing module i need to bring CH_PD HIGH -> LOW -> HIGH.
After this patchwork, I'm able to flash my module with tool and firmware
When i switch to programming mode, also i need to bring CH_PD HIGH -> LOW -> HIGH to boot the module
But during boot, with Esplorer/putty i'm getting
Fatal exception (0):
epc1=0x40210880, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000
Fatal exception (0):
epc1=0x40210880, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000

Hardware used :
ESP8266-01
Arduino is used for Power supply (3.3V) and UART

/////////////////////////////////////////////////////
FIRMWARE/BINARIES INSTALLED :
/////////////////////////////////////////////////////

nodemcu_integer_0.9.5_20150318.bin: 0X00000
esp_init_data_default.bin: 0XFC000
blank.bin: 0XFE000

/////////////////////////////////////////////////////
Flash Configuration
/////////////////////////////////////////////////////

BAUD RATE : 115200 (Tried with 9600 baud also)
FLASH SIZE : 8MB
FLASH SPEED : 40MHz
SPI : DIO(Tried with QIO also)

Trial to recover:
a) Reflash module with NodeMCU 0.9.6 at 0x000  fail, same error
b) Reflash module with following binaries  fail, same error
nodemcu_integer_0.9.5_20150318.bin: 0X00000
esp_init_data_default.bin: 0XFC000
blank.bin: 0XFE000
c) Power supply problem:
Used external power supply from beaglebone 3.3V and applied 100uF capacitor on rails (between VCC and GND, to avoid any noise )  fail, same error

Terminal output:
CODE: SELECT ALL
ets Jan 8 2013,rst cause:2, boot mode:(3,7)

load 0x4010f000, len 1264, room 16
tail 0
chksum 0x42
csum 0x42
~ld
Fatal exception (0):
epc1=0x402147a4, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000

d) Reflash module with latest AT firmware found on github
boot_v1.6.bin: 0X00000
esp_init_data_default.bin: 0XFC000
blank.bin: 0XFE000
user1.1024.new.2.bin: 0x1000
No more fatal exception, just that module goes into reset automatically.

Statistics: Posted by aditgupta100 — Fri Jan 13, 2017 2:12 am

Re: Cannot recover from Fatal exception (0): problem during boot

2017-01-13T01:54:22+08:00

For AT firmware use below address and configuration for ESP8266-01:
boot_v1.6.bin: 0X00000
esp_init_data_default.bin: 0XFC000
blank.bin: 0XFE000
user1.1024.new.2.bin: 0x1000

BAUD RATE : 115200
FLASH SIZE : 8MB
FLASH SPEED : 40MHz
SPI : QIO

This module is very sensitive i guess, because with above settings my module worked in AT but than in middle it might get to reset state (printing that fatal exception).

Even i'm facing same issue with NodeMCU. I'm able to run module with AT but what shall i do to run NodeMCU (Lua scripts on module) it gives same fatal exception (0) error (illegalInstructionCause) which probably is because of firmware not detected.

Statistics: Posted by aditgupta100 — Fri Jan 13, 2017 1:54 am

Re: Cannot recover from Fatal exception (0): problem during boot

2017-01-12T11:18:09+08:00

Hi pezGordo,
You need select 8Mbit flash map at least. AT binary can't support less than 8Mbit flash map.

Statistics: Posted by Guest — Thu Jan 12, 2017 11:18 am

Re: Cannot recover from Fatal exception (0): problem during boot

2017-01-05T00:13:21+08:00

Hello, I'm suffering the same issue now

I can upload , delete flash

I've tried Arduino IDE, esptool.py (in Ubuntu), NodeMCU, NONOS

All 10K resistors are there (breadboard)

100nf capacitor near (into) esp12

still receiving response below

please any advice on how to solve is very appreciated, I have 10 of these and want to use them

Code:

 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x40100000, len 1396, room 16 
tail 4
chksum 0x89
load 0x3ffe8000, len 776, room 4 
tail 4
chksum 0xe8
load 0x3ffe8308, len 540, room 4 
tail 8
chksum 0xc0
csum 0xc0

2nd boot version : 1.4(b1)
  SPI Speed      : 40MHz
  SPI Mode       : QIO
  SPI Flash Size & Map: 4Mbit(256KB+256KB)
  jump to run user1 @ 1000

Fatal exception (0): 
epc1=0x40201670, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000
Fatal exception (0): 
epc1=0x40201670, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000
.
.
.

I can see ets Jan 8 2013,rst cause:2, boot mode:(3,6) , rst cause:2 impliing "reset pin" , but measuring reset pin I see it 3.3V steady

also, I can read SPI Flash Size & Map: 4Mbit(256KB+256KB), but it is suposed I'm using (512KB+512KB) bin/at/ folder of esp8266_nonos_sdk_v2.0.0_16_08_10

please help, thanks

Statistics: Posted by pezGordo — Thu Jan 05, 2017 12:13 am

Re: Cannot recover from Fatal exception (0): problem during boot

2016-12-28T00:17:51+08:00

Thank you Pratik. If you have any news, please, let me know.

Panagis

Statistics: Posted by panaghs — Wed Dec 28, 2016 12:17 am

Re: Cannot recover from Fatal exception (0): problem during boot

2016-12-27T23:06:22+08:00

Hi!

Got the issue now in greater detail, thanks for the long post! I'll forward this and get feedback on the issue.
I'm sure now that it's no issue with the Electrical connection or supply.
I wonder if changing the flash chip will resolve this issue? I'll let you know soon.

Statistics: Posted by Guest — Tue Dec 27, 2016 11:06 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-12-23T22:59:24+08:00

Unfortunatelly, I cannot use the laterversions. This is because the lowest possible flashing speed is 115200 and my esp syncs at 9600. Except if you know a way how to add the option of 9600 at the dropdown list...

Thanks

Statistics: Posted by panaghs — Fri Dec 23, 2016 10:59 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-12-19T01:55:34+08:00

I use flash_download_tools_v3.4.4. the early version doesn't show Efuse error.
efuse is in the processor not flash. when it change it will change the function of the processor so you need different firmware for it to run.
you earsed flash memory but still flashed old firmware into it. so you got same result.
I try not to think the factory hide efuse in the chip could totally disable the chip. if that' the case would make me sad and angry.

Statistics: Posted by jemy — Mon Dec 19, 2016 1:55 am

Re: Cannot recover from Fatal exception (0): problem during boot

2016-12-18T08:29:59+08:00

Hello jemy hello espressif administrators,

I did not get any efuse-connected message... and I erased the whole flash memory several times with Pratik's trick. Do I have to use some later version than FLASH_DOWNLOAD_TOOLS_v2.4_150924 that I used? I also used NodeMCU firmware programmes and got normal flash results for all packages downloaded.

Doesn't make sense...

I am willing to send you the chip for checking and analysis. Would you like that?

Regards,

Panagis

Statistics: Posted by panaghs — Sun Dec 18, 2016 8:29 am

Re: Cannot recover from Fatal exception (0): problem during boot

2016-12-18T03:00:39+08:00

google what is Efuse
I think the problem is that the efuse was blowed up when I uploaded new program by new updated Arduino IDE.
I guess it is designed purposely by someones so they can destroy it when time is up.
if the efuse is located in flash memory maybe we can design code by moving around that address.
so i'm waiting new Arduino IDE to solve this issue.

Statistics: Posted by jemy — Sun Dec 18, 2016 3:00 am

Re: Cannot recover from Fatal exception (0): problem during boot

2016-12-17T00:37:40+08:00

Dear Pratik,

Thank you very much for your reply. Perhaps my post was a bit shorter than it should, trying not to repeat previous posts. The facts:

1) OPEN-SMART ESP-12 ESP8266 bought for 8 euros eight months ago from here:
http://www.dx.com/p/esp-12-esp8266-seri ... FQO7Pl95pg
Download link of guides, schematics etc here: http://pan.baidu.com/s/1ntotvwX

2) Working fine: AT commands issued from serial port, connected to local WiFi, server operation trasmitting specific bytes etc.

3) 2 weeks ago attempted to install the NodeMCU firmware following these instructions:
http://www.whatimade.today/loading-the- ... ows-guide/
specific instructions for ESP12 by the same guy here:
http://whatimade.today/graphic-equalize ... q7-ws2812/

Iterating exception (0) error appeared.

4) Cleared Flash completely and verified that it was done properly using your code:
http://www.pratikpanda.com/completely-f ... sh-memory/

5) Attempted to install official latest AT firmware by Espressif = Exception (0).

6) Cleared flash again. Installed AI-v0.9.5.0 AT Firmware. Exception (0).

7) Cleared flash again. Used FLASH_DOWNLOAD_TOOLS_v2.4_150924 to get things right, read whole Espressif manual that has to do with flashing firmwares, identified flash size, clock etc. Result=exception(0).

8) Used laboratory external switching power supply with perfect voltage and used MKT capacitors (checked with oscilloscope) even if my board has a regulator anyway, checked if GPIOs, Ch_pd, connections, voltage while programming and resetinng at GPIO2. Everything looked OK. Reflashed looking voltages and signals during flashing using a Tektronix isolated 4-ch oscilloscope. Result=exception(0).

9) Wasted 2 weeks reading posts and trying literally everything suggested for the exception (0) and (28) iterating case and still exception (0). Conculsion, if user area (h10000) is left empty there is no exception (0). I never compiled or installed my code. Haven't reached that stage yet.

Pratik, I am an electrical engineer (even if this is clearly not my field) and have access to all shorts of equipment for testing, so I can give you feedback to any suggested test. However, I have tried everything that is out there and going even further... still exception (0). I have some experience with other DSPs and uC, such as Arduino Nano, TI f28377d etc. My only consolation is that many other people out there have exactly the same issue and ended up buying another type/brand of ESP (I do not mean those that compile their own code, so fixed it by correcting their code that caused the issue). Purely out of engineering curiosity, exactly for the same reasons with you about the meaning of exception (0), I insisted.

I hope my post is a bit more precise now. If there is anything you can suggest it will be highly appreciated.

Thank you again for your time,

Panagis

Statistics: Posted by panaghs — Sat Dec 17, 2016 12:37 am

Re: Cannot recover from Fatal exception (0): problem during boot

2016-12-16T17:47:16+08:00

How are you generating the code that causes this fatal exception loop when put on the ESP8266?
The address epc1 in the exception is the address of the code where the problem is caused.
Please locate this address in your assembly listing (.S output when you compile the code) and you will know which function is causing this error. Let me know that to be able to help!
Boot process seems fine to me, and if you are getting the exceptions - it means ESP8266 is working fine.

Statistics: Posted by Guest — Fri Dec 16, 2016 5:47 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-12-15T21:16:29+08:00

I face exactly the same issue after I flashed my first new firmware. It worked perfectly well till then. I tried exactly the same solutions: power supply, firmwares, etc.
(plus I added the 10k Resistance between GPIO 2 and VCC, with no result other than that the blue led doesn't work, when I remove the resistance it works again).

However, my ESP12 is not dead.

When flashed with any (user) code at 0x01000 it iterates with exception error (0) and similar address with everyone else. It flashes at 9600, but only sends readable serial content at 78440bps. Actually, when I reset at programming mode I get only boot(1,7) and reset cause 2, but when I reset at serial communication mode I get the endless exception (0) error. If I erase flash the problem vanishes (but there is no user code, of course).

Do you want me to send it over for examination? I would like to know what is the reason behind this (which made me spent 2 weeks of my life in circles)... Send me details how to do so, if yes.

I have given up, now. Thank you anyway.

Statistics: Posted by panaghs — Thu Dec 15, 2016 9:16 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-12-12T22:33:29+08:00

I have the same problem even tested it to a brand new esp8266 board right after upload a program from arduino-1.6.12 found program not run well then change program upload again got Fatal exception loop. use flash_download_tools_v3.4.4 try to update firmware it detect efuse error right away couldn't flash at all.
I think it is a hardware fail. it could happened to everyone.
what is efuse? what happen to it? how could the program loader destroy efuse. is it a hardware design defect plus malware virus?
I hope arduino expert or chip maker could take a look into it.
thanks

Statistics: Posted by jemy — Mon Dec 12, 2016 10:33 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-09-11T09:30:38+08:00

The following is what I get with ESP Flash Tool v3.3.6;

Code:

KEY PATH NONE...
************
check_res: (True, [])
is running :  False
************
set STOP FLG:  True
*********************
pic path: ./RESOURCE/IDLE_S.bmp
***********************
TEST!!!!
SELF.COMSTR: COM4
test running : False
BAUD 0 : 115200
test COM: COM4 
test self._COM: COM4
test baud:  115200
======
CONNECT BAUD: 115200
============
test type : 
COM type: string
is open:  False
serial port opened
-----------
baud: 115200
root baud: 115200
-------------
===============
BAUD :  115200
===============
Connecting...
*********************
pic path: ./RESOURCE/SYNC_S.bmp
***********************
chip sync ok!
0x3ff00050: 8a790801
0x3ff00054: 0200fe2a
0x3ff00058: 0000a000
0x3ff0005c: 00000000
EFUSE MODE : 1
reg0:8a790801
reg1:0200fe2a
reg2:0000a000
reg3:00000000
check_err_0: 0a
check_err_1: 00
check_err_2: 01
check_err_3: 02
check_err_4: 0a
====================
EFUSE NORMAL MODE
====================
bit[1:0] error
=========================
CRC IN MODE 1:
crc_calc_res: 121
target crc val: 121
=========================
efuse warning found...



==================
EFUSE LOG:
======================
EFUSE LOG:
---------------
REG0:8A790801
REG1:0200FE2A
REG2:0000a000
REG3:00000000
----------------
====================
EFUSE NORMAL MODE
====================
EFUSE VAL ERROR...
EFUSE VAL WARNING...

get mac res:  False
*********************
pic path: ./RESOURCE/EFUSE_ERROR_S.bmp
***********************
KEY PATH NONE...
com closed

Statistics: Posted by dsbaha — Sun Sep 11, 2016 9:30 am

Re: Cannot recover from Fatal exception (0): problem during boot

2016-09-11T04:41:41+08:00

Has anyone found a solution to this problem? I, too, am experiencing the "bootloop" which was mentioned earlier. I can flash, I can place the bootloader into "SDIO" mode, I see the bootloader actually loading up. It just goes straight to "Fatal Exception (0)" trying to run the user code. Maybe there is something wrong with the bootloader?

Code:

 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x40100000, len 28740, room 16
tail 4
chksum 0xcd
load 0x3ffe8000, len 2888, room 4
tail 4
chksum 0xbc
load 0x3ffe8b50, len 15252, room 4
tail 0
chksum 0x4f
csum 0x4f
Fatal exception (0):
epc1=0x4021058c, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000

Then it repeats the following two lines forever;

Code:

Fatal exception (0):
epc1=0x4021058c, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000

Statistics: Posted by dsbaha — Sun Sep 11, 2016 4:41 am

Re: Cannot recover from Fatal exception (0): problem during boot

2016-06-30T02:55:00+08:00

Hi, Yes I have checked GPIO2 and it is High at boot time....
I am afraid that the module is broken... my conclusion is related to the wrong silk screen in GPIO4 and GPIO5. I put a push button in GPIO04 and a Led in GPIO5 (as in silk screen stated) so GPIO05 was OUTPUT thinking the led was in this pin.... so when I pushed the button (attached to the "real" GPIO5), I put the OUTPUT to ground without any resistor... I will try in the future with this module....Just now I am using other ESP07 with no problem.

Statistics: Posted by JLC — Thu Jun 30, 2016 2:55 am

Re: Cannot recover from Fatal exception (0): problem during boot

2016-05-16T23:47:23+08:00

Hi

It is possible that the GPIO2 is not connected to high. ESP is very sensitive to the voltage on the pin and if it is used as IO have very high chances of some issue.

GPIO2 should be high to start reading from the flash or it will continue to give fatal exception.

Statistics: Posted by pk_rulz — Mon May 16, 2016 11:47 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-04-26T01:26:37+08:00

Hi, these are my esp8266-07.
The module with multicolor plane cable is the module with fatal exception as I have described in my previous post.
I remember that I use pin 04 as input with a push button to GND and Pin 05 as an Output with a led & 2k2 ohms serial resistance. However I have read in a site that some esp8266-07 has a problem with the silk screen and the gpio 04 and gpio 05 are changed. So, I am afraid that I put the push button to GND in the Output. Perhaps this condition have damaged the chip....

The second module, with a gray plane cable, is working fine, but I made a previous test of GPIO 04 and GPIO 05 and I verify that GPIO 05 and GPIO 04 silk screen are wrong...taking this issue in mind, I configured the io pins in the correct way.....
I have used 4K7 ohms Pull Up resistors for GPIO 0, RST, CH_PD, GPIO2 and pull down GPIO15.

You can see the FTDI USB interface from Sparkfun. The power supply is taken from the 3.3 v in this break out. I have measure the Current consumption of ESP8266-07 gray cable during 2 hours working as a AP and serving a web page and the current is < 170 ma.

Statistics: Posted by JLC — Tue Apr 26, 2016 1:26 am

Re: Cannot recover from Fatal exception (0): problem during boot

2016-04-20T20:45:16+08:00

@JLC
Could you post the photos of your ESP8266-07 module? Both sides, top and bottom. And the 3.3V voltage regulator.
I'd like to compare it with my setup.

Statistics: Posted by tomchees — Wed Apr 20, 2016 8:45 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-04-18T03:49:24+08:00

Hi All:
I have the same problem with ESP8266-07 from AI-THINKER.

the basic hardware setup was:

VCC = 3.3 v (3.24 read with multimeter and the DC current Consumption is alway about 30 mA to 50 ma)

FTDI usb serial interface form SparkFun work well for programming SparkFun The Thing. The Power Supply for the SparkFun is the from the USB using the FTDI basic break out board.

the ESP8266-07 HW config:

CH_PD -> 10kohm ->VCC
GPIO 0 -> 10Kohm ->VCC (GPIO 0 -> Push Button "PROGRAM" -> GND)
GPIO 15 -> 10Kohm ->GND
REST ->10Kohm - VCC (REST - Push Button "RESET" ->GND)

(see the hardware configuration and program procedure in
http://ediy.com.my/blog/item/133-upload ... rduino-ide)

I had programmed the module with Arduino IDE 1.6.8 on MAC osxI tried all the steps (regrading the changes of the FTDI basic break out) and all workers Fine!

However, then, I put some leds and a button:

GPIO 12, 13, 14 to each RGB led and 3,3 Kohm to GND

GPIO 16 push button to GND (then I changed it to GPIO 4 since GPIO 16 has not internal pull up resistor. )

and the problem began.....

Suddenly the ESP8266-07 module starts with the Blue led light Constant and sent the fatal exception (0)....
I had tried to re program and the same problem. some times the terminal (putty or Tera term in Windows shows garbage in all baud rates)

I have been reading all the post and this is the most complete....

1) I tried fe flashing the original Firwmware with several programs the ESP_DOWNLOAD_TOOL_V2.4 and the programming is OK, but at restart the same problem. I have used

2) I have used the NODEMCU FIRMWARE PROGRAMMER and the Programming was fine but, always the same problem...blue light constant and fatal exceptions....

3) I installed the esptool.py and made several test: get chip_id, read_mac, write_flash, erase_flash, and verify_flash....all the tests were ok, but the result is the same....

(I have used the "v0.9.2.2 AT Firmware.bin" to test the esptool.py, but i used "_" instead of " " in the name)

Finally, I attached the screenshot of each test....

I have read that perhaps I need to connect a pull up resitor to GPIO 2 in order to make sure that this pin was High at boot time....but I record with voltimeter the voltage at this pin at boot time and it is in 3.24 V.....

Always blue light is constant and fatal exception...do you have any Idea?

I will try with another module but I need before if it is a software problem, an electric problem or the module is broken.

Thank you
best regards

Statistics: Posted by JLC — Mon Apr 18, 2016 3:49 am

Re: Cannot recover from Fatal exception (0): problem during boot

2016-04-15T06:10:28+08:00

Thank you for your advice.
Even though I followed the instruction I'm getting the same error. I suspect the chip might be broken (by ESD?) as it behaved properly so far and now I'm not able to make it start any user code.

What is strange, I can see efuse errors reported by the flash download tool. I do not observe this kind of error with my second module. Please compare the two logs below:

non-working module:

Code:

test baudrate:  9600
test baudrate selection:   0
tout as adc
RF option applied...
(True, [])
test running : False
serial port opened
Connecting...
chip sync ok!
0x3ff00050: a8070001
0x3ff00054: 0212126a
0x3ff00058: 6548b001
0x3ff0005c: 205ccf7f
EFUSE MODE : 1
reg0:a8070001
reg1:0212126a
reg2:6548b001
reg3:205ccf7f
check_err_0: 0b
check_err_1: 02
check_err_2: 01
check_err_3: 02
check_err_4: 0b
====================
EFUSE NORMAL MODE
====================
bit[125:124] error
bit[1:0] error
=========================
CRC IN MODE 1:
crc_calc_res: 100
target crc val: 101
=========================
bit[119:96] crc error
=========================
CRC IN MODE 1:
crc_calc_res: 38
target crc val: 7
=========================
bit[47:24] crc warning
efuse warning found...



==================
EFUSE LOG:
======================
EFUSE LOG:
---------------
REG0:A8070001
REG1:0212126A
REG2:6548b001
REG3:205CCF7F
----------------
====================
EFUSE NORMAL MODE
====================
EFUSE VAL ERROR...
EFUSE CRC ERROR...
EFUSE VAL WARNING...
EFUSE CRC WARNING...

=================
reg2>>13: 5
=================
48bit mac
debug:
-----------------------
 5c cf 7f 12 6a a8
ID FOR XM: 06 54 80 01 01 20 70 00
XM_ID: 0654800101207000
-----------------------
crc_efuse_4bit: 0
crc_calc_4bit: 8
48bit mac
MAC AP : 5E-CF-7F-12-6A-A8
MAC STA: 5C-CF-7F-12-6A-A8
get mac res:  True
('tttest uuuuuuuuuuart : uart reg: ', 236)
(' baudrate: ', 230400)
get crystal: 27187200
head: 0 ;total: 0
erase size : 0
get flash id : 0xff1640e0
 manufacturer_id: 0xe0

 device_id: 0x4016

vendor: 224
mode: 64
size: 22
com closed

working module:

Code:

test baudrate:  9600
test baudrate selection:   0
tout as adc
RF option applied...
(True, [])
test running : False
serial port opened
Connecting...
chip sync ok!
0x3ff00050: 7b6a0000
0x3ff00054: 02001269
0x3ff00058: 6400b000
0x3ff0005c: 005ccf7f
EFUSE MODE : 1
reg0:7b6a0000
reg1:02001269
reg2:6400b000
reg3:005ccf7f
check_err_0: 0b
check_err_1: 00
check_err_2: 00
check_err_3: 02
check_err_4: 0b
====================
EFUSE NORMAL MODE
====================
=========================
CRC IN MODE 1:
crc_calc_res: 100
target crc val: 100
=========================
=========================
CRC IN MODE 1:
crc_calc_res: 106
target crc val: 106
=========================



==================
EFUSE LOG:
======================
EFUSE LOG:
---------------
REG0:7B6A0000
REG1:02001269
REG2:6400b000
REG3:005CCF7F
----------------
====================
EFUSE NORMAL MODE
====================
EFUSE CHECK PASS...
=================
reg2>>13: 5
=================
48bit mac
debug:
-----------------------
 5c cf 7f 12 69 7b
ID FOR XM: 06 40 00 00 00 06 A0 00
XM_ID: 064000000006A000
-----------------------
crc_efuse_4bit: 0
crc_calc_4bit: 10
48bit mac
MAC AP : 5E-CF-7F-12-69-7B
MAC STA: 5C-CF-7F-12-69-7B
get mac res:  True
('tttest uuuuuuuuuuart : uart reg: ', 236)
(' baudrate: ', 230400)
get crystal: 27187200
head: 0 ;total: 0
erase size : 0
get flash id : 0xff1640e0
 manufacturer_id: 0xe0

 device_id: 0x4016

vendor: 224
mode: 64
size: 22
com closed

Does the efuse warning and error indicate some chip failure?

Statistics: Posted by tomchees — Fri Apr 15, 2016 6:10 am

Re: Cannot recover from Fatal exception (0): problem during boot

2016-04-14T17:51:37+08:00

Hi,

Please refer to documentation 2A-ESP8266-SDK__Getting_Started_Guide to download bin files into Flash.

To download user1.bin, it should be
boot_v1.5.bin downloads to flash 0x00000.
user1.bin downloads to flash 0x01000.
If your flash size is 8Mbit, download blank.bin into 0xfe000.

Thanks for your interest in ESP8266!

Statistics: Posted by ESP_Faye — Thu Apr 14, 2016 5:51 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-04-13T06:30:33+08:00

Hi,

+1 to the issue report above.
Yesterday my module started to return the same error at bootup:

Code:

ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x40100000, len 612, room 16
tail 4
chksum 0x12
load 0x3ffe8000, len 788, room 4
tail 0
chksum 0x50
load 0x3ffe8314, len 264, room 8
tail 0
chksum 0x4a
csum 0x4a

2nd boot version : 1.1
  SPI Speed      : 40MHz
  SPI Mode       : QIO
  SPI Flash Size : 32Mbit
jump to run user1

Fatal exception (0):
epc1=0x40211558, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000

Fatal exception seems to happen only when "user1.bin" code is being executed. When i tried to flash everything except user1.bin, there's no exception, only the "user code done" message.
There was no special situation causing the module to give this error - it happened just after one of the power cycles.

Is that possible that one of the eFuses was blown accidentally due to e.g. too slow or too fast Vdd ramp up?

Statistics: Posted by tomchees — Wed Apr 13, 2016 6:30 am

Re: Cannot recover from Fatal exception (0): problem during boot

2016-03-02T14:31:35+08:00

Hii,
Please help me. I am also facing the exact problem what he had faced. Exact same Fatal exception (0): while booting time. I don't know why esp8266-01 behaving like this. Yesterday, when I was using esp its working fine for sometime but after 5min it starts booting again i mean reset, showing same error what he had got. same thing like what I see on my serial monitor is
load 0x3ffe8000, len 788, room 4
tail 0
chksum 0x50
load 0x3ffe8314, len 264, room 8
tail 0
chksum 0x4a
csum 0x4a

2nd boot version : 1.1
SPI Speed : 40MHz
SPI Mode : QIO
SPI Flash Size : 32Mbit
jump to run user1

Fatal exception (0):
epc1=0x40211558, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000

I read datasheet, some articles of esp8266 before using it. Powersupply is okay ie 3.3v which I give through asm1117. One more thing, when we give the power to esp-01, after 3-4 min its automatically restarting again and again and red led turn off. I don't know why esp is behaving like this.

Please reply on this, I am trying from last 10 days and seriouslly now I fed up.

Thanks
Shashank Arora

Statistics: Posted by shashank0792 — Wed Mar 02, 2016 2:31 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-02-28T00:12:49+08:00

Now that the module is dead this cant be tested but one of the issues could be this.

If GPIO2 is held even slightly low during boot and GPIO0 is held floating, ESP8266 runs with the same error message of fatal exception on the magic baud rate that you ended with up.

There is a a possibility that something on the RF-12 board or your PCB was causing GPIO2 to held lower than the required voltage.

But now that the board is dead it cant be tested.
However please let us know if you specifically tested this. Typically connecting GPIO2 to Vcc via a 10k solves this problem

Statistics: Posted by pk_rulz — Sun Feb 28, 2016 12:12 am

Re: Cannot recover from Fatal exception (0): problem during boot

2016-01-28T17:10:35+08:00

Admin wrote:
Please send us both. We are curious why it dies. And for your case, we will be glad reimburse for both the board and the module. We will make the results of our debugging available when it's done.

Ok, it is a pleasure if I can help you.
Please send me shipment details, I will send you both parts.

Statistics: Posted by beegee1962 — Thu Jan 28, 2016 5:10 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-01-28T15:02:10+08:00

Please send us both. We are curious why it dies. And for your case, we will be glad reimburse for both the board and the module. We will make the results of our debugging available when it's done.

Statistics: Posted by Admin — Thu Jan 28, 2016 3:02 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-01-28T10:41:40+08:00

Admin wrote:
Would you like to ship your dead module to us? we have very strict RMA policies and we would like to conduct a postmortem on this. There are many possibilities and for this case, the manufacturing process has been rather convoluted from a module house to Adafruit to you. it may be hard for us to pin-point the failure mode. But the usual suspects are ESD or ill-designed power supplies, failure of the flash, or even the capacitor and of course, failure of the chip is a possibility. But because we have done so much testing on our chip, we think that this is absolutely the least probable cause.

.......

If you are using a module other than WROOM modules, it's possible that some manufacturers are not using Espressif's recommended BOM list.

We would be glad to replace your part, if you could send it to us, at our expense, for more analysis.

Yeah, I can send you the part (at your expense) if you are really interested.
Please check the attached pictures of the current status of the board:

Please be aware that the connector pins on the board suffered by the desoldering from the Adafruit HUZZAH carrier board.
Would you like me to send both the ESP8266 module and the Adafruit HUZZAH carrier board?
In case the Espressif SOIC was not destroyed by ESD, will you send me a replacement?
Please send me a private message with the shipment details.

Statistics: Posted by beegee1962 — Thu Jan 28, 2016 10:41 am

Re: Cannot recover from Fatal exception (0): problem during boot

2016-01-27T12:18:25+08:00

Would you like to ship your dead module to us? we have very strict RMA policies and we would like to conduct a postmortem on this. There are many possibilities and for this case, the manufacturing process has been rather convoluted from a module house to Adafruit to you. it may be hard for us to pin-point the failure mode. But the usual suspects are ESD or ill-designed power supplies, failure of the flash, or even the capacitor and of course, failure of the chip is a possibility. But because we have done so much testing on our chip, we think that this is absolutely the least probable cause.

Espressif's chips are exclusively manufactured by TSMC, which in the area of CMOS technology, probably has the best reliability, RF device performance and power consumption in the industry based on what we have seen so far.

We have shipped 50 million WiFi parts in various industries without issues. While it's possible that what you have seen is a statistical blip, it is more probable that some part of the module has been damaged, or there is over-voltage or ESD from the pins of the module, since these pins are directly connected to the chip?

For your case, we suspect that we would see over-voltage, because of the presence of EFUSE errors, which means that a high voltage has occurred and burnt out some EFUSES such that our firmware's CRC detects an error. Burning out EFUSE is probably not possible without entering into a test mode, or direct application of a very high voltage.

On Reliability and Quality:
Our WiFi chip product lines are qualified by accredited external test houses, for ESD performance, reliable operation for 20 years under normal operating conditions and normal usage. The test results are available upon request from us.

The WROOM modules marketed by Espressif are also qualified by accredited external test houses, which means that we qualify all the parts on the module, including capacitors, resistors, crystal, and flash. There are a couple of versions of WROOM modules with different operating temperature range, but they are all qualified for 10 years of reliable operations. Test results are available upon request.

If you are using a module other than WROOM modules, it's possible that some manufacturers are not using Espressif's recommended BOM list.

We would be glad to replace your part, if you could send it to us, at our expense, for more analysis.

Statistics: Posted by Admin — Wed Jan 27, 2016 12:18 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-01-26T10:25:24+08:00

Admin wrote:
I think it's possible that the flash device might have failed. the other possibility is with the regulator.
yes, while it's possible that ESP8266 might have failed, it's extremely unlikely. If it has failed, then probably it is due to very high voltage ESD on the VDD_RTC pin, or VDD33 pin. it's best not to remove the cover.

The module failed while it was mounted in a housing, no possibility that ESD would have touched any pin.
The cover was removed after the module died.

As a last try I separated the ESP8266 module now from the Adafruit carrier board. The carrier board works fine, 3.3V generation is ok, level shifters work fine, switches work fine.
Tried to supply the ESP8266 module just with 3.3V and see if I can get any reaction from it, but it is complete dead now.

RIP

Statistics: Posted by beegee1962 — Tue Jan 26, 2016 10:25 am

Re: Cannot recover from Fatal exception (0): problem during boot

2016-01-19T14:55:25+08:00

I think it's possible that the flash device might have failed. the other possibility is with the regulator.
yes, while it's possible that ESP8266 might have failed, it's extremely unlikely. If it has failed, then probably it is due to very high voltage ESD on the VDD_RTC pin, or VDD33 pin. it's best not to remove the cover.

Statistics: Posted by Admin — Tue Jan 19, 2016 2:55 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-01-18T18:14:08+08:00

Espressif_Faye wrote:
Hi,

Did you use 5V power supply to connect to ESP8266 directly ?

Could you help us debug the hardware of your module following below steps :
1. Measure the voltage of ESP8266's pin VDD.
2. Use hot air gun to remove the wifi Chip from the PCB board and measure the resisitence of each pin to the ground to check if the chip is broken.
3. Power on the ESP8266 module, measure the voltage of ESP8266's 3V3 pin.

Thanks for your interest in ESP8266 !

I am using an Adafruit HUZZAH ESP8266 module. This module has an onboard 3.3V regulator.

I measured the voltage on ESP8266 VDD pin
=> 3.3V

I measured all pins of the ESP8266 module against ground
=> all are high resistance, nothing shorted to ground

I removed the metal cover on the ESP8266 module and measured all pins of the Espressif chip against GND
=> all high resistance

I powered the board and measured all VDD pins at the 32pin QFN chip (Tensilica L106??)
Pin 1 + 30 VDDA = 3.3V
Pin 3 + 4 VDD3P3 = 3.3V
Pin 5 VDD_RTC = 0.08V
Pin 12 + 17 VDDPST = 3.3V
Pin 29 VDDD = 3.3V

But something else has changed before I measured all these values and before I removed the metal cover.

A few days ago, when I powered up the module, the blue LED was light up and the red LED was dimmed light up. When I pressed RESET while keeping GPIO0 connected to ground, the blue LED stayed off, the red LED was dimmed light up and I could get the bootloader message over serial connection. I could even program the module, but the program didn't work (see my first post).

Today when I powered up the module, none of the LEDs was light up nothing is visible on the serial connection (even at 74880 baud) and even with RESET and GPIO0 on ground I cannot get the module into programming mode anymore.

I guess the module is now complete dead. Looks like I need to buy a new module. Hope it is working longer than this one.

Thanks for your support.

Statistics: Posted by beegee1962 — Mon Jan 18, 2016 6:14 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-01-18T14:12:40+08:00

Hi,

Did you use 5V power supply to connect to ESP8266 directly ?

Could you help us debug the hardware of your module following below steps :
1. Measure the voltage of ESP8266's pin VDD.
2. Use hot air gun to remove the wifi Chip from the PCB board and measure the resisitence of each pin to the ground to check if the chip is broken.
3. Power on the ESP8266 module, measure the voltage of ESP8266's 3V3 pin.

Thanks for your interest in ESP8266 !

Statistics: Posted by ESP_Faye — Mon Jan 18, 2016 2:12 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-01-14T17:33:36+08:00

Espressif_Faye wrote:
Hi,

Sorry that it seems your module is broken. Please try it with another module..

I was afraid it is broken. What exactly is the "EFUSE" doing? Any chance to repair the board by e.g. replacing the flash chip?

Statistics: Posted by beegee1962 — Thu Jan 14, 2016 5:33 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-01-13T15:27:19+08:00

Hi,

Sorry that it seems your module is broken. Please try it with another module..

Statistics: Posted by ESP_Faye — Wed Jan 13, 2016 3:27 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-01-11T21:04:35+08:00

Espressif_Faye wrote:
Hi,

Please try:
0x000000 boot_v1.5.bin
0x001000 user1.bin
0x3fc000 esp_init_data_default.bin
0x3fe000 blank.bin

Flash size in ESP FLASH Download Tool to be 32Mbit.

Here is the latest firmware ESP8266_NONOS_SDK_V1.5.1.

If your problem is still unsolved, please provide the captured picture of ESP FLASH Download Tool while downloading.

Thanks for your interest in ESP8266 !

Thanks for your reply.
I tried what you proposed, but no difference, still get Fatal exception(0): after boot (if a user1.bin was flashed).

One question: in the readme.txt in the sdk tool it is written:

Code:

Flash size 32Mbit: 512KB+512KB
boot_v1.2+.bin         0x00000
user1.1024.new.2.bin     0x01000
esp_init_data_default.bin   0x3fc000 (optional)
blank.bin              0x7e000 & 0x3fe000

Is this the one I should use with the ESP12 module? But you said blank.bin needs only to be flashed at 0x3fe000?

I attached three screenshots. Recover-ESP8266-1.JPG is the ESP FLASH Download tool just before flashing, Recover-ESP8266-2.JPG & Recover-ESP8266-3.JPG is the output in the terminal window of the Download tool. Recover-ESP8266-4.JPG is the Download tool after flashing.

I see several EFUSE warnings/errors in the log. Maybe my module is really damaged:

Code:

...
======================
EFUSE NORMAL MODE
======================
bit[1:0] error
bit[59:56] error
...
bit[47:24] crc warning
efuse warning found
...
======================
EFUSE NORMAL MODE
======================
EFUSE VAL ERROR...
EFUSE VAL WARNING...
EFUSE CRC WARNING...
...

I don't know what the EFUSE is doing, but there seems to be something wrong.

Statistics: Posted by beegee1962 — Mon Jan 11, 2016 9:04 pm

Re: Cannot recover from Fatal exception (0): problem during boot

2016-01-11T16:25:34+08:00

Hi,

Please try:
0x000000 boot_v1.5.bin
0x001000 user1.bin
0x3fc000 esp_init_data_default.bin
0x3fe000 blank.bin

Flash size in ESP FLASH Download Tool to be 32Mbit.

Here is the latest firmware ESP8266_NONOS_SDK_V1.5.1.

If your problem is still unsolved, please provide the captured picture of ESP FLASH Download Tool while downloading.

Thanks for your interest in ESP8266 !

Statistics: Posted by ESP_Faye — Mon Jan 11, 2016 4:25 pm

Cannot recover from Fatal exception (0): problem during boot

2016-01-08T12:26:18+08:00

Used hardware: Adafruit HUZZAH ESP8266 ESP12

Used software:

https://github.com/espressif/ESP8266_AT

https://github.com/nodemcu/nodemcu-firmware/releases

Used flash tools:

What happened:

Found error codes:
On serial monitor (74880 baud) module shows always endless loop of

Code:

Fatal exception (0): 
epc1=0x40211668, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000]

Trial to recover:
a) Reflash module with working code (works on different ESP12 module). ==> fail, same error, only epc1=0x... shows different address
Terminal output:

Code:

 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x4010f000, len 1264, room 16 
tail 0
chksum 0x42
csum 0x42
~ld
Fatal exception (0): 
epc1=0x402147a4, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000

b) Reflash module with NodeMCU 0.9.6 ==> fail, same error, only epc1=0x... shows different address

Code:

 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x4010f000, len 1264, room 16 
tail 0
chksum 0x42
csum 0x42
~ld
Fatal exception (0): 
epc1=0x402147a4, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000

c) Reflash module with lates AT firmware found on github => fail, same error, only epc1=0x... shows different address

Code:

 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x40100000, len 612, room 16 
tail 4
chksum 0x12
load 0x3ffe8000, len 788, room 4 
tail 0
chksum 0x50
load 0x3ffe8314, len 264, room 8 
tail 0
chksum 0x4a
csum 0x4a

2nd boot version : 1.1
  SPI Speed      : 40MHz
  SPI Mode       : QIO
  SPI Flash Size : 32Mbit
jump to run user1

Fatal exception (0): 
epc1=0x40211558, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000

d) Erase complete flash with esptool.py. Reflash module with boot and esp_init_data_default.bin (no user1.bin or user2.bin flashed!) from latest AT firmware ==> no more Fatal Exception

Code:

 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x40100000, len 612, room 16 
tail 4
chksum 0x12
load 0x3ffe8000, len 788, room 4 
tail 0
chksum 0x50
load 0x3ffe8314, len 264, room 8 
tail 0
chksum 0x4a
csum 0x4a

2nd boot version : 1.1
  SPI Speed      : 40MHz
  SPI Mode       : QIO
  SPI Flash Size : 32Mbit
jump to run user1

user code done

Try to eliminate power supply problem
Tried 4 different power supplies (Adafruit Huzzah ESP8266 has onboard power regulator, input voltage range 3.3V to 16V) and 3 different Adafruit Huzzah ESP8266 modules

=> all the 4 power supplies work fine on the 2 ESP modules without problem

Try to check for flash failure
a) Erase and read back

esptool.py erase_flash

esptool.py read_flash 0 4194304 erased.bin

b) Flash and read back

esptool.py erase_flash

0x000000 boot_v1.1.bin
0x001000 user1.bin
0x07c000 esp_init_data_default.bin
0x3fc000 esp_init_data_default.bin
0x07e000 blank.bin
0x3fe000 blank.bin
- use CombineBin to create combined file target.bin
- read back complete flash with esptool.py read_flash 0 4194304 at.bin
- compare at.bin with target.bin ==> complete content is identical

==> seems the flash is working fine

I went to a lot of forums and searched for this problem, but found no recovery solution that worked in my case.
Anybody has an idea what else I can try to recover the module?

Statistics: Posted by beegee1962 — Fri Jan 08, 2016 12:26 pm