Official Pi Display - No Touch

[mhedd]

I received the new official Pi display and the touch aspect is not working. I am using a Pi 2B. I used a stock May 5 version of Raspian, performed the apt-get update procedure and the screen displays fine, but no touch. I've reassembled it a couple times. I've used different power methods: GPIO pins, 2 separate power sources, and no-go. I did not see anything, but are there any entries in the system log that would hint at whether it was even being recognized? Anything else I could try?

Thanks!

[gsh]

Check that the little ribbon connector is properly connected....

When you apt-get update'd did it throw any warnings or errors?

[mhedd]

Gordon,
Thanks for the reply. Apt-get completed successfully several times (on the same microSD card, but before and after I re-flashed the OS). I will try again when I get home from work, but I have re-seated the ribbon several times and it does look like pictures of assembly guides I've viewed to double-check. Are there particular devices that should appear in /dev that I can look for?

[mhedd]

I reassembled it again a couple times, and there is no change in behavior. Again, I tried one power supply to the Pi with GPIO jumpers to the display, the reverse, and two separate power supplies. Any other thoughts?

[Paul Webster]

Did you start up the graphical user interface (startx) and check while in that?

[gsh]

Try apt-get install evtest

then just run it, it should give you a list of events one of which should be rpi-ft5406, choose that one then touch the screen

Gordon

[DaHu4wA]

Hello! Maybe a "sudo rpi-update" helps? This updates the PIs firmware.

[BMS Doug]

Hello! Maybe a "sudo rpi-update" helps? This updates the PIs firmware.

to an unstable daily build, rpi-update should not be recommended as a fix-all solution, it is more likely to break things than fix them.

rpi-update is for people who are aware of the risks of beta testing, not for everyone.

[DaHu4wA]

to an unstable daily build, rpi-update should not be recommended as a fix-all solution, it is more likely to break things than fix them.

rpi-update is for people who are aware of the risks of beta testing, not for everyone.

You are right, but there were adaptions to the LCD-drivers which are not in the official release yet. So it's worth a try. Maybe just do a backup first.

[scotty101]

My display worked with a release of Raspbian that was a few months old. I only needed the rpi-update to fix the known touchscreen event handling problem.

[PeterO]

Hello! Maybe a "sudo rpi-update" helps? This updates the PIs firmware.

to an unstable daily build, rpi-update should not be recommended as a fix-all solution, it is more likely to break things than fix them.

rpi-update is for people who are aware of the risks of beta testing, not for everyone.

I can only assume you haven't been following the threads in this forum where Foundation Engineers are recommending a firmware upgrade to to fix a problem in the touch screen driver ?
viewtopic.php?f=43&t=120642#p815808

This is exactly the right time to run rpi-update. On an already up to date system there are no bad side effects. Just don't run it "willy nilly".

PeterO

[BMS Doug]

Hello! Maybe a "sudo rpi-update" helps? This updates the PIs firmware.

to an unstable daily build, rpi-update should not be recommended as a fix-all solution, it is more likely to break things than fix them.

rpi-update is for people who are aware of the risks of beta testing, not for everyone.

I can only assume you haven't been following the threads in this forum where Foundation Engineers are recommending a firmware upgrade to to fix a problem in the touch screen driver ?
viewtopic.php?f=43&t=120642#p815808

This is exactly the right time to run rpi-update. On an already up to date system there are no bad side effects. Just don't run it "willy nilly".

PeterO

I had indeed Peter, I should have made it clearer that I was objecting to the "This updates the PIs firmware" line.

My concern was that it be made clear that updating your firmware to rpi-update will not always be the correct solution, when someone is researching a problem in the future (Search terms: Raspberry Pi firmware update) they might find this thread and not realise the implications of rpi-update.

Sorry that I was unclear.

[mhedd]

Did you start up the graphical user interface (startx) and check while in that?

Paul,
Yes I did. Frankly, I didn't expect it to would work in the terminal anyway!

[mhedd]

I had indeed Peter, I should have made it clearer that I was objecting to the "This updates the PIs firmware" line.

My concern was that it be made clear that updating your firmware to rpi-update will not always be the correct solution, when someone is researching a problem in the future (Search terms: Raspberry Pi firmware update) they might find this thread and not realise the implications of rpi-update.

Sorry that I was unclear.

