Mirrors/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2026-10-01 10:40:47 +03:00
Code Issues Packages Projects Releases Wiki Activity

fix : apply the suggestion from doc team

Browse Source
This commit is contained in:
Zheng Zhong
2025-11-28 10:19:15 +08:00
committed by Zhang Shuxian
parent e3a34f5453
commit a4e05f49c0
4 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/security/flash-encryption.rst
+1 -1
View File
@@ -512,7 +512,7 @@ If all partitions needs to be updated in encrypted format, run:
.. note::
The above operations only apply if the `DIS_DOWNLOAD_MANUAL_ENCRYPT` eFuse bit has not been programmed. If this eFuse bit has been programmed, you need to flash the encrypted firmware image instead.
The above operations are only applicable when the ``DIS_DOWNLOAD_MANUAL_ENCRYPT`` eFuse bit has not been programmed. If this eFuse bit has been programmed, you must flash the pre-encrypted ciphertext image instead.
.. _flash-enc-release-mode:
docs/en/security/security-features-enablement-workflows.rst
+1 -1
View File
@@ -320,7 +320,7 @@ In this case all the eFuses related to Flash Encryption are written with help of
.. note::
If secure boot is also enabled, please perform the secure boot firmware signing first, and then carry out the above encryption operation.
If secure boot is enabled, perform secure boot signing of the firmware before carrying out the above encryption operation.
In the above command, the offsets are used for a sample firmware, and the actual offset for your firmware can be obtained by checking the partition table entry or by running `idf.py partition-table`. Please note that not all the binaries need to be encrypted, the encryption applies only to those generated from the partitions which are marked as ``encrypted`` in the partition table definition file. Other binaries are flashed unencrypted, i.e., as a plain output of the build process.