Searched refs:probe (Results 101 – 125 of 173) sorted by relevance
1234567
| /Zephyr-latest/boards/wiznet/w5500_evb_pico/doc/ |
| D | index.rst | 83 You can Flash the w5500_evb_pico with a SEGGER JLink debug probe as described in
180 Use a SEGGER JLink debug probe and follow the instruction in
|
| /Zephyr-latest/boards/st/nucleo_n657x0_q/doc/ |
| D | index.rst | 15 The NUCLEO-N657X0-Q board does not require any separate probe as it integrates the ST-LINK
112 This probe allows to flash and debug the board using various tools.
|
| /Zephyr-latest/boards/adi/max32680evkit/doc/ |
| D | index.rst | 325 The MAX32680 MCU can be flashed by connecting an external debug probe to the
329 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/doc/services/tracing/ |
| D | index.rst | 190 depend on any particular debug probe or other development tool.
232 Tracealyzer has built-in support for SEGGER RTT to receive trace data using a J-Link probe.
259 If you are tight on RAM, you may consider reducing this setting. If using a regular J-Link probe
270 fast debug probe that allows for SWO speeds of 10 MHz or higher. To use this stream port,
299 The host-side setup depends on what debug probe you are using. Learn more in the Tracealyzer
307 with tracing and try out streaming trace without needing a fast debug probe. The data is streamed
|
| /Zephyr-latest/boards/adi/max32660evsys/doc/ |
| D | index.rst | 100 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/scripts/west_commands/runners/ |
| D | nxp_s32dbg.py | 175 for i, probe in enumerate(probes_snr, 1):
|
| /Zephyr-latest/boards/olimex/stm32_p405/doc/ |
| D | index.rst | 188 interface. You will need to use ST tools or an external JTAG probe.
|
| /Zephyr-latest/boards/nxp/lpcxpresso11u68/doc/ |
| D | index.rst | 101 probe (based on a NXP LPC43xx MCU). This MCU provides either a CMSIS-DAP or
|
| /Zephyr-latest/boards/ti/msp_exp432p401r_launchxl/doc/ |
| D | index.rst | 16 * XDS110-ET, an open-source onboard debug probe featuring EnergyTrace+ technology and application
|
| /Zephyr-latest/boards/nxp/mimxrt1060_evk/doc/ |
| D | index.rst | 384 Regardless of your choice in debug probe, we will use the OpenSDA
481 If the debug probe fails to connect with the following error, it's possible
510 runners.jlink, confirm the J-Link debug probe is configured, powered, and
|
| /Zephyr-latest/boards/st/b_g474e_dpow1/doc/ |
| D | index.rst | 12 B-G474E-DPOW1 Discovery kit does not require any separate probe, as it integrates
|
| /Zephyr-latest/boards/st/nucleo_f334r8/doc/ |
| D | index.rst | 15 The STM32 Nucleo board does not require any separate probe as it integrates the ST-LINK/V2-1
|
| /Zephyr-latest/boards/st/stm32h750b_dk/doc/ |
| D | index.rst | 71 This probe allows flashing and debugging the board using various tools.
|
| /Zephyr-latest/boards/st/nucleo_g031k8/doc/ |
| D | index.rst | 14 The STM32 Nucleo-32 board does not require any separate probe as it integrates the
|
| /Zephyr-latest/boards/nxp/mimxrt1040_evk/doc/ |
| D | index.rst | 233 Regardless of your choice in debug probe, we will use the OpenSDA
297 If the debug probe fails to connect with the following error, it's possible
|
| /Zephyr-latest/boards/nxp/frdm_rw612/doc/ |
| D | index.rst | 88 A debug probe is used for both flashing and debugging the board. This board is
|
| /Zephyr-latest/boards/adi/max32670evkit/doc/ |
| D | index.rst | 187 Once the debug probe is connected to your host computer, then you can simply run the
|
| /Zephyr-latest/boards/nxp/rddrone_fmuk66/doc/ |
| D | index.rst | 114 A debug probe is used for both flashing and debugging the board. This board is
|
| /Zephyr-latest/soc/nordic/ |
| D | Kconfig | 190 Unit) for tracing using a hardware probe. If disabled, the trace
|
| /Zephyr-latest/boards/nxp/mimxrt1010_evk/doc/ |
| D | index.rst | 179 Regardless of your choice in debug probe, we will use the OpenSDA
|
| /Zephyr-latest/boards/st/stm32u5a9j_dk/doc/ |
| D | index.rst | 96 This probe allows to flash and debug the board using various tools.
|
| /Zephyr-latest/boards/st/nucleo_f756zg/doc/ |
| D | index.rst | 15 The STM32 Nucleo-144 board does not require any separate probe as it integrates
|
| /Zephyr-latest/boards/st/nucleo_h753zi/doc/ |
| D | index.rst | 15 The STM32 Nucleo-144 board does not require any separate probe as it integrates
|
| /Zephyr-latest/boards/st/nucleo_h7a3zi_q/doc/ |
| D | index.rst | 15 The STM32 Nucleo-144 board does not require any separate probe as it integrates
|
| /Zephyr-latest/boards/nordic/nrf52840dongle/doc/ |
| D | index.rst | 118 3. Using an external :ref:`debug probe <debug-probes>`
291 If you have one, you can also use an external :ref:`debug probe <debug-probes>`
|
1234567
