deeaitch/ota-reference-design
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

diagrams and simulation

Browse Source
This commit is contained in:
deeaitch committed 2026-10-11 07:21:11 -04:00
1 parent bf9871eb9e
commit d65910a7c5
18 files changed
+926 -4
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/03-system-architecture.md
+6
View File
@@ -45,6 +45,12 @@ Alongside the update files, it needs a few details: which version this is, which
These are roles, not a shopping list of separate services. One tool may cover several of them. What matters is knowing who handles each step.
The following view shows the roles and the server/device boundary for the system-update example used in the next chapter.
![OTA roles and device boundary](../diagrams/rendered/ota-architecture.svg)
[PlantUML source](../diagrams/plantuml/ota-architecture.puml)
## 3. One Update, Start to Finish
Imagine a device running version 1. Version 2 is ready. In this example, the device can prepare the new system while keeping the previous one available for recovery.