This repository houses a set of RISCV tools for the CVA6 core. Most importantly it does not contain openOCD.
Included tools:
- Spike, the ISA simulator
- riscv-tests, a battery of ISA-level tests
- riscv-pk, which contains
bbl, a boot loader for Linux and similar OS kernels, andpk, a proxy kernel that services system calls for a target-machine application by forwarding them to the host machine - riscv-fesvr, the host side of a simulation tether that services system calls on behalf of a target machine
Requirements Ubuntu:
$ sudo apt-get install autoconf automake autotools-dev curl libmpc-dev libmpfr-dev libgmp-dev libusb-1.0-0-dev gawk build-essential bison flex texinfo gperf libtool patchutils bc zlib1g-dev device-tree-compiler pkg-config libexpat-devRequirements Fedora:
$ sudo dnf install autoconf automake @development-tools curl dtc libmpc-devel mpfr-devel gmp-devel libusb-devel gawk gcc-c++ bison flex texinfo gperf libtool patchutils bc zlib-devel expat-develYou can select the XLEN by setting it in the Makefile. Then compile the Linux images with
$ git submodule update --init --recursive
$ make imagesIf you want to cross compile other projects for this target you can add buildroot/output/host/bin/ to your path in order to later make use of the installed tools after compiling them with :
$ make allYou can also build a compatible linux image with bbl that boots linux on the CVA6 fpga mapping:
$ make vmlinux # make only the vmlinux image
# outputs a vmlinux file in the top directory
$ make bbl.bin # generate the entire bootable image
# outputs bbl and bbl.bin
$ make images # generates all images and save them in install$(XLEN)
# outputs install$(XLEN)/vmlinux, install$(XLEN)/bbl and install$(XLEN)/bbl.binYou can test your image on spike
$ $(RISCV)/bin/spike bblSpike allows trace logging
$ $(RISCV)/bin/spike --log-commits bbl 2> trace.log.commitsThe bootloader of CVA6 requires a GPT partition table so you first have to create one with gdisk.
$ sudo fdisk -l # search for the corresponding disk label (e.g. /dev/sdb)
$ sudo sgdisk --clear --new=1:2048:67583 --new=2 --typecode=1:3000 --typecode=2:8300 /dev/sdb # create a new gpt partition table and two partitions: 1st partition: 32mb (ONIE boot), second partition: rest (Linux root)Now you have to compile the linux kernel:
$ make bbl.bin # generate the entire bootable imageThen the bbl+linux kernel image can get copied to the sd card with dd. Careful: use the same disk label that you found before with fdisk -l but with a 1 in the end, e.g. /dev/sdb -> /dev/sdb1.
$ sudo dd if=install$(XLEN)/bbl.bin of=/dev/sdb1 status=progress oflag=sync bs=1MSimilar steps as above but flashing is sligthly different. Get sgdisk using homebrew.
$ brew install gptfdisk
$ sudo sgdisk --clear -g --new=1:2048:67583 --new=2 --typecode=1:3000 --typecode=2:8300 /dev/disk2
$ sudo dd if=bbl.bin of=/dev/disk2s1 bs=1m
If you really need and want to debug on an FPGA/ASIC target the installation instructions are here.
This patch incorporates an overlay to overcome the painful delay in generating public/private key pairs on the target (which happens every time because the root filing system is volatile). Do not use these keys on more than one device. Likewise it also incorporates a script (rootfs/etc/init.d/S40fixup) which replaces the MAC address with a valid Digilent value. This should be replaced by the unique value on the back of the Genesys2 board if more than one device is used on the same VLAN. Needless to say both of these values would need regenerating for anything other than development use.
There is a pretty basic Docker container you can use to get a stable build environment to build the image.
$ cd container
$ sudo docker build -t ghcr.io/pulp-platform/ariane-sdk -f Dockerfile .
And build the image:
$ cd ..
$ sudo docker run -it -v `pwd`:/repo -w /repo -u $(id -u ${USER}):$(id -g ${USER}) ghcr.io/pulp-platform/ariane-sdk