inky: Inky Impression - EEPROM Error
I wondered if anyone might have some ideas on this problem?
I have the inky impression 5.7" display and I can’t get it to work. I have it hooked up to a pi zero w, ran the installer script from the pimoroni website, and I get this below. EEPROM error sounds like it could be a faulty unit to me, but I don’t have a good way of proving otherwise.
pi@rp-mini-phat:~/Pimoroni/inky/examples $ sudo python3 clean.py
Inky pHAT: Clean
Displays solid blocks of red, black, and white to clean the Inky pHAT
display of any ghosting.
Detected 7-Colour (UC8159)
Traceback (most recent call last):
File "/home/pi/Pimoroni/inky/examples/clean.py", line 17, in <module>
inky_display = auto(ask_user=True, verbose=True)
File "/usr/local/lib/python3.9/dist-packages/inky/auto.py", line 24, in auto
return InkyUC8159()
File "/usr/local/lib/python3.9/dist-packages/inky/inky_uc8159.py", line 144, in __init__
eeprom_resolution = _RESOLUTION.keys[self.eeprom.display_variant - 14]
TypeError: 'builtin_function_or_method' object is not subscriptable
pi@rp-mini-phat:~/Pimoroni/inky/examples $
… and the system Diag
pi@rp-mini-phat:~/Pimoroni/inky/examples $ uname -a
Linux rp-mini-phat 5.10.63+ #1459 Wed Oct 6 16:40:27 BST 2021 armv6l GNU/Linux
pi@rp-mini-phat:~/Pimoroni/inky/examples $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
pi@rp-mini-phat:~/Pimoroni/inky/examples $
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 24 (7 by maintainers)
Commits related to this issue
- U8159: Longer busy timeout from #136 — committed to pimoroni/inky by Gadgetoid 3 years ago
… which I’ve now sorted out. Just changed the timeout to 60s. Happy Holidays!
You’re going to laugh (I hope). I went back and looked to see whether I2C and SPI were enabled on the Pi. I2C was not; SPI was. Once I enabled I2C, everything started working.
Now I just need to find a good slideshow program to use with this thing. 😃
Thanks for the help!
Glad that sorted things temporarily!
Leaving this issue open as we still need to fix it properly (also the lurking
busy_wait
issues)