| /Zephyr-latest/cmake/modules/ |
| D | doc.cmake | 1 # SPDX-License-Identifier: Apache-2.0
6 # documentation build.
9 # - extensions
10 # - python
11 # - west
12 # - root
13 # - zephyr_module
16 # The Zephyr package required for documentation build setup.
23 include(root)
|
| 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 …]
|
| D | zephyr_default.cmake | 1 # SPDX-License-Identifier: Apache-2.0
6 # default Zephyr build system.
27 # Find and execute workspace build configuration
40 # Find and execute application-specific build configuration
53 # Test and error-out if we are affected by the PyPI CMake 3.22.1 / 3.22.2 bug
55 # It seems only pip-installed builds are affected so we test to see if we are affected
60 "https://gitlab.kitware.com/cmake/cmake/-/issues/23187\n"
61 "https://github.com/scikit-build/cmake-python-distributions/issues/221\n"
62 "Please install another CMake version or use a build of CMake that"
87 # Load default root settings
[all …]
|
| D | arch.cmake | 1 # SPDX-License-Identifier: Apache-2.0
6 # Configure ARCH settings based on KConfig settings and arch root.
8 # This CMake module will set the following variables in the build system based
9 # on board directory and arch root.
16 # - ARCH: Name of the arch in use.
17 # - ARCH_DIR: Directory containing the arch implementation.
18 # - ARCH_ROOT: ARCH_ROOT with ZEPHYR_BASE appended
21 # - ARCH_ROOT: CMake list of arch roots containing arch implementations
24 # use only and may be removed, renamed, or re-purposed without prior notice.
31 # (read: multi-core and multi-arch SoC).
|
| D | boards.cmake | 1 # SPDX-License-Identifier: Apache-2.0
24 # - BOARD: Board, without revision field.
25 # - BOARD_REVISION: Board revision
26 # - BOARD_QUALIFIERS: Board qualifiers
27 # - NORMALIZED_BOARD_QUALIFIERS: Board qualifiers in lower-case format where slashes have been
29 # - NORMALIZED_BOARD_TARGET: Board target in lower-case format where slashes have been
31 # - BOARD_DIR: Board directory with the implementation for selected board
32 # - ARCH_DIR: Arch dir for extracted from selected board
33 # - BOARD_ROOT: BOARD_ROOT with ZEPHYR_BASE appended
34 # - BOARD_EXTENSION_DIRS: List of board extension directories (If
[all …]
|
| D | snippets.cmake | 1 # SPDX-License-Identifier: Apache-2.0
9 # - searches for snippets in zephyr and any modules
10 # - validates the SNIPPET input variable, if any
18 # - SNIPPET_AS_LIST: CMake list of snippet names, created from the
20 # - SNIPPET_ROOT: CMake list of snippet roots, deduplicated and with
24 # - DTC_OVERLAY_FILE
25 # - OVERLAY_CONFIG
28 # - snippets: when invoked, a list of valid snippets will be printed
31 # - SNIPPET_ROOT: input CMake list of snippet roots (directories containing
80 foreach(root IN LISTS SNIPPET_ROOT)
[all …]
|
| /Zephyr-latest/scripts/ |
| D | list_shields.py | 5 # SPDX-License-Identifier: Apache-2.0
12 # This is shared code between the build system's 'shields' target
17 # 'ninja shields' in a build directory without west installed.)
31 for root in args.board_roots:
32 for shields in find_shields_in(root):
37 def find_shields_in(root): argument
38 shields = root / 'boards' / 'shields'
49 shield_name = file_name[:-len('.overlay')]
60 # Remember to update west-completion.bash if you add or remove
62 parser.add_argument("--board-root", dest='board_roots', default=[],
[all …]
|
| D | list_boards.py | 4 # SPDX-License-Identifier: Apache-2.0
23 BOARD_SCHEMA_PATH = str(Path(__file__).parent / 'schemas' / 'board-schema.yml')
30 # This is shared code between the build system's 'boards' target
35 # 'ninja boards' in a build directory without west installed.)
169 for root in unique_paths(args.board_roots):
170 for arch, boards in find_arch2board_set_in(root, arches, args.board_dir).items():
182 for root in unique_paths(args.arch_roots):
183 arch_set |= find_arches_in(root)
188 def find_arches_in(root): argument
190 arch = root / 'arch'
[all …]
|
| /Zephyr-latest/scripts/west_commands/completion/ |
| D | west-completion.zsh | 4 # SPDX-License-Identifier: Apache-2.0
6 # Ensure this works also when being source-ed
9 typeset -A -g _opt_args
12 local -a builtin_cmds=(
25 local -a zephyr_ext_cmds=(
28 'build[compile a Zephyr application]'
29 'sign[sign a Zephyr binary for bootloader chain-loading]'
34 'zephyr-export[export Zephyr installation as a CMake config package]'
40 local -a all_cmds=(${builtin_cmds} ${zephyr_ext_cmds})
42 if [[ -v WEST_COMP_CHECK_WORKSPACE ]]; then
[all …]
|
| /Zephyr-latest/samples/application_development/external_lib/ |
| D | CMakeLists.txt | 1 # SPDX-License-Identifier: Apache-2.0
10 # how to build for this platform so we export all the flags used in
11 # this zephyr build to the external build system.
13 # Other external build systems may be self-contained enough that they
14 # do not need any build information from zephyr. Or they may be
23 set(target_flag "--target=${CMAKE_C_COMPILER_TARGET}")
32 # Add an external project to be able download and build the third
42 # https://www.gnu.org/software/make/manual/html_node/MAKE-Variable.html
50 PREFIX ${mylib_build_dir} # Root dir for entire project
52 BINARY_DIR ${mylib_src_dir} # This particular build system is invoked from the root
[all …]
|
| /Zephyr-latest/doc/services/tfm/ |
| D | build.rst | 3 TF-M Build System
6 When building a valid ``_ns`` board target, TF-M will be built in the
7 background, and linked with the Zephyr non-secure application. No knowledge
8 of TF-M's build system is required in most cases, and the following will
9 build a TF-M and Zephyr image pair, and run it in qemu with no additional
12 .. code-block:: bash
14 … $ west build -p auto -b mps2/an521/cpu0/ns samples/tfm_integration/psa_protected_storage/ -t run
16 The outputs and certain key steps in this build process are described here,
18 deal with signing the secure and non-secure images before deploying them.
20 Images Created by the TF-M Build
[all …]
|
| D | overview.rst | 1 Trusted Firmware-M Overview
4 `Trusted Firmware-M (TF-M) <https://tf-m-user-guide.trustedfirmware.org/>`__
6 `IoT Security Framework <https://www.psacertified.org/what-is-psa-certified/>`__.
10 Zephyr RTOS has been PSA Certified since Zephyr 2.0.0 with TF-M 1.0, and
11 is currently integrated with TF-M 2.1.0.
13 What Does TF-M Offer?
16 Through a set of secure services and by design, TF-M provides:
18 * Isolation of secure and non-secure resources
19 * Embedded-appropriate crypto
22 * Protected off-chip data storage and retrieval
[all …]
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | chromebooks_adsp.rst | 1 .. _zephyr-audio-dsp-development-on-chromebooks:
8 arbitrary user-developed firmware like Zephyr applications (of which
28 Hold Esc + Refresh (the arrow-in-a-circle "reload" key above "3") and
51 device ID (for example "DELBIN-XHVI D4B-H4D-G4G-Q9A-A9P" for the Asus
54 root filesystem and /usr/local customizations you have made**. So
58 Make the root filesystem writable
62 Linux's dm-verity feature) all access to the read-only root
64 for a custom kernel) requires that the dm-verity layer be turned off:
66 First open a terminal with Ctrl-Alt-T. Then at the "crosh> " prompt
68 user. Finally (in developer mode) a simple "sudo su -" will get you a
[all …]
|
| /Zephyr-latest/samples/boards/nordic/mesh/onoff_level_lighting_vnd_app/ |
| D | README.rst | 1 .. zephyr:code-sample:: nrf_bluetooth_mesh_onoff_level_lighting_vnd_app
3 :relevant-api: bt_mesh
10 which Root element has following models
12 - Generic OnOff Server
13 - Generic OnOff Client
14 - Generic Level Server
15 - Generic Level Client
16 - Generic Default Transition Time Server
17 - Generic Default Transition Time Client
18 - Generic Power OnOff Server
[all …]
|
| /Zephyr-latest/boards/raspberrypi/rpi_5/doc/ |
| D | index.rst | 6 `Raspberry Pi 5 product-brief`_
11 - Broadcom BCM2712 2.4GHz quad-core 64-bit Arm Cortex-A76 CPU, with cryptography extensions, 512KB …
12 - VideoCore VII GPU, supporting OpenGL ES 3.1, Vulkan 1.2
13 - Dual 4Kp60 HDMI® display output with HDR support
14 - 4Kp60 HEVC decoder
15 - LPDDR4X-4267 SDRAM (4GB and 8GB SKUs available at launch)
16 - Dual-band 802.11ac Wi-Fi®
17 - Bluetooth 5.0 / Bluetooth Low Energy (BLE)
18 - microSD card slot, with support for high-speed SDR104 mode
19 - 2 x USB 3.0 ports, supporting simultaneous 5Gbps operation
[all …]
|
| /Zephyr-latest/boards/mediatek/ |
| D | index.rst | 1 .. _boards-mtk_adsp:
27 single-core devices, no parallel SMP is available, but at the same
37 There is comparatively little on-device hardware. The architecture is
38 that interaction with the off-chip audio hardware (e.g. I2S codecs,
42 Beyond that the Zephyr-visible hardware is limited to a bounty of
54 the standard library and can be run (as root, of course) on any
60 * `Developer mode <https://www.chromium.org/chromium-os/developer-library/guides/device/developer-m…
61 …-Install: Installing Developer and Test packages onto a Chrome OS device <https://www.chromium.org…
64 the ``zephyr.img`` file from the build directory to the device
68 .. code-block:: console
[all …]
|
| /Zephyr-latest/samples/subsys/usb/dfu/ |
| D | README.rst | 1 .. zephyr:code-sample:: usb-dfu
3 :relevant-api: _usb_device_core_api
33 to be loaded at the offset of SLOT-0.
36 The build system can do this for you by setting the :kconfig:option:`CONFIG_MCUBOOT_SIGNATURE_KEY_F…
40 .. code-block:: console
42 west build -b nrf52840dk/nrf52840 zephyr/samples/subsys/usb/dfu -d build-dfu -- \
43 -DCONFIG_MCUBOOT_SIGNATURE_KEY_FILE=\"bootloader/mcuboot/root-rsa-2048.pem\"
45 Build and flash MCUboot bootloader for Zephyr project as it is described in
46 the `Using MCUboot with Zephyr`_ documentation. Then build, sign and flash
47 the USB DFU sample at the offset of SLOT-0.
[all …]
|
| /Zephyr-latest/samples/subsys/usb/mass/ |
| D | README.rst | 1 .. zephyr:code-sample:: usb-mass
3 :relevant-api: usbd_api usbd_msc_device _usb_device_core_api file_system_api
25 The selection between a RAM-based or a FLASH-based disk and file system
26 can be chosen passing Kconfig configuration via the -D command-line switch.
28 RAM-disk Example without any file system
31 The default configurations selects RAM-based disk without any file system.
32 This example only needs additional 96KiB RAM for the RAM-disk and is intended
35 .. zephyr-app-commands::
36 :zephyr-app: samples/subsys/usb/mass
38 :gen-args: -DEXTRA_DTC_OVERLAY_FILE="ramdisk.overlay"
[all …]
|
| /Zephyr-latest/samples/drivers/ethernet/eth_ivshmem/ |
| D | README.rst | 1 .. zephyr:code-sample:: eth-ivshmem
2 :name: Inter-VM Shared Memory (ivshmem) Ethernet
3 :relevant-api: ivshmem ethernet
20 .. code-block:: console
22 git clone https://github.com/siemens/jailhouse-images.git
23 cd jailhouse-images
26 Open the menu, select "QEMU ARM64 virtual target" then "Save & Build"
29 .. code-block:: console
31 ./kas-container menu
33 Edit "start-qemu.sh":
[all …]
|
| /Zephyr-latest/boards/intel/ish/doc/ |
| D | index.rst | 8 Intel Integrated Sensor Hub (ISH) is a lower-power/always-on co-processor
15 - LMT MinuteIA Core:
17 - 16KB instruction cache and 16KB data cache.
18 - 640KB SRAM space for code and data - implemented as L2 SRAM.
19 - 8KB AON RF space for code resident during deep D0i2/3 PG states.
21 - Interface-to-Sensor peripherals (I2C, SPI, UART, I3C, GPIO, DMA).
22 - Inter Process Communications (IPC) to core processor and other IP processors.
36 Build Zephyr application
39 #. Build a Zephyr application; for instance, to build the ``hello_world``
42 .. zephyr-app-commands::
[all …]
|
| /Zephyr-latest/tests/subsys/fs/common/ |
| D | test_fs_dirops.c | 5 * SPDX-License-Identifier: Apache-2.0
38 "root init failed"); in check_mkdir()
65 -ENOTEMPTY, in check_mkdir()
85 TC_PRINT("building layout on %s\n", mp->mnt_point); in build_layout()
87 zassert_equal(fs_statvfs(mp->mnt_point, &stat), 0, in build_layout()
95 "root init failed"); in build_layout()
101 zassert_equal(fs_statvfs(mp->mnt_point, &stat), 0, in build_layout()
120 "root init failed"); in check_layout()
132 if (cp->name != NULL) { in check_layout()
134 cp->name, in check_layout()
[all …]
|
| /Zephyr-latest/boards/ct/ctcc/doc/ |
| D | index.rst | 10 using USB device with on-board nRF52840 SoC
12 * The Connectivity Card nRF9161 enables LTE-M/NB-IoT and DECT NR+ over mPCIe or M.2
13 using on-board USB-UART converter
23 * RADIO (LTE-M/NB-IoT and DECT NR+) (only nRF9161)
26 * :abbr:`UARTE (Universal asynchronous receiver-transmitter with EasyDMA)` (only nRF9161)
54 * The ``ctcc/nrf9161`` board target has one external SPI NOR 64Mbit memory and one on-board USB-UART
60 .. zephyr:board-supported-hw::
66 ---
68 Note that boards do not have on-board LEDs, however they expose
92 1. Using an external :ref:`debug probe <debug-probes>`
[all …]
|
| /Zephyr-latest/samples/boards/nordic/mesh/onoff-app/ |
| D | README.rst | 1 .. zephyr:code-sample:: nrf_bluetooth_mesh_onoff
3 :relevant-api: bt_mesh
10 This is a simple application demonstrating a Bluetooth Mesh multi-element node.
19 The models for button 1 and LED 1 are in the node's root element.
21 Assuming the provisioner assigns 0x100 to the root element,
41 This sample has been tested on the Nordic nRF52840-PDK board, but would
47 This sample can be found under :zephyr_file:`samples/boards/nordic/mesh/onoff-app` in the
50 The following commands build the application.
52 .. zephyr-app-commands::
53 :zephyr-app: samples/boards/nordic/mesh/onoff-app
[all …]
|
| /Zephyr-latest/samples/boards/renesas/openamp_linux_zephyr/ |
| D | README.rst | 1 .. zephyr:code-sample:: rz-openamp-linux-zephyr
3 :relevant-api: mbox_interface
6 and the real-time core running Zephyr, using the OpenAMP library.
14 … application uses the OpenAMP library provided by `meta-openamp <https://github.com/OpenAMP/meta-o…
15 a consistent and standardized approach to inter-core communication.
23 Build command:
25 .. zephyr-app-commands::
26 :zephyr-app: samples/boards/renesas/openamp_linux_zephyr
28 :goals: build
37 …he sample currently supports the Linux RZ/G Multi-OS Package V2.2.0. The build steps for Renesas M…
[all …]
|
| /Zephyr-latest/doc/develop/sca/ |
| D | index.rst | 8 The build setting :makevar:`ZEPHYR_SCA_VARIANT` can be used to specify the SCA
12 Use ``-DZEPHYR_SCA_VARIANT=<tool>``, for example ``-DZEPHYR_SCA_VARIANT=sparse``
22 Zephyr itself is always added as an :makevar:`SCA_ROOT` but the build system offers the
28 .. code-block:: none
30 <sca_root>/ # Custom SCA root
38 .. code-block:: none
46 To use ``foo`` as SCA tool you must then specify ``-DZEPHYR_SCA_VARIANT=foo``.
51 ``-DSCA_ROOT=<sca_root>``, or added by a Zephyr module in its :file:`module.yml`
52 file, see :ref:`Zephyr Modules - Build settings <modules_build_settings>`
59 The following is a list of SCA tools natively supported by Zephyr build system.
|
