Tracing on Renesas R7S910017 (RZ/T1)

From SEGGER Wiki
Jump to navigation Jump to search

This article describes how to get started with trace on the Renesas R7S910017 (RZ/T1) 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 R7S910017 (RZ/T1) MCU implements tracing via pins , so a J-Trace can be used for tracing. ETB tracing is implemented as well and can be used even with a J-Link.

Minimum requirements

In order to use pin trace on the Renesas R7S910017 (RZ/T1) devices, the following minimum requirements have to be met:

  • J-Link software version V6.41a or later
  • Ozone V2.60g or later (if streaming trace and / or the sample project from below shall be used)
  • J-Trace PRO for Cortex HW version V2.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 RSK+RZT1 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.

Renesas_RZT1_75MHz_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

The following sample project is designed to be used with J-Trace PRO and Ozone to demonstrate ETB trace on the Cortex-R core. The project has been tested with the minimum requirements mentioned above and a RSK+RZT1 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.

Renesas_RZT1_75MHz_ETB_Trace.zip

Note: ETB does not support streaming trace features.

Tracing on the Cortex-M3 subcore

The Renesas RZ/T1 device family implements a Cortex-M3 sub core on some device types. ETB tracing is also available for the Cortex-M3 sub core. The following trace example project can be used for verification:

Renesas_RZT1_M3_ETB_Trace.zip

Note: ETB does not support streaming trace features.

Tested Hardware

RSK+RZT1 board

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