-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ST77903_QSPI_1_6_400_400 DEMO QSPI Doesn't seem to be working properly (AEGHB-624) #92
Comments
Hi @ckls, the component |
thanks, I also tried switching commit in master and adding patch, but failed while adding patch, and tried using this demo on the master's latest commit |
esp_lcd_st77903_qspi.zip |
sorry,I can't set-Target for this demo, i want to set this demo to esp32s3,but something went wrong. i can't compile this demo properly either |
Hello, this is not a demo, but a driver component. You need to replace the component in your project. |
I created a routine based on sip_lcd_touch and this component. As a result, as I encountered before, QSPI did not work normally. I uploaded my engineering file. This is my SCLK and CS waveforms. |
project-name-1.zip |
I have used the routine you have modified, and it is still the same problem. I think there are any other configurations that affect the work of this part of the pin. |
That would require you to inspect your hardware, as this portion of the code has already been successfully executed and tested on my development board without any issues. |
I just modified the settings of the PSRAM section and modified it to QSPI |
Perhaps your screen's initialization parameters differ from the defaults. You need to confirm your screen's initialization parameters. |
The screen initialization part, I also tried provided by the manufacturer, but my data does not seem to communicate on the screen |
The driver component has been tested, and just now I successfully ran your code on the development board, and everything is working fine. As for your pin issue, it seems there's a problem from the waveform, but the pin sequence appears to be normal. Therefore, I suggest you check your hardware and related configurations. |
Thank you, I found that there is indeed a hardware problem. The schematic diagram is inconsistent with the PCB. This code has been running normally on my hardware. |
Hello, what specific function are you using the TE pin for? You can use this pin in GPIO interrupts. |
Answers checklist.
General issue report
ST77903_QSPI_1_6_400_400 demo
ESP-IDF:master
chip:esp32S3R2
These pin definitions have been modified
#if CONFIG_IDF_TARGET_ESP32S3
/* ESP32-S3 */
#define LCD_SPI_CS (GPIO_NUM_16)
#define LCD_SPI_SCK (GPIO_NUM_17)
#define LCD_SPI_D0 (GPIO_NUM_13)
#define LCD_SPI_D1 (GPIO_NUM_12)
#define LCD_SPI_D2 (GPIO_NUM_11)
#define LCD_SPI_D3 (GPIO_NUM_10)
#define LCD_BACKLED (GPIO_NUM_20)
#endif
#define LCD_RST (GPIO_NUM_14)
I modified these areas to make the code compile and work properly
Phenomenon: Spi Clk pin frequency does not match the set of 40MHz, the Logic analyzer capture only 10MHz, set other frequencies, CLK pin frequency is always only a quarter of the set value, Cs pin does not seem to work properly.
Help: esp-idf need to make what additional settings can make this part of the code work, the screen can not be normal communication brush color bar
Bonus: When I used the GPIO 19 and GPIO 20 pins, configured as a GPIO port, or as an API configured with SPI pins, it seemed like these two pins were still running as USB D + and USB D-, what additional configuration is required
The text was updated successfully, but these errors were encountered: