2025-11-12 4:36 AM - last edited on 2025-11-12 4:43 AM by Andrew Neil
This does not happen in CubeIDE 1.15.1 and the solution suggested in this post does not work either.
How can I fix this issue?
Thanks in advance,
Gaston
2025-11-12 4:45 AM
It says, "Connection failed" - can you do anything else in the debugger?
2025-11-12 4:45 AM - edited 2025-11-12 4:46 AM
Hello @Gaston
Could you please share your Debug configuration, or your Log file?
KR, Souhaib
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2025-11-13 5:08 AM
Where is the Log file?
Here's the Output Console
STMicroelectronics ST-LINK GDB server. Version 7.11.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
Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
-------------------------------------------------------------------
STM32CubeProgrammer v2.20.0
-------------------------------------------------------------------
Log output file: /tmp/STM32CubeProgrammer_RyEdAC.log
ST-LINK SN : 52FF70064980515749250487
ST-LINK FW : V2J46S7
Board : --
Voltage : 3,19V
SWD freq : 4000 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x443
Revision ID : Rev Z
Device name : STM32C01x
Flash size : 16 KBytes
Device type : MCU
Device CPU : Cortex-M0+
BL Version : 0x51
Opening and parsing file: ST-LINK_GDB_server_xCzbYs.srec
Memory Programming ...
File : ST-LINK_GDB_server_xCzbYs.srec
Size : 12.82 KB
Address : 0x08000000
Erasing memory corresponding to segment 0:
Erasing internal memory sectors [0 6]
Download in Progress:
File download complete
Time elapsed during download operation: 00:00:00.480and the Debug Configuration
Gaston
2025-11-13 8:08 AM
Just check "Log to file" in debug configuration so you can find your log.
Could you try to test with OpenOCD and check if the issue persists?
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2025-11-17 12:12 AM - edited 2025-11-17 12:12 AM