A/B slots or snapshots? Two ways to make an OTA update survive failure
Both A/B partitioning and snapshot-based updating can roll back a failed OTA update. They reserve very different amounts of flash to do it, and the gap grows with the image.
We are here to help
Have a question or need guidance? Whether you’re searching for resources or want to connect with an expert, we’ve got you covered. Use the search bar on the right to find what you need.
Both A/B partitioning and snapshot-based updating can roll back a failed OTA update. They reserve very different amounts of flash to do it, and the gap grows with the image.
By Ashok Galla
Embedded storage rarely fails all at once. This guide explains how medical device storage degradation develops across the device lifecycle, why endurance, retention, capacity, temperature, and write amplification matter, and what teams should measure before reduced storage margin becomes a system-level reliability problem.
By Eva Rio
Industrial controllers may restart after a power interruption but return with missing, stale, or inconsistent data. This article explains the storage, database, filesystem, and power-related causes of industrial controller data loss and what teams should test to improve recovery.
By Eva Rio
An industrial embedded file system must provide more than basic file access. This guide explains how to define measurable requirements for uptime, known-good recovery, data consistency, resource use, integration, and flash-storage longevity.
By Tuxera
TrendForce projected NAND contract prices to climb 70 to 75% in the second quarter of 2026, and raw NOR and SLC NAND have repriced sharply too. Embedded file systems and FTLs answer that by right-sizing capacity, removing the controller premium on managed flash, extending flash lifetime, and making parts easier to second-source as vendors retire low-density lines.
By Ashok Galla
Choosing a medical device embedded file system requires more than comparing APIs or benchmark speed. This checklist explains how to evaluate recovery, atomicity, durability, raw versus managed flash, performance, lifecycle behavior, integration, diagnostics, and long-term support on the target device.
By Ashok Galla
Commercial medical device storage software can reduce the burden of specialized storage engineering, field diagnostics, migration, validation preparation, and long-term maintenance. This guide explains how to evaluate that build-versus-buy decision without treating commercial software as a substitute for system engineering or device-level validation.
By Ashok Galla
Medical device data integrity can fail even when storage remains accessible and a file system mounts cleanly. This guide explains how buffering, transaction design, file systems, databases, flash behavior, power interruption, and lifecycle aging can create stale, incomplete, or inconsistent persistent state.
In software-defined vehicles, zonal architecture storage requirements are requirements for predictable behavior under stress rather than peak speed. What changes when storage becomes a shared resource, the requirements that matter most, and the validation evidence to ask for before you trust storage in an SDV.
By Marko Finnig
Physical AI teams treat networking determinism as a first-class engineering problem. Storage determinism rarely gets the same scrutiny, and that is exactly where worst-case failures hide. A look at why flash is structurally non-deterministic, what deterministic storage actually requires, and why it is a precondition for scaling physical AI from pilot to production.
Suggested content for: