Instantly share code, notes, and snippets.

Embed
What would you like to do?
errors using serial port using naive

Using beaglebone with serial devices with usbserial and ftdi_sio

Using usbserial

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.

Using ftdi_sio

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:

[309585.157897] usbcore: registered new interface driver ftdi_sio
[309585.229339] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
[309618.595153] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity
[309618.693115] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
[309618.778869] ftdi_sio ttyUSB0: urb failed to clear flow control
[309618.853057] ftdi_sio ttyUSB0: urb failed to clear flow control
[309619.570465] ftdi_sio ttyUSB0: error from flowcontrol urb
[309626.863403] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity
[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
@ingof

This comment has been minimized.

ingof commented Jan 13, 2016

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment