u/Icy-Primary2171

RISC-V MEETS ROBOTICS--Unitree G1

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.

u/Icy-Primary2171 — 4 days ago
▲ 24 r/RISCV

Upstream Progress Updates --2026 July

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

reddit.com
u/Icy-Primary2171 — 14 days ago

RISC-V MEETS ROBOTICS--Linksee

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

u/Icy-Primary2171 — 14 days ago

RISC-V MEETS ROBOTICS--REACHY MINI

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.

u/Icy-Primary2171 — 14 days ago

Upstream Progress Updates --2026 July

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

reddit.com
u/Icy-Primary2171 — 17 days ago

RISC-V MEETS ROBOTICS

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

https://preview.redd.it/uiyjh9iz4hgh1.png?width=1200&format=png&auto=webp&s=3b64d9884019f360cdbad9da1afa165b4c244b12

reddit.com
u/Icy-Primary2171 — 21 days ago
▲ 22 r/spacemit_riscv+1 crossposts

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

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

u/Icy-Primary2171 — 1 month ago

Community Update: Public Mode – Post Freely Now!

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!

reddit.com
u/Icy-Primary2171 — 1 month ago

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

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!

https://preview.redd.it/gly9kcitnkah1.png?width=1800&format=png&auto=webp&s=f34badd1082a9fd36e7ec3c75a783c90ae31696e

reddit.com
u/Icy-Primary2171 — 2 months ago

Upstream Progress Updates --2026 June

Upstream progress of AI-related software stack

This month, SpacemiT Triton was updated to version 0.5.5, improving the K3 Triton operator IR codegen; the SpacemiT llama.cpp multimodal plugin supports more speech and vision models, and a new streaming 3D reconstruction model, LingBot-MAP, was added; the first patch was submitted to oneDNN, and all four PRs have been merged.

Linux Kernel Upstream

K1

merged:

review:

K3

merged:

review:

Board-level DTS / Device Support:

General Repair:

Upstream progress of basic tools

This month, riscv-elf-psabi was merged into the naming conventions of OpenMP declare simd vector functions, laying the foundation for ABI support for vectorized math libraries such as libmvec; binutils was merged into support for K1/K3 extended instructions.

LLVM

box64

riscv-gnu-toolchain

binutils

gcc

lmbench

chipstar

riscv-elf-psabi-doc

openocd

U-Boot、OpenSBI Upstream Progress

U-Boot

OpenSBI

u/Icy-Primary2171 — 2 months ago
▲ 38 r/spacemit_riscv+1 crossposts

K3 Shipping Update — New inventory arriving by end of June

Hi all,

We want to give a transparent update to everyone who has placed an order for the SpacemiT K3 through our ecosystem hardware partners.

Current stock status: Most configured variants across our five authorized partners (BPI, Firefly, Milk-V, Sipeed, and Ztcd) are sold out.

If you placed an order and haven't received a shipping notification, your reseller is waiting on new stock from us. Here's the timeline:

  • SpacemiT will have new inventory ready for resellers by the end of June
  • Partners will begin fulfilling outstanding orders as soon as they receive stock from us
  • For questions about your specific order status, please contact your reseller directly

We're genuinely grateful for the demand — all five channels selling out at the same time is a strong signal, and we're moving as fast as we can to restock. We expect to ship the next batch to all partners no later than June 30. Thank you for your patience.

For the full list of partner store links: https://www.reddit.com/r/spacemit_riscv/comments/1tcrx4o/

reddit.com
u/Icy-Primary2171 — 2 months ago

SpacemiT at Ubuntu Summit 26.04

We had a great time at Ubuntu Summit this year. Canonical and SpacemiT sat down together to talk about how we're working to accelerate open innovation for the RISC-V community.
Full talk: https://youtu.be/BaY2l17OBRQ?si=TyNv_frpUDrAsbvY
Summit highlights: https://www.youtube.com/watch?v=tErujp4RAWQ

image download link: https://github.com/spacemit-com/K3-Ubuntu-Images

https://preview.redd.it/6rz42w60lt4h1.png?width=3161&format=png&auto=webp&s=8588412c6ce3480afe7d37904dafc5f3b89a2dd0

reddit.com
u/Icy-Primary2171 — 3 months ago

Upstream Progress Updates --2026 May

Here's a roundup of 2026 May's upstream contributions from the SpacemiT. Lots of activity across Linux kernel, LLVM, U-Boot, and several community projects.

Linux Kernel Upstream

merged:

patch:

Board-level DTS / Device support:

Bug fix:

Triton Upstream

Major updates:

SpacemiT Tritonoperator library merged into FlagOS:

https://github.com/flagos-ai/FlagGems/pull/2527 ,merged

Monthly update for the SpacemiT Triton compiler:

https://github.com/spacemit-com/spine-triton/releases/tag/0.5.4

  • Fixed lowering-related issues, including ptr dialect migration, bitcast type bridging, memory space propagation, and scan fixes.
  • Added mapping from 0xF000 arch_id to spacemit-a100 in the backend
  • Added native RISC-V build script for spine-triton
  • Removed special path for f16 matmul
  • Added lib directory and updated variables.env
  • Updated spine-mlir to version 0.5.4 and completed related dependency updates
  • Fixed speir extract root issue in CI

LLVM Upstream

merged:

U-Boot Upstream

patch:

Else

box64:

riscv-gnu-toolchain:

binutils:

reddit.com
u/Icy-Primary2171 — 3 months ago
▲ 67 r/spacemit_riscv+1 crossposts

A note from SpacemiT on K3 community feedback

Since the K3 launched, we've been reading every post, comment, and benchmark thread. Thank you. Here's our honest response to the main concerns:

1. Price

We hear you. The K3 is not cheap, and the main reason is memory cost. We're not happy about it either.

2. Power consumption and process node

Fair criticism. We're a startup with limited R&D budget, which means we can't access the leading-edge process nodes that mobile ARM SoCs use. That directly affects power efficiency. We know it, and it's something we're working toward as we grow.

3. CPU core performance

We've received your feedback loud and clear. Our next-generation cores are already in development:

  • X200 (3rd-gen) — targeted for the K5, planned for 2027
  • X300 (4th-gen) — targeted for the K7, planned for 2028

We're not standing still.

We're a team that genuinely believes in RISC-V — not as a business strategy, but as a conviction. We read your posts, we take the criticism seriously, and we're building toward something better.
Huge thanks to all of you in our developer community — for your trust, your feedback, and your passion. We will never stop improving, and we'll always keep listening.

reddit.com
u/Icy-Primary2171 — 3 months ago
▲ 46 r/spacemit_riscv+1 crossposts

We partnered with BayLibre to bring Android 16 to RISC-V — fully open source, running on SpacemiT K1

We're excited to share that SpacemiT has partnered with BayLibre to successfully run Android 16 on the SpacemiT K1 SoC (RISC-V RVA22 + RVV 1.0).

What was achieved:

  • Android kernel 6.19 running with K1 vendor kernel 6.6 drivers
  • Vulkan support enabled via Imagination GPU in mesa3d
  • Generic HAL Utilization: We leveraged Baylibre’s Android generic Hardware Abstraction Layer (HAL) for essential functions, including thermal management, USB, and audio.
  • Full Android 16 device config built for SpacemiT RISC-V. Boot time under 2 minutes on BananaPi F3 (K1 platform)

The entire project was built on 100% open-source software — AOSP, mainline kernel, no NDAs, no proprietary blobs. Anyone in the community can rebuild the image from scratch.

Source code: https://github.com/BayLibre/android_manifest
Full write-up: https://baylibre.com/blog/baylibre-partners-with-spacemit-to-bring-android-16-to-risc-v/

We welcome the community to test, contribute, and help push RISC-V + Android forward.

Questions welcome!

u/Icy-Primary2171 — 3 months ago