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

Do we still need install-cva6.sh? #1727

Closed
MikeOpenHWGroup opened this issue Dec 19, 2023 · 5 comments
Closed

Do we still need install-cva6.sh? #1727

MikeOpenHWGroup opened this issue Dec 19, 2023 · 5 comments
Assignees
Labels
Component:Tool-and-build For issues in the tool and build flow (e.g. Makefile, FuseSoc, etc.) Type:Question For general questions

Comments

@MikeOpenHWGroup
Copy link
Member

MikeOpenHWGroup commented Dec 19, 2023

Now that the UVM environment has been integrated into this repo and core-v-verif is a submodule of this repo it is not clear that the purpose of the install-cva6.sh script is still needed.

@MikeOpenHWGroup MikeOpenHWGroup added the Type:Question For general questions label Dec 19, 2023
@MikeOpenHWGroup MikeOpenHWGroup added the Component:Tool-and-build For issues in the tool and build flow (e.g. Makefile, FuseSoc, etc.) label Dec 19, 2023
@cathales
Copy link
Contributor

My 2 cents: when I refactored the submodule thing, I had tried to just remove the file but it didn’t work as it seems to export environment variables that we need. I did not investigate much.

@MikeOpenHWGroup
Copy link
Member Author

Yes, you are right @cathales, the file as it currently exists cannot be removed. However, since it does not actually install the CVA6, it should at least be re-named, perhaps to install-tools.sh since its main function is to install Verilator and Spike.

My preference would be to move the functionality currently in install-cva6.sh to other scripts.

@valentinThomazic
Copy link
Contributor

valentinThomazic commented Dec 27, 2023

install-cva6.sh (and its subscripts) and install-riscv-dv.sh set all environment variables required to run simulations with cva6.py and install the tools if they are not found. The only environment variable the user has to manually set is the toolchain location which is somehow convenient.
The fact they do both could indeed be misleading since they are named install-X.sh.

Maybe they could be turned into a setup-sim.sh setting the simulation tools and the appropriate environment variables requiring the tools to have been installed before.
This could also be a one-time thing which would create a .env file loaded by cva.py so the users would not have to source theses scripts each time they want to simulate the cva6.

@JeanRochCoulon
Copy link
Contributor

#1741 has been merged. @MikeOpenHWGroup I let you close the issue (if you agree of course).

@JeanRochCoulon
Copy link
Contributor

As the file has been removed, I close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component:Tool-and-build For issues in the tool and build flow (e.g. Makefile, FuseSoc, etc.) Type:Question For general questions
Projects
None yet
Development

No branches or pull requests

4 participants