Embedded Systems Overview

Embedded Systems Overview

Use this page to revise what makes a system "embedded" compared with a general-purpose computer.

Dedicated function and constraints

An embedded system is a computer built into a product for a specific job. Memory, CPU, and storage are bounded and usually not user-upgradeable. The UI may be LEDs, a small panel, an app, or none.

Typical blocks

MCU or SoC, power, sensors, actuators, communication, and firmware in non-volatile memory. Many products also have a second computer (phone, Pi, cloud) — the embedded part still owns the physical I/O.

Same principles, different budget

You still have a CPU, memory, and I/O. You count bytes and microseconds. Languages are often C/C++; Python may appear on an SBC, not on a tiny MCU.

Starting Points

• Computer systems & architecture
• Firmware architecture

Key Points

• You can define an embedded system and contrast it with a laptop.
• You can name the typical blocks of an embedded product.
• You can explain why resource limits change algorithm and language choices.
• You can place firmware in the product lifecycle (requirements → hardware → firmware → test → maintain).