You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I recently bought 2.8 IPS display module with ILI9341V chip (like this one http://www.lcdwiki.com/2.8inch_IPS_SPI_Module_ILI9341). The standard esp_lcd_ili9341 driver refused to drive this display. So, I figured out that the difference is in initialization sequence. Here is the code snippet of vendor_specific_init array to make this module working. It will be good it this will be integrated in the esp_lcd_ili9341 driver (probably through Kconfig with ability to select chip).
Hi @valkuc , thanks for your information! The issue you mentioned exists in all LCD drivers because even if the driver IC model is the same, different screens often require configuration with initialization commands provided by the manufacturers.
Fortunately, I've submitted a new PR that allows drivers to obtain initialization commands externally, eliminating the need to modify the code within the driver.
Hi. I recently bought 2.8 IPS display module with ILI9341V chip (like this one http://www.lcdwiki.com/2.8inch_IPS_SPI_Module_ILI9341). The standard
esp_lcd_ili9341
driver refused to drive this display. So, I figured out that the difference is in initialization sequence. Here is the code snippet ofvendor_specific_init
array to make this module working. It will be good it this will be integrated in theesp_lcd_ili9341
driver (probably through Kconfig with ability to select chip).The text was updated successfully, but these errors were encountered: