https://thepihut.com/products/papirus-z ... 8041609745
Simply put the eInk screen does not seem to get updated with the content I try to push into it. Just stays completely white.
I have set up a fresh Raspian lite with the quick setup script at https://github.com/PiSupply/PaPiRus after initially noticing the problem. I have enabled the i2c and SPI interfaces and all commands seem to execute just fine except the screen just stays white.
I have tested the pHat on Raspberry Pi Zero and Raspberry Pi 3 with same results.
The five buttons on the board and the temperature sensor seem to be working fine. papirus-temp outputs current temperature on terminal and papirus-buttons when run with strace shows button presses being detected.
epd-fuse daemon is running and I can see the file listing shown below for /dev/epd/.
I have confirmed that the jumper is at correct pin position for the screen size.
Code: Select all
# find /dev/epd/ /dev/epd/ /dev/epd/BE /dev/epd/BE/current /dev/epd/BE/current_inverse /dev/epd/BE/display /dev/epd/BE/display_inverse /dev/epd/LE /dev/epd/LE/current /dev/epd/LE/current_inverse /dev/epd/LE/display /dev/epd/LE/display_inverse /dev/epd/current /dev/epd/current_inverse /dev/epd/display /dev/epd/display_inverse /dev/epd/panel /dev/epd/command /dev/epd/temperature /dev/epd/version
Code: Select all
root@rpi-zero2:/proc/device-tree# sudo papirus-write "Hello" Writing to Papirus....... Finished! root@rpi-zero2:/proc/device-tree#
So in the end this comes to the following guestions:
How can I check that the eInk display is properly detected?
Is there any actual way to determine whether the display or module is broken or not?
Should detection of the phat create /proc/device-tree/hat as that is not currently happening for me?
The board arrived with blank screen originally and is version 1.2.
Thank you for everyone who could bring some light to the issue.