infra: install Scala/Chisel/Chipyard toolchain on agent host

navigator commented

2026-05-25 14:34:42 -03:00

Owner

Goal

Install the Scala/sbt/Chisel/Chipyard toolchain directly on the agent host (Debian 13 KVM, 24 GiB RAM, 24 cores, IPv6 2804:710:d0:5::a6e). Supersedes the original CT 250 path — per recent direction, no dedicated LXC; this host is the development machine.

Acceptance criteria

apt install complete for: build-essential openjdk-17-jdk-headless verilator git curl cmake ninja-build zsh tmux htop
sbt installed via scalasbt repo, sbt --version ≥ 1.9
verilator --version ≥ 5.012 (build from source v5.024 if apt is older)
Chipyard 1.13.0 cloned under ~/chipyard/ with commit hash pinned in rtl/chipyard.hash (replace the placeholder)
./build-setup.sh riscv-tools run successfully (1-3h, ~15 GB) — toolchain under ~/chipyard/.conda-env/
source env.sh && cd sims/verilator && make green on a stock RocketConfig
PR updates rtl/chipyard.hash and adds a short docs/dev/toolchain-install.md recording commands + versions actually run

Notes

Disk budget: this host has 43 GiB free; Chipyard ~15 GiB plus toolchain ~10 GiB → tight but fits. If df -h / drops below 8 GiB during build, abort and request resize.
Long-running resolver run expected (1-3h). If the dispatcher's default timeout aborts, raise the limit for this single issue via env override or split the install into stages.
Closes #2 (CT 250 no longer needed) and #3 (CT-bound install superseded).

Plan ref

PLAN.md §5.2 (toolchain install steps).

## Goal Install the Scala/sbt/Chisel/Chipyard toolchain directly on the agent host (Debian 13 KVM, 24 GiB RAM, 24 cores, IPv6 `2804:710:d0:5::a6e`). Supersedes the original CT 250 path — per recent direction, no dedicated LXC; this host is the development machine. ## Acceptance criteria - [ ] `apt install` complete for: `build-essential openjdk-17-jdk-headless verilator git curl cmake ninja-build zsh tmux htop` - [ ] `sbt` installed via scalasbt repo, `sbt --version` ≥ 1.9 - [ ] `verilator --version` ≥ 5.012 (build from source v5.024 if apt is older) - [ ] Chipyard 1.13.0 cloned under `~/chipyard/` with commit hash pinned in `rtl/chipyard.hash` (replace the placeholder) - [ ] `./build-setup.sh riscv-tools` run successfully (1-3h, ~15 GB) — toolchain under `~/chipyard/.conda-env/` - [ ] `source env.sh && cd sims/verilator && make` green on a stock `RocketConfig` - [ ] PR updates `rtl/chipyard.hash` and adds a short `docs/dev/toolchain-install.md` recording commands + versions actually run ## Notes - Disk budget: this host has 43 GiB free; Chipyard ~15 GiB plus toolchain ~10 GiB → tight but fits. If `df -h /` drops below 8 GiB during build, abort and request resize. - Long-running resolver run expected (1-3h). If the dispatcher's default timeout aborts, raise the limit for this single issue via env override or split the install into stages. - Closes #2 (CT 250 no longer needed) and #3 (CT-bound install superseded). ## Plan ref PLAN.md §5.2 (toolchain install steps).