cancel
Showing results for 
Search instead for 
Did you mean: 

stlink-gdb-server and Nucleo-H73SL8

Uwe Bonnes
Principal III

While "ST-LINK_gdbserver -d -v --frequency 1000 -cp ..." connects fine to STM32U083C-DK, NUCLEO-H7SL8 does not work.

STMicroelectronics ST-LINK GDB server. Version 7.7.0
Copyright (c) 2024, STMicroelectronics. All rights reserved.

Starting server with the following options:
Persistent Mode : Disabled
Logging Level : 31
Listen Port Number : 61234
Status Refresh Delay : 15s
Verbose Mode : Enabled
SWD Debug : Enabled

COM frequency = 1000 kHz
Target connection mode: Default
Target connection failed. Try connecting under reset
Target connection failed
Target unknown error 32

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

 

I lowered the frequency even much lower so frequency  should be no problem. StCubeProgrammer connects fine. Stlink firmware is from stsw-link007-v3-15-6.zip

Has anybody success with this combination? Any hints?

1 ACCEPTED SOLUTION

Accepted Solutions
CMYL
ST Employee

Hello @Uwe Bonnes,

 

I got the same issue by running your command, then I added the -m option and it is connecting. I loaded a GPIO toggle project into the flash and I can see it is running.

Try the following command and let me know if it is working:

 

>ST-LINK_gdbserver --swd  -cp "C:\ST\STM32CubeIDE_1.15.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.1.200.202311302303\tools\bin" -m 1

 

 

 Output is: 

 

STMicroelectronics ST-LINK GDB server. Version 7.6.0
Copyright (c) 2024, STMicroelectronics. All rights reserved.

Starting server with the following options:
        Persistent Mode            : Disabled
        Logging Level              : 31
        Listen Port Number         : 61234
        Status Refresh Delay       : 15s
        Verbose Mode               : Disabled
        SWD Debug                  : Enabled

COM frequency = 24000 kHz
Target connection mode: Default
Reading ROM table for AP 1 @0xe00fefd0
Hardware watchpoint supported by the target
ST-LINK Firmware version : V3J14M5
Device ID: 0x485
PC: 0x8004094
ST-LINK device status: HALT_MODE
ST-LINK detects target voltage = 3.28 V
ST-LINK device status: HALT_MODE
ST-LINK device initialization OK
Stm32Device, pollAndNotify running...
SwvSrv state change: 0 -> 1
Waiting for connection on port 61235...
Waiting for debugger connection...
Waiting for connection on port 61234...
ST-LINK device status: RESET_MODE
ST-LINK device status: RUN_MODE

 

 

best regards,

Younes

View solution in original post

2 REPLIES 2
CMYL
ST Employee

Hello @Uwe Bonnes,

 

I got the same issue by running your command, then I added the -m option and it is connecting. I loaded a GPIO toggle project into the flash and I can see it is running.

Try the following command and let me know if it is working:

 

>ST-LINK_gdbserver --swd  -cp "C:\ST\STM32CubeIDE_1.15.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.1.200.202311302303\tools\bin" -m 1

 

 

 Output is: 

 

STMicroelectronics ST-LINK GDB server. Version 7.6.0
Copyright (c) 2024, STMicroelectronics. All rights reserved.

Starting server with the following options:
        Persistent Mode            : Disabled
        Logging Level              : 31
        Listen Port Number         : 61234
        Status Refresh Delay       : 15s
        Verbose Mode               : Disabled
        SWD Debug                  : Enabled

COM frequency = 24000 kHz
Target connection mode: Default
Reading ROM table for AP 1 @0xe00fefd0
Hardware watchpoint supported by the target
ST-LINK Firmware version : V3J14M5
Device ID: 0x485
PC: 0x8004094
ST-LINK device status: HALT_MODE
ST-LINK detects target voltage = 3.28 V
ST-LINK device status: HALT_MODE
ST-LINK device initialization OK
Stm32Device, pollAndNotify running...
SwvSrv state change: 0 -> 1
Waiting for connection on port 61235...
Waiting for debugger connection...
Waiting for connection on port 61234...
ST-LINK device status: RESET_MODE
ST-LINK device status: RUN_MODE

 

 

best regards,

Younes

Thanks, that did the trick!