Just picked up an Inky 13.3 and paired it with a RPi Zero 2 W. I’ve gone through the getting started instructions, but when I come to run an example the screen does nothing.
So it is communicating with the display over I2C, but it ain’t doing anything on the screen.
I found this thread which describes exactly what I’m seeing, and suggested a change in config.txt, which I’ve tried making, but no change. The console says the screen had been detected correctly, but the display doesn’t change.
I’ve tried the led.py script that is included and that works just fine - the led on the back of the display module blinks away.
The reason I reassigned CS0 to GPIO 7 is because the (now old) inky library I have uses GPIO 8 by grabbing the pin for bit-banging. If GPIO 8 is assigned to CS0 in the overlay, it can’t be used as a general GPIO pin (you can use gpioinfo to check GPIO8 is not preallocated).
Once the upgrade to Debian 13 (Trixie) happens, there’s a new version of the Linux GPIO libraries (libgpiod), and I’ll port the inky code into my C libraries. Hopefully, then, the spidev will be able to dynamically allocate the CS pin and I can streamline things.
Getting it plugged in all the way was a bit agonizing and took some trial and error, despite the device being detected.
Many thanks! I see, so with a fresh install and the Pimoroni examples I shouldn’t need your extra pin reassignment?
Any other thoughts on what would be causing it not to update, but that it can detect the screen type then? That would suggest that the I2C is working, and power to the board (since the led flashing works). I’m not sure how to debug the issue. The header is firmly in to the Inky (as you say, a bit nervous doing that, but it went in okay with the bubble wrap on the other side :-)).