Search the Community

Showing results for tags 'driver'.



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

  1. theAsker

    Program code on PetaLinux

    Hello! Here is another newbie question from me! I am having a running hardware project from Vivado, and I also debugged bare metal code with SDK. Both was running perfectly. Now I also got a PetaLinux (v2017.4) run on my Zybo Z7-20. So far so good. First I thought, that I could only paste the c code on PetaLinux, compile it and let it run. But of course it didn't worked because I used bare metal code. I wrote already that I have to add drivers to the device tree. Here are my problems/questions: 1) I wrote something the following files: system-user.dtsi, zynq-7000.dtsi, system-top.dts and system-conf.dtsi As I wrote I am only allowed to change stuff in the system-user.dtsi file. But when I compare the driver code from your Zybo Z7-20 and the stuff I found in the internet. It looks completly different. So where and what do I have add? I wrote that I have to enable the kernel configuration (where and how)? Am I doing this with petalinux-config -c kernel, is it also possible that when I use my own hardwaretarget for PetaLinux creating , that the enabeling of the drivers happened already? 2) I want to send the voltage values over ethernet, so do I need one or two drivers (XADC-driver or XADC + ethernet-driver) for it and also a gpio driver, right? Is there code for Zybo Z7-20 somewhere existing, or where can I find some code that is fitting? I made more trys but never the petalinux-build was successfully. Thanks again for your help and time, it is always totally helpful! A+ for your job, helping a totally newbie ;-) greetings,
  2. Hello, My Windows 10 system will not correctly install drivers for the WiFire board. (See my related post here) How can I get the drivers so that I can install them manually? Thanks, John
  3. 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
  4. deppenkaiser

    Linux Hardware Driver for Arty-Z7

    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...
  5. I recently purchased the chipkit UC32 from digilent to do a labview project but when I connect it to my Windows 10 laptop, it says “USB device not recognized”. In the device manager of my computer I see the error in the port under Universal Serial Bus Controllers and it has the yellow triangle error symbol next to “Unknown USB Device (Device Descriptor Request Failed)” I have tried many things to try and get it working but have failed. Please help
  6. At the description of the Pmod Step it says that it can drive both motors simultaneously. I want to know if it can drive them with different number of steps on each motor. So the Pmod STEP will be like an 2 in 1 driver or it can only drive identical the motors.
  7. Eddy Debaere

    Error in PmodSD.tcl file ?

    Hi, Inside file https://github.com/Digilent/vivado-library/blob/master/ip/Pmods/PmodSD_v1_0/drivers/PmodSD_v1_0/data/PmodSD.tcl shouldn't 'PmodWIFI' not be replaced by 'PmodSD' ? wkr Eddy
  8. Hi, I installed also petalinux 2015.4 (beside 2017.2) in the scope of solveing my problem, but without success. I want to integrate a kernel driver into petalinux rootfs to comunicate with an PL block which has 2 interfaces (lite interface and full interface - both memory mapped). When i created the module into petalinux, i let the code as it was generated..just i overwrote the ".compatible" section with the comptabile section from pl.dtsi(in my case <xlnx,accHW-1.0>) At insmod it doesn't output both conversions (phisical to virtual adresses). It shows just the conversion for the lite interface (0x43c0 0000 to 0xe09a 0000). root@Avnet-Digilent-ZedBoard-2015_4:/lib/modules/4.0.0-xilinx/extra# insmod driv er-mihai.ko [ 95.237408] <1>Hello module world. [ 95.240737] <1>Module parameters were (0xdeadbeef) and "default" [ 95.246938] driver-mihai 43c00000.accHW: Device Tree Probing [ 95.252540] driver-mihai 43c00000.accHW: no IRQ found [ 95.257580] driver-mihai 43c00000.accHW: driver-mihai at 0x43c00000 mapped to 0xe09a0000 What i have to change in driver code to see both conversions ? Or where can i see them ?
  9. Installed Waveform 2015 software as instructed and installed the driver also. Couldn't get the Analog Discovery 2 to get recognized until after I rebooted the system. But it is only recognized if I plug it directly into my machine. If I use a hub, It doesn't work. The problem is I have several Arduino boards that use FTDI chips also plugged into my system through hubs and they were all working just fine before I installed your provided driver. Now they also only function if they are plugged directly into the laptop. I can't operate that way, how do I uninstall the driver or keep your driver from breaking my other devices on the system. Even one of my hard drives that is connected through an Anker 3.0 HUB no longer connects unless directly connected. Another hard drive is still working through the hub. After restarting the mac several times, I got things to work by unplugging the actual powered hub. Unplugging from the computer wasn't enough, I needed to unplug power from the hub before things started to work again. We still need some sort of uninstall instructions. macOS Sierra 10.12.3 MacBook pro Mid 2012 16 Gig ram.
  10. Hello, I am trying to connect to the DAC using petalinux, but I cannot get it to work. When petalinux is booted i get "axi-i2s: probe of 43c00000.axi_i2s_adi failed with error -2", I have tried to find information about this, but so far i haven't found anything. So, what I have done: I have synthesized the template design and imported the said design into Petalinux. I have configured ALSA as this: The device tree for the axi-i2s is as follows: amba_pl: amba_pl { axi_i2s_adi_0: axi_i2s_adi@43c00000 { compatible = "adi,axi-i2s-1.00.a"; reg = <0x43c00000 0x10000>; clocks = <&clkc 15 &clkc 16>; clock-names = "axi", "i2s"; dmas = <&dmac_s 0 &dmac_s 1>; dma-names = "tx", "rx"; xlnx,bclk-pol = <0x0>; xlnx,dma-type = <0x1>; xlnx,has-rx = <0x1>; xlnx,has-tx = <0x1>; xlnx,lrclk-pol = <0x0>; xlnx,num-ch = <0x1>; xlnx,slot-width = <0x18>; }; }; I am deeply grateful for any help, or any examples showing a working DAC interface. Best regards /Jaxc
  11. Kamal prasath balaji

    Digilent myrio Motor adapter

    Digilent driver providing only 0.6A at max for single motor. But I require current upto 1.5A how to overcome this problem. Also there is no braking in motor driver. Is there any option in driver to electrically brake the motor. Thanks in Advance
  12. Hello, I have been struggling for a while now trying to get sound on the ZyBo board. I built images with the OpenEmbedded and Yocto projects where I added the following layers: https://github.com/emcongiu/meta-zybo https://github.com/Xilinx/meta-xilinx I enabled so many recipes that I couldn't remember exactly which ones. As a test, I also tried the Linaro distro provided in this tutorial: https://reference.digilentinc.com/zybo:zybo:zybotguide But still no sound card detected. I really need to work with the audio on this board, how can I enable it ? Thanks in advance