Lines Matching +full:- +full:a

1 # Porting how-to
4 `MCUboot` to a new target `OS`.
8 * `MCUboot` requires a configuration file, which can be included as
12 * `MCUboot` requires that the target provides a `flash` API with ability to
15 * `MCUboot` doesn't bundle a cryptographic library, which means the target
24 From the perspective of the target OS, the bootloader can be seen as a library,
25 so an entry point must be provided. This is likely a typical `app` for the
32 This function is located at `boot/bootutil/loader.c` and receives a `struct
37     /** A pointer to the header of the image to be executed. */
55 You must provide a file, mcuboot_config/mcuboot_config.h. This is
60 See the file samples/mcuboot_config/mcuboot_config.template.h for a
61 starting point and more information. This is a good place to convert
67 - boot/zephyr/include/mcuboot_config/mcuboot_config.h
68 - boot/mynewt/mcuboot_config/include/mcuboot_config/mcuboot_config.h
73 for MCUboot and images of applications are stored, in system-agnostic way.
78 The common code of MCUboot, that is non-system specific, does not directly
102 instead a system is required to provide following mandatory getter functions:
107 /*< Obtains ID of a device the flash area `fa` described region resides on */
109 /*< Obtains offset, from the beginning of a device, the flash area described
163     relevant only when multi-image support support is enabled */
171 ---
174 …a flash area multiple times simultaneously (through nested calls to `flash_area_open`). As a resul…
176 ---