Simplistic RISC-V emulator
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Go to file
Anton Lydike 242af5c7a3 implemented mmu.allocate_region and reworked how the stack works 4 years ago
.idea parsing of tokenized asm into MemorySections works 4 years ago
docs removed stack pref pseudo-op in preperation for real stack impl 4 years ago
examples added more documentation about debuggin tools 4 years ago
riscemu implemented mmu.allocate_region and reworked how the stack works 4 years ago
sphinx-docs brainfart when configuring readthedocs theme 4 years ago
test added basic tests 4 years ago
.gitignore initial commit 4 years ago
.readthedocs.yaml more readthedocs fixes? 4 years ago
LICENSE now officially MIT licensed 4 years ago
README.md updated docs for new logging 4 years ago
generate-docs.sh more readthedocs fixes? 4 years ago
requirements.txt initial commit 4 years ago
test.asm added scaffolding form RVM instruction set 4 years ago

README.md

RISC-V (userspace) emulator in python

Implementing a basic RISC-V emulator, aimed at being easily extendable.

This emulator contains:

  • RISC-V Assembly parser
  • RISC-V Assembly loader
  • Emulation for parts of the basic RISC-V instruction set
  • Naive memory emulator
  • Basic implementation of some syscalls
  • A debugging environment

Running simple Assembly:

A couple of basic assembly programs are provided inside examples/, such as hello-world.asm.

You can run it by typing python -m riscemu examples/hello-world.asm. It will produce output similar to:

[MMU] Successfully loaded: LoadedExecutable[examples/hello-world.asm](base=0x00000100, size=24bytes, sections=data text, run_ptr=0x00000110)
[CPU] Started running from 0x00000110 (examples/hello-world.asm)
Hello world

Program exited with code 0

The read syscall defaults to readline behaviour. Reading "true chunks" (ignoring newlines) is currently not supported.

See the docs on asembly for more detail on how to write assembly code for this emulator. See the list of implemented syscalls for more details on how to syscall.

Currently, symbols (such as main or loop) are looked-up at runtime. This allows for better debugging, I believe.

Basic IO should work, as open, read, write and close are supported for stdin/stdout/stderr and even aribtrary file paths (if enabled)

When trying to run an assembly program, the emulator first tries to find a symbol named _start, then a symbol named main. if both symbols were not found in the file, it simply starts at the beginning of the .text segment.

Using the CLI:

Current CLI is not final, options may change frequently until a stable version is reached

This is how the interface is used:

usage: riscemu [-h] [--options OPTIONS] [--syscall-opts SYSCALL_OPTS] [--instruction-sets INSTRUCTION_SETS] [--default_stack_size [default-stack-size]] file.asm [file.asm ...]



OPTIONS and SYSCALL_OPTIONS is a list of comma-separated flags that will be enabled

--options OPTIONS: (-o)
disable_debug           Disable the ebreak and sbreak instructions
no_syscall_symbols      Don't make syscall symbols globally available
fail_on_ex              Do not launch an interactive debugger when the CPU loop catches an exception
add_accept_imm          accept "add rd, rs, imm" instructions, even though they are not standard

--syscall-opts SYSCALL_OPTS: (-so)
                        Options to control syscall behaviour
fs_access               Allow access to the filesystem
disable_io              Disallow reading/writing from stdin/stdout/stderr

--instruction-sets INSTRUCTION_SETS: (-is)
                        A list of comma separated instruction sets you want to load:
                        Currently implemented: RV32I, RV32M

If multiple files are specified, all are loaded into memeory, but only the last one is executed. This might be improved later, maybe the _init section of each binary is executed before the main loop starts?

Debugging

Debugging is done using the ebreak (formerly sbreak) instruction, which will launch a debugging session if encountered. See docs/debugging.md for more info.

debuggin the fibs program

The source code:

Check out the documentation.

Resources:

TODO:

  • Currently registers don't enforce 32 bit (no overflows etc)
  • Correctly handle 12 and 20 bit immediate (currently not limited to bits at all)
  • Add a cycle limit to the options and CPU to catch infinite loops
  • Move away from print and use logging.logger instead
  • Properly support stack/heap
  • Writer proper tests