Support for generic ESP32-WROOM-32 boards. More...
Support for generic ESP32-WROOM-32 boards.
This board definition covers not just a single board, but rather a large set of generic boards that use an ESP32-WROOM-32 module and simply break out all GPIOs to external pads without having any special hardware or interfaces on-board. Examples are Espressif's ESP32-DevKitC or NodeMCU-ESP32S and a large number of clones.
This section describes
Most features of the board are provided by the ESP32 SoC. For detailed information about the ESP32, see section MCU ESP32.
Generic ESP32-WROOM-32 boards do not have special hardware on board and all GPIOs are simply broken out for flexibility. Therefore, the board configuration is the most flexible one with provides:
18 x ADC channels at maximum 2 x DAC channels at maximum 2 x SPI at maximum 1 x I2C at maximum 2 x UART
Since all GPIOs have broken out, GPIOs can be used for different purposes in different applications. For flexibility, GPIOs can be listed in various peripheral configurations. For example, GPIO13 is used in the ADC channel definition and the definition of the MOSI signal of SPI_DEV(0).
This is possible because GPIOs are only used for a specific peripheral interface when
That is, the purpose for which a GPIO is used depends on which module or function is used first.
For example, if module periph_i2c is not used, the GPIOs listed in I2C configuration can be used for the other purposes.
The following table shows the default board configuration, which is sorted according to the defined functionality of GPIOs. This configuration can be overridden by application-specific configurations.
|ADC||GPIO0, GPIO2, GPIO4, GPIO12, GPIO13,|
GPIO14, GPIO15, GPIO25, GPIO26, GPIO27,
GPIO32, GPIO33, GPIO34, GPIO35, GPIO36,
|see ADC Channels|
|PWM_DEV(0)||GPIO0, GPIO2, GPIO4, GPIO16, GPIO17||-||DAC Channels|
|PWM_DEV(1)||GPIO27, GPIO32, GPIO33||-||PWM Channels|
|SPI_DEV(0):CLK||GPIO18||VSPI is used||SPI Interfaces|
|SPI_DEV(0):MISO||GPIO19||VSPI is used||SPI Interfaces|
|SPI_DEV(0):MOSI||GPIO23||VSPI is used||SPI Interfaces|
|SPI_DEV(0):CS0||GPIO5||VSPI is used||SPI Interfaces|
|SPI_DEV(1):CLK||GPIO14||HSPI is used||SPI Interfaces|
|SPI_DEV(1):MISO||GPIO12||HSPI is used||SPI Interfaces|
|SPI_DEV(1):MOSI||GPIO13||HSPI is used||SPI Interfaces|
|SPI_DEV(1):CS0||GPIO15||HSPI is used||SPI Interfaces|
|UART_DEV(0):TxD||GPIO1||Console (configuration is fixed)||UART interfaces|
|UART_DEV(0):RxD||GPIO3||Console (configuration is fixed)||UART interfaces|
|UART_DEV(1):TxD||GPIO10||not available in qout and qio flash mode||UART interfaces|
|UART_DEV(1):RxD||GPIO9||not available in qout and qio flash mode||UART interfaces|
For detailed information about the configuration of ESP32 boards, see section Common Peripherals.
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:
For other parameters, the default values defined by the drivers can be used.
The following figure shows the pinout of the defined default configuration for the EPS32-DevKitC board as an example of generic ESP32-WROOM-32 boards. 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 Board Configuration for more information.
The corresponding board schematics can be found here
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:
For detailed information about ESP32 as well as configuring and compiling RIOT for ESP32 boards, see RIOT-OS on ESP32 SoC Series Boards.
|Mapping from MCU pins to Arduino pins. |
|Board specific definitions for generic ESP32-WROOM-32 boards. |
|Board specific configuration of direct mapped GPIOs. |
|Peripheral MCU configuration for generic ESP32-WROOM-32 boards. |