From 26514959ddc496c97ff161ec67528ad196d4ff8c Mon Sep 17 00:00:00 2001 From: Mahavir Jain Date: Mon, 27 Jun 2022 14:24:42 +0530 Subject: [PATCH] docs: secure-boot-v2: remove incorrect note about bootloader re-flash In secure-boot-v2 scheme, one can always regenerate signature using secure boot signing key and re-flash either bootloader or application. --- docs/en/security/secure-boot-v2.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/security/secure-boot-v2.rst b/docs/en/security/secure-boot-v2.rst index d68de774c5..adff145658 100644 --- a/docs/en/security/secure-boot-v2.rst +++ b/docs/en/security/secure-boot-v2.rst @@ -289,7 +289,7 @@ How To Enable Secure Boot V2 4. Select the desired UART ROM download mode in "UART ROM download mode". By default, it is set to "Permanently switch to Secure mode" which is generally recommended. For production devices, the most secure option is to set it to "Permanently disabled". -5. Set other menuconfig options (as desired). Pay particular attention to the "Bootloader Config" options, as you can only flash the bootloader once. Then exit menuconfig and save your configuration. +5. Set other menuconfig options (as desired). Then exit menuconfig and save your configuration. 6. The first time you run ``idf.py build``, if the signing key is not found then an error message will be printed with a command to generate a signing key via ``espsecure.py generate_signing_key``.