Hi all:
The orbuild framework now automatically lints the "ORPSoC V2" repository
at 3 different levels, with both Verilator and Icarus Verilog:
- or1200 (CPU core only, from or1200_top.v downwards)
- orpsoc (from orpsoc_top.v downwards)
- testbench (from orpsoc_testbench.v downwards, Icarus Verilog only)
I have also written a script that generates CPU core configuration files
derived from or1200_defines.v. The tool lets you choose which
configuration settings to set or unset in the generated file. At the
moment, orbuild is generating 3 different configurations:
a) Minimal CPU core features (no cache, no floating point and so on)
b) Maximal CPU core features
c) same as b) with OR1200_ASIC and without OR1200_WB_B3, but this
configuration does not work (!).
orbuild is currently linting a combination of levels and configurations:
- or1200 with minimal CPU core features
- orpsoc with maximal CPU core features
- testbench with configuration c) (disabled at the moment, as it fails)
Each lint results are placed in a separate report file for easy browsing.
The next step is to automatically run the software test suite against
several platforms and configurations like the following:
- or1200/Verilator with both minimal and maximal configurations
- or1200/Icarus Verilog
- or1ksim
- I heard there was another implementation of the OpenRISC CPU, is
that one ready for testing?
In order to achieve this goal, I need to heavily restructure the test
suites, and it would not be practical to do that on a patch basis.
Therefore, I am considering forking the test suites in ORPSoC V2 and
or1ksim and combining them into a separate project with a different
source repository. Any input on this is welcome.
Regards,
rdiez
_______________________________________________
OpenRISC mailing list
[email protected]
http://lists.openrisc.net/listinfo/openrisc
