Difference between revisions of "Tracing on Renesas Synergy R7FS7G2"

From SEGGER Wiki
Jump to: navigation, search
(Specifics/Limitations)
(Minimum requirements)
(10 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
The Renesas Synergy R7FS7G2 MCU implements tracing via pins , so a J-Trace can be used for tracing.
 
The Renesas Synergy R7FS7G2 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 Renesas Synergy R7FS7G2 devices, the following minimum requirements have to be met:
 
In order to use trace on the Renesas Synergy R7FS7G2 devices, the following minimum requirements have to be met:
* J-Link software version V6.13e (beta) or later
+
* J-Link software version V6.86a or later
* Ozone V2.22o or later (if streaming trace and / or the sample project from below shall be used)
+
* Ozone V3.20e 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 ''DK-S7G2 Development Kit''. 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 ''DK-S7G2 Development Kit''. 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:Renesas_R7FS7G2_TracePins.zip | Renesas_R7FS7G2_TracePins.zip]]
[[:File:ST_STM32F769I-EVAL_16MHz_Traceexample.zip | ST_STM32F769I-EVAL_16MHz_Traceexample.zip]]
 
   
= Specifics/Limitations =
+
== Specifics/Limitations ==
 
The Renesas Synergy R7FS7G2 supports traceclock speeds up to 120 MHz like used in the example project. SEGGERs J-Trace PRO supports it out of the box without any additional pinsetups though up to 80 MHz traceclock. Should you need faster traceclock speeds, please set the ''TraceSampleAdjust'' value to 0 like in the example project.
 
The Renesas Synergy R7FS7G2 supports traceclock speeds up to 120 MHz like used in the example project. SEGGERs J-Trace PRO supports it out of the box without any additional pinsetups though up to 80 MHz traceclock. Should you need faster traceclock speeds, please set the ''TraceSampleAdjust'' value to 0 like in the example project.
  +
  +
== Tested Hardware ==
  +
[[File:Renesas_DK-S7G2.jpg|none|thumb|DK-S7G2 Development Kit]]
  +
  +
== 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:S7G2_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:S7G2_Setuptime_TD0.png|none|thumb|TD0 setup time]]

Revision as of 13:43, 1 July 2022

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

Minimum requirements

In order to use trace on the Renesas Synergy R7FS7G2 devices, the following minimum requirements have to be met:

  • J-Link software version V6.86a or later
  • Ozone V3.20e 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 DK-S7G2 Development Kit. 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.

Renesas_R7FS7G2_TracePins.zip

Specifics/Limitations

The Renesas Synergy R7FS7G2 supports traceclock speeds up to 120 MHz like used in the example project. SEGGERs J-Trace PRO supports it out of the box without any additional pinsetups though up to 80 MHz traceclock. Should you need faster traceclock speeds, please set the TraceSampleAdjust value to 0 like in the example project.

Tested Hardware

DK-S7G2 Development Kit

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