Search the Community

Showing results for tags 'linux'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Scopes & Instruments and the WaveForms software
    • 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


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 123 results

  1. Ritsumeikan University uses ZYBOT to teach graduate students embedded systems. Professor Tomonori Izumi shared the materials in Japanese
  2. Hi, In mine development, I have booted Linux on ZedBoard and also i have integrated the Wi-Fi module successfully with the ZedBoard. Now in mine further development i want to explore the partial reconfiguration thing on the ZedBoard as i do not have any idea about this. From here and there i have read some PDFs which talks about some PCAP , ICAP and many more ...but i did not able to get these things fully. So as per mine requirement i would be sending one file(mainly partial config) to the ZedBoard via Wi-Fi. In this regard till now, i have sent one file(that is not reconfig file but is a normal txt file) to the ZedBoard successfully. So i want to know the followings:- 1- Step by step process of executing the partial reconfiguration concept on the ZedBoard..For this Plz suggest any link/video tutorial is there??? 2- Once i got this partial reconfig file on the ZedBoard then how to use the Linux OS to do the dynamic partial reconfiguration on the ZedBoard. Regards Aditya
  3. I have a weird issue with my Analog Discovery 2 and I was wondering if there are ideas out there how to track it: I use a Digilent Adept with the Waveforms 3.3.7 software on linux. It seems to work fine but does not detect my triggers. If I use the provided pyhton examples or C examples trigger detection does not work meaning the program just stays in "Waiting for trigger" state all the time. But if I use the dwfcmd: cd /usr/share/digilent/waveforms/samples/dwfcmd && dwfcmd analogintrigger.txt I get one trigger without a problem. It took me so much time to detect this behavior and now I don't have any idea how to solve this. The dwfcmd is not powerful enough for my application but maybe I'll end up modifying the code to fit my needs. I'd really like to keep using python, any ideas what I am doing wrong or any known bugs? Thanks Daniel Rech
  4. I am unable to make Waveforms working with my Analog Discovery on Linux. I installed Adept 2 and Waveform, when I plug my device in the usb port I have it recognized. It seems it is Waveforms that refuse to recognize the device or something bad happen as soon as I start Waveforms to the USB connection. Here is the log output when I connect the device in the USB port: oct 06 20:49:09 feynman kernel: usb 2-1.7.4: USB disconnect, device number 11 oct 06 20:49:09 feynman dbus[1324]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' oct 06 20:49:09 feynman dbus[1324]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. oct 06 20:49:13 feynman kernel: usb 2-1.7.4: new high-speed USB device number 12 using ehci-pci oct 06 20:49:13 feynman kernel: usb 2-1.7.4: New USB device found, idVendor=0403, idProduct=6014 oct 06 20:49:13 feynman kernel: usb 2-1.7.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 oct 06 20:49:13 feynman kernel: usb 2-1.7.4: Product: Digilent USB Device oct 06 20:49:13 feynman kernel: usb 2-1.7.4: Manufacturer: Digilent oct 06 20:49:13 feynman kernel: usb 2-1.7.4: SerialNumber: 210244540938 oct 06 20:49:13 feynman kernel: ftdi_sio 2-1.7.4:1.0: FTDI USB Serial Device converter detected oct 06 20:49:13 feynman kernel: usb 2-1.7.4: Detected FT232H oct 06 20:49:13 feynman kernel: usb 2-1.7.4: FTDI USB Serial Device converter now attached to ttyUSB0 oct 06 20:49:13 feynman mtp-probe[14777]: checking bus 2, device 12: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7/2-1.7.4" oct 06 20:49:13 feynman mtp-probe[14777]: bus: 2, device: 12 was not an MTP device oct 06 20:49:13 feynman dbus[1324]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' oct 06 20:49:13 feynman dbus[1324]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. oct 06 20:49:28 feynman kernel: ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 oct 06 20:49:28 feynman kernel: ftdi_sio 2-1.7.4:1.0: device disconnected From 20:49:09 to 20:49:13, these messages are issued when I plug the device. At 20:49:28, these are the messages when I start Waveforms. Anyone can tell me what is wrong? Why the device get disconnected when I start Waveforms? And why do I get the device reported in the Waveforms GUI anyway? As shown on the attached screenshot, the serial number of the device is reported correctly. Any help to resolve this issue would be appreciated.
  5. With the original linux installed on my Beaglebone Black the scope worked but then I installed a newer debian version with a 4.1.22 kernel and now I keep getting an error with scope power: dwfcmd analoginout.txt FAILED: FDwfDeviceOpen The device needs at least 2W/400mA from USB cable. To satisfy this: - Try to use different USB cable and computer plug. - Use the USB plug on the back of the PC, not the one on the front panel. - Use short cable, do not use long cable or cable extender. - Use powered USB-hub, avoid un-powered hub. - Use 5V auxiliary power supply. USB: 0.01V 777mA AUX: 3.58V 580mA The Analog Discovery 2 has its own 5V power supply and I use the original cable I don't see a reason why this shouldn't work. Anyone with the same problem or a solution out there?
  6. I'm new to FPGAs and the zynq. I'm interested in a zybo board and would like to know how to put an lvds output on the logic part of the zynq and how to get this connected to a framebuffer device I can use in linux to output graphics to?
  7. Hi, Following is the snippet from the device tree for the MicroZed Board. [email protected] { #address-cells = <0x2>; #interrupt-cells = <0x3>; #size-cells = <0x1>; compatible = "arm,cortex-a9-gic", "arm,gic"; interrupt-controller; num_cpus = <0x2>; num_interrupts = <0x60>; reg = <0xf8f01000 0x1000 0xf8f00100 0x100>; xlnx,irq-f2p-mode = "REVERSE"; linux,phandle = <0x3>; phandle = <0x3>; }; Mine particular interest is the line that is bold in above snippet.Actually i am working on the Zedboard and when i generated the device tree for mine Zedboard then following is the Snippet:- ps7_scugic_0: [email protected] { #address-cells = <2>; #interrupt-cells = <3>; #size-cells = <1>; compatible = "arm,cortex-a9-gic", "arm,gic"; interrupt-controller ; num_cpus = <2>; num_interrupts = <96>; reg = <0xF8F00100 256 0xF8F00100 0x100>; xlnx,irq-f2p-mode = "DIRECT"; } ; So it has become "DIRECT". So what is difference between "DIRECT" and "REVERSE",why for Microzed it is "REVERSE" and why for Zedboard it is "DIRECT". Please reply me. Regards Aditya
  8. 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.
  9. I've been battling trying to get the Analog Discovery 2 to work on usb in linux (Debian 8.5 now) on the cpu board I have from VersaLogic (Iguana). At this point, usb keeps disconnecting and I can't tell if it's the board or the drivers. My preference would be for an ethernet Analog Discovery 2 instead of usb since my experience with usb seems so flaky compared to ethernet. But can someone suggest a small motherboard with a usb chipset that they've gotten to work with linux and the AD2? I'm hoping for something small like a mini-ITX. It needs wired ethernet and video. Any help, or a pointer to another forum that might be able to help, is appreciated.
  10. Hi all, I am currently doing the Xilinx tutorial to run Linux on my zybo : In the process, I have to get these task done : Bitstream (for the programmable logic portion) System hardware project hdf file My question is : can I use the generate the bitstream and the system hardware project ? If I complete the tutorial with the generated files, will I be able to run linux and use it with the hdmi or vga output, get access to any kind of command prompt? Thanks. Regards, Herrmattoon
  11. Greetings everyone, This is the first ever post of a beginner who has set on the path to learn embedded systems. Please forgive me if haven't followed rules of posting. I took the embedded system plunge few weeks back. Bought a strong laptop, a Zybo board, OV7670 camera, installed Vivado. Read online tutorials like 'blinking LEDs' and 'HDMI-to-VGA out' (and the others ones in Zynq Book) to get myself accustomed with Vivado etc. [Abbreviations in the text: PS= Processing System, PL= Programmable Logic] I have been visiting a blog lately and have found that quite helpful. A couple of weeks back I started this project mentioned on the same blog (http://lauri.võ What I'm doing is a bit simpler version of this as I omitted some part of the design which I thought wasn't required, I'll mention about that later. Pretty much like a mixture with another project involving test pattern generator (http://lauri.võ My aim in this project is to get the stream from OV7670 camera, take it through PL (AXI VDMA IPs) to the PS, and then view the stream inside some window within Xillinux (linux). I feel doing so will ensure a bit of learning in both the PL and PS. Following is my progress along with doubts I have so far: 1- I have pasted the picture of my block design (called VDMA_Trial). After playing hit and trial, I managed to go around all the initial errors and successfully generated the bitstream. Which was a big relief. If you compare my block design with the one mentioned on the link I pasted above, you'll notice mine has lesser number of IP blocks. I did not need the RGB, HSYNC and VSYNC outputs from the PL so I omitted that part and only focused on taking the camera stream to the PS. Do you think this makes sense? Or do I need to have the complete IP blocks even if I don't wish to see the stream on HDMI (or VGA)? 2- I'm a normal computer user who has used Windows PCs most part of the life. So I don't have much idea of CLI based Linux. After reading from online resources, I booted Xillinux image (downloaded from on the Zybo through SD card. Since I wish to watch the stream from the camera inside the GUI Xillinux. From a bit of reading I got to know about something called V4L2, which I'm still trying to figure how to install on Xillinux. Now assuming the design in point 1 is fine, can I simple paste the bitstream of the project in the SD card along with the Xillinux boot files (there are some other files in SD card too for Xillinux: devicetree, ulmage and xillydemo.bit). Will the hardware design in the PL activate and start writing the video stream information to the PS memory (DDR) when I boot up the Zybo with this SD card? If not, what step must I follow? Do I need to launch SDK to write some code to tell PS what to do? But I will already have the Xillinux OS running on PS, am I correct when I say I'll have to write and compile some code in Xillinux to tell PS to fetch the stream which is being written to PS memory by VDMA (from PL). 3- While reading different stuff, I came across this thing related to V4L2 and OV7670 ( To a layman like me, it looked like the code to set up OV7670 camera using V4L2 driver. Will I need to compile and run this code in Xillinux to watch the stream? I tried, but it just did not compile. My apologies for making it long and prob'ly silly. Just started traversing a steep learning curve, will take time to learn. I really look forward to seeing your enlightening responses. If there's any more info you need please let me know (in easy English ). Regards, Haris.
  12. Hello everyone; I am trying to boot Linux on Zybo using this tutorial: I have load Boot,bin, devicetree.dtb uImage and uramdisk.image intor fat32 partition of my 16 Gb sd card. size of uramdisk.image is around 5 Mb. when I boot the Linux, I have the problem like this, BAD DATA CRC h Do you have any experience on that ? is the size of kernel correct?
  13. Hi all, I am trying to add an axi-timer to generate an interrupt from PL to PS. I found this guid of xilinx here : My question is how to or where to find the three numbers assigned to interrupt like in this example of xilinx: "interrupts = <0 59 4>;"? I am using ZYBO and Vivado 2015.4. Thanks,
  14. Hiiii, i am looking for answer of this question. How to set that a particular thread always be executed by a specific core in multi-core Linux environment?
  15. Hi all, I am about to run Linux on a Zybo. In the tuto I am following, this is explained I have to generate a device tree after defining the hw with no mention about any Linux drivers. But I think this is not the only thing I have to do to make Linux able to communicate with the peripherals on the board. Tell me if I am wrong : the device tree is just there to tell the kernel how peripherals are mapped in memory. But it does not tell nothing about how to communicate with. This is the role of the driver. Right? If right, will it be fine if I generate the device tree and if I use the kernel in github Digilent/linux-digilent? Does this kernel already have all the required drivers for my board? Thanks, Herrmattoon
  16. Hello, I've successfully installed Waveforms 2015 v3.3.3 and the Adept runtime 2.16.1 on my machine which is running Fedora 21. Both are 64 bit. However, when I plug in the Analog Discovery 2 it shows no device detected. I tried reinstalling the Adept runtime, and the FTDI drivers with no success. The Analog Discovery 2 does show up on my machine as a USB device however. It shows up as "Future Technology Devices International, Ltd FT232H Single HS USB-UART/FIFO IC" Thanks! Kaitlyn
  17. How to setup diligent usb cable for Xilinx Spartan-3 starter kit on CentOS 6? I have already installed ISE WebPack, digilent.adept.runtime, digilent.adept.utilities, libCseDigilent, fxload, and some other packages. lsusb shows: [[email protected] home]$ lsusb Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 03fd:000d Xilinx, Inc. but djtgcfg shows nothing: sudo djtgcfg enum No devices found iMPACT log: Welcome to iMPACT iMPACT Version: 14.7 Project: /home/lukasz/VHDL/QLIW//auto_project.ipf created. // *** BATCH CMD : setMode -bs // *** BATCH CMD : setMode -bs // *** BATCH CMD : setMode -bs // *** BATCH CMD : setMode -bs GUI --- Auto connect to cable... // *** BATCH CMD : setCable -port auto INFO:iMPACT - Digilent Plugin: Plugin Version: 2.4.4 INFO:iMPACT - Digilent Plugin: no JTAG device was found. AutoDetecting cable. Please wait. *** WARNING ***: When port is set to auto detect mode, cable speed is set to default 6 MHz regardless of explicit arguments supplied for setting the baud rates PROGRESS_START - Starting Operation. If you are using the Platform Cable USB, please refer to the USB Cable Installation Guide (UG344) to install the libusb package. Connecting to cable (Usb Port - USB21). Checking cable driver. File version of /opt/Xilinx/14.7/ISE_DS/ISE/bin/lin64/xusbdfwu.hex = 1030. File version of /etc/hotplug/usb/xusbdfwu.fw/xusbdfwu.hex = 1030. WinDriver v10.31 Jungo (c) 1997 - 2011 Build Date: May 24 2011 x86_64 64bit 18:13:19. Cable connection failed. Connecting to cable (Parallel Port - parport0). WinDriver v10.31 Jungo (c) 1997 - 2011 Build Date: May 24 2011 x86_64 64bit 18:13:19. Cable connection failed. Connecting to cable (Parallel Port - parport1). WinDriver v10.31 Jungo (c) 1997 - 2011 Build Date: May 24 2011 x86_64 64bit 18:13:19. Cable connection failed. Connecting to cable (Parallel Port - parport2). WinDriver v10.31 Jungo (c) 1997 - 2011 Build Date: May 24 2011 x86_64 64bit 18:13:19. Cable connection failed. Connecting to cable (Parallel Port - parport3). WinDriver v10.31 Jungo (c) 1997 - 2011 Build Date: May 24 2011 x86_64 64bit 18:13:19. Cable connection failed. PROGRESS_END - End Operation. Elapsed time = 2 sec. Cable autodetection failed. WARNING:iMPACT:923 - Can not find cable, check cable setup !
  18. Hi Everyone! I'm attempting use Waveforms with Ubuntu 15.10. I've installed Adept runtime, and Waveforms 2015 through .debs. Waveforms on start only displays a blackscreen and the terminal reports the following error: waveforms: pthread_mutex_unlock.c:87: __pthread_mutex_unlock_usercnt: Assertion `type == PTHREAD_MUTEX_ERRORCHECK_NP' failed. Aborted (core dumped) If I attempt the cli I receive the following: Set range and print the actual obtained range: dwfcmd connect analogio channel=1 range=5V range dwfcmd: pthread_mutex_unlock.c:87: __pthread_mutex_unlock_usercnt: Assertion `type == PTHREAD_MUTEX_ERRORCHECK_NP' failed. Aborted (core dumped) Anyone have any ideas? I attempted this with the 32-bit and 64-bin installers. I am using a 64-bit system. P.S. On the main diligent site the link to the form at the bottom of the page is broken.
  19. Digilent Waveforms depends on xdg-utils which depends on x11 and many things. Can I install waveforms without all of this and how? Is anyone using this on an embedded device like the Beaglebone Black or Rasberry Pi?
  20. I have an Analog Discovery 1. I have been using it successfully under Windows for some time. I would now like to use it under Linux - Ubuntu 14.04 LTs (64-bit) . I have installed digilent.waveforms_3.2.6_amd64.deb When I start the program I get three error messages 1) WaveForms > dlopen Reinstall Digilent Adept Runtime 2) WaveForms > No device detected 3) Device Manager > Adept NOK No device appears in the list of available devices in the Device Manager. Running dmesg I can see that the device is recognized by the operating system. When connecting I get - "FTDI USB Serial Device converter now attached to ttyUSB0" When disconnecting I get - "FTDI USB Serial Device converter now disconnected from ttyUSB0" Does anybody know how to solve this issue? Regards, Ben
  21. Hi, I am trying to write a linux device driver for a project which uses audio codec. I am using the ip axi_i2s_adi codec for the project on ZYBO . I see that the functions in the demo file are written for Vivado. I mean the functions uses XIlinx header files and functions. I think I cannot use those to build device driver. If somebody has written device driver by themselves or know where i can find, please share the details with me. Thank You, Ramu
  22. mabden

    Nexys 4 DDR

    Hi everyone ! I search a protocol for a quick linux installer on the Nexys4 training board. I don't found this in this forum. Thank you for the help. Greetings !
  23. Count0

    Moving to Linux

    Hi all, i'm moving my development environment to Ubuntu. Last things I'm struggling with are Xilinx WebISE and the JTAG-HS3 programmer. All worked fine under W7pro. But WebISE performs traumatically on Ubuntu. WebISE was designed to run on RedHat and SUSE but it runs there far from flawless. So I put up a W7 in VirtualBox on Ubuntu and got WebISE running fine again. But when forwarding the JTAG-HS3 to the VM, the VM got killed immediately. I can live with this situation if I knew how to operate JTAG-HS3 on Linux, to upload a bitstream to my FPGA. So my questions boil down to: Where can I find a user manual about how to use the Adept software for Linux. I haven't found it on the Digilent website?Does anyone know how to stop VirtualBox VM's crashing when connected to a JTAG-HS3 programmer? Thanks in advance
  24. Hey Guys, I am trying to install a Preempt_RT patch on the linux. I downloaded the Linux kernel from github which is described in 'Embedded Linux Hands-on Tutorial': . I noticed that the kernel version is 3.18.0, so I install the patch 3.18.24-rt22.patch (since there is no patch for 3.18.0). But when I try to compile the patched kernel with the configuration of full RT, I got this following errors: So I am wondering how to solve this. And I also wonder if there is anybody else trying to use a real time linux on the zybo. Regards, Jimmy
  25. jago

    Nexys4DDR Linux

    What happened to the Embedded Linux topic on the Nexys4DDR wiki page? It was "under construction" and now it's removed. I was looking forward to see this project since I got my Nexys4DDR. What happened? Didn't the Artix7 have enough power or did Nexys4DDR have to few ressources? Regards, Jago