kalehrl
Posts: 350
Joined: Tue Jul 24, 2012 10:49 am

Re: USB/serial converters (not very) broken on Pi

Fri Jul 26, 2013 6:54 am

No, I didn't try the fix you mention because since the last corruption issue, I lost will to fiddle with my raspi for some time.
Next time I pick it up, I will try to get filesystem to USB flash disk, and see if there's corruption there.
USB has been dodgy since day 1 for me.
My keyboard and mouse didn't function properly (sticky keys problem) and I had to use dwc_otg.speed=1 which crippled USB transfer speeds.
Then I bought a gamepad and discovered that it won't work at all unless I removed dwc_otg.speed=1 from the command line. :lol:
It was only after fiq_split kernel appeared that I was able to use both my keyboard and my gamepad.
If I remember correctly, it took a whole year to make some USB devices function properly and it is something essential for a normal usage of any device don't you think?
But that's not the end of the story.
Since the installation of fiq_split kernel, the ethernet would just die after a few days (raspi not reachable via ssh).
Some time after that, filesystem corruption kicked in and it was game over for some time for me and raspi.
If I remember correctly, ethernet is dependent on USB bus because it is attached to it so USB problems affect ethernet as well.

Avio
Posts: 2
Joined: Sun Jul 28, 2013 4:11 pm

Re: USB/serial converters (not very) broken on Pi

Sun Jul 28, 2013 4:26 pm

I'm also having USB problems with kernel 3.6.11+ #512. My raspberry should be a fileserver attached to a all-in-one USB docking station (like this one http://goo.gl/wlLPfk), however the docking station is recognized only if I set dwc_otg.speed=1 kernel option in /boot/cmdline.txt.

I'm now using a setup with a powered USB hub in the middle, but the problem exists also with a direct connection.

Any news about this bug?

Regards
Avio

azbest_hu
Posts: 8
Joined: Thu Sep 20, 2012 9:18 am

Re: USB/serial converters (not very) broken on Pi

Sat Oct 19, 2013 3:36 pm

Yeah, it is still buggy.
With 2013-09-25-wheezy-raspbian I got HW_CFG_LRST_ and MII_ACCESS failures after a half minute when I start using the attached Alcor micro AU9540 (058F:9540) smartcard reader. The same failure occures with direct to raspi-card reader and raspi-external hub-card reader setup.

edit: i had to add dwc_otg.speed=1 to get it working. The limited usb speed may be a blocker for my usb dvb-t tuners. :roll:

DeadRinger
Posts: 4
Joined: Thu Mar 14, 2013 6:39 pm

Re: USB/serial converters (not very) broken on Pi

Sun Nov 24, 2013 10:15 am

Has the USB serial port freezing been fixed yet? I am using an FTDI convertor and whether using Python or minicom, data is lost or freezes after a very short while. I tried the dwc_otg.speed=1 suggestion, but this causes the mouse and keyboard to become inoperative.

I have the latest updates and firmware upgrades.

Any suggestions?

Best regards
DeadRinger

cavoknosig
Posts: 18
Joined: Wed May 08, 2013 8:13 am

Re: USB/serial converters (not very) broken on Pi

Fri Dec 06, 2013 9:09 am

i'm also looking to get a stable DMX master running. currently trying via an ftdi usb serial interface i had already laying around.
but i'm getting sporadic freezes. watchdog could be one workaround but the reboots eventually could corrupt the sd card, so not really a solution...

has anybody come up with a stable DMX busmaster via GPIO yet?
or is anyone recommending tweaks to get the ftdi stable?

thanks a lot!

User avatar
scrishton
Posts: 49
Joined: Mon May 07, 2012 8:48 pm
Location: Settle, in the Yorkshire Dales
Contact: Website

Re: USB/serial converters (not very) broken on Pi

Fri Dec 06, 2013 11:25 am

cavoknosig wrote:i'm also looking to get a stable DMX master running. currently trying via an ftdi usb serial interface i had already laying around.
but i'm getting sporadic freezes. watchdog could be one workaround but the reboots eventually could corrupt the sd card, so not really a solution...

has anybody come up with a stable DMX busmaster via GPIO yet?
or is anyone recommending tweaks to get the ftdi stable?

thanks a lot!

I'm currently (as I type this) running four FTDI four port USB to RS422 cards with a Pi, controlling 17 XDCAM video recorders in a studio. It has been working reliably and consistently for several months now, but on an old release of Raspian...

3.6.11+ #389 PREEMPT Wed Mar 6 12:43:30 GMT 2013 armv61 GNU/Linux

and with
dwc_otg.fiq_fix_enable=1 dwc_otg.microframe_schedule=0
in /boot/cmdline.txt

If I update to later versions I have problems with the keyboard not responding when several ports are opened.

