Giter Site home page Giter Site logo

warclab / zycap Goto Github PK

View Code? Open in Web Editor NEW
10.0 10.0 12.0 44.67 MB

Zynq PR Management

Shell 0.10% C 3.65% C++ 0.03% Tcl 0.59% VHDL 78.46% Stata 0.07% SystemVerilog 0.05% Verilog 3.95% Makefile 0.01% HTML 10.30% XSLT 0.95% CSS 0.01% Batchfile 0.14% JavaScript 0.02% Coq 1.67% Perl 0.01%

zycap's People

Contributors

sfahmy avatar shreejithshanker avatar vipinkmenon avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

zycap's Issues

Linux Image

Hello,
I'm trying to figure out if this system would still run on the current vivado systems.
Unfortunately the Image is no longer on the dropbox referred in the repo.
Any chance there is another way to reach it

Program hangs after PR

Hello,

I want to start with expressing my thankfulness for the tutorial file you prepared. Even though, there has been years apart and I am using a new version of Vivado (2017.3), I could easily follow the tutorial. However, at a point I stuck and would like to ask your guidance if possible.

When I follow the steps to run ZyCAP with Vivado using a baremetal test application, I receive the following dump on the UART console, but nothing more. It basically hangs there. Unfortunately, I -kind of- do not know what part to look it.

Reading data from register before PR
Register content is FCFCFCFC
Starting Reconfiguration
Reconfiguration speed: 1 MBytes/sec

Here I suspect of the bin files. The bif file example on the tutorial does not create two different bin files for the two bit files. Might it be an update in the bootgen? To overcome I created individual bif files for both modes, and created the bin files separately; however, I could not get the expected result at program's execution.

Moreover, I tried creating the bin files using Vivado's write_bitstream -bin_file. Weirdly, it creates the bin file which is not at the same size as the one bootgen created. There is 24 bytes difference in file sizes. With that bin file, the execution does not hang, it steps further; however, the new partial reconfiguration is not processed. I still get the same behaviour even though the reconfiguration returns with success. Here is the dump:

Reading data from register before PR
Register content is FCFCFCFC
Starting Reconfiguration
Reconfiguration speed: 1 MBytes/sec
Reading data from register after PR
Register content is FCFCFCFC

I would like to kindly as if you have any guidance to solve this issue?

Kind Regards,

Furkan

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.