Using FRDM-K66F with Segger Jlink and JTAG on J9

[petec20]

I'm considering buying a Freedom FRDM-K66F development platform but want to use it with a Segger Jlink & JTAG rather than SWD. In the FRDMK66FUG user manual (pages 7,8 & 19) it details how to cut the SWD lines bridged by J8 & J12 but looking at the J9 programming connector it seems to lack a TDI connection and a pin9 GND connection to make it into a standard JTAG connector.

So my question is this:

After cutting the SWD signals do I need to connect TDI to pin8, and another ground to pin 9 for the Segger J-link to work correctly? I'm wondering why these signals are not connected anyway, and left unconnected.

[Hui_Ma]

Hi

From the FRDM-K66F board user manual, there shows the board only provides the SWD interface:

The FRDM-K66F board is a low cost board, which could not provide full feature for K66 chip evaluation.

Customer could refer TWR-K65F180M board about JTAG debug interface design:

Wish it helps.

Have a great day,
Ma Hui
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[johntse]

dear Hui Ma

i know it has been a long time but recently i brought a FRDMK66 to work on using my segger jlink

and i followed your example but i could not even erase the memory using jlink commander

looking at the comments above and to peter, it seems disconnecting j8 and j12 actually disconnects the jtag from the resident k66

i am not using an outside target k66,  i want to use the FRDMK66 cpu with my jlink

i could use my jlink on similar 10pin jtag connector on my FRDMK64 board

what did i do wrong?

any help would be greatly appreciated

thanks

[ErichStyger]

Hi @johntse,

I'm not sure what the problem is (or was for me): for me too, it was not possible to use an external debug probe (J-Link EDU in my case) on J9. I suspect it is a problem by the factory default bootloader (DAPLink) and firmware (I believe it was a J-Link firmware loaded by default). I was able to debug it the device with OpenSDA, but using an external debug probe failed. I suspect it was because the K20 and its firmware were pulling some signals high/low which should be tristated.

Anyway, I was able to solve it:

- not changing anything on the board hardware (default jumpers, etc)

- programmed the K20 (using a J-Link on J10) and replaced the firmware on the K20 with the bootloader from my article (https://mcuoneclipse.com/2017/10/29/adding-a-delay-to-the-arm-daplink-bootloader/ )

- optionally load the SEGGER V2.1 'generic' firmware on it.

The key to a working board for me was to get rid of that original firmware on the K20.

You find that patched K20 bootloader at the end (links section) of the above article.

I hope this helps,

Erich

[petec20]

Thankyou for the reply Ma Hui. I did find that the FRDM-K66F works OK with JTAG if it's modified as above.

[johntse]

dear peter

i know it has been a long time but recently i brought a FRDMK66 to work on using my segger jlink

and i followed your example but i could not even erase the memory using jlink commander

looking at the comments above, it seems disconnecting j8 and j12 actually disconnects the jtag from the resident k66

i am not using an outside target k66,  i want to use the FRDMK66 cpu

what did i do wrong?

any help would be greatly appreciated

thanks