Hello,
I've encountered an issue with the light/deep sleep API (IDF v5.1.3) when utilizing external 1 as the wake-up source.
Upon configuring ext1 for sleep wake-up, I noticed an immediate awakening.
This occurred while employing the sleep example on the ESP32-S3 DevKit, specifically on version v5.1.2, where it functioned excellently.
I (0) cpu_start: App cpu up.
I (154) cpu_start: Pro cpu start user code
I (154) cpu_start: cpu freq: 80000000 Hz
I (154) cpu_start: Application information:
I (157) cpu_start: Project name: deep_sleep
I (162) cpu_start: App version: 1
I (166) cpu_start: Compile time: Mar 11 2024 10:45:26
I (172) cpu_start: ELF file SHA256: 2dfafc1cd0a6874f...
I (178) cpu_start: ESP-IDF: v5.1.3-dirty
I (184) cpu_start: Min chip rev: v0.0
I (189) cpu_start: Max chip rev: v0.99
I (193) cpu_start: Chip rev: v0.1
I (198) heap_init: Initializing. RAM available for dynamic allocation:
I (205) heap_init: At 3FC95AD0 len 00053C40 (335 KiB): DRAM
I (212) heap_init: At 3FCE9710 len 00005724 (21 KiB): STACK/DRAM
I (218) heap_init: At 3FCF0000 len 00008000 (32 KiB): DRAM
I (224) heap_init: At 600FE070 len 00001F68 (7 KiB): RTCRAM
I (232) spi_flash: detected chip: generic
I (235) spi_flash: flash io: dio
W (239) spi_flash: Detected size(8192k) larger than the size in the binary image header(2048k). Using the size in the binary image header.
I (253) sleep: Configure to isolate all GPIO pins in sleep state
I (260) sleep: Enable automatic switching of GPIO sleep configuration
I (267) app_start: Starting scheduler on CPU0
I (271) app_start: Starting scheduler on CPU1
I (271) main_task: Started on CPU0
I (281) main_task: Calling app_main()
Enabling timer wakeup, 20s
Enabling EXT0 wakeup on pin GPIO3
Enabling EXT1 wakeup on pins GPIO5, GPIO4
Wake up from GPIO 4
I (291) main_task: Returned from app_main()
deep / light sleep wake ups immediately idf v5.1.3
Who is online
Users browsing this forum: No registered users and 124 guests