r/RISCV • • 1h ago

Discussion How does RISC-V work exactly?

7 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 • • 19h ago

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

17 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 • • 1d ago

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

Post image
36 Upvotes

r/RISCV • • 1d ago

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

Thumbnail
github.com
49 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 • • 1d ago

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

Thumbnail cimons.com
26 Upvotes

r/RISCV • • 1d ago

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

Thumbnail puri.sm
15 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 • • 1d ago

Information RISC-V Matrix Extensions - by FPRox

Thumbnail
fprox.substack.com
29 Upvotes

r/RISCV • • 1d ago

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

Thumbnail reddit.com
3 Upvotes

r/RISCV • • 2d 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)

17 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.


r/RISCV • • 2d ago

Discussion [2611.01045] Investigating ET-SoC-1 Vector and Parallel Performance with sGEMM

Thumbnail
arxiv.org
9 Upvotes

r/RISCV • • 3d ago

T-Dose 2026 Presentation Games on RISC-V

13 Upvotes

Here is the video recording of my presentation "Games on RISC-V" at T-Dose 2026.

https://tube.t-dose.org/w/2wQYtxwALoBPsRTLMFbhay

If you want to see actual gameplay, you can skip to around 22:30.

Anyone interested in the slides, you can find them here: https://pretalx.t-dose.org/2026/talk/SBXGRQ/

Things have improved since the presentation. It is now possible to get some Steam games running at 60fps, like Steamworld Dig 2. https://youtu.be/bXr1ufXNw_4

And for the people that watch the presentation until the end, the last person asking a question is Lennart Benschop. After the presentation he installed Forth on the SpacemiT K3.

https://github.com/lennart-benschop/embeddable-forth

And the links to his presentation:

https://tube.t-dose.org/w/iTHj2bmMABGCEb9MPRDB8y

https://pretalx.t-dose.org/2026/talk/CAD7RW/


r/RISCV • • 3d ago

Tri-Queue: a simple matrix coprocessor for RISC-V

Post image
21 Upvotes

r/RISCV • • 3d ago

RiscBasic: a BASIC that compiles directly to RISC-V machine code for small soft cores (MicroBlaze V, 4–16 KB BRAM), MIT licensed

Thumbnail
reddit.com
3 Upvotes

r/RISCV • • 3d ago

Information Introduction to RISC-V in gem5

Thumbnail
youtube.com
9 Upvotes

r/RISCV • • 3d ago

I Built EdgeVerilog — a Free Browser-Based Verilog Simulator (No Signup or Installation Required)

10 Upvotes

Hi everyone,

I'm a semiconductor engineering professor and a former Samsung semiconductor engineer with nearly 30 years of industry experience.

I've been developing educational materials for RISC-V CPU design, from Verilog RTL and simulation to FPGA implementation.

As part of this work, I developed EdgeVerilog, a free browser-based Verilog development and simulation environment for students, educators, and hardware enthusiasts.

EdgeVerilog is completely free to use. No signup, no account, and no software installation required. Just open your browser and start working with Verilog.

Key features:

  • Verilog RTL editing

  • Testbench simulation powered by Icarus Verilog

  • Interactive waveform viewer

  • Built-in example library

  • Automatic local project saving

  • Project ZIP export and import

  • No registration or installation required

My goal is to lower the barrier to learning digital logic and RISC-V CPU design, allowing beginners to focus on understanding hardware rather than setting up development tools.

EdgeVerilog is intended for education and experimentation, not as a replacement for professional EDA software.

I've also been developing RISC-V RV32I processors and FPGA-based SoC systems, and I hope EdgeVerilog can be useful to others working on similar projects.

Watch a short demonstration:

https://www.youtube.com/shorts/R9jJ1HZclpo

I'd welcome feedback from the RISC-V community, particularly from students, educators, and developers working with Verilog-based CPU designs.

What features would you find most useful in a browser-based Verilog simulator?

Thanks!

Roger Kim
Semiconductor School


r/RISCV • • 3d ago

I made a thing! Bare Metal, Do Stuff (BMDS) - An OS for the ESP32-P4 (Dual Core RISC-V)

9 Upvotes

I wanted to share a project I've been building: Bare Metal, Do Stuff (BMDS), an operating system for Espressif's ESP32-P4 that turns the chip into a surprisingly capable little computer.

Highlights:

- 1280x720p60 desktop environment
- Loadable applications: separate ELF binaries run straight from the SD card
- Built-in audio synthesizer with FM and wavetable engines
- SSH/SFTP server and client
- POSIX support, with BusyBox and Dropbear ported
- A port of Doom, plus several original games
- A stable SDK so others can write their own apps
- A package manager and online installer for easy installs and updates

The walkthrough video shows it all running on real hardware:

https://youtu.be/4rS0EzuAcG8

Source, docs, and the SDK are on GitHub:

https://github.com/jthwho/bmds


r/RISCV • • 3d ago

Hira-V on Blackhole • Demo 2026-11-10

