Home
last modified time | relevance | path

Searched refs:debug (Results 201 – 225 of 846) sorted by relevance

12345678910>>...34

/Zephyr-latest/drivers/usb_c/ppc/
DKconfig22 Add useful shell commands to manipulate and debug the PPCs
/Zephyr-latest/modules/trusted-firmware-a/
DKconfig20 When enabled, the build type of TF-A would be debug.
/Zephyr-latest/boards/raspberrypi/rpi_pico2/
Dboard.cmake12 # https://www.raspberrypi.com/documentation/microcontrollers/debug-probe.html#debugging-with-swd
/Zephyr-latest/subsys/net/lib/dhcpv6/
DKconfig29 module-help = Enables DHCPv6 client code to output debug messages.
/Zephyr-latest/scripts/west_commands/runners/
Dtrace32.py113 self.debug(**kwargs)
131 def debug(self, **kwargs) -> None: member in TRACE32BinaryRunner
/Zephyr-latest/boards/mikroe/stm32_m4_clicker/doc/
Dindex.rst71 Also, see the instructions specific to the debug server that you use.
77 :goals: debug
/Zephyr-latest/boards/qemu/x86/
Dboard.cmake68 -device isa-debug-exit,iobase=0xf4,iosize=0x04
77 # TODO: Support debug
/Zephyr-latest/boards/openisa/rv32m1_vega/support/
Dopenocd_rv32m1_vega_zero_riscy.cfg28 # Select the debug unit core we are using. This debug unit as an option.
/Zephyr-latest/boards/gd/gd32f350r_eval/doc/
Dindex.rst6 The GD32F350R-EVAL board is a hardware platform that enables design and debug
116 #. To debug an image:
121 :goals: debug
/Zephyr-latest/boards/gd/gd32l233r_eval/doc/
Dindex.rst6 The GD32L233R-EVAL board is a hardware platform that enables design and debug
117 #. To debug an image:
122 :goals: debug
/Zephyr-latest/samples/boards/arc_secure_services/
DREADME.rst101 $ west debug
113 # open debug server
121 # open debug server
/Zephyr-latest/boards/native/native_posix/doc/
Dindex.rst26 and can debug and instrument it like any other Linux program.
74 You can run, debug, build it with sanitizers or with coverage just like with
89 and is therefore normally best to test and debug your code, as some bugs are
/Zephyr-latest/boards/96boards/nitrogen/doc/
Dindex.rst41 - SWD debug connectors
230 To use ``pyOCD``, install the :ref:`pyocd-debug-host-tools` and make sure they
277 requires installing the :ref:`pyocd-debug-host-tools`.
304 You can debug an application in the usual way. Here is an example for the
311 :goals: debug
/Zephyr-latest/boards/adi/max32690evkit/doc/
Dindex.rst282 The MAX32690 MCU can be flashed by connecting an external debug probe to the
283 SWD port. SWD debug can be accessed through the Cortex 10-pin connector, J3.
286 Once the debug probe is connected to your host computer, then you can simply run the
291 This board uses OpenOCD as the default debug interface. You can also use
294 be connected to the standard 2*5 pin debug connector (JW3) using an
300 Please refer to the `Flashing`_ section and run the ``west debug`` command
/Zephyr-latest/boards/cypress/cy8ckit_062_wifi_bt/doc/
Dindex.rst10 platform that enables design and debug of the PSOC 62 MCU and the Murata
46 17. PSOC 6 debug and trace header (J12)
48 19. PSOC 6 program and debug header (J11)
129 3. Add the OpenOCD executable file's path to west flash/debug.
131 5. Debug using: west debug --openocd path/to/infineon/openocd/bin/openocd
139 communication over USB. There are also PSOC 6 program and debug headers J11
/Zephyr-latest/drivers/wifi/nxp/
DKconfig.nxp814 BLE coex mode and antenna isolation debug.
1059 If you enable this the debug options will be
1063 bool "OS debug"
1069 bool "NET debug"
1080 menu "Wifi extra debug options"
1083 bool "WiFi driver extra debug control"
1092 bool "WiFi driver uAP debug"
1121 bool "Power save debug"
1129 bool "Scan debug"
1138 bool "Packet debug"
[all …]
/Zephyr-latest/boards/bbc/microbit/
Dboard.cmake7 # https://www.segger.com/products/debug-probes/j-link/models/other-j-links/bbc-microbit-j-link-upgr…
/Zephyr-latest/boards/nxp/mr_canhubk3/doc/
Dindex.rst136 DCD-LZ debug connector ``P6``.
248 The FS26 can also be started in debug mode (watchdog disabled) following
283 in :ref:`lauterbach-trace32-debug-host-tools`, :ref:`jlink-debug-host-tools` and
284 :ref:`pyocd-debug-host-tools`,
285 to setup the flash and debug host tools for these runners, respectively. The
325 Run the ``west debug`` command to start a GDB session using SEGGER J-Link.
326 Alternatively, run ``west debug -r trace32`` or ``west debug -r pyocd``
/Zephyr-latest/cmake/usage/
Dusage.cmake25 message(" debug - Run \"west debug\"")
/Zephyr-latest/boards/arduino/nano_33_ble/support/
Dstartup.cmm11 &command=STRing.SCANAndExtract("&args","command=","debug")
116 ; Setup minimal debug environment
/Zephyr-latest/boards/vcc-gnd/yd_stm32h750vb/doc/
Dindex.rst66 bootloader, and another by using the SWD debug port (which requires additional
100 You can debug an application in the usual way. Here is an example for the
106 :goals: debug
/Zephyr-latest/boards/atmel/sam0/samd20_xpro/doc/
Dindex.rst9 which provides a full debug interface without the need for additional
97 provides a debug interface to the SAMD20 chip and is supported by
111 #. Connect the SAM D20 Xplained Pro to your host computer using the USB debug
/Zephyr-latest/boards/renesas/ek_ra4e2/doc/
Dindex.rst46 - Debug LED (yellow) indicating the debug connection
141 You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
143 Once downloaded and installed, open Segger Ozone and configure the debug project
152 **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_ra6e2/doc/
Dindex.rst45 - Debug LED (yellow) indicating the debug connection
141 You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
143 Once downloaded and installed, open Segger Ozone and configure the debug project
152 **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_ra6m3/doc/
Dindex.rst43 - 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

12345678910>>...34