Analog Discovery 2 / Ubuntu 16.04 / FTDI immediately disconnects

[Geoff]

I've installed the latest AD2 debs on an Ubuntu 16.04 system. I've got two AD2s around; both behave the same way (with different ports / cables tested too). From dmesg:

[2427454.029043] usb 1-5: SerialNumber: 210321A7FC47
[2427454.037097] ftdi_sio 1-5:1.0: FTDI USB Serial Device converter detected
[2427454.037130] usb 1-5: Detected FT232H
[2427454.042080] usb 1-5: FTDI USB Serial Device converter now attached to ttyUSB0
[2427454.049152] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[2427454.049174] ftdi_sio 1-5:1.0: device disconnected

 

[2427880.873236] usb 1-5: SerialNumber: 210321A80041
[2427880.881243] ftdi_sio 1-5:1.0: FTDI USB Serial Device converter detected
[2427880.881269] usb 1-5: Detected FT232H
[2427880.886428] usb 1-5: FTDI USB Serial Device converter now attached to ttyUSB0
[2427880.895309] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[2427880.895329] ftdi_sio 1-5:1.0: device disconnected

 

This is consistent behaviour; I see similar problems reported with the RPIs - but should this happen with a full Linux desktop?

Are there any udev rules I could add to help the issue? Or is it a driver/hub problem?

 

[JColvin]

Hi @Geoff,

I believe the issue with the Raspberry Pi's was the underlying USB firmware on the Raspberry Pi end of things. I presume none of these ports have been through a USB hub?

Thanks,
JColvin

[Geoff]

These connections were directly to the ports on the motherboard.

 

[JColvin]

Hi @Geoff,

I'm personally not super familiar with getting WaveForms up and running on a Ubuntu system, but if you happen to be getting a crash or segmentation fault when you connect the Analog Discovery 2, I would recommend taking a look at this thread. Otherwise, I will likely defer to @attila for any additional troubleshooting advice.

Thanks,
JColvin

[Geoff]

WaveForms starts up fine; it just can't find the AD2 because it has already been disconnected from ttyUSB0.

 

The problem is likely either in the driver, which seems unlikely as I have other FTDI devices which work fine, or in the mode/way the FTDI/UART start up on the AD2.

 

 

 

[attila]

Hi @Geoff

The above disconnect is normal. Linux automatically loads the USB Serial driver, since AD2 does not use this, the driver is unloaded and TTY disconnected.

1. Try to restart and see if it is working.

2. Try running the Enumerate.py which should list the detection of the devices on multiple levels of drivers.
$ python /usr/share/digilent/waveforms/samples/py/Enumerate.py
It should output something like this:

3. Try to reinstall the digilent.adept.runtime package.