MH-ET LIVE MiniKit

Support for MH-ET LIVE MiniKit for ESP32. More...

Detailed Description

Support for MH-ET LIVE MiniKit for ESP32.

Author
Gunar Schorcht gunar.nosp@m.@sch.nosp@m.orcht.nosp@m..net

<a name="toc"> Table of Contents </a>

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

<a name="overview"> Overview </a>    [<a href="#toc">TOC</a>]

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:

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.

MH-ET LIVE MiniKit for ESP32

This stackable platform was tested in an RIOT application with:

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

RIOT application with SD-Card, MRF24J40 Radio, and BMP180 Pressure Sensor

<a name="hardware"> Hardware </a>    [<a href="#toc">TOC</a>]

This section describes

<a name="mcu"> MCU </a>    [<a href="#toc">TOC</a>]

Most features of the board are provided by the ESP32 SoC. For detailed information about the ESP32, see section MCU ESP32.

<a name="board_configuration"> Board Configuration </a>    [<a href="#toc">TOC</a>]

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 application-specific configuration.

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

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

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

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

<a name="optional_hardware"> Optional Hardware Configurations </a>    [<a href="#toc">TOC</a>]

ENC28J60-based Ethernet network interface modules have been tested with the board. You could use the following code in your 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 pinout) to keep the configured GPIO free for other purposes.

<a name="pinout"> Board Pinout </a>    [<a href="#toc">TOC</a>]

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 optional functions in table board configuration.

The corresponding board schematic can be found here

MH-ET LIVE MiniKit for ESP32 pinout

<a name="flashing"> Flashing the Device </a>    [<a href="#toc">TOC</a>]

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 RIOT-OS on ESP32 boards.

Files

file  arduino_board.h
 Board specific configuration for the Arduino API.
 
file  arduino_pinmap.h
 Mapping from MCU pins to Arduino pins.
 
file  board.h
 Board specific definitions for MH-ET LIVE MiniKit for ESP32.
 
file  board_modules.h
 Definitions for Wemos stackable hardware modules (shields)
 
file  gpio_params.h
 Board specific configuration of direct mapped GPIOs.
 
file  periph_conf.h
 Peripheral MCU configuration for MH-ET LIVE MiniKit for ESP32.