ESP32-Ethernet-Kit V1.0 Board

View API Documentation View API documentation generated by Doxygen.

View on GitHub View this source code on GitHub.

Support for for Espressif ESP32-Ethernet-Kit v1.0

Related Boards

ESP32-Ethernet-Kit Support for for Espressif ESP32-Ethernet-Kit

When using this board with RIOT, set the BOARD variable to esp32-ethernet-kit-v1_0 in your Makefile. If you follow the standard RIOT project structure, your Makefile should look like this:

# name of your application
APPLICATION = hello-world

# Change this to your board if you want to build for a different board
BOARD ?= esp32-ethernet-kit-v1_0

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

include $(RIOTBASE)/Makefile.include

Support for for Espressif ESP32-Ethernet-Kit v1.0 @author Gunar Schorcht gunar@schorcht.net @author Erik Ekman eekman@google.com

\section esp32-ethernet-kit-v1_0 Espressif ESP32-Ethernet-Kit V1.0

Overview

The Espressif ESP32-Ethernet-Kit is a development board that uses the ESP32-WROVER-B module. Most important features of the board are

100 Mbps Ethernet via IP101G PHY
USB bridge with JTAG interface

Furthermore, some GPIOs are broken out for extension. The USB bridge based on FDI FT2232HL provides a JTAG interface for OCD debugging through the USB interface. For flashing and debugging the board, see boards_esp32_esp-ethernet-kit common board documentation.

Hardware

Board Configuration

ESP32-Ethernet-Kit v1.0 has the following on-board components

100 Mbps Ethernet via IP101G PHY
USB bridge with JTAG interface

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

@note Only a few GPIOs are broken out and available for external hardware on ESP32-Ethernet-Kit boards. Which GPIOs are available as peripherals depends on used modules.

Function | GPIOs | Remarks |Configuration :---------------|:-------|:--------|:---------------------------------- BTN0 | GPIO0 | not available if `esp_eth` is used | | ADC | GPIO34, GPIO35, GPIO36, GPIO39 | | esp32_adc_channels "ADC Channels" DAC | - | | esp32_dac_channels "DAC Channels" PWM_DEV(0) | GPIO4 | | esp32_pwm_channels "PWM Channels" I2C_DEV(0):SDA | GPIO32 | | esp32_i2c_interfaces "I2C Interfaces" I2C_DEV(0):SCL | GPIO33 | | esp32_i2c_interfaces "I2C Interfaces" SPI_DEV(0):CLK | GPIO14 | HSPI is used | esp32_spi_interfaces "SPI Interfaces" SPI_DEV(0):MISO | GPIO12 | HSPI is used | esp32_spi_interfaces "SPI Interfaces" SPI_DEV(0):MOSI | GPIO13 | HSPI is used | esp32_spi_interfaces "SPI Interfaces" SPI_DEV(0):CS0 | GPIO15 | HSPI is used | esp32_spi_interfaces "SPI Interfaces" UART_DEV(0):TxD | GPIO1 | Console (configuration is fixed) | esp32_uart_interfaces "UART interfaces" UART_DEV(0):RxD | GPIO3 | Console (configuration is fixed) | esp32_uart_interfaces "UART interfaces"
@note - GPIO4 only works properly on the board if the function switch for GPIO4 (DIP SW 5) is OFF. - SPI_DEV(0) is not available if module `esp_jtag` is used. For the SPI_DEV(0) pins to work properly, the function switches (DIP switches) for the JTAG signals must be set to OFF.

Board Pinout

The board schematic can be found here.

By default, only 3 bidirectional GPIO pins are unused: GPIO4, GPIO32, GPIO33. The suggested configuration is for PWM and I2C, but they can also be used for SPI or another serial port. By disabling the JTAG interface on the board, another 4 GPIOs can be made available (GPIO12, GPIO13, GPIO14, GPIO15).