Hubbry Logo
Embedded systemEmbedded systemMain
Open search
Embedded system
Community hub
Embedded system
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
Embedded system
Embedded system
Embedded system
View on Wikipedia
from Wikipedia

An embedded system on a plug-in card with processor, memory, power supply, and external interfaces

An embedded system is a specialized computer system—a combination of a computer processor, computer memory, and input/output peripheral devices—that has a dedicated function within a larger mechanical or electronic system.[1][2] It is embedded as part of a complete device often including electrical or electronic hardware and mechanical parts. Because an embedded system typically controls physical operations of the machine that it is embedded within, it often has real-time computing constraints. Embedded systems control many devices in common use.[3] In 2009, it was estimated that ninety-eight percent of all microprocessors manufactured were used in embedded systems.[4][needs update]

Modern embedded systems are often based on microcontrollers (i.e. microprocessors with integrated memory and peripheral interfaces), but ordinary microprocessors (using external chips for memory and peripheral interface circuits) are also common, especially in more complex systems. In either case, the processor(s) used may be types ranging from general purpose to those specialized in a certain class of computations, or even custom designed for the application at hand. A common standard class of dedicated processors is the digital signal processor (DSP).

Since the embedded system is dedicated to specific tasks, design engineers can optimize it to reduce the size and cost of the product and increase its reliability and performance. Some embedded systems are mass-produced, benefiting from economies of scale.

Embedded systems range in size from portable personal devices such as digital watches and MP3 players to bigger machines like home appliances, industrial assembly lines, robots, transport vehicles, traffic light controllers, and medical imaging systems. Often they constitute subsystems of other machines like avionics in aircraft and astrionics in spacecraft. Large installations like factories, pipelines, and electrical grids rely on multiple embedded systems networked together. Generalized through software customization, embedded systems such as programmable logic controllers frequently comprise their functional units.

Embedded systems range from those low in complexity, with a single microcontroller chip, to very high with multiple units, peripherals and networks, which may reside in equipment racks or across large geographical areas connected via long-distance communications lines.

History

[edit]

Background

[edit]
See also: Microprocessor chronology

The origins of the microprocessor and the microcontroller can be traced back to the MOS integrated circuit, which is an integrated circuit chip fabricated from MOSFETs (metal–oxide–semiconductor field-effect transistors) and was developed in the early 1960s. By 1964, MOS chips had reached higher transistor density and lower manufacturing costs than bipolar chips. MOS chips further increased in complexity at a rate predicted by Moore's law, leading to large-scale integration (LSI) with hundreds of transistors on a single MOS chip by the late 1960s. The application of MOS LSI chips to computing was the basis for the first microprocessors, as engineers began recognizing that a complete computer processor system could be contained on several MOS LSI chips.[5]

The first multi-chip microprocessors, the Four-Phase Systems AL1 in 1969 and the Garrett AiResearch MP944 in 1970, were developed with multiple MOS LSI chips. The first single-chip microprocessor was the Intel 4004, released in 1971. It was developed by Federico Faggin, using his silicon-gate MOS technology, along with Intel engineers Marcian Hoff and Stan Mazor, and Busicom engineer Masatoshi Shima.[6]

Development

[edit]

One of the first recognizably modern embedded systems was the Apollo Guidance Computer,[7] developed ca. 1965 by Charles Stark Draper at the MIT Instrumentation Laboratory. At the project's inception, the Apollo guidance computer was considered the riskiest item in the Apollo project as it employed the then newly developed monolithic integrated circuits to reduce the computer's size and weight.

An early mass-produced embedded system was the Autonetics D-17 guidance computer for the Minuteman missile, released in 1961. When the Minuteman II went into production in 1966, the D-17 was replaced with a new computer that represented the first high-volume use of integrated circuits.

Since these early applications in the 1960s, embedded systems have come down in price and there has been a dramatic rise in processing power and functionality. An early microprocessor, the Intel 4004 (released in 1971), was designed for calculators and other small systems but still required external memory and support chips. By the early 1980s, memory, input and output system components had been integrated into the same chip as the processor forming a microcontroller. Microcontrollers find applications where a general-purpose computer would be too costly. As the cost of microprocessors and microcontrollers fell, the prevalence of embedded systems increased.

A comparatively low-cost microcontroller may be programmed to fulfill the same role as a large number of separate components. With microcontrollers, it became feasible to replace, even in consumer products, expensive knob-based analog components such as potentiometers and variable capacitors with up/down buttons or knobs read out by a microprocessor. Although in this context an embedded system is usually more complex than a traditional solution, most of the complexity is contained within the microcontroller itself. Very few additional components may be needed and most of the design effort is in the software. Software prototype and test can be quicker compared with the design and construction of a new circuit not using an embedded processor.

Applications

[edit]
Embedded Computer Sub-Assembly for Accupoll Electronic Voting Machine[8]

Embedded systems are commonly found in consumer, industrial, automotive, home appliances, medical, telecommunication, commercial, aerospace and military applications.

Telecommunications systems employ numerous embedded systems from telephone switches for the network to cell phones at the end user. Computer networking uses dedicated routers and network bridges to route data.

Consumer electronics include MP3 players, television sets, mobile phones, video game consoles, digital cameras, GPS receivers, and printers. Household appliances, such as microwave ovens, washing machines and dishwashers, include embedded systems to provide flexibility, efficiency and features. Advanced heating, ventilation, and air conditioning (HVAC) systems use networked thermostats to more accurately and efficiently control temperature that can change by time of day and season. Home automation uses wired and wireless networking that can be used to control lights, climate, security, audio/visual, surveillance, etc., all of which use embedded devices for sensing and controlling.

Transportation systems from flight to automobiles increasingly use embedded systems. New airplanes contain advanced avionics such as inertial guidance systems and GPS receivers that also have considerable safety requirements. Spacecraft rely on astrionics systems for trajectory correction. Various electric motors — brushless DC motors, induction motors and DC motors — use electronic motor controllers. Automobiles, electric vehicles, and hybrid vehicles increasingly use embedded systems to maximize efficiency and reduce pollution. Other automotive safety systems using embedded systems include anti-lock braking system (ABS), electronic stability control (ESC/ESP), traction control (TCS) and automatic four-wheel drive.

