ST-Link debug not working

Discuss how to use the features of Atollic TrueSTUDIO, including the editor, assembler, C/C++ compiler, linker, debugger, static code analysis and team collaboration tools.

Moderators: Markus Girdland, Mattias Norlander

gorillagrunt
Posts: 3
Joined: Sat Jan 19, 2019 8:39 pm

Re: ST-Link debug not working

Postby gorillagrunt » Mon Jan 21, 2019 6:26 pm

I have instead the following problem:
failing to bing to port 61234, error code -1:Result too large
failure starting GDB Server: TCP Port 61234 not available
GDB Server exited

Could please someone help me??
Drivers are up to date and firewall is allowing the gdbserver

hazem
Posts: 1
Joined: Wed Jan 30, 2019 12:17 pm

Re: ST-Link debug not working

Postby hazem » Wed Jan 30, 2019 2:41 pm

sztefano wrote:Hi,

I'm using recent Atollic Lite version (5.4). I've got some problems with stm32 discovery/nucleo boards (i've checked on stm32f0 and stm32f411) and ST-Link debug probe:

Atollic TrueSTUDIO gdbserver for ST-Link. Version 2.2.0 Pro
Copyright 2010-2015, Atollic AB.


Starting server with the following options:
Persistant Mode : Disabled
LogFile Name : debug_log.txt
Logging Level : 1
Listen Port Number : 61234
Status Refresh Delay : 15s
Verbose Mode : Disabled
SWD Debug : Enabled

Connecting to the ST-Link Debugger... OK
Waiting for debugger connection...

And nothing more happens. I haven't got any virtual drives in my computer.I've tried also disabling firewall etc. I'm running win7 64bit, ST-Link with upgraded firmware.
Any hints what could be wrong ?


this issue may be in different things that you can check as follows
1-check the option bytes you may be disabled the SWD communication by accident
2-check the debug configuration as autostart local GDB server and SWD interface
3-check the wiring :oops:

gorillagrunt
Posts: 3
Joined: Sat Jan 19, 2019 8:39 pm

Re: ST-Link debug not working

Postby gorillagrunt » Sun Feb 03, 2019 1:28 pm

Thanks a lot,
i have checked the flags and the wiring.
Actually if I launch Run->Debug something happens but it too fast, when I go on the debug configuration and then launch the debugging everything starts to work, is going on the debug perspective but it stops at 96% and it doesn't go further.

I've tried with the STLink Utility, and at least it is possible to connect to the board.

No idea on what is wrong!
Thanks a lot

mhnasseri
Posts: 3
Joined: Wed Feb 20, 2019 9:38 am

Re: ST-Link debug not working

Postby mhnasseri » Wed Feb 20, 2019 10:05 am

Hi,
I have the same problem. any solution? :|

anaisiou
Posts: 4
Joined: Tue Mar 26, 2019 10:06 am

Re: ST-Link debug not working

Postby anaisiou » Tue Mar 26, 2019 10:26 am

Hi,

I have the same issue,
Please see attached picture,

Thanks for your advice and for your help,

Have a great day,
kindly
anais
You do not have the required permissions to view the files attached to this post.

charles.custon
Posts: 2
Joined: Mon Apr 01, 2019 5:17 pm

Re: ST-Link debug not working

Postby charles.custon » Mon Apr 01, 2019 5:22 pm

I was having an issue where I couldn't debug from Truestudio 9.1.1 nor 9.3.0. Eventually found that changing the port number worked. The root cause for me, was that I installed a program called conferencing program Mikogo, which opened the same port number, 61234, for one of its services.

From an elevated command prompt, try this:
"netstat -ano | findstr :61234"

The results will indicate if there is a program "listening" on that port, AND the process number (PID) that opened it. The PID can be correlated to a process name in the "Details" tab of "Task Manager".

So in my case, it was conflict between programs. Hope that helps someone.

-Charles

anaisiou
Posts: 4
Joined: Tue Mar 26, 2019 10:06 am

Re: ST-Link debug not working

Postby anaisiou » Tue Apr 02, 2019 6:13 am

Hi Charles,

Thanks for your answer,

Strangely, when I try to execute the command it said "impossible to open 61234"
Thanks for your help,

Kindly,
Good day,
anais
You do not have the required permissions to view the files attached to this post.

charles.custon
Posts: 2
Joined: Mon Apr 01, 2019 5:17 pm

Re: ST-Link debug not working

Postby charles.custon » Tue Apr 02, 2019 7:20 am

Hi Anais,
Your image shows "/ano" instead of "-ano".

anaisiou wrote:Hi Charles,

Thanks for your answer,

Strangely, when I try to execute the command it said "impossible to open 61234"
Thanks for your help,

Kindly,
Good day,
anais

anaisiou
Posts: 4
Joined: Tue Mar 26, 2019 10:06 am

Re: ST-Link debug not working

Postby anaisiou » Tue Apr 02, 2019 7:25 am

and if I run the bat STLin gdb server , here below the result :

Starting server with the following options:
Persistent Mode : Enabled
LogFile Name : debug.log
Logging Level : 31
Listen Port Number : 61234
Status Refresh Delay : 15s
Verbose Mode : Disabled
SWD Debug : Enabled

Hardware watchpoint supported by the target
SWD frequency = 4000 kHz
ST-LINK Firmware version : V2J31S21
Device ID: 0x437
PC: 0x8000138
ST-LINK device status: HALT_MODE
ST-LINK detects target voltage = 3.25 V
Enter STM32_AppReset() function
NVIC_DFSR_REG = 0x00000009
NVIC_CFGFSR_REG = 0x00000000
XPSR = 0x01000000
ST-LINK device status: HALT_MODE
ST-LINK device initialization OK
Failed to bind to port 61234, error code -1: No error
Failure starting GDB server: TCP port 61234 not available.
GDB server exited
You do not have the required permissions to view the files attached to this post.

anaisiou
Posts: 4
Joined: Tue Mar 26, 2019 10:06 am

Re: ST-Link debug not working

Postby anaisiou » Tue Apr 02, 2019 8:08 am

Hi Charles,

If I do -ano, nothing happens :/

thanks :)
You do not have the required permissions to view the files attached to this post.


Return to “Atollic TrueSTUDIO tool discussions”

Who is online

Users browsing this forum: MSN [Bot] and 2 guests