← ClaudeAtlas

espos-firmware-projectlisted

Start, build, configure, test and maintain an ESP-IDF firmware on espOS: new-repo setup (secrets, Docker Hub login in CI, Dependabot, the release App), the CMake prologue, sdkconfig layering, partition tables per flash size, the IDF version pin, the locked build wrapper and a warning gate, host tests, publishing live and dated Signal K data, bumping the espos submodule and its dependencies.lock, gating a target on a minimum espOS, and releasing through espOS's reusable workflows with GitHub-generated notes.
signalk-espOS/skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill signalk-espOS/skills
# A firmware on espOS Verified against espOS v0.24.0 / ESP-IDF v6.0.3, late October 2026. Primary sources in the espOS tree: `docs/development.md`, `docs/releasing.md`, `cmake/espos_project.cmake`, `cmake/espos_version.cmake`, `scripts/build.sh`. ## Starting a new firmware repository Building outside the project? `espos-own-firmware` is the end-to-end order of work (own key, following espOS releases, several boards, the registry, the README); this skill has the detail behind it. There is no template repository. espOS deleted `espos-template` because it rotted five releases behind. Start from an example CI builds on every release: `idf.py create-project-from-example "signalk-espos/espos_core:from_registry"` (registry consumer), or copy the gateway/cockpit layout for the submodule path below: add `espos` as a submodule **at the latest release tag** (`git -C espos checkout vX.Y.Z`, never a branch tip), copy `espos/.idf-version` to the repo root, and build only through `espos/scripts/build.sh`. ### One-time repository settings (Settings → Actions, Secrets and variables) | what | where | why | |---|---|---| | "Allow GitHub Actions to create and approve pull requests" | Settings → Actions → General | release-please and the espOS bump workflow open PRs; without it they fail with zero jobs | | signing key, e.g. `<NAME>_SIGNING_KEY_PEM` | **Secret** | release builds refuse to run without it; see `espos-keys-ota-fleet` | | `RELEASE_APP_ID`, `RELEASE_APP_PRIVATE_KEY` | **Secrets**