HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
olofk
serv
Verilog2019–2026
olofk / serv

serv

SERV - The SErial RISC-V CPU

24Distinct people
27Mentions
0Explicit recommenders
1.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

SERV - The SErial RISC-V CPU

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 8:03:49 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year27 dated mentions

Observed mentions: 2019-08-14 14:26:27 UTC to 2026-10-08 02:27:55 UTC.

02462019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 5 mentions; 3 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC303
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC505
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC532
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC615
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC321

What Hacker News says

5 sources
I think Western Digital has been shipping disk drives driven by RISC-V microcontrollers in volume for years. I think they won't sell you the microcontrollers, but they definitely aren't the only company doing this, just the loudest. They do offer their designs as free IP cores https://www.westerndigital.com/en-us/company/innovation/open... and apparently run Linux on some of them: https://www.techinsights.com/blog/wd-licenses-risc-v-cpus This last article says, "Since the storage company isn’t a traditional IP vendor, it has worked with Codasip to support its CPU licensees. Including [WD's] Swerv cores and other open-source designs, Codasip has helped customers ship two billion RISC-V chips over the past few years." (Emphasis mine.) But I think instead of "an entity like Google or Apple", or even WD, you should be thinking "an entity l
Read the rest
ike Baidu, Huawei, or AliBaba". The strongest RISC-V story is a Chinese national security thing, and it works like this. — ⁂ — Most computer hardware has been designed and assembled in the PRC for several years now. In 02019 the USG imposed heavy sanctions on a number of PRC hardware companies, including https://en.wikipedia.org/wiki/Huawei, the largest telecommunications equipment manufacturer in the world and since 02020 the largest smartphone manufacturer in the world. These sanctions deprived Huawei of access to chips from TSMC in Taiwan, even though Taiwan is nominally not under US jurisdiction. Computer hardware relies heavily on trade with Taiwan and other countries, including, in particular, MCUs and CPUs fabricated at TSMC in Taiwan using designs licensed from ARM. ARM China, a former ARM subsidiary, has the legal right to license ARM designs for use within China but not overseas. Using a component makes you vulnerable to backdoors inserted by the component's manufacturer or, if you do not understand its design, its designer. Such backdoors are known to have been a major instrument of US foreign policy in the past (the Crypto AG affair) and presumably still are. The Huawei sanctions were justified by allegations that the PRC is doing the same thing. There are rumors that some manufacturers in the PRC are experiencing a new "onshore mandate" that prohibits foreign-sourced components, at least in some products; quoting https://www.cnx-software.com/2022/10/22/10-cents-ch32v003-ri...: > [the WCH CH32V003 is] quite timely as we were forced by HQ last Friday to revise all product line designs to comply with 100% Chinese domestic semiconductors & passive components by latest Q4 end. All western sourced/accounts and parts are now forbidden, apart from those sourced by HQ’s registered jurisdiction. > Worth adding to the list, we’ve also signed accounts with GigaDevice and Expressif Shanghai in the MCU and connectivity range. — ⁂ — So that's the problem to solve. RISC-V already offers PRC manufacturers a path to building ARM-competitive MCUs and low-end CPUs which can be legally sold overseas and which comply with this onshore mandate. As a bonus, they can be sold at prices several times cheaper than any ARM alternative; WCH's CH32V003 is reputedly 10¢, though LCSC doesn't seem to have them in stock yet. Presumably, until SMIC (or another domestic alternative) can move up to more modern process nodes, fully-sanctions-proof versions of these chips will be larger, more expensive, and more power-hungry than TSMC-manufactured chips. But for many applications this doesn't matter. The Allwinner D1, using a RISC-V design from the Honey Badger open-source hardware subsidiary of AliBaba, is already performance-competitive with early Raspberry Pis, though I think that performance relies on TSMC. In 3–5 years RISC-V might be able to move up to today's desktop or laptop CPUs, and SMIC might be able to fabricate things at early Raspberry Pi performance levels (22 nm? Something past the end of Dennard scaling, anyway). — ⁂ — Also, though, you shouldn't totally dismiss the FPGA cores. FPGAs are a lot cheaper than they used to be, thanks to Lattice. It's true that an ASIC MCU will always be faster than an FPGA fabbed in the same process running a softcore, but it may not have the peripherals you need, and there are a lot of applications where we run an MCU at a 32768 Hz clock to save power, so clock speed isn't everything. Olof Kindgren's bit-serial RISC-V core SeRV https://github.com/olofk/serv reputedly fits into 200 4-LUTs like those in the Lattice iCE40LP384, which would cost US$1.82–2.15 at Digi-Key if they had any: https://www.digikey.com/en/products/detail/lattice-semicondu... and that would leave you another 184 LUTs for peripherals. You can get MCUs a lot cheaper than US$2 but US$2 is still within the budget for a lot of projects. Every year there are more and more custom ASICs from more and more companies, and a lot of them include some kind of microcontroller core to orchestrate their activities. Historically this has often been something like an 8051 or Z80, but switching it to RISC-V seems likely to lower development costs significantly, especially if a tiny RV32I core like SeRV or the smaller configurations of PicoRV32 would be adequate.
In Qualcomm says ARM to prohibit proximity of CPU and 3rd-party modules in one chip
There's a community doing "fpga golf". That is, reducing the number of LUT required to implement a CPU of a given ISA. A basic RV32 CPU is down to 500-700 LUT. https://github.com/YosysHQ/picorv32 https://github.com/olofk/serv A minimal 8051 requires about 300 LUT. https://github.com/MicroCoreLabs/Projects/tree/master/MCL51 Not sure how this translates from an FPGA to a transistor count. But RV32 and 8051 should be within a factor of 2-3.
In Apple to Move a Part of Its Embedded Cores to RISC-V

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.