ESP32-H2-DevKitM-1 Board

Caution

This page is automatically generated from RIOT doxygen documentation. If you find any issues or have suggestions for improvement, please report them on Github.

View Doxygen Documentation View this board's documentation as generated by Doxygen.

View on GitHub View this board's source code on GitHub.

Tip

When using this board with RIOT, set the BOARD variable to esp32h2-devkit in your Makefile. If you follow the standard RIOT project structure, your Makefile should look like this:

./Makefile

# name of your application
APPLICATION = hello-world

# Change this to your board if you want to build for a different board
BOARD ?= esp32h2-devkit

# This has to be the absolute path to the RIOT base directory:
RIOTBASE ?= $(CURDIR)/RIOT

include $(RIOTBASE)/Makefile.include

Support for generic ESP32-H2 boards @author Gunar Schorcht gunar@schorcht.net

\section esp32h2_devkit ESP32-H2-DevKitM-1

Table of Contents

-# Overview -# Hardware -# MCU -# Board Configuration -# Board Pinout -# Flashing the Device

Overview

The Espressif ESP32-H2-DevKitM-1 board uses the ESP32-H2-MINI-1x module.

Since the number of GPIOs and their possible uses on the ESP32-H2 are quite limited, the ESP32-H2-DevKitM-1 should also work for most other ESP32-H2 boards. Any modifications required for specific applications could be overridden by esp32_application_specific_configurations “application-specific board configuration”.

Back to table of contents

Hardware

This section describes

• the MCU,
• the default board configuration,
• optional hardware configurations,
• the board pinout.

Back to table of contents

MCU

Most features of the board are provided by the ESP32-H2 SoC. For detailed information about the ESP32-H2 variant (family) and ESP32x SoCs, see section esp32_mcu_esp32 “ESP32 SoC Series”.

Back to table of contents

Board Configuration

ESP32-H2-DevKitM-1 boards have no special hardware on board with the exception of a WS2812-compatible RGB-LED.

All GPIOs are simply broken out for flexibility. Therefore, the board configuration is the most flexible one which provides:

• 5 x ADC channels at maximum
• 1 x SPI
• 1 x I2C
• 1 x UART
• 2 x PWM with 3 channels each
• 1 x RGB-LED

Since all GPIOs are broken out, GPIOs can be used for different purposes in different applications. For flexibility, GPIOs can be listed in multiple peripheral configurations, but they can only be used for one peripheral at a time. For example, GPIO1, GPIO3, GPIO4 and GPIO5 can be used as ADC channels or as signals for SPI_DEV(0) and PWM_DEV(1).

This is possible because GPIOs are only used for a specific peripheral interface when either

• the corresponding peripheral module is used, i.e. periph_spi, or
• the corresponding init function is called, i.e. adc_init, or
• the corresponding init function is called, i.e. pwm_init

That is, the purpose for which a GPIO is used depends on which module or function is used first.

For example, if module periph_spi is not used, the GPIOs listed in SPI configuration can be used for the other purposes, that is, GPIO1, GPIO4 and GPIO5 can be used as ADC channels or PWM channels.

The following table shows the default board configuration, which is sorted according to the defined functionality of GPIOs. This configuration can be overridden by esp32_application_specific_configurations “application-specific configurations”.

Function | GPIOs | Remarks |Configuration :---------------|:-------|:--------|:---------------------------------- BUTTON0 | GPIO9 | | | ADC | GPIO1, GPIO2, GPIO3, GPIO4, GPIO5 | | see esp32_adc_channels "ADC Channels" PWM_DEV(0) | GPIO2, GPIO12, GPIO22 | - | esp32_pwm_channels "PWM Channels" PWM_DEV(1) | GPIO1, GPIO3, GPIO5 | - | esp32_pwm_channels "PWM Channels" I2C_DEV(0):SCL | GPIO10 | | esp32_i2c_interfaces "I2C Interfaces" I2C_DEV(0):SDA | GPIO11 | | esp32_i2c_interfaces "I2C Interfaces" RGB-LED | GPIO8 | supported by driver module `ws281x` | | SPI_DEV(0):SCK | GPIO4 | SPI2_HOST (FSPI) is used | esp32_spi_interfaces "SPI Interfaces" SPI_DEV(0):MISO | GPIO5 | SPI2_HOST (FSPI) is used | esp32_spi_interfaces "SPI Interfaces" SPI_DEV(0):MOSI | GPIO0 | SPI2_HOST (FSPI) is used | esp32_spi_interfaces "SPI Interfaces" SPI_DEV(0):CS0 | GPIO1 | SPI2_HOST (FSPI) is used | esp32_spi_interfaces "SPI Interfaces" UART_DEV(0):TxD | GPIO24 | Console (configuration is fixed) | esp32_uart_interfaces "UART interfaces" UART_DEV(0):RxD | GPIO23 | Console (configuration is fixed) | esp32_uart_interfaces "UART interfaces" USB D- | GPIO26 | | | USB D+ | GPIO26 | | | \n @note - The configuration of ADC channels contains all ESP32-H2 GPIOs that could be used as ADC channels. - GPIO6 and GPIO7 are not broken out for any reason. - GPPIO15 to GPIO21 are used for the in-package flash and are not broken out.

For detailed information about the peripheral configurations of ESP32-H2 boards, see section esp32_peripherals “Common Peripherals”.

Back to table of contents

Board Pinout

The following figures show the pinout as configured by default board definition.

The corresponding board schematics can be found:

• ESP32-H2-DevKitM-1 v1.2
• ESP32-H2-DevKitM-1 v1.3

Back to table of contents

Flashing the Device

Flashing RIOT is quite easy. The board has a Micro-USB connector with reset/boot/flash logic. Just connect the board to your host computer and type using the programming port:

make flash BOARD=esp32h2-devkit ...

For detailed information about ESP32-H2 as well as configuring and compiling RIOT for ESP32-H2 boards, see esp32_riot.

Back to table of contents