Using FRDM-K64F Board to debug another Kinetis Board

Given all the posts I already have published on a similar topic, this one will be a short one: how to use the Freescale FRDM-K64F board with OpenSDAv2 to debug another board:

FRDM-K64F Board to Debug FRDM-KL25Z Board

FRDM-K64F Board to Debug FRDM-KL25Z Board

  1. Identify J11 on the board:

    J11 on FRDM-K64F Schematics (Source: Freescale FRDM-K64F Schematics)

    J11 on FRDM-K64F Schematics (Source: Freescale FRDM-K64F Schematics)

  2. Cut the trace of J11 on the backside of the board:

    Cut Trace J11 on Backside of FRDM-K64F

    Cut Trace J11 on Backside of FRDM-K64F

  3. Install a jumper (have the jumper removed to debug off-board device, have the jumper installed to debug on-board device).

    J11 Jumper

    J11 Jumper

  4. Connect a 10 pin ribbon cable from J9 to the target board (check cable orientation):

    J9 and J11 on FRDM-K64F

    J9 and J11 on FRDM-K64F

  5. Done! Now I can us the OpenSDAv2 circuit on the FRDM-K64F for debugging another board.
Debugging FRDM Board with FRDM-K64F

Debugging FRDM Board with FRDM-K64F

💡 Depending on which OpenSDA firmware you are using, make sure you read the licensing terms and conditions carefully!

Happy Debugging 🙂

Links

Advertisements

15 thoughts on “Using FRDM-K64F Board to debug another Kinetis Board

  1. Hello
    Can I do this but using J-Link instead OpenSDA? I mean, debug other boards with J-Link instead OpenSDA.

    Thanks!!

    Like

    • Hi Manuel,
      You mean with a Segger J-Link probe (https://www.segger.com/jlink-debug-probes.html)? Yes, of course you can debug any board with an ARM device with these :-).
      If you are using the Segger OpenSDA firmware, then you *could* technically, but only Kinetis, and according to the licensing terms you have agreed to (in the OpenSDA), you are not allowed to debug anything else than the device on the FRDM board.
      I hope this makes it clear?
      Erich

      Like

  2. Pingback: How to Recover the OpenSDA V2.x Bootloader | MCU on Eclipse

  3. Hi, Erich! I recently bought a K64F, I was trying to use the component USB CDC as you used on another post, anyway, after that, when I try to debug It, the console says that wasn’t able to REST/HALT the target processor. At first I thought this was the bootloader, I managed to update the bootloader of the K20DX128 using a Keil Ulink2 connected to the K20DX128 SWD/JTAG header. When I connect the board on my computer, it show the MSD and all, but I still have the same result. Even the Keil Ulink2 can’t “find” the K64F chip! =/

    Like

What do you think?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.