[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?)

[Cartu38 OpenDev]

Help > Check for Updates ... STM32CubeIDE 1.4.1 is solving trouble.​

[#3]

Thanks, this update I did right after installation. Still not working.

[HPham.1590]

Hi,

As my experience, I got the same issue when update from 1.3 to 1.4 version.

In CubeIDE 1.4, we need to install STM32Cube Programmer, I'm not sure but I think CubeIDE1.4 use Cube Programmer as default software to run task.

You can download this software here https://www.st.com/en/development-tools/stm32cubeprog.html

Hieu

[#5]

Thank you, I saw your answer just now. I had already downloaded CubeMX and Prog, it really worked. What a pity, too bad, making an IDE of this size but depends on other software.

[HPham.1590]

Cube is an ST's Ecosystem, it includes CubeIDE, CubeMX and CubeProgrammer, so I think that's business strategy =)))

Hieu

[#7]

I did some tests (following the order quoted, in sequence):

• After installing STM32CubeIDE 1.4, ST-Link V2 did not work (as mentioned above).
• After installing STM32CubeMX 6.0, STM32CubeIDE 1.4 worked with ST-Link V2 (as already mentioned above).
• After uninstalling STM32CubeMX 6.0, STM32CubeIDE 1.4 continued to work with ST-Link V2.
• After uninstalling STM32CubeIDE 1.4 and installing STM32CubeIDE 1.4 again, ST-Link V2 stopped working.
• After installing STM32CubeMX 6.0, STM32CubeIDE 1.4 still did not work with ST-Link V2.
• After installing STM32CubeProgrammer 2.5, STM32CubeIDE 1.4 still did not work with ST-Link V2.

So it's not just that yet. I did something else.

[#8]

And it still doesn't work.

I found another post with several users with the same problem:

Some say it is a matter of using HUB, but it has nothing to do with it, since version 1.3 works without problems.

https://community.st.com/s/question/0D53W00000Di9H7SAJ/stlink-not-found-when-debugging-with-stm32cubeide-140

[#9]

I found another post, citing OpenOCD.

https://community.st.com/s/question/0D50X0000BVnlm0/debugger-not-working-after-upgrade-to-stm32cubeide-110

I tried and worked the ST-Link with OpenOCD.

It seems to be a problem with GDB Server, it seems that IDE 1.4 does not work properly with GDB Server.

Download pre-built OpenOCD for Windows:

https://gnutoolchains.com/arm-eabi/openocd/

[Hchao.1]

C:\ST\STM32CubeIDE_1.3.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.win32_1.3.0.202002181050\tools\bin>ST-LINK_gdbserver.exe -d -v -e -cp "C:\ST\STM32CubeIDE_1.3.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.win32_1.3.0.202002181050\tools\bin"

use this command ,it works fine.just run the bat file,and then can debug as normal.