![]() ![]() In revisions 0 and 1 of ESP32, this wakeup source is incompatible with ULP and touch wakeup sources.Įsp_sleep_enable_ext0_wakeup() function can be used to enable this wakeup source.Īfter waking up from sleep, IO pad(s) used for wakeup will be configured as RTC IO. They need to be configured by the application using rtc_gpio_pullup_en() and rtc_gpio_pulldown_en() functions before calling esp_deep_sleep_start(). The RTC IO module is enabled in this mode, so internal pullup or pulldown resistors can also be used. RTC IO is part of the RTC peripherals power domain, so RTC peripherals will be kept powered on during Deep-sleep if this wakeup source is requested. The RTC IO module contains the logic to trigger wakeup when one of RTC GPIOs is set to a predefined logic level. Revisions 0 and 1 of ESP32 only support this wakeup mode when RTC peripherals are not forced to be powered on (i.e., ESP_PD_DOMAIN_RTC_PERIPH should be set to ESP_PD_OPTION_AUTO).Įsp_sleep_enable_touchpad_wakeup() function can be used to enable this wakeup source. To wakeup from a touch sensor interrupt, users need to configure the touch pad interrupt before the chip enters Deep-sleep or Light-sleep modes. The RTC IO module contains the logic to trigger wakeup when a touch sensor interrupt occurs. RTC peripherals or RTC memories don’t need to be powered on during sleep in this wakeup mode.Įsp_sleep_enable_timer_wakeup() function can be used to enable sleep wakeup using a timer. Time is specified at microsecond precision, but the actual resolution depends on the clock source selected for RTC SLOW_CLK.įor details on RTC clock options, see ESP32 Technical Reference Manual > ULP Coprocessor. The RTC controller has a built-in timer which can be used to wake up the chip after a predefined amount of time. Wi-Fi and Bluetooth connections will not be maintained in Deep-sleep or Light-sleep mode, even if these functions are not called. Before entering Deep-sleep or Light-sleep modes, the application must disable Wi-Fi and Bluetooth using the appropriate calls (i.e., esp_bluedroid_disable(), esp_bt_controller_disable(), esp_wifi_stop()). In Deep-sleep and Light-sleep modes, the wireless peripherals are powered down. This will allow the system to wake up from sleep automatically when required by the Wi-Fi driver, thereby maintaining a connection to the AP. If Wi-Fi connections need to be maintained, enable Wi-Fi Modem-sleep mode and automatic Light-sleep feature (see Power Management APIs). At this point, the hardware will be configured according to the requested wakeup sources, and the RTC controller will either power down or power off the CPUs and digital peripherals. ![]() ![]() Once wakeup sources are configured, the application can enter sleep mode using esp_light_sleep_start() or esp_deep_sleep_start() APIs. Wakeup sources can be configured at any moment before entering Light-sleep or Deep-sleep mode.Īdditionally, the application can force specific powerdown modes for RTC peripherals and RTC memories using esp_sleep_pd_config() API. Next section describes these APIs in detail. Wakeup sources can be enabled using esp_sleep_enable_X_wakeup APIs and can be disabled using esp_sleep_disable_wakeup_source() API. These sources can also be combined so that the chip will wake up when any of the sources are triggered. There are several wakeup sources in Deep-sleep and Light-sleep modes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |