Field Update: firmware guides for hardware startups
Practical articles on device firmware and the update path, written for founders, CTOs and first firmware hires, with every factual claim checked against a cited source.
Featured article. Issue:
What it takes to ship firmware you can safely update
Why read it: Most update guides cover only the part their vendor sells; this one walks the whole chain in the order you meet it and links every step to a deeper article.
What has to be in place, from bootloader and signing keys to factory programming and rollout, before a startup can safely update devices in the field?

25 articles in five sections. The issue date on each article is its month in our editorial calendar; the published date on the article is when it went online.
Firmware architecture
Choosing an RTOS, structuring code, languages and the decisions that are hard to undo later. Open the firmware architecture section
| Issue | Article |
|---|---|
| Field crash diagnostics: watchdogs, faults and coredumpsFirmware crash reporting for a first fleet: task watchdogs, reset causes, fault records, coredumps, build IDs and an upload path that fits the battery budget. | |
| Portable firmware architecture: surviving a chip changeA hardware abstraction layer for startup firmware: four seams that make a chip change cost weeks, and the radio, power and secure boot work you redo anyway. | |
| Microcontroller or embedded Linux: which should you ship?Microcontroller vs embedded Linux for a first product: the requirements that need Linux, and the kernel, Yocto and update work it adds over a support period. | |
| How to choose a microcontroller for a connected productHow to choose a microcontroller for a connected product: flash for two image slots, secure boot keys, debug lock, SDK support and longevity, scored per chip. | |
| Zephyr, FreeRTOS or bare metal: choosing for a new productZephyr vs FreeRTOS vs bare metal, decided by your product: the vendor SDK, the update path, the security support window and who maintains the code. |
Updates and releases
Bootloaders, signed images, rollback, staged rollouts and the release habits that keep a fleet current. Open the updates and releases section
| Issue | Article |
|---|---|
| What it takes to ship firmware you can safely updateOTA firmware update best practices in the order a startup meets them: flash layout, bootloader, signing keys, factory identity, releases and rollouts. | |
| Rollback vs anti-rollback: recovering without downgrade riskFirmware anti-rollback blocks old, vulnerable images; recovery rollback undoes a bad update. How MCUboot, ESP-IDF and TF-M do both, and when to raise the floor. | |
| Staged firmware rollouts: what to watch and when to stopHow to run a staged firmware rollout: which fleet health signals to compare with the last release, how long to soak each wave, and when to halt or roll back. | |
| Delta firmware updates: when smaller images pay offWhen a delta firmware update is worth it on a microcontroller fleet: data cost, radio time, battery, and what patches demand from the bootloader and releases. | |
| A/B or single-slot updates: choosing an MCUboot layoutA/B firmware update or single slot? Compare MCUboot swap, overwrite and direct-XIP by flash cost, boot downtime and what happens when power fails mid-update. |
Security and regulation
Secure boot, keys, software bills of materials and the rules connected devices now have to meet. Open the security and regulation section
| Issue | Article |
|---|---|
| FDA cybersecurity for device startups: what your firmware must showFDA premarket cybersecurity under section 524B, turned into firmware work: the cyber device test, update path, SBOM, security controls, testing and records. | |
| Firmware signing keys: storage, rotation and revocationFirmware signing key management for startups: where production keys live, who may sign, and how chip key slots decide if you can rotate or revoke a key. | |
| EN 18031 and the EU RED cybersecurity rules for radiosEN 18031 and the RED cybersecurity rules for wireless products sold in the EU until December 2027: scope, the standard's restrictions and the move to the CRA. | |
| SBOMs for embedded firmware: vendor SDKs, blobs and C codeHow to build a firmware SBOM for microcontroller code: generate it from the build, list vendor SDKs and binary blobs by hand, and meet CRA and FDA expectations. | |
| EU Cyber Resilience Act: what device startups owe and whenCyber Resilience Act requirements for connected devices: what has applied since September 2026, what starts in December 2027, and the firmware work behind it. |
Prototype to production
Bring-up, testing, build gates and factory programming, from the first board to the first shipment. Open the prototype to production section
| Issue | Article |
|---|---|
| RF certification test firmware: what the lab will ask forWhat FCC test mode firmware and radio test modes an RF lab needs, how chip vendors provide them, and what a pre-certified module does and does not remove. | |
| Outsource firmware or hire: how hardware startups decideOutsource firmware development or hire an engineer? When each route wins, how to compare cost, and the code, keys and rights you must own either way. | |
| Firmware testing for startups: unit tests, CI and a HIL rigHardware in the loop testing for firmware, in an order a small team can afford: host unit tests, CI checks, simulation, then real boards on a CI runner. | |
| Factory provisioning: giving every device a unique identityIoT device provisioning in manufacturing: three ways to give each unit its own keys with a contract manufacturer, and what to lock before units ship. | |
| From prototype code to production firmware: keep or rewrite?Prototype to production firmware: a test for which Arduino or vendor example code to keep, what must change before the first run, and in what order. |
Connectivity and power
Bluetooth, cellular, Thread and Matter, and making a battery last as long as the product promises. Open the connectivity and power section
| Issue | Article |
|---|---|
| Matter over Thread or Wi-Fi: choosing the transport for a new deviceMatter over Thread vs Wi-Fi for a new smart home device: battery life, border routers, firmware updates, and the certification steps and fees each path adds. | |
| LTE-M or NB-IoT in 2026: choosing cellular for US deploymentsLTE-M vs NB-IoT for US devices as of November 2026: carrier support, handover, power-saving modes, firmware update time and a module plan for export. | |
| Faster BLE firmware updates: what actually limits the speedBLE DFU speed depends on data length, MTU, connection interval, packets per event, PHY, the phone and flash writes. Which levers matter, with worked numbers. | |
| Measuring sleep current: tools, setup and the errors that fool youHow to measure sleep current and average current you can trust: choosing the meter, preparing board and firmware, marking states, and avoiding common errors. | |
| Why battery life falls short of the estimate, and how to close the gapBattery life shorter than expected? Why capacity-over-current estimates miss pulse loads, cold, self-discharge and firmware behavior, and how to close the gap. |
Field Update is Fumbar’s publication about the code inside connected devices and the path that keeps it current after the devices ship. It is written for people who have to make firmware decisions without necessarily writing the firmware themselves: founders, CTOs, hardware leads and first firmware hires.
Articles are grouped in five sections: firmware architecture, updates and releases, security and regulation, prototype to production, and connectivity and power. Each article explains a decision, shows the numbers where there are numbers, and links to the primary sources behind its facts: standards bodies, regulators and project documentation.
Two dates appear on every article. The issue date is the article’s month in our editorial calendar, which is how the sections are ordered. The published date is when the article actually went online. Where an article needs a worked example, it uses our fictional Loamwick project and labels it as fiction every time.
Articles are written by the Fumbar Editorial Team. The editorial team page explains how we research and check them, how we use software tools, and how to report a correction. Field Update carries no sponsored content. Fumbar sells firmware services, and articles link to them and to our free tools where they are relevant.
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.
Or email sales@fumbar.com, or call (720) 675-4202.