Mike Thompson

Hi @jeremybennett, can you comment?

Hi @mmatzev, thanks for the question. I cannot answer the first part of it (do you plan to pull fpnew into an OpenHW repo), as that is currently still under...

> I would recommend to clone fpnew also in this repository. The manifest file (cv32e40p_manifest.flist) makes it clear that fpnew needs to be cloned separately. > verilator support is very...

> I would recommend to clone fpnew also in this repository. The manifest file (cv32e40p_manifest.flist) makes it clear that fpnew needs to be cloned separately. > verilator support is very...

Hi @klion717, just so you are aware, the current iteration of the CV32E40P is not verified using the FPU. That is, all our verification is done with the top-level parameter...

Hi @ludmila-bta, do you mean something like this: ``` always_comb begin if( EN_rule[j] & ((~data_we_i & R_rule[j]) | (data_we_i & W_rule[j])) ) begin for(j=0;j

Thanks @davideschiavone. We are aware of the parameters used in the single-core testbench. The purpose of this issue is to have these recorded and documented in the User Manual to...

Hmmm. This discussion is not converging on a solution, and its important that we find one quickly. I would like to suggest a conference call instead. I am not available...

During a conference call on 2020-02-27 with @davideschiavone, it was decided to start by creating a manually generated "flist" style manifest. This has been done: see pull-request https://github.com/openhwgroup/cv32e40p/pull/245. Having this...

Hi @Silabs-ArjanB, I have no preference one way or another. However, if anyone wants to use a particular solution (IP_XACT, Bender, YAML, etc.), they must also contribute: - configuration files...