Skip to main content
Associate
September 25, 2026
Question

DEV_TARGET_CMD_ERR when trying to connect my ST-Link to my Debug connector for the WB09 series

I tried to program my STM32WB09ke chip with my ST-LINK V3 MINIE. When pressing the Connect button on stm32cubeprogrammer, I got the DEV_TARGET_CMD_ERR. It says: unable to get core ID. 

When debugging with my J-Link, everything works completely fine. I can program, debug, ...

When connecting my ST-Link to one of my other projects with other ST MCU but with exactly the same debug connector, It completely works fine. 

Here are my schematics:

 

Does someone knows what the problem could be or am I missing something?

I checked the SWDIO and SWCLK signals with my scope and everything looks fine. 

3 replies

ST Technical Moderator
September 28, 2026

Hello ​@GDBY2 and welcome to the Community,

You can try to change the connect mode to "Under reset" on STM32CubeProgrammer or press reset button, keep it pressed, click on Connect and release the button.

May be your board was previously programmed and the device entering Deepstop, which disables SWD access. In that case, use the UART bootloader recovery on PA10 high during reset, or perform mass erase through UART mode before retrying SWD programming. For more details, please refer to this wiki article: STM32WB0 device debug and access in low-power mode - stm32mcu

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks
GDBY2Author
Associate
October 2, 2026

The under reset principle did not work. I already tested it but it gave me the same error. The board is a new PCB from our production and was never programmed before. 

I measured the VCAP value and saw that it was 0V when powered. I don’t know if this can be the issue?

I have now a second PCB made with the STM32WBA52, but with the same debug header, and this works completely fine. 

Laurent LOUAZON
ST Employee
October 5, 2026

Hello,

C18 and C19 should not be set but I guess this is not the problem here.

As you mentionned, if parts are fresh new and no FW was flashed previously, no reason to handle boot pin as explained in wiki link provided above.

Please ensure using Cube programmer with : “Hot plug mode” or “Normal mode” with “Software reset”.
We noticed some problem with STM32WB0 is using “Under reset mode” or “Normal mode” with “Hardware reset”.

Can yo try removing  R6, R7 or R9?

Regards
Laurent