ESP-12E troubleshooting (rst cause:2, boot mode:(3,6)) #2414

rkoptev · 2016-08-20T18:12:41Z

Basic Infos

Hardware

Hardware: ESP-12E (ESP8266MOD)
Core Version: 2.3.0

Description

Hi. Previously, I was able to flash ESP through Arduino IDE. The code worked well, although very often controller restarted with no reason. "... wdt reset ..." has been written to the COM port. I tried to turn off the watch dog timer with the help of ESP.wdtDisable() or simply to increase the timeout with ESP.wdtEnable(65535). This partly solves the problem, but restarts still have a place to be.
But now, after a regular flashing I get this output in COM port:

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

load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v09f0c112
~ld

And that's all. I tried to change the module in the IDE to "ESP8266 Generic", and to change the size of the memory, but no result. What could be the problem? And how to fix this behavior?

Settings in IDE

Module: NodeMCU 1.0
Flash Size: 4MB/3MB
CPU Frequency: 80Mhz
Upload Using: SERIAL

Sketch

#include <ESP8266WiFi.h>
#include <WiFiClient.h> 
#include <ESP8266WebServer.h>
#include <FS.h>

#define DEV true

#define STEPPER_EN_PIN   13
#define STEPPER_DIR_PIN  2
#define STEPPER_STEP_PIN 5

#define STEPPER_RPM 600
#define STEPPER_GEAR_RATIO 64
#define STEPPER_MICROSTEP 16
#define STEPPER_FULL_ROTATION 7000

#define SERVER_URL "example.com"
#define SERVER_PORT 80
#define SERVER_CONNECTION_INTERVAL 10000

#define WIFI_DATA_FILENAME "/wifi.txt"
#define WIFI_CONNECTION_TIMEOUT 10000

ESP8266WebServer server(80);

char* ssid = new char[32];
char* password = new char[64];

bool jalousieState;

void moveStepper(unsigned long steps, bool direction) {
  unsigned long period = 60000000L / (STEPPER_RPM * STEPPER_GEAR_RATIO * STEPPER_MICROSTEP * 2UL);
  steps *= STEPPER_GEAR_RATIO;
  Serial.print("Period = ");
  Serial.println(period);
  digitalWrite(STEPPER_DIR_PIN, direction);
  digitalWrite(STEPPER_EN_PIN, LOW);
  for (int i = 0; i < steps; i++) {
    digitalWrite(STEPPER_STEP_PIN, HIGH);
    delayMicroseconds(period);
    digitalWrite(STEPPER_STEP_PIN, LOW);
    delayMicroseconds(period);
    ESP.wdtFeed();
  }
  digitalWrite(STEPPER_EN_PIN, HIGH);
}

void jalousieClose() {
  if (!jalousieState)
    return;
  Serial.println("Closing jalousie");
  moveStepper(STEPPER_FULL_ROTATION, 1);
  jalousieState = false;
}

void jalousieOpen() {
  if (jalousieState)
    return;
  Serial.println("Opening jalousie");
  moveStepper(STEPPER_FULL_ROTATION, 0);
  jalousieState = true;
}

void jalousieHome() {
  moveStepper(STEPPER_FULL_ROTATION, 1);
  jalousieState = false;
}

void handleWiFiCredentials() {
  if (!server.hasArg("SSID") || !server.hasArg("password")) { server.send(500, "text/plain", "Bag arguments"); return; }

  Serial.print("WiFi Credentials:\nSSID: ");
  Serial.println(server.arg("SSID"));
  Serial.print("Password: ");
  Serial.println(server.arg("password"));

  File wifiData = SPIFFS.open(WIFI_DATA_FILENAME, "w");
  wifiData.println(server.arg("SSID"));
  wifiData.println(server.arg("password"));
  wifiData.close();

  server.send(200, "text/plain", "Data saved");
  ESP.reset();
}

bool loadWiFiCredentials() {
  File wifiData = SPIFFS.open(WIFI_DATA_FILENAME, "r");
  if (!wifiData)
    return false;

  String _ssid = wifiData.readStringUntil('\n');
  _ssid.trim();
  _ssid.toCharArray(ssid, 32);

  String _password = wifiData.readStringUntil('\n');
  _password.trim();
  _password.toCharArray(password, 64);

  wifiData.close();
  return true;
}

