Request a firmware review
Menu
Founders, CTOs and engineers planning device firmware

Firmware architecture, RTOS choice and code structure

The firmware decisions that are cheapest to make early and most expensive to change: the RTOS, the structure of the code, the memory map and the language.

Firmware architecture is the set of decisions every later line of code has to live with: whether to use an RTOS and which one, how the work splits into tasks, drivers and state machines, how memory and flash are laid out, how the device handles errors and power states, and which language it is written in. This section of Field Update covers those decisions for small teams, with the trade-offs written out so a founder can follow them and an engineer can check them.

Long-term support comes up often, because the clock is now easy to read. Zephyr moved in 2026 to major releases every six months, each supported for about a year, with long-term support releases maintained for about five years; the next one is planned for April 2027. FreeRTOS long-term support libraries get security and critical fixes for two years, and the 202406 release reached its end on June 30, 2026. A product that will be in the field for years needs a plan for moving between releases, not only a choice of where to start.

Languages come up too. The Rust Embedded Working Group released embedded-hal 1.0 in January 2024, and CISA and NSA published guidance on adopting memory safe languages in June 2025. This section looks at where Rust fits next to C and C++ on microcontrollers today, without pretending the choice is simple.

To work through these decisions for your own product, use the RTOS selection worksheet, the firmware requirements worksheet, the flash budget calculator and the version scheme builder. If you want the architecture written and built with you, see firmware development, or for machines with tight timing, robotics.

The articles in this section are listed below with their issue dates.

Articles in this section, with issue dates
IssueArticle and the question it answers
Field crash diagnostics: watchdogs, faults and coredumpsWhat should our firmware capture and report when a device crashes or hangs in the field, so we can fix it before the next release?
Portable firmware architecture: surviving a chip changeHow should we structure our firmware so that a forced change of microcontroller or radio module costs weeks, not a rewrite?
Microcontroller or embedded Linux: which should you ship?Does our product need an embedded Linux processor, or will a microcontroller do, once update and maintenance costs over the support period are counted?
How to choose a microcontroller for a connected productWhich microcontroller family should a startup pick for its first connected product, once radio, power, update and security needs are on the table?
Zephyr, FreeRTOS or bare metal: choosing for a new productShould our first production firmware run on Zephyr, FreeRTOS or bare metal, given our chip, radio stack, update path and team?

Send us your board and your plan.

A firmware review reads your schematics, code, flash layout and update plan, and ends with a written plan: what to build first, what could go wrong in the field and how updates will reach your devices.

Request a firmware review

Or email sales@fumbar.com, or call (720) 675-4202.