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

make verilate failed #1489

Closed
1 task done
hhhsiang opened this issue Sep 28, 2023 · 24 comments
Closed
1 task done

make verilate failed #1489

hhhsiang opened this issue Sep 28, 2023 · 24 comments
Assignees
Labels
Type:Item-of-task This issue is an item of a larger task.

Comments

@hhhsiang
Copy link

Is there an existing CVA6 bug for this?

  • I have searched the existing bug issues

Bug Description

I've come across a problem much like the one described in #1410. When I run make verilate, it displays the exact same error.
image

I've been struggling with this issue for a while. Any help in finding a solution would be very welcome. Thank you in advance!

@hhhsiang hhhsiang added the Type:Bug For bugs in the RTL, Documentation, Verification environment or Tool and Build system label Sep 28, 2023
@JeanRochCoulon
Copy link
Contributor

Hello @hhhsiang
Which Verilator version do you use ?
Regards

@hhhsiang
Copy link
Author

hhhsiang commented Oct 2, 2023

Hi,@JeanRochCoulon
I use verilator version 4.110

@JeanRochCoulon
Copy link
Contributor

Please refer to the README.md CVA6 repository file, the supported Verilator is not more 4.110. If it works with the recommanded version, do not hesitate to close the issue.

@hhhsiang
Copy link
Author

hhhsiang commented Oct 2, 2023

@JeanRochCoulon I'm sorry, but I couldn't find the information about the required Verilator version in the README.md file.

@JeanRochCoulon
Copy link
Contributor

You are right. The supported Verilator version is 5.008. README.md need to be updated.

@JeanRochCoulon
Copy link
Contributor

I have created #1492 to add information about Verilator version

@hhhsiang
Copy link
Author

hhhsiang commented Oct 2, 2023

@JeanRochCoulon, thanks for you help!
However, I'm not sure how to update the version of verilator. Should I use ./ci/install-verilator.sh , and change the version to 5.008? Like this:
image

After I executed it, I meet the error:
image

@JeanRochCoulon
Copy link
Contributor

You have to execute the verif/regress/install-verilator.sh file. The Verilator5.008 will be installed.

@hhhsiang
Copy link
Author

hhhsiang commented Oct 2, 2023

@JeanRochCoulon, I have tried it, but it show this:
image

@JeanRochCoulon
Copy link
Contributor

The README.md recommands to execute verif/regress/install-cva6.sh.
I suggest to execute it.

@hhhsiang
Copy link
Author

hhhsiang commented Oct 2, 2023

@JeanRochCoulon, it seems like the installation was successful; however, when I execute the command verilator -version, it still indicates version 4.110, as shown below:
image

I also noticed that the make verilate command continues to use Verilator 4.110, which I had previously installed in the directory /home/user/verilator/, but I have since deleted it.
image
Is there a way to ensure the correct Verilator version is being used? Your assistance is greatly appreciated.

@Moschn
Copy link
Contributor

Moschn commented Oct 2, 2023

Your linux/PATH is not configured properly. There are many ways to fix this, but they are not really related to CVA6. I would suggest to get familiar with the PATH environment variable and how your shell searches for executables. A quick google search results in simple tutorials:

@hhhsiang
Copy link
Author

hhhsiang commented Oct 4, 2023

@Moschn, I can now execute bash verif/regress/smoke-tests.sh and bash verif/regress/dv-riscv-tests.sh without encountering any errors. However, I continue to encounter the same error when executing make verilate. Is it conceivable that there may be an issue with the make verilate command? Perhaps the problem lies with fesvr?
Thanks for your help!

@Moschn
Copy link
Contributor

Moschn commented Oct 4, 2023

I just successfully ran make verilate on verilator 4.110 (not the suggested version but still works). I do not know where your problem lies. Maybe you have a very old gcc version. I have never encountered this issue.

@hhhsiang
Copy link
Author

hhhsiang commented Oct 4, 2023

@Moschn ,did you install verilator from ./ci/install-verilator.sh?

@Moschn
Copy link
Contributor

Moschn commented Oct 4, 2023

No i installed manually using the official instructions from verilator

@JeanRochCoulon
Copy link
Contributor

The "make verilate" is not supposed to be executed by user to run a cva6 simulation. To be functional, some variables should be setup like TARGET. The right way is to execute shell scripts like smoke-tests.sh

@hhhsiang
Copy link
Author

hhhsiang commented Oct 6, 2023

@JeanRochCoulon, what if I want to run user-space applications? How should I proceed? According to the CVA6 README, should I execute make verialte followed by running work-ver/Variane_testharness $RISCV/riscv64-unknown-elf/bin/pk hello.elf?
image

Thanks for your help!

JeanRochCoulon added a commit that referenced this issue Oct 6, 2023
README.md how to run a simulation by executing Makefile commands, for instance 'make verilate'. This way does not work because additional variables need to be setup before executing these commands, for instance TARGET=cv64a6_imafdc_sv39. Many GitHub issues request support #1489. This PR removes the getting start related to these commands to keep the way which is support that is to say using cva6.py command.
@JeanRochCoulon
Copy link
Contributor

Please create another GihHub issue when the topic is different.

Please refer to #1505. Make verilate is a deprecated command. The supported command is cva6.py. Please close the issue if you succeed in simulating with cva6.py.

@JeanRochCoulon
Copy link
Contributor

BTW #1499 is related to your new topic.

@hhhsiang
Copy link
Author

hhhsiang commented Oct 6, 2023

@JeanRochCoulon,
To be honest, I'm not entirely certain about the correct steps for running simulations with cva6.py.
#1505 (comment)

@JeanRochCoulon JeanRochCoulon added Type:Item-of-task This issue is an item of a larger task. and removed Type:Bug For bugs in the RTL, Documentation, Verification environment or Tool and Build system labels Oct 24, 2023
@JeanRochCoulon
Copy link
Contributor

Related to #1569

Copy link
Contributor

👋 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 Nov 24, 2023
@github-actions github-actions bot removed the Status:Stale Issue or PR is stale and hasn't received any updates. label Nov 28, 2023
@valentinThomazic
Copy link
Contributor

Hey @hhhsiang did you manage to close your issue ?
If that is the case, could you close it ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type:Item-of-task This issue is an item of a larger task.
Projects
None yet
Development

No branches or pull requests

4 participants