26 ms·
Google offers free fabbing for 130nm open-source chips
- jcun4128 6y agoHow "bad" is that compared to standard/common 14nm, etc...
- kn0where 6y agoPentium 4 was on a similar process size: https://en.wikipedia.org/wiki/Pentium_4 https://en.wikipedia.org/wiki/Pentium_4
- lnsru 6y agoI don’t know, why do you refer 14 nm as common. It’s for the newest consumer toys. Regular electronics in your dish washer is made using 65, 90 or even 130 nm process.
- why_only_15 6y agoSamsung galaxy A20, a ~$150 phone, uses the exynos 7884 which is fabbed on a 14nm process pricing: https://www.androidauthority.com/cheap-android-phones-269520/ https://www.androidauthority.com/cheap-android-phones-269520... soc: https://www.samsung.com/semiconductor/minisite/exynos/products/mobileprocessor/exynos-7884/ https://www.samsung.com/semiconductor/minisite/exynos/produc...
- innocenat 6y agoThat falls into "newest consumer toys". The bulk of the IC chip is no where near 14nm process.
- jcun4128 6y agoyeah maybe 22nm is more common
- TheSpiceIsLife 6y agoThis range of 32bit Cortex chips are listed as 130 - 40nm https://en.wikipedia.org/wiki/STM32 https://en.wikipedia.org/wiki/STM32
- goatsi 6y ago130nm chips first arrived in 2001, so it's about 20 year old technology. This page has a few examples: https://en.wikichip.org/wiki/130_nm https://en.wikichip.org/wiki/130_nm
- DCKing 6y ago130nm was used to make the Athlon XP, Athlon 64, Pentium M, Pentium 4 and PowerPC G5 in the 2001-2003 timeframe [0]. So at the peak of 130nm's performance spectrum, it was able to produce stuff that can still run 2020 software quite okay. The Athlon 64 is probably the best 130nm silicon produced in its heyday and it's in the ballpark of a Raspberry Pi 4 (which has a 28nm SoC) in single core benchmarks. I don't think this program is meant or likely to produce high frequency 100mm2+ chips (and it's worth remembering those chips had a lot of engineering effort put in them outside of manufacturing process) but it should permit chips of somewhat decent performance. It's a very generous thing! [0]: https://en.wikipedia.org/wiki/130_nm_process https://en.wikipedia.org/wiki/130_nm_process
- walrus01 6y agoAs I recall from that generation, also the first models of AMD opterons, commonly built into dual socket motherboards. For the time they were very speed competitive with the Intel option.
- innocenat 6y agoI think at that time, Opterons was THE server processor.
- walrus01 6y agoI recall the dual socket (everything was single core at the time) Xeon being particularly unimpressive. In fact it was somewhat of a step backwards from the better thermals/power efficiency of a dual socket, 1.13 to 1.4 GHz / 512KB cache Tualatin pentium 3.
- jcun4128 6y agoI see I remember using Dimension 4500's that had Pentium 4
- tdonovic 6y agoThat sounds pretty huge. I've never seen on Hackaday or similar people getting small runs of chip fabbed. What are the broader implications of this? Will other fabs start to lower the barrier to production as well?
- novaRom 6y agoBroader implications: * More people will learn complete digital design workflow; very helpful for many students of EE/CE * More bright ideas and experiments in robotics/IoT * More startups
- ohazi 6y agoYou generally don't do small runs of chips, unless cost is no object. The NRE costs of getting the masks made, even on older processes like these are still comfortably in the $X00,000 range, blowing past $1 million pretty quickly if you need a process that isn't ancient. That's without design software licenses, which can be hundreds of thousands more. So the minimum order quantity usually needs to be at least in the tens to hundreds of thousands of chips if you don't want each chip to be a sizeable chunk of that initial cost. It would be really nice to get to the point where small batch chips were viable though. One aspect is cost -- if they could get the NRE cost down to, say, $20k - $50k, and the software licensing cost down to zero, that would open up a lot of options. The other aspect is the "dark art" nature of the process kit and communicating with the fab. If everybody assumes that chip design is expensive, they're going to be reluctant to even talk to the fab to see what options are available. If they see a bunch of people building interesting things with this shuttle program, then all of a sudden the fab is going to see more business interest as people try to figure out if there's a way to make their project work.
- phonon 6y agoYou don't need your own mask; you can share with other customers. https://en.wikipedia.org/wiki/Multi-project_wafer_service https://en.wikipedia.org/wiki/Multi-project_wafer_service https://www.tekmos.com/products/asics/reducing-the-asic-nre https://www.tekmos.com/products/asics/reducing-the-asic-nre
- est31 6y agoThis is amazing. I think the main reason why open source has taken off is because access to a computer is available to many people, and as cost is negligible, it only required free time and enough dedication + skill to be successful. For hardware though, each compile/edit/run cycle costs money, software often has 5-digit per seat licenses, and thus the number of people with enough resources to pursue this as a hobby is quite small. Reduce the entry cost to affordable levels, and you have increased the number of people dramatically. Which is btw also why I believe that "you can buy 32 core threadripper cpus today" isn't a good argument to ignore large compilation overhead in a code base. If possible, enable people to contribute from potatoes. Relatedly, if possible, don't require gigabit internet connections either, so downloading megabytes of precompiled artifacts that change daily isn't great either.
- andy_ppp 6y agoSounds like there should be open source software for such a thing? I bet the software for laying out transistors and so on will suddenly become viable with something like this, good idea Google!
- fhssn1 6y agoI believe you're talking about the EDA toolchain. Even though it has a long history of open-source attempts, as pointed out by Tim in his presentation, they are few and far between, and massively underwhelming compared to the thriving open source software community. However, if this initiative takes off, it'll be a big help in creating an open source EDA toolchain community.
- why_only_15 6y agoHow much has the power efficiency improved between 130nm and 7nm? Is it plausible to get better performance/watt for a custom chip on 130nm vs a software application running on a 7m chip? I get that hardware has other benefits but just wondering for accelerators where the cost/benefit starts to make sense.
- neltnerb 6y agoI would definitely be rather interested in learning how to design some chips with feature sizes large enough for power handling... I'd love to hear about this as well. This sounds like a clever way to commoditize hardware design, like when printing PCBs became affordable.
- 6nf 6y agoYou won't be able to profitably mine Bitcoin on 130nm ASICs (just as an example) 130nm is almost 20 years old at this point. You can do amazing things with this process but saving power is probably not one of them.
- garmaine 6y agoBut as an example, you WOULD be able to profitably mine bitcoin on 130nm ASICs if all the rest of the world had was CPUs/GPUs/FPGAs, which was more what the grandparent post was asking: 130nm hardware implementations can be much, much faster and/or energy efficient than a 7nm general-purpose chip which simulates the algorithm.
- deleted 6y ago[deleted]
- hristov 6y agoDepending what application you have but if you have a relatively narrow and complex application, I would say definitely yes.
- pjc50 6y ago> Is it plausible to get better performance/watt for a custom chip on 130nm vs a software application running on a 7m chip? This very, very much depends on what the algorithm is (integer or FP? how data dependent?), but I would say no for almost all interesting cases. The only exception would be if you're doing a "mixed signal" chip where some of the processing is inherently analogue and you can save power compared to having to do it with a group of separate chips. Another exception might be low leakage construction, because that gets worse as the process gets smaller. This is only valuable if your chip is off almost all of the time and you want to squeeze down exactly how many nanoamps "off" actually consumes.
- blackrock 6y agoI wonder if you can make micro machines at this level? The MEMS thing. I always wondered why you needed gearing mechanisms in a micro machine. Has there ever been a practical application for gears in MEMS?
- deleted 6y ago[deleted]
- stephen_g 6y agoNot with this PDK or process, no. MEMS processes are quite specialised, and I beleive this project only supports digital standard cells currently, with IO and analogue/RF stuff coming out eventually (it's on the roadmap in the slides).
- qaute 6y ago> I wonder if you can make micro machines at this level? The MEMS thing. At this size range, though state-of-the-art MEMS (mechanical vibrating frequency filters for RF receivers in phones, accelerometers) can have sub-100nm dimensions, basic accelerometers, pressure sensors, and inkjet heads are absolutely doable. > Not with this PDK or process, no. MEMS processes are quite specialised. But yeah, this is the problem. Although ICs and MEMS devices are made with similar tools, MEMS usually needs processing steps that don't play nicely with the steps in an IC process (e.g., etching away huge amounts of silicon to leave gaps and topography, or using processing temperatures and materials that mess up ICs). This SkyWater process cannot do MEMS. A more general problem is that different MEMS devices often need different incompatible process steps, so a standardized process is infeasible (though http://memscap.com/products/mumps/polymumps http://memscap.com/products/mumps/polymumps tries). However, there is a tiny chance that, if we get enough detail on the process steps and leeway in the design rules, a custom layout could implement a rudimentary accelerometer or something that works after post-processing (say, a dangerous HF bath), but only with intimate knowledge of said process steps (e.g., internal material stress levels) and a lot of luck.
- qaute 6y ago> I always wondered why you needed gearing mechanisms in a micro machine. Has there ever been a practical application for gears in MEMS? IIRC, Sandia Lab's SUMMiT V process (the source of videos like [1]) was funded in part to make mechanical latches and fail-safes for nuclear weapons, but I'm not sure what's currently in use for obvious reasons. I don't think they found many other practical applications, though experimentation led to TI's DMD chips, among other things. Occasionally, MEMS techniques are used to make (relatively large) gears for watches. I've also seen people try to use gears for microfluidic pumps, but I don't think any are much better than current simpler solid-state approaches. [1] https://www.youtube.com/watch?v=GiG5czNvV4A https://www.youtube.com/watch?v=GiG5czNvV4A
- quyleanh 6y agoWell done Google. But there is still problem with EDA tool license... Is there any replacement for Cadence Virtuoso tool for chip design?
- stephen_g 6y agoThe efabless people that the talk mentions a bunch of times are using a fully open-source design flow but I think it's a bit hacky (as in, a bunch of command line tools from various open source projects, some of which may be unmaintained judging by the commit logs). They seem to have successfully fabricated a RISC-V based SoC with it though, which is crazy cool. As somebody with a decent amount of FPGA experience, having a go at setting this software up and seeing if I can get anything to synthesise and through place and route is something I've been intending to have a play with, but I haven't had the spare time. It uses yosis for synthesis and a few other tools for the rest of the process, and is called Qflow - http://opencircuitdesign.com/qflow/index.html http://opencircuitdesign.com/qflow/index.html
- quyleanh 6y agoIt is a bit complicated, isn't it? I do hope someday, there is solution which is fully opensource for this problem. And it's seems that this day will be long.
- MayeulC 6y agoIIRC there are a couple ways to produce the intended design. At the end of the day, fabs often take layouts in the GDSII format, which is documented and open. The Klayout open source visualizer is industry-standard in my experience. Now, how do you generate these layouts? It depends on what you are doing. If more on the experimental side of things, writing scripts to generate structures is fine, as long as these conform to the fab-provided design rules. Technically, that's still what everyone is doing at the industrial level, except the scripts -- often written in tcl -- are provided by the fab. Now if you have some FPGA experience, you are probably interested in logic synthesis tools. There are a few ones, I've seen some academic with their own place-and-route stage, for instance. https://open-src-soc.org/program.html#T-CHAPUT https://open-src-soc.org/program.html#T-CHAPUT does that, I think. The slides linked above outline one of the possible ways to do this: leverage chisel ( https://www.chisel-lang.org/ https://www.chisel-lang.org/) and the FIRRTL intermediate representation for RTL description. A few tools can ingest the output and try to come up with a layout. Hammer (https://github.com/ucb-bar/hammer https://github.com/ucb-bar/hammer) is such a tool, but I don't think that PDK is available with it just yet. To be honest, I don't think commercial tools are that advanced, and it would be fairly doable to catch up. There is some interesting work in this field, but since fabbing is expensive, it tends to be more within the academic community than the free software one. I'd look for papers, not on Github, though that's slowly changing. The chip design world is a slow beast to turn around: everything in the fabrication process is optimized to maximize yield, hence very little leeway is allowed: "If it ain't broken, don't fix it" is the motto, for good reason: if changing humidity levels 0.2% can make a fab lose millions; they won't try to use new and experimental software. I'm watching this space, notably with Verilog alternatives such as Migen. The open source community starts to embrace FPGA, wich is already great. I wish more manufacturers opened up their bitstream, so maybe we need an open FPGA? Though this free fabbing offer would be a great fit for Wi-Fi chips, I think. I wonder if People at openwifi (https://github.com/open-sdr/openwifi https://github.com/open-sdr/openwifi) are interested? I hope that gives a few interesting pointers to whoever reads this :)
- cromwellian 6y agoThis reminds me of how cubesats kind of got off the ground because some launch commpanies allowed extra spare capacity to be sold or donated to student projects.
- hinkley 6y agoI couldn't tell which was the cart and which the horse, but the SpaceX telecommunications satellite launch I saw had a rideshare arrangement going on. I suspect what happened is that someone only needed half a payload, and SpaceX filled the rest with their own stuff. But the PR person made it sound like the opposite was happening. I'm not sure what happens when they reach full capacity on their sat network. Space for research projects, or launching surplus consumables?
- moring 6y agoWith the PDK being open, does anyone know if any kind of NDAs are still required to get a chip fabbed? While free-of-charge fabbing is quite nice, I think being NDA-free is even more important so all work including the tweaks necessary for fabbing can be published, e.g. on GitHub. BTW, it will be nice to try this together with the OpenROAD tools [1]. They have support for Google's PDK on their to-do list (planned for q3, but I doubt it will be ready that fast). [1] https://github.com/The-OpenROAD-Project https://github.com/The-OpenROAD-Project https://theopenroadproject.org/ https://theopenroadproject.org/
- lowwave 6y agoyup, NDAs destroys economic productivity.
- lowwave 6y agoFrom talking to VC. NDA are useless. It really comes down to whether you trust the people or not. It is like patent just a gesture. Everything is in the implementation.
- madushan1000 6y agoI think the plan is to let people do exactly what you're talking about(let people publish everything down to layout files). At least that's the impression I got from the talk. There is a distro of OpenROAD called OpenLane trying to target this PDK. fossie have a couple of more talks coming up in the next few months on tooling support including OpenROAD, OpenLane, etc.. And I think they're aiming for the first shuttle run in November, so the tooling will have to be ready at least on Q3.
- cottonseed 6y agoI don't think so. Tim explains in the talk, designs must be submitted via a public Github repository. I think the whole point is to create an open ecosystem.
- ur-whale 6y agoThis is fantastic, for many reasons, but the two that come immediately to mind are: - amazingly good for security. - finally the public at large will get to understand *in details* how an ASIC is designed.
- chrismorgan 6y agoMeta: please don’t use preformatted text for lists. It makes reading much harder, especially on narrower displays. Just put a blank line between each item, treat each as a paragraph.
- ur-whale 6y agoThank you for listing your personal preferences, but I also happen to have mine.
- navanchauhan 6y agoCan I in theory build one optimised for running one program? Will it be of any benefit?
- riffraff 6y agoyes, but it depends on the program, that's what the whole ASIC industry for bitcoin mining is.
- navanchauhan 6y agoI was thinking about AutoDock Vina ( Molecular Docking Software ), I have literally 0 knowledege about hardware :( Then again, this is going to be a really fun experience
- dekhn 6y agoYes, you can build dedicated ASICs. No, it's not worth it for docking software.
- ascorbic 6y agoAccording to Wikipedia there has been some success building FPGAs for Autodock, so maybe it could be. https://en.m.wikipedia.org/wiki/AutoDock https://en.m.wikipedia.org/wiki/AutoDock
- dekhn 6y agoyes but since drug discovery isn't bottlenecked by virtual docking throughput, it doesn't matter. We've seen similar approaches applied to BLAST, and in the end, everybody ends up giving up the ASIC or the FPGA because it's not cost effective long-term.
- exikyut 6y agoI initially did an image search to get a quick idea of what you were referring to. "Oh, that looks commercial/expensive..." - but no, it's open source, under the Apache license. Which means the only question is how motivated you really are to speed it up. If your answer is "really really __REALLY__ motivated", then... - Reimplement the whole thing, in your choice of language, strictly without consideration of performance, to concretely grasp the implementation. - Rewrite your reimplementation efficiently, using profiling etc, and using SSE/AVX or related techniques if/as possible. (I noticed references to Monte Carlo simulation in the code, and found some noise online that suggests this is vectorizable. I don't understand how MC is being used in the code though.) FWIW assembly language is likely 95-99% not worth chasing instead of Rust or C; one of the few real-world scenarios that call for asm is software video decode/encode, which boils down to patterns of hardcore number crunching that compilers are regarded to optimize poorly. I do not know whether this program is slow because it is poorly optimized or slow because it is simply computationally expensive. - Rewrite your implementation to run on a GPU, if possible, using OpenMP or CUDA. (This may require implementing your own engine that achieves the same goals as the existing engine, after you achieve a high-level understanding of why the engine works the way it does, because you may need to rearchitect the way the program works in order to cram it into a GPU.) - Reimplement your implementation in VHDL so it will run on an FPGA. - Retarget your VHDL so it can be fabbed on a fixed-function ASIC. This would be my high-level Handwavy Armchair Guide to achieving what you want :) It's possible that the GPGPU or FPGA milestones will give you a significantly appreciable many-x performance boost. That may be 2x or 10x or 100x; you will be able to find out what is possible almost immediately, as you build your brain-dead implementation and go down little research/analysis paths figuring out how everything works. It's also possible that the current implementation is poorly designed, and that sticking a profiler on it may find low hanging fruit. Likewise, it's equally possible the current implementation is well-tuned above average (despite being written in C++). Oh, I found this random link that may be uninteresting or useful: https://news.ycombinator.com/item?id=18628326 https://news.ycombinator.com/item?id=18628326
- dTal 6y agoCan anyone venture a guess as to why Google might be doing this? What's the incentive structure here?
- amiga-workbench 6y agoI know Google absolutely loathes having Intel silicon in their datacenters, the management engine and other blobs can't be audited. It's conceivable they want to help bring open chips to market to try and remedy this problem.
- Koffiepoeder 6y agoThe market of skilled hardware designers is running low: training costs are high, complexity has skyrocketted. By doing this they can increase attention to a field that is otherwise dominated by big corporates (already somewhat the case). The only way to have a sane and healthy chip market is to make 1) the entry barrier low and 2) stimulate innovation. This does both of that.
- novaRom 6y agoAnother point is that silicon-related tech is currently leaving US and begins booming in China.
- deleted 6y ago[deleted]
- chaz6 6y agoPossibly a new source of intellectual property? I would be interested to read the terms and conditions.
- baybal2 6y agoThey want to spur competition among silicon suppliers. The industry has become dangerously too consolidated, with like of Avago/Broadcomm trying to buy themselves a monopoly. The big semi look at big dotcoms like Google as cows to milk, obviously they don't like it.
- 6y ago
- DCKing 6y agoFrom a hobbyist and preservation perspective, it would be cool if this could be used to produce some form of the Apollo 68080 core to revive the 68k architecture a little bit, and build out the Debian m68k port [0][1]. The last "big" 68k chips were produced in 1995 (that would be a 350nm process?) so this could be hugely improved on 130nm. The 68080 core is currently implemented in FPGAs only and is already the fastest 68k hardware out there. With a real chip, people could continue upgrading their Amigas and Ataris. [0]: http://www.apollo-core.com/ http://www.apollo-core.com/ I can't easily find how "open source" it is though, but it's free to download. [1]: https://news.ycombinator.com/item?id=23668057 https://news.ycombinator.com/item?id=23668057
- herio 6y agoThe Apollo core is not open source. There are some other pretty nice and featured 68k cores that are open source (TG68, WF68K30L etc.) but none that is really close to the features and performance of the Apollo 68080.
- DCKing 6y agoAh that's a shame. I suppose this could be used to perform a revival of 68k without the Apollo core, but it's a shame that the engineering effort already there would not be available. Maybe this would be an incentive for them to open source it, but yeah.
- phonon 6y agoThey have a slack channel... :-) https://wiki.apollo-accelerators.com/doku.php/about_us:links https://wiki.apollo-accelerators.com/doku.php/about_us:links
- armitron 6y agoNote that there have been IP theft and other shadiness allegations from ex-members of the Apollo team. If you do a little research you'll find out that there's plenty of "stay away" and "can't believe they haven't been sued into oblivion yet" indicators and all sorts of misleading claims and marketing. My summary would be that it's a tightly-controlled, closed project lead by questionable people with well-documented histories of questionable practices including ignoring copyrights, distributing infringing software, deleting critical posts from their forums and putting out misleading information.
- jitendrac 6y agoThat is great. It will encourage new hobbyist opensourse Eco-system around hardware community just like many FOSS communities. Even engineers/students from countries with less resources will now be able to design make prototypes in viable way.
- threshold 6y agoFantastic Google! Dream come true
- leojfc 6y agoStrategically, could this be part of a response to Apple silicon? Or put another way, Apple and Google are both responding to Intel/the market’s failure to innovate enough in idiosyncratic manner: - Apple treats lower layers as core, and brings everything in-house; - Google treats lower layers as a threat and tries to open-source and commodify them to undermine competitors. I don’t mean this free fabbing can compete chip-for-chip with Apple silicon of course, just that this could be a building block in a strategy similar to Android vs iOS: create a broad ecosystem of good-enough, cheap, open-source alternatives to a high-value competitor, in order to ensure that competitor does not gain a stranglehold on something that matters to Google’s money-making products.
- janekm 6y agoMy first reaction was that it could be a recruitment drive of sorts to help build up their hardware team. Apple have been really smart in the last decade in buying up really good chip development teams and that is experience that is really hard to find.
- pjc50 6y agoDoes Google have a silicon team?
- daanluttik 6y agoThey created TPU's right? So somewhere inside the alphabet group they must have some expertise
- trsohmers 6y agoAs of a year and a half ago they had over 300+ people across Google working on silicon (RTL, verification, PD, etc) that I’m aware of.
- orbifold 6y agoThey have Norman Jouppi, he apparently was involved in the TPU design.
- temptemptemp111 6y agoLet's build a Ryzen 9 inspired RISC-V with more care for latency please! :)
- novaRom 6y agoCan someone please tell me how photo-masks are produced? I don't understand how can tiny features be printed at almost the same scale as a final structure? With a laser beam? Say, as an input you have a layer description (schematics) - how can you transfer it to a tiny scale so precisely to produce a mask?
- ArchD 6y agoLenses are used so the feature size on the mask is larger than the feature size on the wafer. https://www.nikon.com/about/technology/product/semiconductor/index.htm https://www.nikon.com/about/technology/product/semiconductor...
- rwmj 6y agoPhotographic reduction. The masks are much larger than the final chips. https://commons.wikimedia.org/wiki/File:Semiconductor_photomask.jpg https://commons.wikimedia.org/wiki/File:Semiconductor_photom... (Actually AIUI in EUV photolithography you can't use transparent masks, but must use a kind of mirror with the pattern etched onto it.)
- novaRom 6y agoAccording to Wikipedia masks are only 4 times larger - it is still very tiny.
- ric2b 6y ago
- awalton 6y agoIs enough of the PDK open now to allow for actual hacking on devices? I have a rather simple analog chip I'd love to make for my own personal uses (I'd love a really long modern bucket brigade device to build gritty analog delay lines for synth hacking)...
- fouc 6y agoWhat are the chances that google will add their own hidden or proprietary circuitry to any open-source chips? They'll add all sorts of "Security" and "Tracking" features..
- wolfd 6y agoApproximately zero. They have nothing to gain from doing so, and everything to lose. It isn't a website we're talking about, adding that kind of complexity to a chip would be highly obvious to the people who integrate it, who aren't from Google.
- MaxBarraclough 6y agoTo a chip? Doesn't seem likely. Adding something like an Intel Management Engine is quite a task, and they'd look awful if they got caught trying it in secret. If they're just making the CPU, in isolation from the rest of the system, I imagine it would be just about impossible to do something like that. As to whether such changes could be detected, given that the intended design is known, I'm not sure. Someone more knowledgeable than me might be able to comment on that.
- pjc50 6y agoIf you hand them GDSII then fiddling with it is very time-consuming and difficult, but can be spotted by looking at the resulting chip under a microscope. (Not entirely simple at 130nm as this is shorter than the wavelength of visible light!)
- imtringued 6y agoYou don't need to look at the smallest features of a transistor to notice that the chip has 30% more transistors than your original design.
- Symmetry 6y agoAlso, adding something like that would be an incredible amount of work. Basically you would have to totally re-do the layout even if you're just adding a macro somewhere and totally re-design it if you're not going to end up causing a drastic decrease in max clock rate. That's for an management engine or tracking style thing. A backdoor that makes #5F0A40A3 equal to every other number for password bypass wouldn't be that invasive and might only slow things down by a little bit so I guess that's a possibility if a certain design becomes really popular?
- truth_seeker 6y agoAny Chisel developers here ? How fast is the iterative development and library ecosystem compared to native traditional RTL design tools ?
- seldridge 6y agoI'm one of the Chisel devs. My biased view is that iterative development with Chisel, to the point of functional verification, is going to be faster than in a traditional RTL language primarily because you have a robust unit testing framework for Scala (Scalatest) and a library for testing Chisel hardware, ChiselTest [^1]. Basically, adopting test driven development is zero-cost---most Chisel users are writing tests as they're designing hardware. Note that there are existing options that help bridge this gap for Verilog/VHDL like VUnit [^2] and cocotb [^3]. For libraries, there's multiple levels. The Chisel standard library is providing basic hardware modules, e.g., queues, counters, arbiters, delay pipes, and pseudo-random number generators, as well as common interfaces, e.g., valid and ready/valid. Then there's an IP contributions repo (motivated by something like the old tensorflow contrib package) where people can add third-party larger IP [^4]. Then there's the level of standalone large IP built using Chisel that you can use like the Rocket Chip RISC-V SoC generator [^5], an OpenPOWER microprocessor [^6], or a systolic array machine learning accelerator [^7]. There are comparable efforts for building standard libraries in SystemVerilog, notably BaseJump STL [^8], though SystemVerilog's limited parameterization and lack of parametric polymorphism limit what's possible. You can also find lots of larger IP ready to use in traditional languages, e.g., a RISC-V core [^9]. Just because the user base of traditional languages is larger, you'll likely find more IP in those languages. [^1]: https://github.com/ucb-bar/chisel-testers2 https://github.com/ucb-bar/chisel-testers2 [^2]: https://vunit.github.io/ https://vunit.github.io/ [^3]: https://docs.cocotb.org/en/latest/ https://docs.cocotb.org/en/latest/ [^4]: https://github.com/freechipsproject/ip-contributions https://github.com/freechipsproject/ip-contributions [^5]: https://github.com/chipsalliance/rocket-chip https://github.com/chipsalliance/rocket-chip [^6]: https://github.com/antonblanchard/chiselwatt https://github.com/antonblanchard/chiselwatt [^7]: https://github.com/ucb-bar/gemmini https://github.com/ucb-bar/gemmini [^8]: https://github.com/bespoke-silicon-group/basejump_stl https://github.com/bespoke-silicon-group/basejump_stl [^9]: https://github.com/openhwgroup/cva6 https://github.com/openhwgroup/cva6
- xvilka 6y agoI should note there's open source ASIC toolchain - OpenROAD[1][2]. I wonder if these can be integrated. You also can use SymbiFlow to run your prototype in FPGA[3][4]. [1] https://theopenroadproject.org/ https://theopenroadproject.org/ [2] https://github.com/The-OpenROAD-Project/OpenROAD https://github.com/The-OpenROAD-Project/OpenROAD [3] https://symbiflow.github.io/ https://symbiflow.github.io/ [4] https://github.com/SymbiFlow https://github.com/SymbiFlow
- madushan1000 6y agoThese are already (sort of) integrated. Skywater PDK's primary target is open source EDA flows, commercial flows are they secondary target.
- nihil75 6y agoSpot on. Both are discussed by Tim in the video as part of the solution stack.
- mysterydip 6y agoWould this make it possible to reproduce some historic-but-rare chips like the 4004?
- jecel 6y agoThis is a 0.13µm CMOS process while the 4004 was made using a 10µm PMOS technology. So the electrical characteristics would not be the same. If you don't care about that then the answer is "yes". An attempt to do something like this would have a Z80, a 6502 and a 68000 in a single chip (none of them are rare, however): https://www.crowdsupply.com/chips4makers/retro-uc https://www.crowdsupply.com/chips4makers/retro-uc
- jabl 6y agoWell, the 6502 was famously NMOS which isn't CMOS either. Though wikipedia tells me there is a '65C02' which is a CMOS version of the 6502.
- ibobev 6y agoCould someone explain, is there any advantage of producing a 130nm custom SoC compared to using a lower node FPGA for the same design?
- rnestler 6y agoCurrent consumption. FPGAs are quite energy intensive compared to ASICs. Also for analog stuff you can't use FPGAs. And if you need an ASIC anyways for that why not include the digital part as well?
- Symmetry 6y agoThe crossover point where ASICs become less expensive than FPGAs is also lower than you might think even including mask costs, provided it's on an older process node.
- BurnGpuBurn 6y agoAre there any Risc-V designs that would plug in to this?
- cottonseed 6y agoYes, there are lots of open-source RISC-V cores. Tim Edwards of efabless has another talk about creating a RISC-V based ASIC SOC: https://www.youtube.com/watch?v=EsEcLZc0RO8 https://www.youtube.com/watch?v=EsEcLZc0RO8 based on PicoRV: https://github.com/cliffordwolf/picorv32 https://github.com/cliffordwolf/picorv32. PicoRV is part of the efabless IP offerings. The chips will have a PicoRV harness on them.
- BurnGpuBurn 6y agoThanks!
- chvid 6y agoSounds interesting but what you build as an open source chip? I mean 130nm is 20 year old technology and you can buy general purpose CPUs today which are night and day faster than anything made with 130nm. Allowing you to emulate anything specialized using sofware.
- Symmetry 6y agoGate level emulation is really, really slow. If you've got a nice abstraction like the x86 ISA you can simulate a chip at that level far faster but if you're interested in the net level design rather than the abstraction emulation will be way, way slower. At least in throughput, it takes a long time to fab a chip and so you really ought to do emulation first in any event. And for gate/line level effects things get slower still. Back when I was doing my master's thesis I was running simulations over the weekend on sequences of 100s of instructions in SPICE.
- matheusmoreira 6y agoThat's really awesome. If that gives us widely available open source hardware, our computing freedom will always be safeguarded. We'll always be able to run any software we want even if the hardware is not as good as proprietary designs.
- chrisshroba 6y agoCould anyone offer an explanation of what this means, for all of us who have no experience with hardware at all?
- kingosticks 6y ago> All open source chip designs qualify, no further strings attached! Surely they have some threshold requirements that the thing actually works? How is this going to work? I mean, if there's no investment required from me, what's the incentive for me to verify my design properly? What's the point in them fabbing a load of fatally bugged open-source designs?
- dwild 6y agoI'm pretty sure they'll expect a tiny bit of QA over an FPGA before fabbing them. I don't think they care much about what comes out of it though, whether it's "bugged open-source designs" or not, for sure they want less of the bugged one, but the end-goal isn't the projects, it's the people behind theses projects. Google wants more people that design chips, and then recruit them. This just goes on recruitment cost. They may be interested in the open source part of it, but as soon as they'll stop paying for it (and I'm pretty sure it's not going to stay for long, they mention up to 2021), the state of open source chip design will come back to the current status.
- jsnell 6y agoAll open source designs qualify, doesn't mean they get selected :/ If you look at the slides, they say that each run will be 40 designs, and they'll do one run this year and multiple next. Criteria for how they'll choose if there are more than 40 applicants TBD.
- Taek 6y agoI've spent some time in the chip industry. It is awful, backwards, and super far behind. I didn't appreciate the full power of open source until I saw an industry that operates without it. Want a linter for your project? That's going to be $50k. Also, it's an absolutely terrible linter by software standards. In software, linters combine the best ideas from thousands of engineers across dozens of companies building on each other's ideas over multiple decades. In hardware, linters combine the best ideas of a single team, because everything is closed and proprietary and your own special 'secret sauce'. In software, I can import things for free like nginx and mysql and we have insanely complex compilers like llvm that are completely free. In hardware, the equivalent libraries are both 1-2 orders of magnitude less sophisticated (a disadvantage of everyone absolutely refusing to share knowledge with each other and let other people build on your own ideas for free), and also are going to cost you 6+ figures for anything remotely involved. Hardware is in the stone age of sophistication, and it entirely boils down to the fact that people don't work together to make bigger, more sophisticated projects. Genuinely would not surprise me if a strong open source community could push the capabilities of a 130nm stack beyond what many 7nm projects are capable of, simply because of the knowledge gap that would start to develop between the open and closed world.
- marktangotango 6y agoCould a lot of this backwardness also be explained by patents and litigation risk? There are a lot of patents around hardware, seems like there'd be a high chance of implementing something in hardware that is patented without knowing it's patented.
- chii 6y ago> Want a linter for your project? That's going to be $50k. the thing is that i think the open source software is a miracle that it even exists, and i don't find it strange that nowhere else has replicated the success. Because open source, at heart, is quite altruistic.
- edge17 6y agoOr it's artistic expression for a certain type of individual, and we have accessible art everywhere
- ajb 6y agoSo, this doesn't appear to have been announced by google. It does seem to be real but the OP may be jumping the gun a bit. The authoritative source seems to be the slides of this guy at google: https://docs.google.com/presentation/d/e/2PACX-1vRtwZPc8ykkkgtUkHkoJZrP9jKOo3FYdKqbg-So0ic6_kx7ha1vHnxrWmuxWkTc9GfC8xl0TfEpMLwK/pub?start=false&loop=false&delayms=3000#slide=id.g8a02ce4cad_0_207 https://docs.google.com/presentation/d/e/2PACX-1vRtwZPc8ykkk... From the slides this is "current plans, subject to change". This is an 'open source shuttle process'. Shuttle processes are a relatively cheap way of making small numbers of chips (it is actually more costly per chip, but the fixed cost is smaller). There will be some kind of approval process, and I would imagine that there is a capacity limit for both the number of chips and number of projects. (I didn't have time to watch the talk, so the above is just from the slides)
- cottonseed 6y agoMaybe watch the talk first before commenting? All these questions are answered in the talk.
- deleted 6y ago[deleted]
- ajb 6y agoWell since you evidently did have time to watch the talk, perhaps you also have time to enlighten us about these questions. If not, maybe don't criticise those of us who used at least some of our time to dig out some information for the thread.
- mav3rick 6y agoYou could have just watched the talk instead of reprimanding him.
- rudedogg 6y ago- You get somewhere around ~100-400 chips, TBD later - Each shuttle run will accept 40 projects, if more than that apply a selection process will be used. A lottery was mentioned as a possibility. - First shuttle run this November Like you mention everything is just planned at this point, but the speaker said these were roughly their goals.
- dooglius 6y agoIf you wanted to do something with a hardware root-of-trust, would the GDSII leak needed secrets (i.e. any private keys could be extracted by looking at what you're required to open up), or is that done in some special post-fab way?
- yjftsjthsd-h 6y agoCould you burn in the private key using fuses?
- riking 6y agoTake a look at the Google Titan chip slides for an idea of how to implement this: https://www.hotchips.org/hc30/1conf/1.14_Google_Titan_GoogleFinalTitanHotChips2018.pdf https://www.hotchips.org/hc30/1conf/1.14_Google_Titan_Google... Video: https://youtu.be/ve_64dbM4YI?t=3089 https://youtu.be/ve_64dbM4YI?t=3089 Specifially, slides 35-40. You burn a feature fuse to unlock manufacturing test features. The device is personalized with a serial number + told to generate private key + record stored in database. Then, the key is locked in by burning a second feature fuse that disables any future writing to those segments.
- deleted 6y ago[deleted]
- WatchDog 6y agoMy understanding of ASIC production, is that new circuit designs are capital intensive, they require masks to be produced and machines to be configured for the given pattern. Are older processes more automated? Can the 130nm production line, produce many different designs without any manual intervention?
- bradstewart 6y agoMask sets will still be required for each chip (to my knowledge), but they are significantly cheaper on older processes like 130nm. The process design kit (or PDK) mentioned in the article takes care of "configuring the machiines". The PDK provides describes how to construct low-level primitives (the instruction set, if you will) for the specific fab. Designers then layer on their logic circuits using those primitives.
- deleted 6y ago[deleted]
- timerol 6y agoTFA doesn't really summarize what's available very well, so let me take a shot from a technical perspective: - 130 nm process built with Skywater foundry - Skywater Platform Development Kit (PDK) is currently digital-only - 40 projects will be selected for fabrication - 10 mm^2 area available per-project - Will use a standard harness with a RISC-V core and RAM - Each project will get back ~100 ICs - All projects must be open source via Git - Verilog and gate-level layout I'm curious to see how aggresive designs get with analog components, given that they can be laid out in the GDS, but the PDK doesn't support it yet.
- raverbashing 6y agoI'm thinking 10mm^2 so kinda 3.3mm x 3.3mm. In 130nm (Remember 130nm gave us the late models Pentium 3s, the second model P4s and some Athlons, though all of these had a bigger die size) I'm thinking you could have some low power or very specific ICs, where these would shine as opposed to a generic FPGA solution
- moonchild 6y ago> 10mm^2 so kinda 3.3mm x 3.3mm 3.16mm x 3.16mm?
- raverbashing 6y agoSquare root by head is hard ;)
- lokl 6y agoCould this be suitable for a camera sensor? I don't know anything about hardware, but I am intrigued by the idea of exploring new camera sensor ideas. Edit: Nevermind, another comment says 10 mm^2 per project. That's probably too small for the type of camera sensor I have in mind.
- lizhang 6y agoCan anyone recommend some resources for jumping into asic design to take advantage of this offer?
- makapuf 6y agoInteresting, 130nm was achieved by Pentium III as a reference: https://en.m.wikipedia.org/wiki/130_nm_process https://en.m.wikipedia.org/wiki/130_nm_process
- cmrdporcupine 6y agoI have a friend who has a Verilog clone of the C64 VIC-II chip, which he has interfaced into a real C64 and it's running pretty much everything, demos, etc. even supports weird things like the lightpen. I wonder if his project would fit the bill here... real VIC-II chips are dying all over the place and getting hard to find... manufactured ASICs to replace them could be a popular item....
- phendrenad2 6y agoThis is cool! But I fear the workflow to get a chip out the door requires a lot of niche specialized knowledge. Making a logic design work on an FPGA is much easier, because the chip overhead (stuff like I/O pins) is all handled for you. If I had to design my own I/O pins at the silicon level, I wouldn't know where to start. And having access to open-source tools that give me the ABILITY to build a chip doesn't help with the knowledge I'm missing. I think, however, that this may help Google integrate into academia. I can imagine a lot of MSEE and PhD students are looking at this hungrily.
- canada_dry 6y ago> a logic design work on an FPGA is much easier Whelp... definitely crossing fabbing off my list.
- riking 6y agoThe project comes with a standard harness around your 10mm^2 design, with provided I/O and a working RISC-V supervisor CPU.
- d_tr 6y agoI believe that a lot of people here might be interested in "Minimal Fab", developed by a consortium of Japanese entities. These are kiosk-sized machines that a company can use to set up a fab with a few million dollars. Any individual can then design a chip and have it fabricated very (as in "I want to make a chip for fun") affordably. I was not able to find a ton of information on this, but the 190nm process was supposedly ready last year and there were plans to go below this. The wafers are 12mm in diameter (so basically, one wafer -> one chip) and the clean room is just a small chamber inside the photolithography machine. There are also no masks involved, just direct "drawing".
- derefr 6y agoSo, until now, there's been this niche for FPGAs, where people would buy them in decent numbers to use with static programming, in production devices, simply because they needed some custom DSP or some-such, but the capital costs of an ASIC fab-run would be a killer for their project. Has this announcement thrown that use-case for FPGAs out the window?
- gsmecher 6y agoThe economics of FPGAs and ASICs over the past few decades are covered really well in [1]. It's almost always about production volume. The FPGA's ability to be reprogrammed is often a convenient side-effect. In short, no, this doesn't impact the trade-offs and wouldn't even if Google provided this service as a commercial print-on-demand offering. You can get an ASIC fab'd on older nodes for surprisingly cheap, if you have the know-how and access to tools [2]. When power is a first-class design problem (it frequently is), even an "old" 28nm FPGA like Xilinx's 7 series will run rings around an 130nm ASIC. The extra silicon you're powering in the FPGA is more than offset by the economical access it gives you to modern nodes with lower voltages. [1]: https://ieeexplore.ieee.org/document/7086413 https://ieeexplore.ieee.org/document/7086413 [2]: https://spectrum.ieee.org/tech-talk/computing/hardware/lowbudget-chip-design-how-hard-is-it https://spectrum.ieee.org/tech-talk/computing/hardware/lowbu...
- patwillson22 6y agoMy advice to anyone who's looking for a pathway into open source silicon is to look into E-Beam lithography. Effectively E-Beam lithography involves using a scanning electron microscope to expose a resist on silicon. This process is normally considered to slow for industrial production but it's simplicity and size make it ideal for prototyping and photo mask production. The simplistic explanation for why this works is that electron beams can be easily focused using magnetic lenses into a beam that reaches the nano meter level. These beams can then be deflected and controlled electronically which is what makes it possible to effectively make a cpu from a cad file. Furthermore, It's very easy to see how the complexity of photolithography goes up exponentially as we scale down. Therefore I believe it makes sense to abandon the concept of photolithography entirely if we want open souce silicon. I believe that this approach offers something similar to the sort of economics that enable 3D printers to become localized centers of automated manufacturing. I should also mention that commercial E-beam machines are pretty expensive (something like 1-Mil) but that I dont think it would be that difficult to engineer one for a mere fraction of that price.
- namibj 6y agoI suggest you take a look at how easy maskless photolithography is: https://sam/zeloof.xyz https://sam/zeloof.xyz Theoretically it should be feasible to fab 350 nm without double-patterning by optimizing a simple immersion DLP/DMD i-line stepper. I think ArF immersion with double-patterning should be able to do maskless 90 nm.
- kanwisher 6y agofixing the url http://sam.zeloof.xyz/ http://sam.zeloof.xyz/
- 0xcde4c3db 6y ago> I should also mention that commercial E-beam machines are pretty expensive (something like 1-Mil) but that I dont think it would be that difficult to engineer one for a mere fraction of that price. I'm not sure where it was, but I remember a seeing a project where someone made a rudimentary homebrew electron microscope by chemically etching the tungsten filament from a light bulb (to get the tip sharp enough) and attaching it to a piezo buzzer that was scored to separate it into four quadrants. The filament could be moved by applying various combinations of voltage to the piezo quadrants. I didn't find the one I was thinking of (which I think was ca. 2002 and so maybe just vanished by now), but search results suggest that variations of this have been done by several people.
- gentleman11 6y agoSimple question: aren’t you basically not allowed to make chips because of patents? Not literally forbidden, but aren’t there so many patents that you can’t really work without violating one, even if you have never heard of it or the technique before? It just sounds so hazardous
- StillBored 6y agoBecause apparently no one remembers the other "free" fab service. https://www.themosisservice.com/university-support https://www.themosisservice.com/university-support Previously MOSIS would run select a few student/research designs to go along with the commercial MPW runs, frequently on pretty modern fabs. I'm not really sure how much they still run. (oh here is the MOSIS/TSMC runs for this year https://www.mosis.com/db/pubf/fsched?ORG=TSMC https://www.mosis.com/db/pubf/fsched?ORG=TSMC)
- dasudasu 6y agoBut this one is open to hobbyists. If you're doing a graduate degree in ASIC design and your group doesn't have the funds to do simple fab runs, you're probably in a somewhat questionable program to begin with.
- yummypaint 6y agoAnyone have a sense of how easy it is to audit/verify devices made with this process? I would love to see some properly trustworthy chips for end-to-end encryption come out of this.
- unnouinceput 6y agoQuote: " All open source chip designs qualify, no further strings attached!" There is no such thing as free lunch! I really wonder what is Google's game plan with this. 20 years ago they started to made maps + email + office +... free for everybody, but the game plan was they gathered everything about everybody, so now we know. Sorry Google, I don't trust you one bit anymore.
- resters 6y agoIt would be nice to get all of the HDL used by the HPSDR project fabbed this way.
- kwccoin 6y agoThe difference is one is pure public good but hardware is not that pure. And hence you have other concerns and other means.
- neop1x 6y agoHmm, sounds like Google is hunting for chip design talents. :) We will fab your design and if it looks good, come work for us. :P