topic Re: J-Link GDB Server failed dialog in Kinetis Design Studio

J-Link GDB Server failed dialog

laszlomonda — Thu, 10 Mar 2016 15:40:43 GMT

Hi guys,

From time to time, the following error dialog appears when trying to download the firmware to an FRDM board:

This is a major productivity problem for me, because the only way to reliably recover from this error is to detach the board, exit and re-launch KDS, attach the board, and re-download the firmware. Sometimes I'm able to download the firmware about a dozen times in a row without bumping into this error, other times it occurs almost every time.

The content of the JLinkGDBServerCL console:

SEGGER J-Link GDB Server V4.98b Command Line Version

JLinkARM.dll V4.98b (DLL compiled Apr 10 2015 20:27:35)

-----GDB Server start settings-----
GDBInit file:                  none
GDB Server Listening port:     2331
SWO raw output listening port: 2332
Terminal I/O port:             2333
Accept remote connection:      localhost only
Generate logfile:              off
Verify download:               on
Init regs on start:            on
Silent mode:                   off
Single run mode:               on
Target connection timeout:     0 ms
------J-Link related settings------
J-Link Host interface:         USB
J-Link script:                 none
J-Link settings file:          none
------Target related settings------
Target device:                 MK22FN512xxx12
Target interface:              SWD
Target interface speed:        30kHz
Target endian:                 little

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link OpenSDA 2 compiled Oct 13 2015 12:10:56
Hardware: V1.00
S/N: 621000000
Checking target voltage...
Target voltage: 3.30 V
ERROR: Failed to bind address (Err = 98)
ERROR: Failed to open listener port 2331
Restoring target state and closing J-Link connection...
Shutting down...

Thank you very much in advance!

- Laci

Re: J-Link GDB Server failed dialog

ZhangJennie — Fri, 11 Mar 2016 02:55:27 GMT

Hi,

what KDS version do you work with?

do you use NXP FRDM board or external J-link tool?

Have a great day,
Jennie Zhang

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: J-Link GDB Server failed dialog

laszlomonda — Fri, 11 Mar 2016 10:06:50 GMT

Hi Jennie,

I use KDS 3.1.0 with the internal OpenSDA programming port of the FRDM boards, without an external programmer.

Thank you!

- Laci

Re: J-Link GDB Server failed dialog

ZhangJennie — Mon, 14 Mar 2016 03:59:05 GMT

Hi Laci,

from my understanding, you use FRDM-K22 board, I suggest you update your board firmware with JLink_OpenSDA_V2_1_2015-10-13.bin (see attached) then test it again.

if still can not connect, I suggest you download and install the latest J-Link software package

https://www.segger.com/jlink-software.html

Segger J-Link OpenSDA Firmware update procedure:

Disconnect all power, external circuits and USB cables.
Press and hold the button marked RESET (circled in picture)
Connect a USB cable with debug interface as shown in above picture
The drive should mount named BOOTLOADER in windows explore
The reset button can now be released
Drag and drop the file JLink_OpenSDA_V2_1_2015-10-13.bin onto the USB drive named BOOTLOADER
Repower on board normally
Jlink CDC UART Port will show up in windows device manager.
Then user can download and debug code via KDS3.0 debugger Segger J-Link OpenSDA interface.

if jlink interface can not work for you anyway, I suggest you try P&E OpenSDA. the bootloader image is also attached.

can it help you?

Have a great day,
Jennie Zhang

Re: J-Link GDB Server failed dialog

ZhangJennie — Tue, 15 Mar 2016 05:08:53 GMT

Hi,

I just wrote an article about FRDM-K22F debug interface.

Summary of FRDM-K22F debug interface

Hope this can help you.

Have a great day,
Jennie Zhang

Re: J-Link GDB Server failed dialog

bosleymusic_com — Tue, 15 Mar 2016 11:44:47 GMT

KDS 3.1.0 is suddenly failing with Segger J-Link plus - I had no problem for weeks, and all of a sudden I'm getting this :

Have tried shut down, restart, unplugging, etc... J-Link Commander works freely on its own, but still nothing with KDS. I haven't installed anything new, I haven't changed any settings, windows hasn't updated, so I don't understand how this is magically happening all of a sudden. Any suggestions?

Console Details :

GNU gdb (GNU Tools for ARM Embedded Processors) 7.6.0.20140731-cvs

License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law. Type "show copying"

and "show warranty" for details.

This GDB was configured as "--host=i686-w64-mingw32 --target=arm-none-eabi".

For bug reporting instructions, please see:

<http://www.gnu.org/software/gdb/bugs/>.

Warning: the current language does not match this frame.

/home/build/work/GCC-4-8-build/src/gdb/gdb/linespec.c:2445: internal-error: decode_line_full: Assertion `state->canonical_names[i].suffix != NULL' failed.

A problem internal to GDB has been detected,

further debugging may prove unreliable.

Quit this debugging session? (y or n) [answered Y; input not from terminal]

/home/build/work/GCC-4-8-build/src/gdb/gdb/linespec.c:2445: internal-error: decode_line_full: Assertion `state->canonical_names[i].suffix != NULL' failed.

A problem internal to GDB has been detected,

further debugging may prove unreliable.

Create a core file of GDB? (y or n) [answered Y; input not from terminal]

This application has requested the Runtime to terminate it in an unusual way.

Please contact the application's support team for more information.

Re: J-Link GDB Server failed dialog

laszlomonda — Tue, 15 Mar 2016 22:58:50 GMT

Thank you very much for your help, Jennie!

Actually, I was already using the latest J-Link OpenSDA firmware. I've given P&E a try this time but it seems that it's not better. It takes about 10 seconds to download the firmware to the board, and I get "Error in services launch sequence" error message very often.

Cheers!

Re: J-Link GDB Server failed dialog

ZhangJennie — Wed, 16 Mar 2016 07:48:01 GMT

Hi,

there is customer having similar problem as yours. he solved the problem with below thread:

arm-none-eabi-edb.exe in KDS 3.0.0 failing after J-link firmware update

can it also work for you?
Have a great day,
Jennie Zhang