The wakeup time from Deep-sleep mode is much longer, compared to Light-sleep and Modem-sleep modes as ROM and RAM are both powered down in this case, and the CPU needs more time for SPI booting. However, {IDF_TARGET_NAME} supports running a “deep sleep wake stub” when coming out of deep sleep. This function runs immediately as soon as the chip wakes up - before any normal initialization, bootloader, or ESP-IDF code has run.
Specifically, after waking up from Deep-sleep mode, {IDF_TARGET_NAME} starts partial initialization. Then RTC fast memory will be validated with CRC. If validation passes, the wake stub code will be executed.
As {IDF_TARGET_NAME} has just woken up from deep sleep, most of the peripherals are in the reset state. The SPI flash has not been mapped. Thus, wake stub code can only call functions implemented in ROM or loaded into RTC fast memory, which retains content during deep sleep.
From the above, utilizing the wake stub functionality in an application you can quickly run some code when waking up from Deep-sleep mode, without having to wait for the whole boot-up process. However, the stub size is restricted by the size of RTC fast memory.
SOC_RTC_SLOW_MEM_SUPPORTED
{IDF_TARGET_NAME} supports RTC memory, including both RTC fast memory and RTC slow memory. The wake stub code should be loaded into RTC fast memory, with data utilized by the code being stored in RTC fast or RTC slow memory.
not SOC_RTC_SLOW_MEM_SUPPORTED
{IDF_TARGET_NAME} only supports RTC fast memory. The wake stub code and data that it utilizes should be loaded into RTC fast memory.
Next we will introduce how to implement the wake stub code in an application.
The wake stub in esp-idf is realized by the function :cppesp_wake_deep_sleep(). This function is executed whenever the SoC wakes from deep sleep. As this function is weakly-linked to the default function :cppesp_default_wake_deep_sleep(), if your application contains a function with the name esp_wake_deep_sleep(), the default version :cppesp_default_wake_deep_sleep() in esp-idf will be overridden.
Please note that implementing the function :cppesp_wake_deep_sleep() in your application is not mandatory for utilizing the deep sleep functionality. It becomes necessary only if you want to introduce certain behavior immediately upon the SoC's wake-up.
When you develop a customized wake stub, the first step it should do is to call the default function :cppesp_default_wake_deep_sleep().
In addition, you can switch between different wake stubs by calling the function :cppesp_set_deep_sleep_wake_stub() during runtime.
Implementing the wake stub function in your application includes the following steps:
- Loading wake stub code into RTC fast memory :SOC_RTC_SLOW_MEM_SUPPORTED: - Loading data into RTC memory :not SOC_RTC_SLOW_MEM_SUPPORTED: - Loading data into RTC fast memory
The wake stub code can only call functions present in ROM or loaded into RTC fast memory. All other RAM locations are unintiailized and contain random data. While the wake stub code can use other RAM areas for temporary storage, the contents of these areas will be overwritten either upon returning to deep sleep mode or upon initiating esp-idf.
Wake stub code is a part of the main esp-idf application. During regular execution of esp-idf, functions can call the wake stub code or access RTC memory, treating them as a regular part of the application.
Wake stub code must reside in RTC fast memory. This can be realized in two ways.
- Employ the attribute
RTC_IRAM_ATTRto place :cppesp_wake_deep_sleep()into RTC fast memory:
void RTC_IRAM_ATTR esp_wake_deep_sleep(void) {
esp_default_wake_deep_sleep();
// Add additional functionality here
}The first approach is suitable for short and simple code segments or for source files including both "normal" and "RTC" code.
- Place the function :cpp
esp_wake_deep_sleep()into any source file with name starting withrtc_wake_stub. For files with such namesrtc_wake_stub*, their contents can be automatically put into RTC fast memory by the linker.
The second method is preferable when writing longer code segments in RTC fast memory.
SOC_RTC_SLOW_MEM_SUPPORTED
RTC memory must include read-only data used by the wake stub code. Data in RTC memory is initialized whenever the SoC restarts, except when waking from deep sleep. In such cases, the data retained before entering to deep sleep are kept. Data used by the wake stub code must be resident in RTC memory, i.e. RTC fast memory or in RTC slow memory.
The data can be specified in the following two methods:
- Utilize attributes
RTC_DATA_ATTRandRTC_RODATA_ATTRto specify writable or read-only data, respectively.
RTC_DATA_ATTR int wake_count;
void RTC_IRAM_ATTR esp_wake_deep_sleep(void) {
esp_default_wake_deep_sleep();
static RTC_RODATA_ATTR const char fmt_str[] = "Wake count %d\n";
esp_rom_printf(fmt_str, wake_count++);
}The RTC memory area where the data will be placed can be configured via the menuconfig option CONFIG_{IDF_TARGET_CFG_PREFIX}_RTCDATA_IN_FAST_MEM. This option allows keeping slow memory area for ULP programs. Once it is enabled, the data marked with RTC_DATA_ATTR and RTC_RODATA_ATTR are placed in the RTC fast memory segment; otherwise, it goes to RTC slow memory (the default option). This option depends on the CONFIG_FREERTOS_UNICORE option because RTC fast memory can be accessed only by PRO_CPU.
esp32
This option depends on the CONFIG_FREERTOS_UNICORE because RTC fast memory can be accessed only by PRO_CPU.
The attributes RTC_FAST_ATTR and RTC_SLOW_ATTR can be used to specify data that is forcefully placed into RTC fast memory and RTC slow memory, respectively. Any access to data marked with RTC_FAST_ATTR is allowed by PRO_CPU only.
esp32s2 or esp32s3
The attributes RTC_FAST_ATTR and RTC_SLOW_ATTR can be used to specify data that is forcefully placed into RTC fast memory and RTC slow memory, respectively.
not SOC_RTC_SLOW_MEM_SUPPORTED
Data used by wake stub code must be resident in RTC fast memory.
The data can be specified in the following two methods:
- Use the
RTC_DATA_ATTRandRTC_RODATA_ATTRto specify writable or read-only data, respectively.
RTC_DATA_ATTR int wake_count;
void RTC_IRAM_ATTR esp_wake_deep_sleep(void) {
esp_default_wake_deep_sleep();
static RTC_RODATA_ATTR const char fmt_str[] = "Wake count %d\n";
esp_rom_printf(fmt_str, wake_count++);
}The attributes RTC_FAST_ATTR and RTC_SLOW_ATTR can be used to specify data that will be force placed into RTC fast memory and RTC slow memory respectively. However, {IDF_TARGET_NAME} includes RTC fast memory only, so both these two attributes will map to this region.
However, any string constants used in this way must be declared as arrays and marked with RTC_RODATA_ATTR, as shown in the example above.
- Place the data into any source file with name starting with
rtc_wake_stub, as demonstrated in the example source file :example_file:`system/deep_sleep_wake_stub/main/rtc_wake_stub_example.c`.
if (s_count >= s_max_count) {
// Reset s_count
s_count = 0;
// Set the default wake stub.
// There is a default version of this function provided in esp-idf.
esp_default_wake_deep_sleep();
// Return from the wake stub function to continue
// booting the firmware.
return;
}The second approach is advisable when incorporating strings or more complex code segments.
You can enable the Kconfig option CONFIG_BOOTLOADER_SKIP_VALIDATE_IN_DEEP_SLEEP to reduce wake-up time. See more information in Fast boot from Deep Sleep <bootloader>.
All of the above functions are declared in :component_file:`esp_hw_support/include/esp_sleep.h`.
SOC_RTC_FAST_MEM_SUPPORTED
ESP-IDF provides an example to show how to implement the deep sleep wake stub.
system/deep_sleep_wake_stub