ST-LINK USB driver for Windows 11

[Mparikh06]

Is there ST-Link V2 driver for Windows 11? I am using Microsoft Surface Pro + Copilot and trying to load code on STM32L476.

[Pavel A.]

What do you see in the device manager when the ST-Link is connected? (View->Devices by container)

 

[Mparikh06]

For some reason I am still struggling with this. I bought Surface Pro recently

Config:

Windows 11 Home (Version 24H2)
System: 64-bit OS, ARM processor
Processor: Snapdragon X10-Core

I installed STM IDE and trying to work on STM32L476RG MCU, but USB driver is not working. I disable Digital Driver Signing and secure boot. After spending hours, I was about to install drivers but it installs as AMD64 driver.. when I plug board it doesn't recognize installed drivers. I tried updating driver manually but it doesn't show up in the list as well. Can you please help as I need to work on a few projects using this board? 

[jiangfan]

It seems that no official ARM64 Windows STLink driver is available. Perhaps you may try some workaround found from internet.

@AM Could you please help to clarify ?

[jiangfan]

The USB drivers for the STLINK-Vx (STSW-LINK009)
https://www.st.com/en/development-tools/stsw-link009.html

it mentions "USB driver signed for Windows7, Windows8, Windows10". it works on my PC with Win11 (Windows 11 Enterprise, Version 23H2) also.

[KhPaul]

I don't understand why a giant company like ST has a problem signing drivers for Windows ARM64. Why should developers suffer? Maybe it's some kind of quirk, like the lack of updates for Stm32CubeMonPwr. It would be fine if it were a functionality issue, but no, it's guaranteed to crash during prolonged recording. And unfortunately, it's the same everywhere. Maybe it's time to stop shifting our direct tasks to developers and release drivers for ARM64, what do you think?

[AM]

Hello Mparikh06 and jiangfan,

I confirm the issue is linked to Windows ARM64 OS not yet supported by official ST-Link USB driver.

You may have a look at this topic which is the same issue:

https://community.st.com/t5/stm32-mcus-boards-and-hardware/stlink-stcubeprogrammer-support-on-windows-arm64/td-p/224127

Best regards

[Mparikh06]

I managed to install driver with the help but still having issues with STM IDE as it doesn't recognize the device.. Any suggestions? Will ST provide official USB drivers for ARM64 soon? I have several students with the same issue. 

[SNish]

Hello I had struggled similar things on my Lenovo YOGA slim.
It used Qualcomm X-ELITE chip as Copilot+PC Windows11.
Now I can use STLINK/V2 (NUCLEO-F446) using with Windows driver WinUSB.
But also setting is changed as OpenOCD that was built in version of CubeIDE V1.8.1.

 

[SNish]

In addition, on this case X-ELITE PC cannot update STLINK firmware now.
It should be performed on X86 machine now.
STLINK side is nothing changed and it can use both x86 machine as STLINK and XELITE machine as OpenOCD.
I have installed winusb driver as forced from unrecommend driver as above.

[S C]

Unfortunately you are not the only one suffering (I am suffering too, and I would say, perhaps at first ?). Maybe it's precisely because of big companies involving legal and business aspects over technical ones that the issue occurs and is still not solved ? The first point is that the digital signature through a third-party certificate is not accepted by Windows ARM machines to install drivers, while it works for all previous systems. Microsoft support confirmed me that it is a voluntary policy change. So the ST-Link "drivers" updated for Windows ARM64 and signed with a Digicert cross-certificate are not accepted (trusted) by Windows. The irony is that we don't install a real driver, only descriptors for a device relying on WinUSB (=Microsoft driver natively present on those machines). Then the hell is in the details of the new procedure ...

"Fortunately" this issue impacts "only" the old generations of ST-Link (V2 and V2-1). "Unfortunately" we still produce lots of boards with it. Since V3 generation we implemented another solution, but which can't be retro-actively applied to V2 and V2-1. The topic here shows also the difficulties to maintain something over decades (ST-Link/V2 = 2010) while things evolve around

[KhPaul]

Fortunately, I don’t use st-link v2 at all, my devices is st-link v3, v3 mini and v3 pwr. Have I understood you correctly, there are windows 11 arm drivers for them?

[S C]

No "driver" is required for ST-Link/V3 generation on Windows (even ARM versions). More precisely, it is not necessary to install the .inf descriptors to have the device recognized. WinUSB is expected to be natively present on Windows 11 even on ARM64 machines. The only impact is that without the .inf files, the COM port names are not customized with ST names (and keep their system-attributed standard name, which makes them more difficult to identify, I admit, but functional anyway). If you are not asking for ST-Link/V2 drivers for Windows ARM, please precise the issues you face with ST-Link/V3, most probably they are not related with the initial description of this topic

[SNish]

Thanks s c
At this moment I am using Nucleo-board for teaching seminar.
And I can use ST-LINK/V2 of this parts with ARM64/Windows11 note for debug. 
It can use with openocd gdbserver. And WinUSB driver .

I am planning to enhance seminar using with CubeMonitor and CubeProgrammer.
These tools does not accept WinUSB port.
It is current pending issue for me. (Not big issue)

 

[S C]

@SNish,

I guess you disabled some protections at windows11 level and adapted the inf files to have the ST-Link/V2 enumerated on your machine, didn't you ? If the device enumerated and works with openocd gdbserver, I think it should work also with CubeProgrammer at least (it uses the same USB interface; could be a bug at CubeProgrammer level instead). It looks like there are many different issues in this context ...