summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-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:
```