Skip to content
No description, website, or topics provided.
Assembly C SystemVerilog C++ Makefile Forth Other
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.settings most unit tests passing Sep 15, 2019
doc document requirement for Java Sep 15, 2019
etc doc cleanups and enhancements Sep 15, 2019
rtl
scripts correct spurious branch register writes, add jump tests, begin work o… Oct 31, 2018
soc doc cleanups and enhancements Sep 15, 2019
synth
ve add new fpga bench Sep 15, 2019
.cproject initial RIPE tests failing ;-) Aug 13, 2019
.gitignore first baby steps in bringing up fwrisc Oct 26, 2018
.project
.pydevproject
.svproject first baby steps in bringing up fwrisc Oct 26, 2018
ChangeLog.txt
LICENSE
README.md doc cleanups and enhancements Sep 15, 2019
requirements.txt doc cleanups and enhancements Sep 15, 2019
sve.F Add UVM testbench structure May 3, 2019

README.md

FWRISC

FWRISC-S is a Featherweight RISC-V implementation of the RV32IMC instruction set with IoT-appropriate security features. This implementation supports the integer instructions, registers, CSRs, and exceptions as required by the RISC-V spec.

This revision of the core was created for the 2019 RISC-V security contest: https://riscv.org/2019/07/risc-v-softcpu-core-contest/

FWRISC is a non-pipelined processor that aims to balance performance with FPGA resource utilization. It achieves 0.15 DMIPS/Mhz.

FWRISC correctly runs all RISCV RV32I compliance tests. It also supports the Zephyr RTOS.

Core Features

  • RV32IMC instructions
  • Multi-cycle shift
  • Multi-cycle multiply/divide
  • Support for the compressed-instruction ISA
  • MINSTR, MCYCLE counters
  • ECALL/EBREAK/ERET instrutions
  • Support for address-alignment exceptions

SEcurity Features

FWRISC-S implements Data Execution Prevention, as a way to prevent arbitrary code execution. While more-complex protection techniques are appropriate for more-complex systems, IoT systems typically run a fixed program that can be easily protected in this way. The Zephyr SoC-support configuration has been setup such that data execution prevention is configured just after kernel boot. Using linker symbols, the configuration programs CSRs to only allow execution in the text section of the image. See Zephyr for more information.

Resource Stats

The bare FWRISC-S 1.0.0 core consumes the following resources:

TargetLUTs/LCsRAMFrequency
Microsemi IGLOO2 (Synplify)2592 LUTs2x 64x1836.6Mhz

Getting Started

See the Quickstart document to get started with FWRISC. For more detailed information, see the documents below.

You can’t perform that action at this time.