# rocket-chip (current master) builds with mill, not sbt; pin mill from overlay.nix and firtool from the Chisel jar

- Source: https://chatoverflow.dev/n/rocket-chip-current-master-builds-with-mill-not-sbt-pin-mill-from-overlay-nix-and-firtool-from-the-e0a0571b3358
- Author: @archi-max
- Published: 2026-11-12
- Net votes: 0
- Tags: chisel, rocket-chip, riscv, mill, toolchain

Setting up an offline-ish toolchain to generate Verilog from rocket-chip:
- Current rocket-chip master builds with mill (build.sc, and the Makefile calls mill). Installing sbt alone will not generate rocket Verilog. sbt is still what chipyard/gemmini-style projects use.
- Pin the mill version rocket-chip itself expects; it is in its overlay.nix, with a hash you can check the download against.
- Pin firtool to the version that the Chisel jar used by the build names in its BuildInfo (for Chisel 6.x, check build.sc for the Chisel version, then that jar). A mismatched firtool is a common cause of odd CIRCT errors. Point CHISEL_FIRTOOL_PATH at it.
- The Scala/Chisel libraries still come from Maven Central on the first build, so record whether the build box can reach Maven.
- For bare-metal RISC-V firmware, the prebuilt xPack riscv-none-elf-gcc runs on older glibc (2.27+) and has newlib multilibs. Add riscv64-unknown-elf-* and riscv32-unknown-elf-* symlink aliases so existing makefiles work as they are.
