Difference between revisions of "Debug Probes - J-Link & J-Trace"
| Line 517: | Line 517: | ||
* [[Tracing on NXP LPC1788]] |
* [[Tracing on NXP LPC1788]] |
||
* [[Tracing on NXP LPC1857]] |
* [[Tracing on NXP LPC1857]] |
||
| − | * [[Tracing on Renesas Synergy R7FS7G2]] |
||
| − | * [[Tracing on Renesas Synergy R7FS5D5]] |
||
| − | * [[Tracing on Renesas R7S721001WS (RZ/A1H)]] |
||
| − | * [[Tracing on Renesas R7S910017 (RZ/T1)]] |
||
* [[Tracing on Silicon Labs EFM32GG11B]] |
* [[Tracing on Silicon Labs EFM32GG11B]] |
||
* [[Tracing on Silicon Labs EFM32GG990]] |
* [[Tracing on Silicon Labs EFM32GG990]] |
||
| Line 527: | Line 523: | ||
* [[Tracing on Silicon Labs EZR32LG330]] |
* [[Tracing on Silicon Labs EZR32LG330]] |
||
* [[Tracing on Silicon Labs EZR32WG330]] |
* [[Tracing on Silicon Labs EZR32WG330]] |
||
| − | * [[Tracing on ST STM32F107]] |
||
| − | * [[Tracing on ST STM32F207]] |
||
| − | * [[Tracing on ST STM32F303]] |
||
| − | * [[Tracing on ST STM32F407 (SEGGER Cortex-M Trace Reference Board)]] |
||
| − | * [[Tracing on ST STM32F417]] |
||
| − | * [[Tracing on ST STM32F429]] |
||
| − | * [[Tracing on ST STM32F437]] |
||
| − | * [[Tracing on ST STM32F439]] |
||
| − | * [[Tracing on ST STM32F446]] |
||
| − | * [[Tracing on ST STM32F746]] |
||
| − | * [[Tracing on ST STM32F756]] |
||
| − | * [[Tracing on ST STM32F767]] |
||
| − | * [[Tracing on ST STM32F769]] |
||
| − | * [[Tracing on ST STM32F779]] |
||
| − | * [[Tracing on ST STM32H743 (SEGGER STM32H7 Trace Reference Board)]] |
||
| − | * [[Tracing on ST STM32H743]] |
||
| − | * [[Tracing on ST STM32H753]] |
||
| − | * [[Tracing on ST STM32L476]] |
||
| − | * [[Tracing on ST STM32L4R]] |
||
| − | * [[Tracing on ST STM32L4S]] |
||
| − | * [[Tracing on ST STM32L552]] |
||
| − | * [[Tracing on ST STM32L152]] |
||
* [[Tracing on TI MSP432E4]] |
* [[Tracing on TI MSP432E4]] |
||
* [[Tracing on TI RM57L843]] |
* [[Tracing on TI RM57L843]] |
||
Revision as of 13:46, 3 April 2023
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.
Contents
- 1 Documentation
- 2 Glossary / Definitions of Debug and Trace specific terms
- 3 J-Link
- 3.1 J-Link software
- 3.2 J-Link hardware
- 3.3 J-Link model specifics
- 3.4 Extending device support
- 3.5 Troubleshooting
- 3.6 Device specifics
- 3.6.1 ABOV
- 3.6.2 Alif Semiconductor
- 3.6.3 Altera
- 3.6.4 Ambiq Micro
- 3.6.5 Analog Devices
- 3.6.6 AndesTech
- 3.6.7 ARM
- 3.6.8 Atmel
- 3.6.9 AutoChips
- 3.6.10 CloudBEAR
- 3.6.11 ClouderSemi
- 3.6.12 Codasip
- 3.6.13 China Key System (CKS)
- 3.6.14 Dialog Semiconductor
- 3.6.15 Geehy
- 3.6.16 GigaDevice
- 3.6.17 Hilscher
- 3.6.18 HPMicro
- 3.6.19 HSXP
- 3.6.20 IndieSemi
- 3.6.21 Infineon
- 3.6.22 Intel
- 3.6.23 Maxim
- 3.6.24 MediaTek
- 3.6.25 Microchip
- 3.6.26 Nordic Semi
- 3.6.27 Nuvoton
- 3.6.28 NXP
- 3.6.29 O2Micro
- 3.6.30 ON Semiconductor
- 3.6.31 Qorvo
- 3.6.32 Raspberry Pi
- 3.6.33 Renesas
- 3.6.34 Silicon Labs
- 3.6.35 SiFive
- 3.6.36 ST
- 3.6.37 Syntacore
- 3.6.38 Telink
- 3.6.39 TI
- 3.6.40 Toshiba
- 3.6.41 Xilinx
- 3.6.42 Zilog
- 3.7 Core specifics
- 3.8 Evaluation board specifics
- 3.8.1 ABOV
- 3.8.2 Altera
- 3.8.3 ARM
- 3.8.4 Ambiq Micro
- 3.8.5 Analog Devices
- 3.8.6 Adafruit
- 3.8.7 Arduino
- 3.8.8 Atmel
- 3.8.9 AutoChips
- 3.8.10 BBC
- 3.8.11 ElectroSmith
- 3.8.12 Geehy
- 3.8.13 GigaDevice
- 3.8.14 HPMicro
- 3.8.15 HSXP
- 3.8.16 IndieSemi
- 3.8.17 Infineon
- 3.8.18 MediaTek
- 3.8.19 Microchip
- 3.8.20 Nordic Semiconductor
- 3.8.21 Nuvoton
- 3.8.22 NXP
- 3.8.23 OKdo
- 3.8.24 ON Semiconductor
- 3.8.25 Qorvo
- 3.8.26 RaspberryPi
- 3.8.27 Renesas
- 3.8.28 SiFive
- 3.8.29 Silicon Labs
- 3.8.30 Syntacore
- 3.8.31 STM32Duino
- 3.8.32 Telink
- 3.8.33 TI
- 3.8.34 Samsung
- 3.8.35 ST
- 3.8.36 Xilinx
- 3.9 Flash programming
- 4 J-Trace
- 5 RTT
- 6 WebUSB
- 7 J-Flash
- 8 J-Flash SPI
- 9 IDE and Debugger specifics
- 10 Ozone
- 11 TIF specifics
- 12 FAQ
- 13 Glossary / Definitions
Documentation
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 Installer
- J-Link Registration
- Linux specifics
- J-Link Software CMSIS-DAP
- J-Link software versioning
- J-Link Device Policy
- J-Link control panel
- J-Link Remote Server
- J-Link Software and Documentation Pack
- J-Link GUI Software
- Enable J-Link log file
- Selecting the correct device
- Using J-Link Script Files
- Using J-Link Command Strings
- Using J-Link VCOM functionality
- Using JLinkDevices.xml
- J-Link Commander
- Memory accesses
- Setting up Ethernet interface
- CFI Flash
- Nickname feature
- J-Link in a Docker Container
- How to use SWO with J-Link GDB Server
- Single board computer with J-Link software package support
- Flashloader behaviour
- Custom RAMCode SDK (discontinued)
- J-Link CoreSight support
- How to update the J-Link DLL
- J-Link on Windows ARM
- J-Link on VirtualBox
- Working with multiple flashloader
J-Link hardware
J-Link model specifics
For an overview which hardware versions of the different models support which features, please refer to the model feature overview.
- J-Link OB
- J-Link CALLIOPE mini
- J-Link EDU Mini
- J-Trace PRO Cortex-M
- J-Trace PRO Cortex
- J-Link OB K22 SiFive
- J-Link OB K22 Cortex-A
- J-Link OB K22 Cortex-M
- J-Link OB SAM3U NordicSemi
- J-Link OB K22 NordicSemi
- J-Link OB nRF5340 NordicSemi
- OEM models overview
- J-Link OB S124 Renesas
- Using J-Link via WiFi
Extending device support
Troubleshooting
- J-Link model specific
- J-Trace model specific
- Debug session does not start
- J-Link cannot connect to the CPU
- Could not open J-Link shared library
- J-Link shown as generic BULK device in Windows
- SPI Flash
- Unlimited Number of Breakpoints in Flash
- Debugging self-modifying code in flash
- Cannot update firmware of Flasher Portable
- Manual setup of JTAG chain
- Access to illegal addresses causes core to crash
- J-Link no USB enumeration
- ARM Cortex-M - Application uses cycle counter
- J-Link LITE incorrectly shown as SAM-ICE
- Incorrect J-Link USB driver installed
- J-Link application not starting
- IDE accesses illegal memory regions
- Low power modes production
- J-Trace driver (WinUSB) is installed but the driver could not be started
- J-Link debugging USB applications
- J-Link in Parallels Desktop for Mac
Device specifics
ABOV
Alif Semiconductor
Altera
Ambiq Micro
Analog Devices
AndesTech
ARM
Atmel
AutoChips
CloudBEAR
ClouderSemi
Codasip
China Key System (CKS)
Dialog Semiconductor
Geehy
GigaDevice
Hilscher
HPMicro
HSXP
IndieSemi
Infineon
Intel
Maxim
MediaTek
Microchip
Nordic Semi
Nuvoton
NXP
O2Micro
ON Semiconductor
Qorvo
Raspberry Pi
Renesas
Silicon Labs
SiFive
ST
Syntacore
Telink
TI
- TM4C Security
- TMS470Rx series
- TMS570Lx series
- MSPM0G series
- MSPM0L series
- RM4xL series
- RM5xL series
- AM335x series
Toshiba
Xilinx
Zilog
Core specifics
Evaluation board specifics
ABOV
Altera
ARM
Ambiq Micro
Analog Devices
Adafruit
Arduino
Atmel
AutoChips
BBC
ElectroSmith
Geehy
- APM32E103ZET6
- APM32F003F6P6
- APM32F030RCT6
- APM32F051R8T6
- APM32F072VBT6
- APM32F091VCT6
- APM32F103ZET6
- APM32F407VGT6
GigaDevice
HPMicro
HSXP
IndieSemi
Infineon
MediaTek
Microchip
Nordic Semiconductor
Nuvoton
NXP
OKdo
ON Semiconductor
Qorvo
RaspberryPi
- Raspberry Pi Pico evaluation board
- Pimoroni Tiny 2040 evaluation board
- SparkFun MicroMod RP2040 evaluation board
- SparkFun Thing Plus RP2040 evaluation board
Renesas
SiFive
- SiFive Arty FPGA Dev Kit
- GroupGets LoFive R1.1
- SiFive HiFive1
- SiFive E21 Standard Core Dev Kit (ARTY-100T)
- SiFive E24 Standard Core Dev Kit (ARTY-100T)
- SiFive E34 Standard Core Dev Kit (ARTY-100T)
- SiFive E76 Standard Core Dev Kit (ARTY-100T)
- SiFive S21 Standard Core Dev Kit (ARTY-100T)
- SiFive S51 Standard Core Dev Kit (ARTY-100T)
- SiFive S54 Standard Core Dev Kit (ARTY-100T)
- SiFive S76 Standard Core Dev Kit (ARTY-100T)
Silicon Labs
Syntacore
STM32Duino
Telink
TI
- LAUNCHXL CC2640R2
- LAUNCHXL CC2650
- LAUNCHXL CC26X2R1
- CC1310 LaunchPad
- CC1350 LaunchPad
- CC3220 LaunchPad
- TM4C123G LaunchPad
- TI EK-TM4C1294XL
- TI LP-MSPM0G3507
- TI LP-MSPM0L1306
Samsung
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.
- J-Trace main article
- General information about tracing
- MTB specifics
- How to configure JLinkScript files to enable tracing
- Getting unknown addresses in instruction trace
- SiFive Insight
- J-Trace overflow error
Device Specifics
- Tracing on Atmel ATSAMA5D2
- Tracing on Atmel ATSAMD51
- Tracing on Atmel ATSAME54
- Tracing on Atmel ATSAME70
- Tracing on Atmel ATSAMV71
- Tracing on Hilscher netX90
- Tracing on Infineon Traveo II (CYT2B7)
- Tracing on Infineon XMC4400 series MCUs
- Tracing on Infineon XMC4500 series MCUs
- Tracing on Nordic Semiconductor nRF52
- Tracing on Nordic Semiconductor nRF52832
- Tracing on Nordic Semiconductor nRF52840
- Tracing on NXP iMX RT1050 (iMX RT1050 Trace Reference Board)
- Tracing on NXP LPC1788
- Tracing on NXP LPC1857
- Tracing on Silicon Labs EFM32GG11B
- Tracing on Silicon Labs EFM32GG990
- Tracing on Silicon Labs EFM32PG12
- Tracing on Silicon Labs EFR32MG12
- Tracing on Silicon Labs EZR32LG330
- Tracing on Silicon Labs EZR32WG330
- Tracing on TI MSP432E4
- Tracing on TI RM57L843
- Tracing on TI TM4C129
- Tracing on Toshiba TMPM370
- Tracing on Toshiba TMPM440
Keil MDK
RTT
WebUSB
J-Flash
J-Flash SPI
- Adesto AT25PExx/AT45DBxx1E serial Flashes
- Infineon S25Hx256T / S25Hx512T / S25Hx01GT serial flash
- Winbond W25M512JVFIQ serial Flash
IDE and Debugger specifics
- SEGGER Embedded Studio
- Atmel Studio
- Atollic TrueSTUDIO
- CooCox CoIDE
- Cosmic ZAP
- Eclipse
- emIDE
- Emprog Thunderbench
- IAR EWARM
- IAR EWRX
- IDA Pro incl. ARM Decompiler
- Infineon DAVE 4
- iSystem WinIDEA Open
- J-Link Commander
- Keil MDK-ARM
- Mentor Sourcery CodeBench
- Microchip MPLAB X
- NXP CodeWarrior
- NXP KDS
- NXP LPCXpresso Free Edition
- NXP MCUXpresso Free Edition
- ON Semiconductor IDE
- Renesas HEW
- Renesas e²studio
- Rowley CrossWorks
- STM32CubeIDE
- Silicon Labs Simplicity Studio
- SysProgs VisualGDB
- System Workbench
- TASKING VX-toolset
- TI Code Composer Studio
- Visual Studio Code
Ozone
- About
- Automated test example
- Dual core debugging example based on NXP LPC4350
- Start debug session with bootloader
- Watch window expression examples
TIF specifics
FAQ
- Using Ethernet in TI's Code Composer Studio (CCS)
- Software and Hardware Features Overview
- Multiple J-Links at the same PC
- OpenOCD
- Using J-Link on VirtualBox under Ubuntu
- Flashing Infineon PSoC Creator output data files with J-Flash
- Programming External SPI Flashes
- Unlock maximum SWO speed on SEGGER's high end debug probes
- J-Trace vs. J-Trace PRO
- How to connect JTAG nTRST when using 19-pin trace header
- How to reset "Don't show again" settings
