ST link error: Failed to bind to port 61235; Failure starting SWV server

[meena]

Hi I am experiencing an issue on my IDE I couldn't able to Run/Debug .However the ST Link can be communicated with the target in STM32 Cube programmer but not in STM32 cube IDE.

Console  Error:

STMicroelectronics ST-LINK GDB server. Version 7.7.0

Copyright (c) 2024, 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.

Can someone Please help me

[Andrew Neil]

Please post a legible screenshot.

[mƎALLEm]

Hello @meena ,

The image shared is not clear. So please share a better picture resolution.

Also you didn't mention which product? which board are you using? ST board? custom board? 

Are you using an external ST-LINK? if yes, is it a genuine ST-LINK?

[meena]

I am using STM32 Discovery Kit  board to program my prototype.My target have STM32G030K8 MCU. I can program hex file with STM32 Cube Programmer but not able to use STM32Cube IDE for debugging 

[Andrew Neil]

---

@mƎALLEm wrote:

Are you using an external ST-LINK? if yes, is it a genuine ST-LINK?

---

@meena see: 

https://community.st.com/t5/stm32-mcus/how-to-recognize-a-genuine-st-link-v2-versus-a-cloned-one/ta-p/49471

in particular:

https://community.st.com/t5/stm32-mcus/how-to-recognize-a-genuine-st-link-v2-versus-a-cloned-one/tac-p/703663/highlight/true#M965

---

@mƎALLEm wrote:

Also you didn't mention which product? which board are you using? ST board? custom board? 

---

@meena The article How to write your question to maximize your chances to find a solution will help you with the information to provide, and other tips ...

[meena]

I am using STM 32 Discovery Kit as my ST link it worked fine all of a sudden I am experiencing this error.

[mƎALLEm]

---

@meena wrote:

I am using STM 32 Discovery Kit as my ST link it worked fine all of a sudden I am experiencing this error.

---

Which Discovery board? please provide the exact board name.

"as my ST link it worked fine"

-> Which ST-LINK? could you please provide a photo?

[meena]

This is the board usually I use for my development and debugging STM32F407G-DISC1 .I am finding issues on working in STM CUBE IDE.I can talk to the target withSTM 32Cube Programmer.I am confused why this happening.Please help

[Andrew Neil]

Why is the board still in its plastic packaging??!

---

@meena wrote:

This is the board usually I use for my development and debugging STM32F407G-DISC1 

---

So you're using the ST-Link on the Discovery board to program/debug a custom board?
Does the ST-Link work OK for debugging the Discovery board itself?

[mƎALLEm]

As you have succeded with CubeProgrammer but not with CubeIDE. It could be something related to the debug config in CubeIDE.

This is from a STM32F4 project:

Try to check "ST-LINK S/N" check box and click on "scan" button, do you get the serial number of the ST-LINK?