[Orange Pi Zero 3 ili9486 TFT LCD]

For touch calibration, the straighforward intuitive way does not work.

 

Try this procedure: https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/#findComment-204741

 

The copy location /etc/X11/xorg.conf.d/ might be different. The xinput calibration text output will tell you that directory.

 

The DTS also has some pressure and resistivity parameters, but I don't know how they work exactly.

[Orange Pi Zero 3 ili9486 TFT LCD]

Do you use x11's evdev component? Does it make any difference of stability before and after running xcalibrate/xinput_calibrator?

 

I find that xinput_calibrator does not do anything toward pressure sensitivity. I need to make it less sensitive... anyone knows a good way of doing this?

[Orange Pi Zero 3 ili9486 TFT LCD]

Nicely done!!

 

How are you going to use it? X11? Wayland? What window manger and desktop?

 

Is your mouse cursor jumpy or stable? Is there RGB noise when you drag windows on the desktop?

 

I have those issues. My setup: orange pi zero3, ili9488, drm, x11, openbox and idesk.

 

I wonder if my problem comes from sharing the SPI bus with 2 chip selects... but if you have one SPI and 2 chip selects, but no noise problems, then SPI is not my problem.

[Orange Pi Zero 3]

Differences:

 

20 pin IO, instead of 26 pin

Wifi chip Aw859, instead of CdTech 20U5622 (aw859 is in opi 3 LTS)

1 more built-in USB port

 

Is the wifi antenna included in the package?

Is it wifi 5 or wifi 6?

Under what kernel are they supporting video acceleration?

[Orange Pi Zero 3 ili9486 TFT LCD]

Orangepi had the good idea to make the SPI pins match the Raspberry Pi pins

 

I read somewhere that the mipi-dbi driver doesn't have the rotate/rotation parameter... I guess I need a different initialization byte sequence for the LCD to do the rotation. Or does anyone know that there's a rotation parameter?

[Orange Pi Zero 3 ili9486 TFT LCD]

Great

 

Does the opiz3 fit well under this LCD?

 

Are you still going to modify the DTS to plug the LCD directly on the OPIZ3?

 

There are 2 ways that the touch IC is connected: same SPI bus, and separate SPI bus... which one is it for this LCD?

If it is the same SPI bus, refer my ili9488 thread as a base

If it needs a separate SPI bus, see my ili9341 thread, and search for gpio-spi... I can't make this work in opiz3 yet, only opiz

[Orange Pi Zero 3 ili9486 TFT LCD]

Nice progress.

 

I think that your SPI, DC, CS, RESET configurations are correct. DONT CHANGE THOSE

 

Regarding the ili9341 vs ili9486 driver... hopefully you will find an example using the ilitek,ili9486 driver, with a correct init parameter.

(check that the init is the same as the people having success in https://forum.armbian.com/topic/11701-35-lcd-ili9486-with-orange-pi-zero/#comment-86679 )

 

 

With the correct init parameter, you configure the LCD to receive the data in the correct pixel format and ordering, to match the format sent by the CPU. Also, it configures VCOM, a key parameter that I think is electrical and not data related... read the LCD manual, I can't remember what it is for.

 

Search for ili9486 in the raspberry pi forum. Maybne someone figured it out already.

 

Here's how I used the mipi driver for the ili9488, based on someone's success with Raspberry Pi https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#findComment-207964

 

[Fastest way to set bootup GPIO pin levels]

This is a very interesting topic  I will try to apply it when I need a fast 3.3V output on startup.

 

I am dealing with LCD screens right now, and I know 3 ways to display something on screen faster:

* compiling the LCD driver(s) into the kernel (with the * option instead of "M" in Linux kernel config)
* make uboot drive the LCD display (https://github.com/robutest/u-boot/blob/master/drivers/video/ili9341.c)

* instead of compiling a DTBO to overlay after startup, add the "blob" in the main DT itself and uboot wont lose time on that (there's a discussion about that in onf of the opiz3 gpio threads)

(but I haven't tried any of them)

[shrink-backup - a tool for backing up sbc:s]

Today, I used your shrink-backup tool again

 

It works as expected!

VERY VERY USEFUL!

[OrangePi Zero LTS ili9341 TFT LCD (and later OrangePi Zero 3)]

I can't understand your situation  can yoiu send a photo of the LCD, the kernel version, and do some of the tests that I wrote in this thread?

 

Start with the DTS here: https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/#findComment-205335

 

 

The bgr and rgb parameters are among the last things to fix (applies to only some LCD drivers)... do you even get a picture in the LCD with wrong colors?

[How to install armbian in h618?]

On 11/8/2024 at 12:45 PM, Nick A said:

This patch is in all my builds. For orangepiezero3 I would use my main branch. I haven't test the other branches with zero3.

 

If you are using my main branch, you can disable any patch by adding (-) infront of the patch list files series.armbian and series.conf located in 

https://github.com/NickAlilovic/build/tree/main/patch/kernel/archive/sunxi-6.7

 

Edited November 8, 2024 by Nick A

@Nick A

Has anyone updated the NickA's v4l2/cedrus patches, to work with Linux 6.11 or greater?

 

[Orange pi zero 3 SPI cs pin]

I don't know why you copied a dtbo to /usr/lib/linux-image...

 

I think you only need spidev turned on in armbian-config

 

What shows up in ls /dev/spi* ?

 

Please show your success, if you make it work

[How to install armbian in h618?]

I hope it works for you

 

I wish to have NickA's Armbian patches in Linux 6.11+, because I need to use its improvements for my new LCD screen  

[Run an ili9486 with pine64]

This is the closest you can get to the ili9486... buy this LCD, study the hardware differences, and maybe you can get the ili9486 working

https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/

 

[Lost mipi-dsi display after recent update]

I dont have a Pine64, but I have some experience with LCD displays.

 

Did you try the latest kernel, available by building armbian with the "Edge Linux" option?

 

Can you roll back to the working kernel, get the LCD working again, and examine "dmesg | grep mipi"? If there's no difference, there might be more information in "armbian-monitor -u"

 

DasFisch: in armbianEnv.txt, there is no explicit option to activate ko modules. You can activate armbian or custom user dtbos (overlays), which tell Linux what driver it may use in such port or address.

[NanoPi Neo2 V1.1 / how to control OTG port power with GPIO 354?]

For another orange pi board, someone had success with an official (but old) DTBO:

https://forum.armbian.com/topic/31654-orange-pi-zero-2w/page/2/#findComment-202508

There's a very interesting discussion about GPIO troubleshooting here (and how sysfs is deprecated), I hope it helps:

https://forum.armbian.com/topic/33800-orange-pi-zero-3-gpio

 

[Orange Pi Zero 2W]

I still havent done anything with my orange pi zero 2w, but I will be interested in trying this usb-host in the near future

 

There's a Armbian shortcut that I use all the time with custom dts: armbian-add-overlay, but the dtbo files are kept separate in /boot/user-overlays

[NanoPi Neo2 V1.1 / how to control OTG port power with GPIO 354?]

I have never seen a dts so small.

 

Usually, they have several "fragment" codeblocks.

[LonganPi 3H page w/o ISOs ?]

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.

[opiz3, no hdmi video with Edge]

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.

[Repository for v4l2request hardware video decoding (rockchip, allwinner)]

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

[ST7796 display w/ opiz3]

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.

[OrangePI Zero has no Audio on current community builds.]

that looks like a normal armbianEnv.txt

 

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

[ST7796 display w/ opiz3]

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

[ST7796 display w/ opiz3]

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.