From 5e436add7a21d2c2000a4a8682e93933e1210e51 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 c861744918..c3af85c37e 100644 --- a/docs/en/security/secure-boot-v2.rst +++ b/docs/en/security/secure-boot-v2.rst @@ -223,7 +223,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 ``make`` or ``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``.