robertoj

I confirm that ffmpeg-v4l2request works for opiz3, with OS image Armbian_community_24.8.0-trunk.6_Orangepizero3_bookworm_current_6.6.31_minimal.img.xz I started with the freshly booted OS image, added my DTS for ili9341 SPI LCD (see other thread in community-allwinner), rebooted, and followed all the steps in the original post. The final steps to play an mp4 in tty: Also works with mplayer (more efficient) Next up, I try again with the latest armbian OS image Please ask what information I can get from my working setup, and see what's the roadblock in the latest armbian Update: I confirm that the ffmpeg-v4l2request package is not working for the latest armbian Armbian_community_24.11.0-trunk.351_Orangepizero3_bookworm_current_6.6.54_minimal mplayer does not work either I can only think of using apt to install an older mpv.deb (+dependencies), if starting from the newest Armbian OS... Or forcing apt to never upgrade the mpv.deb and related deb dependencies, if I start with the older Armbian OS As a temporary measure, only needed while ffpmeg gets the patches officially, and the Debian servers include that new version too, right? Reference: https://unix.stackexchange.com/questions/242014/how-to-install-the-previous-version-of-a-deb-package-and-pin-it Another thing to try is to compile an Armbian image (latest), with bleeding edge linux kernel, as I see success for other people in Linux 6.7 https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/?do=findComment&comment=204697 Jock, if I want to build my own ffmpeg with v4l2-request, is this a good recommendation? "You also need to build with --enable-v4l2-request --enable-libudev" https://artemis.sh/2023/03/06/ffmpeg-v4l2-requests-4.4.3.html

https://github.com/jonathan-gatard/ili9486-xpt2046/tree/main use this for inspiration

