[BUG] St-Link is not detected after installing STM32CubeIDE V 1.4.0.

[#1]

I was normally using STM32CubeIDE V 1.3.0 and St-Link was working.

The St-Link firmware is updated.

The St-Link Utility (V 4.4.0.0 and V 4.5.0.0) finds and connects to the St-Link correctly.

Whenever a new IDE version becomes available, will the user have to ask for help to make St-Link work? :|

Can the IDE itself update St-Link? (Or at least report the problem correctly?)

[Hchao.1]

[#3]

I think version 1.4 is different, it doesn't have all these files.

[#4]

Ah got it, you copied the STM32CubeProgrammer files

[#5]

I was not lucky with that, I used IDE 1.4 files

[#6]

Note: found the STM32_Programmer_CLI.exe file inside the IDE too

[Hchao.1]

you can install v1.3.0, then update to 1.4.2

[LaurentL]

You must install v1.4.0 with cubeide installer to have the STLink server installed correctly.

If you update from v1.3.0, the stlink server won't be installed, only plugins will be updated to v1.4.0

If it is still not working after fresh 1.4.0 install, a problem with libusb.dll included in STM32CubeIDE v1.4.x has been identified.

The issue is seen on some usb HUB port on windows.

See forum post

https://community.st.com/s/question/0D73W0000004aNn/bug-stlink-firmware-verification-no-stlink-detected-message-since-14x-update?s1oid=00Db0000000YtG6&s1nid=0DB0X000000DYbd&emkind=chatterCommentNotification&s1uid=0050X0000089LW0&emtm=1598457168832&fromEmail=1&s1ext=0

You can find the latest libusb dll v1.0.23 for windows.

This can be patched in stlink server to solve problem with ST-LINK GDB server AND it shall be patched in openocd plugin to solve issue with OpenOCD.