summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVadim Bendebury <vbendeb@chromium.org>2023-01-25 14:27:44 -0800
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>2023-01-25 23:22:42 +0000
commit87ba96c3b1691ddff51e89384270f0f847fd975f (patch)
tree110424fc26d34cb1113dc72ac5e6e70e52a7891a
parent8ffb055f80a09e9d3b6ad5a285e435cbcc0629ad (diff)
downloadchrome-ec-release-R111-15329.B-cr50_stab.tar.gz
Mention that only certain reset types would trigger rescue attempts. BUG=None TEST=None Change-Id: I6c8b7d331f5491cd8561e168e6a3e4531dcd15cf Signed-off-by: Vadim Bendebury <vbendeb@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/4194953 Reviewed-by: Andrey Pronin <apronin@chromium.org>
-rw-r--r--docs/gsc_without_servod.md7
1 files changed, 6 insertions, 1 deletions
diff --git a/docs/gsc_without_servod.md b/docs/gsc_without_servod.md
index c4bdad0914..f09f4b1290 100644
--- a/docs/gsc_without_servod.md
+++ b/docs/gsc_without_servod.md
@@ -171,7 +171,12 @@ Then to rescue the GSC chip, do the following:
- disconnect terminal from the GSC console TTY device
- invoke `brescue.sh <path to the firmware image> <GSC console TTY device>`
- generate GSC reset pulse using instructions based on the adapter used to
- connect to the GSC ([Servo Micro](#reset-gsc-using-servo-micro) or [C2D2](#reset-gsc-using-c2d2))
+ connect to the GSC ([Servo Micro](#reset-gsc-using-servo-micro) or
+ [C2D2](#reset-gsc-using-c2d2)). Another way to reset the GSC is to
+ disconnect/reconnect the battery.
+
+**Note that resetting Dauntless using the key combo will not trigger a rescue
+ attempt.**
Here is an example of a Ti50 rescue session:
```