Dennis HilkLinux diagnosticsDE

USB controllers & peripherals

Silicon Labs default USB serial identity 10c4:ea60

A USB-to-serial family match whose tty association still needs runtime evidence.

Editorial source review: Share public profileOpen in the identification tool
On this page
  1. Overview & identity
  2. Driver & binding
  3. Firmware
  4. Read-only diagnostics
  5. Limitations & related issues
  6. References

Overview & identity

The checked cp210x table calls 10c4:ea60 the Silicon Labs factory default. This pair is reused across devices and cannot distinguish a CP210x variant, development board or branded cable by itself.

Curated identifiers
usb 10c4:ea60

A numeric match establishes a candidate family within the reviewed evidence. Marketing names, board variants, subsystem conditions and successful operation remain separate questions.

Driver & binding

cp210x probes serial interfaces and performs variant-specific initialization before the USB serial core exposes ttyUSB ports. A visible USB device without a tty does not prove that the serial interface completed probing.

  • cp210x — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

No host payload established here

No external firmware filename was established in the checked driver path. This does not describe firmware stored inside the device.

Inspect firmware packaging on your distribution

Read-only diagnostics

Run one displayed command at a time. Replace uppercase placeholders with the affected device, interface or module from your own output. Commands are never executed here. Read-only output can still contain private identifiers.

Locate the exact USB identity

lsusb -d 10c4:ea60

This read-only usbutils query normally needs no sudo. The bus/device number locates the USB function but does not establish an exact marketed product or active serial-interface driver.

Read one USB interface driver link

readlink /sys/bus/usb/devices/INTERFACE/driver

Replace INTERFACE with an existing interface such as 1-2:1.0, not only the whole-device name 1-2. This reads a symlink without sudo; a missing link leaves binding unconfirmed.

Inspect serial-port device ancestry

ls -l /sys/class/tty/ttyUSB*/device

Read symlinks without opening a tty or sending bytes. Existing paths can associate a ttyUSB node with its USB interface; an empty glob means no matching ttyUSB path was found.

Limitations & related issues

The default identity does not prove flow-control wiring, supported voltage or target configuration. A tty permission error is a different layer from a failed USB interface probe.

These guides are linked for relevant observations, not as known defects of every device in this family.

Choose a hardware diagnostic workflow · Inspect a log excerpt in Fix Lab

References

Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.