blueflare/bfe-core1106-sdk
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

qemu: start every panel daemon, and keep Modbus off the control channel

Browse Source 
Stage-2 init started only warden-flared and warden-modbus from the
payload, so every daemon-backed screen (Automation, MikroTik, Mining,
RS485, Starlink, Services) sat in its "not running" state on the rig
while the bench panel showed the daemons up with nothing attached. It now
starts every warden-* daemon it finds in the panel's own S-number order
(ai, automation, modbus, mikrotik, asic, starlink, stratum, flared), each
with no arguments as start-stop-daemon runs them on the panel. flare-edge
tools/rig-pull-daemons.sh copies a panel's static binaries in.

Doing that exposed a latent alias: init pointed warden-modbus's /dev/ttyS4
at /dev/ttyS0 whenever ttyS0 existed, and with --ctl that port IS the
control channel, so Modbus polls arrived inside the wake reply and the
bridge hung. run.sh now always attaches an RS485 pci-serial (a null
chardev without --rs485), and init aliases ttyS4 to ttyS1 when warden.ctl
is on the cmdline, ttyS0 otherwise.

Verified on a boot with all eight daemons: status json reports
automation.engine, mikrotik.backend, mining.available and rs485.available
true with the Modbus scan sweeping the empty UART; six daemon-backed pages
matched screenshots of the bench panel structurally (0/256 cells differ).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013aHKWzT5EF86RFKRMtAv9n
This commit is contained in:
Noah
2026-09-08 00:47:08 -06:00
co-authored by Claude Fable 5.1
parent eb16a301c0
commit 9b6428db47
4 changed files with 50 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qemu/README.md
+9 -3
View File
@@ -63,9 +63,15 @@ bash qemu/run.sh --kernel $HOME/kbuild-out/linux-6.18.46/arch/arm/boot/zImage --
```
Payload: drop static musl armv7 binaries into `qemu/payload/` (see its
README); `warden-flared`, `warden-modbus`, and `warden-ui` (the LVGL
fbdev+evdev build from flare-edge `tools/build-ui-vm.sh`) are started by
stage-2 init when present.
README). Stage-2 init starts every panel daemon it finds, in the panel's own
S-number order (`warden-ai`, `warden-automation`, `warden-modbus`,
`warden-mikrotik`, `warden-asic`, `warden-starlink`, `warden-stratum`,
`warden-flared`), then `warden-ui` (the LVGL fbdev+evdev build from
flare-edge `tools/build-ui-vm.sh`). The quickest faithful payload is the
daemons a bench panel already runs: flare-edge `tools/rig-pull-daemons.sh
--host <panel>` copies them in. The RS485 UART is always present (a null
chardev without `--rs485`), so `warden-modbus` polls a port with nothing on
it, as on a panel with an empty header, and never the control channel.
The VT cursor is kept off (`vt.global_cursor_default=0`): fbcon shares the
virtio-gpu framebuffer with warden-ui and its blinking cursor would otherwise