J-Trace PRO is an advanced debug probe that supports the advanced tracing features of Arm Cortex cores. It captures complete instruction traces over long periods of time which enables the recording of infrequent, hard-to-reproduce bugs. This is helpful when the program flow “runs off the rails” and stops in a fault state.
J-Trace PRO offers the best possible trace experience. This is thanks to our toolchain-independent debug software, Ozone, which has an extensive example project library (which includes most popular target devices).
J-Trace PRO’s main feature is Streaming Trace. It processes instruction trace data sent from a target device in real time, using trace pins. This lets users know where the target device is, and what it is doing – at any point in time. With Streaming Trace, users get deep insight into any application running on the target device whilst offering additional, powerful debug strategies to apply.
Another powerful feature is Real-Time Profiling: this makes visible which instructions have been executed and how often. Users can address application run time hotspots and identify opportunities to optimize them. These profiles can later be exported using a tool like the Ozone debugger for documentation and analysis purposes.
Through Real-Time Code Coverage, engineers gain fully accurate information about instruction execution on a target application. Engineers can see which parts of the application code have been executed.
As a market leading trace probe, J-Trace PRO boasts an extensive list of features that fulfill any embedded developers’ debugging needs. Streaming Trace, Real-Time Code Coverage and Real-Time Code Profiling are just the beginning. With unlimited trace, developers can isolate and identify hard-to-find code defects. There is also trace support for Cortex-A/R/M target devices.
It doesn’t end there. J-Trace PRO offers cross-platform support for Windows, macOS and Linux making it very versatile. This is also reflected in its support for most popular IDEs. The free, stand-alone debugger Ozone can be used for any toolchain to enable tracing. And for quick, easy first steps there are Trace Reference Boards (see below).
J-Trace PRO is designed to work out-of-the-box with most trace-capable target devices. There is an extensive, regularly-updated list of tested target devices with the latest target device releases. In all other cases J-Trace PRO offers additional features that can make any trace setup possible. It has never been easier to get a trace up and running.
Please note: The J-Trace tutorial can be found here.
Each J-Trace PRO package comes with a Cortex-M Trace Reference Board included. Other Trace Reference Boards based on other target devices are also available. The Trace Reference Boards are perfect for quick and simple trace setups and can be used as reference for custom board designs.
Hardware features like Ethernet interface, USB full- / superspeed interface, etc. are features specific to J-Trace models. These cannot be updated or changed by software updates. Want more information? Be sure to take a look at our J-Trace Pro model overview.
|Feature||J-Trace PRO Cortex-M||J-Trace PRO Cortex|
|USB||3.0 (SuperSpeed)||3.0 (SuperSpeed)|
|Unlimited Streaming Trace + Live Analysis|
|Cortex-M ETM Trace|
|Cortex-A ETM Trace|
|Cortex-A PTM Trace|
|Cortex-R ETM Trace|
|Max. CPU frequency|
|Max. TPIU frequency||300 MHz||300 MHz|
|Max. trace clock frequency||150 MHz||150 MHz|
|Additional information||More information||More information|
J-Trace PRO Cortex
J-Trace PRO Cortex-M
Q: What is the advantage of using the J-Trace PRO over other trace probes?
A: One of the biggest advantages of the J-Trace PRO is its streaming trace capability. Streaming trace allows for continuous live trace analyses, enabling debugging for even the most complex problems.
Q: What are the other differences to the older J-Trace for Cortex-M?
A: J-Trace PRO can now work with trace clocks of up to 150 MHz (300 MHz CPU clock) and is equipped with Gigabit Ethernet for streaming trace and remote debugging. Its debug interface speed has also doubled; additionally J-Trace PRO has more options for configuration and troubleshooting which is easily available through the integrated web server. For more information take a look at our J-Trace vs. J-Trace PRO comparison.
Q: Can I use the J-Trace PRO as a debug probe?
A: Yes. The J-Trace PRO includes all capabilities of the J-Link debug probes and comes with all licenses, such as for unlimited flash breakpoints. It can be used with the J-Link Software and any tool that supports the J-Link.
Q: Can the J-Trace PRO be used with any IDE?
A: Yes. The J-Trace PRO can be used with all common IDEs, just like any J-Link debug probe.
Q: Can any IDE be used for tracing as well?
A: Unfortunately most IDE vendors do not offer trace analysis features. If they do, it is only to a limited degree.
Q: What can I use for tracing and analysis?
A: We recommend using the graphical standalone debugger Ozone. It supports all J-Trace PRO capabilities and compliments them with its advanced analysis features. Ozone can be used independent of a compiler, with the output of any IDE or toolchain. It can also be used completely free of charge with a J-Trace PRO, even for commercial use.
Q: What do I need in order to trace with a J-Trace PRO?
A: Just connect the target device and start debugging. J-Trace PRO is designed to simply get working. It can be up and running in less than 10 minutes.
Q: Where can I find trace-related troubleshooting information?
A: Tracing is a very hardware-dependent debug technique and some target hardware modifications or designs can cause issues when trying to set up the trace debug interface. To give our customers a simple to use troubleshooting platform with the most asked questions answered we have created the following setup page: Setting up Trace.
Any more questions? Please contact us.
Q: Are there any trace example projects that I can use for orientation?
A: Yes, every J-Trace PRO gets shipped with a Cortex-M Trace Reference Board. An example project is part of the J-Trace tutorial. We also created a list of tested devices that each come with an example project that runs out-of-the-box with a J-Trace PRO and Ozone. The list is available here and is updated regularly.
Q: My device is not on the tested devices list, what can i do to get an example project for it?
A: The trace capable MCU market is growing and it is becoming harder to keep track of all devices. If we don't happen to have a trace example for your particular device, feel free to contact us.
The requirements for adding a new example project are:
- Must be supported by J-Link software: overview of supported CPUs and devices
- The target hardware must be publicly available and an evaluation board
- Trace pins must be physically connected to the trace debug interface