2025-11-17 2:41 PM
Hi everyone. I’m trying to connect a genuine ST-Link V2 to an AT32F415 MCU using SWD, but the debugger always reports “Target not detected” and shows Device Update: false.
Here’s my setup:
• SWDIO → SWDIO
• SWCLK → SWCLK
• GND → GND
• 3.3V from the board is present (measured ~3.29V)
• NRST is connected
• Target is externally powered
• Several different ST-Link drivers tested
• STM32CubeProgrammer, OpenOCD, and ReFlasher all fail to detect the device
• Different cables and different USB ports tested
My questions:
Does ST-Link V2 fully support SWD communication with AT32 (Artery) MCUs, or do I need an AT-Link?
If ST-Link V2 should work, what settings or wiring should I double-check?
Is there any special sequence needed to connect if the AT32 has read protection enabled?
Can ST-Link V2 connect to a target that is running firmware which may have disabled SWD pins?
Any insight or experience with ST-Link + AT32 would be appreciated. Thank you.
2025-11-17 3:12 PM
Welcome @Riskybiscuits, to the community!
If it is an original ST-LINK/V2 (see also this Knowledge base article), then it can only work with original STM32 from STMicroelectronics. For 32-bit MCUs from another manufacturer, you would need to use their tools, including debuggers, as STMicroelectronics does not recognise this manufacturer's MCUs and therefore cannot support them.
Good luck!
Regards
/Peter