Edgebox-ESP-100

An industrial-grade ESP32-S3 development board designed for edge computing and IoT gateway applications.

USB-C + USB-A Native USB
Edgebox-ESP-100 board
124 × 92 mm
ESP32-S3
MCU
240MHz
clock
16MB
flash
512KB
SRAM
34· Two 12-bit, 20 Channels ADC
GPIO
BLE 5.0+ WiFi
radio
On this page

Pinout

34 pins
View:
PinGPIOLabelsStatusCapabilitiesNotes
10RSTstrapping-
21CAN_TXDPWMsafe-
32CAN_RXDPWMsafe-
44DI0PWMsafe-
55DI1PWMsafe-
66DI2PWMsafe-
77DI3PWMsafe-
88RS485_RTSPWMsafe-
99I2C_INTPWMstrapping-
1010SSPWMstrappingspi
1111MISOPWMstrappingspi
1212MOSIPWMstrappingspi
1313SCKPWMstrappingspi
1414ETH_INTPWMstrapping-
1515ETH_RSTPWMsafe-
1616LTE_PWR_ENPWMsafe-
1717RS485_TXDPWMsafe-
1818RS485_RXDPWMsafe-
1919SCLPWMuarti2c
2020SDAPWMuarti2c
2121LTE_PWR_KEYPWMsafe-
2235DO5strapping-
2336DO4strapping-
2437DO3strapping-
2538DO2strapping-
2639DO1strapping-
2740DO0strapping-
2841AO1strapping-
2942AO0strapping-
3043TXDstrapping-
3144RXDstrapping-
3245BUZZERstrapping-
3347LTE_RXDstrapping-
3448LTE_TXDstrapping-

Start with these

12 pins with no boot or system involvement
CAN_TXDPWMCAN_RXDPWMDI0PWMDI1PWMDI2PWMDI3PWMRS485_RTSPWMETH_RSTPWMLTE_PWR_ENPWMRS485_TXDPWMRS485_RXDPWMLTE_PWR_KEYPWM

Freely assignable - no strapping, flash, USB or JTAG duties. Ideal first picks for buttons, sensors and LEDs.

Fine - with a little care

sampled at boot or shared with debug/serial
PinLabelWhat to knowRole
RSTGPIO0Must be pulled high (default) or low (to enter UART download mode) at reset. Using it for other functions can interfere with boot mode configuration.Strapping
DO1MTCK (GPIO39)Default JTAG debugging TCK pin. If JTAG is needed, this pin must be free; it may also be used internally for PSRAM chip select on certain modules, so avoid repurposing it.Other
DO0MTDO (GPIO40)Default JTAG TDO output for debugging. Using it as GPIO will interfere with JTAG debugging functionality.Other
AO1MTDI (GPIO41)Default JTAG TDI input for debugging. Should be reserved for JTAG or left unused if JTAG is to remain available.Other
AO0MTMS (GPIO42)Default JTAG TMS signal for debugging. Using this pin for other purposes will disable the JTAG interface (unless JTAG is rerouted to USB).Other
TXDU0TXD (GPIO43)Used for bootloader output and UART console logs. If repurposed, you will lose the default serial output (and programming via UART0).Other
RXDU0RXD (GPIO44)Used for bootloader input (download mode via serial). If repurposed, you cannot use the default UART0 download mode for programming the chip.Other
BUZZERGPIO45Determines flash/PSRAM power voltage (3.3 V vs 1.8 V) at boot. Must match hardware configuration; using as GPIO can upset flash supply setting.Strapping

Only if you know the tricks

