In complement to #7 , I noticed that reading existing CSRs also causes the CPU to hang.
This happens only if the destination register is distinct from zero.
For example, in the snippet below, zero is never written to address zero.
This does not happen in all cases, for example this snippet is fine, probably because the CSR register write signal is (legitimately) overwritten with 0 just after the first register write occurred.
It is possible that the bug only has symptoms when #6 is implemented (I haven't double checked that, since #6 or any such alternative is necessary for RISC-V compliance).
Hi there!
In complement to #7 , I noticed that reading existing CSRs also causes the CPU to hang. This happens only if the destination register is distinct from
zero
.For example, in the snippet below, zero is never written to address zero.
This does not happen in all cases, for example this snippet is fine, probably because the CSR register write signal is (legitimately) overwritten with
0
just after the first register write occurred.It is possible that the bug only has symptoms when #6 is implemented (I haven't double checked that, since #6 or any such alternative is necessary for RISC-V compliance).
Thanks!