Difference between revisions of "Debug Probes - J-Link & J-Trace"

From SEGGER Wiki
Jump to: navigation, search
(21 intermediate revisions by 6 users not shown)
Line 23: Line 23:
 
SEGGER J-Links are the most widely used line of debug probes available today. They've proven their value for more than 10 years in embedded development. This popularity stems from the unparalleled performance, extensive feature set, large number of supported CPUs, and compatibility with all popular development environments.
 
SEGGER J-Links are the most widely used line of debug probes available today. They've proven their value for more than 10 years in embedded development. This popularity stems from the unparalleled performance, extensive feature set, large number of supported CPUs, and compatibility with all popular development environments.
 
=== J-Link software ===
 
=== J-Link software ===
  +
* [[J-Link Installer]]
 
* [[J-Link software versioning]]
 
* [[J-Link software versioning]]
 
* [[J-Link_control_panel | J-Link control panel]]
 
* [[J-Link_control_panel | J-Link control panel]]
Line 40: Line 41:
 
* [[Setting up Ethernet interface]]
 
* [[Setting up Ethernet interface]]
 
* [[CFI Flash]]
 
* [[CFI Flash]]
  +
* [[J-Link:Nickname | Nickname feature]]
  +
* [[J-Link_Docker_Container | J-Link in a Docker Container]]
   
 
=== J-Link model specifics ===
 
=== J-Link model specifics ===
Line 47: Line 50:
 
* [[J-Trace PRO Cortex-M]]
 
* [[J-Trace PRO Cortex-M]]
 
* [[J-Trace PRO Cortex]]
 
* [[J-Trace PRO Cortex]]
  +
* [[J-Link-OB-K22-SiFive | J-Link OB K22 SiFive]]
   
 
=== Extending device support ===
 
=== Extending device support ===
Line 70: Line 74:
 
* [[Incorrect J-Link USB driver installed]]
 
* [[Incorrect J-Link USB driver installed]]
 
* [[J-Link application not starting]]
 
* [[J-Link application not starting]]
  +
* [[IDE accesses illegal memory regions]]
  +
* [[J-Link:Low power modes production | Low power modes production]]
   
 
=== Device specifics ===
 
=== Device specifics ===
 
==== ARM ====
 
* [[CoreLink SSE-200 Subsystem for MPS3]]
 
   
 
==== Ambiq Micro ====
 
==== Ambiq Micro ====
Line 81: Line 84:
 
==== Analog Devices ====
 
==== Analog Devices ====
 
* [[ADuC7xxx]]
 
* [[ADuC7xxx]]
  +
  +
==== AndesTech ====
  +
* [[J-Link:AndesTech A25 | A25 (RISC-V)]]
  +
  +
==== ARM ====
  +
* [[CoreLink SSE-200 Subsystem for MPS3]]
   
 
==== Atmel ====
 
==== Atmel ====
Line 90: Line 99:
 
* [[PSoC series | PSoC series devices]]
 
* [[PSoC series | PSoC series devices]]
 
* [[Traveo 2 CYT2B and CYT4B series devices]]
 
* [[Traveo 2 CYT2B and CYT4B series devices]]
  +
* [[Cypress S6J33xxx series devices]]
   
 
==== Dialog Semiconductor ====
 
==== Dialog Semiconductor ====
Line 116: Line 126:
 
* [[nRF51 Series Devices]]
 
* [[nRF51 Series Devices]]
 
* [[nRF52 Series Devices]]
 
* [[nRF52 Series Devices]]
  +
  +
==== Nuvoton ====
  +
* [[M2351]]
   
 
==== NXP ====
 
==== NXP ====
Line 153: Line 166:
 
==== Zilog ====
 
==== Zilog ====
 
* [[ZNEQ32_Z32F0xx3 series]]
 
* [[ZNEQ32_Z32F0xx3 series]]
  +
  +
=== Core specifics ===
  +
* [[J-Link:RISC-V | RISC-V]]
   
 
=== Evaluation board specifics ===
 
=== Evaluation board specifics ===
Line 178: Line 194:
 
* [[CEC1702 clicker]]
 
* [[CEC1702 clicker]]
 
* [[SAMA5D2 XPlained Ultra]]
 
* [[SAMA5D2 XPlained Ultra]]
  +
  +
==== Nuvoton ====
  +
* [[NuMaker-PFM-M2351]]
   
 
==== Renesas ====
 
==== Renesas ====
Line 271: Line 290:
 
* [[Tracing on NXP Kinetis MKW36A]]
 
* [[Tracing on NXP Kinetis MKW36A]]
 
* [[Tracing on NXP Kinetis KE1xZ]]
 
* [[Tracing on NXP Kinetis KE1xZ]]
  +
* [[Tracing on NXP S32K148]]
 
* [[Tracing on Renesas Synergy R7FS7G2]]
 
* [[Tracing on Renesas Synergy R7FS7G2]]
 
* [[Tracing on Renesas Synergy R7FS5D5]]
 
* [[Tracing on Renesas Synergy R7FS5D5]]
Line 321: Line 341:
 
== J-Flash ==
 
== J-Flash ==
 
* [[CRC calculation]]
 
* [[CRC calculation]]
  +
  +
== J-Flash SPI ==
  +
* [[Adesto AT25PExx/AT45DBxx1E serial Flashes]]
   
 
== IDE and Debugger specifics ==
 
== IDE and Debugger specifics ==
Line 332: Line 355:
 
* [[Renesas e²studio]]
 
* [[Renesas e²studio]]
 
* [[TI Code Composer Studio]]
 
* [[TI Code Composer Studio]]
  +
* [[Visual Studio Code ]]
  +
* [[System Workbench]]
   
 
== Ozone ==
 
== Ozone ==

Revision as of 16:00, 10 September 2019

The J-Link debug probes with their outstanding performance, robustness, and ease of use are the market leading debug probes today. The J-Trace PRO sets a benchmark for instruction tracing with its streaming trace function that enables unlimited tracing at full clock speed.

This wiki page explains and links to details and device specifics that can not be found on the debug and trace probes product pages.

Glossary / Definitions of Debug and Trace specific terms

J-Link

SEGGER J-Links are the most widely used line of debug probes available today. They've proven their value for more than 10 years in embedded development. This popularity stems from the unparalleled performance, extensive feature set, large number of supported CPUs, and compatibility with all popular development environments.

J-Link software

J-Link model specifics

Extending device support

Troubleshooting

Device specifics

Ambiq Micro

Analog Devices

AndesTech

ARM

Atmel

Cypress

Dialog Semiconductor

Infineon

Intel

MediaTek

Microchip

Nordic Semi

Nuvoton

NXP

Renesas

Silicon Labs

SiFive

ST

Syntacore

TI

Toshiba

Xilinx

Zilog

Core specifics

Evaluation board specifics

ARM

Ambiq Micro

Adafruit

Atmel

Infineon

MediaTek

Microchip

Nuvoton

Renesas

SiFive

Silicon Labs

Syntacore

TI

NXP

ST

Xilinx

Flash programming

J-Trace

J-Trace PRO is an advanced debug probe that supports the advanced tracing features of Arm Cortex cores. It can capture complete instruction traces over long periods of time—thereby enabling the recording of infrequent, hard-to-reproduce bugs. This is particularly helpful when the program flow "runs off the rails" and stops in a fault state. Using the right software tools, J-Trace PRO trace probes are particularly helpful in analyzing system behaviour enabling uninstrumented live code coverage and code profiling.

Device Specifics

Keil MDK

RTT

WebUSB

J-Flash

J-Flash SPI

IDE and Debugger specifics

Ozone

FAQ

Glossary / Definitions