infra(toolchain): install Scala/Chisel/Chipyard 1.13.0 on agent host #59

Merged
navigator merged 1 commit from auto/issue-46-20260525T174915Z_issue46 into main 2026-05-25 16:22:04 -03:00
Owner

Summary

Brings the Scala / Chisel / Chipyard toolchain up on the agent host
(navigator@2804:710:d0:5::a6e, Debian 13, 24 cores, 50 GiB), pins
Chipyard 1.13.0 at commit 69eba860a352343e4ac6b6df0f3638a79a86ec78
in rtl/chipyard.hash, and records the exact install commands +
observed tool versions in docs/dev/toolchain-install.md.

The original PLAN.md §5.1 CT 250 / LXC path is superseded: per the
recent host migration this workstation is the development machine and
the toolchain installs directly under ~.

Deviations from PLAN.md §5.2 (documented in the new doc)

  • Debian 13 trixie ships no openjdk-17-jdk-headless; substituted
    OpenJDK 21 (LTS, sbt 1.9+ and Chipyard 1.13.0 both support it).
  • §5.2 plans a from-source Verilator build at v5.024; trixie's apt
    Verilator is 5.032, which already clears the ≥ 5.012 floor, so
    the source build is unnecessary on this host.
  • build-setup.sh needs conda / mamba; Miniforge3 24.11.0 is
    installed into ~/miniforge3 and conda init bash wires it for
    future shells.

Observed on this install

Tool Version observed
OpenJDK 21.0.11 (Debian build, headless)
sbt (runner) 1.12.11
Verilator 5.032
Miniforge conda 24.11.0 + mamba 1.5.11
Chipyard 1.13.0 @ 69eba86
riscv64-elf-gcc 13.2.0 (in ~/chipyard/.conda-env/riscv-tools)
Spike 1.1.1-dev
  • ./build-setup.sh riscv-tools ran clean end-to-end (~67 min wall
    time on a cold clone, 11 steps, "Setup complete!" terminal marker).
  • source env.sh && cd sims/verilator && make -j8 built the stock
    RocketConfig simulator in ~5 min, producing
    simulator-chipyard.harness-RocketConfig (~11 MiB) — the binary
    prints its --help text correctly.

Disk

  • Pre-install: 43 GiB free on /.
  • Post-install: 8.9 GiB free (above the 8 GiB abort threshold).
  • ~/chipyard/ total 29 GiB, of which .conda-env/ is 17 GiB.

The host is tight but viable for further RTL work. Future custom
builds (GemminiRocketConfig, PopSolutions modules) will need a
resize before they fit comfortably; an area:infra follow-up is
worth filing if disk pressure becomes a recurring failure mode.

Files

  • rtl/chipyard.hash — placeholder replaced with the pinned Chipyard
    1.13.0 commit and a short reproduction recipe.
  • docs/dev/toolchain-install.md — new contributor-facing reference
    for area:rtl / area:infra covering all steps, deviations, and
    the smoke test.

Test plan

  • apt install of the §5.2 base packages (with openjdk-21
    substitution) completed without error.
  • sbt --version reports runner 1.12.11 (≥ 1.9).
  • verilator --version reports 5.032 (≥ 5.012).
  • git clone --branch 1.13.0 https://github.com/ucb-bar/chipyard.git
    yields commit 69eba86, recorded in rtl/chipyard.hash.
  • ./build-setup.sh riscv-tools completed end-to-end (~67 min)
    with "Setup complete!" terminal marker.
  • source env.sh && cd sims/verilator && make built a working
    stock RocketConfig simulator.

Closes #46
Closes #2
Closes #3

