robertoj

It would help you to also buy the 2 SBCs that are the closest to the longan pi 3H: * Orange Pi Zero 3 * Orange Pi Zero 2W Learn the differences in hardware. Figure out the differences in their DTS files. Then share those fidings here with us. If there are some things that work in these 2 Orange Pis, but don't work in the Longan Pi 3H... then raise those specific questions in the forum.

Can you try building from NickA's Armbian repo? https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/page/17/#findComment-205764 I also lost HDMI video when I compiled official main armbian on my own... but I don't keep track which Linux version gave me the problem (I am working with SPI LCDs). When I tried NickA's branch, I got HDMI video.

Start by building this armbian branch: https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/?do=findComment&comment=205709 https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/page/2/#findComment-205855 Then install a minimal X11+openbox+lightdm with an HDMI display. Then use the mpv from jock's repository

If you are going to build your own armbian, choose linux edge. It provides a recent enough Linux with improvements in the mipi-panel-spi driver. I didn't say anything about it before, because the latest improvement is for the ili9488, when working in MIPI protocol mode, but you might have a better chance of success with your ST7796. The GPIO codes are as follows: PA0= <&pio 0 0 0> PA1= <&pio 0 1 0> PB0= <&pio 1 0 0> PC0= <&pio 2 0 0> PB1= <&pio 1 1 0> ... PC14= <&pio 2 14 0> There are 2 driver options: staging/fbtft/st7796s, which gets you a classic framebuffer device, and X11 will work Another is the panel-mipi-dbi-spi driver, which gets you "Direct Rendering Manager", and allows smoother 3D and video acceleration. Depending on the driver, be aware of the parameter differences: rotate/rotation, active high reset vs active low reset. See my other LCD threads.

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):

Thank you The panel-mipi-dbi-spi driver, with the improvement it got in Linux 6.11, would be able to drive the ili9488 with the standard mipi protocol. It just needs to have the correct init byte commands. See: https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#findComment-208043

When I activated all the H6, H616, H618 patches, I get 3 patching errors: The 1st patch arm64-dts-H616-Add-overlays-that-are-also-compatible-with-orang is failing because I don't have these lines in the arch/arm64/boot/dts/allwinner/overlay/Makefile sun50i-h616-spi-spidev.dtbo sun50i-h616-spidev0_0.dtbo sun50i-h616-spidev1_0.dtbo Which patch file would insert those lines? Or should I edit the patch file to match the existing Makefile?

A virtualbox instance with 1 CPU and 2GB RAM inside this real PC: CPU: Intel i5-6300U (4) @ 3.000GHz RAM 8GB I started from scratch OK, I will activate all H6, H616 patches

I started with including this patch: patches.armbian/arm64-dts-H616-Add-overlays-that-are-also-compatible-with-orang.patch But it failed with this message: Maybe I need another patch together with this... one patch that adds the lines expected in the reject text

I suddenly have a need to test Linux 6.11 or greater, because there's a needed improvement in the panel-mipi-dbi-spi driver (thread keyword ili9488) User "The Going" has kindly advised me to try his Armbian branch with Linux 6.12, so I am here sharing results as I test it with my Orange Pi Zero 3. Initial instructions: https://forum.armbian.com/topic/35635-armbian-242-is-broken-on-orange-pi-pc2/#findComment-207980 At first try, I decided to NOT follow this step: armbian/build> egrep '^-' patch/kernel/archive/sunxi-6.12/series.conf (finds all the excluded patches) Well, I continued. Choosing Linux Edge, shallow option, Bookworm minimal, there were zero problems: no patching errors and no compilation errors. At the end of the 4 hour compilation, I tested the resulting image in my Orange Pi Zero 3... and it booted fine. Not working at this moment: wifi (#iw dev returns nothing) spi1 (failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND when I use a dts overlay that works in Linux 6.7) usb (lsusb only shows the 2 root hubs, but not my usb devices) when I decompile sun50i-h618-orangepi-zero3.dtb there is no references to spi1 or hdmi (maybe more) Working: serial console ethernet other things not tested Next, I am going execute armbian/build> egrep '^-' patch/kernel/archive/sunxi-6.12/series.conf and find specific patches that maybe will improve my hardware situation. Result of that egrep search command, with patches I will try first, one by one, in bold

What controller is it? ili9486, ili9488 or st7796s?