Searched refs:debug (Results 1 – 25 of 748) sorted by relevance
12345678910>>...30
5 A debug probe is used for both flashing and debugging the board. This board has6 an :ref:`opensda-onboard-debug-probe`. The default firmware present on this7 probe is the :ref:`opensda-daplink-onboard-debug-probe`.10 to setup your debug probe:12 * :ref:`jlink-debug-host-tools`: `Using J-Link on NXP OpenSDA Boards`_13 * :ref:`linkserver-debug-host-tools`: `Using DAPLink on NXP OpenSDA Boards`_14 * :ref:`pyocd-debug-host-tools`: `Using DAPLink on NXP OpenSDA Boards`_19 1. If the debug firmware has been modified, follow the instructions provided at20 :ref:`opensda-daplink-onboard-debug-probe` to reprogram the default debug27 There are two options: the onboard debug circuit can be updated with Segger[all …]
5 A debug probe is used for both flashing and debugging the board. This board has6 an :ref:`lpc-link2-onboard-debug-probe`. The default firmware present on this7 probe is the :ref:`lpclink2-daplink-onboard-debug-probe`.10 to setup your debug probe:12 * :ref:`jlink-debug-host-tools`:14 * :ref:`linkserver-debug-host-tools`:16 * :ref:`pyocd-debug-host-tools`:23 :ref:`lpclink2-cmsis-onboard-debug-probe` to reprogram the default debug30 There are two options: the onboard debug circuit can be updated with Segger31 J-Link firmware, or a :ref:`jlink-external-debug-probe` can be attached to the[all …]
6 A *debug probe* is special hardware which allows you to control execution of a10 also support other debug software and more advanced features such as12 software supported by Zephyr, see :ref:`flash-debug-host-tools`.21 an onboard debug probe, usb-to-serial adapter, and sometimes a drag-and-drop22 flash programmer. This eliminates the need to purchase an external debug probe23 and provides a variety of debug host tool options.25 Several hardware vendors have their own branded onboard debug probe27 `OpenSDA <#opensda-onboard-debug-probe>`_,28 `LPC-Link2 <#lpc-link2-onboard-debug-probe>`_, or29 `MCU-Link <#mcu-link-onboard-debug-probe>`_, probes depending on[all …]
1 .. _flash-debug-host-tools:7 flash and debug Zephyr applications.10 ``debug``, ``debugserver``, and ``attach`` commands, provided your board12 file declares that support properly. See :ref:`west-build-flash-debug` for202 .. _linkserver-debug-host-tools:207 Linkserver is a utility for launching and managing GDB servers for NXP debug probes,210 with custom debug configurations based on GNU tools or as part of a headless solution212 LPC11U35-based and OpenSDA based standalone or on-board debug probes from NXP.215 This method will also install the tools supporting the debug probes below,218 LinkServer is compatible with the following debug probes:[all …]
20 def __init__(self, debug = False): argument21 self.__debug = debug23 def debug(self, text): member in gen_isr_log106 self.__log.debug("Level Bits Bitmask")107 self.__log.debug("----------------------------")110 self.__log.debug(f"{i + 1:>5} {self.__int_bits[i]:>7} {bitmask_str:>14}")119 self.__log.debug('2nd level offsets: {}'.format(self.__irq2_offsets))128 self.__log.debug('3rd level offsets: {}'.format(self.__irq3_offsets))197 self.__log.debug('IRQ = ' + hex(irq))205 self.__log.debug('IRQ_level = 3')[all …]
20 def __init__(self, debug=False): argument21 self.__debug = debug23 def debug(self, text): member in gen_symtab_log85 log.set_debug(args.debug)119 log.debug('%6d: %s %s %.25s' % (
110 if args.debug:128 logger.debug("# Build ID: %s", database.get_build_id())129 logger.debug("# Target: %s, %d-bit", database.get_arch(), database.get_tgt_bits())131 logger.debug("# Endianness: Little")133 logger.debug("# Endianness: Big")135 logger.debug("# Database version: %d", database.get_version())137 ret = log_parser.parse_log_data(logdata, debug=args.debug)
32 logger.debug(f"Copying llext-edk.tar.xz to {tempdir}")37 logger.debug(f"Extracting llext-edk.tar.xz to {tempdir}")44 logger.debug(f"Copying extension to {tempdir_extension}")55 logger.debug(f"Building extension in {tempdir_extension} - cmake")60 logger.debug(f"Building extension in {tempdir_extension} - make")
21 prompt "MEC172x debug interface general configuration"28 bool "Disable debug support"35 bool "Debug support via Serial wire debug"40 bool "Debug support via Serial wire debug with tracing enabled"47 prompt "MEC172X debug interface trace configuration"51 Select tracing mode for debug interface54 bool "Debug support via Serial wire debug"60 bool "debug support via Serial Wire Debug and Viewer"
9 This strategy makes it possible to debug time-sensitive software, that would23 requires an implementation of debug monitor interrupt that will be executed26 With a SEGGER debug probe, it's possible to use a ready, SEGGER-provided implementation29 * :kconfig:option:`CONFIG_SEGGER_DEBUGMON`: enables SEGGER debug monitor interrupt. Can be30 used with SEGGER JLinkGDBServer and a SEGGER debug probe.46 required to debug in the monitor mode using regular GDB commands.47 Steps to configure SEGGER debug monitor:60 After these steps use regular gdb commands to debug your program.65 In order to provide a custom debug monitor interrupt, override ``z_arm_debug_monitor``67 (see :ref:`debug monitor sample<debugmon-sample>`).
21 - Built-in CMSIS-DAP debug adapter (Arduino UNO R4 WiFi only)43 A debug adapter is required to flash and debug programs.44 Arduino UNO R4 WiFi has a built-in debug adapter that48 debug adapter separately. A 5V-compatible CMSIS-DAP adapter74 Debugging can be done with ``west debug`` command.76 Also, see the instructions specific to the debug server that you use.82 :goals: debug88 :goals: debug94 Various debug adapters, including cmsis-dap probes, can debug the Arduino UNO R4 with pyOCD.
9 The Debug Monitor sample shows a basic configuration of debug monitor feature.14 #. Configure registers to enable degugging in debug monitor mode35 :zephyr-app: samples/subsys/debug/debugmon40 After flashing the board enters a breakpoint and executes debug monitor exception code.41 The LED starts to blink, indicating that even though the processor spins in debug monitor
45 prompt "MEC1501 debug interface general configuration"52 bool "Disable debug support"59 bool "Debug support via Serial wire debug"64 bool "Debug support via Serial wire debug with tracing enabled"72 prompt "MEC1501 debug interface trace configuration"76 Select tracing mode for debug interface79 bool "Debug support via Serial wire debug"85 bool "debug support via Serial Wire Debug and Viewer"
18 /* debug only, not using 32KHZ_IN pin */21 /* 32KHZ_IN is a clock source and no debug */24 /* 32KHZ_IN is a clock source with debug */
25 logger.debug(msg, str(args))27 logger.debug(msg, shlex.join(args))
111 logger.debug(f"Expected suite names:{expected_suite_names}")112 logger.debug(f"Detected suite names:{detected_suite_names}")135 logger.debug("Test suite names were not printed or some of them in " \163 logger.debug("Loaded sysbuild domain data from %s" % domain_path)214 logger.debug("OUTPUT: %s", stripped_line)318 logger.debug("Spawning process: " +333 logger.debug("Spawning BinaryHandler Thread for %s" % self.name)408 logger.debug('halted')428 logger.debug("Serial port is already closed, stop reading.")445 logger.debug("DEVICE: {0}".format(sl.rstrip()))[all …]
24 - On-board high-speed USB based debug probe with CMSIS-DAP and J-Link protocol25 support, can debug the on-board LPC51U68 or an external target26 - External debug probe option106 A debug probe is used for both flashing and debugging the board. This board is108 however the :ref:`pyocd-debug-host-tools` do not support this probe so you must109 reconfigure the board for one of the following debug probes instead.111 :ref:`lpclink2-jlink-onboard-debug-probe`114 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search117 Follow the instructions in :ref:`lpclink2-jlink-onboard-debug-probe` to program156 :goals: debug
9 bool "Print debug information"13 bool "Print debug information"
15 options and a built-in debug interface for flash programming and run-control.27 - OpenSDA debug interface125 A debug probe is used for both flashing and debugging the board. This board is126 configured by default to use the :ref:`opensda-daplink-onboard-debug-probe`.132 Option 1: Linkserver: :ref:`opensda-daplink-onboard-debug-probe` (Recommended)135 Install the :ref:`linkserver-debug-host-tools` and make sure they are in your136 search path. LinkServer works with the CMSIS-DAP debug firmware. Please follow the137 instructions on :ref:`opensda-daplink-onboard-debug-probe` and select the latest revision140 Linkserver is the default for this board, ``west flash`` and ``west debug`` will146 west debug[all …]
50 def debug(text): function132 debug("assign IRQ %d to vector %d" % (irq, vector))229 debug("spurious handler (code) : %s" % hex(header[0]))230 debug("spurious handler (no code) : %s" % hex(header[1]))235 debug("Configured interrupt routing")236 debug("handler irq pri vec dpl")237 debug("--------------------------")240 debug("{0:<10} {1:<3} {2:<3} {3:<3} {4:<2}".format(
9 # Ethos-U driver (err=0, warn=1, info=2, debug=3)10 set(ETHOSU_LOG_SEVERITY_MAP err err warning info debug)20 set(ETHOSU_LOG_SEVERITY debug CACHE STRING "")
151 This board supports West runners for the following debug tools:153 - :ref:`NXP S32 Debug Probe <nxp-s32-debug-probe>` (default)154 - :ref:`Lauterbach TRACE32 <lauterbach-trace32-debug-host-tools>`156 Follow the installation steps of the debug tool you plan to use before loading179 You can build and debug the :ref:`hello_world` sample for the board185 :goals: build debug193 :goals: build debug196 At this point you can do your normal debug session. Set breakpoints and then204 To debug with Lauterbach TRACE32 softare run instead:209 :goals: build debug -r trace32[all …]
28 - Onboard, high-speed USB, Link2 debug probe with CMSIS-DAP protocol (supporting Cortex M33 debug o…30 - UART, I2C and SPI port bridging from i.MX RT685 target to USB via the on-board debug probe224 A debug probe is used for both flashing and debugging the board. This board is231 1. Install the :ref:`linkserver-debug-host-tools` and make sure they are in your241 west debug246 1. Install the :ref:`jlink-debug-host-tools` and make sure they are in your search path.247 2. To connect the SWD signals to onboard debug circuit, install jumpers JP17, JP18 and JP19,249 3. Follow the instructions in :ref:`lpclink2-jlink-onboard-debug-probe` to program the255 west debug -r jlink260 1. Install the :ref:`jlink-debug-host-tools` and make sure they are in your search path.[all …]
