Analog Discovery 2 Linux/Python API (armhf / raspberrypi)

[towen]

Hi,

I am trying to get my Analog Discovery 2 going on Raspberry Pi.

I have tried the 'pydwf' library which works on my Linux laptop, however it seems that libdwf (the digilent waveforms library) is only distributed for Arm32 and Arm64, not armhf :( 

What is the best way to use the Analog Discovery 2 on Raspberry Pi?

[towen]

I found an old 'beta' of the waveforms armhf package on this forum, and I tried to install that, but I get:

dpkg: error processing archive digilent.waveforms_beta_3.18.19_armhf.deb (--install):
 new digilent.waveforms package pre-removal script subprocess returned error exit status 2
xdg-mime: file '/usr/share/mime/packages/digilent.waveforms.xml' does not exist

I also tried copying the file in question (/usr/share/mime/packages/digilent.waveforms.xml) from my Linux laptop to the raspberry pi, but I get the same error.

Is the raspberry pi platform still supported by digilent?

[towen]

OK it took some coercion but I managed to get the package to install.. 

Unfortunately after doing that I only just discovered the issue with FTDI drivers on RPI 3 😭 I wasted a couple of hours trying to get a better AUX power supply only to find that it is a fundamental software problem 🤌

https://forum.digilent.com/topic/1713-analog-discovery-2-vs-raspberry-pi-3

I wonder if it could be something to do with FTDI's nasty habit of sending garbage data from the driver if it detects a "fake" FTDI device

https://hackaday.com/2016/02/01/ftdi-drivers-break-fake-chips-again/

[attila]

Hi @towen

This seems to be an unique (hub or driver) bug in earlier versions of RPIs since it is working fine with other SBC and computers. Reducing the transfer lengths and packing reduces the IN transfer oddness on RPI.