topic Re: KDS3.2 Configuring GDB Aborting configuring GDB in Kinetis Design Studio

KDS3.2 Configuring GDB Aborting configuring GDB

PO220 — Wed, 04 May 2016 14:29:40 GMT

I use successfully KDS3.1 after a few bugs as this one, solved

https://community.freescale.com/thread/386356?et=watches.email.thread#618818

Today, I install KDS 3.2 whitch fixe the bug in debug Configurations/debugger/GDB ClientSettings/commands

but I'm always blocked at the same stage !!!

old workspace + old project -> Configuring GDB Aborting configuring GDB (Lauching Test_Debug_PNE : (100%)

old workspace + new project -> Configuring GDB Aborting configuring GDB (Lauching Test_Debug_PNE : (100%)

new workspace + new project -> Configuring GDB Aborting configuring GDB (Lauching Test_Debug_PNE : (100%)

It's the same with OpenSda + FRDM_K64 and with Multilink Universal (the green one) + KL17

It's the same with 2 defferent computer (windows 7)

it's the same after changing USB port, reboot...

No hardware problem : with CW10.6, all is working well :-(

Thanks in advance

Re: KDS3.2 Configuring GDB Aborting configuring GDB

BlackNight — Wed, 04 May 2016 16:38:44 GMT

Hi David,

can you check your lauch configuration as shown/discussed in https://community.freescale.com/thread/386356?et=watches.email.thread#618818 ? Because if you have such a launch configuration with wrong line endings (e.g. created by the previous version), then it still will fail in 3.2.0 because the launch configuration is wrong.

I hope this helps,

Erich

Re: KDS3.2 Configuring GDB Aborting configuring GDB

BlackNight — Thu, 05 May 2016 08:53:13 GMT

Hi David,

in addition to that, see https://mcuoneclipse.com/2016/03/11/solving-launching-configuring-gdb-aborting-configuring-gdb/

I hope this helps,

Erich

Re: KDS3.2 Configuring GDB Aborting configuring GDB

PO220 — Thu, 05 May 2016 09:23:22 GMT

It's not a launch configuration with wrong line endings; I find first the solution here https://community.freescale.com/thread/386356?et=watches.email.thread#618818 and KDS 3.2 fixe this bug.

I solved the new problem this morning by updating some software from eclipse.

I think this is the GNU ARM update which solved the problem but my children are distracted me... I'm not sure of the good update, sorry.

Thank you

Re: KDS3.2 Configuring GDB Aborting configuring GDB

PO220 — Wed, 11 May 2016 16:50:51 GMT

Same problem with an other PC

After instalaltion, problem solved with update of

GNU ARM Eclipse Plug-ins - http://gnuarmeclipse.sourceforge.net/updates

and (/or)

PEMicro - http://www.pemicro.com/eclipse/updates

Re: KDS3.2 Configuring GDB Aborting configuring GDB

kecart — Thu, 08 Sep 2016 17:12:18 GMT

I am experiencing a similar problem with Configuring GDB Aborting configuring GDB. In my case, I have updated the toolchain from the KDS default 4.8.4 to the latest released 5.4.1 version available at Launchpad.net. Everything compiles and builds correctly but the debugger hangs. As a workaround, I replaced the arm-none-eabi-gdb.exe with the older 4.8.4 version and everything seems to work so far. There appears to be some incompatibility between KDS 3.2.0 and the 5.4.1 version of arm-none-eabi-gdb.exe. #GDB Aborting

Re: KDS3.2 Configuring GDB Aborting configuring GDB

kecart — Fri, 09 Sep 2016 19:12:30 GMT

Further information regarding the use of toolchain version 5.4.1. Using the arm-none-eabi-gdb.exe from 4.8.4 does allow the debugger to get past the Aborting configuring GDB error but the task aware FreeRTOS plugin no longer works. It shows FreeRTOS not detected in the associated windows. I was using the FRDM-K64F with PE version of OpenSDA. I changed the OpenSDA to the Segger JLink version with similar results. The plugin still does not detect the FreeRTOS.

Can anyone tell me what the plugin is looking for? I am wondering if it may be a name mangling issue with C++ where the plugin is looking for a symbol that is mangled.

Re: KDS3.2 Configuring GDB Aborting configuring GDB

kecart — Fri, 09 Sep 2016 21:00:02 GMT

Last note of the day. The reason it could not detect FreeRTOS was because some variables in tasks.c and heap_x.c were defined as static and the c++ compiler mangled the names. Removing the static qualifier fixed that. Now the 4.8.4 gdb works reasonably well with the 5.4.1 toolchain and does work with the FreeRTOS debug plugin. :smileyhappy:

Re: KDS3.2 Configuring GDB Aborting configuring GDB

BlackNight — Sat, 10 Sep 2016 11:06:34 GMT

Hi Kelly,

FreeRTOS is written in C, so I'm not sure why you say it mangeled the symbols as they are declared with "C" linkage.

But yes, it requires symbols for detection which heap is used, see https://mcuoneclipse.com/2016/07/06/freertos-kernel-awareness-for-eclipse-from-nxp/

Same for the Segger FreeRTOS Thread awareness (https://mcuoneclipse.com/2016/07/06/freertos-kernel-awareness-for-eclipse-from-nxp/ ) which needs some symbols available.

Which symbols were missing on your side, or can you provide details what problem you saw?

Thanks,

Erich