cancel
Showing results for 
Search instead for 
Did you mean: 

Setting BORF on STM32G041F8 bricks the processor???

STM32CubeProg 2.19.0.  STM32G041F8. MacOS 15.5. ST-Link.

I'm working on setting the brown-out rising, falling, and enable options on an STM32G041F8.

I started out by just using CubeProg to set the BOR_EN enable bit in the option bytes. Works correctly. It gives me the reaction I expected and I'm able to reconnect via CubeProg.

Next I wanted to set the BORF_LEV to something other than 3 so I can test my code. I set it to 1, hit Apply, Cube prog complains that the connection is lost and it has disconnected from the device, and now when I try and connect I just get:

17:13:46 : UR connection mode is defined with the HWrst reset mode
17:13:46 : ST-LINK SN  : 31FF6A064D4E353828580643
17:13:46 : ST-LINK FW  : V2J46S7
17:13:46 : Board       : --
17:13:46 : Voltage     : 3.31V
17:13:46 : Error: Unable to get core ID
17:13:46 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication

No, I did not mess with the RDP values, just BORF_LEV.

CubeProg can't unbrick it. CubeIDE gets similar results. Unfortunately, for me, I duplicated the result in another processor so I thought I'd stop and reach out.

Any ideas as to how to unlock these things?

Thanks,

Andrei (your neighbour from The Great White North) 

0 REPLIES 0