Git Product home page Git Product logo

Comments (4)

michael-platzer avatar michael-platzer commented on July 22, 2024

Hi @Nikhil-311293,

this error indicates that the width of the VLSU's operands does not match the width of Vicuna's memory interface. In your configuration file the width of the VLSU is configured to 32 bits, hence the memory interface must also be 32 bits wide. Unfortunately Vivado does not print the full error message, thus I cannot see which value you have provided for the memory interface width.

The width of Vicuna's memory interface is controlled by the parameter XIF_MEM_W of the vproc_core module or the parameter VMEM_W of the vproc_top module. Set either of these parameters to 32 and you should no longer get that error.

from vicuna.

Nikhil-311293 avatar Nikhil-311293 commented on July 22, 2024

Hi @michael-platzer

With your suggestions now I'm able to synthesize the vicuna vector coprocessor for Genesys2 board using Ibex core.
Thank you for your time.

Now I'll have to implement the design and generate the bitstream for the same.

I wanted to ask this one thing, can I port the same design for other Xilinx FPGA e.g. VCU118 ultrascale FPGA?

from vicuna.

michael-platzer avatar michael-platzer commented on July 22, 2024

Hi @Nikhil-311293,

yes, the design should be portable between Xilinx FPGAs. I am unsure if the primitives used by the ultrascale FGPAs are the same as those used by the 7 series FPGAs, so there might some adaptions required, but these should be rather straightforward.

Have a look at the README in the demo subdirectory, that gives some instructions on how to add another board.

from vicuna.

Nikhil-311293 avatar Nikhil-311293 commented on July 22, 2024

Hi @michael-platzer

After being able to successfully synthesize the vicuna coprocessor for Xilinx's Virtex Ultrascale FPGA, now I'm trying to implement the design and generate the bitstream for it.

My ultimate aim is boot Linux on it run few simple example programs on it. The problem I'm getting now is: referring as you suggested about the demo and sw subdirectory ---->

Do I need to put constraints for mem_req_o, mem_addr_o, mem_wdata_o etc ports which are declared in the top module vproc_top.sv??

or Do I need to initialize the MIG IP from Xilinx to serve this purpose?

As the constraints used in demo subdirectory are exclusively for UART test program, I believe.

I've attached screenshot below to illustrate this. How shall I move ahead in this particular task? Your suggestions will be extremely useful in this further progress.

vivado_project_overview

Thank you in advance.

from vicuna.

Related Issues (20)

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.