robertoj

that looks like a normal armbianEnv.txt If there was a "sun8i-h3-analog-codec" in the overlays line, that is pretty weird.

I meant the ili9488 DTS Also avoid using any other SPI related DTS, when working with a LCD DTS. They will interfere with each other. Use only the ili9488 DTS that I posted, only changing: * the GPIO number codes, to make it fit your wiring connections * the content of the *.txt file with the one in the raspberry forum

Check here for the byte command sequence for st7796s and combine with the dts in my thread https://forums.raspberrypi.com/viewtopic.php?t=380704 using the dts as is with your different touch controller likely wont hurt it, it may just throw error messages in dmesg|grep spi or delete the touch part of the dts, or disconnect the spi pins to the touch controller if you want to be safer.

👍🏽 check that there are no uboot errors related to loading that dtbo (right before loading the kernel).

👍🏽 This is a problem with a specific dts meant for the spidev driver, because I am using the spi1 bus with 2 chip selects everyday with my LCD, which doesn’t use the spidev driver (uses dedicated LCD-spi driver). Do you have an older orange pi zero 3 Armbian image, and see if it works normally? can you rebuild Armbian with ./compile.sh, choose Linux edge (latest) and see if it works normally?

thank you for posting the fix 👍🏽 Can you show the contents of armbianEnv.txt? Also find the sun8i-h3-analog-codec.dtbo file inside the /boot/dtb/… folder you can always check that overlays are being used, by looking at the uboot messages, before loading the kernel. https://docs.armbian.com/User-Guide_Armbian_overlays/

I have seen success cases with ili9341, ili9488 and st7796... and one guy is trying with the ili9486 over in the unsupported sunxi section of this forum. https://forum.armbian.com/topic/46824-orange-pi-zero-3-ili9486-tft-lcd/ https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/ https://forums.raspberrypi.com/viewtopic.php?t=358240&hilit=Ili9341#p2165638 I think that the success case of ili9488 (mine 😎), would be a good starting point. Use the same DTS, and look at the command byte sequence that the driver will use. Get the datasheet for both ili9488 and ili9486, to see if the same commands have different addresses and parameters. Search in google for arduino examples, which will include a byte sequence. Buy a ili9341 LCD, which has many success cases, and test that you can at least make that work. Then you can keep working with the same wiring.

Try all combinations of (I have no idea why these things sometimes work): * Only define the PH26,PH27 in pins = "PC0", "PC1", "PC2", "PC23", "PH26", "PH27"; * only cs-gpios = <0>; //use default CS instead of cs-gpios = <&pio 2 23 0>; /* PC23 for CS */ Make sure that there are no erorrs in: dmesg|grep spi dmesg|grep mipi Usually these are good signs: lsmod|grep ili shows a loaded kernel module ls /dev/fb* shows a created video device

Jock, Doug, Do I only need this 1 patch file? https://github.com/LibreELEC/LibreELEC.tv/blob/master/packages/multimedia/ffmpeg/patches/v4l2-request/ffmpeg-001-v4l2-request.patch Is ffmpeg 5.1.6 recommended? I will follow these straightforward compilation guides:

Change: reset-gpios = <&pio 7 27 1>; /* GPIO 24 */ to: reset-gpios = <&pio 7 27 0>; /* GPIO 24 */ Change the SPI speed to 24MHz Format your DTS so we can read it easily. Correct the comments with GPIO nnn because they are confusing. Show a wiring schematic between the BPI M2 Berry and your LCD Use the "Spoiler" (eye) button, so that your long texts don't take so much space.

Is anyone getting a jumpy cursor, and garbled image around the areas of window refresh? (only at times of touching the screen) I suspect it is caused by sharing the SPI bus with the ads7846 (XPT2040)... anyone knows? I don't have this issue when I use the USB mouse. I also experience the LCD going 3/4 black and frozen, when there are no input events. It restores to normal when I touch the screen or move the mouse (with a white washout/flash in the LCD). My app is continuosly painting pixels, and it happens after a few minutes of no input events. I already have: xset s off & xset s noblank xset s -dpms But it seems that I don't have "xset" installed in my debian bookworm. Fixed with apt install x11-xserver-utils

Is this related to SPI flash? I use opiz3's SPI-1 (with 2 CS) everyday with my LCD

Thank you KungfuPancake!! I tested the command byte sequence, Linux 6.11.9 and my DTS. My LCD is now working I posted the solution in the appropriate thread: https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#findComment-208446 Going: if you make changes for Opiz3, I will continue testing them

THANKS TO USER KungFuPancake, who showed me his github repo, where he indicates to use the latest Armbian-edge, and provides the a command byte sequence for the ili9488 https://github.com/KungfuPancake/v0_ips_touch_display?tab=readme-ov-file If you see inverted colors, edit the panel-mipi-dbi-spi.txt and comment the line #command 0x21 before using the mipi-dbi-cmd If you have the cheap chinese clone LCD (see first post), use this DTS (change the gpio codes as needed):