CPatch: Optimising OTA Upgrades Through Binary Diffs
summary
CPatch produces linear, single-step binary patches for Zephyr devices with a small constant-memory C runtime and a Python patch generation tool that heuristically picks the smallest diff. It validates input/output CRCs, streams writes to flash, and requires a readable original image plus a small flash slot for the patch. Real results: a 440,000-byte firmware becomes a 24,000-byte patch (≈6%), complex 568,000-byte apps drop to ~120KB (~20%), and one demo uses 1,900 patch instructions to change LED behavior. native Zephyr C implementation streaming flash writer
AI-written summary · about
chapters (12)
- 0:00CPatch and OTA upgrades
- 2:29Problem with full firmware updates
- 6:23Existing binary diff limits
- 8:48CPatch optimizes embedded patching
- 13:42Binary diff encoding challenges
- 17:17CPatch instruction set
- 21:32CPatch efficiency gains
- 24:48CPatch versus other tools
- 27:00CPatch embedded implementation
- 30:13Python patch generation
- 33:47Live CPatch demo
- 38:36Q&A on CPatch
related talks
46mCPatch: Optimising OTA Upgrades Through Binary Diffs
41mZephyr RTOS: Under 1KB of RAM
34mComparing Linux OS Image Update Models
34mZephyr Footprint – Where Are We and Where Are We Going
51mDemystifying Memory: A Practical Tutorial on Managing & Optimizing Memory in Zephyr
31mMeasuring the Impacts of the Preempt-RT Patch
30mZephyr Accelerates Tools for Testing External Display Support
49mEmbedded Linux Size Reduction Techniques