How to use Ibex with mainline fusesoc
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 2.1k
- Forks
- 810
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 9
Description
Hi there,
You seem to still be using a custom Fusesoc version that expects a different GAPI structure. The `ot` branch you recommend using is quite a way behind mainline Fusesoc so what are your plans for merging changes and/or pulling the latest changes into your fork?
Can you expand on the main differences? Is it just related to your generators or are there additional features?
What would be the workaround for anyone needing to use the latest features of Fusesoc? Can the Ibex source be generated and exported using something like the OT vendoring scripts? Just thinking how I can work around this.
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
The issue names FuseSoC, Ibex source generation, and the OT vendoring scripts but no specific files or tests. Start by locating the current FuseSoC integration and those vendoring scripts, then compare the referenced OT branch with mainline FuseSoC. Done would be a decided, maintainable explanation of the differences, supported workflow, and any required workaround.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, tooling
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100