icestudio VS chipyard

In fact that docs are out of date and even more boards are supported and you can find the list directly in icestudio menu. If you want to check it beforehand, i think it's possible to see the list here in source code:

https://github.com/FPGAwars/icestudio/tree/develop/app/resou...

This is crazy helpful for beginners: https://github.com/FPGAwars/icestudio

They have drag and drop visual gates and cores with very well documented examples.

This is the project: https://github.com/FPGAwars/icestudio

I am slowly moving off my retro computing hobby. The last straw was recent chip shortage and crazy prices. I bought myself a copy of "The 8088 Project Book" and I wanted to build the presented 8088 breadboard computer. Guess what? The only factory that was building compatible 8088/8086 chips caught fire (Renesas factory fire). I had to order 20 year old chips for the price x2 of the new chips. But not only that, some chips are either unavailable or crazy expensive due to a lot of recent interests in retro-comp.

In other way, the hobby became unreasonably expensive for me. So I decided to move my interests into FPGA. The fun is almost the same, but the cost is way lower (you only need to buy a good board and a book, and you are set up). I started with this extremely simple IDE: https://github.com/FPGAwars/icestudio

As for this build, I have mixed feelings about using FPGAs to revive old computers. Can't we create something new out of it? It would be fun to have a _modern_ FPGA based SBC with easy to program graphics (memory mapped) and with simple device interface (I think USB is way too complicated for hobbyists). Just something powerful enough to create games, yet simple enough so that teenager can write a simple OS in his spare time.

It's probably true that Chisel isn't right for industry -- Google tried it too for the TPU project and eventually went back to Verilog. That said, I think it's main win is that it is great from a research / open-source perspective.

Taking advantage of the functional nature of Chisel enables a set of generators called Chipyard [0] for things like cores, networking peripherals, neural network accelerators, etc. If you're focusing on exploring the design space of one particular accelerator and don't care too much about the rest of the chip, you can get a customized version of the RTL for the rest of your chip with ease. All the research projects in the lab benefit from code changes to the generators.

Chisel even enables undergraduate students (like me!) to tape out a chip on a modern-ish process node in just a semester, letting Chisel significantly reduce the amount of RTL we have to write. Most of the remaining time is spent working on the actual physical design process.

[0]: https://github.com/ucb-bar/chipyard

[1]: https://classes.berkeley.edu/content/2023-Spring-ELENG-194-0...

The repo in question is chipyard: https://github.com/ucb-bar/chipyard

Many companies do just write entire modern SoCs in straight Verilog (maybe with some autogenerated Verilog hacked in there) with no other major organization tools aside from the typical project management stuff. The load-store unit of a modern CPU alone easily exceeds 10k lines of Verilog. It's a similar thing as people who work with kernels—after all, the page table management code in a modern operating system like Linux is absolutely monstrous but still people are able to understand it well enough to be able to make the changes they need and get out.

If you are interested in other languages which hope to make this sort of stuff easier, I'd recommend taking a look at design productivity languages like Chisel and it's associated Chipyard [1], SpinalHDL [2], and Bluespec [3]. Each of these are meant to make defining extremely complex hardware more manageable for humans and there's a lot of interesting work going on right now with each of them.

[1] https://github.com/ucb-bar/chipyard

[2] https://github.com/SpinalHDL/SpinalHDL

[3] https://github.com/B-Lang-org/bsc