Searched refs:debug (Results 176 – 200 of 846) sorted by relevance
12345678910>>...34
| /Zephyr-latest/boards/fanke/fk7b0m1_vbt6/support/ |
| D | openocd.cfg | 14 # Enable debug when in low power modes
|
| /Zephyr-latest/boards/nxp/frdm_mcxn947/doc/ |
| D | index.rst | 150 A debug probe is used for both flashing and debugging the board. This board is
158 :ref:`mcu-link-cmsis-onboard-debug-probe` to reprogram the default MCU-Link
159 firmware. This only needs to be done if the default onboard debug circuit
166 There are two options. The onboard debug circuit can be updated with Segger
168 :ref:`mcu-link-jlink-onboard-debug-probe`.
171 The second option is to attach a :ref:`jlink-external-debug-probe` to the
254 :goals: debug
|
| /Zephyr-latest/samples/boards/st/power_mgmt/serial_wakeup/ |
| D | README.rst | 58 :kconfig:option:`CONFIG_DEBUG` could be enabled to allow debug. Note that debug mode prevents
60 Also note that after debug mode has been disabled, target should also be powered off in order
|
| /Zephyr-latest/cmake/sca/eclair/ECL/ |
| D | out_of_initial_scope.ecl | 9 -file_tag+={out_of_initial_scope, "^zephyr/subsys/(fb|fs|app_memory|fs|blueooth|console|cpp|debug|d…
|
| /Zephyr-latest/samples/net/dsa/ |
| D | README.rst | 5 Test and debug Distributed Switch Architecture
|
| /Zephyr-latest/subsys/net/lib/prometheus/ |
| D | Kconfig | 23 module-help = Enable debug message of PROMETHEUS client library.
|
| /Zephyr-latest/boards/arduino/opta/ |
| D | board.cmake | 15 # Give priority to dfu-util to flash, ST-Link to debug.
|
| /Zephyr-latest/samples/net/ptp/ |
| D | README.rst | 42 By default PTP in Zephyr will not print any PTP debug messages to console.
43 One can enable debug prints by setting
|
| /Zephyr-latest/boards/mikroe/clicker_ra4m1/doc/ |
| D | index.rst | 64 Also, see the instructions specific to the debug server that you use.
70 :goals: debug
|
| /Zephyr-latest/boards/adi/max32666fthr/doc/ |
| D | index.rst | 214 The MAX32666 MCU can be flashed by connecting an external debug probe to the SWD port.
215 SWD debug can be accessed through the Cortex 10-pin connector, JH2.
218 Once the debug probe is connected to your host computer, then you can simply run the
223 This board uses OpenOCD as the default debug interface. You can also use
226 be connected to the standard 2*5 pin debug connector (JH2) using an
232 Please refer to the `Flashing`_ section and run the ``west debug`` command
|
| /Zephyr-latest/boards/adi/apard32690/doc/ |
| D | index.rst | 188 The MAX32690 MCU can be flashed by connecting an external debug probe to the
189 SWD port. SWD debug can be accessed through the Cortex 10-pin connector, P9.
192 Once the debug probe is connected to your host computer, then you can simply run the
197 This board uses OpenOCD as the default debug interface. You can also use
200 be connected to the standard 2*5 pin debug connector (P9) using an
206 Please refer to the `Flashing`_ section and run the ``west debug`` command
|
| /Zephyr-latest/boards/arduino/nano_33_ble/doc/ |
| D | index.rst | 134 You can debug an application on the board with a debug adapter that supports
146 After connecting the debug adapter, you can debug it the usual way.
153 :goals: debug
189 west debug --runner=trace32 -- gdbRemote=:3333
|
| /Zephyr-latest/scripts/logging/dictionary/ |
| D | log_parser_uart.py | 48 if args.debug:
|
| /Zephyr-latest/include/zephyr/linker/ |
| D | common-rom.ld | 15 #include <zephyr/linker/common-rom/common-rom-debug.ld>
|
| /Zephyr-latest/boards/renesas/ek_ra6m2/doc/ |
| D | index.rst | 28 - 5V input through USB debug
133 You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
135 Once downloaded and installed, open Segger Ozone and configure the debug project
144 **Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
|
| /Zephyr-latest/boards/renesas/fpb_ra6e1/doc/ |
| D | index.rst | 38 - Debug/power LED (yellow) indicating power and the debug connection
128 You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
130 Once downloaded and installed, open Segger Ozone and configure the debug project
139 **Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
|
| /Zephyr-latest/cmake/bintools/gnu/ |
| D | target_bintools.cmake | 10 # elfconvert_flag_compress_debug_sections: --compress-debug-sections
38 set_property(TARGET bintools PROPERTY elfconvert_flag_compress_debug_sections "--compress-debug-sec…
84 # strip_flag_debug : --strip-debug
97 set_property(TARGET bintools PROPERTY strip_flag_debug --strip-debug)
|
| /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
117 To debug a previously flashed image, after resetting the board, use the 'debug'
124 :goals: debug
|
| /Zephyr-latest/boards/st/st25dv_mb1283_disco/doc/ |
| D | index.rst | 33 - On board ST link for microcontroller firmware upgrade and debug
88 ST25DV Discovery kit includes an ST-LINK/V2 embedded debug tool interface.
119 You can debug an application in the usual way. Here is an example for the
125 :goals: debug
|
| /Zephyr-latest/boards/st/stm3210c_eval/doc/ |
| D | index.rst | 37 - JTAG and trace debug support.
106 STM3210C-EVAL board includes an ST-LINK/V2-1 embedded debug tool interface.
140 You can debug an application in the usual way. Here is an example for the
147 :goals: debug
|
| /Zephyr-latest/boards/st/stm32373c_eval/doc/ |
| D | index.rst | 47 - JTAG/SWD and ETM trace debug support
114 STM32373C-EVAL board includes an ST-LINK/V2-1 embedded debug tool interface.
134 You can debug an application in the usual way. Here is an example for the
141 :goals: debug
|
| /Zephyr-latest/boards/madmachine/mm_swiftio/doc/ |
| D | index.rst | 177 This board is configured by default to use the :ref:`opensda-daplink-onboard-debug-probe`,
178 however the :ref:`pyocd-debug-host-tools` do not yet support programming the
184 Regardless of your choice in debug probe, we will use the OpenSDA
203 On Ubuntu, DAPLink debug probes appear on the host
|
| /Zephyr-latest/boards/nxp/frdm_rw612/doc/ |
| D | index.rst | 98 A debug probe is used for both flashing and debugging the board. This board is
116 :ref:`jlink-debug-host-tools` as default.
135 :ref:`jlink-debug-host-tools` as default.
140 :goals: debug
|
| /Zephyr-latest/boards/snps/emsdp/doc/ |
| D | index.rst | 8 to accelerate software development and debug of ARC EM processors and subsystems for
214 Using the latest version of Zephyr SDK(>=0.9), you can debug and flash IoT
217 One option is to build and debug the application using the usual
223 :goals: debug
225 At this point you can do your normal debug session. Set breakpoints and then
228 The other option is to launch a debug server, as follows.
235 Then connect to the debug server at the EM Software Development Platform from a
263 Most of the time you will not be flashing your program but will instead debug
|
| /Zephyr-latest/scripts/pylib/pytest-twister-harness/src/twister_harness/device/ |
| D | factory.py | 37 logger.debug('Get device type "%s"', name)
|
12345678910>>...34
