Hardware connection

• Connect the board to the computer using a USB cable

Code analysis

• adc_bsp_init(void): Initializes ADC1, including creating an ADC one-time trigger unit and configuring channel 0 for ADC1.
• adc_get_value(float *value,int *data): Reads the value of ADC1 channel 0 and calculates the corresponding voltage value based on the reference voltage and resolution, stores it at the position where the incoming pointer points to, and stores 0 if the read fails.
• adc_example(void* parmeter): After initializing the ADC, in an infinite loop, read the value of the ADC channel on GPIO1, print the original ADC value, and calculate the system voltage value, performing this operation once every second.

Result demonstration

• Open the serial port monitoring, you can see the ADC value and voltage in the printed output, as shown in the following figure:
  

• The ADC sampling value is around 2518, and the actual voltage is greater than 3.3V, which is due to the voltage boost through the battery chip. For a detailed analysis, you can refer to the schematic diagram

Hardware connection

• Connect the board to the computer using a USB cable

Code analysis

• qmi8658c_example(void* parmeter): The function initializes the QMI8658 device, reading and printing accelerometer data, gyroscope data, and temperature data in an infinite loop, once every second. During the rotation of the board, the gyroscope data increases with greater rotation speed, and the accelerometer calculates the corresponding acceleration based on the current position.

Result demonstration

• Open the serial port monitoring, and you can see the original data output from the IMU (Euler angles need to be converted by yourself), as shown in the following figure:
  

• Data is output once every second. If you need to modify or refer to it, you can directly access the qmi source file for operations.

Hardware connection

• Connect the board to the computer using a USB cable

Code analysis

For LVGL, lvgl_conf.h is its configuration file, and below are explanations for some commonly used contents.

/*Color depth: 1 (1 byte per pixel), 8 (RGB332), 16 (RGB565), 32 (ARGB8888)*/
#define LV_COLOR_DEPTH 16//Color depth, a macro definition that must be concerned with porting LVGL


#define LV_MEM_CUSTOM 0
#if LV_MEM_CUSTOM == 0
    /*Size of the memory available for `lv_mem_alloc()` in bytes (>= 2kB)*/
    #define LV_MEM_SIZE (48U * 1024U)          /*[bytes]*/

    /*Set an address for the memory pool instead of allocating it as a normal array. Can be in external SRAM too.*/
    #define LV_MEM_ADR 0     /*0: unused*/
    /*Instead of an address give a memory allocator that will be called to get a memory pool for LVGL. E.g. my_malloc*/
    #if LV_MEM_ADR == 0
        #undef LV_MEM_POOL_INCLUDE
        #undef LV_MEM_POOL_ALLOC
    #endif

#else       /*LV_MEM_CUSTOM*/
    #define LV_MEM_CUSTOM_INCLUDE <stdlib.h>   /*Header for the dynamic memory function*/
    #define LV_MEM_CUSTOM_ALLOC   malloc
    #define LV_MEM_CUSTOM_FREE    free
    #define LV_MEM_CUSTOM_REALLOC realloc
#endif     /*LV_MEM_CUSTOM*/
//The above section is mainly for LVGL memory allocation, 
//which defaults to lv_mem_alloc() versus lv_mem_free().

There are also some LVGL demos and file systems that can be set in the conf configuration file.

Code modification

• For boards without touch, you need to find EXAMPLE_USE_TOUCH in the file where the main function is located, and change 1 to 0
• For boards with touch, you need to find EXAMPLE_USE_TOUCH in the file where the main function is located, and change 0 to 1

#define EXAMPLE_USE_TOUCH               0

Result demonstration

The LVGL demo has high requirements for RAM and ROM, so it is necessary to configure the demo according to the requirements of environment setup, and after the program is flashed, the running effect of the device is as follows (if it is a board with touch, you need to modify the macro definition EXAMPLE_USE_TOUCH to 1):

Hardware connection

• Install a TF card on the board (you must insert a TF card with a capacity of less than 64G first), and use a USB cable to connect the board to the computer (if it is a V1 board, you need to comment out the macro definition VersionControl_V2, which is enabled by default)

Code analysis

• SD_card_Init(void): This function initializes the TF card according to different configurations, including configuring the mounting parameters, host and card slot parameters, and then tries to mount the TF card, if successful, the card information and capacity are printed.

Result demonstration

• Click on the serial port monitoring device, you can see the information of the output TF card, practical_size is the actual capacity of the TF card, as shown in the figure below:
  

Hardware connection

• Connect the board to the computer using a USB cable

Code modification

The project realizes that the chip is connected to WIFI in STA mode and obtains the IP address, before compiling and downloading the firmware, some code needs to be modified, specifically changing the name and password of the WIFI router to those suitable for the environment.

Code analysis

• wifi_init(void): This function is used to initialize the Wi-Fi connection of the ESP32. It sets the ESP32 to Wi-Fi site mode and tries to connect to the specified Wi-Fi network (via the ssid and password). If the connection is successful, it prints the local IP address; if the connection fails within a certain period (20 * 500 milliseconds), it prints the connection failure message. At the same time, the function can also set the auto-connection and auto-reconnect functions.

Result demonstration

