Adafruit ESP32-S3 Feather (4MB Flash 2MB PSRAM)

Board
by Adafruitadafruit-feather-esp32-s3≈ medium (~$15–50)
Verify my boardCompareEdit on GitHub
Adafruit ESP32-S3 Feather (4MB Flash 2MB PSRAM) board
Board
Adafruit ESP32-S3 Feather (4MB Flash 2MB PSRAM) pinout
Pinout

Specifications

Radiosinherited from ESP32-S3

Wi-Fi
Wi-Fi 4 · 2.4 GHz
Bluetooth LE
BLE 5
Bluetooth Classic
no
802.15.4
no

USB

Native USB
yes
Connector
usb-c
Bridge chip
none — SoC native USB

Board

Form factor
feather
Dimensions
52.3 × 22.7 mm
Battery connector
yes
Charging
yes

Display & extras

Extras
rgb-ledstemma-qt
Built onAdafruit ESP32-S3 Feather (4MB Flash 2MB PSRAM) BoardESP32-S3 SoC

Feather-form ESP32-S3 board: native USB-C, LiPo JST + charging, NeoPixel, STEMMA QT.

Firmware for this board

No firmware recipes yet — help add one.

Notes

  • Main variant: 4 MB flash, 2 MB PSRAM; alternate: 8 MB flash, no PSRAM
  • MAX17048 battery monitor, JST LiPoly, NeoPixel, STEMMA QT
  • io.power_out QUOTED: vendor page states "These pins are the output from the 3.3V regulator, they can supply 500mA peak."
  • io.gpio_exposed=20 QUOTED: vendor pinouts page lists broken-out header pads D5, D6, D9, D10, D11, D12, D13 (7 digital), A0-A5 (6 analog, dual-named D8/D14-D18), SCK/MOSI/MISO (SPI), RX/TX (UART), SCL/SDA (I2C) = 20 GPIO-capable pads (RST/EN are control pins, not counted); same Feather pin-naming as adafruit-feather-esp32-s2. io.gpio_free=16 DERIVED: cross-referencing the vendor firmware repo's own CircuitPython board pin-definition (pins.c) maps every header pad to GPIO3-4, 5-6, 8-18, or 35-39 -- of esp32-s3's soc.reserved_pins, GPIO3 (SDA, strapping) and GPIO35/36/37 (MOSI/SCK/MISO, usb_flash_tied) are exposed pads; NeoPixel/ I2C_POWER/NEOPIXEL_POWER sit on GPIO7/21/33, off-header -- so 20 - 4 = 16
  • usb_serial derived from usb.bridge (native) + soc usb.type otg-full-speed + serial-jtag

Verify my board

Reads the connected chip over USB and checks it against what esp-atlas cites for Adafruit ESP32-S3 Feather (4MB Flash 2MB PSRAM) — over Web Serial, no backend, nothing leaves your browser.

In-browser verify needs Web Serial: Chrome or Edge on a desktop. Safari, Firefox and phones cannot do it.

Serial monitor

Not connected.