I wanted to debug my chromebook so I was looking for SuzyQable which enables to activate debug features on chromebook. Unfortunately this cable is hard to get in my location so after noticing this https://chromium.googlesource.com/chromiumos/third_party/hdctools/+/master/docs/ccd.md#making-your-own-suzyq official google guide to make own diagnostic cable I decided to give it a try. At first I was a bit sceptical about it as the schematic diagram of SuzyQable (https://cdn.sparkfun.com/assets/9/e/f/8/2/951-00273-01_20180607_suzyqable_SCH_1.pdf) is far more advanced than what google is saying. However the hub seems not be necessary there. So I bought usb type A and C breadboards and connected pins exactly as described on chromium page linked above although with one caveat – I currently don't have 56K Ohm resistors so I connected in series:
56k Ohm = 22 + 22 + 10 + 1 + 1 [k ohm]
Once the whole setup is connected I measured voltage on CC1 & CC2 pins:
Voltage on CC1: Position 1 -> 4,81V; Position 2 -> 4,78 V
Voltage on CC2: Position 1 -> 0,44V; Position 2 -> 0,46V
Unfortunately after plugging it in the device is not recognizable as tty serial USB one, which should be visible under /dev/ttyUSBx
Obvious problems which I already eliminated:
-
They say chromebooks discover this debug interface in only on usb type c orientation so I already tried both, same effect.
-
I have usb to serial module (FT232R) I connected it to both devices (chromebook and Ubuntu host) and it was discovered as ttyUSB0 immediately. So this means both devices are serial capable.
Questions:
-
I wonder if the series connection, of 56 k ohm resistor, introducing voltage drop can be responsible for the issue?
-
Is the hub which is on sparkfun schematic really superfluous and can be ommited?
-
What voltage levels are needed for USB to be discoverable as serial device?
UPDATE:
Schematic diagram of my connection (according to chromium page)
Picture of real connections on a breadboard
My Chromebook model is: Acer Chromebook 311 bobba
PS: Chromebook sometimes log weird dmesg messages like:
"PDLOG (date here) P1 SINK (not charging) charger ?? 5000mV max 5000 mV / 500 mA"
Ubuntu on the other hand logs:
"usb usb1-port3: over current condition"
"usb usb1-port4: over current condition"
Yes I have no idea why it mentions two ports if I only tinker with one!
Thanks for any advice!
Best Answer
I have managed to root cause this - the problem was the USB male to male cable I was using, basically it doesn't pass both CCx signals but just one and connect the other to this.