| /Zephyr-latest/samples/subsys/testsuite/pytest/shell/ |
| D | README.rst | 43 DEBUG: #: uart:~$ help
44 DEBUG: #: Please press the <Tab> button to see all available commands.
45 …DEBUG: #: You can also use the <Tab> button to prompt or auto-complete all commands or its subcomm…
46 DEBUG: #: You can try to call commands with <-h> or <--help> parameter for more information.
47 DEBUG: #: Shell supports following meta-keys:
48 DEBUG: #: Ctrl + (a key from: abcdefklnpuw)
49 DEBUG: #: Alt + (a key from: bf)
50 DEBUG: #: Please refer to shell documentation for more details.
51 DEBUG: #: Available commands:
52 DEBUG: #: clear :Clear screen.
[all …]
|
| /Zephyr-latest/soc/microchip/mec/mec172x/ |
| D | Kconfig | 22 prompt "MEC172x debug interface general configuration"
26 Select Debug SoC interface support for MEC172X SoC family
29 bool "Disable debug support"
31 Debug port is disabled, JTAG/SWD cannot be enabled. JTAG_RST#
36 bool "Debug support via Serial wire debug"
41 bool "Debug support via Serial wire debug with tracing enabled"
48 prompt "MEC172X debug interface trace configuration"
52 Select tracing mode for debug interface
55 bool "Debug support via Serial wire debug"
61 bool "debug support via Serial Wire Debug and Viewer"
|
| /Zephyr-latest/boards/nxp/common/ |
| D | opensda-debug.rst | 5 A debug probe is used for both flashing and debugging the board. This board has
6 an :ref:`opensda-onboard-debug-probe`. The default firmware present on this
7 probe is the :ref:`opensda-daplink-onboard-debug-probe`.
10 to setup your debug probe:
12 * :ref:`jlink-debug-host-tools`: `Using J-Link on NXP OpenSDA Boards`_
13 * :ref:`linkserver-debug-host-tools`: `Using DAPLink on NXP OpenSDA Boards`_
14 * :ref:`pyocd-debug-host-tools`: `Using DAPLink on NXP OpenSDA Boards`_
19 1. If the debug firmware has been modified, follow the instructions provided at
20 :ref:`opensda-daplink-onboard-debug-probe` to reprogram the default debug
27 There are two options: the onboard debug circuit can be updated with Segger
[all …]
|
| D | rt1xxx-lpclink2-debug.rst | 5 A debug probe is used for both flashing and debugging the board. This board has
6 an :ref:`lpc-link2-onboard-debug-probe`. The default firmware present on this
7 probe is the :ref:`lpclink2-daplink-onboard-debug-probe`.
10 to setup your debug probe:
12 * :ref:`jlink-debug-host-tools`:
14 * :ref:`linkserver-debug-host-tools`:
16 * :ref:`pyocd-debug-host-tools`:
23 :ref:`lpclink2-cmsis-onboard-debug-probe` to reprogram the default debug
30 There are two options: the onboard debug circuit can be updated with Segger
31 J-Link firmware, or a :ref:`jlink-external-debug-probe` can be attached to the
[all …]
|
| /Zephyr-latest/doc/develop/flash_debug/ |
| D | probes.rst | 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.
[all …]
|
| D | host-tools.rst | 1 .. _flash-debug-host-tools:
3 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:
211 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.
[all …]
|
| /Zephyr-latest/soc/microchip/mec/mec15xx/ |
| D | Kconfig | 46 prompt "MEC1501 debug interface general configuration"
50 Select Debug SoC interface support for MEC15xx SoC family
53 bool "Disable debug support"
55 Debug port is disabled, JTAG/SWD cannot be enabled. JTAG_RST#
60 bool "Debug support via Serial wire debug"
65 bool "Debug support via Serial wire debug with tracing enabled"
73 prompt "MEC1501 debug interface trace configuration"
77 Select tracing mode for debug interface
80 bool "Debug support via Serial wire debug"
86 bool "debug support via Serial Wire Debug and Viewer"
|
| /Zephyr-latest/scripts/west_commands/ |
| D | debug.py | 7 '''west "debug", "debugserver", and "attach" commands.'''
16 class Debug(WestCommand): class
19 super(Debug, self).__init__(
20 'debug',
22 'flash and interactively debug a Zephyr application',
28 self.runner_key = 'debug-runner' # in runners.yaml
43 'connect to board and launch a debug server',
45 Connect to the board and launch a debug server which accepts
48 The debug server binds to a known port, and allows client software
49 started elsewhere to connect to it and debug the running
[all …]
|
| /Zephyr-latest/samples/subsys/debug/debugmon/ |
| D | README.rst | 2 :name: Debug Monitor
4 Configure the Debug Monitor feature on a Cortex-M processor.
9 The Debug Monitor sample shows a basic configuration of debug monitor feature.
14 #. Configure registers to enable degugging in debug monitor mode
24 #. Support Debug Monitor feature (available on Cortex-M processors with the exception of Cortex-M0)
32 Build and flash Debug Monitor as follows, changing ``reel_board`` for your board:
35 :zephyr-app: samples/subsys/debug/debugmon
40 After flashing the board enters a breakpoint and executes debug monitor exception code.
41 The LED starts to blink, indicating that even though the processor spins in debug monitor
|
| D | sample.yaml | 2 name: debug monitor sample
4 sample.debug.debugmon:
7 tags: debug
|
| /Zephyr-latest/doc/services/debugging/ |
| D | debugmon.rst | 3 Cortex-M Debug Monitor
9 This strategy makes it possible to debug time-sensitive software, that would
13 Zephyr provides support for enabling and configuring the Debug Monitor exception.
23 requires an implementation of debug monitor interrupt that will be executed
26 With a SEGGER debug probe, it's possible to use a ready, SEGGER-provided implementation
29 * :kconfig:option:`CONFIG_SEGGER_DEBUGMON`: enables SEGGER debug monitor interrupt. Can be
30 used with SEGGER JLinkGDBServer and a SEGGER debug probe.
46 required to debug in the monitor mode using regular GDB commands.
47 Steps to configure SEGGER debug monitor:
60 After these steps use regular gdb commands to debug your program.
[all …]
|
| /Zephyr-latest/drivers/dp/ |
| D | Kconfig | 6 bool "Debug Port interface driver [EXPERIMENTAL]"
9 Enable Debug Port interface driver
18 int "Debug Port driver initialization priority"
24 bool "Serial Wire Debug Port bit-bang driver"
29 Serial Wire Debug Port bit-bang driver.
|
| /Zephyr-latest/soc/microchip/mec/ |
| D | Kconfig | 207 bool "Debug console output"
210 Enable print output from SPI generator script for debug
214 # Common debug configuration
216 prompt "MEC debug interface general configuration"
220 Select Debug SoC interface support for MEC SoC family
223 bool "Disable debug support"
225 Debug port is disabled, JTAG/SWD cannot be enabled. JTAG_RST#
230 bool "Debug support via Serial wire debug"
235 bool "Debug support via Serial wire debug with tracing enabled"
241 prompt "MEC debug interface trace configuration"
[all …]
|
| /Zephyr-latest/boards/arduino/uno_r4/doc/ |
| D | index.rst | 18 - Built-in CMSIS-DAP debug adapter (Arduino UNO R4 WiFi only)
28 Debug adapter
31 A debug adapter is required to flash and debug programs.
32 Arduino UNO R4 WiFi has a built-in debug adapter that
36 debug adapter separately. A 5V-compatible CMSIS-DAP adapter
62 Debugging can be done with ``west debug`` command.
64 Also, see the instructions specific to the debug server that you use.
70 :goals: debug
76 :goals: debug
82 Various debug adapters, including cmsis-dap probes, can debug the Arduino UNO R4 with pyOCD.
|
| /Zephyr-latest/tests/bsim/bluetooth/host/gatt/notify_multiple/test_scripts/ |
| D | _notify-debug.sh | 7 # `_notify-debug.sh client debug`
8 # `_notify-debug.sh server`
9 # `_notify-debug.sh`
12 # `debug` when running the script.
21 if [[ $2 == "debug" ]]; then
|
| /Zephyr-latest/samples/subsys/logging/syst/ |
| D | README.rst | 16 :file:`<workspace>/modules/debug/mipi-sys-t/printer/`.
23 cd <workspace>/modules/debug/mipi-sys-t/printer/
30 :file:`<workspace>/modules/debug/mipi-sys-t/printer/build`.
93 [ 0.020000] <dbg> syst: Debug message example.
94 [ 0.020000] <dbg> syst: Debug message example, 1
95 [ 0.020000] <dbg> syst: Debug message example, 1, 2
96 [ 0.020000] <dbg> syst: Debug message example, 1, 2, 3
97 [ 0.020000] <dbg> syst: Debug message example, 1, 2, 3, 0x4
103 [ 0.030000] <dbg> syst: Debug message example, %f
145 <workspace>/modules/debug/mipi-sys-t/printer/build/systprint -p /tmp/syst
[all …]
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig.debug | 1 # Debug Options
17 module-help = Enables debug of network packet and buffer allocations and frees.
21 bool "Debug network packet and buffer individual allocation"
51 module-help = Enables core network stack code to output debug messages.
57 module-help = Enables network interface code to output debug messages.
63 module-help = Enables network traffic class code to output debug messages.
69 module-help = Enables utility functions to output debug messages.
81 module-help = Enables UDP/TCP connection debug messages.
87 module-help = Enables routing engine debug messages.
|
| /Zephyr-latest/scripts/build/ |
| D | gen_isr_tables.py | 20 def __init__(self, debug = False): argument
21 self.__debug = debug
23 def debug(self, text): member in gen_isr_log
24 """Print debug message if debugging is enabled.
63 This is done to allow debug function work as soon as possible.
106 self.__log.debug("Level Bits Bitmask")
107 self.__log.debug("----------------------------")
110 self.__log.debug(f"{i + 1:>5} {self.__int_bits[i]:>7} {bitmask_str:>14}")
119 self.__log.debug('2nd level offsets: {}'.format(self.__irq2_offsets))
128 self.__log.debug('3rd level offsets: {}'.format(self.__irq3_offsets))
[all …]
|
| /Zephyr-latest/modules/mbedtls/ |
| D | Kconfig | 82 module-str = Log level mbedTLS library debug hook
86 bool "mbed TLS debug activation"
90 activate debug logging.
95 function in your application. Alternatively implement your own debug
109 Default mbed TLS debug logging level for Zephyr integration code
110 (from ext/lib/crypto/mbedtls/include/mbedtls/debug.h):
111 0 No debug
118 mbedTLS initialization, with the configured debug log level.
130 when debug messages are enabled.
138 Filename passed as argument to debug hook will be stripped from
[all …]
|
| /Zephyr-latest/boards/renesas/ek_ra2l1/doc/ |
| D | index.rst | 42 - Debug LED (yellow) indicating the debug connection
57 You can build and flash an application with onboard J-Link debug adapter.
72 Debugging also can be done with onboard J-Link debug adapter.
74 Also, see the instructions specific to the debug server that you use.
80 :goals: debug
82 Or you can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
84 Once downloaded and installed, open Segger Ozone and configure the debug project
|
| /Zephyr-latest/boards/raspberrypi/rpi_pico/doc/ |
| D | index.rst | 14 It is also possible to flash and debug the boards with their SWD interface,
157 Debug Probe and Host Tools
161 The `Raspberry Pi Debug Probe`_ is an easy-to-obtain CMSIS-DAP adapter
167 - :ref:`openocd-debug-host-tools`
168 - :ref:`pyocd-debug-host-tools`
173 - `Black Magic Debug Probe <Black Magic Debug>`_
201 To use a debugging adapter such as the Raspberry Pi Debug Probe,
205 and debug the onboard SoC. This interface can be used with OpenOCD.
223 **RPI_PICO_DEBUG_ADAPTER** specifies what debug adapter is used for debugging.
228 Any other SWD debug adapter maybe also work with this configuration.
[all …]
|
| /Zephyr-latest/tests/subsys/debug/cpu_load/ |
| D | testcase.yaml | 6 debug.cpu_load:
9 debug.cpu_load.counter:
17 debug.cpu_load.periodic_report:
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | log_helper.py | 26 logger.setLevel(logging.DEBUG)
30 logger.debug(msg, str(args))
32 logger.debug(msg, shlex.join(args))
36 logger.setLevel(logging.DEBUG)
38 # create file handler which logs even debug messages
44 file_handler.setLevel(logging.DEBUG)
|
| /Zephyr-latest/tests/misc/llext-edk/pytest/ |
| D | test_edk.py | 47 logger.debug(f"Copying llext-edk.tar.xz to {tempdir}")
52 logger.debug(f"Extracting llext-edk.tar.xz to {tempdir}")
59 logger.debug(f"Copying extension to {tempdir_extension}")
65 logger.debug(f"Copying file2hex.py to {tempdir_extension}")
77 logger.debug(f"Building extension in {tempdir_extension} - cmake")
82 logger.debug(f"Building extension in {tempdir_extension} - make")
93 logger.debug(f"Running application with extension in {tempdir_extension} - west build")
104 logger.debug(f"west command: {command}")
109 logger.debug(f"Running application with extension in {tempdir_extension}")
|
| /Zephyr-latest/boards/renesas/ek_ra6e2/doc/ |
| D | index.rst | 29 - USB (Debug, Full Speed)
32 - Three Debug modes
34 - Debug on-board (SWD)
35 - Debug in (SWD)
36 - Debug out (JTAG, SWD)
42 - Debug LED (yellow) indicating the debug connection
108 You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
110 Once downloaded and installed, open Segger Ozone and configure the debug project
119 **Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
|
