Pin forgectrl on the gate that waits for the enclosure; add its test

forgectrl now holds the motion check while a lid or the interlock is
open instead of starting the controller unverified: GET /mode reports
controller "waiting" with why, the button blinks amber, and the check
runs when the enclosure closes. motion.gate-waits-for-lid drives the
fixture's lid channel: the lid opens, forgectrl restarts, /mode must
read waiting with why naming the lid, no pid, motion unverified, the
button amber (sampled over a blink period: the smooth trigger's target
reads 0 through the off half) and no probe line in the log; the lid
closes, and the controller must come up verified with MOTION OK on the
first probe.

Proven on the bench reference: PASS, the controller verified 6.5 s
after the lid closed.
This commit is contained in:
ScottW514
2026-09-09 11:03:33 -04:00
parent 8af8b197ee
commit 4a95595afd
2 changed files with 116 additions and 2 deletions
@@ -2,5 +2,5 @@
# only SRCREV and PV here - the image manifest leaves *-pin.inc out of the
# layer content hash because the component entry already identifies the
# pinned source (forgefirm-image-manifest.bbclass).
SRCREV = "6040e64a388005761d7598a5edbc46e55d38af76"
PV = "0.1.9"
SRCREV = "7e03073863c63b93da6281d318eb25dc3e822f2c"
PV = "0.1.10"