WolfSSL
/
wolfBoot
mirror of https://github.com/wolfSSL/wolfBoot.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Update documentation.

pull/265/head
David Garske 2022-12-16 10:44:43 -08:00 committed by Daniele Lacamera
parent f283929161
commit ac6f5207c7
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/compile.md
View File

@ -262,12 +262,16 @@ associated to the UPDATE partition are stored in the BOOT partition itself.
While on one hand this option slightly reduces the space available in the BOOT partition to store the firmware image, it keeps all the flags in
the BOOT partition.
### Invert logic of flags
### Flash Erase value / Flag logic inversion
By default, most NVMs set the content of erased pages to `0xFF` (all ones).
Some FLASH memory models use inverted logic for erased page, setting the content to `0x00` (all zeroes) after erase.
For these special cases, the option `FLAGS_INVERT = 1` can be used to modify the logic of the partition/sector flags used in wolfBoot.
You can also manually override the fill bytes using `FILL_BYTE=` at build-time. It default to `0xFF`, but will use `0x00` if `FLAGS_INVERT` is set.
Note: if you are using an external FLASH (e.g. SPI) in combination with a flash with inverted logic, ensure that you store all the flags in one partition, by using the `FLAGS_HOME=1` option described above.