240x320 spi tft lcd to rasberry pi quotation
The PWR will keep on and the ACT will keep blinking when the Raspberry Pi starts up successfully, in case both of the two LEDs keep on, it is possible that the image was burnt incorrectly OR the TF card was in bad contact.
It is recommended to use a 5V/3A power adapter for the Raspberry Pi other than USB connection, otherwise the Pi may failed to start up because the PC"s USB port might have not enough power.
※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.
While googling for any info about lcd controller I came across this page: http://heikki.virekunnas.fi/2015/raspberry-pi-tft/, author managed to get from manufacturer patch file for kernel sources and tested it with 4.1.y - on which lcd worked. But still LCD replace HDMI, but I want to use this screen as additional for user interaction, while the bigger on HDMI as presentation monitor.
I have looked through files that he (author of page `heikki.virekunnas.fi`) published, and I came to conclusion that the patch do not changes standard ILI9341 driver but only replace default framebuffer and directs it to ili driver while cutting out hdmi, only single mention in patch file about ili9341 is adding it"s .ko file to $obj in makefile... wow I"m so smart
Since, fbtft has been merged with rpi kernel, so the fb drivers (including ili9341.c) was moved to fbtft_device driver (so the author of page can"t compile latest kernel with driver+patch).
So something about hardware, which I reverse engineered by the "hard way" - "grab multimeter and run through all LCD FPC pins and shift register pins"
Now I noticed there is "9486L" which can suggest that LCD screen is controlled by ILI9486L, I found this LCD on taobao too but I can"t contact seller.
I"m pretty sure about D/C (Pin 37 on LCD) and Reset (Pin 19 on LCD) pins by looking into driver code, but I can"t identify other signals (WR/RD/CS/etc...)
[ 0.000000] Linux version 3.18.9-v7 (lgh@lgh-ThinkPad-X200) (gcc version 4.7.1 20120402 (prerelease) (crosstool-NG 1.15.2) ) #7 SMP PREEMPT Sun Jun 28 09:33:18 CST 2015
[ 0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0x2938b030 smsc95xx.macaddr=B8:27:EB:38:B0:30 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
[ 4.838806] input: MOSART Semi. Rapoo 2.4G Wireless Touch Desktop as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:24AE:1000.0001/input/input1
[ 4.862704] hid-generic 0003:24AE:1000.0001: input,hidraw0: USB HID v1.10 Keyboard [MOSART Semi. Rapoo 2.4G Wireless Touch Desktop ] on usb-bcm2708_usb-1.3/input0
[ 4.902783] input: MOSART Semi. Rapoo 2.4G Wireless Touch Desktop as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:24AE:1000.0002/input/input2
[ 4.926400] hid-generic 0003:24AE:1000.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse [MOSART Semi. Rapoo 2.4G Wireless Touch Desktop ] on usb-bcm2708_usb-1.3/input1
- Controller is not ILI9341/ILI9325 - those are for smaller displays (320x240, etc...), I guess this might be ILI9486/9488 because they are for 480x320 displays. But when I compared init with DS it does not fit right so LCD can have a clone of ILI9486/9488 ...
- Module use only SPI interface and two CE signals (CE0 for touch controller, CE1 for LCD shift registers - compared to others lcd modules, in KeDei module this is swapped),
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
3.5 inch RPi LCD V3.0 HVGA 480X320. There is a XPT2046, 74HC04D, 74HC4040D, and 2 74HC4094D chips on the back. Is there a way to determine which driver I need to use in software?
I am not 100% convinced that the distribution given works with the LCD (the item I bought is dis-continued but the seller provided another item that has identical specifications - 3.5" IPS 15fps 480x320 resolution - but I suspect it has a slightly, or altogether different, controller.
[*]Is there any way I can extract some information of what driver has been used, or tried to use, for the TFT via that half working distribution? As far as I know, a GPIO/ SPI connection will not gather connected hardware information...
I am not 100% convinced that the distribution given works with the LCD (the item I bought is dis-continued but the seller provided another item that has identical specifications - 3.5" IPS 15fps 480x320 resolution - but I suspect it has a slightly, or altogether different, controller.
[*]Is there any way I can extract some information of what driver has been used, or tried to use, for the TFT via that half working distribution? As far as I know, a GPIO/ SPI connection will not gather connected hardware information...
I bought a display off Amazon described as [ SainSmart 3.5" inch TFT LCD 240x320 RGB Pixels Touch Screen Display Monitor For Raspberry Pi for Model B & B+] and sold by: Sain Store. What I received is the 320x480 display you described. I am also trying to verify the model before I try to set it up.
What I would like to do is be able to "diff" a clean image and the modified image to find out exactly which drivers were used, what files have been modified for their use to be able to create a standalone install package that be used on a clean install.
TheQuestor wrote:What I would like to do is be able to "diff" a clean image and the modified image to find out exactly which drivers were used, what files have been modified for their use to be able to create a standalone install package that be used on a clean install.
Although, after following the installation instructions, the screen I have behaves weirdly: there seems to be a symmetry between the point where I click on the screen and the real place of the pointer. Depending on the argument of the rotate instruction in
the symmetry is vertical or horizontal. I haven"t figured out yet how to fix this and have the pointer exactly where I touch on the touchscreen. Hope this helps...
It was working but was a bit too slow so, I Increased the speed After setting Everything back to normal the screen is not working properly. The display is fine , but the touch is not responding. Please help! Did I BROKE it ?
This site uses cookies to store information on your computer. Some are essential to make our site work; others help us improve the user experience. By using the site, you consent to the placement of these cookies. Read our Privacy Statement to learn more.
Use this 2.2" Color TFT LCD Display to add a vibrant color display to your Raspberry Pi projects. Just wire up your display and use the SPI protocol to communicate with your TFT. This is more advanced than our Raspberry Pi LCD shields since you have to wire using a breadboard and use the fbtft Raspberry Pi Library when configuring so we recommend it for intermediate users.
For Arduino users, this display is also Arduino compatible however we recommend our 11 Pin 2.2" TFT LCD Display which can be plugged directly into an Arduino UNO or Mega so you don"t have to use a breadboard.