r/spacemit_riscv

Image 1 — K3 is here
Image 2 — K3 is here
🔥 Hot ▲ 115 r/spacemit_riscv+1 crossposts

K3 is here

The K3 RISC-V AI CPU from SpacemiT has officially entered mass production, marking a full-cycle transition from R&D to large-scale commercial deployment. It delivers a native compute foundation ready for high-end applications such as AI PCs and intelligent robots.

As the world’s first RISC-V chip compliant with the RVA23 specification, the K3 leverages homogeneous fusion computing architecture, integrating 8 high-performance compute cores and 8 ultra-wide parallel AI cores. It delivers 130K DMIPS of general-purpose computing power and 60 TOPS of AI performance—enabling local inference for 30B–80B parameter LLMs. Its performance matches mainstream desktop CPUs, making it ideal for AI PCs, robotics, and other advanced use cases.

The K3 has completed full adaptation for humanoid robot motion control and is now building an integrated digital employee solution tailored for Agent OS. With cloud-edge synergy, it reduces token consumption by over 40%, ensures data security via on-device intelligent desensitization, and offers out-of-the-box readiness—accelerating deployment of turnkey digital employee systems. SpacemiT continues to expand RISC-V boundaries and co-build an open, win-win intelligent computing ecosystem.

u/Icy-Primary2171 — 3 days ago
🔥 Hot ▲ 62 r/spacemit_riscv+2 crossposts

T2 on Spacemit K3, RISCV: Mesa3D "imagination" driver running on PowerVR BXM-4-64

Working together with DeepComputing on the Framework 13 (RISCV-64, Spacemit K3 / ROMA III), we’ve been working on bringing up a fully open-source Linux stack.

Good news: we now have the open-source Mesa3D Imagination PowerVR driver running — including Vulkan and Zink for GLES This is a pretty big milestone for the historically under-supported PowerVR (tile-based deferred rendering) GPUs.

Kernel-side was straightforward. Mesa userspace took significantly more effort — lots of debugging and trial-and-error.

https://preview.redd.it/v2ima3pbfbxg1.jpg?width=1919&format=pjpg&auto=webp&s=02309329c031961c90e3c52fc76e51d836ec4ebd

https://preview.redd.it/ay8ncnicfbxg1.jpg?width=1920&format=pjpg&auto=webp&s=2eac837ca62c39886a94232544409f4684efacec

https://preview.redd.it/j6tn3avdfbxg1.jpg?width=2813&format=pjpg&auto=webp&s=7d8d8e9a4218abd01d32a7b9d390c868bb00d065

https://preview.redd.it/vgdrun1ffbxg1.jpg?width=1265&format=pjpg&auto=webp&s=75b0070f35e0a617d7dea2bd9b631b8a7a651d59

Stil WIP:

  • GPU frequency scaling
  • general stability/perf tuning

More updates soon.

https://t2linux.com

reddit.com
u/0xRENE — 3 days ago
▲ 34 r/spacemit_riscv+1 crossposts

mail from SpacemiT: "SpacemiT K3 SBC is Coming !"

I got the mail below from SpacemiT:

Hello,

We're excited to bring some good news: SpacemiT K3 SBC is about to be launched! As an old friend of us, we sincerely invite you to participate in the first review of the K3 SBC.

The K3 chip offers significant performance improvements over the K1. We're very much looking forward to the great review you'll create based on the features of these two SBCs. If you're willing to publish more than one articles or additional videos, we would be extremely grateful.

We will be releasing two SBC models featuring the K3 CPU——The Pico-ITX and the CoM260 kit, and we will send you the Pico‑ITX unit, covering both shipping and customs duties.

Pico-ITX – designed for AI Computer. We will send you a physical board. We've summarized some highlights to help you get to know it better (see attachment).

CoM260 Kit – designed for AI Robot. Due to limited initial production quantities, we regret that we were unable to secure a physical sample of this board for your review. However, we would greatly appreciate it if you could also showcase the CoM260 kit's availability and specifications in your article(or video). This development board is already compatible with embodied AI robots, and we've prepared some supplementary materials in see attachment that we hope will inspire your content.

K3 CPU https://www.spacemit.com/community/document/info?lang=en&nodepath=hardware/key_stone/k3/k3_docs/root_overview.md

K3 Pico-TIX https://www.spacemit.com/community/document/info?lang=en&nodepath=hardware/eco/k3_pico/root_overview.md

K3 CoM260kit https://www.spacemit.com/community/document/info?lang=en&nodepath=hardware/eco/k3_com260/root_overview.md

reddit.com
u/superkoning — 4 days ago
▲ 17 r/spacemit_riscv+1 crossposts

SpacemiT K3 RISC-V OpenCL clpeak Pre-Release Test

Disclosure: SpacemiT has reviewed the video and promised me a free SpacemiT K3 board.

I have remote access to a SpacemiT K3 board.

clpeak is a simple benchmark for OpenCL. The PowerVR BXM-4-64 iGPU in the SpacemiT K3 is a lot faster than the BXE-2-32 in the SpacemiT K1, but I guess that is no surprise. I tested with the vendor driver (binary blob).

As the BXM-4-64 supports Dynamic Voltage and Frequency Scaling, clpeak reports the clock frequency before it starts the benchmark. The BXM-4-64 starts at 409MHz and goes up to 819MHz.

youtu.be/3-meoBGUREw

bianbu@k3:~$ clpeak --version

clpeak version: 1.1.5

bianbu@k3:~$ clpeak

Platform: PowerVR

Device: PowerVR B-Series BXM-4-64

Driver version : 24.2@6603887 (Linux unknown)

Compute units : 1

Clock frequency : 409 MHz

Global memory bandwidth (GBPS)

float : 1.77

float2 : 3.22

float4 : 9.06

float8 : 4.17

float16 : 6.34

Single-precision compute (GFLOPS)

float : 26.00

float2 : 50.62

float4 : 48.73

float8 : 46.75

float16 : 38.57

Half-precision compute (GFLOPS)

half : 25.91

half2 : 50.74

half4 : 49.04

half8 : 47.64

half16 : 38.64

No double precision support! Skipped

Integer compute (GIOPS)

int : 25.84

int2 : 25.67

int4 : 25.60

int8 : 25.37

int16 : 24.80

Integer compute Fast 24bit (GIOPS)

int : 25.84

int2 : 25.66

int4 : 25.60

int8 : 25.37

int16 : 24.79

Integer char (8bit) compute (GIOPS)

char : 25.84

char2 : 25.77

char4 : 25.66

char8 : 25.59

char16 : 25.40

Integer short (16bit) compute (GIOPS)

short : 25.83

short2 : 25.77

short4 : 25.70

short8 : 25.44

short16 : 24.80

Transfer bandwidth (GBPS)

enqueueWriteBuffer : 6.45

enqueueReadBuffer : 6.64

enqueueWriteBuffer non-blocking : 6.52

enqueueReadBuffer non-blocking : 6.64

enqueueMapBuffer(for read) : 8736.71

memcpy from mapped ptr : 7.01

enqueueUnmap(after write) : 47881.46

memcpy to mapped ptr : 6.68

Kernel launch latency : 33.69 us

And here are the results for the SpacemiT K1, with an older version of clpeak.

clpeak --version

clpeak version: 1.1.2

➜ ~ clpeak

Platform: PowerVR

Device: PowerVR B-Series BXE-2-32

Driver version : 24.2@6603887 (Linux unknown)

Compute units : 1

Clock frequency : 614 MHz

Global memory bandwidth (GBPS)

float : 1.32

float2 : 2.40

float4 : 6.15

float8 : 3.13

float16 : 4.68

Single-precision compute (GFLOPS)

float : 9.76

float2 : 18.88

float4 : 18.51

float8 : 17.38

float16 : 14.80

Half-precision compute (GFLOPS)

half : 9.72

half2 : 18.94

half4 : 18.75

half8 : 17.92

half16 : 14.83

No double precision support! Skipped

Integer compute (GIOPS)

int : 9.69

int2 : 9.64

int4 : 9.60

int8 : 9.49

int16 : 9.42

Integer compute Fast 24bit (GIOPS)

int : 9.69

int2 : 9.64

int4 : 9.60

int8 : 9.50

int16 : 9.40

Transfer bandwidth (GBPS)

enqueueWriteBuffer : 2.56

enqueueReadBuffer : 2.43

enqueueWriteBuffer non-blocking : 2.56

enqueueReadBuffer non-blocking : 2.43

enqueueMapBuffer(for read) : 5141.34

memcpy from mapped ptr : 2.43

enqueueUnmap(after write) : 8350.51

memcpy to mapped ptr : 2.55

Kernel launch latency : 69.23 us

u/LivingLinux — 5 days ago

So I guess we're now on a 1 week countdown till K3 release?

Assuming schedules have held?

The chip and product docs are still apparently in progress.

reddit.com
u/TJSnider1984 — 8 days ago

QRV (QNX ported to RISC-V): Spacemit K3 demo? Should be possible!

Dear Spacemit! If you are reading this post, and if you would like to see r/QRV_OS running on your board -- please respond. The K3 board has a chance to become the first ultra-modern RISC-V system on which the QNX-derived OS is running ;)

Currently QRV runs on Unmatched (and under QEMU of course). Kernel and user-space Unix-like environment is up and running.

reddit.com
u/r-tty — 5 days ago