<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Microcontrollers on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/microcontrollers/</link>
    <description>Recent content in Microcontrollers on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/microcontrollers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Embassy vs RTIC vs esp-hal in 2026: Which Async Runtime Should Run Your Embedded Rust?</title>
      <link>https://www.pistack.xyz/posts/2026-10-26-embedded-rust-async-embassy-rtic-esp-hal/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-26-embedded-rust-async-embassy-rtic-esp-hal/</guid>
      <description>&lt;p&gt;Firmware written with a bare superloop plus a handful of interrupt handlers has a predictable failure mode: at 40 MHz everything works, and at 400 kHz of event traffic two handlers start corrupting the same state machine. The classic fix — a real-time operating system — costs you a scheduler tick, a heap, and a debugger workflow that no longer matches the silicon. Rust&amp;rsquo;s answer is different: keep the single stack, drop the RTOS, and get concurrency from &lt;code&gt;async&lt;/code&gt; plus compile-time priority analysis.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
