Wednesday, December 13th 2017, 10:21am UTC+1

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

Fano

Beginner

Date of registration: Jun 11th 2014

Posts: 9

1

Monday, October 13th 2014, 12:52pm

[SOLVED] Debugging session with Jlink in Eclipse enviroment is not reliable

Hi all,
I'm working on a Discovery board STM32F4 with jlink+ARM Eclipse plugin+ Eclipse Luna 4.4.0 + GNU Arm toolchain.
My OS is Opensuse 13.1.

Jlink worked fine for a while, but now sometimes the debugging initialization process fails: no resume/suspend/terminate menu button are available and the cpu doesn't start.
JlinkGDBserver and other GDB thread doesn't write out to console no warning or error message.

To solve it I simply restart my systems with jlink usb cable connected; then it start to work for 1-2 hours till the same problem reappears.
I have update all Jlink software but the problem persists.

Plese help me.
Stefano

Fano

Beginner

Date of registration: Jun 11th 2014

Posts: 9

2

Tuesday, October 14th 2014, 9:39am

I know that my problem is quite unusual, but anyone has encountered the same issue?
It could be an hardware one?
_ jlink debugger broken
_ cable and contact not reliable

Or software:
_ udev, os tricks
_ eclipse
_ arm plugin
_ JlinkGDBserver limitations

Or firmware:
_ some code interrupt stops debug communication


Suggestions are welcome

Thanks
Stefano

SEGGER - Johannes

Super Moderator

Date of registration: Aug 31st 2012

Posts: 365

3

Tuesday, October 14th 2014, 10:35am

Hello Stefano,

When J-Link GDB Server starts and is able to connect to the target, J-Link and target seem to be working.
When J-Link GDB Server is waiting for a connection, it is started correctly, too.

Usually GDB Server and GDB print any output when they receive a command.

To have a look if the communication between GDB and GDB Server or GDB Server and J-Link hangs,
could you post a GDB Server logfile of a session where this problem occures?
The other possibility is that the communication between GDB and Eclipse did not work correctly.

The logfile can be set in the debugger settings of the eclipse plugin.

Best regards
Johannes

SEGGER - Alex

Super Moderator

Date of registration: Dec 18th 2007

Posts: 1,514

4

Tuesday, October 14th 2014, 3:21pm

Hi Stefano,

When you see this issue (Eclipse debug session cannot be started anymore),
what happens if you try J-Link Commander afterwards?
Is it still able to detect the J-Link + target (without restarting your system)?

Which version of the J-Link software are you using?


Best regards
Alex

rigomate

Beginner

Date of registration: Sep 5th 2014

Posts: 18

5

Thursday, October 16th 2014, 10:20am

Stefano:

Make sure you have the Initial Reset and Halt option not set.
See attachment.
rigomate has attached the following image:
  • Debug Configurations.png

Fano

Beginner

Date of registration: Jun 11th 2014

Posts: 9

6

Thursday, October 16th 2014, 1:33pm

@Rigomate:
Hi,
my Debugger init reset is on. If the problem reappears I'll try to deselect it. Thanks for that suggestion.

@Alex
Hi,
no Eclipse error windows appears, just it stops during initialization process. Eclipse remain active and CPU does not overworks.
I use JLinkExe 4.92 in linux enviroment and If the problem reappears I'll execute that command to retreive informations. Thanks!

@Johannes
Hi,
attachments contains two log file. I hope they contain the right info.

Thank all
Stefano
Fano has attached the following files:

This post has been edited 6 times, last edit by "Fano" (Oct 16th 2014, 1:47pm)


Fano

Beginner

Date of registration: Jun 11th 2014

Posts: 9

7

Thursday, October 16th 2014, 6:09pm

Hi all,
_ unsetting Initial Reset and Halt flag does not have any effect
_ JLinkExe gives me the same infomration ( see attachments )

Image of how eclipse stops is posted.

Sob...

Stefano
Fano has attached the following image:
  • screen.png
Fano has attached the following files:

This post has been edited 1 times, last edit by "Fano" (Oct 16th 2014, 6:10pm)


SEGGER - Johannes

Super Moderator

Date of registration: Aug 31st 2012

Posts: 365

8

Friday, October 17th 2014, 4:37pm

Hi Stefano,

So far the GDB Server log and the JLinkExe output look good.
The log shows that GDB Server is behaving correctly and despite from some different memory and register values both logs look identical.
It also shows that GDB Server sends the response for the last received command.

Since JLinkExe can communicate with J-Link and the target and GDB Server behaves identical,
it looks like there is a problem with eclipse or GDB which refuse to work correctly anymore.

Best regards
Johannes

Fano

Beginner

Date of registration: Jun 11th 2014

Posts: 9

9

Monday, October 20th 2014, 10:01am

Hi all.
thank you so much for your work on my problem.
I'll try to ask some advice on GNU ARM Eclipse support.

Thank you again
Stefano

Fano

Beginner

Date of registration: Jun 11th 2014

Posts: 9

10

Monday, October 20th 2014, 10:43am

Hi all,
the bug is in Eclipse Luna. Maybe downgrading to Eclipse Kepler it could work properly.

http://sourceforge.net/p/gnuarmeclipse/bugs/123/?page=0

Thank you all guys
Stefano

SEGGER - Johannes

Super Moderator

Date of registration: Aug 31st 2012

Posts: 365

11

Monday, October 20th 2014, 11:44am

hi Stefano,

Thank you for sharing the bug information.

Since there is no problem on the J-Link side, I will mark the thread as solved
and hope there will be a fix in Eclipse, soon.

Best regards
Johannes