We have been using the Freescale FRDMK22F Development board with KDS 3.0. This has been working fine debugging using the Segger J-Link driver connected through the OpenSDA interface (with the USB connection to the FRDMK22F from the Windows 7 PC running KDS).
But now we are moving toward using our custom hardware which won't have an OpenSDA interface, so I am attempting to connect directly to the FRDMK22F K22F MCU using a PEMicro Multilink Univeral FX probe connected to the J11 connector on the FRDMK22F.
KDS appears to connect fine to the PEMicro Multilink Universal FX probe, but fails when attempting to debug the hardware.
We have cut the J7 trace as indicated in the FRDMK22F User's Guide, to isolate the MCU from the OpenSDA debug interface.
The FRDMK22F is being powered by an external 5V power supply, and the TargerPower present LED lights up on the PEMicro Multilink Universal FX probe.
Hi Carlos,
Thank you for the reply. It appears we misunderstood the statement in the FRDMK22F User’s Guide & Schematic as far as why/when this trace should be cut.
“SHORTING HEADER ON BOTTOM LAYER
Jumper is shorted by a cut-trace
on bottom layer. Cutting the trace
will effectively isolate the on-board
MCU from the OpenSDA
debug interface.”
We no longer have the J7 trace cut, but the debug still fails.
When I attempt to launch the KDS debugger to run the simply hello_world on the FRDMK22F I get the following.
The code which was running on the hardware was toggling the RDB LED. When the Debug is initiated that toggling stops. But the debug fails and once I remove the cable from the PEMicro probe and reboot the previous code is programmed and run.
The debug fails, nor does it update the flash of the device (as the programmer normally does when it works using the OpenSDA interface).
Steve
