servodtool: add device usb-comms

This new helper is designed to identify USB communication failures on
devices that are seemingly present on the system e.g. devices that
enumerated successfully, but have since then lost their data lines for
example, or where leakage current continues to present them as a valid
device when the connection has in actuality been cut off.

BUG=b:183250135
// servo v4 + ccd on grunt, all device working
TEST=sudo servoodtool device -s 0403C044-92D9C359 usb-comms && echo $?
0
     sudo servoodtool device -s C1706310714 usb-comms && echo $?
0

// servo v4 + ccd on grunt, ccd signal artifically broken (no SBU
// forwarding from grunt)
// shows that tool can identify ccd is broken but v4 remains operational
TEST=sudo servodtool device -s 0403C044-92D9C359 usb-comms && echo $?
Device with serial '0403C044-92D9C359' has USB comms issues. The device
has no langid
     sudo servoodtool device -s C1706310714 usb-comms && echo $?
0

Change-Id: Ife0d71264c7c948db637d0b75f1bf8be06918032
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/hdctools/+/2898037
Tested-by: Ruben Rodriguez Buchillon <coconutruben@chromium.org>
Reviewed-by: Brian Nemec <bnemec@chromium.org>
Commit-Queue: Ruben Rodriguez Buchillon <coconutruben@chromium.org>
1 file changed
tree: 9a50ab8e5b04bc282b423267270afe715cd7c11e
  1. beaglebone/
  2. chromeos/
  3. defs/
  4. docs/
  5. include/
  6. lib/
  7. polld/
  8. serial_server/
  9. servo/
  10. src/
  11. test/
  12. usbkm232/
  13. .gitignore
  14. getversion.sh
  15. LICENSE
  16. Makefile
  17. navbar.md
  18. OWNERS
  19. README.md
  20. setup.py
README.md

hdctools: Chrome OS Hardware Debug & Control Tools

This repository contains source code and documentation for the Servo debug boards. The tools in this repository require the full CrOS chroot, while the Standalone hdctools can be used without the chroot.

Servo

servod

Closed Case Debugging (CCD)

Power Measurement

Resources