cancel
Showing results for 
Search instead for 
Did you mean: 

Bricked STM32H743XI - RD/WR Protection Issue

_JJ_
Associate III

Hello

I have been stuck with a bricked STM32H743XI. I was flashing a new FW and accidentally hit reset at the same time, and since then, I have been unable to talk to the MCU. I use Segger JLink for programming the device; it's a custom board built around STM32H743XI.

I have been stuck in the same issue in past, but back then, Segger Jlink STM32 Unlock utility came to the rescue, and the MCU was back on track. But this time, it seems not to be able to set option bytes, hence I can not flash the FW, and my board is unusable at this moment.

_JJ__0-1757693166489.png

Also, tried using JLink Commander, if it can erase MCU banks, but did not help either.

_JJ__1-1757693383098.png

As this didn't turn out to be quite helpful this time, I turned to different available options. First, tried using ST-vLink and ST Cube Programmer, but that too didn't work out well. I was able to connect to MCU but was not able to perform anything using the tool. Every single time I connected, a "Read Memory Error" popped up.

_JJ__2-1757693421241.png

Option byte using ST-vLink:

_JJ__3-1757693443557.png

In one of the forums, someone mentioned updating FW of ST-vLink to get over the issue, not sure how it would have helped, but was desperately looking for a solution, so I tried it, but it did not help either.

Tried ST Cube Programmer with Jlink as well, but same result. I guess no surprise there, if ST-vLink was not able to talk to ST MCU, how a 3rd party could...

_JJ__4-1757693646788.png

Option byte using Segger JLink:

_JJ__5-1757693669142.png

Any sort of help to resolve this issue would be really appreciated.

Thanks in adavance!

 

BR
JJ
0 REPLIES 0