ESP32-S2-DevKitC

Board Overview

ESP32-S2-DevKitC

Name:

esp32s2_devkitc

Vendor:

Espressif Systems

Architecture:

xtensa

SoC:

esp32s2

Browse board sources

Overview

ESP32-S2-DevKitC is an entry-level development board. This board integrates complete Wi-Fi functions. Most of the I/O pins are broken out to the pin headers on both sides for easy interfacing. Developers can either connect peripherals with jumper wires or mount ESP32-S2-DevKitC on a breadboard. For more information, check ESP32-S2-DevKitC [1].

Hardware

ESP32-S2 is a highly integrated, low-power, single-core Wi-Fi Microcontroller SoC, designed to be secure and cost-effective, with a high performance and a rich set of IO capabilities.

The features include the following:

• RSA-3072-based secure boot

• AES-XTS-256-based flash encryption

• Protected private key and device secrets from software access

• Cryptographic accelerators for enhanced performance

• Protection against physical fault injection attacks

• Various peripherals:

  • 43x programmable GPIOs

  • 14x configurable capacitive touch GPIOs

  • USB OTG

  • LCD interface

  • camera interface

  • SPI

  • I2S

  • UART

  • ADC

  • DAC

  • LED PWM with up to 8 channels

For more information, check the datasheet at ESP32-S2 Datasheet [2] or the technical reference manual at ESP32-S2 Technical Reference Manual [3].

Supported Features

The esp32s2_devkitc board supports the hardware features listed below.

on-chip / on-board

Feature integrated in the SoC / present on the board.

2 / 2

Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files.

vnd,foo

Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.

esp32s2_devkitc/esp32s2 target

Type	Location	Description	Compatible
CPU	on-chip	Espressif Xtensa LX7 CPU1	espressif,xtensa-lx7
ADC	on-chip	ESP32 ADC2	espressif,esp32-adc
Bluetooth	on-chip	Bluetooth HCI for Espressif ESP321	espressif,esp32-bt-hci
CAN	on-chip	ESP32 Two-Wire Automotive Interface (TWAI)1	espressif,esp32-twai
Clock control	on-chip	ESP32 RTC (Power & Clock Controller Module) Module1	espressif,esp32-rtc
Counter	on-chip	ESP32 Counter Driver based on RTC Main Timer1	espressif,esp32-rtc-timer
	on-chip	ESP32 general-purpose timers4	espressif,esp32-timer
DAC	on-chip	ESP32 Digital to Analog converter (DAC)1	espressif,esp32-dac
Flash controller	on-chip	ESP32 flash controller1	espressif,esp32-flash-controller
GPIO & Headers	on-chip	ESP32 GPIO controller2	espressif,esp32-gpio
I2C	on-chip	ESP32 I2C1 1	espressif,esp32-i2c
Input	on-chip	ESP32 touch sensor input1	espressif,esp32-touch
	on-board	Group of GPIO-bound input keys1	gpio-keys
Interrupt controller	on-chip	ESP32 Interrupt controller1	espressif,esp32-intc
Memory controller	on-chip	ESP32 pseudo-static RAM controller1	espressif,esp32-psram
MTD	on-chip	Flash node1	soc-nv-flash
	on-chip	Fixed partitions of a flash (or other non-volatile storage) memory1	fixed-partitions
Pin control	on-chip	ESP32 pin controller1	espressif,esp32-pinctrl
PWM	on-chip	ESP32 LED Control (LEDC)1	espressif,esp32-ledc
RNG	on-chip	ESP32 TRNG (True Random Number Generator)1	espressif,esp32-trng
Sensors	on-chip	ESP32 Pulse Counter (PCNT)1	espressif,esp32-pcnt
	on-chip	ESP32 temperature sensor1	espressif,esp32-temp
Serial controller	on-chip	ESP32 UART1 1	espressif,esp32-uart
SPI	on-chip	ESP32 SPI2	espressif,esp32-spi
Watchdog	on-chip	ESP32 XT Watchdog Timer1	espressif,esp32-xt-wdt
	on-chip	ESP32 watchdog1 1	espressif,esp32-watchdog
