Hello,
I am using an STM32WB05KZ board and it was working normally with SWD through STM32CubeProgrammer.
However, after uploading a BLE beacon example firmware, I can no longer connect to the MCU.
CubeProgrammer shows the following errors:
Error: Unable to get core ID
Error: ST-LINK error (DEV_TARGET_CMD_ERR)
No STM32 target found
My setup:
SWDIO, SWCLK, and RST are connected through through-hole pads.
ST-LINK V2 firmware: V2J46M33
Voltage: 3.21 V
SWD frequency tested from 4 MHz down to 100 kHz
Tried "Under Reset", "Hotplug", and "Normal" modes
Tried holding RESET while connecting → still no success
It seems the BLE firmware is blocking SWD or reconfiguring PA13/PA14 very early during boot.
Requested Help:
How can I recover the STM32WB05KZ and re-enable SWD?
Is there a recommended recovery procedure for WB devices stuck after BLE firmware?
Does the WB05KZ support BOOT0 or another method to force the system bootloader?
How can I prevent BLE examples from disabling SWD pins or entering STOP mode?
Any guidance from ST engineers or community experts would be greatly appreciated.
Thank you.
