Segger J-Link Debugger
Note
- This section contains preliminary information and is work-in-progress.
The CMSIS-Toolbox organizes for debuggers projects and configuration options. This chapter explains the usage of the Segger J-Link GDB Server in combination with the CMSIS-Toolbox.
- Extended Options explains additional configuration features that are required in specific use-cases.
Other manual sections describe how to configure debuggers:
- Run and Debug Configuration explains overall structure and how projects and images are configured.
- Debugger Configuration - J-Link Server contains details about the options that are specific to J-Link.
Extended Options
The section Debugger Configuration - J-Link Server contains the J-Link configuration for typical systems.
connect:
Configures the behavior for connecting J-Link to the hardware target for interactive debug.
connect: |
Description | |
|---|---|---|
mode: |
Required | Selects the connect mode: attach, halt (default). |
| Connect Mode | Description |
|---|---|
attach |
Do not change state of the core(s). No reset is executed. |
halt |
Halt core(s) after connect. |
reset:
Configures the reset behavior for each core when a reset is requested during interactive debug.
reset: |
Description | |
|---|---|---|
- pname: |
Optional | Identifies the processor (not requried for single core system). |
type: |
Required | Selects the reset type: hardware, system (default), core. |
| Reset Types | Description |
|---|---|
hardware |
Use the J-Link reset pin reset mode. |
system |
Use the J-Link normal reset mode. |
core |
Use the J-Link core reset mode. |
Examples:
debugger:
name: J-Link Server # default connect, halt and reset behavior
debugger:
name: J-Link Server
connect: attach # connect without reset and without CPU state change
reset:
- type: system # use system reset
debugger:
name: J-Link Server
connect: halt # halt CPU after connect
reset:
- pname: Core0 # for Core0
type: hardware # use hardware reset
- pname: Core1 # for Core1
type: core # use core reset