ESP32-Ethernet-Kit

Support for for Espressif ESP32-Ethernet-Kit. More...

Detailed Description

Support for for Espressif ESP32-Ethernet-Kit.

Author
Gunar Schorcht gunar.nosp@m.@sch.nosp@m.orcht.nosp@m..net
Erik Ekman eekma.nosp@m.n@go.nosp@m.ogle..nosp@m.com

Table of Contents

  1. Overview
  2. Hardware
    1. MCU
    2. Board Configuration
  3. Flashing the Device
  4. On-Chip Debugging with the device

Overview    [TOC]

The Espressif ESP32-Ethernet-Kit is a development board that uses a ESP32-WROVER module (-B or -E depending on version). Most important features of the board are

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.

There are different revisions of the board:

Hardware    [TOC]

This section describes

MCU    [TOC]

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

Board Configuration    [TOC]

ESP32-Ethernet-Kit has the following on-board components

For detailed information about the configuration of ESP32 boards, see section Peripherals in RIOT-OS on ESP32 boards.

The board is available in different versions. See the per-version file for details.

Flashing the Device    [TOC]

Flashing RIOT is quite straight forward. The board has a Micro-USB connector with reset/boot/flash logic. Just connect the board using the programming port to your host computer and type:

make flash BOARD=esp32-ethernet-kit-v1_X ...

where X is the minor revision number of the board.

The USB bridge is based on FDI FT2232HL and offers two USB interfaces:

Therefore, it might be necessary have to declare the USB interface in the make command. For example, if the ESP32-Ethernet-Kit is connected to the host computer through the USB interfaces /dev/ttyUSB0 and /dev/ttyUSB1, the make command would be used as following:

make flash BOARD=esp32-ethernet-kit-v1_X PORT=/dev/ttyUSB1 ...

Please note that /dev/ttyUSB1 is used as the console port by default. Therefore the variable PORT only needs to be defined if the console port is another port.

For detailed information about ESP32 as well as configuring and compiling RIOT for ESP32 boards, see RIOT-OS on ESP32 boards.

On-Chip Debugging with the Device    [TOC]

Since the USB bridge based on FDI FT2232HL provides a JTAG interface for debugging through an USB interface, using ESP32-Ethernet-Kit is the easiest and most convenient way for On-Chip debugging. Please refer the ESP-IDF Programming Guide for details on how to setup and how to use ESP32-Ethernet-Kit and OpenOCD.

To use the JTAG interface, the esp_jtag module must be used to disable the SPI_DEV(0) which normally uses the GPIOs for the JTAG signals. USEMODULE=esp_jtag make flash BOARD=esp32-ethernet-kit-v1_X ... Furthermore the function switches (DIP switches) for the JTAG signals must be set to ON.

Modules

 v1.0 Board
 Support for for Espressif ESP32-Ethernet-Kit v1.0.
 
 v1.1 Board
 Support for for Espressif ESP32-Ethernet-Kit v1.1.
 
 v1.2 Board
 Support for for Espressif ESP32-Ethernet-Kit v1.2.
 

Files

file  board.h
 
file  gpio_params.h
 Board specific configuration of direct mapped GPIOs.
 
file  periph_conf.h
 Peripheral MCU configuration for Espressif ESP32-Ethernet-Kit.