2026-01-04 12:18 PM
Hello all,
I get an error starting a debug session from STM32CubeIDE (1.18.1) (STM32 Nucleo-F767ZI):
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
Logging Level : 1
Listen Port Number : 61234
Status Refresh Delay : 15s
Verbose Mode : Disabled
SWD Debug : Enabled
InitWhile : Enabled
Target USB comms error
Error in initializing ST-LINK device.
Reason: USB communication error. Please reconnect the ST-LINK USB cable and try again.
If I switch to SEGGER J-Link everythink works fine.
Is my debug configuration:
What I tried:
- Restart PC
- Reinstall the USB-Driver (https://www.st.com/en/development-tools/stsw-link009.html)
- Erased the flash with STM32CubeProgrammer
- Changes USB cable
- Googled for solutions
Please help
Best regards
Nikolai
Solved! Go to Solution.
2026-01-05 5:06 AM
2026-01-05 5:18 AM
I just ordered a new Nuceo-Dev-Board to exclude any hardware issues. Will take a week to arrive.
2026-01-07 9:29 AM
Hello all! Here comes the solution!
After reflashing the ST-Link debug probe with ST-Link firmware using STLinkReflash, an update by meens of STLinkUpgrade has to be conducted. STLinkUpgrade is a tool inside the CudeIDE (Help->STLinkUpgrade)(screenshot).
I suppose, the STLinkReflash (Segger Tool) ist outdated. Is has version 190812 (2019.08.12). But it is the latest version currently.
After the "uprade" debugging from the CudeIDE works fine. So switching between SEGGER J-Link und ST ST-Link is now possible.
Best regards
Nikolai
2026-01-07 10:05 AM
@NikolaiB wrote:Here comes the solution!
Thanks for that - please mark it as the solution.
@NikolaiB wrote:I suppose, the STLinkReflash (Segger Tool) ist outdated.
Please raise that with Segger:
https://forum.segger.com/board/4-j-link-flasher-related/