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
Support for TK043F1569 (16 bit parallel RGB mode) #102
Comments
Not being and LCD/LED/display technology expert I am unable to evaluate whether this display can work at all, or not. Can anybody possibly advise on the following questions, it will help us make a decision whether to abort the project and restart with different controllers. Q1. Is it technically feasible to write a display driver to use this controller with the ESP32 DevKit V4 (WROVER-IE) and the Espressif LCDKit v1.1 ? Q2. If possible, can you recommend the optimal starting point (existing driver) to use as foundation for developing an LG4572B driver. Q3. If not, what makes the specific LG4572B controller incompatible with the ESP32 DevKit V4 (WROVER-IE) and the Espressif LCDKit v1.1 ? |
I wonder if the Espressif LCD Kit refered to was this https://github.com/espressif/esp-dev-kits/blob/master/esp32-lcdkit/docs/ESP32_LCDKit_guide_en.md |
@JimNickerson |
@JimNickerson |
I see no mention of the "LG4572 " controller in any of the Espressif examples. |
@JimNickerson |
That controller chip is difficult to find documentation for, I did find this http://www.datasheet.hk/view_download.php?id=2044705&file=0523%5Clg4572b_8093633.pdf |
Correct, I already have the data sheet, it is attached at the bottom of my first post here, below the picture. |
so you have, with that and the example for the other controller used in the Espressif example you can begin to write some code |
Maybe the NT35510 or RM68120 are around to EOL so they changed to other LCD controller chips I guess. The adapter board you bought might not be pin-to-pin to Espressif LCDKit v1.1, better to connect your LCD to ESP32 DevKit with jumper wires. |
I have the same issue, did anybody figured it out? |
@alen1359 no news yet, deadly silence. |
@ammaree @alen1359 TK043F1508: TK043F1569: Update: |
@MH-GoL |
@ammaree Yes, i had a little fight to compile the samplecode in uVision but now its running. |
My key requirements are to use the TK043F1569 displays as purchased, as well as the LCDKIT v1.1. This will enable me to have a stable & reliable dev platform without a bunch of wires. If changing from the current ESP32-DevKitCV[I/IE] to an ESP32-S3 based DevKit, provided it will work with the LCDKIT v1.1, I will be happy to change the devkit. Will a devkit change make the TK043F1569 and LCDKIT v1.1 combination work, if so where can I find a compatible devkit? |
@ammaree It is not possible to run the the TK043F1569 only using the pin header, you need to connect a cable to the connector for DE, PCLK, HSYNC and VSYNC. This is due to the fact that this board is also used for other displays. The only way to change this is to create a custom Board. I have the plan to create a Board with a ESP32-S3-WROOM1 on it were the LCD and CT are directly connected to but right now there is no time for this project. |
Thanks for the feedback, sadly the money is wasted on 2 high spec but unusable displays. |
Problem Description
I recently purchased 2x displays with adapters to use with the ESP32 DevKit V4 (WROVER-IE) and the Espressif LCDKit v1.1
Based on advice from EspressIf (TK043F1508 ) and from users (link below) I ordered what I thought was the correct module.
#89 (comment)
I purchased the display modules from the following link:
https://buy.tbfocus.com/item.php?id=560872117142#3512775208514
Upon receiving the modules I find that the pins are (slightly different) but more important that the controller has changed from NT35510 or RM68120 to LG4572
Expected Behavior
Any chance to get a driver adapted to support the LG4572 when used together with the DevKit and LCDKit mentioned above?
Photo of modules I purchased:
Datasheet of controller:
Datasheet.hk_lg4572b_8093633.pdf
The text was updated successfully, but these errors were encountered: