DFRobot FireBeetle 2 ESP32-E
BoardSpecifications
Radiosinherited from ESP32
- Wi-Fi
- Wi-Fi 4 · 2.4 GHz
- Bluetooth LE
- BLE 4.2
- Bluetooth Classic
- yes
- 802.15.4
- no
USB
- Native USB
- no
- Connector
- usb-c
Board
- Form factor
- firebeetle
- Dimensions
- 25.4 × 60 mm
- Battery connector
- yes
- Charging
- yes
Display & extras
- Extras
- rgb-ledsd-card
Low-power IoT main board on the ESP-WROOM-32E module: 4 MB flash, USB-C, onboard Li-ion charging via PH2.0 connector, WS2812 RGB LED, and a microSD slot.
Firmware for this board
No firmware recipes yet — help add one.
Notes
- 4 MB flash
- ESP32-WROOM-32E module, 520 KB SRAM
- PH2.0 connector for 3.7 V Li-ion, onboard charging circuit
- GDI display connector onboard
- DFRobot sells a separate "FireBeetle 2 ESP32-E (N16R2)" SKU (DFR1139) specifically to add PSRAM, confirming this base DFR0654 board (whose own spec page never mentions PSRAM) uses the non-R2 ESP32-WROOM-32E ordering code with no PSRAM
- io.gpio_free=12 DERIVED, not quoted (SPEC-io-power.md §5.3). The page's stated totals conflict ("up to 24 physical GPIOs" vs "Digital Pins x18"), so gpio_exposed is left unquoted; instead the board's own GPIO pin table is used directly. That table enumerates 20 exposed pads (quoted from the wiki GPIO table): GPIO 0,1,2,3,4,12,13,14,15,18,19,21,22,23,25,26,34,35,36,39. Subtracting esp32's soc.reserved_pins that are exposed -- strapping {0,2,12,15} exposed of {0,2,5,12,15} (4; GPIO5 is not broken out), input_only {34,35,36,39} (4, all exposed), and usb_flash_tied {6,7,8,9,10,11} (0 exposed) -- gives 20 - 4 - 4 - 0 = 12. Math not vendor-stated; verify before treating as exact.
Verify my board
Reads the connected chip over USB and checks it against what esp-atlas cites for DFRobot FireBeetle 2 ESP32-E — 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.
