In order to get access to the AP and EC consoles or reprogram a Chrome OS device's firmware or BIOS without using the AP, older Chrome OS devices required opening the device to get access to a debug header used by Servo. These servo headers are frequently unpopulated on production units.
Newer Chrome OS devices have a secure microcontroller(Google Security Chip or GSC) in them which runs an embedded OS called Cr50 or Ti50. Among other capabilities, this chip allows developers to securely debug the device without physically opening it.
Current GSC capabilities allow read/write access to a UART on the AP and a UART on the EC, as well as a SPI interface (normally used to access the flash chips) and an I2C interface (normally used to access INAs, but may be used to flash the EC). Closed Case Debug replaces the capabilities that previously relied on the servo header. Outside of ccd, the servo USB connection also provides:
This document describes basic “Closed Case Debug” (CCD) and debug cable (SuzyQ) information. For more in depth instructions on using CCD see the following:
The GSC code uses the microcontroller’s USB interface to expose its debugging functionality. This interface can be reached via a special USB Type-C cable called “SuzyQ” on one of the system’s ports.
To put GSC into debug mode, the SuzyQ cable has to present itself as a Debug Accessory (see Chapter B of the USB Type-C Specification). When this cable is detected the system will connect the GSC full-speed USB2.0 interface to the SBU pins of the Type-C connector. Note that this prevents use of the DisplayPort alternate-mode (which also uses the SBU pins) but preserves regular USB operation on the port.
Once the SuzyQ cable is connected, GSC makes several USB endpoints available to the host to communicate with the consoles, to program firmware, etc. More details about [setting up GSC][GSC CCD] and these CCD software interfaces can be found in the documentation section of the EC codebase.
SuzyQ is a cable that tells the GSC to go into debug mode. SuzyQ includes a USB hub in the cable, which allows the host computer to access both the debug interface (on the SBU pins) and any gadget-mode interfaces exposed by the device-under-test (for example an ADB interface for debugging Android applications). Reference schematics are available for the SuzyQ. To run Tauto or TAST tests, you will generally need to attach a USB-to-ethernet adapter as well. While you could try to use wifi, any test that switches boot modes (i.e. normal -> dev) will erase the wifi settings and fail.
Historically, this cable used to be available for purchase from Sparkfun, but as of late 2021, this product will likely be unavailable for the foreseeable future due to a supply chain shortage. See the instructions below for making your own.
NOTE: The cable will generally only work in one port and one orientation. If it doesn't work try the other port, or flip the connector. Check the Chrome OS device list for more details about the specific device you are using.
To see if it worked you can check the presence of
/dev/ttyUSB* devices, or monitor
lsusb for GSC device enumeration:
# H1/Cr50 (chroot) $ watch -n 1 "lsusb | grep 18d1:5014" # D2/Ti50 (chroot) $ watch -n 1 "lsusb | grep 18d1:504A"
One needs a USB Type-C Male breakout board and some way of connecting the other end to a computer’s USB port (like a Type A Male port).
|Type C Male||Other host (Type A Male)|
|A8 (SBU 1)||D+|
|B8 (SBU 2)||D-|
|A4, A9, B4, B9 (VBUS)||VBUS, 5V|
|A5 (CC1)||22 kΩ resistor to VBUS|
|B5 (CC2)||56 kΩ resistor to VBUS|
|A1, A12, B1, B12 (GND)||GND|
Note that unlike the Sparkfun SuzyQable, this cable does not include an internal USB hub, so you won't be able to use the same cable for ADB and CCD at the same time.
There is a video tutorial on making your own SuzyQable available for those interested.
Servo v4 also has CCD capabilities (routing SBU lines to the USB host, signaling on the CC lines debug accessory mode), so it can be used as an alternative to the SuzyQ cable. During debugging, Servo v4 will normally allow the device-under-test to act as a USB host, providing it with an Ethernet interface and USB flash device that may be used for a recovery image. Servo v4 allows USB Type-C connection automation (both data and charging). Servo v4 also has a keyboard emulator.
To use most of the features of CCD, on your Linux workstation you need to build ChromiumOS and create a chroot environment. It’s possible to use a subset of CCD without that; see the Raw Access section.
The hdctools (Chrome OS Hardware Debug & Control Tools) package contains several tools needed to work with
servod. Make sure the latest version is installed in your chroot:
(chroot) $ ~/chromiumos/src/scripts/update_chroot
On your workstation,
servod must also be running to communicate with GSC:
(chroot) $ sudo servod -b "$BOARD"
CPU/AP UART can be accessed by running:
(sdk root) $ minicom -D "$(cros_sdk -- dut-control -o cpu_uart_pty)"
Note that on a normal install of Chrome OS the UART is not normally used. The device must be in Developer Mode or using a custom OS.
On most x86 production images the UART drivers are also disabled for performance reasons, but they can be added back in with a custom AP firmware.
(sdk root) $ minicom -D "$(cros_sdk -- dut-control -o ec_uart_pty)"
The console is read only, unless you have [opened CCD][GSC CCD]. The console will show various debug mesages from charging, keyboard scanning, power state.
GSC itself has a console available, but most commands are locked by default for security:
(sdk root) $ minicom -D "$(cros_sdk -- dut-control -o gsc_uart_pty)"
Most CCD features are locked down by default on GSC. You need to enable them before you can use them. For information on setting up GSC CCD see the [GSC CCD setup doc][GSC CCD].
A subset of these features (e.g., UART lines) can be accessed without a
Once the SuzyQ is plugged in, three
/dev/ttyUSB devices will enumerate:
The “Closed Case Debugging” column in the Chrome OS device list indicates whether CCD is supported.
If the device is ARM, the CPU/AP UART works by default in dev mode (you should see a login prompt). x86 devices disable it for performance / power reasons, but UART can be re-enabled with a custom firmware.