MH-ET LIVE MiniKit¶
Support for MH-ET LIVE MiniKit for ESP32.
Table of Contents¶
Overview [TOC]¶
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
- 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 plattform 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.
Hardware [TOC]¶
This section describes
- the MCU,
- the default board configuration,
- optional hardware configurations,
- the board pinout.
MCU [TOC]¶
Most features of the board are provided by the ESP32 SoC. The following table summarizes these features and gives an overview of which of these features are supported by RIOT. For detailed information about the ESP32, see section .
MCU | ESP32 | Supported by RIOT |
---|---|---|
Vendor | Espressif | |
Cores | 1 or 2 x Tensilica Xtensa LX6 | 1 core |
FPU | yes (ULP - Ultra low power co-processor) | no |
RAM | 520 kByte SRAM 16 kByte RTC SRAM | yes |
ROM | 520 kByte | yes |
Flash | 512 kByte … 16 MByte | yes |
Frequency | 240 MHz, 160 MHz, 80 MHz | yes |
Power Consumption | 68 mA @ 240 MHz 44 mA @ 160 MHz 31 mA @ 80 MHz 5 uA in deep sleep mode | yes yes yes no |
Timers | 4 x 64 bit | yes |
ADCs | 2 x SAR-ADC with up to 18 x 12 bit channels total | yes |
DACs | 2 x DAC with 8 bit | yes |
GPIOs | 34 (6 of them are only inputs) | yes |
I2Cs | 2 | yes |
SPIs | 4 | yes |
UARTs | 3 | yes |
WiFi | IEEE 802.11 b/g/n built in | yes |
Bluetooth | v4.2 BR/EDR and BLE | no |
Ethernet | MAC interface with dedicated DMA and IEEE 1588 support | yes |
CAN | version 2.0 | no |
IR | up to 8 channels TX/RX | no |
Motor PWM | 2 devices x 6 channels | yes |
LED PWM | 16 channels | no |
Crypto | Hardware acceleration of AES, SHA-2, RSA, ECC, RNG | no |
Vcc | 2.5 - 3.6 V | |
Documents | Datasheet Technical Reference |
Board Configuration [TOC]¶
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 .
Pin | Default Configuration* | Optional Modules* | Remarks / Prerequisites | Configuration |
---|---|---|---|---|
GPIO2 | pwm.h::PWM_DEV :0 / LED blue |
|||
GPIO0 | pwm.h::PWM_DEV :1 |
|||
GPIO4 | pwm.h::PWM_DEV :2 |
|||
GPIO15 | pwm.h::PWM_DEV :3 |
|||
GPIO22 | i2c.h::I2C_DEV :SCL |
|||
GPIO21 | i2c.h::I2C_DEV :SDA |
|||
GPIO18 | spi.h::SPI_DEV :SCK |
|||
GPIO19 | spi.h::SPI_DEV :MISO |
|||
GPIO23 | spi.h::SPI_DEV :MOSI |
|||
GPIO5 | spi.h::SPI_DEV :CS0 |
SD Card CS | when module sdcard_spi is used | |
GPIO1 | uart.h::UART_DEV :TxD |
Console (configuration is fixed) | ||
GPIO3 | uart.h::UART_DEV :RxD |
Console (configuration is fixed) | ||
GPIO9 | uart.h::UART_DEV :TxD |
|||
GPIO10 | uart.h::UART_DEV :RxD |
|||
GPIO34 | adc.h::ADC_LINE |
|||
GPIO35 | adc.h::ADC_LINE |
|||
GPIO36 | adc.h::ADC_LINE |
|||
GPIO39 | adc.h::ADC_LINE |
|||
GPIO25 | dac.h::DAC_LINE |
|||
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
Optional Hardware Configurations [TOC]¶
ENC28J60-based Ethernet network interface modules have been tested with the board. You could use the following code in your to use such a module:
1 2 3 4 5 | #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
|
Board Pinout [TOC]¶
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 in table board configuration.
The corresponding board schematic can be found here
MCU [TOC]¶
Most features of the board are provided by the ESP32 SoC. The following table summarizes these features and gives an overview of which of these features are supported by RIOT. For detailed information about the ESP32, see section .
MCU | ESP32 | Supported by RIOT |
---|---|---|
Vendor | Espressif | |
Cores | 1 or 2 x Tensilica Xtensa LX6 | 1 core |
FPU | yes (ULP - Ultra low power co-processor) | no |
RAM | 520 kByte SRAM 16 kByte RTC SRAM | yes |
ROM | 520 kByte | yes |
Flash | 512 kByte … 16 MByte | yes |
Frequency | 240 MHz, 160 MHz, 80 MHz | yes |
Power Consumption | 68 mA @ 240 MHz 44 mA @ 160 MHz 31 mA @ 80 MHz 5 uA in deep sleep mode | yes yes yes no |
Timers | 4 x 64 bit | yes |
ADCs | 2 x SAR-ADC with up to 18 x 12 bit channels total | yes |
DACs | 2 x DAC with 8 bit | yes |
GPIOs | 34 (6 of them are only inputs) | yes |
I2Cs | 2 | yes |
SPIs | 4 | yes |
UARTs | 3 | yes |
WiFi | IEEE 802.11 b/g/n built in | yes |
Bluetooth | v4.2 BR/EDR and BLE | no |
Ethernet | MAC interface with dedicated DMA and IEEE 1588 support | yes |
CAN | version 2.0 | no |
IR | up to 8 channels TX/RX | no |
Motor PWM | 2 devices x 6 channels | yes |
LED PWM | 16 channels | no |
Crypto | Hardware acceleration of AES, SHA-2, RSA, ECC, RNG | no |
Vcc | 2.5 - 3.6 V | |
Documents | Datasheet Technical Reference |
Board Configuration [TOC]¶
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 .
Pin | Default Configuration* | Optional Modules* | Remarks / Prerequisites | Configuration |
---|---|---|---|---|
GPIO2 | pwm.h::PWM_DEV :0 / LED blue |
|||
GPIO0 | pwm.h::PWM_DEV :1 |
|||
GPIO4 | pwm.h::PWM_DEV :2 |
|||
GPIO15 | pwm.h::PWM_DEV :3 |
|||
GPIO22 | i2c.h::I2C_DEV :SCL |
|||
GPIO21 | i2c.h::I2C_DEV :SDA |
|||
GPIO18 | spi.h::SPI_DEV :SCK |
|||
GPIO19 | spi.h::SPI_DEV :MISO |
|||
GPIO23 | spi.h::SPI_DEV :MOSI |
|||
GPIO5 | spi.h::SPI_DEV :CS0 |
SD Card CS | when module sdcard_spi is used | |
GPIO1 | uart.h::UART_DEV :TxD |
Console (configuration is fixed) | ||
GPIO3 | uart.h::UART_DEV :RxD |
Console (configuration is fixed) | ||
GPIO9 | uart.h::UART_DEV :TxD |
|||
GPIO10 | uart.h::UART_DEV :RxD |
|||
GPIO34 | adc.h::ADC_LINE |
|||
GPIO35 | adc.h::ADC_LINE |
|||
GPIO36 | adc.h::ADC_LINE |
|||
GPIO39 | adc.h::ADC_LINE |
|||
GPIO25 | dac.h::DAC_LINE |
|||
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
Optional Hardware Configurations [TOC]¶
ENC28J60-based Ethernet network interface modules have been tested with the board. You could use the following code in your to use such a module:
1 2 3 4 5 | #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
|
Board Pinout [TOC]¶
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 in table board configuration.
The corresponding board schematic can be found here
Flashing the Device [TOC]¶
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:
1 | make flash BOARD=esp32-mh-et-live-minikit ...
|