2021-07-25 04:44 AM
st32h745 after the firmware, the prohibition on reading the program memory itself was set. Trying to remove the ban using STM32CubeProgrammer gives an error. Previously, set boo0 high, erased the chip and all config registers returned to their default state. Tell me what you can do or all the chip is screwed up.
Solved! Go to Solution.
2021-07-25 10:13 AM
To fix, first connect to the chip and set RDP to level 1.
13:13:29 : Option byte command : -ob RDP=187
Then, set the following options all at the same time (RDP 0, empty protection area range, DMEPx=0):
13:13:49 : Option byte command : -ob PROT_AREA_START1=0xff PROT_AREA_START2=0xff DMEP1=0 DMEP2=0 RDP=170
2021-07-25 07:51 AM
From the reference manual:
There are no restrictions in setting DMEP1/2 bit. Resetting DMEP1/2 bit from 1 to 0 can
only be done when an RDP level 1 to 0 regression or a bank erase with protection
removal is requested at the same time.
2021-07-25 10:13 AM
To fix, first connect to the chip and set RDP to level 1.
13:13:29 : Option byte command : -ob RDP=187
Then, set the following options all at the same time (RDP 0, empty protection area range, DMEPx=0):
13:13:49 : Option byte command : -ob PROT_AREA_START1=0xff PROT_AREA_START2=0xff DMEP1=0 DMEP2=0 RDP=170
2021-07-25 03:42 PM