Home › Forums › Forums › Technical Support for PiScreen › [Resolved]PiScreen not displaying anything
- This topic has 6 replies, 2 voices, and was last updated 8 years, 11 months ago by raghavsood.
- AuthorPosts
- October 18, 2014 at 7:16 am #2792raghavsoodParticipant
I received my kickstarter pledge and assembled the PiScreen today.
After connecting to it, I can’t seem to display either the test image, or the console on it.
The backlight works both in hardware and software. I can see the device in /dev/fb1 and /dev/input/event0, as well as /proc/bus/input/devices
Neither the evtest or ts_bin tests show any form of touch input, even though I can see a mouse in my hardware listing, despite having no USB mice connected
October 18, 2014 at 5:02 pm #2802Mark WilliamsKeymasterCan please show me the output of these commands
dmesg ls -l /dev/input/event* cat /proc/bus/input/devices
Mark --OzzMaker.com --
October 19, 2014 at 4:18 pm #2804raghavsoodParticipantOctober 19, 2014 at 5:43 pm #2806Mark WilliamsKeymasterEverything in that output looks correct.
One last question.
When starting X Windows, Does the touchscreen work with the calibration program that runs just before X Windows?Mark --OzzMaker.com --
October 19, 2014 at 11:35 pm #2818raghavsoodParticipantThe touchscreen shows no images and sends no touch events whatsoever.
Even after setting it to display the console, and when trying to display the test logo image, I can see nothing on the screen.
Neither the calibration program, nor evtest can receive any touch events from the screen.
I have a feeling that the screen unit itself is defective, as even when the backlight is on, I need to push the screen up from its bottom edge before the light actually comes on, as shown in this video I took.
October 20, 2014 at 12:28 pm #2822Mark WilliamsKeymasterOK… that looks faulty. Sorry about that.
I will send you out another one today.
Mark --OzzMaker.com --
October 20, 2014 at 2:18 pm #2824raghavsoodParticipantThank you! Appreciate the service
- AuthorPosts
- You must be logged in to reply to this topic.