Searched refs:debug (Results 251 – 275 of 846) sorted by relevance
1...<<11121314151617181920>>...34
| /Zephyr-latest/boards/others/stm32f103_mini/doc/ |
| D | index.rst | 124 bootloader, and another by using the SWD debug port (which requires additional
143 You can debug an application in the usual way. Here is an example for the
150 :goals: debug
|
| /Zephyr-latest/boards/gd/gd32f407v_start/doc/ |
| D | index.rst | 129 #. To debug an image:
134 :goals: debug
137 When using J-Link, append ``--runner jlink`` option after ``west debug``.
|
| /Zephyr-latest/boards/gaisler/generic_leon3/doc/ |
| D | index.rst | 37 GRMON debug monitor v3.2.8 eval version
121 * `GRMON3 debug monitor <https://www.gaisler.com/index.php/products/debug-tools/grmon3>`_
|
| /Zephyr-latest/boards/nxp/mimxrt1170_evk/doc/ |
| D | index.rst | 337 A debug probe is used for both flashing and debugging the board. The on-board
341 - MIMXRT1170-EVKB: :ref:`mcu-link-cmsis-onboard-debug-probe`
342 - MIMXRT1170-EVK: :ref:`opensda-daplink-onboard-debug-probe`
348 :ref:`jlink-debug-host-tools` and make sure they are in your search path.
350 There are two options: the onboard debug circuit can be updated with Segger
351 J-Link firmware, or :ref:`jlink-external-debug-probe` can be attached to the
358 Install the :ref:`linkserver-debug-host-tools` and make sure they are in your
368 Alternatively, pyOCD can be used to flash and debug the board by using the
427 :goals: debug
|
| /Zephyr-latest/boards/st/stm32h7s78_dk/support/ |
| D | openocd.cfg | 8 # Enable debug when in low power modes
|
| /Zephyr-latest/subsys/net/lib/sntp/ |
| D | Kconfig | 25 module-help = Enable debug message of SNTP client library.
|
| /Zephyr-latest/boards/st/nucleo_wl55jc/doc/ |
| D | nucleo_wl55jc.rst | 26 - MIPI debug connector
33 mass storage, Virtual COM port, and debug port
154 - Serial-wire debug (SWD), JTAG
254 Nucleo WL55JC board includes an STLINK-V3 embedded debug tool interface.
302 sleep mode. Unfortunately, default openocd configuration, which is debug
311 You can debug an application in the usual way. Here is an example for the
318 :goals: debug
|
| /Zephyr-latest/boards/cypress/cy8ckit_062_ble/doc/ |
| D | index.rst | 10 enables design and debug of the Cypress PSOC 63 BLE MCU.
53 17. PSOC 6 debug and trace header (J12)
55 19. PSOC 6 program and debug header (J11)
143 3. Add the OpenOCD executable file's path to west flash/debug.
145 5. Debug using: west debug --openocd path/to/infineon/openocd/bin/openocd
152 communication over USB. There are also PSOC 6 program and debug headers J11
230 repeat the steps on programming and debug and add the following parameter
|
| /Zephyr-latest/ |
| D | .gitlint | 12 # Enable debug mode (prints more output). Disabled by default
13 debug = false
|
| /Zephyr-latest/tests/bluetooth/controller/ctrl_isoal/ |
| D | Kconfig | 21 bool "ISO-AL verbose debug logging"
25 Use this option to enable ISO-AL verbose debug logging.
|
| /Zephyr-latest/boards/seeed/lora_e5_mini/doc/ |
| D | index.rst | 154 The LoRa-E5 mini does not include a on-board debug probe.
155 But the module can be debugged by connecting an external debug probe to the
172 Connect the LoRa-E5 to your host computer using the external debug probe.
194 You can debug an application in the usual way. Here is an example for the
201 :goals: debug
|
| /Zephyr-latest/boards/witte/linum/doc/ |
| D | index.rst | 19 - 1 UART serial for debug
357 For debugging or programming Linum you will need to use an external debug
358 debug or flash tool and connect it to the SWD Connnector. JLink or ST-Link
391 You can debug an application in the usual way. Here is an example for the
398 :goals: debug
|
| /Zephyr-latest/boards/infineon/cy8cproto_062_4343w/doc/ |
| D | index.rst | 7 platform that enables design and debug of PSOC 6 MCUs. It comes with a Murata
108 …ebugging, flash programming, and serial communication over USB. Flash and debug commands use OpenO…
134 west debug
147 west debug
149 Once the gdb console starts after executing the west debug command, you may now set breakpoints and…
|
| /Zephyr-latest/boards/ct/ctcc/doc/ |
| D | index.rst | 148 1. Using an external :ref:`debug probe <debug-probes>`
157 Connectivity Card can be programmed using an external debug probe (Segger J-Link) by connecting
160 For Segger J-Link debug probes, follow the instructions in the
244 These boards do not have an on-board J-Link debug IC, however
|
| /Zephyr-latest/boards/gaisler/gr716a_mini/doc/ |
| D | index.rst | 11 * FTDI USB interface for UART debug link (AHBUART) and application UART
23 first APBUART peripheral (apbuart0). The UART debug forwarding setting,
48 GRMON debug monitor v3.2.8
206 * `GRMON3 debug monitor <https://www.gaisler.com/index.php/products/debug-tools/grmon3>`_
|
| /Zephyr-latest/scripts/logging/dictionary/ |
| D | database_gen.py | 436 logger.debug('Found string via extraction at ' + PTR_FMT + ': %s',
446 logger.debug('Found null string via extraction at ' + PTR_FMT,
473 logger.debug('Found string variable at ' + PTR_FMT + ': %s',
506 if args.debug:
|
| /Zephyr-latest/boards/renesas/ek_ra4m2/doc/ |
| D | index.rst | 47 - Debug LED (yellow) indicating the debug connection
143 You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
145 Once downloaded and installed, open Segger Ozone and configure the debug project
154 **Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
|
| /Zephyr-latest/boards/renesas/ek_ra4m3/doc/ |
| D | index.rst | 49 - Debug LED (yellow) indicating the debug connection
145 You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
147 Once downloaded and installed, open Segger Ozone and configure the debug project
156 **Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
|
| /Zephyr-latest/boards/renesas/ek_ra6m4/doc/ |
| D | index.rst | 47 - Debug LED (yellow) indicating the debug connection
146 You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
148 Once downloaded and installed, open Segger Ozone and configure the debug project
157 **Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
|
| /Zephyr-latest/boards/infineon/cy8ckit_062s2_ai/doc/ |
| D | index.rst | 7 enables design and debug of PSOC 6 MCUs.
92 Flash and debug commands use OpenOCD and require a custom Infineon OpenOCD version,
130 west debug
143 west debug
|
| /Zephyr-latest/boards/st/stm32f412g_disco/doc/ |
| D | index.rst | 16 - debug port
136 STM32F412G-DISCO Discovery kit includes an ST-LINK/V2 embedded debug tool interface.
185 You can debug an application in the usual way. Here is an example for the
192 :goals: debug
|
| /Zephyr-latest/boards/st/stm32f413h_disco/doc/ |
| D | index.rst | 16 - debug port
135 STM32F413H-DISCO Discovery kit includes an ST-LINK/V2 embedded debug tool interface.
184 You can debug an application in the usual way. Here is an example for the
191 :goals: debug
|
| /Zephyr-latest/boards/st/stm32g071b_disco/doc/ |
| D | index.rst | 41 mass storage, Virtual COM port and debug port
111 The STM32G071B Discovery board includes an ST-LINK/V2-1 embedded debug tool interface.
142 You can debug an application in the usual way. Here is an example for the
149 :goals: debug
|
| /Zephyr-latest/boards/olimex/stm32_e407/doc/ |
| D | index.rst | 66 JTAG/SWD debug
315 The OLIMEX-STM32-E407 board does not include an embedded debug tool
353 Provided that you have a JTAG probe, you can debug an application in the usual
360 :goals: debug
|
| /Zephyr-latest/boards/olimex/stm32_h407/doc/ |
| D | index.rst | 68 JTAG/SWD debug
317 The OLIMEX-STM32-H407 board does not include an embedded debug tool
356 Provided that you have a JTAG probe, you can debug an application in the usual
363 :goals: debug
|
1...<<11121314151617181920>>...34
