Home
last modified time | relevance | path

Searched +full:manifest +full:- +full:path (Results 1 – 25 of 25) sorted by relevance

/Zephyr-Core-2.7.6/doc/guides/west/
Dmanifest.rst1 .. _west-manifests:
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:
25 .. figure:: west-mr-model.png
27 :alt: West multi-repo history
28 :figclass: align-center
30 West multi-repo history
32 The history of the manifest repository is the line of Git commits which is
[all …]
Drelease-notes.rst1 .. _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
17 the path separator characters ``/`` and ``\``. These invalid characters are
21 topdir, use the ``path:`` key. If you need to customize a project's fetch URL
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
26 which selected the default branch name were leaving the manifest repository
30 - The :envvar:`WEST_CONFIG_LOCAL` environment variable now correctly
[all …]
Dconfig.rst1 .. _west-config:
7 command, and configuration options used by built-in commands. For API
9 :ref:`west-apis-configuration`.
12 ------------------------
14 West's configuration file syntax is INI-like; here is an example file:
16 .. code-block:: ini
18 [manifest]
19 path = zephyr
24 Above, the ``manifest`` section has option ``path`` set to ``zephyr``. Another
25 way to say the same thing is that ``manifest.path`` is ``zephyr`` in this file.
[all …]
Dbuilt-in.rst1 .. _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.
14 names as specified in the manifest file, or (as a fallback) paths to them
17 to using all projects in the manifest file plus the manifest repository
20 For additional help, run ``west <command> -h`` (e.g. ``west init -h``).
22 .. _west-init:
29 1. Cloning a new manifest repository from a remote URL
30 2. Creating a workspace around an existing local manifest repository
[all …]
Dbasics.rst1 .. _west-basics:
9 West's built-in commands allow you to work with *projects* (Git
18 .. code-block:: none
22 │ └── config # per-workspace local configuration file
24 │ # The manifest repository, never modified by west after creation:
26 │ ├── west.yml # manifest file
33 ├── net-tools/ # .git/ project
36 .. _west-workspace:
42 Additional details are in :ref:`west-workspaces`.
47 -- it could be anything, like ``z``, ``my-zephyr-workspace``, etc.)
[all …]
Dworkspaces.rst1 .. _west-workspaces:
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
15 project. This branch points to the revision that the manifest file
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 …]
Dwest-apis.rst3 .. _west-apis:
4 .. _west-apis-west:
10 some additional APIs used by the :ref:`west extensions <west-extensions>` in
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:
38 All built-in and extension commands are implemented as subclasses of the
77 .. py:attribute:: manifest
79 A property which returns the :py:class:`west.manifest.Manifest`
80 instance for the current manifest file or aborts the program if one was
[all …]
Dtroubleshooting.rst1 .. _west-troubleshooting:
14 .. code-block:: shell
16 west -v update
21 .. code-block:: none
23 === updating your_project (path/to/your/project):
24 west.manifest: your_project: checking if cloned
25 [...other west.manifest logs...]
26 --- your_project: fetching, need revision SOME_SHA
27 …west.manifest: running 'git fetch ... https://github.com/your-username/your_project ...' in /some/…
37 ``curl -v FETCH_URL`` (for HTTPS URLs) or ``ssh -v FETCH_URL`` (for SSH URLs)
[all …]
Dextensions.rst1 .. _west-extensions:
8 for short. Extensions show up in the ``west --help`` output in a special
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
30 See :file:`zephyr/scripts/west-commands.yml` and the
37 :ref:`configuration <west-config>` option to ``false``. To set this
40 .. code-block:: console
[all …]
Dmoving-to-west.rst1 .. _moving-to-west:
6 To convert a "pre-west" Zephyr setup on your computer to west, follow these
8 instead. See :ref:`west-troubleshooting` for advice on common issues.
14 pip3 install --user -U west
18 pip3 install -U west
20 For details, see :ref:`west-install`.
38 with no spaces anywhere in the path.
40 #. Create a :ref:`west workspace <west-workspace>` using the zephyr
41 repository as a local manifest repository::
43 west init -l zephyr
Dwithout-west.rst1 .. _no-west:
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 ------------------
35 :term:`west manifest` file inside that repository.
37 .. code-block:: console
41 git clone https://github.com/zephyrproject-rtos/zephyr
50 ---------------------
[all …]
/Zephyr-Core-2.7.6/.github/workflows/
Dmanifest.yml1 name: Manifest
5 - 'west.yml'
9 runs-on: ubuntu-22.04
10 name: Manifest
12 - name: Checkout the code
15 path: zephyrproject/zephyr
17 fetch-depth: 0
18 persist-credentials: false
20 - name: Manifest
21 uses: zephyrproject-rtos/action-manifest@2f1ad2908599d4fe747f886f9d733dd7eebae4ef
[all …]
/Zephyr-Core-2.7.6/
Dwest.yml1 # The west manifest file for upstream Zephyr.
3 # The per-installation west configuration file, .west/config, sets the
4 # path to the project containing this file in the [manifest] section's
5 # "path" variable.
7 # You are free to create your own manifest files and put them in any
9 # For example, you could create a manifest file in your own out of
13 # You can pass your manifest repositories to west init when creating a
17 manifest:
22 - name: upstream
23 url-base: https://github.com/zephyrproject-rtos
[all …]
/Zephyr-Core-2.7.6/scripts/
Dzephyr_module.py5 # SPDX-License-Identifier: Apache-2.0
11 Include file is generated for Kconfig using --kconfig-out.
12 A <name>:<path> text file is generated for use with CMake using --cmake-out.
14 Using --twister-out <filename> an argument file for twister script will
26 from pathlib import Path, PurePath
50 cmake-ext:
54 kconfig-ext:
62 - type: str
86 - type: str
91 - type: str
[all …]
/Zephyr-Core-2.7.6/doc/
Dglossary.rst16 The set of user-supplied files that the Zephyr build system uses
18 It can contain application-specific code, kernel configuration settings,
25 if it does not require any board-specific capabilities.
32 fully-linked binary.
49 specified by the build system can be over-ridden by the application,
61 high-priority conditions that require interrupting the current code
65 The set of Zephyr-supplied files that implement the Zephyr kernel,
72 A multi-repo meta-tool developed for the Zephyr project. See :ref:`west`.
77 west manifest
80 additional metadata. See :ref:`west-basics` for general information
[all …]
/Zephyr-Core-2.7.6/cmake/
Dmcuboot.cmake2 # 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.
13 function(zephyr_runner_file type path)
16 set_target_properties(runners_yaml_props_target PROPERTIES "${type}_file" "${path}")
32 …ROR "Can't sign images for MCUboot: west not found. To fix, install west and ensure it's on PATH.")
51 # The user may also have a custom manifest which doesn't include
67 …x, install imgtool with pip3, or add the mcuboot repository to the west manifest and ensure it has…
72 set(west_sign ${WEST} sign --quiet --tool imgtool
73 --tool-path "${imgtool_path}"
[all …]
/Zephyr-Core-2.7.6/doc/guides/
Dmodules.rst7 order to avoid reinventing the wheel and to reuse as much well-established,
14 modules, an external project is required to have its own life-cycle outside
20 Modules to be included in the default manifest of the Zephyr project need to
29 - Debugger integration
30 - Silicon vendor Hardware Abstraction Layers (HALs)
31 - Cryptography libraries
32 - File Systems
33 - Inter-Process Communication (IPC) libraries
41 * All modules included in the default manifest shall be hosted in repositories
42 under the zephyrproject-rtos GitHub organization.
[all …]
/Zephyr-Core-2.7.6/scripts/west_commands/
Dsign.py3 # SPDX-License-Identifier: Apache-2.0
25 sys.path.append(str(ZEPHYR_SCRIPTS / 'dts' / 'python-devicetree' / 'src'))
29 binaries for chain-loading by a bootloader.
33 west sign -t your_tool -- ARGS_FOR_YOUR_TOOL
39 See tool-specific help below for details.'''
43 -------
48 west sign -t imgtool -- --key YOUR_SIGNING_KEY.pem
51 or you must pass the path to imgtool.py using the -p option.
60 "--version x.y.z+w" after "--key"). As shown above, extra arguments
61 after a '--' are passed to imgtool directly.
[all …]
/Zephyr-Core-2.7.6/scripts/west_commands/completion/
Dwest-completion.bash1 # Bash auto-completion for west subcommands and flags. To initialize, run
3 # source west-completion.bash
7 __west_previous_extglob_setting=$(shopt -p extglob)
8 shopt -s extglob
12 # bash_completion - programmable completion functions for bash 3.2+
14 # Copyright © 2006-2008, Ian Macdonald <ian@caliban.org>
15 # © 2009-2010, Bash Completion Maintainers
16 # <bash-completion-devel@lists.alioth.debian.org>
33 # http://bash-completion.alioth.debian.org/
41 # if test "${words_[cword_-1]}" = -w
[all …]
/Zephyr-Core-2.7.6/modules/trusted-firmware-m/
DCMakeLists.txt4 # SPDX-License-Identifier: Apache-2.0
6 # List of all partitions supported by TF-M
7 # Name must match name in 'trusted-firmware-m/config/config_default.cmake'
18 # Corresponds to the *_MODULE_DISABLED configs in 'trusted-firmware-m/config/config_default.cmake'
34 list(APPEND TFM_CMAKE_ARGS -DTFM_PSA_API=ON)
35 # PSA API awareness for the Non-Secure application
39 list(APPEND TFM_CMAKE_ARGS -DTEST_S=ON)
42 list(APPEND TFM_CMAKE_ARGS -DTEST_NS=ON)
45 list(APPEND TFM_CMAKE_ARGS -DBL2=TRUE)
47 list(APPEND TFM_CMAKE_ARGS -DBL2=FALSE)
[all …]
/Zephyr-Core-2.7.6/doc/application/
Dindex.rst20 The build system is application-centric, and requires Zephyr-based applications
29 application. This directory contains all application-specific files, such as
34 .. code-block:: none
47 such as board-specific kernel configuration files, the ability to run and
52 application-specific values for one or more kernel configuration options.
53 These application settings are merged with board-specific settings to produce
56 See :ref:`application-kconfig` below for more information.
59 or more application-specific files, written in C or assembly language. These
60 files are usually located in a sub-directory called :file:`src`.
65 generated in a build directory; Zephyr does not support "in-tree" builds.
[all …]
/Zephyr-Core-2.7.6/boards/xtensa/intel_adsp_cavs15/tools/
Dcavs-fw-v25.py2 # SPDX-License-Identifier: Apache-2.0
18 log = logging.getLogger("cavs-fw")
25 HUGEPAGE_FILE = "/dev/hugepages/cavs-fw-dma.tmp"
32 if os.system("lsmod | grep -q snd_sof_pci") == 0:
33 log.warning("The Linux snd-sof-pci kernel module is loaded. While this")
40 os.system("mount | grep -q hugetlbfs ||"
41 + " (mkdir -p /dev/hugepages; "
42 + " mount -t hugetlbfs hugetlbfs /dev/hugepages)")
49 log.info(f"Trimming {sz} bytes of extended manifest")
68 # of 1-8 DSP cores: lowest byte controls "stall", the second byte
[all …]
/Zephyr-Core-2.7.6/doc/releases/
Drelease-notes-2.5.rst27 * CVE-2021-3323: Under embargo until 2021-04-14
28 * CVE-2021-3321: Under embargo until 2021-04-14
29 * CVE-2021-3320: Under embargo until 2021-04-14
39 <https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aissue+is%3Aopen+label%3Abug>`_.
56 * Changed vcnl4040 dts binding default for property 'proximity-trigger'.
63 * The :c:func:`mqtt_keepalive_time_left` function now returns -1 if keep alive
67 timeout usage must use the new-style k_timeout_t type and not the
87 GPIO-only regulators a devicetree property ``supply-gpios`` is defined as a
101 * ARM Musca-A board and SoC support deprecated and planned to be removed in 2.6.0.
146 sys_heap/k_heaps. Note that the new-style heap is a general
[all …]
Drelease-notes-2.7.rst19 * :github:`issuenumber` - issue title
21 * :github:`32145` - use ``k_thread_foreach_unlocked()`` with shell callbacks
22 * :github:`56604` - drivers: nrf: rtc: make uptime consistent for app booted from v3.x mcuboot
23 * :github:`25917` - bluetooth: fix deadlock with tx of acl data and hci commands
24 * :github:`47649` - bluetooth: release att notification buffer after reconnection
25 * :github:`43718` - bluetooth: bt_conn: ensure tx buffers can be allocated within timeout
26 * :github:`60707` - canbus: isotp: seal context buffer memory leaks
27 * :github:`60904` - drivers: spi_nor: make erase operation more opportunistic
28 * :github:`61451` - drivers: can: stm32: correct timing_max parameters
29 * :github:`61501` - canbus: isotp: convert SF length check from ``ASSERT`` to runtime check
[all …]
Drelease-notes-2.6.rst13 * Added support for 64-bit ARCv3
14 * Split ARM32 and ARM64, ARM64 is now a top-level architecture
15 * Added initial support for Arm v8.1-m and Cortex-M55
22 https://github.com/zephyrproject-rtos/example-application
34 * CVE-2021-3581: Under embargo until 2021-09-04
41 <https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aissue+is%3Aopen+label%3Abug>`_.
46 * Driver APIs now return ``-ENOSYS`` if optional functions are not implemented.
47 If the feature is not supported by the hardware ``-ENOTSUP`` will be returned.
48 Formerly ``-ENOTSUP`` was returned for both failure modes, meaning this change
194 * Added support for null pointer dereferencing detection in Cortex-M.
[all …]