From 87ba96c3b1691ddff51e89384270f0f847fd975f Mon Sep 17 00:00:00 2001 From: Vadim Bendebury Date: Wed, 25 Jan 2023 14:27:44 -0800 Subject: gsc_without_servod: clarify reset behaviour Mention that only certain reset types would trigger rescue attempts. BUG=None TEST=None Change-Id: I6c8b7d331f5491cd8561e168e6a3e4531dcd15cf Signed-off-by: Vadim Bendebury Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/4194953 Reviewed-by: Andrey Pronin --- docs/gsc_without_servod.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) 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 ` - 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: ``` -- cgit v1.2.1