KL03Z4 OpenSDA Segger Error in Final Launch Sequence

[alexklimaj]

Hello,

I am struggling to get the KL03Z4 working with OpenSDA Segger. When I go to load the application onto the device, I get the following error. 

I have the following debug configuration. 

[alexklimaj]

Erich,

I can start JLinkGDBServerCL.exe manually. 

I can succesfully use jlink debugging with the provided examples in the SDK. And I have matched the debugging profile settings exactly for my project, but I get that error. 

arm-none-eabi-gdb is not already running when I go to debug. 

With PNE, I am able to load programs on just fine, but the serial output is very spotty and hard to get to connect. I would much rather use Segger as the serial output is more reliable. 

[Carlos_Mendoza]

Hi Alex,

I see you mention that this problem is not present with the SDK examples, is it present if you create a new project with the SDK 2.x project wizard? Or the problem is specific to that project only?:

Thanks in advance for your response!

Best Regards,
Carlos Mendoza
Technical Support Engineer

[BlackNight]

Hello,

your settings are looking ok. One possible reasons is that it cannot start the Segger J-Link command line executable, which is <KDS installation path>\segger\JLinkGDBServerCL.exe. Can you check that this executable is present and if you can start it manually?

Another reason could be that there is already the arm-none-eabi-gdb excecutable running somehow. Can you check in your task mananager and if yes, kill it?

Other possible tips are listed here: Debugging Failure: Check List and Hints | MCU on Eclipse 

I hope this helps,

Erich