Open neil-stack opened 2 weeks ago
Hi, I'm using an RP4 with a 7 in display and HyperPixel 4 (no touch) The HyperPixel 4 is completely blank. I have no idea what i need to do to make it work.
As you can tell im new to raspberry pi
Revision c03115 description debian gnu/linux 12 (bookworm)
name -r 6.6.31+rpt-rpi-v8
this is a fresh installation. no changes or software added.
The Raspberry pi has a standard 7in display attached and the hyperpixel4 attached .
The 77 in display works The HyperPixel is completely blank
PLEASE NOTE
:warning: GitHub issues are for reporting problems with the software, tech support do not monitor these. Our software team are smol and busy, and you will not receive a timely response. If you're having a hardware issue with your Hyperpixel 4, you should contact support@pimoroni.com.
:warning: Hyperpixel 4 is only officially supported on Raspberry Pi OS. There are too many operating systems with too many quirks to begin to support them all. Issues relating to other operating systems will be closed.
Describe the bug
What's gone wrong?
To Reproduce
What install steps did you go through so far? Did you install from GitHub or use our one-line-installer?
Your HyperPixel 4
Let us know which HyperPixel 4 board you're using. Note: if you're having a problem with the original HyperPixel you should go to: https://github.com/pimoroni/hyperpixel
Your Raspberry Pi
Give as much detail about your Pi and OS as possible. We only officially support Raspbian, but might be able to point you in the right direction if the problem is with another OS.
cat /proc/cpuinfo | grep Revision
can tell us this exactlylsb_release --description
anduname -r
Extra debugging information
If you're having a problem with touch, try checking
dmesg
for related errors:dmesg | grep Goodix
for HyperPixel 4.0" Rectangulardmesg | grep ft5
for HyperPixel 4.0" SquareAnd check i2c is working:
ls /dev/i2c-*
You should see something like:
And your HyperPixel 4 touch is showing up (there should be an address blocked out with UU in the below command):
i2cdetect -y X
( where X is the number of i2c bus found in the command above)For example: