Difference between revisions of "M2351"

From SEGGER Wiki
Jump to: navigation, search
(Created page with "__TOC__ = Tracing on Nuvoton M2351 = This article describes how to get started with trace on the Nuvoton M2351 MCU. This article assumes that there is already a basic knowle...")
 
Line 6: Line 6:
 
The Nuvoton M2351 MCU implements tracing via pins, so a J-Trace can be used for tracing.
 
The Nuvoton M2351 MCU implements tracing via pins, so a J-Trace can be used for tracing.
   
= Minimum requirements =
+
== Minimum requirements ==
 
In order to use trace on the Nuvoton M2351 MCU devices, the following minimum requirements have to be met:
 
In order to use trace on the Nuvoton M2351 MCU devices, the following minimum requirements have to be met:
 
* J-Link software version V6.50 or later
 
* J-Link software version V6.50 or later
Line 13: Line 13:
 
* Tracepin connection like on the NuMaker-PFM-M2351 eval board
 
* Tracepin connection like on the NuMaker-PFM-M2351 eval board
   
= 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 ''NuMaker-PFM-M2351'' 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 ''NuMaker-PFM-M2351'' 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.
   
 
[[Media:Nuvoton_M2351_Trace.zip | Nuvoton_M2351_Trace.zip]]
 
[[Media:Nuvoton_M2351_Trace.zip | Nuvoton_M2351_Trace.zip]]
   
= Tested Hardware =
+
== Tested Hardware ==
 
[[File:NuMaker_M2351.jpg|none|thumb|NuMaker-PFM-M2351]]
 
[[File:NuMaker_M2351.jpg|none|thumb|NuMaker-PFM-M2351]]
   
= 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].
== Trace clock signal quality ==
+
=== Trace clock signal quality ===
 
The trace clock signal quality shows multiple trace clock cycles on the tested hardware as reference.
 
The trace clock signal quality shows multiple trace clock cycles on the tested hardware as reference.
 
[[File:M2351_Multiple_TCLK.png|none|thumb|Trace clock signal quality]]
 
[[File:M2351_Multiple_TCLK.png|none|thumb|Trace clock signal quality]]
== 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:M2351_Risetime_TCLK.png|none|thumb|TCLK rise time]]
 
[[File:M2351_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:M2351_Setuptime_TD0.png|none|thumb|TD0 setup time]]
 
[[File:M2351_Setuptime_TD0.png|none|thumb|TD0 setup time]]

Revision as of 10:55, 23 August 2019

Tracing on Nuvoton M2351

This article describes how to get started with trace on the Nuvoton M2351 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 Nuvoton M2351 MCU implements tracing via pins, so a J-Trace can be used for tracing.

Minimum requirements

In order to use trace on the Nuvoton M2351 MCU devices, the following minimum requirements have to be met:

  • J-Link software version V6.50 or later
  • Ozone V2.62g 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
  • Tracepin connection like on the NuMaker-PFM-M2351 eval board

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 NuMaker-PFM-M2351 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.

Nuvoton_M2351_Trace.zip

Tested Hardware

NuMaker-PFM-M2351

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.

Trace clock signal quality

The trace clock signal quality shows multiple trace clock cycles on the tested hardware as reference.

Trace clock signal quality

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