Skip to main content
Associate II
July 16, 2024
Question

No ST-LINK detected with IDE but work with CubeProgrammer

  • July 16, 2024
  • 2 replies
  • 1651 views

 

Hello,

I have a problem that I haven't been able to solve for a few days...

I have a project with a NUCLEO-F767ZI that was working a few days ago and now I can't connect to its ST-Link probe.

I instantly get the message: “No ST-LINK detected!Please connect ST-LINK and restart the debug session.”

 

I tested the following points:

  • I can connect and program with STM32CubeProgrammer
  • In Debug Configuration of STM32CubeIDE, I can scan and find my S/N probe, but nothing changes if I specify an S/N or not.
  • I've checked the firewall and, it seems I'm authorized.
  • I have uninstalled/reinstalled STM32CubeIDE and the drivers.
  • The card can be programmed on another PC with STM32CubeIDE.

 

I don't know what to test, if you have any clues to help me, I'd love to hear from you.

Thanks a lot!

    2 replies

    Andrew Neil
    Super User
    July 16, 2024

    @Armageddon wrote:
    • I can connect and program with STM32CubeProgrammer

    Do you disconnect (maybe also close) the Cube Programmer before trying with the IDE?

    A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
    Associate II
    July 16, 2024

    Yes, I disconnect and close, I didn't have STM32CubeProgrammer before.

    I installed it just to ckeck if I could connect to my board.

    Andrew Neil
    Super User
    July 16, 2024

    Please post the full Console output for when you try to start a debug session.

    Also screenshot(s) of any error pop-up(s)

    A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
    Associate II
    May 5, 2025

    was there ever found a fix for this? i have the same problem and reinstalling drivers/ide did absolultley not help!

    but i can debug if i start the gdb server manually via cmd. then everything works but it is quite annoying.