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

Formal: Roadmap #1459

Open
silabs-robin opened this issue Oct 27, 2022 · 2 comments
Open

Formal: Roadmap #1459

silabs-robin opened this issue Oct 27, 2022 · 2 comments
Labels
cv32e40s cv32e40x formal Anything related to properties, asserts, covers and assumptions used in FV. improvement Issues to highlight long-term improvements in core-v-verif

Comments

@silabs-robin
Copy link
Contributor

silabs-robin commented Oct 27, 2022

Task Outcome

Formal support needs improvements, more features, better integration, etc.

Background information

Initial formal scripts for 40s/x has been implemented for Jasper, but there is still more to clean up.

Location Information

  • Common files: mk/fv/
  • 40s: cv32e40s/fv/
  • 40x: cv32e40x/fv

Completion Criteria

TODO

Additional context

Ideas for improvement:

  • Move common functionality to shared directory (e.g. mk/fv/)
  • Make sure all assumes/etc are included, so assertions can be expected to pass
  • Add tb for Onespin-specific assertions
  • Support for more tools {Jasper, Questa, Onespin}

Known issues:

Fixed:

@MikeOpenHWGroup MikeOpenHWGroup added formal Anything related to properties, asserts, covers and assumptions used in FV. cv32e40x cv32e40s labels Nov 17, 2022
@silabs-robin
Copy link
Contributor Author

History:

  • Setup initial testbench-scripts
  • Port from 40x to 40s
  • Create future-plans github-issues
  • Add "formal" github-label
  • ?

(I might or might not maintain this list as we progress.)

@silabs-robin silabs-robin changed the title Formal: Improvements Formal: Roadmap Nov 21, 2022
@silabs-robin
Copy link
Contributor Author

Idea: Before I forget, adding support for tests/cfg/*.yaml might be easy?

The formal makefile already sources some mk/* file(s)(?), so whatever is in there should be visible from the formal makefile.
And the cfgyaml2make script seems to just define some env variables like COMPILE_FLAGS.

Ergo, it should simply be a matter of 1) passing the appropriate env variable to the call to e.g. jasper, and then 2) use CFG=someconfig when calling make?

@silabs-robin silabs-robin added the improvement Issues to highlight long-term improvements in core-v-verif label Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cv32e40s cv32e40x formal Anything related to properties, asserts, covers and assumptions used in FV. improvement Issues to highlight long-term improvements in core-v-verif
Projects
None yet
Development

No branches or pull requests

2 participants