ESP32深度睡眠实操:定时唤醒与外部触发

2026-11-21 13:28:02 23阅读 所属项目:ESP32 开发板

给 ESP32 项目上电池供电,最头疼的不是代码写不出来,是板子两天就把电池喝干。Wi-Fi 开着、主频拉满的时候,整块芯片的电流是几十毫安量级,充电宝都扛不住几周。深度睡眠(Deep Sleep)就是为这个场景准备的:CPU、Wi-Fi、绝大部分 RAM 和数字外设全部断电,只留 RTC 控制器、RTC 外设和 RTC 内存这一小块电路守夜,等定时器到点或者引脚上有动静,再把整块芯片拉起来。这篇把最常用的两路唤醒——定时唤醒和外部触发——的 API、完整例程代码和串口现象一次理清,代码取自 ESP32 Arduino 库自带的 Deep Sleep 例程(TimerWakeUp 和 ExternalWakeUp 两个 sketch),逐字对照没动过。

ESP32 深度睡眠与唤醒源

深度睡眠省电省在哪:先看功耗量级

ESP32 一共有五种电源模式:Active、Modem-sleep、Light-sleep、Deep-sleep、Hibernation。深睡断得最狠的是主时钟域:凡是挂在 APB_CLK 下的 CPU、大部分 RAM、全部数字外设统统断电,芯片里能继续活着的只有 RTC 控制器、RTC 外设和 RTC 内存这三样,外加可选的 ULP 协处理器。省下来的电有多可观,直接看乐鑫数据手册里的功耗对比表:

ESP32 数据手册五种电源模式功耗对比表

按这张表读数:Light-sleep 是 0.8mA;Deep-sleep 里如果只保留 RTC timer 加 RTC 内存,是 10µA;把 ULP 协处理器开着是 150µA,ULP 传感器监测模式 100µA(1% 占空比);Hibernation 只留 RTC timer,低到 5µA。而 Wi-Fi 工作的 Active 模式是几十毫安起步。拿一块 3000mAh 的 18650 粗算:50mA 常开也就六十来个小时,压到深睡之后光睡眠段就是按年计的量级——差出三四个数量级,电池项目能不能活,基本就看这一步做不做。

深睡期间也不是什么都干不了:RTC 内存保持供电(8KB RTC fast memory),ULP 协处理器还能跑自己那一小段程序去摸传感器。这套组合拳的意思是,你可以让主 CPU 睡死,留一个极其省电的哨兵盯事件,有值得处理的动静再把主核叫起来。定时器唤醒的场景里,保持供电的就是 RTC 控制器、RTC 外设和 RTC 内存。

唤醒之后代码从哪跑:RTC_DATA_ATTR 是关键

新手最容易懵的一个点:调用 esp_deep_sleep_start() 之后,写在它后面的代码永远不执行;唤醒时芯片相当于复位一次,从 setup() 的第一行重新跑起,loop() 根本轮不到。所以所有任务都要写进 setup()、放在 esp_deep_sleep_start() 之前。例程里 esp_deep_sleep_start() 后面那句 Serial.println("This will never be printed") 就是官方留的备忘。

那跨睡眠的数据怎么留?给变量加 RTC_DATA_ATTR 前缀,它就会被放进深睡期间不断电的 RTC 内存。例程里的 bootCount 就是干这个的,每唤醒一次加一,用来数芯片到底醒过几回。注意分寸:RTC 内存的数据跨睡眠保留,但按板子上标 EN 的复位键就清零了——EN 是硬复位,跟深睡唤醒不是一回事。

这次醒来是哪一路叫的,用 esp_sleep_get_wakeup_cause() 查,返回值逐个 switch:ESP_SLEEP_WAKEUP_TIMER 是定时器,EXT0、EXT1 是外部触发的两种形式,TOUCHPAD 是触摸,ULP 是协处理器;default 分支打出来的 Wakeup was not caused by deep sleep,说明这次是上电或者硬复位,不是深睡唤醒。例程把这个判断包成了 print_wakeup_reason(),两份例程里都带着。

定时唤醒:esp_sleep_enable_timer_wakeup

定时唤醒靠 RTC 控制器里内置的 timer,API 只有一个参数——睡眠时长,单位是微秒:

esp_sleep_enable_timer_wakeup(time_in_us)

例程用两个宏把微秒换算成秒来写:uS_TO_S_FACTOR 是 1000000ULL,后缀 ULL 是为了让乘法落在 64 位无符号整型里,微秒数大了不溢出;TIME_TO_SLEEP 改成几就睡几秒。在 Arduino IDE 里走 File > Examples > ESP32 > Deep Sleep,打开 TimerWakeUp 就是下面这份,一字未改:

