Closed CoralieAllioux closed 2 weeks ago
:heavy_check_mark: successful run, report available here.
Hello @CoralieAllioux The new parameter name tells the PMP instruction and data will be present when PmpPresent = 1. For instance:
Hello @JeanRochCoulon, About the parameter, it only instantiates the PMP when the MMU is not present. Therefore the parameter PmpPresent is ignore in that case. I could then rename it to PmpStandalonePresent or something similar to be more explicit. Would it be better for you?
This new parameter allows to disable the PMP data when MMU not present and PmpPresent=0. To me this configuration does not need to be supported: this configuration is not compliant to RISC-V (because PMP instruction is present and _data not present) and I do not know a CVA6 user pleased to use it so far (maybe youself ?).
I am not sure to understand your last comment. PmpStandalonePresent was a suggestion to rename PmpPresent if not explicit enough. This is not a new parameter
Here the possible configuration we're proposing:
RISC-V specification tells that PMP is optional. But in CVA6, PMP regions are always 16. To be compliant PMP data and instruction shall be supported. It is not the case Today when MMU is not present. Your modification will make CVA6 compliant to RISCV when MMU is not present.
Oh, so you're telling MmuPresent=0 is sufficient? If so, PmpPresent is not necessary... and the PR is not needed anymore
Yes, that's it !
Sorry for the missunderstanding. Then I cancel the PR.
First step for the PMP standalone: adding a dedicated parameter in config package and all configs.
It contributes to https://github.com/openhwgroup/cva6/issues/1447