ST-Link V2 cannot detect AT32F415 target over SWD

[Riskybiscuits]

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:

1. Does ST-Link V2 fully support SWD communication with AT32 (Artery) MCUs, or do I need an AT-Link?

2. If ST-Link V2 should work, what settings or wiring should I double-check?

3. Is there any special sequence needed to connect if the AT32 has read protection enabled?

4. 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.

[Peter BENSCH]

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

[Andrew Neil]

---

@Riskybiscuits wrote:

1. Does ST-Link V2 fully support SWD communication with AT32 (Artery) MCUs

---

As @Peter BENSCH said, the ST-Link is only supported for use with ST's own products. It is not designed nor supported for use with any 3rd-party MCUs.

Similarly for ST's software tools - CubeIDE, CubeProgrammer, etc ...

---

@Riskybiscuits wrote:

or do I need an AT-Link?.

---

Not necessarily - there are 3rd-party debug probes which do support a wide range of MCU families; eg, Segger J-Link...