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] Error when upgrading Verilator #2817

Open
1 task done
jason23g opened this issue Mar 9, 2025 · 3 comments
Open
1 task done

[BUG] Error when upgrading Verilator #2817

jason23g opened this issue Mar 9, 2025 · 3 comments
Labels
notCV32A65X It is not an CV32A65X issue Type:Bug For bugs in the RTL, Documentation, Verification environment or Tool and Build system

Comments

@jason23g
Copy link

jason23g commented Mar 9, 2025

Is there an existing CVA6 bug for this?

  • I have searched the existing bug issues

Bug Description

Hello guys,

I am trying to upgrade the Verilator version from 5.008 to 5.028. I changed the version number in both the verif/regress/install-verilator.sh script and in verif/sim/cva6.py, but when I run the smoke-tests.sh script, it fails to verilate. I am wondering if anything else needs to be done besides what I have already done, or if anyone has any idea why this is happening.

Thanks in advance for your time.

verilator_error_5028.txt

@jason23g jason23g added the Type:Bug For bugs in the RTL, Documentation, Verification environment or Tool and Build system label Mar 9, 2025
@jason23g jason23g changed the title [BUG] <title> [BUG] Error when upgrading Verilator Mar 9, 2025
@JeanRochCoulon
Copy link
Contributor

By experience, we know that not all Verilator versions work for the cva6 projet (more due to Verilator weaknesses than cva6 RTL). That is the reason why we fixed the version to a functional one.

@JeanRochCoulon JeanRochCoulon added the notCV32A65X It is not an CV32A65X issue label Mar 10, 2025
@jason23g
Copy link
Author

Okay, I understand. Could you let me know if you have tried any version of Verilator greater than or equal to 5.020?

@valentinThomazic
Copy link
Contributor

@jason23g iirc, we did not manage to use (consistently) Verilator versions greater than 5.008, which is why it is still the versions in the scripts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
notCV32A65X It is not an CV32A65X issue Type:Bug For bugs in the RTL, Documentation, Verification environment or Tool and Build system
Projects
None yet
Development

No branches or pull requests

3 participants