FDRM-K82F and J-Link probe

cancel
Showing results for 
Search instead for 
Did you mean: 

FDRM-K82F and J-Link probe

924 Views
mhanuel
Contributor II

Hello ALl,

I am trying to connect J-Link probe to J19 on FDRM-K82F board, so far I cannot connect, my probe is working since i can connect to K20 MCU on same board.  I remove jumpers J6 and J7 as  J17 as well, As a desperate I also remove J8 but it cannot connect after all. I am powering using USB port (not Open SDA port).

Here is the output for K20 sucessful connection

XXX:~$ JLinkExe -device MK20FX512xxx12
SEGGER J-Link Commander V5.12g (Compiled May 27 2016 17:03:43)
DLL version V5.12g, compiled May 27 2016 17:03:38

Connecting to J-Link via USB...O.K.
Firmware: J-Link V9 compiled Apr 22 2016 11:47:06
Hardware version: V9.40
S/N: 269401007
License(s): FlashBP, GDB
OEM: SEGGER-EDU
VTref = 3.304V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify target interface:
J) JTAG (Default)
S) SWD
TIF>S
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "MK20FX512XXX12" selected.


Found SWD-DP with ID 0x2BA01477
Found SWD-DP with ID 0x2BA01477
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl 0 @ E00FF000
ROMTbl 0 [0]: FFF0F000, CID: B105E00D, PID: 000BB000 SCS
ROMTbl 0 [1]: FFF02000, CID: B105E00D, PID: 003BB002 DWT
ROMTbl 0 [2]: FFF03000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl 0 [3]: FFF01000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl 0 [4]: FFF41000, CID: B105900D, PID: 000BB9A1 TPIU
Cortex-M4 identified.

and for K82F 

XXX:~$ JLinkExe -device MK82FN256xxx15
SEGGER J-Link Commander V5.12g (Compiled May 27 2016 17:03:43)
DLL version V5.12g, compiled May 27 2016 17:03:38

Connecting to J-Link via USB...O.K.
Firmware: J-Link V9 compiled Apr 22 2016 11:47:06
Hardware version: V9.40
S/N: 269401007
License(s): FlashBP, GDB
OEM: SEGGER-EDU
VTref = 3.296V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify target interface:
J) JTAG (Default)
S) SWD
TIF>S
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "MK82FN256XXX15" selected.


Can not connect to target.

Am I missing something?

I would appreciate any comments. 

Thank you for reading, 

Tags (3)
0 Kudos
5 Replies

262 Views
carlos_chavez
NXP Employee
NXP Employee

Hi Manuel,

I am able to successfully connect to my FRDM-K82F board via my J-Link probe via J19 by removing J6 and J7 jumpers.  Since J19 is not a keyed header, please make sure that you have the proper orientation for pin 1 and that your Cortex M Adapter is not offset.  As the pins are very small, it is quite easy to do.

Here is my output below:

pastedImage_1.png

So, just to make sure, you are able to communicate to the MCU using the J-Link OpenSDA App with the USB Micro cable connected to J5?

-Carlos

0 Kudos

262 Views
mhanuel
Contributor II

Hi Carlos,

I install J17 and now it works. Section 3.2.1 of User Guide is kind of confusing since I thought I have to cut the trace, with that jumper in place now it works.

Could you please let me know the correct way to interpret that section?

Thank you for your help,

0 Kudos

262 Views
anthony_huereca
NXP Employee
NXP Employee

Hi Manuel,

  The second part of 3.2.1 is describing an additional feature of the Freedom board where you can use your FRDM-K82F to program another board. That however is an atypical use-case, and for normal board operation it's assumed that J17 wouldn't be touched nor that trace cut. You need that connection for the SWD_CLK signal to get to the K82 device to debug. 

Regards,

Anthony 

0 Kudos

262 Views
miduo
NXP Employee
NXP Employee

Hi,

 I am not sure which USB port you used for the power. The OpenSDA is powered by P5V_SDA with J5 USB port; If you power the board with J11 USB port, which will not provide power to OpenSDA, but only the K82 chip.

One another thing, did you update the OpenSDA firmware? I would recommend customer to update FRDM-K82 board OpenSDA firmware to J-Link. Customer could find and download Segger J-Link firmware from:

SEGGER - The Embedded Experts - OpenSDA / OpenSDA V2 

0 Kudos

262 Views
mhanuel
Contributor II

Hello Gang Li,

I am aware of the power supply condition you mention, I actually not interested in powering the openSDA circuitry since my willing is to debug using external J-Link probe, I need to debug the K82F only.

I know is getting power since it's sense by probe as shown on console output.

I already was using the latest J-Link firmware under openSDA, but I am willing to change to external debugger since I have more control.

I already remove J6 and J7, also I cut trace of J8 and J17. Still cannot connect. It may be a board issue?

Thank you for your comments,

0 Kudos