PE Micro Multilink Universal Rev A not working on K64 TWR board

[johnbaker]

I originally posted this on PE Micro's forum but received a reply from another engineer here that it works fine on our K60 board.  He cannot get it to work on the K64 TWR board either.  We keep getting the error, "Cannot enter background mode"  (See original post below):

Thanks,

John Baker

AVG

• I am using a Multilink Universal Rev A (PE5655063) plugged into the JTAG connector of a TWR-K64F120M board. KDS Ver. 1.1.1 debugger is configured properly but I get the following error:
  
  
  P&E GDB Server, Version 5.07.00.00
  Copyright 2014, P&E Microcomputer Systems Inc, All rights reserved
  
  Loading library C:\Freescale\KDS_1.1.1\eclipse\plugins\com.pemicro.debug.gdbjtag.pne_1.1.2.201408071632\win32\gdi\unit_ngs_arm_internal.dll ... Done.
  
  Command line arguments: -device=K64FN1M0M12 -startserver -serverport=7224 -interface=USBMULTILINK -speed=5000 -port=USB1 -USE_CYCLONEPRO_RELAYS=0 -FORCE_MASS_ERASE=0
  Device selected is k64fn1m0m12
  User Specified Hardware Selection : Interface=USBMULTILINK and Port=USB1
  Connecting to target.
  P&E Interface detected - Flash Version 6.10
  
  Can not enter background mode  .
  Comment #1 John B. - September 16, 2014 - 02:42 PM (14:42 hours)
  
  
  
  Comments

  ---

• 
  KDS version 1.1.1 is able to debug a K60 tower board with the exact same Universal Multilink that was referenced in the previous comment, so the problem has to do with the K64 tower board (or with K64 in general). Does anyone have any experience/comments regarding using KDS with the Universal Multilink to target the K64?
  Comment #2 Brian H. - September 26, 2014 - 01:01 PM (13:01 hours)

[Jorge_Gonzalez]

Hello John:

Check that J16 is set to (1-2). See the next article:

First Steps with the Freescale TWR-K64F120M | MCU on Eclipse

Regards!,
Jorge Gonzalez

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[johnbaker]

Jorge,

Thanks for the reply. I checked and yes, J16 is jumpered 1-2. J39 is also there and jumpered.

John

[Jorge_Gonzalez]

Hello John:

I just tested with a TWR-K64 using Multilink Universal and I got the same results.

How are you powering the board? It seems that USB Debug Port cannot be connected at the same time as the external Multilink.

So if using Multilink you need to power the board from another source, but this involves adjusting J18 and J29. Here are two ways that worked for me:

1- Power from the USB connector in a Primary Elevator:

    J18: [Removed].

    J29: [5-6].

2- Power from Micro-USB connector in TWR-K64:

     J18: [5-6].

     J29: [3-4] or [5-6]

With either of these options I was able to enter a debug session.

I hope this works for you.

Regards!,
Jorge Gonzalez

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[johnbaker]

Ahhh, I think that is the problem. J18 is set to but we are getting power from the USB connector on the Primary Elevator.

Thanks!

John

[johnbaker]

Hi Jorge,

Thanks for your responses.

Our actual new development board with the K64 chip arrived two days ago. We were able to get the Multilink to work by changing the ‘Debug Shift Freq (Khz)’ to 2000. Not sure why yet. I think it has something to do with how the board was developed and its external oscillators as we also had to make temporary changes to the clock setup code in system_MK64F12.c and .h just to get the code to run.

I have not had a chance to try the tower board again.

Thanks,

John