robertoj

I haven't tested this... but I see that pins PH1, PI11, PI14 are not connectable in the orange pi zero 3. Only PH3 would be connectable. Is this correct? Is there an overlay to get PWM in PH2? (i read in the post from April 5 that it can be a PWM pin)

Thank you, I found the manual for initramfs-tools and hooks ... it looks like I can do it

Hello WDR_s, If you upgraded kernel recently, did you have any problem starting X11 (or lightdm, or desktop)? I started with a downloaded arm minimal image with linux 6.12, and my DTS would bring up the panel-mipi-dbi-spi driver correctly in text mode, but X11 can't start. When I have my normal 99-fbdev.conf, I get this: FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument, When I remove 99-fbdev.conf and let X11 setup everything automatically, X11 complains about needing panel-mipi-dbi_dri.so. I restored an old armbian OS backup with linux 6.11, and everything worked normally. You are using a different LCD driver, did you have any problem?

labwc is available in debian trixie: Start with a minimal armbian install Make sure your /dev/fb0 is DRM, not framebuffer $ sudo apt install seatd labwc foot $ labwc -s foot

I am having trouble with my SPI LCD, which uses driver panel-mipi-dbi It works great when I use a minimal Armbian image, but with a desktop image it doesn't work. This is because package "plymouth" does something in the ko loading order: it loads panel-mipi-dbi too early. Plymouth provides a graphical boot animation. The driver depends on a binary file /lib/firmware/panel-mipi-dbi-spi.bin (but the file name could change depending on the DTS) At boot time, I saw that the panel-mipi-dbi.ko is loaded BEFORE the EXT4 in the microSD is mounted... and the binary file is not in the initrd.img-version (checked with lsinitramfs) Is it possible to add something in /etc/initramfs-tools/ to include /lib/firmware/panel-mipi-dbi-spi.bin ? With my Raspberry Pi (Raspbian) I don't have this problem, because the panel-mipi-dbi driver is loaded AFTER EXT4-fs (and it also uses plymouth) I found that when plymouth is not installed, usr/lib/modules/6.15.0-edge-sunxi64/modules.dep doesn't have this line kernel/drivers/gpu/drm/tiny/panel-mipi-dbi.ko: kernel/drivers/gpu/drm/drm_mipi_dbi.ko Also, in Raspbian, the same file has the dependency line, but changed with 5 more dependencies kernel/drivers/gpu/drm/tiny/panel-mipi-dbi.ko: kernel/drivers/gpu/drm/drm_dma_helper.ko kernel/drivers/gpu/drm/drm_mipi_dbi.ko kernel/drivers/gpu/drm/drm_kms_helper.ko kernel/drivers/gpu/drm/drm.ko kernel/drivers/gpu/drm/drm_panel_orientation_quirks.ko kernel/drivers/video/backlight/backlight.ko And this is confirmed with modinfo drm_mipi_dbi: 1 dependency in armbian and 5 dependencies in raspbian... could this be the reason why the ko is loading too early?

I haven't been able to use hardware acceleration ffmpeg in: * Orange Pi Zero 3 * self built image with Debian Trixie and Xfce desktop * Linux Edge 6.15.0 * Login in Xfce X11 mode * follow all the instructions in original post * mpv plays most mp4s VERY SMOOTHLY BUT WITH 100% CPU * The "Using hardware decoding (drm)" does not show * Instead, I get "hwdec unsupported=drm" * some resolutions will crash mpv with "Segmentation Fault"

Things you should try: Capture the dmesg since before the sound file is playing Try again with the sound file in the main EXT4 partition

