RISC-V Distros

Yocto / OpenEmbedded

Upstream architecture Build system Needs some effort

Bottom line

Aimed at industrial/production use; hobbyists should start with Armbian or Buildroot instead.

Based on
Built from source (BitBake + oe-core + meta-riscv)
Upstream
Build system: oe-core ships the qemuriscv32/qemuriscv64 machines and a riscv64 tune; concrete boards come from the official RISC-V layer meta-riscv (under the riscv/ org), which provides the machine configs.
Versions
6.1 Blacksail (current series) · 6.0 Wrynose (LTS, supported until 2030-04)
Doc languages
en
Derivatives
Vendor Yocto BSPs from SpacemiT / StarFive / T-Head follow the oe-core + meta-riscv pattern
Checked
2026-11-01

Boards

Download

Docs and videos

Pitfalls

  • Steepest learning curve: BitBake syntax plus layer versions that must match exactly (meta-riscv tracks master)
  • The first build downloads tens of GB and takes hours
  • No ready-made images; you produce the wic/sdimg yourself
  • The vendor FSBL/TEE still has to be obtained separately — a purely open-source flow won't work

RuyiSDK test reports4

Hands-on records from RuyiSDK, board by board. Open a report for the full install steps and verdict.

BoardsStatusVersionsLast testedReport
Milk-V Duo series (Duo / Duo 256M / Duo S)◐ Basic—2024-11-25Open report
Milk-V Duo series (Duo / Duo 256M / Duo S)◐ Basic—2024-11-25Open report
SiFive HiFive Premier P550◌ Needs verification—2025-04-09Open report
STAR64◐ Basic—2025-07-13Open report

Status meanings: good — fully usable (desktop boots); basic — basic system (serial console works); part — partial functionality; cft — image exists, needs verification; cfh — documented as supported but fails to boot; cfi — claimed supported, no image; wip — announced only.

Sources9

The full source list and how each claim is judged: Sources