learn-fpga VS nextpnr

I've followed this tutorial recently, and it's amazing:

https://github.com/BrunoLevy/learn-fpga/blob/master/FemtoRV/...

The author includes detailed instruction for how to build a micro-controller in Verilog on an icestick, starting from a very simple blinker all the way to a functional RISC-V core.

My other suggestion would be: for most of the toolchain, skip your package manager and directly install the binary artifacts published on this Github repo:

https://github.com/YosysHQ/oss-cad-suite-build

You'll spare yourself a world of pain.

You might want to look at https://github.com/BrunoLevy/learn-fpga

Lattice Icestick is pretty cheap and has just enough LUTs to run a small riscv. Also check out https://github.com/BrunoLevy/learn-fpga

Thanks Bruno Levy

These are good starting points: https://github.com/BrunoLevy/learn-fpga/ and, from there, https://github.com/BrunoLevy/learn-fpga/blob/master/FemtoRV/README.md.

The best point-of-entry for "tiny" MCUs these days is FemtoRV32-Quark or SERV. I also maintain my own small RISC-V core (Minimax), though it's early on in graduating from "experiment" to "real design".

Rust blinky on RISC-V soft core If you were looking for, an introduction example of an embedded Rust program, running on a RISC-V soft core, check out this blinky that is using the FemtoRV .

Nope - that's all there is.

It's possible to be incredibly expressive in Verilog and VHDL. This implementation is written in VHDL, which has an outdated reputation for being long-winded.

Also worth a look: FemtoRV32 Quark [0], which is written in Verilog.

[0]: https://github.com/BrunoLevy/learn-fpga/blob/master/FemtoRV/...

If the name were an arbitrary word which didn't attempt to define itself, would that be any better? I don't see why the name must mean anything specific, nor why you should expect the name to explain what the project is. That's what the documentation or other descriptive text is for. That the name gives some understanding at first glance is a bonus.

PnR is "place and route", and is a very common acronym in the ASIC/FPGA/VLSI space. It seems fair to expect those who'd use this specialized variant of Yosys to also be familiar with PnR. For reference, here's [1] Yosys's PnR tool, which expands the acronym in its README title.

Realistically, if you're using Yosys tools, you're going to need to have some familiarity with the underlying flows anyway; in my experience they're very powerful but also pretty DIY. That's not great, but it's the reality. That's just the nature of the space right now, given the alternative is a ~$1M single user license.

[1] https://github.com/YosysHQ/nextpnr

Check out Nextpnr. There's only a few lines it supports, but it is expanding. Smaller devices are especially well supported.

I'm not much aware if it's already considered fully supported but as answered on this issue, ECP5 is the best supported FPGA for the toolchain(but its talking about nextpnr specifically tho). But personally, I found no problem with it.