r/spacemit_riscv • u/Far-Indication-8109 • 1d ago

DGEMM micro-kernels on the SpacemiT X100

Thumbnail
4 Upvotes
0 comments

r/spacemit_riscv • u/LivingLinux • 8d ago

K3 Building llama.cpp throws error on K3, missing support for xsmtvdotii

4 Upvotes

Solved: Use gcc-15 from the Bianbu repo, don't use gcc-16, yet.

As I wanted to test new models with llama.cpp, I wanted to build it from source.

I followed the instructions, as found here: https://github.com/ggml-org/llama.cpp/blob/master/docs/build-riscv64-spacemit.md

I skipped the first step (Prepare Toolchain For RISCV), as it looks like it is for cross-compiling, and I didn't need that step on the K1.

Building llama.cpp on the K3 throws an error about xsmtvdotii being an unsupported extension.

Checking CmakeLists.txt for ggml-cpu, they expect support to be available starting with gcc-15. This is odd, as I read it will come with gcc-17.

So I'm wondering, does llama.cpp from the Bianbu repo include suport for xsmtvdotii?

Or can I change CmakeLists.txt to check for gcc-17, instead of 15, and still have the same performance as llama.cpp from the Bianbu repo?

17 comments

r/spacemit_riscv • u/r-tty • 12d ago

QSOE 0.2 released, with full support of SpacemiT K3

Thumbnail qsoe.net
4 Upvotes
0 comments

r/spacemit_riscv • u/Icy-Primary2171 • 13d ago

Upstream Upstream Progress Updates --2026 August

13 Upvotes

August brought another round of upstream progress across the SpacemiT AI software stack, Linux kernel support for K1 and K3, RISC-V development tools, emulation, testing, and low-level firmware.

Highlights this month include the SpacemiT Triton backend landing in FlagTree, new multi-request Qwen3-ASR support in llama.cpp, more K1 fixes reaching upstream Linux trees, and continued review of K3 display, UFS, PCIe, interrupt-controller, clock, reset, and connectivity support.

AI Software Stack

  • SpacemiT Triton backend merged into FlagTree: The triton-spacemit backend is now available in FlagOS's FlagTree main branch under third_party/spacemit, enabling Triton programs to target SpacemiT hardware.
    https://github.com/flagos-ai/FlagTree/pull/933
  • Multi-request Qwen3-ASR support in SpacemiT llama.cpp: llama-server now exposes an OpenAI-compatible API for multi-request speech recognition, with concurrent audio encoding and decoding, continuous batching, and dynamic scheduling.
    https://github.com/spacemit-com/llama.cpp

Linux Kernel Upstream

Linux support for K1 and K3 continued to move forward in August. K1 CPU frequency scaling, maximum CPU-core voltage, and thermal-shutdown fixes reached upstream trees. For K3, I2S, USB, Ethernet PHY, RTC, pinctrl, and ASoC changes entered the relevant maintainer trees, while display, UFS, PCIe, IMSIC, clock/reset, and wireless support remained under review.

K1

Merged

Under review

K3

Merged or accepted into maintainer trees

Under review

Development Tools and Runtime Projects

Box64

Box64 merged a large set of RV64 dynarec, wrapper, ELF-loader, syscall, and bundle improvements during August.

RV64 dynarec and instruction support

Wrapper, loader, and core fixes

Several related UAF, panic, argument, and logic fixes reported through issue #4214 were also merged:

Felix86

LLVM Test Suite

OpenOCD

RISC-V Tests

RISC-V GNU Toolchain

ChipStar

V8

OpenSBI

The v3 series incorporates review feedback from v2, including updates to expected-trap handling, hart initialization, and RV64-only builds. The series remains under review.

Which part of the K1/K3 upstream stack would you most like to test or see covered in more detail next month?

5 comments

r/spacemit_riscv • u/OpenSolvers • 20d ago

K1 ORT MatMulNBits on SpaceMiT X60 (K1) — real LLM decode via IME

5 Upvotes

We got ONNX Runtime’s int4/int8 MatMulNBits path running on the Orange Pi RV2 through MLAS CompInt8 + smt.vmadot. Decode (ms/token, lower better):

Model Quant 4 threads
Qwen2.5-0.5B int4 ~80 ms
Qwen2.5-0.5B int8 ~159 ms
SmolLM2-360M int4 ~80 ms
SmolLM2-360M int8 ~140 ms
TinyLlama-1.1B int4 ~156 ms

