I am using ESP32 WROOM 32U(4MB)
Following are the errors shown on Serial Logs
rst:0x7 (TG0WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0 Ă \n 0,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4656
load:0x40078000,len:13284
ho 0 tail 12 room 4
load:0x40080400,len:3712
entry 0x4008064c
W (34) boot.esp32: PRO CPU has been reset by WDT.
W (34) boot.esp32: WDT reset info: PRO CPU PC=0x401e1a46 (waiti mode)
W (37) boot.esp32: WDT reset info: APP CPU PC=0x401e1a46 (waiti mode)
e-enable cpu cache.
Guru Meditation Error: Core 0 panic'ed (IllegalInstruction). Exception was unhandled.
Memory dump at 0x4009ab24: 072c0000 1900896c a1440040
Core 0 register dump:
PC : 0x4009ab2a PS : 0x00060f30 A0 : 0x8009bee1 A1 : 0x3ffbb310
A2 : 0x3ffbf37c A3 : 0x3ffbb400 A4 : 0x0000b000 A5 : 0x00000020
A6 : 0x3ff42000 A7 : 0x00000004 A8 : 0x0000001b A9 : 0x00000004
A10 : 0xe0000020 A11 : 0x00000000 A12 : 0x3ffbf3c8 A13 : 0xbfffffff
A14 : 0xfffffffd A15 : 0xffffffff SAR : 0x0000001f EXCCAUSE: 0x00000000
EXCVADDR: 0x00000000 LBEG : 0x4014a6e0 LEND : 0x4014a6e5 LCOUNT : 0x00000000
Backtrace:0x4009ab27:0x3ffbb310 0x4009bede:0x3ffbb350 0x4008d11a:0x3ffbb380 0x4013ebe6:0x3ffbb3a0 0x4008d5d9:0x3ffbb3e0 0x4014a6ed:0x3ffbb400 0x4014ab3d:0x3ffbb450 0x40148664:0x3ffbb4c0 0x40149563:0x3ffbb520 0x401495d6:0x3ffbb550 0x40147bcb:0x3ffbb570 0x40147bea:0x3ffbb590 0x400d5ec7:0x3ffbb5b0 0x400d5ef3:0x3ffbb5d0 0x400d4710:0x3ffbb600
ELF file SHA256: d0595d695c66ca30
Rebooting...
ets Jul 29 2019 12:21:46
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:2
load:0x3fff0030,len:4656
load:0x40078000,len:13284
ho 0 tail 12 room 4
load:0x40080400,len:3712
entry 0x4008064c
ets Jul 29 2019 12:21:46
rst:0x10 (RTCWDT_RTC_RESET),boot:0x17 (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:2
load:0x3fff0030,len:4656
load:0x40078000,len:13284
ho 0 tail 12 room 4
load:0x40080400,len:3712
entry 0x4008064c
ESP32 Reboting
Re: ESP32 Reboting
Not sure what your question is, exactly, but I am guessing you aren't happy about your ESP32 rebooting.
Looking at your logs:
rst:0x7 (TG0WDT_SYS_RESET)
This shows you that your first reset was because of the TG0 Timer Watchdog reset.
Google that - maybe check https://esp32.com/viewtopic.php?t=7980
Next one was a reset (rst:0xc (SW_CPU_RESET))
Then a rst:0x10 (RTCWDT_RTC_RESET)
Maybe here: https://esp32.com/viewtopic.php?t=25729
The RST value is a register which stores the reason an ESP32 reboots, and it's shown as above. You can find all the values in the API documentation fpr esp_reset_reason here : https://docs.espressif.com/projects/esp-idf/en/v5.3.1/esp32/api-reference/system/misc_system_api.html?highlight=esp_reset_reason#_CPPv416esp_reset_reasonv
Hope this helps.
Looking at your logs:
rst:0x7 (TG0WDT_SYS_RESET)
This shows you that your first reset was because of the TG0 Timer Watchdog reset.
Google that - maybe check https://esp32.com/viewtopic.php?t=7980
Next one was a reset (rst:0xc (SW_CPU_RESET))
Then a rst:0x10 (RTCWDT_RTC_RESET)
Maybe here: https://esp32.com/viewtopic.php?t=25729
The RST value is a register which stores the reason an ESP32 reboots, and it's shown as above. You can find all the values in the API documentation fpr esp_reset_reason here : https://docs.espressif.com/projects/esp-idf/en/v5.3.1/esp32/api-reference/system/misc_system_api.html?highlight=esp_reset_reason#_CPPv416esp_reset_reasonv
Hope this helps.
Who is online
Users browsing this forum: Bing [Bot], Google [Bot] and 75 guests