void setup() {
  // Make the watch dog timeout longer
  ESP.wdtEnable(65535);

  Serial.begin(74880);
  Serial.setDebugOutput(DEV);

  pinMode(STEPPER_EN_PIN, OUTPUT);
  pinMode(STEPPER_DIR_PIN, OUTPUT);
  pinMode(STEPPER_STEP_PIN, OUTPUT);
  digitalWrite(STEPPER_EN_PIN, HIGH);

  // Initialize filesystem
  SPIFFS.begin();

  bool loaded = loadWiFiCredentials();
  if (loaded) {
    Serial.println("WiFi credentials loaded");
    unsigned long connectionTime = millis();
    WiFi.mode(WIFI_STA);
    WiFi.begin(ssid, password);
    while (WiFi.status() != WL_CONNECTED) {
      delay(100);
      if (millis() - connectionTime > WIFI_CONNECTION_TIMEOUT) {
        Serial.println("Connection failed. Ereasing old Wifi credentials and starting AP to get new credentials.");
        SPIFFS.remove(WIFI_DATA_FILENAME);
        ESP.reset();
      }
    }
  } else {
    Serial.println("WiFi credentials not found, starting AP");

    WiFi.mode(WIFI_AP);
    WiFi.softAP("Pentagon228");

    server.serveStatic("/", SPIFFS, "/public_html/WifiSetup.html");
    server.serveStatic("/WifiSetup.css", SPIFFS, "/public_html/WifiSetup.css");
    server.serveStatic("/WifiSetup.js", SPIFFS, "/public_html/WifiSetup.jsl");
    server.on("/submit", HTTP_POST, handleWiFiCredentials);

    server.begin();

    while(1) {
      server.handleClient();
      ESP.wdtFeed();
    }
  }
  jalousieHome();
}

void loop() {
  delay(SERVER_CONNECTION_INTERVAL);
  Serial.println("I'm alive");

  WiFiClient client;
  if (!client.connect(SERVER_URL, SERVER_PORT))
    return;

  client.print(String("GET / HTTP/1.1\r\n") +
                      "Host:" + SERVER_URL + ":" + SERVER_PORT + "\r\n" + 
                      "Connection: close\r\n\r\n");
  unsigned long timeout = millis();
  while (client.available() == 0) {
    ESP.wdtFeed();
    delay(100);
    if (millis() - timeout > 5000) {
      client.stop();
      return;
    }
  }

  while(client.available()){
    String line = client.readStringUntil('\r');
    Serial.println("Res: " + line);
    line.trim();
    if (line.equals(String("open"))) {
      jalousieOpen();
      return;
    } else if (line.equals(String("close"))) {
      jalousieClose();
      return;
    }
  }
}

WereCatf · 2016-08-20T18:26:18Z

Have you connected some new devices to GPIO 0, 2 or 15? They control the boot-mode of the ESP and if some device you've connected pulls the wrong pin high or low it'll change boot-mode from normal to something else. See https://zoetrope.io/tech-blog/esp8266-bootloader-modes-and-gpio-state-startup

rkoptev · 2016-08-20T18:35:18Z

I fundamentally don't use these pins in the project. Pin 15 is pulled down, pin 2 is pulled up, in normal mode pin 0 is pulled up, when I flash new firmware, I connect pin 2 to GND. There are no any devices connected to this pins.

WereCatf · 2016-08-20T18:45:06Z

Well, the obvious next step would be to flash the simple "blink LED" - example sketch and see if it works -- you don't mention if you've tried that or not.

rkoptev · 2016-08-20T18:50:52Z

I flashed Blink example and having the same output:
ets Jan 8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v09f0c112
~ld

supersjimmie · 2016-08-22T12:29:41Z

Did you run blink with the other hardware connected or everything disconnected?
And to what pin did you connect the LED (for blink)?

rkoptev · 2016-08-22T12:49:17Z

I have some news regarding to this issue: the module has started to work, but very unstable. Ie yesterday it has started and worked full day. Then this error again. It seems that it occurs at all accidental. The most important thing is that I do not change a sketch and wiring, everything remains as before. It's like some kind of magic ((

@supersjimmie I tried to flash Blink example with disconnected peripheral. And in addition to described ablove message it gives me stack trace:

