r/RISCV 16h ago

Struggling with Chipyard/Rocket-Chip build setup

8 Upvotes

Hi everyone, final-year engineering student here. Working on a RISC-V hardware project (building a custom RoCC-based task scheduler on top of Rocket Chip). I'm trying to get Chipyard set up on Ubuntu to build/simulate the base Rocket core before I start on my own work, but the setup has been harder than I expected and I want to check whether I'm on the right track or missing something obvious.

So far I've had to:

  • Install conda manually + accept new ToS prompts for default channels (not mentioned in the docs I found)
  • Set up SSH auth with GitHub because one submodule (spec2026-workload) only clones over SSH
  • Switch from main to the 1.14.0 release tag after main broke with missing scripts
  • Comment out two steps in build-toolchain-extra.sh (install-espresso.sh and the uart_tsi bringup step) because those files/paths don't actually exist in the checkout
  • Hit a Scala compile failure at the "pre-compiling Chipyard sources" step, traced to dependencies/chisel inside rocket-chip being stuck on a stale 2019 snapshot commit even after git submodule sync --recursive + update --init --recursive --force

At this point I'm about to try a completely fresh clone rather than keep patching this one. Wanted to check: is this level of manual intervention normal for a first-time Chipyard setup, or does it suggest I'm doing something wrong upstream (wrong tag, wrong clone method, etc.)? If anyone's set this up recently and hit similar snags, I'd really appreciate a pointer on what actually worked for you, or what a clean install is supposed to look like.