Firmware
Infuse IoT starts from a maintained firmware codebase built for low-power intelligent IoT on Zephyr RTOS. The goal is to give product teams a production-ready base for device identity, secure communication, telemetry, command handling, and operational definitions.
The current unified docs focus on backend integration APIs. Firmware teams should use this section to understand which cloud concepts their device code needs to align with.
Firmware Responsibilities
Device firmware typically needs to support:
- stable device identity, including MCU and Infuse
deviceIdhandling, - secure provisioning and key material established during manufacturing or onboarding,
- state reporting for backend visibility,
- route participation so downlink commands can be delivered,
- RPC command handling,
- KV entry reads and updates,
- logger state reporting where logger workflows are used,
- TDF, RPC, and KV definitions compatible with the cloud registry.
Zephyr-Based Foundation
Zephyr RTOS provides the embedded operating-system foundation for constrained devices. Infuse IoT builds on that foundation so teams can focus on product-specific firmware and backend integration rather than rebuilding common infrastructure for identity, communication, and operations.
Backend Contracts Firmware Must Match
| Firmware concern | Cloud/API concept |
|---|---|
| Device identifier | deviceId, mcuId, board, organisation |
| Secure provisioning | Cloud public key, shared secret, derived device key |
| Device-to-cloud communication | MQTT token and route tracking |
| Commands | RPC messages and RPC definitions |
| Structured telemetry | TDF definitions |
| Device configuration/state | KV definitions and KV entry updates |
| Logged data | Logger state and downstream ingestion |
For API-led onboarding, see Provisioning and Connect an IoT Device.