summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Hughes <tomhughes@chromium.org>2019-11-18 09:50:20 -0800
committerCommit Bot <commit-bot@chromium.org>2019-11-18 18:45:27 +0000
commit6747da58fb5c07f34b4bfe27fff6715480ff1ec1 (patch)
treed106adfc3fee8c99319c7f9ffc85e669afc3d10f
parent55d2b5df418421db5fcffae3d4c2af847feafe0c (diff)
downloadchrome-ec-6747da58fb5c07f34b4bfe27fff6715480ff1ec1.tar.gz
docs/fingerprint: Clarify flash_fp_mcu behavior
BRANCH=none BUG=none TEST=none Change-Id: I9305add05965579e5cc4ffed54704a17da27e275 Signed-off-by: Tom Hughes <tomhughes@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/1922228 Reviewed-by: Craig Hesling <hesling@chromium.org> Commit-Queue: Craig Hesling <hesling@chromium.org>
-rw-r--r--docs/fingerprint/fingerprint.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/fingerprint/fingerprint.md b/docs/fingerprint/fingerprint.md
index c09520e308..90b6aeeb1c 100644
--- a/docs/fingerprint/fingerprint.md
+++ b/docs/fingerprint/fingerprint.md
@@ -115,9 +115,10 @@ in the field (can’t by design).
***
[`flash_fp_mcu`] enables spidev and toggles some GPIOs to put the FPMCU (STM32)
-into bootloader mode. At that point it uses `stm32mon` to rewrite the entire
-flash (both RO and RW). This will only work if [hardware write protection] is
-disabled.
+into bootloader mode. At that point it uses [`stm32mon`] to rewrite the entire
+flash (both RO and RW). The FPMCU can only be put into bootloader mode when
+[hardware write protection] is disabled, which means [`flash_fp_mcu`] can only
+be used when [hardware write protection] is disabled.
### `stm32mon`