Search the Community

Showing results for tags 'zybo'.



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 338 results

  1. Hello, I want to use the AXI IIC bus Interface found in Vivado to read data from several MLX90393 sensors. My question is about the amount of AXI IIC interfaces needed for this. Is it enough to use only one, or is it necessary to use one for each sensor that will be used? Thanks in advance. MLX90393-Datasheet-Melexis.PDF
  2. I'm trying to develop a video pipeline on the Zybo platform that takes HDMI video in passes it to a custom IP and outputs the new video through VGA. I manage to create a system that takes HDMI and passes the video straight out the VGA interface but when I add in the AXI stream to video IP blocks in I can't seem to get a video out of the VGA. I tried tying all the rst_n and enable on the vid_in_axi4s, axi4s_vid_out and tc off to one but still doesn't output any video on the VGA. I also output the locked signal from the axi4s_vid_out IP to one of the LEDs on the board and it never gets set high. Does anyone have any idea what I might have setup wrong or if I'm missing something?
  3. I am using XADC of Zybo board in DRP mode. I have connected the inputs of the XADC to a potentiometer supplying a voltage in between 0-1 V. I have used the PMOD pins to supply the output to external LEDs. But everytime the board is programmed, the LED outputs show a garbage value which is constant. Changing the potentiometer voltage does not change the outputs. Also resetting the XADC through GPIO buttons has no effect. Please help with the above issue.
  4. Hi I am trying to develop Ethernet transmission with Zybo Z7-10. I tried to add ports like eth_txctl to xdc file, but there is a critical warning I can't understand. You can see pictures in attachments, the ports in my module, the ports I connect pin with, also the project settings. I don't understand why vivado gives my critical warning that the pin is not valid. If I try the ports eth_rxctl and connects it with pin D13, there would't be any warnings. I attached the schematic link as well, where I found the pins and port. I really don't get it, for example, the ports eth_txctl and eth_rxctl are literally on the same block in schematic. According to the schematics, I connect ports and pins, how come there is one work and the other doesn't work? https://reference.digilentinc.com/_media/reference/programmable-logic/zybo-z7/zybo_z7_sch-public.pdf Thanks a lot
  5. I have created a design in Vivado where I have used XADC with Zynq-7000 processor for acquiring a sine wave applied to the auxillary input of XADC. Now I have exported my hardware along with the bitstream file to the SDK. Now I want to create an application project in C/C++ for the corresponding design. I am facing problem in which header files to include and how to configure the code for proper implementation. Please help with the above issue.
  6. Hello, I am having trouble outputting sound on Linux using SSM2603. The SSM2603 device driver loads normally. It is also registered in ALSA sound card list. However, "input / output error" is raised in "alsactl init". ("amixer" is also the same.) It plays when I play wave file with "aplay" but it does not output to "R/LOUT pin" of SSM2603. Regards, Namio
  7. Hello, I have a question about audio. I've already asked about the issue. Another question is "Known Issues" of the BSP provided in "github". (https://github.com/Digilent/Petalinux-Zybo-Z7-10/blob/v2017.2-1/README.md) What does "Audio is currently completely non-functional" mean in "Known Issues"? Does "Zybo Z7-10" mean it is impossible to run audio properly? Do you provide a BSP that solves this problem? We did not have to buy the "Zybo Z7-10" if Audio was not supported. I would appreciate your help in more depth. Regards, Namio
  8. mohammadhgh

    OpenCL on Zybo

    Hello everyone, I am trying to do some projects on Zybo Z7-20 board with Xilinx SDSoC tool. I added the platform files for the board to the SDSoC and now I am able to compile and run C/C++ codes on the board. However when creating a new project, the OpenCL option is not still available. Is there any way to fix this and compile and run OpenCL code on Zybo board? Thanks
  9. I am trying to connect my PMOD MTDS to the Zybo Z7, without Arduino. I have integrated the IP files, connected it via block diagram, and set up a FAT32 microSD with the 2 files that are needed also. When trying to connect to Vivado I can seem to figure out how to get to the console for which I can do MTDS Firmware code so I can do a custom UI. Documentation does not help much with connecting this PMOD. Please advise if you're familiar thanks.
  10. Abhinav Airan

    Pmod GPS not working

    I am using a pmod GPS with a zybo z7-10 board. However, even after running the sample code for the GPS, nothing is being printed on the serial monitor. I'm not entirely sure whether I have connected the pmod right, since there are 6 pins on the GPS but 12 pins on the pmod port. Nowhere has anyone mentioned whether one should connect the pmod GPS on the top six pins or the bottom six pins. Am I doing something wrong here or is there some other problem? I have also attached a picture of my block diagram for reference.
  11. i want to work on a video project which board will be better zybo or pynq . as i have studied that pynq has unbufferd hdmi. suggestions will be highly appreciated. Thanks
  12. theUltimateSource

    SDSoC - couple of questions

    hello, I have a couple of questions about your SDSoC platforms: what is the difference between the platforms reVISION-Zybo-Z7-20 and SDSoC-Zybo-Z7-20? is there an example application for video stream (for example, HDMI-IN -> HDMI-OUT)? what is the use case for the XADC interface in the reVISION platform? what is the best way to start with reVISION? For example, can I follow the reVISION Getting Started Guide on zybo? thank you
  13. Hello, I am still working on Embedded Linux Tutorial Zybo http://www.instructables.com/id/Embedded-Linux-Tutorial-Zybo/, and I get a segmentation fault on the C blink code where puts is writing to the /proc/myled. #include <stdio.h> #include <stdlib.h> #include <unistd.h> int main(){ FILE *fp; while(1){ printf("open /proc/myled 1\n"); fp = fopen("/proc/myled", "w"); if (fp=NULL){ printf("cannot open /proc/myled for write\b"); return -1; } printf("fputs 0x0F\n"); fputs("0x0F\n", fp); //SEGMENTATION FAULT HAPPENS HERE printf("fclose 1\n"); fclose(fp); sleep(1); In the myled driver I put some printk to see which functions get called. When using the blink.c, the proc_myled_write never even runs. When I interact with the driver without the C code using echo "0x05\n" >> /proc/myled in the terminal, the proc_myled_write runs, there is no segmentation fault and the LEDs change state. zynq> echo "0x05\n" >> /proc/myled proc_myled_open proc_myled_open single_open proc_myled_open end proc_myled_write: 5 Here is the myled.c file: #include <linux/kernel.h> #include <linux/module.h> #include <asm/uaccess.h> /* Needed for copy_from_user */ #include <asm/io.h> /* Needed for IO Read/Write Functions */ #include <linux/proc_fs.h> /* Needed for Proc File System Functions */ #include <linux/seq_file.h> /* Needed for Sequence File Operations */ #include <linux/platform_device.h> /* Needed for Platform Driver Functions */ #include<linux/slab.h> /* Define Driver Name */ #define DRIVER_NAME "myled" unsigned long *base_addr; /* Vitual Base Address */ struct resource *res; /* Device Resource Structure */ unsigned long remap_size; /* Device Memory Size */ /* Write operation for /proc/myled * ----------------------------------- * When user cat a string to /proc/myled file, the string will be stored in * const char __user *buf. This function will copy the string from user * space into kernel space, and change it to an unsigned long value. * It will then write the value to the register of myled controller, * and turn on the corresponding LEDs eventually. */ static ssize_t proc_myled_write(struct file *file, const char __user * buf, size_t count, loff_t * ppos) { char myled_phrase[16]; u32 myled_value; printk(KERN_INFO "proc_myled_write:"); if (count < 11) { if (copy_from_user(myled_phrase, buf, count)) return -EFAULT; myled_phrase[count] = '\0'; } myled_value = simple_strtoul(myled_phrase, NULL, 0); printk(KERN_INFO "%i\n", myled_value); wmb(); iowrite32(myled_value, base_addr); return count; } /* Callback function when opening file /proc/myled * ------------------------------------------------------ * Read the register value of myled controller, print the value to * the sequence file struct seq_file *p. In file open operation for /proc/myled * this callback function will be called first to fill up the seq_file, * and seq_read function will print whatever in seq_file to the terminal. */ static int proc_myled_show(struct seq_file *p, void *v) { printk(KERN_INFO "proc_myled_show\n"); u32 myled_value; printk(KERN_INFO "proc_myled_show ioread32\n"); myled_value = ioread32(base_addr); printk(KERN_INFO "proc_myled_show seq_printf\n"); seq_printf(p, "0x%x", myled_value); return 0; } /* Open function for /proc/myled * ------------------------------------ * When user want to read /proc/myled (i.e. cat /proc/myled), the open function * will be called first. In the open function, a seq_file will be prepared and the * status of myled will be filled into the seq_file by proc_myled_show function. */ static int proc_myled_open(struct inode *inode, struct file *file) { unsigned int size = 16; char *buf; struct seq_file *m; int res; printk(KERN_INFO "proc_myled_open\n"); buf = (char *)kmalloc(size * sizeof(char), GFP_KERNEL); if (!buf) return -ENOMEM; printk(KERN_INFO "proc_myled_open single_open\n"); res = single_open(file, proc_myled_show, NULL); if (!res) { m = file->private_data; m->buf = buf; m->size = size; } else { kfree(buf); } printk(KERN_INFO "proc_myled_open end\n"); return res; } /* File Operations for /proc/myled */ static const struct file_operations proc_myled_operations = { .open = proc_myled_open, .read = seq_read, .write = proc_myled_write, .llseek = seq_lseek, .release = single_release }; /* Shutdown function for myled * ----------------------------------- * Before myled shutdown, turn-off all the leds */ static void myled_shutdown(struct platform_device *pdev) { printk(KERN_INFO "myled_shutdown"); iowrite32(0, base_addr); } /* Remove function for myled * ---------------------------------- * When myled module is removed, turn off all the leds first, * release virtual address and the memory region requested. */ static int myled_remove(struct platform_device *pdev) { printk(KERN_INFO "myled_remove"); myled_shutdown(pdev); /* Remove /proc/myled entry */ remove_proc_entry(DRIVER_NAME, NULL); /* Release mapped virtual address */ iounmap(base_addr); /* Release the region */ release_mem_region(res->start, remap_size); return 0; } /* Device Probe function for myled * ------------------------------------ * Get the resource structure from the information in device tree. * request the memory regioon needed for the controller, and map it into * kernel virtual memory space. Create an entry under /proc file system * and register file operations for that entry. */ static int myled_probe(struct platform_device *pdev) { printk(KERN_INFO "myled_probe\n"); struct proc_dir_entry *myled_proc_entry; int ret = 0; res = platform_get_resource(pdev, IORESOURCE_MEM, 0); if (!res) { dev_err(&pdev->dev, "No memory resource\n"); return -ENODEV; } printk(KERN_INFO "myled_probe res->star 0x%08lxt\n", res->start ); remap_size = res->end - res->start + 1; if (!request_mem_region(res->start, remap_size, pdev->name)) { dev_err(&pdev->dev, "Cannot request IO\n"); return -ENXIO; } base_addr = ioremap(res->start, remap_size); if (base_addr == NULL) { dev_err(&pdev->dev, "Couldn't ioremap memory at 0x%08lx\n", (unsigned long)res->start); ret = -ENOMEM; goto err_release_region; } myled_proc_entry = proc_create(DRIVER_NAME, 0, NULL, &proc_myled_operations); if (myled_proc_entry == NULL) { dev_err(&pdev->dev, "Couldn't create proc entry\n"); ret = -ENOMEM; goto err_create_proc_entry; } printk(KERN_INFO DRIVER_NAME " probed at VA 0x%08lx\n", (unsigned long) base_addr); return 0; err_create_proc_entry: iounmap(base_addr); err_release_region: release_mem_region(res->start, remap_size); return ret; } /* device match table to match with device node in device tree */ static const struct of_device_id myled_of_match[] = { {.compatible = "dglnt_myled-1.00.a"}, {}, }; MODULE_DEVICE_TABLE(of, myled_of_match); /* platform driver structure for myled driver */ static struct platform_driver myled_driver = { .driver = { .name = DRIVER_NAME, .owner = THIS_MODULE, .of_match_table = myled_of_match}, .probe = myled_probe, .remove = myled_remove, .shutdown = myled_shutdown }; /* Register myled platform driver */ module_platform_driver(myled_driver); /* Module Informations */ MODULE_AUTHOR("Digilent, Inc."); MODULE_LICENSE("GPL"); MODULE_DESCRIPTION(DRIVER_NAME ": MYLED driver (Simple Version)"); MODULE_ALIAS(DRIVER_NAME); Any ideas? Thanks, Frank
  14. mbo

    Zybo and PmodCAN

    Hello members, I have the Zybo-Z7 Board and I want to connect it with other Zybo-Z7 Board via CAN. The board has an integrated CAN Controller and I need following PmodCAN-Connector which has also can controller integrated. http://store.digilentinc.com/pmod-can-can-2-0b-controller-with-integrated-transceiver/ Which CAN Controller shall I use and how do I make it work? I have implemented a basic design for Zybo in Vivado and added the IP core for PmodCAN. Is something more I need? Cheers, mb
  15. Ankit

    USB OTG on Zybo does not work

    @Bianca @Rainer Urian can you help me ? i am also working on zybo board and suffering from same problem. my usb port ( j10 and j9 ) are not getting detected . can you tell me how to resolve this issue ?
  16. lukap

    I2S IP core and AXI DMA

    Hello. I'm doing a sound analyzing project on the Zybo board and I'm having hard time using the AXI DMA for transferring data from the I2S controller to RAM. I'm using the I2S controller from the Digilent's github. I am trying to do the data transferring "properly" with a DMA and as there are no PL330 examples to be found (at least not bare metal, which is what I'm doing), I'm trying to use the AXI DMA. However I can only get a few samples to the RAM. I don't really know if there's a problem in the I2S controller or in my configuration of the DMA, so I'd first like to know if I understand how the DMA works. I'm basing my code on the Xilinx' interrupt DMA example, so I think the initializations and similar are done correctly. What I'm unsure of is the following: I start the S2MM (Stream to Memory Mapped - I2S to RAM) transfer with the number of bytes to be transferred and expect the I2S controller to only output data when it has it (similarly as in the Zybo base system example, except that there the fifo status register is checked, but for the streaming interface I expect this to be taken care of in the IP). So if I want to transfer 5 seconds of audio, I start the transfer of 5 s * 48000 samples/s * 2 (channels) * 4 bytes/sample For now I then wait for the interrupt in which a flag is set, so that I know the transfer has finished. I expect this to last 5 seconds but instead it happens in a couple hundred ms (I don't have an o-scope) and only a few samples arrive. So is my understanding correct? Has anyone ever tried interfacing the I2S core to an AXI DMA?
  17. sage

    Zybo board repair

    Hello. I have a zybo board that is not working. I was told that a 12 volt power supply was used instead of a 5 volt power supply. Is there anyway that it could be repaired e.g. changing a fuse or chip. thank you. Asim
  18. Hello, I am currently following the first tutorial of the Zynq Book using the Zybo board and I am t the part where I am to launch the SDK after exporting hardware and receive the following error after the SDK loads up: 'Importing Hardware Specification' has encountered a problem. An internal error occurred during: "Importing Hardware Specification". java.lang.NullPointerException. Attached is a screenshot of the error. Thank you for any help.
  19. Kampi

    Ethernet for Zybo Linux

    Hello, my ethernet for my Zybo doesn´t work with Linux. I use this linaro as my rootfs. Additional I follow these instructions to create my Design with all necessary files. My Linux boots up, but I got the message "no phy found". I´ve update my device tree with this: ZyboEthernet.dtsi &gem0 { #address-cells = <1>; #size-cells = <0>; clock-names = "ref_clk", "aper_clk"; clocks = <&clkc 13>, <&clkc 30>; compatible = "cdns,zynq-gem", "cdns,gem"; interrupt-parent = <&intc>; interrupts = <0 22 4>; local-mac-address = [00 0a 35 00 00 00]; phy-handle = <&phy0>; phy-mode = "rgmii-id"; status = "okay"; reg = <0xe000b000 0x1000>; xlnx,eth-mode = <0x1>; xlnx,has-mdio = <0x1>; xlnx,ptp-enet-clock = <111111115>; mdio { #address-cells = <1>; #size-cells = <0>; phy0: phy@1 { compatible = "realtek,RTL8211E"; device_type = "ethernet-phy"; reg = <1>; }; }; }; Bootargs.dts /include/ "system-top.dts" /include/ "ZyboEthernet.dtsi" / { chosen { bootargs = "console=ttyPS0,115200n8 consoleblank=0 root=/dev/mmcblk0p2 rw rootwait earlyprintk"; linux,stdout-path = "&uart1"; }; }; How can I get my ethernet running? Thank you for help!
  20. cgarry

    HDMI In to VGA out on Zybo

    I'm trying create a PL subsystem that takes a HDMI video in and outputs it on the VGA. I got the digilent IP from this github https://github.com/Digilent/ZYBO.git and I created a HDMI in to VGA out loop in Vivado as shown below I have set the clock wizard up to provide 200MHz to the dvi2rgb block and the clock wizard block has an input clock 125MHz. I programmed the dvi2rgb block with the following config After trying to generate the bitstream for this I'm getting critical errors at the implementation stage saying it can't meet timing. It managed to generate the bitstream but its output an video from the VGA. Any ideas what is causing these timing errors? or where I am going wrong with the implementation? ZYBO_Master.xdc.txt
  21. 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
  22. Hello,

    how to use the FMC (in zynq7000 zedboard) as A/D converter?

  23. Hello, I did PATH=$PATH:~/u-boot-Digilent-Dev/tools/ and now I am stuck at step 36 Make Uramdisk http://www.instructables.com/id/Embedded-Linux-Tutorial-Zybo/. Please help. knarf@knarf-VirtualBox:~$ ./u-boot-Digilent-Dev/tools/mkimage -A arm -T ramdisk -c gzip -d ./ramdisk8M.image.gz uramdisk.image.gz ./u-boot-Digilent-Dev/tools/mkimage: Can't open ./ramdisk8M.image.gz: No such file or directory It created a uramdisk.image.gz file of 64 bytes. I didn't make a Tutorial directory, so I work in my home directory. The previous step compiled the kernel and put the kernel images in /home/knarf/Linux-Digilent-Dev/arch/arm/boot/. Also, if I use a ramdisk, that means I don't use a filesystem like Linaro. Wouldn't most of the usual Linux directories be missing? (First, I just wan't to finish the tutorial, later I would redo it with Linaro.) Frank
  24. I tried to synthesise the Zybo HDMI In project https://github.com/Digilent/Zybo-hdmi-in for the latest Vivado 2017.4.1. Without changing anything from the Block design and just upgrading all IP Cores in order to start the synthesis, the timing will not be met: Slack: - 6.327 ns The IP Cores are generated globally. How I can fix this problem?
  25. yohboy

    bitstream and yocto

    Hi everyone ! I'm working on the zybo board. There is a yocto linux on a SD card, and the system boot on the SD card. This works very well. Now I really enjoy if I could understand how to link vivado (to generate bitstream) and yocto ! I'm a little lost about this link. I read that some people say to use the layers meta-xilinx-tools ? Someone already use it ? I don't really understand how to use it, and how manage the boot.bin, u-boot, fsbl ... etc Could you help me please ? best regards, Yohan