Lines Matching full:debug
3 Debug Probes
6 A *debug probe* is special hardware which allows you to control execution of a
7 Zephyr application running on a separate board. Debug probes usually allow
10 also support other debug software and more advanced features such as
12 software supported by Zephyr, see :ref:`flash-debug-host-tools`.
14 Debug probes are usually connected to your host workstation via USB; they
16 connect to the device running Zephyr using the JTAG or SWD protocols. Debug
21 an onboard debug probe, usb-to-serial adapter, and sometimes a drag-and-drop
22 flash programmer. This eliminates the need to purchase an external debug probe
23 and provides a variety of debug host tool options.
25 Several hardware vendors have their own branded onboard debug probe
26 implementations: NXP LPC boards have `LPC-Link2 <#lpclink2-jlink-onboard-debug-probe>`_,
27 NXP Kinetis (former Freescale) boards have `OpenSDA <#opensda-daplink-onboard-debug-probe>`_,
28 and ST boards have `ST-LINK <#stlink-v21-onboard-debug-probe>`_. Each onboard debug probe
30 their respective debug host tools. For example, an OpenSDA microcontroller can
31 be programmed with DAPLink firmware to communicate with pyOCD or OpenOCD debug
32 host tools, or with J-Link firmware to communicate with J-Link debug host
37 || *Debug Probes & Host Tools* | Host Tools …
39 | | **J-Link Debug** | **OpenOCD** | **pyOCD…
45 | Debug Probes | **OpenSDA J-Link** | ✓ | | …
51 | | **NXP S32 Debug Probe** | | | …
55 Some supported boards in Zephyr do not include an onboard debug probe and
56 therefore require an external debug probe. In addition, boards that do include
57 an onboard debug probe often also have an SWD or JTAG header to enable the use
58 of an external debug probe instead. One reason this may be useful is that the
59 onboard debug probe may have limitations, such as lack of support for advanced
61 onboard debug probe from interfering with the external debug probe.
63 .. _mcu-link-cmsis-onboard-debug-probe:
65 MCU-Link CMSIS-DAP Onboard Debug Probe
68 The CMSIS-DAP debug probes allow debugging from any compatible toolchain,
70 MCUXpresso extension for VS Code. In addition to debug probe functionality, the
80 This debug probe is compatible with the following debug host tools:
82 - :ref:`linkserver-debug-host-tools`
87 host tools plus the :ref:`linkserver-debug-host-tools`.
97 .. _mcu-link-jlink-onboard-debug-probe:
99 MCU-Link JLink Onboard Debug Probe
102 The MCU-Link J-Link is an onboard debug probe and usb-to-serial adapter
105 This debug probe is compatible with the following debug host tools:
107 - :ref:`jlink-debug-host-tools`
111 the :ref:`jlink-debug-host-tools` plus the MCU-Link host tools.
121 .. _lpclink2-cmsis-onboard-debug-probe:
123 LPC-LINK2 CMSIS DAP Onboard Debug Probe
126 The CMSIS-DAP debug probes allow debugging from any compatible toolchain,
129 As well as providing debug probe functionality, the LPC-Link2 probes also
150 .. _lpclink2-jlink-onboard-debug-probe:
152 LPC-Link2 J-Link Onboard Debug Probe
155 The LPC-Link2 J-Link is an onboard debug probe and usb-to-serial adapter
158 This debug probe is compatible with the following debug host tools:
160 - :ref:`jlink-debug-host-tools`
175 .. _opensda-daplink-onboard-debug-probe:
177 OpenSDA DAPLink Onboard Debug Probe
180 The OpenSDA DAPLink is an onboard debug probe and usb-to-serial adapter
184 This debug probe is compatible with the following debug host tools:
186 - :ref:`pyocd-debug-host-tools`
187 - :ref:`openocd-debug-host-tools`
192 Install the debug host tools before you program the firmware.
194 As with all OpenSDA debug probes, the steps for programming the firmware are:
208 device (debug port), and a mass storage device (drag-and-drop flash
211 .. _opensda-jlink-onboard-debug-probe:
213 OpenSDA J-Link Onboard Debug Probe
216 The OpenSDA J-Link is an onboard debug probe and usb-to-serial adapter
219 This debug probe is compatible with the following debug host tools:
221 - :ref:`jlink-debug-host-tools`
230 Install the debug host tools before you program the firmware.
232 As with all OpenSDA debug probes, the steps for programming the firmware are:
246 vendor-specific device (debug port).
248 .. _jlink-external-debug-probe:
250 J-Link External Debug Probe
253 `Segger J-Link`_ is a family of external debug probes, including J-Link EDU,
257 This debug probe is compatible with the following debug host tools:
259 - :ref:`jlink-debug-host-tools`
260 - :ref:`openocd-debug-host-tools`
262 Install the debug host tools before you program the firmware.
264 .. _stlink-v21-onboard-debug-probe:
266 ST-LINK/V2-1 Onboard Debug Probe
269 ST-LINK/V2-1 is a serial and debug adapter built into all Nucleo and Discovery
274 It is compatible with the following host debug tools:
276 - :ref:`openocd-debug-host-tools`
277 - :ref:`jlink-debug-host-tools`
281 - :ref:`pyocd-debug-host-tools`
293 Flash and debug with ST-Link
301 and debug tool. Flash and debug can be done as follows:
309 :goals: debug
314 host computer, you can flash and debug as follows:
331 To attach a debugger to your board and open up a debug console with ``jlink``.
335 west debug --runner jlink
378 .. _nxp-s32-debug-probe:
380 NXP S32 Debug Probe
383 `NXP S32 Debug Probe`_ enables NXP S32 target system debugging via a standard
384 debug port while connected to a developer's workstation via USB or remotely via
387 NXP S32 Debug Probe is designed to work in conjunction with NXP S32 Design Studio
388 (S32DS) and NXP Automotive microcontrollers and processors. Install the debug
389 host tools as in indicated in :ref:`nxp-s32-debug-host-tools` before you program
396 https://www.segger.com/products/debug-probes/j-link/models/other-j-links/lpcxpresso-on-board/
408 https://www.segger.com/products/debug-probes/j-link/
411 https://www.segger.com/products/debug-probes/j-link/models/other-j-links/st-link-on-board/
422 .. _NXP S32 Debug Probe:
423 https://www.nxp.com/design/software/automotive-software-and-tools/s32-debug-probe:S32-DP