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

UVM testbench #110

Open
kiniry opened this issue Mar 30, 2022 · 0 comments
Open

UVM testbench #110

kiniry opened this issue Mar 30, 2022 · 0 comments
Labels
assurance Issues that relate to the assurance of the system, whether via models, code, informal, or formal. cryptol Issues related to our Cryptol specifications, or use thereof. ENHANCEMENT New feature or request FEATURE hardware Q/A Quality assurance issue; validation, testing, and formal assurance. Someday Issues that are not required by our current contract, but we'd like to attend to someday. specifications Issues that relate to system specifications, whether of models, code, protocols, or otherwise. suggestion verification
Milestone

Comments

@kiniry
Copy link
Member

kiniry commented Mar 30, 2022

Explore generating a UVM testbench from our Cryptol model. Such a testbench would translate Cryptol properties to UVM properties, which would in turn be validated through runtime verification on all hardware digital twins and the deployment platform as well as formally verified using yosys &c.

This is not a promised outcome of our project for the NRC. I have filed this issue for later IR&D.

@kiniry kiniry added ENHANCEMENT New feature or request specifications Issues that relate to system specifications, whether of models, code, protocols, or otherwise. FEATURE hardware verification To Do assurance Issues that relate to the assurance of the system, whether via models, code, informal, or formal. Q/A Quality assurance issue; validation, testing, and formal assurance. suggestion cryptol Issues related to our Cryptol specifications, or use thereof. labels Mar 30, 2022
@kiniry kiniry added Someday Issues that are not required by our current contract, but we'd like to attend to someday. and removed To Do labels Apr 18, 2022
@kiniry kiniry removed this from the Task 2: Validation and Verification milestone Oct 28, 2022
@kiniry kiniry added this to the Assurance milestone May 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
assurance Issues that relate to the assurance of the system, whether via models, code, informal, or formal. cryptol Issues related to our Cryptol specifications, or use thereof. ENHANCEMENT New feature or request FEATURE hardware Q/A Quality assurance issue; validation, testing, and formal assurance. Someday Issues that are not required by our current contract, but we'd like to attend to someday. specifications Issues that relate to system specifications, whether of models, code, protocols, or otherwise. suggestion verification
Projects
None yet
Development

No branches or pull requests

1 participant