Streamline MCU ESP32S3 (research)
The Streamline MCU ESP32S3 is a planned Streamline MCU board built around an ESP32-S3 module. This page collects the research and design decisions made before the schematic is drawn. Nothing here is final.
The Streamline backplane pin mapping was originally built around 100-pin STM32 MCUs. The ESP32-S3 has far fewer GPIOs, but its GPIO matrix lets almost any digital peripheral go to any pin, so most of the STM32 positions can be matched exactly. See:
Goals
The blade has to do two jobs:
- Main MCU: work as the only MCU on a backplane, together with the existing peripheral blades.
- Wi-Fi co-processor: sit on a backplane next to an STM32 or RP2354 blade and give that host Wi-Fi over SPI (ESP-Hosted or ESP-AT).
Two more requirements:
- USB-Serial-JTAG (flashing, console, debugging) is on the blade's own USB-C connector.
- The ESP's first UART (UART0) goes to the UART the Streamline Connect uses by default (USART1, PA9/PA10), so the serial console is available there in main MCU mode.
Module
The choice is the ESP32-S3-WROOM-1-N16R2 (16 MB quad flash, 2 MB quad PSRAM).
All ESP32-S3 modules are extended parts at JLCPCB. Stock on 2026-11-22:
| Part | LCSC | Stock | ~USD | Notes |
|---|---|---|---|---|
| ESP32-S3-WROOM-1-N16R2 | C2913205 | 7,008 | 5.23 | Chosen. Quad PSRAM leaves GPIO35-37 free (36 GPIOs) |
| ESP32-S3-WROOM-1-N16R8 | C2913202 | 26,482 | 5.27 | Same footprint. Octal PSRAM takes GPIO35-37 (33 GPIOs) |
| ESP32-S3-WROOM-1U-N16R2 | C3013945 | 4,274 | 5.16 | U.FL connector for an external antenna |
| ESP32-S3-WROOM-1U-N16R8 | C3013946 | 19,568 | 5.10 | U.FL connector for an external antenna |
| ESP32-S3-WROOM-1-N8R8 | C2913201 | 11,029 | 4.89 | |
| ESP32-S3-MINI-1-N8 | C2913206 | 14,793 | 4.73 | Smaller LGA module, no PSRAM |
| ESP32-S3-WROOM-2-N32R16V | C42417293 | 357 | 10.89 | Too little stock, too expensive |
Why a module rather than a bare ESP32-S3 chip:
- No crystal, flash, RF matching network or antenna layout on the blade.
- The module carries FCC/CE radio certification.
Why N16R2 rather than N16R8: GPIOs are the scarce resource on this blade. The N16R8 can still be fitted to the same footprint. It only loses the three lowest-priority pins (marked † in the pin map).
Antenna: on a blade sitting a few mm from the ground planes of its neighbours, a PCB antenna loses a lot of range. The module goes at the top edge with the antenna overhanging the copper. The -1U variants have the same pinout and pad positions, so the same footprint takes either.
Specifications (planned)
| Module | ESP32-S3-WROOM-1-N16R2 |
| Flash | 16 MB |
| PSRAM | 2 MB |
| Wireless | Wi-Fi 4 (2.4 GHz), Bluetooth LE 5 |
| USB | USB-C on the blade (USB-Serial-JTAG / USB OTG on GPIO19/20) |
| LED | PC13 position (GPIO38), active low |
| Button | PC15 position (GPIO46), active high, pulled down |
| Boot | BOOT button on GPIO0, also controllable from BOOT0 (B2) |
Pin Mapping
The pin map is built from the backplane pins the existing peripheral blades actually connect to (taken from their netlists), not from the full STM32 pin list.
| ESP32-S3 | Position | STM32 pin | Function |
|---|---|---|---|
| GPIO10 | B5 | PA4 | SPI1 CS, co-processor CS, I2S3 WS |
| GPIO12 | B6 | PA5 | SPI1 SCK, co-processor SCK |
| GPIO13 | B7 | PA6 | SPI1 MISO, co-processor MISO |
| GPIO11 | B8 | PA7 | SPI1 MOSI, co-processor MOSI |
| GPIO17 | B9 | PC4 | Co-processor handshake, SPI-Ethernet INT |
| GPIO4 | B10 | PC5 | Co-processor data ready, SPI-Ethernet RST, ADC |
| GPIO1 | A6 | PA0 | UART4 TX, ADC |
| GPIO2 | A5 | PA1 | UART4 RX, RS485 DE, ADC |
| GPIO5 | A4 | PA2 | USART2 TX (RS485), ADC |
| GPIO6 | B4 | PA3 | USART2 RX (RS485), ADC |
| GPIO7 | A7 | PC3 | SPI2 MOSI, I2S2 SD, ADC |
| GPIO8 | A8 | PC2 | SPI2 MISO, ADC |
| GPIO9 | B24 | PB10 | SPI2 SCK, I2C2 SCL, I2S2 CK |
| GPIO3 | B25 | PB11 | I2C2 SDA |
| GPIO14 | B26 | PB12 | SPI2 CS, I2S2 WS |
| GPIO42 | A25 | PB6 | I2C1 SCL (EEPROM) |
| GPIO41 | A24 | PB7 | I2C1 SDA (EEPROM) |
| GPIO39 | A36 | PD1 | CAN1 TX |
| GPIO40 | A37 | PD0 | CAN1 RX |
| GPIO15 | A39 | PC12 | SDIO CK, SPI3 MOSI, I2S3 SD, CAN standby |
| GPIO16 | A35 | PD2 | SDIO CMD |
| GPIO18 | B42 | PC8 | SDIO D0 |
| GPIO21 | B43 | PC9 | SDIO D1 |
| GPIO47 | A41 | PC10 | SDIO D2, SPI3 SCK, I2S3 CK |
| GPIO48 | A40 | PC11 | SDIO D3, SPI3 MISO |
| GPIO38 | A13 | PC13 | LED (active low) |
| GPIO46 | A11 | PC15 | Button (active high, pulled down) |
| GPIO35 † | A12 | PC14 | SD card detect, EEPROM write control |
| GPIO36 † | A22 | PB9 | I2C1 alternate SDA, CAN1 alternate |
| GPIO37 † | A23 | PB8 | I2C1 alternate SCL, CAN1 alternate |
| GPIO43 | B45 | PA9 | UART0 TX to the Connect (via jumper) |
| GPIO44 | B46 | PA10 | UART0 RX from the Connect (via jumper) |
| GPIO0 | B2 | BOOT0 | Via a MOSFET inverter (via jumper), BOOT button |
| GPIO19/20 | - | - | Blade USB-C only, not on the backplane |
| GPIO45 | - | - | Not connected, 10k pull-down |
† Not available on modules with octal PSRAM (R8).
Notes:
- SPI1 uses the ESP32-S3's dedicated SPI pins (GPIO10-13), which allow 80 MHz. Everything else goes through the GPIO matrix.
- ADC1 (GPIO1-10) lands on STM32 ADC positions (PA0-PA4, PC2-PC5). ADC2 (on PA5-PA7) can't be used while Wi-Fi is on.
- Strapping pins: GPIO45 must be low at reset (it selects the flash voltage), so it stays off the backplane. GPIO46 must be low for download mode, so it goes on the button position, which is pulled down by convention. GPIO3 is only a strapping pin if an eFuse is burned.
- GPIO0 is active low, while STM32 BOOT0 is active high, so B2 drives GPIO0 through an inverter. The BOOT button sits on the same net as on the STM32 blades, so it works the same way.
Reset, power and role jumpers
- Reset: EN is driven by a 74LVC1G09 (2-input AND, open-drain output) from A2 (NRST) and A10 (PC0, a host GPIO). A host reset then also resets the ESP, and the host can reset the ESP on its own for link supervision. The gate keeps the ESP's 1 µF EN capacitor off the STM32's NRST, where it would break software resets.
- Power: the module runs from its own regulator fed from the 5V rail. Running an ESP from the backplane 3V3 alone has caused brownout resets when the radio starts.
- VBAT (A3) and SWD (A43/A46) are not connected.
Solder jumpers select the role:
| Net | Main MCU | Co-processor |
|---|---|---|
| UART0 to B45/B46 | closed | open |
| B2 BOOT0 to GPIO0 inverter | closed | open |
| A2 NRST to EN gate | closed | closed |
| A10 host reset to EN gate | open | closed |
| Local 3V3 to backplane 3V3 | closed | open |
| 3V3 via ferrite to VA (B3) | closed | open |
In co-processor mode the host's own USART1 uses B45/B46, and the ESP ROM prints its boot log on UART0 at every reset. That is why the UART0 jumpers must be open in that mode. The ESP console then goes over its USB port.
Main MCU mode
Works with:
- Streamline Storage Flash and Streamline Storage SD on SPI1, SPI2 or SPI3, and SD over 4-bit SDIO
- Streamline Storage EEPROM on I2C1 or I2C2
- Streamline IO Audio DAC on either the I2S2 or the I2S3 pin set
- Streamline IO CAN on CAN1 (PD1/PD0)
- Streamline RS485 on USART2
- Streamline SPI-Ethernet
- The LED display blade
Not possible (the ESP32-S3 lacks the hardware): Streamline Ethernet (RMII), HS USB (ULPI), DAC outputs, CAN2 (B28) and I2C3 (B44).
Wi-Fi co-processor mode
The ESP32-S3 has no SDIO slave, so the host link is SPI. It uses the same pins as the stm32-esp32-wifi project (ESP-Hosted, and ESP-AT over SPI), so its co-processor firmware runs on the blade unchanged:
| Signal | Position | STM32 | RP2354 | ESP32-S3 | Direction |
|---|---|---|---|---|---|
| CS | B5 | PA4 | GPIO27 | GPIO10 | host to ESP |
| SCK | B6 | PA5 | GPIO42 | GPIO12 | host to ESP |
| MISO | B7 | PA6 | GPIO40 | GPIO13 | ESP to host |
| MOSI | B8 | PA7 | GPIO43 | GPIO11 | host to ESP |
| Handshake | B9 | PC4 | GPIO10 | GPIO17 | ESP to host |
| Data ready | B10 | PC5 | GPIO11 | GPIO4 | ESP to host (ESP-Hosted only) |
| Reset | A10 | PC0 | GPIO46 | EN (via gate) | host to ESP |
This works with every current MCU blade (STM32F407, H723, H562, L475, C551, C071 and RP2354). On the F407 and H723, PC0 is also the HS USB (ULPI) STP line, so the HS USB blade and host reset of the ESP can't be used together.
ESP-AT over UART is also possible without hardware changes, using USART2 (A4/B4).
The co-processor firmware should set every backplane pin it doesn't use to input without pull, as early as possible after boot.
Open questions
- Check that the 74LVC1G09 (or an equivalent) is stocked at JLCPCB.
- Check whether the Streamline Connect can drive NRST and BOOT0 for automatic flashing over UART0. Flashing over the blade's USB works in any case.
- Choose a 3V3 regulator that can supply the module's Wi-Fi peaks (about 500 mA) plus the backplane in main MCU mode.