rln
Posts: 161
Joined: Wed Apr 09, 2014 1:43 pm
Location: Sweden
Contact: Website

Re: FTDI USB Serial Hangs

Thu Jun 19, 2014 9:50 am

astrapotro wrote:Hi,
I'm fighting with a FTDI-serial cable in raspberry for several months and still having troubles with it :evil:
paolom65 : Last firmware from next branch, 4C SD card, your kernel parameters in cmdline.txt, but still the serialport hangs !!
What's the solution for that? I've to terminate with this problem cause my project is stopped thanks to this issue.
Today i'll try with arch linux, and otherwise i'll migrate to Beaglebone Black.
I need help with this, please.
Hi
Which chip is embedded from in you cable? What is the name of the cable? Some work better than others. If you don't know you can try running this command:
dmesg | grep -iE "ftdi|ft23"
/Ronny Nilsson
Author of the robust Nard distro http://www.nard.se

astrapotro
Posts: 5
Joined: Fri Jan 17, 2014 7:49 am

Re: FTDI USB Serial Hangs

Fri Jun 20, 2014 7:11 am

rln wrote:
astrapotro wrote:Hi,
I'm fighting with a FTDI-serial cable in raspberry for several months and still having troubles with it :evil:
paolom65 : Last firmware from next branch, 4C SD card, your kernel parameters in cmdline.txt, but still the serialport hangs !!
What's the solution for that? I've to terminate with this problem cause my project is stopped thanks to this issue.
Today i'll try with arch linux, and otherwise i'll migrate to Beaglebone Black.
I need help with this, please.
Hi
Which chip is embedded from in you cable? What is the name of the cable? Some work better than others. If you don't know you can try running this command:
dmesg | grep -iE "ftdi|ft23"
/Ronny Nilsson
Hi , the chip is the FT232RL one , and the exact name of the cable is USB-RS485-WE-1800-BT
Thanks

rln
Posts: 161
Joined: Wed Apr 09, 2014 1:43 pm
Location: Sweden
Contact: Website

Re: FTDI USB Serial Hangs

Fri Jun 20, 2014 8:03 am

