r/RISCV • • 22h ago

Information RISC-V Vector in a Nutshell

Thumbnail
fprox.substack.com
18 Upvotes

r/RISCV • • 22h ago

Standards IOPMP 0.85 Released

Thumbnail
github.com
7 Upvotes

r/RISCV • • 23h ago Bravo

I made a thing! Bootable Haiku SD Card image for OrangePi RV

Thumbnail
gallery
15 Upvotes

https://github.com/spacemonkeyboom/Beacon-OS

Haiku does not take AI assisted contributions so I forked it to make my own side project. I am having Claude document what it learned so other projects can benefit from my research. Everything is public on GitHub


r/RISCV • • 23h ago

Information XiangShan Tapeout History

Thumbnail docs.xiangshan.cc
9 Upvotes

No new information but a collection of XiangShan tapeout floorplans and photos.

Congrats to the XiangShan group and looking forward to seeing next ones!


r/RISCV • • 1d ago

Anyone got both WiFi and GPU-acceleration working on a OrangePi RV2?

4 Upvotes

Had my OrangePi RV2 since february. If I run the official Ubuntu-image I get working WiFi but no GPU-acceleration (OpenGL/Vulkan). If I install BianbuOS I get working Vulkan, but no WiFi. I am checking if there is any updates regularly. Has anyone been able to get everything working on it?


r/RISCV • • 1d ago

Can I purchase a R5 device in Hong Kong/Shenzhen/Guangzhou from a physical store?

2 Upvotes

r/RISCV • • 1d ago

Help wanted Riscv Profiler

10 Upvotes

Hi everyone,

I’m currently working on a profiling tool targeting RISC-V and could use some guidance from folks who have experience with performance monitoring or low-level tooling on this architecture.


r/RISCV • • 1d ago

Software Windows 11 clone, soon for riscv64

Thumbnail
phoronix.com
40 Upvotes

r/RISCV • • 2d ago

RVV benchmark QingKe3V (CH32V407), MCU with VLEN=64 integer RVV

Thumbnail camel-cdr.github.io
7 Upvotes

r/RISCV • • 3d ago

I made a thing! StarFive VisionFive 2 (Lite) - LibreELEC and Kodi

14 Upvotes

Some days ago I saw this post on Reddit: LibreELEC and Kodi running on the SpacemiT K1. LibreELEC on RISC-V! I have a Milk-V Jupiter K1, so I had to try it.

It did not work out of the box on my Jupiter. The build failed in some places, the kernel hung in the HDMI audio driver and Kodi was falling back to software rendering. With some fixes it worked: Kodi with GPU acceleration, HDMI audio, 4K video and updates. I sent the fixes back as a pull request, and it was merged.

Then I thought: if this can run on a Jupiter K1, it can also run on a StarFive VisionFive 2 (Lite). They have almost the same GPU (Imagination PowerVR), and StarFive has a vendor kernel with a hardware video decoder.

So… can it? Yes!

More information on my blog: https://opvolger.github.io/posts/starfive-visionfive-2/2026-11-18-libreelec/

There is a (test) release with an image you can flash right away: LibreELEC 13.0-devel for StarFive VisionFive 2 / 2 Lite.


r/RISCV • • 3d ago

Software Hartbox boots Alpine Linux on an iPhone 17e with RV64GC emulation

22 Upvotes

Hello everyone, I released Hartbox, a full-system RISC-V emulator that boots alpine linux locally on an iphone. The rust interpreter emulates an a riscv64gc machine and boots the alpine kernel into an interactive terminal. It runs without JIT and is quite fast.

I tested it on an iPhone 17e running iOS 26.6, it ran quite qwell, about 1000 mips with a lot of crazy optimizations. There’s also an rssh binary for connecting to the guest from a Mac if you want to remote work. The same emulator builds as a command-line tool if you want to try it on your computer

I have attached a demo of me running it on iPhone.