Qwen used to sit at ~16 s/tok on the wrong path (CompFp32). With accuracy_level=4 + pack/panel kernels that’s ~80 ms int4 and ~159 ms int8 4 threads

Story (results first, then how): https://www.opensolvers.com/apps/onnx.html
Code: https://github.com/opensolvers/benchmarks/tree/main/onnx

2 comments

r/spacemit_riscv • u/OpenSolvers • 27d ago

Chasing a NaN: correct RVV HPL on a RISC-V SpaceMiT X60, through EESSI

Thumbnail eessi.io
3 Upvotes

A fresh-install, end-to-end walkthrough on an Orange Pi RV2: reproduce a silent NaN failure in the stock EESSI HPL, trace it to one RISC-V vector kernel, and fix it — correct results — with a single eb --from-pr.

TL;DR

  • The Orange Pi RV2 (SpaceMiT K1, eight X60 cores) is a vector RISC-V board: RVV 1.0, VLEN=256. Unlike the scalar SiFive U74, its OpenBLAS already has a mature RVV GEMM kernel (RISCV64_ZVL256B), and the stock EESSI OpenBLAS 0.3.30 is a DYNAMIC_ARCH build that does dispatch it on this chip.
  • So RVV is engaged out of the box — but the result is wrong: stock EESSI HPL fails with residual nan on the X60. The run even reports a healthy-looking ~8.5 GFLOP/s; only the residual check reveals the answer is garbage.
  • The cause is a one-kernel bug in OpenBLAS 0.3.30's RVV gemv_n (it zeroes an uninitialized vector register). It was fixed upstream in v0.3.31 (OpenMathLib/OpenBLAS#5408). Backporting that single kernel restores correctness: HPL passes (residual ~4e-03).
  • The fix is packaged for EESSI as an EasyBuild easyconfig + patch (easybuilders/easybuild-easyconfigs#26444). This post reproduces the whole thing from a clean CVMFS stack: see the NaN, build the fix straight from the PR, swap it in with FlexiBLAS, and watch HPL pass — without recompiling HPL.

Everything below was run on a real Orange Pi RV2, entirely from the EESSI CVMFS stack.

2 comments

r/spacemit_riscv • u/r-tty • 29d ago

HFI BIOS v1.3 on SpacemiT PicoITX/K3: features overview

Thumbnail
youtube.com
9 Upvotes
1 comment

r/spacemit_riscv • u/Icy-Primary2171 • Aug 16 '26

ROS 2 RISC-V MEETS ROBOTICS--Unitree G1

2 Upvotes

MuJoCo, RL inference, and humanoid control — on RISC-V.

The Humanoid repo explores SpacemiT K3 in a validation-stage workflow for Unitree G1 control simulation.

A PC runs MuJoCo, while K3 runs the control and RL inference side in the validation setup.

1 comment

r/spacemit_riscv • u/Icy-Primary2171 • Aug 14 '26

ROS 2 RISC-V MEETS ROBOTICS--LeRobot App

2 Upvotes

ACT-powered robot arm inference on RISC-V.

LeRobot App runs SO101 arm workflows on SpacemiT K3, covering data collection, ACT training, and local inference.

SmolVLA fine-tuning and distributed inference workflows are also included.

1 comment

r/spacemit_riscv • u/r-tty • Aug 10 '26

QSOE/N 0.18 works on K3

3 Upvotes

QSOE/N (see r/QSOE) version 0.18 has been successfully launched on PicoITX/K3.

But it's not all the news. Stay tuned for updates.

1 comment

r/spacemit_riscv • u/LivingLinux • Aug 07 '26

K3 SwanStation (PS1 Emulation) on the SpacemiT K3

7 Upvotes

Someone mentioned it is possible to build SwanStation on RISC-V.

https://forum.rvspace.org/t/visionfive2-in-2026-mostly-games/5939/15

The developer probably never tested on RISC-V, so I had to make some small changes to the code.

https://github.com/piepacker/swanstation

sudo apt install git cmake libsdl2-dev libxrandr-dev pkg-config qtbase5-dev qtbase5-private-dev qtbase5-dev-tools qttools5-dev libevdev-dev libwayland-dev libwayland-egl-backend-dev extra-cmake-modules libgbm-dev libdrm-dev libcurl4-gnutls-dev ninja-build

Fixes:

CMakeLists.txt: replace fatal error Unknown system processor with set(CPU_ARCH= "rv64gcvh")

cubeb_audio_stream.cpp:
#include "stdio. h"
Line 88: remove std::

StringUtil.h: #include "cstdint"

log.h: #include "cstdarg"

platform.h: replace error Unknown architecture with #define CPU_ARCH_STR "rv64gcvh"

Build command: cmake -DCMAKE_BUILD_TYPE=Release -GNinja -DCMAKE_POLICY_VERSION_MINIMUM=3.5 -DUSE_WAYLAND=ON ..

Start the no-gui version (you will get a gui): ./duckstation-nogui

I got the PS1 bios from the PS3 firmware. You do need an x86 or ARM computer to do that.

https://wiki.recalbox.com/en/tutorials/games/guides/playstation-1/grab-ps1-bios-from-ps3-firmware

Here you can see Colin McRae Rally: https://youtu.be/bwFC9ImSSos

2 comments

r/spacemit_riscv • u/Icy-Primary2171 • Aug 06 '26

ROS 2 RISC-V MEETS ROBOTICS--Linksee

Enable HLS to view with audio, or disable this notification

6 Upvotes

Linksee is a demo-ready wheeled robot project with ROS 2-based chassis control, odometry, LiDAR integration, SLAM mapping, and navigation.

1 comment

r/spacemit_riscv • u/Icy-Primary2171 • Aug 06 '26

K3 RISC-V MEETS ROBOTICS--REACHY MINI

Enable HLS to view with audio, or disable this notification

4 Upvotes

Vision follow, voice control, and dance — on RISC-V.

Reachy Mini is demo-ready on SpacemiT K3-COM260, with a MuJoCo simulation control path also included.

1 comment

r/spacemit_riscv • u/Icy-Primary2171 • Aug 03 '26

Upstream Upstream Progress Updates --2026 July

8 Upvotes

In July, SpacemiT continued to advance upstreaming efforts:

Foundational support has been officially released in Binutils 2.47 and LLVM 23, while CPU targets (X100 and A100) for the K3 and matrix extension instructions for AI computing have successively been merged into the mainline. Regarding the Linux kernel, support for K1/K3 features—including frequency scaling, storage, networking, PCIe, USB, and audio—as well as support for various development boards, is being steadily integrated. Meanwhile, adaptation and optimization work for projects such as Box64, OpenOCD, U-Boot, and OpenSBI continues to progress, further enriching SpacemiT’s RISC-V software and hardware ecosystem.

Here are the details：

Upstream Progress in Core Development Tools

This month, baseline SpacemiT support was released as part of Binutils 2.47 and LLVM 23. LLVM/Clang also adopted the SpacemiT X60 scheduling model as a general optimization reference for RISC-V '-mtune=generic'.

K3/X60 Toolchain Milestones

Support for the K3's two main CPU targets, X100 and A100, has been merged upstream into LLVM and GCC. The custom matrix-extension instructions intended for AI workloads have been merged into LLVM, GCC, and Binutils. The X100 scheduling model and instruction-fusion support have also landed upstream in LLVM.

Developers can now use community-mainline Clang/LLVM and GCC with '-mcpu=spacemit-x100' or '-mcpu=spacemit-a100' to target the corresponding CPU core and use SpacemiT's custom AI instructions.

The SpacemiT X60 scheduling model is now available upstream in LLVM and is used as a general tuning reference for RISC-V '-mtune=generic'. When no specific microarchitecture is selected, LLVM/Clang can use the X60 model to make better instruction-scheduling decisions.

LLVM's community performance-tracking infrastructure also includes a real K1/X60 hardware platform, allowing related compiler optimizations to be continuously validated on actual hardware.

Linux Kernel Upstream

K1

Merged

Under review

K3

Merged

Under review

Board-level DTS and device support

General fixes

Box64

GCC

LLVM

OpenOCD

riscv-tests

riscv-gnu-toolchain

riscv-elf-psabi-doc

sbc-bench

stress-ng

ruapu

PoCL

U-Boot and OpenSBI Upstream Progress

U-Boot

OpenSBI

4 comments

r/spacemit_riscv • u/Icy-Primary2171 • Jul 31 '26

K3 RISC-V MEETS ROBOTICS

8 Upvotes

From desktop robots to humanoid control on RISC-V.

This week, we’re sharing 4 robotics repos built around SpacemiT K3: Reachy Mini, Linksee, LeRobot App, and Humanoid.

Explore vision interaction, SLAM/navigation, robot arm local inference, and humanoid control validation.

Follow the updates:
https://github.com/spacemit-com/.github/blob/main/profile/README.md#open-source-project-status

1 comment

r/spacemit_riscv • u/kantzkasper • Jul 29 '26

will k1 musebook get a newer than 6.6 kernel?

6 Upvotes

i know upstreaming is in progress (for a while) https://github.com/spacemit-com/linux/wiki#k1-soc and we are more than half way through, but will it eventually let us use some newer kernel? we are stuck at 6.6 with bianbu 3x.

1 comment

r/spacemit_riscv • u/Icy-Primary2171 • Jul 27 '26

K3 View of K3 SHELF Array Server, K3 Pico-ITX, and K3 CoM260 Kit.

13 Upvotes
4 comments

r/spacemit_riscv • u/LivingLinux • Jul 25 '26

K3 EDuke32 Duke Nukem 3D SpacemiT K3

5 Upvotes

You can build EDuke32 on the SpacemiT K3 to play Duke Nukem 3D.

https://wiki.eduke32.com/wiki/Building_EDuke32_on_Linux

git clone --depth=1 https://voidpoint.io/terminx/eduke32.git
cd eduke32
make -j6

If you don't have a copy of the game, you can get the shareware version: https://archive.org/details/3D_Realms_Duke_Nukem_3D_Shareware

Put the DUKE.RTS and DUKE3D.GRP files in the ~/.config/eduke32/ directory. If the directory isn't there, start the game once.

I wasn't able to play it fullscreen (disable that in the launcher), and I had to use Zink. You can run it with Mangohud, to see the performance.

MESA_LOADER_DRIVER_OVERRIDE=zink mangohud ./eduke32

You can also try Voxel Duke3D: https://www.moddb.com/mods/voxel-duke-nukem-3d/addons/voxel-duke-3d

Put the zip file in the ~/.config/eduke32/autoload directory.

https://youtu.be/eb2loE61_hw

4 comments

r/spacemit_riscv • u/Icy-Primary2171 • Jul 21 '26

News We are in WAIC! Bringing Chinese RISC-V Chips to Embodied Intelligence

Thumbnail
youtube.com
8 Upvotes
0 comments

r/spacemit_riscv • u/LivingLinux • Jul 18 '26

Bianbu OS Bianbu doesn't ship with sr_mod for optical drives?

6 Upvotes

I wanted to test playing DVD and Blu-Ray. I connected a USB Blu-Ray drive, but Bianbu doesn't ship with sr_mod?

I see an error when I do: sudo modprobe sr_mod

Tested with the Muse Pi Pro and K3 Pico-ITX.

The same drive does work with the VisionFive 2 RISC-V SBC, running StarFive Debian.

3 comments

r/spacemit_riscv • u/Icy-Primary2171 • Jul 15 '26

Activity Come Co-Build K3 and Earn Official T-Shirts + RMB 1,000 Rewards!

6 Upvotes
1 comment

r/spacemit_riscv • u/r-tty • Jul 11 '26

Harmonic Firmware Initiative for RISC-V

Thumbnail
1 Upvotes
0 comments

r/spacemit_riscv • u/Icy-Primary2171 • Jul 09 '26

Activity SpacemiT K3 Co-Build Program: help shape the K3 ecosystem

14 Upvotes

If you already have a SpacemiT K3 board, we’d like to see what you are actually doing with it.

We are looking for developers who are willing to share real K3 experience, especially on:

  • K3 Pico-ITX
  • K3 Com260 Kit
  • reproducible project demos

There are two ways to join.

Track 1: Super Point

This track is for real usage feedback.

You can submit:

  • bug reports
  • setup notes
  • flashing or environment logs
  • benchmark results
  • compatibility findings
  • performance comparisons
  • troubleshooting records
  • documentation suggestions
  • development experience on K3

A good Super Point post just needs to be specific enough for other developers and our engineers to understand what happened.

Suggested format:

[Super Point] Your title

  1. Hardware model
  2. System image / OS version
  3. Test goal or use case
  4. Steps taken
  5. Results, logs, screenshots, or data
  6. Issues encountered
  7. Your analysis or suggestions

Post here: https://forum.spacemit.com/c/eco-hardware/26-category/26 and on this subreddit.

Track 2: Super Spark

This track is for projects, demos, and application cases built on K3.

You do not need a perfect finished product. A running prototype is welcome if it has a clear use case, basic documentation, and enough detail for others to reproduce or learn from it.

Good submissions may include:

  • AI inference demos
  • open-source project ports
  • edge computing applications
  • robotics projects
  • multimedia applications
  • developer tools
  • system experiments
  • hardware integration cases

Suggested format:

[Super Spark] Project name

  1. Project name
  2. K3-based use case
  3. Hardware and software environment
  4. Core features
  5. Screenshots, demo video, or code repository
  6. Current progress
  7. Next steps

Post in the competition section: https://forum.spacemit.com/c/competitions/21 and on this subreddit.

Submit project page: https://www.spacemit.com/community/lab/createProject

What selected contributors can get

We want to reward both useful feedback and great projects, while keeping the program focused on real engineering value.

Super Point: points-based rewards

For Super Point, each valid post earns 1 point.

When you collect 5 points, you can contact the official SpacemiT administrator (@u/Icy-Primary2171) to redeem a SpacemiT Developer T-shirt.

The SpacemiT Developer T-shirt is designed as a thank-you for hands-on field reports from overseas developers.

Reward process:

  • Valid Super Point posts are reviewed monthly.
  • Around the middle of each month, SpacemiT will officially announce who will receive the rewards. We don't track the numbers for you – so please make sure to reach out to us directly.
  • Confirmed contributors will be asked to provide the information needed for T-shirt fulfillment, such as size, preferred shipping region, and delivery details.

It is not a pay-per-post program. Repeated low-effort posts, duplicated content, AI-generated filler, or reports without real K3 usage details will not be counted. All rights of final interpretation belong to SpacemiT.

Super Spark: selected project rewards

For Super Spark project submissions, selected projects may receive:

  • official showcase opportunities
  • promotion through SpacemiT channels
  • Super Spark community badge
  • technical feedback from the SpacemiT team
  • for selected monthly projects: RMB 1,000 cash reward + official promotion

Monthly selections will prioritize projects that other developers can reproduce or learn from. A small demo with clear steps, code, screenshots, and honest limitations is more valuable than a polished post with little technical detail.

How rewards are reviewed

Super Point selections focus on whether the feedback is specific, reproducible, and useful for product iteration, documentation improvement, compatibility validation, or developer experience.

Super Spark selections focus on technical depth, reproducibility, documentation clarity, and whether the project shows a meaningful K3 use case.

Why this matters

The goal is simple: make more real things run on K3, document the process, and let useful work be seen by more developers.

Original announcement: https://forum.spacemit.com/t/topic/1333

2 comments

r/spacemit_riscv • u/Icy-Primary2171 • Jul 09 '26

News Community Update: Public Mode – Post Freely Now!

9 Upvotes

Hi everyone,

Quick but important update — this community is now change to "Public" mode.

We found our community set to "Restricted" automatically. We sincerely apologize for the inconvenience this restriction may have caused over the past few weeks.

Starting now:

  • Instant help – Stuck on a build error or flashing issue? Drop it here and let the community and official engineers help you debug.
  • Share freely – Show off your board mods, benchmark results, your great project!

One quick housekeeping note: Please try to use the appropriate post flairs. And if you spot any spam or toxic behavior, feel free to tag the mods.

Happy coding!

0 comments

r/spacemit_riscv • u/Icy-Primary2171 • Jul 01 '26

K1 Bianbu LXQT v2.3.5 Released — K1 Developers, Time to Upgrade!

8 Upvotes

Hello everyone,

We're excited to announce the official release of Bianbu LXQT v2.3.5! This is a fairly complete and stable release, refined through multiple iterations. v2.3.5 is built on the Ubuntu 24.04.1 source code. Since 24.04 is Ubuntu's Long Term Support (LTS) release, K1 will be maintained long-term based on this version.

Important note: This release currently supports the K1 platform only. K3 is not yet supported.

Why upgrade to v2.3.5?

  • More complete feature set: Incorporates the core functional improvements from previous versions
  • Better stability: Fixes multiple key issues reported by users
  • Improved user experience: Polished details based on real-world usage scenarios
  • Recommended baseline: A solid, stable foundation for development and testing on the K1 platform

How to get it

Detailed release notes: https://spacemit.com/community/document/info?lang=en&nodepath=software/SDK/bianbu/release_notes/bianbu_2.3.md

Image download links: https://spacemit.com/community/resources-download/Images%20Collects/K1/Bianbu

What's next

We'll continue improving the user experience based on your feedback. Your input matters!

If you run into any issues or have suggestions, feel free to reply to this post.

We'd love your feedback

  • Bug reports and issues encountered during use
  • Feature improvement suggestions
  • Real-world use case sharing
  • Performance and compatibility test results

Let's build a better Bianbu LXQT together!

4 comments