-
Notifications
You must be signed in to change notification settings - Fork 762
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
[entropy_src/dv] Find out what happened to the group coverage #20565
Comments
Status update: |
Status update #2: Furthermore, since the seed that is generated for systemverilog is not only used for seeding the systemverilog random variables, we can't just change this seed to 32 bits. A potential solution is to take the lowest 32 bits of the 256 bit seed and use it for the command that is issued when the test is being deployed. If I understand correctly, this happens in |
Description
Between the 16. and the 19. of October something caused the entropy source coverage to plummet to around 30 to 40%.
To verify this I ran the following command with a 0.1 reseed-multiplier:
./util/dvsim/dvsim.py hw/ip/entropy_src/dv/entropy_src_sim_cfg.hjson -i all -t vcs --reseed-multiplier 0.1 --cov
We need to find out what happened and fix this issue.
The text was updated successfully, but these errors were encountered: