Searched refs:debug (Results 1 – 25 of 846) sorted by relevance
12345678910>>...34
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` for209 .. _linkserver-debug-host-tools:214 Linkserver is a utility for launching and managing GDB servers for NXP debug probes,217 with custom debug configurations based on GNU tools or as part of a headless solution219 LPC11U35-based and OpenSDA based standalone or on-board debug probes from NXP.222 This method will also install the tools supporting the debug probes below,225 LinkServer is compatible with the following debug probes:[all …]
41 logger.debug(f"Copying llext-edk.tar.xz to {tempdir}")46 logger.debug(f"Extracting llext-edk.tar.xz to {tempdir}")53 logger.debug(f"Copying extension to {tempdir_extension}")59 logger.debug(f"Copying file2hex.py to {tempdir_extension}")70 logger.debug(f"Building extension in {tempdir_extension} - cmake")75 logger.debug(f"Building extension in {tempdir_extension} - make")86 logger.debug(f"Running application with extension in {tempdir_extension} - west build")97 logger.debug(f"west command: {command}")102 logger.debug(f"Running application with extension in {tempdir_extension}")
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' % (
40 logger.debug("# Build ID: %s", database.get_build_id())41 logger.debug("# Target: %s, %d-bit", database.get_arch(), database.get_tgt_bits())43 logger.debug("# Endianness: Little")45 logger.debug("# Endianness: Big")
22 prompt "MEC172x debug interface general configuration"29 bool "Disable debug support"36 bool "Debug support via Serial wire debug"41 bool "Debug support via Serial wire debug with tracing enabled"48 prompt "MEC172X debug interface trace configuration"52 Select tracing mode for debug interface55 bool "Debug support via Serial wire debug"61 bool "debug support via Serial Wire Debug and Viewer"
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 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``
46 prompt "MEC1501 debug interface general configuration"53 bool "Disable debug support"60 bool "Debug support via Serial wire debug"65 bool "Debug support via Serial wire debug with tracing enabled"73 prompt "MEC1501 debug interface trace configuration"77 Select tracing mode for debug interface80 bool "Debug support via Serial wire debug"86 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 */
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
25 logger.debug(msg, str(args))27 logger.debug(msg, shlex.join(args))
9 bool "Print debug information"13 bool "Print debug information"
17 - On-board high-speed USB based debug probe with CMSIS-DAP and J-Link protocol18 support, can debug the on-board LPC51U68 or an external target19 - External debug probe option99 A debug probe is used for both flashing and debugging the board. This board is101 however the :ref:`pyocd-debug-host-tools` do not support this probe so you must102 reconfigure the board for one of the following debug probes instead.104 :ref:`lpclink2-jlink-onboard-debug-probe`107 Install the :ref:`jlink-debug-host-tools` and make sure they are in your search110 Follow the instructions in :ref:`lpclink2-jlink-onboard-debug-probe` to program149 :goals: debug
12 options and a built-in debug interface for flash programming and run-control.19 - OpenSDA debug interface117 A debug probe is used for both flashing and debugging the board. This board is118 configured by default to use the :ref:`opensda-daplink-onboard-debug-probe`.124 Option 1: Linkserver: :ref:`opensda-daplink-onboard-debug-probe` (Recommended)127 Install the :ref:`linkserver-debug-host-tools` and make sure they are in your128 search path. LinkServer works with the CMSIS-DAP debug firmware. Please follow the129 instructions on :ref:`opensda-daplink-onboard-debug-probe` and select the latest revision132 Linkserver is the default for this board, ``west flash`` and ``west debug`` will138 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 "")
94 The MAX32690 MCU can be flashed by connecting an external debug probe to the95 SWD port. SWD debug can be accessed through the Cortex 10-pin connector, J4.98 Once the debug probe is connected to your host computer, then you can run the109 This board uses OpenOCD as the default debug interface. You can also use a112 be connected to the standard 2*5 pin debug connector (J4) using an118 Once the debug probe is connected to your host computer, then you can run the119 ``west debug`` command to write a firmware image into flash and start a debug125 :goals: debug
49 logger.debug(f"{SB_CONFIG_APP_CPUPPR_RUN=}")50 logger.debug(f"{SB_CONFIG_APP_CPUFLPR_RUN=}")116 logger.debug(f"Using serial: {UART_PATH}")123 logger.debug(f"{BUILD_DIR=}")130 logger.debug(f"{config_str=}")
21 - Onboard, high-speed USB, Link2 debug probe with CMSIS-DAP protocol (supporting Cortex M33 debug o…23 - UART, I2C and SPI port bridging from i.MX RT685 target to USB via the on-board debug probe217 A debug probe is used for both flashing and debugging the board. This board is224 1. Install the :ref:`linkserver-debug-host-tools` and make sure they are in your234 west debug239 1. Install the :ref:`jlink-debug-host-tools` and make sure they are in your search path.240 2. To connect the SWD signals to onboard debug circuit, install jumpers JP17, JP18 and JP19,242 3. Follow the instructions in :ref:`lpclink2-jlink-onboard-debug-probe` to program the248 west debug -r jlink253 1. Install the :ref:`jlink-debug-host-tools` and make sure they are in your search path.[all …]
