cancel
Showing results for 
Search instead for 
Did you mean: 

st32h745 after the firmware, a ban on reading program memory was set itself

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.

1 ACCEPTED SOLUTION

Accepted Solutions
TDK
Guru

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

If you feel a post has answered your question, please click "Accept as Solution".

View solution in original post

3 REPLIES 3
TDK
Guru

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.

If you feel a post has answered your question, please click "Accept as Solution".
TDK
Guru

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

If you feel a post has answered your question, please click "Accept as Solution".

0693W00000D0YxEQAV.pngThank you very much for the help. Everything worked out. I'm not quite at ease with the English language, all this is written right in the CubeМХ programmer. I now have full access to the chip.