<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Firmware on Code Circuits</title><link>https://codecircuits.com/tags/firmware/</link><description>Recent content in Firmware on Code Circuits</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>contact@codecircuits.com (Luan Pham)</managingEditor><webMaster>contact@codecircuits.com (Luan Pham)</webMaster><copyright>Copyright © 2019–2026, CodeCircuits</copyright><lastBuildDate>Mon, 07 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://codecircuits.com/tags/firmware/index.xml" rel="self" type="application/rss+xml"/><item><title>RTOS vs Arduino Super Loop</title><link>https://codecircuits.com/post/rtos-vs-arduino-super-loop/</link><pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate><author>contact@codecircuits.com (Luan Pham)</author><guid>https://codecircuits.com/post/rtos-vs-arduino-super-loop/</guid><description>&lt;p&gt;When you build firmware for a microcontroller, you usually end up choosing between two patterns: the simple Arduino-style &lt;code&gt;loop()&lt;/code&gt; or a full RTOS-based design. Both can work well, but they solve different problems.&lt;/p&gt;
&lt;p&gt;The Arduino super loop is easy to understand: run setup once, then repeatedly execute the same code in a loop. An RTOS, on the other hand, gives you multiple tasks that can run concurrently, wake up on timers, wait for events, and share the CPU in a controlled way.&lt;/p&gt;</description></item></channel></rss>