lowRISC / lowRISC/ibex

error gen wrong path and failed to create spike-cosim_trace_core.log file by xrun

Open
#2,210 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

make clean & make --keep-going IBEX_CONFIG=opentitan SIMULATOR=xlm ISS=spike ITERATIONS=1 SEED=1 TEST=riscv_arithmetic_basic_test WAVES=0 COV=0

There is some error when run a subprocess with command xrun -64bit -R -xmlibdirpath /home/usr21/ibex/dv/uvm/core_ibex/out/build/tb -licqueue -svseed 1 -svrnc rand_struct -nokey -l /home/usr21/ibex/dv/uvm/core_ibex/out/run/tests/riscv_arithmetic_basic_test.1/rtl_sim.log +UVM_TESTNAME=core_ibex_base_test +UVM_VERBOSITY=UVM_LOW +bin=/home/usr21/ibex/dv/uvm/core_ibex/out/run/tests/riscv_arithmetic_basic_test.1/test.bin +ibex_tracer_file_base=/home/usr21/ibex/dv/uvm/core_ibex/out/run/tests/riscv_arithmetic_basic_test.1/trace_core +cosim_log_file=/home/usr21/ibex/dv/uvm/core_ibex/out/run/tests/riscv_arithmetic_basic_test.1/spike_cosim_trace_core_00000000.log +signature_addr=8ffffffc +test_timeout_s=1800

Collecting simulation results and checking logs of testcase at /home/usr21/ibex/dv/uvm/core_ibex/out/run/tests/riscv_arithmetic_basic_test.1/trr.yaml
Collecting up results of tests into report regr.log
0.00% PASS 0 PASSED, 1 FAILED

  • First, I did run this make clean... command in the first line and i received errors from line "There is some error when .... ".

  • After i run just command "xrun -64bit...." that i received a new error in the image below.
    image

I already boiled the error in the image. The correct path is home/usr21/ibex/dv/uvm/core_ibex/sigusrdump.out.

Please check this error as soon as possible and notice me in this bug issue.
Thank you!

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

Reproduce the failure with the posted make command and the xrun invocation, then inspect the reported rtl_sim.log, trr.yaml, and output paths under dv/uvm/core_ibex/out/run/tests/riscv_arithmetic_basic_test.1. Done means the xrun run uses the intended path and creates spike_cosim_trace_core_00000000.log without the reported path error.

Written by the indexing model from the issue text.

Assessment

Domain
testing, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.