Lines Matching refs:debug
1 .. _flash-debug-host-tools:
7 flash and debug Zephyr applications.
10 ``debug``, ``debugserver``, and ``attach`` commands, provided your board
12 file declares that support properly. See :ref:`west-build-flash-debug` for
209 .. _linkserver-debug-host-tools:
214 Linkserver is a utility for launching and managing GDB servers for NXP debug probes,
217 with custom debug configurations based on GNU tools or as part of a headless solution
219 LPC11U35-based and OpenSDA based standalone or on-board debug probes from NXP.
222 This method will also install the tools supporting the debug probes below,
225 LinkServer is compatible with the following debug probes:
227 - :ref:`lpclink2-cmsis-onboard-debug-probe`
228 - :ref:`mcu-link-cmsis-onboard-debug-probe`
229 - :ref:`opensda-daplink-onboard-debug-probe`
252 #. debug
265 2. With multiple debug probes attached to the host, use the
284 .. _jlink-debug-host-tools:
289 Segger provides a suite of debug host tools for Linux, macOS, and Windows
297 These debug host tools are compatible with the following debug probes:
299 - :ref:`lpclink2-jlink-onboard-debug-probe`
300 - :ref:`opensda-jlink-onboard-debug-probe`
301 - :ref:`mcu-link-jlink-onboard-debug-probe`
302 - :ref:`jlink-external-debug-probe`
303 - :ref:`stlink-v21-onboard-debug-probe`
314 .. _openocd-debug-host-tools:
324 These debug host tools are compatible with the following debug probes:
326 - :ref:`opensda-daplink-onboard-debug-probe`
327 - :ref:`jlink-external-debug-probe`
328 - :ref:`stlink-v21-onboard-debug-probe`
341 .. _pyocd-debug-host-tools:
351 These debug host tools are compatible with the following debug probes:
353 - :ref:`lpclink2-cmsis-onboard-debug-probe`
354 - :ref:`mcu-link-cmsis-onboard-debug-probe`
355 - :ref:`opensda-daplink-onboard-debug-probe`
356 - :ref:`stlink-v21-onboard-debug-probe`
360 .. _lauterbach-trace32-debug-host-tools:
388 system directory. Then execute ``west flash`` or ``west debug`` commands to
389 flash or debug the Zephyr application as detailed in :ref:`west-build-flash-debug`.
390 The ``debug`` command launches TRACE32 GUI to allow debug the Zephyr
411 .. _nxp-s32-debug-host-tools:
416 :ref:`nxp-s32-debug-probe` is designed to work in conjunction with
421 the necessary debug host tools and associated USB device drivers.
428 1. debug
445 west debug --s32ds-path=/opt/NXP/S32DS.3.5
451 west debug --s32ds-path=C:\NXP\S32DS.3.5
453 If multiple S32 debug probes are connected to the host via USB, the runner will
456 via ``--dev-id=<connection-string>``. Consult NXP S32 debug probe user manual
462 west debug --dev-id='s32dbg:00:04:9f:00:ca:fe'
464 It is possible to pass extra options to the debug host tools via ``--tool-opt``.
465 When executing ``debug`` or ``attach`` commands, the tool options will be passed
468 afterwards detach the debug session:
472 west debug --tool-opt='--batch'
478 out-of-the-box support for a variety of debug probes, including CMSIS-DAP,
494 through both the debug interface (JTAG and SWD) and the bootloader interface (UART and USB DFU, I2C…
504 It is compatible with the following debug probes:
506 - :ref:`stlink-v21-onboard-debug-probe`
507 - :ref:`jlink-external-debug-probe`