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
I installed the co-simulation system, followed this tutorial to install cosim and tested it on ibex. One of the test cases shows unexpected behavior:
FAILURE: Co-simulation mismatch at time 1302
Register write data mismatch to x5 DUT: 2 expected: 1
[1302] %Error: ibex_simple_system_cosim_checker.sv:68: Assertion failed in TOP.ibex_simple_system.u_ibex_simple_system_cosim_checker_bind: Co-simulation mismatch seen
Received stop request, shutting down simulation
I would like to ask, how reliable is the reference model of cosim? I am unsure whether this issue is necessarily a problem with ibex because the reference model version is ibex-cosim-v0.5.
The text was updated successfully, but these errors were encountered:
Thanks the question. This looks a lot like it points at a bug (probably in our cosimulation environment). Can you give us step by step instructions about how to reproduce it at our end? (What command, what seed etc.)
Add the code to examples/sw/simple_system/hello_test.c and make, then run ibex.
In fact, this test code will jump to execute at pc=0x000FF208. However, the link.ld file defines the RAM range to start from 0x00100000, and this pc is outside the RAM range. Therefore, the reference model, Spike, throws an Instruction Access Fault trap, while Ibex retrieves the value and decodes it, leading to an Illegal Instruction trap.
I installed the co-simulation system, followed this tutorial to install cosim and tested it on ibex. One of the test cases shows unexpected behavior:
I would like to ask, how reliable is the reference model of cosim? I am unsure whether this issue is necessarily a problem with ibex because the reference model version is ibex-cosim-v0.5.
The text was updated successfully, but these errors were encountered: