From cd1692f92cd05a656d8f84f609afa2168b55a7dd Mon Sep 17 00:00:00 2001 From: Paul Moy Date: Wed, 30 Mar 2022 14:27:24 -0600 Subject: cr50: fix wp atboot documentation The command to change the `atboot` wp setting should have `atboot` as the last argument, not the second. BUG=none TEST=none Change-Id: I0fff0d7dc206068d1f51bb8e890f2ccaaafb18c8 Signed-off-by: pmoy@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3561026 Reviewed-by: Vadim Bendebury Reviewed-by: Mary Ruthven Commit-Queue: Mary Ruthven Tested-by: Mary Ruthven --- docs/case_closed_debugging_cr50.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/case_closed_debugging_cr50.md b/docs/case_closed_debugging_cr50.md index b57e99d541..bd35ebc6cd 100644 --- a/docs/case_closed_debugging_cr50.md +++ b/docs/case_closed_debugging_cr50.md @@ -429,10 +429,11 @@ power is otherwise lost. The `atboot` setting is the state of the write protect when Cr50 boots; it defaults to `follow_batt_pres`. -To change the `atboot` setting, add the `atboot` arg to the `wp` command: +To change the `atboot` setting, add the `atboot` arg to the end of the `wp` +command: ``` -cr50 > wp atboot [enable|disable|follow_batt_pres] +cr50 > wp [enable|disable|follow_batt_pres] atboot ``` You can query the write protect state with `gsctool`: -- cgit v1.2.1