Embedded system

Key components and characteristics

Most embedded systems share a handful of essential parts: a processor (which can be a microcontroller or a microprocessor), memory (volatile and non-volatile), sensors and actuators for the physical world interface, and software that implements the device’s logic. They are often constrained in resources — limited CPU speed, small memory, and strict power budgets — and may include specialized hardware for communications or signal conditioning.

• Determinism and timing: many embedded designs must satisfy time constraints and deliver results within defined deadlines (real-time requirements). See real-time computing for the concept.
• Reliability and safety: embedded units in medical devices, transportation, or industrial control prioritize fault tolerance and predictable recovery.
• Form factor and environment: systems may be engineered to withstand vibration, temperature extremes, or to fit tiny enclosures.

History and development

The growth of embedded systems followed the advent of small, affordable microprocessors and microcontrollers in the late 20th century. Early embedded controllers replaced bulky electromechanical logic in appliances and instrumentation, and subsequent advances in semiconductor density, low-power design, and networking have steadily broadened their capabilities. Today embedded technology ranges from simple single-purpose boards to complex multicore platforms running networked operating systems.

Common uses and examples

Embedded systems appear in nearly every industry. Some typical examples include:

• Consumer electronics: MP3 players (example), digital cameras (example), smart appliances.
• Transportation: engine control units and safety systems in automobiles, flight control subsystems in aircraft.
• Infrastructure and industry: traffic light controllers (example), programmable logic controllers on an assembly line.
• Home and building automation: door lock controllers in hotels, HVAC controllers, and elevator controllers (see elevator example).
• Set-top and media devices: signal decoders in satellite or cable boxes (set-top box).

Design trade-offs and distinctions

Designing an embedded system involves trade-offs among cost, performance, power, size, and development time. Many embedded projects use real-time or lightweight operating systems, but some are implemented as single-purpose firmware without an OS. The term "embedded" distinguishes these systems from general-purpose computing platforms by their focused functionality, tighter integration with hardware, and often stricter assurance requirements.

Why embedded systems matter

Embedded systems underpin modern conveniences and critical infrastructure alike. Their ubiquity—from handheld devices and household gadgets to transportation and industrial automation—makes them a foundational technology. Understanding their components, constraints, and typical applications helps clarify why specialized engineering practices and testing regimes are necessary to ensure safety, reliability, and longevity.