Raspberry Pi

Definition: A full, low-cost single-board computer capable of running a complete Linux operating system, positioned between a simple microcontroller board like Arduino and a full desktop computer.

How It Works

Built around a real microprocessor (an ARM-based System-on-Chip with a Memory Management Unit), not a microcontroller, capable of running full Linux distributions
Has general-purpose I/O (GPIO) pins for connecting sensors and actuators, similar to Arduino, but backed by vastly more compute power and a real OS underneath
Can run real applications, web servers, databases, even lightweight machine learning models, not just simple embedded control loops
Boots from a microSD card (or, on newer models, USB/NVMe storage) holding a full Linux filesystem, taking seconds to boot rather than the near-instant power-on of a microcontroller
GPIO pins operate at 3.3V logic and are not natively 5V-tolerant, unlike many Arduino boards, connecting a 5V sensor’s output directly to a Pi’s GPIO pin can damage it without a level-shifting circuit
The 40-pin GPIO header exposes not just simple digital I/O but also dedicated protocol pins for I2C, SPI, and UART, letting it talk directly to a wide range of off-the-shelf sensor and peripheral modules
The official Raspberry Pi OS (Debian-based) is the most common choice, but the board can run other Linux distributions, and even other OSes, since it’s a general-purpose computer at heart
Camera and display connectors (CSI and DSI) alongside standard USB, HDMI, and Ethernet give the Pi I/O options no microcontroller board offers natively, without needing separate add-on modules

Under the Hood

Unlike a microcontroller’s single fixed program, this whole pipeline is just one Python or Node.js process running on top of a full Linux OS, which is what makes it easy to add web serving, databases, or cloud integration alongside the GPIO logic.

Worked example 1: GPIO voltage mismatch risk

Given: a 5V-logic sensor’s digital output pin is wired directly to a Raspberry Pi’s 3.3V-logic GPIO input pin
Step: when the sensor outputs a logic HIGH, it drives that pin to 5V; the Pi’s GPIO input is only rated for a maximum of about 3.3V (with a small margin) before risking damage
Step: without a level shifter or a simple voltage divider (two resistors) between them, the 5V signal can exceed the GPIO pin’s absolute maximum rating
Answer: the fix is a level-shifting circuit or a resistor divider that scales the 5V signal down into the Pi’s safe 3.3V range before it ever reaches the GPIO pin, a detail that trips up many people coming from 5V-tolerant Arduino boards

Worked example 2: boot time and instant-response trade-off

Given: a Raspberry Pi 4 running Raspberry Pi OS takes roughly 20-30 seconds to boot from power-on to a usable state
Step: for a security camera application that must start recording within 1 second of a power outage ending, that 20-30 second boot delay is a real functional gap an MCU-based device wouldn’t have (an MCU can be doing useful work in microseconds)
Step: a hybrid design mitigates this: a small microcontroller (or the Pi’s own low-power watchdog features) handles instant power-on detection, while the Pi itself finishes booting in the background and takes over once ready
Answer: this is a concrete, practical reason IoT systems often pair a Raspberry Pi (for heavy compute and networking) with a microcontroller (for instant-response, always-on tasks) rather than relying on the Pi alone for everything

Worked example 3: containerized workloads on a Pi

Given: a home automation hub needs to run three separate services (a database, an MQTT broker, and a web dashboard) on one Raspberry Pi
Step: because the Pi runs a full Linux OS, it can run Docker, and each service runs in its own isolated container with its own dependencies, exactly like a small cloud server would
Step: a microcontroller-based approach couldn’t do this at all, there’s no OS to host multiple isolated processes, let alone a container runtime
Answer: this containerized workflow is a direct consequence of the Pi being a real microprocessor-class computer, it inherits the entire Linux server tooling ecosystem (Docker, systemd, package managers) rather than needing anything custom-built for embedded use

Power Supply Considerations

Model	Typical idle draw	Typical peak draw	Recommended supply
Raspberry Pi Zero 2 W	~0.5-1W	~2W	5V/2.5A micro-USB
Raspberry Pi 4	~2.5-3.5W	~6-7W under load	5V/3A USB-C
Raspberry Pi 5	~3-4W	~8-12W under load	5V/5A USB-C (27W official supply)

Why It Matters

Bridges the gap between Arduino-style embedded control and full computing, letting hobbyists and professionals run genuinely complex software on cheap, small hardware
Its GPIO header combined with a full Linux userland means the same board can prototype hardware interfacing and serve as the application/networking layer, cutting out an entire class of “how do these two systems talk to each other” integration work
Running standard Linux server software (Docker, databases, web frameworks) on hardware small and cheap enough for a hobbyist budget blurs the line between “embedded project” and “small server deployment”
A large, active community and official first-party documentation make it a common teaching platform for both software and physical computing, not just a hobbyist niche product

Common Pitfalls

Using it for a task that only needs simple, low-power sensor control, where a much cheaper and lower-power Arduino would be the better fit
Underestimating that it runs a full OS with real boot times and update requirements, unlike a microcontroller’s near-instant power-on and fixed, unchanging firmware
Wiring 5V-logic components directly to its 3.3V, non-5V-tolerant GPIO pins without a level shifter, risking permanent damage to the board
Powering it from an underrated power supply, the Pi’s CPU and peripherals (especially with USB devices attached) can draw enough current to cause brownouts and unpredictable crashes on a marginal supply
Treating the microSD card as reliable long-term storage without considering wear, frequent writes (logging, databases) can wear out consumer-grade SD cards faster than expected, better handled with a proper filesystem/write strategy or external SSD storage on supported models
Forgetting there’s no reset-to-safe-defaults hardware watchdog by default the way many microcontrollers have, a hung Raspberry Pi in a remote deployment may need a physical power cycle or a software watchdog explicitly configured
Ignoring thermal throttling under sustained heavy load, the Pi’s CPU will automatically reduce clock speed once it gets too hot without adequate cooling, silently degrading performance
Running latency-critical control loops directly in a general-purpose Linux userspace process, which is subject to OS scheduling jitter that a real RTOS or bare-metal MCU wouldn’t have

Comparison

Aspect	Raspberry Pi	Arduino	Typical laptop/desktop
Core chip type	Microprocessor (SoC with MMU)	Microcontroller	Microprocessor
OS	Full Linux (or others)	None, bare-metal	Full desktop OS
Boot time	Seconds	Near-instant	Tens of seconds to minutes
Power draw	~2-7W typical	Milliwatts	Tens of watts
GPIO logic level	3.3V, not 5V-tolerant	Usually 5V	N/A, no GPIO
Best fit	Compute-heavy or networked embedded projects	Simple, low-power sensor/actuator control	General-purpose desktop computing
Real-time guarantees	Not by default	Yes, deterministic bare-metal timing	Not by default
Storage	microSD / USB / NVMe (on supported models)	Onboard flash only	Internal SSD/HDD

Example

A home media server, a retro gaming console, or a local home automation hub are all common Raspberry Pi projects that need real compute power an Arduino can’t provide. The Raspberry Pi 4 and Raspberry Pi 5 are common choices for compute-heavy hobbyist and professional projects, while the smaller, cheaper Raspberry Pi Zero 2 W fits compact, lower-power IoT deployments that still need a full Linux environment, unlike the Raspberry Pi Pico, which is actually a microcontroller board despite sharing the Raspberry Pi name.

Raspberry Pi 5: highest performance in the lineup, suited to local AI inference, NAS, or multi-service home servers
Raspberry Pi Zero 2 W: compact and low-power, common for camera projects and lightweight always-on sensors
Raspberry Pi Pico: not a single-board computer at all, an RP2040-based microcontroller board, closer in role to an Arduino than to the rest of the Pi lineup

Common Interview Questions

What makes a Raspberry Pi fundamentally different from an Arduino? — the Pi is built around a real microprocessor with an MMU running a full Linux OS, capable of multitasking and general-purpose computing, while Arduino runs one fixed bare-metal program on a microcontroller
Why are Raspberry Pi GPIO pins considered more fragile than Arduino’s? — they operate at 3.3V and are not 5V-tolerant, so connecting 5V-logic components directly can damage the board, unlike many Arduino boards that tolerate 5V natively
When would you choose a Raspberry Pi over a microcontroller for an IoT project? — when the project needs real compute power, a full networking stack, a filesystem, or the ability to run varied/updatable software, not just fixed low-power sensor/actuator control
Why might a project use both a Raspberry Pi and a microcontroller together? — to combine the Pi’s compute and networking strength with a microcontroller’s instant-on, low-power, real-time response for the parts of the system that can’t tolerate the Pi’s boot delay or power draw
What’s a practical concern with using a microSD card as a Raspberry Pi’s primary storage? — SD cards have limited write endurance and can degrade or fail under frequent writes (logging, databases), a real operational risk for long-running deployments
Why is thermal management a real concern on a Raspberry Pi but rarely discussed for a microcontroller? — the Pi’s CPU runs hot enough under sustained load to throttle its own clock speed without a heatsink or fan, while a typical MCU’s much lower power draw rarely generates enough heat to matter
What does “headless” mean in the context of Raspberry Pi deployments? — running the board without a monitor or keyboard attached, managed entirely over the network (typically SSH), common for embedded and server-style use cases

FAQ

Can a Raspberry Pi run Windows? — a limited “Windows 11 on Arm” experience is possible on newer models with community tooling, but Linux distributions remain the primary, best-supported OS choice for the platform
Does a Raspberry Pi need a monitor and keyboard to work? — no, “headless” setup (SSH over the network, no display attached) is extremely common, especially for IoT and server-style deployments
Is a Raspberry Pi real-time capable? — not by default, standard Linux scheduling isn’t deterministic; real-time patches or pairing with a microcontroller are the common ways to get hard real-time behavior when a project needs it
What’s the difference between the Raspberry Pi (single-board computer) and the Raspberry Pi Pico (microcontroller board)? — despite the shared branding, the Pico uses the RP2040 microcontroller with no MMU and no OS, architecturally closer to an Arduino than to a Raspberry Pi
How does a Raspberry Pi typically get its software installed? — usually by flashing an OS image (like Raspberry Pi OS) to a microSD card using the official Raspberry Pi Imager tool, then installing additional software through Linux’s normal package manager once it boots

Model Lineup Snapshot

Model	CPU	RAM options	Notable feature
Raspberry Pi 5	Quad-core Arm Cortex-A76	4GB/8GB/16GB	Highest performance, PCIe support
Raspberry Pi 4	Quad-core Arm Cortex-A72	1GB-8GB	Widely deployed, mature ecosystem
Raspberry Pi Zero 2 W	Quad-core Arm Cortex-A53	512MB	Compact, low-power, still full Linux
Raspberry Pi Pico	RP2040 (MCU, dual-core Cortex-M0+)	264KB	Not a single-board computer, a microcontroller board

Referenced by

Dig deeper

Spot an error in this note?