sourdoughconquistador

This solved it!!! Thank you!

Hello! I'm having a strange issue on Arch Linux. I have two Arch machines, one of which works just perfectly. The other has Waveforms and Adept installed exactly the same way, and can see the device both in lsusb as Bus 001 Device 004: ID 0403:6014 Future Technology Devices International, Ltd FT232H Single HS USB-UART/FIFO IC and in the waveforms new window as Discovery2 SN:210321B0E6FD . However, it fails to connect with DptiIO failed ERC:2 out:8 in:28 Communication failed or image device id is wrong. ID: 0x0 Type: 0x0 Version: 0x0 Once again, the same AD2 works seemingly without issue on my other machine with the same distribution, and the same install of Waveforms/Adept. If I click that my device is not listed, I can see it and successfully reprogram it from the waveforms device fix menu, recognizing the serial number and model number, and this works, and the device still functions on my other machine afterwards. VID/PID: 403 / 6014 Manufacturer: Digilent Description: Digilent USB Device SN: 210321B0E6FD Bus Powered 500mA OEMID: 356A92C7 PDID: 40300360 Product: Analog Discovery 2 Name: Discovery2 done However, connecting still simply refuses on this machine. Any more information I can provide to help diagnose, please let me know! It's not a massive issue, as I can simply use my other machine for the time being, but it is somewhat obnoxious and I'd like to figure it out. Thanks! I have tried running waveforms as root in case it was a permissions error, in which case it simply did not see the device at all, and reinstalling waveforms and adept after reboot. Neither of these fixed the issue. I have used this USB port on this machine for other things to test if it was nonfunctional, and it seems to work fine. Using waveforms/adept package from the Arch User Repository, https://aur.archlinux.org/packages/digilent.waveforms/, version 3.14.3-1, and https://aur.archlinux.org/packages/digilent.adept.runtime/, version 2.21.2-1, on both machines.