Have you ever wondered what makes your devices tick? Beyond the casing and processor lies software that starts the hardware, controls its basic functions or runs the complete device. We call that firmware. Understanding it helps you choose the right update, recognise which component a problem belongs to and avoid turning a useful repair into a failed installation.
What Is Firmware and Why Is It Essential?
Firmware is software closely tied to hardware. It may initialise a computer before its operating system starts, control a storage device or operate a small appliance without a desktop operating system at all. Its role, rather than an absolute rule that it can never change, is what makes the term useful.
Many devices keep firmware in non-volatile memory, which retains data without power. Modern flash-based implementations can be updated using a supported process. Other components receive firmware from the host when a driver starts: the Linux kernel's firmware API, for example, can request files for CPU microcode or device microcontrollers. Firmware therefore does not always live permanently in a separate soldered chip.
On a typical modern PC, motherboard firmware initialises the platform and locates a bootloader. UEFI provides interfaces and a boot environment for that process. The operating system then takes over many tasks, while device firmware and some platform services continue to have roles. An embedded appliance may instead spend its whole working life running its own firmware.
Firmware, Drivers and Applications
Firmware is one kind of software. The following distinction helps when a support page offers several downloads for the same device:
| Layer | Typical role | Where an update comes from |
|---|---|---|
| Firmware | Starts or controls the hardware, sometimes including the device's operating system. | The device maker's supported updater, management interface or approved delivery service. |
| Device driver | Lets the host operating system communicate with the hardware. | The operating system or an appropriate manufacturer driver package. |
| Application | Provides a user-facing task, such as a browser or editing tool. | The application publisher or trusted package store. |
These layers can depend on one another. A new driver may expect particular device firmware, while a firmware release can require a supported updater version or intermediate release. Updating an app is not a substitute for a motherboard or router security update. Equally, reinstalling Windows does not automatically replace every firmware component in the machine.
Where You Encounter Firmware
In everyday life, firmware is found in phones, cameras, televisions, game consoles and appliances. A washing machine's controller and a PC motherboard do very different jobs, but both need code suited to their hardware. Vehicle and industrial controllers add their own manufacturer procedures; a home-computer flashing recipe is not appropriate for all of them.
In a homelab, think beyond the BIOS or UEFI version. Storage controllers, drives, network interfaces, routers and access points can have separate firmware. A router's downloadable “firmware image” may include a complete embedded operating system and its configuration interface, rather than only a tiny startup routine.
Some servers also have a baseboard management controller, or BMC, with independent management firmware. Its remote monitoring and power controls are separate from the main operating system. Keep management access restricted and track its update requirements separately; updating the host OS should not be assumed to update every management component.
Storage, Updates and Configuration
ROM, programmable ROM, EEPROM and flash appear in firmware discussions because they describe different ways to retain code. Fixed ROM cannot be updated like a rewritable flash image. Programmable and erasable technologies have their own constraints, so use the actual device documentation rather than treat every memory chip as interchangeable.
A firmware update is also different from a factory reset. The update replaces or changes software; a reset generally restores configuration defaults. One may happen during the other, but resetting a router does not mean it received a newer firmware release. Saving a configuration export is useful, yet it is not necessarily a complete copy of the firmware or a guaranteed restore across incompatible versions.
Manufacturers can deliver updates through an application, a device's web interface, a boot-time utility or an operating-system service. On Linux, LVFS and fwupd provide a supported route for hardware whose vendor has supplied firmware. Their catalogue is not proof that every device is supported.
If fwupd is installed, its documented device-list command can help identify recognised devices and their reported versions:
fwupdmgr get-devicesThis command inspects devices; it does not flash them. Check support, release information and the required installation path before applying an update. A manufacturer-approved Windows updater can also be a supported method. There is no universal rule that a USB flashing utility is always safer than every OS-based tool.
Security: Secure Boot, Measurements and Persistence
Firmware and early boot code are valuable security targets because they participate before many normal operating-system protections. However, an attack on a bootloader stored on disk is different from malicious code written into motherboard flash.
Microsoft's BlackLotus investigation describes malicious files on the EFI System Partition, launched by UEFI firmware. It does not identify BlackLotus as a motherboard-flash implant. The documented recovery includes the EFI partition as well as the OS partition; formatting only the Windows partition is not the same as rebuilding the complete boot environment.
UEFI Secure Boot checks boot images against configured authorised and forbidden signature databases. That is an important trust control, but it is not a scan proving every firmware byte or all later software is harmless. Policy can reject an image or select another boot option, rather than necessarily halt the whole computer at every failure.
TPM-backed measurements and sealed keys serve a related but distinct purpose. Boot components record measurements, and a key-release policy can require particular platform conditions. The TPM is not independently inspecting every line of firmware, and disk encryption does not automatically use the same TPM policy on every system.
Legitimate changes can affect that policy too. Microsoft lists BIOS/UEFI updates among possible BitLocker recovery triggers. Verify that you can access the recovery information before maintenance, follow the documented suspend/resume procedure where required, and confirm protection afterwards. Do not clear a TPM as a routine troubleshooting shortcut.
A Practical Update and Recovery Plan
- Identify the exact target. Record model, hardware revision, current firmware and operating mode. A similarly named router or motherboard is not sufficient identification.
- Read the release notes and instructions. Check prerequisites, supported upgrade order, configuration changes and whether a rollback is allowed. Choose a release for a stated compatibility, security or reliability reason.
- Prepare recovery. Back up relevant data and settings, preserve disk-encryption recovery information and learn the exact manufacturer's recovery method before you need it.
- Choose a maintenance window. Keep power stable and avoid interrupting an update. A battery or UPS can help with power continuity, but does not make an incorrect image safe or eliminate every failure risk.
- Verify the result. Confirm the new version, normal startup, expected configuration and the function the update was meant to fix.
For example, suppose a router starts dropping one phone after an update. Record the installed version and test another client and a wired connection before reflashing. Check whether the problem follows a band or security setting, read the release notes and make one reversible change at a time. A firmware issue is one possibility; a client driver, interference or upstream fault may need a different remedy.
Recovery features vary. A secondary firmware image or a USB recovery button can help only when the particular board supports it and its instructions are followed. Do not assume every “dual BIOS” system recovers automatically or every recovery button works without the same components connected.
Board-level programming is an advanced repair. The flashrom project stresses supported hardware and a backup before writing, and specifically cautions against use on laptops because embedded-controller interactions can brick them. A cheap programmer and clip are not a universal recovery procedure. If the supported recovery path fails, consult the manufacturer or a qualified repair service.
NIST's platform resiliency guidance frames the goal as protection, detection and recovery. That is a useful buying question as well: how will this device receive authenticated updates, how will problems be noticed and what recovery remains if an update fails?
Conclusion
Firmware is the often-unseen software behind the devices we rely on. Knowing the difference between firmware, drivers and configuration makes maintenance easier to reason about. Use the right manufacturer's process, keep a recoverable baseline and verify the result instead of assuming every newer image guarantees better performance.
The original Wikipedia firmware link remains available for further reading; the technical distinctions above are supported by the linked standards and publisher documentation.