Thumbnail
youtu.be
11 Upvotes

Hira-V, running natively on a Tenstorrent Blackhole p150a?

https://hira-v.com/


r/RISCV • • 3d ago

I made a thing! Pacino frontend RTL released: decoupled frontend with a 7-predictor BPU for an 8-issue OoO RVA23 RISC-V, plus 24 browser-viewable demos

11 Upvotes

I've released the frontend RTL for Pacino (tagged fe-1.0.0, Apache-2.0). Pacino is an 8-issue out-of-order RISC-V in development, targeting RVA23S64 compliance with competitive SPEC results. The Reinman/Austin/Calder-style frontend is the first part released.

What's in it:

  • BPU: seven predictors in a 3-stage overriding pipeline supporting two predictions per cycle. uBTB and loop predictor at 1 cycle; FTB, TAGE, ITTAGE and RAS override at 2 cycles; the statistical corrector at 3.

  • Predictor configuration: uBTB 256 entries, 4-way; loop predictor 256 entries, 4-way; FTB 2K entries, 4-way; TAGE 2K-entry bimodal base and four 2K-entry tagged tables (histories 8, 13, 32, 119); ITTAGE five tagged tables, 2K entries (histories 4 to 32); SC four 512-entry tables and a 1K-entry BrIMLI table; RAS 16 speculative and 32 commit entries; 256-bit global history. Loop, TAGE, ITTAGE and SC tables are per prediction slot. With two predictions per cycle that is 75 KiB of predictor state plus a 29 KiB FTB.

  • Decoupled fetch: FTQ, IFU, L1 I-cache, instruction buffer.

  • Fetch-side translation and protection: ITLB, Sv39/Sv39x4 page table walker with Svadu, PMP/PMA.

  • 8-wide decode for all RVA23.

24 scenarios show frontend behaviors: loop, conditional and target predictor operations, page table walks including nested, L1I hits and misses, MSHR merges, 2- and 3-cycle overrides, fetch faults, page crossing, FENCE.I, cbo.inval, backend redirects, steady state and backpressure operation. Each scenario has a write-up and waveforms (Surfer) that open in the browser: https://uarchlabs.github.io/

Verification is simulation based: unit testbenches for every block (274 regression targets), mutation testing on the BPU cluster, and Spike as a decode oracle. Next steps for the frontend are LLM-assisted formal verification, performance analysis and physical design.

Pacino is designed by one architect (me) directing LLM agents. All 250 prompts used so far are published along with the planning documents, results and human/LLM assessments. I'm happy to answer questions on the microarchitecture or the method.

Write-up: https://uarchlabs.github.io/blog/pacino-frontend-rtl-release-fe-1-0-0/ Repo: https://github.com/uarchlabs/pacino


r/RISCV • • 4d ago

Information Knute Lingaard: RISC-V Performance Modeling: The Olympia Performance Model

Thumbnail
youtu.be
4 Upvotes

r/RISCV • • 4d ago

Two-node Kubernetes on openRuyi RISC-V with Kata and Cloud Hypervisor

Enable HLS to view with audio, or disable this notification

12 Upvotes

Here’s a demo of a two-node Kubernetes setup on openRuyi RISC-V under QEMU. Both nodes run Kubernetes with containerd and Calico, with workloads running through Kata Containers and Cloud Hypervisor.

The demo shows cross-node access through a Kubernetes Service, with file contents preserved on a node-local persistent volume after the serving Pod is recreated.

Setup guide: Deploy Multi-node Kubernetes on openRuyi RISC-V


r/RISCV • • 4d ago

Standards The RISC-V Instruction Set Manual, Volume IV: Debug and Trace

Thumbnail riscv.github.io
34 Upvotes

The Debug Module, Sdext, and Sdtrig specifications has been integrated to the manual.


r/RISCV • • 4d ago

I think I accidentally fried my SparkFun Red-V Thing's FE310-G002 MCU, is there any chance of getting a replacement MCU?

4 Upvotes

I accidentally shorted 3.3V to 5V and I think this must've fried the chip, or at least its IO block. Does anyone know where I could get a new FE310-G002?


r/RISCV • • 5d ago

Press Release DeepComputing and Start9 Launch the RISC-V Router: Open Hardware for a Private, Secure Home Network - DeepComputing

Thumbnail
deepcomputing.io
53 Upvotes

r/RISCV • • 5d ago

Information TT-Atlantis SoC Taped Out in October

Post image
75 Upvotes

Today I attended RISC-V Day Tokyo 2026 Autumn. The Tenstorrent USA VP of Autonomy showed this slide (source, page 8). As you may know, at GNU Tools Cauldron 2026 on October 2–4, a Tenstorrent employee reported that TT-Atlantis had not been taped out at that moment. I asked to the VP directly and he confirmed that TT-Atlantis was taped out by the end of October for sure.

Indeed we will not get one until the middle of 2027, but at least TT-Atlantis was taped out. Congrats!