diff options
| author | Craig Hesling <hesling@chromium.org> | 2020-01-07 18:32:01 +0000 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2020-02-15 02:53:47 +0000 |
| commit | 50847744a89591e7c4c867432dcc1b6d75feb087 (patch) | |
| tree | 0b60f6a9d71808f811c0153507d5e42fe1dba64f /docs/write_protection.md | |
| parent | 4588844d403aad4b9c6bd0732ad6423646ce7a51 (diff) | |
| download | chrome-ec-50847744a89591e7c4c867432dcc1b6d75feb087.tar.gz | |
docs: Remove statement about disabling HW WP + reboot
BRANCH=nocturne,hatch
BUG=none
TEST=Remove HW WP and issue reboot_ec command
Change-Id: I2430f3b08bc8136928e471dcb453cb0c779e3e77
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/1989367
Tested-by: Craig Hesling <hesling@chromium.org>
Reviewed-by: Tom Hughes <tomhughes@chromium.org>
Commit-Queue: Craig Hesling <hesling@chromium.org>
Diffstat (limited to 'docs/write_protection.md')
| -rw-r--r-- | docs/write_protection.md | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/docs/write_protection.md b/docs/write_protection.md index b9033a3414..e57f71045a 100644 --- a/docs/write_protection.md +++ b/docs/write_protection.md @@ -110,11 +110,6 @@ EC chips. However the common requirements are that software write protect can only be disabled when hardware write protect is off and that the RO firmware must be protected before jumping to RW firmware if protection is enabled. -*** note -*WARNING*: If you disable HW write protect *and* then reboot the FPMCU, it will do -a mass erase of the chip, due to [RDP1](#rdp1). -*** - Additional reference: https://www.google.com/chromeos/partner/fe/docs/cpfe/firmwaretestmanual.html#software-write-protect |