alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

fix(docs): Fix DIS_ICACHE related information in host security workflow

Browse Source
This commit is contained in:
Aditya Patwardhan 2024-04-03 10:57:54 +05:30
parent 1366949c8a
commit 530fdacd88
No known key found for this signature in database
GPG Key ID: E628B2648FBF0DD8
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/en/security/host-based-security-workflows.rst
View File

@ -255,21 +255,25 @@ In this case, all the eFuses related to Flash Encryption are written with help o
Please update the EFUSE_NAME with the eFuse that you need to burn. Multiple eFuses can be burned at the same time by appending them to the above command (e.g., EFUSE_NAME VAL EFUSE_NAME2 VAL2). More documentation about `espefuse.py` can be found `here <https://docs.espressif.com/projects/esptool/en/latest/esp32/espefuse/index.html>`_.
B) Write protect security eFuses
.. only:: esp32
After burning the respective eFuses we need to write_protect the security configurations
B) Write protect security eFuses
.. only:: esp32
After burning the respective eFuses we need to write_protect the security configurations. It can be done by burning following eFuse
.. code:: bash
espefuse.py --port PORT write_protect_efuse MAC
espefuse.py --port PORT write_protect_efuse DIS_CACHE
.. note::
The write disable bit for MAC also write disables DIS_CACHE which is required to prevent accidental burning of this bit.
The write protection of above eFuse also write protects multiple other eFuses, Please refer to the {IDF_TARGET_NAME} eFuse table for more details.
.. only:: not esp32
.. only:: SOC_EFUSE_DIS_ICACHE
B) Write protect security eFuses
After burning the respective eFuses we need to write_protect the security configurations. It can be done by burning following eFuse
.. code:: bash