cancel
Showing results for 
Search instead for 
Did you mean: 

ST-Link GDB Server Issues

Konami
Senior II

Out of no where, seemingly from one build to the next, CubeIDE is not able to launch GDB. I've tried a different project, a different version of the IDE, restarting my PC and no luck.

How do I debug what is going on?

STMicroelectronics ST-LINK GDB server. Version 6.1.0
Copyright (c) 2022, 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
 
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.

1 ACCEPTED SOLUTION

Accepted Solutions
Konami
Senior II

I had tried to change the port but that resulted in an error as well. It ended up working after fully shutting down my PC. Restarts were not enough. Thanks!

View solution in original post

5 REPLIES 5
Wijeden RHIMI
ST Employee

Hello @Konami 

TCP port 61234 not available:

That error appears when the TCP port by default which is 61234 is not available on debug configuration

So in this case, try to change the TCP port to 61238 for example and give me your feedback

Thanks,

Wijeden,

Wijeden RHIMI
ST Employee

Hi @DB.7ujak​ 

Any updates?

Konami
Senior II

I had tried to change the port but that resulted in an error as well. It ended up working after fully shutting down my PC. Restarts were not enough. Thanks!

Wijeden RHIMI
ST Employee

Hello @Konami

 Please mark this thread as answered by selecting Select as best, as also explained here. This will help other users find that answer faster.

Thanks,

Wijeden,

Konami
Senior II

This happened again. Changing the port changed nothing, and the Windows computer required a full shutdown