ESP8266 Developer Zone

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

2017-06-04T23:21:44+08:00

Yes, check if your power supply is good. You may use a scope to see if power rails fall below 2.7V by setting trigger at 2.7V on your scope.

Statistics: Posted by Guest — Sun Jun 04, 2017 11:21 pm

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

2017-06-02T22:40:15+08:00

This fault because the power supply isn't good. Please prepare good one.
I made instruction to programming ESP12E via Arduino IDE, you can visit here:
http://engineer2you.blogspot.com/2017/05/esp12e-arduino-programming.html

Statistics: Posted by baank83 — Fri Jun 02, 2017 10:40 pm

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

2017-03-17T02:53:48+08:00

I do encounter the same reset:
"ets Jan 8 2013,rst cause:4, boot mode:(3,7)

wdt reset
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v3de0c112
~ld"

I am using Arduino IDE 1.8.1 with Wifi and websocket Connection and FastLED.
The ESP8266 sometimes runs for several hours without error and using the websocket connection (to a Website in a browse) and sometimes resets after several minutes. The remaining heap is constant with NO memory leaking. It seems not to be a programming error.

How can I track the error down? Any post reset information? Can it be an EMC PRoblem? Some Pins floating? I have a ESP12E Devkit 2.x from doit.am

Any ideas?

Best regards from Germany,
Andreas

Statistics: Posted by Captayne — Fri Mar 17, 2017 2:53 am

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

2017-02-12T13:44:48+08:00

I have not seen this happen in the latest firmware. But make sure that you burn in all the BIN files at the correct flash offsets and also never skip the blank.bin files.
It should work just fine then.

Statistics: Posted by Guest — Sun Feb 12, 2017 1:44 pm

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

2017-02-07T15:19:29+08:00

Hi Pratik-san,

Thank you for the feedback
We decided to change the power supply anyway.

Let me ask one more question.
Does the latest firmware include an update for this issue?

Thanks in advance,
Takashi Yamazaki

Statistics: Posted by yamazaki — Tue Feb 07, 2017 3:19 pm

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

2017-02-06T11:38:14+08:00

The reset is caused by the watchdog timer not being loaded in time. This is much more likely to be a bug in the firmware and not really a power related issue. Possible that the whole event was triggered by power issues - but rst cause 4 refers to watchdog reset.

The best solution I can propose is to upgrade to the latest AT command firmware. Also, make sure you have good decoupling close to the ESP8266. A 10uF and a 100nF in parallel are good enough usually. Modules like ESP-01 variants may not be well designed or use high ESR caps (low cost)... and then all this comes down.

Statistics: Posted by Guest — Mon Feb 06, 2017 11:38 am

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

2017-02-01T17:56:40+08:00

A reset was observed with the following message while using non-os sdk version 1.5.1.

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

wdt reset
load 0x40100000, len 1456, room 16
tail 0
chksum 0xa2
load 0x3ffe8000, len 776, room 8
tail 0
chksum 0xc3
load 0x3ffe8310, len 552, room 8
tail 0
chksum 0xb8
csum 0xb8

2nd boot version : 1.5
SPI Speed : 40MHz
SPI Mode : QIO
SPI Flash Size & Map: 16Mbit(512KB+512KB)
jump to run user1 @ 1000

r��
ready

The version info is below.

AT version:0.52.0.0(Jan 7 2016 18:44:24)
SDK version:1.5.1(e67da894)
compile time:Jan 7 2016 19:03:11

According to another topic, the reset is caused by insufficient power supply.
viewtopic.php?t=318
Could someone give me the official opinion about the reset?
If there are another possibilities, please let me know too.

One more question is below.
Does the reset cause in any sdk version?
If the latest version never caused the reset, i will update the sdk.

thanks in advance

Statistics: Posted by yamazaki — Wed Feb 01, 2017 5:56 pm