Skip to content
#

RISC-V

riscv logo

Unlike most other ISA designs, the RISC-V ISA is provided under open source licenses that do not require fees to use. A number of companies are offering or have announced RISC-V hardware, open source operating systems with RISC-V support are available and the instruction set is supported in several popular software toolchains.

Notable features of the RISC-V ISA include a load–store architecture, bit patterns to simplify the multiplexers in a CPU, IEEE 754 floating-point, a design that is architecturally neutral, and placing most-significant bits at a fixed location to speed sign extension. The instruction set is designed for a wide range of uses. The base instruction set has a fixed length of 32-bit naturally aligned instructions, and the ISA supports variable length extensions where each instruction could be an any number of 16-bit parcels in length. Subsets support small embedded systems, personal computers, supercomputers with vector processors, and warehouse-scale 19 inch rack-mounted parallel computers.

Here are 382 public repositories matching this topic...

ccelio
ccelio commented Oct 20, 2017

Summary:
A nice-to-have feature is the ability to enable and disable hardware features from the software.

Examples:

  • Enable TSO memory consistency
  • Enable watchdog timer
  • Change predictor behaviors

High-level thoughts:

  • Do not use non-standard Control/Status Registers (CSRs). The address space will get too congested, not indexable, messy to assemble for, etc.
  • Inst
jonas-schievink
jonas-schievink commented Feb 15, 2021

Currently, J-Link probes that fail to open do not show up as inaccessible in the probe list. Instead, they just have their serial number and device identifier left blank.

Listing probes should instead yield Results, so that the calling code can act properly, by:

  • selecting the only accessible probe when there is more than 1 (but only 1 can be opened successfully)
  • providing guidance to th
mmatzev
mmatzev commented Apr 17, 2020

This is not strictly related to CV32E40P as the problem seems to be in fpnew, but did anybody verify the operation of CV32E40P with fpnew in verilator?

There is a coding-style in fpnew, which prevents verilator to work. But even if this problem is solved, the simulation is not running due to a deadlog in the div_sqrt unit. The same code runs with Questa/Modelsim without problems!?

It is hard

Website
riscv.org
Wikipedia
Wikipedia