Doug, understanding the risks, to confirm: It simply updates the software on the [micro]SD card, not the hardware on the Pi? So at worst, one would just have to re-flash the card?

[BMS Doug]

I had indeed Peter, I should have made it clearer that I was objecting to the "This updates the PIs firmware" line.

My concern was that it be made clear that updating your firmware to rpi-update will not always be the correct solution, when someone is researching a problem in the future (Search terms: Raspberry Pi firmware update) they might find this thread and not realise the implications of rpi-update.

Sorry that I was unclear.

Doug, understanding the risks, to confirm: It simply updates the software on the [micro]SD card, not the hardware on the Pi? So at worst, one would just have to re-flash the card?

Absolutely, the worst you will be able to do with this is make your software stop working, sometimes people will lose a lot of work by re-flashing the card and as such won't be happy to find out that the unstable version they have downloaded is causing them problems.

In this case the stable version hasn't yet had the fixes implemented, so use the rpi-update. In a few weeks (+) time the stable version will have been updated with the fixes (unless they cause other issues, which is why beta testing is needed).

[mhedd]

Absolutely, the worst you will be able to do with this is make your software stop working, sometimes people will lose a lot of work by re-flashing the card and as such won't be happy to find out that the unstable version they have downloaded is causing them problems.

In this case the stable version hasn't yet had the fixes implemented, so use the rpi-update. In a few weeks (+) time the stable version will have been updated with the fixes (unless they cause other issues, which is why beta testing is needed).

Ok, that was my understanding (of rpi-update), just wanted to confirm. I'll try it tonight and see what happens. Also, I'll try the evtest procedure that was offered. Of course everyone's situation is different, but it's no big deal for me to re-flash. I've scripted all my typical setups and apps and time hasn't permitted me to get too fancy!

[mhedd]

I ran evtest. It only showed the event devices related to the wireless keyboard/trackpad combo connected. I went ahead and ran rpi-update. There is still no sign of the touch device in evtest or attempting to use it in X. This seems to be looking like a hardware issue.

[Paul Webster]

I wonder if removing your wireless dongle (and hence the keyboard and trackpad) will make a difference - and temporarily connect a USB keyboard (with no mouse emulation).

[gsh]

Yes, now I'd suggest RMAing the display, it clearly requires further investigation

Gordon

[bfagioli]

When I first installed and attached the display device to my B+ the display worked fine but the touch operation was very intermittent. Several times after reboot the touch would not work at all. Then I read somewhere that you might need adjust the memory split and give the GPU 128 MB. I checked my configuration (sudo raspi-config) and I did have it set at 32. I increased it to 64 and it worked better but still dropped out frequently. Then I went to 128 and it has worked perfectly since.

[gsh]

OK,

Interesting, it might be worth trying to do

sudo vcdbg log msg

And see if there are any errors in there

[mhedd]

I wonder if removing your wireless dongle (and hence the keyboard and trackpad) will make a difference - and temporarily connect a USB keyboard (with no mouse emulation).

Paul, even I went so far as to have no keyboard plugged in and used ssh to start X. With that, evtest came back with "no hardware to test".

[mhedd]

When I first installed and attached the display device to my B+ the display worked fine but the touch operation was very intermittent. Several times after reboot the touch would not work at all. Then I read somewhere that you might need adjust the memory split and give the GPU 128 MB. I checked my configuration (sudo raspi-config) and I did have it set at 32. I increased it to 64 and it worked better but still dropped out frequently. Then I went to 128 and it has worked perfectly since.

I did see someone comment on that for another issue, and mine (the 2B) was already at 128. I even upped it to 256, with no difference. But thank you for the suggestion.

[mhedd]

Yes, now I'd suggest RMAing the display, it clearly requires further investigation

Gordon

Gordon, the command you gave me to run only had entries for HDMI and GPIOMAN (If you want me to post the output, I will). I'm assuming I should go back to Adafruit to RMA it? They sent me here when I first brought up my issue.

[jrspacecadet]

Forgive me if this is nit useful, I'm new to the world of Raspberry Pi,I had the same problem, but running sudo apt-get update followed by sudo apt-get upgrade as mentioned on the site where I bought my touch screen (http://www.mcmelectronics.com/product/83-16872). I know everybody has already talked about running update, but no one seems to have mentioned upgrade, though honestly I have no idea exactly what it does