做电池供电的项目,ESP32最让人焦虑的不是算力,是功耗。按乐鑫官方数据手册的表10,Wi-Fi发射典型电流能到240mA,接收也有95到100mA;一节2000mAh的18650,满打满算撑不了十几个小时。而同一颗芯片进深度睡眠后,只保留RTC定时器和RTC内存供电时,电流是10微安——差了四个数量级。这篇就把深度睡眠的三种唤醒方式:定时唤醒、触摸唤醒、外部唤醒,逐一跑通。

深度睡眠省的是什么电
先看全景。ESP32有五种电源模式:Active(活跃)、Modem-sleep(调制解调器睡眠)、Light-sleep(轻度睡眠)、Deep-sleep(深度睡眠)、Hibernation(冬眠)。官方数据手册给出的对比是这样的:

几个关键数字值得记一下:活跃模式下CPU全速跑、Wi-Fi/BT收发,是耗电大头;Modem-sleep在240MHz主频下还有30到50mA;Light-sleep降到0.8mA;Deep-sleep如果ULP协处理器开着是150微安,RTC timer加RTC内存供电则是10微安,冬眠模式进一步压到5微安。

深度睡眠的逻辑是"该关的全关":CPU、大部分RAM和所有由APB_CLK时钟驱动的数字外设都断电,只保留RTC控制器、RTC外设和RTC内存这三样。代价是醒过来相当于一次软复位,程序从头跑;好处是一块电池能从几天变成几个月,代价对大多数采集类项目完全划算。睡眠期间RTC_GPIO引脚和触摸引脚仍归RTC域管,这正是触摸和外部唤醒能工作的前提。
定时唤醒:RTC里藏一个闹钟
定时唤醒最简单,RTC控制器自带定时器,到点就把芯片叫醒。Arduino核心里只需要一个函数:
esp_sleep_enable_timer_wakeup(time_in_us)参数单位是微秒。官方示例的写法是先定义两个宏,把秒换算成微秒:
#define uS_TO_S_FACTOR 1000000ULL /* Conversion factor for micro seconds to seconds */
#define TIME_TO_SLEEP 5 /* Time ESP32 will go to sleep (in seconds) */想让变量在睡眠期间不丢,把它放进RTC内存:ESP32的RTC部分有8kB SRAM,深度睡眠不清零,但按EN键复位会清掉。加一个RTC_DATA_ATTR属性就够:
RTC_DATA_ATTR int bootCount = 0;唤醒原因可以用esp_sleep_get_wakeup_cause()查,官方示例的判断函数如下:
void print_wakeup_reason() {
esp_sleep_wakeup_cause_t wakeup_reason;
wakeup_reason = esp_sleep_get_wakeup_cause();
switch (wakeup_reason) {
case ESP_SLEEP_WAKEUP_EXT0: Serial.println("Wakeup caused by external signal using RTC_IO"); break;
case ESP_SLEEP_WAKEUP_EXT1: Serial.println("Wakeup caused by external signal using RTC_CNTL"); break;
case ESP_SLEEP_WAKEUP_TIMER: Serial.println("Wakeup caused by timer"); break;
case ESP_SLEEP_WAKEUP_TOUCHPAD: Serial.println("Wakeup caused by touchpad"); break;
case ESP_SLEEP_WAKEUP_ULP: Serial.println("Wakeup caused by ULP program"); break;
default: Serial.printf("Wakeup was not caused by deep sleep: %d\n", wakeup_reason); break;
}
}setup()里依次做四件事:初始化串口、自增并打印启动次数、查唤醒原因、设定时器、最后睡觉:
Serial.begin(115200);
++bootCount;
Serial.println("Boot number: " + String(bootCount));
//Print the wakeup reason for ESP32
print_wakeup_reason();
esp_sleep_enable_timer_wakeup(TIME_TO_SLEEP * uS_TO_S_FACTOR);
esp_deep_sleep_start();注意esp_deep_sleep_start()之后的代码永远不会执行——芯片已经睡了。烧录后打开串口监视器(波特率115200),每5秒能看到一轮输出:Boot number加一,唤醒原因是timer。