## Summary Brings the Scala / Chisel / Chipyard toolchain up on the agent host (`navigator@2804:710:d0:5::a6e`, Debian 13, 24 cores, 50 GiB), pins Chipyard `1.13.0` at commit `69eba860a352343e4ac6b6df0f3638a79a86ec78` in `rtl/chipyard.hash`, and records the exact install commands + observed tool versions in `docs/dev/toolchain-install.md`. The original PLAN.md §5.1 CT 250 / LXC path is superseded: per the recent host migration this workstation is the development machine and the toolchain installs directly under `~`. ## Deviations from PLAN.md §5.2 (documented in the new doc) - Debian 13 trixie ships no `openjdk-17-jdk-headless`; substituted **OpenJDK 21** (LTS, sbt 1.9+ and Chipyard 1.13.0 both support it). - §5.2 plans a from-source Verilator build at `v5.024`; trixie's apt Verilator is **5.032**, which already clears the ≥ 5.012 floor, so the source build is unnecessary on this host. - `build-setup.sh` needs `conda` / `mamba`; **Miniforge3 24.11.0** is installed into `~/miniforge3` and `conda init bash` wires it for future shells. ## Observed on this install | Tool | Version observed | |---------------|-----------------------------------------------------| | OpenJDK | 21.0.11 (Debian build, headless) | | sbt (runner) | 1.12.11 | | Verilator | 5.032 | | Miniforge | conda 24.11.0 + mamba 1.5.11 | | Chipyard | 1.13.0 @ `69eba86` | | riscv64-elf-gcc | 13.2.0 (in `~/chipyard/.conda-env/riscv-tools`) | | Spike | 1.1.1-dev | - `./build-setup.sh riscv-tools` ran clean end-to-end (~67 min wall time on a cold clone, 11 steps, "Setup complete!" terminal marker). - `source env.sh && cd sims/verilator && make -j8` built the stock `RocketConfig` simulator in ~5 min, producing `simulator-chipyard.harness-RocketConfig` (~11 MiB) — the binary prints its `--help` text correctly. ## Disk - Pre-install: 43 GiB free on `/`. - Post-install: 8.9 GiB free (above the 8 GiB abort threshold). - `~/chipyard/` total 29 GiB, of which `.conda-env/` is 17 GiB. The host is tight but viable for further RTL work. Future custom builds (`GemminiRocketConfig`, PopSolutions modules) will need a resize before they fit comfortably; an `area:infra` follow-up is worth filing if disk pressure becomes a recurring failure mode. ## Files - `rtl/chipyard.hash` — placeholder replaced with the pinned Chipyard 1.13.0 commit and a short reproduction recipe. - `docs/dev/toolchain-install.md` — new contributor-facing reference for `area:rtl` / `area:infra` covering all steps, deviations, and the smoke test. ## Test plan - [x] `apt install` of the §5.2 base packages (with `openjdk-21` substitution) completed without error. - [x] `sbt --version` reports runner 1.12.11 (≥ 1.9). - [x] `verilator --version` reports 5.032 (≥ 5.012). - [x] `git clone --branch 1.13.0 https://github.com/ucb-bar/chipyard.git` yields commit `69eba86`, recorded in `rtl/chipyard.hash`. - [x] `./build-setup.sh riscv-tools` completed end-to-end (~67 min) with "Setup complete!" terminal marker. - [x] `source env.sh && cd sims/verilator && make` built a working stock `RocketConfig` simulator. Closes #46 Closes #2 Closes #3
infra(toolchain): install Scala/Chisel/Chipyard 1.13.0 on agent host
All checks were successful
build / scalafmt-check (pull_request) Successful in 4s
build / sbt-compile (pull_request) Successful in 3s
build / shell-lint (pull_request) Successful in 20s
6407f1c97b
Pins Chipyard 1.13.0 at commit 69eba860a352343e4ac6b6df0f3638a79a86ec78 in
rtl/chipyard.hash and records the actual install commands + observed tool
versions in docs/dev/toolchain-install.md.

The original CT 250 / LXC path in PLAN.md §5.1 is superseded — the agent
host (2804:710:d0:5::a6e, Debian 13, 24 cores, 50 GiB) is the development
machine and the toolchain installs directly under ~/. Debian 13 trixie has
no openjdk-17-jdk-headless package, so OpenJDK 21 (LTS, JDK-17-compatible
for sbt 1.9+ and Chipyard 1.13.0) is substituted; PLAN.md §5.2's source
verilator build is unnecessary because the apt verilator (5.032) already
clears the >= 5.012 floor.

