SW_RESET continuous reboot

[Anisul Mostafa]

Had you fixed this problem? Please let me know, I'm also facing same problem. How can I fix my ESP-32.
Thanks in Advance.

I have exactly same problem. Did you solve this problem?
I try to test external 3.3V power with FTDI serial board. but the result is the same with old.

rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1100
load:0x40078000,len:9232
load:0x40080400,len:6400
entry 0x400806a8
ets Jun 8 2016 00:22:57

rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1100
load:0x40078000,len:9232
load:0x40080400,len:6400
entry 0x400806a8
ets Jun 8 2016 00:22:57

rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1100
load:0x40078000,len:9232
load:0x40080400,len:6400
entry 0x400806a8
ets Jun 8 2016 00:22:57

[sumantakec]

Its due to wrong Flash Frequency selection, change 80Mhz to 40Mhz in Arduino ide tools option

for details check below video link
https://youtu.be/xvhtGhtiVn0

[juan07]

In Tools, I had selected ESP32 dev as the board, where as i was using ESP32 wrover. When i changed it accordingly in the tools>Board, my problem was solved

[tcross99]

I have spent the last three days trying EVERYTHING I could find on this forum and other sources to resolve this error on my ESP32-WROOM-32D board including the flash download tool, online reflash from (https://espressif.github.io/esptool-js/) and nothing has resolved it including:
- changing flash frequency from 80Mhz to 40Mhz
- loading board library "esp32-1.0.3-rc3.zip"
- changing board to "wrover"
- changing CPU frequency from 240Mhz to 160Mhz

Is my board fried?

Just in case I've missed something (I am a newb!), this is the error message (note counter value of 4097 - it's been going on for some time and the chip seems to have a place to store the counter so it appears healthy to me but...):

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13836
load:0x40080400,len:3608
entry 0x400805f0
Current counter value: 4097
ets Jul 29 2019 12:21:46

Is it time to move on to Teensy?

Thanks, Tom

[ESP_Sprite]

tcross99: It looks like you've flashed an Arduino example (File > Examples > Preferences > StartCounter) that is supposed to do this: it reads a counter from nonvolatile memory, increments it, prints the value, writes it back and then reboots.

[tcross99]

This is what is displayed in the serial monitor after a complete flash before even trying to load a sketch. And though I can load a sketch this continuous reboot prevents anything from running.

[tcross99]

After further pursuit of this issue via the manufacturers website (Hiletgo), this is a different beast than what I thought. I've explored esp32 via espressif and github only to finally learn that this device is NOT that but rather a "nodemcu" product. These are links related:

https://nodemcu.readthedocs.io/en/release/support/
https://nodemcu.readthedocs.io/en/release/support/
https://github.com/nodemcu/nodemcu-firm ... /dev-esp32

Having tried using esptool.py (after loading python, etc.) unsuccessfully with it's copious documentation, I was not about to embark on the road again with this nodemcu product.

Live and learn, eh?

[frevobr]

I have tried flash erase without success.
I managed to solve this issue starting the partition in 0xe000 instead of the original 0x9000.

[ByronGriggs]

Hi, I had this problem and managed to fix it. Under the board manager, I was using M5Stack by M5Stack official as my package.

When I had version 2.0.7 it worked fine, but when I updated it, it stopped working. I downgraded to 2.0.7 and it worked again.

It's worth noting that the default Baudrate is 1500000 for 2.0.8 and 921600 for 2.0.7. That's not the only difference, I'm sure, but it is the one I noticed. Maybe just changing the baudrate is sufficient?

[larsesilen]

I succeeded in fixing the continuous reboot by selecting a big partition schema and uploading a very small blink application. My guess is that the reason for the reboot was that I tried to upload an application that was too large for the previously selected partition schema (I uploaded runCPM). This probable over wrote something causing the start of the ESP32-WROOM to fail.
My guess is that any partition change will force a correction.
/Lasse