ESP-wroom-32 Continous rebooting

[Intector]

Hallo,

I'm using a ESP-WROOM-32 module and if i program a example code to it, it continously reboots with the following message:

Rebooting...
ets Jun 8 2016 00:22:57

rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3ffc0008,len:0
load:0x3ffc0008,len:1964
load:0x40078000,len:3648
ho 0 tail 12 room 4
load:0x40080000,len:256
entry 0x40080034
[0;32mI (1183) heap_alloc_caps: Initializing. RAM available for dynamic allocation:[0m
[0;32mI (1184) heap_alloc_caps: At 3FFB6094 len 00029F6C (167 KiB): DRAM[0m
[0;32mI (1215) heap_alloc_caps: At 3FFE8000 len 00018000 (96 KiB): D/IRAM[0m
[0;32mI (1279) heap_alloc_caps: At 40095AC4 len 0000A53C (41 KiB): IRAM[0m
[0;32mI (1341) cpu_start: Pro cpu up.[0m
[0;32mI (1376) cpu_start: Starting app cpu, entry point is 0x40080afc[0m
[0;32mI (0) cpu_start: App cpu up.[0m
[0;32mI (1470) cpu_start: Pro cpu start user code[0m
Guru Meditation Error of type IllegalInstruction occurred on core 0. Exception was unhandled.
Register dump:
PC : 0x40107f66 PS : 0x00060930 A0 : 0x80081d25 A1 : 0x3ffe3aa0
A2 : 0x00000100 A3 : 0x000000ff A4 : 0x00000000 A5 : 0x80029d04
A6 : 0x00ff0000 A7 : 0x3ffe3aa0 A8 : 0x800818a3 A9 : 0x3ffe3a60
A10 : 0x00000026 A11 : 0x00000026 A12 : 0x00000028 A13 : 0x80028e00
A14 : 0x00000004 A15 : 0x3ffe3a60 SAR : 0x00000014 EXCCAUSE: 0x00000000
EXCVADDR: 0x00000000 LBEG : 0x4000c46c LEND : 0x4000c477 LCOUNT : 0x00000000

Backtrace: 0x40107f66:0x3ffe3aa0 0x40081d25:0x3ffe3ad0 0x400e9d06:0x3ffe3b50 0x400e9b7b:0x3ffe3b90 0x400e9c88:0x3ffe3bd0 0x400e631d:0x3ffe3c10 0x40080bf8:0x3ffe3c40 0x40080afa:0x3ffe3c80 0x4007838d:0x3ffe3ca0 0x40078506:0x3ffe3cd0 0x400787b5:0x3ffe3d50 0x400800fd:0x3ffe3e70 0x40007c34:0x3ffe3eb0 0x40000740:0x3ffe3f20


I'm using the sample code from the SDK.

[ESP_Sprite]

Are you using a power supply that can feed the ESP32 at least 500mA?

[Intector]

Thank you.
I have to check, at the moment I'm using the power from USB 3 port of computer. It is possible that this is not enough, because i have other components like a OLED display an that same 5V.
I'll try different power supply.

[Intector]

I changed the power supply and it can provide 20A, but the continous rebooting is still happening.

I checked closer into the problem, the module I,m using is the ESP32-DevKitC. for the programming i use the OLIMEX ARM-USB-OCD-H jtag(but even with the standart serial flash tool the problem occurs), I'm running the LED-Blink example from the SDK.

If i start a brand new module(out of the box) i get the following message in the terminal:

ets Jun 8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
Falling back to built-in command interpreter.
OK
>ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3ffc0000,len:0
load:0x3ffc0000,len:2304
load:0x40078000,len:3788
ho 0 tail 12 room 4
load:0x40098000,len:532
entry 0x4009813c
[1;36m

[0m[1;36m**************************************
[0m[1;36m* hello espressif ESP32! *
[0m[1;36m* 2nd boot is running! *
[0m[1;36m* version (V0.1) *
[0m[1;36m**************************************
[0m[0;36mcompile time 18:16:58

[0m[0;36m SPI Speed : 40MHz
[0m[0;36m SPI Mode : DIO
[0m[0;36m SPI Flash Size : 4MB
[0m[1;36mPartition Table:
[0m[1;36m## Label Usage Type ST Offset Length
[0m[1;36m 0 factory factory app 00 00 00010000 00100000
[0m[1;36m 1 rfdata RF data 01 01 00110000 00040000
[0m[1;36m 2 wifidata WiFi data 01 02 00150000 00040000
[0m[1;36mEnd of partition table
[0m[1;36mLoading app partition at offset 00010000
[0m[0;36msection 0: paddr=0x00000020 vaddr=0x00000000 size=0x0ffe8 ( 65512)
[0m[0;36msection 1: paddr=0x00010010 vaddr=0x3f400010 size=0x05b64 ( 23396) map
[0m[0;36msection 2: paddr=0x00015b7c vaddr=0x3ffba720 size=0x01378 ( 4984) load
[0m[0;36msection 3: paddr=0x00016efc vaddr=0x40080000 size=0x00400 ( 1024) load
[0m[0;36msection 4: paddr=0x00017304 vaddr=0x40080400 size=0x126ac ( 75436) load
[0m[0;36msection 5: paddr=0x000299b8 vaddr=0x00000000 size=0x06658 ( 26200)
[0m[0;36msection 6: paddr=0x00030018 vaddr=0x400d0018 size=0x325b4 (206260) map
[0m[0;36mstart: 0x400807ac

[0mInitializing heap allocator:
Region 19: 3FFBBA98 len 00024568 tag 0
Region 25: 3FFE8000 len 00018000 tag 1
Pro cpu up.
Pro cpu start user code
nvs_flash_init
frc2_timer_task_hdl:3ffbc564, prio:22, stack:2048
tcpip_task_hdlxxx : 3ffbeca8, prio:20,stack:2048
phy_version: 80, Aug 26 2016, 13:04:06, 0
pp_task_hdl : 3ffc34f0, prio:23, stack:8192

:>enter uart init
uart init wait fifo succeed
exit uart init

IDF version : master(db93bceb)

WIFI LIB version : master(934d079b)

ssc version : master(r283 4d376412)

!!!ready!!!
mode : softAP(26:0a:c4:03:b2:58)
dhcp server start:(ip: 192.168.4.1, mask: 255.255.255.0, gw: 192.168.4.1)

+WIFI:AP_START


The module don't reboot all the time. The IP is 192.168.4.1, but no web page comes up(i guess no http server is running)

[gado070707]

hello,
I have the same problem. Has anyone found the solution ?

[gado070707]

The problem has been solved.
The ESP32 must be powered with 5V and not with 3.3V

[ESP_Sprite]

Hehe Slight clarification for anyone reading this: Feeding the ESP32 *itself* from 3.3V is perfectly acceptable. However, if you have an ESP32 *development board* which is made to accept 5V (and has an LDO or SMPS to convert that down to the 3.3V the ESP32 needs internally), plugging that board into 3.3V is not going to work.