ESP32 Simulation
The ESP32 is a popular WiFi and Bluetooth-enabled microcontroller, widely used for IoT Projects. Wokwi simulates the ESP32, ESP32-C3, ESP32-S2, ESP32-S3 (beta) and ESP32-C6 (alpha).
ESP32 boards
| Name | Chip | Description |
|---|---|---|
| ESP32 DevKit v1 | ESP32 | Popular ESP32 development board |
| ESP32-S2-DevKitM-1 | ESP32-S2 | Entry-level ESP32-S2 development board |
| Franzininho WiFi | ESP32-S2 | Board by the Franzininho Community |
| Wemos S2 mini | ESP32-S2 | Small ESP32-S2 board by Wemos |
| ESP32-C3-DevKitM-1 | ESP32-C3 | Entry-level ESP32-C3 development board |
| Rust Board ESP32-C3 | ESP32-C3 | ESP32-C3 board designed for Rust trainings |
| ESP32-S3-DevKitC-1 | ESP32-S3 | Entry-level ESP32-C3 development board (beta) |
| ESP32-C6-DevKitC-1 | ESP32-C6 | Entry-level ESP32-C6 (alpha) |
You can contribute additional boards by sending a pull request to wokwi-boards.
Getting Started
You can use the ESP32 simulator to run different kinds of applications:
- ESP32 Arduino Core projects (including ESP-IDF projects)
- MicroPython and CircuitPython projects (examples at https://wokwi.com/micropython)
- Rust projects (see https://wokwi.com/rust)
- Custom application firmware files (e.g. applications built using the ESP-IDF)
Arduino Core
Start from the Arduino-ESP32 Project Template, or from the ESP32 Blink Example.
If you want to use third-party Arduino libraries, add a libraries.txt file with the list of libraries that you use.
MicroPython
Start from the MicroPython ESP32 Project Template, or from the MicroPython ESP32 Blink Example.
Note: While the simulation is running, press Ctrl+C inside the Serial Terminal to get into the MicroPython REPL. Alternatively, you can edit the Blink Example code and remove the while loop. For more information, check out the MicroPython Guide.
Custom Application Firmware
Open the ESP32 custom application project template, and press "F1" in the code editor. Then choose "Upload Firmware and Start Simulation…". Choose any .bin, .elf or .uf2 file from your computer and the simulation will start.
When uploading a custom firmware, it's recommended to create a single .bin file that contains the bootloader, partition table, and application. You can use the esptool merge_bin command to create such file.
For ESP-IDF projects, you can also build a single UF2 file using the command: idf.py uf2. The file will be located in build/uf2.bin, and can be uploaded to the simulator.
Simulator Examples
Arduino Examples
MicroPython Examples
ESP-IDF Examples
The following examples use the ESP-IDF functions. They are compiled using Arduino ESP32 Core:
- Blink using FreeRTOS API
- Binary LED counter using FreeRTOS tasks
- GPIO button input + interrupts
- WiFi Example
Simulation Features
| Peripheral | ESP32 | S2 | S3 | C3 | Notes |
|---|---|---|---|---|---|
| Processor core(s) | ✔️ | ✔️ | ✔️ | ✔️ | |
| GPIO | ✔️ | ✔️ | 🟡 | ✔️ | Interrupts supported |
| IOMUX | ✔️ | ✔️ | ✔️ | ✔️ | |
| PSRAM | ✔️ | ✔️ | ✔️ | — | 4MB of external SRAM * |
| UART | ✔️ | ✔️ | ✔️ | ✔️ | |
| USB | — | ✔️ | ✔️ | ❌ | Support for UART over USB (CDC) |
| I2C | ✔️ | ✔️ | ✔️ | ✔️ | Master only. 10-bit addressing not supported. |
| I2S | ❌ | ❌ | ❌ | ❌ | Open for voting |
| SPI | ✔️ | ✔️ | ✔️ | ✔️ | |
| TWAI | ❌ | ❌ | ❌ | ❌ | |
| RMT | 🟡 | 🟡 | ❌ | 🟡 | Transmit-only, use to control NeoPixels |
| LEDC PWM | ✔️ | ✔️ | ❌ | ✔️ | Used by analogWrite(), Servo, Buzzer, etc. |
| MCPWM | ❌ | — | ❌ | — | |
| DMA | 🟡 | 🟡 | ❌ | ❌ | |
| WiFi | ✔️ | ✔️ | ✔️ | ✔️ | See the ESP32 WiFi Guide |
| Bluetooth | ❌ | — | ❌ | ❌ | Open for voting |
| Timers | 🟡 | ✔️ | 🟡 | ✔️ | |
| Watchdog | ❌ | ❌ | ❌ | ❌ | |
| RTC | 🟡 | 🟡 | 🟡 | 🟡 | Only RTC Pull-up / Pull-down resistors |
| ADC | ✔️ | ✔️ | ❌ | ✔️ | Note: analogRead() returns values up to 4095 |
| RNG | ✔️ | ✔️ | ✔️ | ✔️ | Random Number Generator |
| AES Accelerator | ✔️ | ✔️ | ❌ | ✔️ | |
| SHA Accelerator | ✔️ | ✔️ | ❌ | ✔️ | |
| RSA Accelerator | ✔️ | ✔️ | ❌ | ✔️ | |
| Hall Effect Sensor | ❌ | — | ❌ | — | |
| ULP Processor | ❌ | ❌ | ❌ | ❌ | |
| GDB Debugging | ✔️ | ✔️ | ✔️ | ✔️ | Works with Wokwi for VS Code |
Legend:
✔️ - Simulated
🟡 - Partial implementation/work in progress
❌ - Not implemented (but if you need it, please open a feature request)
— - Not available on this chip
* The amount of SRAM can be customized using the "psramSize" attribute.
WiFi Simulation
See the ESP32 WiFi Guide.
Advanced Usage
Flash and memory size
You can customize the size of flash and PSRAM by adding the following attributes to the chip:
| Attribute | Description | Default |
|---|---|---|
| flashSize | Flash size in MB. Valid values: "2", "4", "8", "16", "32". | "4" |
| psramSize | PSRAM size in MB. Valid values: "2", "4", "8". | "4" |
Custom Partition Table
You can specifiy a custom partititon table by adding a "partitions.csv" file to your project. Check out the ESP32 Partition Table Guide for the exact format of this file.
Custom firmware offset
When loading a custom firmware, you can specify the offset of the firmware in the flash memory. By default, Wokwi will look at the firmware binary and try to figure out the offset automatically, based on the presence of the bootloader and the type of the chip. If Wokwi can't figure out the offset, it will assume that your firmware is an application firmware and load it at offset 0x10000.
You can specify the offset manually by adding the following attribute to the chip:
| Attribute | Description | Default |
|---|---|---|
| firmwareOffset | Offset of the firmware in the flash memory, in bytes. | "" |
Skipping the bootloader
On ESP32 and ESP32-S2 chips, Wokwi skips the boot ROM and the bootloader, so that your firmware starts running immediately. Other chips (ESP32-C3, ESP32-S3, etc.) always run the full boot sequence.
If you want Wokwi to always run the bootloader, you can add the following attribute to the chip:
| Attribute | Description | Default |
|---|---|---|
| fullBoot | Set to "1" to simulate the complete boot sequence: boot ROM -> bootloader -> application. | "" |