astrapotro wrote: Hi , the chip is the FT232RL one , and the exact name of the cable is USB-RS485-WE-1800-BT
Thanks
Hi
My systems use the same chip and is working flawlessy... (with speed 115,200 haven't tried any faster). Before you migrate to BeagleBone I could send you an SD-card image to try out if you like, for ruling things out?
/Ronny
Author of the robust Nard distro http://www.nard.se

astrapotro
Posts: 5
Joined: Fri Jan 17, 2014 7:49 am

Re: FTDI USB Serial Hangs

Fri Jun 20, 2014 10:06 am

rln wrote:
astrapotro wrote: Hi , the chip is the FT232RL one , and the exact name of the cable is USB-RS485-WE-1800-BT
Thanks
Hi
My systems use the same chip and is working flawlessy... (with speed 115,200 haven't tried any faster). Before you migrate to BeagleBone I could send you an SD-card image to try out if you like, for ruling things out?
/Ronny
You're lucky i think :D
Three questions: Do you keep the port opened or for each query to the port do you open and close?
How many often do you query the ftdi port? Which language do yo use to acces the ftdi ??

Many thanks for the offering of the image. I'll ask you if my solutions don't work.

rln
Posts: 161
Joined: Wed Apr 09, 2014 1:43 pm
Location: Sweden
Contact: Website

Re: FTDI USB Serial Hangs

Fri Jun 20, 2014 8:58 pm

astrapotro wrote: Three questions: Do you keep the port opened or for each query to the port do you open and close?
How many often do you query the ftdi port? Which language do yo use to acces the ftdi ??
I access the port with applications downloaded from net only. Are you trying to develop a program of your own? Then I would recommend the Serial Programming HOWTO
http://tldp.org/HOWTO/Serial-Programming-HOWTO/

Also, you need to describe your problem in detail for us to be able to help.
/Ronny
Author of the robust Nard distro http://www.nard.se

astrapotro
Posts: 5
Joined: Fri Jan 17, 2014 7:49 am

Re: FTDI USB Serial Hangs

Mon Jun 23, 2014 7:41 am

Hi,
Thanks for the how-to, direct to favorites.

Weel this weekend i've tested my java program in the beagleboneblack with the same fuc* results that i've gotten with the raspi.
My installation: The raspi attached to a 7 port usb-hub (2A) , with a 3G modem and two or more ftdi-serial cables attached to some boards via the usb-hub. The problem is still there and i don know what i'm doing wrong. Today i'll try to open and close the port each time that i've to query or send a command to the ftdi's boards.
This is a nightmare :oops:

garygid
Posts: 1
Joined: Thu Sep 18, 2014 9:45 am

Re: FTDI USB Serial Hangs

Tue Oct 28, 2014 2:31 am

Are you all using the virtual com port drivers, or the USB driver?

We are using a 4-port "USB2-H-1004" device from easysync (which uses the ftdi FT4232H chip) with the Raspbian virtual com driver, at 115.2k baud, but only open once and close once over days or weeks of the program running.

However, we have not been successful in opening the port at higher speeds, like 230.4k. Any suggestions, please?

manuloup
Posts: 1
Joined: Fri Jul 10, 2015 6:02 pm

Re: FTDI USB Serial Hangs

Fri Jul 10, 2015 6:13 pm

Hi,

I am running raspbian latest firmware 8Linux raspberrypi 4.0.7+ #802 PREEMPT) on a RPI B+ and I am some difficulties to make work my latest new device Xbee Powermeter (with domoticz).

When I plug the device I get this :

Code: Select all

[    1.983882] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
[    2.113814] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6001
[    2.115993] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.117907] usb 1-1.2: Product: Interface XBEE -> Compteur
[    2.119756] usb 1-1.2: Manufacturer: Cartelectronic
[    2.121589] usb 1-1.2: SerialNumber: C10124
[    7.650874] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
[    7.653137] usb 1-1.2: Detected FT232RL
[    7.776974] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0


This device is using the same ftdi_sio driver that my other RFXTRX433E device which works fine for a long time :

Code: Select all

[    2.213883] usb 1-1.4: new full-speed USB device number 5 using dwc_otg
[    2.337719] usb 1-1.4: New USB device found, idVendor=0403, idProduct=6001
[    2.339684] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.341500] usb 1-1.4: Product: RFXtrx433
[    2.343246] usb 1-1.4: Manufacturer: RFXCOM
[    2.345026] usb 1-1.4: SerialNumber: A1XZPRVH
[    7.808141] ftdi_sio 1-1.4:1.0: FTDI USB Serial Device converter detected
[    7.846753] usb 1-1.4: Detected FT232RL
[    7.893865] usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB2
So, my Xbee device is attached to USB0 but I can't make it work with Domoticz. It looks like nothing comes out from the ttyUSB0 and I suspect a problem with the driver or the configuration.

How can I make sure the driver is ok ? For your information, I tried the same XBee USB Powermeter on my laptop with windows and I get the informations coming.

Thanks in advance for your help.

Regards,

Manu

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

Re: FTDI USB Serial Hangs

Fri Jul 29, 2016 11:53 pm

I've been struggling with this issue for months now after deploying a handful of RPis (v2) to monitor APC UPSes. I am currently using the SIIG Serial to USB adapter which has a FTDI FT232BM chip. I noticed, using FTDI's programming software, that the chip has attributes to use USB 1.1 and USB 2.0. Of course the RPi will opt for the faster speed by default.

I can confirm that adding dwc_otg.speed=1 to the cmdline.txt does indeed allow the chip to work flawlessly. However, in my case, once I add that attribute to the cmdline.txt it also doesn't allow me to plug in a usb and keyboard since these are high-speed USB devices.

