Is it possible to re-flash the user program in a device secured with SB V2 or is it permanently burned?
If it can be re-flashed, then what's the procedure? I've read the docs many times, and it's obviously possible with V1, but I can't see how it's done in V2.
Stupid question about Secure Boot V2
-
- Posts: 8
- Joined: Thu Oct 22, 2020 9:08 am
Re: Stupid question about Secure Boot V2
Replying to myself, it wasn't stupid, the menuconfig is confusing and over-cautious.
When you turn on secure boot the menu turns on "Permanently disable ROM Download Mode". You have to turn on "Allow potentially insecure options" then go into "Potentially insecure options --->" and turn on "Don’t automatically restrict UART download mode".
This option is documented in https://docs.espressif.com/projects/esp ... onfig.html
Would have been nice to mention this in the Secure Boot V2 docs.
Can I have a few Devkit-C's to replace the ones I screwed having to figure this out myself?
A follow-up question - does OTA still work in secure boot mode if the UART download is restricted?
When you turn on secure boot the menu turns on "Permanently disable ROM Download Mode". You have to turn on "Allow potentially insecure options" then go into "Potentially insecure options --->" and turn on "Don’t automatically restrict UART download mode".
This option is documented in https://docs.espressif.com/projects/esp ... onfig.html
Would have been nice to mention this in the Secure Boot V2 docs.
Can I have a few Devkit-C's to replace the ones I screwed having to figure this out myself?
A follow-up question - does OTA still work in secure boot mode if the UART download is restricted?
-
- Posts: 9582
- Joined: Thu Nov 26, 2015 4:08 am
Re: Stupid question about Secure Boot V2
Yes. OTA has no overlap in code with UART download mode.
Who is online
Users browsing this forum: mark.k92 and 123 guests