Home
last modified time | relevance | path

Searched refs:probe (Results 76 – 100 of 173) sorted by relevance

1234567

/Zephyr-latest/boards/pimoroni/pico_plus2/doc/
Dindex.rst59 https://www.raspberrypi.com/documentation/microcontrollers/debug-probe.html
/Zephyr-latest/boards/ti/lp_em_cc2340r5/doc/
Dindex.rst84 The LP_EM_CC2340R5 requires an external debug probe such as the LP-XDS110 or
/Zephyr-latest/drivers/dai/nxp/micfil/
Dmicfil.c163 .probe = dai_nxp_micfil_probe,
/Zephyr-latest/boards/adafruit/feather_m4_express/doc/
Dindex.rst130 debugged using a SWD probe such as the Segger J-Link.
132 #. Connect the board to the probe by connecting the :code:`SWCLK`,
/Zephyr-latest/boards/arduino/giga_r1/doc/
Dindex.rst75 probe, such as a J-Link or Black Magic Probe, connected to the on board MIPI-10
125 Debugging is supported by using ``west debug`` with an external probe such as a
/Zephyr-latest/boards/nxp/mimxrt700_evk/doc/
Dindex.rst182 A debug probe is used for both flashing and debugging the board. This board is
200 3. Connect the J-Link probe to J18 20-pin header.
202 See :ref:`jlink-external-debug-probe` for more information.
/Zephyr-latest/boards/nxp/mimxrt1160_evk/doc/
Dindex.rst262 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`,
294 J-Link firmware, or :ref:`jlink-external-debug-probe` can be attached to the
311 Regardless of your choice in debug probe, we will use the OpenSDA
/Zephyr-latest/boards/nxp/frdm_k64f/doc/
Dindex.rst232 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`.
273 instructions in :ref:`opensda-jlink-onboard-debug-probe` to program to the
289 Regardless of your choice in debug probe, we will use the OpenSDA
/Zephyr-latest/boards/rakwireless/rak3172/doc/
Dindex.rst46 The RAK3172 board can be debugged and flashed with an external debug probe connected
/Zephyr-latest/boards/adi/max32655evkit/doc/
Dindex.rst167 The MAX32655 MCU can be flashed by connecting an external debug probe to the
171 Once the debug probe is connected to your host computer, then you can simply run the
/Zephyr-latest/drivers/dai/intel/alh/
Dalh.c198 .probe = dai_alh_probe,
/Zephyr-latest/boards/ct/ctcc/doc/
Dindex.rst92 1. Using an external :ref:`debug probe <debug-probes>`
101 Connectivity Card can be programmed using an external debug probe (Segger J-Link) by connecting
/Zephyr-latest/boards/nxp/s32z2xxdc2/doc/
Dindex.rst198 - :ref:`NXP S32 Debug Probe <nxp-s32-debug-probe>` (default)
207 Connect the external debugger probe to the board's JTAG connector (``J134``)
208 and to the host computer via USB or Ethernet, as supported by the probe.
/Zephyr-latest/subsys/net/lib/dhcpv4/
DKconfig145 Decline message or due to ICMP probe detecting conflict), the address
156 DHCPv4 server will probe the offered IP address (send ICMP echo
Ddhcpv4_server.c955 bool probe = false; in dhcpv4_handle_discover() local
1020 probe = true; in dhcpv4_handle_discover()
1043 probe = true; in dhcpv4_handle_discover()
1065 probe = true; in dhcpv4_handle_discover()
1075 if (IS_ENABLED(DHCPV4_SERVER_ICMP_PROBE) && probe) { in dhcpv4_handle_discover()
/Zephyr-latest/boards/nxp/mimxrt1170_evk/doc/
Dindex.rst357 A debug probe is used for both flashing and debugging the board. The on-board
361 - MIMXRT1170-EVKB: :ref:`mcu-link-cmsis-onboard-debug-probe`
362 - MIMXRT1170-EVK: :ref:`opensda-daplink-onboard-debug-probe`
371 J-Link firmware, or :ref:`jlink-external-debug-probe` can be attached to the
/Zephyr-latest/boards/olimex/stm32_h405/doc/
Dindex.rst128 interface. You will need to use ST tools or an external JTAG probe.
/Zephyr-latest/boards/adi/max32666fthr/doc/
Dindex.rst216 The MAX32666 MCU can be flashed by connecting an external debug probe to the SWD port.
220 Once the debug probe is connected to your host computer, then you can simply run the
/Zephyr-latest/boards/adi/apard32690/doc/
Dindex.rst188 The MAX32690 MCU can be flashed by connecting an external debug probe to the
192 Once the debug probe is connected to your host computer, then you can simply run the
/Zephyr-latest/boards/adi/max78000evkit/doc/
Dindex.rst281 The MAX78000 MCU can be flashed by connecting an external debug probe to the
285 Once the debug probe is connected to your host computer, then you can simply run the
/Zephyr-latest/boards/digilent/arty_a7/doc/
Dindex.rst101 (SWD) capable debug probe connected to the ARM Cortex-M1 CPU.
106 The external SWD debug probe can be connected to connector ``J4`` (``nSRST`` on
/Zephyr-latest/boards/adi/max32690evkit/doc/
Dindex.rst282 The MAX32690 MCU can be flashed by connecting an external debug probe to the
286 Once the debug probe is connected to your host computer, then you can simply run the
/Zephyr-latest/boards/adi/max32666evkit/doc/
Dindex.rst294 The MAX32666 MCU can be flashed by connecting an external debug probe to the
298 Once the debug probe is connected to your host computer, then you can simply run the
/Zephyr-latest/boards/nxp/mimxrt1064_evk/doc/
Dindex.rst345 Regardless of your choice in debug probe, we will use the OpenSDA
408 If the debug probe fails to connect with the following error, it's possible
437 runners.jlink, confirm the J-Link debug probe is configured, powered, and
/Zephyr-latest/boards/raspberrypi/rpi_5/doc/
Dindex.rst140 https://www.raspberrypi.com/products/debug-probe/

1234567