Ok I was able to get the LCD working with a self built image, by copying the linux config from the armbian.com image to the build/userpatches/linux-sunxi64-edge.config Currently rebuilding without the successful linux config, and then I will look at the difference Update: I didn't find any differences and the new image without the userpatches config accepts the LCD DTS and bin file. Ok, I dont understand what was happening before. Now I am getting the same X11 error as before: MESA-LOADER: failed to open panel-mipi-dbi: /usr/lib/dri/panel-mipi-dbi_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) I see that this panel-mipi-dbi_dri.so is part of libgl1-mesa-dri debian package, in DEBIAN SID, but not Bookworm https://packages.debian.org/sid/arm64/libgl1-mesa-dri/filelist https://packages.debian.org/bookworm/arm64/libgl1-mesa-dri/filelist Next, when I rebuilt the armbian OS with xfce desktop, I get the same panel-mipi-dbi-spi error: can't find the bin file. I checked the config again... and it was the same Update: It was easier to build Sid minimal, and install labwc (wayland), just remember to install seatd: https://eirenicon.org/labwc-a-tutorial/ I isolated why the panel-mipi-dbi-spi can't load when I apply it in an Armbian OS with XFCE. xcfe requires plymouth, and plymouth does something to the uInitRd And when I reboot immediately after installing plymouth, the SPI LCD does not start, and dmesg shows that panel-mipi-dbi-spi could not find the firmware file. Update: I realized that even before plymouth, the uinitrd does not contain the LCD firmware file... but it is doing something that prevents panel-mipi-dbi-spi from loading the file. Update: the initrd.img lacks the LCD bin file ... I will work on including this file later. An interesting observation from my X11-running armbian OS: it does not contain the file /usr/lib/dri/panel-mipi-dbi_dri.so (not even the dri folder) This working Xorg is version 1.21.1.7. Same as in my failed attempt with Armbian bookworm. It was failing because it demanded panel-mipi-dbi_dri.so... I will re-test tomorrow. UPDATE July 11: the instructions here https://forum.armbian.com/topic/53568-how-to-add-a-specific-single-file-in-the-initrdimg-ideally-automatically-with-update-initramfs/ allow the LCD firmware to be readable when plymouth is installed. Update: Linux 6.15.4-edge does not allow X11 to start in the LCD with panel-mipi-dbi-spi.ko. The 99-fbdev.conf was present. Only text console is usable (and maybe Wayland) Trying with other linux images... available linux-image packages to install: $ apt -a list linux-image-edge-sunxi64 linux-image-edge-sunxi64/now 25.08.0-trunk arm64 [installed,local] linux-image-edge-sunxi64/trixie 25.5.1 arm64 linux-image-edge-sunxi64/trixie 25.2.3 arm64 linux-image-edge-sunxi64/trixie 25.2.2 arm64 linux-image-edge-sunxi64/trixie 24.11.1 arm64 linux-image-edge-sunxi64/trixie 24.8.3 arm64 linux-image-edge-sunxi64/trixie 24.5.1 arm64 linux-image-edge-sunxi64/trixie 24.2.1 arm64 Trying with older linux. Today, July 11, Armbian 25.5.1 installs Linux 6.14.8: sudo apt install linux-image-edge-sunxi64=25.5.1 ...upon reboot plymouth graphics works, but X11 didn't start Trying older kernel: 6.13.7 sudo apt install linux-image-edge-sunxi64=25.2.3 Success: it shows the plymouth boot graphic, the lightdm login and the xfce desktop Update: July 15... when I built the armbian OS minimal again, the image did not include panel-mipi-dbi.ko, we must activate it in the kernel config before compilation: Drivers > Graphics > DRM > DRM support for MIPI DBI compatible panels

I keep having trouble with panel-mipi-dbi-spi not finding /lib/firmware/panel-mipi-dbi-spi.bin even if it exists and it works in another Armbian and Raspberry. This happens only with the armbian OS that I compiled with default linux configuration. The armbian OS image that I downloaded from armbian.com can drive the LCD (but has other problems with X11). When I boot my image while watching the serial output, I only see "Starting kernel", then a few lines regarding udev, then the login prompt (sorry, I will be more exact when I get back home). I changed console=both to console=serial, in armbianEnv.txt but I still don't see more kernel or init messages while booting. How can I activate this verbose boot? Is there any chance that the /lib/firmware is not mounted and available to the kernel module in this early stage?

Can you confirm that you can still run X11 with Linux 6.12?

Please someone help I can't start X11... I installed: sudo apt install xserver-xorg-video-fbdev openbox x11-xserver-utils xinit xserver-xorg-input-evdev Created this /etc/X11/xorg.conf.d/99-fbdev.conf file And tried sudo startx, then the LCD got a black screen for a fraction of a second, and I got (in my ssh session) The error message is FBIOPUT_VSCREENINFO: Invalid argument I also see that xorg wants to use 24 bit color, but my LCD is 18 bit color. <- update: this does not matter... my opiz3 with running X11 shows the same message I will try to get X11 working again with the linux 6.13 build folders that worked for me in april panel-mipi-dbi-spi reference: https://github.com/notro/panel-mipi-dbi/wiki https://www.kernel.org/doc/Documentation/devicetree/bindings/display/panel/panel-mipi-dbi-spi.yaml Is anyone here experienced with panel-mipi-dbi-spi? I am having problems loading the bin file again. What's weird is that sometimes the same bin file works in one Armbian version and Raspberry, but not for the Armbian version I want. Ok. Here, they say that if the LCD works in console, but not X, then it is not a kernel problem https://github.com/raspberrypi/linux/issues/5615 This might be related: https://forums.raspberrypi.com/viewtopic.php?t=386528

