RTPatch reduces the size of an ECU or head-unit update by 90–99% and applies it in place, with rollback — making frequent OTA updates practical over constrained cellular links, and safe across an interruption or power loss. Because RTPatch does one narrowly-defined job with minimal safety exposure, it is straightforward to bring into a functional-safety program.
Designed to support ISO 26262
RTPatch's client-resident code is developed under static analysis against the MISRA C guidelines, in support of the software requirements of ISO 26262. All mandatory rules are followed; deviations are documented in source and available to customers. Pocket Soft engaged an independent, third-party code audit to assess RTPatch against these standards.
RTPatch can be integrated either as a proven-in-use software component or as a Safety Element out of Context (SEooC). Documentation to support either path is available to ISO 26262 customers under NDA. Where an independent verification step is required, RTPatch integrates cleanly with a separate integrity check (for example SHA-256) on another core.
Why it fits automotive
- In-place flash update with rollback and power-loss resume — the running image is never left partially updated
- 90–99% smaller updates — lower cellular OTA cost and faster campaigns across large fleets
- Low integration effort — minimal sensitivity to platform, OS, and surrounding software components, reducing time to market
- Runs deeply embedded — no filesystem required, non-POSIX, 16/32/64-bit, ~41–45 KB footprint
- Mission-critical heritage — a three-decade record in aerospace, defense, and in-vehicle systems (Pioneer, Clarion) that maps directly to automotive reliability requirements
- Clean, owned technology — 100% Pocket Soft-owned, with IP indemnity and a Certificate of Originality available