In electronic systems and computing, firmware is the combination of persistent memory and program code and data stored in it. Typical examples of devices containing firmware are embedded systems (such as traffic lights, consumer appliances, and digital watches), computers, computer peripherals, mobile phones, and digital cameras. The firmware contained in these devices provides the control program for the device.
Firmware is held in non-volatile memory devices such as ROM, EPROM, or flash memory. Changing the firmware of a device may rarely or never be done during its economic lifetime; some firmware memory devices are permanently installed and cannot be changed after manufacture. Common reasons for updating firmware include fixing bugs or adding features to the device. This may require ROM integrated circuits to be physically replaced, or flash memory to be reprogrammed through a special procedure. Firmware such as the ROM BIOS of a personal computer may contain only elementary basic functions of a device and may only provide services to higher-level software. Firmware such as the program of an embedded system may be the only program that will run on the system and provide all of its functions.
Before integrated circuits, other firmware devices included a discrete semiconductor diode matrix. The Apollo guidance computer had firmware consisting of a specially manufactured core memory plane, called "core rope memory", where data were stored by physically threading wires through (1) or around (0) the core storing each data bit.
Origin of the term
Ascher Opler coined the term "firmware" in a 1967 Datamation article. Originally, it meant the contents of a writable control store (a small specialized high speed memory), containing microcode that defined and implemented the computer's instruction set, and that could be reloaded to specialize or modify the instructions that the central processing unit (CPU) could execute. As originally used, firmware contrasted with hardware (the CPU itself) and software (normal instructions executing on a CPU). It was not composed of CPU machine instructions, but of lower-level microcode involved in the implementation of machine instructions. It existed on the boundary between hardware and software; thus the name "firmware".
Until the mid-1990s, updating firmware typically involved replacing a storage medium containing firmware, usually a socketed ROM integrated circuit. Flash memory allows firmware to be updated without physically removing an integrated circuit from the system. An error during the upgrade process may make the device non-functional, or "bricked".
In some respects, the various firmware components are as important as the operating system in a working computer. However, unlike most modern operating systems, firmware rarely has a well-evolved automatic mechanism of updating itself to fix any functionality issues detected after shipping the unit.
The BIOS may be "manually" updated by a user, using a small utility program. In contrast, firmware in storage devices (harddisks, DVD drives, flash storage) rarely gets updated, even when flash (rather than ROM) storage is used for the firmware; there are no standardized mechanisms for detecting or updating firmware versions.
Most computer peripherals are themselves special-purpose computers. Devices such as printers, scanners, cameras, USB drives, have firmware stored internally. Some devices may permit field replacement of firmware.
Some low-cost peripherals no longer contain non-volatile memory for firmware, and instead rely on the host system to transfer the device control program from a disk file or CD.
As of 2010[update] most portable music players support firmware upgrades. Some companies use firmware updates to add new playable file formats (codecs); iriver added Vorbis playback support this way, for instance. Other features that may change with firmware updates include the GUI or even the battery life. Most mobile phones have a Firmware Over The Air firmware upgrade capability for much the same reasons; some may even be upgraded to enhance reception or sound quality, illustrating the fact that firmware is used at more than one level in complex products (in a CPU-like microcontroller versus in a digital signal processor, in this particular case).
Since 1996 most automobiles have employed an on-board computer and various sensors to detect mechanical problems. As of 2010[update] modern vehicles also employ computer-controlled ABS systems and computer-operated Transmission Control Units (TCU). The driver can also get in-dash information while driving in this manner, such as real-time fuel-economy and tire-pressure readings. Local dealers can update most vehicle firmware.
Examples of firmware include:
- In consumer products:
- In computers:
- The BIOS found in IBM-compatible personal computers
- The (U)EFI-compliant firmware used on Itanium systems, Intel-based computers from Apple, and many Intel desktop computer motherboards
- Open Firmware, used in SPARC-based computers from Sun Microsystems and Oracle Corporation, PowerPC-based computers from Apple, and computers from Genesi
- ARCS, used in computers from Silicon Graphics
- Kickstart, used in the Amiga line of computers (POST, hardware init + Plug and Play auto-configuration of peripherals, kernel, etc.)
- RTAS (Run-Time Abstraction Services), used in computers from IBM
- The Common Firmware Environment (CFE)
- In routers and firewalls:
- In NAS systems:
Flashing refers to the overwriting of existing firmware or data on EEPROM modules present in an electronic device with new data. This can be done to upgrade a device  or to change the provider of a service associated with the function of the device, such as changing from one mobile phone service provider to another or installing a new operating system. If firmware is upgradable, it is often done via a program from the provider, and will often allow the old firmware to be saved before upgrading so it can be reverted to if the process fails, or the newer version was worse.
Sometimes third parties create an unofficial new or modified ("aftermarket") version of firmware to provide new features or to unlock hidden functionality. Examples include:
- Rockbox for digital audio players.
- CHDK and Magic Lantern for Canon digital cameras.
- Nikon Hacker project for Nikon EXPEED DSLRs.
- Many third-party firmware projects for wireless routers, including:
- Firmware that allows DVD drives to be region-free.
- SamyGO, modified firmware for Samsung televisions.
- Many homebrew projects for gaming consoles. These often unlock general-purpose computing functionality in previously limited devices (e.g., running Doom on iPods).
These hacks usually take advantage of the firmware update facility on many devices to install or run themselves. Some, however, must resort to exploits in order to run, because the manufacturer has attempted to lock the hardware to stop it from running unlicensed code.
Mark Shuttleworth, founder of the Ubuntu Linux distribution, has described proprietary firmware as a security risk, saying that "firmware on your device is the NSA's best friend" and calling firmware "a trojan horse of monumental proportions". He has pointed out that low-quality, closed source firmware is a major threat to system security: "Your biggest mistake is to assume that the NSA is the only institution abusing this position of trust – in fact, it's reasonable to assume that all firmware is a cesspool of insecurity, courtesy of incompetence of the highest degree from manufacturers, and competence of the highest degree from a very wide range of such agencies".
As a solution to this problem, he has called for declarative firmware. Firmware should be open source so that the code can be checked and verified; it should also be declarative, meaning that it should describe "hardware linkage and dependencies" and "should not include executable code".
Custom firmware hacks have also focused on injecting malware into devices such as smartphones or USB devices. One such smartphone injection was demonstrated on the Symbian OS at MalCon, a hacker convention. A USB device firmware hack called BadUSB was presented at Black Hat USA 2014 conference, demonstrating how a USB flash drive microcontroller can be reprogrammed to spoof various other device types in order to take control of a computer, exfiltrate data, or spy on the user.
- The Authoritative Dictionary of IEEE Standards Terms. p. 438. doi:10.1109/IEEESTD.2000.322230. ISBN 0738126012.
- "What is firmware?". incepator.pinzaru.ro. Retrieved 2013-06-14.
- Dag Spicer (August 12, 2000). "One Giant Leap: The Apollo Guidance Computer". Dr. Dobbs. Retrieved August 24, 2012.
- Opler, Ascher (January 1967). "Fourth-Generation Software". Datamation 13 (1): 22–24.
- Corbet, Jonathan; Rubini, Alessandro; Kroah-Hartman, Greg (2005). Linux Device Drivers. O'Reilly Media. p. 405. ISBN 0596005903.
- "Flashing Firmware". Tech-Faq.com. Retrieved July 8, 2011.
- "HTC Developer Center". HTC. Retrieved July 8, 2011.[dead link]
- "Custom Firmware Rocks!". 2009-08-05. Retrieved 2009-08-13.
- "SamyGO: replacing television firmware". LWN.net. 2009-11-14. Retrieved 2009-12-11.
- Linux Format n°184, June 2014, page 7.
- Linux Magazine issue 162, May 2014, page 9.
- "We will be back soon!". Malcon.org. Retrieved 2013-06-14.
- "Hacker plants back door in Symbian firmware". H-online.com. 2010-12-08. Archived from the original on 21 May 2013. Retrieved 2013-06-14.
- "Why the Security of USB Is Fundamentally Broken". Wired.com. 2014-07-31. Retrieved 2014-08-04.
- "BadUSB - On Accessories that Turn Evil". BlackHat.com. Retrieved 2014-08-06.
- Karsten Nohl; Sascha Krißler; Jakob Lell (2014-08-07). "BadUSB – On accessories that turn evil" (PDF). srlabs.de. Retrieved 2014-08-23.