I haven't tried updating it recently. DMX sounds like a good next project for me.

Simon R.

User avatar
Hayden_James
Posts: 24
Joined: Thu Dec 19, 2013 10:10 am
Contact: Website

Re: USB/serial converters (not very) broken on Pi

Mon Feb 03, 2014 11:42 am

Sooooo many USB problem related threads. No fixes. :/

User avatar
scruss
Posts: 2819
Joined: Sat Jun 09, 2012 12:25 pm
Location: Toronto, ON
Contact: Website

Re: USB/serial converters (not very) broken on Pi

Mon Feb 03, 2014 1:35 pm

Hayden_James wrote:Sooooo many USB problem related threads. No fixes. :/
I've been using FTDI, Prolific and SiLabs USB→Serial connectors with the Raspberry Pi and Raspbian with no problems for at least the last six months. Yeah, there used to be issues, but everything that affected me has been cleaned up.

You've got the latest firmware, right?
‘Remember the Golden Rule of Selling: “Do not resort to violence.”’ — McGlashan.

User avatar
Hayden_James
Posts: 24
Joined: Thu Dec 19, 2013 10:10 am
Contact: Website

Re: USB/serial converters (not very) broken on Pi

Mon Feb 03, 2014 6:10 pm

Yes latest firmware. Properly powered. all depends on what your using the Pi for, USB still flawed. Using a 2.1 amp, 2.0 amp and 1.5 amp and 3 USB wifi dongles. (3 RPi board, I thought I had bad hardware, trchincall I do... All three) Glad it works for your needs it works fine for some of mine as well and some of the fixes in threads has improved all 3 of my Pi boards so that keyboard at least does not disconnect randomly and sound for one I have setup for media is clear. But USB is certainly as one thread calls it the elephant in the room.

jdb
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2215
Joined: Thu Jul 11, 2013 2:37 pm

Re: USB/serial converters (not very) broken on Pi

Mon Feb 03, 2014 6:14 pm

I'm sorry, what part of your post is relevant to USB-serial adapters not working on Pi?
Rockets are loud.
https://astro-pi.org

User avatar
Hayden_James
Posts: 24
Joined: Thu Dec 19, 2013 10:10 am
Contact: Website

Re: USB/serial converters (not very) broken on Pi

Mon Feb 03, 2014 6:28 pm

None. I've read enough recent deadend threads to realize it makes no sense posting spcifics just to go in circles. Plus I'm posting via mobile today, I will blog post a video of the issue in action once I get back.

Cheers!

gsh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1468
Joined: Sat Sep 10, 2011 11:43 am

Re: USB/serial converters (not very) broken on Pi

Sat Feb 22, 2014 7:21 am

P33M's latest fixes for the USB have been pushed into the BRANCH=next firmware update

http://www.raspberrypi.org/forum/viewto ... 85#p509285

Try again, this should now be working _much_ better
--
Gordon Hollingworth PhD
Raspberry Pi - Director of Software Engineering

User avatar
iggynach
Posts: 15
Joined: Sat Apr 16, 2016 12:03 am
Location: Whittier, CA

Re: USB/serial converters (not very) broken on Pi

Wed Aug 10, 2016 7:21 pm

Has this issue been resolved for FTDI chips using the FT232BM variant? I posted something a while back viewtopic.php?f=28&t=154379&p=1009930#p1009930 and replied on viewtopic.php?f=44&t=8010&p=1017893#p1017893 showing issues still occurring on recent Raspbian, ArchLinux, KaliLinux, Fedberry distributions (currently using RPi 2 Model B).

The temporary patch (adding dwc_otg.speed=1) works but in my case causes two problems:
  • A. It significantly reduces the ethernet port speed
  • B. I have other devices connected (APC UPS) that are high speed and cease to function once patch is applied
As indicated in my post and replies (see urls), I'm very confident that these SIIG USB-Serial adapters are not counterfeit and the problem seems to worsen when you connect two of these adapters into the same RPi. I am running out of ideas of how to fix this issue (short of buying a whole new set of knowingly working adapters) and frustration is rising.

Any help will do. I will post pertinent information below...

Code: Select all

[email protected]:~ $ sudo cat /proc/version
Linux version 4.4.13-v7+ ([email protected]) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #894 SMP Mon Jun 13 13:13:27 BST 2016
Post serial communication attempt:

