On Sat, Feb 15, 2014 at 5:35 PM, Ouabache Designworks <[email protected]> wrote: > OpenRISC Verification > ----------------------- > > Brief explanation: one of the main hurdles to adoption of OpenRISC (OR) > based SoC's is the lack of credible verification results. To have such > results an automated system for a running a test suite providing acceptable > code coverage (preferably 100% Verilog statement coverage) is needed. A good > tool to run RTL simulation and measure code coverage results is the > Verilator simulator. The goal of this project is to setup the verification > environment to assess coverage, and make it easy to add new test cases. > Obtaining high coverage is left for a future project. This project will > extend the OR Platform SoC (ORPSoC) program, which is a python script for > generating and running OR-based SoCs on various simulators and FPGAs. > > Expected results: a new mode for OrpSOC, which runs a regression suite using > Verilator and reports coverage results. The regression suite should reuse > the tests currently existing for Or1ksim, the OR architectural simulator and > the GCC regression suite. > > > > > Why make this OpenRISC specific? Create a generic set of tools and libraries > to do this for any module and you will make every bodies job easier. Check > out my socgen project for some examples. > > > John Eaton >
Hi John and Jose, I feel that I should add some info here to avoid confusion as there are some things that will change soon. ORPSoCv3 as it is today is a generic set of tools and libraries without a single line of OpenRISC-specific code. Very much like your SoCgen project (that I also need to take a closer look at). I just released version 3.2 of ORPSoC now, and the idea has been to make this the last release under the name ORPSoC (as it really has nothing to do with OpenRISC anymore). I still think that having an easy way to run multiple OpenRISC test suites against different simulators and targets is a great idea for a project, and it could use socgen or the-project-formerly-known-as-orpsocv3 internally. //Olof _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
