Wemos LOLIN D32 Pro

Support for Wemos LOLIN D32 Pro. More...

Detailed Description

Support for Wemos LOLIN D32 Pro.

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

Table of Contents

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

Overview    [TOC]

Wemos LOLIN D32 Pro is a development board that uses the ESP32-WROVER module which has a built-in 4 MByte SPI RAM. Most important features of the board are

Wemos LOLIN D32 Pro belongs to the class of general purpose boards where most ESP32 pins are broken out for easier access.

products:d32:d32_pro_v2.0.0_1_16x9.jpg
Wemos LOLIN D32 PRO

Hardware    [TOC]

This section describes

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.

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 448 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 yes
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 board for the Wemos LOLIN D32 Pro has the following on-board components:

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 Configuration* Remarks / Prerequisites Configuration
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 / LED0 SPI Interfaces
GPIO4 SPI_DEV(0):CS1 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
GPIO36 ADC_LINE(0) ADC Channels
GPIO39 ADC_LINE(1) ADC Channels
GPIO34 ADC_LINE(2) ADC Channels
GPIO35 ADC_LINE(3) VBat measurement (GPIO is not broken out) ADC Channels
GPIO32 ADC_LINE(4) TFT_LED when TFT is connected ADC Channels
GPIO33 ADC_LINE(5) TFT_RESETwhen TFT is connected ADC Channels
GPIO25 DAC_LINE(0) DAC Channels
GPIO26 DAC_LINE(1) DAC Channels
GPIO0 PWM_DEV(0):0MRF24J40/ENC28J60 RESET when module mrf24j40/enc2860 is used PWM Channels
GPIO2 PWM_DEV(0):1MRF24J40/ENC28J60 CS when module mrf24j40/enc2860 is used PWM Channels
GPIO13 - MRF24J40/ENC28J60 INT when module mrf24j40/enc2860 is used
GPIO15 -
GPIO12 - TS_CS when TFT is connected
GPIO14 - TFT_CS when TFT is connected
GPIO27 - TFT_DC when TFT is connected

* Default configuration cannot be used or is not available at all when optional configuration is used. For example, when the TFT is connected, GPIO32 is used as TFT_LED signal and ADC_LINE(4) is not available.

Note
When the TFT display is connected, add the following line to the makefile of the application to enable the according default board and peripheral configuration:
USEMODULE += esp_lolin_tft

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

Optional Hardware Configurations    [TOC]

MRF24J40-based IEEE 802.15.4 radio modules and 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 modules:

#ifdef BOARD_ESP32_WEMOS_LOLIN_D32_PRO
#if MODULE_MRF24J40
#define MRF24J40_PARAM_CS GPIO15 /* MRF24J40 CS signal */
#define MRF24J40_PARAM_RESET GPIO2 /* MRF24J40 RESET signal */
#define MRF24J40_PARAM_INT GPIO13 /* MRF24J40 INT signal */
#endif
#if MODULE_ENC28J80
#define ENC28J80_PARAM_CS GPIO15 /* ENC28J80 CS signal */
#define ENC28J80_PARAM_RESET GPIO2 /* ENC28J80 RESET signal */
#define ENC28J80_PARAM_INT GPIO13 /* ENC28J80 INT signal */
#endif
#endif

For other parameters, the default values defined by the drivers can be used.

Note
  • Only a few GPIOs are available for external hardware on the Wemos LOLIN D32 PRO. Therefore, MRF24J40 and ENC28J60 based modules use the same GPIOs and only one of these modules can be used simultaneously.
  • The RESET signal of MRF24J40 and 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.

Board Pinout    [TOC]

The following picture shows the pinout of WEMOS LOLIN D32 PRO 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.

Wemos_LOLIN_D32_PRO_pinout.png?inline=false
Wemos LOLIN D32 PRO pinout

Flashing the Device    [TOC]

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 using the programming port and type:

make flash BOARD=esp32-wemos-lolin-d32-pro ...

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 Wemos LOLIN D32 Pro.
 
file  gpio_params.h
 Board specific configuration of direct mapped GPIOs.
 
file  periph_conf.h
 Peripheral MCU configuration for Wemos LOLIN D32 Pro.