Skip to main content
Visitor II
December 12, 2018
Question

STLINK-V3 not recognized

  • December 12, 2018
  • 4 replies
  • 5545 views

Hello there,

I have just obtained the STLINK-V3 device:

0690X000006CoGyQAK.jpg

I have installed the STM32Cube Programmer (v 1.3.0) *** the drivers that comes along with it. The problem is that I cannot find the device:

0690X000006CoH8QAK.png

There is no drivers missing, the device manager is "clean". I am using windows 10 64 bit version. Also there is no COM port available in the device manager.

According to the TN1235, this is correct:

0690X000006CoIkQAK.png

I would appreciate all help.

    This topic has been closed for replies.

    4 replies

    Visitor II
    December 13, 2018

    Any support here please? @Imen DAHMEN​  ?

    Graduate II
    December 13, 2018

    Ok, but what driver is it reportedly using here? That would be the most helpful screen shot.

    Will try a V3 in a Win10 box later but honestly, it doesn't look to me as if you have the right drivers loaded/functional.

    Get it to refresh or find the most current drivers on your box, check the Win10 settings for allowing that to occur.

    Visitor II
    December 14, 2018
    Hi Clive,
    This is an interesting situation. Will move further on my own then, trying to reinstall the drivers. Thank you.
    Visitor II
    July 25, 2022

    If using a corporate pc, it security may prohibit usb memory storage class. Mbed boards or rpi pico wouldn't work as well if thus is the case. I think STLink has 2 driver versions, ine with mass storage disabled. Try it to compare. As it is a composite device pc allows all ar none....

    Visitor II
    September 28, 2023

    Sorry , but I didnt see comments how you resolved this topic : I have the same topic

    Graduate II
    September 28, 2023

    Having the same issue 5 years on perhaps something where you lead with specific detail of your situation.

    Like what drivers are actually loaded against the ST-LINK/V3, and what ST-LINK/V3 are we talking about.

    Solution: Get the right drivers loaded, make sure Windows recognizes the device, that you have the right cable, not a charger / power-only one.