Normally issuing modprobe usbserial vendor=0xF00D product=0xDEAD creates a
/dev/ttyUSB$x. The parameters here are optional, so if you are
lucky and your device is curated by the linux community, modprobe usbserial might work. On my ubuntu home systems, this usually uses
the pl2302 driver or something similar.
This assumes a lot: that you have a working kernel with a bunch of
modules that are configured to load. Many distributions, including
Angstrom for beaglebone et al do this. opkg has a distribution
channel for the beaglebone, I am using the cloud9-image.
The cloud9-image produces an error about the kernel not recognizing
parameters for vendor and argument.
- bunch of uarts http://www.jerome-bernard.com/blog/2012/06/04/beaglebone-serial-ports-and-xbees/
- https://groups.google.com/forum/?fromgroups=#!topic/beagleboard/Kyq1NQOFSns
- http://www.sealevel.com/support/article/AA-00524/154/Resource-Center/Serial-Interfaces/How-to-configure-USB-serial-adapters-in-Linux.html
- https://groups.google.com/forum/?fromgroups=#!topic/beagleboard/_oDALGqphdU
- http://lakm.us/logit/2012/01/compile-usb-serial-modem-using-option-c-ubuntu-on-beagleboard-xm/ - The beaglebone already ships with many many kernel modules, including
spidev. If you do find yourself without modules (unlikely) there are numerous ways to get new ones. First tryopkg install kernel-modules-FOO. - http://cateee.net/lkddb/web-lkddb/USB_SERIAL.html
- http://lakm.us/logit/2012/01/compile-usb-serial-modem-using-option-c-ubuntu-on-beagleboard-xm/
- http://lakm.us/logit/2012/01/compile-usb-serial-modem-using-option-c-ubuntu-on-beagleboard-xm/
- http://www.sealevel.com/support/article/AA-00524/154/Resource-Center/Serial-Interfaces/How-to-configure-USB-serial-adapters-in-Linux.html
However, the ftdi_sio module is able to accept parameters.
modprobe ftdi_sio vendor=0x0a21 product=0x8001
This now creates the devices as expected. However, I get the
following errors in dmesg:
[309626.961791] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to
set baudrate
[309627.046783] ftdi_sio ttyUSB0: urb failed to clear flow control
[309629.082489] ftdi_sio ttyUSB0: error from flowcontrol urb
[309653.386657] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set
databits/stopbits/parity
[309653.484313] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to
set baudrate
[309653.569152] ftdi_sio ttyUSB0: urb failed to clear flow control
[309660.163940] ftdi_sio ttyUSB0: error from flowcontrol urb
[309695.287475] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set
databits/stopbits/parity
[309695.386383] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to
set baudrate
[309695.471618] ftdi_sio ttyUSB0: urb failed to clear flow control
[309697.508728] ftdi_sio ttyUSB0: error from flowcontrol urb
Misc:
i had the same problem. My Problem was an unpowered 4-port usb hub. When unplugging all other devices on the hub or plugging direct into the computer-port the problem was solved. If this was your problem ,too, then use an powerded usb-hub