mirror of
https://github.com/espressif/esp-idf.git
synced 2024-10-05 20:47:46 -04:00
docs: Provide translationfor low power
This commit is contained in:
zhangshuxian
Zhang Shuxian
parent
1c351e5194
commit
002c10d97b
@ -56,7 +56,8 @@ CLASSIC_BT_DOCS = ['api-reference/bluetooth/classic_bt.rst',
|
||||
BLUFI_DOCS = ['api-guides/blufi.rst',
|
||||
'api-reference/bluetooth/esp_blufi.rst']
|
||||
|
||||
WIFI_DOCS = ['api-guides/wifi.rst',
|
||||
WIFI_DOCS = ['api-guides/low-power-mode/low-power-mode-wifi.rst',
|
||||
'api-guides/wifi.rst',
|
||||
'api-guides/wifi-security.rst',
|
||||
'api-guides/wireshark-user-guide.rst',
|
||||
'api-reference/network/esp_now.rst',
|
||||
|
||||
@ -29,6 +29,7 @@ API Guides
|
||||
:CONFIG_IDF_TARGET_ARCH_XTENSA: hlinterrupts
|
||||
jtag-debugging/index
|
||||
linker-script-generation
|
||||
low-power-mode/index
|
||||
lwip
|
||||
memory-types
|
||||
openthread
|
||||
@ -45,5 +46,4 @@ API Guides
|
||||
:SOC_USB_SERIAL_JTAG_SUPPORTED: usb-serial-jtag-console
|
||||
:SOC_WIFI_SUPPORTED: wifi
|
||||
:SOC_WIFI_SUPPORTED: wifi-security
|
||||
low-power-mode
|
||||
:SOC_WIFI_SUPPORTED or SOC_BT_SUPPORTED or SOC_IEEE802154_SUPPORTED: phy
|
||||
|
||||
@ -1,7 +0,0 @@
|
||||
Low Power Mode User Guide
|
||||
==========================
|
||||
|
||||
|
||||
:link_to_translation:`zh_CN:[中文]`
|
||||
|
||||
The document has not been translated into English yet. In the meantime, please refer to the Chinese version.
|
||||
15
docs/en/api-guides/low-power-mode/index.rst
Normal file
15
docs/en/api-guides/low-power-mode/index.rst
Normal file
@ -0,0 +1,15 @@
|
||||
Low Power Modes
|
||||
===================
|
||||
|
||||
:link_to_translation:`zh_CN:[中文]`
|
||||
|
||||
Overview
|
||||
----------
|
||||
|
||||
The standby power consumption plays an important role in embedded IoT application scenarios. This guide aims to introduce the basic principles of low power consumption of the {IDF_TARGET_NAME} and the low power modes supported by the {IDF_TARGET_NAME}. Besides, it also covers recommended configurations, configuration steps, and power consumption performance of each mode to help users quickly configure the appropriate low power mode according to the needs at hand.
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
|
||||
low-power-mode-soc
|
||||
:SOC_WIFI_SUPPORTED: low-power-mode-wifi
|
||||
495
docs/en/api-guides/low-power-mode/low-power-mode-soc.rst
Normal file
495
docs/en/api-guides/low-power-mode/low-power-mode-soc.rst
Normal file
@ -0,0 +1,495 @@
|
||||
Introduction to Low Power Mode for Systemic Power Management
|
||||
==============================================================
|
||||
|
||||
:link_to_translation:`zh_CN:[中文]`
|
||||
|
||||
The {IDF_TARGET_NAME} supports various low power modes. From a systemic perspective on power management, the typical modes include DFS, Light-sleep mode, and Deep-sleep mode. These modes reduce power consumption by lowering clock frequencies (DFS) or entering sleep states without affecting system functionality. During sleep, unnecessary power domains are shut down, or clock gating is applied to peripherals not in use. Sleep modes are further classified into Light-sleep mode and Deep-sleep mode based on whether powering down domains would disrupt program execution context.
|
||||
|
||||
.. only:: SOC_WIFI_SUPPORTED or SOC_BLE_SUPPORTED
|
||||
|
||||
Furthermore, for common use cases of the {IDF_TARGET_NAME} such as Wi-Fi/Bluetooth operation, ESP-IDF segment the modes above and optimize them specifically, which will be introduced in subsequent sections.
|
||||
|
||||
This section will first introduce low power modes from a systemic perspective, without considering specific use cases.
|
||||
|
||||
DFS
|
||||
------
|
||||
|
||||
Dynamic Frequency Scaling (DFS) is a fundamental feature of the power management mechanism integrated into ESP-IDF. DFS adjusts the Advanced Peripheral Bus (APB) frequency and CPU frequency based on the application's holding of power locks. When holding a high-performance lock, it utilizes high frequency, while in idle states without holding power locks, it switches to low frequency to reduce power consumption, thereby minimizing the power consumption of running applications as much as possible.
|
||||
|
||||
The frequency adjustment mechanism of DFS operates based on the maximum frequency demand dictated by held power locks. Additionally, the values of :ref:`CONFIG_FREERTOS_HZ` also influence the frequency adjustments of DFS. Higher values lead to a higher frequency of task scheduling, then the system can also more quickly re-adjust the clock frequencies according to the system requirements. For further details regarding the frequency adjustment mechanism, please refer to :doc:`Power Management <../../api-reference/system/power_management>`.
|
||||
|
||||
The following graph illustrates the ideal current situation during the operation of the DFS mechanism.
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
Hold CPU and APB MAX lock
|
||||
│
|
||||
│ Release CPU MAX lock
|
||||
▲ │ /
|
||||
Current │ ▼ /
|
||||
│ ──────────┐ Release APB MAX lock
|
||||
│ │ /
|
||||
│ │ /
|
||||
│ └─────────┐
|
||||
│ ▲ │
|
||||
│ │ │
|
||||
│ m-th tick │ └───────────
|
||||
│ ▲
|
||||
│ │
|
||||
│ n-th tick │
|
||||
└──────────────────────────────────────►
|
||||
Time
|
||||
Ideal DFS Mechanism Frequency Adjustment Current Graph
|
||||
|
||||
DFS is suitable for scenarios where the CPU must remain active but low power consumption is required. Therefore, DFS is often activated with other low power modes, as will be detailed in the following sections.
|
||||
|
||||
.. _Light-sleep Mode:
|
||||
|
||||
Light-sleep Mode
|
||||
---------------------
|
||||
|
||||
Light-sleep mode is a low power mode preset in the {IDF_TARGET_NAME}. Users can switch to Light-sleep mode by calling :cpp:func:`esp_light_sleep_start` interface. Upon entering sleep, the chip will shut down unnecessary power domains and apply clock gating to modules not in use, based on the current operational states of peripherals. The {IDF_TARGET_NAME} supports various wake-up sources. Please refer to :doc:`Sleep Modes <../../api-reference/system/sleep_modes>` for more information. When the chip wakes up from Light-sleep mode, the CPU continues running from the context it was in before entering sleep, and the operational states of peripherals remain unaffected. To effectively reduce chip power consumption under Light-sleep mode, it is highly recommended that users utilize Auto Light-sleep mode described below.
|
||||
|
||||
Auto Light-sleep mode is a low power mode provided by ESP-IDF :doc:`Power Management <../../api-reference/system/power_management>` component that leverages FreeRTOS's Tickless IDLE feature. When the application releases all power locks and all FreeRTOS tasks are in a blocked or suspended state, the system automatically calculates the next time point when an event will wake the operating system. If this calculated time point exceeds a set duration (:ref:`CONFIG_FREERTOS_IDLE_TIME_BEFORE_SLEEP`), the ``esp_pm`` component automatically configures the timer wake-up source and enters light sleep to reduce power consumption. To enable this mode, users need to set the ``light_sleep_enable`` field to true in :cpp:type:`esp_pm_config_t` when configuring DFS. For more details, please refer to `DFS Configuration`_.
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
┌────────┐
|
||||
│ │
|
||||
│ DFS │
|
||||
│ │
|
||||
└───┬────┘
|
||||
│
|
||||
▼
|
||||
┌──────────┐ when idle ┌──────────┐ exceed set time ┌──────────┐
|
||||
│ │ ─────────────► │ │ ────────────► │ │
|
||||
│ │ │ │ │ auto │
|
||||
│ active │ │ IDLE │ │ light │
|
||||
│ │ │ │ │ sleep │
|
||||
│ │ ◄───────────── │ │ │ │
|
||||
└──────────┘ not idle └──────────┘ └──────┬───┘
|
||||
▲ │
|
||||
│ configure wake-up source │
|
||||
└───────────────────────────────────────────────────────────────┘
|
||||
|
||||
Auto Light-sleep Mode Workflow
|
||||
|
||||
Based on the workflow of Auto Light-sleep mode, its ideal current graph can be obtained, with key nodes marked on the chart.
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
▲ DFS frequency reduced
|
||||
Current | │ exceed set idle time
|
||||
| ▼ / light sleep
|
||||
| ┌──┐ / ┌──┐
|
||||
| │ └──┐ │ └──┐
|
||||
| | | | |
|
||||
| │ │ │ │
|
||||
| ───┘ └────────┘ └────
|
||||
│ \
|
||||
│ wake-up source wakes up
|
||||
└───────────────────────────────►
|
||||
Time
|
||||
Ideal Current Graph of Auto Light-sleep Mode
|
||||
|
||||
.. note::
|
||||
|
||||
- To better illustrate the main changes of Auto Light-sleep mode, the DFS frequency reduction process is omitted from the graph above.
|
||||
|
||||
- Auto Light-sleep mode is suitable for scenarios where real-time response to external demands is not required.
|
||||
|
||||
- Auto Light-sleep mode operates based on timer wake-up sources. Therefore, users should not manually configure timer wake-up sources in their application.
|
||||
|
||||
|
||||
.. _Deep-sleep Mode:
|
||||
|
||||
Deep-sleep Mode
|
||||
-----------------
|
||||
|
||||
Deep-sleep mode is designed to achieve better power performance by retaining only RTC/LP memory and peripherals during sleep, while all other modules are shut down. Similar to Light-sleep mode, Deep-sleep mode is entered through API calls and requires configuration of wake-up sources for awakening. Users can switch to Deep-sleep mode by calling :cpp:func:`esp_deep_sleep_start` interface.
|
||||
|
||||
Deep-sleep mode requires the configuration of wake-up sources. The {IDF_TARGET_NAME} supports multiple wake-up sources. For a complete list of wake-up sources, please refer to :doc:`Sleep Modes <../../api-reference/system/sleep_modes>`. These wake-up sources can also be combined so that any wake-up source can trigger the awakening. If no wake-up source is configured when entering deep sleep, the chip will remain in sleep state until an external reset occurs. Unlike Light-sleep mode, Deep-sleep mode upon awakening will lose the CPU's running context before, so the bootloader needs to be run again to enter the user program.
|
||||
|
||||
The workflow of Deep-sleep mode is shown as below:
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
┌───────┐ call API ┌───────┐
|
||||
│ ├───────────►│ deep │
|
||||
│active │ │ sleep │
|
||||
│ │ │ │
|
||||
└───────┘ └───┬───┘
|
||||
▲ │
|
||||
└────────────────────┘
|
||||
wake-up source wakes up
|
||||
Deep-sleep Mode Workflow
|
||||
|
||||
The primary application scenario of Deep-sleep mode determines that the system will awaken only after a long period and will return to deep sleep state after completing its task. The ideal current graph is as follows.
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
▲
|
||||
Current |
|
||||
| call API
|
||||
| │
|
||||
| ▼
|
||||
| ┌────┐
|
||||
| │ │
|
||||
| wake-up source| |
|
||||
| wakes up \ | |
|
||||
| \ │ │
|
||||
│ ──────────┘ └────────────────
|
||||
│
|
||||
└──────────────────────────────────────────►
|
||||
Time
|
||||
Ideal Current Graph of Deep-sleep Mode
|
||||
|
||||
Deep-sleep mode can be utilized in low power sensor applications or situations where data transmission is not required for most of the time, commonly referred to as standby mode.
|
||||
|
||||
|
||||
.. only:: ESP_ROM_SUPPORT_DEEP_SLEEP_WAKEUP_STUB
|
||||
|
||||
Devices can wake up periodically from deep sleep to measure and upload data, and then return to deep sleep. Alternatively, it can store multiple data sets in RTC memory and transmit them all at once upon the next wake-up. This feature can be implemented using the deep-sleep-stub functionality. For details, please refer to :doc:`Deep-sleep Wake Stubs <../../api-guides/deep-sleep-stub>`.
|
||||
|
||||
Low Power Mode Configuration on Pure System
|
||||
----------------------------------------------
|
||||
|
||||
After introducing low power modes from a systemic perspective, this section will present common configuration options, recommended configuration options for each mode, and configurations steps.
|
||||
|
||||
Common Configuration Options
|
||||
------------------------------------
|
||||
|
||||
.. note::
|
||||
|
||||
The configuration options below are briefly introduced. For more detailed information, please click the link behind each option.
|
||||
|
||||
.. only:: esp32 or esp32s3
|
||||
|
||||
- single/dual core operation mode (:ref:`CONFIG_FREERTOS_UNICORE`)
|
||||
For multi-core chips, the single core operation mode can be selected.
|
||||
|
||||
|
||||
- RTOS Tick rate (Hz) (:ref:`CONFIG_FREERTOS_HZ`)
|
||||
This parameter denotes the frequency of the system's periodic task scheduling.
|
||||
|
||||
|
||||
DFS Configuration
|
||||
------------------------
|
||||
|
||||
DFS offers the following configurable options:
|
||||
|
||||
- ``max_freq_mhz``
|
||||
This parameter denotes the maximum CPU frequency (MHz), i.e., the frequency at which the CPU operates at its highest performance level. It is typically set to the maximum value specified by the chip parameters.
|
||||
|
||||
- ``min_freq_mhz``
|
||||
This parameter denotes the minimum CPU frequency (MHz), i.e., the CPU's operating frequency when the system is in an idle state. This field can be set to the crystal oscillator (XTAL) frequency value or the XTAL frequency value divided by an integer.
|
||||
|
||||
- ``light_sleep_enable``
|
||||
Enabling this option allows the system to automatically enter the light sleep during idle periods, i.e., enabling Auto Light-sleep mode, as detailed earlier.
|
||||
|
||||
Specific configuration steps are as follows:
|
||||
|
||||
1. Enable :ref:`CONFIG_PM_ENABLE`
|
||||
2. Configure ``max_freq_mhz`` and ``min_freq_mhz`` as follows:
|
||||
|
||||
::
|
||||
|
||||
esp_pm_config_t pm_config = {
|
||||
.max_freq_mhz = CONFIG_EXAMPLE_MAX_CPU_FREQ_MHZ,
|
||||
.min_freq_mhz = CONFIG_EXAMPLE_MIN_CPU_FREQ_MHZ,
|
||||
.light_sleep_enable = false
|
||||
};
|
||||
ESP_ERROR_CHECK(esp_pm_configure(&pm_config));
|
||||
|
||||
Recommended Configuration
|
||||
++++++++++++++++++++++++++++
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 40 20
|
||||
|
||||
* - Configuration Name
|
||||
- Configuration Status
|
||||
|
||||
* - Enable power management component (:ref:`CONFIG_PM_ENABLE`)
|
||||
- ON
|
||||
|
||||
* - RTOS Tick rate (Hz) (:ref:`CONFIG_FREERTOS_HZ`)
|
||||
- 1000
|
||||
|
||||
* - ``max_freq_mhz``
|
||||
- 160
|
||||
|
||||
* - ``min_freq_mhz``
|
||||
- 40
|
||||
|
||||
* - ``light_sleep_enable``
|
||||
- false
|
||||
|
||||
.. note::
|
||||
Configurations not mentioned in the above table are set to default.
|
||||
|
||||
|
||||
Light-sleep Mode Configuration
|
||||
---------------------------------
|
||||
|
||||
This section introduces the recommended configuration and configuration steps for Auto Light-sleep mode.
|
||||
|
||||
.. note::
|
||||
|
||||
The configuration options below are briefly introduced. For more detailed information, please click the link behind each option.
|
||||
|
||||
- Minimum IDLE Tick count before entering sleep state (:ref:`CONFIG_FREERTOS_IDLE_TIME_BEFORE_SLEEP`)
|
||||
- Put light sleep related codes in IRAM (:ref:`CONFIG_PM_SLP_IRAM_OPT`)
|
||||
- Put RTOS IDLE related codes in IRAM (:ref:`CONFIG_PM_RTOS_IDLE_OPT`)
|
||||
- RTC slow clock source (:ref:`CONFIG_RTC_CLK_SRC`)
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 40 40 20
|
||||
|
||||
* - Clock Source
|
||||
- Timer Accuracy
|
||||
- Frequency Offset
|
||||
|
||||
* - RTC_CLK_SRC_INT_RC
|
||||
- High
|
||||
- Large
|
||||
|
||||
* - RTC_CLK_SRC_EXT_CRYS
|
||||
- Low
|
||||
- Small
|
||||
|
||||
- Disable all GPIO when chip at sleep (:ref:`CONFIG_PM_SLP_DISABLE_GPIO`)
|
||||
|
||||
.. only:: SOC_PM_SUPPORT_MAC_BB_PD
|
||||
|
||||
- Power down MAC and baseband (:ref:`CONFIG_ESP_PHY_MAC_BB_PD`)
|
||||
|
||||
|
||||
.. only:: SOC_PM_SUPPORT_CPU_PD
|
||||
|
||||
- Power down CPU (:ref:`CONFIG_PM_POWER_DOWN_CPU_IN_LIGHT_SLEEP`)
|
||||
|
||||
|
||||
.. only:: SOC_PM_SUPPORT_TAGMEM_PD
|
||||
|
||||
- Power down I/D-cache tag memory (:ref:`CONFIG_PM_RESTORE_CACHE_TAGMEM_AFTER_LIGHT_SLEEP`)
|
||||
|
||||
|
||||
.. only:: SOC_PM_SUPPORT_VDDSDIO_PD
|
||||
|
||||
- Power down flash in light sleep (:ref:`CONFIG_ESP_SLEEP_POWER_DOWN_FLASH`)
|
||||
|
||||
.. only:: SOC_SPIRAM_SUPPORTED
|
||||
|
||||
Due to the shared power pins between flash and PSRAM, cutting power to PSRAM would result in data loss. Therefore, to ensure light sleep does not disrupt program execution, enabling this option requires that the system does not utilize PSRAM.
|
||||
|
||||
|
||||
Configuration Steps:
|
||||
|
||||
1. Configure wake-up sources (refer to :doc:`Sleep Modes <../../api-reference/system/sleep_modes>` for details)
|
||||
2. Enable :ref:`CONFIG_PM_ENABLE`
|
||||
3. Enable :ref:`CONFIG_FREERTOS_USE_TICKLESS_IDLE`
|
||||
4. Configure DFS parameters
|
||||
5. ``light_sleep_enable`` = true, detailed as follows:
|
||||
|
||||
::
|
||||
|
||||
esp_pm_config_t pm_config = {
|
||||
.max_freq_mhz = CONFIG_EXAMPLE_MAX_CPU_FREQ_MHZ,
|
||||
.min_freq_mhz = CONFIG_EXAMPLE_MIN_CPU_FREQ_MHZ,
|
||||
#if CONFIG_FREERTOS_USE_TICKLESS_IDLE
|
||||
.light_sleep_enable = true
|
||||
#endif
|
||||
};
|
||||
ESP_ERROR_CHECK(esp_pm_configure(&pm_config));
|
||||
|
||||
6. Additional relevant parameters for configuration introduction
|
||||
|
||||
Recommended Configuration
|
||||
+++++++++++++++++++++++++++++
|
||||
|
||||
.. only:: esp32c3 or esp32s3
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 30 15
|
||||
|
||||
* - Configuration Name
|
||||
- Configuration Status
|
||||
|
||||
* - Enable power management component (:ref:`CONFIG_PM_ENABLE`)
|
||||
- ON
|
||||
|
||||
* - Enable RTOS Tickless IDLE mode (:ref:`CONFIG_FREERTOS_USE_TICKLESS_IDLE`)
|
||||
- ON
|
||||
|
||||
* - RTOS Tick rate (Hz) (:ref:`CONFIG_FREERTOS_HZ`)
|
||||
- 1000
|
||||
|
||||
* - Minimum IDLE Tick count before entering sleep mode (:ref:`CONFIG_FREERTOS_IDLE_TIME_BEFORE_SLEEP`)
|
||||
- 3
|
||||
|
||||
* - Put light sleep related codes in IRAM (:ref:`CONFIG_PM_SLP_IRAM_OPT`)
|
||||
- OFF
|
||||
|
||||
* - Put RTOS IDLE related codes in IRAM (:ref:`CONFIG_PM_RTOS_IDLE_OPT`)
|
||||
- OFF
|
||||
|
||||
* - RTC slow clock source (:ref:`CONFIG_RTC_CLK_SRC`)
|
||||
- Internal 150 kHz OSC
|
||||
|
||||
* - Disable all GPIO when chip at sleep (:ref:`CONFIG_PM_SLP_DISABLE_GPIO`)
|
||||
- ON
|
||||
|
||||
* - Power down MAC and baseband (:ref:`CONFIG_ESP_PHY_MAC_BB_PD`)
|
||||
- ON
|
||||
|
||||
* - Power down CPU (:ref:`CONFIG_PM_POWER_DOWN_CPU_IN_LIGHT_SLEEP`)
|
||||
- ON
|
||||
|
||||
.. only:: SOC_PM_SUPPORT_TAGMEM_PD
|
||||
|
||||
* - Power down I/D-cache tag memory (:ref:`CONFIG_PM_RESTORE_CACHE_TAGMEM_AFTER_LIGHT_SLEEP`)
|
||||
- ON
|
||||
|
||||
|
||||
* - Power down flash in light sleep (:ref:`CONFIG_ESP_SLEEP_POWER_DOWN_FLASH`)
|
||||
- OFF
|
||||
|
||||
* - ``max_freq_mhz``
|
||||
- 160
|
||||
|
||||
* - ``min_freq_mhz``
|
||||
- 40
|
||||
|
||||
* - ``light_sleep_enable``
|
||||
- true
|
||||
|
||||
.. note::
|
||||
Configurations not mentioned in the above table are set to default.
|
||||
|
||||
.. only:: esp32 or esp32s2
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 30 15
|
||||
|
||||
* - Configuration Name
|
||||
- Configuration Status
|
||||
|
||||
* - Enable power management component (:ref:`CONFIG_PM_ENABLE`)
|
||||
- ON
|
||||
|
||||
* - Enable RTOS Tickless IDLE mode (:ref:`CONFIG_FREERTOS_USE_TICKLESS_IDLE`)
|
||||
- ON
|
||||
|
||||
* - RTOS Tick rate (Hz) (:ref:`CONFIG_FREERTOS_HZ`)
|
||||
- 1000
|
||||
|
||||
* - Minimum IDLE Tick count before entering sleep mode (:ref:`CONFIG_FREERTOS_IDLE_TIME_BEFORE_SLEEP`)
|
||||
- 3
|
||||
|
||||
* - Put light sleep related codes in IRAM (:ref:`CONFIG_PM_SLP_IRAM_OPT`)
|
||||
- OFF
|
||||
|
||||
* - Put RTOS IDLE related codes in IRAM (:ref:`CONFIG_PM_RTOS_IDLE_OPT`)
|
||||
- OFF
|
||||
|
||||
* - RTC slow clock source (:ref:`CONFIG_RTC_CLK_SRC`)
|
||||
- Internal 150 kHz OSC
|
||||
|
||||
* - Disable all GPIO when chip at sleep (:ref:`CONFIG_PM_SLP_DISABLE_GPIO`)
|
||||
- ON
|
||||
|
||||
* - ``max_freq_mhz``
|
||||
- 160
|
||||
|
||||
* - ``min_freq_mhz``
|
||||
- 40
|
||||
|
||||
* - ``light_sleep_enable``
|
||||
- true
|
||||
|
||||
.. note::
|
||||
Configurations not mentioned in the above table are set to default.
|
||||
|
||||
.. only:: esp32c2
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 30 15
|
||||
|
||||
* - Configuration Name
|
||||
- Configuration Status
|
||||
|
||||
* - Enable power management component (:ref:`CONFIG_PM_ENABLE`)
|
||||
- ON
|
||||
|
||||
* - Enable RTOS Tickless IDLE mode (:ref:`CONFIG_FREERTOS_USE_TICKLESS_IDLE`)
|
||||
- ON
|
||||
|
||||
* - RTOS Tick rate (Hz) (:ref:`CONFIG_FREERTOS_HZ`)
|
||||
- 1000
|
||||
|
||||
* - Minimum IDLE Tick count before entering sleep mode (:ref:`CONFIG_FREERTOS_IDLE_TIME_BEFORE_SLEEP`)
|
||||
- 3
|
||||
|
||||
* - Put light sleep related codes in IRAM (:ref:`CONFIG_PM_SLP_IRAM_OPT`)
|
||||
- OFF
|
||||
|
||||
* - Put RTOS IDLE related codes in IRAM (:ref:`CONFIG_PM_RTOS_IDLE_OPT`)
|
||||
- OFF
|
||||
|
||||
* - RTC slow clock source (:ref:`CONFIG_RTC_CLK_SRC`)
|
||||
- Internal 150 kHz OSC
|
||||
|
||||
* - Disable all GPIO when chip at sleep (:ref:`CONFIG_PM_SLP_DISABLE_GPIO`)
|
||||
- ON
|
||||
|
||||
* - Power down flash in light sleep (:ref:`CONFIG_ESP_SLEEP_POWER_DOWN_FLASH`)
|
||||
- OFF
|
||||
|
||||
* - ``max_freq_mhz``
|
||||
- 120
|
||||
|
||||
* - ``min_freq_mhz``
|
||||
- 40
|
||||
|
||||
* - ``light_sleep_enable``
|
||||
- true
|
||||
|
||||
.. note::
|
||||
Configurations not mentioned in the above table are set to default.
|
||||
|
||||
Deep-sleep Mode Configuration
|
||||
---------------------------------
|
||||
|
||||
For Deep-sleep mode, other configurations are of minimal significance except wake-up source-related configurations.
|
||||
|
||||
Configuration Steps:
|
||||
|
||||
1. Configure wake-up sources (refer to :doc:`Sleep Modes <../../api-reference/system/sleep_modes>` for details)
|
||||
2. Call the API, as follows
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
/* Enter deep sleep */
|
||||
esp_deep_sleep_start();
|
||||
|
||||
Users can keep specific modules powered on during sleep using the following configuration options:
|
||||
|
||||
- Power up External 40 MHz XTAL
|
||||
In some special applications, certain modules require high clock accuracy and stability during sleep (e.g., BT). In such cases, it is recommended to enable the External 40 MHz XTAL during sleep.
|
||||
Code to enable and disable, as follows::
|
||||
|
||||
ESP_ERROR_CHECK(esp_sleep_pd_config(ESP_PD_DOMAIN_XTAL, ESP_PD_OPTION_ON));
|
||||
ESP_ERROR_CHECK(esp_sleep_pd_config(ESP_PD_DOMAIN_XTAL, ESP_PD_OPTION_OFF));
|
||||
|
||||
- Power up Internal 8 MHz OSC
|
||||
In some special applications, certain modules (e.g., LEDC) use the Internal 8 MHz OSC as a clock source and need to function normally during light sleep. In such cases, it is recommended to enable the Internal 8 MHz OSC during sleep.
|
||||
Code to enable and disable, as follows::
|
||||
|
||||
ESP_ERROR_CHECK(esp_sleep_pd_config(ESP_PD_DOMAIN_RTC8M, ESP_PD_OPTION_ON));
|
||||
ESP_ERROR_CHECK(esp_sleep_pd_config(ESP_PD_DOMAIN_RTC8M, ESP_PD_OPTION_OFF));
|
||||
417
docs/en/api-guides/low-power-mode/low-power-mode-wifi.rst
Normal file
417
docs/en/api-guides/low-power-mode/low-power-mode-wifi.rst
Normal file
@ -0,0 +1,417 @@
|
||||
Introduction to Low Power Mode in Wi-Fi Scenarios
|
||||
==================================================
|
||||
|
||||
:link_to_translation:`zh_CN:[中文]`
|
||||
|
||||
After the previous introduction to low power mode from a systemic perspective, this section delves into low power mode in Wi-Fi scenarios. Due to the complexity of Wi-Fi scenarios, basic principles of Wi-Fi power saving will be introduced before specific low power mode. This section is focused on station mode.
|
||||
|
||||
Choosing Low Power Mode in Wi-Fi Scenarios
|
||||
---------------------------------------------
|
||||
|
||||
To help users select appropriate low power mode, a summary table of low power modes in Wi-Fi scenarios is provided before detailed introduction.
|
||||
|
||||
.. todo - add sleep-current/esp32c5_summary.inc
|
||||
|
||||
.. only:: not esp32c5
|
||||
|
||||
.. include:: ../sleep-current/{IDF_TARGET_PATH_NAME}_summary.inc
|
||||
|
||||
.. note::
|
||||
|
||||
All currents in the table are average currents, and the terms in the table are explained in the following text. Users can refer to them as needed.
|
||||
|
||||
.. _Basic Principles of Wi-Fi Power Saving:
|
||||
|
||||
Basic Principles of Wi-Fi Power Saving
|
||||
----------------------------------------
|
||||
|
||||
Firstly, during the operation of a station, prolonged channel monitoring is required to avoid conflicts during transmission and reception. It leads to significant energy consumption as the RF module remains active, thus wasting power. Therefore, Wi-Fi protocols introduce power-saving modes.
|
||||
|
||||
The basic principle of power-saving mode is to reduce energy consumption by minimizing unnecessary monitoring time. Access points (APs) will cache packets for a station that has entered power-saving mode. At the same time, it will periodically send beacon frames containing Traffic Indication Map (TIM) information. TIM indicates the unicast packets cached by the AP. Within TIM, the Delivery Traffic Indication Message (DTIM) is special as it caches broadcast packets and sends them out periodically every n TIM intervals (determined by the AP). For stations, TIM is optional listening, while DTIM is mandatory listening. Therefore, station can choose to wake up only before each DTIM frame to power up Wi-Fi-related modules (RF modules) instead of constantly being in listening state. This effectively reduces power consumption.
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
DTIM DTIM
|
||||
TIM │ │
|
||||
│ │ │ │ │ │ │ │ │ │ │
|
||||
│ │ │ │ │ │ │ │ │ │ │
|
||||
AP ───┴────┴────┴────┴────┴────┴────┴────┴────┴────┴────┴────
|
||||
|
||||
|
||||
┌────┐ ┌────┐
|
||||
│ │ │ │
|
||||
│ │ │ │
|
||||
│ │ │ │
|
||||
Sta ────────────────┴────┴─────────────┴────┴─────────────────
|
||||
|
||||
DTIM4 Power Saving Mode Diagram
|
||||
|
||||
Second, the time from powering up to powering down Wi-Fi related modules in a station also affects power consumption. Apart from the necessary time for data transmission processing, there are four configurations mainly affecting the duration:
|
||||
|
||||
- Time offset caused by clock accuracy. The main reason is that clocks may deviate from ideal time to some extent, and the deviation can be positive or negative.
|
||||
- Time spent processing missed beacon frames, such as the duration of continuous listening after a missed beacon, the maximum allowable number of missed beacons, etc. The existence and duration of this period are uncertain but can be configured within a range.
|
||||
- Active time added to ensure the reception of burst data packets, which can be determined by configuration.
|
||||
- ILDE time is required for specific power-saving modes to meet entry conditions. Therefore, reducing the working time can improve power performance while meeting communication requirements.
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
┌────────────┬────────────┬────────────┬────────────┬────────────┐
|
||||
│ │ │ time spent │ │ │
|
||||
│time offset │ necessary │ processing │ active time│ IDLE time │
|
||||
│ │ processing │ missed │ │ │
|
||||
│ │ time │ beacon │ │ │
|
||||
└────────────┴────────────┴────────────┴────────────┴────────────┘
|
||||
Chip Operation Time Overview
|
||||
|
||||
Furthermore, when the station is not in a Wi-Fi transmission or reception state, other modules begin to affect the chip's power consumption. Different power-saving modes will configure different clock sources or dynamically adjust the operating frequencies of certain modules such as the CPU, while also shutting down varying numbers of functional modules, which effectively reduces the power consumption. Users can select suitable configurations according to their needs.
|
||||
|
||||
If time is plotted on the horizontal axis and current on the vertical axis, then the ideal current consumption graph of the chip under low power mode can be simplified as shown below:
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
▲
|
||||
Current |
|
||||
|
|
||||
| interval period
|
||||
| │ ◄──────────► │ │ ◄─► │
|
||||
| ┌─────┐ ┌─────┐ ┌─────┐
|
||||
| │ │ │ │ │ │
|
||||
| | | | | | | base current
|
||||
| | | | | | | |
|
||||
| | | | | | | ▼
|
||||
| ───┘ └────────┘ └────────┘ └──────
|
||||
|
|
||||
└───────────────────────────────────────────────►
|
||||
Time
|
||||
Ideal Current Graph of the Chip Under Low Power Mode
|
||||
|
||||
When the station needs to engage in Wi-Fi communication, the Wi-Fi-related modules (PHY) are activated, causing a significant increase in current. The current remains at a relatively high level until the task is completed. After that, the chip will deactivate the Wi-Fi-related modules, causing the current to decrease to a lower level.
|
||||
|
||||
Three main factors affect power consumption performance: interval, period, and base current.
|
||||
|
||||
- **Interval** refers to the interval at which the station's Wi-Fi-related modules operate. It can be customized by low power mode or determined by the DTIM interval according to Wi-Fi protocol power-saving mechanisms (see first part in :ref:`Basic Principles of Wi-Fi Power Saving`). Generally, a larger interval leads to better power performance under the same conditions. But it also results in slower response times, affecting communication timeliness.
|
||||
|
||||
- **Period** can be seen as the duration of each time the station's Wi-Fi operates, which also affects power performance. The period is not fixed (see second part in :ref:`Basic Principles of Wi-Fi Power Saving`). In ensuring normal Wi-Fi communication, a shorter period leads to better power performance. However, reducing the period will inevitably affect communication reliability.
|
||||
|
||||
- **Base current** refers to the current of the chip when the Wi-Fi-related modules are not active. It is influenced by various factors. Different power-saving modes have different sleep strategies. Therefore, optimizing the configuration to reduce the base current can improve power performance. But closing other modules will affect related functions and the wake-up time of the chip.
|
||||
|
||||
Therefore, power consumption can be reduced by considering the three aspects. Next, Modem-sleep mode and Auto Light-sleep mode will be introduced. The main difference between the two modes lies in the optimization of these three factors.
|
||||
|
||||
|
||||
Modem-sleep Mode
|
||||
----------------
|
||||
|
||||
The main principle of Modem-sleep mode is based on the DTIM mechanism. In this mode, the chip periodically wakes up for Wi-Fi-related tasks, and enters sleep state between intervals to power down PHY (RF module) to reduce power consumption. Besides, through the DTIM mechanism, the station can maintain Wi-Fi connection and data transmission with the AP.
|
||||
|
||||
Modem-sleep mode automatically enters sleep after the Wi-Fi task ends without the need to call an API. During sleep, only the Wi-Fi-related modules (PHY) are closed, while other modules remain in power-up state.
|
||||
|
||||
Modem-sleep mode will wake up according to the DTIM interval or listen interval (as introduced below in :ref:`Modem-sleep Mode Configuration`), acting as if the system has automatically set a Wi-Fi wake-up source. Therefore, users do not need to configure a wake-up source. The system can also wake up when actively sending packets.
|
||||
|
||||
Modem-sleep mode is a toggle mode that automatically runs after calling the API to activate it. Its workflow is very clear, as shown in the diagram below.
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
┌───────────┐ Wi-Fi task finished ┌───────────┐
|
||||
│ ├─────────────────────────────►│ modem │
|
||||
│ active │ │ sleep │
|
||||
│ │◄─────────────────────────────┤ │
|
||||
└───────────┘ DTIM interval activated └───────────┘
|
||||
/ sending packets
|
||||
|
||||
Modem-sleep Mode Workflow
|
||||
|
||||
Based on the base current graph provided above and combined with the operating principle of Modem-sleep mode, an ideal current graph can be derived, taking Min Modem-sleep mode (as introduced below in :ref:`Modem-sleep Mode Configuration`) as an example.
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
▲
|
||||
Current|
|
||||
| DTIM interval
|
||||
| │ ◄──────────► │
|
||||
| ┌─────┐ ┌─────┐ ┌─────┐
|
||||
| before │ │ │ │ │ │
|
||||
| DTIM | | | | | | Wi-Fi task
|
||||
| interval| | | | | | finished
|
||||
|activated | | | | | | /
|
||||
| \ │ │ │ │ │ │/
|
||||
| ────────┘ └────────┘ └────────┘ └──────
|
||||
|
|
||||
└─────────────────────────────────────────────────────►
|
||||
Time
|
||||
Ideal Current Graph of Min Modem-sleep Mode
|
||||
|
||||
Modem-sleep mode is generally used in scenarios where the CPU needs to remain active and maintain a Wi-Fi connection. For example, it is utilized to realize local voice wake-up by the {IDF_TARGET_NAME}, where the CPU continuously collects and processes audio data.
|
||||
|
||||
DFS + Modem-sleep Mode
|
||||
------------------------
|
||||
|
||||
In Modem-sleep mode, the CPU remains active while the DFS mechanism primarily adjusts the CPU and APB operating frequencies to reduce power consumption. Therefore, combining DFS with Modem sleep mode can further optimize power performance. Additionally, as the Wi-Fi task requests the :cpp:enumerator:`ESP_PM_CPU_FREQ_MAX` power lock to ensure the rapid execution of Wi-Fi tasks, frequency adjustment by DFS and Modem-sleep mode only occurs during the base current phase, which is after the Wi-Fi task ends.
|
||||
|
||||
In Wi-Fi scenarios, to help users understand main changes, the state of DFS can be simplified. Specifically, although DFS primarily adjusts frequencies based on the maximum demands of the CPU and APB locks, in Wi-Fi scenarios, the CPU frequency needs to be maximized for operation. Besides, after the Wi-Fi task ends, it can be ideally assumed that no other tasks need to be completed, and that after some time, both locks are released to enter IDLE state. This simplified situation also ignores any current variations caused by changes in the locks during this time.
|
||||
|
||||
In Wi-Fi scenarios, the flowchart of DFS csn be simplified as follows:
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
┌────────┐
|
||||
│ │
|
||||
│ DFS │
|
||||
│ │
|
||||
└───┬────┘
|
||||
│
|
||||
▼
|
||||
┌──────────┐ when IDLE ┌──────────┐
|
||||
│ │ ─────────────► │ │
|
||||
│ │ │ │
|
||||
│ active │ │ IDLE │
|
||||
│ │ │ │
|
||||
│ │ ◄───────────── │ │
|
||||
└──────────┘ not IDLE └──────────┘
|
||||
|
||||
Simplified Flowchart of DFS in the Wi-Fi Scenario
|
||||
|
||||
The system transitions between active state and IDLE state in Wi-Fi scenarios. After the Wi-Fi task is completed, the system releases all locks after a period of time and enters the IDLE state. At this point, the DFS mechanism reduces the frequency to the set minimum value, ignoring the frequency adjustment actions during the state transition, which facilitates understanding.
|
||||
|
||||
The DFS + Modem-sleep mode's ideal current graph is simplified as below:
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
▲ Wi-Fi task finished
|
||||
Current | / modem sleep
|
||||
| /
|
||||
| ┌─────┐ ┌─────┐
|
||||
| │ │ │ │
|
||||
| | | | | lock released
|
||||
| | | | | DFS frequency
|
||||
| | | | | reduced
|
||||
| | | | | / IDLE
|
||||
| | | | | /
|
||||
| | │ | │ /
|
||||
| │ └─┐ │ └─┐
|
||||
| ────────┘ └───────────────┘ └─────────
|
||||
|
|
||||
└─────────────────────────────────────────────────────►
|
||||
Time
|
||||
DFS + Modem-sleep Mode's Ideal Current Graph
|
||||
|
||||
Auto Light-sleep Mode + Wi-Fi Scenario
|
||||
----------------------------------------
|
||||
|
||||
Auto Light-sleep mode combines the ESP-IDF power management mechanism, the DTIM mechanism, and Light-sleep mode in Wi-Fi scenarios. Enabling power management is a prerequisite of this mode, and its auto aspect is demonstrated by the system automatically entering Light-sleep after being in the IDLE state for a set duration. Additionally, auto Auto Light-sleep mode adheres to the DTIM mechanism. The system will automatically wake up to maintain Wi-Fi connection with AP.
|
||||
|
||||
In the Wi-Fi environment, the sleep mechanism of Auto Light-sleep mode remains consistent with that of the pure system. It still relies on the power management mechanism, where the condition for entering sleep is when the system has been IDLE for a duration exceeding the set time. The system will assess if the IDLE time meets the conditions, and if so, it will directly enter sleep. This process is automatic. During sleep, RF, the 8 MHz oscillator, the 40 MHz high-speed crystal oscillator, PLL, and gated digital core clock are automatically turned off, and CPU operation is suspended.
|
||||
|
||||
In the Wi-Fi environment, the Auto Light-sleep mode follows the DTIM mechanism. The system will automatically wake up before the arrival of DTIM frames, as if a Wi-Fi wake-up source has been set. Therefore, there is no need for configuration. Additionally, the system can be awakened when actively sending packets.
|
||||
|
||||
The operation workflow of Auto Light-sleep mode in the Wi-Fi environment is relatively complex, but it is entirely automated throughout. Specific details are illustrated in the diagram.
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
┌────────┐
|
||||
│ │
|
||||
│ DFS │
|
||||
│ │
|
||||
└───┬────┘
|
||||
│
|
||||
▼
|
||||
┌──────────┐ when IDLE ┌──────────┐ exceed set time ┌──────────┐
|
||||
│ │ ─────────────► │ │ ────────────► │ │
|
||||
│ │ │ │ │ auto │
|
||||
│ active │ │ IDLE │ │ light │
|
||||
│ │ │ │ │ sleep │
|
||||
│ │ ◄───────────── │ │ │ │
|
||||
└──────────┘ not IDLE └──────────┘ └──────┬───┘
|
||||
▲ │
|
||||
│ DTIM interval activated / sending packets │
|
||||
└───────────────────────────────────────────────────────────────┘
|
||||
|
||||
Auto Light-sleep Mode Workflow
|
||||
|
||||
In Wi-Fi scenarios, Auto Light-sleep mode is often enabled simultaneously with Modem-sleep mode. Here, an ideal current graph of Modem + Auto Light-sleep mode is provided, with key nodes marked on the graph.
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
DTIM interval
|
||||
▲ │ ◄───────────────────► │
|
||||
Current | ┌─────┐ ┌─────┐
|
||||
| │ │ \ │ │
|
||||
| | | \ | |
|
||||
| | | Wi-Fi task | |
|
||||
| | | finished | |
|
||||
| | | modem sleep | |
|
||||
| before | | | | IDLE time
|
||||
| DTIM | | IDLE | | exceeds set time
|
||||
| activated| │ DFS frequency | │ light sleep
|
||||
| \ | └─┐ / reduced | └─┐ /
|
||||
| \ │ └─┐ / │ └─┐ /
|
||||
| ────────┘ └─────────────┘ └─────────
|
||||
|
|
||||
└─────────────────────────────────────────────────────►
|
||||
Time
|
||||
Ideal Current Graph of Modem + Auto Light-sleep Mode
|
||||
|
||||
In the Wi-Fi environment, Auto Light-sleep mode can be utilized to maintain Wi-Fi connection and respond promptly to data sent by AP. Additionally, the CPU can remain IDLE when no commands are received. For example, in applications such as Wi-Fi switches, the CPU is mostly IDLE until it receives a control command to operate on GPIO.
|
||||
|
||||
|
||||
Deep-sleep Mode + Wi-Fi Scenario
|
||||
-----------------------------------
|
||||
|
||||
The Deep-sleep mode in Wi-Fi scenarios is essentially the same as in a pure system. For details, please refer to :ref:`Deep-sleep Mode`. Here, it will not be further discussed.
|
||||
|
||||
|
||||
Low Power Mode Configuration in Wi-Fi Scenarios
|
||||
-----------------------------------------------------
|
||||
|
||||
After introducing the low power mode in Wi-Fi scenarios, this section will cover common configuration options, unique configuration options for each mode, and instructions for using the corresponding low power mode APIs. Additionally, recommendations for the respective modes' configurations (including recommended configurations for pure systems) will be provided, along with specific performance details.
|
||||
|
||||
.. note::
|
||||
|
||||
The configuration options below are briefly introduced. For more detailed information, please click the link behind each option.
|
||||
|
||||
Common Configuration Options
|
||||
++++++++++++++++++++++++++++++++
|
||||
|
||||
- Power consumption related:
|
||||
|
||||
- Max Wi-Fi TX power (dBm) (:ref:`CONFIG_ESP_PHY_MAX_WIFI_TX_POWER`)
|
||||
|
||||
- Speed optimization related:
|
||||
|
||||
- Wi-Fi IRAM speed optimization (:ref:`CONFIG_ESP_WIFI_IRAM_OPT`)
|
||||
- Wi-Fi RX IRAM speed optimization (:ref:`CONFIG_ESP_WIFI_RX_IRAM_OPT`)
|
||||
- Wi-Fi Sleep IRAM speed optimization (:ref:`CONFIG_ESP_WIFI_SLP_IRAM_OPT`)
|
||||
|
||||
|
||||
- Wi-Fi Protocol related:
|
||||
|
||||
- Minimum active time (:ref:`CONFIG_ESP_WIFI_SLP_DEFAULT_MIN_ACTIVE_TIME`)
|
||||
|
||||
- Maximum keep alive time (:ref:`CONFIG_ESP_WIFI_SLP_DEFAULT_MAX_ACTIVE_TIME`)
|
||||
|
||||
- Send gratuitous ARP periodically (:ref:`CONFIG_LWIP_ESP_GRATUITOUS_ARP`)
|
||||
|
||||
- Wi-Fi sleep optimize when beacon lost (:ref:`CONFIG_ESP_WIFI_SLP_BEACON_LOST_OPT`)
|
||||
|
||||
|
||||
.. _Modem-sleep Mode Configuration:
|
||||
|
||||
Modem-sleep Mode Configuration
|
||||
++++++++++++++++++++++++++++++++
|
||||
|
||||
- Configurable Options
|
||||
|
||||
- Min Modem
|
||||
This parameter indicates that the station operates according to the DTIM cycle. It wakes up before each DTIM to receive beacon frames, which ensures that broadcast information is not missed. However, the DTIM cycle is determined by the AP. If the DTIM cycle is short, the power saving effect will be reduced.
|
||||
|
||||
- Max Modem
|
||||
This parameter indicates that the station customizes a listen interval and wakes up to receive beacon frames at intervals defined by the listen interval. This approach saves power when the listen interval is large but may lead to missed DTIMs and broadcast data.
|
||||
|
||||
|
||||
- Configuration Steps
|
||||
|
||||
- Call the API and select the mode parameters
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
typedef enum {
|
||||
WIFI_PS_NONE,
|
||||
WIFI_PS_MIN_MODEM,
|
||||
WIFI_PS_MAX_MODEM,
|
||||
} wifi_ps_type_t;
|
||||
esp_err_t esp_wifi_set_ps(wifi_ps_type_t type);
|
||||
|
||||
If WIFI_PS_MAX_MODEM is selected, the listen interval also needs to be configured. An example is provided below::
|
||||
|
||||
#define LISTEN_INTERVAL 3
|
||||
wifi_config_t wifi_config = {
|
||||
.sta = {
|
||||
.ssid = "SSID",
|
||||
.password = "Password",
|
||||
.listen_interval = LISTEN_INTERVAL,
|
||||
},
|
||||
};
|
||||
ESP_ERROR_CHECK(esp_wifi_set_mode(WIFI_MODE_STA));
|
||||
ESP_ERROR_CHECK(esp_wifi_set_config(ESP_IF_WIFI_STA, &wifi_config));
|
||||
ESP_ERROR_CHECK(esp_wifi_start());
|
||||
|
||||
- Recommended Configuration
|
||||
|
||||
The recommended configuration provided here is for Min Modem-sleep mode + DFS.
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 15
|
||||
|
||||
* - Configuration Name
|
||||
- Configuration Status
|
||||
|
||||
* - WIFI_PS_MIN_MODEM
|
||||
- ON
|
||||
|
||||
* - CONFIG_PM_ENABLE
|
||||
- ON
|
||||
|
||||
* - RTOS Tick rate (Hz)
|
||||
- 1000
|
||||
|
||||
* - ``max_freq_mhz``
|
||||
- 160
|
||||
|
||||
* - ``min_freq_mhz``
|
||||
- 40
|
||||
|
||||
* - ``light_sleep_enable``
|
||||
- false
|
||||
|
||||
- Configuration Performance
|
||||
|
||||
.. todo - add sleep-current/esp32c5_modem_sleep.inc
|
||||
|
||||
.. only:: not esp32c5
|
||||
|
||||
.. include:: ../sleep-current/{IDF_TARGET_PATH_NAME}_modem_sleep.inc
|
||||
|
||||
|
||||
Auto Light-sleep Mode + Wi-Fi Scenario Configuration
|
||||
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
|
||||
|
||||
Auto Light-sleep mode in Wi-Fi scenarios does not require wake-up source configuration compared with a pure system. But the remaining part of configuration is basically the same in the two operation scenarios. Therefore, detailed introduction of configurable options, configuration steps, and recommended configurations can be found in the previous section :ref:`Deep-sleep Mode`, with the Wi-Fi-related configurations set to default.
|
||||
|
||||
- Configuration Performance
|
||||
|
||||
The configuration performance mirrors that of the recommended Auto Light-sleep mode configuration in a pure system, combined with the default Wi-Fi-related configurations in the Wi-Fi environment.
|
||||
|
||||
.. todo - add sleep-current/esp32c5_light_sleep.inc
|
||||
|
||||
.. only:: not esp32c5
|
||||
|
||||
.. include:: ../sleep-current/{IDF_TARGET_PATH_NAME}_light_sleep.inc
|
||||
|
||||
Deep-sleep Mode + Wi-Fi Scenario Configuration
|
||||
++++++++++++++++++++++++++++++++++++++++++++++++
|
||||
|
||||
Deep-sleep mode configuration in Wi-Fi scenarios is essentially the same as in a pure system. Therefore, detailed introduction of configurable options, configuration steps, and recommended configurations can be found in the previous section :ref:`Deep-sleep Mode`, with the Wi-Fi-related configurations set to default.
|
||||
|
||||
- Configuration Performance
|
||||
|
||||
The performance of this configuration mirrors that of the recommended Deep-sleep mode configuration in a pure system, combined with the default Wi-Fi-related configurations in the Wi-Fi environment.
|
||||
|
||||
.. only:: esp32
|
||||
|
||||
Average current approximately 5.0 μA
|
||||
|
||||
.. only:: esp32s2
|
||||
|
||||
Average current approximately 5.0 μA
|
||||
|
||||
.. only:: esp32s3
|
||||
|
||||
Average current approximately 6.9 μA
|
||||
|
||||
.. only:: esp32c3
|
||||
|
||||
Average current approximately 4.8 μA
|
||||
|
||||
.. only:: esp32c2
|
||||
|
||||
Average current approximately 4.9 μA
|
||||
@ -1 +1,27 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32_light_sleep.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
- DTIM
|
||||
- Average current (mA)
|
||||
- Max current (mA)
|
||||
- Min current (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- 1
|
||||
- 3.34
|
||||
- 129.36
|
||||
- 1.35
|
||||
|
||||
* - 160 MHz
|
||||
- 3
|
||||
- 2.33
|
||||
- 130.17
|
||||
- 1.33
|
||||
|
||||
* - 160 MHz
|
||||
- 10
|
||||
- 2.19
|
||||
- 129.87
|
||||
- 1.32
|
||||
|
||||
@ -1 +1,52 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32_modem_sleep.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 10 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
- DFS
|
||||
- DTIM
|
||||
- Average current (mA)
|
||||
- Max current (mA)
|
||||
- Min current (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
- 1
|
||||
- 22.65
|
||||
- 133.03
|
||||
- 5.48
|
||||
|
||||
* - 160 MHz
|
||||
- OFF
|
||||
- 1
|
||||
- 31.12
|
||||
- 253.74
|
||||
- 27.18
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
- 3
|
||||
- 21.89
|
||||
- 247.68
|
||||
- 5.25
|
||||
|
||||
* - 160 MHz
|
||||
- OFF
|
||||
- 3
|
||||
- 28.81
|
||||
- 209.42
|
||||
- 27.77
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
- 10
|
||||
- 20.01
|
||||
- 216.51
|
||||
- 6.02
|
||||
|
||||
* - 160 MHz
|
||||
- OFF
|
||||
- 10
|
||||
- 29.66
|
||||
- 114.17
|
||||
- 27.77
|
||||
|
||||
@ -1 +1,69 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32_summary.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 20 30 20 20
|
||||
|
||||
* - Item
|
||||
- Modem-sleep
|
||||
- Modem-sleep+DFS
|
||||
- Auto Light-sleep
|
||||
- Deep-sleep
|
||||
|
||||
* - Sleep
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Manual
|
||||
|
||||
* - Wake-up
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Configure Wake-up Source
|
||||
|
||||
* - Wi-Fi Connection
|
||||
- Maintain
|
||||
- Maintain
|
||||
- Maintain
|
||||
- Disconnect
|
||||
|
||||
* - CPU
|
||||
- On
|
||||
- On/Throttled
|
||||
- Paused
|
||||
- Off
|
||||
|
||||
* - System Clock
|
||||
- On
|
||||
- On
|
||||
- Off
|
||||
- Off
|
||||
|
||||
* - Peripherals
|
||||
- On
|
||||
- On
|
||||
- On
|
||||
- Off
|
||||
|
||||
* - DTIM1
|
||||
- 31.12 mA
|
||||
- 22.65 mA
|
||||
- 3.34 mA
|
||||
- /
|
||||
|
||||
* - DTIM3
|
||||
- 28.81 mA
|
||||
- 21.89 mA
|
||||
- 2.33 mA
|
||||
- /
|
||||
|
||||
* - DTIM10
|
||||
- 29.66 mA
|
||||
- 20.01 mA
|
||||
- 2.19 mA
|
||||
- /
|
||||
|
||||
* - Average Current
|
||||
- /
|
||||
- /
|
||||
- /
|
||||
- 5 μA
|
||||
|
||||
@ -1 +1,27 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32c2_light_sleep.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
- DTIM
|
||||
- Average current (mA)
|
||||
- Max current (mA)
|
||||
- Min current (mA)
|
||||
|
||||
* - 120 MHz
|
||||
- 1
|
||||
- 1.6
|
||||
- 67.8
|
||||
- 0.12
|
||||
|
||||
* - 120 MHz
|
||||
- 3
|
||||
- 0.71
|
||||
- 66.5
|
||||
- 0.12
|
||||
|
||||
* - 120 MHz
|
||||
- 10
|
||||
- 0.39
|
||||
- 64.8
|
||||
- 0.12
|
||||
|
||||
@ -1 +1,52 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32c2_modem_sleep.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 10 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
- DFS
|
||||
- DTIM
|
||||
- Average current (mA)
|
||||
- Max current (mA)
|
||||
- Min current (mA)
|
||||
|
||||
* - 120 MHz
|
||||
- ON
|
||||
- 1
|
||||
- 7.5
|
||||
- 65.9
|
||||
- 6.0
|
||||
|
||||
* - 120 MHz
|
||||
- OFF
|
||||
- 1
|
||||
- 13.6
|
||||
- 221.5
|
||||
- 12.6
|
||||
|
||||
* - 120 MHz
|
||||
- ON
|
||||
- 3
|
||||
- 6.9
|
||||
- 65.4
|
||||
- 6.0
|
||||
|
||||
* - 120 MHz
|
||||
- OFF
|
||||
- 3
|
||||
- 13.0
|
||||
- 220.2
|
||||
- 12.6
|
||||
|
||||
* - 120 MHz
|
||||
- ON
|
||||
- 10
|
||||
- 6.6
|
||||
- 64.9
|
||||
- 6.0
|
||||
|
||||
* - 120 MHz
|
||||
- OFF
|
||||
- 10
|
||||
- 12.9
|
||||
- 216.8
|
||||
- 12.6
|
||||
|
||||
@ -1 +1,69 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32c2_summary.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 20 30 20 20
|
||||
|
||||
* - Item
|
||||
- Modem-sleep
|
||||
- Modem-sleep+DFS
|
||||
- Auto Light-sleep
|
||||
- Deep-sleep
|
||||
|
||||
* - Sleep
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Manual
|
||||
|
||||
* - Wake-up
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Configure Wake-up Source
|
||||
|
||||
* - Wi-Fi Connection
|
||||
- Maintain
|
||||
- Maintain
|
||||
- Maintain
|
||||
- Disconnect
|
||||
|
||||
* - CPU
|
||||
- On
|
||||
- On/Throttled
|
||||
- Paused
|
||||
- Off
|
||||
|
||||
* - System Clock
|
||||
- On
|
||||
- On
|
||||
- Off
|
||||
- Off
|
||||
|
||||
* - Peripherals
|
||||
- On
|
||||
- On
|
||||
- On
|
||||
- Off
|
||||
|
||||
* - DTIM1
|
||||
- 13.6
|
||||
- 7.5
|
||||
- 1.6
|
||||
- /
|
||||
|
||||
* - DTIM3
|
||||
- 13.0
|
||||
- 6.9
|
||||
- 0.71
|
||||
- /
|
||||
|
||||
* - DTIM10
|
||||
- 12.9
|
||||
- 6.6
|
||||
- 0.39
|
||||
- /
|
||||
|
||||
* - Average Current
|
||||
- /
|
||||
- /
|
||||
- /
|
||||
- 4.9 μA
|
||||
|
||||
@ -1 +1,27 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32c3_light_sleep.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
- DTIM
|
||||
- Average current (mA)
|
||||
- Max current (mA)
|
||||
- Min current (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- 1
|
||||
- 1.4
|
||||
- 87.26
|
||||
- 0.14
|
||||
|
||||
* - 160 MHz
|
||||
- 3
|
||||
- 0.62
|
||||
- 86.33
|
||||
- 0.14
|
||||
|
||||
* - 160 MHz
|
||||
- 10
|
||||
- 0.31
|
||||
- 86.11
|
||||
- 0.14
|
||||
|
||||
@ -1 +1,52 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32c3_modem_sleep.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 10 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
- DFS
|
||||
- DTIM
|
||||
- Average current (mA)
|
||||
- Max current (mA)
|
||||
- Min current (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
- 1
|
||||
- 11.35
|
||||
- 83.31
|
||||
- 5.03
|
||||
|
||||
* - 160 MHz
|
||||
- OFF
|
||||
- 1
|
||||
- 21.47
|
||||
- 191.53
|
||||
- 20.58
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
- 3
|
||||
- 10.71
|
||||
- 82.82
|
||||
- 5.09
|
||||
|
||||
* - 160 MHz
|
||||
- OFF
|
||||
- 3
|
||||
- 20.82
|
||||
- 82.98
|
||||
- 20.48
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
- 10
|
||||
- 10.32
|
||||
- 81.05
|
||||
- 5.74
|
||||
|
||||
* - 160 MHz
|
||||
- OFF
|
||||
- 10
|
||||
- 20.67
|
||||
- 229.83
|
||||
- 20.48
|
||||
|
||||
@ -1 +1,69 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32c3_summary.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 20 30 20 20
|
||||
|
||||
* - Item
|
||||
- Modem-sleep
|
||||
- Modem-sleep+DFS
|
||||
- Auto Ligh-sleep
|
||||
- Deep-sleep
|
||||
|
||||
* - Sleep
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Manual
|
||||
|
||||
* - Wake-up
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Configure Wake-up Source
|
||||
|
||||
* - Wi-Fi Connection
|
||||
- Maintain
|
||||
- Maintain
|
||||
- Maintain
|
||||
- Disconnect
|
||||
|
||||
* - CPU
|
||||
- On
|
||||
- On/Throttled
|
||||
- Paused
|
||||
- Off
|
||||
|
||||
* - System Clock
|
||||
- On
|
||||
- On
|
||||
- Off
|
||||
- Off
|
||||
|
||||
* - Peripherals
|
||||
- On
|
||||
- On
|
||||
- On
|
||||
- Off
|
||||
|
||||
* - DTIM1
|
||||
- 21.47 mA
|
||||
- 11.35 mA
|
||||
- 1.4 mA
|
||||
- /
|
||||
|
||||
* - DTIM3
|
||||
- 20.82 mA
|
||||
- 10.71 mA
|
||||
- 0.62 mA
|
||||
- /
|
||||
|
||||
* - DTIM10
|
||||
- 20.67 mA
|
||||
- 10.32 mA
|
||||
- 0.31 mA
|
||||
- /
|
||||
|
||||
* - Average Current
|
||||
- /
|
||||
- /
|
||||
- /
|
||||
- 4.8 μA
|
||||
|
||||
@ -1 +1,27 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32c6_light_sleep.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
- DTIM
|
||||
- Average current (mA)
|
||||
- Max current (mA)
|
||||
- Min current (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- 1
|
||||
- 0.919
|
||||
- 103.149
|
||||
- 0.053
|
||||
|
||||
* - 160 MHz
|
||||
- 3
|
||||
- 0.368
|
||||
- 102.428
|
||||
- 0.052
|
||||
|
||||
* - 160 MHz
|
||||
- 10
|
||||
- 0.172
|
||||
- 102.087
|
||||
- 0.052
|
||||
|
||||
@ -1 +1,52 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32c6_modem_sleep.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 10 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
- DFS
|
||||
- DTIM
|
||||
- Average current (mA)
|
||||
- Max current (mA)
|
||||
- Min current (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
- 1
|
||||
- 14.37
|
||||
- 84.40
|
||||
- 10.02
|
||||
|
||||
* - 160 MHz
|
||||
- OFF
|
||||
- 1
|
||||
- 27.48
|
||||
- 87.55
|
||||
- 26.92
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
- 3
|
||||
- 13.9
|
||||
- 83.9
|
||||
- 10.13
|
||||
|
||||
* - 160 MHz
|
||||
- OFF
|
||||
- 3
|
||||
- 27.08
|
||||
- 87.74
|
||||
- 26.91
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
- 10
|
||||
- 13.71
|
||||
- 82.77
|
||||
- 10.04
|
||||
|
||||
* - 160 MHz
|
||||
- OFF
|
||||
- 10
|
||||
- 26.85
|
||||
- 88.07
|
||||
- 26.7
|
||||
|
||||
@ -1 +1,69 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32c6_summary.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 20 30 20 20
|
||||
|
||||
* - Item
|
||||
- Modem-sleep
|
||||
- Modem-sleep+DFS
|
||||
- Auto Light-sleep
|
||||
- Deep-sleep
|
||||
|
||||
* - Sleep
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Manual
|
||||
|
||||
* - Wake-up
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Configure Wake-up Source
|
||||
|
||||
* - Wi-Fi Connection
|
||||
- Maintain
|
||||
- Maintain
|
||||
- Maintain
|
||||
- Disconnect
|
||||
|
||||
* - CPU
|
||||
- On
|
||||
- On/Throttled
|
||||
- Paused
|
||||
- Off
|
||||
|
||||
* - System Clock
|
||||
- On
|
||||
- On
|
||||
- Off
|
||||
- Off
|
||||
|
||||
* - Peripherals
|
||||
- On
|
||||
- On
|
||||
- On
|
||||
- Off
|
||||
|
||||
* - DTIM1
|
||||
- 27.48 mA
|
||||
- 14.37 mA
|
||||
- 0.919 mA
|
||||
- /
|
||||
|
||||
* - DTIM3
|
||||
- 27.08 mA
|
||||
- 13.9 mA
|
||||
- 0.368 mA
|
||||
- /
|
||||
|
||||
* - DTIM10
|
||||
- 26.85 mA
|
||||
- 13.71 mA
|
||||
- 0.172 mA
|
||||
- /
|
||||
|
||||
* - Average Current
|
||||
- /
|
||||
- /
|
||||
- /
|
||||
- 6.7 μA
|
||||
|
||||
@ -1 +1,27 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32s2_light_sleep.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
- DTIM
|
||||
- Average current (mA)
|
||||
- Max current (mA)
|
||||
- Min current (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- 1
|
||||
- 2.48
|
||||
- 94.88
|
||||
- 0.96
|
||||
|
||||
* - 160 MHz
|
||||
- 3
|
||||
- 2.96
|
||||
- 97.15
|
||||
- 2.25
|
||||
|
||||
* - 160 MHz
|
||||
- 10
|
||||
- 2.69
|
||||
- 98.66
|
||||
- 2.25
|
||||
|
||||
@ -1 +1,52 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32s2_modem_sleep.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 10 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
- DFS
|
||||
- DTIM
|
||||
- Average current (mA)
|
||||
- Max current (mA)
|
||||
- Min current (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
- 1
|
||||
- 11.71
|
||||
- 83.87
|
||||
- 5.04
|
||||
|
||||
* - 160 MHz
|
||||
- OFF
|
||||
- 1
|
||||
- 31.14
|
||||
- 160.26
|
||||
- 29.04
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
- 3
|
||||
- 12.4
|
||||
- 84.85
|
||||
- 10.0
|
||||
|
||||
* - 160 MHz
|
||||
- OFF
|
||||
- 3
|
||||
- 29.06
|
||||
- 178.67
|
||||
- 28.25
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
- 10
|
||||
- 12.15
|
||||
- 84.18
|
||||
- 10.01
|
||||
|
||||
* - 160 MHz
|
||||
- OFF
|
||||
- 10
|
||||
- 28.5
|
||||
- 176.69
|
||||
- 28.21
|
||||
|
||||
@ -1 +1,69 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32s2_summary.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 20 30 20 20
|
||||
|
||||
* - Item
|
||||
- Modem-sleep
|
||||
- Modem-sleep+DFS
|
||||
- Auto Light-sleep
|
||||
- Deep-sleep
|
||||
|
||||
* - Sleep
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Manual
|
||||
|
||||
* - Wake-up
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Configure Wake-up Source
|
||||
|
||||
* - Wi-Fi Connection
|
||||
- Maintain
|
||||
- Maintain
|
||||
- Maintain
|
||||
- Disconnect
|
||||
|
||||
* - CPU
|
||||
- On
|
||||
- On/Throttled
|
||||
- Paused
|
||||
- Off
|
||||
|
||||
* - System Clock
|
||||
- On
|
||||
- On
|
||||
- Off
|
||||
- Off
|
||||
|
||||
* - Peripherals
|
||||
- On
|
||||
- On
|
||||
- On
|
||||
- Off
|
||||
|
||||
* - DTIM1
|
||||
- 31.14 mA
|
||||
- 11.71 mA
|
||||
- 2.48 mA
|
||||
- /
|
||||
|
||||
* - DTIM3
|
||||
- 29.06 mA
|
||||
- 12.4 mA
|
||||
- 2.96 mA
|
||||
- /
|
||||
|
||||
* - DTIM10
|
||||
- 28.5 mA
|
||||
- 12.15 mA
|
||||
- 2.69 mA
|
||||
- /
|
||||
|
||||
* - Average Current
|
||||
- /
|
||||
- /
|
||||
- /
|
||||
- 5 μA
|
||||
|
||||
@ -1 +1,27 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32s3_light_sleep.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
- DTIM
|
||||
- Average current (mA)
|
||||
- Max current (mA)
|
||||
- Min current (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- 1
|
||||
- 2.45
|
||||
- 120.21
|
||||
- 0.28
|
||||
|
||||
* - 160 MHz
|
||||
- 3
|
||||
- 1.33
|
||||
- 120.25
|
||||
- 0.28
|
||||
|
||||
* - 160 MHz
|
||||
- 10
|
||||
- 0.93
|
||||
- 120.04
|
||||
- 0.28
|
||||
|
||||
@ -1 +1,52 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32s3_modem_sleep.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 10 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
- DFS
|
||||
- DTIM
|
||||
- Average current (mA)
|
||||
- Max current (mA)
|
||||
- Min current (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
- 1
|
||||
- 20.7
|
||||
- 113.5
|
||||
- 15.0
|
||||
|
||||
* - 160 MHz
|
||||
- OFF
|
||||
- 1
|
||||
- 40.1
|
||||
- 235.8
|
||||
- 37.8
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
- 3
|
||||
- 19.9
|
||||
- 113.4
|
||||
- 15.0
|
||||
|
||||
* - 160 MHz
|
||||
- OFF
|
||||
- 3
|
||||
- 38.7
|
||||
- 267.2
|
||||
- 37.9
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
- 10
|
||||
- 19.5
|
||||
- 113.4
|
||||
- 15.0
|
||||
|
||||
* - 160 MHz
|
||||
- OFF
|
||||
- 10
|
||||
- 38.2
|
||||
- 259.7
|
||||
- 37.9
|
||||
|
||||
@ -1 +1,69 @@
|
||||
.. include:: ../../../zh_CN/api-guides/sleep-current/esp32s3_summary.inc
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 20 30 20 20
|
||||
|
||||
* - Item
|
||||
- Modem-sleep
|
||||
- Modem-sleep+DFS
|
||||
- Auto Light-sleep
|
||||
- Deep-sleep
|
||||
|
||||
* - Sleep
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Manual
|
||||
|
||||
* - Wake-up
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Automatic
|
||||
- Configure Wake-up Source
|
||||
|
||||
* - Wi-Fi Connection
|
||||
- Maintain
|
||||
- Maintain
|
||||
- Maintain
|
||||
- Disconnect
|
||||
|
||||
* - CPU
|
||||
- On
|
||||
- On/Throttled
|
||||
- Paused
|
||||
- Off
|
||||
|
||||
* - System Clock
|
||||
- On
|
||||
- On
|
||||
- Off
|
||||
- Off
|
||||
|
||||
* - Peripherals
|
||||
- On
|
||||
- On
|
||||
- On
|
||||
- Off
|
||||
|
||||
* - DTIM1
|
||||
- 40.1
|
||||
- 20.7
|
||||
- 2.45
|
||||
- /
|
||||
|
||||
* - DTIM3
|
||||
- 38.7
|
||||
- 19.9
|
||||
- 1.33
|
||||
- /
|
||||
|
||||
* - DTIM10
|
||||
- 38.2
|
||||
- 19.5
|
||||
- 0.93
|
||||
- /
|
||||
|
||||
* - Average Current
|
||||
- /
|
||||
- /
|
||||
- /
|
||||
- 6.8 μA
|
||||
|
||||
@ -1759,7 +1759,7 @@ A config option :ref:`CONFIG_ESP_WIFI_11R_SUPPORT` and configuration parameter :
|
||||
{IDF_TARGET_NAME} Wi-Fi Power-saving Mode
|
||||
-----------------------------------------
|
||||
|
||||
This subsection will briefly introduce the concepts and usage related to Wi-Fi Power Saving Mode, for a more detailed introduction please refer to the :doc:`Low Power Mode User Guide <../api-guides/low-power-mode>`
|
||||
This subsection will briefly introduce the concepts and usage related to Wi-Fi Power Saving Mode, for a more detailed introduction please refer to the :doc:`Low Power Mode User Guide <../api-guides/low-power-mode/index>`
|
||||
|
||||
Station Sleep
|
||||
++++++++++++++++++++++
|
||||
|
||||
@ -29,6 +29,7 @@ API 指南
|
||||
:CONFIG_IDF_TARGET_ARCH_XTENSA: hlinterrupts
|
||||
jtag-debugging/index
|
||||
linker-script-generation
|
||||
low-power-mode/index
|
||||
lwip
|
||||
memory-types
|
||||
openthread
|
||||
@ -45,5 +46,4 @@ API 指南
|
||||
:SOC_USB_SERIAL_JTAG_SUPPORTED: usb-serial-jtag-console
|
||||
:SOC_WIFI_SUPPORTED: wifi
|
||||
:SOC_WIFI_SUPPORTED: wifi-security
|
||||
low-power-mode
|
||||
:SOC_WIFI_SUPPORTED or SOC_BT_SUPPORTED or SOC_IEEE802154_SUPPORTED: phy
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
15
docs/zh_CN/api-guides/low-power-mode/index.rst
Normal file
15
docs/zh_CN/api-guides/low-power-mode/index.rst
Normal file
@ -0,0 +1,15 @@
|
||||
低功耗模式
|
||||
============
|
||||
|
||||
:link_to_translation:`en:[English]`
|
||||
|
||||
概述
|
||||
------
|
||||
|
||||
在嵌入式物联网应用场中，待机性能表现十分重要。本指南旨在介绍 {IDF_TARGET_NAME} 低功耗的基本原理，同时介绍 {IDF_TARGET_NAME} 支持的低功耗模式。文档还会具体给出推荐配置、配置步骤和每种模式下的功耗表现，以帮助用户根据实际需求快速配置适合的低功耗模式。
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
|
||||
low-power-mode-soc
|
||||
:SOC_WIFI_SUPPORTED: low-power-mode-wifi
|
||||
495
docs/zh_CN/api-guides/low-power-mode/low-power-mode-soc.rst
Normal file
495
docs/zh_CN/api-guides/low-power-mode/low-power-mode-soc.rst
Normal file
@ -0,0 +1,495 @@
|
||||
系统低功耗模式介绍
|
||||
===================
|
||||
|
||||
:link_to_translation:`en:[English]`
|
||||
|
||||
{IDF_TARGET_NAME} 支持多种低功耗模式，从系统功耗管理角度来看，主要有 DFS、Light-sleep 模式和 Deep-sleep 模式。这些模式降低功耗的主要策略是在不影响系统功能的前提下，尽可能降低时钟频率 (DFS) 或进入睡眠状态，在睡眠状态下关闭不必要的电源域或对不使用的外设进行时钟门控以降低功耗。根据关闭电源域的等级是否会破坏程序运行上下文又细分为 Light-sleep 模式和 Deep-sleep 模式。
|
||||
|
||||
.. only:: SOC_WIFI_SUPPORTED or SOC_BLE_SUPPORTED
|
||||
|
||||
其次地，对于 {IDF_TARGET_NAME} 常用的工作场景，如 Wi-Fi/蓝牙工作时，基于上述的几种低功耗模式，ESP-IDF 还提供了进行过针对性优化的细分低功耗模式，将在后续章节介绍。
|
||||
|
||||
本节将首先从纯系统角度介绍，不涉及具体工作场景的低功耗模式。
|
||||
|
||||
DFS
|
||||
------
|
||||
|
||||
Dynamic Frequency Scaling (DFS) 即动态频率切换，是 ESP-IDF 中集成的电源管理机制的基础功能。DFS 可以根据应用程序持有电源锁的情况，调整外围总线 (APB) 频率和 CPU 频率。持有高性能锁就使用高频，空闲状态不持有电源锁时则使用低频来降低功耗，以此来尽可能减少运行应用程序的功耗。
|
||||
|
||||
DFS 的调频机制即根据持有电源锁的最大频率需求来调整频率，同时，`CONFIG_FREERTOS_HZ` 的数值也会对 DFS 调频产生影响。:ref:`CONFIG_FREERTOS_HZ` 值越大，即系统任务调度的频率越高，意味着系统能更及时地根据需求调整频率。有关调频机制的详细信息，请参见 :doc:`电源管理 <../../api-reference/system/power_management>`。
|
||||
|
||||
下图为 DFS 调频机制运行的理想电流情况。
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
持有 CPU 和 APB MAX 锁
|
||||
│
|
||||
│ 释放 CPU MAX 锁
|
||||
▲ │ /
|
||||
电流大小 │ ▼ /
|
||||
│ ──────────┐ 释放 APB MAX 锁
|
||||
│ │ /
|
||||
│ │ /
|
||||
│ └─────────┐
|
||||
│ ▲ │
|
||||
│ │ │
|
||||
│ 第 m 个 tick │ └───────────
|
||||
│ ▲
|
||||
│ │
|
||||
│ 第 n 个 tick │
|
||||
└──────────────────────────────────────►
|
||||
时间
|
||||
理想 DFS 机制调频电流图
|
||||
|
||||
DFS 适用于 CPU 必须处于工作状态但是对低功耗有需求的场景，因此 DFS 通常与其他低功耗模式共同开启，下文会详细介绍。
|
||||
|
||||
.. _Light-sleep 模式:
|
||||
|
||||
Light-sleep 模式
|
||||
-------------------
|
||||
|
||||
Light-sleep 模式是 {IDF_TARGET_NAME} 预设的一种低功耗模式，用户可以通过调用 :cpp:func:`esp_light_sleep_start` 接口主动切换至 Light-sleep 模式，进入睡眠后，芯片将根据当前各外设的工作状态，关闭不必要的电源域和对睡眠期间不使用的模块进行时钟门控。{IDF_TARGET_NAME} 支持多种唤醒源，详见 :doc:`睡眠模式 <../../api-reference/system/sleep_modes>`，当芯片从 Light-sleep 模式唤醒后，CPU 会接着入睡时的上下文继续运行，外设的工作状态也不会被破坏。为充分利用 Light-sleep 模式以降低芯片功耗，更推荐用户使用下述的 Auto Light-sleep 模式。
|
||||
|
||||
Auto Light-sleep 模式是 ESP-IDF :doc:`电源管理 <../../api-reference/system/power_management>` 组件基于 FreeRTOS 的 Tickless IDLE 功能提供的一种低功耗模式。当应用程序释放所有电源锁，FreeRTOS 的所有任务都进入阻塞态或挂起态时，系统会自动获取下一个有就绪事件需要唤醒操作系统的时间点，当判定此时间点距当前超过设定时间（:ref:`CONFIG_FREERTOS_IDLE_TIME_BEFORE_SLEEP`）后，``esp_pm`` 组件会自动配置定时器唤醒源并进入 light sleep 以降低功耗。用户在配置 DFS 时置真 :cpp:type:`esp_pm_config_t` 中的 ``light_sleep_enable`` 字段即可启用该模式，详见下文中的 `DFS 配置`_。
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
┌────────┐
|
||||
│ │
|
||||
│ DFS │
|
||||
│ │
|
||||
└───┬────┘
|
||||
│
|
||||
▼
|
||||
┌──────────┐ 系统空闲 ┌──────────┐ 超过设定时间 ┌──────────┐
|
||||
│ │ ─────────────► │ │ ────────────► │ │
|
||||
│ │ │ │ │ auto │
|
||||
│ active │ │ IDLE │ │ light │
|
||||
│ │ │ │ │ sleep │
|
||||
│ │ ◄───────────── │ │ │ │
|
||||
└──────────┘ 系统非空闲 └──────────┘ └────┬────┘
|
||||
▲ │
|
||||
│ 配置唤醒源唤醒 │
|
||||
└──────────────────────────────────────────────────────────────┘
|
||||
|
||||
Auto Light-sleep 模式工作流程图
|
||||
|
||||
根据 Auto Light-sleep 模式的工作流程可得其理想电流图，关键节点均在图上标出。
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
电流 ▲ 系统 IDLE DFS 降频
|
||||
大小 | │ 系统判断空闲时间超过设定值
|
||||
| ▼ / light sleep
|
||||
| ┌──┐ / ┌──┐
|
||||
| │ └──┐ │ └──┐
|
||||
| | │ | │
|
||||
| │ │ │ │
|
||||
| ───┘ └────────┘ └────
|
||||
| \
|
||||
│ 唤醒源唤醒
|
||||
└───────────────────────────────►
|
||||
时间
|
||||
Auto Light-sleep 模式理想电流图
|
||||
|
||||
.. note::
|
||||
|
||||
- 为更加清晰地展现出 Auto Light-sleep 模式的主要变化，上图中省略了 DFS 降频过程。
|
||||
|
||||
- Auto Light-sleep 模式适用于不需要实时响应外界需求的场景。
|
||||
|
||||
- Auto Light-sleep 功能基于定时器唤醒源实现，所以用户应用程序中不可以再主动配置定时器唤醒源。
|
||||
|
||||
|
||||
.. _Deep-sleep 模式:
|
||||
|
||||
Deep-sleep 模式
|
||||
-----------------
|
||||
|
||||
Deep-sleep 模式是为了追求更好的功耗表现所设计，休眠时仅保留 RTC/LP 相关内存及外设，其余模块全部关闭。与 Light-sleep 模式类似，Deep-sleep 模式同样通过 API 进入，且需要配置唤醒源进行唤醒，用户可以通过调用 :cpp:func:`esp_deep_sleep_start` 接口主动切换至 Deep-sleep 模式。
|
||||
|
||||
Deep-sleep 模式需配置唤醒源，{IDF_TARGET_NAME} 支持多种唤醒源，完整唤醒源列表详见 :doc:`睡眠模式 <../../api-reference/system/sleep_modes>`。这些唤醒源也可以组合在一起，此时任何一个唤醒源都可以触发唤醒。若不配置唤醒源进入 Deep-sleep 模式，芯片将一直处在睡眠状态，直到外部复位。与 Light-sleep 模式不同，Deep-sleep 模式唤醒后会丢失睡眠前的 CPU 运行上下文，因此，唤醒后需要重新运行引导加载程序才可进入用户程序。
|
||||
|
||||
Deep-sleep 模式工作流程如下图所示：
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
┌───────┐ 调用 API ┌───────┐
|
||||
│ ├───────────►│ deep │
|
||||
│active │ │ sleep │
|
||||
│ │ │ │
|
||||
└───────┘ └───┬───┘
|
||||
▲ │
|
||||
└────────────────────┘
|
||||
配置的唤醒源唤醒
|
||||
Deep-sleep 模式工作流程图
|
||||
|
||||
Deep-sleep 模式主要应用场景决定了系统很长时间才会苏醒一次，完成工作后又会继续进入 deep sleep 状态，所以其理想电流图如下。
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
电流 ▲
|
||||
大小 |
|
||||
| 调用 API
|
||||
| │
|
||||
| ▼
|
||||
| ┌────┐
|
||||
| │ │
|
||||
| 唤醒源唤醒 | |
|
||||
| \ | |
|
||||
| \ │ │
|
||||
│ ──────────┘ └────────────────
|
||||
│
|
||||
└──────────────────────────────────────────►
|
||||
时间
|
||||
Deep-sleep 模式理想电流图
|
||||
|
||||
Deep-sleep 模式可以用于低功耗的传感器应用，或是大部分时间都不需要进行数据传输的情况，也就是通常所说的待机模式。
|
||||
|
||||
|
||||
.. only:: ESP_ROM_SUPPORT_DEEP_SLEEP_WAKEUP_STUB
|
||||
|
||||
设备也可以每隔一段时间从 deep sleep 状态醒来测量数据并上传，之后重新进入 deep sleep；也可以将多个数据存储于 RTC 内存，然后在下次唤醒时一次性发送。此特性可借助 deep-sleep-stub 功能实现，详见 :doc:`Deep-sleep 唤醒存根 <../../api-guides/deep-sleep-stub>`。
|
||||
|
||||
如何配置纯系统下低功耗模式
|
||||
------------------------------
|
||||
|
||||
介绍完纯系统下的低功耗模式后，本节将介绍公共配置选项、每种模式的推荐配置以及配置方法。
|
||||
|
||||
公共配置选项
|
||||
------------
|
||||
|
||||
.. note::
|
||||
|
||||
下文为公共配置选项的简单介绍，点击相应链接获取详细内容。
|
||||
|
||||
.. only:: esp32 or esp32s3
|
||||
|
||||
- 单双核工作模式 (:ref:`CONFIG_FREERTOS_UNICORE`)
|
||||
对于多核心芯片，可以选择单核工作模式。
|
||||
|
||||
|
||||
- RTOS Tick rate (Hz) (:ref:`CONFIG_FREERTOS_HZ`)
|
||||
该参数表示系统周期任务调度的频率。
|
||||
|
||||
|
||||
DFS 配置
|
||||
------------
|
||||
|
||||
DFS 有如下可配置选项：
|
||||
|
||||
- ``max_freq_mhz``
|
||||
该参数表示最大 CPU 频率 (MHz)，即 CPU 最高性能工作时候的频率，一般设置为芯片参数的最大值。
|
||||
|
||||
- ``min_freq_mhz``
|
||||
该参数表示最小 CPU 频率 (MHz)，即系统处在空闲状态时 CPU 的工作频率。该字段可设置为晶振 (XTAL) 频率值，或者 XTAL 频率值除以整数。
|
||||
|
||||
- ``light_sleep_enable``
|
||||
使能该选项，系统将在空闲状态下自动进入 light sleep 状态，即 Auto Light-sleep 模式使能，上文已经具体介绍。
|
||||
|
||||
具体配置方法如下：
|
||||
|
||||
1. 使能 :ref:`CONFIG_PM_ENABLE`
|
||||
2. 配置 ``max_freq_mhz`` 和 ``min_freq_mhz``，方式如下：
|
||||
|
||||
::
|
||||
|
||||
esp_pm_config_t pm_config = {
|
||||
.max_freq_mhz = CONFIG_EXAMPLE_MAX_CPU_FREQ_MHZ,
|
||||
.min_freq_mhz = CONFIG_EXAMPLE_MIN_CPU_FREQ_MHZ,
|
||||
.light_sleep_enable = false
|
||||
};
|
||||
ESP_ERROR_CHECK(esp_pm_configure(&pm_config));
|
||||
|
||||
推荐配置
|
||||
++++++++++++++
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 40 20
|
||||
|
||||
* - 配置名称
|
||||
- 设置情况
|
||||
|
||||
* - 启用电源管理组件 (:ref:`CONFIG_PM_ENABLE`)
|
||||
- ON
|
||||
|
||||
* - RTOS Tick rate (Hz) (:ref:`CONFIG_FREERTOS_HZ`)
|
||||
- 1000
|
||||
|
||||
* - ``max_freq_mhz``
|
||||
- 160
|
||||
|
||||
* - ``min_freq_mhz``
|
||||
- 40
|
||||
|
||||
* - ``light_sleep_enable``
|
||||
- false
|
||||
|
||||
.. note::
|
||||
上表中不涉及的配置均是默认。
|
||||
|
||||
|
||||
Light-sleep 模式配置
|
||||
---------------------
|
||||
|
||||
本节介绍 Auto Light-sleep 模式的推荐配置和配置步骤。
|
||||
|
||||
.. note::
|
||||
|
||||
下文为 Auto Light-sleep 模式配置选项的简单介绍，点击相应链接获取详细内容。
|
||||
|
||||
- 进入睡眠模式前最小 IDLE Tick 数 (:ref:`CONFIG_FREERTOS_IDLE_TIME_BEFORE_SLEEP`)
|
||||
- 将 light sleep 相关代码放置在片内 RAM 中 (:ref:`CONFIG_PM_SLP_IRAM_OPT`)
|
||||
- 将 RTOS IDLE 相关代码放置在片内 RAM 中 (:ref:`CONFIG_PM_RTOS_IDLE_OPT`)
|
||||
- RTC 慢速时钟源 (:ref:`CONFIG_RTC_CLK_SRC`)
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 40 40 20
|
||||
|
||||
* - 时钟源
|
||||
- 定时精度
|
||||
- 频偏
|
||||
|
||||
* - RTC_CLK_SRC_INT_RC
|
||||
- 高
|
||||
- 大
|
||||
|
||||
* - RTC_CLK_SRC_EXT_CRYS
|
||||
- 低
|
||||
- 小
|
||||
|
||||
- 芯片休眠时禁用所有 GPIO (:ref:`CONFIG_PM_SLP_DISABLE_GPIO`)
|
||||
|
||||
.. only:: SOC_PM_SUPPORT_MAC_BB_PD
|
||||
|
||||
- 关闭 MAC 和基带 (:ref:`CONFIG_ESP_PHY_MAC_BB_PD`)
|
||||
|
||||
|
||||
.. only:: SOC_PM_SUPPORT_CPU_PD
|
||||
|
||||
- 关闭 CPU (:ref:`CONFIG_PM_POWER_DOWN_CPU_IN_LIGHT_SLEEP`)
|
||||
|
||||
|
||||
.. only:: SOC_PM_SUPPORT_TAGMEM_PD
|
||||
|
||||
- 关闭指令和数据缓存中的标签存储器 (I/D-cache tag memory) (:ref:`CONFIG_PM_RESTORE_CACHE_TAGMEM_AFTER_LIGHT_SLEEP`)
|
||||
|
||||
|
||||
.. only:: SOC_PM_SUPPORT_VDDSDIO_PD
|
||||
|
||||
- 在 light sleep 状态关闭 flash 供电 (:ref:`CONFIG_ESP_SLEEP_POWER_DOWN_FLASH`)
|
||||
|
||||
.. only:: SOC_SPIRAM_SUPPORTED
|
||||
|
||||
由于 flash 和 PSRAM 共用供电管脚，PSRAM 关闭供电将会导致数据丢失，因此，为保证 light sleep 不破坏程序运行状态，启用该选项的前提是系统没有使用 PSRAM。
|
||||
|
||||
|
||||
配置方法：
|
||||
|
||||
1. 配置唤醒源（详见 :doc:`睡眠模式 <../../api-reference/system/sleep_modes>`）
|
||||
2. 使能 :ref:`CONFIG_PM_ENABLE`
|
||||
3. 使能 :ref:`CONFIG_FREERTOS_USE_TICKLESS_IDLE`
|
||||
4. 配置 DFS 参数
|
||||
5. ``light_sleep_enable`` = true，具体如下：
|
||||
|
||||
::
|
||||
|
||||
esp_pm_config_t pm_config = {
|
||||
.max_freq_mhz = CONFIG_EXAMPLE_MAX_CPU_FREQ_MHZ,
|
||||
.min_freq_mhz = CONFIG_EXAMPLE_MIN_CPU_FREQ_MHZ,
|
||||
#if CONFIG_FREERTOS_USE_TICKLESS_IDLE
|
||||
.light_sleep_enable = true
|
||||
#endif
|
||||
};
|
||||
ESP_ERROR_CHECK(esp_pm_configure(&pm_config));
|
||||
|
||||
6. 配置介绍的其余相关参数
|
||||
|
||||
推荐配置
|
||||
+++++++++
|
||||
|
||||
.. only:: esp32c3 or esp32s3
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 30 15
|
||||
|
||||
* - 配置名称
|
||||
- 设置情况
|
||||
|
||||
* - 启用电源管理组件 (:ref:`CONFIG_PM_ENABLE`)
|
||||
- ON
|
||||
|
||||
* - 启用 Tickless IDLE 模式 (:ref:`CONFIG_FREERTOS_USE_TICKLESS_IDLE`)
|
||||
- ON
|
||||
|
||||
* - RTOS Tick rate (Hz) (:ref:`CONFIG_FREERTOS_HZ`)
|
||||
- 1000
|
||||
|
||||
* - 进入睡眠模式前最小 IDLE Tick 数 (:ref:`CONFIG_FREERTOS_IDLE_TIME_BEFORE_SLEEP`)
|
||||
- 3
|
||||
|
||||
* - 将 light sleep 相关代码放置在片内 RAM 中 (:ref:`CONFIG_PM_SLP_IRAM_OPT`)
|
||||
- OFF
|
||||
|
||||
* - 将 RTOS IDLE 相关代码放置在片内 RAM 中 (:ref:`CONFIG_PM_RTOS_IDLE_OPT`)
|
||||
- OFF
|
||||
|
||||
* - RTC 慢速时钟源 (:ref:`CONFIG_RTC_CLK_SRC`)
|
||||
- 内部 150 kHz 振荡器
|
||||
|
||||
* - 芯片休眠时禁用所有 GPIO (:ref:`CONFIG_PM_SLP_DISABLE_GPIO`)
|
||||
- ON
|
||||
|
||||
* - 关闭 MAC 和基带 (:ref:`CONFIG_ESP_PHY_MAC_BB_PD`)
|
||||
- ON
|
||||
|
||||
* - 关闭 CPU (:ref:`CONFIG_PM_POWER_DOWN_CPU_IN_LIGHT_SLEEP`)
|
||||
- ON
|
||||
|
||||
.. only:: SOC_PM_SUPPORT_TAGMEM_PD
|
||||
|
||||
* - 关闭指令和数据缓存中的标签存储器 (I/D-cache tag memory) (:ref:`CONFIG_PM_RESTORE_CACHE_TAGMEM_AFTER_LIGHT_SLEEP`)
|
||||
- ON
|
||||
|
||||
|
||||
* - 在 light sleep 状态关闭 flash 供电 (:ref:`CONFIG_ESP_SLEEP_POWER_DOWN_FLASH`)
|
||||
- OFF
|
||||
|
||||
* - ``max_freq_mhz``
|
||||
- 160
|
||||
|
||||
* - ``min_freq_mhz``
|
||||
- 40
|
||||
|
||||
* - ``light_sleep_enable``
|
||||
- true
|
||||
|
||||
.. note::
|
||||
上表中不涉及的配置均是默认。
|
||||
|
||||
.. only:: esp32 or esp32s2
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 30 15
|
||||
|
||||
* - 配置名称
|
||||
- 设置情况
|
||||
|
||||
* - 启用电源管理组件 (:ref:`CONFIG_PM_ENABLE`)
|
||||
- ON
|
||||
|
||||
* - 启用 Tickless IDLE 模式 (:ref:`CONFIG_FREERTOS_USE_TICKLESS_IDLE`)
|
||||
- ON
|
||||
|
||||
* - RTOS Tick rate (Hz) (:ref:`CONFIG_FREERTOS_HZ`)
|
||||
- 1000
|
||||
|
||||
* - 进入睡眠模式前最小 IDLE Tick 数 (:ref:`CONFIG_FREERTOS_IDLE_TIME_BEFORE_SLEEP`)
|
||||
- 3
|
||||
|
||||
* - 将 light sleep 相关代码放置在片内 RAM 中 (:ref:`CONFIG_PM_SLP_IRAM_OPT`)
|
||||
- OFF
|
||||
|
||||
* - 将 RTOS IDLE 相关代码放置在片内 RAM 中 (:ref:`CONFIG_PM_RTOS_IDLE_OPT`)
|
||||
- OFF
|
||||
|
||||
* - RTC 慢速时钟源 (:ref:`CONFIG_RTC_CLK_SRC`)
|
||||
- 内部 150 kHz 振荡器
|
||||
|
||||
* - 芯片休眠时禁用所有 GPIO (:ref:`CONFIG_PM_SLP_DISABLE_GPIO`)
|
||||
- ON
|
||||
|
||||
* - ``max_freq_mhz``
|
||||
- 160
|
||||
|
||||
* - ``min_freq_mhz``
|
||||
- 40
|
||||
|
||||
* - ``light_sleep_enable``
|
||||
- true
|
||||
|
||||
.. note::
|
||||
上表中不涉及的配置均是默认。
|
||||
|
||||
.. only:: esp32c2
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 30 15
|
||||
|
||||
* - 配置名称
|
||||
- 设置情况
|
||||
|
||||
* - 启用电源管理组件 (:ref:`CONFIG_PM_ENABLE`)
|
||||
- ON
|
||||
|
||||
* - 启用 Tickless IDLE 模式 (:ref:`CONFIG_FREERTOS_USE_TICKLESS_IDLE`)
|
||||
- ON
|
||||
|
||||
* - RTOS Tick rate (Hz) (:ref:`CONFIG_FREERTOS_HZ`)
|
||||
- 1000
|
||||
|
||||
* - 进入睡眠模式前最小 IDLE Tick 数 (:ref:`CONFIG_FREERTOS_IDLE_TIME_BEFORE_SLEEP`)
|
||||
- 3
|
||||
|
||||
* - 将 light sleep 相关代码放置在片内 RAM 中 (:ref:`CONFIG_PM_SLP_IRAM_OPT`)
|
||||
- OFF
|
||||
|
||||
* - 将 RTOS IDLE 相关代码放置在片内 RAM 中 (:ref:`CONFIG_PM_RTOS_IDLE_OPT`)
|
||||
- OFF
|
||||
|
||||
* - RTC 慢速时钟源 (:ref:`CONFIG_RTC_CLK_SRC`)
|
||||
- 内部 150 kHz 振荡器
|
||||
|
||||
* - 芯片休眠时禁用所有 GPIO (:ref:`CONFIG_PM_SLP_DISABLE_GPIO`)
|
||||
- ON
|
||||
|
||||
* - 在 light sleep 状态关闭 flash 供电 (:ref:`CONFIG_ESP_SLEEP_POWER_DOWN_FLASH`)
|
||||
- OFF
|
||||
|
||||
* - ``max_freq_mhz``
|
||||
- 120
|
||||
|
||||
* - ``min_freq_mhz``
|
||||
- 40
|
||||
|
||||
* - ``light_sleep_enable``
|
||||
- true
|
||||
|
||||
.. note::
|
||||
上表中不涉及的配置均是默认。
|
||||
|
||||
Deep-sleep 模式配置
|
||||
---------------------
|
||||
|
||||
对 Deep-sleep 模式来说，除了唤醒源相关配置，其余配置意义已经不大。
|
||||
|
||||
配置方法：
|
||||
|
||||
1. 配置唤醒源（详见 :doc:`睡眠模式 <../../api-reference/system/sleep_modes>`）
|
||||
2. 调用 API，具体如下
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
/* Enter deep sleep */
|
||||
esp_deep_sleep_start();
|
||||
|
||||
用户可以通过下列配置选项，让一些特定模块在休眠时保持开启状态：
|
||||
|
||||
- 打开外部 40 MHz 晶振 (XTAL)
|
||||
在一些特殊应用中，部分模块对休眠时的时钟精度及稳定度有很高要求（例如蓝牙模块）。这种情况下，可以考虑在休眠过程中打开 外部 40 MHz 晶振。
|
||||
打开和关闭代码如下::
|
||||
|
||||
ESP_ERROR_CHECK(esp_sleep_pd_config(ESP_PD_DOMAIN_XTAL, ESP_PD_OPTION_ON));
|
||||
ESP_ERROR_CHECK(esp_sleep_pd_config(ESP_PD_DOMAIN_XTAL, ESP_PD_OPTION_OFF));
|
||||
|
||||
- 打开内部 8 MHz 振荡器 (OSC)
|
||||
在一些特殊应用中，部分模块（例如 LEDC 模块）将 内部 8 MHz 振荡器作为时钟源，并且希望在 light sleep 状态也可以正常使用。这种情况下，可以考虑在休眠过程中打开内部 8 MHz 振荡器。
|
||||
打开和关闭代码如下::
|
||||
|
||||
ESP_ERROR_CHECK(esp_sleep_pd_config(ESP_PD_DOMAIN_RTC8M, ESP_PD_OPTION_ON));
|
||||
ESP_ERROR_CHECK(esp_sleep_pd_config(ESP_PD_DOMAIN_RTC8M, ESP_PD_OPTION_OFF));
|
||||
417
docs/zh_CN/api-guides/low-power-mode/low-power-mode-wifi.rst
Normal file
417
docs/zh_CN/api-guides/low-power-mode/low-power-mode-wifi.rst
Normal file
@ -0,0 +1,417 @@
|
||||
Wi-Fi 场景下低功耗模式介绍
|
||||
==========================
|
||||
|
||||
:link_to_translation:`en:[English]`
|
||||
|
||||
本节将结合纯系统下的功耗模式来介绍 Wi-Fi 场景下的低功耗模式。因为 Wi-Fi 场景的复杂性，本节会首先介绍 Wi-Fi 省电的基本原理，然后再介绍具体的低功耗模式。本节主要针对 station 模式。
|
||||
|
||||
Wi-Fi 场景如何选择低功耗模式
|
||||
--------------------------------------
|
||||
|
||||
在介绍具体内容前先给出 Wi-Fi 场景下低功耗模式总结表，以方便用户根据需求快速选择想要了解的内容，选择合适的低功耗模式。
|
||||
|
||||
.. todo - add sleep-current/esp32c5_summary.inc
|
||||
|
||||
.. only:: not esp32c5
|
||||
|
||||
.. include:: ../sleep-current/{IDF_TARGET_PATH_NAME}_summary.inc
|
||||
|
||||
.. note::
|
||||
|
||||
上表中所有电流均为平均电流，表中术语在下文均有介绍，用户可根据需求进行查看。
|
||||
|
||||
.. _Wi-Fi 省电的基本原理:
|
||||
|
||||
Wi-Fi 省电的基本原理
|
||||
---------------------
|
||||
|
||||
首先，在 station 的工作过程中，为在接收发送过程中避免冲突，需要长时间监听信道，能耗较大的 RF 模块会一直处于工作中，浪费电量。为此，Wi-Fi 协议引入省电模式。
|
||||
|
||||
省电模式的基本原理是通过减少不必要的监听时间来降低耗能。AP 会缓存进入省电模式的 station 的包，同时周期发送包含 TIM 信息的 beacon 帧，TIM 会指示 AP 缓存的单播包。TIM 中，DTIM 较为特殊，其会缓存广播包，并以 n 个（由 AP 决定）TIM 为周期发送。对 station 来说，TIM 非必听，而 DTIM 为必听。因此，station 可以选择只在每一个 DTIM 帧前醒来打开 Wi-Fi 相关模块（RF 模块），而不必时刻处于监听状态，这样就能有效降低功耗。
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
DTIM DTIM
|
||||
TIM │ │
|
||||
│ │ │ │ │ │ │ │ │ │ │
|
||||
│ │ │ │ │ │ │ │ │ │ │
|
||||
AP ───┴────┴────┴────┴────┴────┴────┴────┴────┴────┴────┴────
|
||||
|
||||
|
||||
┌────┐ ┌────┐
|
||||
│ │ │ │
|
||||
│ │ │ │
|
||||
│ │ │ │
|
||||
Sta ────────────────┴────┴─────────────┴────┴─────────────────
|
||||
|
||||
DTIM4 省电模式示意图
|
||||
|
||||
其次，station 从打开到再次关闭 Wi-Fi 相关模块的时间也会影响功耗。除必要的数据传输处理时间外，主要有四项配置会影响时间长短：
|
||||
|
||||
- 时钟准确性导致的 time offset，主要原因是时钟或多或少都会与理想的时间存在偏移，同时偏移的正负不定。
|
||||
- 处理 beacon 漏听后的时间，如漏听后持续监听时间、允许最多丢失 beacon 数目等，这段时间存不存在以及存在多久都不定，但是可以配置范围。
|
||||
- 为了确保能够接受突发数据包而添加的 active 时间，可由配置决定。
|
||||
- ILDE 时间是具体某些功耗模式进入条件要求。因此在满足通信需求的情况下，降低工作时间可以改善功耗表现。
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
┌────────────┬────────────┬────────────┬────────────┬────────────┐
|
||||
│ │ │ │ │ │
|
||||
│time offset │ 必要处理时间 │ beacon │ active │ IDLE │
|
||||
│ │ │ 漏听处理时间 │ 时间 │ 时间 │
|
||||
│ │ │ │ │ │
|
||||
└────────────┴────────────┴────────────┴────────────┴────────────┘
|
||||
芯片工作时间组成图
|
||||
|
||||
此外，在 station 没有处于 Wi-Fi 接收或发送状态时，影响功耗的因素变成了芯片的其他模块。不同的功耗模式会配置不同的时钟源，或者动态调整一些模块的工作频率如 CPU，同时还会关闭不同数量的功能模块，这将有效降低芯片的功耗。用户可根据需求自己选择合适的配置。
|
||||
|
||||
如果以时间为横轴，电流大小为纵轴建立坐标轴，那么处在低功耗模式下芯片的理想工作电流图可以简化成下图：
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
▲
|
||||
电流 |
|
||||
大小 |
|
||||
| interval period
|
||||
| │ ◄──────────► │ │ ◄─► │
|
||||
| ┌─────┐ ┌─────┐ ┌─────┐
|
||||
| │ │ │ │ │ │
|
||||
| | | | | | | base current
|
||||
| | | | | | | |
|
||||
| | | | | | | ▼
|
||||
| ───┘ └────────┘ └────────┘ └──────
|
||||
|
|
||||
└───────────────────────────────────────────────►
|
||||
时间
|
||||
理想情况下 Wi-Fi 场景低功耗模式电流图
|
||||
|
||||
其中 station 要进行 Wi-Fi 通信时，Wi-Fi 相关模块 (PHY) 开启，电流会显著上升，在工作完成前，电流会一直维持在一个较高的水平。工作完成后，芯片会关闭 Wi-Fi 相关模块，这时电流又会降低到一个较低水平。
|
||||
|
||||
可以看出影响功耗表现的主要有三点：interval、period 和 base current。
|
||||
|
||||
- **interval** 是 station Wi-Fi 相关模块工作的间隔，既可以由低功耗模式自定义，也可根据 Wi-Fi 协议省电机制（详细内容请见 :ref:`Wi-Fi 省电的基本原理`），由 DTIM 周期决定。可以看出在同等情下，interval 越大，功耗表现会更好，但是响应会更慢，影响通信的及时性。
|
||||
|
||||
- **period** 可以看作每次 station Wi-Fi 工作的时间，这段时间的长度也会影响功耗的表现。period 不是一个固定的时长（详细内容请见 :ref:`Wi-Fi 省电的基本原理`），在保证 Wi-Fi 通信正常的情况下，period 持续时间越短，功耗表现越好。但是减少 period 时间，必然会影响通信的可靠性。
|
||||
|
||||
- **base current** 是 Wi-Fi 相关模块不工作时芯片的电流，影响其大小的因素很多，不同的功耗模式下休眠策略不同。所以，在满足功能的情况下，优化配置降低该电流大小可以提高功耗表现，但同时关闭其余模块会影响相关功能和芯片的唤醒时间。
|
||||
|
||||
知道了影响功耗的三点因素之后，要想降低功耗应从这三点入手，接下来介绍两种低功耗模式，Modem-sleep 模式、Auto Light-sleep 模式。两种模式主要区别就是对三点因素的优化不同。
|
||||
|
||||
|
||||
Modem-sleep 模式
|
||||
------------------
|
||||
|
||||
Modem-sleep 模式主要工作原理基于 DTIM 机制，周期性的醒来处理 Wi-Fi 相关工作，又在周期间隔之间进入休眠，关闭 PHY（RF 模块）来降低功耗。同时通过 DTIM 机制，station 可以与 AP 保持 Wi-Fi 连接，数据传输。
|
||||
|
||||
Modem-sleep 模式会在 Wi-Fi 任务结束后自动进入休眠无需调用 API，休眠时仅会关闭 Wi-Fi 相关模块 (PHY)，其余模块均处在正常上电状态。
|
||||
|
||||
Modem-sleep 模式默认会根据 DTIM 周期或 listen interval（于 :ref:`Modem-sleep 模式配置` 中介绍）醒来，相当于系统自动设置了一个 Wi-Fi 唤醒源，因此用户无需再配置唤醒源，同时系统主动发包时也可以唤醒。
|
||||
|
||||
Modem-sleep 模式是一个开关型的模式，调用 API 开启后一直自动运行，其工作流程十分简单，具体如下图。
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
┌───────────┐ Wi-Fi 任务结束 ┌───────────┐
|
||||
│ ├────────────────────────►│ modem │
|
||||
│ active │ │ sleep │
|
||||
│ │◄────────────────────────┤ │
|
||||
└───────────┘ DTIM 周期到来 └───────────┘
|
||||
/ 主动发包
|
||||
|
||||
Modem-sleep 模式工作流程图
|
||||
|
||||
根据上文的基本电流图，结合 Modem-sleep 模式的工作原理，以 Min Modem 模式（于 :ref:`Modem-sleep 模式配置` 中介绍）为例可得理想情况下电流变化图。
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
电流 ▲
|
||||
大小 |
|
||||
| DTIM 周期
|
||||
| │ ◄──────────► │
|
||||
| ┌─────┐ ┌─────┐ ┌─────┐
|
||||
| │ │ │ │ │ │
|
||||
| DTIM | | | | | |
|
||||
| 到来前 | | | | | | Wi-Fi 任务结束
|
||||
| \ | | | | | | /
|
||||
| \ │ │ │ │ │ │/
|
||||
| ────────┘ └────────┘ └────────┘ └──────
|
||||
|
|
||||
└─────────────────────────────────────────────────────►
|
||||
时间
|
||||
Min Modem-sleep 模式理想电流图
|
||||
|
||||
Modem-sleep 模式一般用于 CPU 持续处于工作状态并需要保持 Wi-Fi 连接的应用场景，例如，使用 {IDF_TARGET_NAME} 本地语音唤醒功能，CPU 需要持续采集和处理音频数据。
|
||||
|
||||
DFS + Modem-sleep 模式
|
||||
-------------------------
|
||||
|
||||
Modem-sleep 模式休眠状态中 CPU 仍处在工作状态，而 DFS 机制主要作用于 CPU 和 APB 工作频率来降低功耗，因此 DFS + Modem sleep 模式可以进一步优化功耗表现，又因为 Wi-Fi 任务会申请 :cpp:enumerator:`ESP_PM_CPU_FREQ_MAX` 电源锁来保证 Wi-Fi 任务快速运行，所以 DFS + Modem-sleep 模式产生调频只会发生在 base current 阶段，即 Wi-Fi 任务结束后。
|
||||
|
||||
在 Wi-Fi 场景下，为了让用户抓住主要的变化，DFS 可以进行一定的状态简化。具体来说，虽然 DFS 主要根据 CPU 和 APB 两把锁的最高需求来调频，但是 Wi-Fi 场景都需要 CPU 的频率最大化来工作，同时 Wi-Fi 任务结束后，也可以理想化的认为，没有其余的工作要完成，这样就可以简单认为经过一段时间会释放两把锁进入空闲状态（IDLE 状态），也同时忽略这段时间锁的变化导致的电流变化，简化状态。
|
||||
|
||||
在 Wi-Fi 场景下，DFS 最终简化为如下流程：
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
┌────────┐
|
||||
│ │
|
||||
│ DFS │
|
||||
│ │
|
||||
└───┬────┘
|
||||
│
|
||||
▼
|
||||
┌──────────┐ 系统空闲 ┌──────────┐
|
||||
│ │ ─────────────► │ │
|
||||
│ │ │ │
|
||||
│ active │ │ IDLE │
|
||||
│ │ │ │
|
||||
│ │ ◄───────────── │ │
|
||||
└──────────┘ 系统非空闲 └──────────┘
|
||||
|
||||
Wi-Fi 场景 DFS 简化流程图
|
||||
|
||||
在 Wi-Fi 工作的 active 状态与系统空闲的 IDLE 状态转换，Wi-Fi 任务结束后，系统经过一段时间释放了所有锁进入 IDLE 状态，此时 DFS 机制降低频率到设定最低值，忽略了转换状态期间的调频动作，方便理解。
|
||||
|
||||
简化过后的 DFS + Modem sleep 模式理想状态下的电流大小如下图所示：
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
电流 ▲ Wi-Fi 任务结束
|
||||
大小 | / modem sleep
|
||||
| /
|
||||
| ┌─────┐ ┌─────┐
|
||||
| │ │ │ │
|
||||
| | | | | 锁释放完
|
||||
| | | | | DFS 降频
|
||||
| | | | | IDLE
|
||||
| | | | | /
|
||||
| | | | | /
|
||||
| | │ | │ /
|
||||
| │ └─┐ │ └─┐
|
||||
| ────────┘ └───────────────┘ └─────────
|
||||
|
|
||||
└─────────────────────────────────────────────────────►
|
||||
时间
|
||||
DFS + Modem sleep 模式理想电流图
|
||||
|
||||
Auto Light-sleep 模式 + Wi-Fi 场景
|
||||
------------------------------------
|
||||
|
||||
Auto Light-sleep 模式在 Wi-Fi 场景下是 ESP-IDF 电源管理机制、DTIM 机制和 Light-sleep 模式的结合。开启电源管理是其前置条件，auto 体现在系统进入 IDLE 状态超过设定值后自动进入 light sleep。同时 Auto Light-sleep 模式同样遵循 DTIM 机制，会自动苏醒，可以与 AP 保持 Wi-Fi 连接。
|
||||
|
||||
Auto Light-sleep 模式在 Wi-Fi 场景下休眠机制与纯系统下一样，仍然依赖于电源管理机制，进入休眠的条件为系统处于 IDLE 状态的时间超过设定时间，并且系统会提前判断空闲时间是否满足条件，若满足直接休眠。该过程为自动进行。休眠时会自动关闭 RF、8 MHz 振荡器、40 MHz 高速晶振、PLL，门控数字内核时钟，暂停 CPU 工作。
|
||||
|
||||
Auto Light-sleep 模式在 Wi-Fi 场景下遵循 DTIM 机制，自动在 DTIM 帧到来前苏醒，相当于系统自动设置了一个 Wi-Fi 唤醒源，因此用户无需再配置唤醒源。同时系统主动发包时也可以唤醒。
|
||||
|
||||
Auto Light-sleep 模式在 Wi-Fi 场景下工作流程较为复杂，但全程都是自动进行，具体如下图所示：
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
┌────────┐
|
||||
│ │
|
||||
│ DFS │
|
||||
│ │
|
||||
└───┬────┘
|
||||
│
|
||||
▼
|
||||
┌──────────┐ 系统空闲 ┌──────────┐ 超过设定时间 ┌──────────┐
|
||||
│ │ ─────────────► │ │ ────────────► │ │
|
||||
│ │ │ │ │ auto │
|
||||
│ active │ │ IDLE │ │ light │
|
||||
│ │ │ │ │ sleep │
|
||||
│ │ ◄───────────── │ │ │ │
|
||||
└──────────┘ 系统非空闲 └──────────┘ └────┬────┘
|
||||
▲ │
|
||||
│ DTIM 周期到来 / 主动发包 │
|
||||
└──────────────────────────────────────────────────────────────┘
|
||||
|
||||
Auto Light-sleep 模式工作流程图
|
||||
|
||||
Auto Light-sleep 模式在 Wi-Fi 场景下经常与 Modem-sleep 模式同时开启，这里给出 Modem + Auto Light-sleep 模式的理想电流图，关键节点均在图上标出。
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
DTIM 周期
|
||||
电流 ▲ │ ◄───────────────────► │
|
||||
大小 | ┌─────┐ ┌─────┐
|
||||
| │ │ \ │ │
|
||||
| | | \ | |
|
||||
| | | Wi-Fi 任务结束 | |
|
||||
| | | modem sleep | |
|
||||
| | | | |
|
||||
| | | | | 系统判断空闲
|
||||
| DTIM | | 系统 IDLE | | 时间超过设定值
|
||||
| 到来前 | │ DFS 降频 | │ light sleep
|
||||
| \ | └─┐ / | └─┐ /
|
||||
| \ │ └─┐ / │ └─┐ /
|
||||
| ────────┘ └─────────────┘ └─────────
|
||||
|
|
||||
└─────────────────────────────────────────────────────►
|
||||
时间
|
||||
Modem + Auto Light-sleep 模式理想电流图
|
||||
|
||||
Auto Light-sleep 模式在 Wi-Fi 场景下可用于需要保持 Wi-Fi 连接，可以实时响应 AP 发来数据的场景。并且在未接收到命令时，CPU 可以处于空闲状态。比如 Wi-Fi 开关的应用，大部分时间 CPU 都是空闲的，直到收到控制命令，CPU 才需要进行 GPIO 的操作。
|
||||
|
||||
|
||||
Deep-sleep 模式 + Wi-Fi 场景
|
||||
------------------------------
|
||||
|
||||
Deep-sleep 模式在 Wi-Fi 场景下与纯系统下基本相同，详情可以参考 :ref:`Deep-sleep 模式`，这里不再介绍。
|
||||
|
||||
|
||||
如何配置 Wi-Fi 场景下低功耗模式
|
||||
----------------------------------------
|
||||
|
||||
介绍完 Wi-Fi 场景下低功耗模式后，本节将介绍公共配置选项、每种模式独有的配置选项，以及相应低功耗模式 API 的使用说明，同时给出相应模式推荐的配置（包含纯系统下的低功耗推荐配置）以及该配置的具体表现。
|
||||
|
||||
.. note::
|
||||
|
||||
下文为配置选项的简单介绍，点击相应链接获取详细内容。
|
||||
|
||||
公共配置选项
|
||||
++++++++++++++
|
||||
|
||||
- 功耗类：
|
||||
|
||||
- Max Wi-Fi TX power (dBm) (:ref:`CONFIG_ESP_PHY_MAX_WIFI_TX_POWER`)
|
||||
|
||||
- 速度优化类：
|
||||
|
||||
- Wi-Fi IRAM 速度优化 (:ref:`CONFIG_ESP_WIFI_IRAM_OPT`)
|
||||
- Wi-Fi RX IRAM 速度优化 (:ref:`CONFIG_ESP_WIFI_RX_IRAM_OPT`)
|
||||
- Wi-Fi Sleep IRAM 速度优化 (:ref:`CONFIG_ESP_WIFI_SLP_IRAM_OPT`)
|
||||
|
||||
|
||||
- Wi-Fi 协议类：
|
||||
|
||||
- Minimum active time (:ref:`CONFIG_ESP_WIFI_SLP_DEFAULT_MIN_ACTIVE_TIME`)
|
||||
|
||||
- Maximum keep alive time (:ref:`CONFIG_ESP_WIFI_SLP_DEFAULT_MAX_ACTIVE_TIME`)
|
||||
|
||||
- 周期性发送无条件 ARP (:ref:`CONFIG_LWIP_ESP_GRATUITOUS_ARP`)
|
||||
|
||||
- 丢失 beacon 时睡眠优化 (:ref:`CONFIG_ESP_WIFI_SLP_BEACON_LOST_OPT`)
|
||||
|
||||
|
||||
.. _Modem-sleep 模式配置:
|
||||
|
||||
Modem-sleep 模式配置
|
||||
+++++++++++++++++++++++
|
||||
|
||||
- 可配置选项
|
||||
|
||||
- Min Modem
|
||||
该参数表示 station 按照 DTIM 周期工作，在每个 DTIM 前醒来接收 beacon，这样不会漏掉广播信息，但是 DTIM 周期由 AP 决定，如果 DTIM 周期较短，省电效果会降低。
|
||||
|
||||
- Max Modem
|
||||
该参数表示 station 会自定义一个 listen interval，并以 listen interval 为周期醒来接受 beacon。这样在 listen interval 较大时会省电，但是容易漏听 DTIM，错过广播数据。
|
||||
|
||||
|
||||
- 配置方法
|
||||
|
||||
- 调用 API，选择模式参数
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
typedef enum {
|
||||
WIFI_PS_NONE,
|
||||
WIFI_PS_MIN_MODEM,
|
||||
WIFI_PS_MAX_MODEM,
|
||||
} wifi_ps_type_t;
|
||||
esp_err_t esp_wifi_set_ps(wifi_ps_type_t type);
|
||||
|
||||
若选择 WIFI_PS_MAX_MODEM，还需配置 listen interval，示例如下::
|
||||
|
||||
#define LISTEN_INTERVAL 3
|
||||
wifi_config_t wifi_config = {
|
||||
.sta = {
|
||||
.ssid = "SSID",
|
||||
.password = "Password",
|
||||
.listen_interval = LISTEN_INTERVAL,
|
||||
},
|
||||
};
|
||||
ESP_ERROR_CHECK(esp_wifi_set_mode(WIFI_MODE_STA));
|
||||
ESP_ERROR_CHECK(esp_wifi_set_config(ESP_IF_WIFI_STA, &wifi_config));
|
||||
ESP_ERROR_CHECK(esp_wifi_start());
|
||||
|
||||
- 推荐配置
|
||||
|
||||
这里给出的推荐配置是 Min Modem-sleep 模式 + DFS 开启的配置
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 20 15
|
||||
|
||||
* - 配置名称
|
||||
- 设置情况
|
||||
|
||||
* - WIFI_PS_MIN_MODEM
|
||||
- ON
|
||||
|
||||
* - CONFIG_PM_ENABLE
|
||||
- ON
|
||||
|
||||
* - RTOS Tick rate (Hz)
|
||||
- 1000
|
||||
|
||||
* - ``max_freq_mhz``
|
||||
- 160
|
||||
|
||||
* - ``min_freq_mhz``
|
||||
- 40
|
||||
|
||||
* - ``light_sleep_enable``
|
||||
- false
|
||||
|
||||
- 配置表现
|
||||
|
||||
.. todo - add sleep-current/esp32c5_modem_sleep.inc
|
||||
|
||||
.. only:: not esp32c5
|
||||
|
||||
.. include:: ../sleep-current/{IDF_TARGET_PATH_NAME}_modem_sleep.inc
|
||||
|
||||
|
||||
Auto Light-sleep 模式 + Wi-Fi 场景配置
|
||||
+++++++++++++++++++++++++++++++++++++++++
|
||||
|
||||
Auto Light-sleep 在 Wi-Fi 场景下的配置比纯系统下少了唤醒源的配置要求，其余几乎与纯系统下配置一致，因此可配置选项、配置步骤、推荐配置的详细介绍可以参考上文 :ref:`Deep-sleep 模式`。同时 Wi-Fi 相关配置保持默认。
|
||||
|
||||
- 配置表现
|
||||
|
||||
该配置表现为 Auto Light-sleep 模式纯系统推荐配置 + 默认的 Wi-Fi 相关配置在 Wi-Fi 场景的表现。
|
||||
|
||||
.. todo - add sleep-current/esp32c5_light_sleep.inc
|
||||
|
||||
.. only:: not esp32c5
|
||||
|
||||
.. include:: ../sleep-current/{IDF_TARGET_PATH_NAME}_light_sleep.inc
|
||||
|
||||
Deep-sleep 模式 + Wi-Fi 场景配置
|
||||
+++++++++++++++++++++++++++++++++++
|
||||
|
||||
Deep-sleep 模式在 Wi-Fi 场景下的配置与纯系统下配置基本一致，因此可配置选项、配置步骤、推荐配置的详细介绍可以参考上文 :ref:`Deep-sleep 模式`。同时 Wi-Fi 相关配置保持默认。
|
||||
|
||||
- 配置表现
|
||||
|
||||
该配置表现为 Deep-sleep 模式纯系统推荐配置 + 默认的 Wi-Fi 相关配置在 Wi-Fi 场景的表现。
|
||||
|
||||
.. only:: esp32
|
||||
|
||||
平均电流约 5.0 μA
|
||||
|
||||
.. only:: esp32s2
|
||||
|
||||
平均电流约 5.0 μA
|
||||
|
||||
.. only:: esp32s3
|
||||
|
||||
平均电流约 6.9 μA
|
||||
|
||||
.. only:: esp32c3
|
||||
|
||||
平均电流约 4.8 μA
|
||||
|
||||
.. only:: esp32c2
|
||||
|
||||
平均电流约 4.9 μA
|
||||
@ -2,11 +2,11 @@
|
||||
:header-rows: 1
|
||||
:widths: 20 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
* - CPU 频率
|
||||
- DTIM
|
||||
- Average current(mA)
|
||||
- Max current(mA)
|
||||
- Min current(mA)
|
||||
- 平均电流 (mA)
|
||||
- 最大电流 (mA)
|
||||
- 最小电流 (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- 1
|
||||
|
||||
@ -2,12 +2,12 @@
|
||||
:header-rows: 1
|
||||
:widths: 20 10 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
* - CPU 频率
|
||||
- DFS
|
||||
- DTIM
|
||||
- Average current(mA)
|
||||
- Max current(mA)
|
||||
- Min current(mA)
|
||||
- 平均电流 (mA)
|
||||
- 最大电流 (mA)
|
||||
- 最小电流 (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
|
||||
@ -3,10 +3,10 @@
|
||||
:widths: 20 20 30 20 20
|
||||
|
||||
* - 项目
|
||||
- Modem Sleep
|
||||
- Modem Sleep+DFS
|
||||
- auto light Sleep
|
||||
- Deep Sleep
|
||||
- Modem-sleep
|
||||
- Modem-sleep+DFS
|
||||
- Auto Light-sleep
|
||||
- Deep-sleep
|
||||
|
||||
* - 休眠
|
||||
- 自动
|
||||
|
||||
@ -2,11 +2,11 @@
|
||||
:header-rows: 1
|
||||
:widths: 20 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
* - CPU 频率
|
||||
- DTIM
|
||||
- Average current(mA)
|
||||
- Max current(mA)
|
||||
- Min current(mA)
|
||||
- 平均电流 (mA)
|
||||
- 最大电流 (mA)
|
||||
- 最小电流 (mA)
|
||||
|
||||
* - 120 MHz
|
||||
- 1
|
||||
|
||||
@ -2,12 +2,12 @@
|
||||
:header-rows: 1
|
||||
:widths: 20 10 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
* - CPU 频率
|
||||
- DFS
|
||||
- DTIM
|
||||
- Average current(mA)
|
||||
- Max current(mA)
|
||||
- Min current(mA)
|
||||
- 平均电流 (mA)
|
||||
- 最大电流 (mA)
|
||||
- 最小电流 (mA)
|
||||
|
||||
* - 120 MHz
|
||||
- ON
|
||||
|
||||
@ -3,10 +3,10 @@
|
||||
:widths: 20 20 30 20 20
|
||||
|
||||
* - 项目
|
||||
- Modem Sleep
|
||||
- Modem Sleep+DFS
|
||||
- auto light Sleep
|
||||
- Deep Sleep
|
||||
- Modem-sleep
|
||||
- Modem-sleep+DFS
|
||||
- Auto Light-sleep
|
||||
- Deep-sleep
|
||||
|
||||
* - 休眠
|
||||
- 自动
|
||||
|
||||
@ -2,11 +2,11 @@
|
||||
:header-rows: 1
|
||||
:widths: 20 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
* - CPU 频率
|
||||
- DTIM
|
||||
- Average current(mA)
|
||||
- Max current(mA)
|
||||
- Min current(mA)
|
||||
- 平均电流 (mA)
|
||||
- 最大电流 (mA)
|
||||
- 最小电流 (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- 1
|
||||
|
||||
@ -2,12 +2,12 @@
|
||||
:header-rows: 1
|
||||
:widths: 20 10 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
* - CPU 频率
|
||||
- DFS
|
||||
- DTIM
|
||||
- Average current(mA)
|
||||
- Max current(mA)
|
||||
- Min current(mA)
|
||||
- 平均电流 (mA)
|
||||
- 最大电流 (mA)
|
||||
- 最小电流 (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
|
||||
@ -3,10 +3,10 @@
|
||||
:widths: 20 20 30 20 20
|
||||
|
||||
* - 项目
|
||||
- Modem Sleep
|
||||
- Modem Sleep+DFS
|
||||
- auto light Sleep
|
||||
- Deep Sleep
|
||||
- Modem-sleep
|
||||
- Modem-sleep+DFS
|
||||
- Auto Ligh-sleep
|
||||
- Deep-sleep
|
||||
|
||||
* - 休眠
|
||||
- 自动
|
||||
|
||||
@ -2,11 +2,11 @@
|
||||
:header-rows: 1
|
||||
:widths: 20 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
* - CPU 频率
|
||||
- DTIM
|
||||
- Average current(mA)
|
||||
- Max current(mA)
|
||||
- Min current(mA)
|
||||
- 平均电流 (mA)
|
||||
- 最大电流 (mA)
|
||||
- 最小电流 (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- 1
|
||||
|
||||
@ -2,12 +2,12 @@
|
||||
:header-rows: 1
|
||||
:widths: 20 10 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
* - CPU 频率
|
||||
- DFS
|
||||
- DTIM
|
||||
- Average current(mA)
|
||||
- Max current(mA)
|
||||
- Min current(mA)
|
||||
- 平均电流 (mA)
|
||||
- 最大电流 (mA)
|
||||
- 最小电流 (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
|
||||
@ -3,10 +3,10 @@
|
||||
:widths: 20 20 30 20 20
|
||||
|
||||
* - 项目
|
||||
- Modem Sleep
|
||||
- Modem Sleep+DFS
|
||||
- auto light Sleep
|
||||
- Deep Sleep
|
||||
- Modem-sleep
|
||||
- Modem-sleep+DFS
|
||||
- Auto Light-sleep
|
||||
- Deep-sleep
|
||||
|
||||
* - 休眠
|
||||
- 自动
|
||||
|
||||
@ -2,11 +2,11 @@
|
||||
:header-rows: 1
|
||||
:widths: 20 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
* - CPU 频率
|
||||
- DTIM
|
||||
- Average current(mA)
|
||||
- Max current(mA)
|
||||
- Min current(mA)
|
||||
- 平均电流 (mA)
|
||||
- 最大电流 (mA)
|
||||
- 最小电流 (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- 1
|
||||
|
||||
@ -2,12 +2,12 @@
|
||||
:header-rows: 1
|
||||
:widths: 20 10 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
* - CPU 频率
|
||||
- DFS
|
||||
- DTIM
|
||||
- Average current(mA)
|
||||
- Max current(mA)
|
||||
- Min current(mA)
|
||||
- 平均电流 (mA)
|
||||
- 最大电流 (mA)
|
||||
- 最小电流 (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
|
||||
@ -3,10 +3,10 @@
|
||||
:widths: 20 20 30 20 20
|
||||
|
||||
* - 项目
|
||||
- Modem Sleep
|
||||
- Modem Sleep+DFS
|
||||
- auto light Sleep
|
||||
- Deep Sleep
|
||||
- Modem-sleep
|
||||
- Modem-sleep+DFS
|
||||
- Auto Light-sleep
|
||||
- Deep-sleep
|
||||
|
||||
* - 休眠
|
||||
- 自动
|
||||
|
||||
@ -2,11 +2,11 @@
|
||||
:header-rows: 1
|
||||
:widths: 20 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
* - CPU 频率
|
||||
- DTIM
|
||||
- Average current(mA)
|
||||
- Max current(mA)
|
||||
- Min current(mA)
|
||||
- 平均电流 (mA)
|
||||
- 最大电流 (mA)
|
||||
- 最小电流 (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- 1
|
||||
|
||||
@ -2,12 +2,12 @@
|
||||
:header-rows: 1
|
||||
:widths: 20 10 10 20 20 20
|
||||
|
||||
* - CPU frequency
|
||||
* - CPU 频率
|
||||
- DFS
|
||||
- DTIM
|
||||
- Average current(mA)
|
||||
- Max current(mA)
|
||||
- Min current(mA)
|
||||
- 平均电流 (mA)
|
||||
- 最大电流 (mA)
|
||||
- 最小电流 (mA)
|
||||
|
||||
* - 160 MHz
|
||||
- ON
|
||||
|
||||
@ -3,10 +3,10 @@
|
||||
:widths: 20 20 30 20 20
|
||||
|
||||
* - 项目
|
||||
- Modem Sleep
|
||||
- Modem Sleep+DFS
|
||||
- auto light Sleep
|
||||
- Deep Sleep
|
||||
- Modem-sleep
|
||||
- Modem-sleep+DFS
|
||||
- Auto Light-sleep
|
||||
- Deep-sleep
|
||||
|
||||
* - 休眠
|
||||
- 自动
|
||||
|
||||
@ -1727,7 +1727,7 @@ WPA2-Enterprise 是企业无线网络的安全认证机制。在连接到接入
|
||||
{IDF_TARGET_NAME} Wi-Fi 节能模式
|
||||
-----------------------------------------
|
||||
|
||||
本小节将简单介绍Wi-Fi节能模式相关的概念和使用方式，更加详细的介绍请参考 :doc:`低功耗模式使用指南 <../api-guides/low-power-mode>`。
|
||||
本小节将简单介绍Wi-Fi节能模式相关的概念和使用方式，更加详细的介绍请参考 :doc:`低功耗模式使用指南 <../api-guides/low-power-mode/index>`。
|
||||
|
||||
station 睡眠
|
||||
++++++++++++++++++++++
|
||||
|
||||
Loading…
Reference in New Issue
Block a user