Code: Select all

    [email protected]:~ $ sudo lsusb -v -d 0403:6001

    Bus 001 Device 010: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
    Device Descriptor:
      bLength                18
      bDescriptorType         1
      bcdUSB               1.10
      bDeviceClass            0 (Defined at Interface level)
      bDeviceSubClass         0
      bDeviceProtocol         0
      bMaxPacketSize0         8
      idVendor           0x0403 Future Technology Devices International, Ltd
      idProduct          0x6001 FT232 USB-Serial (UART) IC
      bcdDevice            4.00
      iManufacturer           1 FTDI
      iProduct                2 (error)
      iSerial                 3 (error)
      bNumConfigurations      1
      Configuration Descriptor:
        bLength                 9
        bDescriptorType         2
        wTotalLength           32
        bNumInterfaces          1
        bConfigurationValue     1
        iConfiguration          0
        bmAttributes         0xa0
          (Bus Powered)
          Remote Wakeup
        MaxPower               44mA
        Interface Descriptor:
          bLength                 9
          bDescriptorType         4
          bInterfaceNumber        0
          bAlternateSetting       0
          bNumEndpoints           2
          bInterfaceClass       255 Vendor Specific Class
          bInterfaceSubClass    255 Vendor Specific Subclass
          bInterfaceProtocol    255 Vendor Specific Protocol
          iInterface              2 (error)
          Endpoint Descriptor:
            bLength                 7
            bDescriptorType         5
            bEndpointAddress     0x81  EP 1 IN
            bmAttributes            2
              Transfer Type            Bulk
              Synch Type               None
              Usage Type               Data
            wMaxPacketSize     0x0040  1x 64 bytes
            bInterval               0
          Endpoint Descriptor:
            bLength                 7
            bDescriptorType         5
            bEndpointAddress     0x02  EP 2 OUT
            bmAttributes            2
              Transfer Type            Bulk
              Synch Type               None
              Usage Type               Data
            wMaxPacketSize     0x0040  1x 64 bytes
            bInterval               0
    Device Status:     0x3538
      (Bus Powered)

Code: Select all

[email protected]:~ $ dmesg

[16712.713722] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity
[16712.713958] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
[16712.714194] ftdi_sio ttyUSB0: urb failed to clear flow control
[16712.715053] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[16712.723567] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[16712.745942] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[16718.147843] ftdi_sio ttyUSB0: failed to get modem status: -32
[16718.148177] ftdi_sio ttyUSB0: error from flowcontrol urb
Pre serial communication attempt:

Code: Select all

    Bus 001 Device 013: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
    Device Descriptor:
      bLength                18
      bDescriptorType         1
      bcdUSB               1.10
      bDeviceClass            0 (Defined at Interface level)
      bDeviceSubClass         0
      bDeviceProtocol         0
      bMaxPacketSize0         8
     idVendor           0x0403 Future Technology Devices International, Ltd
      idProduct          0x6001 FT232 USB-Serial (UART) IC
      bcdDevice            4.00
      iManufacturer           1 FTDI
      iProduct                2 USB to Serial Cable
      iSerial                 3 FT920101
      bNumConfigurations      1
      Configuration Descriptor:
        bLength                 9
        bDescriptorType         2
        wTotalLength           32
        bNumInterfaces          1
        bConfigurationValue     1
        iConfiguration          0
        bmAttributes         0xa0
          (Bus Powered)
          Remote Wakeup
        MaxPower               44mA
        Interface Descriptor:
          bLength                 9
          bDescriptorType         4
          bInterfaceNumber        0
          bAlternateSetting       0
          bNumEndpoints           2
          bInterfaceClass       255 Vendor Specific Class
          bInterfaceSubClass    255 Vendor Specific Subclass
          bInterfaceProtocol    255 Vendor Specific Protocol
          iInterface              2 USB to Serial Cable
          Endpoint Descriptor:
            bLength                 7
            bDescriptorType         5
            bEndpointAddress     0x81  EP 1 IN
            bmAttributes            2
              Transfer Type            Bulk
              Synch Type               None
              Usage Type               Data
            wMaxPacketSize     0x0040  1x 64 bytes
            bInterval               0
          Endpoint Descriptor:
            bLength                 7
            bDescriptorType         5
            bEndpointAddress     0x02  EP 2 OUT
            bmAttributes            2
              Transfer Type            Bulk
              Synch Type               None
              Usage Type               Data
            wMaxPacketSize     0x0040  1x 64 bytes
            bInterval               0
    Device Status:     0x0000
      (Bus Powered)

Code: Select all

    [249089.332202] usb 1-1.2: new full-speed USB device number 13 using dwc_otg
    [249089.457981] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6001
    [249089.458015] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [249089.458032] usb 1-1.2: Product: USB to Serial Cable
    [249089.458047] usb 1-1.2: Manufacturer: FTDI
    [249089.458063] usb 1-1.2: SerialNumber: FT920101
    [249089.468546] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
    [249089.468816] usb 1-1.2: Detected FT232BM
    [249089.470214] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB1

---Nacho---
Are you learning?... Good, so am I!

Return to “Troubleshooting”