riscv_em - GitLite

KO | EN

gitlite — search

#python #hacktoberfest #ai #llm #golang #machine-learning #rust #linux #docker #nodejs #macos #java #windows #openai

riscv_em

(★ 151)

Simple risc-v emulator, able to run linux, written in C.

파일 탐색기

최종 버전 다운로드 (.zip)

- - riscv_em_tests.yml
- build_dtb.sh
- riscv_em.dts
- riscv_em32_linux.dts
- riscv_em_backup.dts
- build_fw.sh
- main.c
- sections.lds
- start.s
- - build_test.sh
  - link.ld
  - riscv_test.h
- encoding.h
- - core.c
  - core.h
  - riscv_config.h
  - riscv_helper.h
  - riscv_instr.h
  - riscv_types.h
  - riscv_xlen_specifics.h
- - fifo.c
  - fifo.h
  - fifo_test.c
  - file_helper.c
  - file_helper.h
- - riscv_example_soc.c
  - riscv_example_soc.h
- main.c
.gitignore
.gitmodules
CMakeLists.txt
github_ci_prepare.sh
github_ci_run_tests.sh
LICENSE
README.md
Unity

# 설치 가이드

1. 코드 내려받기

git clone https://github.com/franzflasch/riscv_em

깃허브에서 프로젝트 코드 전체를 내 컴퓨터로 내려받습니다.

cd riscv_em

방금 내려받은 프로젝트 폴더 안으로 이동합니다.

2. CMake

보통 추천

사전 준비물

Git GitHub에서 프로젝트 코드를 내려받으려면 필요합니다.
CMake 빌드 설정을 생성하는 도구입니다.
C/C++ 컴파일러 Windows는 Visual Studio(Community 무료), macOS는 Xcode Command Line Tools, Linux는 gcc/g++ 패키지가 필요합니다.

cmake -DRV_ARCH=64 ..

이 명령어를 터미널에 그대로 입력해 실행하세요.

cmake -DRV_ARCH=32 ..

이 명령어를 터미널에 그대로 입력해 실행하세요.

✅ build 폴더 안에 실행 파일이 생성됐는지 확인하고, 직접 실행해보세요 (예: ./build/앱이름).

이 레포의 README에 적힌 실제 명령어를 그대로 가져왔습니다.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# riscv_em
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 ;)

### Ever wanted to know what the absolute minimum requirements are to run linux?
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.

## UPDATE 2021: Now the emulator also fully implements PMP and MMU.
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.

### How-To build RV64-nommu:
```console
mkdir build && cd build
cmake -DRV_ARCH=64 ..
make
```

### How-To build RV32-mmu:
```console
mkdir build && cd build
cmake -DRV_ARCH=32 ..
make
```

### Build the device tree binaries for RV64-nommu and RV32-mmu (device-tree-compiler needed):
```sh
cd dts
./build_dtb.sh
```

### Build a linux image for this emulator:
Please see https://github.com/franzflasch/linux_for_riscv_em

### Start the emulator and load (uc)linux (RV64-nommu):
```sh
./build/riscv_em -f <linux_for_riscv_em-path>/output/linux/loader_64.bin -d dts/riscv_em.dtb
```

### Start the emulator and load a full blown linux with opensbi (RV32-mmu):
```sh
./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
```

### RAM disk

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

```sh
./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).