Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using a newer chipyard/firesim version? #359

Open
AnjelicaB opened this issue Jun 12, 2024 · 5 comments
Open

Using a newer chipyard/firesim version? #359

AnjelicaB opened this issue Jun 12, 2024 · 5 comments

Comments

@AnjelicaB
Copy link

I was just wondering if there's a particular reason that the readme said to use the Chipyard 1.9.1 version, instead of newer versions (eg 1.10 or 1.11). Additionally, if I want to run FireSim with Gemmini on a U280 board, I need the version of Firesim that is 1.17 +.

Could I generate a Gemmini accelerator using Chipyard 1.11 and run a simulation on Firesim 1.18 with Xilinx U280 board?

@jerryz123
Copy link
Contributor

The README in this repo has not been updated in a while.

Generally, the versions of all the projects referenced by chipyard/main will work together, and will support recent features in chipyard/firesim.

@AnjelicaB
Copy link
Author

AnjelicaB commented Jun 25, 2024

I'm a still a little confused about the different chipyard/gemmini/firesim versions...If I run the steps:

cd generators/gemmini
git config remote.origin.fetch "+refs/heads/:refs/remotes/origin/"
git fetch && git checkout v0.7.1

with Chipyard 1.11.0, build-verilator fails with version conflicts. I'm using Chipyard 1.11.0 because it sets up Firesim 1.18.0, which is compatible with a U280 FPGA (since I don't have F1 instances).

I've skipped these steps completely and Verilator builds fine, but run-verilator fails with:

(/home/anjelica/chipyard/.conda-env) anjelica@genie05:~/chipyard/generators/gemmini$ ./scripts/run-verilator.sh template
./scripts/run-verilator.sh: line 91: ./simulator-chipyard-CustomGemminiSoCConfig: No such file or directory

I understand that the error is probably because I didn't follow the Gemmini installation script completely, but is there a way to work around this problem?

@shirohasuki
Copy link

@AnjelicaB I'm having the same problem, I think it's due to chipyard version upgrade (previously it was fine to run verilator scripts in chipyard 1.9.1). Did you solve the problem?

@AnjelicaB
Copy link
Author

AnjelicaB commented Sep 9, 2024 via email

@shirohasuki
Copy link

Thanks for the reply, I'm also experimenting with verilator in 1.9.1 and running firesim in 1.11 now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants