On Thu, Mar 28, 2013 at 09:30:54AM -0700, Ouabache Designworks wrote: > Stefan, > > I also tried to run code coverage on your code using covered and it doesn't > like it.
First let's direct credit where credit is due, Julius Baxter is the mor1kx project founder. My involvment in the project has evolved into taking the cappuccino pipeline implementation under my wings and to implement caches and MMUs for it. Julius has the final say in all design decisions affecting the core. > Every time you do a this: > > generate > /* verilator lint_off WIDTH */ > if (OPTION_CPU=="CAPPUCCINO") begin : cappuccino > /* verilator lint_on WIDTH */ > mor1kx_cpu_cappuccino > > > covered flags a syntax error on the option test statement > > > ERROR! syntax error, unexpected STRING, > > > > > This will work but its a hack > > parameter CAPPUCCINO ="CAPPUCCINO" > > generate > /* verilator lint_off WIDTH */ > if (OPTION_CPU==CAPPUCCINO) begin : cappuccino > /* verilator lint_on WIDTH */ > mor1kx_cpu_cappuccino > > That sounds like a hack, yes, but if no better solution comes up maybe we could have a 'feature_parameter_defines.v' file where all the feature strings are defined as localparams and have that file included in all the designs files. I have to admit that I'm not familiar with covered, but glancing at their website, it sounds like an interesting tool. You wouldn't happen to be able to share your setup where you run it against mor1kx? Stefan _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
