View source for Tracing on NXP Kinetis MK64FN1M0

__TOC__

This article describes how to get started with trace on the NXP Kinetis MK64FN1M0 MCU. This article assumes that there is already a basic knowledge about trace in general (what is trace, what different implementations of trace are there, etc.). If this is not the case, we recommend to read '''Trace''' chapter in the J-Link User Manual (UM08001).
The NXP Kinetis MK64FN1M0 MCU implements tracing via pins or via on-chip trace buffer (ETB), so a J-Trace as well as the ETB can be used for tracing.

== Minimum requirements ==
In order to use trace on the NXP Kinetis MK64FN1M0 MCU devices, the following minimum requirements have to be met:
* J-Link software version V6.18c or later
* Ozone V2.46a or later (if streaming trace and / or the sample project from below shall be used)
* J-Trace PRO for Cortex-M HW version V1.0 or later
To rebuild the project our IDE Embedded Studio can be used. The recommended version to rebuild the projects is V6.30. But the examples are all prebuild and work out-of-the box with Ozone, so rebuilding is not necessary.

== Sample project ==
=== Streaming trace ===
The following sample project is designed to be used with J-Trace PRO and Ozone to demonstrate streaming trace. The project has been tested with the minimum requirements mentioned above and a TWR-K64F120M Evalboard. The sample project comes with a pre-configured project file for Ozone that runs out-of-the box. In order to rebuild the sample project, [https://www.segger.com/embedded-studio.html SEGGER Embedded Studio] can be used.

[[Media:NXP_Kinetis_K64FN1M0_60MHz_TraceExample_pex.zip | NXP_Kinetis_K64FN1M0_60MHz_TraceExample.zip]]

'''Note:''' The example is shipped with a compiled .JLinkScriptfile, should you need the original source, please get in touch with SEGGER directly via our support system: https://www.segger.com/ticket/.

To create your own .JLinkScriptfile you can use the following guide as reference: [[How_to_configure_JLinkScript_files_to_enable_tracing]]

=== ETB trace ===
'''Note:''' The ETB does not support stream tracing.

== Tested Hardware ==
[[File:TWR-K64F120M.jpg|none|thumb|TWR-K64F120M]]


== Reference trace signal quality ==
The following pictures show oscilloscope measurements of trace signals output by the "Tested Hardware" using the example project.
All measurements have been performed using a Agilent InfiniiVision DSO7034B 350 MHz 2GSa/s oscilloscope and 1156A 1.5 GHz Active Probes. If your trace signals look similar on your trace hardware, chances are good that tracing will work out-of-the-box using the example project.
More information about correct trace timing can be found at the following [https://www.segger.com/products/debug-probes/j-trace/technology/setting-up-trace/ website].
=== Rise time ===
The rise time of a signal shows the time needed for a signal to rise from logical 0 to logical 1. For this the values at 10% and 90% of the expected voltage level get used as markers. The following picture shows such a measurement for the trace clock signal.
[[File:k64_Risetime_TCLK.png|none|thumb|TCLK rise time]]
=== Setup time ===
The setup time shows the relative setup time between a trace data signal and trace clock. The measurement markers are set at 50% of the expected voltage level respectively. The following picture shows such a measurement for the trace data signal 0 relative to the trace clock signal.
[[File:k64_Setuptime_TD0.png|none|thumb|TD0 setup time]]