有个细节:如果按板子上的EN键,bootCount会从1重新数,因为那是真复位,RTC内存被清了;深度睡眠唤醒不算复位,所以计数能一直累加。定时唤醒适合定时打点:每小时读一次温湿度、每天发一次数据,中间全在睡觉。
触摸唤醒:一根杜邦线就是触摸键
ESP32自带10个电容触摸引脚,睡眠期间触摸外设留在RTC域里,摸一下就能醒。核心函数:
touchSleepWakeUpEnable(TOUCH_PIN, THRESHOLD);阈值方向要留意:经典ESP32上,触摸时读数变小,THRESHOLD=40表示读数低于40就唤醒,值越大越灵敏;但ESP32-S2和S3正好相反,值越小越灵敏,示例里默认给了5000。官方示例用条件编译兼容两种芯片:
#if CONFIG_IDF_TARGET_ESP32
#define THRESHOLD 40 /* Greater the value, more the sensitivity */
#else //ESP32-S2 and ESP32-S3 + default for other chips (to be adjusted) */
#define THRESHOLD 5000 /* Lower the value, more the sensitivity */
#endif示例把T3(GPIO15)和T7(GPIO27)都设成唤醒源;S2/S3只支持一个触摸引脚做唤醒:
#if CONFIG_IDF_TARGET_ESP32
//Setup sleep wakeup on Touch Pad 3 + 7 (GPIO15 + GPIO 27)
touchSleepWakeUpEnable(T3, THRESHOLD);
touchSleepWakeUpEnable(T7, THRESHOLD);
#else //ESP32-S2 + ESP32-S3
//Setup sleep wakeup on Touch Pad 3 (GPIO3)
touchSleepWakeUpEnable(T3, THRESHOLD);
#endif接线很简单:往GPIO15上插一根杜邦线,线头就是触摸点。

烧录后芯片进睡眠,摸一下那根线,串口监视器会打印启动次数、唤醒原因,还能用esp_sleep_get_touchpad_wakeup_status()查出具体是哪个引脚把你叫醒的。10个触摸引脚的对应关系在代码注释里列得很全:T0对应GPIO4、T1对应GPIO0、T2对应GPIO2、T3对应GPIO15,一直到T9对应GPIO32。

实测手感:金属、潮湿的表面比干燥悬空的线头灵敏得多,阈值40摸裸线头有时要压紧一点才触发。做电池供电的触摸开关(比如床头灯)时,建议先在 awake 状态用touchRead()读一遍裸值,再据此定阈值。
外部唤醒:ext0与ext1怎么选
按钮触发用的是外部唤醒,分两条路:ext0走RTC_IO,要求RTC外设保持供电;ext1走RTC控制器,不需要外设常开。不是所有GPIO都能当唤醒源,只有RTC IO可以:0、2、4、12-15、25-27、32-39这批引脚。单引脚用ext0:
esp_sleep_enable_ext0_wakeup(GPIO_NUM_X, level)level指定唤醒电平,1是高电平触发,0是低电平触发。示例电路是按钮接GPIO33、经10k电阻下拉,按下拉高唤醒:

