
用电池喂 ESP32 的项目,最后死掉的原因十有八九不是代码写错,而是它太清醒了。CPU 加 Wi-Fi 全时运转,再大的电池也扛不了几天。深度睡眠(Deep Sleep)就是给这个毛病准备的药方——把芯片大部分电路断电,只留一点点"闹钟"电路,等需要的时候再叫醒它。
这篇照着 Random Nerd Tutorials 那篇经典教程理了一遍,把四种唤醒源(定时器、触摸、ext0、ext1)的示例代码和踩坑点拆开讲,代码全部原样搬运,新手照着敲就能跑。
一、深度睡眠睡的是什么,什么还醒着
进入深度睡眠后,CPU、大部分 RAM、所有由 APB 时钟驱动的数字外设全部断电。还活着的只有三样:RTC 控制器、RTC 外设和 RTC 内存。另外 ULP 协处理器也可以保持供电,能干点"偷偷量一下传感器"这种低功耗活。
Espressif datasheet 里给五种电源模式做了对比,也专门有一张表列出各模式的电流。下图就是 datasheet 里的功耗对比表,做电池方案前建议先看一眼。

这里给新手标一个坎:你拿万用表量开发板整板,量出来的电流跟 datasheet 表里的数字对不上是正常的。板载的 USB 转串口芯片、电源 LED 都在偷电,Datasheet 说的微安级指的是芯片本身,想真测到那个量级,得把外围电路摘干净。
二、定时器唤醒:最省事的一种
定时器唤醒是四种里最简单的——睡够时间自己醒,不需要接任何外部电路。核心就两行定义,睡眠时长以微秒为单位换算:
#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_DATA_ATTR 声明变量。存进 RTC 内存的变量,深度睡眠期间不会丢:
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));然后配置定时器并入睡,esp_deep_sleep_start() 一执行,芯片立刻断电睡过去:
esp_sleep_enable_timer_wakeup(TIME_TO_SLEEP * uS_TO_S_FACTOR);
esp_deep_sleep_start()这里有个所有人都会踩的坑:esp_deep_sleep_start() 之后的任何代码永远不会执行。芯片在那行直接"断片",醒来后从 setup() 第一行重新跑,所以 loop() 在深度睡眠程序里基本是摆设。
三、外部唤醒 ext0 与 ext1:用按键叫醒它
定时器唤醒是"到点就醒",外部唤醒是"有事才醒",电池项目里往往更实用。要注意的是:不是随便哪个 GPIO 都能当唤醒源,只有 RTC IO 可以,具体是 0、2、4、12-15、25-27、32-39 这批引脚。
ext0 用单个引脚加单个电平触发,走 RTC_IO;ext1 用位掩码配置多个引脚,走 RTC 控制器,不需要 RTC 外设保持供电。教程用的硬件很简单:一个按键接到 GPIO 33,用 10K 电阻下拉到地,按下拉高即触发。

完整示例代码原样搬过来,通过 USE_EXT0_WAKEUP 这个宏切换 ext0 和 ext1 两种模式:
/*
Deep Sleep with External Wake Up
=====================================
This code displays how to use deep sleep with
an external trigger as a wake up source and how
to store data in RTC memory to use it over reboots
This code is under Public Domain License.
Hardware Connections
======================
Push Button to GPIO 33 pulled down with a 10K Ohm
resistor
NOTE:
======
Only RTC IO can be used as a source for external wake
source. They are pins: 0,2,4,12-15,25-27,32-39.
Author:
Pranav Cherukupalli <[email protected]>
*/
#include "driver/rtc_io.h"
#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
RTC_DATA_ATTR int bootCount = 0;
/*
Method to print the reason by which ESP32
has been awaken from sleep
*/
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;
}
}
void setup() {
Serial.begin(115200);
delay(1000); //Take some time to open up the Serial Monitor
//Increment boot number and print it every reboot
++bootCount;
Serial.println("Boot number: " + String(bootCount));
//Print the wakeup reason for ESP32
print_wakeup_reason();
/*
First we configure the wake up source
We set our ESP32 to wake up for an external trigger.
There are two types for ESP32, ext0 and ext1 .
ext0 uses RTC_IO to wakeup thus requires RTC peripherals
to be on while ext1 uses RTC Controller so does not need
peripherals to be powered on.
Note that using internal pullups/pulldowns also requires
RTC peripherals to be turned on.
*/
#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
//Go to sleep now
Serial.println("Going to sleep now");
esp_deep_sleep_start();
Serial.println("This will never be printed");
}
void loop() {
//This is not going to be called
}烧录后打开串口监视器,按一下按键就能看到唤醒原因被打印出来;把位掩码扩展成两个引脚,还能区分"是哪个 GPIO 把我叫醒的":

四、触摸唤醒:手一碰就醒
ESP32 自带触摸传感器,不用接任何东西,摸一下裸露的引脚就能唤醒,适合做"拍一下桌子灯就亮"这种交互。唤醒阈值按芯片型号区分,老王标第二个坎:ESP32 和 ESP32-S2/S3 的灵敏度逻辑是反的,ESP32 阈值越大越灵敏,S2/S3 阈值越小越灵敏,照抄别人代码报错多半栽在这:
#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使能触摸唤醒只需 touchSleepWakeUpEnable 两行,示例里用的是 T3 和 T7(对应 GPIO15 和 GPIO27):
#if CONFIG_IDF_TARGET_ESP32
// Setup sleep wakeup on Touch Pad 3 + 7 (GPIO15 + GPIO 27)
touchSleepWakeUpEnable(T3, THRESHOLD);
touchSleepWakeUpEnable(T7, THRESHOLD);再标一个坎:ESP32 可以同时开多个触摸 pad 当唤醒源,但 ESP32-S2 和 ESP32-S3 只支持 1 个。用新芯片的改的时候别贪多。
四种唤醒源怎么选
| 唤醒源 | 触发方式 | 适合场景 |
|---|---|---|
| 定时器 | 睡满设定时间自动醒 | 定时上报数据、周期巡检 |
| 触摸 | 手碰触摸引脚 | 免按键的人机交互 |
| ext0 | 单个 RTC IO 电平变化 | 单个按键、门磁开关 |
| ext1 | 多个 RTC IO 位掩码组合 | 多按键、需要区分触发源 |
我的建议是从定时器开始跑通流程,RTC_DATA_ATTR 计数器那一套先玩明白,再按项目需求往外部唤醒或触摸唤醒升级。深度睡眠这东西,理解了"睡的是什么、什么还醒着",剩下的就是查着 RTC IO 引脚表接线的事了。











定时器唤醒那一节讲得挺清楚,TIME_TO_SLEEP乘uS_TO_S_FACTOR这个换算我以前一直记不住,其实就是微秒换秒,前面那个ULL后缀容易漏。
触摸唤醒适合做桌面小玩具,摸一下就醒,不用布线。不过S2和S3只能开一个触摸pad这点确实容易翻车,文档里不显眼。
按键接GPIO33加10K下拉那个图很实用,新手照着接就行。ext0和ext1的区别一句话总结:一个引脚用ext0,多个引脚要区分谁触发的用ext1位掩码。
电池项目不睡等于慢性自杀,这篇把四种唤醒源摆一张表挺直观。
这块我踩过坑:以为深度睡眠是代码层面的事,其实关键是RTC内存那点小心思。RTC_DATA_ATTR声明的变量能跨睡眠保留,普通变量醒来就归零,bootCount永远停在1,查了半天才发现原因。另外esp_deep_sleep_start()后面那行永远不会执行,教程里特意写了This will never be printed,第一次看还以为是搞笑注释,后来才明白是真的。