| /Zephyr-latest/.github/workflows/ |
| 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 - "boards/nordic/nrf5*/*dt*"
12 - "dts/*/nordic/**"
13 - "tests/bluetooth/common/testlib/**"
14 - "samples/bluetooth/**"
15 - "boards/native/**"
[all …]
|
| /Zephyr-latest/scripts/kconfig/ |
| D | lint.py | 4 # SPDX-License-Identifier: Apache-2.0
7 Linter for the Zephyr Kconfig files. Pass --help to see
14 Requires west, because the checks need to see Kconfig files
47 for check in checks:
51 check()
55 # args.checks is set to a list of check functions to run
62 "-n", "--check-always-n",
71 "-u", "--check-unused",
78 - Isn't referenced in Kconfig
79 - Isn't referenced as CONFIG_<NAME> outside Kconfig
[all …]
|
| /Zephyr-latest/cmake/modules/ |
| D | dts.cmake | 1 # SPDX-License-Identifier: Apache-2.0
15 # - To Zephyr and application source code files, as a C macro API
18 # - To other arbitrary Python scripts (like twister) using a
22 # - To users as a final devicetree source (DTS) file which can
25 # - To CMake files, after this module has finished running, using
28 # - To Kconfig files, both using some Kconfig symbols we generate
36 # files in scripts/dts to make all this work. We also optionally will
44 # - The pre_dt module has been included; refer to its outcome
46 # - DTS_SOURCE: set to the path to the devicetree file which
48 # - ${BINARY_DIR_INCLUDE_GENERATED}/devicetree_generated.h exists
[all …]
|
| D | extensions.cmake | 1 # SPDX-License-Identifier: Apache-2.0
14 # 1. Zephyr-aware extensions
21 # 2. Kconfig-aware extensions
23 # 3. CMake-generic extensions
44 # 1. Zephyr-aware extensions
49 # "zephyr". zephyr is a catch-all CMake library for source files that
51 # compiler flags that all zephyr source files use.
52 # [0] https://cmake.org/cmake/help/latest/manual/cmake-buildsystem.7.html
66 # As a very high-level introduction here are two call graphs that are
72 # zephyr_library_compile_options() --> target_compile_options()
[all …]
|
| /Zephyr-latest/doc/develop/test/twister/ |
| D | twister_blackbox.rst | 7 to understand existing files and create their own. All developers should fix any tests
21 call twister as user would and check the results.
35 .. code-block:: console
37 twister -i --outdir $OUTDIR -T $TEST_DATA/tests -y --level $LEVEL
38 --test-config $TEST_DATA/test_config.yaml -p qemu_x86 -p frdm_k64f
40 It presumes a CLI with the ``zephyr-env.sh`` or ``zephyr-env.cmd`` already run.
45 We can check the standard output or stderr in ``out`` and ``err`` variables.
48 ``twister-out`` directories. Most of the time, we will use the ``out_path`` fixture in conjunction
49 with ``--outdir`` flag (L52) to keep test-generated files in temporary directories.
50 Typical files read in blackbox tests are ``testplan.json`` , ``twister.xml`` and ``twister.log`` .
[all …]
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | tips.rst | 3 Kconfig - Tips and Best Practices
11 The official Kconfig documentation is `kconfig-language.rst
12 <https://www.kernel.org/doc/html/latest/kbuild/kconfig-language.html>`__
13 and `kconfig-macro-language.rst
14 <https://www.kernel.org/doc/html/latest/kbuild/kconfig-macro-language.html>`__.
29 :ref:`menuconfig`), or by manually editing configuration files. Conversely, a
31 manually editing configuration files.
54 a fixed machine-specific setting. Usually, such settings should be handled via
55 :ref:`devicetree <dt-guide>` instead.
64 controlled by. See :ref:`dt-drivers-that-depend` for alternatives.
[all …]
|
| D | setting.rst | 11 <kconfig-search>`.
15 Before making changes to Kconfig files, it's a good idea to also go through
25 - A visible symbol is a symbol defined with a prompt. Visible symbols show
27 set in configuration files.
31 .. code-block:: kconfig
39 .. code-block:: none
43 - An *invisible* symbol is a symbol without a prompt. Invisible symbols are
50 .. code-block:: kconfig
61 Setting symbols in configuration files
64 Visible symbols can be configured by setting them in configuration files. The
[all …]
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | soc_porting.rst | 18 - SoC: the exact system on a chip the board's CPU is part of.
19 - SoC series: a group of tightly related SoCs.
20 - SoC family: a wider group of SoCs with similar characteristics.
21 - CPU Cluster: a cluster of one or more CPU cores.
22 - CPU core: a particular CPU instance of a given architecture.
23 - Architecture: an instruction set architecture.
35 and check that it's not already in use. In some cases someone else may have
39 in Zephyr, for example ``./scripts/list_hardware.py --soc-root=. --socs`` from
48 structure under ``<your-repo>/soc`` is permitted.
50 :zephyr_file:`dts/bindings/vendor-prefixes.txt`. If the SoC vendor does not
[all …]
|
| D | board_porting.rst | 7 directory* with various files in it. Files in the board directory inherit
21 - Support for multi-core, multi-arch AMP (Asymmetrical Multi Processing) SoCs
22 - Support for multi-SoC boards
23 - Support for reusing the SoC and board Kconfig trees outside of the Zephyr
25 - Support for advanced use cases with :ref:`sysbuild`
26 - Removal of all existing arbitrary and inconsistent uses of Kconfig and folder
38 Some non-critical features, enhancements and improvements of the new hardware
39 model are still in development. Check the
47 with two options if they have an out-of-tree board (or SoC):
49 #. Convert the out-of-tree board to the current hardware model (recommended)
[all …]
|
| /Zephyr-latest/tests/subsys/fs/littlefs/src/ |
| D | test_lfs_basic.c | 4 * SPDX-License-Identifier: Apache-2.0
29 TC_PRINT("mounting %s\n", mp->mnt_point); in mount()
39 TC_PRINT("clearing partition %s\n", mp->mnt_point); in clear_partition()
52 TC_PRINT("checking clean statvfs of %s\n", mp->mnt_point); in clean_statvfs()
54 zassert_equal(fs_statvfs(mp->mnt_point, &stat), 0, in clean_statvfs()
58 mp->mnt_point, in clean_statvfs()
66 zassert_equal(stat.f_bfree, stat.f_blocks - 2U, in clean_statvfs()
83 zassert_equal(fs_statvfs(mp->mnt_point, &stat), 0, in check_medium()
87 mp->mnt_point, in check_medium()
95 zassert_equal(stat.f_bfree, stat.f_blocks - 2U, in check_medium()
[all …]
|
| /Zephyr-latest/scripts/utils/ |
| D | pinctrl_nrf_migrate.py | 4 # SPDX-License-Identifier: Apache-2.0
10 This script can be used to automatically migrate the Devicetree files of
11 nRF-based boards using the old <signal>-pin properties to select peripheral
13 file by removing old pin-related properties replacing them with pinctrl states.
14 A board-pinctrl.dtsi file will be generated containing the configuration for
15 all pinctrl states. Note that script will also work on files that have been
20 Devicetree files will be converted correctly. **ADJUSTED/GENERATED FILES
28 -i path/to/board.dts
29 [--no-backup]
30 [--skip-nrf-check]
[all …]
|
| /Zephyr-latest/doc/develop/west/ |
| D | basics.rst | 1 .. _west-basics:
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.
24 .. code-block:: none
28 │ └── config # per-workspace local configuration file
33 │ └── [... other files ...]
40 │ └── net-tools/ # .git/ project
43 .. _west-workspace:
49 Additional details are in :ref:`west-workspaces`.
54 -- it could be anything, like ``z``, ``my-zephyr-workspace``, etc.)
[all …]
|
| /Zephyr-latest/samples/basic/button/ |
| D | README.rst | 1 .. zephyr:code-sample:: button
3 :relevant-api: gpio_interface
14 debouncing, check out :ref:`input` and :zephyr:code-sample:`input-dump`
23 The button must be configured using the ``sw0`` :ref:`devicetree <dt-guide>`
24 alias, usually in the :ref:`BOARD.dts file <devicetree-in-out-files>`. You will
27 .. code-block:: none
35 the same alias used by the :zephyr:code-sample:`blinky` sample. If this is provided, the LED
48 .. code-block:: devicetree
58 gpio-controller;
59 #gpio-cells = <2>;
[all …]
|
| /Zephyr-latest/doc/build/dts/ |
| D | howtos.rst | 1 .. _dt-howtos:
6 This page has step-by-step advice for getting things done with devicetree.
8 .. tip:: See :ref:`dt-trouble` for troubleshooting advice.
10 .. _get-devicetree-outputs:
15 A board's devicetree (:ref:`BOARD.dts <devicetree-in-out-files>`) pulls in
16 common node definitions via ``#include`` preprocessor directives. This at least
18 is by opening these files, e.g. by looking in
26 You can build :zephyr:code-sample:`hello_world` to see the "base" devicetree for your board
27 without any additional changes from :ref:`overlay files <dt-input-files>`.
30 :zephyr:code-sample:`hello_world`:
[all …]
|
| D | bindings-syntax.rst | 1 .. _dt-bindings-file-syntax:
7 files are YAML files. A :ref:`simple example <dt-bindings-simple-example>` was
17 The top level of a bindings file maps keys to values. The top-level keys look
20 .. code-block:: yaml
24 This is the Vendomatic company's foo-device.
29 See https://yaml-multiline.info/ for formatting help.
35 compatible: "manufacturer,foo-device"
41 child-binding:
50 # SPI memory chip, use 'on-bus:' to say what type of bus, like this.
53 on-bus: spi
[all …]
|
| /Zephyr-latest/ |
| D | MAINTAINERS.yml | 35 # files:
36 # List of paths and/or glob patterns giving the files in the area,
39 # If a path or glob pattern ends in a '/', it matches all files within
45 # files-regex:
50 # Can be combined with a 'files' key.
52 # Note: Prefer plain 'files' patterns where possible. get_maintainer.py
53 # will check that they match some file, but won't check regexes
56 # files-exclude:
57 # Like 'files', but any matching files will be excluded from the area.
59 # files-regex-exclude:
[all …]
|
| /Zephyr-latest/soc/ |
| D | CMakeLists.txt | 1 # SPDX-License-Identifier: Apache-2.0
3 # FIXME: SHADOW_VARS: Remove this once we have enabled -Wshadow globally.
5 # Limit warning of shadow variables to in-tree SoC files for now.
12 add_subdirectory(common)
16 ---------------------------------------------------------------------
17 --- WARNING: Functionality to describe SoCs in HWMv1 is ---
18 --- deprecated and should be replaced with HWMv2, including ---
19 --- boards. HWMv1 SoCs support remains only to ease the migration ---
20 --- of out-of-tree SoCs and associated boards. It will not be ---
21 --- possible to build using HWMv1 SoCs at all in future releases. ---
[all …]
|
| /Zephyr-latest/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
31 The main zephyr repository contains Zephyr's source code, configuration files,
36 The files in the **application directory** link Zephyr and any modules with the
37 application. This directory contains all application-specific files, such as
38 application-specific configuration files and source code.
40 Here are the files in a simple Zephyr application:
42 .. code-block:: none
[all …]
|
| /Zephyr-latest/doc/contribute/documentation/ |
| D | guidelines.rst | 15 view this content either in its raw form as .rst markup files, or (with
24 .. _Sphinx extensions: http://www.sphinx-doc.org/en/stable/contents.html
26 .. _Sphinx Inline Markup: http://sphinx-doc.org/markup/inline.html#inline-markup
30 Sphinx-defined directives and roles used to create the documentation
42 the first non-white space in the preceding line. For example::
50 .. code-block::
66 * Third section heading level (h4) use ``-``
84 For bullet lists, place an asterisk (``*``) or hyphen (``-``) at
113 #. This is a second-level list under the first item (also
143 Multi-column lists
[all …]
|
| /Zephyr-latest/share/zephyr-package/cmake/ |
| D | ZephyrConfig.cmake | 1 # SPDX-License-Identifier: Apache-2.0
5 # The purpose of this files is to allow users to decide if they want to:
6 # - Use ZEPHYR_BASE environment setting for explicitly set select a zephyr installation
7 # - Support automatic Zephyr installation lookup through the use of find_package(ZEPHYR)
9 # First check to see if user has provided a Zephyr base manually.
29 set(Zephyr_DIR ${ZEPHYR_BASE}/share/zephyr-package/cmake CACHE PATH
61 # The module messages are intentionally higher than STATUS to avoid the -- prefix
132 …means this Zephyr is likely the correct one, but there could be an alternative installed along-side
133 # Thus, check if there is an even better candidate.
134 # This check works the following way.
[all …]
|
| /Zephyr-latest/include/zephyr/toolchain/ |
| D | common.h | 2 * Copyright (c) 2010-2014 Wind River Systems, Inc.
4 * SPDX-License-Identifier: Apache-2.0
11 #error Please do not include toolchain-specific headers directly, use <zephyr/toolchain.h> instead
16 * @brief Common toolchain abstraction
18 * Macros to abstract compiler capabilities (common to all toolchains).
28 /* Use TASK_ENTRY_CPP to tag task entry points defined in C++ files. */
115 * even ignoring -fno-inline. So for code coverage, do not
144 * until https://github.com/zephyrproject-rtos/zephyr/issues/5006 is
145 * fixed via possibly #4174, we introduce this hack -- which will
169 /* Compile-time assertion that makes the build to fail.
[all …]
|
| /Zephyr-latest/samples/subsys/mgmt/updatehub/ |
| D | README.rst | 1 .. zephyr:code-sample:: updatehub-fota
2 :name: UpdateHub embedded Firmware Over-The-Air (FOTA) update
3 :relevant-api: updatehub
5 Perform Firmware Over-The-Air (FOTA) updates using UpdateHub.
10 UpdateHub is an enterprise-grade solution which makes it simple to remotely
12 Firmware Over-the-Air (FOTA) updates with maximum security and efficiency,
33 :zephyr:board:`Freedom-K64F <frdm_k64f>` kit using the ethernet connectivity. The
36 * The sample provides overlay files to enable other technologies like WIFI,
52 Zephyr sub-systems and it uses CoAP over UDP.
60 directory. This allows to construct and run everything from a common place.
[all …]
|
| /Zephyr-latest/tests/subsys/fs/ext2/src/ |
| D | testfs_mount.c | 4 * SPDX-License-Identifier: Apache-2.0
18 mp->flags |= FS_MOUNT_FLAG_NO_FORMAT; in ZTEST()
23 /* Test FS_MOUNT_FLAG_READ_ONLY on non-formatted volume*/ in ZTEST()
24 mp->flags = FS_MOUNT_FLAG_READ_ONLY; in ZTEST()
29 /* Format volume and add some files/dirs to check read-only flag */ in ZTEST()
30 mp->flags = 0; in ZTEST()
39 /* Check fs operation on volume mounted with FS_MOUNT_FLAG_READ_ONLY */ in ZTEST()
40 mp->flags = FS_MOUNT_FLAG_READ_ONLY; in ZTEST()
41 TC_PRINT("Mount as read-only\n"); in ZTEST()
54 size_t partition_size = MIN(0x800000, get_partition_size((uintptr_t)mp->storage_dev)); in ZTEST()
[all …]
|
| /Zephyr-latest/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
34 this, check out articles such as `Why choose Apache 2.0 licensing`_ and
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-latest/drivers/gpio/ |
| D | gpio_rt1718s.c | 4 * SPDX-License-Identifier: Apache-2.0
8 * @file File that collects common data and configs for RS1718S chip. The file
9 * doesn't provide any API itself. The feature-specific API should be provided
10 * in separated files e.g. GPIO API.
33 k_work_submit(&data->alert_worker); in rt1718s_alert_callback()
39 const struct device *const dev = data->dev; in rt1718s_alert_worker()
40 const struct rt1718s_config *const config = dev->config; in rt1718s_alert_worker()
45 k_sem_take(&data->lock_tcpci, K_FOREVER); in rt1718s_alert_worker()
50 k_sem_give(&data->lock_tcpci); in rt1718s_alert_worker()
56 * defined by the TCPCI specification - "A masked in rt1718s_alert_worker()
[all …]
|