- [GitHub source and build instructions](https://github.com/u6420771547-hash/hartbox)

- [Download Hartbox.ipa](https://github.com/u6420771547-hash/hartbox/releases/download/v1.0.0/Hartbox.ipa)

The IPA is unsigned, so it needs signing for your device before installation. The README walks through running it from Xcode.

I’d love to know what is your experience when you try this. If you get it running, I’d also be interested in your iPhone model, iOS version, and how first boot went. It is recommended to install via altstore or sidestore

if this is helpful, it will be great if you leave a star in the GitHub repo so it reaches more people


r/RISCV • • 4d ago

Software Milk-V Mars and Haiku OS

Post image
117 Upvotes

For a few weeks I have been porting Haiku, and its fork RenkuOS, to the Milk-V Mars. It is a RISC-V board the size of a Raspberry Pi, built around the StarFive JH7110 SoC with 4 SiFive U74 cores at 1.5 GHz; mine has 4 GB of RAM. I wanted to share the progress, because the board finally boots to the desktop and is usable.


r/RISCV • • 4d ago

Discussion [Project Idea] Building a modern, wide out-of-order RISC-V core (RV64IMAFDC + RVV) with a pre-decoder and multi-core cache coherence from scratch. Would anyone read this?

27 Upvotes

Most open-source CPU tutorials stop at a toy 5-stage in-order RV32I pipeline. They teach you how to build a calculator, not a processor. Real industrial hardware is a massive parallel execution engine that deals with variable-length instructions, out-of-order scheduling, vector extensions (RVV), and multi-core cache coherence.

I’m planning to write a deep, no-bullshit guide that takes you from a blank SystemVerilog file all the way to a multi-core RV64 system with a pre-decoder, instruction stream buffers, execution units, and actual cache coherence. No hand-waving, just real RTL, Verilator testbenches, and hardware design pain.

Before I spend months writing this: would people actually be interested in it?


r/RISCV • • 4d ago

Discussion Kunminghu V3 hits mind-blowing 24.138 SPECint06/GHz in "Ideal" (target) build yesterday, higher than score of 22 from Alibaba's XAUNTIE C950 (currently fastest RISCV CPU deployed), and 23 from AMD's Zen 5 based Epyc processors.

31 Upvotes

Damn this thing has been cooked well by XiangShan project.

AMD's Zen 6 processors have just launched and have not been benchmarked yet, but are expected to be around 24.5-25. Pretty sure KMH V3 can overtake that number within next few months before release.

With SPECint06/GHz > 24 almost guarantees EVERY cloud provider will use this design white-labelled as their own Graviton/Cobalt/etc servers within months of launch.

Other than target, KMH V3 scores 21.9 on nightly branch, will slowly catch up to target score in next few months.


r/RISCV • • 4d ago

I made a thing! We have received FramePico2 Expansion Cards based on RP2354 MCU, soon on Crowd Supply!

Thumbnail
gallery
33 Upvotes

r/RISCV • • 5d ago

Discussion How does RISC-V work exactly?

39 Upvotes

Im amazed to see the potential of RISC-V in the next years

Probably a dumb question, but do most RISC-V CPUs support interoperability between each other? Like build once run everywhere? Because I see multiple companies doing different CPUs, and each one of them going a different way


r/RISCV • • 6d ago

Half-Life 2 on the onboard GPU of a RISC-V board (VisionFive 2, PowerVR)

24 Upvotes

HDMI output with GPU acceleration on the StarFive VisionFive 2 (JH7110), running Debian 13 (Trixie).

On my StarFive VisionFive 2 I always used an AMD graphics card, see my posts about Debian Trixie with an AMDGPU and Half-Life 1. The same as in my last post on the Milk-V Jupiter, where Half-Life 2 runs native on RISC-V with an AMD Radeon R9 290.

After that post I got a question: “Can you also run it on the onboard GPU of the Jupiter (SpacemiT K1)?”. Good question! So I started searching, but for the GPU of the K1 I could find almost nothing upstream. Only a few pull requests, nothing that I could use.

But I knew the JH7110 (the SoC of the VisionFive 2) was further along. The display driver is on the mailing list, and the GPU (PowerVR BXE-4-32) already has a driver in Mesa. So let’s try that board first!

It was possible, see all the details on this project on https://opvolger.github.io/

Here the game-play: https://youtu.be/PihJHGE2QRw


r/RISCV • • 6d ago

How Tenstorrent just bagged a massive $1.5B Series E to take on Nvidia with open RISC-V

Post image
42 Upvotes

r/RISCV • • 6d ago

Information OpenXiangShan/XiangShan: Open-source high-performance RISC-V processor

Thumbnail
github.com
60 Upvotes

Kunminghu-V3 (kunminghu-v3 branch)

Capabilities:

ISA & Privileged Support
RV64GCB + major RVA23-profile extensions (primary focus is functional correctness of RVA23)

RVV 1.0 (vector unit fully reworked; VLEN typically 128-bit × 2 in documented configs)

Unaligned accesses (Zicclsm) with 16B atomicity guarantees (Zama16b) in cacheable space

Atomic extensions: RVA + Zacas

Cache-block operations: Zicbom, Zicboz, Zicbop (software prefetch)

Virtualization (RVH) with two-stage address translation

Page-based memory attributes (Svpbmt), contiguous pages (Svnapot)

Pointer masking (Supm / Ssnpm / Sspm)

Sv39 / Sv48 (and x4 variants), up to 48-bit physical addresses

AIA 1.0 (CSR + IMSIC), Sstc, NMI support

Debug Module 0.13, HPM, E-trace (partial)

Frontend
High-bandwidth fetch: up to 32 instructions / cycle, dual-fetch capable

Advanced BPU with multi-level predictors (uBTB, MainBTB / VictimBTB, TAGE, ITTAGE, SC, RAS, etc.)

Can predict up to 8 branches per cycle

Instruction prefetch (FDIP-style + enhanced iprefetch work)

ICache: configurable (commonly 64 KB), 4-way, supports two consecutive lines, way-lookup, ECC/Parity, MSHR

Backend / Out-of-Order Core
Decode / Rename / Dispatch width: commonly 6–8

Issue width increased to 8 ports (vs earlier 6)

ROB: 160 entries (recently raised), with hybrid compression (CROB) — up to ~6 uops per entry

Retire up to 8 instructions per cycle

Physical register files (typical DefaultConfig-scale numbers):
Integer: 224 entries

Floating-point: 192 entries

Vector: 128 entries

Move elimination + instruction fusion

Rename snapshots + Rename Buffer (RAB)

Unified VFMac functional unit (vector FP add/mul/FMA)

Vector instructions can use scalar FP sources

Integer, FP, and vector execution pipelines with early wakeup / bypass

Memory Subsystem
LSU: up to 3 integer loads + 2 integer stores + vector memory uops per cycle; non-blocking DCache

DCache: up to 64 KB, 8-way, VIPT, ECC, multi-port

L2: unified, inclusive (w.r.t. DCache), configurable (commonly 1–2 MB), banked, ECC; supports CHI (Issue B / E.b subsets) and TileLink

Custom L1–L2 fabric with miss tracking and speculative buffering

SoftTLB / softPTW simulation path for two-stage translation evaluation

Multiple hardware prefetchers (Berti, CDP-style, matrix-guided, stream, etc.)

StoreQueue / LoadQueueReplay with advanced forwarding, dependency tracking, and fast wakeup

PMP / PMA (default 16 entries each)

System / Multi-core Oriented Features
Designed toward high multi-core density (target 32–64 cores per die + multi-die support)

On-core AIA IMSIC, Timer (Sstc), Debug

DiffTest / co-simulation infrastructure, TopDown performance counters, extensive debug/trace hooks

Configurable for both TileLink and CHI interconnects

Notable Recent Additions (last few months)
VictimBTB

Hybrid Compressed ROB (CROB)

Unified VFMac + scalar-FP sources for vector

Set-banked CoupledL2 + CustomL1L2Fabric

ZhuJiang NoC integration path

Expanded ROB size, improved RAS / BPU training, many vector and memory correctness/performance refinements.

If anyone follows this project can you point out the significance of this open source project or what have you learned from it?


r/RISCV • • 6d ago

Hardware LibreCore RISC-V achieves ~50x+ hardware optimization in GPT/AI workloads

Thumbnail cimons.com
27 Upvotes

r/RISCV • • 6d ago

Crowdfunding: Purism – Librem 5 v2 – RISC-V SpacemiT K1 Phone

Thumbnail puri.sm
18 Upvotes

I'm not affiliated with Purism, and you have to decide for yourself if you want to take the risk.

Do note that it is possible to get Android working on the K1: https://www.reddit.com/r/spacemit_riscv/comments/1tgacnw/we_partnered_with_baylibre_to_bring_android_16_to/

And Purism points out the following risks:

RISC-V is not yet drop-in and boot-up ready for PureOS. This is going to take invention, innovation, and investment. These are major reasons why we need to run a crowdfunding campaign to prove interest to plan and execute all the necessary parts to deliver a fully functioning device.

Graphics

The graphics stack is able to display to a screen, but it needs complete 3D support and optimization to be a usable and responsive mobile phone.

Peripherals

Most peripherals are not supported in mainline Linux. We must adapt and port drivers from the vendor’s 6.6 kernel.

ARM64 compatibility

We must be able to execute ARM64 code efficiently to support Flathub and Android apps. ARM64 emulation for RISC-V exists, but needs optimization.

Browser performance

Firefox supports RISC-V, including in the JavaScript/WASM compiler, but support is relatively recent and may require more optimization.

Power management

RISC-V power management is relatively recent and might require work throughout the stack to reach our goals.


r/RISCV • • 6d ago

Information RISC-V Matrix Extensions - by FPRox

Thumbnail
fprox.substack.com
33 Upvotes

r/RISCV • • 7d ago

I made a thing! blaris: Windowless random-access LZSS in C (~110 B total RAM, <800 B Flash) for microcontrollers

Thumbnail reddit.com
5 Upvotes

r/RISCV • • 7d ago

I made a thing! Fursoy Slice-1: Open-source 2-wide out-of-order RV64IMAFDV core in SystemVerilog (Linux 6.6, 500 MHz Nangate 45nm STA)

18 Upvotes

I've been working on an open-source 64-bit out-of-order RISC-V core (RV64IMAFDV + Zba/Zbb/Zicsr/Zifencei) in SystemVerilog, along with a minimal SoC (5-master crossbar, CLINT, PLIC, 16550 UART, and custom SBI v2.0 firmware).

Repo: https://github.com/FURSOY/fursoy-cpu

Main specs:

- 2-wide fetch/decode/rename/retire, 128-entry ROB, 160-entry integer PRF, 8 branch checkpoints for single-cycle RAT rollback, separate Int/Mem/FP/Vec issue queues.

- Dual-port Sv39 DTLB (64-entry 4-way Tree-PLRU + 8-entry 2 MiB/1 GiB superpage CAM), ITLB, and a 16 KiB 8-bank non-blocking L1D. The hardware PTW snoops dirty L1D sets non-destructively so page-table updates are visible without flushing on every walk, paired with a store-queue drain on SFENCE.VMA.

- Boots mainline Linux 6.6.50 + BusyBox in Verilator (~89.8M cycles, ~76.2M retired instructions, 2,255 page faults) while checking an 8-bucket single-owner CPI conservation invariant every cycle with 0 cycle leakage.

- Synthesizing the 8 main core blocks standalone with sv2v + Yosys + OpenSTA on Nangate 45nm (SRAMs/PRFs black-boxed, pre-P&R) meets 500 MHz across all 8 blocks at ~219 kGE, after rebuilding the ALU and branch unit as Kogge-Stone prefix trees.

I used AI tools for RTL iteration and verification scaffolding while handling the microarchitecture, timing closure, and debugging myself. The nastiest late bug was a Linux boot livelock around 90M cycles—per Priv Spec §3.1.9, CSR RMW instructions on `mip` have to read the software-writable `mip_q[9]` bit rather than the live `irq_seip_i` wire, otherwise `SEIP` gets permanently latched when SBI clears `STIP` while a PLIC IRQ is active.

Curious how others handling Sv39 in open-source cores deal with page-table walk coherency—do you prefer non-destructive L1D snooping like this or forcing a clean/drain path? Also open to thoughts on whether an inclusive L2 or jumping straight to dual-core coherency makes more sense next.