One should be careful as incorrect timings can lead to unpleasant things. some of them are reversible.You shouldn't be able to damage the display through incorrect timings...
Waveshare is publishing the data sheet of the display they claim to use https://files.waveshare.com/upload/1/1a ... LCD_DS.pdf
What I don't understand is why they don't follow the timing specified in the spec.
So give a try to the timing below
Code:
# waveshare SKU12885 as per 7inch_1024X600_LCD_DS.pdfdtoverlay=vc4-kms-dpi-genericdtparam=clock-frequency=51200000# display is using DPI mode6dtparam=width-mm=154,height-mm=85dtparam=hactive=1024,hfp=160,hsync=20,hbp=140dtparam=vactive=600,vfp=12,vsync=3,vbp=20Code:
0: a2 pu | lo // ID_SDA/GPIO0 = PCLK 1: a2 pu | lo // ID_SCL/GPIO1 = DE 2: a2 pu | lo // GPIO2 = LCD_VSYNC 3: a2 pu | lo // GPIO3 = LCD_HSYNC 4: a2 pu | lo // GPIO4 = DPI_D0 5: a2 pu | hi // GPIO5 = DPI_D1 6: a2 pu | lo // GPIO6 = DPI_D2 7: a2 pu | lo // GPIO7 = DPI_D3 8: a2 pu | lo // GPIO8 = DPI_D4 9: a2 pd | lo // GPIO9 = DPI_D510: a2 pd | lo // GPIO10 = DPI_D611: a2 pd | lo // GPIO11 = DPI_D712: a2 pd | lo // GPIO12 = DPI_D813: a2 pd | lo // GPIO13 = DPI_D914: a2 pn | lo // GPIO14 = DPI_D1015: a2 pu | lo // GPIO15 = DPI_D1116: a2 pd | lo // GPIO16 = DPI_D1217: a2 pd | lo // GPIO17 = DPI_D1318: a2 pd | lo // GPIO18 = DPI_D1419: a2 pd | lo // GPIO19 = DPI_D1520: a2 pd | lo // GPIO20 = DPI_D1621: a2 pd | lo // GPIO21 = DPI_D1722: ip pd | lo // GPIO22 = input23: ip pd | lo // GPIO23 = input24: ip pd | lo // GPIO24 = input25: ip pd | lo // GPIO25 = input26: ip pd | lo // GPIO26 = input27: ip pd | lo // GPIO27 = inputCode:
pi@raspberrypi:~ $ xrandrScreen 0: minimum 16 x 16, current 1024 x 600, maximum 32767 x 32767XWAYLAND0 connected 1024x600+0+0 (normal left inverted right x axis y axis) 154mm x 83mm 1024x600 59.85*+ 800x600 59.86 640x480 59.38 320x240 59.52 720x480 59.71 640x400 59.95 320x200 58.96 1024x576 59.90 864x486 59.92 720x400 59.55 640x350 59.77 pi@raspberrypi:~ $ sudo cat /sys/kernel/debug/device_component/gpuaggregate_device name status-------------------------------------------------------------gpu bounddevice name status-------------------------------------------------------------fe400000.hvs boundfef00700.hdmi boundfef05700.hdmi boundfe208000.dpi boundfe004000.txp boundfe206000.pixelvalve boundfe207000.pixelvalve boundfe20a000.pixelvalve boundfe216000.pixelvalve boundfec12000.pixelvalve boundpi@raspberrypi:~ $ kmsprintConnector 0 (32) HDMI-A-1 (disconnected) Encoder 0 (31) TMDSConnector 1 (41) HDMI-A-2 (disconnected) Encoder 1 (40) TMDSConnector 2 (46) DPI-1 (connected) Encoder 2 (45) DPI Crtc 1 (74) 1024x600@59.99 51.200 1024/160/20/140/+ 600/12/3/20/+ 60 (59.99) P|D Plane 1 (64) fb-id: 346 (crtcs: 1) 0,0 1024x600 -> 0,0 1024x600 (XR24 AR24 AB24 XB24 RG16 BG16 AR15 XR15 RG24 BG24 YU16 YV16 YU24 YV24 YU12 YV12 NV12 NV21 NV16 NV61 P030 XR30 AR30 AB30 XB30 RGB8 BGR8 XR12 AR12 XB12 AB12 BX12 BA12 RX12 RA12) FB 346 1024x600 XR24pi@raspberrypi:~ $ Statistics: Posted by aBUGSworstnightmare — Wed Mar 27, 2024 6:26 am