Open jackcarey opened 2 years ago
unless you're using 2 SPI devices I don't think hooking up CS to GPIO7 will work, that's the pin that goes low to tell a "second" SPI device to start listening out for SPI data, because GPIO7 is Chip Select 1.
GPIO8 is Chip Select 0 (the "first" in binary)
again, if you're doing clever-er stuff with SPI than I am, this could be moot, but I connect my SPI displays to GPIO8.
I think GPIO9 is also a bad call for DC as GPIO9 is the SPIO MISO pin, even though it's not used by fcbp it is still "doing SPI stuff" with SPI enabled. (make sure SPI is enabled in raspi-config
that's caught me out more than once)
I hook up DC to GPIO24 and I also include -DGPIO_TFT_RESET_PIN=number
in my cmake config, I connect the reset pin on the display to GPIO25
I hope that helps, good news is I'm pretty sure its just mis-wired at this point :) It took me finding this driver on like, 4 different projects before I got it working the first time.
Hardware
The display works with Pimoroni's examples, but I'm unsure if the V variant of the driver chip will make a difference for this drivers support.
Software
Using Raspberry Pi OS with Desktop Release date: April 4th 2022 System: 64-bit Kernel version: 5.15 Debian version: 11 (bullseye)
Following the steps in the readme, I ran:
My
/boot/config.txt
file looks like this:When I then run
sudo ./fbcp-ili9341
, the last console line is "All initialized, now running main loop" but the screen stays black.The same happens when I run the cmake step, replacing
-DST7789VW=ON
with-DST7789=ON
.