esp32 poweron reset

mr.engineer
Posts: 6
Joined: Wed Feb 23, 2022 5:38 am

esp32 poweron reset

Postby mr.engineer » Fri Jun 24, 2022 7:40 pm

Hello,

We have a problem with poweron reset. When ESP32 is connected to our device, it works correctly. However, sometimes poweron reset occurs and esp32 restart again. There is no special case which causes this reset. Sometimes, it occurs after 5 minutes, sometimes it occurs after 5 or 10 hours.
It is important thing for us. Can someone give information about it? What is the reason of reset? Is it related to software or hardware?

ESP_Sprite
Posts: 8921
Joined: Thu Nov 26, 2015 4:08 am

Re: esp32 poweron reset

Postby ESP_Sprite » Fri Jun 24, 2022 11:47 pm

Possibly a power-supply issue, the ESP is known for being a somewhat spikey load when WiFi is enabled. You're sure you have 500mA power budget for the ESP32?

Would be nice if you could post boot logs if you have them, perhaps that can give us a bit more info.

mr.engineer
Posts: 6
Joined: Wed Feb 23, 2022 5:38 am

Re: esp32 poweron reset

Postby mr.engineer » Mon Jun 27, 2022 11:13 am

ESP_Sprite wrote:
Fri Jun 24, 2022 11:47 pm
Possibly a power-supply issue, the ESP is known for being a somewhat spikey load when WiFi is enabled. You're sure you have 500mA power budget for the ESP32?

Would be nice if you could post boot logs if you have them, perhaps that can give us a bit more info.
I share two different logs. This reset does not occur during wifi connection. When reset occurs, wifi is already connected and works correctly.
Thanks for your help
  • [2022-03-03 09:33:06.273] [app] aws ota update periodic check count down = 20357.
    [2022-03-03 09:33:06.283] [app] d_status=15, [DS_Aws_iot_connect_OK], u_status = 0 [US_OK], free heap = 0xb114, user_active = 1
    [2022-03-03 09:33:06.293] [wifi] RSSI of Wifi: -44
    [2022-03-03 09:33:06.293] [app] aws ota update periodic check count down = 20356.
    [2022-03-03 09:33:06.743] [app] d_status=15, [DS_Aws_iot_connect_OK], u_status = 0 [US_OK], free heap = 0xb114, user_active = 1
    [2022-03-03 09:33:07.083] [wifi] RSSI of Wifi: -44
    [2022-03-03 09:33:07.083] [app] aws ota update periodic check count down = 20355.
    [2022-03-03 09:33:07.093] [app] d_status=15, [DS_Aws_iot_connect_OK], u_status = 0 [US_OK], free heap = 0xb114, user_active = 1
    [2022-03-03 09:33:07.213] [wifi] RSSI of Wifi: -44
    [2022-03-03 09:33:07.213] [app] aws ota update periodic check count down = 20354.
    [2022-03-03 09:33:07.433] [app] d_status=15, [DS_Aws_iot_connect_OK], u_status = 0 [US_OK], free heap = 0xb114, user_active = 1
    [2022-03-03 09:33:07.443] [wifi] RSSI of Wifi: -44
    [2022-03-03 09:33:07.633] [app] aws ota update periodic check count down = 20353.
    [2022-03-03 09:33:07.643] [app] d_status=15, [DS_Aws_iot_connect_OK], u_status = 0 [US_OK], free heap = 0xb114, user_active = 1
    [2022-03-03 09:33:07.843] [wifi] RSSI of Wifi: -44
    [2022-03-03 09:33:07.843] [app] aws ota update periodic check count down = 20352.
    [2022-03-03 09:33:07.853] I (66466804) wifi:bcn_timout,ap_probe_send_start
    [2022-03-03 09:33:08.043] ESP-ROM:esp32s2-rc4-20191025
    [2022-03-03 09:33:08.053] Build:Oct 25 2019
    [2022-03-03 09:33:08.053] rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
    [2022-03-03 09:33:08.053] SPIWP:0xee
    [2022-03-03 09:33:08.083] mode:DIO, clock div:1
    [2022-03-03 09:33:08.093] load:0x3ffe6100,len:0x4
    [2022-03-03 09:33:08.093] load:0x3ffe6104,len:0x1b08
    [2022-03-03 09:33:08.323] load:0x4004c000,len:0x1684
    [2022-03-03 09:33:08.333] load:0x40050000,len:0x2288
    [2022-03-03 09:33:08.333] entry 0x4004c320
    [2022-03-03 09:33:08.333] I (46) boot: ESP-IDF HEAD-HASH-NOTFOUND 2nd stage bootloader
    [2022-03-03 09:33:09.333] I (46) boot: compile time 16:00:42
    [2022-03-03 09:33:09.333] I (46) boot: chip revision: 0
    [2022-03-03 09:33:10.093] I (49) boot.esp32s2: SPI Speed : 80MHz
    [2022-03-03 09:33:10.103] I (53) boot.esp32s2: SPI Mode : DIO
    [2022-03-03 09:33:11.383] I (58) boot.esp32s2: SPI Flash Size : 4MB
    [2022-03-03 09:33:11.393] I (63) boot: Enabling RNG early entropy source...
    [2022-03-03 09:33:11.393] I (68) boot: Partition Table:
    [2022-03-03 09:33:13.383] I (72) boot: ## Label Usage Type ST Offset Length

