4 ms·
Our most recent update was releasing an untethered version of the Rocket core http://www.lowrisc.org/blog/2015/12/untethered-lowrisc-release/ http://www.lowrisc
by asb 11y ago
Our most recent update was releasing an untethered version of the Rocket core http://www.lowrisc.org/blog/2015/12/untethered-lowrisc-release/ http://www.lowrisc.org/blog/2015/12/untethered-lowrisc-relea.... Our next development goals are integrating the minion cores and integrating with third-party IP in order to produce the initial test chip, which we're intending to tape out later this year.
We haven't yet produced a silicon prototype, but will be taping one out this year. The Berkelely Rocket implementation has been silicon-proven multiple times as has the ETH Zurich PULP core which we also hope to use. The aim of this test chip is to integrate an LPDDR3 memory controller+PHY, plus USB host controller+PHY.
I don't have the link handy, but the Rocket implementation has clocked at 1.5GHz on a 45nm process.
For the final question, perhaps it's useful to define some of these terms:
* OpenRISC: an older 32-bit open ISA.
* OpenSPARC: The open-sourced design from Oracle. GPL-licensed. I don't know of anyone planning to produce a commercially available ASIC using it.
* Z-scale and BOOM are both RISC-V implementations from Berkeley. Z-Scale is a microcontroller-class RISC-V implementation and BOOM is an out-of-order implementation. Both make use of parts of the Rocket implementation (essentially using the codebase as a library). I believe only the base Rocket design has been produced in silicon so far. With lowRISC, we hope to discuss at the upcoming RISC-V workshop (this Tuesday and Wednesday) the status of BOOM, and whether it will make sense to use it as our application cores.
I hope we'll see commercially available lowRISC chips towards the end of 2017, but we'll be able to make a better judgement about how realistic that is once we reach our first test chip.
- alain94040 11y agoRocket implementation has clocked at 1.5GHz on a 45nm process That's not bad. How many instructions can this issue per cycle?
- asb 11y agoThe current Rocket implementation is single issue in-order, but it was designed as a dual issue in-order core.
- zhemao 11y agoThere has been one tape-out of Z-scale. An early iteration of it was used as a power management controller in one of our DVFS test chips. But we've made many changes since then and haven't taped it out since.
- _chris_ 11y ago"With lowRISC, we hope to discuss at the upcoming RISC-V workshop (this Tuesday and Wednesday) the status of BOOM, and whether it will make sense to use it as our application cores." Hi Alex, I look forward to chatting with you guys about BOOM. =)
- asb 11y agoDefinitely, looking forward to catching up with you and everyone else this week. With areas we're currently estimating, it seems we would have the area budget for 4x 2-wide BOOM cores (of course it's all quite rough at the minute). I'm keen to hear more on Tim Newsome's debug work and whether BOOM will also reap the rewards of it. See you Tuesday!