/* Simple Deep Sleep with Timer Wake Up
   ESP32 offers a deep sleep mode for effective power saving as power is an important factor for IoT applications. In this mode CPUs, most of the RAM, and all the digital peripherals which are clocked
   from APB_CLK are powered off. The only parts of the chip which can still be powered on are: RTC controller, RTC peripherals ,and RTC memories This code displays the most basic deep sleep with a timer to wake it up and how to store data in RTC memory to use it over reboots This code is under Public Domain License.
   Author: Pranav Cherukupalli <[email protected]> */

#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 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 every 5 seconds
  esp_sleep_enable_timer_wakeup(TIME_TO_SLEEP * uS_TO_S_FACTOR);
  Serial.println("Setup ESP32 to sleep for every " + String(TIME_TO_SLEEP) +
  " Seconds");

  /*
  Next we decide what all peripherals to shut down/keep on
  By default, ESP32 will automatically power down the peripherals
  not needed by the wakeup source, but if you want to be a poweruser
  this is for you. Read in detail at the API docs
  http://esp-idf.readthedocs.io/en/latest/api-reference/system/deep_sleep.html
  Left the line commented as an example of how to configure peripherals.
  The line below turns off all RTC peripherals in deep sleep.
  */
  //esp_deep_sleep_pd_config(ESP_PD_DOMAIN_RTC_PERIPH, ESP_PD_OPTION_OFF);
  //Serial.println("Configured all RTC Peripherals to be powered down in sleep");

  // Now that we have setup a wake cause and if needed setup the peripherals state in deep sleep, we can now start going to deep sleep.
  // In the case that no wake up sources were provided but deep sleep was started, it will sleep forever unless hardware reset occurs.
  Serial.println("Going to sleep now");
  delay(1000);
  Serial.flush(); 
  esp_deep_sleep_start();
  Serial.println("This will never be printed");
}

void loop(){
  // This is not going to be called
}

setup() 里的顺序值得看一眼:Serial.begin(115200) 开串口、delay(1000) 等监视器就绪、bootCount 自加并打印、print_wakeup_reason() 报唤醒原因,然后才 esp_sleep_enable_timer_wakeup() 配睡眠时长,最后 Serial.flush() 把串口缓冲吐干净再 esp_deep_sleep_start()。这个 flush 是很多教程不讲的细节:不吐干净缓冲就睡,最后半行日志会丢。

选好板子和 COM 口烧进去,串口监视器开 115200,每 5 秒一轮输出。库例程跑起来之后,串口里长这样:

ESP32 定时唤醒串口监视器输出

红框里是关键三行:Boot number 一路往上加(截图里已经到 109、110),说明 RTC 内存里的计数跨睡眠一直活着;Wakeup caused by timer 点明这次是定时器叫醒的;Setup ESP32 to sleep for every 5 Seconds 说明睡眠配置生效,然后 Going to sleep now 重新睡下。另外注意,中途按 EN 键硬复位的话,bootCount 会从 1 重新数。定时唤醒的典型改法是把打印那几行换成读一次传感器、发一条数据再睡,周期性任务的骨架就搭完了。

外部唤醒:ext0 和 ext1 两条路

外部触发是靠某个引脚上的电平变化把芯片叫醒,比如按钮按下。ext0 和 ext1 两种写法,对应两个 API:

ext0 单引脚:esp_sleep_enable_ext0_wakeup(GPIO_NUM_X, level)。第一个参数是引脚号,必须写成 GPIO_NUM_X 这种形式;第二个参数是触发电平,1 = 高电平唤醒,0 = 低电平唤醒。ext0 走 RTC_IO,深睡期间 RTC 外设要保持供电。

ext1 多引脚:esp_sleep_enable_ext1_wakeup_io(bitmask, mode)。第一个参数是引脚位掩码,第二个是触发逻辑:ESP_EXT1_WAKEUP_ALL_LOW 全部变低才醒,ESP_EXT1_WAKEUP_ANY_HIGH 任意一个变高就醒;S2、S3、C6、H2 这几颗还多一个 ESP_EXT1_WAKEUP_ANY_LOW。ext1 由 RTC 控制器实现,RTC 外设和 RTC 内存都可以断电,比 ext0 更省电。

无论 ext0 还是 ext1,都只能用 RTC GPIO,具体是 0、2、4、12-15、25-27、32-39 这一批,普通数字引脚配不进去,这是外部唤醒最常见的翻车点。原因也好理解:深睡期间主电源域整个断掉,只有 RTC 电源域还活着,唤醒电路必须挂在这个还带电的域上才有人值守。数据手册第 14 页有 RTC GPIO 对照表,查引脚归属最稳。例程的接法是按钮接 GPIO 33,10K 电阻下拉到 GND:

ESP32 外部唤醒按钮接 GPIO 33 电路

