Skip to content

[dv,sram] Update SRAM vPlan with Metric Types - #697

Open
tchilikov-semify wants to merge 1 commit into
lowRISC:mainfrom
tchilikov-semify:axi_vplan
Open

[dv,sram] Update SRAM vPlan with Metric Types#697
tchilikov-semify wants to merge 1 commit into
lowRISC:mainfrom
tchilikov-semify:axi_vplan

Conversation

@tchilikov-semify

Copy link
Copy Markdown
Collaborator

Closes issue #696

Comment thread hw/top_chip/dv/axi_sram/data/axi_sram_vplan.hjson Outdated
'''
Description: Confirm DUT parameterisation matches spec: AxiDataWidth = 64 (8-byte word), CapSize = 128-bit (16-byte capability), 1 CHERI tag bit per 128-bit aligned region, SramMemSize = 128 KiB
Node_Type: metric
Metric_Type: assert

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you plan to write an assertion in an "initial begin"? Maybe a formal test is more appropriated for these kind of things?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was planning to write this as an assertion inside an initial block, since its just a static check. We could also use formal for this, but since its a simple assertion, I don't know if its worth the effort to set up this test in a separate tool. What do you think?

Comment thread hw/top_chip/dv/axi_sram/data/axi_sram_vplan.hjson
Comment thread hw/top_chip/dv/axi_sram/data/axi_sram_vplan.hjson Outdated
Comment thread hw/top_chip/dv/axi_sram/data/axi_sram_vplan.hjson Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants