What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
RISC-V is changing processor development by making the instruction set architecture (ISA) an open, modular standard rather than a proprietary specification controlled by one vendor. Ratified extensions provide stable features, while profiles such as RVA23 define a common baseline for a class of processors. Together they can make hardware competition and software portability easier—but they do not make every RISC-V chip interchangeable or guarantee that applications will run without matching implementation and software support.
What is RISC-V and why does it matter?
RISC-V (pronounced “risk-five”) is an open standard ISA: the specification that defines the instructions a processor can execute, how those instructions behave, and related architectural rules. It is not a processor model, chip company, operating system or finished computer.
The architecture is modular. A designer can implement a ratified base ISA, add ratified extensions for capabilities such as multiplication, atomics or vectors, and—where appropriate—create custom extensions for a particular product. This lets one architecture serve tiny microcontrollers, embedded devices, application processors and specialized accelerators.
That flexibility also creates a compatibility problem. Two processors can both be RISC-V while supporting different extension combinations, privilege features or system-level conventions. Software compiled for one feature set may therefore require conditional builds, fallbacks or a different target on another chip.
#1 Best Overall
- Flexible MCU Board: Incorporate the ESP32-C3 32-bit RISC-V chip, operating up to 160 MHz, mounted multiple development ports,
- Developer Friendly: Compatible with Arduino IDE, MicroPython, CircuitPython, PlatformIO, ESP IDF, Zephyr, Matter, ESPNow, Meshtastic, WLED, ESPHome, Home Assistant, Ubidots
- Outstanding RF performance: Complete Wi-Fi functions and Bluetooth Low Energy, while supporting communication over 100m with anFL antenna
- Elaborate Power Design: 4 working modes as low as 44 μA in deep sleep mode, while supporting lithium battery charge management
- Thumb-sized Design: 21 x 17.5mm, Seeed Studio XIAO series classic form factor
How do RISC-V standards improve compatibility?
Ratified extensions create stable building blocks
When the RISC-V community ratifies an extension, its definition becomes a stable architectural contract. Compiler, operating-system and hardware developers can implement that feature against a published specification instead of a changing draft.
Ratification alone does not require every RISC-V processor to implement the extension. An implementation can conform to the base architecture while omitting optional extensions, so software still needs to know which capabilities are present.
Profiles define a shared minimum
A profile groups required architectural features for a particular class of processor. It answers a more practical question than “Is this chip RISC-V?”: “Does this processor provide the agreed features that this software target expects?”
Profiles improve the odds that an operating system, compiler, library or application built for the profile will work across processors that meet it. They are a portability target, not a claim that all RISC-V hardware is identical.
Rank #2
- CH32V003 Development Minimum System Board for Nano RISC-V CH32V003F4U6 Chip TYPE-C USB 22Pin
- on-board 24MHz Crystal oscillator
- Power by TYPE-C USB
What is the RVA23 profile?
RVA23 is an application-class profile for 64-bit RISC-V processors. Version 1.0 was ratified on October 17, 2024. It gives operating-system, toolchain, library and application developers a clearer baseline than a loose collection of optional extensions.
The distinction between an extension and a profile matters:
| Item | What it standardizes | What it does not promise |
|---|---|---|
| Ratified ISA extension | A defined architectural feature and its behavior | That every processor implements the feature |
| RVA23 profile | A required set of features for a 64-bit application-processor class | That every RISC-V chip is RVA23-compliant or binary-compatible |
| Specific implementation | A vendor’s actual core, SoC, memory system and platform | That its documentation or software support matches another implementation |
For software vendors, the value is a more predictable target. For chip designers, it provides a recognized application-processor baseline while leaving room for differentiation outside the required set.
Will RISC-V software run on different RISC-V processors?
Sometimes, but the name alone is not enough. Portability depends on the processor’s profile or documented extension set, privilege and memory-management behavior, platform interfaces, and the software’s own support.
Rank #3
- The ESP32-C3 SUPERMINI is positioned as a high-performance, low-power, cost-effective IoT mini development board, suitable for low-power IoT applications and wireless wearable applications
- It is equipped with a rich set of interfaces, including 11 digital I/Os that can be used as PWM pins and 4 analog I/Os that can be used as ADC pins.
- It supports four serial interfaces, including UART, I2C, and SPI.
- The ESP32-C3 features a 32-bit RISC-V CPU, including an FPU (Floating Point Unit) capable of 32-bit single-precision
- Package: 2PCS ESP32-C3 MINI Development Board ESP32 SuperMini ESP32 C3 WiFi Module
Check the ISA and profile target
Confirm which base ISA, ratified extensions and profile the processor implements. A program using vector instructions, for example, cannot assume they exist on a chip that implements only a smaller scalar feature set.
Check system-level requirements
Operating systems and hypervisors also depend on boot conventions, interrupt controllers, debugging interfaces, memory-management features and platform-management standards. Matching instruction support is necessary but may not be sufficient for a working system.
Check upstream software support
Drivers, board support, compilers, kernels and libraries must be available for the actual platform. Upstream support in common open-source projects generally reduces long-term maintenance compared with a private vendor fork, but it remains an implementation and project-status question.
How are standards work expanding beyond the ISA?
RISC-V standardization is increasingly addressing the platform around the processor. RISC-V International’s 2025 annual report describes RVA23 as an application-processor baseline and records work on server, boot, debug, platform-management, vector-intrinsics and memory-management standards. It also emphasizes upstreaming drivers and other software into shared open-source projects.
Rank #4
- ESP32-C6 WiFi 6 microcontroller development board adopts ESP32-C6-WROOM-1-N8 module, which is equipped with RISC-V 32-bit single-core processor, up to 160MHz main frequency, built-in 8MB Flash
- Integrates WiFi 6, Bluetooth 5 and and IEEE 802.15.4 (Zigbee 3.0 and Thread) wireless communication, with superior RF performance
- Integrates rich peripherals including SPI, UART, I2C, I2S, LED PWM, SDIO and other interfaces, compatible with the pinout of ESP32-C6-DevKitC-1-N8 development board, more convenient to use and expand a variety of peripheral modules
- Onboard CH343 and CH334 USB HUB chips, supports USB and UART development at the same time via a USB-C port
- Comes with online examples and tutorials for ESP-IDF development environment
These milestones show the standards organization’s priorities and reported progress. They are not, by themselves, independent measurements of shipment volume, production deployment or market share. A platform standard becomes useful to users only when implementations document compliance and the required software is available.
Is RISC-V widely adopted?
Adoption depends on what is being counted. Membership in the standards organization, ratified specifications, shipping chips, deployed systems and market share are different measures.
RISC-V International reported more than 4,120 members across 52 countries and more than 80 technical working groups in 2024. Its 2025 annual report also reported 17 new members and described RVA23 adoption as an application-processor baseline. Those figures are organizational reports, not independent processor-shipment or market-share statistics.
No precise market-share conclusion follows from them. The evidence supports a growing standards and development ecosystem, but not a claim that RISC-V has replaced incumbent architectures or that all RISC-V products are broadly deployed.
Best Value
- Ample PSRAM Storage – The development board offers 8MB PSRAM, providing substantial extra memory for handling more complex tasks, large data buffers, and advanced processing.
- Enhanced Multi-Tasking Capability – With the additional 8MB PSRAM, the ESP32-C5-WIFI6-KIT can efficiently manage multiple protocol stacks simultaneously, ensuring smooth operation in multi-tasking IoT environments.
- Support for Medium-Load Applications – The 8MB PSRAM allows the ESP32-C5 to handle medium-load applications more effectively, making it ideal for scenarios requiring real-time data processing or continuous communication.
- Seamless Performance – The increased memory improves the overall performance and responsiveness of the device, particularly when running applications with larger memory footprints or more demanding computations.
- Future-Proof for Complex Projects – With 8MB of PSRAM, developers are better equipped to build scalable, high-performance solutions that support both current and future IoT use cases, offering flexibility for future-proofing designs.
What changes for the people building technology?
For chip designers
- They can start from a public ISA specification and choose only the standard features their product needs.
- They can add custom instructions for differentiated workloads while retaining a standard foundation.
- Profiles provide clearer targets for application-class compatibility.
For operating-system and toolchain developers
- Profiles reduce the number of hardware combinations that must be treated as first-class targets.
- Stable ratified extensions make compiler and library support less dependent on draft specifications.
- Platform standards and upstream drivers can reduce board-specific integration work.
For device and system buyers
- They can compare a processor’s profile, extensions and platform compliance instead of relying on the RISC-V label.
- They should ask whether the required kernel, drivers, debugging tools and application stack support the exact model.
- They should distinguish a development board from evidence that a product implements an application-class profile.
How to evaluate a RISC-V implementation
- Identify the target workload. Decide whether you need a microcontroller, embedded Linux system, application processor, server platform or specialized accelerator.
- Read the implementation’s ISA declaration. Record the base ISA, ratified extensions, privilege features and vector or other optional capabilities.
- Verify profile compliance. For an application-class target, check whether the documentation explicitly claims compliance with RVA23 or another applicable profile.
- Inspect platform requirements. Check boot, interrupt, debug, memory-management and platform-management interfaces required by your operating system and tools.
- Test the software path. Confirm compiler, kernel, libraries, drivers, firmware and debugging support for the exact board or SoC, preferably in upstream projects.
- Plan for nonstandard features. If custom extensions are used, provide fallbacks or isolate that code so it does not prevent software from running on standard implementations.
What are the limits of the standards approach?
- Standards do not implement themselves. A ratified feature still needs reliable hardware, compiler support, operating-system code and drivers.
- Profiles are class-specific. RVA23 targets 64-bit application processors; it is not a requirement for every embedded or microcontroller product.
- Compliance does not erase performance differences. Two profile-compliant processors can differ substantially in frequency, cache design, memory bandwidth, power use and accelerator integration.
- Version status changes. The official ratified-specification library is the authoritative place to verify current versions and status; it listed, among other recent entries, a Server Platform v1.0 dated May 2026.
Try RISC-V hands-on
A RISC-V development board can make the architecture concrete. Milk-V documents its Duo family as embedded development platforms with RISC-V CPUs and publishes model-specific hardware specifications. Choose a model only after checking its supported ISA extensions, memory, storage, peripherals and software image.
A board demonstrates one implementation, not every RISC-V feature. The available documentation does not establish that the Milk-V Duo family implements RVA23, so it should not be used as proof of application-profile compliance.
What the world-changing claim really means
RISC-V’s most consequential change is organizational as much as technical: an open ISA lets more companies and research teams design compatible processors without licensing a closed instruction-set specification, while profiles and platform standards give software a more dependable common target. The result can be more supplier diversity, customization and negotiating choice. Whether users experience those benefits depends on compliant implementations and a mature software stack, not on the architecture’s name alone.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
