ESP32-WROVER stuck in reboot loop with simple Serial.println() sketch

Hello everyone,

I’m using an ESP32-WROVER board and trying to upload a simple sketch that just prints “Hello world!” to the serial monitor. However, after uploading, the board keeps rebooting and the serial monitor shows an infinite stream of output like this:

rst:0x7 (TG0WDT_SYS_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:4888
load:0x40010000,len:0
load:0x3fb52000,len:259983820
1150 mmu set 00010000, pos 00010000
1150 mmu set 00020000, pos 00020000
...

Here is the exact sketch I’m uploading:

void setup() {
    Serial.begin(115200);
}

void loop() {
    Serial.println("Hello world!");
    delay(1000);
}

I selected “ESP32 Wrover Module” as the board in the Arduino IDE. The upload works fine (no compilation or upload error), but the board keeps restarting.

Has anyone encountered this issue? What could be causing this reboot loop, and how can I fix it?

Thank you in advance!

Add a delay of 1000 or 2000 after the begin. Make sure the Serial monitor is also set to 115200. Let us know what happens.

If it still fails, post in code tags the entire verbose upload log.

FYI BTW, your log does NOT show a loop. Always post the entire cycle with some overlap.

Watchdog barks :).

Looks like damaged flash. Can not be segment length like this

Just select a normal esp32 Dev module. Also show an entire cycle from boot to boot.

thank you for answers here is what I get in my serial monitor (I ve add the delay like you said but it changes nothing and I also tried blink)

ets Jul 29 2019 12:21:46

rst:0x10 (RTCWDT_RTC_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:4888

load:0x40078000,len:16516

load:0x40080400,len:4

load:0x40080404,len:3476

entry 0x400805b4

E (30) qio_mode: Failed to set QIE bit, not enabling QIO mode

E (30) flash_parts: partition 0 invalid magic number 0x502a

E (30) boot: Failed to verify partition table

E (34) boot: load partition table error!

ets Jul 29 2019 12:21:46

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:0x3fff0030,len:4888

load:0x40010000,len:0

load:0x3ff5a000,len:1073677764

1150 mmu set 00010000, pos 00010000

1150 mmu set 00020000, pos 00020000

1150 mmu set 00030000, pos 00030000

1150 mmu set 00040000, pos 00040000

1150 mmu set 00050000, pos 00050000

ets Jul 29 2019 12:21:46

rst:0x10 (RTCWDT_RTC_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:4888

load:0x40078000,len:16516

load:0x40080400,len:4

load:0x40080404,len:3476

entry 0x400805b4
E (30) qio_mode: Failed to set QIE bit, not enabling QIO mode

E (30) flash_parts: partition 0 invalid magic number 0xa102

E (30) boot: Failed to verify partition table

E (34) boot: load partition table error!

ets Jul 29 2019 12:21:46

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:0x3fff0030,len:4888

load:0x40050000,len:0

load:0x0f752000,len:536808908

ets Jul 29 2019 12:21:46

rst:0x7 (TG0WDT_SYS_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:4888

load:0x40058000,len:0

load:0x1f75a000,len:536808896

ets Jul 29 2019 12:21:46

rst:0x7 (TG0WDT_SYS_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:4888

load:0x40050000,len:0

load:0x3f352000,len:536806860

1150 mmu set 00010000, pos 00010000

1150 mmu set 00020000, pos 00020000

1150 mmu set 00030000, pos 00030000

1150 mmu set 00040000, pos 00040000

1150 mmu set 00050000, pos 00050000

1150 mmu set 00060000, pos 00060000
1150 mmu set 00070000, pos 00070000

1150 mmu set 00080000, pos 00080000

1150 mmu set 00090000, pos 00090000

1150 mmu set 000a0000, pos 000a0000

1150 mmu set 000b0000, pos 000b0000

ets Jul 29 2019 12:21:46

rst:0x7 (TG0WDT_SYS_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:4888

load:0x40010000,len:0

load:0x3f352000,len:268370380

1150 mmu set 00010000, pos 00010000

1150 mmu set 00020000, pos 00020000

1150 mmu set 00030000, pos 00030000

1150 mmu set 00040000, pos 00040000

1150 mmu set 00050000, pos 00050000

1150 mmu set 00060000, pos 00060000

1150 mmu set 00070000, pos 00070000

1150 mmu set 00080000, pos 00080000

1150 mmu set 00090000, pos 00090000

1150 mmu set 000a0000, pos 000a0000

1150 mmu set 000b0000, pos 000b0000

ets Jul 29 2019 12:21:46

rst:0x7 (TG0WDT_SYS_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:4888

load:0x40030000,len:16516

load:0x40000400,len:0

ho 12 tail 0 room 4

load:0x00008104,len:1028

ets Jul 29 2019 12:21:46

btw it's not really a cycle but it keeps giving me this kind of messages it doesn't stop

yes I ve tried both the ESP32 Dev Module and the ESP32 WROVER Module !!

I ve got 2 and I ve tried them both it's the same ! I don't know if they both damaged? (I ve just got them and it's the first use)

You have to play with Arduino IDE->Tools->Flash mode

Also, you have to select Arduino IDE->Tools->Partition scheme->Default 4MB With SPIFFS: this will fix you bad partition table.

As I said before - it is defenitely problems with FLASH: either hardware or, most likely, wrong setup.

Try to use DIO mode for flash. Try to lower frequency for the flash. Set default partichion scheme (a must now)

I did like you said here is the setup but it seems like nothing have changed!

but the message error has changed here is what I have now

ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

ets Jul 29 2019 12:21:46

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

ets Jul 29 2019 12:21:46

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

invalid header: 0x00000000

ets Jul 29 2019 12:21:46

wait it s weird I did reupload it again and it actaully works

1 Like

Thank you so much, It works now!

Please always enclose code and outputs inside a "<CODE/>" block. It makes the text more readable and copyable, and the post shorter. And because it's required by forum policies.

Please edit your post #8 above (don't add another one!) using the pencil button :pencil2:, select the output and click the <CODE/> toolbar button, and save. Thanks.

1 Like

Yes, you changed the Tools menu back to what it should be. Unless you are 10000% sure you know what you are doing, it is best NOT to mess with that, no matter what you read on the internet. Many people plant false posts to mess you up; they are sick.

1 Like