[ESP32-S2-Kaluga-1 Review] Running ESP32 3 Driver Installation Bug

北方

[ESP32-S2-Kaluga-1 Review] Running ESP32 3 Driver Installation Bug [Copy link]

 

1. After installing the driver according to the manual and configuring the development tools, I found that the serial port driver was not successfully connected.

In fact, the entire serial port is quite informative. It is a dual serial port, one of which is a VCP virtual serial port, so it is displayed as two yellow exclamation marks. After many experiments, the FTDI driver was successfully installed, but the hardware cannot be recognized. Let's continue to study.

2. However, it is meaningful to take some time to analyze the four supporting expansion boards.

2.1 ESP-LyraP-CAM camera function. The specific connection is as follows:

Mainboard camera pin header	Connect to motherboard header
Power LED indicator	If the power supply voltage is normal, the red LED lights up
Camera module connector	Hardware supports OV2640 and OV3660 camera modules; currently, ESP-LyraP-CAM provides OV2640 camera module by default

The corresponding interfaces and pins are as follows

OV2640 is a 1/4-inch CMOS UXGA (1632*1232) image sensor produced by OmniVision. It supports automatic control functions such as automatic exposure control, automatic gain control, automatic white balance, and automatic elimination of light streaks.

UXGA up to 15 frames/second, SVGA up to 30 frames, CIF up to 60 frames; Support image compression, that is, output JPEG image data. The specific pin functions are as follows

Pin Name	Pin Type	Pin Description
OV_SCL	enter	The clock line of the SCCB bus is similar to the SCL of I2C.
OV_SDA	I/O	The data line of the SCCB bus is similar to the SDA of I2C.
RESETB	enter	System reset pin, low level is effective
PWDN	enter	Power-down/power-saving mode, high level is effective
HREF	Output	Line sync signal
VSYNC	Output	Frame synchronization signal
PCLK	Output	Pixel synchronization clock output signal
XCLK	enter	External clock input port, can be connected to an external crystal oscillator
D0…D7	Output	Pixel data output port

It is implemented in the driver.

2.2 ESP-LyraT-8311A audio processing function. Realize audio playback/recording, audio signal processing.

The connected functional components are as follows,

Main Components	describe
Expansion board pin header	The pin headers on the other side of the expansion board are used to connect to the female headers on the main board; the female headers on the expansion board are used with other main boards that use pin headers.
Function buttons	Programmable buttons
microphone	Supports electret and MEMS microphones; this expansion board comes with an electret microphone by default
Headphone jack	1/8” headphone jack
Speaker connector	2-pin connector for external speakers
PA	3 W audio signal amplifier for use with external speakers
External microphone matrix connector	(Reserved) External microphone matrix (microphone expansion board) FPC connector
ADC	(Reserved) High-performance ADC/ES7243, including 1 microphone channel, 1 acoustic echo cancellation (AEC) function channel
Mono audio codec	ES8311 audio ADC and DAC, which can convert analog signals picked up by microphones or convert digital signals so that they can be played through speakers or headphones

2.3 ESP-LyraP-TouchA Touch button function, mainly used for audio applications.

Main Components	describe
Mainboard touch FPC connector	Touch FPC connector for connecting the daughterboard to the main board.
Touchpad	Capacitive touch electrodes.
Protection ring	Connect to a touch sensor to trigger an interrupt protection when the development board is exposed to water (water circuit protection). At this time, the sensor array will also be exposed to water, and most (or all) touch pads will be unusable due to a large number of false touches. After receiving this interrupt, the user can decide whether to disable all touch sensors through software.

Use FPC to connect the two FPC connectors. The connection ports correspond to the touch positions.

2.4 ESP-LyraP-LCD32 LCD Image Display Function

Implements a 3.2” LCD graphic display (320 x 240 resolution). The display is connected to the ESP32-S2 via the SPI bus.

The process of connecting the FPC to the expansion board and the expansion board to the main board is realized respectively.

3. As a complete hardware ecosystem, menuconfig is used here to implement configuration, and users do not need to participate too much in the development of basic drivers. This is more convenient for developers for a product with a huge shipment volume. It is close to fool-proof development. The previous post was configured and installed in the Windows environment. Although it was smooth and compiled successfully, using Linux may be the most convenient place for this tool. Then I switched to it.

宋元浩

It is recommended to develop under Linux, which compiles quickly. With vscode, the efficiency is much higher.

北方

Song Yuanhao posted on 2020-8-7 10:28 It is recommended to develop under Linux, which compiles quickly. With vscode, the efficiency is much higher

This system was developed for Linux.

Actually it is not friendly to Windows, but it seems that the driver has been modified. It is being fixed.

宋元浩

Northern published on 2020-8-7 11:13 This system is developed for Linux. In fact, it is not friendly to Windows, but it seems that the driver has been modified. It is being repaired. ...

esp32s2 is a new chip, and currently AT, mpy, and arduino have not made any porting, so it can only be developed by IDF. IDF development is best done under Linux.

北方

Song Yuanhao posted on 2020-8-7 13:21 esp32s2 is a new chip. Currently, AT, mpy, and arduino have not made any porting. It can only be developed in IDF. IDF development is best developed under Linux. ...

There is also a problem with IDF this time. There is a set-target instruction in the document, but I found it was not there when I used it. I used --help and it was indeed not there.

The default setting of this idf is esp32, and I haven't figured out how to set it to esp32s2.

宋元浩

Northern published on 2020-8-7 13:43 This time, there is also a problem with the IDF. There is a set-target command in the document, but it is not found when I use it. I use --help and it is indeed not found. This idf is missing...

Specifically, you need to look at the source code of the idf.py file. Maybe the set-target is not parsed in the window environment, but there is no problem with idf.py set-target esp32s2 in Linux. So the fastest way to develop is to install a Linux distribution in the virtual machine and develop directly in Linux.

okhxyyo

ESP32-S2-Kaluga-1 Review Summary
https://en.eeworld.com/bbs/thread-1134201-1-1.html