Hello OpenHW Members - as we have grown the OpenHW Group ecosystem over the past several months, we've had many different ideas put forward for various projects that could be started within the ecosystem. The enthusiasm and overall potential is awesome, but this may also lead to spreading our collective resource / bandwidth too thinly making it difficult to achieve critical mass on any specific project / initiative. To that end, I'd like to suggest we bring a "sprint mentality" to achieving RTL freeze for the CORE-V CV32E40(P). That is, we ask for all available FTE resources to be focused on RTL, Verification, SW and HW tasks related to achieving RTL freeze for the CV32E40(P). We are furthest along with this core and it would be beneficial to all of us to get a project "finished" and under our belt. I realize some members may be interested in other CORE-V cores such as the CV64A6 and / or CV32A6, but much of the Verification, SW and HW efforts for RTL freeze for the CV32E40(P) will be re-used across other cores as will the overall methodology we use to execute our projects. Also, with a sprint mentality to reach RTL freeze for the CV32E40(P) and finish the project, we'll be able to bring greater focus to the other cores and subsequent projects. To be clear, this is not meant to imply the CV32E40(P) is more important than other cores. Rather the intent here is to keep us focused on completing an initial project thereby allowing us to get to other projects faster. Over my career, I have rarely encountered companies that have failed as a result of trying to do too little, but have seen many companies fail as a result of trying to do too much. Let's be known as an ecosystem that "executes" and gets things done! Please post any comments you may have in the
TWG Channel on our Mattermost site and we'll convene a TWG meeting shortly to map out our collective plan.
Also, feel free to reach out to me directly if you have any questions.
Cheers,
Rick
Rick O'Connor
+1 613 614-4101
