What debugger i-face should I use with FRDM-K66F in MCUXpresso IDE

Showing results for 
Search instead for 
Did you mean: 

What debugger i-face should I use with FRDM-K66F in MCUXpresso IDE

Contributor I

I am looking for some debugger recommendations from NXP veterans. I am starting a project that will be developed on an FRDM-K66F evaluation board under the MCUXpresso IDE v10.0.2 free edition. The project has a pretty small budget. I am confused by the openSDAv2.1 USB ports abilities to be "the debugger" connection from the FRDM-K66F to the MCUXpresso IDE. I have not bought any hardware yet and am scoping the effort for our 2 man shop (me and a HW guy). I know better than to scrimp on debugger support, but overbuying on debug support may scuttle the project before it starts. I need to choose wisely and hopefully buy the right things at the beginning.

Does an openSDAv USB connection to the PC running the IDE provide a debug connection the IDE I can use?

Is it a viable option on a tight budget?

If you were spending your own money, what would you use? What probe (Segger J-Link base?), IDE and/or debugger SW add on to that IDE?

Should I upgrade MCUXpresso to the pro version?

In case you want some background, this first project will use FreeRTOS and IwIP TCP/IP stack to (mostly) bridge Enet packets to an SPI connection on another board.  I may end up simplifying(?)  it by doing without the stack or RTOS, but I am starting with them in to learn how usable they really are for future projects. While working for a company making ICs with embedded ARM processors I have used ARM compilers in a codewarrior/codeblocks environment with expensive debuggers bought through ARM. That experience is dated now, but I am familiar with the process and the incredible expense involved in that flow.

0 Kudos
1 Reply

NXP Employee
NXP Employee

In the first place, just buy your FRDM-K66 board. This has a built in OpenSDA debug probe which can be programmed with different firmware to provide either a CMSIS-DAP (for OpenSDA, generally called DAPLink), a SEGGER J-Link, or a P&E Micro debug probe interface for the IDE to connect to. 

I'm not sure which probe firmware variant is shipped by default with FRDM-K66, but all are available for download from

This will give you the chance to play with the three firmware variants and see what you prefer. They all provide slightly different capabilities when used with the IDE - for instance the Live Variables functionality built into the IDE will only work with the CMSIS-DAP firmware.

This built in probe does have some advantages over a standalone probe - in particular it will generally provide a VCOM port back up to the host PC for UART like I/O. However generally the built in probe is slower than a standalone probe, and the OpenSDA probe hardware was not designed to be used to debug an MCU on another board (i.e. it can't be used once you have your own hardware).

If you decide you want to try a standalone probe, particularly once you have your own hardware, then probably the cheapest route- but the one that provides the most built in capabilities within MCUXpresso IDE - is the LPC-Link2 (http://www.nxp.com/lpclink2) which generally are around $20.  This will also support the use of the SWO Trace capabilities built directly into the IDE.

But both SEGGER and P&E offer various price points for their standalone probes too. And do provide other software to provide other capabilities. See their websites for more details.

Anyway for more details of using each of the various probe types plus their capabilities within the IDE, please see the MCUXpresso IDE v10.0.2 User Guide, which is provided as part of the product install and can also be downloaded from http://www.nxp.com/mcuxpresso/ide/documentation

As far as the Pro version goes, at least in the first place, there is probably little point - as the additional SWO functionality is only available using LPC-Link2 (with our own LPC-Link2 CMSIS-DAP firmware), as described in the purchase page at: MCUXpresso IDE|NXP 


MCUXpresso IDE Support

0 Kudos