FAQ
Q: The computer cannot recognize the COM port when connecting via USB?
A: Press and hold the BOOT button, reconnect the USB cable, and release the BOOT button after powering on.
Q: What is the difference between the onboard UART1 and UART2 interfaces? How should I choose which one to use?
A: Both UART1 and UART2 on the development board actually use the ESP32-S3's UART0 (IO43, IO44). The difference lies in their routing:
- The UART2 interface is directly routed from UART0 to a terminal block, making it convenient to connect external modules using wires.
- The UART1 interface is routed through the onboard CH343 chip for USB-to-serial conversion and connects to the computer via the Type-C port.
- You can switch between UART1 and UART2 using the onboard DIP switch. Slide the switch to the side corresponding to the desired interface.
Q: What is the total thickness of the product?
A: The distance from the bottom of the screen glass to the highest point of the white terminal block is approximately 18.30 mm. Please reserve appropriate space during mechanical design.
Q: The RS485_Test example program can only send data but cannot receive. How can I fix this?
A: RS485 communication issues can sometimes occur due to IDF version problems:
- For ESP-IDF environment: It is recommended to upgrade to v5.5.2.
- For Arduino environment: It is recommended to downgrade the esp32 package version to v3.0.7.
Q: CAN reception fails on the ESP32-S3-Touch-LCD-7B?
A:
- Re-open the COM port in the UCANV2.0.exe software and press the Reset button on the ESP32-S3-Touch-LCD-7B several times.
- Uncheck the "DTR" option in the serial debugging assistant.
Q: After flashing an Arduino program for the RGB screen, the ESP32-S3-Touch-LCD-7B shows no response?
A: If the screen shows no response after flashing the code, please check the configuration in Arduino IDE -> Tools:
- Select Flash Size as 16 MB.
- Enable PSRAM and select 8 MB OPI mode.
Q: Compilation fails or shows errors when flashing the Arduino RGB screen program on the ESP32-S3-Touch-LCD-7B?
A: Check if the required libraries are installed. Please refer to the Library Installation Guide.
Q: The libraries are all installed, but flashing the lvgl program reports an error missing lv_conf.h?
A:
The library installation path may contain Chinese characters, preventing the library files from being found. Also, check if the lv_conf.h file is placed in the Arduino libraries folder.
Q: Why is there no display on the screen after successful Arduino flashing?
A: You can refer to the following steps to run the demo for comparison:
- Before running the program, install the required libraries.
- Install libraries video reference.
- Run and flash the example programs.
Q: When compiling an example in Arduino IDE, I get a fatal error: esp_memory_utils.h: No such file or directory
A: Please install Arduino esp32 version ≥ v3.0.2 to resolve this issue.
Q: Can the CAN communication debugging tool send continuous frames?
A: Yes, you can also customize the frequency of consecutive frames. If the frequency is too high and causes the computer to lag, it may trigger bus errors.
Q: What should I do if flashing with ESP-IDF fails?
A:
- Try setting the development board to download mode. Power off completely, press and hold the Boot button and power it on again, then release it, enter the download mode, re-flash the program, reset and run.
- Try clicking the fullclean button in the status bar and recompile/flash. This function cleans all compiled content, useful when the project compilation reports errors or other operations have polluted the build content.
Q: How to handle not finding the AppData folder?
A: The AppData folder is often hidden by default. You can change the settings to show hidden items:
- File Explorer -> View -> Check "Hidden items"
Q: How to check the COM port?
A:
- Press the Windows + R keys to open the "Run" dialog box, input
devmgmt.mscand press Enter to open the Device Manager; - Expand the "Ports (COM & LPT)" section. All COM ports and their current status will be listed here.
Q: What to do if the first program compilation is extremely slow?
A: It is normal for the first compilation to be very slow. Please be patient and wait for it to complete.
Q: The program flashes successfully, but nothing is shown on the screen. How to solve this?
A: If the development board has a reset button, press it. If there is no reset button, please disconnect and reconnect the power.
Q: When using a MAC device, program flashing fails?
A: Install the MAC driver and then flash again.
Q: How to use SquareLine Studio to design interfaces?
A: Refer to the SquareLine Studio Tutorial.
Q: How to port the provided lib libraries? Or how to develop my own LCD screen? How to drive?
A: The display driver IC for this product is the ST7262, and the touch controller is the GT911. It is recommended to directly refer to the Arduino or ESP-IDF example programs for porting and secondary development.
Q: The compiler cannot find the common folder during compilation?
A: This is likely caused by an inconsistency between old and new IDF versions. Update to the latest IDF version.
Q: The screen appears to 'drift' when reconnecting to Wi-Fi. What should I do?
A: When driving an RGB screen with the ESP32-S3, some early IDF versions have an issue with overall LCD "drift". Recommendations:
- Use ESP-IDF release/v5.1 or later, or the corresponding Arduino-ESP32 version (v3.x or later).
- Refer to the official Espressif LCD FAQ entry regarding "ESP32-S3 driving RGB LCD screen drift" to confirm correct hardware connections, initialization timing, and RGB clock configuration. Detailed explanation can be found here: https://docs.espressif.com/projects/esp-faq/en/latest/software-framework/peripherals/lcd.html#why-do-i-get-drift-overall-drift-of-the-display-when-esp32-s3-is-driving-an-rgb-lcd-screen
Q: How to use LVGL on a board without touch?
A: If you are using a version without touch functionality, or if you temporarily do not need touch input, you can disable touch initialization and input device registration in the main function:
- Locate the touch controller initialization function (e.g., GT911 initialization) and the LVGL input device registration code in the example code.
- Comment out the entire section of code related to touch initialization and input event handling. Only keep the LCD display and LVGL rendering parts.
This will allow the LVGL graphical interface to run normally, but touch interaction will not be supported.