Searched +full:extra +full:- +full:user +full:- +full:files (Results 1 – 25 of 77) sorted by relevance
1234
| /Zephyr-latest/scripts/schemas/ |
| D | build-schema.yml | 1 # SPDX-License-Identifier: Apache-2.0
18 source-dir:
20 configuration-dir:
35 - type: str
39 files:
42 - type: str
43 user-files:
46 - type: str
47 extra-user-files:
50 - type: str
[all …]
|
| /Zephyr-latest/ |
| D | .gitlint | 2 # Zephyr-specific defaults are located in scripts/gitlint/zephyr_commit_rules.py
4 ignore=title-trailing-punctuation, T3, title-max-length, T1, body-hard-tab, B3, B1
5 # verbosity should be a value between 1 and 3, the commandline -v flags take precedence over this
8 ignore-merge-commits=false
9 ignore-revert-commits=false
10 ignore-fixup-commits=false
11 ignore-squash-commits=false
15 # Set the extra-path where gitlint will search for user defined rules
17 extra-path=scripts/gitlint
19 [title-max-length-no-revert]
[all …]
|
| D | Kconfig.zephyr | 3 # Copyright (c) 2014-2015 Wind River Systems, Inc.
6 # SPDX-License-Identifier: Apache-2.0
12 # Include Kconfig.defconfig files first so that they can override defaults and
13 # other symbol/choice properties by adding extra symbol/choice definitions.
92 bool "Link application into /chosen/zephyr,code-partition from devicetree"
95 selected by the zephyr,code-partition property in /chosen in devicetree.
100 DT_CHOSEN_Z_CODE_PARTITION := zephyr,code-partition
103 # Only user-configurable when USE_DT_CODE_PARTITION is disabled
116 # Only user-configurable when USE_DT_CODE_PARTITION is disabled
121 If non-zero, this option specifies the size, in bytes, of the flash
[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 | kconfig.cmake | 1 # SPDX-License-Identifier: Apache-2.0
13 # Re-configure (Re-execute all CMakeLists.txt code) when autoconf.h changes
16 # Folders needed for conf/mconf files (kconfig has no method of redirecting all output files).
17 # conf/mconf needs to be run from a different directory because of: GH-3408
77 build_info(kconfig user-files PATH ${CONF_FILE_AS_LIST})
83 build_info(kconfig extra-user-files PATH ${EXTRA_CONF_FILE_AS_LIST})
90 # character in the C shell, so we make it into a question-mark
95 # This allows Kconfig files to refer relative from a modules root as:
156 # glob-sources all arch roots, but for Zephyr itself, the current approach is
163 # Allow out-of-tree users to add their own Kconfig python frontend
[all …]
|
| /Zephyr-latest/scripts/ |
| D | twister | 4 # SPDX-License-Identifier: Apache-2.0
7 Also check the "User and Developer Guides" at https://docs.zephyrproject.org/
16 files in the application's project directory. This file may contain one or more
19 that testsuite meta-data. The full canonical name for each test case is <path to
34 Don't build or run this test case unless --enable-slow was passed
35 in on the command line. Intended for time-consuming test cases
39 extra_args: <list of extra arguments>
40 Extra cache entries to pass to CMake when building or running the
43 extra_configs: <list of extra configurations>
44 Extra configuration options to be merged with a master prj.conf
[all …]
|
| D | set_assignees.py | 4 # SPDX-License-Identifier: Apache-2.0
31 parser.add_argument("-M", "--maintainer-file", required=False, default="MAINTAINERS.yml",
35 group.add_argument("-P", "--pull_request", required=False, default=None, type=int,
36 help="Operate on one pull-request only.")
37 group.add_argument("-I", "--issue", required=False, default=None, type=int,
39 group.add_argument("-s", "--since", required=False,
40 help="Process pull-requests since date.")
41 group.add_argument("-m", "--modules", action="store_true",
42 help="Process pull-requests from modules.")
44 parser.add_argument("-y", "--dry-run", action="store_true", default=False,
[all …]
|
| /Zephyr-latest/scripts/native_simulator/ |
| D | Makefile | 2 # SPDX-License-Identifier: Apache-2.0
8 # By default all the build output is placed under the _build folder, but the user can override it
12 # See "Configurable/user overridible variables" below.
18 -include ${NSI_CONFIG_FILE}
22 # Configurable/user overridible variables:
35 NSI_ARCH?=-m32
37 NSI_COVERAGE?=--coverage
43 # Extra source files to be built in the runner context
45 # Extra include directories to be used while building in the runner context
47 # Extra libraries to be linked to the final executable
[all …]
|
| /Zephyr-latest/doc/services/llext/ |
| D | config.rst | 9 ----------
20 When :ref:`user mode <usermode_api>` is enabled, the heap size must be
27 ---------------
34 Build and expect relocatable files as binary object type for the LLEXT
40 Build and expect relocatable (partially linked) files as the binary
41 object type for the LLEXT subsystem. These object files are generated
42 by the linker by combining multiple object files into a single one.
48 library from multiple object files.
57 --------------------
87 <https://github.com/zephyrproject-rtos/zephyr/issues/75341>`_.
[all …]
|
| /Zephyr-latest/doc/develop/sca/ |
| D | codechecker.rst | 8 `Clang-Tidy <http://clang.llvm.org/extra/clang-tidy/>`__,
9 `Clang Static Analyzer <http://clang-analyzer.llvm.org/>`__ and
18 .. code-block:: shell
25 To run CodeChecker, :ref:`west build <west-building>` should be
26 called with a ``-DZEPHYR_SCA_VARIANT=codechecker`` parameter, e.g.
28 .. code-block:: shell
30 west build -b mimxrt1064_evk samples/basic/blinky -- -DZEPHYR_SCA_VARIANT=codechecker
39 .. list-table::
40 :header-rows: 1
42 * - Parameter
[all …]
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | overview.rst | 9 User mode threads are considered to be untrusted by Zephyr and are therefore
10 isolated from other user mode threads and from the kernel. A flawed or
11 malicious user mode thread cannot leak or modify the private data/resources
13 control another user mode thread or the kernel.
15 Example use-cases of Zephyr's user mode features:
17 - The kernel can protect against many unintentional programming errors which
20 - The kernel can sandbox complex data parsers such as interpreters, network
21 protocols, and filesystems such that malicious third-party code or data
24 - The kernel can support the notion of multiple logical "applications", each
31 For threads running in a non-privileged CPU state (hereafter referred to as
[all …]
|
| D | memory_domain.rst | 24 - Any configuration of memory regions which need to have special caching or
25 write-back policies for basic hardware and driver function. Note that most
29 to maximize the number of available MPU regions for the end user. On
30 ARMv7-M/ARMv8-M this is called the System Address Map, other CPUs may
34 - A read-only, executable region or regions for program text and ro-data, that
35 is accessible to user mode. This could be further sub-divided into a
36 read-only region for ro-data, and a read-only, executable region for text, but
38 threads running in user mode can read ro-data and fetch instructions.
40 - Depending on configuration, user-accessible read-write regions to support
41 extra features like GCOV, HEP, etc.
[all …]
|
| /Zephyr-latest/subsys/testsuite/ |
| D | Kconfig | 2 # SPDX-License-Identifier: Apache-2.0
18 int "Test function extra thread stack size"
38 This option will build your application with the -coverage option
53 Build natively with the compiler standard `--coverage` options,
54 that is with gcov/GCC-compatible coverage
70 gen_gcov_files.py which creates the required .gcda files. These
101 bool "Indicate that this test exercises user mode"
103 This option indicates that a test case puts threads in user mode,
106 a per-test basis and is not meant to be used outside test cases.
110 The userspace APIs are no-ops if userspace is not enabled, so it is
[all …]
|
| /Zephyr-latest/scripts/kconfig/ |
| D | kconfig.py | 3 # Copyright (c) 2018-2023 Nordic Semiconductor ASA and Ulf Magnusson
7 # SPDX-License-Identifier: ISC
10 # files passed as arguments, e.g. board *_defconfig and application prj.conf
11 # files.
14 # output, which just updates it. This is handled in the CMake files.
51 # fragments, to avoid warnings-turned-errors when using an old
52 # configuration file together with updated Kconfig files
65 # Only if user has modified to a value that gets overruled by the forced
69 # Load files
86 # when using an old configuration and updating Kconfig files.
[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>`__.
27 If a symbol has a prompt (e.g. ``bool "Enable foo"``), then the user can change
29 :ref:`menuconfig`), or by manually editing configuration files. Conversely, a
30 symbol without a prompt can never be changed directly by the user, not even by
31 manually editing configuration files.
33 Only put a prompt on a symbol if it makes sense for the user to change its
[all …]
|
| /Zephyr-latest/cmake/compiler/ |
| D | compiler_flags_template.cmake | 27 # GCC options for warning levels 1, 2, 3, when using `-DW=[1|2|3]`
28 # Property for warning levels 1, 2, 3 in Zephyr when using `-DW=[1|2|3]`
48 # Compiler flags for C standard. The specific standard must be appended by user.
49 # For example, gcc specifies this as: set_compiler_property(PROPERTY cstd -std=)
58 set_property(TARGET compiler-cpp PROPERTY nostdincxx)
61 set_property(TARGET compiler-cpp PROPERTY required)
64 set_property(TARGET compiler-cpp PROPERTY dialect_cpp98)
65 set_property(TARGET compiler-cpp PROPERTY dialect_cpp11)
66 set_property(TARGET compiler-cpp PROPERTY dialect_cpp14)
67 set_property(TARGET compiler-cpp PROPERTY dialect_cpp17)
[all …]
|
| /Zephyr-latest/doc/hardware/porting/ |
| 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
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)
57 can then use the `example-application conversion Pull Request`_ as an example on
[all …]
|
| /Zephyr-latest/doc/ |
| D | zephyr.doxyfile.in | 20 # doxygen -x [configFile]
24 # doxygen -x_noenv [configFile]
26 #---------------------------------------------------------------------------
28 #---------------------------------------------------------------------------
31 # file that follow. The default is UTF-8 which is also the encoding used for all
35 # The default value is: UTF-8.
37 DOXYFILE_ENCODING = UTF-8
40 # double-quotes, unless you are using Doxywizard) that should identify the
80 # sub-directories (in 2 levels) under the output directory of each output format
81 # and will distribute the generated files over these directories. Enabling this
[all …]
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 6 Sysbuild is a higher-level build system that can be used to combine multiple
7 other build systems together. It is a higher-level layer that combines one
27 Single-image build
31 Multi-image build
39 Multi-domain
45 This figure is an overview of sysbuild's inputs, outputs, and user interfaces:
50 :figclass: align-center
55 - You can run sysbuild either with :ref:`west build
56 <west-building>` or directly via ``cmake``.
58 - You can use sysbuild to generate application images from each build system,
[all …]
|
| /Zephyr-latest/boards/arduino/mkrzero/doc/ |
| D | index.rst | 7 This board come with microSD card holder that allows you to play with music files with no extra har…
12 - ATSAMD21G18A ARM Cortex-M0+ processor at 48 MHz
13 - 32.768 kHz crystal oscillator
14 - 256 KiB flash memory and 32 KiB of RAM
15 - One user LEDs
16 - One reset button
17 - microSD card slot
18 - ATECC508A secure element
23 .. zephyr:board-supported-hw::
35 with the on-chip PLL generating the 48 MHz system clock. The internal
[all …]
|
| /Zephyr-latest/arch/ |
| D | Kconfig | 3 # Copyright (c) 2014-2015 Wind River Systems, Inc.
6 # SPDX-License-Identifier: Apache-2.0
18 # Should be 'select'ed by low-level symbols like SOC_SERIES_* or, lacking that,
37 # is really only necessary for Cortex-M with ARM MPU!
173 symbols above. See the top-level CMakeLists.txt.
180 module-str = arch
186 This option tells the build system that the target system is big-endian.
187 Little-endian architecture is the default and should leave this option
189 soc/**/Kconfig, or boards/**/Kconfig and the user should generally avoid
195 # Hidden Kconfig option representing the default little-endian architecture
[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/build/cmake/ |
| D | index.rst | 1 .. _cmake-details:
32 .. code-block:: cmake
46 When introducing build system code using CMake or adding new CMake files,
47 please follow the style guidelines outlined :ref:`here <cmake-style>`.
59 -------------------
61 The configuration phase begins when the user invokes *CMake* to generate a
64 .. figure:: build-config-phase.svg
67 :figclass: align-center
72 top-level directory, which in turn refers to :file:`CMakeLists.txt` files
74 set of Makefiles or Ninja files to drive the build process, but the CMake
[all …]
|
| /Zephyr-latest/cmake/compiler/arcmwdt/ |
| D | compiler_flags.cmake | 3 -Werror=implicit-int
4 -Wold-style-definition
14 set_compiler_property(PROPERTY no_optimization -O0)
15 set_compiler_property(PROPERTY optimization_debug -O0)
16 set_compiler_property(PROPERTY optimization_speed -O2)
17 set_compiler_property(PROPERTY optimization_size -Os)
18 set_compiler_property(PROPERTY optimization_fast -O3)
27 -Wformat
28 -Wformat-security
29 -Wno-format-zero-length
[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
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`:
32 .. code-block:: sh
[all …]
|
1234
