2024-05-23 05:41 PM - edited 2024-05-24 12:52 PM
EDITED:
Resolved, but leaving here for the next person who stumbles into this issue.
I'm using the STM32G030K6 and encountered two issues:
The rest of this thread is obsolete, it was the result of a failed component where I could not set the nBOOT_SEL bit successfully. Many thanks to @waclawek.jan for all of the patience and help!
Solved! Go to Solution.
2024-05-28 02:52 AM
Hello @DAlbe.3 ,
I agree there is an issue in the documentation.
Now regarding the actual protection of OTP value, I don't think this is an issue.
OTP are One Time Programmable and are not erased on RDP regression.
So, protecting OTP while in RDP1 does not bring you any OTP confidentiality protection as long as you can regress the device to RDP0 and read the OTP in clear.
Here, OTP purpose is to ensure immutability of the data, not confidentiality
If you need this confidentiality, you must use RDP2. In that case, it you need to update the firmware, you will need a secure boot and loader in user flash to make sure a fake firmware cannot be installed.
Best regards
Jocelyn
2024-05-28 04:04 AM
@Jocelyn RICARD wrote:So, protecting OTP while in RDP1 does not bring you any OTP confidentiality protection as long as you can regress the device to RDP0 and read the OTP in clear.
Good point!
2024-10-01 01:47 AM
Thank you! I've encountered the very same problem with STM32G030F6P6. Setting nBOOT_SEL option works for me.
I would like to add some hardware details about the issue I encountered. This problem is highly related to the power supply. On my PCB, there is a 470uF capacitor. When the system powers on, if this capacitor is fully discharged, the STM32 fails to start. However, if the capacitor has a small residual voltage (> 0.xV), the STM32 starts normally.
I used an oscilloscope to check the VCC voltage rise curves in both cases, and I didn’t find obvious differences.