Wi-Fi	on-chip	ESP32 SoC Wi-Fi1	espressif,esp32-wifi

System requirements

Prerequisites

Espressif HAL requires WiFi and Bluetooth binary blobs in order work. Run the command below to retrieve those files.

west blobs fetch hal_espressif

Note

It is recommended running the command above after west update.

Building & Flashing

Simple boot

The board could be loaded using the single binary image, without 2nd stage bootloader. It is the default option when building the application without additional configuration.

Note

Simple boot does not provide any security features nor OTA updates.

MCUboot bootloader

User may choose to use MCUboot bootloader instead. In that case the bootloader must be built (and flashed) at least once.

There are two options to be used when building an application:

1. Sysbuild

2. Manual build

Note

User can select the MCUboot bootloader by adding the following line to the board default configuration file.

CONFIG_BOOTLOADER_MCUBOOT=y

Sysbuild

The sysbuild makes possible to build and flash all necessary images needed to bootstrap the board with the ESP32 SoC.

To build the sample application using sysbuild use the command:

west build -b esp32s2_devkitc --sysbuild samples/hello_world

By default, the ESP32 sysbuild creates bootloader (MCUboot) and application images. But it can be configured to create other kind of images.

Build directory structure created by sysbuild is different from traditional Zephyr build. Output is structured by the domain subdirectories:

build/
├── hello_world
│   └── zephyr
│       ├── zephyr.elf
│       └── zephyr.bin
├── mcuboot
│    └── zephyr
│       ├── zephyr.elf
│       └── zephyr.bin
└── domains.yaml

Note

With --sysbuild option the bootloader will be re-build and re-flash every time the pristine build is used.

For more information about the system build please read the Sysbuild (System build) documentation.

Manual build

During the development cycle, it is intended to build & flash as quickly possible. For that reason, images can be built one at a time using traditional build.

The instructions following are relevant for both manual build and sysbuild. The only difference is the structure of the build directory.

Note

Remember that bootloader (MCUboot) needs to be flash at least once.

Build and flash applications as usual (see Building an Application and Run an Application for more details).

# From the root of the zephyr repository
west build -b esp32s2_devkitc samples/hello_world

The usual flash target will work with the esp32s2_devkitc board configuration. Here is an example for the Hello World application.

# From the root of the zephyr repository
west build -b esp32s2_devkitc samples/hello_world
west flash

Open the serial monitor using the following command:

west espressif monitor

After the board has automatically reset and booted, you should see the following message in the monitor:

***** Booting Zephyr OS vx.x.x-xxx-gxxxxxxxxxxxx *****
Hello World! esp32s2_devkitc

Debugging

ESP32-S2 support on OpenOCD is available at OpenOCD ESP32 [5].

The following table shows the pin mapping between ESP32-S2 board and JTAG interface.

ESP32 pin	JTAG pin
MTDO / GPIO40	TDO
MTDI / GPIO41	TDI
MTCK / GPIO39	TCK
MTMS / GPIO42	TMS

Further documentation can be obtained from the SoC vendor in JTAG debugging for ESP32-S2 [4].

Here is an example for building the Hello World application.

# From the root of the zephyr repository
west build -b esp32s2_devkitc samples/hello_world
west flash

You can debug an application in the usual way. Here is an example for the Hello World application.

# From the root of the zephyr repository
west build -b esp32s2_devkitc samples/hello_world
west debug

References

[1]

https://docs.espressif.com/projects/esp-idf/en/latest/esp32s2/hw-reference/esp32s2/user-guide-saola-1-v1.2.html

[2]

https://www.espressif.com/sites/default/files/documentation/esp32-s2_datasheet_en.pdf

[3]

https://espressif.com/sites/default/files/documentation/esp32-s2_technical_reference_manual_en.pdf

[4]

https://docs.espressif.com/projects/esp-idf/en/latest/esp32s2/api-guides/jtag-debugging/index.html

[5]

https://github.com/espressif/openocd-esp32/releases