Hi Christian, Excellent idea. I would like to volunteer to mentor the following project, picked up from the wish list, and reformatted as below:
*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. *Knowledge Prerequisite: *Python, Verilog, RTL simulation, SystemC. Knowledge of hardware/software co-design and verification. *Mentor: *Jose T. de Sousa ([email protected]) On Fri, Feb 14, 2014 at 7:13 AM, Olof Kindgren <[email protected]>wrote: > On Fri, Feb 14, 2014 at 6:22 AM, Christian Svensson <[email protected]> > wrote: > > Hi, > > > > I threw in a last minute submission to have OpenRISC in GSOC 2014. > > I have extracted and reformatted the future work section in the wiki > > to this: http://opencores.org/or1k/OR1K:FutureWork > > > > The ideas list is a very important part of GSOC, so I plead: > > I would love if people could add more ideas / reformat what is > > currently in the Wishlist section. Also, if people want to mentor that > > would be awesome. > > > > The deadline is formally in 15 hours or so, so if you don't have > > anything to do today please take 10-20 minutes and reflect on 'What > > kind of feature have I been putting of doing but would be awesome to > > have?' and write it down! > > Even after the deadline (I don't think they read all of them at once, > > and if they go alphabetically we're in a good position ;-)) this > > document is a good to keep somewhat up to date. > > > > Finally, GSOC would be a nice way to introduce more people to OS and > > low level stuff outside of the CS class. > > > > Christian > > - Taking one step closer to OpenRISC world domination. > > _______________________________________________ > > OpenRISC mailing list > > [email protected] > > http://lists.openrisc.net/listinfo/openrisc > > Hi Christian, > > This is awesome. I've been thinking about doing this for several years > now, but never gotten around to do it. Now I just have to quickly dig > up all the old ideas :) > > I will try to make myself available as mentor, but I'm not sure I will > be able to > > //Olof > _______________________________________________ > OpenRISC mailing list > [email protected] > http://lists.openrisc.net/listinfo/openrisc > -- Jose T. de Sousa, PhD Office: +351 213 100 213 R. Alves Redol 9 1000-029 Lisboa Portugal
_______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
