From 530fdacd88dc87de45207e99ed50db2f918b0d5f Mon Sep 17 00:00:00 2001 From: Aditya Patwardhan Date: Wed, 3 Apr 2024 10:57:54 +0530 Subject: [PATCH] fix(docs): Fix DIS_ICACHE related information in host security workflow --- .../security/host-based-security-workflows.rst | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/docs/en/security/host-based-security-workflows.rst b/docs/en/security/host-based-security-workflows.rst index 4382e743a9..36a877777a 100644 --- a/docs/en/security/host-based-security-workflows.rst +++ b/docs/en/security/host-based-security-workflows.rst @@ -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 `_. - 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