Closed SolidStateLEDLighting closed 7 months ago
Hi, @SolidStateLEDLighting
The hardware of esp32s3 does not support waking up deepsleep through GPIO. The corresponding function can be replaced by ext0/ext1 wake-up source. Please refer to:
Oh... crap. No wonder it didn't make sense to me. Sorry to bother you on this... and I appreciate the guidance.
I just don't know why I didn't get this understanding from the documentation.
Give me a day, I'll close out this ticket.
Confirmed, the correct method for using GPIO (RTC pin) to wake from a deep sleep is to configure that input as an ext0 wakeup.
Answers checklist.
IDF version.
5.2
Operating System used.
Windows
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
What is the expected behavior?
I'm following the IDF example in how to work with Deep Sleep. I am not able to use this function:
esp_deep_sleep_enable_gpio_wakeup(BIT(DEFAULT_WAKEUP_PIN), DEFAULT_WAKEUP_LEVEL)
The include/source files require a definition of SOC_GPIO_SUPPORT_DEEPSLEEP_WAKEUP = 1
Compiler can't find this SOC_GPIO_SUPPORT_DEEPSLEEP_WAKEUP definition for some reason.
I have looked in header files, sdkconfig, Kconfig -- I just don't know where else to look to enable this setting.
Sometimes intellisense can see this setting in esp32p4\include\soc and sometimes it sees it in esp32c2\include\soc -- but this not correct because I'm setup for s3.
The setting and the functions are related to the component esp_hw_support and I have added that to my Requires CMakeLists file and this doesn't help at all. There is a good chance that esp_hw_support is already a component in my project.
What is the actual behavior?
C:/Users//Desktop/ESP_Projects/v.5.2/project-name/main/main_sleep.cpp:24:5: error: 'esp_deep_sleep_enable_gpio_wakeup' was not declared in this scope; did you mean 'esp_sleep_enable_gpio_wakeup'?
Steps to reproduce.
Just try to use the function:
esp_deep_sleep_enable_gpio_wakeup(BIT(DEFAULT_WAKEUP_PIN), DEFAULT_WAKEUP_LEVEL)
Build or installation Logs.
No response
More Information.
No response