240x320 spi tft lcd to rasberry pi brands
※Price Increase NotificationThe TFT glass cell makers such as Tianma,Hanstar,BOE,Innolux has reduced or stopped the production of small and medium-sized tft glass cell from August-2020 due to the low profit and focus on the size of LCD TV,Tablet PC and Smart Phone .It results the glass cell price in the market is extremely high,and the same situation happens in IC industry.We deeply regret that rapidly rising costs for glass cell and controller IC necessitate our raising the price of tft display.We have made every attempt to avoid the increase, we could accept no profit from the beginning,but the price is going up frequently ,we"re now losing a lot of money. We have no choice if we want to survive. There is no certain answer for when the price would go back to the normal.We guess it will take at least 6 months until these glass cell and semiconductor manufacturing companies recover the production schedule. (Mar-03-2021)
All the accessories listed below tier pricing need to pay.We won"t deliver until you select. Power adaptor should be 5V/2000mA in output and center pin for positive voltage and the outer shield for negative voltage .The temperature for controller RTD2660 would increase during working.That"s normal phenomenon,not quality problem.
ER-TFTV050A1-1 is 480x272 dots 5" color tft lcd module display with small HDMI signal driver board,optional capacitive touch panel with USB controller board and cable and 4-wire resistive touch panel with USB driver board and cable, optional remote control,superior display quality,super wide view angle.It can be used in any embedded systems,car,industrial device,security and hand-held equipment which requires display in high quality and colorful video. It"s also ideal for Raspberry PI by HDMI.
I just finished two solid days of work trying to get an HDMI LCD panel working with one of the inexpensive older model TFT LCD displays in a "Dual mode" configuration. There was a tremendous amount of help from this post, which got me most of the way there, but the infamous "last mile" still took me a while. I"m leaving some breadcrumbs here, as well as asking the group if anyone knows of a better way.
I am working on a device that uses a Raspberry Pi 4 as an embedded controller. For output, I need an 2K DSI LCD w/ its own HDMI adapter (Sharp LS055R1SX04, about $65 USD), as well as an inexpensive TFT LCD used for a basic touch user interface. The TFT LCD, which uses an ILI9341 LCD controller and an ads7846 touchscreen controller, can be had for about $10 USD. The Pi was flashed with the latest Raspberry Pi OS 32 bit then updated, so everything is current as of this writing (March 2021).
Initial configuration of the display worked with little issue. The HDMI adapter for the Sharp LCD works at 50 Hz only, so it requires custom timings. The TFT LCD uses the same controller chips as the original 3.5" Raspberry Pi LCD, so I was able to activate it with the rpi-display dtoverlay.
Booting with the above correctly revealed two framebuffer devices listed with ls -l /dev/fb*. The display initially showed as all white, then went all black, indicating correct initialization. However, when starting the desktop GUI, only the Sharp LCD showed any contents, and only it was listed as a device by xrandr.
The relevant X11 configuration files are located in /usr/share/X11/xorg.conf.d. The reference forum post mentioned replacing the contents of the file 99-fbturbo.conf. My first problem that took way to long to discover: 99-fbturbo.conf gets automatically deleted if the vc4-fkms-v3d overlay is activated (which is the default for a RasPi4). So, the configuration would work fine, but would suddenly stop working if the Pi is rebooted!
The above configuration seems to work well. Both displays showed data. VNC showed a single combined desktop. Moving a window from left to right moved to the appropriate display as expected by the Option "Xinerama" "true" option of the server layout.
Based on claims of the above not being "ideal", I experimented with various settings. If the above file is deleted entirely, xrandr reports the Sharp LCD as the sole display. If you put the above file in place, and remove all references to the Sharp LCD (including the Device, Monitor, Screen, and ServerLayouts), xrandr correctly reports the TFT LCD, but not the Sharp LCD. I left JUST the Device sections in, but xrandr failed to correctly report one of the other.
No matter what combinations I tried, I was unable to get xrandr to list both the HDMI display and the SPI display at the same time. If all parts above ARE explicitly listed in the configuration, running xrandr reports an error that the RandR extension is not loaded. Thus I was unable to use the more advanced built in layout management of X11 using the RandR extension.
Simply using raspi-config"s System Options to boot to the Desktop works as expected, as my X11 configuration changed the last option in the "ServerFlags" section to:
Since xrandr was INOP in this configuration, I could not use xinput --map-to-output to limit touchscreen coordinates to the TFT LCD. Instead, I settled on using a combination of touch screen rotation, and input coordinate translation:
Note that the TransformationMatrix is very specific to a 1440x2560 in portrait mode with 320x240 in landscape mode to the right of the Sharp LCD. The numbers are basically:
You may be tempted to try to hack a dtoverlay that uses the ads7846 driver and specifies the x-min, x-max, etc. parameters. Don"t. I wasted a huge amount of time on this. While you can specify min/max, they apparently do NOT affect the output of that driver. The raw numbers are still reported when watching X11 input events via sudo DISPLAY=:0.0 evtest /dev/input/event0 no matter what the min/max parameters to that driver are.
The reference post noted that you can"t change the background color or image of the small display with this configuration. While that is true using the GUI, those configuration options are stored in the following files:
My question to the group, if anyone knows, is simple: is it possible to configure a Pi4 so an SPI connected LCD can co-exist without disabling the RandR extension in X11?
My question to the group, if anyone knows, is simple: is it possible to configure a Pi4 so an SPI connected LCD can co-exist without disabling the RandR extension in X11?
Xserver wants to talk to either DRM/KMS for all rendering, or goes to /dev/fbX nodes if there is no DRM/KMS available (and then Xinerama is required to support multiple displays).
With DRM/KMS X will render one "super desktop" covering all displays in their correct positions, and then tell each DRM/KMS device to display the correct bit of it. That"s how it works with dual HDMI on Pi4.
Now these SPI displays used to be driven by a driver that only exposed them as /dev/fbX nodes. They now appear to be under the tinydrm driver, so I would have expected them to show up as DRM/KMS devices. The output from modetest would be interesting to see (X can not be running when you run modetest). "xrandr --verbose" may tell you if you have vc4-(f)kms-v3d enabled. (Sorry, I don"t have one of these displays to test with)
If it is a DRM device, then I would expect X to be able to render to that as an alternate output device, providing it supports a suitable pixel format.
That is how I believe things work if you were to drop 2 different graphics cards into an x86 PC - one does all the rendering through OpenGL, and then they each get told which bits of the resultant image to display.
So, "TinyDRM" is new to me. Of all the extensive google searches I did, I never came across this. Adding "tinydrm" to my previous searches has revealed a lot of new information to explore. So far, this is what I have uncovered:
As I mentioned in my initial post, what "works" for me is the "rpi-display" overlay. If I execute fdtdump /boot/overlays/rpi-display.dtbo on my current configuration, I see this fragement:
I"m not real familiar with this stuff (I stumbled across it while I was stuck in the mud), but I assume by these results that there are two different drivers possible: fb_ili9341 which is the framebuffer version, and ili9341 which I assume is the DRM version. If I understand how this all fits together, it appears that when I select the "rpi-display" overlay, its picking the framebuffer version due to the last line in modules.alias?
Adding "tinydrm" to my google searches revealed this Github issue: https://github.com/notro/tinydrm/issues/14, and it mentions in passing "here is an example overlay source file", pointing to the rpi-display overlay. However, when I look at the referenced source, https://github.com/notro/tinydrm/blob/m ... verlay.dts, it contains this:
which is of course a different driver. I already had a customized overlay source, so I changed it to use the mentioned "mi0283qt" driver. It did not work (my screen remains blank white). I also tried the straight ili9341 driver (with no "fb_" prefix). Both showed results from modetest, but the screen remained white.
I suspect that perhaps my pins may not be set up correctly for those drivers? The overlay sources seemed to indicate they were the same, but I don"t know if that is true.
I"m not sure if I uncovered an inconsistency in what is supposed to be in the distribution, or if in order to get this to work, I need to download and compile the drivers? I"ll keep experimenting, but I wanted to report what I found thus far.
I do note that the mi0283qt driver also appears to be a 320x240 ILI934 based panel from looking at the source. That"s also the compatible ("multi-inno,mi0283qt") referenced by notro in https://github.com/notro/tinydrm/issues/14 (different vendor prefix though). It"d be nice to know the differences.
Is it fair to say that there is more to a board than just saying it"s controlled by a an ILS9341? That seems to be the case with these multiple initialization sequences. I believe my board to be one from HiLetgo. Is it possible to create a DRM driver that functions EXACTLY like the fb_ili9341? Another possibility: for $10 USD, I could just get another board. That certainly might be easier. I"d just like to know the best way to match a board to a driver. The "brand name" ADAfruit board is $27 - almost 3 x the cost of the Hiletgo. Not super significant for a one-off, but a significant increase in unit cost.
Switching to the "multi-inno,mi0283qt" compatible and I get nothing. Reading the DT bindings, the backlight has been moved from being a GPIO property of the display to being a link to the backlight device driver, so it"s understandable that the backlight stays off.
Hmm, my x86 system (Ubuntu 20.10 with 5.8 kernel) seems quite happy to share the desktop between two graphics cards (one Radeon 6450 (XFX 6450 HD-645-ZQ 1GB), and one Nvidia Geforce GT710).
On my CM4 xrandr didn"t even list the extra SPI display, whereas on x86 it is listing all the connected and disconnected displays (7 of them total!). On both systems they show up under /sys/class/drm, so it may be the way that X enumerates the displays.
So, I tried the dtoverlay you posted, and sure enough - I was also able to get a test pattern using modetest! So, that explains part 1 - the pinout is different on some of these displays.
Next, I removed my previous 99-multihead-conf file from my "/usr/share/X11/xorg.conf.d/" and restarted the desktop manager. I opened a terminal window, entered "xrandr", and both displays listed! I thought it was solved, but at that point, my poor little Pi completely locked up. I had this same problem in the past when I was trying the various DRM driver overlays. The desktop just became very unstable.
At this point, I"m going to just fall back to the configuration I posted at the beginning of this first thread. It seems to work fine. And while it may in theory not be ideal, it works for my purposes (I"m creating a very basic touch UI on the touchscreen. I"m not trying to stream video to it or anything crazy).
Strange that the SPI display showed up for you but not me, even if it did then crash. I"ve tried an upgrade of my RaspiOS 32bit install (although with latest kernel) and it still doesn"t want to acknowledge the SPI display through xrandr. Could you post the output from xrandr when it sees both displays?
is needed for xrandr to see the display (listed as Unknown19-1 for me, presumably as X hasn"t been built with any knowledge of DRM_MODE_CONNECTOR_SPI being 19. https://elixir.bootlin.com/linux/latest ... ode.h#L390
However it is as I suspected - we have no mouse pointer on the TFT screen, presumably as X can"t cope with one display having a cursor plane and the other not. I don"t know the best way to overcome that.
*edit*: Minor correction there. If the two displays overlap, then the mouse cursor disappears on the SPI screen. If you set them to be independent (eg "xrandr --output Unknown19-1 --right-of HDMI-1"), then X switches mode and renders the mouse cursor.
Which sounds like yours (i.e the "Unknown19-1). I got the "lock up" again, but it turns out that lock-up was actually VNC (I"ve been using that to develop, as the text on a Sharp LCD is VERY tiny to look at in desktop mode). My console was still alive, so I hooked up an actual keyboard and mouse to the Pi, and the desktop on my Sharp LCD came alive. With the above two commands you"ve discovered, I now have two desktops. Sort of...
It appears as if the upper left hand corner of my Sharp LCD desktop is mirrored on the small LCD. It"s not two independent desktops. Instead, it"s the same desktop duplicated. I suspect that is probably more X configuration than driver stuff, however.
It appears as if the upper left hand corner of my Sharp LCD desktop is mirrored on the small LCD. It"s not two independent desktops. Instead, it"s the same desktop duplicated. I suspect that is probably more X configuration than driver stuff, however.
New: A brand-new, unused, unopened, undamaged item in its original packaging (where packaging is applicable). Packaging should be the same as what is found in a retail store, unless the item was packaged by the manufacturer in non-retail packaging, such as an unprinted box or plastic bag. See the seller"s listing for full details.See all condition definitionsopens in a new window or tab
The new Raspberry Pi Pico development board isn’t just exciting because it is affordable and capable; it is also exciting because it is based on a brand-new microcontroller, the RP2040, that Raspberry Pi designed themselves. That is unusual, as most development boards, including every board in the Arduino lineup, utilize existing microcontrollers. The RP2040 is a very capable and feature-packed microcontroller, but the downside of using a completely new design like this is that hardware support is somewhat lacking. If you’re using an Arduino, there are libraries available for most popular hardware. In order todrive an ILI9341 display with their Raspberry Pi Pico, Redditor JermMX5 had to develop their own library.
The ILI9341 is a very popular display driver that you’ll find in many smaller TFT LCD screens. If your TFT LCD is somewhere between 2”-3.5” and accepts SPI input, there is a very good chance that it is driven by an ILI9341. Because the ILI9341 is so popular, there are many libraries out there that you can take advantage of if you’re using an Arduino or another established development board. While both Arduino boards and the new Raspberry Pi Pico can be programmed in a combination of C and C++, there are differences that prevent you from simply using an Arduino library with your Pico. But if you know what you’re doing, you can adapt those libraries to make them work. JermMX5 did that and improved the frame buffer while they were at it.
When drivinga display, the frame buffer is a portion of the RAM that is used to store all of the data for the pixels that will be sent to the screen the next time it is updated. Because Arduino boards like the UNO have a relatively small amount of RAM, the existing ILI9341 libraries have a frame buffer that breaks the screen up into small sections. Each time the display is updated, only one portion of the screen is actually changed. That results in flickering that looks pretty bad. Fortunately, the Raspberry Pi Pico’s RP2040 has a generous 264KB of RAM. That is more than enough for the frame buffer to contain the entire screen so it can be updated all at once, eliminating flickering. The frame buffer uses a total of 153KB of RAM, so there is plenty left over for the other tasks. JermMX5 plans to use this for a Game Boyemulatorin the future, but we hope they release this ILI9341 library for the Raspberry Pi Pico soon so that we can all take advantage of it.
5.We maintain high standards of excellence and strive for 100% customer satisfaction. Feedback is very important,We hope you can contact us immediately before you give us neutral or negative feedback.
6.If you have any questions, our Customer Service staffs welcome you to email or call us. We strive to answer all questions and resolve any problems as quickly as possible
I just finished two solid days of work trying to get an HDMI LCD panel working with one of the inexpensive older model TFT LCD displays in a "Dual mode" configuration. There was a tremendous amount of help from this post, which got me most of the way there, but the infamous "last mile" still took me a while. I"m leaving some breadcrumbs here, as well as asking the group if anyone knows of a better way.
I am working on a device that uses a Raspberry Pi 4 as an embedded controller. For output, I need an 2K DSI LCD w/ its own HDMI adapter (Sharp LS055R1SX04, about $65 USD), as well as an inexpensive TFT LCD used for a basic touch user interface. The TFT LCD, which uses an ILI9341 LCD controller and an ads7846 touchscreen controller, can be had for about $10 USD. The Pi was flashed with the latest Raspberry Pi OS 32 bit then updated, so everything is current as of this writing (March 2021).
Initial configuration of the display worked with little issue. The HDMI adapter for the Sharp LCD works at 50 Hz only, so it requires custom timings. The TFT LCD uses the same controller chips as the original 3.5" Raspberry Pi LCD, so I was able to activate it with the rpi-display dtoverlay.
Booting with the above correctly revealed two framebuffer devices listed with ls -l /dev/fb*. The display initially showed as all white, then went all black, indicating correct initialization. However, when starting the desktop GUI, only the Sharp LCD showed any contents, and only it was listed as a device by xrandr.
The relevant X11 configuration files are located in /usr/share/X11/xorg.conf.d. The reference forum post mentioned replacing the contents of the file 99-fbturbo.conf. My first problem that took way to long to discover: 99-fbturbo.conf gets automatically deleted if the vc4-fkms-v3d overlay is activated (which is the default for a RasPi4). So, the configuration would work fine, but would suddenly stop working if the Pi is rebooted!
The above configuration seems to work well. Both displays showed data. VNC showed a single combined desktop. Moving a window from left to right moved to the appropriate display as expected by the Option "Xinerama" "true" option of the server layout.
Based on claims of the above not being "ideal", I experimented with various settings. If the above file is deleted entirely, xrandr reports the Sharp LCD as the sole display. If you put the above file in place, and remove all references to the Sharp LCD (including the Device, Monitor, Screen, and ServerLayouts), xrandr correctly reports the TFT LCD, but not the Sharp LCD. I left JUST the Device sections in, but xrandr failed to correctly report one of the other.
No matter what combinations I tried, I was unable to get xrandr to list both the HDMI display and the SPI display at the same time. If all parts above ARE explicitly listed in the configuration, running xrandr reports an error that the RandR extension is not loaded. Thus I was unable to use the more advanced built in layout management of X11 using the RandR extension.
Simply using raspi-config"s System Options to boot to the Desktop works as expected, as my X11 configuration changed the last option in the "ServerFlags" section to:
Since xrandr was INOP in this configuration, I could not use xinput --map-to-output to limit touchscreen coordinates to the TFT LCD. Instead, I settled on using a combination of touch screen rotation, and input coordinate translation:
Note that the TransformationMatrix is very specific to a 1440x2560 in portrait mode with 320x240 in landscape mode to the right of the Sharp LCD. The numbers are basically:
You may be tempted to try to hack a dtoverlay that uses the ads7846 driver and specifies the x-min, x-max, etc. parameters. Don"t. I wasted a huge amount of time on this. While you can specify min/max, they apparently do NOT affect the output of that driver. The raw numbers are still reported when watching X11 input events via sudo DISPLAY=:0.0 evtest /dev/input/event0 no matter what the min/max parameters to that driver are.
The reference post noted that you can"t change the background color or image of the small display with this configuration. While that is true using the GUI, those configuration options are stored in the following files:
My question to the group, if anyone knows, is simple: is it possible to configure a Pi4 so an SPI connected LCD can co-exist without disabling the RandR extension in X11?
My question to the group, if anyone knows, is simple: is it possible to configure a Pi4 so an SPI connected LCD can co-exist without disabling the RandR extension in X11?
Xserver wants to talk to either DRM/KMS for all rendering, or goes to /dev/fbX nodes if there is no DRM/KMS available (and then Xinerama is required to support multiple displays).
With DRM/KMS X will render one "super desktop" covering all displays in their correct positions, and then tell each DRM/KMS device to display the correct bit of it. That"s how it works with dual HDMI on Pi4.
Now these SPI displays used to be driven by a driver that only exposed them as /dev/fbX nodes. They now appear to be under the tinydrm driver, so I would have expected them to show up as DRM/KMS devices. The output from modetest would be interesting to see (X can not be running when you run modetest). "xrandr --verbose" may tell you if you have vc4-(f)kms-v3d enabled. (Sorry, I don"t have one of these displays to test with)
If it is a DRM device, then I would expect X to be able to render to that as an alternate output device, providing it supports a suitable pixel format.
That is how I believe things work if you were to drop 2 different graphics cards into an x86 PC - one does all the rendering through OpenGL, and then they each get told which bits of the resultant image to display.
So, "TinyDRM" is new to me. Of all the extensive google searches I did, I never came across this. Adding "tinydrm" to my previous searches has revealed a lot of new information to explore. So far, this is what I have uncovered:
As I mentioned in my initial post, what "works" for me is the "rpi-display" overlay. If I execute fdtdump /boot/overlays/rpi-display.dtbo on my current configuration, I see this fragement:
I"m not real familiar with this stuff (I stumbled across it while I was stuck in the mud), but I assume by these results that there are two different drivers possible: fb_ili9341 which is the framebuffer version, and ili9341 which I assume is the DRM version. If I understand how this all fits together, it appears that when I select the "rpi-display" overlay, its picking the framebuffer version due to the last line in modules.alias?
Adding "tinydrm" to my google searches revealed this Github issue: https://github.com/notro/tinydrm/issues/14, and it mentions in passing "here is an example overlay source file", pointing to the rpi-display overlay. However, when I look at the referenced source, https://github.com/notro/tinydrm/blob/m ... verlay.dts, it contains this:
which is of course a different driver. I already had a customized overlay source, so I changed it to use the mentioned "mi0283qt" driver. It did not work (my screen remains blank white). I also tried the straight ili9341 driver (with no "fb_" prefix). Both showed results from modetest, but the screen remained white.
I suspect that perhaps my pins may not be set up correctly for those drivers? The overlay sources seemed to indicate they were the same, but I don"t know if that is true.
I"m not sure if I uncovered an inconsistency in what is supposed to be in the distribution, or if in order to get this to work, I need to download and compile the drivers? I"ll keep experimenting, but I wanted to report what I found thus far.
I do note that the mi0283qt driver also appears to be a 320x240 ILI934 based panel from looking at the source. That"s also the compatible ("multi-inno,mi0283qt") referenced by notro in https://github.com/notro/tinydrm/issues/14 (different vendor prefix though). It"d be nice to know the differences.
Is it fair to say that there is more to a board than just saying it"s controlled by a an ILS9341? That seems to be the case with these multiple initialization sequences. I believe my board to be one from HiLetgo. Is it possible to create a DRM driver that functions EXACTLY like the fb_ili9341? Another possibility: for $10 USD, I could just get another board. That certainly might be easier. I"d just like to know the best way to match a board to a driver. The "brand name" ADAfruit board is $27 - almost 3 x the cost of the Hiletgo. Not super significant for a one-off, but a significant increase in unit cost.
Switching to the "multi-inno,mi0283qt" compatible and I get nothing. Reading the DT bindings, the backlight has been moved from being a GPIO property of the display to being a link to the backlight device driver, so it"s understandable that the backlight stays off.
Hmm, my x86 system (Ubuntu 20.10 with 5.8 kernel) seems quite happy to share the desktop between two graphics cards (one Radeon 6450 (XFX 6450 HD-645-ZQ 1GB), and one Nvidia Geforce GT710).
On my CM4 xrandr didn"t even list the extra SPI display, whereas on x86 it is listing all the connected and disconnected displays (7 of them total!). On both systems they show up under /sys/class/drm, so it may be the way that X enumerates the displays.
So, I tried the dtoverlay you posted, and sure enough - I was also able to get a test pattern using modetest! So, that explains part 1 - the pinout is different on some of these displays.
Next, I removed my previous 99-multihead-conf file from my "/usr/share/X11/xorg.conf.d/" and restarted the desktop manager. I opened a terminal window, entered "xrandr", and both displays listed! I thought it was solved, but at that point, my poor little Pi completely locked up. I had this same problem in the past when I was trying the various DRM driver overlays. The desktop just became very unstable.
At this point, I"m going to just fall back to the configuration I posted at the beginning of this first thread. It seems to work fine. And while it may in theory not be ideal, it works for my purposes (I"m creating a very basic touch UI on the touchscreen. I"m not trying to stream video to it or anything crazy).
Strange that the SPI display showed up for you but not me, even if it did then crash. I"ve tried an upgrade of my RaspiOS 32bit install (although with latest kernel) and it still doesn"t want to acknowledge the SPI display through xrandr. Could you post the output from xrandr when it sees both displays?
is needed for xrandr to see the display (listed as Unknown19-1 for me, presumably as X hasn"t been built with any knowledge of DRM_MODE_CONNECTOR_SPI being 19. https://elixir.bootlin.com/linux/latest ... ode.h#L390
However it is as I suspected - we have no mouse pointer on the TFT screen, presumably as X can"t cope with one display having a cursor plane and the other not. I don"t know the best way to overcome that.
*edit*: Minor correction there. If the two displays overlap, then the mouse cursor disappears on the SPI screen. If you set them to be independent (eg "xrandr --output Unknown19-1 --right-of HDMI-1"), then X switches mode and renders the mouse cursor.
Which sounds like yours (i.e the "Unknown19-1). I got the "lock up" again, but it turns out that lock-up was actually VNC (I"ve been using that to develop, as the text on a Sharp LCD is VERY tiny to look at in desktop mode). My console was still alive, so I hooked up an actual keyboard and mouse to the Pi, and the desktop on my Sharp LCD came alive. With the above two commands you"ve discovered, I now have two desktops. Sort of...
It appears as if the upper left hand corner of my Sharp LCD desktop is mirrored on the small LCD. It"s not two independent desktops. Instead, it"s the same desktop duplicated. I suspect that is probably more X configuration than driver stuff, however.
It appears as if the upper left hand corner of my Sharp LCD desktop is mirrored on the small LCD. It"s not two independent desktops. Instead, it"s the same desktop duplicated. I suspect that is probably more X configuration than driver stuff, however.
7-inches Smart LCM DGUS 800x480 DMT80480T070-09WN DWIN. Operating temperature: -30ºC - + 70ºC. DGUS is the abbreviation of a Graphic Application Service Software from DWIN Technology. It is an intelligent GUI software completely innovated by DWIN Technology.It is mainly designed for MCU users to quickly develop high-reliability full-graphics, touch screen HMI interface. It has the characteristics of simple development, flexible UI design, no operating system, fast running speed, strong reliability and stability. According to the application environment, it is divided into simple application grade, commercial grade, industrial grade, medical grade, military grade and automotive grade.
3.2 Inch TFT LCD Touch Screen Display V4.0 for Raspberry PiFeatures320x240 hardware resolutionResistive touch controlSupports any revision of Raspberry Pi (directly-pluggable)Drivers provided (works with your own Raspbian/Ubuntu/Kali)Supports FBCP software driver as well, allows to config software r..
The LCD in the TFT01 is ILI9341. It"s a 240 * 320 (resolution), 2.2S inch TFT LCD screen.The LCD has a wide viewing angle, the contrast is also very suitable.
I know that this is an old post but I have the same LCD and used Brian Lavery"s python driver as suggested in the comments above. I modified his code a bit to make it work "better". If anyone is interested with some step-by-step guide, you can read it at https://behindthesciences.com/electronics/connecting-ili9341-SPI-TouchScreen-lcd-to-a-raspberry-pi-in-python/
KL-TFT028B-PCB is 240x320 dots 2.8" color tft lcd module display with ILI9341 controller and 4-wire resistive touch panel,superior display quality,super wide viewing angle and easily controlled by MCU such as 8051, PIC, AVR, ARDUINO, and ARM .
It can be used in any embedded systems,industrial device,security and hand-held equipment which requires display in high quality and colorful image.It supports 8080 8-bit,9-bit,16-bit,18-bit parallel,3-wire,4-wire serial spi interface. FPC with zif connector is easily to assemble or remove.
In different modes, the welding method is different. For example, if I need to use the 8Bit SPImethod, I can move the position of the 0 ohm resistor as shown in the figure below.