I haven't tried using a USB 1.1 hub (I don't have one handy), but I assume that this should work since it would force the FT232BM chip to work at the 1.1 speed rather than 2.0.

I have researched this problem extensively and it looks to be a 10 year old problem https://lists.debian.org/debian-amd64/2 ... 00040.html and https://www.linuxquestions.org/question ... 289-print/

And it continues today (as recently as April 2016): http://www.spinics.net/lists/linux-usb/msg139739.html

Just a quick info on what I've tested this on:

Code: Select all

[email protected] /dev $ sudo cat /proc/version
Linux version 4.1.13-v7+ ([email protected]) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #826 SMP PREEMPT Fri Nov 13 20:19:03 GMT 2015
and

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
and

Code: Select all

[[email protected] squid]# cat /proc/version
Linux version 4.4.7-300.fc23.i686 ([email protected]) (gcc version 5.3.1 20151207 (Red Hat 5.3.1-2) (GCC) ) #1 SMP Wed Apr 13 03:22:17 UTC 2016
I'll also include the error codes I've gotten:

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)
The next one is when I connect two of the SIIG cables... sometimes both begin to get errors and some even revert to the dreaded DEBUG state!!! (This got me so frustrated at the beginning)...

Code: Select all

[email protected]:~ $ sudo lsusb -vd 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 (error)
  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:     0x0538
  (Bus Powered)
Lastly I'll attach what I get when I attempt to communicate via Serial to a switch:

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
This was driving me crazy for a long time and what I have found has given me a little piece of mind, but it still bothers the h$#% out of me. My last idea is to be able to program the chip to only use USB 1.1, but I am just barely reading up engineering manuals on how to do that and will post if it's even remotely possible to do this...
---Nacho---
Are you learning?... Good, so am I!

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

Re: FTDI USB Serial Hangs

Sat Jul 30, 2016 6:37 pm

iggynach wrote:I've been struggling with this issue for months now after deploying a handful of RPis (v2) to monitor APC UPSes. I am currently using the SIIG Serial to USB adapter which has a FTDI FT232BM chip.
You shouldn't need the dwc_otg.speed hack any more. It was an issue that went away in 2013 or so with the Raspberry Pi kernel.

I think your problem lies elsewhere.
I'll also include the error codes I've gotten:

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:
 ...
  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)
I think your serial cables are using counterfeit FTDI chips. Real ones give this lsusb -v output:

Code: Select all

 ...
  idVendor           0x0403 Future Technology Devices International, Ltd
  idProduct          0x6001 FT232 USB-Serial (UART) IC
  bcdDevice            6.00
  iManufacturer           1 
  iProduct                2 
  iSerial                 3 
 ...
Notice the iProduct and iSerial entries, where yours reported (error)? The two known-counterfeit ones that I have (bought from dx.com and ebay very cheaply) give the same error as yours.

When you plug your serial adapter in, does the dmesg output include SerialNumber: DDDDDDDD, with a unique identifier? Counterfeit ones return zero. Another clue might be if you bought FT232BM adapters recently. FTDI discontinued the BM variant some time ago. Yet another clue is how much you paid for the adapter: real FTDI chips are quite expensive - around US $4 each in quantity - so if you paid less than say US $15 for the cable, it's probably fake. It might not even be a real SIIG cable you have; counterfeit electronics are a big problem.
‘Remember the Golden Rule of Selling: “Do not resort to violence.”’ — McGlashan.

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

Re: FTDI USB Serial Hangs

Mon Aug 01, 2016 4:28 pm

You shouldn't need the dwc_otg.speed hack any more. It was an issue that went away in 2013 or so with the Raspberry Pi kernel.

I think your problem lies elsewhere.

I think your serial cables are using counterfeit FTDI chips. Real ones give this lsusb -v output:

Code: Select all

 ...
  idVendor           0x0403 Future Technology Devices International, Ltd
  idProduct          0x6001 FT232 USB-Serial (UART) IC
  bcdDevice            6.00
  iManufacturer           1 
  iProduct                2 
  iSerial                 3 
 ...