wired to flash or USB - expect a fight
PinLabelWhat to knowRole
I2C_INTFSPIHDConnected to external flash (data/hold signal) on most modules. Not recommended for use as GPIO, since it must remain dedicated to flash communication.Flash
SSFSPICS0Used to select the external flash chip. It is required for flash access and cannot be repurposed without losing flash connectivityFlash
MISOFSPIDUsed as a data line for flash (and in-package PSRAM). It should not be used as GPIO when the flash/PSRAM is in use.Flash
MOSIFSPICLKDrives the flash (and PSRAM) clock. This critical signal must be reserved for memory and not used as general GPIO.Flash
SCKFSPIQUsed as a data line for flash/PSRAM transfers. Not available for other uses when flash/PSRAM is connected.Flash
ETH_INTFSPIWPConnected to external flash (data/write-protect signal). Not recommended as GPIO because it’s reserved for flash operations.Flash
SCLUSB_D-By default connected to the on-chip USB Serial/JTAG controller. Using it as general GPIO without reconfiguring IO MUX will interfere with USB functionality.USB
SDAUSB_D+By default connected to the on-chip USB Serial/JTAG controller. Using it as general GPIO without reconfiguring IO MUX will interfere with USB functionality.USB
DO5FSPID / PSRAM_D0In modules with octal PSRAM, this pin is connected to the PSRAM data line. It is reserved for memory interface and not free for general GPIO when flash/PSRAM is present.Flash
DO4FSPICLK / PSRAM_CLKIn modules with octal PSRAM, this pin drives the PSRAM clock. It must be dedicated to the memory interface, not used as a regular GPIO when that interface is in use.Flash
DO3FSPIQ / PSRAM_DQSIn modules with octal PSRAM, this pin is connected to the PSRAM’s DQS signal. It cannot be repurposed without disrupting the PSRAM/flash communication.Flash
DO2FSPIWPOn flash-equipped chips, this pin is tied to the flash’s WP# (or D3) line. It should be avoided for other use, as it’s needed for flash operations.Flash
LTE_RXDSPICLK_PUsed only on variants with Octal SPI interface (e.g. ESP32-S3R16V) as part of the differential clock pair. On such chips it operates at 1.8 V and is reserved for the high-speed octal SPI clock, not for general GPIO use.Flash
LTE_TXDSPICLK_NUsed only on variants with Octal SPI interface, as the negative leg of the differential clock&. On such chips it operates at 1.8 V; it should be avoided for GPIO to prevent conflicts with the octal flash/PSRAM clock.Flash
These are recommendations, not hard rules - with the right pull-ups, timing and boot-state awareness most pins can be made to work. When in doubt, start green.
Pinout notes All 34 pins on the Edgebox-ESP-100 are usable GPIO. Peripheral wiring is straightforward: I²C is mapped to SDA on GPIO20 and SCL on GPIO19, while the SPI bus (…

All 34 pins on the Edgebox-ESP-100 are usable GPIO.

Peripheral wiring is straightforward: I²C is mapped to SDA on GPIO20 and SCL on GPIO19, while the SPI bus (MOSI, MISO, SCK, SS) is broken out in full.

8 of the exposed pins carry boot-time or system duties on the ESP32-S3 (RST, DO1, DO0 and 5 more) - check the guidance above before wiring anything to them. CAN_TXD, CAN_RXD, DI0, DI1 and 8 more are free of any such role - the safest first picks.

Getting started

flash your first firmware in ~2 minutes
Tool:
1
Connect over USB
Native USB - shows up as a port right away, no driver needed. Not detected? Hold BOOT while plugging in.
2
Match & flash
Set the Tools options shown, then click Upload.
3
Verify it runs
The onboard LED on GPIO1 blinks - swap the pin if your board's LED differs.
Set these in Tools · leave everything else at default
Arduino IDE 2.x — Tools Copy
Board: "ESP32S3 Dev Module"
USB CDC On Boot: "Enabled"
Flash Size: "16MB (128Mb)"
Flash Mode: "DIO"
PSRAM: "QSPI PSRAM"
Partition Scheme: "16M Flash (3MB APP / 9.9MB FATFS)" (default)
Upload Speed: "921600"
▸ every other Tools option — leave at default
Board: ESP32S3 Dev Module
USB CDC On Boot: Enabled
Flash Size: 16MB (128Mb)
Flash Mode: DIO
PSRAM: QSPI PSRAM
Partition Scheme: 16M Flash (3MB APP / 9.9MB FATFS)
Upload Speed: 921600
Find it: Tools ▸ Board ▸ ESP32 Arduino ▸ ESP32S3 Dev Module
blink.ino Copy
// blink the onboard LED
void setup() {
  pinMode(1, OUTPUT);
}
void loop() {
  digitalWrite(1, HIGH); delay(500);
  digitalWrite(1, LOW);  delay(500);
}
board to selectesp32-s3-devkitc-1⧉ copy
platformio.ini Copy
[env:Edgebox-ESP-100]
platform = espressif32
board = esp32-s3-devkitc-1
framework = arduino
monitor_speed = 115200
upload_speed = 921600
board_build.arduino.memory_type = qio_qspi
build_flags = -DBOARD_HAS_PSRAM
Find it: PlatformIO Home ▸ Boards, search esp32-s3-devkitc-1 — or type it after board =.
board to selectesp32-s3-devkitc-1⧉ copy
device.yaml Copy
esp32:
  board: esp32-s3-devkitc-1
  variant: Edgebox-ESP-100
  framework:
    type: esp-idf
psram:
  mode: quad
  speed: 80MHz

# blink - GPIO1
output:
  - platform: gpio
    pin: 1
    id: led_out
light:
  - platform: binary
    name: "LED"
    output: led_out
Find it: search ESPHome's board list for esp32-s3-devkitc-1 (same ids as PlatformIO).
esptool doesn't pick board settings — a prebuilt .bin already has them baked in. This is just the raw flash command.
terminal Copy
esptool.py --chip esp32s3 --port /dev/ttyACM0 \
  --baud 921600 write_flash 0x0 firmware.bin
--port = your /dev/tty* (macOS/Linux) or COMx (Windows).
Build details: sketch space 1310720 B · data 327680 B · DIO

Specifications

ESP32-S3 · 124 × 92 mm
Compute
MCU
ESP32-S3
Clock
240 MHz
SRAM · Flash
512 KB · 16MB · 8MB (QSPI) PSRAM
Radio
Wi-Fi
802.11 b/g/n
Bluetooth
5.0 LE
Antenna
External
I/O
GPIO · ADC
34 · Two 12-bit, 20 Channels
UART · I²C · SPI
3 · 2 · 4
PWM
8 channels
Power
USB
USB-C (native) · USB-A
Serial
Native (CDC)
Boot address
0x0
Flashing
Upload · OTA
esptool_py · esp_ota
Flash · Boot mode
DIO · QIO
Sketch · Data
1.25 MB · 320 KB
92 mm124 mm
124 × 92 mm
The Edgebox-ESP-100 uses esptool_py for firmware uploads, esp_ota for over-the-air (OTA) updates. Flash mode is DIO with QIO boot mode. The maximum sketch size is 1.25 MB with 320 KB available for data.

About this board

Inside sits the ESP32-S3 - a dual-core Xtensa with vector extensions suited to AI workloads.

At $139.00 it's on the expensive side for an ESP32-S3 board - most land around $30.

With 34 GPIO broken out, you get more pins to play with than most ESP32-S3 boards offer.

Around the module: 8MB (QSPI) PSRAM, a PCF8563 RTC, a buzzer, an RS485 interface, a CAN bus interface, cellular connectivity (SIMCom A7670G) and wired Ethernet (W5500).

It flashes over native USB - no serial-converter driver needed, which isn't a given among ESP32-S3 boards.

  • 4 isolated digital inputs (24V) and 6 isolated digital outputs
  • 4 isolated analog inputs (0-20mA / 0-10V) and 2 isolated analog outputs (0-5V)
  • Isolated RS485 and CAN Bus with onboard 120Ω termination
  • SIMCom A7670G 4G LTE Cat-1 cellular modem
  • ATECC608A crypto element and FM24CL64B FRAM (non-volatile retain memory)
  • SGM58031 16-bit ADC for the isolated analog inputs
  • Industrial enclosure, operating temperature -20 to 60°C

Where to buy

prices are typical street prices
Edgebox-ESP-100
Edgebox-ESP-100
$139.00per unit, typical

Resources

Similar boards