4 ms·
This open source chip is an FPGA with all the cost and speed limitations that carries. What would it take to create a truly open-source chip? I assume a chip
by mulmen 6y ago
This open source chip is an FPGA with all the cost and speed limitations that carries. What would it take to create a truly open-source chip? I assume a chip fab can be contracted to build them given a workable design. Is this conceivable for a general purpose CPU? Will these FPGA approaches get us closer to such a goal?
- mschuster91 6y ago> What would it take to create a truly open-source chip? From the article: 1M US-$ at least for the masks plus a boatload of other upfront investment. If you're for bleeding-edge tech like new fab processes, orders of magnitude more.
- mulmen 6y agoThanks I skimmed and missed that.
- rektide 6y agoAs the other comments say, it's going to cost a million bucks probably to get something made. I wouldn't be shocked to hear numbers way lower for some smart folks. I wonder, for example, what it cost GreenArrays to get their chips made, how big their run was. But $1M i probably a pretty safe ballpark starting place. And we have pretty great open source cpu & ram design tools. MAGIC is free. There's a lot of great tools fora lot of this. What is not so great is all the un-core. And GPU, if you want that. The SiFive boards were coming with TileLink[1] as the main way to talk to the core, for a while, I believe, which is a pretty low level cache-coherent fabric used no where else. There's decent off the shelf to design a lot of the digital systems here. But I don't know what resources if any are available to help you build a chip-to-chip interface, to expose the TileLink. And there's basically the world's tiniest market for things to plug in on the other end anyways. When you buy an SoC, almost all embedded folk expect a bunch of semi-standard capabilities. I2C, I2S, DisplayPort, USB, Ethernet, &c are all common things you might want. While we can make a decent cpu now a days, afaik, we are still in very very very early days, very pre-implementation, for almost all of these. Thusfar almost everyone relies on buying closed IP to provide connectivity for the SoC they are making. It's quite likely to be the case as well for the new SiFive Unmatched board; I expect they bought someone's PCIe IP & integrated it. We are starting to see more neat work with FPGA implementations of various protocols like USB3 & PCIe but these all rely on the FPGA having really good transceivers that tackle the PHYsical layers, do the dirty work. Building actual transistors to be receivers & transmitters into & out of the chip, that's where, atm, we are all but babes, it feels like. [1] https://www.youtube.com/watch?v=EVITxp-SEp4 https://www.youtube.com/watch?v=EVITxp-SEp4
- nereye 6y agoOn the other hand, https://www.efabless.com/ https://www.efabless.com/ offers: $70K 20 WEEKS 100 SAMPLES See also: https://theamphour.com/503-fabless-chip-design-with-mohammed-kassem/ https://theamphour.com/503-fabless-chip-design-with-mohammed...
- egsmi 6y agoDon’t get me wrong, I think what those guys are doing is cool, but it’s 130nm, a fairly small die, and it’s not a fully custom ASIC. That’s how they’re getting the cost down to under $100K. “Degree of Customization: Only what is available through configuration of the design template”
- bunnie 6y agoThanks for pointing that out. Yes, the $1mm number I cited in my post is the estimated raw cost of a full mask set for a relatively modern process in the 2Xnm or smaller range. Definitely older processes have much cheaper mask sets -- in part because there are just fewer metal layers, and fewer & cheaper masks required to image the transistors when the wavelength of light used (193nm) is close to the line width of the devices themselves.
- rektide 6y ago> What's more, SoCs incorporate components from a small number of vendors supplying designs for USB, DDR, and PCI controllers: "this means the same disused logic motifs are baked into hundreds of millions of devices, even across competing brands and dissimilar product lines." https://mamot.fr/@pluralistic/105183378364921755 https://mamot.fr/@pluralistic/105183378364921755 I really think this is the killer point of it all. The cores are the easy part. The digital part. Are we making headway anywhere else? Eh, yes, a tiny bit? Barely?
- amock 6y agoI don't know what the current status is, but I think https://hackaday.com/2020/06/30/your-own-open-source-asic-skywater-pdf-plans-first-130-nm-wafer-in-2020/ https://hackaday.com/2020/06/30/your-own-open-source-asic-sk... is a good start on getting an open source fabricated.
- octoberfranklin 6y agoCurrent status is "it's dead, Jim". The promised "November run" did not materialize, and there's nothing solid on rescheduling it. Kind of a let-down.
- snvzz 6y ago>Will these FPGA approaches get us closer to such a goal? The same HDL that can be configured into an FPGA can be used to make chips. But we won't get there without the FPGA step. Chips aren't designed directly anymore. The sort of complexity we need these days means it's impossible to get right on the first try, and mistakes are very costly with ASICs.
- mschuster91 6y ago> The same HDL that can be configured into an FPGA can be used to make chips. Not exactly, you'll likely have to replace FPGA HW blocks for "hard IP" such as I/O (especially high speed interfaces such as HDMI/DP, MII, but also RAM controllers), power and clock management...
- iron2disulfide 6y agoOf course "the same HDL" is a reductive statement, since components like high-speed IO, or even clock gates are not easily portable between FPGA vendors or foundries. But the user-land Verilog/VHDL code that describes how your custom thing "works" is generally portable.
- bunnie 6y agoI'm also worried about this, which is part of the reason why the Precursor design avoids using hard IP blocks like RAM and USB controllers. It does limit the performance of the system (we have a simple async RAM interface and full-speed USB only), but the explicit priority is transparency over performance. The main attack surfaces to worry about when translating this design to an IC are the RAM, boundary scan and eFuse macros, and perhaps slightly less so the PLL and ADC blocks. While these are not trivial blocks to be worried about, there may be things we can do at a design level to complicate attempts to bake back doors into these blocks, and we're investigating methods to verify their correct in-silicon construction non-destructively.
- octoberfranklin 6y agoWhat about the metrology cutouts you have to leave in every 2mm by 2mm region on 28nm and lower processes? I hear the interval is even smaller on 14nm/7nm. I always thought those were only half for process control and half to force you to leave a blank spot on your mask where they could pattern in nasty additional circuitry on a few wafers. Edit: TSMC calls this the "Dummy TCD macro". If you have the 28nm design rule book T-N28-CL-DR-002 version 1.3 it's Section 6.3.3 "Dummy TCD Design Insertion Guideline" (if you don't have the design rule book then no, I can't send it to you, please don't ask). The TCD macro is a black box -- nobody outside TSMC gets to see what's in it. You have to leave a 9um*3.5um empty region on all layers in every 2mm by 2mm region of your maskset. Now that Multi Layer Maskset (MLM) is widespread every fab has the ability to "blade off" regions of a mask and expose a pattern from a different mask in that region (of course wafers processed this way are much much more expensive). The TCD macro rules force you to leave an empty hole in your design at regular intervals where this can be done without breaking your chip.
- EvanAnderson 6y agoFor the Precursor platform, though, I believe being FPGA-based is a specifically-desired feature. Bunnie did a hardware security talk at Chaos Computer Congress 36 (https://www.bunniestudios.com/blog/?p=5706 https://www.bunniestudios.com/blog/?p=5706) that argued for using FPGAs as a means to gain visibility into the "hardware" to find implementation backdoors.
- nickik 6y agoGoogle, FOSSi and eFabless are working on a 100% open source chip design workflow that would allow you to use only open source tools to create a chip, and thanks to other efforts open source chips and ISA exist already: See: https://www.youtube.com/watch?v=EczW2IWdnOM https://www.youtube.com/watch?v=EczW2IWdnOM