Difference between revisions of "Tracing on NXP Kinetis MK80FN2"

From SEGGER Wiki
Jump to: navigation, search
(Minimum requirements)
(4 intermediate revisions by 3 users not shown)
Line 4: Line 4:
 
The NXP Kinetis MK80FN2 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.
 
The NXP Kinetis MK80FN2 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 =
+
== Minimum requirements ==
 
In order to use trace on the NXP Kinetis MK80FN2 MCU devices, the following minimum requirements have to be met:
 
In order to use trace on the NXP Kinetis MK80FN2 MCU devices, the following minimum requirements have to be met:
 
* J-Link software version V6.18c or later
 
* 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)
 
* 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
 
* 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 =
+
== Sample project ==
== Streaming trace ==
+
=== 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-K80F150M evaluation board. 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.
+
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-K80F150M evaluation board. 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. The recommended version to rebuild the projects is ES V6.30. But the examples are all pre-build and work out-of-the box with Ozone, so rebuilding is not necessary.
   
 
[[Media:NXP_Kinetis_MK80FN256_10_MHz_TraceExample.zip | NXP_Kinetis_MK80FN256_10_MHz_TraceExample.zip]]
 
[[Media:NXP_Kinetis_MK80FN256_10_MHz_TraceExample.zip | NXP_Kinetis_MK80FN256_10_MHz_TraceExample.zip]]
   
'''Note:''' The example is shipped with a compiled .JLinkScriptfile, should you need the original source it can be requested at [mailto:support@segger.com support@segger.com]
+
{{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 project as reference: [https://wiki.segger.com/Tracing_on_ST_STM32F407_(SEGGER_Cortex-M_Trace_Reference_Board) Tracing on SEGGER_Cortex-M_Trace_Reference_Board]
 
To create your own .JLinkScriptfile you can use the following project as reference: [https://wiki.segger.com/Tracing_on_ST_STM32F407_(SEGGER_Cortex-M_Trace_Reference_Board) Tracing on SEGGER_Cortex-M_Trace_Reference_Board]
   
== ETB trace ==
+
=== ETB trace ===
'''Note:''' The ETB does not support stream tracing.
+
{{Note|The ETB does not support stream tracing.}}
   
== Specifics/Limitations==
+
=== Specifics/Limitations ===
 
This particular evaluation board's hardware needs to be modified manually to enable the trace functionally. To do this 0 Ohm resistors R57,R61,R63,R65 and R67 need to be placed.
 
This particular evaluation board's hardware needs to be modified manually to enable the trace functionally. To do this 0 Ohm resistors R57,R61,R63,R65 and R67 need to be placed.
   
= Tested Hardware =
+
== Tested Hardware ==
 
[[File:TWR-K80F150M.jpg|none|thumb|TWR-K80F150M]]
 
[[File:TWR-K80F150M.jpg|none|thumb|TWR-K80F150M]]
   
= Reference trace signal quality =
+
== Reference trace signal quality ==
 
The following pictures show oscilloscope measurements of trace signals output by the "Tested Hardware" using the example project.
 
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.
 
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].
 
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 ==
+
=== 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.
 
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:k80_Risetime_TCLK.png|none|thumb|TCLK rise time]]
 
[[File:k80_Risetime_TCLK.png|none|thumb|TCLK rise time]]
== Setup 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.
 
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:k80_Setuptime_TD0.png|none|thumb|TD0 setup time]]
 
[[File:k80_Setuptime_TD0.png|none|thumb|TD0 setup time]]

Revision as of 13:42, 1 July 2022

This article describes how to get started with trace on the NXP Kinetis MK80FN2 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 MK80FN2 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 MK80FN2 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-K80F150M evaluation board. 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, SEGGER Embedded Studio can be used. The recommended version to rebuild the projects is ES V6.30. But the examples are all pre-build and work out-of-the box with Ozone, so rebuilding is not necessary.

NXP_Kinetis_MK80FN256_10_MHz_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 project as reference: Tracing on SEGGER_Cortex-M_Trace_Reference_Board

ETB trace

Note:
The ETB does not support stream tracing.

Specifics/Limitations

This particular evaluation board's hardware needs to be modified manually to enable the trace functionally. To do this 0 Ohm resistors R57,R61,R63,R65 and R67 need to be placed.

Tested Hardware

TWR-K80F150M

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 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.

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.

TD0 setup time