STM32H563ZI: Error in initializing ST-Link for GDB Server

[Engineer0815]

Dear all,

 

I want to evaluate a STM32H5 (NUCLEO-H653ZI) via the built in STLink (ST-LINK FW: V3J16M7). I use VS Code with STM32CubeCLT_1.18.0 as IDE and control the flashing and debugging with a .json.

 

Checking the STLink connection to the board by executing “<Path>\STM32_Programmer_CLI.exe –list” works fine.

 

Also, flashing the board and running a simple LED toggle application by executing “<Path>\STM32_Programmer_CLI.exe --connect port=swd --download <Path>\H563ZI_Test.elf -hardRst” works just fine.

 

When trying to start the GDB server for debugging by executing “<Path>\ ST-LINK_gdbserver.exe -p 50000 -cp <Path>\STM32CubeProgrammer\bin --swd –halt” an error occurs and the debug process is terminated:

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        : 50000
        Status Refresh Delay      : 15s
        Verbose Mode              : Disabled
        SWD Debug                 : Enabled

Target unknown error 32

Error in initializing ST-LINK device.
Reason: Unknown. Please check power and cabling to target.

Is this a known problem with the STM32H5? How to  

Best Regards

[vincent_grenet]

​@Engineer0815 

STM32CubeCLT is no longer used with STM32CubeIDE for VS Code. STM32Cube bundles now provide all back-end components. STM32CubeIDE for VS Code is self-contained and fully integrated. No additional components are required.

To have a try resolving the error that occurs during STLINK device initialization, update the STLINK firmware. 

Note: According to the shared information, STLINK GDB server version 7.10.0 is in use. That version is acceptable. However, if not forcing STM32CubeCLT usage, version 7.14.0 is available. Version 7.14.0 is less sensitive to STLINK versions. Let’s enjoy bundle system ! See