Searched +full:west +full:- +full:commands (Results 1 – 25 of 151) sorted by relevance
1234567
| /Zephyr-Core-2.7.6/doc/guides/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 | 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 | 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 | 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 *projects* (Git
18 .. code-block:: none
20 zephyrproject/ # west topdir
21 ├── .west/ # marks the location of the topdir
22 │ └── config # per-workspace local configuration file
24 │ # The manifest repository, never modified by west after creation:
26 │ ├── west.yml # manifest file
29 │ # Projects managed by west:
[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 | release-notes.rst | 1 .. _west-release-notes:
3 West Release Notes
11 - ``west status`` now only prints output for projects which have a nonempty
16 - The manifest file parser was incorrectly allowing project names which contain
22 relative to its remote ``url-base:``, use ``repo-path:``. See
23 :ref:`west-manifests-projects` for examples.
25 - The changes made in west v0.10.1 to the ``west init --manifest-rev`` option
30 - The :envvar:`WEST_CONFIG_LOCAL` environment variable now correctly
31 overrides the default location, :file:`<workspace topdir>/.west/config`.
33 - ``west update --fetch=smart`` (``smart`` is the default) now correctly skips
[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
15 These APIs should be considered unstable until west version 1.0 (see `west
19 https://github.com/zephyrproject-rtos/west/issues/38
29 2. if you add a :ref: target here, add it to west-not-found.rst too.
31 .. _west-apis-commands:
33 west.commands
[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 | 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 | west-not-found.rst | 3 .. _west-apis:
4 .. _west-apis-west:
5 .. _west-apis-commands:
6 .. _west-apis-configuration:
7 .. _west-apis-log:
8 .. _west-apis-manifest:
9 .. _west-apis-util:
11 West APIs
14 The west APIs are not documented since either west was missing or the zephyr
15 repository was not initialized using west during the documentation build.
|
| 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 …]
|
| D | workspaces.rst | 1 .. _west-workspaces:
6 This page describes the *west workspace* concept introduced in
7 :ref:`west-basics` in more detail.
9 .. _west-manifest-rev:
11 The ``manifest-rev`` branch
14 West creates and controls a Git branch named ``manifest-rev`` in each
16 specified for the project at the time :ref:`west-update` was last run.
17 Other workspace management commands may use ``manifest-rev`` as a reference
19 purposes, the ``manifest-rev`` branch allows the manifest file to use SHAs
22 Although ``manifest-rev`` is a normal Git branch, west will recreate and/or
[all …]
|
| D | sign.rst | 1 .. _west-sign:
6 The ``west sign`` :ref:`extension <west-extensions>` command can be used to
8 external tool. Run ``west sign -h`` for command line help.
16 step by setting some Kconfig options. If you do, ``west flash`` will use the
19 If you use this feature, you don't need to run ``west sign`` yourself; the
23 :ref:`hello_world` application for chain-loading by MCUboot. Run these commands
27 .. code-block:: console
29 west build -b YOUR_BOARD -s bootloader/mcuboot/boot/zephyr -d build-mcuboot
30 west build -b YOUR_BOARD -s zephyr/samples/hello_world -d build-hello-signed -- \
31 -DCONFIG_BOOTLOADER_MCUBOOT=y \
[all …]
|
| D | manifest.rst | 1 .. _west-manifests:
3 West Manifests
6 This page contains detailed information about west's multiple repository model,
7 manifest files, and the ``west manifest`` command. For API documentation on the
8 ``west.manifest`` module, see :ref:`west-apis-manifest`. For a more general
9 introduction and command overview, see :ref:`west-basics`.
16 .. _west-mr-model:
21 West's view of the repositories in a :term:`west workspace`, and their
23 specific to upstream Zephyr's use of west):
25 .. figure:: west-mr-model.png
[all …]
|
| /Zephyr-Core-2.7.6/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 import log
9 from west.commands import WestCommand
12 COMPLETION_REL_PATH = 'completion/west-completion'
19 # Keep this in sync with the string in west-commands.yml.
31 # Remember to update west-completion.bash if you add or remove
|
| D | flash.py | 5 # SPDX-License-Identifier: Apache-2.0
7 '''west "flash" command'''
9 from west.commands import WestCommand
19 # Keep this in sync with the string in west-commands.yml.
23 self.runner_key = 'flash-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.'''
14 from west import log
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 log.die('refusing to proceed without --force due to above error')
|
| D | boards.py | 3 # SPDX-License-Identifier: Apache-2.0
12 from west import log
13 from west.commands import WestCommand
26 # Keep this in sync with the string in west-commands.yml.
40 --------------
51 - name: board name
52 - arch: board architecture
53 - dir: directory that contains the board definition
56 # Remember to update west-completion.bash if you add or remove
58 parser.add_argument('-f', '--format', default=default_fmt,
[all …]
|
| D | export.py | 3 # SPDX-License-Identifier: Apache-2.0
9 from west.commands import WestCommand
10 from west import log
29 'zephyr-export',
30 # Keep this in sync with the string in west-commands.yml.
47 run_cmake_export(share / 'zephyr-package' / 'cmake')
48 run_cmake_export(share / 'zephyrunittest-package' / 'cmake')
53 # Filtering out lines that start with -- ignores the normal
57 lines = run_cmake(['-P', str(path / 'zephyr_export.cmake')],
59 msg = [line for line in lines if not line.startswith('-- ')]
[all …]
|
| /Zephyr-Core-2.7.6/ |
| D | west.yml | 1 # The west manifest file for upstream Zephyr.
3 # The per-installation west configuration file, .west/config, sets the
13 # You can pass your manifest repositories to west init when creating a
14 # new Zephyr installation. See the west documentation for more
22 - name: upstream
23 url-base: https://github.com/zephyrproject-rtos
28 - name: canopennode
31 - name: civetweb
34 - name: cmsis
38 - hal
[all …]
|
| /Zephyr-Core-2.7.6/.github/workflows/ |
| D | west_cmds.yml | 2 # SPDX-License-Identifier: Apache-2.0
4 name: Zephyr West Command Tests
9 - v2.7-branch
11 - 'scripts/west-commands.yml'
12 - 'scripts/west_commands/**'
13 - '.github/workflows/west_cmds.yml'
16 - v2.7-branch
18 - 'scripts/west-commands.yml'
19 - 'scripts/west_commands/**'
20 - '.github/workflows/west_cmds.yml'
[all …]
|
| /Zephyr-Core-2.7.6/doc/_extensions/zephyr/ |
| D | application.py | 3 # SPDX-License-Identifier: Apache-2.0
19 of the shell commands needed to manage (build, flash, etc.) an application.
21 For example, to generate commands to build samples/hello_world for
24 .. zephyr-app-commands::
25 :zephyr-app: samples/hello_world
32 which tool to use. Valid options are currently 'cmake', 'west' and 'all'.
33 The default is 'west'.
38 \:zephyr-app:
42 \:cd-into:
51 \:host-os:
[all …]
|
| /Zephyr-Core-2.7.6/cmake/ |
| D | mcuboot.cmake | 2 # SPDX-License-Identifier: Apache-2.0
7 # It builds signed binaries using imgtool as a post-processing step
11 # function to avoid polluting the top-level scope.
14 # Property magic which makes west flash choose the signed build
30 if(NOT WEST)
31 # This feature requires west.
32 …message(FATAL_ERROR "Can't sign images for MCUboot: west not found. To fix, install west and ensur…
38 # Relative paths are relative to 'west topdir'.
43 …message(FATAL_ERROR "west sign can't find file ${${file}} (Note: Relative paths are relative to th…
50 # Find imgtool. Even though west is installed, imgtool might not be.
[all …]
|
1234567
