Difference between revisions of "i.MXRT1176"

From SEGGER Wiki
Jump to: navigation, search
(Tracing on iMXRT1176 series)
 
(12 intermediate revisions by 3 users not shown)
Line 1: Line 1:
This article coverst the NXP i.MXRT1076 family devices.
+
This article coverst the NXP i.MXRT1176 family devices.
As for all i.MXRT10xx devices, JTAG is not active per default. Instead SWD can be used.
+
As for all i.MXRT11xx devices, JTAG is not active per default. Instead SWD can be used.
 
To activate JTAG on this target device eFuses must be set. For more information see the corresponding target reference manual.
 
To activate JTAG on this target device eFuses must be set. For more information see the corresponding target reference manual.
   
 
__TOC__
 
__TOC__
   
= Tracing on iMXRT1176 series =
+
== Tracing on iMXRT1176 series ==
This section describes how to get started with trace on the ST iMXRT1176 MCUs.
+
This section describes how to get started with trace on the NXP iMXRT1176 MCUs.
 
This section assumes that there is already a basic knowledge about trace in general (what is trace, what different implementations of trace are there, etc.).
 
This section 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).
 
If this is not the case, we recommend to read '''Trace''' chapter in the J-Link User Manual (UM08001).
Line 14: Line 14:
 
* The following sample project is designed to be used with J-Trace PRO and Ozone to demonstrate streaming trace.
 
* The following sample project is designed to be used with J-Trace PRO and Ozone to demonstrate streaming trace.
 
* In order to rebuild the sample project, [https://www.segger.com/embedded-studio.html SEGGER Embedded Studio] can be used.
 
* In order to rebuild the sample project, [https://www.segger.com/embedded-studio.html SEGGER Embedded Studio] can be used.
* All examples are shipped with a compiled .JLinkScriptfile (.pex), should you need the original source, please get in touch with SEGGER directly via our support system: https://www.segger.com/ticket/.
+
* 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]]
   
  +
== Tracing on NXP iMXRT1176 dual core ==
 
=== Minimum requirements ===
+
=== Tracing on NXP iMXRT1176 dual core ===
  +
==== Minimum requirements ====
In order to use trace on the ST iMXRT1176 MCU devices, the following minimum requirements have to be met:
 
  +
In order to use trace on the NXP iMXRT1176 MCU devices, the following minimum requirements have to be met:
 
* J-Link software version V6.72b or later
 
* J-Link software version V6.72b or later
 
* Ozone V3.20 or later (if streaming trace and / or the sample project from below shall be used)
 
* Ozone V3.20 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 for streaming trace
 
* J-Trace PRO for Cortex-M HW version V1.0 or later for streaming trace
  +
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.
   
=== Streaming trace ===
+
==== Streaming trace ====
 
The projects have been tested with the minimum requirements mentioned above. The board used for this example is not publicly available yet. To enable trace on the board some solder bridges had to be closed. For reference consult the manual of the board you are using.
 
The projects have been tested with the minimum requirements mentioned above. The board used for this example is not publicly available yet. To enable trace on the board some solder bridges had to be closed. For reference consult the manual of the board you are using.
 
As the iMXRT1176 series is a dual core device two trace examples are available, one for the Cortex-M7 core and one for the Cortex-M4 core.
 
As the iMXRT1176 series is a dual core device two trace examples are available, one for the Cortex-M7 core and one for the Cortex-M4 core.
   
=== iMXRT1176_M7 ===
+
==== Tested Hardware ====
  +
[[File:NXP_MIMXRT1170-EVKRevC1.jpg|none|thumb|NXP MIMXRT1170-EVK Rev. C1]]
'''Example project:''' [[Media:NXP_iMRT1176_M7_TracePins.zip | NXP_iMRT1176_M7_TracePins.zip]]
 
  +
  +
==== Example projects ====
  +
*'''iMXRT1176_M7:''' [[Media:NXP_iMXRT1176_M7_TracePins.zip | NXP_iMXRT1176_M7_TracePins.zip]]
  +
*'''iMXRT1176_M4:''' [[Media:NXP_iMXRT1176_M4_TracePins.zip | NXP_iMXRT1176_M4_TracePins.zip]]
  +
  +
==== 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].
  +
===== Trace clock signal quality =====
  +
The trace clock signal quality shows multiple trace clock cycles on the tested hardware as reference.
  +
[[File:IMXRT1176_EVK_Multiple_TCLK.png|none|thumb|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.
  +
[[File:IMXRT1176_EVK_RiseTime_TCLK.png|none|thumb|TCLK rise time]]
   
=== iMXRT1176_M4 ===
+
===== Setup time =====
  +
The setup time shows the relative setup time between a trace data signal and trace clock.
'''Example project:''' [[Media:NXP_iMXRT1176_M4_TracePins.zip | NXP_iMXRT1176_M4_TracePins.zip]]
 
  +
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:IMXRT1176_EVK_SetupTime_TD0.png|none|thumb|TD0 setup time]]

Latest revision as of 15:38, 16 August 2023

This article coverst the NXP i.MXRT1176 family devices. As for all i.MXRT11xx devices, JTAG is not active per default. Instead SWD can be used. To activate JTAG on this target device eFuses must be set. For more information see the corresponding target reference manual.

Tracing on iMXRT1176 series

This section describes how to get started with trace on the NXP iMXRT1176 MCUs. This section 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).

Note:

  • The sample projects come with a pre-configured project file for Ozone that runs out-of-the box.
  • The following sample project is designed to be used with J-Trace PRO and Ozone to demonstrate streaming trace.
  • In order to rebuild the sample project, SEGGER Embedded Studio can be used.
  • 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/.


Tracing on NXP iMXRT1176 dual core

Minimum requirements

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

  • J-Link software version V6.72b or later
  • Ozone V3.20 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 for streaming trace

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.

Streaming trace

The projects have been tested with the minimum requirements mentioned above. The board used for this example is not publicly available yet. To enable trace on the board some solder bridges had to be closed. For reference consult the manual of the board you are using. As the iMXRT1176 series is a dual core device two trace examples are available, one for the Cortex-M7 core and one for the Cortex-M4 core.

Tested Hardware

NXP MIMXRT1170-EVK Rev. C1

Example projects

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