DIY Suzy Cable not detected on TELIKS360

Hi,

I would like to ask what could be the reason my device TELIKS360 based is not detecting the home made Suzy Cable. I’ve followed the instructions from here [1]. I tried:

  1. loopback, tested all ports on the Chromebook itself
  2. with another linux machine

Nothing seems to work. I’ve followed the instructions on the website [2] to enable the CCD mode.

Any help on this issue is appreciated.

Regards.

References:
[1]: https://electronics.stackexchange.com/a/629436
[2]: Disabling Firmware Write Protection | MrChromebox.tech

2 possibilities:

  • wrong port or wrong cable orientation
  • issue with your cable

that’s it. nothing needs to be enabled for the ttyUSB ports to show up

I will upload pictures tomorrow but basically, I’ve made:

  1. A5: D+, B5: D-, A8: 22K resistor to VCC, B8: 56K resistor to VCC
  2. connected the VCC pins
  3. connected the GND pins.
  4. 56K resistor shows actual 56k3 (not sure if its an issue) it claims 5% is ok
  5. 22K resistor shows around 22k12
  6. the board itself is male board type as described in [1]
  7. the solder itself I’ve checked it with multimeter, pretty sure the contact is well made (I could double check it again tomorrow)

As for wrong port and orientation, I’ve tried all of them (two possibilities only)

  1. The device has only 2 USB-C ports and 2-USB-A ports. since the breakout board is big rectangle, you cannot use USB-C and USB-A on adjacent ports, so you have to connect with the ports from the other side, which I tried both ways.
  2. I’ve also tried using another linux device to connect USB-A end. There is no detection whatsoever. I’ve tried of course both USB-C ports in each orientation (4 combinations in total).

So I’m not sure whats going on. We could suspect that the cable is the problem but multimeter says otherwise :smiley:

Not sure what I could try more.

Regards.

there really aren’t any other options.

some boards don’t work in loopback, so put the USB-A end on another linux device. Disconnect all power from the Chromebook.

Hi, since my last update I’ve given up on building my own cable (not working). I’ve however in parallel ordered a ebay one, which arrived today:

I’ve followed the instructions and I get:

# ls /dev/ttyUSB*
/dev/ttyUSB0 /dev/ttyUSB1 /dev/ttyUSB2 /dev/ttyUSB3

I’ve ran the commands as instructed:

  • Step 1: Enabling Closed Case Debugging (CCD) (a while back, not now)
  • Step 2: Disabling Write Protection
    • echo "wp false" > /dev/ttyUSB0
    • echo "wp false atboot" > /dev/ttyUSB0
    • echo "ccd reset factory" > /dev/ttyUSB0
    • gsctool -a -I
      • state: Locked
      • not all flags are Y/Always some are IfOpened
      • AllowUnverifiedRo is Never
    • crossystem wpsw_cur returns 1 (instead of 0)

Any help on what I’ve might do wrong?

Kind regards

Some more context maybe:

  • I’ve already did Step 1: Enabling Closed Case Debugging (CCD) long time ago (like more than a week ago) should I do that again?
  • also, the cable as I plugged in before, was while fully logged in, it showed same USB[0-3], but after reboot it stopped showing it. The cable was connected via USB-C to USB-C. thats stopped working now. I’ve reconnected the cable via USB-A with USB-C. its strange that was working anod now not anymore like that. Unclear why. Now I’m afraid to restart again maybe USB-A also stops working :smiley:

Hi,

UPDATE: I’ve re-run all the procedure Step 1 and Step 2 and success, it works now. I’ve managed to get crossystem wpsw_cur to return 0. I think its good. and the rest looks okay now (always on all of them)

Continuing with the rest now

Kind regards.

Hi,

Update #2: a full success. I could change the boot flags and now finally no more beeping among other things :smiley:

Kind regards.