Search the Community

Showing results for tags 'debian'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Scopes & Instruments
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. I am using Debian/Jessie on a AMD64 platform. I am unable to use my Analog Discovery because Waveforms does not function any longer. Here are the problems. 1) Both the available versions of Waveforms2 (version 2.9.4 and version 2.7.5) install without problems (using "dpkg -i"). However both versions fail to run because of a missing libdmgr.so.2 library. 2) Adept (version 2.16.5) installs without problem. However Waveforms3 (version 3.4.7) fails to install because it is missing a system menu definition. Is there an existing fix or work around for this ? Are these problems likely to be fixed in the near future ? Just my two cents : I am grateful that Digilent is supporting Linux users and providing Debian packages. However there is much to be desired in the quality of this packaging. There have been similar problems with the Waveforms previously. I do appreciate supporting the difference between multiple Linux distributions can be quite a problem. For software that is offered gratis, such as Waveforms the best solutions is to open source it, under a suitable license so it can be integrated into and customized for each Linux distribution by or with the help of, the maintainers of those distributions. Not to mention the cost savings and community support that Digilent will gain in the process. If this is not a possibility then the next best thing is to create source packages (.spec for rpm and debian directory for deb) that confirm to the packaging policies of few chosen seminal distributions such as Fedora and Debian (stable) and then use build servers (perhaps using docker) that create builds for each version of those distributions on the distribution itself. On Debian, tools such as pbuilder and lintian eliminate a lot of these packaging problems. It seems like the above deb packages are not being built using the Debian packaging system on a Debian system. This is because in trying to included the package into a local Debian package repository (created using reprepro) corrupts the APT dependency metadata.
  2. I had a working Debian 8 production system using python2.7 to talk to an Analog Discovery 2. I decided to update the .deb packages to be current and now I get "Segmentation fault" "stack smashing detected" when I try to start my python program. I was using the amd64.deb files: digilent.adept.runtime 2.16.6 digilent.waveforms 3.5.4 (for the libdwf.so file) Upgraded to digilent.adept.runtime 2.17.1 digilent.waveforms 3.7.5 Also on the system is digilent.adept.utilities 2.2.1. I tested just upgrading the runtime package and my program works. Upgrading the waveforms package (and thus libdwf.so) causes the segfault. Any thoughts on how I might track down where the problem is?
  3. I'm trying to use an Analog Discovery 2 on linux Debian 8.5 (jessie). I recently upgraded from 7.9 (wheezy) because I couldn't get the AD2 usb to work reliably. But I seem to have the same trouble here. $ dpkg-query -l 'digilent*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-============================-===================-===================-========================== ii digilent.adept.runtime 2.16.5 i386 Digilent Adept Runtime ii digilent.adept.utilities 2.2.1 i386 Digilent Adept Utilities ii digilent.waveforms 3.3.7 i386 Digilent WaveForms In particular, the AD2 is not found at boot time, but unplugging and then replugging the usb cable causes it to be detected. Once the os knows the device is there, 'dadutil enum' will answer back a device and serial number. But eventually (haven't found a pattern yet but current max is 26 minutes, min < 2 minutes) the device disconnects from the usb. After that 'dadutil enum' says 'No devices found'. Using 'lsusb' shows the device is gone. Physically unplugging and replugging usb brings the device back for a while. 'waveforms' will work for a while, but I believe the usb disconnect makes it die. E.g. from /var/log/messages, grepping for 'usb.*2-2' Sep 6 16:27:29 deb85-Iguana kernel: [ 7974.156045] usb 2-2: new high-speed USB device number 8 using ehci-pci Sep 6 16:27:29 deb85-Iguana kernel: [ 7974.293336] usb 2-2: New USB device found, idVendor=0403, idProduct=6014 Sep 6 16:27:29 deb85-Iguana kernel: [ 7974.293345] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 6 16:27:29 deb85-Iguana kernel: [ 7974.293351] usb 2-2: Product: Digilent USB Device Sep 6 16:27:29 deb85-Iguana kernel: [ 7974.293356] usb 2-2: Manufacturer: Digilent Sep 6 16:27:29 deb85-Iguana kernel: [ 7974.293361] usb 2-2: SerialNumber: 210321A1A55D Sep 6 16:27:29 deb85-Iguana kernel: [ 7974.296225] usb 2-2: Detected FT232H Sep 6 16:27:29 deb85-Iguana kernel: [ 7974.296234] usb 2-2: Number of endpoints 2 Sep 6 16:27:29 deb85-Iguana kernel: [ 7974.296242] usb 2-2: Endpoint 1 MaxPacketSize 512 Sep 6 16:27:29 deb85-Iguana kernel: [ 7974.296249] usb 2-2: Endpoint 2 MaxPacketSize 512 Sep 6 16:27:29 deb85-Iguana kernel: [ 7974.296255] usb 2-2: Setting MaxPacketSize 512 Sep 6 16:27:29 deb85-Iguana kernel: [ 7974.296752] usb 2-2: FTDI USB Serial Device converter now attached to ttyUSB0 Sep 6 16:27:29 deb85-Iguana mtp-probe: checking bus 2, device 8: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-2" Sep 6 16:34:32 deb85-Iguana kernel: [ 8398.020689] usb 2-2: USB disconnect, device number 8 My system info: $ uname -a Linux deb85-Iguana 3.16.0-4-686-pae #1 SMP Debian 3.16.36-1+deb8u1 (2016-09-03) i686 GNU/Linux All of this happens to be on a VersaLogic Iguana board. Thanks for any help.
  4. Searched for this issue but couldn't find any earlier queries. I've just installed the software tree up through waveform3 on a debian box. Dwfcmd returns nothing when I run it as an unprivileged user but gives the correct result (finds the Analog discovery) if I run it as root. Same is true for my python scripts that access the AD. Is there anything I can do to be able to access the AD as a normal user? Thanks. O/S details are: Description: Debian GNU/Linux 7.9 (wheezy) Linux debian73-Iguana 3.2.0-4-686-pae #1 SMP Debian 3.2.73-2+deb7u2 i686 GNU/Linux libc is 2.21