33 lines
1.7 KiB
Markdown
33 lines
1.7 KiB
Markdown
# ota-reference-design
|
|
|
|
A practical reference design for reliable and secure over-the-air updates on embedded Linux.
|
|
|
|
This repository is intended as an educational reference design. It demonstrates one possible approach to designing and implementing a reliable OTA update system for embedded Linux.
|
|
|
|
The project focuses on the engineering decisions behind OTA systems, including:
|
|
|
|
* update strategies;
|
|
* system and storage architecture;
|
|
* bootloader interaction;
|
|
* atomic updates;
|
|
* rollback and recovery;
|
|
* integrity verification and signing;
|
|
* testing and failure handling.
|
|
|
|
It is not tied to a specific OTA framework, hardware platform, or cloud provider.
|
|
|
|
Raspberry Pi may be used for practical demonstrations, but the underlying concepts are applicable to a broader range of embedded Linux devices.
|
|
|
|
This repository is not intended to be a production-ready framework. Instead, it is designed to explain the architectural principles, trade-offs, and failure scenarios that should be considered when building a real OTA system.
|
|
|
|
The repository is being developed incrementally as a structured series of articles, diagrams, architecture decisions, and practical examples.
|
|
|
|
Start with the [series overview](docs/00-series-overview.md). The current practical material includes [PlantUML diagrams](diagrams/readme.md) and an [A/B trial boot simulation](examples/simulations/ab-trial-boot/readme.md) with startup and recovery failure scenarios.
|
|
|
|
See the [changelog](CHANGELOG.md) for dated updates to the chapters, architecture decisions, diagrams, and simulations, with links to the material and related history.
|
|
|
|
|
|
## License
|
|
|
|
This project is licensed under the MIT License. See [LICENSE](LICENSE) for details.
|