Skip to content

Rewrite README with verified build docs (issue #26)#1

Merged
TriplEight merged 2 commits into
devfrom
readme-issue-26
Jun 11, 2026
Merged

Rewrite README with verified build docs (issue #26)#1
TriplEight merged 2 commits into
devfrom
readme-issue-26

Conversation

@TriplEight

@TriplEight TriplEight commented Jun 11, 2026

Copy link
Copy Markdown
Owner

Closes flipperdevices#26

README rewrite with four sections from issue flipperdevices#26. Every build command was run in the repo's own container image before writing it down.

What's in this

  • Four new top-level sections: Repos structure, Automated builds, How to build image manually, How to contribute
  • PR New README flipperdevices/flipperone-linux-build-scripts#27's Supported boards table, with two corrected target names (roc-pc not rock-pc, evb not evb1)
  • Dockerfile fix: stale WORKDIR and clone URL pointed at rk3576-linux-build (old repo name) instead of flipperone-linux-build-scripts. HTTP 301 redirect kept builds working but the container's working directory had the wrong name.

Build runs

All commands verified in podman run --privileged -v $PWD/out:/artifacts against the repo's own container image:

Script Result
build-uboot.sh pass - all 8 boards
build-kernel-mainline.sh pass - Linux 7.1.0-rc6 arm64, ~1h35m
build-kernel-bsp.sh pass when run alone; fails if run in parallel with mainline (both scripts write to the same prebuilt/linux/ by default and the final mv step conflicts)
build-images.sh pass - debos KVM fakemachine, debian-512-*-20260611-1448.img.gz for all 8 boards
dep list pass - derived from Dockerfile

Corrections from build runs

  • Loader filename in Maskrom section was rk3576_spl_loader_*.bin - no such file exists; actual filename is rk3576_loader_v*.bin
  • Image filename format was debian-<board>.img.gz; actual format is debian-512-<board>-<timestamp>.img.gz
  • Dep list was missing 7 packages (qemu-user-binfmt, device-tree-compiler, mmdebstrap, systemd-container, libglib2.0-dev, libostree-dev, fakemachine); gdown/repo are not in trixie apt and were removed; apt install -t testing debos replaced with go install
  • Flash commands used container output paths (out/u-boot/, out/images/); manual builds use prebuilt/u-boot/ and out/ (the script defaults)
  • pipx install --global needs sudo on a non-root install (writes to /opt/pipx and /usr/local/bin)

Add four sections required by issue flipperdevices#26: Repos structure, Automated
builds, How to build image manually, How to contribute.

Every documented build command was verified inside the repo's own
container image (localhost/fobl built from the Dockerfile):
- build-uboot.sh: PASS — all 8 boards from flipperdevices/u-boot rk3576
- build-kernel-mainline.sh: PASS — Linux 7.1.0-rc6 arm64 .deb packages
- build-kernel-bsp.sh: FAIL when run in parallel with mainline (mv
  cross-fs conflict); note added to not run builds in parallel
- build-images.sh: PASS — debian-512-*-20260611-1448.img.gz produced
  for all 8 boards via debos fakemachine (KVM)

Fixes from build verification:
- Correct loader filename: rk3576_loader_v*.bin (not rk3576_spl_loader)
- Correct image filename format: debian-512-<board>-<timestamp>.img.gz
- Correct dep list: add 7 packages missing from old README; remove
  gdown/repo (not in trixie); use go install for debos (not apt)
- Fold in PR flipperdevices#27 boards table with corrected target names:
  roc-pc (not rock-pc), evb (not evb1)
- Preserve original SD card warning, Maskrom/Rockusb flashing prose

Dockerfile fix: correct stale WORKDIR and clone URL from rk3576-linux-build
to flipperone-linux-build-scripts (justified by container-quickstart build).
Flashing commands were using container output paths (out/u-boot/,
out/images/) in the manual build section. Manual builds default to
prebuilt/u-boot/ for bootloaders and out/ for disk images. Also add
missing sudo to pipx install --global, which requires root on a
non-root system install.
@TriplEight TriplEight merged commit 651dc47 into dev Jun 11, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

README for main repo

1 participant