-
Notifications
You must be signed in to change notification settings - Fork 496
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
TFT35" Touch Shield For RPi SKU: AC-TFT35V-2.1 #252
Comments
Looking at the ic's, it uses this interface circuit: https://github.com/notro/fbtft/wiki/SPI-interface-circuit |
Got in a Pi B+ today and looked at some of the files. lsmod reports I tried to use this as a guide: http://www.circuitbasics.com/setup-lcd-touchscreen-raspberry-pi/ using the contents of the files found on the Pi B+. It did not work. I did see the device name is flexfb and the touch device is an ads7846. The touch driver does not seem to load, although the fbtft driver do seem to load. I am new to Linux and the Pi. I don't know how to check the init sequence to see if it matches. I also tried to modify /boot/config.txt with the addition of the line dtoverlay=piscreen. lcwii |
If you add this to /boot/cmdline.txt you'll get the applied init sequence output in the kernel log. Shown with dmesg.
|
Ok I put the fbtft_device.debug=3 line in /boot/config.txt. dtparam=spi=on The only part of dmesg that seems to be pertinent is the following, it [ 18.044018] i2c /dev entries driver I am also not seeing the ads7648_device anywhere. Here is my /etc/modules /etc/modules: kernel modules to load at boot time.This file contains the names of kernel modules that should be loadedat boot time, one per line. Lines beginning with "#" are ignored.Parameters can be specified after the module name.snd-bcm2835 flexfb width=320 height=480 regwidth=16 Looking at this again, it looks like the fbtft_device was already set to lcwii On 3/4/2015 8:47 AM, notro wrote:
|
Notro,
device... lcwii On 3/4/2015 8:47 AM, notro wrote:
|
You should put debug it in /boot/cmdline.txt not config.txt If you use Device Tree to load the device, do it like this in /boot/config.txt
This means that spi-bcm2708 is not loaded. Which kernel are you using? |
Notro,
3.18.6-v7i-aufs lcwii On 3/4/2015 10:15 AM, notro wrote:
|
Notro,
this webpage it breaks I2C, I2S & SPI. lcwii On 3/4/2015 10:15 AM, notro wrote:
|
This kernel is unknown to me. If you have the folder
|
Notro,
follows: dtparam=spi=on
[info] Loading kernel module snd-bcm2835. lcwii On 3/4/2015 10:55 AM, notro wrote:
|
I bought same TFT35" Touch Shiled For RPi. SKU: AC-TFT35-V2.1 from dx.com That worked: I've made raspi-config to enable SPI and I2C I've modified /etc/modules And I've added into /boot/config.txt After reboot is TFT screen finally black (instead of white) and after typing Thanks a lot! |
Milan,
Lester... On 3/4/2015 4:30 PM, Milan Kryl wrote:
|
Pi2 |
Milan,
version of kernel are you running? Lester... On 3/4/2015 5:09 PM, Milan Kryl wrote:
|
I have latest Raspbian installation from http://www.raspberrypi.org/downloads/ Linux 3.18.5-v7+ #1 SMP PREEMPT Fri Feb 6 23:06:57 CET 2015 armv7l |
Milan,
for some reason. Notro indicated that he was not familiar with that version.
from there. That way I know there isn't anything else that has been Lester... On 3/4/2015 5:26 PM, Milan Kryl wrote:
|
Milan, Thank you! I have the display working now. Now I just need to calibrate Your last step 'sudo con2fbmap 1 1', did not seem to work for me.
http://www.circuitbasics.com/setup-lcd-touchscreen-raspberry-pi/ : Next we need to configure the /fbturbo video driver/ to output the sudo nano /usr/share/X11/xorg.conf.d/99-fbturbo.conf In this file, find the line that says: Option “fbdev” “/dev/fb0″ and I had screwed up my /boot/config.txt file. Lester... //||//|| On 3/4/2015 5:26 PM, Milan Kryl wrote:
|
Yes, that's where I ended yesterday. With running text mode on PiScreen. I'll try to continue with other steps today or tomorrow. If I'll be succcessful I let you know here. Some resources: |
@krylm you only need one of fbtft_device or dtoverlay, not both. Regarding touch, here's a guide I wrote: https://github.com/notro/fbtft/wiki/FBTFT-on-Raspian |
@notro Thanks for your help! Finally I understand it a bit. Default was dtoverlay. I wasn't able to make it work only with fbtft_device so I am using SPI & dtoverlay with 90deg rotation. I've calibrated Touchpanel, didn't understand it that I need to touch the red crosses for the first time and had swapped axes. But now after proper calibration it's ok. So I don't need missing /etc/X11/xorg.conf.d/ directory. Just one non related question. Not initialized TFT is shining white, after init it's ok in black. But when I shutdown raspberry it's white again. I have to remove power cord to make it black. |
Ok, how do you incorporate piscreen_overlay.dts ? I tried lcwii On 3/5/2015 10:40 AM, Milan Kryl wrote:
|
I just removed line from /etc/modules Changed line and rebooted after everything working, I've added into /boot/cmdline.txt from my description before |
Milan,
because a friend also got the same set up and is not a console person
/usr/share/X11/xorg.conf.d/99-fbturbo.conf
time and locked up the Pi2. Had to power down everything and start over Lester... On 3/5/2015 12:16 PM, Milan Kryl wrote:
|
The Pi gpios are set as inputs on poweron. The display has the backlight control tied high, so a floating backlight pin turns on backlight. |
Hello, How do you do to use this TFT ? Can you please explan step by step ? Thanks you so much Sorry for my bad english ;-) |
I would if I could, but I still don't have the touch screen working Lester... On 3/12/2015 9:13 AM, leoneo wrote:
|
Hi all, |
I lost a lot of time , I tried to install it several times but every time I have a hdmi black screen with a dash flashing _ ... _ ... _ ... _ ... Please help |
It stoped working after i tried to calibrate the touchscreen and now it doesn't want to work again. |
I already spend a few hours on getting this lcd working, but I only have the white screen. According to syslog and startup messages it looks quite good, nonetheless it doesn't work. If anyone has a working image I would really appreciate any help! |
Pi 2? Lester... On 3/24/2015 4:24 PM, Seb wrote:
|
Jep Pi2. I currently install it on a Pi1. Hope this works out. |
Even on Pi1 same result. I tried also another Kernel, since I read it could be bug in the SPI communication in one of the last builds. I tried this yesterday on my Pi2 and produced kernel panic. It hasn't worked on the Pi1 either. Last shot is an image from dx.com. As soon as I know more I post it here. |
Same result. dx.com Image was from 2014/10/31. I give up at that point. Spend to much time on this piece of crap. |
For console or desktop? Lester... On 3/25/2015 12:38 PM, Seb wrote:
|
The image? It didn't run on both Pi versions - so I can't tell... |
Just chiming in here unfortunately. I have also spent quite a lot of time trying to get the display to work - it's white regardless what I do :-( Same problem on my RPI 1 incidentally. Anyway, I have one question: How connected is the screen and the touch? I see pin 11 high all the time, even if I have a pin placed constantly on the resistive pad.... come to think of it, this may be expected behaviour, but I am clutching for straws. These are the relevant files from my RPI 2 - I think! let me know if you need more /etc/modprobe.d/raspi-blacklist.conf#blacklist spi and i2c by default (many users don't need them) #blacklist spi-bcm2708 pi@raspberrypi ~ $ ls /proc/device-tree#address-cells clocks interrupt-parent name sound cmdline.txtdwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fbtft_device.debug=3 rootwait config.txt #for more options see http://elinux.org/RPi_config.txt no 99-fbturbo.conf file/etc/modules: kernel modules to load at boot time.#This file contains the names of kernel modules that should be loaded #snd-bcm2835 #tft #fbtft_device name=piscreen rotate=90 speed=16000000 #flexfb width=320 height=480 regwidth=16 init=-1,0xb0,0x0,-1,0x11,-2,250,-1,0x3A,0x55,-1,0x36,0x28,-1,0xC2,0x44,-1,0xC5,0x00,0x00,0x0,0x0,-1,0xE0,0x0F,0x1F,0x1C,0x0C,0x0F,0x08,0x48,0x98,0x37,0x0A,0x13,0x04,0x11,0x0D,0x00,-1,0xE1,0x0F,0x32,0x2E,0x0B,0x0D,0x05,0x47,0x75,0x37,0x06,0x10,0x03,0x24,0x20,0x00,-1,0xE2,0x0F,0x32,0x2E,0x0B,0x0D,0x05,0x47,0x75,0x37,0x06,0x10,0x03,0x24,0x20,0x00,-1,0x11,-1,0X29,-3 #fbtft_device debug=3 rotate=90 name=flexfb speed=16000000 gpios=reset:25,dc:24,led:22 redacted DMESG:[ 3.045390] usb 1-1.5: Manufacturer: Microsoft As you can see from the dmesg, the display is recognized, and set as fb1 |
I forgot to mention, that there is no input from input3, when I test that. |
I am working on installing this into my pi also. I am in the step of downloading the image and I am using a pi b. Do you guys know where I can find the pin layout? I want to be able to free up pins, especially the communication pins 'I2C, SPI'. |
Here is the schematic I got from the seller I got mine from. Pi Lester... On 4/11/2015 9:48 PM, exzile wrote:
|
No picture or attachment ? |
On 4/14/2015 6:58 PM, Texy wrote:
Lester... |
Ok, attachments don't work, clipboard paste doesn't seem to work either. Lester... On 4/14/2015 6:58 PM, Texy wrote:
|
I have this touch screen installed on a pi 2 with latest kernel 3.18.11-v7. When I used Notro's firmware for kernel 3.18.10 everything worked correctly, including the touch screen. When I upgraded to latest raspbian firmware, the touch screen no longer works. Dmesg error ads7846: probe of spi0.1 failed with error 22. I am using device tree with piscreen and ads7846 overlays. How do I fix the ads7846 error to get touch working again? |
For those interested with latest raspbian on pi 2 B, the install for only the lcd display using device tree. This orientation puts the power cord on top. #LCD Screen #install lcd and touch screen #move display to lcd #move console to lcd |
ShinyPC, I followed what u wrote and got it working but without touch screen any ideas why is doing that ? i am using rpi2 with latest software. |
Hi. I'm pretty new to Linux/RPi, but with your help guys I was able to make TFT and touchscreen work on RPi2. However, one weird wrinkle. If I skip the step of installing FBTFT kernel with SPI DMA, everything is perfect (albeit slow). But if I do use it, I get some sort of corruption in the frame buffer - some colors are wrong, random white dots on the screen etc. What could be the cause for this? Any parameters to adjust? If I do raspi-update I go back to normal colors.
|
Reduce the speed below to 24000000 or 16000000. See if that makes a difference
|
mwilliams03, thanks! 24000000 made slight improvements, but 16000000 fixed it completely. |
Updates from here I finally got myfbturbo file to edit - by installing fbturbo, duh! @futuneral thanks! I updated to match your settings, and Do you have dtparam=spi=on in tour cmdline.txt? When I try startx I get "module g2d_23 not found", so FBTURBO is installed - or I did not notice it before :-/, anyway it should be benign I still have a display that's just white, but I'll keep hacking away - it's probably due to having an old image that's been upgraded over the years |
overheder |
Has anyone been able to get emulationstation working on this tft display. I can get the console working well as well as x windows really well but by default emulationstsation won't display on the tft. I have been able to get it to display using fbcp but it's rather slow and not playable :-( |
Hi, |
Hi, have a Raspberry pi 2 B |
Closing issue since there has been no activity for more than 2 months. Reopen if needed. |
Hello friends, 1- I disabled the calibration at start like this: 2- Run: Section "InputClass" or simply change the option to "0" 3- Restart the Raspberry Pi 2 4- Run in terminal: Do the touch screen calibration and follow the instructions that will guide copying the calibration result and save the file: 5- Ready! Reinice to test! Grades: I followed the information from our friend futuneral shortly after instação system. I did not realize the system upgrade (step 1) as was already the latest version of Raspbian, funciou well, so I left anyway! Follows playback futuneral Tutorial, by changing paso 7 since it would be necessary to change later (step 2 of the above tutorial):
Section "InputClass" |
I have got the same screen and I have RPi3. I followed the instructions for setting up pi-screen and it just worked. Also instructions for the touch screen worked fine. |
The same experience as alexeyzimarev. I have got the same screen and but I have RPi. I followed the instructions for setting up pi-screen and it just worked. |
Anyone seen this one? Looks similar to the Waveshare. Acquired from eBay.
They have a .img for the RPi B+, but not the RPi 2 yet.
The text was updated successfully, but these errors were encountered: