Lines Matching full:build
74 together. In order to have the same artefacts at the end of the build regardless
79 ``bl2/ext/mcuboot/scripts/``. At the end of a successful build the signed TF-M
164 switch (see `Build time configuration`_). With swapping image upgrade strategy
191 switch (see `Build time configuration`_). When enabling direct-xip operation
207 two build directories when building images using this mode, as intermediate
282 configuration variable in the build configuration file, or include this
286 ``MCUBOOT_UPGRADE_STRATEGY`` configuration variable in the build
290 ``MCUBOOT_UPGRADE_STRATEGY`` configuration variable in the build
347 Build time configuration
394 public key(s) must be known at MCUBoot build time.
414 by setting it to ``OFF``. Its value depends on the build type. If the build
418 build type.
459 this case, the last component (the build number) automatically increments from
460 the previous one: 0.0.0+1 -> 0.0.0+2, for as many times as the build is re-ran,
464 then set to the last number that has been specified, and the build number would
467 versioning, please start a clean build without specifying the image version
485 be specified at build time in the cmake configuration step::
490 necessarily. Alternatively, if it is not specified at build time with the
492 from the image version number (not including the build number) and this value
503 Normally the build system handles the signing (computing hash over the image
511 expecting. In case of single image boot after a successful build the
512 ``tfm_s_ns.bin`` build artifact (contains the concatenated secure and non-secure
540 firmware package, TF-M is built twice with different build configurations.
544 Run TF-M build twice with ``MCUBOOT_IMAGE_NUMBER`` set to "1" in both cases
545 (single image boot), but with two different build configurations: default and
547 original binaries. Download default build to the primary slot and regression
548 build to the secondary slot.
654 overwriting build including these changes:
657 before build.
659 boot) or "2" (multiple image boot) before build.
683 overwriting build including these changes:
686 before build.
687 - set ``MCUBOOT_EXECUTION_SLOT`` to ``1`` in the regression build dir.
688 - Make sure the image version number was increased between the two build runs
689 either by specifying it manually or by checking in the build log that it was