RISC-V Distros

Canaan K230 (Kendryte K230 / CanMV-K230)

Kendryte K230 (2×C908) On sale Canaan
Specs
Dual-core 64-bit RISC-V C908: big core 1.6GHz with RVV1.0, little core 0.8GHz; KPU rated at 6 TOPS equivalent (INT8/INT16) (1 TOPS on the K230D); the CanMV-K230 board carries 512MB LPDDR4, microSD, HDMI, 3× MIPI-CSI and USB; typical chip power is about 2W
form factor
CanMV-K230 / BPI-K230D-ZERO (K230D)
Price
CanMV-K230 about $40–60 (AliExpress/Newegg and similar); 01Studio kits $49–88; no official list price (reseller quotes)
Preinstalled / official OS
buildroot / debian / ubuntu
Doc languages
zh / en
Checked
2026-11-01

CanMV (MicroPython firmware) is the highest-volume, best-documented form; on the Linux side the vendor pushes Buildroot. Apache NuttX has separate CanMV-K230 board support (not a distro), and the RuyiSDK support matrix already covers the CanMV K230(D), so `ruyi device provision` can fetch images.

Distros

  • Buildroot Official k230_linux_sdk's default Buildroot setup (k230_canmv/k230_evb defconfigs)
  • Debian Official The SDK supports make debian, and there is an official K230 Debian/Ubuntu guide
  • Ubuntu Official The SDK supports make ubuntu, same guide

Download

Docs and videos

Pitfalls

  • AMP heterogeneous design: by default the little core runs Linux and the big core RT-Smart/CanMV; only the big core has the V extension, so vector workloads must land on the right core
  • The official Linux path is Buildroot; Debian/Ubuntu must be built with make debian / make ubuntu, and there are no ready official desktop images
  • Firmware must match: CanMV IDE only accepts files named CanMV-K230_micropython*, and a K230 SDK image won't connect
  • The nncase toolchain is closed source and tightly bound to firmware versions; early build docs are Chinese only

RuyiSDK test reports3

Systems RuyiSDK actually tested on this board. Open a report for install steps and the verdict.

DistrosStatusVersionsLast testedReport
Debian◐ Basic—2024-06-21Open report
Fedora◐ Basic382024-06-21Open report
Ubuntu◐ Basic—2024-06-21Open 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.

Sources11

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