Chip, module, board — the three layers of every dev board
Question this page answers: “My board, the chip on it and the metal can all say ESP32-S3 — which one am I actually reading about?”
The three layers
| Layer | What it is | Identified by |
|---|---|---|
| Chip (SoC/MCU) | the silicon die in a package, soldered somewhere | full chip part number (ESP32-S3, RP2040) |
| Module | chip + flash/PSRAM + antenna/crystal, sealed in a shield can | module part number on the shield (ESP32-S3-WROOM-1) |
| Board | the development board you hold; headers, USB, regulators, buttons | board name + ordering SKU + PCB revision (ESP32-S3-DevKitC-1 v1.1) |
A fact belongs to exactly one layer. “8 MB PSRAM” is a module-variant fact; “RGB LED on GPIO38” is a board-revision fact; “native USB OTG” is a chip fact. Mixing layers is how tutorials contradict each other.
All four MCUID boards, one per layer situation
- ESP32-S3-DevKitC-1 — the full three-layer stack: ESP32-S3 chip inside a WROOM-1/-1U/-2 module, soldered on the board. Which module decides storage; which PCB revision decides the LED pin.
- ESP32-DevKitC — same structure, and the module choice even changes pin availability: WROOM boards can use GPIO16/17, WROVER boards cannot (PSRAM wiring occupies them).
- Raspberry Pi Pico — no module layer at all: the RP2040 and its flash are soldered directly on the board. A “which module do I have?” question simply has no answer here.
- Raspberry Pi Pico 2 — same no-module design, different chip generation.
The practical test
Read the markings in this order, per the DevKitC-1 identification guide: shield-can silkscreen (module) → seller page/order code (SKU) → board documentation revision note (PCB revision). When a tutorial says “ESP32-S3”, check whether it means chip, module or board before applying its pin table.
What this page cannot tell you
- Third-party “DevKitC-compatible” boards may mix layers arbitrarily (clone boards with different revisions or LED pins) — layer logic still applies, the specific facts do not transfer.
- MCUID publishes qualified records per layer on each object page; we do not publish chip-internal capabilities (timers, peripherals) without a fixed source — those stay in vendor datasheets.
Sources
- MCUID data records: ESP32-S3-DevKitC-1 (five-layer identification table), ESP32-DevKitC (module-dependent pin availability), Pico, Pico 2 (no-module-layer facts)
- Which ESP32-S3-DevKitC-1 do I have? — the official identification path with pinned sources