summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMary Ruthven <mruthven@chromium.org>2019-05-07 13:21:41 -0700
committerchrome-bot <chrome-bot@chromium.org>2019-05-12 19:27:50 -0700
commit1fd8e3b0c5609612cf3339edab73bd7b7bb93f54 (patch)
treed8c2df1e26350265dc5e3f455724bc99ff383234
parent2bef7af80941cc793c0bf864d149233a470dc179 (diff)
downloadchrome-ec-1fd8e3b0c5609612cf3339edab73bd7b7bb93f54.tar.gz
ccd doc: link to suzyq instructions in cr50 setup
Plugging in suzyq and finding the cr50 console requires some knowledge about how CCD works. Link to the specific instructions from the main CCD doc, so people can find out how to do it. BUG=none BRANCH=none TEST=none Change-Id: I49ee6d8d937f61599f8b18378e5775eb78bacfcf Signed-off-by: Mary Ruthven <mruthven@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1599682 Reviewed-by: Aseda Aboagye <aaboagye@chromium.org>
-rw-r--r--docs/case_closed_debugging_cr50.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/docs/case_closed_debugging_cr50.md b/docs/case_closed_debugging_cr50.md
index 5aabff1b8f..a73003affa 100644
--- a/docs/case_closed_debugging_cr50.md
+++ b/docs/case_closed_debugging_cr50.md
@@ -67,8 +67,10 @@ functionality.
### Basic Steps for CCD setup
-1. Use instructions from the case\_closed\_debugging doc to connect to the cr50
- console.
+1. Use the general [setup](case_closed_debugging.md#Setup) instructions to
+ connect Suzy-Q and access the Cr50 console. The Cr50 console will be the
+ lowest `/dev/ttyUSB*` device created by Cr50 or
+ `/dev/google/<device name>/serial/Shell`
2. [Open CCD](#Open-CCD)