Connecting a ESP32-C3 and cannot seem to resolve "Errno 113" issue... Thoughts?

ESPHome
1

Trying to connect a ESP32-C3 dev board for the first time (tried both a M5Stamp C3 & ESP32-C3-DevKitM-1) and I cannot seem to get past the “Errno 113” error no matter what I’ve try.

Any suggestions on what I might be missing?

esphome:
  name: voc-sensor

esp32:
  board: esp32-c3-devkitm-1
  framework:
    type: esp-idf
    version: recommended
    # Custom sdkconfig options
    sdkconfig_options:
      CONFIG_COMPILER_OPTIMIZATION_SIZE: y
    # Advanced tweaking options
    advanced:
      ignore_efuse_mac_crc: false
      
# Enable logging
logger:

# Enable Home Assistant API
api:
  encryption:
    key: !secret encryption_key

#ota:
  password: !secret ota_password

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  manual_ip:
    static_ip: 192.168.1.230
    gateway: 192.168.1.1
    subnet: 255.255.255.0

  # Enable fallback hotspot in case wifi connection fails
  ap:
    ssid: "Voc-Sensor Fallback Hotspot"
    password: "1oeAgxJ7Cgts"

image
image1450×430 24.8 KB

2

As far as I have understood the newer models are not working or have issues at least.
I have not put more thought to it than noted that there are reports on not working.

3

I have been playing with a couple of C3 modules and after a lot of searching random sources for info the config that works for me is to use the latest version of ESPhome and this:

esphome:
  name: esp32-c3-test1
  platformio_options:
    board_build.flash_mode: dio
    platform_packages:
     - framework-espidf @ 3.40300.0

esp32:
  board: esp32-c3-devkitm-1
  variant: esp32c3
  framework:
    type: esp-idf
    platform_version: 3.4.0
4

I managed to run C3 in kinda “sneaky” way: i uploaded tasmota FW to it via tasmota’s web installer (that one works!), then when module was alive i uploaded esphome’s image via tasmota’s web server. Further OTA uploads then work perfectly from OTA.
And, arduino doesn’t work, you must set esp-idf.

5

I also tested the C3’s built-in USB-serial port on GPIO 18 & 19 and that works OK with ESPHome V22.6.3.

You get a ‘USB JTAG/serial debug unit’ at /dev/ttyACM0, so no need for any other adapters to do the initial load. Which is why Seeed and Adafruit and maybe others have released tiny C3 boards with a USB connector.

builtin usb-serial

6

@gaz99 I used your code and still seem to be having an issue. Does anything in mine look obviously problematic?

esphome:
  name: esp32-c3-test1
  platformio_options:
    board_build.flash_mode: dio
    platform_packages:
     - framework-espidf @ 3.40300.0

esp32:
  board: esp32-c3-devkitm-1
  variant: esp32c3
  framework:
    type: esp-idf
    platform_version: 3.4.0

# Enable logging
logger:

# Enable Home Assistant API
api:
  encryption:
    key: !secret encryption_key

#ota:
  password: !secret ota_password

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  manual_ip:
    static_ip: 192.168.1.230
    gateway: 192.168.1.1
    subnet: 255.255.255.0

  # Enable fallback hotspot in case wifi connection fails
  ap:
    ssid: "Esp32-C3-Test1 Fallback Hotspot"
    password: "0VTHlA2kSP9e"

image
image1813×403 16.9 KB

7

What version of ESPHome are you using ??

8

I am using 2022.8.0

9

I received a ESP-C3-12F dev board a couple of days ago and did some fresh tests last night.

My system is HAOS 2022.8.2 and ESPHome 2022.6.3

A ESP-C3 selected from the new device menu with the default settings will load OK but won’t boot.
Adding the ‘board_build.flash_mode: dio’ line allows it to boot OK

On my system the download logs it shows that I am using platform version 3.5.0 and framework version 3.40302.0 .

INFO Reading configuration /config/esphome/esp32-c3-12-kit.yaml...
INFO Generating C++ source...
INFO Compiling app...
Processing esp32-c3-12-kit (board: esp32-c3-devkitm-1; framework: espidf; platform: platformio/espressif32 @ 3.5.0)
--------------------------------------------------------------------------------
HARDWARE: ESP32C3 160MHz, 320KB RAM, 4MB Flash
 - framework-espidf 3.40302.0 (4.3.2) 
 - tool-cmake 3.16.4 
 - tool-ninja 1.7.1 
 - toolchain-riscv32-esp 8.4.0+2021r2-patch2 
 - toolchain-xtensa-esp32s2 8.4.0+2021r2-patch2

I will upgrade my system tonight to the latest version of ESPHome and re-do the tests.

My test code is:

esphome:
  name: esp32-c3-12-kit
  platformio_options:
    board_build.flash_mode: dio

esp32:
  board: esp32-c3-devkitm-1
  framework:
    type: esp-idf

# Enable logging
logger:

# Enable Home Assistant API
api:
#  encryption:
#    key: "zhHeUXsRkEbP42bp9LLO8LHr2rwRYirod60qMFyiRbs="

ota:
  password: "236451aa62da200cee65911e2e54fc3e"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot in case wifi connection fails
  ap:
    ssid: "Esp32-C3-12-Kit Fallback Hotspot"
    password: "g3NHYNcmJe1z"
  
  
sensor:

  - platform: wifi_signal
    name: "C3 WiFi"
    update_interval: 10s
10

Updated to HAOS 22.8.6 and ESPHome 22.8.0 and there is no change, it still works OK with just the addition of the ‘board_build.flash_mode: dio’ line. The platformio stuff is the same as ESPHome 22.6.3

What is the serial log showing, when I first tried a few weeks ago with aESP32-C3-01M I had a similar error and the log indicated it was a brownout error so I tried a different USB-serial converter.

[15:15:24]################################################
[15:15:24]arch:ESP32C3, 3
[15:15:24]compile_time:Ai-Thinker|B&T
[15:15:24]ble_mac:84F70352AAEE
[15:15:24]wifi_mac:84F70352AAEC
[15:15:24]sdk_version:v4.3-beta3-195-g6be10fab0
[15:15:24]firmware_version:2.2.0
[15:15:24]compile_time:Jul  5 2021 13:46:35
[15:15:24]
[15:15:24]ready
[15:15:24]
[15:15:25]################################################ESP-ROM:esp32c3-api1-20210207
[15:15:25]Build:Feb  7 2021
[15:15:25]rst:0xf (BROWNOUT_RST),boot:0xc (SPI_FAST_FLASH_BOOT)
[15:15:25]SPIWP:0xee
[15:15:25]mode:DIO, clock div:2
[15:15:25]load:0x3fcd6100,len:0x147c
[15:15:25]load:0x403ce000,len:0x91c
[15:15:25]load:0x403d0000,len:0x2838
[15:15:25]entry 0x403ce000
11

Bingo…You’re correct mine seems to work now with just the ‘board_build.flash_mode: dio’ line.