例程在 File > Examples > ESP32 > Deep Sleep > ExternalWakeUp 里,USE_EXT0_WAKEUP 置 1 就是 ext0,置 0 就是 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
}

ext0 分支下面那两行 rtc_gpio_pullup_dis() 和 rtc_gpio_pulldown_en() 别看着眼生就删:深睡期间内部上下拉依赖 RTC 外设供电,这里用 RTC IO 层的 API 把 GPIO 33 明确下拉到inactive电平,按钮按下拉高才触发,睡眠期间引脚不会悬空乱触发。ext1 分支如果引脚没有外部上下拉,同样要用 rtc_gpio_pulldown_en() 把待机电平钉死,位掩码用 BUTTON_PIN_BITMASK(GPIO) 这个宏生成,本质上就是 1ULL 左移引脚号;要挂多个触发源,按位或起来就行,比如 GPIO 2 和 GPIO 4 两个引脚各占一位。

烧录后打开串口,按一下按钮,输出是这三行:

ESP32 外部唤醒串口输出

Wakeup caused by external signal using RTC_IO,说明这次唤醒走的是 ext0 这条 RTC_IO 路。ext1 唤醒时串口打的是 using RTC_CNTL,一眼就能区分两条路;如果 ext1 配了多个引脚,再用 esp_sleep_get_ext1_wakeup_status() 反查具体是哪个引脚叫醒的,取对数算出 GPIO 号,进阶例程里有现成写法。

两路唤醒怎么选

选择逻辑不复杂:按固定周期干活的上定时——每小时采一次温湿度、每天定点上报,都是 timer 的主场;等人的事件上外部触发——按钮、门磁、传感器脉冲,ext1 的位掩码还能同时挂好几个触发源。两路也可以组合,esp_sleep_enable_timer_wakeup() 和 esp_sleep_enable_ext0_wakeup() 先后都配上,谁先到先醒谁,醒来再查 wakeup cause 决定干哪件事。另外还有第三条路:触摸引脚唤醒,API 是 touchSleepWakeUpEnable(TOUCH_PIN, THRESHOLD),例程里 ESP32 用 GPIO 15 和 GPIO 27 两个触摸垫,阈值方向分芯片型号,ESP32 是值越小越灵敏、阈值设 40,S2/S3 是反过来且默认 5000,要用的话照库例程 TouchWakeUp 核对,别拿错方向。

固件烧录仔多提醒一句:板子在深睡循环里时串口是间歇性被占的,重新烧录如果撞上睡眠窗口连不上端口,按住 BOOT 键再按 EN 复位,强制进下载模式就能抓到。睡眠时间也别设太短,短到唤醒任务还没跑完又睡回去,串口输出都看不全,排查问题会更费劲。

睡前还有个工程习惯值得提:唤醒周期和任务耗时一起规划,读传感器加发数据如果只要两秒,睡 60 秒就是合理配比;反过来任务比睡眠还长,那深睡省的电就没什么意义了,先优化任务本身。DHT11 这类单总线器件唤醒后要等它稳定再读,别把唤醒瞬间就当成数据就绪的瞬间。

电池项目里,深度睡眠不是可选项,是及格线。10µA 和几十毫安差着三四个数量级,这两份例程加起来不到一百行,值得直接抄进项目里当模板。


作者:固件烧录仔
链接:https://www.aiddithome.com/p/587b64e7dbdd6.html
本作版权归作者所有,未经允许请勿转载。若存在违规行为,您可以点击 “举报”。


登录 后发表评论
4条评论
拆机党
1楼 · 1天前

这个思路其实就是电池项目的分水岭:之前一块 18650 顶着 Wi-Fi 跑,三天就没电,后来把逻辑改成每小时定时唤醒采一次数、发完立刻睡,深睡段 10µA,续航直接从三天变成按月算。几个细节帮大家划下重点:RTC_DATA_ATTR 的变量按 EN 键会清零,想留数据别乱按复位;esp_deep_sleep_start() 前面记得 Serial.flush(),不然串口最后半行日志必丢;外部唤醒只认 0、2、4、12-15、25-27、32-39 这批 RTC GPIO,用普通引脚配半天不触发,八成就是栽在这。

阿强焊点总飞
2楼 · 1天前

GPIO33 要配 rtc_gpio_pulldown_en 那段太真实了,之前直接删了那两行,睡眠期间引脚悬空,半夜乱唤醒好几次。

线比代码多
3楼 · 1天前

唤醒后从 setup 第一行重跑、loop 永远不执行,这个点新人必踩,当初我对着 loop 写了半天逻辑全白搭。

学生党玩机
4楼 · 1天前

数据手册那张功耗表存了,10µA 对几十毫安,差四个数量级,讲得比datasheet原文还直白。