Searched +full:- +full:- +full:build +full:- +full:only (Results 1 – 25 of 810) sorted by relevance
12345678910>>...33
| /Zephyr-latest/tests/drivers/eeprom/api/ |
| D | testcase.yaml | 4 - drivers
5 - eeprom
8 # Tests overwrite EEPROM content, only run on select boards
10 - native_sim
11 - native_sim/native/64
12 - qemu_x86
13 - nucleo_l152re
14 - nucleo_l073rz
16 - qemu_x86
18 # Tests overwrite EEPROM content, only run on select boards
[all …]
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-arch.rst | 1 .. _bluetooth-arch:
13 Zephyr supports mainly Bluetooth Low Energy (BLE), the low-power
18 .. _bluetooth-layers:
27 multiple (non real-time) network and transport protocols enabling
31 low-level, real-time protocol which provides, in conjunction with the Radio
32 Hardware, standard-interoperable over-the-air communication. The LL schedules
39 .. _bluetooth-hci:
54 .. _bluetooth-configs:
63 * **Single-chip configuration**: In this configuration, a single microcontroller
65 system-on-chip (SoC) implementation. In this case the BLE Host and the BLE
[all …]
|
| D | bluetooth-dev.rst | 1 .. _bluetooth-dev:
10 Additional information that is only relevant to Bluetooth applications can be
26 .. _bluetooth-hw-setup:
38 #. :ref:`Embedded <bluetooth-hw-setup-embedded>`
39 #. :ref:`External controller <bluetooth-hw-setup-external-ll>`
41 - :ref:`QEMU host <bluetooth-hw-setup-qemu-host>`
42 - :ref:`native_sim host <bluetooth-hw-setup-native-sim-host>`
44 #. :ref:`Simulated nRF5x with BabbleSim <bluetooth-hw-setup-bsim>`
46 .. _bluetooth-hw-setup-embedded:
53 All the :ref:`bluetooth-configs` and :ref:`bluetooth-build-types` are supported
[all …]
|
| /Zephyr-latest/arch/posix/ |
| D | Kconfig | 4 # SPDX-License-Identifier: Apache-2.0
19 In bytes, stack size for Zephyr threads meant only for the POSIX
21 (In this architecture only part of the thread status is kept in the Zephyr
26 bool "Build fuzz test target"
28 Build as an LLVM libfuzzer target. Requires
29 support from the toolchain (currently only clang works, and
30 only on native_{posix,sim}[//64]), and should normally be used in
|
| /Zephyr-latest/tests/net/all/ |
| D | testcase.yaml | 2 # Only used for compile testing so it is enough to use one platform here.
7 - net
8 - net-all
10 net.build:
12 - CONFIG_NET_TC_THREAD_COOPERATIVE=y
13 net.build.preempt:
15 - CONFIG_NET_TC_THREAD_PREEMPTIVE=y
|
| /Zephyr-latest/scripts/ |
| D | twister | 4 # SPDX-License-Identifier: Apache-2.0
11 build each test case on one platform per architecture, using a precedence
18 the test case, which only needs to be unique for the test cases specified in
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
36 that are only run under certain circumstances, like daily
51 If true, build the sample using the sysbuild infrastructure. Filtering
52 will only be enabled for the main project, and is not supported for
60 If true, attempt to build test on all available platforms.
[all …]
|
| /Zephyr-latest/subsys/llext/ |
| D | Kconfig | 2 # 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
41 Build and expect shared libraries as binary object type for
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
60 most internal linking is performed by the linker at build time. Select "y"
90 bool "Export built-in symbols to llexts via SLIDs"
[all …]
|
| /Zephyr-latest/doc/develop/west/ |
| D | build-flash-debug.rst | 1 .. _west-build-flash-debug:
6 Zephyr provides several :ref:`west extension commands <west-extensions>` for
8 ``build``, ``flash``, ``debug``, ``debugserver`` and ``attach``.
11 commands, see :ref:`flash-and-debug-support` in the board porting guide.
13 .. Add a per-page contents at the top of the page. This page is nested
16 .. only:: html
21 .. _west-building:
23 Building: ``west build``
26 .. tip:: Run ``west build -h`` for a quick overview.
28 The ``build`` command helps you build Zephyr applications from source. You can
[all …]
|
| /Zephyr-latest/soc/mediatek/mt8xxx/ |
| D | CMakeLists.txt | 2 # SPDX-License-Identifier: Apache-2.0
25 # its own at build time. And likewise the signing key isn't provided
26 # by Zephyr and needs tob e found by a SOF build by passing it in
29 # The short version is that zephyr.ri can only realistically be
30 # exercised from a SOF build and it doesn't belong here in Zephyr;
31 # rimage is a SOF tool. Signing audio firmware is only done for SOF
41 COMMAND west $<$<BOOL:${CMAKE_VERBOSE_MAKEFILE}>:--verbose> sign
42 --if-tool-available --tool rimage --build-dir ${CMAKE_BINARY_DIR}
|
| /Zephyr-latest/ |
| D | Kconfig.zephyr | 3 # Copyright (c) 2014-2015 Wind River Systems, Inc.
6 # SPDX-License-Identifier: Apache-2.0
56 menu "Build and Link Features"
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
136 If the application is built for chain-loading by a bootloader this
[all …]
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | environment.py | 4 # Copyright (c) 2018-2024 Intel Corporation
8 # SPDX-License-Identifier: Apache-2.0
37 # for. Don't use it when invoking other components of the build system
45 def _get_installed_packages() -> Generator[str, None, None]:
63 PYTEST_PLUGIN_INSTALLED = 'pytest-twister-harness' in installed_packages
71 def add_parse_arguments(parser = None) -> argparse.ArgumentParser:
82 $ ./scripts/twister -v \\
83 --testsuite-root tests/ztest/base \\
84 --testsuite-root tests/kernel \\
85 --test tests/ztest/base/testing.ztest.verbose_0 \\
[all …]
|
| /Zephyr-latest/scripts/west_commands/ |
| D | build_helpers.py | 3 # SPDX-License-Identifier: Apache-2.0
10 See build.py for the build command itself.
27 DEFAULT_BUILD_DIR = 'build'
28 '''Name of the default Zephyr build directory.'''
34 If the build directory is not given, the default is {}/ unless the
35 build.dir-fmt configuration variable is set. The current directory is
36 checked after that. If either is a Zephyr build directory, it is used.
57 # Guess the build folder by iterating through all sub-folders from the
59 # proceed to iterate over subfolders only if there is a single folder
72 # Missing key, check sub-folders and match if a single one exists
[all …]
|
| D | build.py | 3 # SPDX-License-Identifier: Apache-2.0
22 _ARG_SEPARATOR = '--'
30 west build [-h] [-b BOARD[@REV]]] [-d BUILD_DIR]
31 [-S SNIPPET] [--shield SHIELD]
32 [-t TARGET] [-p {auto, always, never}] [-c] [--cmake-only]
33 [-n] [-o BUILD_OPT] [-f]
34 [--sysbuild | --no-sysbuild] [--domain DOMAIN]
35 [--extra-conf FILE.conf]
36 [--extra-dtc-overlay FILE.overlay]
37 [source_dir] -- [cmake_opt [cmake_opt ...]]
[all …]
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | overview.rst | 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
34 - We prevent access to memory not specifically granted, or incorrect access to
36 read-only area.
38 - Access to thread stack buffers will be controlled with a policy which
41 - A user thread will by default have read/write access to its own stack
[all …]
|
| /Zephyr-latest/samples/subsys/llext/edk/ |
| D | README.rst | 1 .. zephyr:code-sample:: llext-edk
3 :relevant-api: llext_apis
26 providing some level of isolation - although the kernel one still has access
29 Note that the kernel extension is only available when the EDK is built with
33 The application is built using the Zephyr build system. The EDK is built using
34 the Zephyr build system as well, via ``llext-edk`` target. The EDK is then
38 during build time, which is not really practical. This sample is about the EDK
39 providing the ability to build extensions independently from the application.
40 One could build the extensions in different directories, not related to the
41 Zephyr application - even on different machines, using only the EDK. At the
[all …]
|
| /Zephyr-latest/boards/shields/lcd_par_s035/doc/ |
| D | index.rst | 9 The LCD-PAR-S035 is a 3.5” 480x320 IPS TFT LCD module with wide viewing angle
10 and 5-point capacitive touch functionality. The LCD module can be controlled
13 at the `LCD-PAR-S035 product page`_.
18 This shield can only be used with FRDM-X evaluation kits with a parallel LCD
19 connector or a PMOD connector. Currently only the parallel LCD connector is
25 Set ``--shield lcd_par_s035_8080`` when you invoke ``west build``. For
28 .. zephyr-app-commands::
29 :zephyr-app: samples/drivers/display
32 :goals: build
37 .. target-notes::
[all …]
|
| /Zephyr-latest/samples/net/sockets/echo_service/ |
| D | README.rst | 1 .. zephyr:code-sample:: sockets-service-echo
3 :relevant-api: bsd_sockets
16 of sockets. This saves memory as only one thread needs to be created in the
26 - :ref:`networking_with_host`
27 - or, a board with hardware networking
32 Build the Zephyr version of the sockets/echo_service application like this:
34 .. zephyr-app-commands::
35 :zephyr-app: samples/net/sockets/echo_service
37 :goals: build
44 .. code-block:: console
[all …]
|
| /Zephyr-latest/samples/sysbuild/with_mcuboot/ |
| D | README.rst | 1 .. zephyr:code-sample:: with_mcuboot
4 Build a Zephyr application + MCUboot using sysbuild.
29 configures MCUboot to prevent downgrades and operate in upgrade-only mode.
31 To build both the sample and MCUboot with ``west`` for the ``reel_board``, run:
33 .. zephyr-app-commands::
35 :zephyr-app: samples/sysbuild/with_mcuboot
37 :goals: build
38 :west-args: --sysbuild
43 .. code-block:: console
45 *** Booting Zephyr OS build v3.2.0-rc3-209-gdcf4201d3573 ***
[all …]
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | crosstool_ng.rst | 3 Crosstool-NG (Deprecated)
9 :ref:`cross-compile toolchain variant <other_x_compilers>` should be used
10 when using a custom toolchain built with Crosstool-NG.
12 You can build toolchains from source code using crosstool-NG.
14 #. Follow the steps on the crosstool-NG website to `prepare your host
15 <http://crosstool-ng.github.io/docs/os-setup/>`_.
18 <https://github.com/zephyrproject-rtos/sdk-ng/blob/master/README.md>`_ to
19 build your toolchain. Repeat as necessary to build toolchains for multiple
22 You will need to clone the ``sdk-ng`` repo and run the following command:
24 .. code-block:: console
[all …]
|
| /Zephyr-latest/boards/native/native_posix/doc/ |
| D | index.rst | 21 which will set its configuration to mimic a native_posix-like configuration.
24 Just like with :ref:`native_sim<native_sim>` you can build your Zephyr application
28 But unlike with :ref:`native_sim<native_sim>` you are limited to only using the host C library.
53 Moreover, being limited to build only with the host C library, it is not possible to build
62 To build, simply specify the ``native_posix`` board as target:
64 .. zephyr-app-commands::
65 :zephyr-app: samples/hello_world
66 :host-os: unix
68 :goals: build
71 Now you have a Linux executable, ``./build/zephyr/zephyr.exe``, you can use just like any
[all …]
|
| /Zephyr-latest/cmake/modules/ |
| D | zephyr_module.cmake | 1 # SPDX-License-Identifier: Apache-2.0
9 # files for Zephyr modules into Zephyr build system.
13 # The `<module>/zephyr/module.yml` file specifies whether the build files are
16 # A list of Zephyr modules can be provided to the build system using:
17 # -DZEPHYR_MODULES=<module-path>[;<additional-module(s)-path>]
21 # to load the Zephyr module into Zephyr build system.
25 # If the module.yml file specifies that build files are located in a
27 # - `ZEPHYR_<MODULE_NAME>_CMAKE_DIR` is used for inclusion of the CMakeLists.txt
28 # - `ZEPHYR_<MODULE_NAME>_KCONFIG` is used for inclusion of the Kconfig
29 # files into the build system.
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | wifi.rst | 3 Wi-Fi Management
9 The Wi-Fi management API is used to manage Wi-Fi networks. It supports below modes:
14 Only personal mode security is supported with below types:
17 * WPA2-PSK
18 * WPA2-PSK-256
19 * WPA3-SAE
21 The Wi-Fi management API is implemented in the ``wifi_mgmt`` module as a part of the networking L2
23 Currently, two types of Wi-Fi drivers are supported:
28 Wi-Fi PSA crypto supported build
31 To enable PSA crypto API supported Wi-Fi build, the :kconfig:option:`CONFIG_WIFI_NM_WPA_SUPPLICANT_…
[all …]
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 3 Sysbuild (System build)
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
8 or more Zephyr build systems and optional additional build systems
9 into a hierarchical build system.
11 For example, you can use sysbuild to build a Zephyr application together
19 Like Zephyr's :ref:`build system <build_overview>`, sysbuild is written in
27 Single-image build
29 build system.
31 Multi-image build
[all …]
|
| /Zephyr-latest/samples/net/virtual/ |
| D | README.rst | 1 .. zephyr:code-sample:: virtual-network-interface
3 :relevant-api: virtual virtual_mgmt
18 one provides only IPv6 tunnel, and the other only IPv4. These two tunnels
29 - :ref:`networking_with_host`
34 The `net-tools`_ project provides a configuration that can be used
37 .. code-block:: console
39 net-setup.sh -c zeth-tunnel.conf
42 an Ethernet network interface. Build the sample application like this:
44 .. zephyr-app-commands::
45 :zephyr-app: samples/net/virtual
[all …]
|
| /Zephyr-latest/samples/ |
| D | sample_definition_and_criteria.rst | 11 Samples should be limited in scope and should focus only on demonstrating non-trivial or
34 :zephyr_file:`tests/` folder. In a sample, the only thing you test is
38 2. Twister should be able to build every sample.
44 .. code-block:: yaml
49 - native_sim
51 - kernel
52 - condition_variables
57 - ".*Waited and joined with 3 threads"
59 * Do not mark the test as build only. A sample should be able to build *and*
61 execution. Twister only attempts to flash and execute the build binary if
[all …]
|
12345678910>>...33
