lowRISC / lowRISC/ibex

Facing issue with ibex DUT

Open
#2,264 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hi team

After the simulation i am facing the below error

make: *** [/Projects/marmik_project/hemashri.bhagavati/april/ibex/riscof_work/Makefile.DUT-ibex:9: TARGET1] Error 1
Flag could not be matched: isa

STEPS FOLLOWED:

cloned by using this: git clone https://github.com/Abdulwadoodd/ibex
Inside ibex again cloned complince tests: git clone https://github.com/riscv-non-isa/riscv-arch-test.git

For env setup
riscof setup --dutname=ibex
riscof --verbose info arch-test --clone
riscof validateyaml --config=config.ini

EXPORT COMMANDS:
export SAIL_RISCV=/tools/sail-riscv-new/c_emulator
export PATH=/tools/sail-riscv-new/c_emulator:$PATH

RUN COMMAND:
riscof run --config=config.ini --suite=riscv-arch-test/riscv-test-suite/rv32i_m/C --env=riscv-arch-test/riscv-test-suite/env

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 reviewing Makefile.DUT-ibex:9 and the supplied config.ini, then reproduce the command with riscof --verbose using the listed environment variables. Trace the source of “Flag could not be matched: isa” and confirm the RISCOF Ibex setup accepts the configured ISA before rerunning the RV32I compliance suite.

Written by the indexing model from the issue text.

Assessment

Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.