0x40216d48: tx_pwr_backoff at ?? line ?
0x40211771: set_txcap_reg at ?? line ?
0x402135d4: tx_pwctrl_init_cal at ?? line ?
0x40211771: set_txcap_reg at ?? line ?
0x40213b40: tx_pwctrl_init at ?? line ?
0x402153a4: chip_v6_initialize_bb at ?? line ?
0x402153b9: chip_v6_initialize_bb at ?? line ?
0x40100574: malloc at C:\Users\Ruslan Koptiev\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.3.0\cores\esp8266\umm_malloc/umm_malloc.c line 1664
0x40210f77: phy_init at ?? line ?
0x40101fea: register_phy_ops at ?? line ?
0x4021615a: register_chipv6_phy at ?? line ?
0x4020498e: wifi_station_set_default_hostname at ?? line ?
0x40201789: __wrap_register_chipv6_phy at C:\Users\Ruslan Koptiev\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.3.0\cores\esp8266/core_esp8266_phy.c line 261
0x4022e340: rijndaelKeySetupEnc at ?? line ?
0x40101b1a: spi_flash_read at ?? line ?
0x40205d57: system_get_sdk_version at ?? line ?
0x402063e4: user_uart_wait_tx_fifo_empty at ?? line ?
0x402063bf: user_uart_wait_tx_fifo_empty at ?? line ?
0x4010171c: wdt_feed at ?? line ?
0x402241ed: ieee80211_node_pwrsave at ?? line ?
0x4010020c: umm_assimilate_up at C:\Users\Ruslan Koptiev\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.3.0\cores\esp8266\umm_malloc/umm_malloc.c line 1180
0x4010068c: _umm_realloc at C:\Users\Ruslan Koptiev\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.3.0\cores\esp8266\umm_malloc/umm_malloc.c line 1584
:  (inlined by) realloc at C:\Users\Ruslan Koptiev\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.3.0\cores\esp8266\umm_malloc/umm_malloc.c line 1709
0x4020bd00: tcp_send_fin at /Users/igrokhotkov/espressif/arduino/tools/sdk/lwip/src/core/tcp_out.c line 131
0x4020a638: pbuf_alloc at /Users/igrokhotkov/espressif/arduino/tools/sdk/lwip/src/core/pbuf.c line 329
0x4020c111: tcp_output at /Users/igrokhotkov/espressif/arduino/tools/sdk/lwip/src/core/tcp_out.c line 1025
0x4020ca70: udp_input at /Users/igrokhotkov/espressif/arduino/tools/sdk/lwip/src/core/udp.c line 269

But that's just matter of chance: I can get this stack trace even with peripherals connected, and can not get even when it's disconnected.

Believe me, I tried different power supplies, testing them on an oscilloscope, added a capacitor 600 uF as near as possible to the board and I tried absolutely all combinations of pins 0, 2 and 15. I even replaced the board to the other. All to no avail. I'm in a state of frustration.
I will be very grateful for any hint or tip, as I spent on the solution of this problem for over a week.

RudyFiero · 2016-08-22T17:02:31Z

What voltage regulator are you using? How far from the regulator to the ESP module? What are you using for interconnections?

I have found that capacitance alone does not deal with the dynamic current requirements. I suspect that you are having power issues.

rkoptev · 2016-08-22T18:53:00Z

ok, in order:
I use LM2596 DC voltage regulator tuned to 3.3v. Datasheet says that it is able to provide a current of 3A.
Also I use DC power adapter from old radio phone. It's provide 7.5V at 300mA.
For interconnections I use standart breadboard wires.

I tried to replace the power supply, but nothing has changed. Then, I tried to configure the voltage regulator to 3.7V, and ESP started! I do not know for how long, but if this problem is over, I'll write about it here.
Thank you for the advice, @RudyFiero .

supersjimmie · 2016-08-23T07:04:57Z

I think that the 300mA from your DC power adapter is really "on the edge"...

RudyFiero · 2016-08-23T13:11:25Z

I was a little concerned about that. But with a switching supply the current available at the output would be higher. The switcher acts more like a transformer and does a power conversion. A linear regulator just consumes the voltage difference and does not give any current gain.

WereCatf · 2016-08-23T13:19:41Z

7.5V at 300mA would equal 2.25W of power and just assuming roughly a conversion-efficiency of 90% that'd result in 3.3V and ~600mA max current, if I understand things right. I think I read somewhere that the ESP8266 can peak at a little over 200mA, so that should still be plenty for it. That does make me wonder why his ESP would only turn on at 3.7V, not 3.3V -- there must be something else at play.

rkoptev · 2016-08-23T14:30:47Z

@supersjimmie, it seems like you are right. I replaced this power supply with 24v@500mA and ESP works corectly and starts every time. It was extremely difficult to determine that the problem is in power. I am very astonished, because this chip is positioned as super energy efficient, capable of operating from a small CR2032 battary for a years.
In any case, I think that this problem can be considered solved. Thank you all for your help.

architmuchhal12 · 2017-06-06T18:04:50Z

I am having the same problem when I connect the Adafruit GSM FONA808. But it works fine when I run other programs.
Please suggest me a solution.
Thanks

kamrulroky · 2017-10-05T13:07:11Z

@architmuchhal12
Have you figured out what is the solution? I am facing the same issue with SIM800l+Nodemcu to connecting adafruit MQTT

therealsputnik · 2017-12-09T07:14:20Z

I was also having this issue powering my device (wemos D1 Mini) directly from an 18650. It seems that the problem was that as the battery runs down it creates a power problem as RudyFiero above correctly suspected. Replacing the single 18650 with a "powerbank" that puts out a constant 5V solved the problem for me immediately.

diraniyoussef · 2017-12-23T13:58:04Z

