You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
I have searched the issue tracker for a similar issue and not found a similar issue.
General issue report
Hi, I have a WIP prototype on a ESP32-PICO-D4, that uses touch wake from deep sleep.
It has 4 pins/pads (touch buttons), and it wakes from deep sleep under any touch on them.
Then, I simply use touch_ll_read_trigger_status_mask() to detect the firing one and perform the 4 different actions.
Due to lack of GPIOs that i needed to extend my design, I decided that ESP32-S3 was the only valid option, since it is the only new generation chip with Touch pad support, as well as more GPIOs.
However, I am unable to make this wakeup form deep sleep feature work on the 4 pads, only 1 pad/pin wakes the chip, the last one configured. The rest don´t wake up the chip from deep sleep. Calling the read trigger_status_mask() gives always 0, when this wakeup occurs.
I read here: https://esp32.com/viewtopic.php?t=41970
That there is a way to make it work, however I failed making it work.
I tried this with no sucess: esp_sleep_pd_config(ESP_PD_DOMAIN_RTC_PERIPH, ESP_PD_OPTION_ON);
This is for me quite a trap, since the 14 touch pads are totally useless for me, if I can´t use them in deep sleep.
My ESP is all the time in deep sleep, until a user input occurs (on any pin!).
Any help to fix it using more power in deep sleep is welcomed, as well as alternatives (I can change to another chip still, since i am prototyping)
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
ESP32-S3 DeepSleep Touch Wakeup from any pin
ESP32-S3 DeepSleep Touch Wakeup from any pin (IDFGH-14712)
Feb 23, 2025
Hi @DarkZeros ! Seems you are still using the legacy touch driver, FYI, the new touch driver is ready on the master branch, please take a try! (see the programming guide)
About the issue you met, it actually a limitation of the legacy driver.
As you know the touch hardwares are different on ESP32 and S3, and the S3 Touch has more features, 'only can wake-up by one touch pad' is one of these features, it allows the touch power domain (i.e, RTC_PERIPH power domain) shutdown during the deep sleep, which can help to save more power consumption. However, this feature is enabled by default, and not likely to disable by a public API.
Answers checklist.
General issue report
Hi, I have a WIP prototype on a ESP32-PICO-D4, that uses touch wake from deep sleep.
It has 4 pins/pads (touch buttons), and it wakes from deep sleep under any touch on them.
Then, I simply use
touch_ll_read_trigger_status_mask()
to detect the firing one and perform the 4 different actions.Due to lack of GPIOs that i needed to extend my design, I decided that ESP32-S3 was the only valid option, since it is the only new generation chip with Touch pad support, as well as more GPIOs.
However, I am unable to make this wakeup form deep sleep feature work on the 4 pads, only 1 pad/pin wakes the chip, the last one configured. The rest don´t wake up the chip from deep sleep. Calling the read trigger_status_mask() gives always 0, when this wakeup occurs.
I read here: https://esp32.com/viewtopic.php?t=41970
That there is a way to make it work, however I failed making it work.
I tried this with no sucess:
esp_sleep_pd_config(ESP_PD_DOMAIN_RTC_PERIPH, ESP_PD_OPTION_ON);
This is for me quite a trap, since the 14 touch pads are totally useless for me, if I can´t use them in deep sleep.
My ESP is all the time in deep sleep, until a user input occurs (on any pin!).
Any help to fix it using more power in deep sleep is welcomed, as well as alternatives (I can change to another chip still, since i am prototyping)
The text was updated successfully, but these errors were encountered: