topic Using KDS with USBDM in OSBDM and TBDML

Using KDS with USBDM

gustavsl — Tue, 24 Mar 2015 18:52:49 GMT

Hi, I've managed to install and run KDS with USBDM and configure it successfully. I'm running a Ubuntu Server installation.

However, when I try to run (or debug) an application, there's an error in the final launch sequence:

Error in final launch sequence

Failed to execute MI command:

monitor reset halt

Error message from debugger back end:

"monitor" command not supported by this target.

Failed to execute MI command:

monitor reset halt

Error message from debugger back end:

"monitor" command not supported by this target.

I have GDB installed on KDS.

What could it be?

Thanks.

Re: Using KDS with USBDM

kerryzhou — Thu, 26 Mar 2015 05:09:40 GMT

Hi Gustavo leal,

Could you tell me the full name of you chip?

What the detail operation system you are using? You can try it in windows 7 system, it can works ok.

You should make sure your USBDM can works in your platform.

About the configuration, you can refer to this link and check it again:

USBDM Functions in Eclipse (including Kinetis Design Studio)

Regards,

Jingjing

Re: Using KDS with USBDM

gustavsl — Thu, 26 Mar 2015 16:04:43 GMT

Hi. I'm using the MKL26Z64.

I'm running it on a Ubuntu 14.04 server with XFCE.

I managed to partially solve the problem.

One of the libraries required to launch the USBDM ARM GDB Server (libwx_gtk2u-unnoficial) was missing. I installed this library and tcl-8.5 and the GDB server launched.

Now I can flash the chip using the ARM Flash Programmer application, but I still can't do it from inside KDS.

Thanks,

Gustavo.

Re: Re: Using KDS with USBDM

kerryzhou — Fri, 27 Mar 2015 01:47:28 GMT

Hi Gustavo Leal,

From the kds_user_guide.pdf, it need ubuntu14.04 LTS,

So, maybe KDS in your ubuntu 14.04 with XFCE will have problem, you should better working in the operation system which KDS defined.

At least, when I working in Window7 ,USBDM can works ok.

Regards,

Jingjing

Re: Using KDS with USBDM

andrewmeyerbti — Wed, 09 Jun 2021 18:43:09 GMT

In my case I get that all the time when I have too many breakpoints enabled. Using KE06 chips that is two, and since you need 1 for main . . . I also get it if one of the breakpoints is not able to be properly set.