Difference between revisions of "J-Trace"

From SEGGER Wiki
Jump to: navigation, search
(General information about tracing)
Line 20: Line 20:
 
** [[SWO | SWO / SWV]]
 
** [[SWO | SWO / SWV]]
 
** [[SystemView]]
 
** [[SystemView]]
* General information about TRACE Coresight elements:
+
* General information about Arm Coresight trace elements:
 
** [[ETM]]
 
** [[ETM]]
 
** [[ETB]]
 
** [[ETB]]

Revision as of 10:14, 20 September 2022

THIS ARTICLE IS STILL IN PROGRESS
J-Trace is a SEGGER debug probe, specialized on live instruction tracing.

For the full feature set and best performance, it is recommended to use J-Trace in combination with the Ozone debugger.

For purchasing information and technical specification, please refer to the SEGGER homepage

General information about tracing

Available Trace features

J-Link

J-Trace

Tested devices

The tested devices page on the SEGGER homepage contains a variety of different devices, trace support has been tested with. For these devices example projects are available, including J-Link script files containing the required (pin) init. This is usually the best starting point if you want to trace a device, as it provides an out of the box experience.

Together with the J-Trace Pro, a trace reference board is shipped. For this board, a trace tutorial project is available on the SEGGER homepage.

Setting up Trace with J-Trace

If no example project is available for a specific device, and example project can be request via the official SEGGER Technical support. Otherwise, support can also be added manually.

Pinout / Trace debug interface

Usually, devices provide multiple trace pin combinations to use trace with. This also means, that the pins have to be initialized before tracing can work.

The trace pinout (19-pin) used by J-Trace can be used with JTAG and SWD:

The pins, clocks, etc. required for tracing can be initialized either via the device application, or via a J-Link Script file. Using a J-Link script file is generally recommended, as otherwise the init section of the code will not be traced when initializing trace from the target application.

Setting up Trace with Ozone

Setting up Trace with different IDEs

Trouble shooting

In this section multiple trouble shooting articles are referenced.

Trace related

J-Trace Probe / driver related