Firmware Images
Use a firmware build system to include Nexigon Agent, its configuration, and your update integration in a reproducible embedded Linux image. Nexigon provides integrations for Yocto and Rugix Bakery.
Putting these components into the build makes every device image contain the same integration and default configuration. The running device still needs its own identity and credentials. Keep the distinction between shared image contents and per-device state when deciding what to bake into an image and what to retain on persistent storage.
Choose a Build Integration
| Build System | Integration | Starting Point |
|---|---|---|
| Yocto | meta-nexigon layers and recipes | Kas example configurations |
| Rugix Bakery | nexigon-rugix recipes | Getting Started with Rugix |
The Nexigon Rugix Bakery template includes OTA integration and release scripts for a new project.
Separate Provisioning and Production Images
For production enrollment, build a dedicated image with Nexigon Agent’s provisioning mode enabled. Build a separate production image with provisioning disabled. The provisioning image accepts initial enrollment; the production image reuses the saved identity. Disabling provisioning in production makes missing credentials fail startup instead of reopening the enrollment endpoint.
After pairing, use Nexigon to assign the production image and per-device configuration through your update and configuration integrations. Persist the device’s credentials, TLS identity, and fingerprint across the image change. Follow Device Provisioning for the complete workflow.