2022-01-17 07:00 AM
I'm working on a project where we are using the new STM32U575xx series. Now I created a bootloader and wanted to write protect the bootloader section. However I'm not able to disable the write protection using the ST-Link v3 and STM32CubeProgrammer.
If I try to unlock the write protection I get the following error:
Is there a way to fix this problem? Or do I have to file a bug report in the support section? How long will it take to fix this? I'm kind of stuck now because also the J-Link STM32 Unlock application doesn't support the STM32U575xx yet...
Solved! Go to Solution.
2022-01-18 02:34 AM
Sorry, I first had to read the reference manual as answered in: https://community.st.com/s/question/0D53W00001JWUPVSA5/resetting-option-bytes-of-stm32u575xx-with-ram-application
While trying to do it with a custom application I got it working.
Please not that you are not allowed to change the start and end offset, if you want to reset those you will have to do this in step 4.
2022-01-18 02:34 AM
Sorry, I first had to read the reference manual as answered in: https://community.st.com/s/question/0D53W00001JWUPVSA5/resetting-option-bytes-of-stm32u575xx-with-ram-application
While trying to do it with a custom application I got it working.
Please not that you are not allowed to change the start and end offset, if you want to reset those you will have to do this in step 4.
2022-01-20 02:52 AM
However after removing the write protection using these steps I am still not allowed to program the previous locked pages. Any idea on how to fix this?
2022-01-26 07:22 AM
After steps 1 to 3 you can reset the WRPStart and WRPEnd to there factory default to disable the write protection. There factory default is 0x7f for start and 0x00 for end.