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

[BUG] cva6/core/Flist.cva6 mentions " ENV variable CVA6_REPO_DIR" but there are others #1597

Closed
1 task done
rajatkmitra opened this issue Nov 5, 2023 · 9 comments
Closed
1 task done
Assignees
Labels
Component:Doc For issues in the Documentation (e.g. for README.md files) Type:Question For general questions

Comments

@rajatkmitra
Copy link

Is there an existing CVA6 bug for this?

  • I have searched the existing bug issues

Bug Description

The header should also mention that HPDCACHE_DIR and HPDCACHE_TARGET_CFG need to be set. I noticed that HPCACHE_DIR can easily be inferred as it already resides under -
cva6/core/cache_subsystem/hpdcache/
So why do we need a seperate macro for it ? Also where do I find the options for HPDCACHE_TARGET_CFG?

@rajatkmitra rajatkmitra added the Type:Bug For bugs in the RTL, Documentation, Verification environment or Tool and Build system label Nov 5, 2023
@MikeOpenHWGroup MikeOpenHWGroup added Type:Question For general questions and removed Type:Bug For bugs in the RTL, Documentation, Verification environment or Tool and Build system labels Nov 6, 2023
@MikeOpenHWGroup
Copy link
Member

Hi @rajatkmitra, thanks for your interest in OpenHW and CVA6. We are updating our script-ware and associated documentation to simplify supporting CVA6 and also to enable compilation of multiple configurations of the CVA6. We will ensure your questions are addressed in a future update of the docs.

@MikeOpenHWGroup MikeOpenHWGroup added the Component:Doc For issues in the Documentation (e.g. for README.md files) label Nov 6, 2023
@rajatkmitra
Copy link
Author

Many thanks @MikeOpenHWGroup !!
--Raj

@JeanRochCoulon
Copy link
Contributor

JeanRochCoulon commented Nov 7, 2023

Hello @rajatkmitra
You do not need to setup these variables when using cva6.py, which is the recommended way to simulate, except for the pk, which is under fixing. Do you get the issue using pk?

@rajatkmitra
Copy link
Author

rajatkmitra commented Nov 7, 2023

Hi @JeanRochCoulon
As you noted in the othere post #1358 , I had some difficulties using pk.. The instructions were not clear. But @valentinThomazic
clarified the directions. I noticed that the default Makefile is looking for verilator target in cva6/tmp. Again this was missing from the instructions. I have still to try using pk and will inform shortly if that was successful. My goal is to replace verilator with Xcelium and then use pk + Xcelium. If that is successful I plan to run ariane SoC on emulator - Z2.

Copy link
Contributor

github-actions bot commented Dec 8, 2023

👋 Hi there!

This issue seems inactive. Need more help? Feel free to update us. If there are no updates within the next few days, we'll go ahead and close this issue. 😊

@github-actions github-actions bot added the Status:Stale Issue or PR is stale and hasn't received any updates. label Dec 8, 2023
@JeanRochCoulon
Copy link
Contributor

Hello @rajatkmitra
@valentinThomazic has just updated the README.md. Pk support has been removed but recommandations to simulate CVA6 updated. Can you review it to give us your feedback ?

@github-actions github-actions bot removed the Status:Stale Issue or PR is stale and hasn't received any updates. label Dec 9, 2023
@rajatkmitra
Copy link
Author

Hi @JeanRochCoulon
Apologies for the delay.. Yes I will try this and inform on Monday

Copy link
Contributor

github-actions bot commented Jan 9, 2024

👋 Hi there!

This issue seems inactive. Need more help? Feel free to update us. If there are no updates within the next few days, we'll go ahead and close this issue. 😊

@github-actions github-actions bot added the Status:Stale Issue or PR is stale and hasn't received any updates. label Jan 9, 2024
@rajatkmitra
Copy link
Author

Yes it's okay to close... Following up with @valentinThomazic on a separate thread...

@JeanRochCoulon JeanRochCoulon removed the Status:Stale Issue or PR is stale and hasn't received any updates. label Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component:Doc For issues in the Documentation (e.g. for README.md files) Type:Question For general questions
Projects
None yet
Development

No branches or pull requests

4 participants