Anthony Huereca

KDS 3.0 and KSDK 1.3 Eclipse Update

Discussion created by Anthony Huereca Employee on Nov 2, 2015

Hello KDSK and KDS users!

There's been some reports of issues after updating KDS 3.0 with the KSDK 1.3 Eclipse Plugin. You may get the following error when debugging using CMSIS-DAP/OpenOCD or JLink:


"An internal error occurred during "Launching hello_world_frdmk64f debug cmsisdap". ilg.gnuarmeclipse.debug.gdbjtag.dsf.GnuArmServicesFactory <init>(Ljava/lang/String;Ljava/lang/String;)V"



The reason this occurs is when the KSDK 1.3 Eclipse Update is installed on a fresh KDS 3.0 installation, KDS also asks to update several other components during the update install process. Unfortunately two of those debugging components that are updated cause the debugger to stop working as they conflict with other components of KDS. If you already see this issue on your computer, the work-around is to over-write those two debugger components with their original versions, which can be found in the file Erich Styger provided in this thread: Re: Unable to Debug after KDS Update 




However to avoid this issue in the first place, use the Help->"Check for New Updates" menu to ONLY update the Processor Expert for Kinetis item. That's the only required component, and the most important thing is that the debugging components aren't updated.

kds-select - Copy.PNG


and then install the (as described in the Getting Started with Kinetis SDK Guide in Section 5.2) afterwards.




So the steps would be:

1) Install KDS 3.0

2) Go to Help->Check for New Updates

3) Only select the Processor Expert for Kinetis item to update it to 3.0.1

4) Finish the Update process

5) Install Kinetis SDK 1.3

6) Install the KSDK 1.3.0 Eclipse (using the steps described in Section 5.2)