Segger cannot unlock after stm32f05x is added to RDP (LV1)

After the RDP function is added to the stm32f10x series of the cm3 core, RDP cannot be removed from the unsecured chip of the segger or the CMD of the unlock stm32, And the unlock stm32 prompts that the model cannot be recognized. After trying many methods, you still cannot remove RDP. It is estimated that the model is relatively new and segger is not fully supported yet. The segger used is the latest official release and beta versions v4.65d and v4.67c/

The following three methods are available:

1. Configure the boot zone, start with system bootloader, boot1 = 0, boot0 = 1, and then use host a of the serial ISP to remove read protection;

2. Configure the boot area, run the program with the SRAM, and perform the RDP removal operation in the main program of the SRAM;

3. Purchase stlink II, download stvp, select option byte programming, and set Option byte to lv0 again;

The above only verifies the third method because the hardware is fixed. Verification passed, perfect removal of RDP!

Attached to the RDP method:

If (set! = Flash_ob_getrdp () {flash_unlock (); // The value must be added; otherwise, the flash_ob_unlock (); flash_ob_rdpconfig (timeout); flash_ob_lock (); flash_lock (); flash_ob_launch (); // This statement must be added and will be automatically reset and loaded. Otherwise, the RDP will not take effect when powered on for the first time and will take effect only after reset. }