Live data from Hacker News

Developing open-source FPGA tools

twitter.com

21–30 of 80 posts

Re: Developing open-source FPGA tools

#21

For those who are not familiar with silicon vendors' toolchain, it really is very poor quality especially when they started pushing for GUI based Graphical/System development. Vendors make money selling silicon, they see the toolchain as a necessary evil. There are 2018 tools that are still unable to fully support VHDL-2008 standard. Many bugs reported years again remain open. And often the GUI centric approach means…

Xilinx's toolchain is the worst piece of software I've ever had to work with.

There are two things that amaze me:

1. That the dumpster fire is actually capable at all to synthesize hardware without exploding

2. That their head of software still has a job.

Re: Developing open-source FPGA tools

#23

For those who are not familiar with silicon vendors' toolchain, it really is very poor quality especially when they started pushing for GUI based Graphical/System development. Vendors make money selling silicon, they see the toolchain as a necessary evil. There are 2018 tools that are still unable to fully support VHDL-2008 standard. Many bugs reported years again remain open. And often the GUI centric approach means…

Psst…I think you mean "silicon".

Psst...I think you mean "silicium" :P

(before any of you start typing your answers: that's the joke)

Re: Developing open-source FPGA tools

#25
post #19
post #13

Earlier quoted context omitted.

Can't agree more. We literally have a version controlled Windows image with Vivada just to be able to quickly restore it when it breaks. We switched nearly all of our PCs to Linux, and it's ironic that it is our engineers' computers that still have to be on Windows because of Solidworks, MCU toolchains, Virtuoso and other semi tooling

The non-software engineering world is laughably behind the times when it comes to computer technology and software. SolidWorks is one of the defacto industry standard CAD packages, and their version control software essentially just creates copies of the files and increments the versions. There's no real concept of change management on the content level.

OpenSCAD is a nice example of how this kinda stuff can work. It's nowhere near viable as a general purpose CAD program, but the concept could easily scaled up to the level of SolidWorks.

Its file format works very well with version control systems, is human readable to an extent and can be opened with any text editor (so your data isn't 100% gone if one bit gets accidentally flipped).

Re: Developing open-source FPGA tools

#26

What are people doing with FPGAs? I'd be really interested in understanding or seeing some cool projects!

Motor control for a pretty high number of motors.

There's rumors that a couple of the big cloud vendors use them on network cards for SDN.

Integration with non standard peripherals like ku band radios on a satellite.

Re: Developing open-source FPGA tools

#27

For those who are not familiar with silicon vendors' toolchain, it really is very poor quality especially when they started pushing for GUI based Graphical/System development. Vendors make money selling silicon, they see the toolchain as a necessary evil. There are 2018 tools that are still unable to fully support VHDL-2008 standard. Many bugs reported years again remain open. And often the GUI centric approach means…

> Also specifically with Xilinx they seem to have zero consideration for basic version control and create/duplicate/modify an explosion of files and cached versions of files.

There is an ugly feedback loop here. HDL tools interact poorly with version control -> it is difficult to collaborate using those tools -> HDL engineers would rather silo up than fight the tools -> no pressure to improve tools' support for version control.

Re: Developing open-source FPGA tools

#28

What are people doing with FPGAs? I'd be really interested in understanding or seeing some cool projects!

Motor control for a pretty high number of motors. There's rumors that a couple of the big cloud vendors use them on network cards for SDN. Integration with non standard peripherals like ku band radios on a satellite.

>There's rumors that a couple of the big cloud vendors use them on network cards for SDN.

No rumours needed, the papers are out there in the open.

Re: Developing open-source FPGA tools

#29
post #28

Earlier quoted context omitted.

Motor control for a pretty high number of motors. There's rumors that a couple of the big cloud vendors use them on network cards for SDN. Integration with non standard peripherals like ku band radios on a satellite.

>There's rumors that a couple of the big cloud vendors use them on network cards for SDN. No rumours needed, the papers are out there in the open.

I said rumors due to saying "a couple". I know that azure is pretty public about it, but I didn't think AWS and Google were.

Re: Developing open-source FPGA tools

#30

For those who are not familiar with silicon vendors' toolchain, it really is very poor quality especially when they started pushing for GUI based Graphical/System development. Vendors make money selling silicon, they see the toolchain as a necessary evil. There are 2018 tools that are still unable to fully support VHDL-2008 standard. Many bugs reported years again remain open. And often the GUI centric approach means…

Xilinx's toolchain is the worst piece of software I've ever had to work with. There are two things that amaze me: 1. That the dumpster fire is actually capable at all to synthesize hardware without exploding 2. That their head of software still has a job.

Try inaccel.com
Post reply on HN