ESP32-C3 SuperMini pinout

Sixteen header pins, and five of them can break a build that looks fine on paper: three strapping pins, an analog pin that can’t read analog, and the UART that the boot log uses. Here’s every pin, then the same rules as a check you can rewire.

PinADCWhat to know
5V–USB-C 5 V. Too high for 3.3 V sensors, or for anything whose output goes to a GPIO.
GND–Ground. Every module needs it shared with the board.
3V3–The board’s 3.3 V rail. Power sensors from here.
IO4ADC1_CH4Free to use. Also pad-JTAG MTMS, which only matters if you debug over pins instead of USB.
IO3ADC1_CH3Free to use.
IO2ADC1_CH2Strapping pin. Espressif recommends keeping it high at reset.
IO1ADC1_CH1Free to use. Also XTAL_32K_N, for an optional 32 kHz crystal.
IO0ADC1_CH0Free to use. Also XTAL_32K_P, for an optional 32 kHz crystal.
IO5ADC2_CH0Fine as digital I/O, but ADC2 reads aren’t supported on the C3. Also pad-JTAG MTDI.
IO6–Free to use. Also pad-JTAG MTCK.
IO7–Free to use. Also pad-JTAG MTDO.
IO8–Strapping pin: must be high to flash over the BOOT button. The onboard LED is on it, active low.
IO9–Strapping pin: low at reset means download mode. The BOOT button pulls it to GND.
IO10–Free to use.
IO20–UART0 RX. Free to use when you don’t need the UART.
IO21–UART0 TX. The boot ROM prints its log here at every reset.

Rows in bold need care. USB-C is the C3’s own USB on GPIO18/19, which aren’t on the header.

Try it on the real rules

Pick a module pin, then a pin on the board, and the check re-runs. It opens on a wiring with real mistakes in it.

BME280

I²C sensor. 3.3 V breakout, no regulator, pull-ups on SDA/SCL

GNDGND

Soil probe

Analog. AOUT swings 0–75% of VCC: 0–2.5 V at 3.3 V

GNDGND

Pump MOSFET

Low-side switch. 10 kΩ pull-down keeps the pump off

GNDGND

ESP32-C3 SuperMini5VGND3V3IO4IO3IO2IO1IO0IO5IO6IO7IO8LEDIO9BOOTIO10IO20RXIO21TX

$ boardless check greenhouse-node

    Strapping pins: IO2, IO8, IO9

    The C3 reads these three pins once, at reset, to decide how to boot. IO9 has a weak internal pull-up, so it boots your code by default; anything that holds it low at reset (a MOSFET gate’s pull-down, a sensor that idles low, the BOOT button) starts the board in download mode instead. Download mode also needs IO8 high, so a pull-down on IO8 can make flashing fail. IO2 doesn’t choose the boot mode, but Espressif recommends pulling it up because of glitches.

    After reset they’re normal GPIOs. They’re fine for outputs and for signals that idle high, like I²C with pull-ups. Keep pull-downs and low-idling inputs off them.

    Analog: use IO0 to IO4

    IO0–IO4 are ADC1. IO5 is the only ADC2 pin on the header, and ESP-IDF no longer supports ADC2 one-shot reads on the C3: Espressif says the results aren’t stable (it’s in the C3 errata). The ADC’s calibrated range at the highest attenuation is 0–2.5 V, so a sensor powered from 3V3 that swings past that will clip.

    3.3 V only

    A C3 input takes at most VDD + 0.3 V, which is 3.6 V on this board. A sensor powered from the 5V pin can put more than that on a GPIO, through its output or its pull-ups.

    IO20 and IO21: the boot log

    They’re UART0. At every reset the boot ROM prints its log on TX (IO21), so whatever is wired there sees a burst of serial data: an I²C bus sees garbage, a MOSFET gate pulses its load. Programming and the serial monitor go over USB-C, so you can use both pins once you know that.

    Onboard: LED and BOOT button

    The LED is on IO8 and lights when the pin is low. The BOOT button connects IO9 to GND: hold it while resetting to get download mode. Pressing it while your code runs pulls IO9 low, so a signal on IO9 sees that too.

    Sources

    Boardless runs these checks on your whole project

    I’m building Boardless to check your schematic, case and firmware against each other on every change. The rules on this page are the first ones it knows.

    Used only to tell you when Boardless is ready and to decide what it supports first. No newsletter, no sharing. See the privacy note.