-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reset-vector issue #19
Comments
Hi, So far,nearly all simulation of VexiiRIscv were done using Verilator, which doesn't have x-prop simulation. Can you sent me your wave ? As a VCD or a FST ? |
Hi Sir, And I found another problem? When I try to use "--reset-vector 0x8F00000000000000 --physical-width 64" to generate RTL, I got the following error message. Actuaully, if reset-vectore's bit[63] is 1, the error will occur. Most of my job is verification, so I like to try some corner cases, sorry.... |
Hi,
That should be because
to var resetVector : BigInt = 0x80000000l .
to opt[BigInt]("reset-vector") .That should fix it. |
Hi, So the reason why 0x0 can't be used is that by default the PMA specification used by VexiiRiscv is :
Which mean, address zero is unmapped, and will always fault. We need to add a way to parametrized the PMA specification via arguments.
I would say, avoid 64 bits physical memory address space, as anyway, no mmu allows such width, aswell as it create overhead in the CPU.
Yes right :) |
Hi Sir, got it, thanks for your help :) |
Hi,
when I use these parameters "--xlen 64 --with-mul --with-div --with-rva --with-rvZb --with-boot-mem-init --reset-vector 0x0 --physical-width 32" to generate the VexiiRisc.v, the FetchCachelessPlugin_logic-bus_cmd_valid can't assert to fetch the code, is there something wrong?
thanks a lot
The text was updated successfully, but these errors were encountered: