It's the strangest, most frustrating thing I've encountered. I have three ST-LINK programmers; two /V2 and one /V3. All have been working fine for a good long time.
Today, CubeIDE won't program my device anymore, through any of the three programmers. Invariably, the debug console contains the following messages:
STMicroelectronics ST-LINK GDB server. Version 7.5.0
Copyright (c) 2023, 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
InitWhile : Enabled
Failed to bind to port 61235, error code -1: No error
Failure starting SWV server on TCP port: 61235
Failed to bind to port 61234, error code -1: No error
Failure starting GDB server: TCP port 61234 not available.
Shutting down...
Exit.
The "Problem Occurred" dialog appears, and the following is visible upon clicking "Details >>"
Error in final launch sequence:
Failed to start GDB server
Failed to start GDB server
Error in initializing ST-LINK device.
Reason: (0) Unknown. Please check power and cabling to target.
Bizarrely, CubeProgrammer can communicate with the target just fine, aside from this warning that appears in the log:
11:27:02 : Warning: Connection to AP 0 requested and Failed, Connection established with AP 1
I have Segger's software suite installed as well, and they all claim "no probes connected via USB".
Notably, if the JTAG cable is disconnected, the Console text changes to:
STMicroelectronics ST-LINK GDB server. Version 7.5.0
Copyright (c) 2023, 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
InitWhile : Enabled
Target unknown MCU target
Error in initializing ST-LINK device.
Reason: Unknown MCU found on target.
...and the Problem Occurred Details changes to this:
Error in final launch sequence:
Failed to execute MI command:
target remote localhost:61234
Error message from debugger back end:
localhost:61234: Connection timed out.
Failed to execute MI command:
target remote localhost:61234
Error message from debugger back end:
localhost:61234: Connection timed out.
localhost:61234: Connection timed out.
J-Link just keeps saying no probes connected via USB.
This has happened across two prototypes of my project involving an STM32H563ZI microcontroller, and is a new issue as of this morning.
What's going on? More importantly, how do I fix it? I'm dead in the water if I can't debug my code.
