With the rising need of automation and advent of faster and smaller processing technologies, embedded systems are being universally used across the industries we serve. Whether you are seeking embedded system architecture consulting or building your first product, understanding the fundamentals is essential. As a leading embedded system architecture consulting provider, Embien helps organizations design reliable, high-performance systems. In this embedded systems tutorials series, we discuss the various techniques that go into embedded system design, starting with its general architecture.
Embedded Systems Tutorials: This Blog Series
This post is the first in Embien's embedded systems tutorials series, covering the full embedded system design lifecycle — from architecture fundamentals to processor selection, memory design, and power management. Each tutorial is designed to guide engineers and product teams through key design decisions.
Embedded Systems Definition and Overview
The embedded systems definition refers to a computer system designated to perform a dedicated function within a larger system or as a standalone product. Understanding the embedded systems definition is the first step in any embedded system architecture consulting engagement — it helps align teams on scope, functionality, and design constraints.
Embedded systems constantly evolve with advances in technology and dramatic decreases in the cost of implementing various hardware and software components. The embedded systems definition also encompasses a wide range of reliability and quality requirements: a critical medical device malfunctioning at the time of surgery can be life-threatening, while devices such as TVs, games, and cell phones present inconveniences rather than safety risks.
Some examples of embedded systems include Ignition systems, Engine control in Automotive, Set-top boxes, PDAs, Microwave Ovens in Consumer Electronics, Robotics, Assembly Control Systems in Industrial, Gateways, and Mobile devices — all relying on expert embedded system architecture consulting for design guidance.
Components of an Embedded System
Essentially an embedded system is a miniaturized computer. The following block diagram depicts a typical embedded system.
Modules in an embedded system
As with any computing device, it has the following components:
Processor:
The processor is the brain that controls the entire system. It holds the logic circuitry that responds to and processes the basic instructions that drive the system. It manipulates the control and data path to achieve the expected functionality. There are many application-specific and general-purpose microprocessors available. We will discuss the microprocessors in detail in the next post.
Memories:
Memories are the components that support the processor to hold data temporarily or permanently for immediate use and/or later use. Memories are of two types: non-volatile — capable of withholding data after a power cycle, and volatile — not capable of persistent data storage. Memories come in various technologies and sizes that can be chosen based on the specific needs of the system.
Inputs/Outputs – IOs:
An embedded system responds to events from the external world and results in certain actions being taken. This is accomplished with the IOs — inputs and outputs. While a real external world event may be a continuous analog signal (temperature reading of a furnace) or a discrete digital signal (on/off state of a switch), the input presented to the embedded system is generally digitized via ADCs, comparator circuits, or digital channels. Similarly, outputs in digital form are converted to suit the real world using techniques to be discussed later.
User Interface:
While the IOs typically refer to interaction between the embedded system and the controlled system, the user interface represents the interaction between the user and the system. Various technologies implement the user interface including LCDs, touch panels, key pads, and buttons. An intuitive design enables easier and enhanced control of the system and is now more of a mandatory requirement rather than an option.
Power Supply:
The power supply is one of the most important design considerations. The system may be powered directly from the power line or using a battery depending on the nature of the use. Its design requires deep analysis and careful incorporation per system requirements. Improper power supply design can affect system performance or damage the system. With emphasis on a greener world, power-efficient design is increasingly critical.
Mechanicals:
The mechanicals include the cabinet and connectors. The cabinet protects the system from external factors and provides the housing for the internals. The connectors support the connection of external signals into the system. Various factors determine the selection of cabinet and connectors, discussed in the upcoming post.
Working with an Embedded Systems Design and Development Firm
Selecting the right embedded systems design and development firm means evaluating hardware, software, and systems integration capabilities together. Embien's Electronic Circuit Design Services team brings deep embedded system architecture consulting expertise to every component selection decision — from processor and memory to power supply and mechanical enclosure design.
Consulting for Embedded System Design: Models and Approach
As with any design, the design of an embedded system is determined by various requirements including functional requirements, processing capabilities, power supply requirements, environmental considerations, and reliability requirements. Consulting for embedded system design helps teams select the right model and avoid costly rework.
There are various models practiced for embedded system design. Effective consulting for embedded system design guides teams in choosing the best-fit approach:
- Big-Bang model: Essentially no planning or procedures in place before and during the development of a system.
- Code and Fix model: Product requirements are defined but no formal processes are in place before the start of the development.
- Waterfall model: Process for developing a system in steps, where the result in one step flows into the next step.
- Spiral model: Process for developing a system in steps, and throughout the various steps, feedback is obtained and incorporated back into the process.
Since choosing any of these models is highly implementation and implementer specific, our embedded system architecture consulting approach focuses on helping teams evaluate their specific context. We will discuss the various considerations for selecting each component of the embedded system, starting with the processor in the next post.