Searched +full:run +full:- +full:in +full:- +full:debug (Results 1 – 25 of 555) sorted by relevance
12345678910>>...23
| /Zephyr-latest/doc/develop/west/ |
| D | build-flash-debug.rst | 1 .. _west-build-flash-debug:
6 Zephyr provides several :ref:`west extension commands <west-extensions>` for
8 ``build``, ``flash``, ``debug``, ``debugserver`` and ``attach``.
11 commands, see :ref:`flash-and-debug-support` in the board porting guide.
13 .. Add a per-page contents at the top of the page. This page is nested
14 deeply enough that it doesn't have any subheadings in the main nav.
21 .. _west-building:
26 .. tip:: Run ``west build -h`` for a quick overview.
29 use :ref:`west config <west-config-cmd>` to configure its behavior.
33 - If there is a Zephyr build directory named :file:`build` in your current
[all …]
|
| D | without-west.rst | 1 .. _no-west:
7 not recommended for beginners due to the extra effort involved. In
11 - cloning the additional source code repositories used by Zephyr in
13 - specifying the locations of these repositories to the Zephyr build
15 - flashing and debugging without understanding detailed usage of the
23 .. code-block:: console
31 ------------------
33 In addition to downloading the zephyr source code repository itself,
34 you will need to manually clone the additional projects listed in the
37 .. code-block:: console
[all …]
|
| D | extensions.rst | 1 .. _west-extensions:
8 for short. Extensions show up in the ``west --help`` output in a special
13 Some commands you can run when using west with Zephyr, like the ones used to
14 :ref:`build, flash, and debug <west-build-flash-debug>` and the
15 :ref:`ones described here <west-zephyr-ext-cmds>` , are extensions. That's why
16 help for them shows up like this in ``west --help``:
18 .. code-block:: none
24 sign: sign a Zephyr binary for bootloader chain-loading
25 flash: flash and run a binary on a board
26 debug: flash and interactively debug a Zephyr application
[all …]
|
| /Zephyr-latest/tests/subsys/debug/gdbstub/ |
| D | testcase.yaml | 4 # SPDX-License-Identifier: Apache-2.0
9 - debug
10 - gdbstub
14 # Basic build-only test for all platforms supporting gdbstub
15 debug.gdbstub.build_only:
17 - qemu_x86
18 - qemu_cortex_a9
21 # Connect to Zephyr gdbstub and run a simple GDB script
22 debug.gdbstub.breakpoints:
24 - qemu_x86
[all …]
|
| /Zephyr-latest/scripts/west_commands/ |
| D | README.txt | 3 and debug commands.
6 extensions in upstream west. For example, any commands which operate
7 on the multi-repo need to be in upstream west, not here. Try to limit
8 what goes in here to Zephyr-specific features.
10 When extending this code, please keep the unit tests (in tests/) up to
11 date. The mypy static type checker is also run on the runners package.
13 To run these tests locally on Windows, run:
15 py -3 run_tests.py
21 Note that these tests are run as part of Zephyr's CI when submitting
|
| /Zephyr-latest/dts/bindings/pwm/ |
| D | nxp,imx-pwm.yaml | 2 # SPDX-License-Identifier: Apache-2.0
6 compatible: "nxp,imx-pwm"
8 include: [pwm-controller.yaml, pinctrl-device.yaml, base.yaml]
19 run-in-wait:
22 Enable for PWM to keep running in WAIT mode.
24 run-in-debug:
27 Enable for PWM to keep running in debug mode.
39 - "immediate"
40 - "half-cycle"
41 - "full-cycle"
[all …]
|
| /Zephyr-latest/tests/misc/llext-edk/pytest/ |
| D | test_edk.py | 3 # SPDX-License-Identifier: Apache-2.0
28 "-b",
30 "-t",
31 "llext-edk",
32 "--build-dir",
41 logger.debug(f"Copying llext-edk.tar.xz to {tempdir}")
42 edk_path = Path(unlaunched_dut.device_config.build_dir) / "zephyr/llext-edk.tar.xz"
46 logger.debug(f"Extracting llext-edk.tar.xz to {tempdir}")
47 command = ["tar", "-xf", "llext-edk.tar.xz"]
53 logger.debug(f"Copying extension to {tempdir_extension}")
[all …]
|
| /Zephyr-latest/cmake/usage/ |
| D | usage.cmake | 1 # SPDX-License-Identifier: Apache-2.0
8 set(verbose "-v")
14 message(" clean - Remove most generated files but keep configuration and backup files")
15 message(" pristine - Remove all files in the build directory")
18 message(" menuconfig - Update .config using a console-based interface")
19 message(" guiconfig - Update .config using a graphical interface")
22 message(" all - Build a zephyr application")
23 message(" run - Build a zephyr application and run it if the board supports emulation")
24 message(" flash - Run \"west flash\"")
25 message(" debug - Run \"west debug\"")
[all …]
|
| /Zephyr-latest/samples/boards/arc_secure_services/ |
| D | README.rst | 15 In this sample:
17 * Secure application will be in the secure memory space defined in
27 mpu entry in ``arc_mpu_regions.c``.
39 To use this sample, ARC processor should be equipped with ARC SecureShield. In
60 .. zephyr-app-commands::
61 :zephyr-app: samples/boards/arc_secure_services
69 Currently, in normal application, MPU is not accessible, so no user space and
70 mpu-based stack checking. Please copy the specific dts file and def_config
73 Here,take :zephyr:code-sample:`dining-philosophers` as an example for normal
76 .. zephyr-app-commands::
[all …]
|
| /Zephyr-latest/scripts/ |
| D | requirements-run-test.txt | 1 # RUN-TEST: required to do run time tests of zephyr
3 # things used by twister or related in run time testing
5 # used to flash & debug various boards
19 python-can>=4.3.0
|
| D | west-commands.yml | 1 # Keep the help strings in sync with the values in the .py files!
2 west-commands:
3 - file: scripts/west_commands/completion.py
5 - name: completion
8 - file: scripts/west_commands/boards.py
10 - name: boards
13 - file: scripts/west_commands/shields.py
15 - name: shields
18 - file: scripts/west_commands/build.py
20 - name: build
[all …]
|
| /Zephyr-latest/boards/snps/nsim/arc_classic/doc/ |
| D | index.rst | 6 This platform can be used to run Zephyr RTOS on the widest possible range of ARC processors in
7 simulation with `Designware ARC nSIM`_ or run same images on FPGA prototyping platform `HAPS`_. The
16 are currently supported in the Zephyr RTOS for ARC, again please refer to
19 There are multiple supported sub-configurations for that platform. Some but not all of currently
22 * ``nsim/nsim_em`` - ARC EM core v4.0 with two register banks, FastIRQ's, MPUv2, DSP options and
23 XY-memory
24 * ``nsim/nsim_em7d_v22`` - ARC EM core v3.0 with one register bank and FastIRQ's
25 * ``nsim/nsim_em11d`` - ARC EM core v4.0 with one register bank, no FastIRQ's, MPUv2, DSP options a…
26 XY-memory
27 * ``nsim/nsim_sem`` - ARC EM core v4.0 with secure features (thus "SEM", i.e. Secure EM) and MPUv4
[all …]
|
| /Zephyr-latest/doc/develop/tools/ |
| D | clion.rst | 8 This guide describes how to set up, build, and debug Zephyr's sample application in CLion, using
12 way to open, build, and run/debug Zephyr projects. This guide will be updated soon, but is still
15 CLion_ is a cross-platform C/C++ IDE that supports multi-threaded RTOS debugging.
18 :zephyr:code-sample:`multi-thread-blinky` sample in CLion.
20 The instructions have been tested on Windows. In terms of the CLion workflow, the steps would be the
32 This guide gives details on how to build and debug the :zephyr:code-sample:`multi-thread-blinky`
34 layout <west-workspaces>`.
37 instructions in the :ref:`getting_started`.
39 Open the project in CLion
42 #. In CLion, click :guilabel:`Open` on the Welcome screen or select :menuselection:`File --> Open`
[all …]
|
| /Zephyr-latest/doc/services/debugging/ |
| D | gdbstub.rst | 14 Serial Protocol (RSP) that allows you to remotely debug Zephyr
51 * If there are spare UART devices on the board, set ``zephyr,gdbstub-uart``
75 .. code-block:: bash
81 .. code-block:: bash
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.
95 Run the test with the following command from your :envvar:`ZEPHYR_BASE` directory:
97 .. code-block:: console
99 ./scripts/twister -p qemu_x86 -T tests/subsys/debug/gdbstub
101 The test should run successfully, and now let's do something similar step-by-step
[all …]
|
| /Zephyr-latest/boards/gaisler/generic_leon3/doc/ |
| D | index.rst | 7 designs available in the GRLIB GPL distribution.
14 designs such as the Digilent Arty A7, Terasic DE0-Nano and Microsemi
15 M2GL-EVAL-KIT.
25 In order to build the application for ``generic_leon3``, set the ``BOARD`` variable
31 Connect with GRMON, then load and run the application. The example below uses
32 the Terasic DE2-115 Cyclone IV FPGA board.
34 .. code-block:: console
36 $ grmon -altjtag -u
37 GRMON debug monitor v3.2.8 eval version
39 Copyright (C) 2020 Cobham Gaisler - All rights reserved.
[all …]
|
| /Zephyr-latest/boards/arm/fvp_baser_aemv8r/doc/ |
| D | debug-with-arm-ds.rst | 3 Debug with Arm DS
10 ``Version: 2020.b Build: 2020110909`` is used in the following example.
12 .. image:: images/version-info.jpg
16 Download Arm FVP BaseR AEMv8-R
25 From menu choose ``Window -> Perspective -> Open Perspective -> Other...``:
27 .. image:: images/perspective-choose-other.jpg
31 In the opened window, choose ``Development Studio (default)``:
33 .. image:: images/perspective-choose-ds.jpg
40 Create a new configuration database by selecting ``File -> New -> Other... -> Configuration Databas…
42 .. image:: images/create-new-configuration-database.jpg
[all …]
|
| /Zephyr-latest/boards/nxp/s32z2xxdc2/doc/ |
| D | index.rst | 6 The X-S32Z27X-DC (DC2) board is based on the NXP S32Z2 Real-Time Processor,
7 which includes two Real-Time Units (RTU) composed of four ARM Cortex-R52 cores
12 - ``s32z2xxdc2/s32z270/rtu0``, for S32Z270/RTU0
13 - ``s32z2xxdc2/s32z270/rtu1``, for S32Z270/RTU1.
19 `NXP S32Z2 Real-Time Processors website`_.
26 +-----------+------------+-------------------------------------+
29 | Arm GIC | on-chip | interrupt_controller |
30 +-----------+------------+-------------------------------------+
31 | Arm Timer | on-chip | timer |
32 +-----------+------------+-------------------------------------+
[all …]
|
| /Zephyr-latest/scripts/west_commands/completion/ |
| D | west-completion.fish | 1 # check if we are currently in a west workspace
4 # return 0 if in west workspace
15 # exclude the caller if one of the arguments is present in the command line
17 # return 1 if one of the arguments is present in the command line
20 set -l tokens (commandline -opc)
22 for t in $tokens
23 for a in $argv
41 set -l tokens (commandline -opc)
42 set -l argc (count $argv)
43 set -l max $argv[1]
[all …]
|
| /Zephyr-latest/samples/subsys/testsuite/pytest/shell/ |
| D | README.rst | 1 .. zephyr:code-sample:: pytest_shell
13 and then calls pytest in subprocess which runs tests from
17 is defined in ``pytest-twister-harness`` plugin. More information about plugin
28 Build and run sample by Twister:
30 .. code-block:: console
32 $ ./scripts/twister -vv --platform native_sim -T samples/subsys/testsuite/pytest/shell
38 .. code-block:: console
43 DEBUG: #: uart:~$ help
44 DEBUG: #: Please press the <Tab> button to see all available commands.
45 …DEBUG: #: You can also use the <Tab> button to prompt or auto-complete all commands or its subcomm…
[all …]
|
| /Zephyr-latest/boards/snps/iotdk/doc/ |
| D | index.rst | 11 SMIC's 55-nm ultra-low power process, and a rich set of peripherals commonly
12 used in IoT designs such as USB, UART, SPI, I2C, PWM, SDIO, and ADCs.
22 <https://embarc.org/project/arc-iot-development-kit/>`__
35 board is to run standalone, the universal switching power adaptor (110-240V
36 AC to 5V DC), provided in the package, can be used to power the board.
40 * Terminal emulator software for use with the USB-UART. Suggestion:
50 To run Zephyr application on IoT Development Kit, you need to
64 the one called :zephyr:code-sample:`hello_world`.
65 It is found in :zephyr_file:`samples/hello_world`.
68 -----------
[all …]
|
| /Zephyr-latest/boards/nxp/ucans32k1sic/doc/ |
| D | index.rst | 8 provides two CAN SIC interfaces and is based on the 32-bit Arm Cortex-M4F
14 - NXP S32K146
15 - Arm Cortex-M4F @ up to 112 Mhz
16 - 1 MB Flash
17 - 128 KB SRAM
18 - up to 127 I/Os
19 - 3x FlexCAN with 2x FD
20 - eDMA, 12-bit ADC, MPU, ECC and more.
22 - Interfaces:
23 - DCD-LZ debug interface with SWD + Console / UART
[all …]
|
| /Zephyr-latest/.github/workflows/ |
| D | compliance.yml | 6 - edited
7 - opened
8 - reopened
9 - synchronize
13 runs-on: ubuntu-22.04
14 name: Run compliance checks on patch series (PR)
16 - name: Update PATH for west
17 run: |
20 - name: Checkout the code
24 fetch-depth: 0
[all …]
|
| /Zephyr-latest/doc/develop/debug/ |
| D | index.rst | 11 This section is a quick hands-on reference to start debugging your
12 application with QEMU. Most content in this section is already covered in
19 In this quick reference, you'll find shortcuts, specific environmental
23 The simplest way to debug an application running in QEMU is using the GNU
24 Debugger and setting a local GDB server in your development system through QEMU.
27 debugging purposes. The build system generates the image in the build
43 You can run QEMU to listen for a "gdb connection" before it starts executing any
44 code to debug it.
46 .. code-block:: bash
48 qemu -s -S <image>
[all …]
|
| /Zephyr-latest/boards/raspberrypi/rpi_pico/doc/ |
| D | index.rst | 6 The Raspberry Pi Pico and Pico W are small, low-cost, versatile boards from
7 Raspberry Pi. They are equipped with an RP2040 SoC, an on-board LED,
9 Infineon CYW43439 2.4 GHz Wi-Fi/Bluetooth module. The USB bootloader allows the
10 ability to flash without any adapter, in a drag-and-drop manner.
11 It is also possible to flash and debug the boards with their SWD interface,
16 - Dual core Arm Cortex-M0+ processor running up to 133MHz
17 - 264KB on-chip SRAM
18 - 2MB on-board QSPI flash with XIP capabilities
19 - 26 GPIO pins
20 - 3 Analog inputs
[all …]
|
| /Zephyr-latest/scripts/west_commands/runners/ |
| D | mdb.py | 3 # SPDX-License-Identifier: Apache-2.0
18 # ZephyrBinaryRunner.__subclasses__() such sub-sub-classes won't be found.
28 # for nsim, we can't run and quit immediately
31 # if hostlink is used we can't run and quit immediately, as we still need MDB process
37 # for simulation targets we start cores in direct order
40 # and core ID in instruction traces
45 # with secondary cores startup - so we reverse start order
46 return mdb_runner.cores - 1 - id
53 mdb_basic_options = ['-nooptions', '-nogoifmain', '-toggle=include_local_symbols=1']
64 mdb_target = ['-nsim', '@' + mdb_runner.nsim_args]
[all …]
|
12345678910>>...23
