CubeIDE 1.18 cannot detect ST-Link anymore

[funky]

Hi,

starting with Update 1.18  (update from 1.17) sth. broke and i cannot debug anymore.
I tried a nucleo Board with integrated St-Link and an ST-Link V3. All Screenshots were done with the v3 St-Link
I reinstalled CubeIDE already from the complete download-package, but still the same problem

i always get

But the update works ( so my st-link is found)

I can flash my image via st-link utility without problems.

but cannot get debug to work with 1.18.

With v1.17 i had no problems at all and debugging worked flawlessly.

So what can i do to fix this?

i tried with stlink-v3 and v2.1

and i use Windows 11 Enterprise
Regards

[funky]

nope, nothing. 

And as said...in the debugging configuration the IDE detects my st-link. But it is not usable when i want to debug.

I'm out of ideas

I downgraded the IDE, uninstalled all (old) drivers/devices in the device manager, nothing helps 

[Andrew Neil]

Show the console log from when CubeIDE tries to start a debug session.

[funky]

the firewall was the problem. i deleted all cubeide entries in the firewall and when i started the IDE there was a firewall message that gdb server wants to connect. i just accepted that. same problem...no connection

now i deleted the entries in the firewall and checked again. in the defaults there weren't all networks selected/allowed. i selected everything and accepted and suddenly my gdb server is started again and i can debug.
now i also see my st-link in the programmer again

[AScha.3]

good !

[Andrew Neil]

So same issue as here: https://community.st.com/t5/stm32cubeide-mcus/st-link-error-failed-to-bind-to-port-61235-failure-starting-swv/m-p/784642 ?

Did you not get any error messages like that one?

[funky]

No, the whole gdb-server start output was missing

I did not see the whole startup output. As soon as i pressed the debug button the message box with the missing st-link notice appeared and none of the gdb server output

i don't know what triggered my firewall to behave like this. Because i'm pretty sure when i first installed cubeIDE in the past i did not hit any extra checkboxes in the firewall configuration. 
And my colleagues who also use cubeIDE 1.18 did not have these problems and everything worked flawlessly after the update

[funky]

ok, i'm starting to cry. monday morning in the office. same problem again.

no st-link found, no gdbserver started.  (on friday i was at home so little different network setup)

[funky]

ok... it seems the autostart of the gdb server does not work anymore. i absolutley do not know why.

in the debugger configuration there is the "show command line" button for the gdb server start. if i copy that command and start it manually via commandline i get another firewall popup for my gdb server, i accept that and my gdb server is started and listening for connection. when i configure my settings to connect to a remote gdb server with that port everthing works fine i can start my program and debug.

when i switch back to autostart local gdb server, nothing is started i get the no st-link connected message instantly

[funky]

after starting that gdb server manually it worked one time and now i switched back to automatic start and i get after reboot this logoutput ONCE

STMicroelectronics ST-LINK GDB server. Version 7.10.0

Copyright (c) 2025, STMicroelectronics. All rights reserved.



Starting server with the following options:

Persistent Mode : Disabled

LogFile Name :...\st-link_gdbserver_log.txt

Logging Level : 31

Listen Port Number : 6124

Status Refresh Delay : 15s

Verbose Mode : Enabled

SWD Debug : Enabled

ST-Link enumeration failed

Error in initializing ST-LINK device.

Reason: ST-LINK DLL error.

and the next try the "NO ST-Link detected" message box is back again.

this is *^°?!#111 :D

[AScha.3]

Hi,

so : > 

Reason: ST-LINK DLL error.

Just try:

close IDE ; 

load/install (actual) STM32CubeProgrammer , check connection to board (maybe : update st-link);

then try IDE again.