CubeIDE 1.18 cannot detect ST-Link anymore
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-18 7:38 AM - edited ‎2025-03-18 8:20 AM
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
Solved! Go to Solution.
- Labels:
-
STM32CubeIDE
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-20 8:06 AM
Hi,
just because i have IDE 1.18 (on my MxLinux PC) also, no problems with st-link xxx whatever -
it might be something on Win as anti-virus or something about the "rights" you or part of new program has (or not.).
So try to disable all firewall, anti-virus and check rights...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-18 7:49 AM
@funky wrote:I can flash my image via st-link utility without problems.
What about CubeProgrammer?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-18 7:50 AM
did not use it until now but will check
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-18 7:56 AM
hmmm...interesting. cubeprogrammer does not detect my st-link?!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-18 8:10 AM
this is what my device manager shows me. it is an st-link v3 but with the nucleo st-link v2 it is also not working :(
in the cubeprogrammer: when i try to upgrade my st-link it wants to downgrade the firmware.
this is the version i get via cubeprogrammer
and via stm32cubeide
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-19 4:56 AM - edited ‎2025-03-19 4:57 AM
afte rebooting i see my st-link in the cubeide programmer. but as soon as i click on it it disappears and refreshing etc does not bring it back. i tried to reinstall all the drivers, but this did not help. in cubeprogrammer and cubeIDE the st-link is not usable. with the st-link utility i can still flash.
but all in all debugging is not working anymore. i'm lost here
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-20 3:43 AM
i downgrade to cubeIDE 1.17. Also not working anymore :(
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-20 6:43 AM
still no luck.
what i noticed: cubeIDE does not even try to start GDBServer. it performas a prelaunch check and then the message box with "No St-Link connected..." appears
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-20 7:35 AM
Well, that makes sense - if it can't find any ST-Link, then there's no point in it starting a GDB server.
You haven't got anything else using the ST-Link at the same time, have you?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-20 8:06 AM
Hi,
just because i have IDE 1.18 (on my MxLinux PC) also, no problems with st-link xxx whatever -
it might be something on Win as anti-virus or something about the "rights" you or part of new program has (or not.).
So try to disable all firewall, anti-virus and check rights...
