For the sake of simplicity, in this tutorial, we refer to the Rocket chip extended with the hypervisor extensions as Rocket-H.
For all software (except Linux) you should use the riscv64-unkowen-elf- gcc 8.3.0 2020.04.0.
You can donwload from:
Specifically for building linux, we recommend to use a different toolchain: riscv64-linux- gcc version 9.3.0 2020.02-2
You can downloaded from:
Setup ARCH and your RISC-V toolchain prefix:
export ARCH=riscv
export CROSS_COMPILE=toolchain-prefix-
Repeat these steps every time you start a new terminal.
For the remaining of this tutorial, for every path starting with /path/to/, please replace by the corresponding absolute path on your machine.
Download and build the bare-metal guest:
git clone https://github.com/bao-project/bao-baremetal-guest
cd bao-baremetal-guest
git checkout rocket
make PLATFORM=rocket-firesim
Note: The following steps shall be done using the riscv64-linux- toolchain.
Clone Linux, defconfig and apply sifive uart patch:
git clone https://github.com/torvalds/linux.git --depth 1 --branch=v5.9 linux-5.9
cd linux-5.9
make defconfig
git apply /path/to/patches/0001-force-sifive-uart-config.patch
Enable the following configs in make menuconfig:
- SERIAL_SIFIVE (Device Drivers -> Character devices -> Serial drivers -> SiFive UART support)
- SERIAL_SIFIVE_CONSOLE (Device Drivers -> Character devices -> Serial drivers -> SiFive UART support -> Console on SiFive UART)
- HVC_RISCV_SBI (Device Drivers -> Character devices -> RISC-V SBI console support)
- set INITRAMFS_SOURCE to /path/to/linux/initramfs.cpio (General Setup -> Initial RAM filesystem and RAM disk (initramfs/initrd) support)
Note: You can search for symbols using the character '/' and jump directly into the option by using the numbers (e.g., 1, 2, ...)
Build Linux:
make -j$(nproc)
Build the device tree:
cd /path/to/this/repo/linux
dtc rocket-firesim-minimal.dts > rocket-firesim-minimal.dtb
Note: The following steps shall be done using the riscv64-unkowen-elf- toolchain.
And build the final guest images by concatening the minimal bootloader, linux and device tree binaries:
cd /path/to/this/repo/linux/lloader
make ARCH=rv64 IMAGE=/path/to/linux-5.9/arch/riscv/boot/Image DTB=/path/to/this/repo/linux/rocket-firesim-minimal.dtb TARGET=linux-rv64-rocket-firesim
Download opensbi and checkout the firesim branch:
git clone https://github.com/josecm/opensbi.git
cd opensbi
git checkout josecm/rocket
Note: OpenSBI will be compiled at later stage.
Clone Bao and checkout the RISC-V branch with support for rocket-chip:
git clone https://github.com/bao-project/bao-hypervisor
cd bao-hypervisor
git checkout wip/riscv-rocket
Copy the provided external tools to the bao-hypervisor dir:
cp -r /path/to/this/repo/bao/tools .
Copy the provided configs to bao's directory:
cp -r /path/to/this/repo/linux/bao/configs .
For the target configuration file (configs/xxxconfig/config.c), setup the absolute path for the VM image.
For example, for running Linux as VM:
VM_IMAGE(linux_image, /path/to/linux/lloader/linux-rv64-rocket-firesim.bin);
Build the system image:
cd /path/to/bao-hypervisor
make -C tools/firesim CONFIG=rocket-firesim-xxx
At this stage, the final system image is ready to be sent to the AWS machine (FireSim).
Note: There is a public afi for "our" Rocket-H design.
In case the public afi is used (see details below), please jump directly to Step 3 "Running your Rocket-H simulation"
[firesim-rocket-h-quadcore-no-nic-l2-llc4mb-ddr3]
agfi=agfi-0fc72a5b136b0f1e7
deploytripletoverride=None
customruntimeconfig=None
For FireSim Initial Setup/Installation please refer to the FireSim documentation:
https://docs.fires.im/en/latest/Initial-Setup/index.html
Note: While selecting the AMI, you can use the FPGA Developer AMI - 1.6.1
On your AWS machine, add our rocket-chip design:
cd firesim/target-design/chipyard/generators/rocket-chip/
git remote add josecm https://github.com/josecm/rocket-chip.git
git fetch josecm
git checkout hyp
Note: You should install nano (or other editor) on your AWS machine to perform the following steps
sudo yum install nano
Edit the 'parameters.scala' file to include the useHype parameter:
firesim/target-design/chipyard/generators/boom/src/main/scala/common/parameters.scala
useSupervisor: Boolean = false,
useHype: Boolean = false,
useVM: Boolean = true,
Edit the 'ArianeTile.scala' file to include the useHype parameter:
firesim/target-design/chipyard/generators/ariane/src/main/scala/ArianeTile.scala
'val useSupervisor: Boolean = false'
'val useHype: Boolean = false'
'val useDebug: Boolean = true'
Edit the 'RocketConfigs.scala' file to define the QuadRocketHypConfig class:
firesim/target-design/chipyard/generators/chipyard/src/main/scala/config/RocketConfigs.scala
class QuadRocketHypConfig extends Config(
new freechips.rocketchip.subsystem.WithHyp ++
new QuadRocketConfig)
Note: As a sugestion, add the class at the top of the file
Edit the 'TargetConfigs.scala' file to include the QuadRocketHypConfig class:
firesim/target-design/chipyard/generators/firechip/src/main/scala/TargetConfigs.scala
class FireSimQuadRocketHypConfig extends Config(
new WithDefaultFireSimBridges ++
new WithDefaultMemModel ++
new WithFireSimConfigTweaks ++
new chipyard.QuadRocketHypConfig)
Note: As a sugestion, add the class after the definition of the FireSimQuadRocketConfig class
Edit the build configuration, per instructions described in FireSim documentation:
firesim/deploy/config_build.ini
https://docs.fires.im/en/latest/Building-a-FireSim-AFI.html
Edit the build recipe file to include the Rocket-H configuration:
firesim/deploy/config_build_recipes.ini
# Quad-core, Rocket-based recipes
[firesim-rocket-quadcore-nic-l2-llc4mb-ddr3]
DESIGN=FireSim
TARGET_CONFIG=WithNIC_DDR3FRFCFSLLC4MB_FireSimQuadRocketConfig
PLATFORM_CONFIG=F90MHz_BaseF1Config
instancetype=z1d.2xlarge
deploytriplet=None
[firesim-rocket-quadcore-no-nic-l2-llc4mb-ddr3]
DESIGN=FireSim
TARGET_CONFIG=DDR3FRFCFSLLC4MB_FireSimQuadRocketConfig
PLATFORM_CONFIG=F90MHz_BaseF1Config
instancetype=z1d.2xlarge
deploytriplet=None
[firesim-rocket-h-quadcore-no-nic-l2-llc4mb-ddr3]
DESIGN=FireSim
TARGET_CONFIG=DDR3FRFCFSLLC4MB_FireSimQuadRocketHypConfig
PLATFORM_CONFIG=F90MHz_BaseF1Config
instancetype=z1d.2xlarge
deploytriplet=None
Edit the build file to include the Rocket-H configuration:
firesim/deploy/config_build.ini
[builds]
# this section references builds defined in config_build_recipes.ini
# if you add a build here, it will be built when you run buildafi
#firesim-rocket-quadcore-nic-l2-llc4mb-ddr3
#firesim-rocket-quadcore-no-nic-l2-llc4mb-ddr3
#firesim-boom-singlecore-no-nic-l2-llc4mb-ddr3
#firesim-boom-singlecore-nic-l2-llc4mb-ddr3
firesim-rocket-h-quadcore-no-nic-l2-llc4mb-ddr3
firesim buildafi
Note: Depending on your AWS instance resources, the build can take around 5-6 hours (i.e., c4.4xlarge)
In ~/firesim/deploy/workloads create a bao directory and a bao.json file with the following content:
{
"benchmark_name" : "bao",
"common_bootbinary" : "bao_rocket-firesim-xxx.elf",
"common_rootfs" : "dummy.rootfs",
"common_simulation_outputs" : ["uartlog"]
}
Upload the dummy.rootfs and the final bao binary built in step 1.5 (named /path/to/bao-hypervisor/tools/firesim/images/bao-rocket-firesim_rocket-firesim-xxx.elf) to ~/firesim/deploy/workloads/bao in the aws machine.
Finally, please refer to the FireSim documentation "Running FireSim Single Node Simulations" (https://docs.fires.im/en/latest/Running-Simulations-Tutorial/Running-a-Single-Node-Simulation.html) to run the simulation. You'll just need to adapt the defaulthwconfig and workload fields in config_runtime.ini:
defaulthwconfig=firesim-rocket-h-quadcore-no-nic-l2-llc4mb-ddr3
...
workloadname=bao.json