ESP32-C3 Debug Diary

littleshrimp

ESP32-C3 Debug Diary [Copy link]

 

This was my first time using ESP32 . Because I didn’t know Linux and couldn’t understand various command line operations, I finally chose the vscode tool.

Search for IDF in vscode to find ESP-IDF . After installation, the following interface will pop up. The latest version of IDF that can be installed on May 23 , 2021 is V4.2.1 . The other is Master. I don’t know if it is the latest version. However, the installation has failed many times and it has failed to connect to the specified file on github .

The ESP32 in hand can work normally with V4.2.1 , but when switching to ESP32-C3, it prompts "invalid choice: esp32c3. (choose from esp32, esp32s2) at ChildProcess." Because 4.2.1 does not support ESP32-C3 , 4.3 needs to be installed .

I downloaded 4.3 IDF from https://dl.espressif.com/dl/esp-idf/releases/esp-idf-v4.3-beta3.zip , unzipped it locally, and then selected Find ESP-IDF in your system and chose the corresponding directory. The directory when I unzipped it was D:\esp-idf-v4.3-beta3 , but I didn't expect that there was another esp- idf-v4.3-beta3 directory under D:\ esp-idf-v4.3-beta3 , and all the files were in the subdirectory D:\esp-idf-v4.3-beta\esp-idf-v4.3-beta3 . This may be the reason why I failed to install it many times.

I started to suspect that it was a python version issue after reading the logs, so I uninstalled several old versions and installed the latest version. Then when I installed the IDF plugin, it prompted that the python.exe file could not be found in the path of an old version . Even if I used the previous successful method to install v4.2.1 , the same error message appeared. To solve this problem, I uninstalled both IDF and VSCODE and it still didn't work again. Later, I deleted .espressif in the user folder and reinstalled IDF , but the problem was solved.

After successfully installing IDF 4.3 , I can switch to the ESP32-C3 model. After I downloaded a blink routine to the board, the LED did not blink. I began to suspect that there was something wrong with the GPIO logo on the schematic , because I contacted the seller on the weekend and there was no response. Later, I tried to use the serial port to check the data and found that the prompt "esp32c3 boot_comm: can't run on lower chip revision, expected 2, found 3" was found in the configuration file and everything was normal after changing the Rev 3 of the Minmum Supported ESP32-C3 Revision to Rev 2 .

After success, I finally saw the shining LED

soso

It was quite tortuous. I remembered how hard it was to install a software N years ago. Fortunately, I succeeded. There are things we can learn from my experience.

tagetage

I support the original poster, although I don't have ESP32.

数码小叶

The C series has just been released, so there are definitely a lot of pitfalls.

littleshrimp

Digital Leaf published on 2021-5-24 13:20 The C series has just been released, so there are definitely many pitfalls

This is my first time using ESP32, so these shouldn’t be a big problem. The main problem is that I don’t understand the development environment.

bigbat

There are many pitfalls in new products, and some products are commercialized before they are perfect. For example, Baidu's AI product! When it was first used, the test samples showed obvious errors, and that's not all! They also falsified it!!!

freebsder

Come on, Linux operation is not much more difficult than FPGA