Runs the rice RISC-V core (RV32IM) on a Digilent Arty A7-35 with veryl-harness.
The host loads a program with hio, and the program's console is RTT, in
memory that the host also reads.
What a program sees.
| Address | Size | Region | Backed by |
|---|---|---|---|
0x8000_0000 – 0x8000_FFFF |
64 KB | imem: the reset PC, and code; fetches read only this |
FPGA block RAM (one cycle) |
0x8000_0000 – 0x8000_FFFF |
64 KB | dmem: data, the stack, the RTT console; loads and stores reach only this |
FPGA block RAM (one cycle) |
The two memories have the same addresses. hio cpu boot loads each segment
into both, and a store is not seen by fetches. Nothing else is mapped: a read
returns 0, a write is dropped, and imem_oor / dmem_oor count them. There
is no I/O device. Harness.dram.toml has another map, with the DRAM (below).
- Veryl, with
veryl-harnessandhio - Vivado
- An Arty A7-35 on USB
- Rust through rustup, for the firmware
qemu-system-riscv32, to run the firmware without the board
veryl harness gen --target digilent/arty-a7-35
make -C hns/syn
hio program
hio run bringup.hio # loads asm/smoke.elf and reads back what it wroteFirmware in Rust: hio cpu boot loads it and shows its RTT console (Ctrl-A x
leaves). If gen wrote somewhere other than hns/, change HIO_REGS in
.cargo/config.toml.
cargo run -p hello
cargo run -p console
cargo run-emu -p console # the same on QEMUriscv-tests: scripts/riscv-tests.sh <riscv-tests>/share/riscv-tests/isa
(built for RV32).
Harness.dram.toml runs the core on rtl/rice_mem_top.veryl, with one
address space for fetches, loads and stores, so a program of any size fits.
It needs a board with a DRAM that the harness can reach (not the PYNQ-Z1).
| Address | Size | Region | Backed by |
|---|---|---|---|
0x8000_0000 – 0x8000_FFFF |
64 KB | tcm: the reset PC, and code |
FPGA block RAM (two cycles for a fetch) |
0x8001_0000 – 0x9000_FFFF |
256 MB | dmem: data, the stack, the RTT console |
the board's DRAM |
Nothing else is mapped: the harness refuses such an access and counts it in
dmem_oor.
veryl harness gen --config Harness.dram.toml --out-dir hns_mem --target digilent/arty-a7-35
make -C hns_mem/syn
HIO_REGS=hns_mem/regs.json hio programpicoruby/ runs a Ruby script on it with mruby/c (the same firmware as
run-hazard3's, for 40 MHz): make -C picoruby, then
HIO_REGS=hns_mem/regs.json hio cpu boot picoruby/picoruby.elf.
What the build needs (PicoRuby, Ruby, an RV32 toolchain):
doc/picoruby.md.
make -C sim mem runs asm/mem.S in Verilator; make -C sim pico runs the
firmware. Speed: doc/performance.md.
LUT and FF counts, block RAM in 36 Kb blocks, after place and route. The core is the DUT alone; the design adds the harness and the memory behind it (block RAM, or the board's memory controller). The DRAM design includes it.
| Target | Clock | Core LUT / FF / BRAM / DSP | Design LUT / FF / BRAM / DSP |
|---|---|---|---|
digilent/arty-a7-35 |
40 MHz | 7,004 / 9,680 / 0 / 0 | 7,488 / 10,161 / 32 / 0 |
digilent/pynq-z1 |
40 MHz | 7,007 / 9,680 / 0 / 0 | 7,489 / 10,161 / 32 / 0 |
xilinx/vcu118 |
40 MHz | 6,988 / 9,678 / 0 / 0 | 7,468 / 10,159 / 32 / 0 |
digilent/arty-a7-35, DRAM (Harness.dram.toml) |
40 MHz | 6,542 / 6,476 / 0 / 0 | 12,905 / 11,774 / 16 / 0 |
rtl/rice_top.veryl, Harness.toml |
the DUT with two block RAMs, and where each port goes |
rtl/rice_mem_top.veryl, Harness.dram.toml |
the DUT with FPGA memory and the DRAM in one address space |
bsp/, apps/ |
the Rust firmware |
picoruby/ |
mruby/c firmware |
asm/, sim/ |
the test programs, and the DUTs in Verilator |
Put paths for your machine in local.mk; see Makefile.
MIT (LICENSE).