The critical tier proven on a rising loop; the board temperatures watched

mirror of https://github.com/openglow-org/forgefirm.git synced 2026-09-27 08:41:13 -07:00

forgectrl pin 76115fd: the chassis LM75 and the supply sensor ride /status
as temps (degrees and a raw count), the engine ranges them over every run
session into one run-end line, and a critical fault that clears with its
session yields the reason to the standing hold.

Bench: critical_tier_drill.py (a bench tool now, registered as
critical-tier) sets the ceiling, the resume gate and the critical line a
few tenths above the live upstream reading and lets the engine's own
flow-check heater warm the loop through them inside one M8 session;
temp_calibrate.py gains supply-watch, supply-point and supply-fit for the
supply sensor against a thermometer on its heatsink, the fit shown beside
UAPI.md's unverified guess.

Catalog: cooling.gate-off checks the /status temps fields and the run-end
board-temperature line (the unit fake mirrors both, one new failure
case); cooling.critical-tier checks the reason after a faulted session.

Docs: CAMPAIGN-LOG entries for cooling.critical-tier on dev image
20260822154257 and the warm-loop drill (OVERTEMP at 10 s, CRITICAL at
14 s, the fault ending with the session); BRINGUP item 19, the facts bank
(board temperatures at idle), COOLING section 9, the bench README.

This commit is contained in:

ScottW514

2026-08-22 12:56:40 -04:00

parent f51140e528

commit 9fae47cf14

10 changed files with 372 additions and 9 deletions

									
										meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc
									
		+1
		-1
	
												View File
												
				@@ -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 = "a1875a8113b45c42e252caa3e4b409c1ba4b39fe"

				SRCREV = "76115fd87d0b085cd087a59ae0d58213007c42bf"

				PV = "0.1.0"