This is a risc-v emulator written in plain C. It started as a fun project a while ago and is now capable of doing a few things (but still just a hobby, won't be big and professional like qemu ;)

riscv_em is the answer. Yes, the emulator is capable of running Linux.

One goal of this project is to be easily able to understand its source code and thus also the risc-v isa. You can also see this project as an attempt to directly translate the RISC-V ISA specs (Currently Unprivileged Spec v.20191213 and Privileged Spec v.20190608) into plain C. Implementation focus is simplicity NOT efficiency! Altough I always try to improve it's performance whenever possible, as long as the code does not suffer losses in readability!

Currently the emulator supports RV32IMA and RV64IMA instructions. Furthermore it implements a CLINT (Core-Local Interrupt Controller) and also a PLIC (Platform Level Interrupt Controller), as well as a simple UART.

Please see https://github.com/franzflasch/linux_for_riscv_em for a how-to-build appropriate linux images.

• MMU support is currently only available for RV32 (Sv32). Support for RV64 MMU (Sv39, Sv48) will follow.
• NOMMU is currently only supported for RV64 due to the kernel at the time of this writing only supports this for RV64.

mkdir build && cd build
cmake -DRV_ARCH=64 ..
make

mkdir build && cd build
cmake -DRV_ARCH=32 ..
make

cd dts
./build_dtb.sh

Please see https://github.com/franzflasch/linux_for_riscv_em

./build/riscv_em -f <linux_for_riscv_em-path>/output/linux/loader_64.bin -d dts/riscv_em.dtb

./build/riscv_em -f <linux_for_riscv_em-path>/output_mmu_rv32/opensbi/build/platform/generic/firmware/fw_payload.bin -d dts/riscv_em32_linux.dtb

Make a filesystem image using the normal filesystem tools (e.g. mkfs.ext3, mksquashfs etc) with a maximum size of 200Mb. Then run

./build/riscv_em -f <linux_for_riscv_em-path>/output/linux/loader_64.bin -d dts/riscv_em.dtb -i mydiskimage.ext3

The filesystem will be available as /dev/pmem0, which can be either mounted from userspace, or specified as the root filesystem. Note that this does not use the initrd or initramdisk functionality, as that has severe size limitations (tries to unpack/copy the whole filesystem at boot).