ardangelo / sharp-drm-driver

Linux DRM Driver for 2.7" Sharp Memory LCD
GNU General Public License v2.0
35 stars 18 forks source link

Glitchy artifacting with adafruit sharp display #12

Open pwncity opened 3 months ago

pwncity commented 3 months ago

https://github.com/user-attachments/assets/fc1987eb-1eb3-4773-a3ae-1c6eb1473b64

Video of issue attached. Getting weird glitchy screen artifacts and hard lagging with Adafruit sharp display + zero 2 w. Have you ever seen anything like this and do you have any suggestions on what might be causing this issue?

prokrypt commented 3 months ago

Bad connections or wires too long (most common)

Noise/interference (probably from wires being too long)

Voltage too low (uncommon, as adafruit display has a charge pump to boost voltage)

A possible software solution to all of these is to lower the SPI clock frequency (currently set to 4MHz in the dts). I believe the listed maximum in the datasheet is 2MHz.

pwncity commented 3 months ago

I resolved the issue. The pinout displayed on the original repo is not correct for this setup. Chip select is on GPIO8(actual CE0 chip select pin) instead of the marked GPIO23. DISP is on GPIO 22 instead of the marked GPIO 24 and EXTIN is actually vcom on GPIO 23 instead of the marked GPIO 25. GPIO 22 and 23 are labeled clear as day in the .dts 😆

Thanks for all your help!

On Mon, Aug 5, 2024, 5:24 PM prokrypt @.***> wrote:

Bad connections or wires too long (most common)

Noise/interference (probably from wires being too long)

Voltage too low (uncommon, as adafruit display has a charge pump to boost voltage)

A possible solution to all of these is to lower the SPI clock frequency (currently set to 4MHz in the dts).

— Reply to this email directly, view it on GitHub https://github.com/ardangelo/sharp-drm-driver/issues/12#issuecomment-2270021346, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADMZF4ANOPUK5DSDMVAP3R3ZP73RNAVCNFSM6AAAAABMBB5IGGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZQGAZDCMZUGY . You are receiving this because you authored the thread.Message ID: @.***>