RISC-V Processors, Microcontrollers & Development Boards

RISC-V processors and development hardware: choose the actual device, not just the architecture label

Explore RISC-V microcontrollers, development boards and related computing hardware for embedded control, wireless prototyping, FPGA experiments and Linux-based edge systems. This collection also includes mixed-architecture boards, configurable FPGA platforms and a few adjacent accessories. An item appearing here is not a promise that its main processor executes RISC-V instructions. Check the exact model and selected variant before ordering.

What you may find here

• Native RISC-V MCU chips and boards: WCH CH32V003, CH32V203, CH32V305, CH32V307 and CH32X035 listings include bare IC packs, minimum-system boards and evaluation boards. ESP32-C3, ESP32-C5, ESP32-C6 and ESP32-P4 listings include compact development boards, modules and interface-rich boards. A chip-only listing does not include a programmed development board, USB interface or peripheral kit unless its selected option explicitly says so.
• RP2350-based boards: Pico 2, Pico 2 W, XIAO RP2350 and WeAct RP2350A/B options are based on the RP2350 family, which provides selectable Arm Cortex-M33 and Hazard3 RISC-V processor cores. Verify the firmware build and debug workflow for the chosen architecture; a board's presence here does not mean it runs RISC-V by default. Check A versus B silicon, exposed GPIO, wireless capability, flash and board form factor by listing and variant.
• Heterogeneous embedded Linux hardware: Luckfox RV1103/RV1106 Pico and Core1106 boards, and Allwinner T113/F133 or other multi-core boards, can combine an Arm application processor with RISC-V microcontroller or auxiliary processing resources. Their Linux software stack, camera/display interfaces, NPU or ISP features depend on the exact chip and board. Do not treat an auxiliary RISC-V core as a replacement for the main Arm CPU.
• FPGA platforms for RISC-V projects: Sipeed Tang Nano, Primer and Mega boards, as well as listed Artix-7, ECP5 and iCE40 boards, are primarily FPGA development hardware. Some projects can implement a RISC-V soft processor in programmable logic, but the FPGA is not automatically a fixed RISC-V CPU, nor is Linux support inherent to every board. Verify fabric capacity, memory, configuration flash, toolchain, bitstream, dock/carrier and display accessories for your project.
• Peripheral and mixed listings: NanoKVM options, screens, carrier boards, optocoupler modules, an ESP8266 Wi-Fi module, an ATmega48 AVR MCU and a portable heating tool appear among the products. These are not interchangeable RISC-V processors. AVR's RISC terminology is not the RISC-V instruction-set architecture. Their inclusion does not make these accessories or unrelated items compatible with any specific RISC-V board.

Specification checklist before you buy

1. Identify the compute architecture: distinguish a native RISC-V MCU from an Arm-led heterogeneous SoC, an RP2350 architecture choice and an FPGA soft-core project. Match your compiler target, binary, board support package and debugger to the selected device.
2. Choose the hardware level: bare IC, soldered module, breakout/minimum-system board, core board, dock or fully equipped development kit are different purchases. Confirm whether a carrier, heatsink, cable, screen, header or power adapter is included; a product image may show an example setup rather than box contents.
3. Read the variant, not just the headline: option labels such as Color or Model Number may encode chip version, board revision, storage capacity, PSRAM/flash, antenna, soldered headers, display size, kit contents or quantity. A headline containing several part numbers does not imply a mixed assortment. Listings marked 1/5/10 pieces or 10 pcs require the selected option to establish the actual quantity.
4. Check electrical and mechanical fit: compare supply voltage, GPIO logic levels, pinout, package, USB connector, programming interface, boot mode, antenna arrangement, Ethernet/PoE implementation, display/camera connectors and carrier mating dimensions against your design. Never assume that similarly named boards have identical pin assignments or that a USB connector provides every advertised interface.
5. Confirm software and peripherals: verify the exact flash/PSRAM/eMMC configuration, wireless bands and protocol support, required external radio, Linux image or MCU SDK, available GPIO and peripheral routing in the chosen listing and official device documentation. In particular, an ESP32-P4 board does not gain Wi-Fi simply because another option or companion ESP32-C6 module mentions wireless support. Marketing claims about throughput, certifications, authenticity or industrial grade are not collection-wide specifications.

Frequently asked questions

Does every product in this collection contain a RISC-V CPU? No. Some use Arm for the primary CPU, some are FPGAs that can host a configured soft core, and some are accessories or unrelated products. Use the chip identifier and selected option as the starting point.

Are Pico 2 and RP2350 boards RISC-V-only? No. RP2350 designs support an Arm Cortex-M33 or Hazard3 RISC-V execution choice; your firmware, development environment and board implementation must match.

Is a Tang FPGA board ready to run RISC-V code out of the box? Not necessarily. A compatible RISC-V soft core must be implemented or supplied as a suitable bitstream with the required memory, firmware and peripherals. A board advertised for RISC-V learning does not guarantee a preloaded processor or Linux image.

Can I substitute a Luckfox Linux board for a CH32V MCU board? Not as a drop-in replacement. A heterogeneous Linux SoC, a standalone MCU and their software, voltages, connectors and power needs are substantially different.

Is the title's flash, wireless feature, display or pack size included in every option? No. The title can describe a family. Confirm the chosen variant's memory, network hardware, accessory bundle and piece count on the individual product page before checkout.

Use each product's variant and technical documentation as the final authority where seller descriptions conflict. Verify suitability for your application before integrating hardware into a system.