Skip to main content
SoonuVerma
SoonuVerma
Associate II
Oct 29, 2026 7:59 AM UTC
Question

STM32CubeIDE 2.2.0 – Local ST-LINK GDB Server launch fails with “No ST-LINK detected!”, but manual and remote debugging work

Hello ST Community,

I am troubleshooting a local debugging issue with the STM32N6570-DK (MB1939C) using STM32CubeIDE 2.2.0 on Windows 11.

Environment

  • Board: STM32N6570-DK / MB1939C

  • IDE: STM32CubeIDE 2.2.0

  • ST-LINK GDB Server: v7.14.0

  • Debug interface: SWD

  • Debug access port: AP1 – Cortex-M55

  • Connection: ST-LINK USB directly connected to the PC

Problem

When I start a normal local ST-LINK GDB Server debug session from CubeIDE, I encounter the popup:

“ST-LINK firmware verification – No ST-LINK detected!”

However, STM32CubeProgrammer can connect to the board and successfully read, erase, and program the target.

Tests already completed

  1. STM32CubeProgrammer detects the ST-LINK and communicates with the target successfully.

  2. Manually launching the same ST-LINK_gdbserver.exe command used by CubeIDE works and reaches “Waiting for debugger connection…”.

  3. Connecting CubeIDE using a remote GDB server configuration (127.0.0.1:61234) works.

  4. The GDB server listens on TCP port 61234, and arm-none-eabi-gdb.exe clients establish connections.

  5. Windows enumerates the ST-LINK USB composite device. Its debug interface uses WinUSB and its VCP interface uses usbser.

  6. The local launch command uses the GDB server and CubeProgrammer executables installed with CubeIDE.

Questions

  1. Can the “No ST-LINK detected!” message originate from the ST-LINK firmware verification utility or a pre-launch check, rather than from ST-LINK_gdbserver.exe itself?

  2. Is there a recommended diagnostic log or configuration setting to identify which executable or plugin returns this error?

Since manual GDB server startup and remote debugging both work, I suspect the issue is in CubeIDE's local debug launch or ST-LINK verification sequence rather than basic USB connectivity.

I would appreciate any guidance on how to isolate the failing component without reinstalling CubeIDE or changing the working ST-LINK drivers.

Thank you.

Terms & ConditionsAccessibility statement