Open ChiaLiu0618 opened 1 month ago
IIRC the perf.log file is only used for the OpenSPARC T1 core. As it is now, we don't have a mechanism to check which core is in use and avoid this, but it could be done in the near future with a different PR I'm merging.
It does seem like the broader issue/bug with verilator failing on multicore is still the case. It would be good to dig in this. Not sure who will have time to do so, though. Any volunteers reading this would be very welcome :)
Hi, we’ve been trying to run assembly code on the OpenPiton multicore, but it seems that the code isn't properly linked to the riscv_test.h
and test_macros.h
header files. Do you have any suggestions on what could be the issue, or where I should place these files to resolve the problem?
Thank you~
I think I see two main issues here:
Hi, I’d like to ask if the rv64ui-p-addi.S
file located at ~/openpiton/piton/design/chip/tile/ariane/tmp/riscv-tests/build/isa
is the compiled binary version of the addi.S
file located at ~/openpiton/piton/design/chip/tile/ariane/tmp/riscv-tests/isa/rv64ui
?
Thank you~
Do you mean the .riscv file (I think that's the extension)? To the best of my knowledge, it should be, yes. You can use -precompiled to run that test. I think the readme should have an example
Hi, I was trying to reduce the sims.log
file by minimizing the number of instructions, but I encountered a bad trap. Does the sims.log
still capture the transmission behavior, or is the bad trap message fatal? I ran the following command:
sims -sys=manycore -vlt_run -x_tiles=2 -y_tiles=2 addi_example.s -ariane -finish_mask=1111 -rtl_timeout 100000
. The attached are my terminal, code, and sims.log.
Thank you~
sims.log
Bad trap corresponds with the core's PC going to the "fail" label in the program's binary. You should be able to use your riscv64 objdump (or check diag.dump) to see what address that label exists at. From that you should be able to trace why the program reached that PC, based on your modifications.
Hi, I tried running it with just one tile. While there don't appear to be any errors based on the terminal messages, my perf.log file is still empty. Is this expected behavior, or could there be an issue? Thank you ~