The NEORV32 RISC-V Processor

The NEORV32 Processor is a customizable microcontroller-like system on chip (SoC) built around the NEORV32 RISC-V CPU that is written in platform-independent VHDL. The processor is intended as auxiliary controller in larger SoC designs or as tiny and customized microcontroller. The project is intended to work out of the box and targets FPGA / RISC-V beginners as well as experienced users.

Key Features

• all-in-one package: CPU + SoC + Software Framework + Test Infrastructure
• fully self-contained - no external dependencies
• completely described in behavioral, platform-independent VHDL - no primitives, macros, attributes, etc.
• technology friendly; e.g. all internal memories can be mapped to FPGA or ASIC primitives
• extensive CPU & SoC configuration options for adapting to application requirements
• aims to be as small as possible while being as RISC-V-compliant as possible
• optimized for high clock frequencies to ease integration and timing closure
• from zero to printf("hello world"); - completely open-source and documented
• easy to use – intended to work out of the box

• :recycle: Looking for an all-Verilog version? Have a look at the auto-conversion setup.
• :mag: Continuous integration to check for regressions.
• :open_file_folder: Exemplary setups and community projects targeting various FPGA boards and toolchains to get started.
• :package: The entire processor is also available as Vivado IP Block.
• :kite: Upstream Zephyr and FreeRTOS operating system support.
• :penguin: Capable of running nommu-Linux.
• :building_construction: LiteX SoC builder integration.
• :gear: MicroPython port, Ada support, and Rust integration via Embassy framework.
• :desktop_computer: Pre-configured Eclipse project.
• :label: The project's change log is available in CHANGELOG.md.
• :rocket: Check out the quick links below and the User Guide to get started.
• :books: For detailed information see the online documentation.

Project Status

Task	CI Status
GitHub pages
Documentation
Processor check
Verilog conversion
RISC-V compliance

The processor passes the official RISC-V Architectural Certification Tests (ACT). It can successfully run any software including CoreMark and FreeRTOS and can be synthesized for any target technology - tested on AMD, Intel, Lattice, Microchip, Gowin and Cologne Chip FPGAs. The processor has also been taped out several times as an ASIC.

Features

The NEORV32 Processor provides a full-featured microcontroller-like SoC build around the NEORV32 CPU. By using generics the design is highly configurable and allows a flexible customization to tailor the setup according to your needs. Note that all of the following SoC modules are entirely optional.

CPU Core(s)

• 
• RISC-V 32-bit little-endian pipelined/multi-cycle modified-Harvard architecture
• Single-core or SMP dual-core configuration
• configurable instruction sets and extensions:
  RV32 I E M A C B U X Sdext Sdtrig Smcntrpmf Smpmp Zaamo Zalrsc Zba Zbb Zbc Zbkb Zbkc Zbkx Zbs Zcb Zcmop Zfinx Zibi Zicntr Zicond Zicsr Zifencei Zihpm Zimop Zmmul Zkn Zknd Zkne Zknh Zkt Zks Zksed Zksh Xcfu
• compliant with subsets of the RISC-V "Unprivileged ISA Specification" and "Privileged Architecture Specification"
• machine and optional user privilege modes
• implements all RISC-V machine-level exceptions and interrupts + 16 fast interrupt request channels as NEORV32-specific extension
• custom functions unit (CFU as custom Xcfu ISA extension) for custom RISC-V instructions

Memories

• tightly-coupled data and instruction memories (DMEM & IMEM) and caches (iCACHE & dCACHE)
• serial memory controller (SMC) for transparent access to up to 2x PSRAM/flash chips (supporting XIP)
• pre-installed bootloader (BOOTLDROM) with serial user interface; allows booting application code via UART, I²C or SPI flash and from SD card

Timers and Counters

• RISC-V-compatible core-local interruptor (CLINT)
• 32-bit general purpose timer (GPTMR) with up to 16 individual timer slices
• watchdog timer (WDT)

Input / Output

