Short answer
Embedded software is code written to control a specific piece of hardware inside a larger product. Common examples include:
- The engine control unit (ECU) firmware in a car, which manages fuel injection and ignition timing.
- Anti-lock braking (ABS) and airbag controller software, which reacts to sensor data within tight time limits.
- Washing machine and microwave oven controllers, which run wash cycles, timers and the button panel.
- Smart thermostat software, which reads temperature, runs schedules and connects to an app.
- Fitness tracker and smartwatch firmware, which reads motion and heart-rate sensors on very little power.
- Pacemaker and infusion pump software, which must be highly reliable.
- Industrial robot and programmable logic controller (PLC) software, which controls motors and machines on a factory floor.
- Smart electricity meter firmware, which measures energy use and reports it to the utility.
- ATM and card payment terminal software, which handles card reading, the keypad and secure communication.
- Wi-Fi router firmware, often built on embedded Linux.
The rest of this article explains what the code in these devices does, and the different kinds of embedded software you’d find inside them.
What makes software “embedded”
Software is usually called embedded when:
- It runs on a dedicated device rather than a general-purpose computer.
- It is written for that particular hardware and closely tied to it.
- It controls or monitors something physical: a motor, a valve, a display, a sensor, a radio.
- The user usually can’t install other programs on the device or replace the software freely.
- It often works under constraints on memory, processing power, energy and response time.
The program running on a microcontroller is often called firmware, because it is stored in non-volatile memory and traditionally changed rarely. Today many devices receive firmware updates, but the name has stuck.
Examples by everyday product
Home appliances
- Washing machines: the software reads the program dial and buttons, controls the water inlet valves, heater and drum motor, monitors water level and door lock, and sequences the wash, rinse and spin stages.
- Microwave ovens: a small controller runs the keypad and display, counts down the timer and switches the magnetron on and off to set power levels.
- Refrigerators: firmware reads temperature sensors, controls the compressor and defrost cycle, and raises alarms if the door is left open.
- Smart thermostats: software reads temperature (and sometimes humidity or occupancy), runs schedules, controls the heating or cooling system and talks to a phone app over Wi-Fi.
Consumer electronics and wearables
- Fitness trackers and smartwatches: firmware samples accelerometer and optical heart-rate sensors, runs algorithms to count steps or estimate sleep, drives a small display and syncs over Bluetooth Low Energy, all while trying to save battery.
- Digital cameras: image-processing firmware handles autofocus, exposure, the shutter and writing files to the memory card.
- TV remote controls: a tiny microcontroller scans the buttons and sends infrared or radio codes, then goes back to sleep.
- Wireless earbuds: firmware manages Bluetooth audio, touch controls, battery charging and noise cancellation.
Cars and transport
A modern car contains many electronic control units, each running its own embedded software:
- Engine control: manages fuel injection, ignition timing and emissions based on sensor readings.
- Anti-lock brakes and stability control: monitors wheel speeds and modulates brake pressure to prevent skids.
- Airbag control: reads crash sensors and decides whether and when to deploy airbags.
- Infotainment and instrument clusters: run the displays, navigation and media, often on a larger operating system.
- Battery management in electric vehicles: monitors cell voltages and temperatures and controls charging.
Outside cars, embedded software runs aircraft avionics and autopilots, railway signalling, ticket gates and fare collection systems.
Medical devices
- Pacemakers: monitor the heart’s rhythm and deliver pacing pulses when needed.
- Infusion pumps: deliver measured doses of fluid or medication and raise alarms on blockages.
- Patient monitors: measure and display vital signs such as heart rate and blood oxygen.
- Blood glucose meters: read a test strip and calculate a reading.
Medical device software is usually developed under strict processes, such as those described in the IEC 62304 standard, because failures can harm patients.
Industrial and infrastructure
- PLCs: run control logic for production lines, pumps and conveyors.
- Industrial robots: coordinate motors and sensors to move precisely and safely.
- Motor drives: control the speed and torque of electric motors.
- Smart meters: measure electricity, gas or water use and report it remotely.
- Building systems: control lifts, lighting, access control and fire alarm panels.
Retail, banking and public services
- ATMs: software reads cards, runs the keypad and screen, controls the cash dispenser and communicates securely with the bank.
- Card payment terminals: handle chip and contactless card reading and encrypted transactions.
- Self-service kiosks and vending machines: manage the user interface, payments and dispensing mechanisms.
- Electric vehicle chargers: control charging, communicate with the vehicle and report status to the operator.
Examples by type of embedded software
Inside a single device there are usually several layers of software. Each of these is itself an example of embedded software.
Bootloaders
A bootloader is the first code that runs when a device powers up. It sets up the hardware and starts the main program. Many bootloaders also handle firmware updates, checking a new image before installing it. U-Boot is a widely used bootloader on embedded Linux systems; microcontrollers often have a small custom or vendor-supplied one.
Bare-metal firmware
Many simple devices run “bare-metal” firmware with no operating system: a main loop that reads inputs, makes decisions and updates outputs, with interrupts handling time-critical events. A remote control, a basic kitchen timer or a simple sensor node often works this way.
Real-time operating systems
More complex microcontroller projects use a real-time operating system (RTOS) such as FreeRTOS or Zephyr. The RTOS lets the application be split into tasks with priorities, so a time-critical motor-control task isn’t delayed by a slower communications task.
Device drivers and hardware abstraction layers
Drivers are the code that talks directly to hardware peripherals: timers, analog-to-digital converters, UART, SPI and I2C interfaces, displays and sensors. Hardware abstraction layers (HALs), often supplied by chip vendors, give application code a more consistent way to use those peripherals.
Communication stacks
Connected devices run protocol stacks for Bluetooth Low Energy, Wi-Fi, TCP/IP, USB, CAN or Modbus. These are often among the largest pieces of code on a small device.
Embedded Linux applications
Routers, set-top boxes, smart TVs, some industrial gateways and many in-car infotainment systems run embedded Linux. The applications on top look more like ordinary software but are still built for one specific device.
Real-time vs non-real-time examples
Some embedded software must respond within strict deadlines:
- Hard real-time: missing a deadline counts as a failure. Airbag deployment, ABS control and flight control are typical examples.
- Soft real-time: occasional late responses degrade quality but aren’t dangerous. Audio and video playback are common examples.
- Not real-time in any strict sense: a smart plug’s app connection or a weather station’s hourly upload can tolerate delays.
What counts as embedded software (and what doesn’t)
The boundary is fuzzy. A useful rule of thumb: if the software is built for a specific device and mainly exists to make that device do its job, it is embedded software.
- Clearly embedded: washing machine firmware, a pacemaker’s control code, an ECU.
- Usually considered embedded: router firmware, smart TV system software, the operating system on a games console.
- Usually not considered embedded: a phone app downloaded from an app store, desktop programs and web services. They run on general-purpose platforms and aren’t tied to one product’s hardware.
Embedded software vs embedded system
An embedded system is the whole dedicated computer inside a product: the processor, memory, inputs and outputs, power supply and software. Embedded software is just the code part. Many lists of “examples of embedded software” are really lists of embedded systems, which is fine as long as you remember that the software is only one piece.
For how these systems are designed from requirements to production, see our introduction to embedded system design. For how the code and the circuit board are developed together, see hardware-software co-design and integration. And for how software like this is checked before it ships, read what embedded testing means.