Skip to content

Discover. Identify. Build.

Find your board. Understand every pin.

Explore microcontrollers, development boards, pinouts and hardware revisions.

    Try: ESP32-S3-DevKitC-1 · ESP32-S3 · ESP32-S3-WROOM-1 · ESP32-S3-WROOM-1U — or browse the hardware index

    Open the ESP32-S3-DevKitC-1 pinout Browse the hardware index

    MCUID connects microcontrollers, modules, development boards, pinouts and hardware revisions. Every published field carries a fixed official source, so you can verify what a pin does — and when a board revision changes it — instead of trusting a copied pinout image.

    What you can do here. Look up a chip, module or board and read its identity, revision-scoped facts and interactive 2D pinouts; follow the task-based guides to answer concrete questions like which GPIO drives your onboard LED. Every fact traces to a fixed official source — no unsourced filler pages.

    Explore hardware (4)

    ESP32-S3-DevKitC-1 Official Espressif ESP32-S3 entry-level evaluation board, assembled with ESP32-S3-WROOM-1, -1U or -2 modules, dual 22-pin headers (J1/J3), onboard addressable RGB LED, USB-to-UART bridge and native USB OTG port.espressif · ESP32-S3 · 2 revisions · 9 SKUs Raspberry Pi Pico RP2040 microcontroller board with 2 MB flash, 40-pin 2.54 mm castellated/through-hole DIP format (51 x 21 mm), micro-USB B for power/data and drag-and-drop mass-storage flashing, 3-pin SWD pads at the bottom edge. No module layer: the RP2040 chip is soldered directly on the board.raspberry · RP2040 · 1 revision Raspberry Pi Pico 2 RP2350A microcontroller board with 4 MB flash, hardware- and software-compatible with Raspberry Pi Pico: same 40-pin 2.54 mm castellated/through-hole format, same pinout, micro-USB B with drag-and-drop UF2 flashing and 3-pin SWD pads. No module layer: the RP2350A chip is soldered directly on the board.raspberry · RP2350 · 1 revision ESP32-DevKitC Official Espressif ESP32 evaluation board. V4 (current) assembles ESP32-WROOM-32E/32UE or ESP32-WROVER-E/IE modules on dual 19-pin headers (J2/J3), with a single micro-USB port through a USB-to-UART bridge, EN/Boot buttons and a 5 V power-on LED. There is no user-programmable onboard RGB LED on this board.espressif · ESP32 · 2 revisions · 4 SKUs

    Explore pinouts

    44 header contacts, every one annotated

    ESP32-S3-DevKitC-1

    • power
    • ground
    • GPIO
    • flash/PSRAM, module-conditioned
    • RGB LED, revision-scoped

    One pin question: which pin is the RGB LED on? all claims →

    RevisionLED GPIOHeader position
    v1.0GPIO48J3-16
    v1.1GPIO38J3-10

    It depends on the board revision — pick one on the board page and every assignment follows, each field tied to a fixed official source.

    Solve a problem (13)

    Chip, module, board — the three layers of every dev board Why the same name appears on a chip, a metal can, and a circuit board. How to tell which layer a claim belongs to, with all four MCUID boards as examples. Getting started with the Raspberry Pi Pico First steps for the plain Raspberry Pi Pico (RP2040): pick MicroPython or C/C++, flash over BOOTSEL, and what to expect at each step — with the failure exits when the board does not show up. USB board not detected — the ordered checklist Power LED, the cable, the port, the mode: an observable-steps checklist for ESP32 and Pico boards when the computer sees nothing, with the per-board differences that matter. Which ESP32-S3-DevKitC-1 do I have? Five different things are called an ESP32-S3: chip, module, board, sales SKU and PCB revision. How to tell them apart, and what to do when you cannot. Getting started with the Raspberry Pi Pico 2 First steps for the plain Raspberry Pi Pico 2 (RP2350): pick MicroPython or C/C++, flash over BOOTSEL with the RP2350 volume and RPI_PICO2 firmware, and what to expect at each step. Pin numbers, GPIO numbers and pin functions — three different things Physical pin position, GPIO number and silk-screen function name answer different questions. Why the same on-board device can move to a different GPIO and header position across revisions, with examples from all four boards. Why the onboard LED is GPIO38 or GPIO48 Two ESP32-S3-DevKitC-1 revisions are on the market and they moved the addressable RGB LED. Which pin yours is on, how to drive it, and what the documentation does not say. 3.3 V and 5 V — power rails, logic levels and the one diode rule Where 5 V appears on a dev board, why the GPIOs are 3.3 V logic, and the Pico ADC reverse-diode limit stated in its datasheet. What we can and cannot claim without a per-chip abs-max field. Can I use GPIO35, GPIO36 and GPIO37? Depends on which module your ESP32-S3-DevKitC-1 carries. The condition, how to check your board, and why some tutorials ban these pins outright. Pico vs Pico 2 — which one do you have, and which should you get? Same 40-pin pinout, same layout, two generations: RP2040 vs RP2350. The official compatibility claim, the concrete spec deltas, and the naming traps (W, H, with headers). First connection, flashing and LED troubleshooting Two USB ports, one charging-cable trap, a download mode, and why the first blink sketch may not light the LED — the ESP32-S3-DevKitC-1 bring-up path in order. UART, I2C and SPI — what the three buses are, and how to check a pin before you wire it The three wired protocols every tutorial assumes, seen through real pins on real boards — then the three-layer check that tells you whether the pin you picked actually works: SDK default, chip mux, board wiring. ESP32-DevKitC V4 — first connection and flash The classic ESP32 board's bring-up path: one USB port, one boot mode, no user LED to blink — what to check before flashing and where the V4 traps are.

    Learning paths

    Just unboxed a board?

    From USB cable to first firmware, per board.

    Not sure which one you have?

    Identify the board before trusting any pin table.

    Computer sees nothing?

    Observable breakpoints, checked in order.

    Start building (1)

    Lab: blink the ESP32-S3-DevKitC-1 RGB LED A reproducible first experiment for the ESP32-S3-DevKitC-1: both board revisions compiled with the pinned Arduino core and NeoPixel driver (receipt inside); not flashed to hardware.

    Open data, open code

    The site, validator and data contract live in edamcu/mcuid.com. The build gate re-validates every dataset on each deploy.

    Spot a stale fact?

    Every claim pins the exact document and commit it was read from. If a vendor doc moved on, open an issue with the newer source and the field will be re-verified.

    Bring your board

    Want another board qualified? Propose it with links to its official documentation — revision-scoped facts land here the same fixed-source way, never as unsourced copies.