Searched refs:debug (Results 51 – 75 of 846) sorted by relevance
12345678910>>...34
| /Zephyr-latest/drivers/ieee802154/ |
| D | Kconfig.kw41z | 22 bool "Simplified debug tracing of events"
25 trace of events without going to debug logging to avoid timing impact
|
| /Zephyr-latest/boards/nxp/hexiwear/doc/ |
| D | index.rst | 170 A debug probe is used for both flashing and debugging the board. This board is
171 configured by default to use the :ref:`opensda-daplink-onboard-debug-probe`,
173 you reconfigure the board for the :ref:`opensda-jlink-onboard-debug-probe`.
179 Option 1: :ref:`opensda-jlink-onboard-debug-probe` (Recommended)
182 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search
185 Follow the instructions in :ref:`opensda-jlink-onboard-debug-probe` to program
190 Option 2: :ref:`opensda-daplink-onboard-debug-probe`
193 Install the :ref:`pyocd-debug-host-tools` and make sure they are in your search
196 Follow the instructions in :ref:`opensda-daplink-onboard-debug-probe` to
214 Regardless of your choice in debug probe, we will use the OpenSDA
[all …]
|
| /Zephyr-latest/boards/wiznet/w5500_evb_pico/doc/ |
| D | index.rst | 13 drag-and-drop manner. It is also possible to flash and debug the boards with
143 You can Flash the w5500_evb_pico with a SEGGER JLink debug probe as described in
171 interface that can be used to program and debug the on board RP2040. This
198 **RPI_PICO_DEBUG_ADAPTER** specifies what debug adapter is used for debugging.
203 described in `Getting Started with Raspberry Pi Pico`_. Any other SWD debug
207 ``west flash`` and ``west debug`` if it was previously set while running
212 **RPI_PICO_DEBUG_ADAPTER** needs to be assigned the file name of the debug
234 The SWD interface can also be used to debug the board. To achieve this, you can
240 Use a SEGGER JLink debug probe and follow the instruction in
255 :goals: debug
[all …]
|
| /Zephyr-latest/arch/x86/ |
| D | gen_mmu.py | 115 def debug(text): function
344 debug("%s starting at physical address 0x%x" %
407 debug("new %s at physical addr 0x%x"
435 debug("Reserving paging structures for 0x%x (0x%x)" %
472 debug("Mapping 0x%x (0x%x) to 0x%x: %s" %
536 debug("change flags for %s at 0x%x (0x%x): %s" %
573 debug("top-level %s at physical addr 0x%x" %
745 debug("building %s" % pclass.__name__)
777 debug("Address space: 0x%x - 0x%x size 0x%x" %
780 debug("Zephyr image: 0x%x - 0x%x size 0x%x" %
[all …]
|
| /Zephyr-latest/boards/nxp/usb_kw24d512/doc/ |
| D | index.rst | 23 - 10-pin (0.05”) JTAG debug port for target MCU
138 A debug probe is used for both flashing and debugging the board. This board is
139 configured by default to use the :ref:`jlink-external-debug-probe`.
141 :ref:`jlink-external-debug-probe`
144 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search
156 Once you have started a debug session, run telnet:
177 The Segger RTT console is only available during a debug session. Use ``attach``
201 :goals: debug
227 https://www.segger.com/products/debug-probes/j-link/technology/about-real-time-transfer/
|
| /Zephyr-latest/samples/subsys/ipc/rpmsg_service/ |
| D | README.rst | 24 :goals: debug
32 :goals: debug
40 :goals: debug
86 :goals: debug
91 :goals: debug
138 :goals: debug
|
| /Zephyr-latest/subsys/mgmt/ec_host_cmd/ |
| D | Kconfig.logging | 7 bool "Log full params and response buffers in debug log level"
10 Every command is logged with the debug logging level. Use this config
|
| /Zephyr-latest/soc/microchip/mec/ |
| D | Kconfig | 210 Enable print output from SPI generator script for debug
214 # Common debug configuration
216 prompt "MEC debug interface general configuration"
223 bool "Disable debug support"
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"
245 Select tracing mode for debug interface
248 bool "Debug support via Serial wire debug"
255 bool "debug support via Serial Wire Debug and Viewer"
|
| /Zephyr-latest/boards/wiznet/w5500_evb_pico/ |
| D | board.cmake | 3 # This configuration allows selecting what debug adapter debugging w5500_evb_pico
7 # And any other SWD debug adapter might also be usable with this configuration.
9 # Set RPI_PICO_DEBUG_ADAPTER to select debug adapter by command-line arguments.
|
| /Zephyr-latest/cmake/linker_script/common/ |
| D | debug-sections.cmake | 1 # Content of this file originates from include/zephyr/linker/debug-sections.ld
14 # DWARF debug sections.
18 zephyr_linker_section(NAME .debug ADDRESS 0)
|
| /Zephyr-latest/boards/raspberrypi/rpi_pico/ |
| D | board.cmake | 3 # This configuration allows selecting what debug adapter debugging rpi_pico
7 # And any other SWD debug adapter might also be usable with this configuration.
9 # Set RPI_PICO_DEBUG_ADAPTER to select debug adapter by command-line arguments.
|
| /Zephyr-latest/samples/subsys/debug/ |
| D | index.rst | 1 .. zephyr:code-sample-category:: debug
|
| /Zephyr-latest/boards/nxp/frdm_ke15z/doc/ |
| D | index.rst | 75 A debug probe is used for both flashing and debugging the board. This board is
85 Install the :ref:`linkserver-debug-host-tools` and make sure they are in your
89 Linkserver is the default for this board, ``west flash`` and ``west debug`` will
92 Option 2: :ref:`opensda-jlink-onboard-debug-probe`
95 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search
98 Follow the instructions in :ref:`opensda-jlink-onboard-debug-probe` to program
109 Regardless of your choice in debug probe, we will use the OpenSDA
148 :goals: debug
|
| /Zephyr-latest/boards/olimex/lora_stm32wl_devkit/doc/ |
| D | olimex_lora_stm32wl_devkit.rst | 86 The board contains an on-board debug probe which implements the CMSIS-DAP
89 It can also be debugged and flashed with an external debug probe connected
92 The built-in debug probe works with pyOCD, but requires installing an additional
129 You can debug an application in the usual way. Here is an example for the
136 :goals: debug
144 :goals: debug
|
| /Zephyr-latest/doc/develop/west/ |
| D | build-flash-debug.rst | 1 .. _west-build-flash-debug:
8 ``build``, ``flash``, ``debug``, ``debugserver`` and ``attach``.
11 commands, see :ref:`flash-and-debug-support` in the board porting guide.
416 tool, such as ``flash`` and ``debug``.
473 ``BOARD_FLASH_RUNNER`` CMake variable, and the debug runner with
554 Debugging: ``west debug``, ``west debugserver``
559 Run ``west debug -h`` or ``west debugserver -h`` for additional help.
565 open up a debug console (e.g. a GDB session)::
567 west debug
574 Without options, the behavior is the same as ``ninja debug`` and
[all …]
|
| /Zephyr-latest/boards/arduino/nano_33_ble/support/ |
| D | debug.cmm | 6 DO ~~~~/startup.cmm command=debug &args
|
| /Zephyr-latest/samples/drivers/mbox_data/ |
| D | README.rst | 27 :goals: debug
36 :goals: debug
45 :goals: debug
54 :goals: debug
|
| /Zephyr-latest/boards/nxp/frdm_k64f/doc/ |
| D | index.rst | 15 - OpenSDAv2, the NXP open source hardware embedded serial and debug adapter
30 - Programmable OpenSDAv2 debug circuit supporting the CMSIS-DAP Interface
34 - CMSIS-DAP debug interface over a driver-less USB HID connection providing
232 A debug probe is used for both flashing and debugging the board. This board is
233 configured by default to use the :ref:`opensda-daplink-onboard-debug-probe`.
243 Install the :ref:`linkserver-debug-host-tools` and make sure they are in your
247 Linkserver is the default for this board, ``west flash`` and ``west debug`` will
254 Alternatively, pyOCD can be used to flash and debug the board by using the
263 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search
273 instructions in :ref:`opensda-jlink-onboard-debug-probe` to program to the
[all …]
|
| /Zephyr-latest/boards/nxp/ucans32k1sic/support/ |
| D | debug.cmm | 11 DO ~~~~/startup.cmm command=debug &args
|
| /Zephyr-latest/boards/nxp/mr_canhubk3/support/ |
| D | debug.cmm | 11 DO ~~~~/startup.cmm command=debug &args
|
| /Zephyr-latest/boards/nxp/s32z2xxdc2/support/ |
| D | debug.cmm | 11 DO ~~~~/startup.cmm command=debug &args
|
| /Zephyr-latest/scripts/coredump/ |
| D | coredump_gdbserver.py | 66 if args.debug:
75 if args.debug:
84 if args.debug:
|
| /Zephyr-latest/scripts/west_commands/runners/ |
| D | nrfutil.py | 94 self.logger.debug(f'Found boards: {snrs}')
120 self.logger.debug(f'Executing batch in: {json_file}')
125 self.logger.debug(f'Executing op: {op}')
|
| /Zephyr-latest/boards/sparkfun/pro_micro_rp2040/ |
| D | board.cmake | 3 # This configuration allows selecting what debug adapter debugging to use
7 # And any other SWD debug adapter might also be usable with this configuration.
12 # Set RPI_PICO_DEBUG_ADAPTER to select debug adapter by command-line arguments.
|
| /Zephyr-latest/boards/nxp/mimxrt1180_evk/doc/ |
| D | index.rst | 174 A debug probe is used for both flashing and debugging the board. This board is
175 configured by default to use the :ref:`mcu-link-cmsis-onboard-debug-probe`,
176 however the :ref:`pyocd-debug-host-tools` do not yet support programming the
178 following debug probes instead.
192 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search
195 There are two options: the onboard debug circuit can be updated with Segger
196 J-Link firmware, or :ref:`jlink-external-debug-probe` can be attached to the
212 Regardless of your choice in debug probe, we will use the MCU-Link
256 :goals: debug
|
12345678910>>...34
