Search the Community

Showing results for tags 'vivado 2015.4'.



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

  1. Please let me apologize, but I'm back with this issue. I downloaded the original Vivado 2015.4 OOB project, located in "Github as the Projects/user_demo directory of this repo", as gently explained by Artvb I follow the instructions, generate the project from tcl using Vivado 2015.4, and I achieved a complete Vivado 2015.4 project. Then I exported the HDF and create a local SDK15.4 project. Compiled, fine. then I downloaded to the Genesys2.... this time too the Displayport does not work (all the remaining are ok). You can imagine, I' quite disappointed. Or I'm applying every time the same mistake in the preparation of the design, or there is something else. Now, I checked possible differences between my recompiled design and what is available from GIT I recompiled an SDK 2015.4 application "G2demo" from scratch, and then i compared with downloaded files from git I noted that, while the "downloaded_system.hdf" file available in GIT sizes 1.441 Kbyte, the one regenerated by compilation spans 1535 Kbyte, That is rather strange. .lnk and .mss generated from them are exactly the same in both cases. So, I'm currently blocked, Any suggestion may be of help.
  2. Hi Digilent, zedboard, vivado 2015.4, petalinux 2015.4, /dev/zed_oled, pmodoled-gpio.ko I am working on zedboard to enable onboard-OLED display. First vivado outputs bitstream hardware, then petalinux generates " BOOT.BIN + Image.ub ", finally zedboard bootup by the SD card. " insmod pmodoled-gpio.ko " does bring /dev/zed_oled . However, " cat logo.bin > /dev/zed_oled " has nothing to display. Then I decided to add oled block design in vivado project. I tried two different versions, including tamu https://github.com/ama142/ZedboardOLED-v1.0-IP and Digilent https://github.com/Digilent/vivado-library/tree/master/ip/Pmods/PmodOLED_v1_0 . After making external pin assignment, Vivado / petalinux all functions. However, there is still no outputs on OLED. Please advise how to turn on OLED in petalinux/vivado. Thanks in advance Mike (P.S. OLED by itself works well on OOB package with digilent logo output)
  3. When trying to run the Digilent bsd project for Arty, Vivado 2015.4 cannot run Bitgen due to 2 critical warnings. I have been able to run the Digilent Xadc_Demo and GPIO projects successfully with no problems. I'm wondering if there is an error in the .tcl script for the bsd project. I've attached the Vivado critical warning messages. I'm new to both VIvado and Arty so I would appreciate help.