Lines Matching +full:multi +full:- +full:image

16       The set of user-supplied files that the Zephyr build system uses
17       to build an application image for a specified board configuration.
18       It can contain application-specific code, kernel configuration settings,
25       if it does not require any board-specific capabilities.
27    application image
30       Each application image contains both the application's code and the
32       fully-linked binary.
33       Once an application image is loaded onto a board, the image takes control
43       which can load and execute an application image. It may be an actual
53       specified by the build system can be over-ridden by the application,
57       The human-readable name of a :term:`board`. Uniquely and descriptively
59       information that may be required to actually build a Zephyr image for it.
78      compile and link an image for a particular hardware system. This string
84      A group of one or more :term:`CPU cores <CPU core>`, all executing the same image
114       high-priority conditions that require interrupting the current code
118       The set of Zephyr-supplied files that implement the Zephyr kernel,
155       introducing both secure and non-secure builds for platforms with Trusted
160       A multi-repo meta-tool developed for the Zephyr project. See :ref:`west`.
168       additional metadata. See :ref:`west-basics` for general information
169       and :ref:`west-manifests` for details.
174       configuration option <west-config-index>`. See :ref:`west-basics`.
181       modules. See :ref:`west-manifests-projects` for additional information.
188       :ref:`west-basics`.