ESP32-C6-DevKit Board

Support for generic ESP32-C6 boards. More...

Detailed Description

Support for generic ESP32-C6 boards.

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

ESP32-C6-DevKit

Table of Contents

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

Overview

The Espressif ESP32-C6-DevKit boards are a couple of boards that use one of the following modules:

Since the number of GPIOs and their possible uses on the ESP32-C6 are quite limited, the ESP32-C6-DevKit should also work for most other ESP32-C6 boards. Any modifications required for specific applications could be overridden by application-specific board configuration.

Espressif ESP32-C6-DevKitM-1

Back to table of contents

Hardware

This section describes

Back to table of contents

MCU

Most features of the board are provided by the ESP32-C6 SoC. For detailed information about the ESP32-C6 variant (family) and ESP32x SoCs, see section ESP32 SoC Series.

Back to table of contents

Board Configuration

ESP32-C6-DevKit boards have no special hardware on board with the exception of a WS2812-compatible RGB-LED.

All GPIOs are simply broken out for flexibility. Therefore, the board configuration is the most flexible one which provides:

Since all GPIOs are broken out, GPIOs can be used for different purposes in different applications. For flexibility, GPIOs can be used in multiple peripheral configurations, but they can only be used for one peripheral at a time. For example, GPIO4 and GPIO5 are defined as ADC channels and signals for I2C_DEV(0), GPIO7 and GPIO18 are defined as channels for PWM_DEV(1) and signals for SPI_DEV(0).

This is possible because GPIOs are only used for a specific peripheral interface when either

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, that is, GPIO4 and GPIO5 can be used as ADC channels.

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.

Function GPIOs Remarks Configuration
BUTTON0 GPIO9
ADC GPIO0, GPIO1, GPIO2, GPIO3, GPIO4, GPIO5, GPIO6 see ADC Channels
PWM_DEV(0) GPIO19, GPIO20, GPIO21 - PWM Channels
PWM_DEV(1) GPIO22, GPIO18, GPIO7 - PWM Channels
I2C_DEV(0):SCL GPIO5 I2C Interfaces
I2C_DEV(0):SDA GPIO4 I2C Interfaces
RGB-LED GPIO8 supported by driver module ws281x
SPI_DEV(0):CLK GPIO6 SPI2_HOST (FSPI) is used SPI Interfaces
SPI_DEV(0):MISO GPIO2 SPI2_HOST (FSPI) is used SPI Interfaces
SPI_DEV(0):MOSI GPIO7 SPI2_HOST (FSPI) is used SPI Interfaces
SPI_DEV(0):CS0 GPIO18 SPI2_HOST (FSPI) is used SPI Interfaces
UART_DEV(0):TxD GPIO16 Console (configuration is fixed) UART interfaces
UART_DEV(0):RxD GPIO17 Console (configuration is fixed) UART interfaces
USB D- GPIO12
USB D+ GPIO13


Note
  • The configuration of ADC channels contains all ESP32-C6 GPIOs that could be used as ADC channels.
  • GPIO10, GPIO11 and GPIO24 to GPIO30 are used for internal flash and are not broken out.
  • GPIO0 and GPIO1 can be used to connect an external 32.678 kHz crystal.
  • GPIO15 is a strapping pin used to select the JTAG interface if JTAG_SEL_ENABLE is burned in the eFuses.

For detailed information about the peripheral configurations of ESP32-C6 boards, see section Common Peripherals.

Back to table of contents

Board Pinout

The following figures show the pinouts as configured by default board definition.

EPS32-C6-DevKitM-1x Pinout
EPS32-C6-DevKitC-1x Pinout

The corresponding board schematics can be found:

Back to table of contents

Flashing the Device

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 execute command:

BOARD=esp32c6-devkit make flash ...

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

Back to table of contents

Files

file  arduino_iomap.h
 Mapping from MCU pins to Arduino pins.
 
file  board.h
 Board definitions for ESP32-C6-DevKit boards.
 
file  gpio_params.h
 Board specific configuration of direct mapped GPIOs.
 
file  periph_conf.h
 Peripheral configurations for ESP32-C6-DevKit boards.