Lines Matching full:build

66 together. In order to have the same artefacts at the end of the build regardless
71 ``bl2/ext/mcuboot/scripts/``. At the end of a successful build the signed TF-M
156 switch (see `Build time configuration`_). With swapping image upgrade strategy
181 switch (see `Build time configuration`_). When enabling direct-xip operation
197 two build directories when building images using this mode, as intermediate
272     configuration variable in the build configuration file, or include this
276     ``MCUBOOT_UPGRADE_STRATEGY`` configuration variable in the build
280     ``MCUBOOT_UPGRADE_STRATEGY`` configuration variable in the build
337 Build time configuration
384       public key(s) must be known at MCUBoot build time.
396     by setting it to ``OFF``. Its value depends on the build type. If the build
400     build type.
441 this case, the last component (the build number) automatically increments from
442 the previous one: 0.0.0+1 -> 0.0.0+2, for as many times as the build is re-ran,
446 then set to the last number that has been specified, and the build number would
449 versioning, please start a clean build without specifying the image version
467 be specified at build time in the cmake configuration step::
472 necessarily. Alternatively, if it is not specified at build time with the
474 from the image version number (not including the build number) and this value
485 Normally the build system handles the signing (computing hash over the image
493 expecting. In case of single image boot after a successful build the
494 ``tfm_s_ns.bin`` build artifact (contains the concatenated secure and non-secure
522 firmware package, TF-M is built twice with different build configurations.
526 Run TF-M build twice with ``MCUBOOT_IMAGE_NUMBER`` set to "1" in both cases
527 (single image boot), but with two different build configurations: default and
529 original binaries. Download default build to the primary slot and regression
530 build to the secondary slot.
636 overwriting build including these changes:
639   before build.
641   boot) or "2" (multiple image boot) before build.
665 overwriting build including these changes:
668   before build.
669 - set ``MCUBOOT_EXECUTION_SLOT`` to ``1`` in the regression build dir.
670 - Make sure the image version number was increased between the two build runs
671   either by specifying it manually or by checking in the build log that it was