[问答]

esp32s3在esp-idf v4.4.1环境下启用ext1进deepsleep会触发上电复位，为什么？

问答对人有帮助，内容完整，我也想知道答案 0 log如下： ESP-ROM:esp32s3-20210327 Build:Mar 27 2021 rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT) SPIWP:0xee mode:DIO, clock div:1 load:0x3fcd0108,len:0x1714 load:0x403b6000,len:0xb7c load:0x403ba000,len:0x3094 entry 0x403b6248 I (24) boot: ESP-IDF v4.4.1-dirty 2nd stage bootloader I (25) boot: compile time 10:52:31 I (25) boot: chip revision: 0 I (27) boot.esp32s3: Boot SPI Speed : 80MHz I (32) boot.esp32s3: SPI Mode : DIO I (36) boot.esp32s3: SPI Flash Size : 2MB I (41) boot: Enabling RNG early entropy source... I (47) boot: Partition Table: I (50) boot: ## Label Usage Type ST Offset Length I (57) boot: 0 nvs WiFi data 01 02 00009000 00006000I (65) boot: 1 phy_init RF data 01 01 0000f000 00001000I (72) boot: 2 factory factory app 00 00 00010000 00100000I (80) boot: End of partition table I (84) esp_image: segment 0: paddr=00010020 vaddr=3c020020 size=07f50h ( 32592) map I (98) esp_image: segment 1: paddr=00017f78 vaddr=3fc91e60 size=02774h ( 10100) load I (103) esp_image: segment 2: paddr=0001a6f4 vaddr=40374000 size=05924h ( 22820) load I (114) esp_image: segment 3: paddr=00020020 vaddr=42000020 size=1778ch ( 96140) map I (135) esp_image: segment 4: paddr=000377b4 vaddr=40379924 size=08530h ( 34096) load I (143) esp_image: segment 5: paddr=0003fcec vaddr=50000000 size=00010h ( 16) load I (143) esp_image: segment 6: paddr=0003fd04 vaddr=600fe000 size=00028h ( 40) load I (155) boot: Loaded app from partition at offset 0x10000 I (155) boot: Disabling RNG early entropy source... I (172) cpu_start: Pro cpu up. I (172) cpu_start: Starting app cpu, entry point is 0x403751e8 0x403751e8: call_start_cpu1 at H:/ESP32/Espressif/frameworks/esp-idf-v4.4.1/esp-idf-v4.4.1/components/esp_system/port/cpu_start.c:160 I (0) cpu_start: App cpu up. I (186) cpu_start: Pro cpu start user code I (186) cpu_start: cpu freq: 160000000 I (186) cpu_start: Application information: I (189) cpu_start: Project name: deep_sleep I (194) cpu_start: App version: 1 I (199) cpu_start: Compile time: Oct 19 2022 10:51:47 I (205) cpu_start: ELF file SHA256: d221e5cbd6a9a6da... I (211) cpu_start: ESP-IDF: v4.4.1-dirty I (216) heap_init: Initializing. RAM available for dynamic allocation: I (223) heap_init: At 3FC94FD8 len 0004B028 (300 KiB): D/IRAM I (230) heap_init: At 3FCE0000 len 0000EE34 (59 KiB): STACK/DRAM I (236) heap_init: At 3FCF0000 len 00008000 (32 KiB): DRAM I (243) heap_init: At 600FE028 len 00001FC8 (7 KiB): RTCRAM I (249) spi_flash: detected chip: generic I (254) spi_flash: flash io: dio W (257) spi_flash: Detected size(8192k) larger than the size in the binary image header(2048k). Using the size in the binary image header. I (271) sleep: Configure to isolate all GPIO pins in sleep state I (278) sleep: Enable automatic switching of GPIO sleep configuration I (285) cpu_start: Starting scheduler on PRO CPU. I (0) cpu_start: Starting scheduler on APP CPU. core 0: 01 core 1: 01 Not a deep sleep reset Enabling EXT1 wakeup on pins GPIO2, GPIO4 Entering deep sleep ESP-ROM:esp32s3-20210327 Build:Mar 27 2021 rst:0x1 (POWERON),boot:0xb (SPI_FAST_FLASH_BOOT) SPIWP:0xee mode:DIO, clock div:1 load:0x3fcd0108,len:0x1714 load:0x403b6000,len:0xb7c load:0x403ba000,len:0x3094 entry 0x403b6248 I (24) boot: ESP-IDF v4.4.1-dirty 2nd stage bootloader I (25) boot: compile time 10:52:31 I (25) boot: chip revision: 0 I (27) boot.esp32s3: Boot SPI Speed : 80MHz I (32) boot.esp32s3: SPI Mode : DIO I (36) boot.esp32s3: SPI Flash Size : 2MB I (41) boot: Enabling RNG early entropy source... I (47) boot: Partition Table: I (50) boot: ## Label Usage Type ST Offset Length I (57) boot: 0 nvs WiFi data 01 02 00009000 00006000I (65) boot: 1 phy_init RF data 01 01 0000f000 00001000I (72) boot: 2 factory factory app 00 00 00010000 00100000I (80) boot: End of partition table I (84) esp_image: segment 0: paddr=00010020 vaddr=3c020020 size=07f50h ( 32592) map I (98) esp_image: segment 1: paddr=00017f78 vaddr=3fc91e60 size=02774h ( 10100) load I (103) esp_image: segment 2: paddr=0001a6f4 vaddr=40374000 size=05924h ( 22820) load I (114) esp_image: segment 3: paddr=00020020 vaddr=42000020 size=1778ch ( 96140) map I (135) esp_image: segment 4: paddr=000377b4 vaddr=40379924 size=08530h ( 34096) load I (143) esp_image: segment 5: paddr=0003fcec vaddr=50000000 size=00010h ( 16) load I (143) esp_image: segment 6: paddr=0003fd04 vaddr=600fe000 size=00028h ( 40) load I (155) boot: Loaded app from partition at offset 0x10000 I (155) boot: Disabling RNG early entropy source... I (172) cpu_start: Pro cpu up. I (172) cpu_start: Starting app cpu, entry point is 0x403751e8 0x403751e8: call_start_cpu1 at H:/ESP32/Espressif/frameworks/esp-idf-v4.4.1/esp-idf-v4.4.1/components/esp_system/port/cpu_start.c:160 I (0) cpu_start: App cpu up. I (186) cpu_start: Pro cpu start user code I (186) cpu_start: cpu freq: 160000000 I (186) cpu_start: Application information: I (189) cpu_start: Project name: deep_sleep I (194) cpu_start: App version: 1 I (199) cpu_start: Compile time: Oct 19 2022 10:51:47 I (205) cpu_start: ELF file SHA256: d221e5cbd6a9a6da... I (211) cpu_start: ESP-IDF: v4.4.1-dirty I (216) heap_init: Initializing. RAM available for dynamic allocation: I (223) heap_init: At 3FC94FD8 len 0004B028 (300 KiB): D/IRAM I (230) heap_init: At 3FCE0000 len 0000EE34 (59 KiB): STACK/DRAM I (236) heap_init: At 3FCF0000 len 00008000 (32 KiB): DRAM I (243) heap_init: At 600FE028 len 00001FC8 (7 KiB): RTCRAM I (249) spi_flash: detected chip: generic I (254) spi_flash: flash io: dio W (257) spi_flash: Detected size(8192k) larger than the size in the binary image header(2048k). Using the size in the binary image header. I (271) sleep: Configure to isolate all GPIO pins in sleep state I (278) sleep: Enable automatic switching of GPIO sleep configuration I (285) cpu_start: Starting scheduler on PRO CPU. I (0) cpu_start: Starting scheduler on APP CPU. core 0: 01 core 1: 01 Not a deep sleep reset Enabling EXT1 wakeup on pins GPIO2, GPIO4 Entering deep sleep 貌似是触发ext1唤醒时会导致这个问题，但不确定。代码如下： #include #include #include #include "sdkconfig.h" #include "freertos/FreeRTOS.h" #include "freertos/task.h" #include "esp_sleep.h" #include "esp_log.h" #include "driver/rtc_io.h" #include "rom/rtc.h" void app_main(void) { printf("core 0: %02xtcore 1: %02xrn", rtc_get_reset_reason(0), rtc_get_reset_reason(1)); switch (esp_sleep_get_wakeup_cause()) { #ifdef CONFIG_EXAMPLE_EXT1_WAKEUP case ESP_SLEEP_WAKEUP_EXT1: { uint64_t wakeup_pin_mask = esp_sleep_get_ext1_wakeup_status(); if (wakeup_pin_mask != 0) { int pin = __builtin_ffsll(wakeup_pin_mask) - 1; printf("Wake up from GPIO %dn", pin); } else { printf("Wake up from GPIOn"); } break; } #endif // CONFIG_EXAMPLE_EXT1_WAKEUP case ESP_SLEEP_WAKEUP_UNDEFINED: default: printf("Not a deep sleep resetn"); } vTaskDelay(1000 / portTICK_PERIOD_MS); #ifdef CONFIG_EXAMPLE_EXT1_WAKEUP const int ext_wakeup_pin_1 = 2; const uint64_t ext_wakeup_pin_1_mask = 1ULL << ext_wakeup_pin_1; const int ext_wakeup_pin_2 = 4; const uint64_t ext_wakeup_pin_2_mask = 1ULL << ext_wakeup_pin_2; printf("Enabling EXT1 wakeup on pins GPIO%d, GPIO%dn", ext_wakeup_pin_1, ext_wakeup_pin_2); esp_sleep_enable_ext1_wakeup(ext_wakeup_pin_1_mask \| ext_wakeup_pin_2_mask, ESP_EXT1_WAKEUP_ANY_HIGH); #endif // CONFIG_EXAMPLE_EXT1_WAKEUP printf("Entering deep sleepn"); esp_deep_sleep_start(); } 目前是esp-idf 4.4.1中会有这样的问题，但esp-idf4.4.2里则可以正常运行，我在github中4.4.2的更新中没看到有关于此的记录，如果有大佬知道还望告知我一下是为什么。 0 本主题由 Harmony技术专家于 2024-6-13 14:55 审核通过
2024-6-13 08:28:18　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × wang21cj 该类别下有 38 个回答。邀请回答 hgimtk 该类别下有 38 个回答。邀请回答新星之火12138 该类别下有 33 个回答。邀请回答 chm5 该类别下有 32 个回答。邀请回答 zyh34997 该类别下有 32 个回答。邀请回答就好国dd 该类别下有 32 个回答。邀请回答 zaichenxi 该类别下有 31 个回答。邀请回答 heks 该类别下有 31 个回答。邀请回答四川赵赵该类别下有 29 个回答。邀请回答 flowerddd 该类别下有 29 个回答。邀请回答 muwersddg 该类别下有 29 个回答。邀请回答 caosurround 该类别下有 28 个回答。邀请回答星星公交站该类别下有 28 个回答。邀请回答 vinww特烦恼该类别下有 28 个回答。邀请回答 lkjflksjfsa 该类别下有 27 个回答。邀请回答 h1654155143.8331 该类别下有 27 个回答。邀请回答 723662364d 该类别下有 27 个回答。邀请回答 overheat 该类别下有 27 个回答。邀请回答 gvjhvbc 该类别下有 27 个回答。邀请回答安德森大该类别下有 27 个回答。邀请回答举报张亮相关推荐 • esp32s3在esp-idf v4.4.1环境下启用ext1进deepsleep会触发上电复位是为什么？ 126 • esp32s3在esp-idf v4.4.1环境下启用ext1进deepsleep会触发上电复位是为什么？ 194 • 使用esp-idf-tools2.12不能搭建esp32s3开发环境的原因？ 312 • ESP32S3 WIFI无法连接和softap下扫描不了的问题如何解决？ 403 • esp32-s3芯片esp-idf-v4.4-dev编译带LVGL工程出错怎么解决？ 462 • esp32-s3芯片esp-idf-v4.4-dev编译带LVGL工程出错怎么解决？ 239 • esp32-s3芯片esp-idf-v4.4-dev编译带LVGL工程出错怎么解决？ 489 • esp32-s3芯片esp-idf-v4.4-dev编译带LVGL工程出错的原因？怎么解决？ 296 • vscode下的ESP-IDF环境安装总不对，为什么？ 165 • esp-homekit-sdk的例程编译失败的原因？怎么解决？ 231 1个回答

