Searched refs:debug (Results 101 – 125 of 846) sorted by relevance
12345678910>>...34
| /Zephyr-latest/boards/nxp/lpcxpresso55s36/doc/ |
| D | index.rst | 18 - LPC-Link2 debug high speed USB probe with VCOM port
162 A debug probe is used for both flashing and debugging the board. This board is
163 configured by default to use the integrated :ref:`mcu-link-onboard-debug-probe`
165 :ref:`linkserver-debug-host-tools` and make sure they are in your search path.
166 Then, use the ``linkserver`` runner option to flash and debug the board. Refer
171 firmware update, as described in :ref:`mcu-link-jlink-onboard-debug-probe`.
172 The :ref:`jlink-debug-host-tools` should be available in this case.
212 :goals: debug
|
| /Zephyr-latest/boards/st/nucleo_wba55cg/doc/ |
| D | nucleo_wba55cg.rst | 35 mass storage, Virtual COM port, and debug port
119 - Flexible life cycle scheme with RDP and password protected debug
136 - Serial wire debug (SWD), JTAG
231 Nucleo WBA55CG board includes an ST-LINK/V3 embedded debug tool interface.
232 It could be used for flash and debug using either OpenOCD or STM32Cube ecosystem tools.
265 You can debug an application in the usual way using OpenOCD. Here is an example for the
272 :goals: debug
277 You can debug an application using a STM32WBA compatible version of STM32CubeIDE.
287 - Run debug
|
| /Zephyr-latest/scripts/pylib/pytest-twister-harness/src/twister_harness/helpers/ |
| D | domains_helper.py | 26 logger.debug("Loaded sysbuild domain data from %s" % domains_file)
|
| /Zephyr-latest/doc/develop/ |
| D | index.rst | 13 debug/index.rst
|
| /Zephyr-latest/scripts/west_commands/runners/ |
| D | linkserver.py | 141 self.logger.debug(f'LinkServer cmd: + {linkserver_cmd}')
170 self.logger.debug("flash erase command = " + str(linkserver_cmd))
190 self.logger.debug(f'LinkServer cmd: + {linkserver_cmd}')
216 self.logger.debug("flash command = " + str(linkserver_cmd))
|
| /Zephyr-latest/boards/renesas/ek_ra2a1/doc/ |
| D | index.rst | 102 You can build and flash an application with onboard J-Link debug adapter.
117 Debugging also can be done with onboard J-Link debug adapter.
119 Also, see the instructions specific to the debug server that you use.
125 :goals: debug
|
| /Zephyr-latest/boards/olimex/stm32_h405/doc/ |
| D | index.rst | 65 JTAG debug
152 The OLIMEX-STM32-H405 board does not include an embedded debug tool
188 You can debug an application in the usual way. Here is an example for the
195 :goals: debug
|
| /Zephyr-latest/scripts/west_commands/completion/ |
| D | west-completion.fish | 177 "debug" "flash and interactively debug a Zephyr application" \
178 "debugserver" "connect to board and launch a debug server" \
179 "attach" "interactively debug a board" \
463 # debug
464 …subcommand; and __zephyr_west_check_if_in_workspace" -ra debug -d "flash and interactively debug a…
467 …_zephyr_west_check_if_in_workspace" -ra debugserver -d "connect to board and launch a debug server"
470 …se_subcommand; and __zephyr_west_check_if_in_workspace" -ra attach -d "interactively debug a board"
472 ## flash, debug, debugserver, attach
473 complete -c west -n "__zephyr_west_seen_subcommand_from flash debug debugserver attach" -o d -l bui…
474 complete -c west -n "__zephyr_west_seen_subcommand_from flash debug debugserver attach" -o r -l run…
[all …]
|
| /Zephyr-latest/subsys/net/lib/socks/ |
| D | Kconfig | 14 module-help = Enable debug messages for SOCKS5 protocol
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | coverage.py | 45 logger.debug(f"Select {tool} as the coverage tool...")
50 logger.debug(f"Working on {input_file}")
112 logger.debug("Generating gcda files")
144 logger.debug(f"Gcov data captured: {filename}")
182 logger.debug(f"All coverage data processed: {coverage_completed}")
240 logger.debug(f"Running {cmd_str}...")
367 logger.debug(f"Running {cmd_str}...")
|
| /Zephyr-latest/boards/nxp/lpcxpresso55s16/doc/ |
| D | index.rst | 18 - LPC-Link2 debug high speed USB probe with VCOM port
158 A debug probe is used for both flashing and debugging the board. This
160 Debug Probe, however the :ref:`pyocd-debug-host-tools` does not yet
162 J-Link debug probe instead.
164 First install the :ref:`jlink-debug-host-tools` and make sure they are
168 :ref:`lpclink2-jlink-onboard-debug-probe` to program the J-Link
210 :goals: debug
|
| /Zephyr-latest/boards/nxp/frdm_mcxa156/doc/ |
| D | index.rst | 117 A debug probe is used for both flashing and debugging the board. This board is
125 :ref:`mcu-link-cmsis-onboard-debug-probe` to reprogram the default MCU-Link
126 firmware. This only needs to be done if the default onboard debug circuit
133 There are two options. The onboard debug circuit can be updated with Segger
135 :ref:`mcu-link-jlink-onboard-debug-probe`.
138 The second option is to attach a :ref:`jlink-external-debug-probe` to the
184 :goals: debug
|
| /Zephyr-latest/boards/nxp/frdm_mcxn236/doc/ |
| D | index.rst | 129 A debug probe is used for both flashing and debugging the board. This board is
137 :ref:`mcu-link-cmsis-onboard-debug-probe` to reprogram the default MCU-Link
138 firmware. This only needs to be done if the default onboard debug circuit
145 There are two options. The onboard debug circuit can be updated with Segger
147 :ref:`mcu-link-jlink-onboard-debug-probe`.
150 The second option is to attach a :ref:`jlink-external-debug-probe` to the
196 :goals: debug
|
| /Zephyr-latest/samples/drivers/ipm/ipm_mcux/ |
| D | README.rst | 30 :goals: debug
40 :goals: debug
|
| /Zephyr-latest/boards/adi/max32655evkit/doc/ |
| D | index.rst | 167 The MAX32655 MCU can be flashed by connecting an external debug probe to the
168 SWD port. SWD debug can be accessed through the Cortex 10-pin connector, JH3.
171 Once the debug probe is connected to your host computer, then you can simply run the
176 This board uses OpenOCD as the default debug interface. You can also use
179 be connected to the standard 2*5 pin debug connector (JW3) using an
185 Please refer to the `Flashing`_ section and run the ``west debug`` command
|
| /Zephyr-latest/boards/nxp/mimxrt1010_evk/doc/ |
| D | index.rst | 155 This board supports 3 debug host tools. Please install your preferred host
159 * :ref:`linkserver-debug-host-tools` (Default, Supported by NXP)
160 * :ref:`jlink-debug-host-tools` (Supported by NXP)
161 * :ref:`pyocd-debug-host-tools` (Not supported by NXP)
173 .. include:: ../../common/rt1xxx-lpclink2-debug.rst
179 Regardless of your choice in debug probe, we will use the OpenSDA
|
| /Zephyr-latest/boards/nxp/twr_kv58f220m/doc/ |
| D | index.rst | 7 MCU-based platforms. The onboard OpenSDAv2 serial and debug adapter,
104 This board integrates an OpenSDA debug probe. However, it can currently only be
111 An external J-Link debug probe connected to the JTAG header J13 is used to debug
114 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search
165 :goals: debug
|
| /Zephyr-latest/scripts/ |
| D | requirements-run-test.txt | 5 # used to flash & debug various boards
|
| /Zephyr-latest/boards/nxp/mimxrt1050_evk/doc/ |
| D | index.rst | 316 Newer revisions of this board use :ref:`lpc-link2-onboard-debug-probe`,
317 while older revisions use the :ref:`opensda-onboard-debug-probe`.
321 This board supports 3 debug host tools. Please install your preferred host
326 * :ref:`linkserver-debug-host-tools` (Default, NXP Supported)
327 * :ref:`jlink-debug-host-tools` (NXP Supported)
328 * :ref:`pyocd-debug-host-tools` (Not supported by NXP)
340 .. include:: ../../common/opensda-debug.rst
350 .. include:: ../../common/rt1xxx-lpclink2-debug.rst
356 Regardless of your choice in debug probe, we will use the OpenSDA
397 :goals: debug
[all …]
|
| /Zephyr-latest/scripts/coredump/gdbstubs/ |
| D | gdbstub.py | 63 logger.debug(f"Received GDB packet: {data}")
67 logger.debug("ACK")
73 logger.debug(f"NACK (checksum {in_chksum} != {checksum}")
92 logger.debug(f"Sending GDB packet: {pkt}")
320 logger.debug(f"Got packet type: {pkt_type}")
|
| /Zephyr-latest/boards/tdk/robokit1/doc/ |
| D | index.rst | 19 - Micro-AB USB debug (Microchip EDBG) interface supporting CMSIS-DAP, Virtual COM Port and Data
126 Both west flash and west debug commands should correctly work with both USB0 and USB1
148 USB debug port (USB1), USB2 for a serial console, and remaining micro USB for
161 You can debug an application in the usual way. Here is an example for the
168 :goals: debug
|
| /Zephyr-latest/boards/makerbase/mks_canable_v20/doc/ |
| D | index.rst | 17 - Development support: serial wire debug (SWD), JTAG, Embedded Trace Macrocell.
87 MKS CANable V2.0 board includes an SWDIO debug connector header J4.
118 The argument ``-S rtt-console`` is needed for debug purposes with SEGGER RTT protocol.
140 You can debug an application in the usual way. Here is an example for the
147 :goals: debug
|
| /Zephyr-latest/boards/nxp/mimxrt1160_evk/doc/ |
| D | index.rst | 262 A debug probe is used for both flashing and debugging the board. This board is
263 configured by default to use the :ref:`opensda-daplink-onboard-debug-probe`,
264 however the :ref:`pyocd-debug-host-tools` do not yet support programming the
266 following debug probes instead.
271 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search
274 There are two options: the onboard debug circuit can be updated with Segger
275 J-Link firmware, or :ref:`jlink-external-debug-probe` can be attached to the
281 Install the :ref:`linkserver-debug-host-tools` and make sure they are in your
292 Regardless of your choice in debug probe, we will use the OpenSDA
336 :goals: debug
|
| /Zephyr-latest/boards/nxp/mimxrt1040_evk/doc/ |
| D | index.rst | 208 This board supports 3 debug host tools. Please install your preferred host
212 * :ref:`jlink-debug-host-tools` (Default, Supported by NXP)
213 * :ref:`linkserver-debug-host-tools` (Supported by NXP)
214 * :ref:`pyocd-debug-host-tools` (Not supported by NXP)
226 .. include:: ../../common/rt1xxx-lpclink2-debug.rst
232 Regardless of your choice in debug probe, we will use the OpenSDA
273 :goals: debug
296 If the debug probe fails to connect with the following error, it's possible
317 #. Run ``west debug`` or ``west flash`` again with a known working Zephyr
339 the M.2 WiFi module is interfering with the debug signals
|
| /Zephyr-latest/boards/seagate/faze/doc/ |
| D | index.rst | 103 The NXP LPC11U67 MCU can be flashed by connecting an external debug probe to
106 You may need to replace it with the interface of your debug probe.
108 Once the debug probe is connected to both the FaZe board and your host computer
115 Please refer to the `Flashing`_ section and run the ``west debug`` command
|
12345678910>>...34