官方示例用宏切换ext0和ext1两种写法:
#define BUTTON_PIN_BITMASK(GPIO) (1ULL << GPIO) // 2 ^ GPIO_NUMBER in hex
#define USE_EXT0_WAKEUP 1 // 1 = EXT0 wakeup, 0 = EXT1 wakeup
#define WAKEUP_GPIO GPIO_NUM_33 // Only RTC IO are allowed - ESP32 Pin example#if USE_EXT0_WAKEUP
esp_sleep_enable_ext0_wakeup(WAKEUP_GPIO, 1); //1 = High, 0 = Low
// Configure pullup/downs via RTCIO to tie wakeup pins to inactive level during deepsleep.
// EXT0 resides in the same power domain (RTC_PERIPH) as the RTC IO pullup/downs.
// No need to keep that power domain explicitly, unlike EXT1.
rtc_gpio_pullup_dis(WAKEUP_GPIO);
rtc_gpio_pulldown_en(WAKEUP_GPIO);
#else // EXT1 WAKEUP
//If you were to use ext1, you would use it like
esp_sleep_enable_ext1_wakeup_io(BUTTON_PIN_BITMASK(WAKEUP_GPIO), ESP_EXT1_WAKEUP_ANY_HIGH);
/*
If there are no external pull-up/downs, tie wakeup pins to inactive level with internal pull-up/downs via RTC IO
during deepsleep. However, RTC IO relies on the RTC_PERIPH power domain. Keeping this power domain on will
increase some power comsumption. However, if we turn off the RTC_PERIPH domain or if certain chips lack the RTC_PERIPH
domain, we will use the HOLD feature to maintain the pull-up and pull-down on the pins during sleep.
*/
rtc_gpio_pulldown_en(WAKEUP_GPIO); // GPIO33 is tie to GND in order to wake up in HIGH
rtc_gpio_pullup_dis(WAKEUP_GPIO); // Disable PULL_UP in order to allow it to wakeup on HIGH
#endif一个容易踩的坑:睡眠期间引脚必须被拉到非触发电平,否则浮空引脚的抖动会反复把你叫醒。上面代码里的rtc_gpio_pulldown_en()就是干这个的。实测按一下按钮,串口会报Wakeup caused by external signal using RTC_IO:

ext1的真正价值是多引脚:一个掩码塞进多个GPIO,任何一个满足条件都能醒。用ANY_HIGH模式配GPIO2和GPIO15的写法:
#define BUTTON_PIN_BITMASK(GPIO) (1ULL << GPIO) // 2 ^ GPIO_NUMBER in hex
#define WAKEUP_GPIO_2 GPIO_NUM_2 // Only RTC IO are allowed -
#define WAKEUP_GPIO_15 GPIO_NUM_15 // Only RTC IO are allowed
// Define bitmask for multiple GPIOs
uint64_t bitmask = BUTTON_PIN_BITMASK(WAKEUP_GPIO_2) | BUTTON_PIN_BITMASK(WAKEUP_GPIO_15);esp_sleep_enable_ext1_wakeup_io(bitmask, ESP_EXT1_WAKEUP_ANY_HIGH);醒了之后想知道是哪个引脚触发的,用esp_sleep_get_ext1_wakeup_status()拿掩码再取对数:
void print_GPIO_wake_up(){
int GPIO_reason = esp_sleep_get_ext1_wakeup_status();
Serial.print("GPIO that triggered the wake up: GPIO ");
Serial.println((log(GPIO_reason))/log(2), 0);
}功耗数据角度的几点提醒
数据媛的总结习惯是把账算清楚。第一,10微安是"RTC timer+RTC内存"这条最省配置的值;如果你用ext0并保持RTC外设供电,睡眠电流会高一些,ext1配合HOLD特性可以把这块开销压回来。第二,ULP协处理器开着做传感器监测(1%占空比)是100微安档,适合"睡中采样"的场景,但要按ULP的玩法另写程序。第三,唤醒后Wi-Fi连接那几秒才是电池账单里的大头:100到240mA的活跃电流乘上每次联网的时长,比睡眠一小时的耗电多得多,所以定时上报的间隔设计比睡眠参数本身更影响续航。第四,触摸阈值和按钮电平都建议在 awake 状态先读原始值再定,别照抄示例的40和10k电阻。
一句话收口:能定时就定时唤醒,要人交互就用触摸或按钮,多路触发上ext1,剩下的交给RTC内存记住上下文——这四招配齐,一块18650带一块ESP32跑几个月是常规操作。











刚好在做太阳能土壤湿度计,这篇把功耗账算清楚了:Wi-Fi发射典型240mA,深度睡眠只留RTC定时器和RTC内存时10微安。之前一直纠结睡眠参数,其实每次唤醒后连Wi-Fi那几秒才是耗电大头,把上报间隔从10分钟改到1小时,同样的18650估摸能多扛两三个月。
ext1多引脚掩码那段实用,按下不用的按钮分别唤醒做不同动作,靠log取对数还原引脚号有点野但确实好用。
触摸唤醒试过,干燥天气摸裸线头要按很紧才触发,文章建议先touchRead读原始值再定阈值是对的。
bootCount被EN键清零这个细节好,之前还以为代码写错了。