Hi,
i am using stm32IDE if i entering into debug mode getting this error please help me to crack this.
Failed to bind to port 61234, error code -1: No error
Failure starting GDB server: TCP port 61234 not available.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-02-14 6:52 AM
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-10-14 5:55 AM
I could fix it by restarting my PC. apparently the GDB server needed a restart
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-05-22 7:17 AM
me to
CubeIDE win10
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-10-14 5:40 AM
Me too
It just happend and I don't know how.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-10-14 5:47 AM
downloaded 1.4.0
installed it
ran 1.4.0
compiled latest program
0 errors 0 warnings
Check for upgrade
upgraded to 1.4.2
Compiled current program
0 errors 0 warnings
Click Debug
LED turned red
No other indication
Help -> ST Link Upgrade
refresh list
open in upgrade mode
upgrade successful
LED still red
COM port shows up, but teraterm cannot connect to it
Click Debug
and get the error message
Error in final launch sequence:
Failed to start GDB server
Failed to start GDB server
Error in initializing ST-LINK device.
Reason: (-1) Unknown. Please check power and cabling to target.
look at comsole
STMicroelectronics ST-LINK GDB server. Version 5.6.0
Copyright (c) 2020, 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 61234, error code -1: Result too large
Failure starting GDB server: TCP port 61234 not available.
Try again to debug
0 errors 0 warnings
pop up saying newer version of ST Link available Upgrade? YES
Open in upgrade mode
Unexpected error during opening (1)
Device 0672FF534953867067064047 not found. No device connected.
this is on two Nucleo-STM32F401RE boards
How do I fix both boards so they can communicate again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-10-14 5:55 AM
I could fix it by restarting my PC. apparently the GDB server needed a restart
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-10-14 10:43 AM
I tried restarting my PC and it WORKED. I guess Windows doesn't like being up for 2 months. :)
Thanks for the suggestion.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-01-15 12:40 AM
I encountered the same. The problem was that the link server was still running in the background. I used the Task Manager to kill it, restarted STM32CubeIDE, and it worked again without the need of rebooting my PC.
C:\Program Files (x86)\STMicroelectronics\stlink_server\stlinkserver.exe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-02-15 2:02 AM
Hi all,
Instead of restarting the PC, connecting to St board or MCU with ST-Link Utility and erasing the chip before loading the code helps too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-03-30 5:08 AM
Restart the PC works fine after an upgrade.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-09-14 7:10 PM
Changing port number might help. I changed the port number of GDB server from 61234 to 41234 in debug configurations, and it worked without rebooting my computer.