build-setup.sh riscv-tools completed cleanly (~67 min wall time, ~17 GiB
under .conda-env/) and a stock RocketConfig builds end-to-end under
sims/verilator in ~5 min, producing a working ~11 MiB simulator binary.

Closes #2 (CT 250 install path retired) and #3 (CT-bound install retired).
fluidpop-bot approved these changes 2026-05-25 16:12:42 -03:00
Dismissed
fluidpop-bot left a comment
Collaborator

CI green (head 6407f1c97b), auto-approving

CI green (head 6407f1c97b47bd3026f0e67b504fb1f5b51e5249), auto-approving
fluidpop-bot approved these changes 2026-05-25 16:13:23 -03:00
Dismissed
fluidpop-bot left a comment
Collaborator

CI green (head 6407f1c97b), auto-approving

CI green (head 6407f1c97b47bd3026f0e67b504fb1f5b51e5249), auto-approving
fluidpop-bot approved these changes 2026-05-25 16:14:24 -03:00
Dismissed
fluidpop-bot left a comment
Collaborator

CI green (head 6407f1c97b), auto-approving

CI green (head 6407f1c97b47bd3026f0e67b504fb1f5b51e5249), auto-approving
fluidpop-bot approved these changes 2026-05-25 16:15:26 -03:00
Dismissed
fluidpop-bot left a comment
Collaborator

CI green (head 6407f1c97b), auto-approving

CI green (head 6407f1c97b47bd3026f0e67b504fb1f5b51e5249), auto-approving
fluidpop-bot approved these changes 2026-05-25 16:16:27 -03:00
Dismissed
fluidpop-bot left a comment
Collaborator

CI green (head 6407f1c97b), auto-approving

CI green (head 6407f1c97b47bd3026f0e67b504fb1f5b51e5249), auto-approving
fluidpop-bot approved these changes 2026-05-25 16:17:29 -03:00
Dismissed
fluidpop-bot left a comment
Collaborator

CI green (head 6407f1c97b), auto-approving

CI green (head 6407f1c97b47bd3026f0e67b504fb1f5b51e5249), auto-approving
fluidpop-bot approved these changes 2026-05-25 16:18:30 -03:00
Dismissed
fluidpop-bot left a comment
Collaborator

CI green (head 6407f1c97b), auto-approving

CI green (head 6407f1c97b47bd3026f0e67b504fb1f5b51e5249), auto-approving
fluidpop-bot approved these changes 2026-05-25 16:19:32 -03:00
Dismissed
fluidpop-bot left a comment
Collaborator

CI green (head 6407f1c97b), auto-approving

CI green (head 6407f1c97b47bd3026f0e67b504fb1f5b51e5249), auto-approving
fluidpop-bot approved these changes 2026-05-25 16:20:36 -03:00
Dismissed
fluidpop-bot left a comment
Collaborator

CI green (head 6407f1c97b), auto-approving

CI green (head 6407f1c97b47bd3026f0e67b504fb1f5b51e5249), auto-approving
navigator force-pushed auto/issue-46-20260525T174915Z_issue46 from 6407f1c97b
All checks were successful
build / scalafmt-check (pull_request) Successful in 4s
build / sbt-compile (pull_request) Successful in 3s
build / shell-lint (pull_request) Successful in 20s
to 729adfa161
All checks were successful
build / scalafmt-check (pull_request) Successful in 4s
build / sbt-compile (pull_request) Successful in 4s
build / shell-lint (pull_request) Successful in 12s
2026-05-25 16:21:35 -03:00
Compare
fluidpop-bot left a comment
Collaborator

CI green (head 729adfa161), auto-approving

CI green (head 729adfa161d43b5f16a7da813fbe7b99d36cf760), auto-approving
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Fluid/fluidpop-v1!59
No description provided.