• The chip is successfully connected to WIFI in STA mode, and you can see the obtained IP address by clicking on the serial port monitoring device.
  

Hardware connection

• Connect the board to the computer using a USB cable

Code analysis

• The code initializes serial communication on the ESP32 and then creates a WiFi access point named "bsp_esp_demo" with the password "waveshare", and no other continuous operations are performed in a loop while the program runs.

const char* ssid     = "bsp_esp_demo";
const char* password = "waveshare"; 

WiFi.softAP(ssid,password);

Result demonstration

• Use your mobile phone or other device to connect to WIFI, the WiFi name is "bsp_esp_demo", and the password is "waveshare"
  

• We also provide some playable demos for your reference, but it should be noted that the following demos are based on ESP32_Arduino versions below V3.0. Environment setup can be referred to below
  • Install the 2.0.9 environment directly by downloading the Arduino2.0.9 offline package, double-click to install it after the download is completed
  • Click to download the required library files, the library file is installed in the same way as the Arduino library file installation above
  • You can click ESP32-S3-AMOLED-1.91-Arduino_Playablity to download the demo

Hardware connection

• Connect the board to the computer using a USB cable

Result demonstration

Hardware connection

• Connect the board to the computer using a USB cable

Code analysis

• qmi8658c_example(void* parmeter): The function initializes the QMI8658 device, reading and printing accelerometer data, gyroscope data, and temperature data in an infinite loop, once every second.

Result demonstration

After the demo is flashed, the running result of the device is as follows:

• Open the serial port monitoring, and you can see the original data output from the IMU (Euler angles need to be converted by yourself), as shown in the following figure:
  

• You can see that it is output every 1 second. If you need to modify or refer to it, you can directly go to the qmi source file to modify it

Hardware connection

• Connect the board to the computer using a USB cable

Code analysis

• There are two projects in the LVGL catalog, one is the original display, and the other is the 90-degree rotation display, which can be selected according to your needs.
  
• The original display and the 90-degree rotation display are mainly different from two points:

① and ②: There is a difference in the number of pixels in the horizontal and vertical directions
③ and ④: The register at the 0x36 address under the lcd_init_cmds array is responsible for rotation, and modifying its value can achieve a rotation effect. If no rotation is needed, you can directly delete {0x36,(uint8_t []){0xF0,1,0}}

Code modification

• For boards without touch, you need to find EXAMPLE_USE_TOUCH in the file where the main function is located, and change 1 to 0
• For boards with touch, you need to find EXAMPLE_USE_TOUCH in the file where the main function is located, and change 0 to 1

#define EXAMPLE_USE_TOUCH               0

Result demonstration

Hardware connection

• Install a TF card on the board (you must insert a TF card with a capacity of less than 64G first), and use a USB cable to connect the board to the computer (if it is a V1 board, you need to comment out the macro definition VersionControl_V2 in sd_card_bsp.c, which is enabled by default)

Code analysis

• SD_card_Init(void): This function initializes the TF card according to different configurations, including configuring the mounting parameters, host and card slot parameters, and then tries to mount the TF card, if successful, the card information and capacity are printed.

Result demonstration

• You can see the output TF card information
  

Hardware connection

• Connect the board to the computer using a USB cable

Code analysis

• espwifi_Init(void): This function is used for WiFi initialization on ESP32. It sequentially initializes non-volatile storage, the TCP/IP stack, creates a default event loop and a default WiFi site network interface, initializes WiFi with the default configuration, registers event handlers to handle WiFi and IP-related events, sets WiFi connection parameters, and starts WiFi.

Code modification

The project realizes that the chip is connected to WIFI in STA mode and obtains the IP address, before compiling and downloading the firmware, some code needs to be modified, specifically changing the name and password of the WIFI router to those suitable for the environment.

Result demonstration

After the demo is flashed, the running result of the device is as follows:

* The chip successfully connects to WIFI and obtains an IP address while in STA mode. 

Hardware connection

• Connect the board to the computer using a USB cable

Code analysis

• wifi_init_softap(void): This function is used to initialize the ESP32's Wi-Fi soft access point, including setting up the network interface, registering event handling functions, configuring soft AP parameters, and starting the soft AP.

Result demonstration

• When the chip is in AP mode, use the mobile phone to successfully connect to WIFI and the serial port will print the MACA address of the connected device and the IP address assigned to the device.
  

Hardware connection

• Use a USB cable to connect the board to the computer (if it is a V1 version, you need to comment out the CMake statement target_compile_definitions which is enabled by default in the CMakeLists.txt file under the ui_bsp directory)

Code modification

• For boards without touch, you need to find EXAMPLE_USE_TOUCH in the file where the main function is located, and change 1 to 0
• For boards with touch, you need to find EXAMPLE_USE_TOUCH in the file where the main function is located, and change 0 to 1

#define EXAMPLE_USE_TOUCH               0

Result demonstration

• The touch version supports BOOT button and touch switching
• Switch pages by using the BOOT button on the side of the board to display the analog clock interface first
  

• Switch to the Argument interface by pressing the BOOT button, where you can see a page with information on the onboard hardware
  

• Click the BOOT button again to jump to the Touch interface, which is the component interface
  

• Click the BOOT button again to jump to the WIFI interface