Support for for Espressif ESP32-Ethernet-Kit. More...
Support for for Espressif ESP32-Ethernet-Kit.
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:
This section describes
Most features of the board are provided by the ESP32 SoC. For detailed information about the ESP32, see section MCU ESP32.
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 SoC Series Boards.
The board is available in different versions. See the per-version file for details.
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:
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/ttyUSB1, the make command would be used as following:
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 SoC Series Boards.
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] (https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/jtag-debugging/index.html) 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.
Furthermore the function switches (DIP switches) for the JTAG signals must be set to ON.
To flash and debug using OpenOCD, the precompiled version of OpenOCD for ESP32 has to be installed using the install script while being in RIOT's root directory, see also section [Using Local Toolchain Installation] (#esp32_local_toolchain_installation).
Before OpenOCD can then be used, the
PATH variable has to be set correctly and the
OPENOCD variable has to be exported using the following command.
PATH variable and the
OPENOCD variable are set, OpenOCD can be used
by setting the
PROGRAMMER variable to
esptool.pycan still be used. In that case, the
flashtarget is made without setting the
|ESP32-Ethernet-Kit V1.0 Board|
|Support for for Espressif ESP32-Ethernet-Kit v1.0. |
|ESP32-Ethernet-Kit V1.1 Board|
|Support for for Espressif ESP32-Ethernet-Kit v1.1. |
|ESP32-Ethernet-Kit V1.2 Board|
|Support for for Espressif ESP32-Ethernet-Kit V1.2. |
|Board specific configuration of direct mapped GPIOs. |
|Peripheral MCU configuration for Espressif ESP32-Ethernet-Kit. |