Searched refs:debug (Results 151 – 175 of 846) sorted by relevance
12345678910>>...34
8 # Enable debug when in low power modes
98 runners_yaml_append("\n# Default debug runner if --runner is not given.")99 runners_yaml_append("debug-runner: ${BOARD_DEBUG_RUNNER}")155 # Generate the flash, debug, debugserver, attach targets within the build157 foreach(target flash debug debugserver attach rtt)160 elseif(target STREQUAL debug)
21 - Micro-AB USB debug interface supporting CMSIS-DAP, Virtual COM Port and Data99 memory or connect to it via a debug interface. The only way to clear GPNVM0118 debug port. Then build and flash the :zephyr:code-sample:`hello_world` application.170 You can debug an application in the usual way. Here is an example for the177 :goals: debug
101 the embedded debug unit and can works as a console. The USART0 is shared108 `J-Link OB <https://www.segger.com/jlink-ob.html>`_. This provides a debug135 #. Connect the SAM4L-EK board to your host computer using the USB debug port.148 You can debug an application in the usual way. Here is an example for the155 :goals: debug
10 DAPLink debug access to the ARM DesignStart FPGA reference designs implemented19 In addition to DAPLink debug access, the V2C-DAPLink shield provides the
150 def debug(text): function170 debug(str(die))171 debug("File '%s', line %d:" % (path, lineno))172 debug(" %s" % text)642 debug("symbol '%s' at %s contains %d object(s)"660 debug("object '%s' found in invalid location %s"666 debug("skip kernel-only stack at %s" % hex(addr))695 debug("device instance at 0x%x has no associated subsystem"698 debug("device instance at 0x%x has unknown API 0x%x"707 debug("found %d kernel object instances total" % len(ret))
215 This board supports 3 debug host tools. Please install your preferred host219 * :ref:`linkserver-debug-host-tools` (Default, Supported by NXP)220 * :ref:`jlink-debug-host-tools` (Supported by NXP)221 * :ref:`pyocd-debug-host-tools` (Not supported by NXP)233 .. include:: ../../common/rt1xxx-lpclink2-debug.rst239 Regardless of your choice in debug probe, we will use the OpenSDA280 :goals: debug
40 self.logger.debug(" ".join(command))
40 logger.debug("Skip, requires non-secure connection")
58 JTAG/SWD debug121 :goals: debug124 https://www.segger.com/products/debug-probes/j-trace/accessories/trace-reference-boards/overview/
8 ; valid values: flash, debug *111 ELSE IF ("&command"=="debug")113 ; Setup minimal debug environment
284 logger.debug(f"HARNESS:{self.__class__.__name__}:EXPECTED:"291 logger.debug(f"HARNESS:{self.__class__.__name__}:EXPECTED("302 logger.debug(f"HARNESS:{self.__class__.__name__}:EXPECTED("549 logger.debug(f'Running pytest command: {cmd_to_print}')560 logger.debug(f'PYTEST: {line}')765 logger.debug(f"On {phase}: detected new Ztest suite '{ts_name}'")776 logger.debug(f"On {phase}: Ztest case '{tc_name}' matched to '{tc_fq_id}")778 logger.debug(794 logger.debug(f"START suite '{suite_name}'")809 logger.debug(f"END {phase} suite '{suite_name}':{self.started_suites[suite_name]}")[all …]
536 logger.debug(f"Building {self.source_dir} for {self.platform.name}")557 logger.debug(f'Running {" ".join(cmd)}')569 logger.debug(msg)610 logger.debug(f"Test skipped due to {overflow_found[0]} Overflow")643 logger.debug(f"Running cmake on {self.source_dir} for {self.platform.name}")672 logger.debug(f"Building {self.source_dir} using sysbuild")728 logger.debug(msg)774 logger.debug(f"Loaded sysbuild domain data from {domain_path}")967 logger.debug(f"filtering {self.instance.name}")993 logger.debug(f"CMake only: PASS {self.instance.name}")[all …]
160 We strongly recommend to debug with MetaWare debugger (MDB) because it:163 * Allows to debug both single-core and multi-core ``nsim`` targets.164 * Allows to debug on `HAPS`_ platform.171 west debug --runner mdb-nsim178 west debug --runner mdb-hw181 The ``west debug`` (as well as ``west flash``) is just a wrapper script and so it's possible to187 west -v debug --runner mdb-nsim195 -- west debug: using runner mdb-nsim217 simulator without ``west flash`` and ``west debug`` wrappers it's necessary to219 ``west debug`` it's done automatically by wrappers.[all …]
10 # elfconvert_flag_compress_debug_sections: --compress-debug-sections38 set_property(TARGET bintools PROPERTY elfconvert_flag_compress_debug_sections "--compress-debug-sec…91 # strip_flag_debug : --strip-debug104 set_property(TARGET bintools PROPERTY strip_flag_debug --strip-debug)
97 `J-Link OB <https://www.segger.com/jlink-ob.html>`_. This provides a debug124 #. Connect the RAK5010 board to your host computer using the USB debug port.137 You can debug an application in the usual way. Here is an example for the144 :goals: debug
62 JTAG debug203 The OLIMEX-STM32-P405 board does not include an embedded debug tool238 You can debug an application in the usual way. Here is an example for the245 :goals: debug
10 <zephyr/debug/symtab.h> header.
64 def parse_log_data(self, logdata, debug=False): argument
10 # Enable debug when in low power modes
14 # Enable debug when in low power modes
27 supported by the given MCU. Not all debug probes support high33 debug probe. Such configuration will persist only until the device
39 and debug configuration. The main difference is that debug configuration
335 This board supports 3 debug host tools. Please install your preferred host339 * :ref:`jlink-debug-host-tools` (Default, Supported by NXP)340 * :ref:`linkserver-debug-host-tools` (Supported by NXP)341 * :ref:`pyocd-debug-host-tools` (Not Supported by NXP)355 .. include:: ../../common/rt1xxx-lpclink2-debug.rst364 Regardless of your choice in debug probe, we will use the OpenSDA411 :goals: debug424 If the debug probe fails to connect with the following error, it's possible445 #. Run ``west debug`` or ``west flash`` again with a known working Zephyr452 If the west flash or debug commands fail, and the command hangs while executing[all …]
