If you have ever flashed an ESP32 or updated a router, you have worked with firmware. The word is so ordinary now that few people stop to ask where it came from or what the "firm" is doing in the middle of it. The answer goes back to 1967, when a computer scientist named Ascher Opler coined the term to describe something that was neither fully hardware nor fully software. That in-between layer is still the beating heart of every connected device we build today.
Who coined the word firmware?
The term first appeared in print in a 1967 issue of the trade magazine Datamation, in a short piece by Ascher Opler. At the time, computer designers were wrestling with a new idea: instead of hard-wiring a processor's instructions directly into its circuits, you could store a set of very low-level instructions, called microcode, in a special control memory inside the CPU. That microcode told the hardware how to interpret the machine instructions it received.
Opler needed a word for this microcode, because it did not fit the two categories everyone already used. It was not "hardware" in the sense of soldered transistors and copper traces, and it was not "software" in the sense of programs a user could freely load and change. It sat in between: more permanent than an application, but not physically fixed like a logic gate. So he called it "firm" ware, and the name stuck.
How the meaning shifted
Opler's original firmware lived deep inside the processor as microcode. Over the following decades, the meaning drifted outward. As read-only memory (ROM), then EPROM, then flash memory became cheap and common, engineers started using "firmware" for any low-level program stored in a device's non-volatile memory: the code that runs the moment you switch the device on, before any operating system or user application gets involved.
Today, when we say firmware, we usually mean exactly that. It is the program burned into the flash of a microcontroller, the boot code in a hard drive's controller, the software running a smart thermostat, or the sketch you upload to an Arduino. The "firm" quality is still there: it does not change on a whim like an app, but you can update it in the field when you need to, unlike a fixed circuit. That combination of permanence and updatability is precisely what makes modern connected products possible.
Why firmware matters for IoT
For an Internet of Things device, firmware is not a supporting detail. It is the product. A temperature sensor, a smart plug, an agricultural monitor, or an industrial controller is really just a small circuit board plus the firmware that decides how it behaves. That firmware handles reading sensors, managing power, talking to the network over protocols like MQTT or HTTP, and deciding what to do when the WiFi drops or the battery runs low.
Three things make firmware the make-or-break layer for connected devices. First, reliability: an IoT node might sit in a field or a wall for years, so its firmware has to recover cleanly from crashes, power loss, and flaky connections without a human nearby. Second, security: because these devices are exposed to the network, their firmware is the front line against attackers, which is why secure boot and signed updates matter so much. Third, updatability: good firmware supports over-the-air (OTA) updates, so a product can be patched and improved long after it ships. Get the firmware right and a cheap microcontroller becomes a dependable product; get it wrong and even the best hardware becomes an expensive brick.
From a 1967 word to today's devices
It is a small piece of history, but a telling one. Ascher Opler reached for a new word because the technology had outgrown the neat division between hardware and software, and that middle ground has only grown more important since. Every connected product now lives or dies on the quality of the code sitting just above its silicon.
At Fluidwire we design and write that firmware for embedded and IoT projects here in the Philippines, from thesis prototypes to production-ready connected devices. If you have an idea that needs to become working, reliable hardware, get in touch and let us build the layer between your silicon and your cloud.
Top comments (0)