mirror of
https://github.com/espressif/esp-idf.git
synced 2025-08-04 05:04:33 +02:00
Merge branch 'docs/update_unsync_cn_translation' into 'master'
docs: Sync CN translation with EN Closes DOC-11657 See merge request espressif/esp-idf!40262
This commit is contained in:
@@ -15,7 +15,6 @@ RTC Subsystem Control
|
|||||||
|
|
||||||
RTC control APIs have been moved from ``driver/rtc_cntl.h`` to ``esp_private/rtc_ctrl.h``.
|
RTC control APIs have been moved from ``driver/rtc_cntl.h`` to ``esp_private/rtc_ctrl.h``.
|
||||||
|
|
||||||
|
|
||||||
.. _deprecate_adc_driver:
|
.. _deprecate_adc_driver:
|
||||||
|
|
||||||
ADC
|
ADC
|
||||||
|
@@ -9,7 +9,6 @@ Wi-Fi Enterprise Security
|
|||||||
|
|
||||||
APIs defined in `esp_wpa2.h` have been deprecated. Please use newer APIs from `esp_eap_client.h`.
|
APIs defined in `esp_wpa2.h` have been deprecated. Please use newer APIs from `esp_eap_client.h`.
|
||||||
|
|
||||||
|
|
||||||
Wi-Fi Disconnect Reason Codes
|
Wi-Fi Disconnect Reason Codes
|
||||||
------------------------------
|
------------------------------
|
||||||
|
|
||||||
@@ -22,7 +21,7 @@ For the event WIFI_EVENT_STA_DISCONNECTED, the original reason code WIFI_REASON_
|
|||||||
|
|
||||||
For details, please refer to :ref:`esp_wifi_reason_code`.
|
For details, please refer to :ref:`esp_wifi_reason_code`.
|
||||||
|
|
||||||
|
|
||||||
WiFi Multiple Antennas
|
WiFi Multiple Antennas
|
||||||
----------------------
|
----------------------
|
||||||
|
|
||||||
WiFi multiple antennas api will be deprecated. Please use newer APIs from `esp_phy.h`.
|
WiFi multiple antennas api will be deprecated. Please use newer APIs from `esp_phy.h`.
|
||||||
|
@@ -16,7 +16,6 @@ ADC
|
|||||||
|
|
||||||
The legacy ADC driver ``driver/adc.h`` is deprecated since version 5.0 (see :ref:`deprecate_adc_driver`). Starting from version 6.0, the legacy driver is completely removed. The new driver is placed in the :component:`esp_adc`, and the header file path is ``esp_adc/adc_oneshot.h``, ``esp_adc/adc_continuous.h``, ``esp_adc/adc_cali.h`` and ``esp_adc/adc_cali_scheme.h``.
|
The legacy ADC driver ``driver/adc.h`` is deprecated since version 5.0 (see :ref:`deprecate_adc_driver`). Starting from version 6.0, the legacy driver is completely removed. The new driver is placed in the :component:`esp_adc`, and the header file path is ``esp_adc/adc_oneshot.h``, ``esp_adc/adc_continuous.h``, ``esp_adc/adc_cali.h`` and ``esp_adc/adc_cali_scheme.h``.
|
||||||
|
|
||||||
|
|
||||||
RMT
|
RMT
|
||||||
---
|
---
|
||||||
|
|
||||||
|
@@ -7,6 +7,7 @@ Xtensa
|
|||||||
------
|
------
|
||||||
|
|
||||||
The Xtensa special register header files have been updated to use a new naming convention. The old ``specreg.h`` header files are now deprecated and will be removed in a future release.
|
The Xtensa special register header files have been updated to use a new naming convention. The old ``specreg.h`` header files are now deprecated and will be removed in a future release.
|
||||||
|
|
||||||
The register names have been updated to use the ``XT_REG_`` prefix. Please use the new ``xt_specreg.h`` file instead.
|
The register names have been updated to use the ``XT_REG_`` prefix. Please use the new ``xt_specreg.h`` file instead.
|
||||||
|
|
||||||
Power Management
|
Power Management
|
||||||
|
@@ -40,3 +40,4 @@ ESP-IDF 支持但不包含在芯片 ROM 中的功能
|
|||||||
:esp32s3: - 修复了只能将 16 MB 虚拟地址范围映射到 flash 只读数据中的问题。
|
:esp32s3: - 修复了只能将 16 MB 虚拟地址范围映射到 flash 只读数据中的问题。
|
||||||
:esp32c3: - 修复了只能将 128 KB 虚拟地址范围映射到 flash 指令中的问题。
|
:esp32c3: - 修复了只能将 128 KB 虚拟地址范围映射到 flash 指令中的问题。
|
||||||
:esp32c2: - 修复了只能将最多 128 KB 虚拟地址范围映射到 flash 指令中的问题。
|
:esp32c2: - 修复了只能将最多 128 KB 虚拟地址范围映射到 flash 指令中的问题。
|
||||||
|
- 修复了擦除和写入函数在地址与长度相加超出 32 位边界时,可能绕过边界检查的问题。
|
||||||
|
@@ -9,6 +9,18 @@ Wi-Fi 企业级安全
|
|||||||
|
|
||||||
在 `esp_wpa2.h` 中定义的 API 已弃用,请使用来自 `esp_eap_client.h` 的新 API。
|
在 `esp_wpa2.h` 中定义的 API 已弃用,请使用来自 `esp_eap_client.h` 的新 API。
|
||||||
|
|
||||||
|
Wi-Fi 断开连接原因代码
|
||||||
|
------------------------
|
||||||
|
|
||||||
|
对于事件 WIFI_EVENT_STA_DISCONNECTED,原有的断开原因代码 WIFI_REASON_NO_AP_FOUND 已细分为以下几种情况:
|
||||||
|
|
||||||
|
- REASON_NO_AP_FOUND(原始原因码,仍在某些场景中使用)
|
||||||
|
- REASON_NO_AP_FOUND_IN_RSSI_THRESHOLD(在 RSSI 门限范围内未找到 AP)
|
||||||
|
- REASON_NO_AP_FOUND_IN_AUTHMODE_THRESHOLD(在认证模式门限范围内未找到 AP)
|
||||||
|
- REASON_NO_AP_FOUND_W_COMPATIBLE_SECURITY(未找到具有兼容安全性的 AP)
|
||||||
|
|
||||||
|
|
||||||
Wi-Fi 多天线
|
Wi-Fi 多天线
|
||||||
------------------------
|
------------------------
|
||||||
|
|
||||||
Wi-Fi 多天线相关的 API 将要被弃用,请使用来自 `esp_phy.h` 的新 API。
|
Wi-Fi 多天线相关的 API 将要被弃用,请使用来自 `esp_phy.h` 的新 API。
|
||||||
|
@@ -11,13 +11,13 @@ Wi-Fi 扫描和连接
|
|||||||
|
|
||||||
- :component_file:`esp_wifi/include/esp_wifi_he_types.h`
|
- :component_file:`esp_wifi/include/esp_wifi_he_types.h`
|
||||||
|
|
||||||
- :cpp:struct:`esp_wifi_htc_omc_t` 中:
|
- :cpp:struct:`esp_wifi_htc_omc_t` 中:
|
||||||
|
|
||||||
- ``uph_id``, ``ul_pw_headroom``, ``min_tx_pw_flag`` 字段被弃用
|
- ``uph_id``, ``ul_pw_headroom``, ``min_tx_pw_flag`` 字段被弃用
|
||||||
|
|
||||||
- :component_file:`esp_wifi/include/esp_wifi_types_generic.h`
|
- :component_file:`esp_wifi/include/esp_wifi_types_generic.h`
|
||||||
|
|
||||||
- :cpp:struct:`wifi_ap_record_t` 中:
|
- :cpp:struct:`wifi_ap_record_t` 中:
|
||||||
|
|
||||||
- ``bandwidth`` 的类型从 ``uint8_t`` 更改为 ``wifi_bandwidth_t``
|
- ``bandwidth`` 的类型从 ``uint8_t`` 更改为 ``wifi_bandwidth_t``
|
||||||
|
|
||||||
@@ -27,7 +27,7 @@ Wi-Fi 扫描和连接
|
|||||||
WPA3 企业版 Wi‑Fi 认证模式更改
|
WPA3 企业版 Wi‑Fi 认证模式更改
|
||||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||||
|
|
||||||
在 ESP‑IDF v5.4 之前,支持 WPA3‑Enterprise‑Only 和 WPA3‑Enterprise‑Transition 的接入点(AP)的认证模式(``wifi_auth_mode_t``)均被识别为 ``WIFI_AUTH_WPA2_ENTERPRISE``.
|
在 ESP‑IDF v5.4 之前,支持 WPA3‑Enterprise‑Only 和 WPA3‑Enterprise‑Transition 的接入点 (AP) 的认证模式(``wifi_auth_mode_t``)均被识别为 ``WIFI_AUTH_WPA2_ENTERPRISE``.
|
||||||
|
|
||||||
从 v5.4 开始,该行为已更新:
|
从 v5.4 开始,该行为已更新:
|
||||||
|
|
||||||
@@ -40,7 +40,6 @@ WPA3 企业版 Wi‑Fi 认证模式更改
|
|||||||
|
|
||||||
如果您的应用程序严格检查 ``WIFI_AUTH_WPA2_ENTERPRISE`` 或 ``WIFI_AUTH_ENTERPRISE`` 来识别企业级 AP,则无法识别以 WPA3‑Enterprise‑Only 或 WPA3‑Enterprise‑Transition 模式运行的 AP.
|
如果您的应用程序严格检查 ``WIFI_AUTH_WPA2_ENTERPRISE`` 或 ``WIFI_AUTH_ENTERPRISE`` 来识别企业级 AP,则无法识别以 WPA3‑Enterprise‑Only 或 WPA3‑Enterprise‑Transition 模式运行的 AP.
|
||||||
|
|
||||||
|
|
||||||
**建议操作**
|
**建议操作**
|
||||||
|
|
||||||
为确保与这些模式兼容,请更新您的应用程序关于认证模式的检查逻辑,将新的 ``WIFI_AUTH_WPA3_ENTERPRISE`` 和 ``WIFI_AUTH_WPA2_WPA3_ENTERPRISE`` 模式包含进来.
|
为确保与这些模式兼容,请更新您的应用程序关于认证模式的检查逻辑,将新的 ``WIFI_AUTH_WPA3_ENTERPRISE`` 和 ``WIFI_AUTH_WPA2_WPA3_ENTERPRISE`` 模式包含进来.
|
||||||
|
Reference in New Issue
Block a user