Home
last modified time | relevance | path

Searched refs:probe (Results 51 – 75 of 173) sorted by relevance

1234567

/Zephyr-latest/boards/olimex/stm32_e407/doc/
Dindex.rst296 interface. You will need to use ST tools or an external JTAG probe.
299 If you have an external JTAG probe compliant with the default Zephyr OpenOCD
333 Provided that you have a JTAG probe, you can debug an application in the usual
/Zephyr-latest/boards/nxp/frdm_mcxn236/doc/
Dindex.rst131 A debug probe is used for both flashing and debugging the board. This board is
139 :ref:`mcu-link-cmsis-onboard-debug-probe` to reprogram the default MCU-Link
149 :ref:`mcu-link-jlink-onboard-debug-probe`.
152 The second option is to attach a :ref:`jlink-external-debug-probe` to the
/Zephyr-latest/boards/seagate/faze/support/
Dopenocd.cfg5 # An external debug probe must be connected to the SWD port (4-pins J2 header).
/Zephyr-latest/boards/seeed/lora_e5_dev_board/doc/
Dlora_e5_dev_board.rst176 The LoRa-E5 Dev Board does not include a on-board debug probe.
177 But the module can be debugged by connecting an external debug probe to the
179 Depending on the external probe used, ``openocd``, the ``stm32cubeprogrammer``,
194 Connect the LoRa-E5 to your host computer using the external debug probe.
/Zephyr-latest/boards/nxp/lpcxpresso11u68/support/
Dopenocd.cfg9 # The on-board LPC-Link2 debug probe (based on a NXP LPC43xx MCU) provides
/Zephyr-latest/boards/nxp/frdm_ke17z/doc/
Dindex.rst94 A debug probe is used for both flashing and debugging the board. This board is
116 External JLink: :ref:`jlink-external-debug-probe`
134 Regardless of your choice in debug probe, we will use the OpenSDA
/Zephyr-latest/boards/adi/max32650evkit/doc/
Dindex.rst93 The MAX32650 MCU can be flashed by connecting an external debug probe to the
97 Once the debug probe is connected to your host computer, then you can simply run the
/Zephyr-latest/boards/adi/max32650fthr/doc/
Dindex.rst92 The MAX32650 MCU can be flashed by connecting an external debug probe to the
96 Once the debug probe is connected to your host computer, then you can simply run the
/Zephyr-latest/boards/renesas/rcar_h3ulcb/doc/
Drcar_h3ulcb_r7.rst183 The "Olimex ARM-USB-OCD-H" probe is the only officially supported probe. This probe is supported by…
185 The "Olimex ARM-USB-OCD-H" probe needs to be connected with a SICA20I2P adapter to CN3 on H3ULCB.
/Zephyr-latest/boards/nxp/frdm_mcxw71/doc/
Dindex.rst97 A debug probe is used for both flashing and debugging the board. This board is
105 :ref:`mcu-link-cmsis-onboard-debug-probe` to reprogram the default MCU-Link
115 :ref:`mcu-link-jlink-onboard-debug-probe`.
118 The second option is to attach a :ref:`jlink-external-debug-probe` to the
/Zephyr-latest/drivers/dai/intel/hda/
Dhda.c136 .probe = pm_device_runtime_get,
/Zephyr-latest/boards/nxp/usb_kw24d512/doc/
Dindex.rst138 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`
/Zephyr-latest/boards/adi/ad_swiot1l_sl/doc/
Dindex.rst97 The MAX32650 MCU can be flashed by connecting an external debug probe to the
101 Once the debug probe is connected to your host computer, then you can simply run the
/Zephyr-latest/boards/nxp/mimxrt1050_evk/doc/
Dindex.rst316 Newer revisions of this board use :ref:`lpc-link2-onboard-debug-probe`,
317 while older revisions use the :ref:`opensda-onboard-debug-probe`.
318 Schematic revisions A/A1 use the K20 OpenSDA probe, and B/B1 use the
319 LPC-Link2 LPC4322 probe.
356 Regardless of your choice in debug probe, we will use the OpenSDA
410 If the debug probe fails to connect with the following error, it's possible
/Zephyr-latest/boards/madmachine/mm_swiftio/doc/
Dindex.rst153 This board is configured by default to use the :ref:`opensda-daplink-onboard-debug-probe`,
160 Regardless of your choice in debug probe, we will use the OpenSDA
/Zephyr-latest/boards/olimex/stm32_h103/doc/
Dindex.rst160 will have to use an external probe connected to the available 20-pin JTAG
165 probe, for instance. For the latter, you should replace the file ``openocd.cfg``
/Zephyr-latest/boards/adafruit/grand_central_m4_express/doc/
Dindex.rst119 debugged using a SWD probe such as the Segger J-Link.
121 #. Connect the probe to the board using the 10-pin SWD interface.
/Zephyr-latest/boards/nxp/mimxrt1180_evk/doc/
Dindex.rst230 A debug probe is used for both flashing and debugging the board. This board is
231 configured by default to use the :ref:`mcu-link-cmsis-onboard-debug-probe`.
252 J-Link firmware, or :ref:`jlink-external-debug-probe` can be attached to the
278 Regardless of your choice in debug probe, we will use the MCU-Link
/Zephyr-latest/subsys/logging/backends/
DKconfig.swo33 debug probe. Such configuration will persist only until the device
/Zephyr-latest/boards/raspberrypi/rpi_pico2/doc/
Dindex.rst44 …ry Pi Debug Probe <https://www.raspberrypi.com/documentation/microcontrollers/debug-probe.html>`_ .
/Zephyr-latest/boards/arduino/nicla_vision/doc/
Dindex.rst79 probe, such as a J-Link or Black Magic Probe, connected to the on board MIPI-10
124 Debugging is supported by using ``west debug`` with an external probe such as a
/Zephyr-latest/boards/seeed/wio_terminal/doc/
Dindex.rst108 debugged using an SWD probe such as the Segger J-Link.
114 #. Connect the board to the probe by connecting the :code:`SWCLK`,
/Zephyr-latest/boards/adafruit/itsybitsy_m4_express/doc/
Dindex.rst129 debugged using a SWD probe such as the Segger J-Link.
131 #. Connect the board to the probe by connecting the :code:`SWCLK`,
/Zephyr-latest/subsys/net/l2/wifi/
DKconfig8 results (beacons or probe responses) are provided to the application.
24 results (beacons or probe responses) are provided to the application.
/Zephyr-latest/boards/nxp/frdm_mcxn947/doc/
Dindex.rst187 A debug probe is used for both flashing and debugging the board. This board is
195 :ref:`mcu-link-cmsis-onboard-debug-probe` to reprogram the default MCU-Link
205 :ref:`mcu-link-jlink-onboard-debug-probe`.
208 The second option is to attach a :ref:`jlink-external-debug-probe` to the

1234567