lowRISC / lowRISC/opentitan

[documentation] generating scripts used to run Jasper Gold

Open
#23,268 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

### Description

I'm attempting to get Siemens property-checker running.
My first step would be to see what commands are being executed to run Jasper Gold

util/dvsim/dvsim.py /opentitan_org/hw/top_earlgrey/formal/top_earlgrey_fpv_prim_cfgs.hjson --verbose --select-cfgs prim_arbiter_fixed_fpv

runs, and I do get verbosity, but I just get this, not something showing me what arguments were passed to Jasper.
How do I get the information needed so I can get Questa property checker to run?

VERBOSE: [FlowCfg] Deleting temp cfg file:
/opentitan_org/scratch/.master__prim_sum_tree_cfg.hjson
INFO: [StatusPrinter]   [ legend ]: [Q: queued, D: dispatched, P: passed, F: failed, K: killed, T: total]
VERBOSE: [Scheduler] [00:00:00]: [build]: [dispatch]:
prim_arbiter_fixed_fpv:default
INFO: [StatusPrinter] 00:00:00  [ build ]: [Q: 0, D: 1, P: 0, F: 0, K: 0, T: 1] 0% prim_arbiter_fixed_fpv:defau..
INFO: [StatusPrinter] 00:00:01  [ build ]: [Q: 0, D: 1, P: 0, F: 0, K: 0, T: 1] 0% prim_arbiter_fixed_fpv:defau..
WARNING: [Deploy] prim_arbiter_fixed_fpv:default: jaspergold is unsupported for job runtime extraction. Using dvsim-maintained job_runtime instead.
VERBOSE: [Launcher] Job returned non-zero exit code
ERROR: [Scheduler] [00:00:06]: [build]: [status] [prim_arbiter_fixed_fpv:default: F]
INFO: [StatusPrinter] 00:00:06  [ build ]: [Q: 0, D: 0, P: 0, F: 1, K: 0, T: 1] 100%
INFO: [FlowCfg] [results]: [prim_arbiter_fixed_fpv]:
## PRIM_ARBITER_FIXED_FPV Formal FPV Results

### Thursday May 23 2024 00:41:26 UTC
### GitHub Revision: [`32a11c2ff3`](https://github.com/lowrisc/opentitan/tree/32a11c2ff3ba8b64cfb2896868ae111502f58235)
### Branch: master
### Tool: JASPERGOLD

## Formal FPV Results
No summary information found

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with util/dvsim/dvsim.py and reproduce the shown command using --verbose. Determine how the flow exposes the Jasper Gold commands and arguments, then document the invocation and diagnostics needed to adapt the run for Questa property checker, with a clear example of the expected output.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation, tooling
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.