Skip to main content
Associate
September 21, 2026
Question

Can not find STM32 on ST-LINK V2

  • September 21, 2026
  • 8 replies
  • 72 views

Hi there! I'm using STM32F407G-DISC. Because the debug port on Kit was broken, I temporary using ST-LINK V2 mini. And my problem is my ST-LINK can’t found my STM32F407-DISC1 on STM32CubeProgrammer even though I choose “Connect under reset” mode. I don't know how to fix them. Can you solve this?

8 replies

Andrew Neil
Super User
September 21, 2026

ST-LINK V2 mini

You mean something like this:

 

Despite the logo (it’s fake), there is no such ST product:

 

 

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
Peter BENSCH
ST Technical Moderator
September 21, 2026

 Can you solve this?

We can’t solve that, but you can do it yourself: buy a genuine ST-LINK, because it not only works, but is also supported here.

Regards
/Peter

In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
Associate
September 22, 2026

I’m using an genuine ST-LINK, which I have been using successfully to program an STM32F103C8T6 for about three months.

Recently, I tried to use the same ST-LINK to program an STM32F407-DISC1. However, the onboard programming/debugging port on the STM32F407-DISC1 is damaged, so I’m trying to connect the external ST-LINK directly to the SWD interface.

When I try to connect to the STM32F407-DISC1 using STM32CubeProgrammer, I get the error message shown in the attached image.

The same ST-LINK works normally with my STM32F103C8T6.

What could be causing this issue, and what should I check on the STM32F407-DISC1?

 

Andrew Neil
Super User
September 22, 2026

I’m using an genuine ST-LINK,

Again, there is no such ST product as an “ST-LINK V2 mini”.

So please post photos of the front & back of the device you have.

 

the onboard programming/debugging port on the STM32F407-DISC1 is damaged

How do you know that?

How was it damaged?

How do you know that the target STM32F407 wasn’t also damaged?

 

Anyhow, to use an external debug probe (whether genuine ST or not), you will first need to disconnect the onboard STLink - see the User Manual and/or schematics for details.

Please show how you are connecting your STLink to the Disco board - schematic, photos.

 

 

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
Associate
September 23, 2026

The first photo shows my ST-LINK.
The second photo shows my development board. As you can see, the onboard programming/debugging connector is damaged.
The third and fourth photos show the front and back of my wiring connection.

My connections are as follows:

  • PA14 (SWDIO) → ST-LINK (SWDIO)

  • PA13 (SWCLK) → ST-LINK (SWCLK)

  • GND → ST-LINK (GND)

  • 3V → 3.3V

After the programming/debugging connector on the board was damaged last month, I tested the connection using STM32CubeProgrammer, and it connected successfully.

However, I am still using exactly the same wiring and setup now, but STM32CubeProgrammer reports that it cannot find the STM32, as shown in my previous screenshot.

I don't know what happened or why it suddenly stopped working, so I would appreciate any advice on what I should check next.

ST-LINK
development board

 

Explorer II
September 23, 2026

‘XTW ST-Link V2’ is not a ST authorized debugger/programmer.
Or be more plain, IT’S FAKE.

 

SO WHAT IS A REAL, GENUINE ST-LINK???
https://www.st.com/en/development-tools/st-link-v2.html

IMO, never bring disgrace on yourself by asking for official support with a fake merchandise.

 

Best Regards.