diff options
| -rw-r--r-- | docs/write_protection.md | 73 |
1 files changed, 0 insertions, 73 deletions
diff --git a/docs/write_protection.md b/docs/write_protection.md index 0ce6253a04..20d7e146ab 100644 --- a/docs/write_protection.md +++ b/docs/write_protection.md @@ -188,79 +188,6 @@ If the `ro_at_boot` flag set, and the EC resets with the HW gpio disabled, the EC will leave the flash unprotected (`ro_now` and `all_now` flags are not set) but leave `ro_at_boot` flag set. -### Changing Software Write Protection with flashrom - -#### View the current state of software write protection - -```bash -(chroot) $ flashrom -p ec --wp-status -``` - -``` -WP: status: 0x00 -WP: status.srp0: 0 -WP: write protect is disabled. -WP: write protect range: start=0x00000000, len=0x00000000 -``` - -#### Enable software write protection - -This is immediate. The protection range indicates the RO region of the firmware. - -```bash -(chroot) $ flashrom -p ec --wp-enable -``` - -``` -SUCCESS -``` - -```bash -(chroot) $ flashrom -p ec --wp-status -``` - -``` -WP: status: 0x80 -WP: status.srp0: 1 -WP: write protect is enabled. -WP: write protect range: start=0x00000000, len=0x0001f800 -``` - -#### Disable software write protection - -Disable can only be done with hardware write protect disabled. - -```bash -(chroot) $ flashrom -p ec --wp-disable -``` - -``` -FAILED: RO_AT_BOOT is not clear. -FAILED -``` - -Reboot with [hardware write protection](#hw_wp) disabled. Note that protection -is still enabled, but the protection range is zero. - -```bash -(chroot) $ flashrom -p ec --wp-status -``` - -``` -WP: status: 0x80 -WP: status.srp0: 1 -WP: write protect is enabled. -WP: write protect range: start=0x00000000, len=0x00000000 -``` - -```bash -(chroot) $ flashrom -p ec --wp-disable -``` - -``` -SUCCESS -``` - ## system_is_locked() The [`system_is_locked()`] function in the EC code returns false if the HW write |