<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ota on Santiago Hurtado | System Architect</title><link>/tags/ota/</link><description>Recent content in Ota on Santiago Hurtado | System Architect</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 04 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/ota/index.xml" rel="self" type="application/rss+xml"/><item><title>Zephyr OTA Updates Demand Deliberate System Design</title><link>/posts/zephyr-ota-integration/</link><pubDate>Sat, 04 Jul 2026 00:00:00 +0000</pubDate><guid>/posts/zephyr-ota-integration/</guid><description>&lt;p&gt;Adding OTA to an embedded application is not just a library integration, it is system integration that requires thinking about your architecture first. On constrained microcontrollers, the A/B partition layout already cuts available flash in half before a single update is downloaded.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; More critically, a secure firmware download requires a concurrent cryptographic network session while the system is still running: sensor sampling, data publishing, and the update process all compete for the same network buffers and volatile memory. That resource contention, not the update process itself, is the real failure mode when there is no design that accounts for it, and regulations like the Cyber Resilience Act make getting it right a compliance requirement, not just an engineering one.&lt;sup id="fnref:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;</description></item></channel></rss>