• standard serial interfaces: 2x UART, SPI (SPI host), SDI (SPI device), TWI (I²C host), TWD (I²C device), ONEWIRE (1-wire host)
• up to 32 general purpose IOs (GPIO, interrupt-capable) and up to 32 individual PWM channels
• smart LED interface (NEOLED) to directly control NeoPixel(TM) LEDs

SoC Connectivity

• 32-bit external bus interface - Wishbone-compatible (XBUS); bridge for AXI4-compatible interfaces
• stream link interface with independent RX and TX channels - AXI4-Stream-compatible (SLINK)

Advanced

• true-random number generator (TRNG) based on the neoTRNG
• custom functions subsystem (CFS) for custom tightly-coupled co-processors, accelerators or interfaces
• direct memory access controller (DMA) for CPU-independent data transfers and conversions
• RVFI-compatible trace port for advanced debugging, profiling or verification

Debugging

• on-chip debugger (OCD) accessible via standard JTAG interface
• compatible to the "RISC-V Debug Specification Version 1.0"
• compatible with OpenOCD, GDB and Segger Embedded Studio
• RISC-V trigger module for hardware-assisted break- and watchpoints
• optional JTAG authentication module to implement custom security mechanisms
• execution trace buffer (TRACER)

Size and Performance

The NEORV32 processor is optimized for minimal size. However, the actual size (silicon area or FPGA resources) depends on the specific configuration. For example, an RTOS-capable setup based on a rv32imc_Zicsr_Zicntr CPU configuration requires about 2300 LUTs and 1000 FFs and can run at up to 130 MHz (implementation results for an Altera Cyclone IV E EP4CE22F17C6 FPGA). This configuration provides a CoreMark score of 95 (0.95 CoreMarks/MHz). The corresponding dual-core version achieves a CoreMark score of 190 (1.9 CoreMarks/MHz).

More information regarding the CPU performance can be found in the Data Sheet: Performance.

Getting Started

This overview provides some quick links to the most important sections of the online Data Sheet and the online User Guide.

:mag: NEORV32 Project - An Introduction

• Key Features - what makes it special
• Structure - folders, RTL files and compile order
• File-List Files - to simplify HDL setup
• Metrics - FPGA implementation and performance evaluation

:desktop_computer: NEORV32 Processor - The SoC

• Top Entity - Signals - how to connect to the processor
• Top Entity - Generics - processor/CPU configuration options
• Address Space - memory layout and address mapping
• Boot Configuration - how to make the processor start execution
• SoC Modules - IO/peripheral modules and memories
• On-Chip Debugger - in-system debugging via JTAG

:abacus: NEORV32 CPU - The Core

• Architecture - a look under the hood
• Full Virtualization - execution safety
• ISA and Extensions - available (RISC-V) ISA extensions
• CSRs - control and status registers
• Traps - interrupts and exceptions

:floppy_disk: Software Framework - The Software Ecosystem

• Example Programs - examples how to use the processor's IO/peripheral modules
• Core Libraries - high-level functions for accessing the processor's peripherals
• Software Framework Documentation - doxygen-based
• Application Makefile - turning your application into an executable
• Bootloader - the build-in NEORV32 bootloader
• Image Generator - create (FPGA) memory initialization files from your application
• Semihosting - access files and system services on the host computer

:rocket: User Guide - Getting Started

• Toolchain Setup - install and set up the RISC-V GCC toolchain
• General Hardware Setup - set up a new NEORV32 FPGA project
• Adding Custom Hardware Modules - add your custom hardware
• Convert to Verilog - turn the NEORV32 into an all-Verilog design
• Package as Vivado IP block - turn the entire processor into an interactive AMD Vivado IP block
• Using Eclipse - use the Eclipse IDE for developing and debugging

This is an open-source project that is free of charge and provided under an permissive license. See the legal section for more information.

Contributing

Contributions are very welcome! If you’d like to improve something, fix a bug, or add a feature, feel free to open an issue or submit a pull request. See how to contribute. A big thank you goes out to the community and all contributors who help improve this project: