Searched full:images (Results 1 – 25 of 292) sorted by relevance
12345678910>>...12
| /Zephyr-latest/share/sysbuild/cmake/modules/ |
| D | sysbuild_images.cmake | 5 # This module is responsible for including images into sysbuild and to call
8 # Internal function to update build info with list of images abnd write the file.
10 # Function takes a list of images.
11 function(sysbuild_info_image images)
13 foreach(image ${images})
22 build_info(images VALUE ${info_image_list})
23 # Save current state of build info. This allow external tools to fetch sysbuild controlled images
33 sysbuild_add_subdirectory(${sysbuild_toplevel_SOURCE_DIR}/images sysbuild/images)
35 get_property(IMAGES GLOBAL PROPERTY sysbuild_images)
36 sysbuild_module_call(PRE_CMAKE MODULES ${SYSBUILD_MODULE_NAMES} IMAGES ${IMAGES})
[all …]
|
| /Zephyr-latest/boards/arm/fvp_baser_aemv8r/doc/ |
| D | debug-with-arm-ds.rst | 12 .. image:: images/version-info.jpg
27 .. image:: images/perspective-choose-other.jpg
33 .. image:: images/perspective-choose-ds.jpg
42 .. image:: images/create-new-configuration-database.jpg
48 .. image:: images/create-new-configuration-database_database-name.jpg
54 .. image:: images/create-new-configuration-database_shown-in-project-explorer.jpg
63 .. image:: images/create-new-model-configuration.jpg
73 .. image:: images/create-new-model-configuration_model-path.jpg
80 .. image:: images/create-new-model-configuration_model-use-V8R64-Generic.jpg
89 .. image:: images/create-new-launch-configuration_context-menu.jpg
[all …]
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | images.rst | 3 Sysbuild images
6 Sysbuild can be used to add additional images to builds, these can be added by projects or boards
9 Methods of adding images
12 Images can be added to project or projects in various ways, multiple ways can be used
18 Applications can add sysbuild images using the ``sysbuild.cmake`` file in the application
19 directory, the inclusion of images can be controlled with a ``Kconfig.sysbuild`` file in the
25 Boards can add sysbuild images by using the ``sysbuild.cmake`` file in the board directory, the
26 inclusion of images can be controlled with a ``Kconfig.sysbuild`` file in the board directory.
31 SoCs can add sysbuild images by using the ``sysbuild.cmake`` file in the soc directory.
36 :ref:`modules` can add sysbuild images with the ``sysbuild-cmake`` and ``sysbuild-kconfig``
[all …]
|
| /Zephyr-latest/subsys/usb/device_next/class/ |
| D | Kconfig.dfu | 12 int "Number of possible DFU images"
16 Number of possible DFU images.
19 bool "Allow images to be uploaded to the host"
23 allows images to be uploaded to the host.
|
| /Zephyr-latest/share/sysbuild/cmake/ |
| D | domains.cmake | 5 sysbuild_images_order(IMAGES_FLASHING_ORDER FLASH IMAGES ${IMAGES})
10 foreach(image ${IMAGES})
|
| /Zephyr-latest/doc/services/tfm/ |
| D | build.rst | 18 deal with signing the secure and non-secure images before deploying them.
20 Images Created by the TF-M Build
56 Signing Images
60 (BL2) and firmware images must be signed with a private key. The firmware image
65 images, and ``<tfm-dir>/bl2/ext/mcuboot/root-rsa-3072_1.pem`` is used to sign
66 non-secure images. These default .pem keys can (and **should**) be overridden
88 lose this key file, you will be unable to sign any future firmware images,
140 The build system offers targets to view and analyse RAM and ROM usage in generated images.
141 The tools run on the final images and give information about size of symbols and code being used in…
|
| /Zephyr-latest/soc/nxp/lpc/lpc55xxx/ |
| D | linker.ld | 11 * This is the linker script for both standard images and XIP images.
|
| /Zephyr-latest/soc/nxp/lpc/lpc54xxx/ |
| D | linker.ld | 11 * This is the linker script for both standard images and XIP images.
|
| /Zephyr-latest/soc/native/inf_clock/ |
| D | Kconfig | 39 string "Other cores images to include"
42 This option can be used to provide the native simulator with other MCUs/Cores images which have
45 have it produce the final link with the native simulator runner and the other MCU images.
|
| /Zephyr-latest/boards/nordic/nrf5340_audio_dk/ |
| D | Kconfig | 13 image application where one or more images should be located on
26 image application where one or more images should be located on
|
| /Zephyr-latest/boards/nordic/nrf5340dk/ |
| D | Kconfig | 13 image application where one or more images should be located on
25 image application where one or more images should be located on
|
| /Zephyr-latest/boards/raytac/mdbt53_db_40/ |
| D | Kconfig | 13 image application where one or more images should be located on
26 image application where one or more images should be located on
|
| /Zephyr-latest/boards/raytac/mdbt53v_db_40/ |
| D | Kconfig | 13 image application where one or more images should be located on
26 image application where one or more images should be located on
|
| /Zephyr-latest/boards/nordic/thingy53/ |
| D | Kconfig | 19 image application where one or more images should be located on
32 image application where one or more images should be located on
|
| /Zephyr-latest/boards/ezurio/bl5340_dvk/ |
| D | Kconfig | 14 image application where one or more images should be located on
27 image application where one or more images should be located on
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfd_srv.rst | 15 images over SMP service only.
24 The Firmware Distribution Server is capable of storing multiple firmware images for distribution.
26 nodes in the network in any order. The contents, format and size of the firmware images are vendor
|
| /Zephyr-latest/boards/panasonic/pan1783/ |
| D | Kconfig | 15 image application where one or more images should be located on
28 image application where one or more images should be located on
|
| /Zephyr-latest/boards/nordic/nrf7002dk/ |
| D | Kconfig | 27 image application where one or more images should be located on
44 image application where one or more images should be located on
|
| /Zephyr-latest/soc/nxp/imxrt/imxrt5xx/cm33/ |
| D | linker.ld | 10 * This is the linker script for both standard images and XIP images.
|
| /Zephyr-latest/tests/boot/test_mcuboot/ |
| D | sysbuild.cmake | 17 # Add the swapped app to the list of images to flash
18 # Ensure the flashing order of images is as follows:
|
| /Zephyr-latest/include/zephyr/display/ |
| D | mb_display.h | 56 /** Default mode ("single" for images, "scroll" for text). */
59 /** Display images sequentially, one at a time. */
62 /** Display images by scrolling. */
117 * @brief Display one or more images on the BBC micro:bit LED display.
119 * This function takes an array of one or more images and renders them
130 * @param img_count Number of images in 'img' array.
|
| /Zephyr-latest/samples/boards/nordic/dynamic_pinctrl/ |
| D | README.rst | 38 .. figure:: images/nrf52840dk-dynamic-pinctrl.webp
76 .. figure:: images/terminals-empty.png
83 .. figure:: images/terminals-default.png
91 .. figure:: images/terminals-alt.png
|
| /Zephyr-latest/samples/tfm_integration/ |
| D | tfm_integration.rst | 16 built, in addition to the TF-M S and Zephyr NS binary images. The S and NS
17 images are then merged and signed using the private signing keys, whose public
19 images to be verified and either accepted or rejected during the image
|
| /Zephyr-latest/tests/cmake/zephyr_get/ |
| D | sysbuild.cmake | 13 list(APPEND IMAGES ${image})
19 foreach(image ${IMAGES})
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/img_mgmt/ |
| D | Kconfig | 47 int "Number of supported images"
51 Sets how many application images are supported (pairs of secondary and primary slots).
55 boot_util and the UPDATEABLE_IMAGE_NUMBER controls number of images supported
100 (two DTS images for Zephyr); this allows to treat every DTS defined image as direct
160 MCUboot images should be limited to the maximum size that the bootloader can swap, in
166 confirmed images, if support for that is required then this feature should be left as
209 images and slots that the application can see.
|
12345678910>>...12
