Skip to main content
jgauthier
Senior
Sep 14, 2022 12:25 PM UTC
Solved

Issues with ST-Link serial number

I am assuming this is a Windows driver issue, but I do not know how to resolve it.

I use several Nucleo boards. Additionally, I use some USB ST-Link programmers.

These programmers always show up with a single letter serial number: A, B,C, D.

Using Keil ARM, I can often click around and get them to work (program)

But with STM32CubeIDE and STM32CubeProgrammer they always show up as a single letter and the software refuses to use them.

For instance CubeProgrammer:

0693W00000SvMUsQAN.png 

Does anyone know the path to resolution for this problem?

This topic has been closed for replies.
Peter BENSCH
Peter BENSCHBest answer
ST Technical Moderator
Sep 14, 2022 4:33 PM UTC
You expect the same behaviour from replicas as from original parts?
The software does not recognize these clones because they are not genuine ST-LINK from STMicroelectronics. An original ST-LINK/V2 or ST/LINK-V3 would perfectly work.
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.

16 replies

Peter BENSCH
ST Technical Moderator
Sep 14, 2022 1:47 PM UTC

What type are the USB ST-Link programmers?

Can you post an example photo?

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.
jgauthier
jgauthierAuthor
Senior
Sep 14, 2022 4:11 PM UTC
Peter BENSCH
Peter BENSCHBest answer
ST Technical Moderator
Sep 14, 2022 4:33 PM UTC
You expect the same behaviour from replicas as from original parts?
The software does not recognize these clones because they are not genuine ST-LINK from STMicroelectronics. An original ST-LINK/V2 or ST/LINK-V3 would perfectly work.
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.
Tesla DeLorean
Guru
Sep 14, 2022 8:27 PM UTC

Bad cables and hubs can be a contributory factor

Target connectivity, perhaps powering of buffers via VTarget, or non-responsiveness of Target (ie Off, Sleeping, pins disabled/reconfigured)

Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
Javier1
Principal
Dec 20, 2022 4:55 PM UTC

Same issue here, the guy from purchasing tought they were original, and they look original to me untill you try to use them:

https://community.st.com/s/question/0D53W000020jfDLSAY/fake-stlinks-reaching-me-trough-legit-distributorswhich-stcubeprogrammer-version-shall-we-use0693W00000WLQ02QAH.png0693W00000WLQ1yQAH.png

hit me up in https://www.linkedin.com/in/javiermuñoz/
Peter BENSCH
ST Technical Moderator
Mar 2, 2023 1:23 PM UTC

Update: meanwhile there is a knowledge base article on the topic: How to recognize a genuine ST-Link/V2 versus a cloned one?, created by Amel NASRI.

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.
NLima.1
Visitor II
Mar 28, 2023 5:41 AM UTC

This happens because the STLink you are using must be the generic one. probably the Geehy APM32F103CBT6 ie fake.

So it will only communicate with the STLink Utility

Aqui: stsw-link004.html.

Explorer
Sep 8, 2023 12:13 AM UTC

Screenshot 2023-09-07 180739.png

Screenshot 2023-09-07 180819.png

This seems to work for me just enable Shared and click then click the refresh button quite a few times and it'll show a serial number and connect. a little late but i figure it'll help someone out

MGerz
Associate
Oct 30, 2023 9:12 AM UTC

Thank you, I have the same problem, but the Shared checkbox solved it :)