Marno van der Maas

If I remember correctly, we talked about the case when the instruction fault trap handler is set to non-executable. We can catch this case by checking whether two RVFI packets...

We discussed this in the meeting and Greg mentioned that we could check the signal Ibex produces on a nested double trap (a trap raised within the trap handler). In...

While running the following command: ```console make -j7 --keep-going IBEX_CONFIG=opentitan ITERATIONS=1 WAVES=0 COV=0 ``` I encountered the following error: ```make riscv32-unknown-elf-gcc: error: ibex/dv/uvm/core_ibex/out/run/riscv_csr_test.2825/test.S: No such file or directory riscv32-unknown-elf-gcc: fatal...

One other thing I was thinking was automatically generating a `test.dump` file. I always end up running the following command when I'm debugging a test: ```console riscv32-unknown-elf-objdump -D test.o >...

Closing this because the remaining issue of infinite loops is captured in this issue: https://github.com/lowRISC/ibex/issues/1823

> Second item can be solved by adding a "if we are enabling `pmp_randomize`, do not owerride `pmp_cfg0`" clause to the place where we do PMP related instruction generation in...

I created a PR for the second point: https://github.com/google/riscv-dv/pull/885 > spent 4

I adjusted https://github.com/google/riscv-dv/pull/885 to initialize the PMP config entries as disabled in the case that MML or MMWP are enabled. > spent 2

I spent quite some time debugging https://github.com/google/riscv-dv/pull/885 and solved a number of problems: - Full random test now generates random addresses instead of offsets from main. - Stop CSR write...

@johngt As far as I can tell the simplifications are mostly done by @GregAC in: https://github.com/lowRISC/ibex/commit/72a892d62ce820d9519825e308df45c05cfbe867 The only other thing Rupert mentions is the: > need to work on this...