答案对人有帮助，有参考价值 0 从您提供的日志信息来看，ESP32-S3在ESP-IDF v4.4.1环境下启用EXT1进入deepsleep时，触发了上电复位。这可能是由于以下几个原因导致的： 1. 电源问题：如果电源不稳定或者电源质量不佳，可能会导致ESP32-S3在进入deepsleep后无法正常唤醒，从而触发上电复位。 2. GPIO配置问题：在进入deepsleep之前，确保所有的GPIO都已正确配置。如果某些GPIO配置不正确，可能会导致ESP32-S3在唤醒时无法正常工作，从而触发上电复位。 3. Wakeup源配置问题：在ESP-IDF中，需要正确配置唤醒源以确保ESP32-S3能够从deepsleep中正确唤醒。如果唤醒源配置不正确，可能会导致ESP32-S3无法正常唤醒，从而触发上电复位。 4. 软件问题：ESP-IDF v4.4.1可能存在一些已知或未知的bug，导致ESP32-S3在进入deepsleep后无法正常唤醒。您可以尝试升级到最新版本的ESP-IDF，看看问题是否得到解决。 5. 硬件问题：如果ESP32-S3硬件存在问题，可能会导致无法正常进入deepsleep或唤醒。您可以尝试更换一块新的ESP32-S3模块，看看问题是否得到解决。建议您首先检查电源和GPIO配置，然后检查唤醒源配置。如果问题仍然存在，您可以尝试升级ESP-IDF或更换硬件。同时，您也可以在ESP-IDF的GitHub仓库中查找相关问题的讨论，看看是否有其他开发者遇到了类似的问题，并找到了解决方案。

2024-6-13 16:42:18 评论举报爱吃果冻