Repository navigation
feat: set devices up over USB with tedge-onboard - #19
Merged
Merged
Conversation
Builds with the thin-edge.io client now include tiny-edge's provisioning library (APP_TEDGE_PROVISIONING), so tedge-onboard, run on a computer the device is plugged into, can give it a Wi-Fi network and register it in Cumulocity: - net.c gains app_net_switch_network(). It tries a network through the normal reconnect path, and stores it only once the device has an address. Otherwise it goes back to the stored network, so a mistyped password cannot strand a device. - lib/common/prov_tedge.c provides the library's hooks: Wi-Fi through that switch, identify by flashing the status LED, the tiny-edge Zephyr port's scan, and the application's firmware name and version. - A device with no Wi-Fi network starts the client first and waits for the tool, instead of rebooting into the Wi-Fi provisioner (the button pattern still starts it). It then waits for a network for as long as it takes, and the reconnect loop no longer retries without credentials. tiny-edge is pinned to its serial-onboarding branch for now. Co-Authored-By: Claude Opus 5.5 <[email protected]>
A tedge-* device with no Wi-Fi network waits for tedge-onboard, and shows the provisioning pattern on its status LED until it is set up. Pressing the button 3 times within 2 seconds still starts the Wi-Fi provisioner (Improv over BLE, or lab-ztp-provisioner). The README describes both. Co-Authored-By: Claude Opus 5.5 <[email protected]>
lib/common/prov_tedge.c starts provisioning with tedge_provisioning_zephyr_init(). It passes only what these applications do their own way: Wi-Fi through net.c, which owns connecting; identify on the status LED; and the firmware name. The scan and the chip come from the tiny-edge Zephyr port. The start-up block that each of the four apps repeated, "no Wi-Fi yet: start the client first, wait for the network", is now one call, app_prov_tedge_start_unprovisioned(). In builds without the client it is a macro that names no client symbol. tiny-edge is pinned to the branch of thin-edge/tiny-edge#9 for now. Co-Authored-By: Claude Opus 5.5 <[email protected]>
The release with the provisioning library, its Zephyr defaults (tedge_provisioning_zephyr_init()), tedge-onboard, and the code-scanning fixes. It replaces the pin to the pull request branch. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Every build that runs the thin-edge.io client now carries tiny-edge's provisioning library. On the ESP32-S3 and C6, that adds about 1.2 KB of flash and 6.5 KB of static RAM, for the worker's stack and buffers. On the classic ESP32, it adds about 6 KB of flash and 6.4 KB of RAM. The standalone builds don't change. Two images move by a 64 KB alignment step: - modbus-server tedge-full on the C6 (content +8.5 KB). - snmp-agent tedge-full on the QT Py S3, which dropped by the same step in #18. Both are within their flash budgets. The sizes come from a CI run of every build (release workflow, run 42801580748), using the same size.py report that --write-baseline records. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This was referenced Nov 10, 2026
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.
What
The apps that run the thin-edge.io client can now be set up over USB with
tedge-onboard, the guided tool released in tiny-edge v0.3.0. The tool reuses the computer's Wi-Fi, registers the device in Cumulocity through go-c8y-cli, and sends the Wi-Fi network, tenant, and one-time password to the device over Improv Serial.Changes
west.ymlmoves from v0.2.0 to v0.3.0, which adds the optional provisioning library and the Zephyr hooks.APP_TEDGE_PROVISIONING(default on when the app has the tedge client and the Wi-Fi credential store, and no BLE provisioner):lib/common/prov_tedge.cstarts tiny-edge's provisioning with the app's own hooks:app_net_switch_network(), which tries the new network, keeps it only once it has an address, and otherwise returns to the previous one.app_prov_tedge_start_unprovisioned()replaces the per-app logic in modbus-server, opcua-server, snmp-agent, and tedge-agent.Testing
Size
release/size-baseline.jsonis updated for all 36 builds, from a CI run of every build (run 42801580748, made with a temporary branch that raised the growth tolerance and has since been deleted). All 36 builds pass their flash budgets.Two images move by a 64 KB alignment step: modbus-server tedge-full on the C6 (content +8.5 KB), and snmp-agent tedge-full on the QT Py S3, which dropped by the same step in #18.
🤖 Generated with Claude Code