An embedded system is a computer designed to perform a specific function within a device or a larger system. It combines hardware and software to monitor inputs, make decisions, and produce outputs—often without looking anything like a conventional computer.
The controller inside a washing machine, the electronics regulating an electric motor, and the firmware in a digital thermometer all fit this idea. Their job is defined by the product they serve. Success depends on doing that job reliably within limits on timing, power, memory, size, and cost.
What makes up an embedded system?
The exact components vary, but most designs bring together four building blocks. A simple device may fit almost everything onto one small circuit board; a complex product may coordinate many embedded controllers.
1. Processing hardware
A microcontroller (MCU) typically combines a processor, memory, and peripherals on one chip. More demanding devices may use a microprocessor or a system-on-chip (SoC), sometimes alongside dedicated hardware for signal processing, graphics, or machine learning.
2. Memory and firmware
Nonvolatile memory, such as flash, retains program code when power is off. RAM holds working data while the device runs. Firmware initializes the hardware, manages its peripherals, and implements the device's behavior.
3. Inputs and outputs
Sensors, switches, and communication interfaces supply inputs. Outputs may drive a display, activate a relay, adjust a motor, or send data to another controller. Analog-to-digital converters let software work with analog measurements.
4. Power and interfaces
Power circuitry supplies stable operating voltages. Timers, clocks, and interfaces such as GPIO, UART, SPI, and I2C support communication and control. Some systems also include CAN, Ethernet, or wireless connectivity.
How embedded systems work
A useful starting point is a repeating cycle: sense, process, act, and check. The system reads an input, applies a rule or algorithm, changes an output, and observes what happens next. Interrupts can signal events that need prompt attention, while timers schedule recurring work.
Real-time means meeting deadlines
A real-time system must deliver a result within a specified time. A correct answer that arrives too late may be unusable. In a hard real-time task, missing a deadline violates a required timing constraint; in a soft real-time task, lateness degrades service but may be tolerable. The distinction concerns predictable timing, rather than raw processor speed.
Not every embedded function has the same urgency. Updating a status screen can often wait; servicing a time-sensitive control loop may not. Engineers must account for interrupt latency, competing tasks, and worst-case execution time.
Bare metal, RTOS, or embedded Linux?
Embedded software can run directly on the hardware or use an operating system. The choice follows the workload, resource budget, and timing requirements.
| Approach | Where it fits | Main tradeoff |
|---|---|---|
| Bare metal | Small, focused applications using a main loop and interrupt handlers. | Low overhead, but coordinating more activities can make scheduling and shared data harder to manage. |
| Real-time operating system (RTOS) | Devices that need multiple tasks, priorities, timers, and communication between tasks. | Provides scheduling tools, but deadlines still depend on application design, configuration, and hardware. |
| Embedded Linux | Devices needing richer networking, user interfaces, file systems, or application services. | Usually needs more memory and storage. Strict timing may require additional configuration or a separate controller. |
FreeRTOS is one example of an RTOS for microcontrollers and small microprocessors. An RTOS does not automatically make a product deterministic: poorly bounded tasks or long blocking operations can still cause missed deadlines.
C and C++ are widely used for low-level embedded software. Other languages, including Rust and Python on supported platforms, can also have a role. The relevant questions are whether the toolchain supports the hardware and whether the resulting program meets the device's resource and timing requirements.
Where embedded systems are used
- Home appliances: Washing machines sequence cycles, refrigerators regulate temperature, and induction cooktops manage heating power.
- Transportation: Controllers manage propulsion, battery monitoring, lighting, and vehicle instrumentation.
- Industrial equipment: Embedded electronics control drives, collect measurements, and monitor machine conditions.
- Medical devices: Systems acquire physiological signals, operate instruments, and manage device interfaces, with verification needs determined by their intended use.
- Communications: Routers and other network equipment use dedicated computing hardware and software to move and manage data.
- Battery-powered sensors: Small controllers wake to take measurements, transmit when needed, and return to a low-power state.
Some of these devices connect to the Internet of Things (IoT). Others operate entirely offline. Connectivity is an optional capability, not a defining requirement of an embedded system.
The engineering is in the constraints
A working prototype is only the beginning. A finished device must behave predictably across its operating conditions and remain supportable throughout its service life.
Power and performance
Higher clock speeds can finish work sooner but may increase power demand. Sleep modes, efficient peripherals, and carefully scheduled communication help conserve energy. Designers measure the entire operating cycle, including idle time and radio activity.
Reliability and recovery
Watchdog timers can help detect stalled software. Brownout detection, startup checks, and persistent fault records support recovery. Resetting the processor is only part of the solution: outputs must also reach a defined, appropriate state.
Security and updates
Limit access to device interfaces, protect sensitive data, and authenticate software updates. Plan for interrupted installations and recovery. Secure boot can help verify software before execution, but it does not replace secure application design.
Lifecycle and maintainability
Component availability, manufacturing tests, diagnostics, and firmware support influence long-term viability. A design needs a way to identify its hardware and software versions and to investigate failures after deployment.
For connected devices, the NIST IoT Device Cybersecurity Capability Core Baseline provides a useful reference covering device identification, configuration, data protection, interface access, software updates, and cybersecurity state awareness.
How engineers test the complete system
Software tests check individual functions, while integration tests exercise drivers and hardware together. On-target measurements reveal timing and memory behavior that a desktop simulation may miss. Hardware-in-the-loop testing supplies controlled signals to a real controller so engineers can evaluate both normal operation and faults.
Useful tests include sudden power loss, a disconnected sensor, malformed communication, full storage, and repeated restarts. Testing should establish what the device does when something fails, as well as whether it works under ideal conditions.
Common questions
Is a microcontroller an embedded system?
A microcontroller is a component. It becomes part of an embedded system when combined with firmware and the circuitry needed to perform a defined function.
Does every embedded system need an operating system?
No. Many small devices run a single program directly on the hardware. An operating system becomes useful when its scheduling and services justify the additional complexity and resource use.
What is the difference between firmware and embedded software?
The terms overlap. Firmware usually refers to software closely tied to device hardware and stored in nonvolatile memory. Embedded software is broader and can include higher-level applications running on an embedded operating system.
Can an embedded system use artificial intelligence?
Yes. A device can run a trained model locally to recognize sounds, classify sensor readings, or detect anomalies. Whether that is practical depends on model size, available memory, compute capacity, energy use, and the consequences of incorrect predictions.
Further reading
- FreeRTOS — an embedded real-time operating system and its development resources.
- NISTIR 8259A — foundational cybersecurity capabilities for IoT devices.
- NIST software update capabilities — considerations for authorized updates and supporting mechanisms.