Giter Site home page Giter Site logo

Comments (7)

pengpeng-lian avatar pengpeng-lian commented on August 15, 2024

Could it be because "set ::env(VERILOG_FILES_BLACKBOX) ""? BLACKBOX this parameter?

from riscduino.

pengpeng-lian avatar pengpeng-lian commented on August 15, 2024

Could it be because "set ::env(VERILOG_FILES_BLACKBOX) ""? BLACKBOX this parameter?

from riscduino.

dineshannayya avatar dineshannayya commented on August 15, 2024

Each Macro are separately Hardened and Integrated as block box at user_project_wrapper. If you include all the RTL at user_project_wrapper tool will not be able harden full design in one go.
You need to first run sub macro harden scripts and followed by user_project_wrapper final integration

make pinmux
make uart_i2cm_usb_spi_top
make wb_host
make ycr_core_top
make ycr_iconnect
make qspim_top
make wb_interconnect
make ycr_intf

make user_project_wrapper

from riscduino.

pengpeng-lian avatar pengpeng-lian commented on August 15, 2024

Our team had questions, why separate integrations? Instead of using the total project which contains all the RTL code to integrate at once? Is there a flaw in doing this?

from riscduino.

pengpeng-lian avatar pengpeng-lian commented on August 15, 2024

Each Macro are separately Hardened and Integrated as block box at user_project_wrapper. If you include all the RTL at user_project_wrapper tool will not be able harden full design in one go. You need to first run sub macro harden scripts and followed by user_project_wrapper final integration

make pinmux make uart_i2cm_usb_spi_top make wb_host make ycr_core_top make ycr_iconnect make qspim_top make wb_interconnect make ycr_intf

make user_project_wrapper

Sorry for the late reply, thank you very much for your answer.
Wouldn't it be more automatic to execute the "make master project" only once?
What is the purpose of this separate integration?

from riscduino.

dineshannayya avatar dineshannayya commented on August 15, 2024

Current Makefile flow does call automatically all the sub macro. I prefer to run the each macro on need basis to avoid long run time. As most of the time design changes are specific to one macro. For each top-level integration update, you don't need to re-harden all the block.

from riscduino.

pengpeng-lian avatar pengpeng-lian commented on August 15, 2024

Current Makefile flow does call automatically all the sub macro. I prefer to run the each macro on need basis to avoid long run time. As most of the time design changes are specific to one macro. For each top-level integration update, you don't need to re-harden all the block.

Thanks for the reply, very useful for me, really appreciate it, solved my problem!

from riscduino.

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.