Happy to report that with a different wiring, I got the touch part working... it served me well to follow examples from the Raspberry forum The mipi command string is the same as the one kungfupancake github, but removing the 0x21 command. The bin file should be copied into /lib/firmware/panel-mipi-dbi-spi.bin I used the vanilla armbian image with kernel 6.12.30 (not using my custom build method of removing the arm64-dts-sun50i-h618-orangepi-zero2w-Add-missing-nodes.patch ) It works with all the 3.5" and 4.0" red LCDs I have (some 3.5" LCDs I have are ili9486).

They are in the same pin numbers, but different GPIO Update: I found that I can just use both CS0 and CS1 in opiz3 normally as expected in a DTS for a SPI ili948x LCD and touch screen, as seen in my ili9488 thread. (PH9=CS0, PC10=CS1) I was having so much trouble before, but now I finally got it

Connect to the orange pi's serial port with a usb-serial from your laptop. Make sure you connect the TX with the RX, and viceversa. The speed is 115200. You will see booting messages, before the login prompt. If nothing works, re-write the img to the microSD.

Thank you! I will try it tomorrow. What is spi1_cs0_pin and spi1_cs1_pin equal to, in Orange Pi Zero 2W, and in Opiz3? Is it defined in the spi-spidev dtso, or in the main opiz3/opiz2w dts? I need to have it correctly in the main DTS, because the LCD driver doesn't use spidev (and it would conflict). cs0 matches the pin position in raspberry pi: pin 24.... so it would make sense if cs1 is pin 26. Reference. This is the patch that changes the opiz3/2w DTS https://forum.armbian.com/topic/50418-dont-use-kernel-61216-on-sunxi64/page/2/#findComment-216934

Success story: https://forums.raspberrypi.com/viewtopic.php?p=2322591#p2322591 with the 3.5 inch ili9488, graphics (wayland) and touch in raspberry pi 3b I hope this helps with making it work in orange pi zero 3 and 2w (only touch missing)

Hello all Is anybody having success with spidev with orange pi zero 3 and Linux 6.12? I want to test my LCD panel's touch, but I need spidev working first

You can build an armbian image with these instructions:https://docs.armbian.com/Developer-Guide_Build-Preparation/ You can configure it: https://docs.armbian.com/ When you have a setup you like, use this to backup as an image: https://forum.armbian.com/topic/29427-shrink-backup-a-tool-for-backing-up-sbcs/ I still suggest only armbian... but please share if you can use buildroot for opiz2w

Thank you!

Last year, I tried to set up "Access Point" mode in orange pi zero 3 and never got it working. Do you have a link to the instructions to make it work?

Nice Are you going to use apps that will need high fps? If so, comment about the performance. Does the touch function feel steady and reliable? (dragging windows without jumpiness, with the stylus) The app for keyboard emulation with touch screen is "matchbox", if you need it.

I am glad you could do it with the orange pi zero 2w, because I also want to use a very small arm board I am having trouble with the red ili9488 red LCD's touch function, and if I keep having no results, I will replace with the waveshare LCD model (I wanted to have 4-inch LCD ) What armbian and linux version did you use? If you go to the latest linux, you may need to modify the DTS a little bit (modifications are in my ili9488 thread). Warning: I use a different driver (parameter "compatible") for DRM graphics, and different drivers might need different DTS lines. Always use a different microSD for experiments, so you don't mess with your working setup Does the orange pi zero 2w just need male pin headers on the 40-pin connector, and then plug the LCD on top?

i answered in your thread.

https://forum.armbian.com/topic/46824-orange-pi-zero-3-ili9486-tft-lcd/ user wdr_s had success with that same lcd. Try it with linux 6.1 (check the success case) If you have a file named orangeEnv.txt... you arent using armbian yet! Make sure to use armbian-add-overlay In the ili9341 or ili9488 there's someone trying with orange pi zero 2w, which is very close to zero 3

I just did some new experiments, trying to get touch working in ili9488 LCD v2.1 Increasing or decreasing the SPI MHz in both the LCD and touch section of the DTS DONT WORK... I couldn't get touch working Next is to use a software defined SPI with spi-gpio (based on my experience in my ili9341 thread) does anybody know a Python soft spi program which can talk to ads7846/xpt2046? update: I am getting some good touch results with Raspberry, which I hope I can transfer to opiz3. https://forums.raspberrypi.com/viewtopic.php?t=389230