Skip to content

luckfox: UART console off by default, seedsigner-os images always dev, dev levers in file names - #144

Merged
3rdIteration merged 2 commits into
mainfrom
luckfox-uart-default-off-and-dev-tags
Oct 23, 2026
Merged

3rdIteration merged 2 commits into
mainfrom
luckfox-uart-default-off-and-dev-tags

Conversation

@3rdIteration

Copy link
Copy Markdown
Owner

Why

A user's Luckfox Pico showed the secure-boot screen and never reached SeedSigner. I unpacked their two card dumps (HDD Raw Copy .imgc):

  • B13 card: a byte-exact copy of the seedsigner-os SeSi-0.8.7+ShSi-B13-pre release image …-mini-sd-SeSi-0.8.7_ShSi-B13-pre-osproduction-signed-devkey.img (sha256 91e6b65d…). The app repo release has the same file name with different contents (efd3a910…), and that one boots.
  • B12 card: also a seedsigner-os -pre release image (63c1a1a4…).
  • Both have earlycon=… console=ttyFIQ0 in boot.img. The B13-pre release run was build_variant=non-dev with disable_uart2_console_debug=false, so the console was on while the name said osproduction. The card data itself was intact.

Changes

  1. Serial console stripped by default on every variant (os-build.sh resolve_uart2_console): auto used to keep it on dev builds, and those don't boot through to the app. Only an explicit false keeps it now. build-local.sh already defaulted to stripped.
  2. seedsigner-os builds are always dev (build-luckfox.yml): forced whenever github.repository ends in /seedsigner-os, and the dispatch form no longer offers build_variant. Inside a workflow_call, github.repository is the caller, so the app repo's production builds (which pass build_variant: non-dev) are unaffected.
  3. Dev levers in artifact names: a new shared opt/luckfox/artifact-tag.sh is used by both os-build.sh and build-local.sh, so the two can't drift. Format: <appref>-os<develop|production>[-dev-<lever>...]-<signing>.
    • -dev-uart and -dev-testing on any variant
    • -dev-adb, -dev-otg, -dev-net, -dev-rw, -dev-bootlog, -dev-adbfiles on production builds whose levers are off their production defaults
    • clean production names are unchanged (e.g. SeSi-0.8.7_ShSi-B13-osproduction-signed-devkey)
  4. Docs (docs/luckfox/README.md): the variant policy, an artifact-name table, and a new Troubleshooting section:
    • stuck on the secure-boot screen → a UART/dev image; check the name and the SHA-256 against the app release
    • SocToolKit shows no Maskrom/Loader device → install RK Driver Assistant per the Luckfox wiki, restart, run as admin

Testing

  • bash tests/test_luckfox_artifact_tag.sh: all cases pass, including the B13-pre case, which now yields …-osproduction-dev-uart-signed-devkey.
  • bash -n on every changed script; the workflow YAML parses.
  • Not yet verified by a full build. This PR's Luckfox CI run will be the first build with the console stripped on a dev image; check its artifact names and that the boot.img cmdline has no console=ttyFIQ0.

Follow-up (not in this PR)

The existing seedsigner-os releases (B12-pre, B13-pre, …) still carry the misleading names. Consider renaming or removing those assets, or adding a warning to their release notes.

🤖 Generated with Claude Code

3rdIteration and others added 2 commits October 12, 2026 11:07
…, tag dev levers in names

A user's Pico showed the secure-boot screen and never reached the app. Their
card was a byte-exact copy of the seedsigner-os SeSi-0.8.7+ShSi-B13-pre release
image: a non-dev build with disable_uart2_console_debug=false. It was named
"...-osproduction-signed-devkey", identical to the app repo's working release
image, so nothing told the two apart.

- os-build.sh: disable_uart2_console_debug=auto now strips the serial console
  on every variant (it used to keep it on dev). Only an explicit false keeps it.
  build-local.sh already defaulted to stripped.
- build-luckfox.yml: runs in */seedsigner-os always build dev, and the dispatch
  form drops build_variant. Production images come from the app repo via
  workflow_call, where github.repository is the caller, so it is unaffected.
- New opt/luckfox/artifact-tag.sh, shared by os-build.sh and build-local.sh.
  It adds -dev-uart / -dev-testing on any variant, plus -dev-adb, -dev-otg,
  -dev-net, -dev-rw, -dev-bootlog and -dev-adbfiles on a production build.
  Clean production names are unchanged.
- docs/luckfox/README.md: the variant policy, an artifact-name table, and a
  Troubleshooting section (stuck on the secure-boot screen; no
  Maskrom/Loader device in SocToolKit -> install RK Driver Assistant).
- tests/test_luckfox_artifact_tag.sh covers the naming rules.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Resolve conflicts with #138, which landed the same UART default independently
(console + FIQ debugger stripped on every variant). Main's
resolve_uart2_console() and its wording win: only false/0 keeps the console
and anything else strips it, which fails safe. Added on top: the
-dev-uart artifact tag, the note that a console-on Pico stalls after the
secure-boot screen, and seedsigner-os builds being forced to dev (so main's
reworded build_variant dispatch input stays removed).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@3rdIteration
3rdIteration merged commit 8483af5 into main Oct 23, 2026
12 checks passed
@3rdIteration
3rdIteration deleted the luckfox-uart-default-off-and-dev-tags branch October 23, 2026 01:48
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.

1 participant