Searched +full:west +full:- +full:commands (Results 1 – 25 of 471) sorted by relevance
12345678910>>...19
| /Zephyr-latest/doc/develop/west/ |
| D | extensions.rst | 1 .. _west-extensions:
6 West is "pluggable": you can add your own commands to west without editing its
7 source code. These are called **west extension commands**, or just "extensions"
8 for short. Extensions show up in the ``west --help`` output in a special
10 information on west extension commands, and has a tutorial for writing your
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
[all …]
|
| D | release-notes.rst | 1 .. _west-release-notes:
3 West Release Notes
11 - New ``west grep`` command for running a "grep tool" in your west workspace's
18 .. code-block:: console
20 west grep foo
22 Here are some other examples for running different grep commands
23 with ``west grep``:
25 .. list-table::
27 * - ``git grep --untracked``
28 - ``west grep --untracked foo``
[all …]
|
| D | alias.rst | 1 .. _west-aliases:
3 West aliases
6 West allows to add alias commands to the local, global or system configuration files.
8 commands for ease of development.
18 To add a new alias simply call the ``west config`` command:
20 .. code-block:: shell
22 west config alias.mylist "list -f '{name} {revision}'"
24 To list aliases, use :samp:`west help {some_alias}`.
27 building more complex but easy-to-remember commands.
31 .. code-block:: shell
[all …]
|
| D | index.rst | 3 West (Zephyr's meta-tool)
6 The Zephyr project includes a swiss-army knife command line tool named
7 ``west``\ [#west-name]_. West is developed in its own `repository`_.
9 West's built-in commands provide a multiple repository management system with
10 features inspired by Google's Repo tool and Git submodules. West is also
11 "pluggable": you can write your own west extension commands which add
12 additional features to west. Zephyr uses this to provide conveniences for
15 Like ``git`` and ``docker``, the top-level ``west`` command takes some common
16 options, a sub-command to run, and then options and arguments for that
17 sub-command::
[all …]
|
| D | built-in.rst | 1 .. _west-built-in-cmds:
3 Built-in commands
6 This page describes west's built-in commands, some of which were introduced in
7 :ref:`west-basics`, in more detail.
9 Some commands are related to Git commands with the same name, but operate
10 on the entire workspace. For example, ``west diff`` shows local changes in
13 Some commands take projects as arguments. These arguments can be project
15 on the local file system. Omitting project arguments to commands which
16 accept them (such as ``west list``, ``west forall``, etc.) usually defaults
20 For additional help, run ``west <command> -h`` (e.g. ``west init -h``).
[all …]
|
| D | config.rst | 1 .. _west-config:
6 This page documents west's configuration file system, the ``west config``
7 command, and configuration options used by built-in commands. For API
8 documentation on the ``west.configuration`` module, see
9 :ref:`west-apis-configuration`.
11 West Configuration Files
12 ------------------------
14 West's configuration file syntax is INI-like; here is an example file:
16 .. code-block:: ini
29 1. **System**: Settings in this file affect west's behavior for every user
[all …]
|
| D | basics.rst | 1 .. _west-basics:
6 This page introduces west's basic concepts and provides references to further
9 West's built-in commands allow you to work with :term:`projects <west project>`
10 (Git repositories) under a common :term:`workspace <west workspace>` directory.
12 West works in the following manner: the ``west init`` command creates the
13 :term:`west workspace`, and clones the :term:`manifest repo <west manifest
14 repository>`, while the ``west update`` command initially clones, and later updates, the
15 :term:`projects <west project>` listed in the manifest in the workspace.
21 :term:`west workspace`, which in this case is the folder named
24 .. code-block:: none
[all …]
|
| D | west-apis.rst | 3 .. _west-apis:
4 .. _west-apis-west:
6 West APIs
9 This page documents the Python APIs provided by :ref:`west <west>`, as well as
10 some additional APIs used by the :ref:`west extensions <west-extensions>` in
21 2. if you add a :ref: target here, add it to west-not-found.rst too.
23 .. _west-apis-commands:
25 west.commands
28 .. module:: west.commands
30 All built-in and extension commands are implemented as subclasses of the
[all …]
|
| D | troubleshooting.rst | 1 .. _west-troubleshooting:
3 Troubleshooting West
6 This page covers common issues with west and how to solve them.
8 ``west update`` fetching failures
11 One good way to troubleshoot fetching issues is to run ``west update`` in
14 .. code-block:: shell
16 west -v update
18 The output includes Git commands run by west and their outputs. Look for
21 .. code-block:: none
24 west.manifest: your_project: checking if cloned
[all …]
|
| D | west-not-found.rst | 3 .. _west-apis:
4 .. _west-apis-west:
5 .. _west-apis-commands:
6 .. _west-apis-westcommand:
7 .. _west-apis-configuration:
8 .. _west-apis-log:
9 .. _west-apis-manifest:
10 .. _west-apis-util:
12 West APIs
15 The west APIs are not documented since either west was missing or the zephyr
[all …]
|
| D | build-flash-debug.rst | 1 .. _west-build-flash-debug:
6 Zephyr provides several :ref:`west extension commands <west-extensions>` for
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
21 .. _west-building:
23 Building: ``west build``
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
34 working directory, it is incrementally re-compiled. The same is true if you
[all …]
|
| D | without-west.rst | 1 .. _no-west:
3 Using Zephyr without west
6 This page provides information on using Zephyr without west. This is
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
20 If you have previously installed west and want to stop using it,
23 .. code-block:: console
25 pip3 uninstall west
31 ------------------
[all …]
|
| /Zephyr-latest/scripts/west_commands/ |
| D | debug.py | 5 # SPDX-License-Identifier: Apache-2.0
7 '''west "debug", "debugserver", and "attach" commands.'''
11 from west.commands import WestCommand
21 # Keep this in sync with the string in west-commands.yml.
25 debugging session. Use "west attach" instead to attach
28 self.runner_key = 'debug-runner' # in runners.yaml
42 # Keep this in sync with the string in west-commands.yml.
52 self.runner_key = 'debug-runner' # in runners.yaml
66 # Keep this in sync with the string in west-commands.yml.
68 "Like \"west debug\", but doesn't reflash the program.",
[all …]
|
| D | README.txt | 1 This directory contains implementations for west commands which are
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.
15 py -3 run_tests.py
|
| D | completion.py | 3 # SPDX-License-Identifier: Apache-2.0
8 from west.commands import WestCommand
11 COMPLETION_REL_PATH = 'completion/west-completion'
14 Output shell completion scripts for west.
20 # one-time
21 source <(west completion bash)
23 west completion bash > ~/west-completion.bash
25 source $HOME/west-completion.bash
28 # one-time
29 source <(west completion zsh)
[all …]
|
| D | flash.py | 5 # SPDX-License-Identifier: Apache-2.0
7 '''west "flash" command'''
9 from west.commands import WestCommand
21 # Keep this in sync with the string in west-commands.yml.
25 self.runner_key = 'flash-runner' # in runners.yaml
|
| D | robot.py | 3 # SPDX-License-Identifier: Apache-2.0
5 from west.commands import WestCommand
18 # Keep this in sync with the string in west-commands.yml.
23 self.runner_key = 'robot-runner' # in runners.yaml
|
| D | simulate.py | 3 # SPDX-License-Identifier: Apache-2.0
5 from west.commands import WestCommand
18 # Keep this in sync with the string in west-commands.yml.
23 self.runner_key = 'sim-runner' # in runners.yaml
|
| D | zephyr_ext_common.py | 3 # SPDX-License-Identifier: Apache-2.0
5 '''Helpers shared by multiple west extension command modules.
8 commands are in run_common -- that's for common code used by
9 commands which specifically execute runners.'''
15 from west.commands import WestCommand
27 '''WestCommand subclass for commands with a --force option.'''
31 '''Add a -f / --force option to the parser.'''
32 parser.add_argument('-f', '--force', action='store_true',
47 self.die('refusing to proceed without --force due to above error')
51 self.dbg(f'west config {section_key}={unparsed}')
|
| /Zephyr-latest/samples/psa/its/ |
| D | README.rst | 1 .. zephyr:code-sample:: psa_its
3 :relevant-api: psa_secure_storage
11 …orage (ITS) API <https://arm-software.github.io/psa-api/storage/1.0/overview/architecture.html#the…
12 which is part of the `PSA Secure Storage API <https://arm-software.github.io/psa-api/storage/>`_,
34 .. tab:: TF-M
36 For board targets with TF-M:
38 .. zephyr-app-commands::
39 :zephyr-app: samples/psa/its
40 :tool: west
43 :west-args: -T sample.psa.its.tfm
[all …]
|
| /Zephyr-latest/samples/psa/persistent_key/ |
| D | README.rst | 1 .. zephyr:code-sample:: persistent_key
15 …orage (ITS) API <https://arm-software.github.io/psa-api/storage/1.0/overview/architecture.html#the…
32 .. tab:: TF-M
34 For board targets with TF-M:
36 .. zephyr-app-commands::
37 :zephyr-app: samples/psa/persistent_key
38 :tool: west
41 :west-args: -T sample.psa.persistent_key.tfm
45 For board targets without TF-M.
49 .. zephyr-app-commands::
[all …]
|
| /Zephyr-latest/doc/develop/manifest/ |
| D | index.rst | 5 West Projects index
8 See :ref:`external-contributions` for more information about
15 call :command:`west update`. Many of the projects or modules listed below are
20 following commands::
22 west config manifest.project-filter -- -hal_FOO
23 west update
25 .. manifest-projects-table::
33 call :command:`west update`. You can add any of the projects or modules listed below
37 To enable any of the modules below, use the following commands::
39 west config manifest.project-filter -- +nanopb
[all …]
|
| /Zephyr-latest/samples/subsys/ipc/openamp/ |
| D | README.rst | 1 .. zephyr:code-sample:: openamp
3 :relevant-api: ipm_interface
18 .. zephyr-app-commands::
19 :zephyr-app: samples/subsys/ipc/openamp
22 :west-args: --sysbuild
27 .. zephyr-app-commands::
28 :zephyr-app: samples/subsys/ipc/openamp
31 :west-args: --sysbuild
36 .. zephyr-app-commands::
37 :zephyr-app: samples/subsys/ipc/openamp
[all …]
|
| /Zephyr-latest/boards/m5stack/m5stack_cores3/doc/ |
| D | index.rst | 6 M5Stack CoreS3 is an ESP32-based development board from M5Stack. It is the third generation of the …
12 - ESP32-S3 chip (dual-core Xtensa LX7 processor @240MHz, WIFI, OTG and CDC functions)
13 - PSRAM 8MB
14 - Flash 16MB
15 - LCD ISP 2", 320x240 pixel ILI9342C
16 - Capacitive multi touch FT6336U
17 - Speaker 1W AW88298
18 - Dual Microphones ES7210 Audio decoder
19 - RTC BM8563
20 - USB-C
[all …]
|
| /Zephyr-latest/scripts/ |
| D | west-commands.yml | 2 west-commands:
3 - file: scripts/west_commands/completion.py
4 commands:
5 - name: completion
8 - file: scripts/west_commands/boards.py
9 commands:
10 - name: boards
13 - file: scripts/west_commands/shields.py
14 commands:
15 - name: shields
[all …]
|
12345678910>>...19
