Request a firmware review
Menu
Startups building battery systems, EV charging, solar and environmental sensors

Firmware for climate and energy hardware

Energy and environmental hardware stays in the field for years, often far from anyone who can press a reset button. Its firmware has to be updated cheaply and carefully, without touching what keeps it safe.

Key characteristics

Field life
Years, often unattended
Typical links
LTE-M, NB-IoT, LoRaWAN and Wi-Fi
Watch closely
Data cost per rollout and energy per update
Boundary
Safety functions kept apart and changed separately

Battery storage, EV chargers, solar equipment, grid monitors and environmental sensors look like different businesses. Their firmware has three things in common. The devices stay in service for years, often outdoors and unattended. They usually talk over links that are slow, metered or both. And some of what the firmware controls (charge current, cell temperature limits, a contactor) can damage equipment or hurt someone if it goes wrong.

That combination changes how firmware should be built and updated. A fix that would be routine on a desk gadget needs a plan when the device sits on a ranch hours from the nearest technician, on a cellular plan billed by the megabyte, next to a battery pack.

Long field lives

Plan the firmware for the whole service life, not for the launch. In practice that means three things.

  • Pick a software base with support that lasts. Zephyr long-term support releases are maintained for about five years; the current one, Zephyr 3.7, reaches end of life on July 27, 2029, and the next is planned for April 2027. FreeRTOS long-term support libraries get security and critical fixes for two years; the 202604 release runs to April 30, 2028. A product meant to run for ten years will move between releases at least once, so plan that migration as part of sustaining releases.
  • Leave room to grow. Firmware gets bigger over the years. Size the image slots and storage for that now with the flash budget calculator.
  • State a support period you can keep. If you sell in the EU, the Cyber Resilience Act requires a support period of at least five years unless the product is expected to be in use for less, with security updates provided free of charge. Its main obligations apply from December 11, 2027. This is not legal advice; check how it applies to your product.

Cellular costs and update size

Many field devices use LTE-M (3GPP eMTC) or NB-IoT, low-power cellular technologies that are part of 3GPP Release 13, or LoRaWAN where a local network makes sense. On cellular, every byte of every update is billed. A full image sent to every device, plus the devices that need a second try, is a real line in the operating budget, and you will send many of them over the product’s life.

Four design choices drive that cost:

Choice Effect on each rollout
Who downloads the image A gateway that fetches once and relays to nearby devices over a local link sends far less over cellular than every device fetching on its own
Full or delta images Delta images carry only what changed, but need the device to hold the base version and an update agent that can apply them
Retries Downloads that resume instead of restarting waste less data on weak links
When to download Waiting for good signal and enough battery or solar charge saves both data and energy

Model your own fleet with the over-the-air data cost calculator and the energy side with the battery life calculator. For battery devices, the update policy should check charge before a download starts, and every release should re-measure sleep current so a bug does not quietly shorten battery life. See low-power design.

Example (fictional). Loamwick’s LW-1 probes run on two AA lithium cells and talk Bluetooth LE to 4 solar-powered gateways, which forward readings over LTE-M. For a release, each gateway downloads the 412 KB probe image once and relays it to its probes over Bluetooth LE. That is 4 cellular downloads instead of 40, about a tenth of the cellular data. Version 1.1.0 then goes out in waves of 4, 12 and 24 probes with 48 hours between waves. See the example project.

Battery protection, charger control and inverter shutdown are safety functions. They are often backed by hardware protection circuits, and the standards that apply to them are set by your market and your certification lab. Fumbar does not certify safety functions or claim any functional-safety certification. What we do is draw a clear line in the firmware architecture and keep it:

  • Safety-related code lives in its own component, ideally on its own microcontroller or in a protected region, with its own requirements, tests and change history.
  • The connected application (telemetry, scheduling, user interface, cloud link) can change often. The safety component changes rarely, and only through a separate review that your safety engineer signs off.
  • The safety component keeps working, and fails to a safe state, if the connected side crashes, reboots or is in the middle of an update.
  • Updates are applied when the equipment is idle: a charger between sessions, a battery system at rest, a logger when it has charge to spare.

None of this makes a device incapable of failure. It limits what a bad update to the connected side can reach.

What we usually do

For climate and energy products the work tends to combine low-power design, connectivity, a signed over-the-air update path with tested rollback, and test automation that includes a power regression test. One technical lead writes you a weekly status and a release report after every release, so investors and field partners can see what changed and how the rollout went.

Where to start

Request a firmware review. We read your schematics, code, flash layout and update plan, estimate what each rollout will cost in data and energy, and send a written plan with the risks and the order of work.

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.