ESP32-C3-DevKitC-02 is an entry-level development board based on ESP32-C3-WROOM-02, a general-purpose module with 4 MB SPI flash. This board integrates complete Wi-Fi and Bluetooth® Low Energy functions. For more information, check ESP32-C3-DevKitC [1].
HardwareïESP32-C3 is a single-core Wi-Fi and Bluetooth 5 (LE) microcontroller SoC, based on the open-source RISC-V architecture. It strikes the right balance of power, I/O capabilities and security, thus offering the optimal cost-effective solution for connected devices. The availability of Wi-Fi and Bluetooth 5 (LE) connectivity not only makes the device configuration easy, but it also facilitates a variety of use-cases based on dual connectivity.
The features include the following:
32-bit core RISC-V microcontroller with a maximum clock speed of 160 MHz
400 KB of internal RAM
802.11b/g/n/e/i
A Bluetooth LE subsystem that supports features of Bluetooth 5 and Bluetooth Mesh
Various peripherals:
12-bit ADC with up to 6 channels
TWAI compatible with CAN bus 2.0
Temperature sensor
3x SPI
1x I2S
1x I2C
2x UART
LED PWM with up to 6 channels
Cryptographic hardware acceleration (RNG, ECC, RSA, SHA-2, AES)
For more information, check the datasheet at ESP32-C3 Datasheet [2] or the technical reference manual at ESP32-C3 Technical Reference Manual [3].
Supported FeaturesïThe esp32c3_devkitc board supports the hardware features listed below.
vnd,foo
esp32c3_devkitc/esp32c3 targetï
Type
Location
Description
Compatible
CPU
on-chip
Espressif RISC-V CPU1
ADC
on-chip
ESP32 ADC1
Bluetooth
on-chip
Bluetooth HCI for Espressif ESP321
CAN
on-chip
ESP32 Two-Wire Automotive Interface (TWAI)1
Clock control
on-chip
ESP32 Clock (Power & Clock Controller Module) Module1
Counter
on-chip
ESP32 general-purpose timers2
on-chip
ESP32 counters2
DMA
on-chip
ESP32 GDMA (General Direct Memory Access)1
Flash controller
on-chip
ESP32 flash controller1
espressif,esp32-flash-controller
GPIO & Headers
on-chip
ESP32 GPIO controller1
I2C
on-chip
ESP32 I2C1
I2S
on-chip
ESP32 I2S1
Input
on-board
Group of GPIO-bound input keys1
Interrupt controller
on-chip
ESP32 Interrupt controller1
MTD
on-chip
Flash node1
on-chip
Fixed partitions of a flash (or other non-volatile storage) memory1
Pin control
on-chip
ESP32 pin controller1
PWM
on-chip
ESP32 LED Control (LEDC)1
RNG
on-chip
ESP32 TRNG (True Random Number Generator)1
Sensors
on-chip
ESP32 temperature sensor1
Serial controller
on-chip
on-chip
ESP32 UART1
SPI
on-chip
ESP32 SPI1
Timer
on-chip
ESP32 System Timer1
Watchdog
on-chip
ESP32 XT Watchdog Timer1
on-chip
Wi-Fi
on-chip
ESP32 SoC Wi-Fi1
System requirementsï PrerequisitesïEspressif HAL requires WiFi and Bluetooth binary blobs in order work. Run the command below to retrieve those files.
west blobs fetch hal_espressif
Note
It is recommended running the command above after west update.
The esp32c3_devkitc board supports the runners and associated west commands listed below.
The board could be loaded using the single binary image, without 2nd stage bootloader. It is the default option when building the application without additional configuration.
Note
Simple boot does not provide any security features nor OTA updates.
MCUboot bootloaderïUser may choose to use MCUboot bootloader instead. In that case the bootloader must be built (and flashed) at least once.
There are two options to be used when building an application:
Sysbuild
Manual build
Note
User can select the MCUboot bootloader by adding the following line to the board default configuration file.
CONFIG_BOOTLOADER_MCUBOOT=ySysbuildï
The sysbuild makes possible to build and flash all necessary images needed to bootstrap the board with the ESP32 SoC.
To build the sample application using sysbuild use the command:
west build -b esp32c3_devkitc --sysbuild samples/hello_world
By default, the ESP32 sysbuild creates bootloader (MCUboot) and application images. But it can be configured to create other kind of images.
Build directory structure created by sysbuild is different from traditional Zephyr build. Output is structured by the domain subdirectories:
build/ âââ hello_world â âââ zephyr â âââ zephyr.elf â âââ zephyr.bin âââ mcuboot â âââ zephyr â âââ zephyr.elf â âââ zephyr.bin âââ domains.yaml
Note
With --sysbuild option the bootloader will be re-build and re-flash every time the pristine build is used.
For more information about the system build please read the Sysbuild (System build) documentation.
Manual buildïDuring the development cycle, it is intended to build & flash as quickly possible. For that reason, images can be built one at a time using traditional build.
The instructions following are relevant for both manual build and sysbuild. The only difference is the structure of the build directory.
Note
Remember that bootloader (MCUboot) needs to be flash at least once.
Build and flash applications as usual (see Building an Application and Run an Application for more details).
# From the root of the zephyr repository west build -b esp32c3_devkitc samples/hello_world
The usual flash target will work with the esp32c3_devkitc board configuration. Here is an example for the Hello World application.
# From the root of the zephyr repository west build -b esp32c3_devkitc samples/hello_world west flash
Open the serial monitor using the following command:
After the board has automatically reset and booted, you should see the following message in the monitor:
***** Booting Zephyr OS vx.x.x-xxx-gxxxxxxxxxxxx ***** Hello World! esp32c3_devkitcBoard variants using Snippetsï
ESP32 boards can be assembled with different modules using multiple combinations of SPI flash sizes, PSRAM sizes and PSRAM modes. The snippets under snippets/espressif provide a modular way to apply these variations at build time without duplicating board definitions.
The following snippet-based variants are supported:
Snippet name
Description
Flash memory size
flash-4M
Board with 4MB of flash
flash-8M
Board with 8MB of flash
flash-16M
Board with 16MB of flash
flash-32M
Board with 32MB of flash
PSRAM memory size
psram-2M
Board with 2MB of PSRAM
psram-4M
Board with 4MB of PSRAM
psram-8M
Board with 8MB of PSRAM
PSRAM utilization
psram-reloc
Relocate flash to PSRAM
psram-wifi
Wi-Fi buffers in PSRAM
To apply a board variant, use the -S flag with west build:
west build -b <esp_board_name_qualifier> -S flash-32M -S psram-4M samples/hello_world
Note: These snippets are applicable to boards with compatible hardware support for the selected flash/PSRAM configuration.
DebuggingïAs with much custom hardware, the ESP32-C3 modules require patches to OpenOCD that are not upstreamed yet. Espressif maintains their own fork of the project. The custom OpenOCD can be obtained at OpenOCD ESP32 [4].
The Zephyr SDK uses a bundled version of OpenOCD by default. You can overwrite that behavior by adding the -DOPENOCD=<path/to/bin/openocd> -DOPENOCD_DEFAULT_PATH=<path/to/openocd/share/openocd/scripts> parameter when building.
Here is an example for building the Hello World application.
# From the root of the zephyr repository west build -b esp32c3_devkitc samples/hello_world -- -DOPENOCD=<path/to/bin/openocd> -DOPENOCD_DEFAULT_PATH=<path/to/openocd/share/openocd/scripts> west flash
You can debug an application in the usual way. Here is an example for the Hello World application.
# From the root of the zephyr repository west build -b esp32c3_devkitc samples/hello_world west debugReferencesï
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4