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
    • 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 115 results

  1. I would like to get a HDMI Video output working with Petalinux on the Zybo Z7-10, and would appreciate any pointers, links etc. I'm particularly interested in how you get Xilinx DRM working on the Zybo Z7-10. I've seen quite a few posts on the old (VGA) Zybo, and running Xillinux, and also designs using the Xylon video cores. My design will be based on zybo-z7-10-base-linux. Eventually, I'd like to get an Ubuntu installation running Xfce working. Thanks Andy PS I eventually managed to get Lubuntu running on the Zybo - but with remote login (xrdp) instead of via the HDMI port- this has the advantage of not using any extra PL resource Much more difficult was trying to get my WiFi dongle working ...
  2. Hello, i made the following design: You can see two GPIO Ports: - GPIO_RGB_LED, 3 Bit, Output only - GPIO_SW, two data bits plus one interrupt bit (e.g. Input clk), this port should throw Interrupts into the Linux App. After i build that design with Vivado, i used petalinux to create a Linux image. Here you can see the "/dev"-Folder which contains the installed Drivers: You can see three GPIO-Drivers. Now my question: In former questions i ask for the Driver Support in Linux and how i can write or use them. You told me, that there is a simple way to access memory mapped ip-cores with the "uio"-Driver. First i was glad to see that the Drivers are automaticaly added to the image. But i'am missing the expected "uio"-Drivers. What must i do to get the "uio"-Drivers for my design with petalinux? Thank you...
  3. Hi! I've implemented a Microblaze system on the ARTY board, which includes a Texas Instruments DP83848 PHY chip to manage ethernet communications. Xilkernel and example program 'echo server' works wonderfully, so any hardware issue is discarded. However, on linux (using both mainstream and xilinx' github repo), I can't get ethernetlite core to work. This is the info I can provide: axi_ethernetlite_0: ethernet@40e00000 { compatible = "xlnx,xps-ethernetlite-1.00.a"; device_type = "network"; interrupt-parent = <&microblaze_0_axi_intc>; interrupts = <1 0>; reg = <0x40e00000 0x10000>; xlnx,duplex = <0x1>; xlnx,include-global-buffers = <0x1>; xlnx,include-internal-loopback = <0x0>; xlnx,include-mdio = <0x1>; xlnx,rx-ping-pong = <0x1>; xlnx,s-axi-id-width = <0x1>; xlnx,tx-ping-pong = <0x1>; xlnx,use-internal = <0x0>; axi_ethernetlite_0_mdio: mdio { #address-cells = <1>; #size-cells = <0>; phy0: phy@0 { device_type = "ethernet-phy"; reg = <0>; }; }; }; phy0 section was written by me, as it was not provided by dts creation utility for the SDK. dmesg output: xilinx_emaclite 40e00000.ethernet: Device Tree Probing xilinx_emaclite 40e00000.ethernet: Failed to register mdio bus. xilinx_emaclite 40e00000.ethernet: error registering MDIO bus xilinx_emaclite 40e00000.ethernet: MAC address is now 00:0a:35:00:00:00 xilinx_emaclite 40e00000.ethernet: Xilinx EmacLite at 0x40E00000 mapped to 0xF0140000, irq=2 Relevant kernel config: CONFIG_NET_VENDOR_XILINX=y CONFIG_XILINX_EMACLITE=y CONFIG_PHYLIB=y CONFIG_DP83848_PHY=y CONFIG_XILINX_PHY=y eth0 interface appears, and ifconfig eth0 doesn't produce any error. However, no other host on the network can reach the ARTY nor viceversa, not by ping, nor by poking at any random port. Any ideas? Thanks!
  4. I am having a similar issue when running as a normal user under Ubuntu 16.04.4 LTS and have installed the following packages per the standard instructions for running the Analog Discovery 2 device. ii digilent.adept.runtime 2.17.1 amd64 Digilent Adept Runtime ii digilent.waveforms 3.7.5 amd64 Digilent WaveForms Currently I am only able to run waveforms under "sudo" and not as a standard user. As a standard user executing env LD_LIBRARY_PATH=/usr/lib/digilent/waveforms/qtlibs gdb /usr/lib/digilent/waveforms/waveforms Thread 10 "waveforms" received signal SIGSEGV, Segmentation fault 0x00007fffecce2fc6 in libusb_close () from /lib/x86_64-linux-gnu/ The Full Backtrace is as follows #0 0x00007fffecce2fc6 in libusb_close () from /lib/x86_64-linux-gnu/ #1 0x00007fff375e492d in CloseDevice () from /usr/lib64/digilent/adept/ #2 0x00007fff375e5c91 in OpenDevice () from /usr/lib64/digilent/adept/ #3 0x00007fff375e61ed in FTCommonOpen () from /usr/lib64/digilent/adept/ #4 0x00007fff375e633e in FT_OpenEx () from /usr/lib64/digilent/adept/ #5 0x00007fffefd55cae in ?? () from /usr/lib64/digilent/adept/ #6 0x00007fffefd501b3 in ?? () from /usr/lib64/digilent/adept/ #7 0x00007fffefd4c6f8 in ?? () from /usr/lib64/digilent/adept/ #8 0x00007fffefd4a3d6 in ?? () from /usr/lib64/digilent/adept/ #9 0x00007fffefd498dc in ?? () from /usr/lib64/digilent/adept/ #10 0x00007ffff395a6ba in start_thread (arg=0x7fffc4907700) at pthread_create.c:333 #11 0x00007ffff48b941d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Running strace this line appears 3 times: open("/dev/bus/usb/002/004", O_RDWR) = -1 EACCES (Permission denied) At a glance this appears to be a permission issue for accessing the USB port/driver for this device; is there a recommended adjustment or fix for this at this time?
  5. Hi all, I m beginner in Fpga, actually i dont know anything in FPGA. Last week I bought a zybo z7-10 board from diligent store. I want to run a linux on this borad, for that i did everything as per the tutorial link: And i installed linario in the sdcard. I only have a VGA monitor to connect to zybo, so that i used a vga to hdmi converter and boot the zybo. But i cant see nothing in the screen except the text "Input Not Supported". Three leds in the board is lighted up and glow still. I dont know , whats the actual problem with this? Can anyone help me... Thanks in advance
  6. 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 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 causes the segfault. Any thoughts on how I might track down where the problem is?
  7. tekson


    Hi all, How to implent delay in verilog code? I want to run a led blink code with one second delay using zynq zybo-7-z10 Thanks in advance
  8. Hi all, I m beginner in Fpga, actually i dont know anything in FPGA. Last week I bought a zybo z7-10 board from diligent store. I want to run a linux on this borad, for that i did everything as per the tutorial link: And i installed linario in the sdcard. I only have a VGA monitor to connect to zybo, so that i used a vga to hdmi converter and boot the zybo. But i cant see nothing in the screen except the text "Input Not Supported". Three leds in the board is lighted up and glow still. I dont know , whats the actual problem with this? Can anyone help me... Thanks in advance
  9. tekson

    Linux image for Zybo Z-10

    Hi all, I m a beginner in FPGA. Last month I got a Zybo Z-10 board from diligent web store. Started working on it using Vivado 2017 edition. I played with leds and switches in PL section. Now I want to run linux image on this board. I tried many tuturials which showing how to boot zybo with linux. but failed. As in the tutorials, I created sdcard with two partitions, one with ext4 and another with fat and then I copied devicetree files, boot files etc in one partition and linux files in another partition. When I boot the board with sdcard monitor shows a black screen with some text like petalinux 2015, zybo login etc. Actually i dont know how the it boot up with linux in zybo board. I dont know whether this screen which I got is correct screen or not. Can anyone help me to boot a linux from my zybo z-10 board Thanks in advance.
  10. Hello, i have successfully implemented a hardware design smilar to this one. I am able to use the PL as a bridge between the PS and DDR. I would also like to trace the exact addresses that are being carried by the s2mm/mm2s between the ddr and dma. Is it possible to assign them some addresses(e.g. in the address editor in vivado) and track them from the OS running on the board ? Thanks.
  11. Hello, is there an IP that can track memory reads and writes and, eg. output them to a minicom (program thisvia XSDK)? I have tried this works fine, all tests run through. But I don't really know where to look for an approach to this. Is it possible to trigger something within the sdk when a memory access is happening ? Thanks
  12. Hello, so I followed this axi-dma tutorial and everything looks pretty fine. Now, this tutorial only goes to running a HelloWorld application inside de XSDK. I would like to know how t write something to DDR and how to read something back (specifying addresses e.g.)? To be precise this is how the actual design looks like I would really appreciate some sample C code of how to instantiate (?) the AXI Slave/Master ports to be able to read something from the DDR. Thanks !!
  13. Hello, first i must say, that i'am not glad about the way to handle device issues. It seems to be very complicated when using linux. If i use a bare metal System, then i have a very simple and Logical System which is easy to use. What i want is an easy way, similar to a bare metal System, where i can use the customized Hardware in a zync (FPGA) Environment. While i'am discovered my Project Folder i found a Subfolder where example c-source code was stored. In this example is a peek and poke app included. When i look at the Details i found, that the "mem" device was used and similar to "uio" interfacing - Memory mapped Access was used. Now my questions: - What is the difference between "mem" and "uio" devices? - Are "mem" devices still installed and ready to use? - Is there a disadvantage, if i use "mem" devices? Thank you...
  14. Hello, i have been searching for a ready to use image to boot form a zybo. where i can make a bootable sdcard just like this e.g.: dd bs=4M if=/path/to/zybo.iso of=/dev/sdx I tried building it with the peta linux guide. This is old and deprecated. Peta linux is missing from the Xilinx website if you dig a little bit deeper you get to the download site for this peta linux. I couldn't find anything there. Isn't there some prebuild image for this hardware somewhere ? Thank you very much.
  15. Hello, I create project on SDSoc 2015.4 using platform ( and I select Operating System is Linux because I use about image processing. but I want to access 4 LEDs on PL. Can I access the LED on PL? How to access GPIO (e.g. LEDs) on OS: Linux Previously I used OS: Standalone project. I can access by Xil_Out32(XPAR_AXI_GPIO_LED_BASEADDR, 0x2); but on Linux I can't. Thanks in advance
  16. The uio_dmem_genirq driver is backwards compatible with the uio_pdrv_genirq driver but with the addition that it dynamically allocates continuous memory. How do the device tree entries have to be defined to load the dmem driver? The working configuration for the pdrv version consists of the following device tree entry: spw0@7aa00000 { compatible = "generic-uio"; reg = <0x7aa00000 0x10000>; interrupts = <0x0 0x1D 0x4>; interrupt-parent = <0x3>; clocks = <0x1>; }; and changing the bootargs to console=ttyPS0,115200 root=/dev/mmcblk0p1 rw rootwait earlyprintk uio_pdrv_genirq.of_id=generic-uio. My current configuration for the dmem version looks as follows, but does not load the UIO driver despite it being compiled into the kernel. This is the output of /lib/modules/4.4.0-xilinx/modules.builtin kernel/drivers/uio/uio.ko kernel/drivers/uio/uio_pdrv_genirq.ko kernel/drivers/uio/uio_dmem_genirq.ko The two different styles used to try and configure the drivers are: spw0@7aa00000 { compatible = "generic-uio"; reg = <0x7aa00000 0x10000>; uio,number-of-dynamic-regions = <1>; uio,dynamic-regions-sizes = <0x4000>; interrupts = <0x0 0x1D 0x4>; interrupt-parent = <0x3>; clocks = <0x1>; }; spw1@7aa00000 { compatible = "generic-uio"; num_dynamic_regions = <2>; dynamic_region_sizes = <0x8000>; interrupts = <0x0 0x1E 0x4>; interrupt-parent = <0x3>; clocks = <0x1>; }; And the bootargs are updated to console=ttyPS0,115200 root=/dev/mmcblk0p1 rw rootwait earlyprintk uio_dmem_genirq.of_id=generic-uio. Note: this is based on my StackOverflow question
  17. I wish to access own ip-cores while i'am using Linux on the Arty-Z7 board. What is the general workflow to write a Linux-Hardware-Driver for the Arty-Plattform? Do you have any examples? Thank you...
  18. I need help with the SDK i am doing the xilinx lab 1. The "mem_test" project and when i try to use the terminal I cant see the port for the board? any suggestings? Thank you
  19. Hello, since now, i have only experience in debugging bare metal apps. I will write a linux tcp/ip-server, therefor i must be able to debug my c-code. I have tried the known bare-metal-workflow and instead of Chose "bare-metal" i Chose Linux as operating System. When i start the debugging process then i got the following error: What is a "Linux Agent" and why is it disconnected? Thank you...
  20. Hello, i used the "Arty-Z7-20-base-linux"-project with Vivado 2017.2, first i copied the board files to my new installed vivado 2017.2 Installation and then i run the "create_project.tcl" script. So far so good. After that i have tried to create a hdl-wrapper, because i liked to generate a bitstream. Vivado has got the following error: As you can see, the reason is: "IP definition not found" for the listed ip-cores (see error message). Can you tell me, what i should do? What is a "Petalinux-Arty-Z7-20-2017.2-2.bsp" file and what is it good for? Thank you...
  21. Hello, I want to use Arty Z7-20 for embedded computer vision project. So I tried to make platform file using and followed "SDSoC_Platform_creation_Guide.txt". But Platform make was failed because "Include directory 'C:/~~/SDSoC_Staging/include_linux' doesnt exist." I looked for "include_linux" folder on github repository but I couldn't find it. Where is "include_linux" folder? Or, Did I take any mistakes? I hope you will be able to provide the information. sdspfm.log Arty-Z7-20-base_src_others_SDSoC_Staging at master · sbobrowicz_Arty-Z7-20-base · GitHub.html
  22. As I mentioned days ago, I made a java version GUI for the Adept2 command line tools on linux. Please try it out and tell me if it is usable or useful. Many thanks, Dake Feng JAdept2-2016-7-16.jar README src-2016-7-16.tar.gz
  23. I'm making a project about image processing. The board used in the project is the Zybo board and operates on a frame 1920x1080 (Full HD). My project is Square Area Detection Then motion detection within the rectangular area. I would like to ask for advice or guidance directs the operation of the mine. (I'm new to Zybo boards and I just learned recently.) If anyone has suggestions and links for learning. Please direct me and attach the link. Thanks in advance. ^__^
  24. Hello I just received my Zybo Z7-10 board a few days ago, and have been working on it. I think the USB type A (the USB OTG) is not working. Because I have plugged a simple flash memory with a LED on its back and when I plug it, its LED doesn't turn on. I have another FPGA board "Basys3", and if I plug my flash memory, the back LED on flash memory turns on. I have implemented a Petalinux on the board and it cannot also recognize that USB when I plug it. I have also tested the USB A voltage pins,the voltage between the far right and left pins, and the voltage difference is zero which has to be around 5 volt. Since the warranty time is 30 days, I was wondering if one of the technicians could help me whats going on and if the board is defective. Thank you