Dennis HilkLinux diagnosticsDE

USB controllers & peripherals

FTDI USB serial identity 0403:6001

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 upstream table resolves FTDI_VID and FTDI_8U232AM_PID to 0403:6001. This identifies a supported USB identity, not a verified cable brand, authenticity or every chip revision using it.

Curated identifiers
usb 0403:6001

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

ftdi_sio handles serial interfaces through the USB serial core, typically producing a ttyUSB node. Interface binding and permissions on the resulting tty are separate from recognizing the VID/PID.

  • ftdi_sio — 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 0403:6001

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

USB identity cannot prove the electrical voltage level, wiring or connected target. Never open a console or transmit bytes merely to test a driver match; this profile only lists binding and tty associations.

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.