mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-09-27 08:41:13 -07:00
An ESP32-S3 DevKitC-1 on the bench network drives three relays at the machine's connectors so the acceptance tool can open the lid loop, pull the interlock loop and press the button with nobody in the room. Two contacts are normally closed in loops the safety chain already reads, the third is normally open across the button input and only ever pulsed (20 to 500 ms, the end armed before the line rises); every line is low at boot and after any reset, the task watchdog panics and reboots, and the button channel needs a jumper. HTTP on port 80 under a key in X-Fixture-Key; the hostname announced over DHCP and mDNS. ESP-IDF v5.5 native, the mDNS component pinned in dependencies.lock; fixture.env (git-ignored) is the one input: the wifi, the key, the hostname. fixture.sh builds with idf.py or in the espressif/idf container, flashes with esptool from pip. The decisions that need no hardware live in policy.c with a gcc host test; CI runs it and builds the firmware in the pinned container.
17 lines
664 B
Bash
17 lines
664 B
Bash
# forgefixture build settings. Copy to fixture.env (git-ignored) and fill
|
|
# in; `./fixture.sh env` does the copy and generates the API key.
|
|
# KEY=value, one per line; quotes around a value are optional.
|
|
|
|
# The wifi network the fixture joins (2.4 GHz; the ESP32-S3 has no 5 GHz).
|
|
WIFI_SSID=
|
|
WIFI_PSK=
|
|
|
|
# The key every API request must carry in X-Fixture-Key. The same value
|
|
# goes into the bench's /data/forgetest/fixture.json. Any string; 32 hex
|
|
# characters from `openssl rand -hex 16` is what `./fixture.sh env` writes.
|
|
API_KEY=
|
|
|
|
# The fixture's hostname: announced over mDNS (<HOSTNAME>.local) and in
|
|
# its DHCP request. Leave empty for forgefixture.
|
|
HOSTNAME=
|