Home
last modified time | relevance | path

Searched refs:debug (Results 76 – 100 of 846) sorted by relevance

12345678910>>...34

/Zephyr-latest/scripts/pylib/pytest-twister-harness/src/twister_harness/device/
Dhardware_adapter.py108 logger.debug('Flashing device %s', self.device_config.id)
132 logger.debug('Flashing finished')
140 logger.debug('Opening serial connection for %s', serial_name)
187 logger.debug('Closed serial connection for %s', serial_name)
195 logger.debug('Process %s terminated', self.device_config.serial_pty)
275 logger.debug(stdout.decode())
/Zephyr-latest/boards/gd/gd32f403z_eval/doc/
Dindex.rst6 The GD32F403Z-EVAL board is a hardware platform that enables design and debug
31 - CMSIS-DAP swd debug interface over USB HID.
105 allow flash programming and debug over USB. There are also program and debug
141 #. To debug an image:
146 :goals: debug
/Zephyr-latest/boards/gd/gd32a503v_eval/doc/
Dindex.rst6 The GD32A503V-EVAL board is a hardware platform that enables design and debug
26 - CMSIS-DAP swd debug interface over USB HID.
110 allow flash programming and debug over USB. There are also program and debug
146 #. To debug an image:
151 :goals: debug
/Zephyr-latest/boards/olimex/stm32_h103/doc/
Dindex.rst90 JTAG/SWD debug
184 This board does not include any embedded debug tool interface, instead you
186 connector to program and debug the board. Both JTAG and SWD are supported.
188 By default when using ``west debug`` ST-Link will be used with OpenOCD's
208 You can debug an application in the usual way. Here is an example for the
215 :goals: debug
/Zephyr-latest/boards/gd/gd32e103v_eval/doc/
Dindex.rst6 The GD32E103V-EVAL board is a hardware platform that enables design and debug
28 - CMSIS-DAP swd debug interface over USB HID.
102 allow flash programming and debug over USB. There are also program and debug
138 #. To debug an image:
143 :goals: debug
/Zephyr-latest/boards/atmel/sam/sam4s_xplained/doc/
Dindex.rst17 - Micro-AB USB debug interface supporting SEGGER OB and Virtual COM Port and
82 The section flashing uses the UART from the Segger USB debug connection.
88 `J-Link OB <https://www.segger.com/jlink-ob.html>`_. This provides a debug
106 #. Connect the SAM4S Xplained board to your host computer using the USB debug
162 You can debug an application in the usual way. Here is an example for the
169 :goals: debug
/Zephyr-latest/doc/services/debugging/
Dgdbstub.rst14 Serial Protocol (RSP) that allows you to remotely debug Zephyr
90 There is a test application :zephyr_file:`tests/subsys/debug/gdbstub` with one of its
91 test cases ``debug.gdbstub.breakpoints`` demonstrating how the Zephyr GDB stub can be used.
99 ./scripts/twister -p qemu_x86 -T tests/subsys/debug/gdbstub
113 :zephyr-app: tests/subsys/debug/gdbstub
165 #1 0x00104140 in gdb_init () at <ZEPHYR_BASE>/zephyr/subsys/debug/gdbstub.c:852
198 gdb_init () at <ZEPHYR_BASE>/subsys/debug/gdbstub.c:857
222 … Breakpoint 1 at 0x10064d: file <ZEPHYR_BASE>/tests/subsys/debug/gdbstub/src/main.c, line 27.
234 Breakpoint 1, main () at <ZEPHYR_BASE>/tests/subsys/debug/gdbstub/src/main.c:27
275 Run till exit from #0 test () at <ZEPHYR_BASE>/tests/subsys/debug/gdbstub/src/main.c:17
[all …]
/Zephyr-latest/boards/arm/fvp_base_revc_2xaemv8a/
Dboard.cmake39 set(FVP_SECURE_FLASH_FILE ${TFA_BINARY_DIR}/fvp/debug/bl1.bin)
40 set(FVP_FLASH_FILE ${TFA_BINARY_DIR}/fvp/debug/fip.bin)
/Zephyr-latest/samples/subsys/debug/fuzz/
DREADME.rst29 $ west build -t run -b native_sim/native/64 samples/subsys/debug/fuzz
54 …NEW_FUNC[1/6]: 0x55cbe3339c45 in check1 /home/andy/z/zephyr/samples/subsys/debug/fuzz/src/main.c:43
64 …NEW_FUNC[1/1]: 0x55cbe3339ff7 in check6 /home/andy/z/zephyr/samples/subsys/debug/fuzz/src/main.c:48
75 #0 0x55cbe333a09d in check6 /home/andy/z/zephyr/samples/subsys/debug/fuzz/src/main.c:48:1
/Zephyr-latest/boards/nxp/lpcxpresso55s06/doc/
Dindex.rst18 - LPC-Link2 debug high speed USB probe with VCOM port
123 A debug probe is used for both flashing and debugging the board. This
125 Debug Probe, however the :ref:`pyocd-debug-host-tools` does not yet
127 J-Link debug probe instead.
129 First install the :ref:`jlink-debug-host-tools` and make sure they are
133 :ref:`lpclink2-jlink-onboard-debug-probe` to program the J-Link
175 :goals: debug
/Zephyr-latest/boards/nxp/ucans32k1sic/doc/
Dindex.rst23 - DCD-LZ debug interface with SWD + Console / UART
109 The serial console is provided via ``lpuart1`` on the 7-pin DCD-LZ debug
132 in :ref:`lauterbach-trace32-debug-host-tools` and :ref:`jlink-debug-host-tools`,
133 to setup the flash and debug host tools for these runners, respectively. The
172 Run the ``west debug`` command to start a GDB session using SEGGER J-Link.
173 Alternatively, run ``west debug -r trace32`` to launch the Lauterbach TRACE32
/Zephyr-latest/boards/atmel/sam/sam_e70_xplained/doc/
Dindex.rst21 - Micro-AB USB debug interface supporting CMSIS-DAP, Virtual COM Port and Data
109 memory or connect to it via a debug interface. The only way to clear GPNVM0
137 USB debug port. Then build and flash the :zephyr:code-sample:`hello_world`
156 You can flash the image using an external debug adapter such as J-Link
158 debug adapter (e.g., ``jlink``) via an OPENOCD_INTERFACE environment
166 You can debug an application in the usual way. Here is an example for the
173 :goals: debug
/Zephyr-latest/boards/atmel/sam/sam_v71_xult/doc/
Dindex.rst27 - Micro-AB USB debug interface supporting CMSIS-DAP, Virtual COM Port and Data
112 memory or connect to it via a debug interface. The only way to clear GPNVM0
140 USB debug port. Then build and flash the :zephyr:code-sample:`hello_world`
159 You can flash the image using an external debug adapter such as J-Link
161 debug adapter (e.g., ``jlink``) via an OPENOCD_INTERFACE environment
169 You can debug an application in the usual way. Here is an example for the
176 :goals: debug
/Zephyr-latest/boards/raspberrypi/rpi_pico/doc/
Dindex.rst11 It is also possible to flash and debug the boards with their SWD interface,
181 You can Flash the rpi_pico with a SEGGER JLink debug probe as described in
209 and debug the on board RP2040. This interface can be utilized by OpenOCD.
232 **RPI_PICO_DEBUG_ADAPTER** specifies what debug adapter is used for debugging.
237 Any other SWD debug adapter maybe also work with this configuration.
240 ``west flash`` and ``west debug`` if it was previously set while running
244 Thus, **RPI_PICO_DEBUG_ADAPTER** needs to be assigned the file name of the debug adapter.
265 The SWD interface can also be used to debug the board. To achieve this, you can
271 Use a SEGGER JLink debug probe and follow the instruction in
286 :goals: debug
[all …]
/Zephyr-latest/scripts/footprint/
Dcompare_footprint68 logging.debug("Log init completed")
125 logger.debug('Sanity (%s) %s' %(commit, cmd))
131 logger.debug(output)
139 logging.debug("footprint build for %s" % commit)
148 logging.debug("cloning into %s" % tmp_location)
/Zephyr-latest/boards/rakwireless/rak4631/doc/
Dindex.rst22 programming/debug interface.
89 `J-Link OB <https://www.segger.com/jlink-ob.html>`_. This provides a debug
116 #. Connect the RAK4631 board to your host computer using the USB debug port.
129 You can debug an application in the usual way. Here is an example for the
136 :goals: debug
/Zephyr-latest/boards/st/stm32mp157c_dk2/support/
Dopenocd.cfg3 # By default the port 3333 is assigned for the Cortex-A debug. Disable them
/Zephyr-latest/boards/qemu/xtensa/
Dboard.cmake13 # TODO: Support debug
/Zephyr-latest/scripts/build/
Dllext_inject_slids.py48 self.log.debug(f"section {section_name} not found.")
51 self.log.debug(f"(symbol table is at file offset 0x{symtab['sh_offset']:X})")
64 self.log.debug(f"found imported symbol '{sym.name}' at index {i}")
/Zephyr-latest/samples/boards/microchip/mec15xxevb_assy6853/power_management/
Dmec15xxevb_assy6853.overlay16 /* debug only, not using 32KHZ_IN pin */
/Zephyr-latest/doc/develop/west/
Dwithout-west.rst81 Running build system targets like ``ninja flash``, ``ninja debug``,
83 <west-build-flash-debug>`. For example, ``ninja flash`` calls ``west
85 those targets will fail. You can of course still flash and debug using
86 any :ref:`flash-debug-host-tools` which work for your board (and which those
109 to flash and debug, you must specify the west directory. This can be
121 invoke ``ninja flash``, ``debug``, etc. The one exception is if you
/Zephyr-latest/boards/seeed/xiao_ble/doc/
Dindex.rst97 can use an :ref:`External Debug Probe <debug-probes>`. To flash and debug Zephyr
101 For Segger J-Link debug probes, follow the instructions in the
102 :ref:`jlink-external-debug-probe` page to install and configure all the
108 Setup and connect a supported debug probe (JLink, instructions at :ref:`jlink-external-debug-probe`…
149 Refer to the :ref:`jlink-external-debug-probe` page to learn about debugging
/Zephyr-latest/boards/snps/iotdk/doc/
Dindex.rst120 Using the latest version of Zephyr SDK(>=0.9), you can debug and flash IoT
123 One option is to build and debug the application using the usual
129 :goals: debug
131 At this point you can do your normal debug session. Set breakpoints and then
134 The other option is to launch a debug server, as follows.
141 Then connect to the debug server at the IoT Development Kit from a second
168 Most of the time you will not be flashing your program but will instead debug
/Zephyr-latest/boards/nxp/frdm_mcxc242/doc/
Dindex.rst134 A debug probe is used for both flashing and debugging the board. This board is
142 :ref:`mcu-link-cmsis-onboard-debug-probe` to reprogram the default MCU-Link
143 firmware. This only needs to be done if the default onboard debug circuit
150 There are two options. The onboard debug circuit can be updated with Segger
152 :ref:`mcu-link-jlink-onboard-debug-probe`.
155 The second option is to attach a :ref:`jlink-external-debug-probe` to the
201 :goals: debug
/Zephyr-latest/boards/nxp/frdm_mcxc444/doc/
Dindex.rst131 A debug probe is used for both flashing and debugging the board. This board is
139 :ref:`mcu-link-cmsis-onboard-debug-probe` to reprogram the default MCU-Link
140 firmware. This only needs to be done if the default onboard debug circuit
147 There are two options. The onboard debug circuit can be updated with Segger
149 :ref:`mcu-link-jlink-onboard-debug-probe`.
152 The second option is to attach a :ref:`jlink-external-debug-probe` to the
198 :goals: debug

12345678910>>...34