Lines Matching refs:flash

12 * `MCUboot` requires that the target provides a `flash` API with ability to
13   get the flash's minimum write size, and read/write/erase individual sectors.
41      * The flash offset of the image to execute.  Indicates the position of
72 The bootloader requires to be able to address flash regions where the code
75 that should uniquely identify each flash region.
76 Such flash regions are served by object of `const struct flash_area` type while
81 This way systems are free to implement internal logic of flash map or define
86 of flash map, on the other side system specific code, within MCUboot, is
96     uint32_t fa_off;        /** The flash offset from the beginning */
105 /*< Obtains ID of the flash area characterized by `fa` */
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
112 /*< Obtains size, from the offset, of the flash area `fa` characterized region */
118 specific header files and are used to identify destination of flash area by ID:
140 flash characterized by `struct flash_area` objects is as follows:
146 /*< Reads `len` bytes of flash memory at `off` to the buffer at `dst` */
149 /*< Writes `len` bytes of flash memory at `off` from the buffer at `src` */
152 /*< Erases `len` bytes of flash memory at `off` */
156 /*< What is value is read from erased flash bytes. */
158 /*< Given flash area ID, return info about sectors within the area. */
174 …flash area multiple times simultaneously (through nested calls to `flash_area_open`). As a result,…