OrgZephyr/mcuboot
OrgZephyr
/
mcuboot
mirror of https://github.com/zephyrproject-rtos/mcuboot.git
1
0
Fork 0
Code Issues Releases Wiki Activity

doc: design: clarifications to "FLASH MAP" section 

Distinguish between flash areas and flash area IDs. Say what the
bootloader area is, since that's not discussed anywhere else.

Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org>
This commit is contained in:
Marti Bolivar 2017-08-04 14:53:33 -04:00
parent 7c057e9e74
commit 4e64d56e4d
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/design.txt
View File

@ -110,13 +110,16 @@ region of disk with the following properties:
(1) An area can be fully erased without affecting any other areas.
(2) A write to one area does not restrict writes to other areas.
The boot loader uses the following flash areas:
The boot loader uses the following flash area IDs:
#define FLASH_AREA_BOOTLOADER 0
#define FLASH_AREA_IMAGE_0 1
#define FLASH_AREA_IMAGE_1 2
#define FLASH_AREA_IMAGE_SCRATCH 3
The bootloader area contains the bootloader image itself. The other areas are
described in subsequent sections.
*** IMAGE SLOTS
A portion of the flash memory is partitioned into two image slots: a primary