juj

Do you have a link to the display? The `-DILI9341=ON` option will definitely not work without modifications on a 128x128 display, because it assumes a 320x240 ILI9341 controller based display.

If it is this one https://www.adafruit.com/product/1431, try using `-DSSD1351=ON` instead of `-DILI9341=ON` option (delete CMakeCache.txt when changing that option)

> How can the binary know that device was initialized/reset properly? Unfortunately it does not. Communication to the display is fully unidirectional, the driver only sends data, but never receives...

That looks good, nothing stands out on the command line. If no other troubleshooting items help, try verifying the display using a different driver to double check physical connection.

It reads like you got it going with some pixels at least. Reading https://github.com/juj/fbcp-ili9341/blob/662e8db76ba16d86cf6fd09d85240adc19e62735/ssd1351.cpp#L36 it suggests there is a vertical swap directive in there. Try changing the `0x34` to `0x24`,...

See the documentation section about Screen Tearing at https://github.com/juj/fbcp-ili9341#about-tearing. Ghosting is an effect of the voltages and refresh rate timings that the panel is driven at. Some displays have specific...

Thanks! Looks great! Had a couple of notes above.

Ops, very sorry, I had reviewed this code, but it looks like the comments had got stuck behind GitHub's "pending comments" feature. Published them now.

Sorry, missed this issue from before. I would recommend building the driver to different build directories for different device. The SPI speed parameter could be configured for runtime use, but...

Sorry, missed this issue from before. I have not seen ST7789H2 before. There are a couple of backends for ST7789 and ST7789VW in fbcp-ili9341, but not for H2. No idea...