Another log is below:

  • [2022-03-04 08:53:00.501] [iot] Acquiring device lock..
    [2022-03-04 08:53:00.511]
    [2022-03-04 08:53:00.511] [iot] No instant msg to be published! command count=0.
    [2022-03-04 08:53:01.401] [app] d_status=15, [DS_Aws_iot_connect_OK], u_status = 0 [US_OK], free heap = 0xb1d8, user_active = 0
    [2022-03-04 08:53:01.411] [wifi] RSSI of Wifi: -40
    [2022-03-04 08:53:01.411] [app] aws ota update periodic check count down = 18977.
    [2022-03-04 08:53:01.501] [iot] Acquiring device lock..
    [2022-03-04 08:53:01.511]
    [2022-03-04 08:53:01.511] [iot] No instant msg to be published! command count=0.
    [2022-03-04 08:53:02.081] I (67845779) wifi:bcn_timout,ap_probe_send_start
    [2022-03-04 08:53:02.131] ESP-ROM:esp32s2-rc4-20191025
    [2022-03-04 08:53:02.131] Build:Oct 25 2019
    [2022-03-04 08:53:02.131] rst:0x1 (POWERON),boot:0xa (SPI_FAST_FLASH_BOOT)
    [2022-03-04 08:53:02.141] SPIWP:0xee
    [2022-03-04 08:53:02.141] mode:DIO, clock div:1
    [2022-03-04 08:53:02.141] load:0x3ffe6100,len:0x4
    [2022-03-04 08:53:02.141] load:0x3ffe6104,len:0x1b08
    [2022-03-04 08:53:02.141] load:0x4004c000,len:0x1684
    [2022-03-04 08:53:02.151] load:0x40050000,len:0x2288
    [2022-03-04 08:53:02.151] entry 0x4004c320
    [2022-03-04 08:53:02.171] I (46) boot: ESP-IDF HEAD-HASH-NOTFOUND 2nd stage bootloader
    [2022-03-04 08:53:02.181] I (46) boot: compile time 16:00:42
    [2022-03-04 08:53:02.181] I (46) boot: chip revision: 0
    [2022-03-04 08:53:02.191] I (49) boot.esp32s2: SPI Speed : 80MHz
    [2022-03-04 08:53:02.191] I (53) boot.esp32s2: SPI Mode : DIO
    [2022-03-04 08:53:02.201] I (58) boot.esp32s2: SPI Flash Size : 4MB
    [2022-03-04 08:53:02.201] I (63) boot: Enabling RNG early entropy source...
    [2022-03-04 08:53:02.211] I (68) boot: Partition Table:
    [2022-03-04 08:53:02.211] I (72) boot: ## Label Usage Type ST Offset Length
    [2022-03-04 08:53:02.221] I (79) boot: 0 nvs WiFi data 01 02 00010000 00006000
    [2022-03-04 08:53:02.221] I (87) boot: 1 otadata OTA data 01 00 00016000 00002000
    [2022-03-04 08:53:02.231] I (94) boot: 2 phy_init RF data 01 01 00018000 00001000
    [2022-03-04 08:53:02.241] I (101) boot: 3 ota_0 OTA app 00 10 00020000 00177000
    [2022-03-04 08:53:02.251] I (109) boot: 4 ota_1 OTA app 00 11 001a0000 00177000
    [2022-03-04 08:53:02.251] I (117) boot: 5 storage WiFi data 01 02 00317000 00010000
    [2022-03-04 08:53:02.261] I (124) boot: End of partition table
    [2022-03-04 08:53:02.271] I (128) boot: ota rollback check done
    [2022-03-04 08:53:02.271] I (133) esp_image: segment 0: paddr=0x00020020 vaddr=0x3f000020 size=0x366b8 (222904) map
    [2022-03-04 08:53:02.321] I (188) esp_image: segment 1: paddr=0x000566e0 vaddr=0x3ffc1ab0 size=0x03600 ( 13824) load
    [2022-03-04 08:53:02.321] I (192) esp_image: segment 2: paddr=0x00059ce8 vaddr=0x40024000 size=0x00404 ( 1028) load
    [2022-03-04 08:53:02.331] I (195) esp_image: segment 3: paddr=0x0005a0f4 vaddr=0x40024404 size=0x05f24 ( 24356) load
    [2022-03-04 08:53:02.341] I (210) esp_image: segment 4: paddr=0x00060020 vaddr=0x40080020 size=0xbbd30 (769328) map
    [2022-03-04 08:53:02.501] I (373) esp_image: segment 5: paddr=0x0011bd58 vaddr=0x4002a328 size=0x07788 ( 30600) load
    [2022-03-04 08:53:02.521] I (389) boot: Loaded app from partition at offset 0x20000
    [2022-03-04 08:53:02.521] I (390) boot: Disabling RNG early entropy source...
    [2022-03-04 08:53:02.531] I (390) cache: Instruction cache : size 8KB, 4Ways, cache line size 32Byte
    [2022-03-04 08:53:02.541] I (398) cpu_start: Pro cpu up.
    [2022-03-04 08:53:02.541] I (401) cpu_start: Application information:

ESP_Sprite
Posts: 8921
Joined: Thu Nov 26, 2015 4:08 am

Re: esp32 poweron reset

Postby ESP_Sprite » Mon Jun 27, 2022 11:21 am

Smells like a hardware issue, specifically because the reset reason is POWERON. If it were a software issue, that would usually be either a watchdog or a digital reset. Just guessing: Perhaps the reset line of the ESP32 is constructed in such a way that EMC can get into it and reset the chip?

mr.engineer
Posts: 6
Joined: Wed Feb 23, 2022 5:38 am

Re: esp32 poweron reset

Postby mr.engineer » Mon Jun 27, 2022 12:10 pm

Thanks for your reply. We will review hardware

stoumk
Posts: 11
Joined: Tue May 24, 2022 10:54 am

Re: esp32 poweron reset

Postby stoumk » Tue Aug 08, 2023 5:21 pm

What is the solution to the problem? I have the same problem, I don't know what to do.
WiFi/BLE disabled. ESP32E spontaneously calls POWERON_RESET after 5-50 seconds

Who is online

Users browsing this forum: AdsBot [Google] and 63 guests