MH-ET LIVE MiniKit

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 esp32-mh-et-live-minikit 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 ?= esp32-mh-et-live-minikit

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

include $(RIOTBASE)/Makefile.include

Support for MH-ET LIVE MiniKit for ESP32 @author Gunar Schorcht gunar@schorcht.net

\section esp32_mh_et_live_minikit MH-ET LIVE MiniKit for ESP32

Table of Contents

1. Overview
2. Hardware
   1. MCU
   2. Board Configuration
   3. Board Pinout
   4. Optional Hardware Configurations
3. Flashing the Device

Overview

The MH-ET LIVE MiniKit for ESP32 uses the ESP32-WROOM-32 module. It is a very interesting development kit as it uses in the stackable Wemos D1 Mini format. Thus, all shields for Wemos D1 mini for ESP8266 can also be used with ESP32. Examples for such shields are:

• Micro SD-Card Shield (enable module sdcard_spi to use it)
• MRF24J40 IEEE 802.15.4 radio Shield
• Button Shield
• RGB LED Shield
• …

This makes it possible to create different hardware configurations without the need for a soldering iron or a breadboard.

MH-ET LIVE MiniKit for ESP32 belongs to the class of general purpose boards where most ESP32 pins are broken out for easier access.

This stackable platform was tested in an RIOT application with:

• Micro SD-Card Shield
• MRF24J40 IEEE 802.15.4 radio Shield (contact gunar@schorcht.net for more information)
• BMP180 Pressure Sensor Shield

This application is a good example how easy it is with this board to create different hardware applications.

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 SoC. For detailed information about the ESP32, see section esp32_mcu_esp32 “MCU ESP32”.

Back to table of contents

Board Configuration

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

Pin | Default Configuration* | Optional Modules | Remarks / Prerequisites | Configuration :------|:-------------------------|:--------------------------|:--------|:------ GPIO2 | PWM_DEV(0):0 / LED blue | | | esp32_pwm_channels "PWM Channels" GPIO0 | PWM_DEV(0):1 | | | esp32_pwm_channels "PWM Channels" GPIO4 | PWM_DEV(0):2 | | | esp32_pwm_channels "PWM Channels" GPIO15 | PWM_DEV(0):3 | | | esp32_pwm_channels "PWM Channels" GPIO22 | I2C_DEV(0):SCL | | | esp32_i2c_interfaces "I2C Interfaces" GPIO21 | I2C_DEV(0):SDA | | | esp32_i2c_interfaces "I2C Interfaces" GPIO18 | SPI_DEV(0):SCK | | | esp32_spi_interfaces "SPI Interfaces" GPIO19 | SPI_DEV(0):MISO | | | esp32_spi_interfaces "SPI Interfaces" GPIO23 | SPI_DEV(0):MOSI | | | esp32_spi_interfaces "SPI Interfaces" GPIO5 | SPI_DEV(0):CS0 | SD Card CS | when module drivers_sdcard_spi "sdcard_spi" is used | esp32_spi_interfaces "SPI Interfaces" GPIO1 | UART_DEV(0):TxD | | Console (configuration is fixed) | esp32_uart_interfaces "UART interfaces" GPIO3 | UART_DEV(0):RxD | | Console (configuration is fixed) | esp32_uart_interfaces "UART interfaces" GPIO9 | UART_DEV(1):TxD | | | esp32_uart_interfaces "UART interfaces" GPIO10 | UART_DEV(1):RxD | | | esp32_uart_interfaces "UART interfaces" GPIO34 | ADC_LINE(0) | | | esp32_adc_channels "ADC Channels" GPIO35 | ADC_LINE(1) | | | esp32_adc_channels "ADC Channels" GPIO36 | ADC_LINE(2) | | | esp32_adc_channels "ADC Channels" GPIO39 | ADC_LINE(3) | | | esp32_adc_channels "ADC Channels" GPIO25 | DAC_LINE(0) | | | esp32_dac_channels "DAC Channels" GPIO13 | - | | | | GPIO12 | - | | | | GPIO14 | - | | | | GPIO16 | - | MRF24J40 RESET | when module drivers_mrf24j40 "mrf24j40" is used | | GPIO17 | - | MRF24J40 INT | when module drivers_mrf24j40 "mrf24j40" is used | | GPIO26 | - | MRF24J40 CS | when module drivers_mrf24j40 "mrf24j40" is used | | GPIO27 | - | | | | GPIO32 | - | | | | GPIO33 | - | | | |

\b * Default configuration cannot be used or is not available at all when optional hardware is used.

@note

• GPIO9 and GIOP10 can only be used in dout and dio esp32_flash_modes “flash modes”.
• The RESET signal of MRF24J40 shield can be connected to the RST pin of the board (see esp32_mh_et_live_minikit_pinout_img “pinout”) to keep the configured GPIO free for other purposes.

For detailed information about the configuration of ESP32 boards, see section esp32_peripherals “Common Peripherals”.

Back to table of contents

Optional Hardware Configurations

ENC28J60-based Ethernet network interface modules have been tested with the board. You could use the following code in your esp32_application_specific_configurations “application-specific configuration” to use such a module:

#if MODULE_ENC28J80 && BOARD_ESP32_MH_ET_LIVE_MINIKIT
#define ENC28J80_PARAM_CS       GPIO14      /* ENC28J80 CS signal    */
#define ENC28J80_PARAM_INT      GPIO33      /* ENC28J80 INT signal   */
#define ENC28J80_PARAM_RESET    GPIO12      /* ENC28J80 RESET signal */
#endif

For ENC28J80_PARAM_SPI the default parameter defined by the driver can be used.

Note: The RESET signal of ENC28J60 based modules can also be connected to the RST pin of the board (see esp32_mh_et_live_minikit_pinout_img “pinout”) to keep the configured GPIO free for other purposes.

Back to table of contents

Board Pinout

The following picture shows the pinout of MH-ET LIVE MiniKit for ESP32 board as defined by the default board configuration. The light green GPIOs are not used by configured on-board hardware components and can be used for any purpose. However, if optional off-board hardware modules are used, these GPIOs may also be occupied, see section esp32_mh_et_live_minikit_board_configuration for more information.

The corresponding board schematic can be found here

\anchor esp32_mh_et_live_minikit_pinout_img

Back to table of contents

Flashing the Device

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

make flash BOARD=esp32-mh-et-live-minikit ...

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

Back to table of contents