Lines Matching refs:image

27 Single-image build
31 Multi-image build
33 …The word "image" is used because your main goal is usually to generate the binaries of the firmware
68   link your main Zephyr application as an MCUboot-bootable image, using sysbuild's
113          Since sysbuild supports both single- and multi-image builds, this lets you
287 image is flashed in sequence. Extra arguments such as ``--runner jlink`` are
348    erase the entire flash, including the main application image.
404 Sysbuild creates build targets for each image (including sysbuild itself) for
413 are ran with a prefix of the image name and an underscore e.g. ``sysbuild_`` or
414 ``mcuboot_``, using ninja or make - for details on how to run image build
420 Dedicated image build targets
429 image can be provided to west/ninja/make along with the name of the build
479 as the main image, use this example:
524 If the extra application image is specific to the board or an application,
578 but it will be excluded from the default image sequence used by ``west flash``.
580 to produce a secondary image for DFU, or to merge multiple images together.
605 in order to give users full control of an image's configuration.
612 :file:`<image>.conf` or :file:`<image>.overlay`, for example if your main
627 :file:`sysbuild/<image>/`.
629 ``<image>``.
663 a globally provided option will be passed down to all images. In addition, the image configuration
699 image name:
729 Sometimes, in a multi-image build, you may want certain Zephyr applications to
771 You can include non-Zephyr applications in a multi-image build using the
792 each image that is part of a project. Alternatively, there are
795 image itself, this is where e.g. a custom image for a particular board or SoC