Repository navigation
refactor: take the thin-edge.io client from tiny-edge - #17
Merged
Merged
Conversation
The client (tedge-zephyr/) now lives in its own repository,
thin-edge/tiny-edge, with its history, board profiles, Smart Functions,
its own DTM sets and its specs. This repository becomes an example of
applications built with it.
- west.yml pins tiny-edge as a west project; west adds it as a Zephyr
module, so the apps no longer list it in ZEPHYR_EXTRA_MODULES.
- release/devices.yml names tiny-edge's profiles as
"{tiny-edge}/ports/zephyr/profiles/...", which matrix.py resolves with
`west list`; package.py reads tiny-edge's VERSION the same way.
- The tedge-zephyr CI workflow moved to tiny-edge.
Kconfig, the tedge_* API, the release JSON keys and every message the
devices send are unchanged. Built against the pinned commit, the four
sample release images have identical sorted .config, and every symbol
has the same size; only link-order placement differs on Xtensa.
A workspace needs `west update` to fetch tiny-edge, and
paths under tedge-zephyr/ and lib/common/tedge-boards/ are gone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The thin-edge.io client (
tedge-zephyr/) moves to its own repository, thin-edge/tiny-edge, with its history (thin-edge/tiny-edge#1). This repository becomes the example of applications built with it. tiny-edge is laid out as a portable core plus one port per RTOS, so it can later support FreeRTOS, ThreadX, QNX, and VxWorks.Its board profiles (
lib/common/tedge-boards/), the Smart Functions, the client's own DTM sets (zephyr_tedge,zephyr_tedge_remote_access), its OpenSpec specs and archived changes, and thetedge-zephyrCI workflow move with it.Changes
west.ymladds tiny-edge as a west project atmodules/lib/tiny-edge. West adds it as a Zephyr module, so the four apps no longer list it inZEPHYR_EXTRA_MODULES.release/devices.ymlrefers to the profiles as"{tiny-edge}/ports/zephyr/profiles/...".matrix.pyresolves those paths withwest list. Where west is missing (the release workflow's matrix job), it skips the existence check.package.pyreads tiny-edge'sVERSIONthe same way.scripts/measure_tedge.sh, the READMEs,SCOPE.md,DEVICES.md, and the OpenSpec config point at tiny-edge.cumulocity/keeps the applications' DTM sets and points at tiny-edge for the Smart Functions.Unchanged: Kconfig, the
tedge_*API, every message a device sends, and the release JSON keys (tedgeZephyrVersionincluded).For developers: run
west updateonce to fetch tiny-edge. To work on the client and an app together, mount a tiny-edge clone over/ws/modules/lib/tiny-edge(README, "First-time workspace setup").Testing
Four release images were built from
mainand from this branch against tiny-edge48a42201(now released as v0.1.0):tedge-agent-tedge-full-esp32c6-devkitc,modbus-server-tedge-ota-esp32-devkitc,snmp-agent-tedge-ota-esp32-cam, andopcua-server-tedge-ota-qtpy-esp32s3..configis identical for all four..textchanged by 16 B and 144 B, smaller in both. This comes from the new link order (west modules now link before the app's extra modules), not from the client.{project}/paths.matrix.pyvalidatesrelease/devices.ymlwith west.Not flashed to hardware: the client's code compiles the same, and the only differences are link-order placement.
Release
west.ymlpins tiny-edge v0.1.0, the first release from its own repository (thin-edge/tiny-edge#1, thin-edge/tiny-edge#2). Its code is the same as48a42201, which the testing above used. The only differences areVERSION(0.0.2 → 0.1.0) and the new changelog.🤖 Generated with Claude Code