lowRISC / lowRISC/ibex

Ask a question related to Ibex

Open
#1,961 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Type:Question
Dominant language
SystemVerilog
Stars
2.1k
Forks
810
Avg merge
5d 23h
Merged PRs (30d)
9

Description

## My Environment

I wish to create a logic simulation environment while using ibex as a core. I have a question related on the structure of the core though.

1. Besides manual modification of the HDL, is there a way of including the Register File (FF) in the Instruction Decode stage ? In the current version I see that the RF is instantiated in the top module rather than in the ID whereas I would like to embed it in the core.
2. Is there a pre-written TB for the core in SystemVerilog ? I can't seem to find something relevant. Do i have to create a TB from scratch?
3. Is there a .tcl synthesis script that can be used instead of the yosys synthesis one?

**EDA tool and version:**

QuestaSIM 10.5c_4
Design Compiler Version S-2021.06-SP4 (for synthesis/DfT insertion)

**Operating system:**

OpenSUSE Leap 42.3 (EOL)

**Version of the Ibex source code:**

Latest

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 by reading the Ibex top module and instruction-decode structure referenced in the question, then inspect the existing core testbench and Yosys synthesis setup. Determine whether the repository documents a SystemVerilog testbench, register-file placement, or an alternative Tcl synthesis flow; done would require a clearly scoped documentation change or separate implementation issue.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, embedded-iot, testing-qa
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.