The Core Idea
Unlike a laptop or phone, an embedded system is built for a single function.
It usually runs a simple loop:
read input → process → control output
For example, in a temperature-controlled fan:
- A sensor reads temperature
- A microcontroller processes it
- The fan turns on or off
What’s Inside It?
Even though it’s small, the hardware stack is quite clear:
- Microcontroller (MCU) → the brain
- Memory → stores program & data
- Peripherals → GPIO, UART, SPI, I2C
- Sensors/Actuators → the real-world link
What is Firmware?
The code running on an embedded system is called firmware.
It’s usually written in C or C++, and it directly controls hardware.
- reading registers
- configuring peripherals
- handling interrupts
What Makes It Different?
- It does one job, not many
- It often has to respond on time (real-time)
- Limited memory and processing power
- Industrial reliability
Where You’ll Find Them
- Cars (engine control, braking)
- Home appliances
- Medical devices
- Industrial machines
The Big Shift: Desktop vs. Silicon
No Safety Net
In Embedded: You are the OS. If your code crashes, the entire system reboots.
Limited RAM
Microcontrollers often have only 32KB of RAM. Precision matters.
Direct Control
Writing a value to an address flips a physical transistor. Silicon power.