Skip to main content
Visitor II
April 22, 2023
Solved

ST-Link GDB Server Issues

  • April 22, 2023
  • 5 replies
  • 8702 views

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.

    This topic has been closed for replies.
    Best answer by Konami

    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!

    5 replies

    ST Employee
    April 24, 2023

    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,

    ST Employee
    April 26, 2023

    Hi @DB.7ujak​ 

    Any updates?

    KonamiAuthorAnswer
    Visitor II
    April 26, 2023

    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!

    ST Employee
    April 26, 2023

    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,

    KonamiAuthor
    Visitor II
    May 3, 2023

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