diff --git a/docs/docs_not_updated/esp32c5.txt b/docs/docs_not_updated/esp32c5.txt index f5b05b3141..9eeeccd3b6 100644 --- a/docs/docs_not_updated/esp32c5.txt +++ b/docs/docs_not_updated/esp32c5.txt @@ -1,7 +1,6 @@ api-guides/low-power-mode.rst api-guides/deep-sleep-stub.rst api-guides/inc/external-ram-esp32-notes.rst -api-guides/current-consumption-measurement-modules.rst api-reference/storage/vfs.rst api-reference/storage/spiffs.rst api-reference/storage/nvs_encryption.rst @@ -15,5 +14,3 @@ api-reference/storage/fatfsgen.rst api-reference/storage/index.rst api-reference/storage/nvs_partition_parse.rst api-reference/system/sleep_modes.rst -api-reference/system/power_management.rst -api-reference/system/inc/power_management_esp32c5.rst diff --git a/docs/en/api-guides/current-consumption-measurement-modules.rst b/docs/en/api-guides/current-consumption-measurement-modules.rst index 49f9586001..1c73558532 100644 --- a/docs/en/api-guides/current-consumption-measurement-modules.rst +++ b/docs/en/api-guides/current-consumption-measurement-modules.rst @@ -3,7 +3,7 @@ Current Consumption Measurement of Modules :link_to_translation:`zh_CN:[中文]` -{IDF_TARGET_SOC_BOOT_PIN:default="Not updated", esp32="IO0", esp32s2="IO0", esp32s3="IO0", esp32c3="IO9", esp32c2="IO9", "esp32c6"="IO9", "esp32h2"="IO9", "esp32p4"="IO35"} +{IDF_TARGET_SOC_BOOT_PIN:default="Not updated", esp32="IO0", esp32s2="IO0", esp32s3="IO0", esp32c3="IO9", esp32c2="IO9", "esp32c6"="IO9", "esp32h2"="IO9", "esp32p4"="IO35", "esp32c5"="IO28"} You may want to know the current consumption of a `module `__ in Deep-sleep mode, :doc:`other power-saving modes `, and Active mode to develop some applications sensitive to power consumption. This section introduces how to measure the current consumption of a module running such an application. @@ -22,7 +22,11 @@ Can We Use a Development Board? For {IDF_TARGET_NAME}, you can use development boards such as `ESP32-H2-DevKitM-1 `__ to measure current consumption of corresponding modules as these development boards are equipped with headers, which can be used to measure current drawn by modules. -.. only:: esp32c6 or esp32h2 +.. only:: esp32c5 + + For {IDF_TARGET_NAME}, you can use development boards such as `ESP32-C5-DevKitC-1 `__ to measure current consumption of corresponding modules as these development boards are equipped with headers, which can be used to measure current drawn by modules. + +.. only:: esp32c6 or esp32h2 or esp32c5 With such development boards, you can measure current consumption of modules in Deep-sleep mode by flashing chips with the :example:`deep_sleep ` example. However, you can also measure current of bare modules equipped with {IDF_TARGET_NAME} chip using the following method. diff --git a/docs/en/api-reference/system/inc/power_management_esp32c5.rst b/docs/en/api-reference/system/inc/power_management_esp32c5.rst index 754feffa03..a5b78f7ed6 100644 --- a/docs/en/api-reference/system/inc/power_management_esp32c5.rst +++ b/docs/en/api-reference/system/inc/power_management_esp32c5.rst @@ -5,3 +5,21 @@ * - Max CPU Frequency Set - Lock Acquisition - CPU and APB Frequencies + * - :rspan:`2` 240 + - ``ESP_PM_CPU_FREQ_MAX`` acquired + - + - CPU: 240 MHz + - APB: 80 MHz + * - ``ESP_PM_APB_FREQ_MAX`` acquired, ``ESP_PM_CPU_FREQ_MAX`` not acquired + - + - CPU: 80 MHz + - APB: 80 MHz + * - None + - Min values for both frequencies set with :cpp:func:`esp_pm_configure` + * - :rspan:`1` 80 + - Any of ``ESP_PM_CPU_FREQ_MAX`` or ``ESP_PM_APB_FREQ_MAX`` acquired + - + - CPU: 80 MHz + - APB: 80 MHz + * - None + - Min values for both frequencies set with :cpp:func:`esp_pm_configure` diff --git a/docs/en/api-reference/system/power_management.rst b/docs/en/api-reference/system/power_management.rst index 79385700bc..911a5bddc1 100644 --- a/docs/en/api-reference/system/power_management.rst +++ b/docs/en/api-reference/system/power_management.rst @@ -55,7 +55,7 @@ Dynamic frequency scaling (DFS) and automatic Light-sleep can be enabled in an a Power Management Locks ---------------------- -{IDF_TARGET_MAX_CPU_FREQ: default="Not updated yet", esp32="80 MHz, 160 MHz, or 240 MHz", esp32s2="80 MHz, 160 MHz, or 240 MHz", esp32s3="80 MHz, 160 MHz, or 240 MHz", esp32c2="80 MHz or 120 MHz", esp32c3="80 MHz or 160 MHz", esp32c6="80 MHz or 160 MHz", esp32p4="360 MHz"} +{IDF_TARGET_MAX_CPU_FREQ: default="Not updated yet", esp32="80 MHz, 160 MHz, or 240 MHz", esp32s2="80 MHz, 160 MHz, or 240 MHz", esp32s3="80 MHz, 160 MHz, or 240 MHz", esp32c2="80 MHz or 120 MHz", esp32c3="80 MHz or 160 MHz", esp32c6="80 MHz or 160 MHz", esp32p4="360 MHz", esp32c5="80 MHz, 160 MHz or 240 MHz"} Applications have the ability to acquire/release locks in order to control the power management algorithm. When an application acquires a lock, the power management algorithm operation is restricted in a way described below. When the lock is released, such restrictions are removed. diff --git a/docs/zh_CN/api-guides/current-consumption-measurement-modules.rst b/docs/zh_CN/api-guides/current-consumption-measurement-modules.rst index fe45a7ccec..17893ee2bc 100644 --- a/docs/zh_CN/api-guides/current-consumption-measurement-modules.rst +++ b/docs/zh_CN/api-guides/current-consumption-measurement-modules.rst @@ -3,7 +3,7 @@ :link_to_translation:`en:[English]` -{IDF_TARGET_SOC_BOOT_PIN:default="Not updated", esp32="IO0", esp32s2="IO0", esp32s3="IO0", esp32c3="IO9", esp32c2="IO9", "esp32c6"="IO9", "esp32h2"="IO9", "esp32p4"="IO35"} +{IDF_TARGET_SOC_BOOT_PIN:default="Not updated", esp32="IO0", esp32s2="IO0", esp32s3="IO0", esp32c3="IO9", esp32c2="IO9", "esp32c6"="IO9", "esp32h2"="IO9", "esp32p4"="IO35", "esp32c5"="IO28"} 开发功耗敏感型应用时，需要了解 `模组 `__ 在 Deep-sleep 模式、:doc:`其他节能模式 ` 和 Active 模式下的功耗。本节介绍如何测量运行此类应用程序时模组的功耗。 @@ -22,7 +22,11 @@ 对于 {IDF_TARGET_NAME}，可以使用 `ESP32-H2-DevKitM-1 `__ 等开发板。这些开发板配有排针，可以用来测量模组的功耗。 -.. only:: esp32c6 or esp32h2 +.. only:: esp32c5 + + 对于 {IDF_TARGET_NAME}，可以使用 `ESP32-C5-DevKitC-1 `__ 等开发板。这些开发板配有排针，可以用来测量模组的功耗。 + +.. only:: esp32c6 or esp32h2 or esp32c5 使用上述开发板，可以烧写 :example:`deep_sleep ` 示例来测量模组在 Deep-sleep 模式下的功耗。也可以使用以下方法来测量配有 {IDF_TARGET_NAME} 芯片的裸模组的电流。 diff --git a/docs/zh_CN/api-reference/system/inc/power_management_esp32c5.rst b/docs/zh_CN/api-reference/system/inc/power_management_esp32c5.rst index 95ed4eee05..44b2cae10c 100644 --- a/docs/zh_CN/api-reference/system/inc/power_management_esp32c5.rst +++ b/docs/zh_CN/api-reference/system/inc/power_management_esp32c5.rst @@ -5,3 +5,21 @@ * - CPU 最高频率 - 电源管理锁获取情况 - APB 频率和 CPU 频率 + * - :rspan:`2` 240 + - 获取 ``ESP_PM_CPU_FREQ_MAX`` + - + - CPU: 240 MHz + - APB: 80 MHz + * - 获取 ``ESP_PM_APB_FREQ_MAX``，未获得 ``ESP_PM_CPU_FREQ_MAX`` + - + - CPU: 80 MHz + - APB: 80 MHz + * - 无 + - 使用 :cpp:func:`esp_pm_configure` 为二者设置最小值 + * - :rspan:`1` 80 + - 获取 ``ESP_PM_CPU_FREQ_MAX`` 或 ``ESP_PM_APB_FREQ_MAX`` + - + - CPU: 80 MHz + - APB: 80 MHz + * - 无 + - 使用 :cpp:func:`esp_pm_configure` 为二者设置最小值 diff --git a/docs/zh_CN/api-reference/system/power_management.rst b/docs/zh_CN/api-reference/system/power_management.rst index 77196a833a..0c459aac70 100644 --- a/docs/zh_CN/api-reference/system/power_management.rst +++ b/docs/zh_CN/api-reference/system/power_management.rst @@ -55,7 +55,7 @@ ESP-IDF 中集成的电源管理算法可以根据应用程序组件的需求， 电源管理锁 ---------------------- -{IDF_TARGET_MAX_CPU_FREQ: default="Not updated yet", esp32="80 MHz, 160 MHz, or 240 MHz", esp32s2="80 MHz, 160 MHz, 或 240 MHz", esp32s3="80 MHz, 160 MHz, 或 240 MHz", esp32c2="80 MHz 或 120 MHz", esp32c3="80 MHz 或 160 MHz", esp32c6="80 MHz 或 160 MHz", esp32p4="360 MHz"} +{IDF_TARGET_MAX_CPU_FREQ: default="Not updated yet", esp32="80 MHz, 160 MHz, or 240 MHz", esp32s2="80 MHz, 160 MHz, 或 240 MHz", esp32s3="80 MHz, 160 MHz, 或 240 MHz", esp32c2="80 MHz 或 120 MHz", esp32c3="80 MHz 或 160 MHz", esp32c6="80 MHz 或 160 MHz", esp32p4="360 MHz", esp32c5="80 MHz, 160 MHz, 或 240 MHz"} 应用程序可以通过获取或释放管理锁来控制电源管理算法。应用程序获取电源管理锁后，电源管理算法的操作将受到下面的限制。释放电源管理锁后，限制解除。