Searched refs:debug (Results 26 – 50 of 846) sorted by relevance
12345678910>>...34
17 - On-board high-speed USB based debug probe with CMSIS-DAP and J-Link protocol18 support, can debug the on-board LPC54114 or an external target19 - External debug probe option28 debug probe129 A debug probe is used for both flashing and debugging the board. This board is131 however the :ref:`pyocd-debug-host-tools` do not support this probe so you must132 reconfigure the board for one of the following debug probes instead.134 :ref:`lpclink2-jlink-onboard-debug-probe`137 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search140 Follow the instructions in :ref:`lpclink2-jlink-onboard-debug-probe` to program[all …]
20 :goals: debug29 :goals: debug38 :goals: debug47 :goals: debug56 :goals: debug
21 :goals: debug30 :goals: debug39 :goals: debug48 :goals: debug57 :goals: debug
114 logger.debug(f"Expected suite names:{expected_suite_names}")115 logger.debug(f"Detected suite names:{detected_suite_names}")140 logger.debug(173 logger.debug(f"Loaded sysbuild domain data from {domain_path}")230 logger.debug(f"OUTPUT: {stripped_line}")346 logger.debug("Spawning process: " +362 logger.debug(f"Spawning BinaryHandler Thread for {self.name}")435 logger.debug('halted')455 logger.debug("Serial port is already closed, stop reading.")471 logger.debug(f"DEVICE: {sl}")[all …]
19 bool "Prepend debug header, disabling flash verification" if XIP24 bool "Prepend debug header, disabling flash verification" if XIP
17 module-help = Enables debug of network packet and buffer allocations and frees.51 module-help = Enables core network stack code to output debug messages.57 module-help = Enables network interface code to output debug messages.63 module-help = Enables network traffic class code to output debug messages.69 module-help = Enables utility functions to output debug messages.81 module-help = Enables UDP/TCP connection debug messages.87 module-help = Enables routing engine debug messages.
75 self.__log.debug(str(header_raw))90 self.__log.debug("Configured interrupt routing")91 self.__log.debug("handler irq flags param")92 self.__log.debug("--------------------------")95 self.__log.debug("{0:<10} {1:<3} {2:<3} {3}".format(124 self.__log.debug('offset is ' + str(offset))125 self.__log.debug('num_vectors is ' + str(nvec))
93 self.__log.debug(str(header_raw))121 self.__log.debug("Unpacked IRQ{}, flags: {}, sname: \"{}\"\n".format(128 self.__log.debug("Configured interrupt routing with linker")129 self.__log.debug("irq flags sname")130 self.__log.debug("--------------------------")133 self.__log.debug("{0:<3} {1:<5} {2}".format(167 self.__log.debug('offset is ' + str(offset))168 self.__log.debug('num_vectors is ' + str(nvec))
22 logger.debug('Found matching key: %s' % line.strip())24 logger.debug('Not found key: %s' % config_key)
182 This board supports West runners for the following debug tools:184 - :ref:`NXP S32 Debug Probe <nxp-s32-debug-probe>` (default)185 - :ref:`Lauterbach TRACE32 <lauterbach-trace32-debug-host-tools>`187 Follow the installation steps of the debug tool you plan to use before loading210 You can build and debug the :zephyr:code-sample:`hello_world` sample for the board216 :goals: build debug224 :goals: build debug227 At this point you can do your normal debug session. Set breakpoints and then235 To debug with Lauterbach TRACE32 softare run instead:240 :goals: build debug -r trace32[all …]
7 MCU-based platforms. The onboard OpenSDAv2 serial and debug adapter,96 A debug probe is used for both flashing and debugging the board. This board is106 Install the :ref:`linkserver-debug-host-tools` and make sure they are in your110 Linkserver is the default for this board, ``west flash`` and ``west debug`` will113 Option 2: :ref:`opensda-jlink-onboard-debug-probe`116 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search119 Follow the instructions in :ref:`opensda-jlink-onboard-debug-probe` to program130 Regardless of your choice in debug probe, we will use the OpenSDA169 :goals: debug197 .. _linkserver-debug-host-tools:[all …]
21 - Onboard, high-speed USB, Link2 debug probe with CMSIS-DAP protocol (supporting Cortex M33 debug o…184 For detailed instructions on how to debug DSP firmware, please refer to196 A debug probe is used for both flashing and debugging the board. This board is204 1. Install the :ref:`jlink-debug-host-tools` and make sure they are in your search path.205 2. To connect the SWD signals to onboard debug circuit, install jumpers JP17, JP18 and JP19,207 3. Follow the instructions in :ref:`lpclink2-jlink-onboard-debug-probe` to program the213 1. Install the :ref:`jlink-debug-host-tools` and make sure they are in your search path.215 2. To disconnect the SWD signals from onboard debug circuit, **remove** jumpers J17, J18,220 See :ref:`jlink-external-debug-probe` for more information.224 … 1. Install the :ref:`linkserver-debug-host-tools` and make sure they are in your search path.[all …]
8 This guide describes how to set up, build, and debug Zephyr's sample application in CLion, using12 way to open, build, and run/debug Zephyr projects. This guide will be updated soon, but is still32 This guide gives details on how to build and debug the :zephyr:code-sample:`multi-thread-blinky`93 Configure Zephyr parameters for debug124 This option enables Zephyr tasks view during debugging. See `Multi-threaded RTOS debug`_ in CLion132 In order to debug a Zephyr application in CLion, you need to create a run/debug configuration out of135 Instructions below show the case of a Nordic Semiconductor board and a Segger J-Link debug probe. If208 :alt: Viewing Zephyr tasks during a debug session210 Refer to `CLion web help`_ for detailed description of the IDE debug capabilities.216 .. _Multi-threaded RTOS debug: https://www.jetbrains.com/help/clion/rtos-debug.html
7 MCU-based platforms. The onboard OpenSDAv2 serial and debug adapter,133 A debug probe is used for both flashing and debugging the board. This board is134 configured by default to use the :ref:`opensda-daplink-onboard-debug-probe`.140 Option 1: :ref:`opensda-daplink-onboard-debug-probe` (Recommended)143 Install the :ref:`pyocd-debug-host-tools` and make sure they are in your search146 Follow the instructions in :ref:`opensda-daplink-onboard-debug-probe` to program149 Option 2: :ref:`opensda-jlink-onboard-debug-probe`152 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search155 Follow the instructions in :ref:`opensda-jlink-onboard-debug-probe` to program171 Regardless of your choice in debug probe, we will use the OpenSDA[all …]
15 - OpenSDAv2, the NXP open source hardware embedded serial and debug adapter30 - Programmable OpenSDAv2 debug circuit supporting the CMSIS-DAP Interface34 - CMSIS-DAP debug interface over a driver-less USB HID connection providing177 A debug probe is used for both flashing and debugging the board. This board is178 configured by default to use the :ref:`opensda-daplink-onboard-debug-probe`.184 Option 1: :ref:`opensda-daplink-onboard-debug-probe` (Recommended)187 Follow the instructions in :ref:`opensda-daplink-onboard-debug-probe` to program190 Install the :ref:`linkserver-debug-host-tools` and make sure they are in your194 Linkserver is the default for this board, ``west flash`` and ``west debug`` will201 Alternatively, pyOCD can be used to flash and debug the board by using the[all …]
14 /* DWARF debug sections.18 SECTION_PROLOGUE(.debug, 0,) { *(.debug) }
11 - On-board debug probe J-Link-OB for programming20 - On-board debug probe J-Link-OB for programming94 A debug probe is used for both flashing and debugging the board. This board is95 configured by default to use the :ref:`opensda-jlink-onboard-debug-probe`.97 :ref:`opensda-jlink-onboard-debug-probe`100 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search103 Follow the instructions in :ref:`opensda-jlink-onboard-debug-probe` to program130 :goals: debug
82 module-str = Log level mbedTLS library debug hook86 bool "mbed TLS debug activation"90 activate debug logging.95 function in your application. Alternatively implement your own debug109 Default mbed TLS debug logging level for Zephyr integration code110 (from ext/lib/crypto/mbedtls/include/mbedtls/debug.h):111 0 No debug118 mbedTLS initialization, with the configured debug log level.130 when debug messages are enabled.138 Filename passed as argument to debug hook will be stripped from[all …]
15 - OpenSDAv2.1, the NXP open source hardware embedded serial and debug adapter31 - Programmable OpenSDAv2.1 debug circuit supporting the CMSIS-DAP Interface35 - CMSIS-DAP debug interface over a driver-less USB HID connection providing136 A debug probe is used for both flashing and debugging the board. This board is137 configured by default to use the :ref:`opensda-daplink-onboard-debug-probe`.143 Option 1: :ref:`opensda-daplink-onboard-debug-probe` (Recommended)146 Install the :ref:`pyocd-debug-host-tools` and make sure they are in your search149 Follow the instructions in :ref:`opensda-daplink-onboard-debug-probe` to program152 Option 2: :ref:`opensda-jlink-onboard-debug-probe`155 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search[all …]
8 architecture. The board includes a high performance onboard debug probe, audio16 - Onboard, high-speed USB, Link2 debug probe with CMSIS-DAP and SEGGER J-Link18 - UART and SPI port bridging from LPC55S69 target to USB via the onboard debug20 - Hardware support for external debug probe277 A debug probe is used for both flashing and debugging the board. This board is279 however the :ref:`pyocd-debug-host-tools` does not yet support this probe so you280 must reconfigure the board for one of the following debug probes instead.282 :ref:`lpclink2-jlink-onboard-debug-probe`285 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search288 Follow the instructions in :ref:`lpclink2-jlink-onboard-debug-probe` to program[all …]
94 A debug probe is used for both flashing and debugging the board. This board is104 Install the :ref:`linkserver-debug-host-tools` and make sure they are in your108 Linkserver is the default for this board, ``west flash`` and ``west debug`` will116 External JLink: :ref:`jlink-external-debug-probe`119 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search134 Regardless of your choice in debug probe, we will use the OpenSDA173 :goals: debug199 …https://www.nxp.com/design/design-center/software/sensor-toolbox/opensda-serial-and-debug-adapter:…201 .. _linkserver-debug-host-tools:
34 - OpenSDA and JTAG debug147 A debug probe is used for both flashing and debugging the board. This board is148 configured by default to use the :ref:`opensda-daplink-onboard-debug-probe`.150 Option 1: :ref:`opensda-daplink-onboard-debug-probe` (Recommended)153 Install the :ref:`pyocd-debug-host-tools` and make sure they are in your search156 Follow the instructions in :ref:`opensda-daplink-onboard-debug-probe` to program159 Option 2: :ref:`opensda-jlink-onboard-debug-probe`162 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search165 Follow the instructions in :ref:`opensda-jlink-onboard-debug-probe` to program181 Regardless of your choice in debug probe, we will use the OpenSDA[all …]
54 def debug(text): function78 debug("create pseudo descriptor: %x %x" % (addr, size))101 debug("create code or data entry: %x %x %x %x %x" %130 debug("create TSS entry: %x %x %x" % (base, limit, dpl))
64 logger.debug(f"{SB_CONFIG_APP_CPUPPR_RUN=}")65 logger.debug(f"{SB_CONFIG_APP_CPUFLPR_RUN=}")138 logger.debug(f"Using serial: {UART_PATH}")145 logger.debug(f"{BUILD_DIR=}")152 logger.debug(f"{config_str=}")
253 A debug probe is used for both flashing and debugging the board. This board is254 configured by default to use the :ref:`opensda-daplink-onboard-debug-probe`,255 however the :ref:`pyocd-debug-host-tools` do not yet support programming the257 following debug probes instead.264 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search269 There are two options: the onboard debug circuit can be updated with Segger270 J-Link firmware, or :ref:`jlink-external-debug-probe` can be attached to the277 Regardless of your choice in debug probe, we will use the OpenSDA280 Connect a USB cable from your PC to PixHawk debug adapter.322 :goals: debug[all …]
