Ask a question related to Ibex
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 2.1k
- Forks
- 810
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 9
Description
Hello, I have a question about RVFI (RISC-V Formal Interface).
If I just want to monitor RVFI signals or let RVFI signals output to other modules and without creating a text file, do I only need to `define RVFI in ibex_top.sv?
Is it unnecessary to use ibex_top_tracing.sv and ibex_tracer.sv?
## My Environment
**EDA tool and version:**
Vivado 2020.2
**Operating system:**
Ubuntu Linux 18.04
**Version of the Ibex source code:**
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ibex_top.sv, ibex_top_tracing.sv, and ibex_tracer.sv, focusing on how RVFI signals are exposed and how tracing is used. Check the Ibex documentation and source at the relevant revision; done means a clear, revision-specific answer to the question for Vivado 2020.2.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100