Interesting, I would never have thought counterfeit chips to be the problem. I must note though that I get different information when I run lsusb -v and sudo lsusb -v. Also, the errors are sporadic and usually occur when serial communication is attempted. When I run sudo lsusb -v before the cable gets all screwy, I get this output:

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)
When I run lsusb -v at the point that I initially plug in the adapter I get:

Code: Select all

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 
  iProduct                2 
  iSerial                 3 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
I also would like to note that I downloaded the FTDI programming utility for FTDI chips http://www.ftdichip.com/Support/Utilities.htm#FT_PROG (for Windows) and the chip is read perfectly. Can this be done with counterfeits as well? I am able to flash it and change attributes using the utility very easily...
Notice the iProduct and iSerial entries, where yours reported (error)? The two known-counterfeit ones that I have (bought from dx.com and ebay very cheaply) give the same error as yours.

When you plug your serial adapter in, does the dmesg output include SerialNumber: DDDDDDDD, with a unique identifier? Counterfeit ones return zero. Another clue might be if you bought FT232BM adapters recently. FTDI discontinued the BM variant some time ago. Yet another clue is how much you paid for the adapter: real FTDI chips are quite expensive - around US $4 each in quantity - so if you paid less than say US $15 for the cable, it's probably fake. It might not even be a real SIIG cable you have; counterfeit electronics are a big problem.
For the dmesg output, again before the cable gets all weird, I get this output:

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

As for the price of the cables, they each came out to about $25 each cable (is this about right for a legitimate cable? Here is the link to the cables I bought from Amazon: https://www.amazon.com/SIIG-JU-CB1S12-S ... -CB1S12-S3

I mean if these cables are counterfeit, they are pretty darn good counterfeits. The cables have zero problems on Windows (haven't tried them on a Mac). It's only when I try to use them in Linux that they give me problems... Thank you for the info, though. I'll need to continue digging to confirm that indeed these are counterfeit...

PS: I registered the cables with SIIG and the serial numbers were valid... Again, it amazes me if they are still counterfeit after all of this :shock:
---Nacho---
Are you learning?... Good, so am I!

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

Re: FTDI USB Serial Hangs

Tue Aug 02, 2016 2:04 pm

Okay, probably not counterfeit, then. Your output just matched what I get out of counterfeit ones.

This has been a real problem for FTDI: the counterfeit chips are very hard to detect, and are actually pretty okay usb→serial interfaces.
‘Remember the Golden Rule of Selling: “Do not resort to violence.”’ — McGlashan.

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

Re: FTDI USB Serial Hangs

Wed Aug 10, 2016 12:19 am

scruss wrote:Okay, probably not counterfeit, then. Your output just matched what I get out of counterfeit ones.

This has been a real problem for FTDI: the counterfeit chips are very hard to detect, and are actually pretty okay usb→serial interfaces.
Hey scruss,

I've tried these cables on a multitude of RPi distros (Kali Linux, ArchLinux, FedBerry, etc...) and the same result occurs! I'm pretty frustrated now. The problem seems to stem from the the otg device used in the RPi because in depth research shows many people having issues with other USB devices not just USB-Serial adapters... Using the cables on a Centos 6.8 i386 (Kernel 2.6) seems to work flawlessly...

Would you be able to provide me a list USB-Serial cables that have functioned perfectly for you? (i.e. cables not using FTDI FT232BM, or any other discontinued device for that matter...) I would really appreciate it...
---Nacho---
Are you learning?... Good, so am I!

peterz
Posts: 1
Joined: Thu May 10, 2018 3:26 pm

Re: FTDI USB Serial Hangs

Thu May 10, 2018 3:31 pm

I had the same problem and spent many hours reading forum messages and trying different approaches without any success.
I had cascaded hubs and what finally helped: rearranging the same hubs physically using another cable.
So you might want to check cables, shielding and power supply, avoid ground loops etc.

Return to “Interfacing (DSI, CSI, I2C, etc.)”