Medical equipment uses embedded systems for monitoring, and various medical imaging (positron emission tomography (PET), single-photon emission computed tomography (SPECT), computed tomography (CT), and magnetic resonance imaging (MRI) for non-invasive internal inspections. Embedded systems within medical equipment are often powered by industrial computers.[9]

Embedded systems are used for safety-critical systems in aerospace and defense industries. Unless connected to wired or wireless networks via on-chip 3G cellular or other methods for IoT monitoring and control purposes, these systems can be isolated from hacking and thus be more secure.[citation needed] For fire safety, the systems can be designed to have a greater ability to handle higher temperatures and continue to operate. In dealing with security, the embedded systems can be self-sufficient and be able to deal with cut electrical and communication systems.

Miniature wireless devices called motes are networked wireless sensors. Wireless sensor networking makes use of miniaturization made possible by advanced integrated circuit (IC) design to couple full wireless subsystems to sophisticated sensors, enabling people and companies to measure a myriad of things in the physical world and act on this information through monitoring and control systems. These motes are completely self-contained and will typically run off a battery source for years before the batteries need to be changed or charged.

Characteristics

[edit]

Embedded systems are designed to perform a specific task, in contrast with general-purpose computers designed for multiple tasks. Some have real-time performance constraints that must be met, for reasons such as safety and usability; others may have low or no performance requirements, allowing the system hardware to be simplified to reduce costs.

Embedded systems are not always standalone devices. Many embedded systems are a small part within a larger device that serves a more general purpose. For example, the Gibson Robot Guitar features an embedded system for tuning the strings, but the overall purpose of the Robot Guitar is to play music.[10] Similarly, an embedded system in an automobile provides a specific function as a subsystem of the car itself.

e-con Systems eSOM270 & eSOM300 Computer on Modules

The program instructions written for embedded systems are referred to as firmware, and are stored in read-only memory or flash memory chips. They run with limited computer hardware resources: little memory, small or non-existent keyboard or screen.

User interfaces

[edit]
Embedded system text user interface using MicroVGA[nb 1]

Embedded systems range from no user interface at all, in systems dedicated to one task, to complex graphical user interfaces that resemble modern computer desktop operating systems. Simple embedded devices use buttons, light-emitting diodes (LED), graphic or character liquid-crystal displays (LCD) with a simple menu system. More sophisticated devices that use a graphical screen with touch sensing or screen-edge soft keys provide flexibility while minimizing space used: the meaning of the buttons can change with the screen, and selection involves the natural behavior of pointing at what is desired.

Some systems provide user interface remotely with the help of a serial (e.g. RS-232) or network (e.g. Ethernet) connection. This approach extends the capabilities of the embedded system, avoids the cost of a display, simplifies the board support package (BSP) and allows designers to build a rich user interface on the PC. A good example of this is the combination of an embedded HTTP server running on an embedded device (such as an IP camera or a network router). The user interface is displayed in a web browser on a PC connected to the device.

Processors in embedded systems

[edit]

Examples of properties of typical embedded computers when compared with general-purpose counterparts, are low power consumption, small size, rugged operating ranges, and low per-unit cost. This comes at the expense of limited processing resources.

Numerous microcontrollers have been developed for embedded systems use. General-purpose microprocessors are also used in embedded systems, but generally, require more support circuitry than microcontrollers.

Ready-made computer boards

[edit]

PC/104 and PC/104+ are examples of standards for ready-made computer boards intended for small, low-volume embedded and ruggedized systems. These are mostly x86-based and often physically small compared to a standard PC, although still large compared to most simple (8/16-bit) embedded systems. They may use a standard operating system such as Linux or NetBSD or an embedded real-time operating system (RTOS) such as MicroC/OS-II, QNX or VxWorks.

In certain applications, where small size or power efficiency are not primary concerns, the components used may be compatible with those used in general-purpose x86 personal computers. Boards such as the VIA EPIA range help to bridge the gap by being PC-compatible but highly integrated, physically smaller or have other attributes making them attractive to embedded engineers. The advantage of this approach is that low-cost commodity components may be used along with the same software development tools used for general software development. Systems built in this way are still regarded as embedded since they are integrated into larger devices and fulfill a single role. Examples of devices that may adopt this approach are automated teller machines (ATM) and arcade machines, which contain code specific to the application.

However, most ready-made embedded systems boards are not PC-centered and do not use the ISA or PCI busses. When a system-on-a-chip processor is involved, there may be little benefit to having a standardized bus connecting discrete components, and the environment for both hardware and software tools may be very different.

One common design style uses a small system module, perhaps the size of a business card, holding high density BGA chips such as an ARM-based system-on-a-chip processor and peripherals, external flash memory for storage, and DRAM for runtime memory. The module vendor will usually provide boot software and make sure there is a selection of operating systems, usually including Linux and some real-time choices. These modules can be manufactured in high volume, by organizations familiar with their specialized testing issues, and combined with much lower volume custom mainboards with application-specific external peripherals. Prominent examples of this approach include Arduino and Raspberry Pi.

ASIC and FPGA SoC solutions

[edit]

A system on a chip (SoC) contains a complete system - consisting of multiple processors, multipliers, caches, even different types of memory and commonly various peripherals like interfaces for wired or wireless communication on a single chip. Often graphics processing units (GPU) and DSPs are included such chips. SoCs can be implemented as an application-specific integrated circuit (ASIC) or using a field-programmable gate array (FPGA) which typically can be reconfigured.

ASIC implementations are common for very-high-volume embedded systems like mobile phones and smartphones. ASIC or FPGA implementations may be used for not-so-high-volume embedded systems with special needs in kind of signal processing performance, interfaces and reliability, like in avionics.

Peripherals

[edit]
A close-up of the SMSC LAN91C110 (SMSC 91x) chip, an embedded Ethernet chip

Embedded systems talk with the outside world via peripherals, such as:

Tools

[edit]

As with other software, embedded system designers use compilers, assemblers, and debuggers to develop embedded system software. However, they may also use more specific tools:

  • In circuit debuggers or emulators (see next section).
  • Utilities to add a checksum or CRC to a program, so the embedded system can check if the program is valid.
  • For systems using digital signal processing, developers may use a computational notebook to simulate the mathematics.
  • System-level modeling and simulation tools help designers to construct simulation models of a system with hardware components such as processors, memories, DMA, interfaces, buses and software behavior flow as a state diagram or flow diagram using configurable library blocks. Simulation is conducted to select the right components by performing power vs. performance trade-offs, reliability analysis and bottleneck analysis. Typical reports that help a designer to make architecture decisions include application latency, device throughput, device utilization, power consumption of the full system as well as device-level power consumption.
  • A model-based development tool creates and simulates graphical data flow and UML state chart diagrams of components like digital filters, motor controllers, communication protocol decoding and multi-rate tasks.
  • Custom compilers and linkers may be used to optimize specialized hardware.
  • An embedded system may have its own special language or design tool, or add enhancements to an existing language such as Forth or Basic.
  • Another alternative is to add a RTOS or embedded operating system
  • Modeling and code generating tools often based on state machines

Software tools can come from several sources:

  • Software companies that specialize in the embedded market
  • Ported from the GNU software development tools
  • Sometimes, development tools for a personal computer can be used if the embedded processor is a close relative to a common PC processor

Embedded software often requires a variety of development tools, including programming languages such as C++, Rust, or Python, and frameworks like Qt for graphical interfaces. These tools enable developers to create efficient, scalable, and feature-rich applications tailored to the specific requirements of embedded systems. The choice of tools is driven by factors such as real-time performance, integration with hardware, or energy efficiency.

As the complexity of embedded systems grows, higher-level tools and operating systems are migrating into machinery where it makes sense. For example, cellphones, personal digital assistants and other consumer computers often need significant software that is purchased or provided by a person other than the manufacturer of the electronics. In these systems, an open programming environment such as Linux, NetBSD, FreeBSD, OSGi or Embedded Java is required so that the third-party software provider can sell to a large market.

Debugging

[edit]

Embedded debugging may be performed at different levels, depending on the facilities available. Considerations include: does it slow down the main application, how close is the debugged system or application to the actual system or application, how expressive are the triggers that can be set for debugging (e.g., inspecting the memory when a particular program counter value is reached), and what can be inspected in the debugging process (such as, only memory, or memory and registers, etc.).

From simplest to most sophisticated debugging techniques and systems are roughly grouped into the following areas:

  • Interactive resident debugging, using the simple shell provided by the embedded operating system (e.g. Forth and Basic)
  • Software-only debuggers have the benefit that they do not need any hardware modification but have to carefully control what they record in order to conserve time and storage space.[11]
  • External debugging using logging or serial port output to trace operation using either a monitor in flash or using a debug server like the Remedy Debugger that even works for heterogeneous multicore systems.
  • An in-circuit debugger (ICD), a hardware device that connects to the microprocessor via a JTAG or Nexus interface.[12] This allows the operation of the microprocessor to be controlled externally, but is typically restricted to specific debugging capabilities in the processor.
  • An in-circuit emulator (ICE) replaces the microprocessor with a simulated equivalent, providing full control over all aspects of the microprocessor.
  • A complete emulator provides a simulation of all aspects of the hardware, allowing all of it to be controlled and modified, and allowing debugging on a normal PC. The downsides are expense and slow operation, in some cases up to 100 times slower than the final system.
  • For SoC designs, the typical approach is to verify and debug the design on an FPGA prototype board. Tools such as Certus[13] are used to insert probes in the FPGA implementation that make signals available for observation. This is used to debug hardware, firmware and software interactions across multiple FPGAs in an implementation with capabilities similar to a logic analyzer.

Unless restricted to external debugging, the programmer can typically load and run software through the tools, view the code running in the processor, and start or stop its operation. The view of the code may be as high-level programming language, assembly code or mixture of both.

Tracing

[edit]

Real-time operating systems often support tracing of operating system events. A graphical view is presented by a host PC tool, based on a recording of the system behavior. The trace recording can be performed in software, by the RTOS, or by special tracing hardware. RTOS tracing allows developers to understand timing and performance issues of the software system and gives a good understanding of the high-level system behaviors. Trace recording in embedded systems can be achieved using hardware or software solutions. Software-based trace recording does not require specialized debugging hardware and can be used to record traces in deployed devices, but it can have an impact on CPU and RAM usage.[14] One example of a software-based tracing method used in RTOS environments is the use of empty macros which are invoked by the operating system at strategic places in the code, and can be implemented to serve as hooks.

Reliability

[edit]

Embedded systems often reside in machines that are expected to run continuously for years without error, and in some cases recover by themselves if an error occurs. Therefore, the software is usually developed and tested more carefully than that for personal computers, and unreliable mechanical moving parts such as disk drives, switches or buttons are avoided.

Specific reliability issues may include:

  • The system cannot safely be shut down for repair, or it is too inaccessible to repair. Examples include space systems, undersea cables, navigational beacons, bore-hole systems, and automobiles.
  • The system must be kept running for safety reasons. Reduced functionality in the event of failure may be intolerable. Often backups are selected by an operator. Examples include aircraft navigation, reactor control systems, safety-critical chemical factory controls, train signals.
  • The system will lose large amounts of money when shut down: Telephone switches, factory controls, bridge and elevator controls, funds transfer and market making, automated sales and service.

A variety of techniques are used, sometimes in combination, to recover from errors—both software bugs such as memory leaks, and also soft errors in the hardware:

  • watchdog timer that resets and restarts the system unless the software periodically notifies the watchdog subsystems
  • Designing with a trusted computing base (TCB) architecture ensures a highly secure and reliable system environment[15]
  • A hypervisor designed for embedded systems is able to provide secure encapsulation for any subsystem component so that a compromised software component cannot interfere with other subsystems, or privileged-level system software.[16] This encapsulation keeps faults from propagating from one subsystem to another, thereby improving reliability. This may also allow a subsystem to be automatically shut down and restarted on fault detection.
  • Immunity-aware programming can help engineers produce more reliable embedded systems code.[17][18] Guidelines and coding rules such as MISRA C/C++ aim to assist developers produce reliable, portable firmware in a number of different ways: typically by advising or mandating against coding practices which may lead to run-time errors (memory leaks, invalid pointer uses), use of run-time checks and exception handling (range/sanity checks, divide-by-zero and buffer index validity checks, default cases in logic checks), loop bounding, production of human-readable, well commented and well structured code, and avoiding language ambiguities which may lead to compiler-induced inconsistencies or side-effects (expression evaluation ordering, recursion, certain types of macro). These rules can often be used in conjunction with code static checkers or bounded model checking for functional verification purposes, and also assist in determination of code timing properties.[17]

High vs. low volume

[edit]

For high-volume systems such as mobile phones, minimizing cost is usually the primary design consideration. Engineers typically select hardware that is just good enough to implement the necessary functions.

For low-volume or prototype embedded systems, general-purpose computers may be adapted by limiting the programs or by replacing the operating system with an RTOS.

Embedded software architectures

[edit]
Main article: Embedded software

In 1978 National Electrical Manufacturers Association released ICS 3-1978, a standard for programmable microcontrollers,[19] including almost any computer-based controllers, such as single-board computers, numerical, and event-based controllers.

There are several different types of software architecture in common use.

Simple control loop

[edit]

In this design, the software simply has a loop which monitors the input devices. The loop calls subroutines, each of which manages a part of the hardware or software. Hence it is called a simple control loop or programmed input-output.

Interrupt-controlled system

[edit]

Some embedded systems are predominantly controlled by interrupts. This means that tasks performed by the system are triggered by different kinds of events; an interrupt could be generated, for example, by a timer at a predefined interval, or by a serial port controller receiving data.

This architecture is used if event handlers need low latency, and the event handlers are short and simple. These systems run a simple task in a main loop also, but this task is not very sensitive to unexpected delays. Sometimes the interrupt handler will add longer tasks to a queue structure. Later, after the interrupt handler has finished, these tasks are executed by the main loop. This method brings the system close to a multitasking kernel with discrete processes.

Cooperative multitasking

[edit]

Cooperative multitasking is very similar to the simple control loop scheme, except that the loop is hidden in an API.[3][1] The programmer defines a series of tasks, and each task gets its own environment to run in. When a task is idle, it calls an idle routine which passes control to another task.

The advantages and disadvantages are similar to that of the control loop, except that adding new software is easier, by simply writing a new task, or adding to the queue.

Preemptive multitasking or multi-threading

[edit]

In this type of system, a low-level piece of code switches between tasks or threads based on a timer invoking an interrupt. This is the level at which the system is generally considered to have an operating system kernel. Depending on how much functionality is required, it introduces more or less of the complexities of managing multiple tasks running conceptually in parallel.

As any code can potentially damage the data of another task (except in systems using a memory management unit) programs must be carefully designed and tested, and access to shared data must be controlled by some synchronization strategy such as message queues, semaphores or a non-blocking synchronization scheme.

Because of these complexities, it is common for organizations to use an off-the-shelf RTOS, allowing the application programmers to concentrate on device functionality rather than operating system services. The choice to include an RTOS brings in its own issues, however, as the selection must be made prior to starting the application development process. This timing forces developers to choose the embedded operating system for their device based on current requirements and so restricts future options to a large extent.[20]

The level of complexity in embedded systems is continuously growing as devices are required to manage peripherals and tasks such as serial, USB, TCP/IP, Bluetooth, Wireless LAN, trunk radio, multiple channels, data and voice, enhanced graphics, multiple states, multiple threads, numerous wait states and so on. These trends are leading to the uptake of embedded middleware in addition to an RTOS.

Microkernels and exokernels

[edit]

A microkernel allocates memory and switches the CPU to different threads of execution. User-mode processes implement major functions such as file systems, network interfaces, etc.

Exokernels communicate efficiently by normal subroutine calls. The hardware and all the software in the system are available to and extensible by application programmers.

Monolithic kernels

[edit]

A monolithic kernel is a relatively large kernel with sophisticated capabilities adapted to suit an embedded environment. This gives programmers an environment similar to a desktop operating system like Linux or Microsoft Windows, and is therefore very productive for development. On the downside, it requires considerably more hardware resources, is often more expensive, and, because of the complexity of these kernels, can be less predictable and reliable.

Common examples of embedded monolithic kernels are embedded Linux, VXWorks and Windows CE.

Despite the increased cost in hardware, this type of embedded system is increasing in popularity, especially on the more powerful embedded devices such as wireless routers and GPS navigation systems.

Additional software components

[edit]

In addition to the core operating system, many embedded systems have additional upper-layer software components. These components include networking protocol stacks like CAN, TCP/IP, FTP, HTTP, and HTTPS, and storage capabilities like FAT and flash memory management systems. If the embedded device has audio and video capabilities, then the appropriate drivers and codecs will be present in the system. In the case of the monolithic kernels, many of these software layers may be included in the kernel. In the RTOS category, the availability of additional software components depends upon the commercial offering.

Domain-specific architectures

[edit]

In the automotive sector, AUTOSAR is a standard architecture for embedded software.

See also

[edit]

Notes

[edit]

References

[edit]

Further reading

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Embedded system

View on Grokipedia
from Grokipedia
An embedded system is a specialized, microprocessor-based computer system designed to perform dedicated functions within a larger mechanical, electrical, or electronic device, often under constraints of size, power consumption, and cost. These systems integrate hardware components such as microcontrollers, , and interfaces with tailored software to control and monitor specific tasks, distinguishing them from general-purpose computers. Key components of embedded systems include a central processing unit (CPU) or microcontroller that executes instructions, volatile memory like RAM for temporary data storage, non-volatile memory such as ROM or flash for program storage, and peripherals for interacting with the environment, including sensors for input and actuators for output. Software in these systems is typically custom-developed, often using real-time operating systems (RTOS) to ensure timely responses, and is programmed in languages like C or assembly for efficiency. Architectures vary, with common designs employing Harvard architecture—separating instruction and data buses for parallel access—or von Neumann architecture using a shared bus, influencing performance in resource-limited environments. Embedded systems are classified by scale and : small-scale systems use 8- or 16-bit microcontrollers without an OS for simple tasks like sensor monitoring; medium-scale employ 32-bit processors with RTOS for applications requiring multitasking, such as (HVAC) controls; and large-scale involve multiprocessor setups with extensive codebases for sophisticated functions like network routing. They operate in real-time modes, reacting to inputs within strict deadlines to maintain and reliability, particularly in critical domains. Applications span diverse industries, including automotive systems like engine controls and airbags, medical devices such as pacemakers, consumer electronics like smart appliances, industrial automation for , and infrastructure. In the Internet of Things (IoT) era, embedded systems enable connectivity, allowing devices to interface with networks for data exchange and remote monitoring. Their evolution traces back to early control systems in the but accelerated in the late with affordable microcontrollers, embedding computing intelligence into everyday objects and forming the backbone of cyber-physical systems.

Overview

Definition

An embedded system is a specialized computer system—a combination of hardware and software—designed to perform specific, dedicated functions within a larger mechanical or electrical system, often operating under constraints to meet precise timing requirements. This integration allows the system to control, monitor, or automate tasks without the need for general user interaction beyond its intended purpose. At its core, an embedded system comprises a or for processing, for storing instructions and data, and input/output peripherals for interfacing with the external environment, all combined into a compact, integrated unit. These components are tailored to the system's specific application, enabling efficient operation in constrained environments. In contrast to general-purpose computers, which support a wide range of tasks and user modifications, embedded systems prioritize reliability and efficiency due to their resource limitations, including restricted and power, and hardware that is typically not user-upgradable. The term "embedded system" originated in the as became integrated into non-computer products. Examples include simple thermostats for temperature regulation and complex control units (ECUs) for vehicle management.

Key Characteristics

Embedded systems are distinguished by their stringent resource limitations, which prioritize efficiency over the expansive capabilities of . These systems typically operate with minimal compared to general-purpose systems, often ranging from kilobytes to several gigabytes depending on the application and scale, to accommodate compact hardware designs while executing specialized tasks without excess overhead. Processing power varies widely, featuring processors from low MHz speeds in simple controllers to multi-GHz in complex applications, optimized for specific functions to ensure predictable behavior under computational budgets tailored to the task. Power consumption is a critical constraint, with designs emphasizing low energy use—ranging from microwatts in ultra-low-power sensors to several watts in more demanding devices—to support prolonged operation in resource-scarce environments, such as remote sensors or portable devices. A defining trait of embedded systems is their real-time operation, where timely task execution is paramount to functionality and safety. Hard real-time systems enforce strict deadlines, where missing a response—such as within milliseconds for safety-critical applications like automotive braking controls—can result in , demanding deterministic scheduling to guarantee compliance. In contrast, soft real-time systems tolerate occasional deadline misses, accepting performance degradation but avoiding total system collapse, as seen in streaming where brief delays affect quality but not operability. These constraints necessitate specialized operating mechanisms that prioritize temporal predictability over throughput. Reliability is engineered into embedded systems through metrics like (MTBF), often targeting tens of thousands of hours or more to ensure long-term stability in unattended deployments. is achieved via , such as duplicating critical components or using error-correcting codes, to detect and recover from hardware or software faults without interrupting core operations. This focus on robustness stems from the systems' integration into mission-critical environments, where is intolerable. Cost and size constraints drive embedded system design toward for high-volume production, minimizing per-unit expenses through standardized components and streamlined processes. Compact form factors, often smaller than a for many applications, enforce to fit within host devices like wearables or appliances, balancing functionality with physical limitations. User interfaces in embedded systems vary from basic elements like LEDs for status indication and buttons for simple input to more advanced touchscreens in consumer-oriented designs, yet many prioritize non-interactive operation to reduce complexity and power draw. Power sources for embedded systems range from battery-operated configurations, which demand high to extend operational life—often through techniques like dynamic voltage scaling—to plugged-in setups in stationary applications, where steady power availability allows less stringent optimization. remains a universal design goal, targeting minimal leakage and idle consumption to sustain performance across diverse energy profiles.

History

Origins and Background

The conceptual foundations of embedded systems trace back to early developments in , particularly the field of pioneered by in his 1948 book Cybernetics: Or Control and Communication in the Animal and the Machine. Wiener introduced the idea of feedback loops as mechanisms for self-regulation in both biological and mechanical systems, emphasizing how cycles enable stable control despite external disturbances. This work laid the groundwork for automated systems by highlighting the need for continuous monitoring and adjustment, influencing later designs in industrial and computational controls. In the pre-digital era of the 1940s and 1950s, automation relied heavily on analog control systems and relay-based mechanisms to manage industrial processes. These systems used electromagnetic relays for on-off switching and basic sequencing in machinery, such as assembly lines and power plants, where analog sensors provided continuous variable inputs for proportional control. Relay logic allowed for rudimentary programmable behavior without electronic computation, enabling early automation in factories to handle repetitive tasks like material handling and process monitoring. For instance, relay panels in manufacturing equipment from this period facilitated sequential operations, marking a shift from manual oversight to semi-automated workflows. The advent of transistorization in the 1950s further propelled the evolution toward more compact and reliable control systems, replacing bulky vacuum tubes and paving the way for minicomputers and early integrated circuits (ICs). Transistors enabled smaller, lower-power circuits suitable for dedicated control applications, reducing size and heat generation while improving reliability in harsh environments. By the late 1950s, these advancements allowed for the integration of computational elements into machinery, setting the stage for digital control in specialized devices. The term "embedded system" emerged in the context of military and applications, coinciding with projects like the developed by MIT's Instrumentation Laboratory. These early systems were motivated by the need for in appliances and machinery to minimize human intervention, enhancing efficiency, safety, and precision in critical operations such as guidance and navigation. Civilian applications soon followed, with the 1968 Volkswagen 1600 introducing the first embedded system in a production vehicle to control electronic fuel injection. By embedding computational logic directly into devices, engineers addressed constraints like size, power, and real-time responsiveness, fundamentally shaping the discipline's focus on integrated, purpose-built computing.

Major Developments

The 1970s marked the microprocessor revolution, fundamentally transforming embedded systems by enabling compact, programmable control in dedicated devices. Intel's 4004, introduced in 1971 as the world's first single-chip , was initially designed for Busicom's electronic calculators, representing one of the earliest commercial embedded applications where it handled arithmetic and logic operations within a constrained environment. This innovation extended to consumer products like digital watches by the mid-1970s, where variants of the 4004 and subsequent chips like the facilitated timing and display functions in portable devices. In the 1980s, the rise of microcontrollers further integrated into everyday appliances, emphasizing single-chip solutions with built-in and peripherals for cost-effective embedded designs. The 8051, launched in 1980, became a cornerstone for this era due to its versatile architecture supporting timers, serial ports, and handling, making it ideal for real-time control. It saw widespread adoption in , such as VCRs, where it managed tape transport mechanisms, decoding, and playback timing, enabling more reliable and feature-rich home entertainment systems. The 1990s witnessed the emergence of sophisticated software ecosystems and networked applications, propelling embedded systems into complex domains like automotive control. Real-time operating systems (RTOS) such as , which gained traction after its 1987 debut, became essential for deterministic performance in safety-critical applications, while embedded Linux distributions like uClinux (introduced in 1998) offered open-source flexibility for resource-constrained devices. In , Bosch's electronic control units (ECUs) proliferated in 1990s vehicles, managing engine timing, , and emissions control through integrated microcontrollers and protocols developed earlier in the decade. The 2000s advanced wireless connectivity, laying groundwork for interconnected embedded ecosystems that foreshadowed the (IoT). The protocol, standardized in 2004 by the Zigbee Alliance based on , enabled low-power, for battery-operated sensors and actuators, facilitating applications in and industrial monitoring as an early IoT precursor. From the into the , embedded systems evolved toward intelligent, edge-computing paradigms, incorporating AI and open architectures for autonomous operations. Google's (TPU), announced in 2016, accelerated inference on specialized hardware, paving the way for AI/ML deployment at the edge in devices like smart cameras and wearables by optimizing computations with high efficiency. The , with its base specification frozen and openly released in 2014 before formal ratification of versions like 2017's v2.2, gained widespread adoption in embedded systems by the due to its , customizable design, powering microcontrollers in IoT and automotive applications from companies like and . Concurrently, integration enabled ultra-low-latency communication in embedded devices, supporting real-time applications such as connected vehicles and industrial robotics starting from commercial deployments around 2019. Throughout these decades, —positing that the number of transistors on a chip doubles approximately every two years, leading to exponential improvements in —drove profound and cost reductions in embedded systems, allowing integration of advanced features into smaller, more affordable devices like smartphones and sensors.

Hardware Components

Processors and Microcontrollers

units (MCUs) serve as the core of many embedded systems, integrating a (CPU), on-chip memory, and peripherals into a single chip for compact, low-power applications. These devices are optimized for cost-sensitive and energy-efficient designs, often featuring 8-bit, 16-bit, or 32-bit architectures suitable for real-time control tasks. A prominent example is the series, which targets deeply embedded systems with small footprints and minimal power consumption; the Cortex-M4, for instance, provides low interrupt latency and a while maintaining a low gate count for in devices like sensors and actuators. In contrast, microprocessors (MPUs) offer higher performance through separate components that interface with external and peripherals, making them ideal for more complex embedded applications requiring greater computational power. Unlike MCUs, MPUs emphasize and speed, often using architectures like x86 for industrial control systems such as panel PCs and human-machine interfaces (HMIs). Intel's embedded x86 processors, for example, enable analytics in industrial environments by supporting multi-core configurations and high-speed interfaces. For prototyping and development, ready-made boards like the and provide accessible platforms with integrated ARM-based processors and (GPIO) pins. The Compute Module 5 features a 64-bit processor running at 2.4 GHz, along with video and PCIe interfaces, facilitating rapid embedded system experimentation. Similarly, boards, such as the Zero, use a 32-bit Cortex-M0+ core with multiple digital I/O pins for interactive projects in IoT and control applications. Custom solutions extend embedded processing capabilities through application-specific integrated circuits () and field-programmable gate arrays (FPGAs). ASICs deliver tailored, low-power performance for specialized uses, such as in wearable medical devices where they balance functionality with battery life by integrating custom logic for health monitoring. FPGAs, like the AMD Xilinx Zynq UltraScale+ SoCs, combine reconfigurable programmable logic with processor cores, enabling dynamic hardware adaptation in embedded systems for tasks requiring flexibility, such as . Emerging trends in embedded processors include the adoption of open instruction set architectures (ISAs) like for cost-effective IoT deployments and dedicated AI accelerators. 's royalty-free design supports low-cost, customizable cores increasingly used in 2020s IoT devices for efficient . Recent trends as of 2025 also include hardware root of trust for enhanced security and neuromorphic architectures for energy-efficient AI processing. AI accelerators, such as Google's Coral Edge TPU, provide high-efficiency inference at 4 trillion operations per second () with just 2 watts, integrated into embedded boards for always-on applications like . Selecting processors for embedded systems involves evaluating factors like clock speed, core count, and ISA to match application demands. Clock speeds range from MHz in low-power MCUs to GHz in high-performance MPUs, influencing execution ; for instance, higher rates enable faster processing but require careful thermal management. Core count determines parallelism, with multi-core options boosting throughput in data-intensive tasks, while the ISA—such as ARM's for code density—affects compatibility and optimization. These criteria ensure alignment with constraints like power and cost, prioritizing architectures that deliver balanced performance without excess overhead.

Peripherals and Interfaces

Embedded systems rely on peripherals and interfaces to interact with the physical world, enabling them to sense environmental conditions, control actuators, and communicate with other devices or networks. These components are typically connected via the microcontroller's (GPIO) pins or dedicated ports, allowing the system to process inputs and generate outputs efficiently. Common peripherals in embedded systems include sensors for input and actuators for output. Sensors convert physical phenomena into electrical signals, often requiring analog-to-digital converters (ADCs) to interface with digital processors; for instance, temperature sensors like thermistors or thermocouples use ADCs to measure analog voltages and digitize them for processing. Actuators, conversely, receive control signals to perform actions, such as (PWM) outputs driving motors in or fans in cooling systems, where the duty cycle of the PWM signal regulates speed or power. These peripherals are selected based on the application's needs, with examples like accelerometers for motion detection in wearables or relays for switching high-power loads in industrial controls. Communication interfaces facilitate data exchange between the embedded system and external devices, categorized into wired and wireless types. Short-range wired protocols include (UART) for simple serial communication, (SPI) for high-speed synchronous transfers between a master and multiple slaves, and Inter-Integrated Circuit (I2C) for multi-device buses with addressing capabilities, commonly used in sensor networks. For networking, Ethernet provides high-bandwidth connectivity in industrial embedded systems, while Controller Area Network (CAN), standardized in 1986 by Bosch for automotive applications, enables robust, fault-tolerant communication in vehicles with real-time requirements like engine control units. Wireless interfaces extend connectivity for (IoT) and distributed systems. (BLE), introduced in 2010 as part of the Bluetooth 4.0 specification, supports low-power, short-range communication for devices like fitness trackers, with typical active mode (RX/TX) power consumption of 10–50 mW depending on transmit power and implementation. , based on standards, offers higher data rates up to 1 Gbps for multimedia streaming in smart home appliances, though it demands more power than BLE. , adhering to , is favored for low-power mesh networks in IoT applications like smart lighting, supporting up to 65,000 nodes with data rates around 250 kbps. Human-machine interfaces (HMI) in embedded systems are often simplified to conserve resources, focusing on essential user interaction. Displays such as liquid crystal displays (LCDs) or organic light-emitting diode (OLED) screens provide visual feedback in devices like digital thermostats, with OLEDs offering higher contrast and flexibility for compact designs. Keypads or touch interfaces allow input, but in resource-constrained systems like pacemakers, these are minimized or omitted in favor of remote configuration via links. Integrating multiple peripherals and interfaces poses challenges, particularly in managing shared resources and ensuring reliable operation. Bus arbitration protocols, such as those in I2C or SPI, resolve conflicts when multiple devices compete for access to the communication bus, using mechanisms like clock stretching or priority schemes to prevent . Interrupt handling is crucial for timely responses, where peripherals signal the processor via dedicated lines to trigger software routines, as seen in real-time systems where latency must remain below microseconds to avoid failures in safety-critical applications like airbags. These integration aspects demand careful hardware design to balance performance, power, and cost.

Memory and Power Management

In embedded systems, memory management revolves around balancing non-volatility, density, and access speed to support firmware storage and runtime operations within constrained resources. Non-volatile memory, such as Read-Only Memory (ROM) and Flash, is essential for storing firmware and boot code, retaining data without power. Flash memory variants include NOR Flash, which enables direct code execution (XIP) due to its random access capabilities, and NAND Flash, favored for higher density and lower cost in bulk storage applications. For runtime data, volatile Random Access Memory (RAM) like Static RAM (SRAM) provides fast, low-latency access for caches and variables, while Dynamic RAM (DRAM) offers greater density for larger datasets; typical embedded RAM capacities range from kilobytes in microcontrollers to up to 512 MB in more complex systems. Secondary storage options extend embedded systems' capabilities for data logging and persistent user data beyond on-chip limits. Secure Digital (SD) cards provide removable, high-capacity storage up to several terabytes, suitable for field-upgradable applications like in sensors. Embedded MultiMediaCard (eMMC) integrates NAND Flash with a controller for compact, high-performance block storage in devices such as smartphones and IoT gateways, enabling efficient logging of operational data. Power management techniques are crucial for prolonging battery life and ensuring reliability in resource-limited environments. Sleep modes, including ARM's C-states (e.g., C0 for active, deeper states like C3 for standby), halt clock signals to idle components, reducing dynamic power while allowing quick resumption via interrupts. Dynamic Voltage Scaling (DVS) adjusts supply voltage and frequency based on workload, yielding quadratic reductions in dynamic power consumption—enabling transitions from active levels around 100 mW to sleep states as low as 1 μW in optimized designs. further minimizes leakage by disabling clocks to unused modules, a standard in low-power microcontrollers (MCUs). Battery considerations in embedded systems prioritize lithium-ion (Li-ion) cells for their high , managed through systems that monitor voltage, , and state-of-charge to prevent overcharge or . Energy harvesting supplements or replaces batteries in remote sensors, capturing ambient sources like solar photovoltaic cells for steady illumination or piezoelectric/vibrational mechanisms for in wearables. These elements involve inherent trade-offs: non-volatile memories like Flash offer density advantages over volatile SRAM/DRAM but at the cost of slower write speeds and limited endurance, impacting performance in write-intensive tasks. Power optimizations such as DVS and sleep modes enhance efficiency but require careful calibration to avoid latency penalties in real-time applications, balancing energy savings against computational demands.

Embedded Software

Core Architectures

Core architectures in embedded systems refer to the fundamental software structures that manage task execution, , and responsiveness to events without relying on a full operating system layer. These architectures evolve from basic polling mechanisms in resource-constrained environments to sophisticated scheduling techniques that ensure deterministic behavior, particularly in real-time applications. The choice of architecture depends on factors such as , timing requirements, and hardware capabilities, with simpler designs prioritizing minimal overhead and predictability. The simplest core architecture is the bare-metal or foreground-background model, often implemented as a "superloop" or infinite main loop that sequentially executes tasks. In this approach, the software runs directly on the hardware without an intermediary OS, using polling to periodically check for events such as sensor inputs or user interactions. For example, an infinite loop might continuously monitor a temperature sensor by reading its value at fixed intervals, processing data if a threshold is exceeded, and then looping back to repeat the cycle. This model, also known as the foreground-background architecture, divides execution into a background loop for non-time-critical tasks and foreground interrupts for urgent events, enabling low-power operation by allowing the microcontroller to sleep between polls while keeping interrupt enables active. Its advantages include simplicity, minimal memory footprint, and full hardware control, making it ideal for small, low-complexity systems like basic controllers. To handle asynchronous events more efficiently, interrupt-driven systems build on bare-metal by incorporating hardware interrupts that pause the main loop and transfer control to an interrupt service routine (ISR). Interrupts signal the processor when an external or internal event occurs, such as a timer overflow or peripheral data ready, allowing asynchronous processing without constant polling. For instance, a interrupt can trigger periodic tasks like updating a display every , ensuring timely execution even if the main loop is busy. This architecture reduces CPU idle time and improves responsiveness, but requires careful management to avoid interrupt overload, where excessive nesting or latency disrupts timing. In , interrupts are typically kept short to minimize context-switching overhead, with longer operations deferred to the main loop via flags or queues. For systems requiring concurrency among multiple tasks, cooperative multitasking introduces a lightweight form of scheduling where tasks voluntarily yield control to others, often using a round-robin mechanism. In this non-preemptive model, tasks run to completion or explicitly call a yield function before switching, relying on cooperative behavior to share the CPU. An example is the use of co-routines in FreeRTOS, which employ prioritized cooperative scheduling for lightweight threads that switch only at predefined yield points, suitable for memory-limited microcontrollers handling periodic sensor polling and communication. This approach simplifies debugging and reduces overhead compared to preemption but risks system hangs if a task fails to yield, limiting its use to applications with predictable task durations. More robust concurrency is achieved through preemptive multitasking, where a scheduler forcibly switches tasks based on priorities, enabling higher-priority tasks to interrupt lower ones via context switching. This priority-based scheduling ensures critical tasks meet deadlines by dynamically allocating , often implemented in real-time operating systems (RTOS). For example, employs preemptive priority scheduling, where tasks are assigned system-wide priorities, and the highest-priority ready task always runs, with round-robin time-slicing for equal-priority tasks to prevent . Context switches occur on interrupts or ticks, supporting deterministic execution in complex embedded environments like controls. In real-time embedded systems, core architectures emphasize deterministic execution to guarantee tasks complete within deadlines, often incorporating schedulability analysis for preemptive fixed-priority scheduling. Rate monotonic scheduling (RMS), a seminal fixed-priority algorithm, assigns higher priorities to tasks with shorter periods, optimizing for periodic workloads. RMS is optimal among static priority policies: if any fixed-priority scheduler can meet all deadlines, RMS can as well. Schedulability is tested using bounds like the utilization limit U≤n(21/n−1)U \leq n(2^{1/n} - 1) for nn tasks, where U=∑Ci/TiU = \sum C_i / T_i (execution time CiC_i over period TiT_i), ensuring feasibility even in worst-case simultaneous arrivals. This analysis, rooted in foundational work, enables verification of real-time performance without exhaustive simulation, critical for safety-critical applications.

Operating Systems and Kernels

Embedded systems often rely on specialized operating systems and kernels tailored for resource-constrained environments, where predictability, low latency, and efficient are paramount. These kernels manage core functions such as process scheduling, allocation, and device interactions, enabling reliable operation in devices ranging from microcontrollers to complex IoT nodes. Unlike general-purpose OS kernels, embedded variants prioritize minimal footprint and real-time capabilities to meet stringent timing requirements. Software is typically developed in languages like or assembly for efficiency, though emerging languages such as are gaining adoption for their features, particularly in safety-critical applications. Monolithic kernels, which integrate all major services—including file systems, device drivers, and networking—into a single address space, are widely used in embedded Linux distributions due to their performance efficiency and simplicity in implementation. This design minimizes inter-component communication overhead, allowing faster system calls and better throughput on resource-limited hardware. For instance, Buildroot facilitates the creation of customized embedded Linux systems by compiling a monolithic kernel alongside essential user-space tools, supporting cross-compilation for various architectures while keeping the overall image size small. In contrast, microkernels adopt a modular approach, confining the core kernel to essential functions like (IPC) and basic scheduling, while delegating services such as drivers and file systems to user-space processes. This architecture enhances reliability and fault isolation, as a failure in one service does not crash the entire system, making it suitable for safety-critical embedded applications. QNX Neutrino exemplifies this design, employing synchronous for IPC to coordinate modules efficiently, which supports its use in automotive and medical devices requiring high dependability. Exokernels represent a more radical, research-oriented paradigm, providing applications with direct access to hardware resources while the kernel handles only low-level and . Developed in prototypes at MIT, such as the system, exokernels avoid traditional abstractions to allow customized resource management, potentially improving performance for specialized workloads but at the cost of increased application complexity. These designs remain largely experimental in embedded contexts, influencing modern secure enclave technologies rather than widespread adoption. Real-time operating systems (RTOS) are prevalent in embedded systems to ensure deterministic behavior, with kernels supporting preemptive multitasking for timely task execution. , an open-source RTOS, offers a lightweight, preemptive scheduler that prioritizes higher-priority tasks, making it ideal for microcontrollers in and industrial controls, with a minimal under 10 KB. Similarly, Zephyr RTOS targets IoT applications, providing a scalable kernel with native support for architectures alongside and others, enabling secure, networked embedded devices through its modular device tree configuration. As of 2024, Zephyr includes support for , allowing developers to write applications in this safer language. Hybrid approaches bridge general-purpose and real-time needs, such as the patchset for the , which converts non-preemptible sections into preemptible ones and prioritizes real-time threads via high-resolution timers. This enables embedded systems to achieve soft real-time performance suitable for and automotive applications without fully replacing the kernel. In embedded deployments, reduces worst-case latencies to microseconds on standard hardware, facilitating reuse of Linux's vast ecosystem. At their core, embedded kernels handle essential functions to abstract hardware complexities: process management coordinates task creation, scheduling, and termination to optimize CPU utilization; memory protection enforces isolation between processes to prevent faults from propagating; and device drivers provide standardized interfaces for peripherals like sensors and actuators, ensuring portable code across hardware variants. These mechanisms collectively enable efficient in constrained environments.

Additional Components and Frameworks

Embedded systems often incorporate middleware layers to facilitate communication and integration between core software and application-specific needs, particularly in networked environments. , such as communication stacks, abstracts underlying protocols to enable efficient data exchange. For instance, serves as a lightweight publish/subscribe messaging protocol optimized for IoT applications, supporting low-bandwidth, high-latency connections with minimal overhead. Libraries extend embedded software functionality by providing reusable code for specialized tasks, reducing development time while maintaining resource efficiency. In graphics rendering, LVGL offers a free, open-source library for creating intuitive user interfaces on microcontrollers, supporting features like animations and touch inputs across various display types. For mathematical computations, the CMSIS-DSP library delivers optimized functions, including filters and transforms, tailored for processors to leverage . Domain-specific frameworks standardize architectures for particular industries, promoting interoperability and scalability. , established in 2003, defines a layered for automotive electronic control units, separating application logic from hardware-dependent modules to enhance reusability across vehicle systems. Similarly, the (ROS), introduced in 2007, provides a node-based suite for , enabling modular development through distributed processes that communicate via topics and services. Bootloaders initialize hardware and load the primary operating , forming a critical foundational layer in many embedded designs. U-Boot, an open-source universal bootloader, supports Linux-based systems by handling board-specific configurations, , and loading on diverse architectures like and PowerPC. Firmware updates ensure long-term reliability and security, with over-the-air (OTA) mechanisms becoming prevalent in 2020s smart devices for remote deployment without physical access. OTA processes typically involve secure download, validation, and seamless switching between partitions, as implemented in IoT ecosystems to address vulnerabilities efficiently. AI frameworks adapt machine learning for resource-constrained edges, enabling on-device inference. TensorFlow Lite, launched in 2017, optimizes models for microcontrollers through quantization and pruning, supporting deployments in applications like image recognition on embedded hardware.

Development and Debugging

Design Tools

Design tools for embedded systems encompass a range of software and hardware instruments that facilitate the creation, simulation, and verification of hardware and software components before physical implementation. These tools enable engineers to model system behavior, generate code, and debug signals efficiently, reducing development time and costs in resource-constrained environments. Integrated Development Environments (IDEs) are central to design, providing unified platforms for editing, compiling, and configuring peripherals. , developed by , is an Eclipse-based IDE tailored for microcontrollers, offering graphical peripheral configuration, automatic code generation from layers, and integrated capabilities. Similarly, Keil with µVision IDE supports processors, featuring an optimizer , real-time simulation, and integration for of embedded applications. Hardware tools aid in signal analysis and programming during the design phase. Oscilloscopes capture and display analog waveforms to verify voltage levels, timing, and noise in embedded circuits, while logic analyzers monitor multiple digital signals simultaneously to decode protocols and detect timing violations. For programming and initial debugging, (IEEE 1149.1 standard) and SWD interfaces provide standardized access to internals, allowing testing and flashing via debug probes. Simulation tools enable virtual prototyping without hardware. serves as an open-source for full-system simulation of embedded architectures, supporting and other CPUs to test software on virtual boards before deployment. For analog aspects, SPICE-based simulators like model circuit behavior, predicting responses in power supplies and sensors integrated into embedded designs. Version control and build systems streamline collaborative development of embedded C/C++ code. manages source code repositories, enabling branching and merging for team workflows in firmware projects. complements this as a cross-platform build generator, configuring toolchains for embedded targets and automating compilation across diverse hardware platforms. Modeling tools support high-level design of control systems. and from allow block-diagram-based modeling of algorithms, with Embedded Coder generating optimized C code for deployment on embedded processors, ensuring MISRA compliance for safety-critical applications. In the 2020s, open-source trends have popularized unified ecosystems like PlatformIO, which integrates IDE support, , and multi-platform builds for over 1,000 boards, fostering in embedded development. As of 2025, AI-driven tools for code generation, testing, and debugging have surged in adoption, streamlining development processes. The rise of open-source architectures is enabling more flexible and cost-effective designs, while enhanced practices, including continuous integration/continuous deployment () pipelines tailored for embedded targets, are improving collaboration and deployment speed.

Debugging and Testing Methods

Embedded systems debugging and testing are essential processes to identify and resolve issues in hardware-software integration, given the constrained environments and real-time demands that limit traditional diagnostic approaches. These methods enable developers to verify functionality, optimize performance, and ensure reliability without disrupting the target system's operation. Techniques range from hardware-assisted to simulation-based validation, often leveraging standardized interfaces for non-intrusive . In-circuit debugging provides direct access to the target's internal state during execution, allowing precise control and observation. This is commonly achieved through the interface, standardized as IEEE 1149.1, which connects debugging tools to the embedded processor via dedicated pins for access. Breakpoints halt execution at specific instructions, while watchpoints monitor memory or register changes to detect anomalies. The GNU Debugger (GDB) integrates seamlessly with JTAG probes, using the remote serial protocol to enable command-line control of embedded targets over TCP/IP or serial links. Tracing methods capture runtime events for post-execution analysis, minimizing intrusion on system timing. In -based systems, the Embedded Trace Macrocell (ETM) collects instruction execution history, including branches and data accesses, outputting compressed trace streams via dedicated pins for decoding by host tools. For simpler logging, printf-style output can be redirected through semihosting, a mechanism where ARM targets invoke host I/O routines via software interrupt (SWI) calls, facilitating debug messages without additional hardware. In-circuit emulation (ICE) offers advanced real-time monitoring by substituting the target with a pod that mimics its behavior while providing full visibility into signals and cycles. This approach, supported in processors from the ARM7TDMI onward, allows insertion, single-stepping, and directly in the circuit. Testing strategies complement debugging by validating components at various integration levels. isolates software modules using frameworks like Unity, a portable harness that runs assertions on resource-limited embedded platforms, supporting test suites for verification. Hardware-in-the-loop (HIL) integrates the real with a simulated plant model on a real-time host, enabling closed-loop testing of control algorithms under realistic conditions. Profiling tools analyze system dynamics, particularly in real-time operating systems (RTOS). Tracealyzer, developed by Percepio, delivers cycle-accurate visualizations of task scheduling, interrupts, and usage from trace data, aiding in the identification of timing bottlenecks and inefficiencies. Among common challenges, race conditions in multitasking environments pose significant debugging hurdles, arising from concurrent thread access to shared resources and leading to nondeterministic outcomes that are difficult to reproduce. Peripheral misconfigurations, such as incorrect register settings for interfaces like UART or SPI, often manifest as integration failures detectable through tracing or emulation.

Reliability and Security Practices

Embedded systems, integral to safety-critical applications such as automotive and domains, employ reliability practices to mitigate failures from hardware faults, environmental stressors, or software errors. (TMR) is a widely adopted technique where three identical modules perform computations in parallel, with a majority voting mechanism to select the correct output, thereby achieving against single-point failures; this approach has been foundational in radiation-hardened embedded designs for space missions since its conceptualization in the and practical implementation in systems like NASA's . Error-correcting codes (ECC), particularly Hamming codes and Reed-Solomon codes, are routinely integrated into memory subsystems to detect and correct bit errors caused by cosmic rays or , ensuring in resource-constrained environments; for instance, is commonly used in safety-critical automotive ECUs to prevent silent that could lead to system malfunctions. These practices enhance (MTBF), with TMR systems demonstrating significant improvements, often by factors of 10 to 100, in reliability for transient faults compared to non-redundant designs. Safety standards provide structured frameworks for certifying embedded systems in regulated industries. The ISO 26262 standard, published in 2011 and revised in 2018, outlines a risk-based approach for automotive electrical/electronic systems, defining Integrity Levels (ASIL) from A to D, where ASIL D requires the highest rigor for functions like to achieve failure rates below 10^-8 per hour; compliance involves , verification, and validation throughout the lifecycle. In avionics, , released in 2012 by RTCA, specifies software considerations for airborne systems, categorizing development assurance levels (DAL) A through E based on failure severity, with DAL A demanding exhaustive testing and traceability for catastrophic failure avoidance in flight control software. testing under these standards includes simulations and probabilistic modeling to verify that systems maintain safe states during faults, as seen in certified embedded controllers for unmanned aerial vehicles. Security practices in embedded systems address vulnerabilities inherent to their limited resources and connectivity. Secure boot mechanisms, such as ARM TrustZone introduced in 2003, partition the system into secure and non-secure worlds, using cryptographic signatures to verify integrity during startup, preventing unauthorized code execution; this has become ubiquitous in mobile and IoT devices to thwart rootkits. Encryption standards like the (AES), formalized by NIST in 2001 with FIPS 197, protect data at rest and in transit within embedded networks, employing 128-256 bit keys for in protocols such as TLS for smart home gateways. Vulnerability mitigation strategies include stack canaries and (ASLR) to prevent exploits, which remain a top threat in C-based embedded , significantly reducing the success of such attacks in hardened implementations. Threat models for embedded systems encompass both physical and logical attacks. Side-channel attacks, notably differential power analysis (DPA) detailed in 1999, exploit variations in power consumption during cryptographic operations to extract keys from devices like RFID tags, necessitating countermeasures such as masking or noise injection in embedded crypto engines. tampering in IoT ecosystems, often via compromises or over-the-air updates, poses risks of remote , as evidenced by vulnerabilities in devices like Mirai botnets affecting millions in 2016; mitigation involves runtime integrity checks and signed updates. Penetration testing tools like Binwalk, an open-source utility for analysis, enable to identify hidden or weak , supporting security audits in compliance with standards like NIST SP 800-53. Post-2020 trends reflect the convergence of embedded systems with cloud and , emphasizing advanced paradigms. Zero-trust models, as outlined in NIST SP 800-207 from 2020, advocate continuous verification of all access requests in embedded networks, eliminating implicit trust boundaries to counter insider threats and lateral movement in industrial IoT; implementations in systems like 5G base stations have reduced breach impacts by verifying device identities per transaction. AI-driven , leveraging models such as autoencoders on edge devices, identifies deviations in system behavior indicative of attacks or faults in real-time, with studies showing high detection accuracies for zero-day exploits in resource-limited sensors. These practices, integrated with reliability measures, ensure embedded systems remain resilient amid escalating cyber-physical threats. As of 2025, advancements in AI for continue to evolve, with improved models achieving accuracies exceeding 95% in IoT and embedded contexts.

Applications

Consumer and Everyday Devices

Embedded systems are integral to a wide array of consumer and everyday devices, where they enable efficient, user-friendly functionality while prioritizing low cost, compact design, and seamless integration with daily life. These systems often rely on specialized hardware like microcontrollers and system-on-chips (SoCs) to handle tasks ranging from data processing to connectivity, ensuring devices operate reliably in familiar environments such as homes and personal accessories. In smartphones, embedded systems are exemplified by highly integrated SoCs such as the series, which combine multiple CPU cores, GPUs, and modems on a single chip to manage demanding applications, sensor inputs, and processing. These ARM-based SoCs, like the Snapdragon 8 Elite, deliver high performance for tasks including AI acceleration and connectivity, powering a significant portion of the global market. Home appliances have long incorporated embedded systems for intelligent control, with washing machines adopting controllers starting in the late 1980s to dynamically adjust wash cycles based on load weight, fabric type, and soil level, improving efficiency over traditional fixed programs. Similarly, smart thermostats like the Learning use Wi-Fi-enabled embedded processors to learn user patterns, optimize heating and cooling, and integrate with home networks for . Wearable devices, such as fitness trackers, employ low-power microcontrollers (MCUs) like series to monitor and activity in real time while minimizing battery drain, often syncing data via (BLE) to smartphones or cloud services. These MCUs handle and basic algorithms with power consumption under a few milliwatts, enabling all-day operation on small batteries. Consumer embedded systems are produced in high volumes, often exceeding millions of units annually, which drives down costs for simple chips to under $1 per unit through mature manufacturing processes and . User interfaces in these devices emphasize , featuring touchscreens for direct interaction in smartphones and appliances, alongside voice controls integrated via platforms like for hands-free operation in thermostats and wearables.

Industrial and Specialized Systems

Embedded systems play a pivotal role in industrial and specialized applications, where they must operate in harsh environments, ensure high reliability, and deliver precise real-time control to support processes, transportation safety, and operations. These systems are engineered for durability against extreme temperatures, vibrations, and , often incorporating fault-tolerant designs to minimize downtime and risks in safety-critical scenarios. Unlike consumer devices, industrial embedded systems prioritize ruggedness and compliance with sector-specific standards, enabling automated control in sectors like automotive, medical, and . In the automotive sector, embedded systems are integral to vehicle performance and diagnostics through Electronic Control Units (ECUs), which manage functions such as engine timing, fuel injection, and emissions control. A key example is the On-Board Diagnostics II (OBD-II) standard, mandated for U.S. gasoline vehicles since 1996, which integrates with ECUs to provide standardized diagnostic access via various communication protocols, including those overlaid on the Controller Area Network (CAN) bus in modern vehicles, allowing real-time monitoring of parameters like engine speed and fault codes. Advanced Driver Assistance Systems (ADAS) further leverage embedded processors for processing sensor data from cameras and LiDAR, enabling features like object detection and collision avoidance through high-performance computing that handles uncompressed video and point-cloud data in real time, while adhering to safety standards such as ISO 26262. These systems ensure precise vehicle dynamics control, enhancing safety in high-speed transportation environments. Medical devices rely on embedded systems for life-sustaining precision, particularly in implantable and therapeutic equipment where ultra-low power consumption and are essential. Pacemakers employ low-power microcontrollers to continuously monitor heart rhythms and deliver electrical stimuli as needed, optimizing energy use in battery-operated designs that can last 5–15 years, while complying with for quality management in design, development, and manufacturing to ensure device safety and traceability. Similarly, infusion pumps use embedded control software to regulate fluid delivery rates with high accuracy, often managing over 100,000 lines of code for user interfaces, pumping mechanisms, and safety interlocks that prevent dosing errors, as researched by the FDA to mitigate software vulnerabilities through model-based verification and static analysis. These applications underscore the need for embedded systems that maintain therapeutic precision in clinical settings, reducing in critical care. Industrial automation benefits from embedded systems in programmable logic controllers (PLCs) and supervisory control architectures, which provide robust, deterministic control for manufacturing lines and process plants. PLCs function as rugged, solid-state industrial computers that replace traditional panels, interfacing with sensors and actuators via discrete inputs and outputs to execute control logic for tasks like conveyor sequencing and motor starting, programmed using diagrams that mimic electrical schematics for intuitive relay-based operations. Complementing PLCs, Supervisory Control and (SCADA) systems incorporate embedded microcontrollers, such as 32-bit devices, to enable remote monitoring and control of distributed processes like heat exchangers, supporting communication for visualization and emergency overrides in medium-scale industrial setups. These embedded solutions enhance and fault detection in environments demanding continuous uptime. Aerospace applications demand highly redundant embedded systems in to ensure flight safety amid extreme conditions, with data buses facilitating reliable inter-system communication. Avionics suites use triple-redundant architectures to process flight controls, navigation, and instrumentation, connected via the bus—a unidirectional, point-to-point serial protocol operating at 12.5 or 100 kbps with 32-bit word formats, designed in the for commercial and like the and A320. This bus supports through parallel wiring and multiple channels, though its low bandwidth poses challenges for integrating modern sensors, often requiring hybrid upgrades for legacy fleets. Such designs prioritize precision in attitude control and , critical for transportation in high-altitude operations. The design of embedded systems in these fields varies by production scale: aerospace often employs custom Application-Specific Integrated Circuits () for low-volume, mission-critical needs, where development costs can exceed $10–20 million due to rigorous certification and reliability demands, making per-unit expenses high despite superior performance in radiation-hardened environments. In contrast, automotive embedded systems favor standardized, off-the-shelf components and ECUs to support high-volume in the millions of units, amortizing s while meeting through software configurability rather than hardware. This distinction highlights how volume influences hardware choices, with industrial sectors balancing , customization, and .

Emerging Technologies

Embedded systems are increasingly integrated into (IoT) ecosystems, where vast networks facilitate collection and processing. These networks often employ edge gateways that utilize protocols like for efficient, lightweight communication between devices and cloud services, enabling scalable deployment across diverse environments. Projections indicate that the number of connected IoT devices will reach approximately 21.1 billion by the end of , underscoring the explosive growth of these interconnected systems. Edge computing represents a pivotal advancement, allowing embedded systems to perform local near the source, thereby minimizing latency and bandwidth demands on central networks. For instance, AWS IoT Greengrass, introduced in 2017, extends capabilities to edge devices, supporting functions such as inference and device shadowing while reducing response times to milliseconds. This approach is particularly vital for time-sensitive applications, where traditional reliance could introduce delays exceeding hundreds of milliseconds. The fusion of with embedded systems through TinyML enables on-device on resource-constrained microcontrollers (MCUs), democratizing AI deployment. A landmark example is the 2017 Google research on keyword spotting, adapted for processors, which achieved high accuracy with models under 100 KB in size—well below 1 MB—allowing always-on voice activation without cloud dependency. This integration empowers embedded devices to handle complex tasks like directly, conserving power and enhancing . Advancements in and emerging networks further amplify embedded systems' potential via ultra-reliable low-latency communication (URLLC), targeting latencies under 1 and reliability above 99.999%. URLLC supports critical applications such as drone swarms for and autonomous vehicles requiring instantaneous coordination, where embedded controllers process data in tandem with network slicing for prioritized traffic. These capabilities enable seamless operation in dynamic, high-stakes scenarios previously limited by connectivity constraints. Sustainability efforts in embedded systems emphasize energy-harvesting techniques, where sensors draw power from ambient sources like vibrations, light, or signals, eliminating battery replacements in remote deployments. In smart cities, piezoelectric and solar-based harvesters power nodes, contributing to efficient urban resource management and reducing . Such innovations align with global goals for low-carbon , enabling perpetual operation of distributed arrays. Despite these progresses, embedded systems in face significant challenges in and . The sheer volume of devices strains network resources and management frameworks, necessitating robust architectures to handle without performance degradation. remains a barrier due to fragmented protocols, though standards like the Matter protocol, initially released in 2022 and updated through versions such as 1.4.2 in 2025 to improve , , and stability, promote cross-vendor compatibility over IP-based networks, fostering unified ecosystems for seamless device integration.

References

  1. https://www.sciencedirect.com/topics/computer-science/embedded-systems
  2. https://users.ece.utexas.edu/~valvano/mspm0/ebook/Ch1_Introduction.html
  3. https://www.parasoft.com/blog/what-are-embedded-systems/
  4. https://www.techtarget.com/iotagenda/definition/embedded-system
  5. https://www.eetimes.com/just-what-is-an-embedded-system/
  6. https://cmte.ieee.org/tcrts/education/terminology-and-notation/
  7. https://technav.ieee.org/topic/embedded-systems
  8. https://www.microchipusa.com/electrical-components/embedded-computers-what-is-an-embedded-system
  9. https://www.electronicsforu.com/electronics-projects/electronics-design-guides/selecting-right-operating-system-next-embedded-design
  10. https://www.ebsco.com/research-starters/computer-science/embedded-system
  11. https://www.digi.com/blog/post/examples-of-embedded-systems
  12. https://www.embedded.com/embedded-systems-a-contemporary-design-tool/
  13. https://www.analog.com/en/resources/analog-dialogue/articles/low-power-embedded-systems.html
  14. https://users.ece.cmu.edu/~koopman/des_s99/real_time/
  15. https://cseweb.ucsd.edu/classes/wi01/cse221/OSSurveyW01/papers/khushu%2Csimmons.scheduling_and_synchronization_in_embedded_real-time_operating_systems.pdf
  16. https://ieeexplore.ieee.org/document/9684471
  17. https://www.researchgate.net/publication/3250129_Incorporating_cost_modeling_in_embedded-system_design
  18. https://users.ece.cmu.edu/~koopman/forth/sdnc90a.pdf
  19. https://ieeexplore.ieee.org/document/799441
  20. https://ieeexplore.ieee.org/document/7054928
  21. https://www.giac.org/paper/gicsp/95/abbreviated-history-automation-industrial-controls-system-cybersecurity/139645
  22. https://www.computerhistory.org/siliconengine/transistorized-computers-emerge/
  23. https://www.intel.com/content/www/us/en/history/virtual-vault/articles/the-intel-4004.html
  24. https://timeline.intel.com/1980/the-8051-microcontroller
  25. https://www.ibm.com/think/topics/microcontroller-vs-microprocessor
  26. https://www.arm.com/architecture/cpu/m-profile
  27. https://www.arm.com/products/silicon-ip-cpu/cortex-m/cortex-m4
  28. https://www.intel.com/content/www/us/en/products/details/embedded-processors.html
  29. https://builders.intel.com/docs/networkbuilders/intel-entry-processors-the-right-balance-of-performance-and-power-for-the-industrial-iot-market-1709278712.pdf
  30. https://www.raspberrypi.org/products/compute-module-5/
  31. https://store-usa.arduino.cc/products/arduino-zero
  32. https://www.embedded.com/managing-asic-design-tradeoffs-for-wearable-medical-devices/
  33. https://www.amd.com/en/products/adaptive-socs-and-fpgas/soc.html
  34. https://www.embedded.com/embedded-world-2025-recap-of-latest-innovations/
  35. https://coral.ai/docs/edgetpu/benchmarks/
  36. https://www.embien.com/blog/embedded-system-design-processor-selection
  37. https://www.cast-inc.com/blog/consider-code-density-when-choosing-embedded-processors
  38. https://www.nordicsemi.com/Products/nRF52840
  39. https://cacm.acm.org/practice/the-life-of-a-data-byte/
  40. https://dl.acm.org/doi/pdf/10.1109/DATE.2005.92
  41. https://ieeexplore.ieee.org/iel8/6287639/10820123/10908588.pdf
  42. https://dl.acm.org/doi/abs/10.1109/TCE.2016.7448558
  43. https://dl.acm.org/doi/10.1145/2930668
  44. https://developer.arm.com/documentation/dui0646/latest/The-Cortex-M7-Processor/Power-management/Entering-sleep-mode
  45. https://dl.acm.org/doi/10.1145/502217.502255
  46. https://ieeexplore.ieee.org/iel7/6287639/9312710/09370135.pdf
  47. https://ieeexplore.ieee.org/document/5694272/
  48. https://dl.acm.org/doi/10.1145/860176.860179
  49. https://ieeexplore.ieee.org/document/7745026/
  50. https://dl.acm.org/doi/10.1145/1165573.1165663
  51. https://ieeexplore.ieee.org/iel8/8784029/10423923/10585308.pdf
  52. https://dl.acm.org/doi/10.1145/3686259
  53. https://dl.acm.org/doi/10.1109/TC.2010.108
  54. https://www.trust-in-soft.com/resources/blogs/rusts-rise-hybrid-code-needs-advanced-analysis
  55. https://www.baeldung.com/linux/monolithic-kernel
  56. https://buildroot.org/
  57. https://www.qnx.com/developers/docs/8.0/com.qnx.doc.neutrino.getting_started/topic/s1_msg_Microkernel_and_messages.html
  58. https://cseweb.ucsd.edu/~voelker/cse221/papers/qnx-paper92.pdf
  59. https://dspace.mit.edu/bitstream/handle/1721.1/41351/34889746-MIT.pdf
  60. https://pdos.csail.mit.edu/papers/exo-sosp97/exo-sosp97.html
  61. https://www.freertos.org/
  62. https://www.freertos.org/Documentation/02-Kernel/02-Kernel-features/01-Tasks-and-co-routines/04-Task-scheduling
  63. https://risc-v-getting-started-guide.readthedocs.io/en/latest/zephyr-introduction.html
  64. https://docs.zephyrproject.org/latest/develop/languages/rust/index.html
  65. https://github.com/zephyrproject-rtos/zephyr
  66. https://www.linuxfoundation.org/blog/blog/intro-to-real-time-linux-for-embedded-developers
  67. https://bootlin.com/doc/training/preempt-rt/preempt-rt-slides.pdf
  68. https://www.armosec.io/glossary/linux-kernel/
  69. https://www.alibabacloud.com/blog/what-is-linux-kernel_599980
  70. https://mqtt.org/
  71. https://lvgl.io/
  72. https://arm-software.github.io/CMSIS_5/DSP/html/index.html
  73. https://www.autosar.org/
  74. https://www.ros.org/
  75. https://ai.stanford.edu/~ang/papers/icraoss09-ROS.pdf
  76. https://u-boot.org/
  77. https://memfault.com/blog/ota-for-iot/
  78. https://developers.googleblog.com/en/tensorflow-lite-is-now-litert/
  79. https://www.st.com/en/development-tools/stm32cubeide.html
  80. https://www.keil.com/
  81. https://www.tek.com/en/documents/primer/logic-analyzer-fundamentals
  82. https://www.qemu.org/
  83. https://www.analog.com/en/resources/design-tools-and-calculators/ltspice-simulator.html
  84. https://www.mathworks.com/solutions/embedded-systems.html
  85. https://platformio.org/
  86. https://www.designnews.com/embedded-systems/7-embedded-software-trends-to-watch-in-2025
  87. https://developer.arm.com/documentation/100893/latest/Debug-and-trace-interface
  88. https://developer.arm.com/documentation/dui0471/g/Semihosting/What-is-semihosting-?lang=en
  89. https://developer.arm.com/documentation/dai0167/latest/BABHGGBA
  90. https://www.throwtheswitch.org/unity
  91. https://ieeexplore.ieee.org/document/7423229
  92. https://percepio.com/tracealyzer/
  93. https://link.springer.com/chapter/10.1007/978-3-030-10591-4_11
  94. https://www.layerzero.com/Innovations/Industry-Firsts/Triple-Modular-Redundancy.html
  95. https://link.springer.com/article/10.1007/s43926-025-00184-8
  96. https://www.totalphase.com/blog/2025/04/embedded-systems-in-wearable-health-devices/
  97. https://iies.in/blog/snapdragon-and-arm-the-core-technology-powering-qualcomm-chipsets/
  98. https://www.allaboutcircuits.com/news/qualcomm-comes-out-with-fastest-mobile-soc-and-fastest-windows-cpus/
  99. https://antmicro.com/blog/2021/07/high-end-low-cost-android-devices-using-qualcomm-snapdragon/
  100. https://www.researchgate.net/publication/352225498_AN_OVERVIEW_FUZZY_LOGIC_APPLICATIONS_ON_WASHING_MACHINE
  101. https://www.techmonitor.ai/technology/invisible_at_home_fuzzy_logic_crosses_the_pacific_and_bursts_out_all_over
  102. https://blackhat.com/docs/us-14/materials/us-14-Jin-Smart-Nest-Thermostat-A-Smart-Spy-In-Your-Home-WP.pdf
  103. https://promwad.com/news/developing-embedded-software-for-smart-fitness-trackers
  104. https://www.wevolver.com/article/leading-wearables-into-a-new-era-with-cutting-edge-connected-bluetooth-le-based-mcus
  105. https://cordis.europa.eu/article/id/86894-feature-stories-bringing-embedded-chips-to-the-mass-market-for-smart-devices
  106. https://developer.amazon.com/en-US/alexa/devices/alexa-built-in
  107. https://blog.cranksoftware.com/the-rise-of-voice-activation-and-what-is-means-for-embedded-user-interfaces
  108. https://www.csselectronics.com/pages/obd2-explained-simple-intro
  109. https://www.fda.gov/medical-devices/infusion-pumps/infusion-pump-software-safety-research-fda
  110. https://iot-analytics.com/number-connected-iot-devices/
  111. https://www.forbes.com/sites/janakirammsv/2017/06/07/amazon-makes-foray-into-edge-computing-with-aws-greengrass/
  112. https://arxiv.org/abs/1711.07128
  113. https://www.mdpi.com/2078-2489/13/9/430
  114. https://pmc.ncbi.nlm.nih.gov/articles/PMC8703737/
  115. https://www.azosensors.com/article.aspx?ArticleID=3142
  116. https://www.weforum.org/stories/2023/02/what-challenges-to-look-out-for-now-the-era-of-connected-things-has-quietly-arrived/
  117. https://www.sciencedirect.com/science/article/pii/S016636152500082X
  118. https://www.forbes.com/sites/moorinsights/2022/01/11/ces-2022-matter-and-thread-win-the-iot-connectivity-wars/
  119. https://csa-iot.org/all-solutions/matter/
Add your contribution
Related Hubs
Contribute something
User Avatar
No comments yet.