8 ms·
"Most importantly, we have to change the culture of hardware design. Today, we don’t have open sharing … " This, to the 100th power. The culture in the EDA in
by ur-whale 8y ago
"Most importantly, we have to change the culture of hardware design. Today, we don’t have open sharing … "
This, to the 100th power.
The culture in the EDA industry is stuck in the 1950's when it comes to collaboration and sharing, it's very frustrating for newcomers and people who want to learn the trade.
As was pointed out by someone in another hardware related HN thread, what can you expect from an industry that is still stuck calling a component "Intellectual Property"?
The un-sharing is built into the very names used to describe things.
- sametmax 8y agoThey have been some attempt. E.g: the mit project called sirus that used python 2.5 as a dsl to describe high level components you could combine and reuse and then process to generate system c or verilog. Unfortunaly, while the tool is pretty nice, it never resulted in major adoption (qualcom has some tool using it internally and a few others) and we haven't seen the idea of making reusable libs and components florish. Somebody would need to find this project and up it to python 3.6. With current tooling, it would make writting code in it really nice and ease the creation of reusable components. Reusability in raw verilig is hard
- rixrax 8y ago>> "Most importantly, we have to change the culture of hardware design. Today, we don’t have open sharing … " I'll have popcorn ready for the eventuality where IP blocks are widely available under GPL type of FOSS licenses and Intel|AMD|ARM|TI|... is eventually found to include one or more of those open sourced blocks with incompatible license in their chips.
- ur-whale 8y agoThe exact same arguments have been perused ad nauseam by old-timers in the software industry in the 80's and 90's when they clamored against open-source being anti-capitalist and un-american. Not sure how and why H/W is different.
- wrs 8y agoDifferent level of liability. When GPL missteps are discovered in software, the offender can usually just re-release the software without the GPL code and move on. In hardware…it's soldered into a bunch of devices all over the place. Consider Intel taking a $475 million hit for the FDIV bug (requiring a hardware replacement) vs the invisible bugfixing through microcode (i.e., software) they do now.
- rixrax 8y agoI was thinking this mostly from the standpoint of viral nature of GPL-kind of FOSS licenses. E.g. somehow, somewhere someone manages to inject a GPL licensed IP block into a commercial CPU, after which, with my layman understanding, chip manufacturer now owes under the terms of GPL everyone who happens to have purchased one of those chips a full VHDL, Verilog etc. source code of the entire chip. In software you can always replace a library that had incompatible license with another. Not sure how this would work with a chip. As for attempts to modernize EDA industry, I welcome that in open arms. And if in the process we end up open sourcing a lot of current IP blocks (think of USB, HDMI, etc. designs) - all the better.
- analognoise 8y agoThis will never, ever happen, so why ponder it?
- JoachimS 8y agoNot sure what cores will be needed for you to break out the popcorn. But there are actually quite a few cores available under open and free licenses. First off, the RISC-V community is based on the open ISA. There are several open implementations of the ISA. And the RISC-V community is meaking good headways in developing open tools, peripheral cores etc. https://riscv.org/ https://riscv.org/ Secondly there are at least two attempts at collecting and tracking open cores for FPGA- and ASIC-implementations. LibreCores is the newer project. They have collected quite a few projects: https://www.librecores.org/ https://www.librecores.org/ https://www.librecores.org/project/list https://www.librecores.org/project/list Related to LibreCores is the SoC-builder and core package handler Fusesoc by Olof Kindgren. Fusesoc makes creating your SoC easy: https://github.com/olofk/fusesoc https://github.com/olofk/fusesoc The older project is OpenCores. OpenCores has been quite tightly related to the OpenRISC CPU core, the wishbone set of on-chip interconnect solutions. They have been used in many FPGAs and ASICs https://opencores.org/ https://opencores.org/ https://openrisc.io/ https://openrisc.io/ Then you have projects like Cryptech that develops a complete, totally open, Hardware Security Module capable of doing certificate signing, OpenDNSSEC signing etc. The Cryptech Alpha design from PCB to FPGA cores and SW including pkcs11 handling is open. The project has amassed quite a few cores. The PCB design is available in kiCAD. (disclaimer: I'm part of the Cryptech core team doing a lot of the FPGA design work.) https://cryptech.is/ https://cryptech.is/ https://trac.cryptech.is/wiki/GitRepositories https://trac.cryptech.is/wiki/GitRepositories Speaking of tools like KiCAD, there are aqtually quite a few open tools for HW design. For simuation there are Icarus Verilog, Verilator, cver for example. They might not be as fast as VCS by Synoptsys. But they do work. I use them daily. http://iverilog.icarus.com/ http://iverilog.icarus.com/ https://www.veripool.org/projects/verilator/wiki/Intro https://www.veripool.org/projects/verilator/wiki/Intro For synthesis, P&R the state is less good. For implementation in Altera and Xilinx devices you currently have to use the cost free tools from the vendors. But there is work ongoing to reverse engineer Xilinx Spartan devices. I don't know the current state though. But what has been reverse engineered are the ICE40 FPGA devices from Lattice. And for these you can use the open tool Yosys by Clifford Wolf (also mentioned below by someone else). http://www.clifford.at/yosys/ http://www.clifford.at/yosys/ And if you are looking for open implementations of crypto functions etc I have quite a few on Github and try to develop more all the time: https://github.com/secworks https://github.com/secworks The sha256 and aes cores has been used in quite a few FPGA and ASIC designs. Right now I'm working on completing cores for the Blake2b and Blake2s hash functions. I agree that we in the HW community is waay behind the SW community in terms of open tools, libraries (i.e. cores). But it is not totally rotten, and it is getting better. RISC-V is to me really exciting.
- civilitty 8y agoIt's not just the EDA industry, it's almost all of hardware including most of the embedded software people. Yeah, I get it - I too am sometimes stuck using some old proprietary compiler with a C standard older than some of the people I work with - but come on. On my last job I used a Qualcomm radio and they ended up giving me close to a thousand zip files of driver revisions going back a decade because their build process kept screwing up the output source code. All it took was running an open source static analysis tool and 200 man-hours of junior developer time to fix the root causes of 90% of their bugs - for a product that has made billions of dollars (and I'm not talking about the GSM/4G chips with crazy standards that require tons of real R&D). You read that right. Their build system outputs source code, generated from another C code base, using macros to feature gate bug fixes depending on who the customer is. The account managers would sent a list of bugs that a given client had experienced and the backoffice engineers would make a build that fixed only those bugs. Forget about collaboration and sharing. They haven't even figured out the basic business processes that many software engineers take for granted.
- makmanalp 8y ago> the backoffice engineers would make a build that fixed only those bugs Makes perfect business sense! Those customers didn't pay to get those bugs fixed, so why should they get the fixes??? /s Holy moly.
- usmannk 8y agoI think a reasonable explanation may be that other customers possibly have come to unknowingly rely on some of the bugs. Shipping a fix of all the bugs could actually break their code!
- emeraldd 8y agoOr their hardware, some of the impact of those bugs could be built into the physical hardware. By that point. Edit:fixed a typo.
- 8y ago
- WalterBright 8y agoI designed the ABEL language back in the 80's for compiling designs targeted at programmable logic arrays and gate arrays. It was very successful, but it died after a decade or so. It'd probably be around today and up to date if it was open source. A shame it isn't. I don't even know who owns the rights to it these days, or if whoever owns it even knows they have the rights to it, due to spinoffs and mergers.
- phkahler 8y agoHave you looked at chisel?
- stn8188 8y agoI believe there are some Lattice ispPAC parts that still use ABEL, at least on the back end of their GUI.
- analognoise 8y agoVerilog was heavily influenced by ABEL, and is now the predominant HDL in many places.
- Tade0 8y agoIt was very successful, but it died after a decade or so. Perhaps not entirely. We had one lab session dedicated to it during my junior year in college. That was ten years ago but apparently they haven't changed that[0] (course description in english at the bottom of the page). [0] http://studia.elka.pw.edu.pl/pl/18L/s/eres/eres/wwersje$.startup?Z_ID_PRZEDMIOTU=PTCY http://studia.elka.pw.edu.pl/pl/18L/s/eres/eres/wwersje$.sta...
- drblast 8y agoHoly shit, around 2005/6 I took an EE class in programmable logic that used ABEL for the labs. I couldn't find any information on it anywhere and all we had to learn the language was an old single-page photocopy of an example that had been re-copied so many times it was barely readable. And the ends of the lines were cut off. Needless to say, the ABEL projects were frustrating...indeed a shame that it's not open source.
- tryptophan 8y agoI wonder how a system would turn out in which all electronics/software are forced to have both their diagrams/schematics and code published, but in exchange this is copyrighted for like ~7 years or so.
- fjsolwmv 8y agoYou are describing the patent system
- esmi 8y agoWhat in the EDA industry is preventing this? Every CAD system I know of supports ways of group circuits into modules and libraries for multiple Instantation. And those libraries are distributable.
- deleted 8y ago[deleted]