Skip to content

Development Cycle Speedrun ‐ 11th of October

Amund Bergland Kvalsvik edited this page Oct 11, 2023 · 2 revisions

This is a guide for getting started with the latest version of chipyard as we best know for use on the IDUN-cluster.

Downloading and getting started

You want to do this on a dedicated node and not on a log-in node.

salloc --nodes=1 --exclusive --partition=CPUQ --account=ie-idi --time=1000:00:00

ssh idun-<allocated-node>

Start by cloning the git-repository It is recommended to use ssh keys for this as this will allow you to push automatically later

git clone [email protected]:EECS-NTNU/chipyard.git

Then, install conda-lock through the pip environment // Ensure that version is 3

python --version

python -m pip install conda-lock

At this point you should be able to install chipyard. // This is going to take an hour

cd chipyard

// Most recent as of now - tea

git checkout <branch-you-want>

./build-setup.sh riscv-tools

This will setup chipyard. Afterwards, go to generators/boom and sims/firesim and change to the appropriate branch. For boom this is most recently tracedoctor, or shadow-binding depending on your project

cd generators/boom

git checkout tea

cd ../../sims/firesim

git checkout tracedoctor

Then, setup firesim so that it knows it is a submodule under chipyard

cd ~/chipyard

./scripts/firesim-setup.sh

To run a binary with medium boom config:

make run-binary-debug -j10 VERILATOR_THREADS=10 VERILATOR_FST_MODE=1 BINARY=<PATH/TO/BINARY> LOADMEM=<PATH/TO/BINARY> CONFIG=MediumBoomConfig

To run with firesim, see u250 page.

Clone this wiki locally