Unable to Debug or Connect STM32L562E-DK After Enabling Read Protection

[Sankar_Eswaran]

Hi,
I am facing an issue with my STM32L562E-DK board. Initially, I was able to debug it using STM32CubeIDE. However, after attempting to configure the controller in UART boot mode, I accidentally enabled read protection (DC:LEVEL 1). Since then, I cannot debug the board or connect to it using STM32CubeProgrammer.

Whenever I try to connect the controller via STM32CubeProgrammer, it fails to establish a connection. I suspect something went wrong during the configuration.

I have attached an image below showing the error that occurs when I try to connect.

How can I resolve this issue and regain access to my controller?

Edited by ST Moderator to correct the board name STM32L562E-DK (instead STM32L62E-DK)

[STea]

Hello @Sankar_Eswaran ,

connect using the hotplug mode in CubeProgrammer .
Regards

[Sankar_Eswaran]

Hi,

i tried every mode but it still not connecting is there any specific documents steps need to be follow ?

 

Thanks & Regards 

Sankar Eswaran.

[Sunt]

Hello, I also encountered the same problem after modifying RDP. I am also using the stm32l56e-dk board. Can you successfully connect to this board?

[Imen.D]

Hello @Sankar_Eswaran ,

Did you try connecting under reset? Once connected, perform a mass erase to remove the read protection.

Try using the ST-LINK for debugging only and use another power supply source. Apply a power off/on cycle while the ST-LINK USB cable is already plugged in. After that, the tool should be able to connect to the target and launch RDP regression.

Please refer to this article, this will help you What option bytes in STM32 are, and how to use the... - STMicroelectronics Community