Developer Guide on EdS

Firmware: lp-stand

Mon, 01 Jan 0001 00:00:00 +0000

Firmware: lp-stand

ESP-IDF in C, following the conventions of esp32-ma-bell-gateway: main/app/, main/config/, main/hardware/, main/network/, with a Makefile wrapper over idf.py.

The split that matters

Scene validation, effect rendering, gamma and event formatting are pure C with no ESP-IDF dependency, because that is where a bug is subtle: it shows up only as the light looks wrong, or, for an event that is not valid JSON, as nothing at all. They are tested with a compiler and nothing else:

Firmware: cover-screen

Mon, 01 Jan 0001 00:00:00 +0000

Firmware: cover-screen

The touch screen that shows the cover and has the five buttons (ADR-0020). ESP-IDF in C, laid out as lp-stand is, for an ESP32-2432S028R.

The split that matters

What a touch means and what is painted over the cover are pure C, because that is where a bug shows up only as it did the wrong thing when I touched it:

make test # needs gcc; no ESP-IDF, no hardware
make pictures # draws each screen to a BMP, with a made-up cover

make pictures runs the board’s own drawing code. Change an icon, run it, and look.

Services: palette and lightd

Mon, 01 Jan 0001 00:00:00 +0000

Services

palette

cd services/palette
make venv # .venv with editable install + dev extras
make test # pytest, no network
make serve PORT=8731

Run a single test:

.venv/bin/pytest tests/test_extract.py::test_name -q

Tuning by eye

The thresholds are judgment calls that no test can settle — where a color stops being a color, how much black field to discard. The CLI exists for that loop:

make palette COVERS=~/covers
make sheet COVERS=~/covers # PNG contact sheet
.venv/bin/eds-palette ~/covers --min-chroma 0.05 --min-lightness 0.08

It prints truecolor swatches in the terminal and can render a sheet of thumbnails beside their weighted palettes, so many sleeves can be compared at once.

Tenant: deevnet-tenant-eds

Mon, 01 Jan 0001 00:00:00 +0000

Tenant: deevnet-tenant-eds

The EdS tenant as code: its overlay network, its workload and its DNS records, rebuildable from scratch against Deevnet IoTaaS without a Deevnet IoTaaS commit (Deevnet ADR-0006).


Index	1 (to be allocated in the factory’s `TENANTS.md`)
Subnet	`10.20.129.0/24`, gateway `10.20.129.1`
Zone	`eds.mobile.deevnet.net`
Service host	`10.20.129.10` — `palette` and `lightd`
Module	`tenant-module-v1.1.0`

Status: written, never applied

terraform validated against the real module, with derived addressing checked against Deevnet ADR-0002. It has not been planned or applied, and three things must happen first:

This Site

Mon, 01 Jan 0001 00:00:00 +0000

This Site

Hugo with the hugo-book theme, following the deevnet-docs pattern. It lives at docs/ inside the monorepo so documentation and the thing it documents move in the same commit.

cd docs
make server # live reload on :1313
make html # build to public/

The theme is a git submodule. After a fresh clone:

git submodule update --init --recursive

Living in a monorepo

Two consequences, both handled:

A repository serves exactly one Pages site. The site is therefore published at https://cdeever.github.io/eds/ — the repository name, not the site name — and baseURL reflects that. BookEditPath carries the docs/ prefix so “edit this page” links resolve.