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 524 public repositories matching this topic...

MaixPy
junhuanchen
junhuanchen commented Jan 11, 2021

About this question, here is a unified reply.

We need to see this place where one is the definition and load the configuration.

https://github.com/sipeed/MaixPy/blob/master/components/micropython/port/builtin_py/board.py

If you don't provide the configuration, you won't get the concrete variable.

If it is SIPEED published hardware, the appropriate configuration is provided here.

htt

good first issue usage
David-OConnor
David-OConnor commented Apr 28, 2022

Is your feature request related to a problem? Please describe.
Yes

Describe the solution you'd like
Please add STM32 G491 series

Describe alternatives you've considered
Running probe-run --list-chips does not include any STM32 G491 entries

Additional context
Thanks!

  • edit: This line is similar to the G431. I was able to flash and get code running with no evident is
enhancement good first issue
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

Type:Bug Component:RTL PARAM:FPU Good First Issue
Website
riscv.org
Wikipedia
Wikipedia