I had the same error
ets Jan 8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v09f0c112
~ld
⸮
but it happened in a specific place of code, it's when I close the client socket, the NodeMCU being a server. It happens when the client closes from NodeMCU's side or from the client's side.

KlausNZ · 2018-01-09T21:07:34Z

Hi folks,

I encountered the same issue with boot modes(1,6) and (3,6).
Development went perfectly fine and all was running smooth at 2am.
Revisiting the project the next morning all went to custard.

Finally I found the culprit and the cause for having the effect with the boot modes.

The exact reason for the continues boot mode errors shown I can;t give, but in my project it was some code failing in a class initialization of a global instance which runs before setup() is called.
Took me a while to figure out, but I got there.

So my recommendation if you encounter the same issue:
Look to your global class instances and see if code is causing exceptions before setup() is called!

Cheers,
Klaus

devyte · 2018-01-10T00:12:06Z

@KlausNZ you can't have global classes that on construction depend on on other global classes being already constructed. The order of construction of global classes is non-deterministic in C++ (it depends on the order that Translation Units are linked, which can't be controlled).

bkrajendra · 2018-01-20T18:08:33Z

Something weird is happening recently.
All our ESP boards stopped working
Getting Blank after flashing program. Nothing happens. After checking by changing baud rate to 74880
this is what we getting


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

load 0x4010f000, len 1384, room 16 
tail 8
chksum 0xef
csum 0xef
csum err
ets_main.c

gbetous · 2018-01-27T21:45:01Z

Hi,

I bought a few D1 Mini Lite, and every one is only responding with uart @74880 and this message :

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

load 0x40100000, len 2592, room 16
tail 0
chksum 0xef
load 0x00000000, len 0, room 8
tail 0
chksum 0xef
load 0x00000000, len 0, room 0
tail 0
chksum 0xef
csum 0xef
csum err
ets_main.c

I tried to flash NodeMCU, I have no errors on esptool, but nothing change : I still have this issue, and NodeMCU is not loaded

damo1023 · 2018-01-30T13:28:52Z

Something weird is happening recently.
All our ESP boards stopped working

Also my boards.... tried different ESP's, power supplies, etc... Looks like there might be a virus in IDE?

Any success solving this?

matiascolon · 2018-01-31T16:27:21Z

i have same problem

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

load 0x4010f000, len 1384, room 16
tail 8
chksum 0xef
csum 0xef
csum err
ets_main.c

WereCatf · 2018-01-31T20:19:15Z

@damo1023 I have one board that used to work in QOUT-mode, but all of sudden it now only works in DIO-mode, so I would recommend you try changing the board to a generic ESP8266, then test if changing the flash-mode to something else works. (DOUT-mode is the slowest and most compatible one, so I'd start with that.) If it does, then I suppose the issue needs further investigation.

tstepnia · 2018-02-09T12:24:14Z

In my case cause of resets and exceptions was FT232 TX line to ESP.
Now, after program upload, I disconnect it, reset ESP, leaving FT232 RX connection only to see debug output.

Chriss217 · 2018-03-07T00:13:24Z

edit: reformat

I have a UNO+WiFi R3 ATmega328P+ESP8266 32Mb board (with 8 dip switches). I tried many times to flash the firmware without success using the esptool.py. By setting sw7 to off, running miniterm.py and pressing reset button I received the same message as matiascolon e.g "ets Jan 8 2013, rst, cause:2, boot modes:(3,6)" followed by the other lines and stopping at "ets_main.c".

Following the info on "https://www.bountysource.com/issues/47667636-esp-link-on-a-robotdyn-atmega2560-esp8266" I d/l esp-link v3.0.14 and reflashed the firmware. This failed as before until I added the option "-fm dio". Now when I connected via miniterm.py and hit RST I see the result:

 ets Jan  8 2013,rst cause:2, boot mode:(3,7)
load 0x40100000, len 2408, room 16 
tail 8
chksum 0xe5
load 0x3ffe8000, len 776, room 0 
tail 8
chksum 0x84
load 0x3ffe8310, len 632, room 0 
tail 8
chksum 0xd8
csum 0xd8

2nd boot version : 1.6
  SPI Speed      : 80MHz
  SPI Mode       : DIO
  SPI Flash Size & Map: 32Mbit(512KB+512KB)
jump to run user1 @ 1000

rf cal sector: 128
rf[112] : 00
rf[113] : 00
rf[114] : 01

SDK ver: 2.0.0(5a875ba) S <binary chars>

The sequence to flash it was:

SW7 on
Reset
run "esptool.py -p /dev/ttyUSB0 erase_flash"
Reset
run "esptool.py -p /dev/ttyUSB0 write_flash -fm dio -fs 32m -ff 80m 0x00000 boot_v1.6.bin 0x01000 user1.bin 0x3fc000 esp_init_data_default.bin 0x3fe000 blank.bin"
Set SW7 off
Reset.

Using my phone I can now (at last see) a wifi station called "ESP_809A70".
I haven't tried any further tests so far, but thought I would post these results in case it helps others progress. Best. Chris

ferm10n · 2019-03-06T05:43:30Z

I just want to throw a note in here, I was having the same issue and I believe it was caused by a watchdog timer or something. Initially I had a loop function with no delays. the device would reboot about every 5 or 6 seconds.
Adding in a delay(0) in the loop corrected the issue. Removing it brings it back.

Atanas-Kolev · 2019-03-27T06:48:35Z

I have same error

Septikos94 · 2019-04-13T21:56:13Z

@damo1023 I have one board that used to work in QOUT-mode, but all of sudden it now only works in DIO-mode, so I would recommend you try changing the board to a generic ESP8266, then test if changing the flash-mode to something else works. (DOUT-mode is the slowest and most compatible one, so I'd start with that.) If it does, then I suppose the issue needs further investigation.

This worked for me! By default, flash mode DIO is selected in the Arduino IDE. I have an ESP-01S, so change flash mode to DOUT and just worked great. Thanks.

LanFly · 2019-05-23T06:14:34Z

edit: reformat

I have a UNO+WiFi R3 ATmega328P+ESP8266 32Mb board (with 8 dip switches). I tried many times to flash the firmware without success using the esptool.py. By setting sw7 to off, running miniterm.py and pressing reset button I received the same message as matiascolon e.g "ets Jan 8 2013, rst, cause:2, boot modes:(3,6)" followed by the other lines and stopping at "ets_main.c".

Following the info on "https://www.bountysource.com/issues/47667636-esp-link-on-a-robotdyn-atmega2560-esp8266" I d/l esp-link v3.0.14 and reflashed the firmware. This failed as before until I added the option "-fm dio". Now when I connected via miniterm.py and hit RST I see the result:
 ets Jan  8 2013,rst cause:2, boot mode:(3,7)
load 0x40100000, len 2408, room 16 
tail 8
chksum 0xe5
load 0x3ffe8000, len 776, room 0 
tail 8
chksum 0x84
load 0x3ffe8310, len 632, room 0 
tail 8
chksum 0xd8
csum 0xd8

2nd boot version : 1.6
  SPI Speed      : 80MHz
  SPI Mode       : DIO
  SPI Flash Size & Map: 32Mbit(512KB+512KB)
jump to run user1 @ 1000

rf cal sector: 128
rf[112] : 00
rf[113] : 00
rf[114] : 01

SDK ver: 2.0.0(5a875ba) S <binary chars>
The sequence to flash it was:
SW7 on
Reset
run "esptool.py -p /dev/ttyUSB0 erase_flash"
Reset
run "esptool.py -p /dev/ttyUSB0 write_flash -fm dio -fs 32m -ff 80m 0x00000 boot_v1.6.bin 0x01000 user1.bin 0x3fc000 esp_init_data_default.bin 0x3fe000 blank.bin"
Set SW7 off
Reset.
Using my phone I can now (at last see) a wifi station called "ESP_809A70".
I haven't tried any further tests so far, but thought I would post these results in case it helps others progress. Best. Chris

Hi, I recently encountered this problem when designing open source hardware.

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

The reason for this problem is that the current of the power supply is insufficient.

Solution：At least 3.3V 300mA of power supply.

I hope this will help you.

molsondry · 2019-07-15T22:54:05Z

Hi guys,
I had the same problem: after 3 or 4 connection fails the system restarted with the codes mentioned above. I just moved the Wifi connection routine to the beginning of the setup routine. Before I started two ISRs before starting the Wifi. Now it works.

void setup() {
// put your setup code here, to run once:
// Console parameters
Serial.begin(115200);

// Wifi startup, should be here in the beginning of setup, further down it caused periodically restarts
connectWiFi();

// Capacitive Sensor for detecting door open-close/
// Oscillator configurations
pinMode(oscillatorPin, INPUT_PULLUP);
attachInterrupt(digitalPinToInterru........................

void volatile connectWiFi (){
// We start by connecting to a WiFi network

Serial.println();
Serial.println();
Serial.print("Connecting to ");
Serial.println(ssid);

/* Explicitly set the ESP8266 to be a WiFi-client, otherwise, it by default,
would try to act as both a client and an access-point and could cause
network-issues with your other WiFi-devices on your WiFi-network. */

WiFi.mode(WIFI_STA);
WiFi.begin(ssid, password);

while (WiFi.status() != WL_CONNECTED) {
delay(500);
Serial.print(".");
}

Serial.println("");
Serial.println("WiFi connected");
Serial.println("IP address: ");
Serial.println(WiFi.localIP());

// Try and create TCP connections
/*
if (!sta.connect("heise.de", 80)) {
Serial.println("connection failed");
delay(5000);
return;
}
*/

norellanac · 2019-07-29T19:29:33Z

i started the connection to wifi again before to use the http.begin(). it worked for me

theicfire · 2019-08-16T17:25:56Z

Some details I found:

rst cause:2, boot mode:(3,6) happens on startup for all my ESP8266 devices. (WeMos D1, NodeMCU v1.0). I didn't realize this was the case because at startup by default the baud rate is 74880. However, after this message prints everything works fine
I was finding that sometimes my devices would continually boot loop with this message. I haven't found the root cause, but I had 3 devices on at the same time and the third one was always boot looping. Very odd, but probably just my own problem

quango2304 · 2019-09-22T15:21:18Z

Hi,
I have solved the problem by
Tools > Erase Flash > All contents
compiled and uploaded again
the boot problem did not occur anymore ... until now !

thank you, it works greatly!!

philongvn99 · 2019-09-29T17:08:57Z

I dont think anyone get in rediculous situation as me, but if you have declared iostream lib. in cpp or header file, lets remove it first!!!

muito93 · 2019-10-09T02:19:05Z

Hi,
I have solved the problem by
Tools > Erase Flash > All contents
compiled and uploaded again
the boot problem did not occur anymore ... until now !

@hassin23ayz It worked, thank you

shubham-kulkarni · 2019-10-18T12:26:46Z

I am facing the same issue. I accidentally pressed "reset" button on the board while uploading was in progress (nearly 60%). Now when I am connecting the board to my PC, its detected. I am also able to upload the sketch to the board. But its misbehaving. Inbuilt LED is constantly flashing and I see the mentioned error on serial screen (Baud Rate 115200 / NL&CR).

vivekanandRdhakane · 2019-12-03T13:56:45Z

Hi,
I have solved the problem by
Tools > Erase Flash > All contents
compiled and uploaded again
the boot problem did not occur anymore ... until now !

thanks. It worked

faelpinho · 2020-01-03T01:51:30Z

Have no solution?
I got only this message when GPIO_0 is GND:
" ets Jan 8 2013,rst cause:2, boot mode:(3,6)

ets_main.c "

Nothing more.
And I got this message when GPIO_0 is VCC:
" ets Jan 8 2013,rst cause:2, boot mode:(1,7)"
Nothing more.

I have clicked "Erase" button on ESP8266 Download Tool V.3.6.8, and the prompt shows this message:
CONNECT BAUD: 115200

.Uploading stub...
Running stub...
Stub running...

crc_efuse_4bit: 0
crc_calc_4bit: 8
48bit mac
"

bbxmbb · 2020-04-01T14:17:36Z

I solve this problem when download older version of the esp8266 to version 2.5.0 and everything works again.

skybadger · 2020-04-27T08:43:43Z

I am using ESP8266-12 and 2.6.3 core.
I had this problem and walked back to code, sorted out some bad variables ( clash with internal libraries vs local include settings, turned off pre-cache to ensure libraries got rebuilt and fixed my pins allocation - I was forgetting pins are not the same as GPIOs and it all works.

Oh, and having downloaded the GH latest head ( v4.1) , I still needed to add the ICACHE RA ATTR in front of all the ISR functions.
But it is working and with interrupts too.
Very nice. Took about 3 hours of faff when it should have taken 5 mins but that's hardware.

k-byte-rgb · 2020-07-26T18:49:33Z

Find the problem, since I am new to esp8266, don't know bad program will cause rest loop of hardware ...., Download another program solve the problem ...

which programmer?

DavidDeeds · 2020-09-21T13:46:56Z

I had the same issue and resolved it.
My code was originally written using ESP8266 Arduino Core 2.6.3 (or close to - it was an older version..).
I updated to ESP8266 Arduino Core 2.7.4 tonight and got this issue.

I recalled reading in recent months that there were some changes and enhancements in how interrupts ( ISR s ) were handled as a result of the ESP8266 Arduino Core development over time.

I revisited my interrupt code and had to add ICACHE_RAM_ATTR in.

There is a good read here on stackoverflow about it: https://stackoverflow.com/questions/58113937/esp8266-arduino-why-is-it-necessary-to-add-the-icache-ram-attr-macro-to-isrs-an and also the general ESP8266 Arduino Core reference library here https://arduino-esp8266.readthedocs.io/en/latest/reference.html

My boards are both the Lolin Wemis D1 Mini Pro 2.0.0 and Lolin Wemis D1mini that I was experiencing this on.
Problem solved and not soo much time lost! Hope this helps someone else!! :)

ThovReime · 2021-03-13T11:42:44Z

I had the same problem, solved it with hassin23ayz 's method:
Tools -> Erase flash -> All flash contents.
No more rst cause:2 boot mode (3,6), all working well :)

mmdhossein · 2021-03-17T11:19:26Z

The problem i had (rst cause:1, boot mode:(3,7)), was laid down in my code where i defined an ISR which encountered the code memory and due to that , esp rebooted continuously.
Thanks to this thread, i used ICACHE_FLASH_ATTR in my ISR function which solved the rebooting thing. Hope it be a help for anyone have my problem.

jhalak333 · 2021-03-27T08:54:07Z

this is due to long processing on loop while acting as webserver...

k-byte-rgb · 2021-03-27T16:55:26Z

Fine problem solve a while ago thanks for the awnsers sorry for not responding Outlook for Android<https://aka.ms/ghei36> downloaden

…

________________________________ From: jhalak333 ***@***.***> Sent: Saturday, March 27, 2021 9:54:20 AM To: esp8266/Arduino ***@***.***> Cc: k-byte-rgb ***@***.***>; Comment ***@***.***> Subject: Re: [esp8266/Arduino] ESP-12E troubleshooting (rst cause:2, boot mode:(3,6)) (#2414) this is due to long processing on loop while acting as webserver... — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#2414 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQLDSIJ37L2VUXKZYB5MSILTFWMLZANCNFSM4CNEQWYQ>.

Archy404 · 2021-05-11T08:05:06Z

To everyone having the same Problem as the OP. I had it too.

The Problem is, that the ESP8266 crashes during the rotation of the stepper motor because it can not handle the WiFi tasks that continuisly run in the background while only having a few microseconds delay.

I added the yield(); function to my rotation loops and the crashes are gone.

At least that was the Problem with me, since we are basically doing the same thing and i had the problem i assume this would be the solution for this case too.

AbdelrahmanMryan · 2021-07-10T22:09:06Z

Try to upload a blink code on Arduino Uno , then switch to ESP and upload the code again , I had the same problem and it solved

HamzaHajeir · 2021-08-03T17:49:22Z

Hi,
I have solved the problem by
Tools > Erase Flash > All contents
compiled and uploaded again
the boot problem did not occur anymore ... until now !

It seems to work

But it's too ugly to be forced to do it everytime, especially if we must do dynamic configuration each time! Why just does it happens?

jorgecujcuj · 2021-10-23T07:09:18Z

me dio ese error:

ets Jan 8 2013,rst cause:2, boot mode:(3,6) load 0x4010f000, len 3460, room 16 tail 4 chksum 0xcc load 0x3fff20b8, len 40, room 4 tail 4 chksum 0xc9 csum 0xc9 v00041c40 ~ld

lo que hice fue eliminar la librería de LiquidCrystal_I2C y funciono de nuevo con otra librería

whogarden · 2022-02-02T16:53:11Z

If it can help.
I had the same pb (from initial post 20 Aug 2016)
Just try Flash mode : "Dout compatible"

halilcankaroglu · 2022-08-13T06:56:14Z

I have same issue. ESP8266 in restarting loop. I try this ICACHE_RAM_ATTR and working :) you must add before setup() and same name your method like this void ICACHE_RAM_ATTR door();

I had the same issue and resolved it. My code was originally written using ESP8266 Arduino Core 2.6.3 (or close to - it was an older version..). I updated to ESP8266 Arduino Core 2.7.4 tonight and got this issue.

I recalled reading in recent months that there were some changes and enhancements in how interrupts ( ISR s ) were handled as a result of the ESP8266 Arduino Core development over time.

I revisited my interrupt code and had to add ICACHE_RAM_ATTR in.

There is a good read here on stackoverflow about it: https://stackoverflow.com/questions/58113937/esp8266-arduino-why-is-it-necessary-to-add-the-icache-ram-attr-macro-to-isrs-an and also the general ESP8266 Arduino Core reference library here https://arduino-esp8266.readthedocs.io/en/latest/reference.html

My boards are both the Lolin Wemis D1 Mini Pro 2.0.0 and Lolin Wemis D1mini that I was experiencing this on. Problem solved and not soo much time lost! Hope this helps someone else!! :)

ttww · 2022-08-14T18:17:21Z

Hi folks,

I encountered the same issue with boot modes(1,6) and (3,6). Development went perfectly fine and all was running smooth at 2am. Revisiting the project the next morning all went to custard.

Finally I found the culprit and the cause for having the effect with the boot modes.

The exact reason for the continues boot mode errors shown I can;t give, but in my project it was some code failing in a class initialization of a global instance which runs before setup() is called. Took me a while to figure out, but I got there.

So my recommendation if you encounter the same issue: Look to your global class instances and see if code is causing exceptions before setup() is called!

Cheers, Klaus

Same problem here.
I had some errors in a global class instance (SoftwareSerial) which cause this problem.
The declaration for the baudRate were u_int8_t instead u_int_32 and switching to 19200 leads to an overflow which leads to a baud rate of 0 which leads to a division by zero exception....

Thank you Klaus!

Ciao
Thomas

villivateur · 2023-04-16T06:24:12Z

Hi, I have solved the problem by Tools > Erase Flash > All contents compiled and uploaded again the boot problem did not occur anymore ... until now !

It works. But I just wonder, why?

rkoptev closed this as completed Aug 23, 2016

dilthings mentioned this issue Oct 24, 2017

[SOLVED]ESP8266 crashes after firmware upgrade (Arduino, nodemcu) #3753

Closed

Aypac mentioned this issue Oct 30, 2017

Incompatibility to WiFi Manager or another WiFi Connection? Aypac/Arduino-TR-064-SOAP-Library#2

Closed

adavidzh mentioned this issue Dec 11, 2017

rst cause:4,boot mode(1,6) #2829

Closed

Avamander mentioned this issue Jan 11, 2018

Help making sense of the library NodeMCU nRF24/RF24#403

Closed

Dattel mentioned this issue Jan 30, 2021

Strange Total-Crash Failure after a couple of days/weeks ESP32 RF gateway 1technophile/OpenMQTTGateway#854

Closed

ESP-12E troubleshooting (rst cause:2, boot mode:(3,6)) #2414

ESP-12E troubleshooting (rst cause:2, boot mode:(3,6)) #2414

Comments

rkoptev commented Aug 20, 2016 • edited

Basic Infos

Hardware

Description

Settings in IDE

Sketch

WereCatf commented Aug 20, 2016

rkoptev commented Aug 20, 2016

WereCatf commented Aug 20, 2016

rkoptev commented Aug 20, 2016 • edited

supersjimmie commented Aug 22, 2016

rkoptev commented Aug 22, 2016

RudyFiero commented Aug 22, 2016

rkoptev commented Aug 22, 2016

supersjimmie commented Aug 23, 2016

RudyFiero commented Aug 23, 2016

WereCatf commented Aug 23, 2016

rkoptev commented Aug 23, 2016

architmuchhal12 commented Jun 6, 2017

kamrulroky commented Oct 5, 2017

therealsputnik commented Dec 9, 2017

diraniyoussef commented Dec 23, 2017

KlausNZ commented Jan 9, 2018

devyte commented Jan 10, 2018

bkrajendra commented Jan 20, 2018

gbetous commented Jan 27, 2018

damo1023 commented Jan 30, 2018

matiascolon commented Jan 31, 2018

WereCatf commented Jan 31, 2018

tstepnia commented Feb 9, 2018 • edited

Chriss217 commented Mar 7, 2018 • edited by d-a-v

ferm10n commented Mar 6, 2019

Atanas-Kolev commented Mar 27, 2019

Septikos94 commented Apr 13, 2019

LanFly commented May 23, 2019

molsondry commented Jul 15, 2019

norellanac commented Jul 29, 2019

theicfire commented Aug 16, 2019

quango2304 commented Sep 22, 2019

philongvn99 commented Sep 29, 2019 • edited

muito93 commented Oct 9, 2019

shubham-kulkarni commented Oct 18, 2019

vivekanandRdhakane commented Dec 3, 2019

faelpinho commented Jan 3, 2020

I have clicked "Erase" button on ESP8266 Download Tool V.3.6.8, and the prompt shows this message: CONNECT BAUD: 115200

.Uploading stub... Running stub... Stub running...

bbxmbb commented Apr 1, 2020 • edited

skybadger commented Apr 27, 2020

k-byte-rgb commented Jul 26, 2020

DavidDeeds commented Sep 21, 2020

ThovReime commented Mar 13, 2021

mmdhossein commented Mar 17, 2021

jhalak333 commented Mar 27, 2021

k-byte-rgb commented Mar 27, 2021 via email

Archy404 commented May 11, 2021 • edited

AbdelrahmanMryan commented Jul 10, 2021

HamzaHajeir commented Aug 3, 2021

jorgecujcuj commented Oct 23, 2021

whogarden commented Feb 2, 2022

halilcankaroglu commented Aug 13, 2022

ttww commented Aug 14, 2022 • edited

villivateur commented Apr 16, 2023

rkoptev commented Aug 20, 2016 •

edited

rkoptev commented Aug 20, 2016 •

edited

tstepnia commented Feb 9, 2018 •

edited

Chriss217 commented Mar 7, 2018 •

edited by d-a-v

philongvn99 commented Sep 29, 2019 •

edited

I have clicked "Erase" button on ESP8266 Download Tool V.3.6.8, and the prompt shows this message:
CONNECT BAUD: 115200

.Uploading stub...
Running stub...
Stub running...

bbxmbb commented Apr 1, 2020 •

edited

Archy404 commented May 11, 2021 •

edited

ttww commented Aug 14, 2022 •

edited