| /Zephyr-Core-3.4.0/ |
| D | west.yml | 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.
22 - name: upstream
23 url-base: https://github.com/zephyrproject-rtos
24 - name: babblesim
25 url-base: https://github.com/BabbleSim
27 group-filter: [-babblesim]
32 - name: bsim
33 repo-path: babblesim-manifest
[all …]
|
| D | Kconfig.zephyr | 3 # Copyright (c) 2014-2015 Wind River Systems, Inc.
6 # SPDX-License-Identifier: Apache-2.0
91 bool "Link application into /chosen/zephyr,code-partition from devicetree"
94 selected by the zephyr,code-partition property in /chosen in devicetree.
99 DT_CHOSEN_Z_CODE_PARTITION := zephyr,code-partition
102 # Only user-configurable when USE_DT_CODE_PARTITION is disabled
115 # Only user-configurable when USE_DT_CODE_PARTITION is disabled
120 If non-zero, this option specifies the size, in bytes, of the flash
135 If the application is built for chain-loading by a bootloader this
157 The templates are pre-processed by the C pre-processor to create the
[all …]
|
| /Zephyr-Core-3.4.0/doc/develop/west/ |
| D | manifest.rst | 1 .. _west-manifests:
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
48 - Projects can be added (like ``P1`` between manifest repository
52 - Project and manifest repository histories don't have to move
[all …]
|
| D | workspaces.rst | 1 .. _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
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
27 rebase it on top of a new ``manifest-rev``, or merge ``manifest-rev`` into
[all …]
|
| D | release-notes.rst | 1 .. _west-release-notes:
11 - ``west compare``: new command that compares the state of the
14 - Support for a new ``manifest.project-filter`` configuration option.
15 See :ref:`west-config-index` for details. The ``west manifest --freeze``
16 and ``west manifest --resolve`` commands currently cannot be used when
19 - Project names which contain comma (``,``) or whitespace now generate
20 warnings. These warnings are errors if the new ``manifest.project-filter``
26 - ``west forall`` now takese a ``--group`` argument that can be used
30 - All west commands will now output log messages from west API modules at
31 warning level or higher. In addition, the ``--verbose`` argument to west
[all …]
|
| D | basics.rst | 1 .. _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
25 ├── zephyr/ # .git/ repo
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.)
50 using :ref:`west init <west-init-basics>`.
[all …]
|
| /Zephyr-Core-3.4.0/.github/workflows/ |
| D | clang.yaml | 6 group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.head_ref || github.ref }}
7 cancel-in-progress: true
10 clang-build:
11 if: github.repository_owner == 'zephyrproject-rtos'
12 runs-on: zephyr-runner-linux-x64-4xlarge
14 image: ghcr.io/zephyrproject-rtos/ci:v0.26.4
15 options: '--entrypoint /bin/bash'
17 - /repo-cache/zephyrproject:/github/cache/zephyrproject
19 fail-fast: false
23 ZEPHYR_SDK_INSTALL_DIR: /opt/toolchains/zephyr-sdk-0.16.1
[all …]
|
| D | codecov.yaml | 5 - cron: '25 */3 * * 1-5'
8 group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.head_ref || github.ref }}
9 cancel-in-progress: true
13 if: github.repository == 'zephyrproject-rtos/zephyr'
14 runs-on: zephyr-runner-linux-x64-4xlarge
16 image: ghcr.io/zephyrproject-rtos/ci:v0.26.4
17 options: '--entrypoint /bin/bash'
19 - /repo-cache/zephyrproject:/github/cache/zephyrproject
21 fail-fast: false
25 ZEPHYR_SDK_INSTALL_DIR: /opt/toolchains/zephyr-sdk-0.16.1
[all …]
|
| D | twister.yaml | 6 - main
7 - v*-branch
10 - main
11 - v*-branch
14 - cron: '0 3 * * 0'
17 group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.head_ref || github.ref }}
18 cancel-in-progress: true
21 twister-build-prep:
22 if: github.repository_owner == 'zephyrproject-rtos'
23 runs-on: zephyr-runner-linux-x64-4xlarge
[all …]
|
| D | bsim-tests.yaml | 6 - ".github/workflows/bsim-tests.yaml"
7 - ".github/workflows/bsim-tests-publish.yaml"
8 - "west.yml"
9 - "subsys/bluetooth/**"
10 - "tests/bsim/**"
11 - "samples/bluetooth/**"
12 - "boards/posix/**"
13 - "soc/posix/**"
14 - "arch/posix/**"
15 - "samples/net/sockets/echo_*/**"
[all …]
|
| /Zephyr-Core-3.4.0/scripts/ |
| D | set_assignees.py | 4 # SPDX-License-Identifier: Apache-2.0
15 TOP_DIR = os.path.join(os.path.dirname(__file__))
16 sys.path.insert(0, os.path.join(TOP_DIR, "scripts"))
29 parser.add_argument("-M", "--maintainer-file", required=False, default="MAINTAINERS.yml",
31 parser.add_argument("-P", "--pull_request", required=False, default=None, type=int,
32 help="Operate on one pull-request only.")
33 parser.add_argument("-s", "--since", required=False,
34 help="Process pull-requests since date.")
36 parser.add_argument("-y", "--dry-run", action="store_true", default=False,
39 parser.add_argument("-o", "--org", default="zephyrproject-rtos",
[all …]
|
| D | zephyr_module.py | 5 # 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
28 from pathlib import Path, PurePath
52 cmake-ext:
56 kconfig-ext:
60 sysbuild-cmake:
63 sysbuild-kconfig:
66 sysbuild-cmake-ext:
[all …]
|
| /Zephyr-Core-3.4.0/scripts/footprint/ |
| D | upload_data.py | 4 # SPDX-License-Identifier: Apache-2.0
14 from git import Repo
56 parser.add_argument("-d", "--data", help="Data Directory")
57 …parser.add_argument("-y", "--dryrun", action="store_true", help="Dry run, do not upload to databas…
58 parser.add_argument("-z", "--zephyr-base", help="Zephyr tree")
59 parser.add_argument("-f", "--file", help="JSON file with footprint data")
99 repo = Repo(zephyr_base)
111 json_file = os.path.basename(file)
124 gitcommit = repo.commit(f'{commit}')
127 cidx = commit.find('-g') + 2
[all …]
|
| /Zephyr-Core-3.4.0/scripts/ci/ |
| D | test_plan.py | 2 # SPDX-License-Identifier: Apache-2.0
15 from pathlib import Path
16 from git import Repo
21 repository_path = Path(os.environ['ZEPHYR_BASE'])
24 sys.path.append(os.path.join(repository_path, 'scripts'))
53 # The glob regexes must anchor to the beginning of the path, since we
54 # return search(). (?:) is a non-capturing group.
78 def _contains(self, path): argument
79 # Returns True if the area contains 'path', and False otherwise
81 return self._match_fn and self._match_fn(path) and not \
[all …]
|
| D | check_compliance.py | 5 # SPDX-License-Identifier: Apache-2.0
12 from pathlib import Path
25 sys.path.insert(0, str(Path(__file__).resolve().parents[1]))
46 f"{cp.stdout.decode('utf-8')}\n"
48 f"{cp.stderr.decode('utf-8')}\n")
50 return cp.stdout.decode("utf-8").rstrip()
59 return git('rev-list',
60 f'--max-count={-1 if "." in refspec else 1}', refspec).split()
63 filter_arg = (f'--diff-filter={filter}',) if filter else ()
64 paths_arg = ('--', *paths) if paths else ()
[all …]
|
| /Zephyr-Core-3.4.0/boards/arm/qomu/doc/ |
| D | index.rst | 9 The Qomu board is a platform with an on-board QuickLogic EOS S3 Sensor Processing Platform.
12 .. figure:: img/qomu-board.png
21 - QuickLogic EOS S3 MCU Platform
22 - 16 Mbit of on-board flash memory
23 - Touchpads (4)
24 - RGB LED
25 - Powered from USB
43 .. zephyr-app-commands::
44 :zephyr-app: samples/boards/qomu
50 #. While the blue LED is blinking (for 5 seconds), touch the touch-pads with your finger.
[all …]
|
| /Zephyr-Core-3.4.0/doc/connectivity/bluetooth/autopts/ |
| D | autopts-win10.rst | 1 .. _autopts-win10:
19 Start -> Settings -> Update & Security -> Windows Update
28 installation directory to the PATH and disable the path length limitation.
43 Download and install `Git <https://git-scm.com/downloads>`_.
78 https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Command-Line-Tools/Download
111 .. code-block::
115 Build the auto-pts tester app
117 .. code-block::
119 west build -p auto -b nrf52840dk_nrf52840 zephyr/tests/bluetooth/tester/
123 .. code-block::
[all …]
|
| D | autopts-linux.rst | 1 .. _autopts-linux:
17 - Testing Zephyr Host Stack on QEMU
19 - Testing Zephyr Host Stack on native posix
21 - Testing Zephyr combined (controller + host) build on Real hardware (such as nRF52)
32 https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Command-Line-Tools/Download.
41 - JLink_Linux_V688a_x86_64.deb
43 - nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb
60 ---------------
64 Start -> Settings -> Update & Security -> Windows Update
67 ----------------
[all …]
|
| /Zephyr-Core-3.4.0/doc/develop/application/ |
| D | index.rst | 10 …- your **application directory**, :file:`<app>`, is something like :file:`<home>/zephyrproject/app`
11 - its **build directory** is :file:`<app>/build`
19 <important-build-vars>` is set appropriately, though.)
26 The build system is application-centric, and requires Zephyr-based applications
37 application. This directory contains all application-specific files, such as
38 application-specific configuration files and source code.
42 .. code-block:: none
56 such as board-specific configuration files, the ability to run and
60 application-specific changes which should be applied to the base devicetree
69 * **prj.conf**: This is a Kconfig fragment that specifies application-specific
[all …]
|
| /Zephyr-Core-3.4.0/doc/develop/ |
| D | beyond-GSG.rst | 1 .. _beyond-gsg:
6 The :ref:`getting_started` gives a straight-forward path to set up
11 .. _python-pip:
22 ``--user`` flag to the ``pip3`` command when installing new packages. This is
25 information about pip\ [#pip]_, including `information on -\\-user`_.
27 - On Linux, make sure ``~/.local/bin`` is at the front of your :envvar:`PATH`
28 :ref:`environment variable <env_vars>`, or programs installed with ``--user``
29 won't be found. Installing with ``--user`` avoids conflicts between pip
30 and the system package manager, and is the default on Debian-based
33 - On macOS, `Homebrew disables -\\-user`_.
[all …]
|
| /Zephyr-Core-3.4.0/doc/ |
| D | glossary.rst | 16 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,
71 high-priority conditions that require interrupting the current code
75 The set of Zephyr-supplied files that implement the Zephyr kernel,
95 A multi-repo meta-tool developed for the Zephyr project. See :ref:`west`.
103 additional metadata. See :ref:`west-basics` for general information
104 and :ref:`west-manifests` for details.
[all …]
|
| /Zephyr-Core-3.4.0/doc/contribute/documentation/ |
| D | generation.rst | 11 .. _documentation-overview:
18 using Sphinx to create a formatted stand-alone website. Developers can
36 * Doxygen-generated material used to create all API-specific documents
39 * Script-generated material for kernel configuration options based on Kconfig
51 rtd [shape="rectangle" label="read-the-docs\ntheme"]
56 images -> sphinx
57 rst -> sphinx
58 conf -> sphinx
59 header -> doxygen
60 doxygen -> xml
[all …]
|
| /Zephyr-Core-3.4.0/cmake/emu/ |
| D | qemu.cmake | 1 # SPDX-License-Identifier: Apache-2.0
23 NAMES qemu-system-${QEMU_binary_suffix}
28 qemu-system-${QEMU_binary_suffix}
32 # We need to set up uefi-run and OVMF environment
35 find_program(UEFI NAMES uefi-run REQUIRED)
41 list(APPEND UEFI -b ${OVMF_FD_PATH} -q ${QEMU})
50 set(QEMU_FLAGS -pidfile)
61 # Redirect console to a pseudo-tty, used for running automated tests.
62 list(APPEND QEMU_FLAGS -chardev pty,id=con,mux=on)
65 list(APPEND QEMU_FLAGS -chardev pipe,id=con,mux=on,path=${QEMU_PIPE})
[all …]
|
| /Zephyr-Core-3.4.0/doc/contribute/ |
| D | guidelines.rst | 6 As an open-source project, we welcome and encourage the community to submit
24 https://github.com/zephyrproject-rtos/zephyr/blob/main/LICENSE
26 .. _GitHub repo: https://github.com/zephyrproject-rtos/zephyr
29 the project's `GitHub repo`_) to strike a balance between open
38 https://www.zephyrproject.org/faqs/#1571346989065-9216c551-f523
41 https://www.whitesourcesoftware.com/whitesource-blog/top-10-apache-license-questions-answered/
64 See :ref:`external-contributions` for more information about
84 https://www.linuxfoundation.org/blog/copyright-notices-in-open-source-software-projects/
97 later in this document), the developer simply adds a ``Signed-off-by``
104 .. code-block:: none
[all …]
|
| /Zephyr-Core-3.4.0/doc/build/ |
| D | zephyr_cmake_package.rst | 6 The Zephyr `CMake package`_ is a convenient way to create a Zephyr-based application.
9 The :ref:`zephyr-app-types` section introduces the application types
13 the application, whether it is a :ref:`Zephyr repository application <zephyr-repo-app>`,
14 a :ref:`Zephyr workspace application <zephyr-workspace-app>`, or a
15 :ref:`Zephyr freestanding application <zephyr-freestanding-app>`.
17 When developing a Zephyr-based application, then a developer simply needs to write
27 .. group-tab:: Ubuntu
33 .. group-tab:: macOS
39 .. group-tab:: Windows
56 to export Zephyr using ``west zephyr-export``.
[all …]
|
