Lines Matching refs:in
5 There are some pretty significant differences in how apps are built
13 partitions defined in its device tree. These partitions are:
27 The flash partitions are typically defined in the Zephyr boards folder, in a
29 flash partitions defined is the frdm_k64f's in
30 `boards/arm/frdm_k64f/frdm_k64f.dts`. Make sure the labels in your board's
46 be made before building it. Most of this can be done as documented in
47 the `CMakeLists.txt` file in boot/zephyr. There are comments there for
51 To build MCUboot, create a build directory in boot/zephyr, and build
61 In addition to the partitions defined in DTS, some additional
63 MCUboot itself. All the needed configuration is collected in
68 After building the bootloader, the binaries should reside in
79 In addition to flash partitions in DTS, some additional configuration
83 in the `CONFIG_BOOTLOADER_MCUBOOT` Kconfig variable, which must be enabled in
86 The directory `samples/zephyr/hello-world` in the MCUboot tree contains
94 placement and generation in order for an application to be bootable by
105 production, since the private key is publicly available in this
129 The signing keys used by MCUboot are represented in standard formats,
131 `scripts/imgtool.py` is able to generate key pairs in all of the
151 bootloader. The keys live in `boot/zephyr/keys.c`, and can be
161 Once this is done, this new keypair file (`mykey.pem` in this