Home
last modified time | relevance | path

Searched +full:user +full:- +full:files (Results 1 – 25 of 325) sorted by relevance

12345678910>>...13

/Zephyr-latest/scripts/schemas/
Dbuild-schema.yml1 # 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/subsys/logging/backends/
DKconfig.fs2 # SPDX-License-Identifier: Apache-2.0
11 either configured for auto-mount or manually mounted by the application.
17 backend-str = fs
28 bool "Old log files overwrite"
31 When enabled backend overwrites oldest log files.
46 User defined name of log files saved in the file system.
53 Directory to which log files will be written.
56 int "User defined log file size"
63 int "Max number of files containing logs"
66 Limit of number of files with logs. It is also limited by
/Zephyr-latest/cmake/modules/
Duser_cache.cmake1 # SPDX-License-Identifier: Apache-2.0
5 # Configure user cache directory.
7 # The user cache can be used for caching of data that should be persistent
11 # Only data that can be safely re-generated should be placed in this cache.
13 # Zephyr build system uses this user cache to store Zephyr compiler check
15 # See https://github.com/zephyrproject-rtos/zephyr/pull/7102 for details.
20 # - USER_CACHE_DIR: User cache directory in use.
26 # use only and may be removed, renamed, or re-purposed without prior notice.
69 # The directory is write-able
80 # files. Prefer a directory outside of the git repository because it
[all …]
Dshields.cmake1 # SPDX-License-Identifier: Apache-2.0
14 # - shield_conf_files: List of shield-specific Kconfig fragments
15 # - shield_dts_files : List of shield-specific devicetree files
16 # - SHIELD_AS_LIST : A CMake list of shields created from the SHIELD variable.
17 # - SHIELD_DIRS : A CMake list of directories which contain shield definitions
20 # - shields: when invoked, a list of valid shields will be printed
26 # - BOARD_ROOT: CMake list of board roots containing board implementations
29 # use only, and may be removed, renamed, or re-purposed without prior notice.
45 # SHIELD-NOTFOUND is a real CMake list, from which valid shields can be popped.
47 set(SHIELD-NOTFOUND ${SHIELD_AS_LIST})
[all …]
Ddts.cmake1 # 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 …]
Dconfiguration_files.cmake1 # SPDX-License-Identifier: Apache-2.0
5 # Zephyr build system configuration files.
7 # Locate the Kconfig and DT config files that are to be used.
13 # - CONF_FILE: List of Kconfig fragments
14 # - EXTRA_CONF_FILE: List of additional Kconfig fragments
15 # - DTC_OVERLAY_FILE: List of devicetree overlay files
16 # - EXTRA_DTC_OVERLAY_FILE List of additional devicetree overlay files
17 # - DTS_EXTRA_CPPFLAGS List of additional devicetree preprocessor defines
18 # - APPLICATION_CONFIG_DIR: Root folder for application configuration
24 # use only and may be removed, renamed, or re-purposed without prior notice.
[all …]
Dkconfig.cmake1 # 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 …]
Dpre_dt.cmake1 # SPDX-License-Identifier: Apache-2.0
9 # DTS files, bindings, and vendor prefixes are.
14 # - DTS_ROOT: a deduplicated list of places where devicetree
15 # implementation files (like bindings, vendor prefixes, etc.) are
17 # - DTS_ROOT_SYSTEM_INCLUDE_DIRS: set to "PATH1 PATH2 ...",
19 # may be found for devicetree files
25 # - APPLICATION_SOURCE_DIR: path to app (added to DTS_ROOT)
26 # - BOARD_DIR: directory containing the board definition (added to DTS_ROOT)
27 # - DTS_ROOT: initial contents may be populated here
28 # - ZEPHYR_BASE: path to zephyr repository (added to DTS_ROOT)
[all …]
/Zephyr-latest/soc/aspeed/ast10x0/
DKconfig1 # SPDX-License-Identifier: Apache-2.0
22 The non-cached SRAM size in kB. The default value comes from reg[1]
23 of /chosen/zephyr,sram in devicetree. The user should generally avoid
24 changing it via menuconfig or in configuration files.
29 The non-cached SRAM base address. The default value comes from
30 reg[1] of /chosen/zephyr,sram in devicetree. The user should
31 generally avoid changing it via menuconfig or in configuration files.
/Zephyr-latest/.github/workflows/
Dbsim-tests.yaml6 - ".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/boards/shields/eval_ad4052_ardz/doc/
Dindex.rst3 EVAL-AD4052-ARDZ
9 The EVAL-AD4052-ARDZ is a 16-Bit SAR ADC Arduino shield powered
15 Set ``--shield eval_ad4052_ardz`` when you invoke ``west build``. For example:
17 .. zephyr-app-commands::
18 :zephyr-app: samples/drivers/adc/
33 - `EVAL-AD4052-ARDZ product page`_
34 - `EVAL-AD4052-ARDZ user guide`_
35 - `EVAL-AD4052-ARDZ schematic`_
36 - `AD4052 product page`_
37 - `AD4052 data sheet`_
[all …]
/Zephyr-latest/boards/nuvoton/numaker_pfm_m467/doc/
Dindex.rst7 specially developed by Nuvoton. The PFM-M467 is based on the NuMicro® M467
8 Ethernet series MCU with ARM® -Cortex®-M4F core.
12 - 32-bit Arm Cortex®-M4 M467HJHAE MCU
13 - Core clock up to 200 MHz
14 - 1024 KB embedded Dual Bank Flash and 512 KB SRAM
15 - Ethernet (IP101GR) for network application
16 - USB 2.0 High-Speed OTG / Host / Device
17 - USB 1.1 Full-Speed OTG / Host / Device
18 - External SPI Flash (Winbond W25Q20) which can be regarded as ROM module
19 - MicroSD Card slot for T-Flash
[all …]
/Zephyr-latest/boards/nuvoton/numaker_pfm_m487/doc/
Dindex.rst7 specially developed by Nuvoton. The PFM-M487 is based on the NuMicro® M487
8 Ethernet series MCU with ARM® -Cortex®-M4F core.
12 - 32-bit Arm Cortex®-M4 M487JIDAE MCU
13 - Core clock up to 192 MHz
14 - 512 KB embedded Dual Bank Flash and 160 KB SRAM
15 - Audio codec (NAU88L25) with Microphone In and Headphone Out
16 - Ethernet (IP101GR) for network application
17 - USB 2.0 High-Speed OTG / Host / Device
18 - USB 1.1 Full-Speed OTG / Host / Device
19 - External SPI Flash (Winbond W25Q20) which can be regarded as ROM module
[all …]
/Zephyr-latest/doc/develop/west/
Dzephyr-cmds.rst1 .. _west-zephyr-ext-cmds:
6 This page documents miscellaneous :ref:`west-zephyr-extensions`.
8 .. _west-boards:
21 specify the display format yourself you can use the ``--format`` (or ``-f``)
24 west boards -f "{arch}:{name}"
28 west boards -h
30 .. _west-completion:
40 - bash
41 - zsh
42 - fish
[all …]
/Zephyr-latest/boards/atmel/sam/sam4s_xplained/doc/
Dindex.rst12 - ATSAM4S16C ARM Cortex-M4 Processor
13 - 12 MHz crystal oscillator
14 - internal 32.768 kHz crystal oscillator
15 - IS66WV51216DALL 8 Mb SRAM
16 - Micro-AB USB device
17 - Micro-AB USB debug interface supporting SEGGER OB and Virtual COM Port and
19 - One reset and one user pushbutton
20 - 2 yellow user LEDs
21 - IC pads for external flash chip
26 .. zephyr:board-supported-hw::
[all …]
/Zephyr-latest/samples/tfm_integration/tfm_secure_partition/
DREADME.rst1 .. zephyr:code-sample:: tfm_secure_partition
2 :name: TF-M Secure Partition
9 A Secure Partition is an isolated module that resides in TF-M. It exposes a number of functions or
10 "secure services" to other partitions and/or to the non-secure firmware. TF-M already contains
14 This sample creates a dummy secure partition and secure service for TF-M and instructs the TF-M
16 main file (in the non-secure firmware).
22 build files and build configuration files. The partition is built by the TF-M build system, refer to
25 For more information on how to add custom secure partitions refer to TF-M's guide:
26 https://tf-m-user-guide.trustedfirmware.org/integration_guide/services/tfm_secure_partition_additio…
30 both the secure and non-secure CMakeLists.txt file and make relevant changes, as well as the yaml
[all …]
/Zephyr-latest/boards/espressif/esp8684_devkitm/doc/
Dindex.rst6 The ESP8684-DevKitM is an entry-level development board based on ESP8684-MINI-1, a general-purpose
7 module with 1 MB/2 MB/4 MB SPI flash. This board integrates complete Wi-Fi and Bluetooth LE functio…
8 For more information, check `ESP8684-DevKitM User Guide`_
13 ESP32-C2 (ESP8684 core) is a low-cost, Wi-Fi 4 & Bluetooth 5 (LE) chip. Its unique design
14 makes the chip smaller and yet more powerful than ESP8266. ESP32-C2 is built around a RISC-V
15 32-bit, single-core processor, with 272 KB of SRAM (16 KB dedicated to cache) and 576 KB of ROM.
16 ESP32-C2 has been designed to target simple, high-volume, and low-data-rate IoT applications,
17 such as smart plugs and smart light bulbs. ESP32-C2 offers easy and robust wireless connectivity,
18 which makes it the go-to solution for developing simple, user-friendly and reliable
19 smart-home devices. For more information, check `ESP8684 Datasheet`_.
[all …]
/Zephyr-latest/scripts/kconfig/
Dkconfig.py3 # 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/kernel/usermode/
Doverview.rst9 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 …]
/Zephyr-latest/boards/shields/eval_adxl362_ardz/doc/
Dindex.rst3 EVAL-ADXL362-ARDZ
9 The EVAL-ADXL362-ARDZ is a 3-axis digital accelerometer Arduino shield powered
15 Set ``--shield eval_adxl362_ardz`` when you invoke ``west build``. For example:
17 .. zephyr-app-commands::
18 :zephyr-app: samples/sensor/sensor_shell
33 - `EVAL-ADXL362-ARDZ product page`_
34 - `EVAL-ADXL362-ARDZ user guide`_
35 - `EVAL-ADXL362-ARDZ schematic`_
36 - `ADXL362 product page`_
37 - `ADXL362 data sheet`_
[all …]
/Zephyr-latest/boards/shields/eval_adxl372_ardz/doc/
Dindex.rst3 EVAL-ADXL372-ARDZ
9 The EVAL-ADXL372-ARDZ is a 3-axis digital accelerometer Arduino shield powered
15 Set ``--shield eval_adxl372_ardz`` when you invoke ``west build``. For example:
17 .. zephyr-app-commands::
18 :zephyr-app: samples/sensor/sensor_shell
33 - `EVAL-ADXL372-ARDZ product page`_
34 - `EVAL-ADXL372-ARDZ user guide`_
35 - `EVAL-ADXL372-ARDZ schematic`_
36 - `ADXL372 product page`_
37 - `ADXL372 data sheet`_
[all …]
/Zephyr-latest/doc/kernel/services/other/
Dthread_local_storage.rst6 Thread Local Storage (TLS) allows variables to be allocated on a per-thread
25 variable. This allows user threads to access the value of ``errno`` without
34 For example, to declare a thread local variable in header files:
36 .. code-block:: c
40 And to declare the actual variable in source files:
42 .. code-block:: c
48 .. code-block:: c
54 .. code-block:: c
/Zephyr-latest/doc/build/kconfig/
Dtips.rst3 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/
D.gitlint2 # 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 …]
/Zephyr-latest/subsys/llext/
DKconfig2 # SPDX-License-Identifier: Apache-2.0
26 Build and expect object files as binary object type for the
28 generate the object file. Currently not supported on RISC-V.
33 Build and expect relocatable (partially linked) files as the
34 binary object type for the llext subsystem. These object files
35 are generated by the linker by combining multiple object files
43 generate the shared library from multiple object files.
54 bool "Use -fPIC when building LLEXT"
58 By default LLEXT compilation is performed with -fno-pic -fno-pie compiler
59 flags. Some platforms can benefit from using -fPIC instead, in which case
[all …]

12345678910>>...13