topic Re: Cannot debug FDRM-K64F via J-link. in MCUXpresso IDE

Cannot debug FDRM-K64F via J-link.

geraldhilderink — Wed, 22 Mar 2017 22:56:00 GMT

I am using a FDRM-K64F board and I cannot debug with MCUXpresso IDE via J-Link (USB). I get a "Cannot get Jtag device" error. It worked fine with the Kinetis Designer IDE. The debug configuration is set to SWD.

Any idea what the problem can be?

Re: Cannot debug FDRM-K64F via J-link.

BlackNight — Thu, 23 Mar 2017 09:19:31 GMT

Hi Gerald,

are you using an external J-Linkk (connected to J9)? If so, it depends what debug firmware you are running on the K20/OpenSDA: if this is the mbed/CMSIS-DAP, it can interfere with the SWD signals. In that case, power the board with the K64 USB port (not with the OpenSDA one).

I hope this helps,

Erich

Re: Cannot debug FDRM-K64F via J-link.

geraldhilderink — Thu, 23 Mar 2017 10:01:18 GMT

Hi Erich,

I am using the USB cable and I flashed the SDA to OpenSDA/J-Link. This works fine with the Kinetis IDE. This debug connection is fast but limited to 5 break points.

This morning, I’ve found out how to use the LinkServer with OpenSDA/USB. It works, but slower than using SDA/J-Link.

Gerald.

Re: Cannot debug FDRM-K64F via J-link.

lpcxpresso_supp — Thu, 23 Mar 2017 13:20:42 GMT

Can you confirm how you are creating your launch configuration? With MCUXpresso IDE you really need to be using the Quickstart Panel -> Debug option to autodetect and configure the probe. If you manually created a launch config, I would suggest deleting and starting again.

See the supplied MCUXpresso IDE User Guide for more details of how to use the built in J-Link support.

Regards,

LPCXpresso / MCUXpresso IDE Support

Re: Cannot debug FDRM-K64F via J-link.

geraldhilderink — Fri, 24 Mar 2017 00:58:05 GMT

Thanks. This helped. Deleting all existing launch configs was important for autodetect. Now, it detects the J-Link and it is working. :-)

I did this the first time (in Quickstart Panel) and autodetect went wrong for J-Link for some reason. Now, this second time autodetect went right. When I look at the debug launch config nothing is different with the first attempt. Must be some hidden setting that went wrong.

Re: Cannot debug FDRM-K64F via J-link.

harsh_bhuva — Tue, 11 Aug 2020 07:12:10 GMT

Hi Erich Styger,

We have successfully able to load FRDM-K64F target MCU via JLink plus debugger with SWD interface using MCUexpresso. But we are not able to do it with JTAG interface.

Below is connection between FRDM_K64F and JLink Plus debugger:

Please suggest your view on this.

Regards,

Harsh Bhuva

Re: Cannot debug FDRM-K64F via J-link.

ErichStyger — Tue, 11 Aug 2020 08:31:03 GMT

Is your K64F enabled for JTAG signals? Note that the JTAG pins can be disabled to only use SWD.

Re: Cannot debug FDRM-K64F via J-link.

harsh_bhuva — Tue, 11 Aug 2020 08:57:32 GMT

Hi Erich,

Whether FRDM-K64F is normally dispatched with JTAG disabled? If yes how to enable the JTAG pins for the same.

We are not doing any configuration to make JTAG and SWD enabled or disabled.

Regards,

Harsh

Re: Cannot debug FDRM-K64F via J-link.

ErichStyger — Tue, 11 Aug 2020 18:14:24 GMT

It depends on your pin muxing and I believe there is a bit in the system control registers about it. Search for jtag in the reference manual and you should find it. Just wondering: why would you need JTAG except you would have multiple devices on the scan chain?