Other meanings of Embedded systems
COMPUTING
Embedded systems are computer systems built into a larger product to monitor conditions, control operations, or provide a dedicated function. Unlike general-purpose computers, they are usually constrained by cost, power, memory, size, and timing requirements; many must respond predictably to events in the physical world.
Embedded systems combine processing hardware, software, and product-specific electronics to perform a defined role. A typical design contains a microcontroller or microprocessor, memory, input and output interfaces, sensors, actuators, and firmware. A microcontroller integrates a processor core with memory and peripherals on one chip, while more capable products may use a processor running an operating system such as Linux.1
The boundary is functional rather than technological: a networked camera, vehicle controller, medical instrument, printer, and household appliance can all be embedded systems. Some operate independently; others form nodes in larger cyber-physical systems. Their software is commonly stored in nonvolatile memory and starts automatically when power is applied.
Many embedded systems are defined by deadlines, not merely by average speed. A real-time system must produce a response within a specified interval; missing that interval may reduce quality in a soft real-time application or create danger in a hard real-time one. Real-time operating systems provide scheduling, timers, interrupt handling, and intertask communication, although small products often use a simple loop instead.
Reliability also depends on predictable hardware behavior, fault detection, watchdog timers, redundancy, safe-state design, and controlled software updates. Automotive, aviation, railway, industrial, and medical applications frequently require formal processes for hazard analysis, verification, traceability, and cybersecurity rather than relying only on functional testing.
Embedded development is a hardware–software co-design process. Engineers partition functions between circuitry and code, select a processor and communication buses, define timing and power budgets, and test interactions with sensors and actuators. Common interfaces include I2C, SPI, UART, CAN, USB, Ethernet, and wireless links. Firmware is often written in C or C++, with assembly used for startup code, optimization, or tightly controlled hardware access.
Applications range from engine controllers and anti-lock braking systems to pacemakers, satellites, robots, cameras, smart meters, and industrial drives. Field-programmable gate arrays and digital signal processors extend the design space when parallel computation, high-speed signal processing, or specialized acceleration matters.2
Embedded systems are not necessarily small, isolated, or resource-poor. A modern automobile may contain many networked controllers, while an advanced spacecraft or telecommunications product can contain processors, real-time operating systems, and complex update mechanisms comparable to those in larger computers. Conversely, an eight-bit microcontroller may be sufficient for a thermostat, toy, or battery monitor.
Long service lives create unusual engineering problems: components may become obsolete, firmware must remain maintainable for decades, and electromagnetic interference or radiation can cause faults. Extremely low-power designs may spend almost all their time asleep and wake only on an interrupt. Security is likewise a lifecycle concern: secure boot, signed firmware, hardware-backed keys, isolation, and authenticated updates help prevent a device from becoming an entry point into a larger network.3 Standards such as IEC 61508 and sector-specific rules formalize safety practices for critical products.4
Embedded systems span a broad range of products; their defining feature is dedicated integration with a larger device or physical process, not a particular processor, operating system, or physical size.
Help improve the encyclopedia. Reports go straight to the site manager.