An update system is a product feature, not a shell script. ArmSoM documents Debian, Android and Buildroot support across the Sige family, while Forge1 is Buildroot-oriented. The image format, bootloader and rollback mechanism must therefore be defined per product.
A minimal release contract
Version the kernel, device tree, root filesystem, bootloader configuration and application together. Sign artifacts in CI, verify before install, and keep a known-good slot or external recovery path. Capture serial logs from failed boots.
sha256sum Image *.dtb rootfs.squashfs
printf '%s %s\n' "$VERSION" "$(git rev-parse HEAD)" > release.manifest
The command is evidence generation, not a complete secure-boot implementation. Key storage, fuse state, boot ROM behavior and field-recovery policy require board-specific review.
Compatibility boundary
Raspberry Pi OTA tools often assume a particular boot partition layout. Jetson update flows assume NVIDIA boot components. Do not reuse either without mapping ArmSoM media, bootloader and recovery semantics.
References
Pre-publication check
- Test interrupted power during update.
- Verify rollback and factory recovery on the exact SKU.
- Publish key ownership and support-lifetime assumptions.