Show understanding of embedded systems
3.1 Computers and their Components
Embedded Systems: Definition and Examples
An embedded system is a computer that is built into a device to perform a specific task. Think of it as a mini‑brain that lives inside everyday objects. 🧩
Examples:
- Washing machine controller – decides when to spin, rinse, or stop.
- Car ECU (Engine Control Unit) – manages fuel injection and ignition timing.
- Smart thermostat – reads temperature and adjusts heating.
- Digital camera – processes images and controls shutter.
Hardware Components of Embedded Systems
Typical hardware pieces are similar to those in a PC but often smaller and more specialised:
- Microcontroller (MCU) – the CPU that runs the code.
- Memory – Flash for program storage, RAM for temporary data.
- Input/Output (I/O) – pins, sensors, actuators, communication ports.
- Power supply – often battery‑powered, so energy efficiency is key.
- Clock – provides timing signals.
Software in Embedded Systems
Software is usually firmware – code that is permanently stored in Flash. It may run on a tiny real‑time operating system (RTOS) or even bare metal.
- Write firmware in C or assembly.
- Compile and flash onto the MCU.
- Test with hardware simulators or on the actual device.
- Deploy and update via over‑the‑air (OTA) if supported.
Real‑World Applications
Embedded systems power many gadgets we use daily:
- 🚗 Automotive – anti‑lock braking, airbags, infotainment.
- 🏠 Home appliances – microwaves, smart fridges, HVAC.
- 📺 Consumer electronics – TVs, game consoles, smartwatches.
- 🛠️ Industrial – PLCs, robotic arms, sensors.
- 🩺 Medical – pacemakers, insulin pumps, imaging devices.
Key Differences from General‑Purpose Computers
| Feature | Embedded System | General‑Purpose Computer |
|---|---|---|
| Purpose | Single, specialised task | Multiple tasks, multitasking |
| Real‑time | Often required – must respond within strict time limits | Not usually time‑critical |
| Power | Very low – battery or small power supply | Higher consumption, mains power |
| Memory | Limited – often < 1 MB | Large – GBs of RAM and storage |
| Cost | Low – mass‑produced components | Higher – more complex hardware |
Design Considerations
When building an embedded system, keep these points in mind:
- Cost – choose components that meet budget.
- Size – smaller form factor often required.
- Power – optimise for battery life: $P = V \times I$.
- Reliability – must run continuously without failure.
- Security – protect against tampering or hacking.
- Scalability – design for future updates or expansions.
Analogy: The Chef vs. The Kitchen
Imagine a chef who can only cook one dish – that’s like an embedded system: it’s focused, efficient, and reliable for that specific job. 🍳
Now picture a full kitchen with many chefs, appliances, and menus – that’s a general‑purpose computer, capable of doing many things but less specialised for any single task. 🍲
Revision
Log in to practice.