The last reported success was with Debian Bookworm, in a comment from July 23... can you repeat the experiment with an OS image from before that date? (I don't have access to my orange pi zero 3 for a few days)

I see that you didnt change any gpios. You must change them... what are the pins in the orange pi zero 3 that will control the lcd? (you must have the LCD schematic) If you try my original DTS, without having a screen like mine, do you get these 2 files? /dev/fb0 /dev/input/event0 According to this https://mjmwired.net/kernel/Documentation/devicetree/bindings/display/ilitek,ili9486.yaml You must use the line: compatible = "waveshare,rpi-lcd-35", "ilitek,ili9486";

Thank you I will try to modify it for opiz3

Starting with the DTS that worked for me in the orange pi zero 3, with ili9341: https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/?do=findComment&comment=204672 My DTS is for a customized set of pins that works for me, and it is different than/from the waveshare set of pins. You need to change: * file name change to: ili9486-ads7846-spi1.dts * gpio pin selections everywhere in the DTS * "adafruit,yx240qv29" should be "ilitek,ili9486" * change "rotation" to "rotate" * change "reset-gpios = <&pio N N 0>;" to "reset-gpios = <&pio N N 1>; Then sudo armbian-add-overlay ili9486-ads7846-spi1.dts Reboot (does anyone know the correct DRM driver for ili9486?)

Thank you!

Thank you, but I was referring to the 1 DTS that enables the ili9341, ads7846 and pwm-backlight, just in case you made a last change that you didn't mention.

Hello Ivano Can you control the backlight? If so, can you share your whole DTS? (opiz2w)

Hello all, I tried the apt repo install instructions in the first post... but it seems that my armbian bookworm is still installing its own .deb package and not the one from the apt.undo.it repo Is there an obvious step that I am missing? What version of mpv should I have if I installed successfully? Thank you in advance!! (my target is orange pi zero 3) P.S. I see that the debian repo (through my web browser) does not provide mpv.deb, but Ubuntu Jammy does... does this mean that the armbian-bookworm mpv.deb does not need the patches? I also see that the available debs are 11 months old... perhaps if you could point to some instructions that work, we could do it ourselves and share the outcome.

If /media does not exist, if you type mkdir -p /media/usbdrive, it will not complain about /media not there, and create that folder too

I HAD the same issues with calibration. The 99-calibration.conf needs to be created, with the output of xinput-calibrator. It is not automatically done. You also need the evdev.conf file copied from usr/share/... to /etc/X11. When I wasn't doing this, I did the calibration many times and it wasn't effective. Read https://www.waveshare.com/wiki/3.5inch_RPi_LCD_(A)_Manual_Configuration very carefully and follow all steps regarding calibration.

That’s very interesting… why my opiz3 needs both CS defined and the opiz2w only wants one CS defined. but please make further tests and confirm this works with lightdm Sudo apt install lightdm xorg-input-evdev sudo cp /usr/share/X11/xorg.conf.d/45-evdev.conf /etc/X11/xorg.conf.d/ (https://www.waveshare.com/wiki/3.5inch_RPi_LCD_(A)_Manual_Configuration) sudo systemctl disable lightdm sudo startx (in second ssh) sudo DISPLAY=:0.0 xinput-calibrator do the calibration plug usb keyboard and mouse Sudo systemctl start lightdm check that the cursor moves with touch or pen right click and

Thank you. My target is the orange pi zero 3

Hello Rafman, did you get MPV working for the first time with Linux 6.7.12? Or did you see it with an earlier Linux too? Which Debian or Ubuntu did you build? What are the most critical linux modules and debian packages, for hardware video acceleration? Thank you!

did you do systemctl daemon-reload as advised? Did you create the /media/250hdd folder beforehand? Can you comment out the fstab line, and try mount /dev/sda1 /media/hdd250 ?

More progress: this single DTS configures 1 SPI bus control the ili9341 and XPT2046 touch chip I needed to specify explicitly both CS in: cs-gpios = <&pio 7 9 0>,<&pio 2 15 0>; /*PH9=CS0 for lcd, PC15=CS1 for touch*/ That "<0>" that I saw in other examples IS NOT WORKING! Ivano, try modifying this DTS. It doesn't have backlight function, so plug the LED wire to 3.3V to test.

I tried it... and I wished that the -d option was still there... I had to download an old version... however, it didn't work with -d /dev/mmcblk0 ... it started scanning my nvme root But I like the mechanics and the interface Now I am going to try it the normal way, with latest version. Update: I tried it from my orange pi zero 3, Armbian Linux 6.6 Now I have a 2.7GB IMG file in a USB drive which I bring to my Linux Mint laptop Balena etcher has just finished flashing, and is estimating 30 minutes to validate 2.7 GB completed validating quickly too (I was using the laptop sd writer and that is not as reliable as my very cheap USB microSD writer). The Armbian Image booted just fine in a newer Orange Pi Zero 3. THANK YOU FOR MAKING THIS TOOL. I WILL USE IT MANY TIMES

Thank you for the suggestion With my modified DTS, which takes hints from your DTS and my reference, I get the LCD to display with the DRM driver... but no touch events (with evtest) I dont have more time to analyze this problem for now... but I havent triple checked my connections. Ivano, check whether PI5 (your desired IRQ) is not already claimed by the kernel, with the last command I show up there (pinmux-pins) Maybe you can try other GPIO. Then, if it doesn't work, try changing the level and edge polarity parameter (I talk about it in this thread or the other recent ili9341 thread). In your case: use PI5 <8 5 _>, interrupts = <2 10 2>; /* PC10 - IRQ */ < try changing 2 (active high) into 8 (active low) I HAVE NEVER CHANGED THIS pendown-gpio = <&pio 2 10 1>; /* PC10 */ <try changing 1 (edge rising) into 0 (edge falling) Opiz2w reference: More useful discussion here: https://forum.armbian.com/topic/27457-connecting-banana-pi-m2-zero-with-ili9341-display-over-spi-on-latest-armbian-image/page/2/#comments

I got the same in my orangepizero3 I looked for it in debian.org https://packages.debian.org/search?keywords=rear&searchon=names&suite=bookworm&section=all The explanation: it is only available for x86

I am glad it worked Are those DTS available somewhere?

I either have something miswired, or the hardware doesn't like the spi-gpio, but I have constant problems switching into X11. I want to try the most commonly method: one SPI bus, 2 chip selects, as shown in this example: https://github.com/dev-null2019/orangepizero2w35tft/blob/main/joyit35a-overlay.dts But modifying it from opiz2w to opiz3. The DTS by dev-null2019 has this connection wiring list: cs0=ph5 pin 24 (user defined,lcd) cs1=ph9 pin 26 (_____,touch) res=pi6 dc=ph4 irq=ph2 mosi=ph7 (native) miso=ph8 (native) clk=ph6 (native) 3v3=native 0v=native It looks weird to me that in line 9 of the DTS, only the CS0 is specified, but not CS1... is that normal? Is everyone feeeding the LCD with 3.3V or 5V? (I was using 3.3V because that works great in my orange pi zero) Has anyone had success with the backlight gpio parameter? Is it ok to use 5V instead of 3.3v? This would be the modified wiring list, for opiz3: cs0=ph5 pin 24 (user defined,lcd, next to 5V) cs1=ph9 pin 26 (native,touch) res=pc14 dc=pc7 irq=pc10 mosi=ph7 (native, both touch and lcd) miso=ph8 (native, touch only) clk=ph6 (native, both touch and lcd) led=3v3 (native) 5v=pin 5 (native, use next pin ph5 for cs0) 0v=native 11 wires, 2 with Y splitter in physical pin order: 3=cs0 4=5v 17=3v3 18=res < 3v3 for LED 19=mosi 20=gnd < mosi with Y 21=miso 22=dc 23=clk 24=cs1 < clk with Y 26=irq

Interesting references: https://learn.sparkfun.com/tutorials/how-to-run-a-raspberry-pi-program-on-startup/all https://community.element14.com/products/raspberry-pi/f/forum/5609/launching-an-x11-app-exclusivly-on-startup-with-a-pi https://forums.raspberrypi.com/viewtopic.php?t=314455 https://forums.raspberrypi.com/viewtopic.php?t=353649 https://raspberrypi.stackexchange.com/questions/52099/using-openbox-to-autostart-gui-application-raspberry-pi-3

Check the /boot/armbianEnv.txt line "overlays=..." . It should contain "usbhost2 usbhost3" Similar older problem: https://forum.armbian.com/topic/7855-corrupted-armbianenvtxt-in-opz-fails-to-access-expansion-board/ If it doesn't work, check that uboot is not complaining about usbhost2.dtbo, usbhost3.dtbo What other tests did you do?

Look for successful or failure experiences in SBCs with the same ARM chip. For example, the banana pi zero m2 zero shares the same chip as the orange pi zero. Execute dmesg|grep w1 to see if the kernel module is loaded Look in the uboot messages, to see if there's an error applying the DTBO Use gpioinfo to see if PA6 is not already claimed by the kernel for something else