You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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!
The text was updated successfully, but these errors were encountered:
ThanhDo288
changed the title
Report a bug in Ibex|
Compile_tb.py generate options not recogised by xrun ,
Aug 27, 2024
ThanhDo288
changed the title
Compile_tb.py generate options not recogised by xrun ,
error gen wrong path and failed to create spike-cosim_trace_core.log file by xrun
Aug 27, 2024
I'm not sure exactly what's going wrong, but the symptom is a segfault in the simulation binary (which presumably happens after some memory corruption that's trashing the string holding the path that gets reported afterwards).
To debug it further, you'll need to add some debug prints to figure out what code is running. I suspect it will be some C++ function that we're running over DPI. Then add some prints to that code (to stderr so it doesn't get buffered) to figure out exactly what is exploding.
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.
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!
The text was updated successfully, but these errors were encountered: