Microcontrollers and embedded systems overview

Key takeaways

Every cellular IoT device, whether it tracks a shipping container across an ocean or monitors soil moisture on a farm, runs on a small, purpose-built computer called a microcontroller. This page explains what a microcontroller is, how it differs from the processors in your laptop or phone, and how it fits into the broader embedded system that makes an IoT device work. By the end you will see why this component is the foundation every other layer of the IoT stack depends on.

What you'll learn

What a microcontroller (MCU) is and what lives on the chip

A microcontroller (often abbreviated MCU) is a compact integrated circuit that contains a processor, memory, and input/output peripherals all on a single chip. Think of it as a self-contained computer designed to do one job reliably, efficiently, and cheaply. That single-chip design is what makes it ideal for embedded uses like washing machines, smart thermostats, and IoT devices.

How a microcontroller differs from a microprocessor

Microcontrollers and microprocessors look similar but are built for different purposes:

• Microcontroller (MCU): lower clock speed, built-in RAM and peripherals on one chip, very low power draw, typically runs bare-metal firmware or a lightweight real-time operating system (RTOS), and is inexpensive.
• Microprocessor: much higher clock speeds, relies on external RAM and peripherals, consumes more power, typically runs a full operating system such as Windows or Linux, and costs more.

This is why microprocessors power desktops, laptops, and smartphones where speed matters, while microcontrollers suit low-power, dedicated IoT tasks.

Common MCU families used in cellular IoT

You will frequently encounter general-purpose low-power MCU families (widely used across many embedded and IoT products), MCUs popular for prototyping, and specialized cellular-integrated MCUs that combine the processor and cellular modem on a single system-in-package.

What makes up the embedded system around the MCU

A microcontroller alone does not make a device. It is the brain of a larger embedded system, a set of hardware components working together for a dedicated function. In a cellular IoT context that typically includes:

• The MCU that runs the application logic and coordinates the other components.
• Sensors that capture real-world data like temperature, acceleration, or location.
• A cellular modem that handles radio communication with the network.
• A SIM or eSIM that provides the identity credentials for network authentication.
• Power management circuitry that regulates battery voltage to the levels each component needs.
• Flash memory or storage for firmware, configuration data, and buffered sensor readings.
• An antenna to transmit and receive radio signals.

This Device Layer is where analog meets digital. This is where the physical hardware that captures real-world data using sensors, actuators, and microcontrollers.

How the MCU runs your application: bare-metal vs RTOS

Most IoT MCUs run in one of two modes:

• Bare-metal programming: Your code runs directly on the hardware with no operating system. You write a main loop that reads sensors, processes data, and triggers transmissions. It is simple, predictable, and uses minimal memory making it a good fit for a single, straightforward task.
• Real-Time Operating System (RTOS): A lightweight scheduler lets you run multiple tasks concurrently, such as reading a sensor on one thread while managing a cellular connection on another. Popular choices include FreeRTOS, Zephyr, and ThreadX. An RTOS adds some overhead but makes complex applications far easier to manage.

A simple temperature logger reporting once per hour can run bare-metal; a device juggling GPS tracking, motion detection, and cellular communication at once benefits from an RTOS.

Key specifications to evaluate when selecting an MCU

Five specifications matter most for a cellular IoT project:

1. Processing power: Enough clock speed and throughput to handle your sensor processing and communication protocols, but no more (excess speed wastes power).
2. Memory: RAM for runtime variables and flash for firmware storage. Cellular stacks alone can consume 100–200 KB of RAM, so budget accordingly.
3. Peripheral interfaces: SPI, I2C, UART, ADC, and GPIO pins for connecting sensors, modems, and other components.
4. Power modes: Deep sleep current consumption is critical for battery life; look for single-digit microampere draw in the deepest sleep states.
5. Development ecosystem: SDKs, documentation, community support, and evaluation boards all affect how quickly you can build and iterate.

Lesson 3.1 Self-assessment

Frequently asked questions