adafruit / Raspberry-Pi-Installer-Scripts

381 stars 160 forks source link

pttft 2.8 resistive screen not working on a Pi 1B+ #215

Open KalixtShawxo opened 2 years ago

KalixtShawxo commented 2 years ago

Sorry for the delay on opening this.....I had been sick for the past month or so. This is a followup/ repeat(?) issue from "PiTFT black screen on Bullseye Raspberry Pi OS Desktop (Issue #195)"

Hi, I have been going round and round for a few days now trying to get my pttft 2.8 resistive screen working on a Raspi B+ running Bullseye based Raspberry PI OS from the imager v1.62, using FBCP and no matter what I have done, the HDMI output works, but the tft screen does not display anything in a mirror mode. Now, I can run the script for console mode, and it will display on the screen and the not HDMI...but now there is no GUI and no touchscreen. I am trying to setup for use without a keyboard and mouse, so I kinda need the GUI. I went so far as to even delete the existing adafruit-pitft.py file and create a new one with a copy/paste from your listed fix. this was after following the instructions from Adafruit's "easy Install". Now I had at one point in the past gotten it to work with Buster as a mirror but the touchpoints were all off by 90* and I could never get it to align properly. And now with your fix I was hoping to try it again and use Bullseye. But I can't even get to the point of seeing if the touchscreen works at all, much less being misaligned like it was before. Any help pointing me to a fix would be greatly appreciated.

makermelissa commented 2 years ago

I'll give it another look. Maybe they changed something since the last fix.

makermelissa commented 2 years ago

The script is working fine on the latest version of buster. IMG_3981 Things to keep in mind:

KalixtShawxo commented 2 years ago

Thanks Melissa, but I now give up on this. I ultimately need a console mode with touchscreen and not mirror mode, I just listed that I couldn't get either one to work correctly. Mirror mode would not show on the tft screen but did show on the monitor, while console mode showed on the tft but would not get to the gui not would the touchscreen work correctly.  I can follow the directions perfectly and it does not work, must be hardware. Thanks again for your time, sorry to have wasted it.  Roger.

Sent from Yahoo Mail on Android

On Mon, Mar 7, 2022 at 13:27, Melissa @.***> wrote:

The script is working fine on the latest version of buster.

Things to keep in mind:

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

makermelissa commented 2 years ago

If you want touchscreen and console, you may want to look at Raspberry Pi Lite and use Mirror Mode. If it is in fact the hardware that is the issue, you should definitely try posting your issue on the forums.

makermelissa commented 2 years ago

Hey, I think I might have been able to finally reproduce this issue with a Raspberry Pi 3 while working on another project. Which specific Model of Raspberry Pi are you using?

KalixtShawxo commented 2 years ago

Ok, hopefully that means I'm not crazy here. 😊👍I've been trying with a 2014 model  B+ v 1.2

Sent from Yahoo Mail on Android

On Sat, Mar 12, 2022 at 18:51, Melissa @.***> wrote:

Hey, I think I might have been able to finally reproduce this issue with a Raspberry Pi 3 while working on another project. Which specific Model of Raspberry Pi are you using?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

makermelissa commented 2 years ago

Interestingly enough, the problem doesn't happen on the Pi Zero 2 W, but does on the Pi 3. So it's not related to 1 HDMI vs 2 HDMI ports like I initially thought.

makermelissa commented 2 years ago

On a whim, I tried a different HDMI cable on the Pi 3 and it seems to be working now.

StephenGrable1 commented 1 year ago

I am also seeing this issue with my Raspberry pi B+ 2014 - explained more in this post but it doesnt seem hardware related since the screen works fine displaying the "console" - its only when the install type is set to "fcbp" when the screen goes black after booting up (but the touchscreen works to move the cursor)